diff --git a/marked/Rel-11/29_series/29007/05da2a3257316bbf6f448a830dc0380a_img.jpg b/marked/Rel-11/29_series/29007/05da2a3257316bbf6f448a830dc0380a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7cca00a17d22a879ef358fa667544d68a7509c91 --- /dev/null +++ b/marked/Rel-11/29_series/29007/05da2a3257316bbf6f448a830dc0380a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5780b93bae90e80d060e98beb182b42a3a91dcf7e94d573696040cdb377a38e1 +size 39563 diff --git a/marked/Rel-11/29_series/29007/0f6e3cdce0f01d6ccceabcced508bb5b_img.jpg b/marked/Rel-11/29_series/29007/0f6e3cdce0f01d6ccceabcced508bb5b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b0d026e0d91b5224bca01e7ed7732a4f332458d3 --- /dev/null +++ b/marked/Rel-11/29_series/29007/0f6e3cdce0f01d6ccceabcced508bb5b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:06018bcd6dcfb3dac4f4338e664987f0b3cfa89d854d767740c3a06e282a8bc6 +size 37808 diff --git a/marked/Rel-11/29_series/29007/1399c76ef88f22b70d05ed3f781d3c48_img.jpg b/marked/Rel-11/29_series/29007/1399c76ef88f22b70d05ed3f781d3c48_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..367a782ba89f3fd3f6d7ecddc1f207e177b69dd2 --- /dev/null +++ b/marked/Rel-11/29_series/29007/1399c76ef88f22b70d05ed3f781d3c48_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4b696a6ee909a176a1d4d3ff9081f894f2071358a2600eb858e58c14c85add27 +size 32441 diff --git a/marked/Rel-11/29_series/29007/190217f95ce423a68d4a144cbd9df011_img.jpg b/marked/Rel-11/29_series/29007/190217f95ce423a68d4a144cbd9df011_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..176ad58dc048ed1e38eab3705ec824237487b2ec --- /dev/null +++ b/marked/Rel-11/29_series/29007/190217f95ce423a68d4a144cbd9df011_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:95db50ce49e52a6b9d381141dce83ceae2065be9b93d6ddbda5c7d66cf587c2b +size 45058 diff --git a/marked/Rel-11/29_series/29007/24a27d17656bcf0ee131539f2bbb34cd_img.jpg b/marked/Rel-11/29_series/29007/24a27d17656bcf0ee131539f2bbb34cd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9c353fc18f2216d2a06d14554fd96ddbd0f87f26 --- /dev/null +++ b/marked/Rel-11/29_series/29007/24a27d17656bcf0ee131539f2bbb34cd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:00006f9a731909a1c1e8e7153d93ecf4e7281d5cc6d594e1ebc75f7eb0b05bcc +size 48919 diff --git a/marked/Rel-11/29_series/29007/2734e7f9be3e1dc046f14be2e6c9a085_img.jpg b/marked/Rel-11/29_series/29007/2734e7f9be3e1dc046f14be2e6c9a085_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..28134ad1ddea2290269c63945c8cb201f28c1f27 --- /dev/null +++ b/marked/Rel-11/29_series/29007/2734e7f9be3e1dc046f14be2e6c9a085_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ea98921a03f78dc97f80741683a68843bc6cb355a96a49f2f6e600115a720155 +size 7742 diff --git a/marked/Rel-11/29_series/29007/29a9cd1cb2a960eb91dbf79aab5d8668_img.jpg b/marked/Rel-11/29_series/29007/29a9cd1cb2a960eb91dbf79aab5d8668_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b85bca846f29125a7c11f27e298aa6c24da380f9 --- /dev/null +++ b/marked/Rel-11/29_series/29007/29a9cd1cb2a960eb91dbf79aab5d8668_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:baaf88a60a1bb30cb99730e37810c48a85c5f7238788da22f95264e45abaadc3 +size 26484 diff --git a/marked/Rel-11/29_series/29007/303fadfb9def251d1575d6221199b158_img.jpg b/marked/Rel-11/29_series/29007/303fadfb9def251d1575d6221199b158_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6ab19a7cc878a893f81cdcddc1f0e5a2110f83f5 --- /dev/null +++ b/marked/Rel-11/29_series/29007/303fadfb9def251d1575d6221199b158_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e29807861654941c39f4b4feac9378648775de6c49ad97a69f7e1b9f81519cc5 +size 29650 diff --git a/marked/Rel-11/29_series/29007/32ff77da4286b58c4778033acaa10836_img.jpg b/marked/Rel-11/29_series/29007/32ff77da4286b58c4778033acaa10836_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..de9f9376d6440ce5dd57aa0b8a9e274c332ae553 --- /dev/null +++ b/marked/Rel-11/29_series/29007/32ff77da4286b58c4778033acaa10836_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0377de3c881d0b7f7e7b7c62e6e4d4951c2737d45609037bb192ddd55363110d +size 65870 diff --git a/marked/Rel-11/29_series/29007/4dd5f00d74e7db5bbb2d011609bcc43d_img.jpg b/marked/Rel-11/29_series/29007/4dd5f00d74e7db5bbb2d011609bcc43d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ec7e2bfa448acc9e4ced88fc3101b62a04d39fca --- /dev/null +++ b/marked/Rel-11/29_series/29007/4dd5f00d74e7db5bbb2d011609bcc43d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ae63bddb64d7ea1dd1ceb3c94eb297663e5a6af1a2b7f34d885c0e8421b1e8a0 +size 13387 diff --git a/marked/Rel-11/29_series/29007/659f4d3d272deea8021d0bb2e22465fd_img.jpg b/marked/Rel-11/29_series/29007/659f4d3d272deea8021d0bb2e22465fd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3b2cf6d6f78190fc8a192e509afc142af52daf87 --- /dev/null +++ b/marked/Rel-11/29_series/29007/659f4d3d272deea8021d0bb2e22465fd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:40535d86c1a1b0ab96de3c06ca2b1ad77c16b1af8e96802f5ee0d6cd016f417f +size 32541 diff --git a/marked/Rel-11/29_series/29007/7e1c9b51e067a48cd0fcc9748d8bd8d8_img.jpg b/marked/Rel-11/29_series/29007/7e1c9b51e067a48cd0fcc9748d8bd8d8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..41a5cb2c03d1c3e156b0ae07c8d392e006fdaad5 --- /dev/null +++ b/marked/Rel-11/29_series/29007/7e1c9b51e067a48cd0fcc9748d8bd8d8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2a3946fb0bb81adb5eb4d4ef96cf670d6aa4c66d36ec4d55b856b99054b68003 +size 54106 diff --git a/marked/Rel-11/29_series/29007/7fe4241eea8865aa6d2686d711c13ba6_img.jpg b/marked/Rel-11/29_series/29007/7fe4241eea8865aa6d2686d711c13ba6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5c73b388d40f6d370d0600326433a60ff333896b --- /dev/null +++ b/marked/Rel-11/29_series/29007/7fe4241eea8865aa6d2686d711c13ba6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9b048591c164d58260e50d03b6ae5051339f520cdd55990c081249c166167340 +size 16210 diff --git a/marked/Rel-11/29_series/29007/a0eb8d30ac11ba97b2733c187b89ff22_img.jpg b/marked/Rel-11/29_series/29007/a0eb8d30ac11ba97b2733c187b89ff22_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..015e4bf013ce7b9f6b23265242d49932120503fc --- /dev/null +++ b/marked/Rel-11/29_series/29007/a0eb8d30ac11ba97b2733c187b89ff22_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bace2e2f9391bb4265aa04e5f27551673c69fd60fde5a3fd37d37412c402aa26 +size 78099 diff --git a/marked/Rel-11/29_series/29007/a320e67b369bfde4a5fa360b100da55c_img.jpg b/marked/Rel-11/29_series/29007/a320e67b369bfde4a5fa360b100da55c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7c66945cd1ff93e629998daf2d8594e06aef429c --- /dev/null +++ b/marked/Rel-11/29_series/29007/a320e67b369bfde4a5fa360b100da55c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3c905e48202fefc629370b1342c951b45774bb381961813e9ee6e2831c2d8704 +size 162972 diff --git a/marked/Rel-11/29_series/29007/ced309874aec0546651b0976d5030a42_img.jpg b/marked/Rel-11/29_series/29007/ced309874aec0546651b0976d5030a42_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f1933dd8245e353c9373d226a0ee4f028eb5abbd --- /dev/null +++ b/marked/Rel-11/29_series/29007/ced309874aec0546651b0976d5030a42_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ec87845aa09f80ace1c386f2c63bdf0834595702fffc46ddfdd3f97024417c37 +size 15557 diff --git a/marked/Rel-11/29_series/29007/db0c433df107439122051d7b834cd262_img.jpg b/marked/Rel-11/29_series/29007/db0c433df107439122051d7b834cd262_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e047b7128d12b8ac0e4f6184ae9ac97c3459d14e --- /dev/null +++ b/marked/Rel-11/29_series/29007/db0c433df107439122051d7b834cd262_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7952b10f739a28aa99d3f8184baf672557f58b29fe2079ff41dfe9b9f5c82d7d +size 20656 diff --git a/marked/Rel-11/29_series/29007/ddee3e67e0dfc22e25188fa635a19558_img.jpg b/marked/Rel-11/29_series/29007/ddee3e67e0dfc22e25188fa635a19558_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bfdb8ce2db74e84e12cf7c3f6b30cf98bebbf8b4 --- /dev/null +++ b/marked/Rel-11/29_series/29007/ddee3e67e0dfc22e25188fa635a19558_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3e5cced3bc5d5e4eab944a1ddb89e45e9cd7ddeec8e45d65af15c98b9970fc1e +size 55880 diff --git a/marked/Rel-11/29_series/29007/eb03559a4d92ea9ebd63ea9be663c50a_img.jpg b/marked/Rel-11/29_series/29007/eb03559a4d92ea9ebd63ea9be663c50a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..95e1fa6629d1913f4f8a28aa74f815ed267ad2b1 --- /dev/null +++ b/marked/Rel-11/29_series/29007/eb03559a4d92ea9ebd63ea9be663c50a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9e819df31ad4ff6f5c01037dd1eea3d8b0cc8b4cf6f4754df1650df56466ea33 +size 53187 diff --git a/marked/Rel-11/29_series/29007/f0a97d0d3818a253c1d2a009966081b1_img.jpg b/marked/Rel-11/29_series/29007/f0a97d0d3818a253c1d2a009966081b1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e04988d5828cc7bfb3e171e48c490c14466e633a --- /dev/null +++ b/marked/Rel-11/29_series/29007/f0a97d0d3818a253c1d2a009966081b1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a23e11dbe4a158257b6e1500fd72519eef87347f023f853106f3a5aefe0fb200 +size 11439 diff --git a/marked/Rel-11/29_series/29007/f59ced6eaab3181501fc23fdfb52297e_img.jpg b/marked/Rel-11/29_series/29007/f59ced6eaab3181501fc23fdfb52297e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5b4ac8f17ce5be8bedfca89f2e026021ebc5989d --- /dev/null +++ b/marked/Rel-11/29_series/29007/f59ced6eaab3181501fc23fdfb52297e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b312203347f9f2246bc8b705a49744cb9c95b3567011b310a037da4caecaf1cd +size 41721 diff --git a/marked/Rel-11/29_series/29007/raw.md b/marked/Rel-11/29_series/29007/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..c30a905779216e4493350310a1b10b6dcbf0f869 --- /dev/null +++ b/marked/Rel-11/29_series/29007/raw.md @@ -0,0 +1,3742 @@ + + + + +GSM® and the GSM logo are registered and owned by the GSM Association + +# Contents + +| | | +|-------------------------------------------------------------------------------|----| +| Foreword ..... | 8 | +| 1 Scope..... | 9 | +| 2 References..... | 9 | +| 3 Definitions and abbreviations ..... | 14 | +| 3.1 Definitions..... | 14 | +| 3.2 Abbreviations ..... | 15 | +| 4 Introduction..... | 15 | +| 5 Void..... | 16 | +| 6 Network Characteristics..... | 16 | +| 6.1 Key Characteristics of Networks Concerned ..... | 16 | +| 6.1.1 Characteristics of PLMNs ..... | 16 | +| 6.1.2 Characteristics of PSTNs..... | 16 | +| 6.1.3 Characteristics of ISDN..... | 17 | +| 7 Interworking classifications ..... | 17 | +| 7.1 Service interworking ..... | 17 | +| 7.2 Network interworking ..... | 17 | +| 7.3 Signalling interworking..... | 18 | +| 7.4 Numbering..... | 18 | +| 7.5 Supplementary service interworking..... | 18 | +| 8 Compatibility and subscription checking..... | 18 | +| 9 Interworking to PSTN..... | 19 | +| 9.1 Speech Calls..... | 19 | +| 9.1.1 Interworking indications to PLMN terminal ..... | 19 | +| 9.1.2 Transmission aspects..... | 19 | +| 9.1.3 Generation of In-band Tones and Announcements (PLMN-PSTN) ..... | 19 | +| 9.2 Data Calls..... | 19 | +| 9.2.1 Network interworking mobile originated ..... | 20 | +| 9.2.1.1 Selection of interworking function ..... | 20 | +| 9.2.1.2 Modem Selection..... | 20 | +| 9.2.1.3 Mapping of BC-IE from PLMN to ISUP (or other) ..... | 21 | +| 9.2.2 Network Interworking Mobile terminated PSTN Originated..... | 21 | +| 9.2.2.1 Multi-numbering Scheme ..... | 21 | +| 9.2.2.2 Single-numbering Scheme..... | 23 | +| 9.2.3 Transparent service support..... | 24 | +| 9.2.3.1 Structure of the MSC/IWF for Iu mode..... | 25 | +| 9.2.3.2 Structure of the MSC/IWF for A/Gb mode ..... | 25 | +| 9.2.3.3 Mapping of signalling UE/MSC/IWF to modem interface requirements..... | 25 | +| 9.2.3.4 Establishment of end-to-end terminal synchronizations..... | 26 | +| 9.2.3.4.1 Terminating side (towards the UE)..... | 27 | +| 9.2.3.4.1.1 Traffic channel types TCH/F4.8 and TCH/F9.6 for A/Gb mode ..... | 27 | +| 9.2.3.4.1.2 Traffic channel type TCH/F14.4 for A/Gb mode ..... | 27 | +| 9.2.3.4.2 Transit side (towards the fixed network)..... | 28 | +| 9.2.3.5 Network Independent Clocking (NIC) ..... | 28 | +| 9.2.4 Non-transparent service support..... | 29 | +| 9.2.4.1 Structure of the MSC/IWF for Iu mode..... | 29 | +| 9.2.4.2 Structure of the MSC/IWF for A/Gb mode ..... | 29 | +| 9.2.4.3 Re-constitution of user data ..... | 29 | +| 9.2.4.4 Layer 2 relay functionality..... | 29 | +| 9.2.4.5 In band signalling mapping flow control..... | 30 | +| 9.2.4.5.1 Conditions requiring flow control towards the fixed network ..... | 30 | +| 9.2.4.5.2 Conditions requiring flow control towards the UE ..... | 30 | +| 9.2.4.6 Data buffers..... | 30 | +| 9.2.4.6.1 Transmit buffers (towards UE) ..... | 30 | + +| | | | +|--------------|---------------------------------------------------------------------------------------------------|----| +| 9.2.4.6.2 | Receive buffers (from UE)..... | 31 | +| 9.2.4.7 | Transportation of the Break condition..... | 31 | +| 9.2.4.8 | In band signalling mapping modem status information..... | 31 | +| 9.2.4.9 | Support of out-band flow control..... | 32 | +| 9.2.4.10 | Establishment of end-to-end terminal synchronizations..... | 32 | +| 9.2.4.10.1 | Terminating side (towards the UE)..... | 32 | +| 9.2.4.10.2 | Transit side (towards the fixed network)..... | 32 | +| 9.2.4.11 | Data compression..... | 33 | +| 9.2.4.12 | Service level up and down grading..... | 33 | +| 9.2.5 | DTE/DCE interface (Filtering)..... | 33 | +| 9.3 | Interworking Alternate Speech / Facsimile Group 3 Calls ..... | 34 | +| 9.3.1 | General ..... | 34 | +| 9.3.2 | Mobile originated PSTN terminated calls ..... | 35 | +| 9.3.3 | PSTN originated mobile terminated calls..... | 35 | +| 9.3.4 | BICC network architecture..... | 35 | +| 9.4 | 3G-H.324/M calls over 3,1kHz audio ..... | 35 | +| 9.4.1 | Mobile originated multimedia call ..... | 36 | +| 9.4.1.1 | Call setup ..... | 36 | +| 9.4.1.2 | Fallback to speech after setup..... | 36 | +| 9.4.2 | Mobile terminated multimedia call ..... | 36 | +| 9.4.2.1 | Call setup ..... | 36 | +| 9.4.2.2 | Fallback to speech after setup..... | 37 | +| 9.4.3 | Seamless data rate change ..... | 37 | +| 10 | Interworking to the ISDN ..... | 37 | +| 10.1 | Speech Calls..... | 38 | +| 10.2 | Data Calls..... | 38 | +| 10.2.1 | Network interworking mobile originated ..... | 38 | +| 10.2.2 | Network interworking mobile terminated ..... | 38 | +| 10.2.2.1 | General..... | 38 | +| 10.2.2.2 | Functions in GMSC ..... | 39 | +| 10.2.2.3 | Functions in HLR..... | 39 | +| 10.2.2.4 | Functions in VMSC ..... | 40 | +| 10.2.2.4A | Functions in VLR..... | 41 | +| 10.2.2.5 | Call Flows..... | 43 | +| 10.2.2.6 | Mapping Functions ..... | 44 | +| 10.2.2.7 | Creation of Backup Bearer Capability Information Element ..... | 60 | +| 10.2.3 | Transparent service support..... | 66 | +| 10.2.3.1 | Structure of the MSC/IWF for Iu mode..... | 66 | +| 10.2.3.2 | Structure of the MSC/IWF for A/Gb mode ..... | 66 | +| 10.2.3.3 | Mapping of signalling UE/MSC/IWF to modem or ISDN (V.110) TA-function interface requirements..... | 66 | +| 10.2.3.4 | Establishment of end-to-end terminal synchronizations..... | 67 | +| 10.2.3.4.1 | Terminating side (towards the UE)..... | 68 | +| 10.2.3.4.1.1 | Traffic channel types TCH/F4.8 and TCH/F9.6 in A/Gb mode..... | 68 | +| 10.2.3.4.1.2 | Traffic channel type TCH/F14.4 for A/Gb mode ..... | 68 | +| 10.2.3.4.1.3 | User Plane for Iu mode..... | 68 | +| 10.2.3.4.2 | Transit side (towards the fixed network)..... | 68 | +| 10.2.3.5 | Network independent Clocking (NIC)..... | 69 | +| 10.2.4 | Non-transparent service support..... | 69 | +| 10.2.4.1 | Structure of the MSC/IWF for Iu mode..... | 69 | +| 10.2.4.2 | Structure of the MSC/IWF for A/Gb mode ..... | 69 | +| 10.2.4.3 | Re-constitution of user data ..... | 70 | +| 10.2.4.4 | Layer 2 relay functionality..... | 70 | +| 10.2.4.5 | In band signalling mapping flow control..... | 70 | +| 10.2.4.5.1 | Conditions requiring flow control - if flow control is provided - towards the fixed network . | 71 | +| 10.2.4.5.2 | Conditions requiring flow control towards the UE ..... | 71 | +| 10.2.4.6 | Data buffers..... | 71 | +| 10.2.4.6.1 | Transmit buffers (towards UE) ..... | 71 | +| 10.2.4.6.2 | Receive buffers (from UE)..... | 71 | +| 10.2.4.7 | BREAK Indication..... | 72 | + +| | | | +|---------------|-------------------------------------------------------------------------------------------------|----| +| 10.2.4.8 | Signalling mapping of modem or ISDN (V.110, V.120 or PIAFS) TA-function status information..... | 72 | +| 10.2.4.9 | Support of out-band flow control..... | 72 | +| 10.2.4.10 | Synchronizations..... | 73 | +| 10.2.4.10.1 | V.110 and V.120 Frame synchronizations ..... | 73 | +| 10.2.4.10.2 | RLP Frame start indication ..... | 73 | +| 10.2.4.10.3 | L2R Frame synchronizations ..... | 73 | +| 10.2.4.10.4 | Establishment of end-to-end terminal synchronizations ..... | 73 | +| 10.2.4.10.4.1 | Terminating side (towards the UE) ..... | 73 | +| 10.2.4.10.4.2 | Transit side (towards the fixed network)..... | 73 | +| 10.2.4.11 | Data compression..... | 74 | +| 10.2.4.12 | Additional aspects of V.120 Interworking..... | 74 | +| 10.2.4.12.1 | V.120 Signalling parameters ..... | 74 | +| 10.2.4.12.2 | V.120 Protocol parameters..... | 74 | +| 10.2.4.12.3 | Data compression on the ISDN..... | 74 | +| 10.2.4.12.4 | Use of the V.120 Control State (header extension) octet..... | 75 | +| 10.2.4.13 | Interworking with restricted 64 kbit/s networks ..... | 75 | +| 10.2.4.13.1 | Rate adaptation..... | 75 | +| 10.2.4.13.2 | MSC - ISDN signalling..... | 75 | +| 10.2.4.14 | Service level up and down grading..... | 75 | +| 10.2.4.15 | Interworking in Frame Tunneling Mode ..... | 75 | +| 10.2.4.16 | Additional aspects of PIAFS Interworking..... | 76 | +| 10.2.5 | DTE/DCE interface (Filtering)..... | 76 | +| 10.3 | Interworking Alternate speech facsimile group 3 calls..... | 76 | +| 10.3.1 | Alternate speech data bearer interworking..... | 76 | +| 10.3.1.1 | General..... | 76 | +| 10.3.1.2 | Mobile originated ISDN terminated ..... | 77 | +| 10.3.1.3 | ISDN originated mobile terminated..... | 77 | +| 10.4 | 3G-H.324/M calls over UDI/RDI..... | 77 | +| 10.4.1 | Mobile originated multimedia call ..... | 77 | +| 10.4.1.1 | Call setup ..... | 77 | +| 10.4.1.2 | Fallback after setup..... | 78 | +| 10.4.1.3 | User initiated service change after setup ..... | 78 | +| 10.4.2 | Mobile terminated multimedia call ..... | 78 | +| 10.4.2.1 | Call setup ..... | 78 | +| 10.4.2.2 | User initiated service change after setup ..... | 78 | +| 11 | Interworking between A/Gb mode MSC and Iu mode MSC ..... | 78 | +| 11.0 | Signalling issues..... | 78 | +| 11.0.1 | Loss of BC Information during Handover from A/Gb mode to UTRAN Iu mode..... | 78 | +| 11.0.2 | Handover from UTRAN Iu mode to A/Gb mode..... | 79 | +| 11.0.3 | Loss of BC Information during Handover from A/Gb mode to GERAN Iu mode ..... | 79 | +| 11.0.4 | Handover from GERAN Iu mode to A/Gb mode..... | 79 | +| 11.0.5 | Handover from UTRAN Iu mode to GERAN Iu mode ..... | 79 | +| 11.0.6 | Handover from GERAN Iu mode to UTRAN Iu mode ..... | 80 | +| 11.1 | Handover to A/Gb mode MSC..... | 80 | +| 11.2 | Handover from A/Gb mode MSC to UTRAN Iu mode MSC..... | 80 | +| 11.3 | Handover from A/Gb mode MSC to GERAN Iu mode MSC..... | 81 | +| 11.3.1 | User plane for transparent services..... | 81 | +| 11.3.2 | User plane for non-transparent services ..... | 81 | +| 11.4 | Handover within Iu mode PLMNs..... | 81 | +| 11.5 | Handover for 56kbit/s..... | 82 | +| 11.6 | Void..... | 83 | +| 11a | Transport Protocols ..... | 83 | +| 11a.1 | Core Network ..... | 83 | +| 11a.1.0 | Overview ..... | 83 | +| 11a.1.1 | Void ..... | 84 | +| 11a.1.2 | Transport beyond the IWF..... | 84 | +| 11a.1.2.1 | UDI and RDI..... | 84 | +| 11a.1.2.2 | Modem..... | 84 | +| 11a.1.3 | Transport on the access side of the IWF..... | 84 | + +| | | | +|-------------------------------|----------------------------------------------------------------------------------------------------------------|------------| +| 11a.1.3.0 | Inter MSC-Relocation..... | 84 | +| 11a.1.3.0a | Several MGWs controlled by same MSC server ..... | 85 | +| 11a.1.3.1 | Non-Transparent CSD ..... | 86 | +| 11a.1.3.2 | Transparent CSD..... | 88 | +| 11a.2 | NT services..... | 90 | +| 11a.2.1 | Iu interface and Nb interface at access side of IWF in a BICC based CS CN ..... | 90 | +| 11a.2.2 | Nb interface at access side of IWF in a BICC based CS CN for Inter-MSC relocation ..... | 90 | +| 11a.2.3 | Nb interface at network side of IWF in a BICC based CS CN ..... | 90 | +| 11a.2.4 | Nb interface at access side of IWF in a SIP-I based CS CN ..... | 90 | +| 11a.2.5 | Nb interface at network side of IWF in a SIP-I based CS CN ..... | 91 | +| 11a.2.6 | A interface with IP transport ..... | 91 | +| 11a.3 | T services..... | 91 | +| 11a.3.0 | Iu interface..... | 91 | +| 11a.3.0a | Nb interface in BICC based CS CN ..... | 91 | +| 11a.3.1 | Avoidance of delay at RNC..... | 91 | +| 11a.3.2 | Recovery from the loss of ATM cells ..... | 92 | +| 11a.3.3 | A interface with IP transport ..... | 92 | +| 11a.3.4 | Nb interface at access side of IWF in a SIP-I based CS CN ..... | 92 | +| 11a.3.5 | Nb interface at network side of IWF in a SIP-I based CS CN ..... | 92 | +| 12 | Frame Synchronization ..... | 92 | +| 12.1 | Initial frame synchronization ..... | 93 | +| 12.1.1 | Terminating side (towards the UE) ..... | 93 | +| 12.1.2 | Transit side (towards the fixed network)..... | 93 | +| 12.1.2.1 | Interworking to the PSTN..... | 93 | +| 12.1.2.2 | Interworking to the ISDN ..... | 93 | +| 12.2 | Action on loss of frame synchronization..... | 93 | +| 12.2.1 | Loss on the transit side (towards the fixed network)..... | 93 | +| 12.2.2 | Loss on the terminating side (towards the UE) ..... | 93 | +| 13 | Call Clearing ..... | 94 | +| 14 | The A-TRAU Framing Protocols..... | 94 | +| 14.1 | A-TRAU' Protocol ..... | 94 | +| 14.1.1 | Frame layout for the different transparent user rates..... | 94 | +| 14.1.2 | A-TRAU' frame format ..... | 95 | +| 14.2 | A-TRAU'' Protocol ..... | 97 | +| 15 | RTP Payload Type Negotiation for Data Calls within a SIP-I based CS Core Network..... | 99 | +| 15.1 | RTP payload type negotiation at access side of IWF..... | 99 | +| 15.2 | RTP payload type negotiation at network side of IWF ..... | 99 | +| Annex A (informative): | SDLs..... | 100 | +| Annex B (informative): | General mapping of V.24 circuits to channel status bits ..... | 102 | +| Annex C (normative): | RTP payload type for SCUDIF in SIP-I based CS core network .... | 102 | +| C.1 | Scope ..... | 102 | +| C.2 | RTP payload Type definition ..... | 103 | +| C.3 | Describing the RTP payload Type in SDP..... | 103 | +| C.4 | SDP Offer-Answer considerations ..... | 103 | +| C.5 | SDP Example ..... | 103 | +| Annex D (informative): | IANA registration information for RTP payload types for SCUDIF
in SIP-I based CS core network ..... | 104 | +| D.1 | Introduction ..... | 104 | +| D.2 | IANA Registration information ..... | 104 | +| D.2.1 | Media Type Name ..... | 104 | +| D.2.2 | Subtype Name ..... | 104 | +| D.2.3 | Required parameters ..... | 104 | +| D.2.4 | Optional parameters..... | 104 | +| D.2.5 | Encoding considerations..... | 104 | +| D.2.6 | Security considerations..... | 104 | +| D.2.7 | Interoperability considerations ..... | 104 | + +| | | | +|------------------------|-------------------------------------------------|-----| +| D.2.8 | Published specification..... | 104 | +| D.2.9 | Applications which use this media type ..... | 105 | +| D.2.10 | Additional information ..... | 105 | +| D.2.10.1 | Magic number(s)..... | 105 | +| D.2.10.2 | File extension(s)..... | 105 | +| D.2.10.3 | Macintosh File Type Code(s)..... | 105 | +| D.2.10.2 | Object Identifier(s) or OID(s) ..... | 105 | +| D.2.11 | Intended usage ..... | 105 | +| D.2.12 | Other Information/General Comment ..... | 105 | +| D.2.13 | Person to contact for further information ..... | 105 | +| Annex E (informative): | Change history..... | 106 | + +# --- Foreword + +This Technical Specification (TS) has been produced by the 3rd Generation Partnership Project (3GPP). + +The present document identifies the Mobile-services Switching Centre/Interworking functions (MSC/IWFs) and requirements to support interworking between: + +- i) PLMN and PSTN; +- ii) PLMN and ISDN; + +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 identifies the Mobile-services Switching Centre/Interworking Functions (MSC/IWFs) and requirements to support interworking between: + +- a) PLMN and PSTN; +- b) PLMN and ISDN; + +for circuit switched services in the PLMN. It is not possible to treat ISDN and PSTN as one type of network, even when both ISDN and PSTN subscribers are served by the same exchange because of the limitations of the PSTN subscribers access i.e. analogue connection without D-channel signalling. + +Within the present document, the requirements for voice and non-voice (data) calls are considered separately. + +From R99 onwards the following services are no longer required by a PLMN: + +- the dual Bearer Services "alternate speech/data" (BS 61) and "speech followed by data" (BS 81); +- the dedicated services for PAD (BS 4x) and Packet access (BS 5x); +- the single asynchronous and synchronous Bearer Services (BS 21..26, BS 31..34). + +From Rel-4 onwards the following services are no longer required by a PLMN: + +- the synchronous Bearer Service non-transparent (BS 30 NT); +- the Basic Packet access; +- Non-transparent facsimile (TS 61/62 NT) for the A/Gb mode and GERAN Iu mode. + +If a PLMN still provides these services it shall fulfil the specification of former releases. + +The present document is valid for a PLMN in A/Gb mode as well as in Iu mode. If text applies only for one of these systems it is explicitly mentioned by using the terms "A/Gb mode" and "Iu mode". If text applies to both of the systems, but a distinction between the ISDN/PSTN and the PLMN is necessary, the term "PLMN" is used. + +NOTE: The Gb interface does not play any role in the scope of the present document although the term "A/Gb mode" is used. + +# --- 2 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. +- For a specific reference, subsequent revisions do not apply. +- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. + +- [1] ITU-T Recommendation G.711 (11/88): "Pulse Code Modulation (PCM) of voice frequencies". +- [2] ITU-T Recommendation I.460 (02/99): "Multiplexing, rate adaption and support of existing interfaces". +- [3] ITU-T Recommendation I.464 (02/99): "Multiplexing, rate adaption and support of existing interfaces for restricted 64 kbit/s transfer capability". +- [4] ITU-T Recommendation Q.922 (1992): "DSS 1 Data link layer: ISDN data link layer specification for frame mode bearer services". + +- [5] ITU-T Recommendation Q.931 (05/98): "DSS 1 - ISDN user network interface layer 3 specification for basic call control". +- [6] ITU-T Recommendation V.22 (11/88): "1200 bits per second duplex modem standardized for use in the general switched telephone network and on point-to-point 2-wire leased telephone-type circuits". +- [7] ITU-T Recommendation V.24: "List of definitions for interchange circuits between data terminal equipment (DTE) and data circuit-terminating equipment (DCE)". +- [8] ITU-T Recommendation V.25 (10/96): "Automatic answering equipment and general procedures for automatic calling equipment on the general switched telephone network including procedures for disabling of echo control devices for both manually and automatically established calls". +- [9] ITU-T Recommendation V.32 (03/93): "A family of 2-wire, duplex modems operating at data signalling rates of up to 9600 bit/s for use on the general switched telephone network and on leased telephone-type circuits". +- [10] ITU-T Recommendation V.32bis (02/91): "A duplex modem operating at data signalling rates of up to 14 400 bit/s for use on the general switched telephone network and on leased point-to-point 2-wire telephone-type circuits". +- [11] ITU-T Recommendation V.34 (02/98): "A modem operating at data signalling rates of up to 33 600 bit/s for use on the general switched telephone network and on leased point-to-point 2-wire telephone-type circuits". +- [12] ITU-T Recommendation V.42 (03/02): "Error-correcting procedures for DCEs using asynchronous-to-synchronous conversion". +- [13] ITU-T Recommendation V.42bis (01/90): "Data compression procedures for Data Circuit Terminating Equipment (DCE) using error correction procedures". +- [14] ITU-T Recommendation V.90 (09/98): "A digital modem and analogue modem pair for use on the Public Switched Telephone Network (PSTN) at data signalling rates of up to 56 000 bit/s downstream and up to 33 600 bit/s upstream". +- [15] ITU-T Recommendation V.110: "Support by an ISDN of data terminal equipments with V-Series type interfaces". +- [16] ITU-T Recommendation V.120 (10/96): "Support by an ISDN of data terminal equipment with V-Series type interfaces with provision for statistical multiplexing". +- [17] ETSI ETR 018 (11/95): "Integrated Services Digital Network (ISDN); Application of the Bearer Capability (BC), High Layer Compatibility (HLC) and Low Layer Compatibility (LLC) information elements by terminals supporting ISDN services". +- [18] ETSI ETS 300 102-1 Edition 1 (1990): "Integrated Services Digital Network (ISDN); User-network interface layer 3; Specifications for basic call control". +- [19] ETSI EN 300 403-1 V1.2.2 (1998-04): "Integrated Services Digital Network (ISDN); Digital Subscriber Signalling System No. one (DSS1) protocol; Signalling network layer for circuit-mode basic call control; Part 1: Protocol specification". +- [20] 3GPP TS 41.103: "GSM Release 5 specifications". +- [21] 3GPP TR 21.905: "Vocabulary for 3GPP specifications" +- [22] 3GPP TS 22.001: "Principles of circuit telecommunication services supported by a Public Land Mobile Network (PLMN)". +- [23] 3GPP TS 22.003: "Circuit teleservices supported by a Public Land Mobile Network (PLMN)". +- [24] 3GPP TS 43.010: "GSM Public Land Mobile Network (PLMN) connection types ". +- [25] 3GPP TS 43.045: "Technical realization of facsimile group 3 service - transparent". + +- [26] 3GPP TS 43.050: "Transmission planning aspects of the speech service in the GSM Public Land Mobile Network (PLMN) system". +- [27] 3GPP TS 44.021: "Rate adaption on the Mobile Station - Base Station System (MS - BSS) interface". +- [28] 3GPP TS 48.020: "Rate adaption on the Base Station System - Mobile-services Switching Centre (BSS - MSC) interface". +- [29] 3GPP TS 48.060: "Inband control of remote transcoders and rate adaptors for full rate traffic channels". +- [30] 3GPP TS 09.02 : "Mobile Application Part (MAP) specification GSM Phase 1". +- [31] 3GPP TS 49.003: "Signalling requirements on interworking between the Integrated Services Digital Network (ISDN) or Public Switched Telephone Network (PSTN) and the Public Land Mobile Network (PLMN)". +- [32] 3GPP TS 21.103: "3rd Generation mobile system Release 5 specifications ". +- [33] 3GPP TS 22.002: "Circuit Bearer Services (BS) supported by a Public Land Mobile Network (PLMN)". +- [34] 3GPP TS 22.004: "General on supplementary services". +- [35] 3GPP TS 23.003: "Numbering, addressing and identification". +- [36] 3GPP TS 23.008: "Organization of subscriber data". +- [37] 3GPP TS 23.011: "Technical realization of supplementary services". +- [38] 3GPP TS 23.146: "Technical realization of facsimile group 3 non-transparent". +- [39] Void. +- [40] 3GPP TS 24.008: "Mobile radio interface layer 3 specification; Core network protocols; Stage 3". +- [41] 3GPP TS 24.022: "Radio Link Protocol (RLP) for circuit switched bearer and teleservices ". +- [42] 3GPP TS 25.415: "UTRAN Iu interface user plane protocols". +- [43] 3GPP TS 27.001: "General on Terminal Adaptation Functions (TAF) for Mobile Stations (MS)". +- [44] 3GPP TS 27.002: "Terminal Adaptation Functions (TAF) for services using Asynchronous bearer capabilities". +- [45] 3GPP TS 27.003: "Terminal Adaptation Functions (TAF) for services using Synchronous bearer capabilities". +- [46] 3GPP TS 29.002: "Mobile Application Part (MAP) specification". +- [47] 3GPP TS 24.002: "GSM - UMTS Public Land Mobile Network (PLMN) access reference configuration " +- [48] ISO/IEC 3309 (1993): "Information technology - Telecommunications and information exchange between systems - High-level Data Link Control (HDLC) procedures - Frame structure". +- [49] IETF RFC 1662: "PPP in HDLC-like framing". +- [50] Mobile Internet Access Forum: "PIAFS Specification Ver. 1.1, 2.1". +- [51] ITU-T Recommendation V.8: "Procedures for starting sessions of data transmission over the public switched telephone network". +- [52] 3GPP TS 26.111: "Codec for circuit switched multimedia telephony service; Modifications to H.324". + +- [53] Void +- [54] ITU-T Recommendation H.223 (03/96): "Multiplexing protocol for low bit rate multimedia communication". +- [55] ITU-T Recommendation H.223 (Annex A) (02/98): "Multiplexing protocol for low bit rate multimedia communication over low error-prone channels". +- [56] ITU-T Recommendation H.223 (Annex B) (02/98): "Multiplexing protocol for low bit rate multimedia communication over moderate error-prone channels". +- [57] ITU-T Recommendation H.223 (Annex C) (02/98): "Multiplexing protocol for low bit rate multimedia communication over highly error-prone channels". +- [58] ITU-T Recommendation H.324: "Terminal for low bit-rate multimedia communication". +- [59] ITU-T Recommendation H.221: "Frame structure for a 64 to 1920 kbit/s channel in audiovisual teleservices". +- [60] ITU-T Recommendation H.242: "System for establishing communication between audiovisual terminals using digital channels up to 2 Mbit/s". +- [61] ITU-T Recommendation H.245: "Control protocol for multimedia communication". +- [62] ITU-T Recommendation V.8 bis: "Procedures for the identification and selection of common modes of operation between data circuit-terminating equipments (DCEs) and between data terminal equipments (DTEs) over the public switched telephone network and on leased point-to-point telephone-type circuits". +- [63] ITU-T Recommendation V.21 (11/88): "300 bits per second duplex modem standardized for use in the general switched telephone network". +- [64] ITU-T Recommendation V.22bis (1988): "2400 bits per second duplex modem using the frequency division technique standardized for use on the general switched telephone network and on point-to-point 2-wire leased telephone-type circuits". +- [65] ITU-T Recommendation V.23 (11/88): "600/1200-baud modem standardized for use in the general switched telephone network". +- [66] ITU-T Recommendation V.26 (11/88): "2400 bits per second modem standardized for use on 4-wire leased telephone-type circuits". +- [67] ITU-T Recommendation V.26 bis (11/88): "2400/1200 bits per second modem standardized for use in the general switched telephone network". +- [68] ITU-T Recommendation V.26 ter (11/88): "2400 bits per second duplex modem using the echo cancellation technique standardized for use on the general switched telephone network and on point-to-point 2-wire leased telephone-type circuits". +- [69] ITU-T Recommendation V.27 (11/88): "4800 bits per second modem with manual equalizer standardized for use on leased telephone-type circuits". +- [70] ITU-T Recommendation V.27 bis (11/88): "4800/2400 bits per second modem with automatic equalizer standardized for use on leased telephone-type circuits". +- [71] ITU-T Recommendation V.29 (11/88): "9 600 bits per second modem standardized for use on point-to-point 4-wire leased telephone-type circuits". +- [72] ITU-T Recommendation Q.921 (09/97): "ISDN user-network interface - Data link layer specification". +- [73] ITU-T Recommendation X.21 (09/92): "Interface between Data Terminal Equipment (DTE) and Data Circuit-terminating Equipment (DCE) for synchronous operation on public data networks". + +- [74] ITU-T Recommendation X.25 (10/96): "Interface between Data Terminal Equipment (DTE) and Data Circuit - terminating Equipment (DCE) for terminals operating in the packet mode and connected to public data networks by dedicated circuit". +- [75] ITU-T Recommendation X.28 (12/97): "DTE/DCE interface for a start-stop mode Data Terminal Equipment accessing the Packet Assembly/Disassembly facility (PAD) in a public data network situated in the same country". +- [76] ITU-T Recommendation X.31 (11/95): "Support of packet mode terminal equipment by an ISDN". +- [77] ITU-T Recommendation X.75 (10/96): "Packet-switched signalling system between public networks providing data transmission services". +- [78] ISO 2110 (1989): "Information technology - Data communication - 25-pole DTE/DCE interface connector and contact number assignments". +- [79] ISO/IEC 6429 (1992): "Information technology - Control functions for coded character sets". +- [80] 3GPP TS 29.415: "Core Network Nb Interface User Plane Protocols" +- [81] ITU-T Recommendation I.366.2: "AAL type 2 service specific convergence sublayer for trunking". +- [82] 3GPP TS 29.232: "Media Gateway Controller (MGC); Media Gateway (MGW) interface; Stage 3" +- [83] 3GPP TS 23.172: "Technical Realisation of the Circuit Switched (CS) multimedia service; UDI/RDI fallback and service modification; Stage 2" +- [84] ITU-T Recommendation E.163 (11/88): "Numbering plan for the international telephone service". +- [85] ITU-T Recommendation E.164 (02/05): "The international public telecommunication numbering plan". +- [86] 3GPP TS 27.001: "General on Terminal Adaption Functions (TAF) for Mobile Station (MS)". +- [87] ITU-T Recommendation I.363.2: "B-ISDN ATM Adaptation Layer specification : Type 2 AAL". +- [88] ITU-T Recommendation I.366.2: "AAL type 2 service specific convergence sublayer for narrow-band services". +- [89] ITU-T Recommendation Q.2630.1 (12/99): "AAL type 2 signalling protocol (Capability Set 1)". +- [90] 3GPP TS 23.202: "Circuit switched data bearer services". +- [91] 3GPP TS 23.153: "Out of band transcoder control; Stage 2". +- [92] IETF RFC 4040: "RTP Payload Format for a 64 kbit/s Transparent Call " +- [93] 3GPP TS 29.414: "Core network Nb data transport and transport signalling ". +- [94] IETF RFC 2198: "RTP Payload for Redundant Audio Data". +- [95] IETF RFC 3551: "RTP Profile for Audio and Video Conferences with Minimal Control". +- [96] ITU-T Recommendation T.38: "Procedures for real-time Group 3 facsimile communication over IP networks" +- [97] IETF RFC 3362: "Real-time Facsimile (T.38) - image/t38 MIME Sub-type Registration" +- [98] IETF RFC 4566: "SDP: Session Description Protocol". +- [99] 3GPP TS 23.231: "SIP-I based Circuit Switched Core Network; Stage 2" + +# --- 3 Definitions and abbreviations + +## 3.1 Definitions + +For the purposes of the present document, the following terms and definitions apply: + +**bearer capability information:** specific information defining the lower layer characteristics required within the network. + +**low layer compatibility information:** information defining the lower layer characteristics of the terminal. + +**high layer compatibility information:** information defining the higher layer characteristics of the terminal. + +**compatibility information:** this term subsumes the entirety of Bearer Capability, Low Layer Compatibility, High Layer Compatibility, Progress Indicator and Address Information conveyed out-of-band prior to call establishment for the support of compatibility checking and terminal/function/service selection at the ISDN-type user-network interface. + +**protocol identifier:** information defining the specific protocols utilized for the support of data transfer by a terminal. + +**progress indicator:** information supplied to indicate to the terminal that network interworking has taken place. + +**out-of-band parameter exchange:** information exchanged via an associated or non-associated signalling link e.g. SS No 7. + +**PSTN:** subscriber to network interface supports only analogue terminals. + +**ISDN:** subscriber to network interface supports digital or analogue terminals, plus a standardized user to network associated signalling system and a standardized internetwork signalling system. + +**autobauding type 1:** this information element value may be contained in the setup or call confirm messages from the UE in association with a non transparent data service. This implies that the MSC/IWF may select any speed and modem type according to what it can negotiate with the remote modem on the PSTN/ISDN. The parameters User Rate and FNUR (Fixed Network User Rate), if present, has no meaning when Modem Type is autobauding type 1. + +**Multi self selecting speed modem:** this term applies to V series modems capable of handling one or more lower speeds as a fall back position. When such a modem is requested in the call setup or call confirm message from the UE in association with a non transparent service, the MSC/IWF may select any of the speeds supported according to the negotiation with the remote modem on the PSTN/ISDN. The parameters User Rate and FNUR (Fixed Network User Rate), if present, has no meaning when Modem Type is autobauding type 1. + +**Unrestricted 64 kbit/s network:** a digital network which has 64 kbit/s octet-structured Information Transfer Capability (ITC) with no restrictions on the contents of each octet. + +**restricted 64 kbit/s network:** ITU-T Recommendation I.464 defines "restricted 64 kbit/s transfer capability" as "64 kbit/s octet-structured capability with the exception that an all-zero octet is not permitted". In the present document, the term "restricted 64 kbit/s network" refers not only to networks with the ITU-T Recommendation I.464 restriction but also to those in which the 8th bit of each octet is unusable for data transmission. + +**directly connected restricted 64 kbit/s network:** restricted 64 kbit/s network which is connected directly to the MSC/IWF. + +**indirectly connected restricted 64 kbit/s network:** restricted 64 kbit/s network which is connected to the MSC/IWF via an unrestricted 64 kbit/s network. + +**EDGE channel:** general term referring to channels based on 8PSK modulation; i.e. TCH/F28.8, TCH/F32.0, and TCH/F43.2. + +**A/Gb mode:** a system or a subsystem operates in A/Gb mode if an A or Gb interface is used between the radio access network and the core network. + +**Iu mode:** a system or a subsystem operates in Iu mode if an Iu-CS or Iu-PS interface is used between the radio access network and the core network. It operates in UTRAN Iu mode if UTRAN is used as radio access network. It operates in GERAN Iu mode if GERAN is used as radio access network. + +## 3.2 Abbreviations + +For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 and the following apply: + +| | | +|---------|-------------------------------------------------| +| ADPCM | Adaptive Differential Pulse Coded Modulation | +| BS | Bearer Service | +| DP | Dial Pulse | +| DSS1 | Digital Subscriber Signalling 1 | +| FTM | Frame Tunnelling Mode | +| ITC | Information Transfer Capability | +| LE | Local Exchange | +| NT | Network Termination | +| NT | non-transparent | +| PABX | Private Automatic Branch Exchange | +| PIAFS | PHS Internet Access Forum Standard | +| PPP | Point to Point Protocol | +| SPC | Stored Program Control | +| SS No.7 | Signalling System No.7 | +| T | transparent | +| TE | Terminal Equipment | +| TA | Terminal Adaptor | +| TS | Teleservice | +| TS | Technical Specification | +| TUP | Telephone User Part (of Signalling System No.7) | +| UNI | User Network Interface | + +# --- 4 Introduction + +Since the numbering plan for the ISDN era (E.164) includes the numbering plan for the telephone network (E.163), it is not possible to distinguish by the number whether a given subscriber is a PSTN or ISDN subscriber. Further, in some countries both PSTN and ISDN subscribers will be connected to the same exchange, so the only difference for this type of combined network will be in the nature of the customer access. In the present document a PSTN is considered to support only an analogue interface towards the subscriber. An ISDN shall be considered to support digital interface towards the subscriber. In addition, the ISDN is considered to support a standardized outband signalling protocol both between the subscriber and the network and within the network, i.e. DSS1 and ISUP, thus enabling the generation and transport of Compatibility Information for compatibility checking and terminal/function/service selection at the user-network interface as well as for MSC/IWF selection. + +There now exist networks which do not fall into either of these categories in that they provide for digital connectivity from subscriber to subscriber through the network. The subscribers have access to a wide range of services by a limited set of standard multi-purpose user network interfaces. However, these networks do not support the standardized inter-exchange signalling protocol throughout, in that they are e.g. using TUP or National User Part (NUP). These types of network support 64 kbit/s connections, so in service support are comparable to ISDN, however, the signalling system provided may not support transport of all Compatibility Information allowed for in the standardized ISDN signalling. The present document will therefore identify interworking to PSTN and ISDN on the principle of the network characteristics as identified in the previous paragraph. The aforementioned existing networks then constitute one particular case in the ISDN interworking scenarios. These cases will be itemized when the implication of the various degrees of exhaustiveness of the Compatibility Information - delivered via the ISDN - used for deducting a PLMN Basic Service needs to be set forth. + +When two dissimilar networks are required to interwork in order to support a communication between two subscribers, one on each network, a number of Interworking Functions (MSC/IWFs) are required to support the communication. Some of these are related to the differences in signalling and are dealt with in 3GPP TS 49.003. + +Examples of other aspects of interworking are: + +- the need or otherwise of echo control devices; +- the need or otherwise of modem pools and network-based rate adaptation. + +For the purposes of determining the required MSC/IWFs, it is necessary, however, to consider separately each type of interworking (i.e. PLMN-ISDN and PLMN-PSTN) since, in the worst case, "PSTN" could refer to an essentially analogue network with electromechanical switching not controlled by software and without common-channel signalling. + +Some facilities associated with alternate speech and facsimile group 3 may not be available with version 1 of the MAP (3GPP TS 09.02). Version 1 of the Mobile Application Part (MAP) does not support in-call modification and channel mode modification following an inter-MSC handover. + +# 5 Void + +# 6 Network Characteristics + +## 6.1 Key Characteristics of Networks Concerned + +**Table 1: Key Characteristics of Networks Concerned** + +| Characteristic | PLMN | ISDN | PSTN | +|-----------------------------------|------------------------------------------------------------------|---------------------------------------------------------|------------------------------------------------------------------------| +| Subscriber Interface | Digital | Digital | Analogue | +| User-network signalling | 3GPP TS 24.008 | DSS1, other UNIs | loop-disconnect and DTMF | +| User-terminal equipment supported | see 3GPP TS 24.002 | Digital TE (ISDN NT, TE1 or TE2+TA)
see e.g. 1.411 | Analogue TE (e.g. dial pulse telephones PABXs modern equipped DTEs) | +| Inter-exchange signalling | SS No.7 ISUP
TUP+, MAP | SS No.7 ISUP
TUP+, TUP, NUP | Channel associated (e.g. R2, No.4, No.5) or common channel (e.g. No.6) | +| Transmission facilities | Digital | Digital | Analogue | +| Exchange types | Digital | Digital | Analogue/digital | +| Information transfer mode | Circuit | Circuit | Circuit | +| Information transfer capability | Speech, digital unrestricted, alternate speech/ group 3 fax etc. | Speech, digital unrestricted, 3,1 kHz audio, video etc. | 3,1 kHz audio (voice/voice- band data) | + +### 6.1.1 Characteristics of PLMNs + +The PLMN is fully defined in the Technical Specifications summarised in 3GPP TS 41.003 for a 2nd generation PLMN (A/Gb mode) or in 3GPP TS 21.103 for a 3rd generation PLMN (Iu mode). + +### 6.1.2 Characteristics of PSTNs + +Because of the efforts at an early stage to standardize ISDNs in different countries, the differences between any two ISDNs will be small compared with the differences between PSTNs, which have evolved in different ways in different countries. In some cases the evolution has occurred over many decades, and therefore each PSTN is distinct, and for a recommendation on interworking, it is necessary to make certain assumptions about a generalized PSTN. + +Whilst the key characteristics of PSTNs are given in table 1 above, the specific MSC/IWFs needed to allow interworking between a PLMN and a PSTN will depend on the nature of the PSTN concerned. + +Table 2 gives a number of categories that can be used to classify PSTNs and a number of possibilities within each category. + +**Table 2: Characteristics of PSTNs** + +| Category | Possibilities within Category | +|------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------| +| Type of subscriber signalling | a) PSTN with loop disconnect subscriber signalling (10 pps)
b) PSTN with DTMF subscriber signalling | +| Type of interexchange signalling | a) PSTN with channel-associated signalling
b) PSTN with common-channel signalling | +| Type of interexchange transmission | a) Analogue
b) Digital | +| Type of exchange switching | a) PSTN with electro-mechanical switching
b) PSTN with electronic (non-digital) switching
c) PSTN with electronic digital switching | +| Type of exchange control | a) Non-SPC
b) SPC | +| NOTE: | Under each category, it is possible that a PSTN will have a combination of the possibilities rather than only one. | + +### 6.1.3 Characteristics of ISDN + +For the "standardized ISDN" in principle taken into account here, these are defined in the ETS/ITU-T-series. + +# 7 Interworking classifications + +## 7.1 Service interworking + +Service interworking is required when the Teleservices at the calling and called terminals are different. No service interworking, except for facsimile group 3 (Teleservice 61 or 62 interworking with standard facsimile group 3 service), has been identified as a requirement of the PLMN system for PSTN/ISDN network based services. + +## 7.2 Network interworking + +Network interworking is required whenever a PLMN and a non-PLMN together are involved to provide an end to end connection and may be required in instances of PLMN to PLMN connections. + +The concept of Bearer Services was developed for the ISDN and has been extended to the PLMN. A bearer service is defined (in 3GPP TS 22.001) as. + +A type of telecommunication service that provides the capability for the transmission of signals between user-network interfaces. + +Bearer services are described by a number of attributes, where an attribute is defined as a specified characteristic of an object or element whose values distinguish that object or element from others. + +For the purpose of the present document, a PSTN is assumed to provide a bearer service which equates to an ISDN 3,1 kHz audio bearer service. + +Refer to 3GPP TS 22.002 for complete list of bearer services. Refer to 3GPP TS 24.008 for coding of Bearer Capabilities. Refer to 3GPP TS 27.001 for the allowed combinations of parameter value settings. + +**Table 3: Bearer Service Interworking** + +| Bearer service category in PLMN | Bearer Service in PLMN | Bearer service in ISDN | Service in PSTN | +|---------------------------------------------------------------------------------------------------|-------------------------------|-----------------------------------------------|---------------------------| +| Circuit mode unstructured with unrestricted digital capability
Transparent and Non-transparent | Asynchronous Data general | Cct mode structured
64 kbit/s unrestricted | Not Applicable | +| Circuit mode unstructured with unrestricted digital capability
Transparent | Synchronous Data general | | | +| 3,1 kHz Audio Ex PLMN
Transparent and Non-transparent | Asynchronous Data general | Cct Mode
3,1 kHz Audio | Cct Mode
3,1 kHz Audio | +| 3,1 kHz Audio Ex PLMN
Transparent | Synchronous Data general | | | + +**Table 4: Network interworking of Teleservices** + +| Teleservice in PLMN | Lower layer capabilities addressed in the PLMN Bearer Capabilities IE | Bearer service in ISDN | Service in PSTN | +|------------------------------------|------------------------------------------------------------------------------------------------------------|-------------------------------|------------------------| +| Telephony | Unstructured with speech capability | Speech or Cct mode | Cct Mode | +| Emergency calls | Unstructured with speech capability | 3,1 kHz audio | 3,1 kHz audio | +| Alternate speech/facsimile group 3 | Data Cct duplex synchronous (A/Gb mode) / asynchronous (UTRAN Iu mode) access alternate speech group 3 fax | Cct mode 3,1 kHz audio | Cct mode 3,1 kHz audio | +| Automatic Facsimile group 3 | Data Cct duplex synchronous (A/Gb mode) / asynchronous (UTRAN Iu mode) access group 3 fax | Cct mode 3,1 kHz audio | | + +This table does not identify any relationship between Teleservices in the PLMN with those in the ISDN/PSTN, it is merely to identify the interworking of the lower network layers of that teleservice with the network layers i.e. bearer service in the ISDN/PSTN. + +## 7.3 Signalling interworking + +See 3GPP TS 49.003[31]. + +## 7.4 Numbering + +See 3GPP TS 23.003[35] + +## 7.5 Supplementary service interworking + +For general aspects of supplementary services refer to 3GPP TS 22.004[34] and 23.011[37]. + +Not every supplementary service may be used in combination with each basic service. The applicability of each supplementary service for a basic service is defined in 3GPP TS 22.004[34]. + +# --- 8 Compatibility and subscription checking + +Compatibility checking is carried out on the following items: + +- Low layer compatibility - utilizing low layer compatibility and bearer capability information elements. +- High layer compatibility - utilizing high layer compatibility information element. + +The use of the progress indicator for compatibility checking is outside the scope of the present document. + +Indication of compatibility requirements is carried out as described in subclauses 9.2.2 and 10.2.2. + +For subscription checking, relevant for the interworking described in clauses 9 and 10 of the present document, refer to 3GPP TS 22.001. + +# 9 Interworking to PSTN + +## 9.1 Speech Calls + +### 9.1.1 Interworking indications to PLMN terminal + +An indication to inform the PLMN terminal that: + +- i) instead of receiving out-of-band indications for certain types of failure conditions, a tone or announcement will be received in-band from the PSTN. +- ii) the available compatibility information will be not exhaustive for deducing a PLMN Basic Service and there will be a limitation on address - the terminal may be required to accept the call on the basis of indicating its compatibility requirements. +- iii) (if a DTE) in-band handshaking signals should be anticipated. + +### 9.1.2 Transmission aspects + +Includes control of Speech Processing and Echo Control Devices, see 3GPP TS 43.050. + +### 9.1.3 Generation of In-band Tones and Announcements (PLMN-PSTN) + +In-band tones and announcements shall be provided for all speech and 3,1 kHz audio bearer services between a PLMN and a PSTN. + +## 9.2 Data Calls + +Low Layer Compatibility Checking on the received PLMN bearer capability information element will be carried out by the MSC/IWF to check if the call setup is compatible to the bearer service (3,1 kHz audio) provided by a PSTN and to the IWFs provided by the PLMN. + +In case the call setup does not conform to these requirements (e.g. an information transfer capability value "unrestricted digital information" is requested), the call shall fail with an error cause indicating that the network is unable to support the service requested. + +As well as compatibility checking subscription checking shall be performed. If the subscription check fails the call setup shall be rejected. + +For the case where the UE offers negotiable values in the PLMN bearer capability information element (e.g. both transparent and non-transparent connection element) refer to the definitions specified in 3GPP TS 27.001. + +For interworking of data calls between a PLMN and a PSTN a modem will be utilized to provide the interworking function. + +![Diagram of PLMN PSTN interworking for circuit switched calls](db0c433df107439122051d7b834cd262_img.jpg) + +The diagram illustrates the interworking between a PLMN and a PSTN for circuit-switched calls. On the left, a triangle labeled 'TE' (Terminal Equipment) is connected to a square labeled 'MT' (Mobile Terminal). The 'MT' is connected to a large oval labeled 'PLMN'. Inside the 'PLMN' oval, there is a square labeled 'RA MODEM' and a square labeled 'IWF'. The 'RA MODEM' is connected to an oval labeled 'PSTN'. The 'PSTN' is connected to a square labeled 'MODEM'. The 'MODEM' is connected to a triangle labeled 'V.series'. + +Diagram of PLMN PSTN interworking for circuit switched calls + +Figure 1: PLMN PSTN interworking for circuit switched calls + +### 9.2.1 Network interworking mobile originated + +#### 9.2.1.1 Selection of interworking function + +The interworking function will need to negotiate with the user to establish the appropriate modem selection e.g. data rate, modulation scheme, etc. In addition, it will also be required to convert the signalling format, from a combination of out of band and in band, to that suitable for controlling the modem and the autocalling line procedure function where applicable. It is assumed that the interworking function and modems will be associated with each MSC. + +For a data call originated by a circuit mode data terminal on the PLMN, the modem selection is done by using the elements "modem type" and "other modem type" in the bearer capability (PLMN-BC) of the call set-up message. + +In addition, other elements of the call setup will indicate the user rate, etc. to be used via that modem. The use of this information however means that the network is only able to select a modem from the modem pool which conforms to the speed which the terminal is utilizing at the DTE/DCE interface at the UE (e.g. V.22 for 1 200 bps). The exception to this is where the user has selected the non transparent service in which case either an autobauding or multi self selecting speed modem (e.g. V.32) may be used. + +If in A/Gb or GERAN Iu mode the PLMN-BC(s) received with the set-up message indicated a multislot, 14.4 kbit/s, or EDGE-operation (refer to 3GPP TS 27.001) and the network does not support any of the required such services, the PLMN-BC(s) sent with the call proceeding message shall not contain the "fixed network user rate", "other modem type" and "user initiated modification indicator" parameters - the MSC shall discard the multislot, 14.4 kbit/s and EDGE-related parameters and use the fall-back bearer service indicated by the remaining parameters of the PLMN-BS(s) on a singleslot configuration (refer to 3GPP TS 48.020 and 3GPP TS 44.021) on the MSC/IWF-RAN link. The MSC/IWF shall modify the relevant parameters in a possibly present LLC accordingly. + +If the MSC supports in A/Gb or GERAN Iu mode the multislot, 14.4 kbit/s, or EDGE-operation or if the MSC supports UTRAN Iu mode, the PLMN-BC(s) shall include the "fixed network user rate", "other modem type" and if applicable the "user initiated modification indicator" parameters of the call proceeding message if these parameters were present in the call set-up message received from the UE. In A/Gb or GERAN Iu mode the MSC shall apply on the MSC/IWF-RAN link a singleslot or multislot configuration according to the rules defined in 3GPP TS 44.021, 3GPP TS 48.020 and 3GPP TS 24.022. In case the UE signals an ACC containing TCH/F4.8 only and the network does not support TCH/F4.8 channel coding, then the MSC may act as if TCH/F9.6 were included in the ACC. + +If in A/Gb or GERAN Iu mode the PLMN-BC(s) received with the set-up message did not indicate a multislot, 14.4 kbit/s or EDGE-operation, the MSC shall not include the "fixed network user rate", "other modem type" and "user initiated modification indicator" parameters in the PLMN-BC(s) of the call proceeding message - the MSC shall use a singleslot configuration on the MSC/IWF-RAN link. + +The MSC may negotiate parameters with the UE according to the rules defined in 3GPP TS 27.001. The MSC/IWF shall modify the relevant parameters in a possibly present LLC accordingly. + +#### 9.2.1.2 Modem Selection + +In general terms the indication of the bearer capability parameter "Information Transfer Capability" will be utilized in the call set-up message to determine when the modem should be selected in the call. + +In case of single calls, the modem function shall operate in the calling mode in case of mobile originated calls and in the answering mode in case of mobile terminated calls. + +In case of dual data calls (alternate speech/facsimile group 3) the operation mode of the modem (working in calling or answering mode) depend on the initial call setup direction and on the optional parameter "Reverse Call Setup Direction" information element of the MODIFY message. If this information element is omitted the direction is derived from the initial call setup direction, i.e. the mode is the same as in case of single calls. + +For the attribute value "3,1 kHz audio Ex PLMN" and "facsimile group 3", the modem will be selected immediately. The line procedure according to ITU-T Recommendation V.25 will then be carried out using the appropriate modem functions. + +For the Teleservice 61 "Alternate speech/facsimile group 3", (if speech is selected as the first service), the modem is made available but not selected until the subscriber indicates the change of service request (see subclause 9.3). + +For "alternate speech/facsimile group 3" calls refer to 3GPP TS 43.045 (A/Gb mode) and 3GPP TS 23.146 (UTRAN Iu mode). + +#### 9.2.1.3 Mapping of BC-IE from PLMN to ISUP (or other) + +As it cannot be determined from the called address whether the distant network is a PSTN or an ISDN the same mapping takes place as for ISDN calls (see table 7A), if ISDN signalling is used between different MSCs (e.g. on the link VMSC - GMSC). + +### 9.2.2 Network Interworking Mobile terminated PSTN Originated + +This subclause describes the interworking of calls where the calling subscriber cannot generate or communicate Compatibility Information exhaustive for deducing a PLMN Basic Service to a PLMN (gateway MSC/interrogating node) because of lack of ISDN signalling capability. Thus the HLR is relieved from any compatibility checking for such calls. + +Two methods of allocating UE International ISDN Numbers (MSISDNs) are allowed: Firstly, a separate MSISDN may be allocated for each service, or service option, which a subscriber uses for incoming calls; or, alternatively, a single number, applicable for all incoming calls is used. + +It should be noted that it is possible for both schemes to co-exist within the PLMN and that they are not mutually exclusive. + +- a) Multiple MSISDNs are used ("The Multi-numbering Scheme"). See figure 2. +- b) A single MSISDN is used ("The Single-numbering Scheme"). See figure 3. + +#### 9.2.2.1 Multi-numbering Scheme + +In this scheme, the HPLMN will allocate a number of MSISDNs to a subscriber and associate with each of these numbers a Bearer Capability to identify a Bearer or a Teleservice. This Bearer Capability comprises a complete PLMN Bearer Capability (PLMN BC) information element with contents according to 3GPP TS 27.001 and coded as per 3GPP TS 24.008. In either case, when the HLR receives an interrogation relating to an incoming call (i.e. the MAP "Send Routing Information" procedure), it requests a roaming number (MSRN) from the VLR. This request will contain the PLMN BC reflecting the service associated with the called MSISDN, i.e. the PLMN BC is passed to the VLR within the MAP parameter "GSM Bearer Capability" of the message "Provide Roaming Number". + +If the HLR completes the MAP "Send Routing Information" procedure by providing the MAP "GSM Bearer Capability" to the interrogating entity, as specified in sub-clause 10.2.2.3, the GMSC may then map the received PLMN BC into the User Service Information field of the IAM message sent to the succeeding node according to the rules defined in table 7A. This allows subsequent transit switches to select a codec transparent for data call (e.g. G.711). If the GMSC belongs to a Layered Architecture -backbone, it may also use the PLMN BC to select an appropriate codec for the call during the BICC codec negotiation (e.g. transparent codec for a data call). + +If the MAP "GSM Bearer Capability" is not included in the MAP "Send Routing Information" response, the GMSC may use the MAP "Basic Service Code", if received in the MAP "Send Routing Information" response, to determine whether the call is a speech or data call. + +At the VMSC, when the incoming call arrives, the PLMN BC associated with the MSRN are retrieved from the VLR and sent to the UE at call set-up. + +Where the PLMN specific parameter "connection element" contained in the retrieved PLMN BC-IE, indicates dual capabilities then the VMSC shall set it according to its capabilities/preferences. Additionally the parameters correlated to "connection element" shall be modified in accordance with 3GPP TS 27.001. + +The same applies to the parameter modem type if "autobauding type 1" is indicated but the IWF does not support this feature. The parameter "data compression" may also be modified according to the capabilities of the IWF. + +Where single capabilities are indicated then the VMSC shall use the requested values if it is able to support the service requested. If it is unable to support the requested service then it shall set them according to its capabilities/preferences. + +Where the Compatibility Information is provided in a degree exhaustive to deduce a PLMN Basic Service (see application rules in subclause 10.2.2), then the VMSC in providing the PLMN BC IE in the setup message shall set the PLMN specific parameters to its capabilities/preferences. + +On receipt of a Set-up message containing the compatibility information, the UE will analyse the contents to decide whether the service can be supported (with or without modification, see 3GPP TS 27.001) and the call will be accepted or rejected as appropriate. + +The UE may negotiate parameters with the MSC according to the rules defined in 3GPP TS 27.001. If the UE proposes to the network to modify the User Rate as well as the correlated parameters Modem Type and Intermediate Rate in the call confirmed message or if the UE proposes to the network to modify the Fixed Network User Rate and Other Modem Type parameters for multislot, 14.4kbit/s, EDGE and Iu Mode operations, the network may accept or release the call (see 3GPP TS 27.001). + +This negotiation takes place by means of the UE reflecting back to the MSC a complete bearer capability information element in the call confirmed message, with the relevant parameters changed. If this does not take place (i.e. if there is no PLMN BC present in the call confirmed message), then the MSC will assume that the values originally transmitted to the UE are accepted with the following exceptions: + +- If in A/Gb or GERAN Iu mode, the PLMN-BC sent with the set-up message contained the "fixed network user rate", "other modem type" and if applicable the "user initiated modification indicator" parameters and no multislot, 14.4 kbit/s, and/or EDGE related parameters (refer to 3GPP TS 27.001 and 24.008) are received in the PLMN-BC of the call confirmed message or no PLMN-BC is received, the MSC shall discard the "fixed network user rate", "other modem type" and "user initiated modification indicator" parameters - the MSC shall use the fall-back bearer service indicated by the remaining parameters of the PLMN-BC on a singleslot configuration (refer to 3GPP TS 48.020 and 3GPP TS 44.021) on the MSC/IWF-RAN link. +- On the other hand, if in A/Gb or GERAN Iu mode the PLMN-BC received with the call confirmed message contain(s) multislot, 14.4kbit/s or EDGE-related parameters the MSC shall apply on the MSC/IWF-RAN link a singleslot or multislot configuration according to the rules defined in 3GPP TS 44.021, 3GPP TS 48.020 and 3GPP TS 24.022. In case the UE signals an ACC containing TCH/F4.8 only and the network does not support TCH/F4.8 channel coding, then the MSC may act as if TCH/F9.6 were included in the ACC. +- If in UTRAN Iu mode the PLMN-BC sent with the set-up message contained the "fixed network user rate", "other modem type" and if applicable the "user initiated modification indicator" parameters, but no related parameters (refer to 3GPP TS 27.001 and 24.008) are received in the PLMN-BC of the call confirmed message or no PLMN-BC is received, the MSC shall release the call. + +The VMSC may map the received PLMN BC into an ISDN BC according to the rules defined in table 7A. This ISDN BC can be transported together with possibly available LLC and HLC in the access transport parameter of the Answer message (ANM) according to ITU-T Q.763. + +![Sequence diagram showing the call flow for a mobile terminated, PSTN originated call. The diagram involves five lifelines: UE, VMSC, VLR, HLR, and IN. The sequence of messages is: (1) IN sends SRI (MSISDNk) to HLR; HLR responds with PRN (Bck) to VLR and MSRN to IN; VLR sends MSRN to HLR. (2) HLR sends IAM (MSRN) to VMSC; VMSC sends SIFICSU (MSRN) to VLR; VLR sends Comp. Call (BC' k) to VMSC; VMSC sends Setup (BC' k) to UE. (3) UE sends Call Conf. (BC' k) to VMSC. (4) VMSC sends ANM (BC'' k) to VLR; VLR sends ANM to IN.](eb03559a4d92ea9ebd63ea9be663c50a_img.jpg) + +``` + +sequenceDiagram + participant IN as IN + participant HLR as HLR + participant VLR as VLR + participant VMSC as VMSC + participant UE as UE + + Note right of IN: Incoming Call + IN->>HLR: SRI (MSISDNk) + Note right of HLR: (1) + HLR->>VLR: PRN (Bck) + HLR->>IN: MSRN + VLR->>HLR: MSRN + HLR->>VMSC: IAM (MSRN) + VMSC->>VLR: SIFICSU (MSRN) + VLR->>VMSC: Comp. Call (BC' k) + VMSC->>UE: Setup (BC' k) + Note right of UE: (2) + UE->>VMSC: Call Conf. (BC' k) + Note right of VMSC: (3) + VMSC->>VLR: ANM (BC'' k) + VLR->>IN: ANM + Note right of IN: (4) + +``` + +Sequence diagram showing the call flow for a mobile terminated, PSTN originated call. The diagram involves five lifelines: UE, VMSC, VLR, HLR, and IN. The sequence of messages is: (1) IN sends SRI (MSISDNk) to HLR; HLR responds with PRN (Bck) to VLR and MSRN to IN; VLR sends MSRN to HLR. (2) HLR sends IAM (MSRN) to VMSC; VMSC sends SIFICSU (MSRN) to VLR; VLR sends Comp. Call (BC' k) to VMSC; VMSC sends Setup (BC' k) to UE. (3) UE sends Call Conf. (BC' k) to VMSC. (4) VMSC sends ANM (BC'' k) to VLR; VLR sends ANM to IN. + +- NOTES: (1) The HLR translates the received MSISDN\_ called address (MSISDNk) into the relevant bearer capability information (Bck). + (2) Some parameters of Bck may be provided/modified according to the MSC's capabilities/preferences. See subclause 9.2.2. + (3) In the "Call Confirmed" message, the UE may modify some parameters of the BC. See subclause 9.2.2. + (4) The VMSC may map the PLMN BC (BC'k) into an ISDN BC (BC''k) according to the rules defined in table 7A. + +Abbr.: + SRI - Send Routing Information. + PRN - Provide Roaming Number. + MSRN - Mobile Station Roaming Number. + IAM - Initial Address Message. + SIFICSU - Send Information For Incoming Call Set Up. + ANM- Answer Message + +**Figure 2: Call Flow for a mobile terminated, PSTN originated call where the compatibility information provided are not exhaustive for deducing a PLMN Bearer Service; HLR uses multiple MSISDN numbers with corresponding BCs** + +#### 9.2.2.2 Single-numbering Scheme + +In the single-numbering scheme, the HPLMN will allocate one MSISDN to a subscriber, applicable to all services. + +In this case, when the HLR receives an interrogation relating to an incoming call without compatibility information exhaustive for deducing a PLMN Basic Service (i.e. the MAP "Send Routing Information" procedure), the request to the VLR for a roaming number will not contain compatibility information i.e. a PLMN BC. + +At the VLR, when the incoming call arrives, there is no PLMN BC associated with the MSRN and so the call set-up to the UE will not contain the PLMN BC information element. However, the VMSC may include all available information in the BACKUP BC information element of the call set-up message, see subclause 10.2.2.7. + +In the case the PLMN was not able to provide a PLMN BC, the UE will return a complete single or dual PLMN BC in the Call Confirmed message, indicating the service required by the mobile subscriber. The VMSC will analyse this + +PLMN BC and optionally perform subscription checking (see 3GPP TS 22.001). If the requested PLMN BC can be supported the call is established, otherwise the call will be released. + +The VMSC may map the received PLMN BC into an ISDN BC according to the rules defined in table 7A. This ISDN BC can be transported together with possibly available LLC and HLC in the access transport parameter of the Answer message (ANM) according to ITU-T Q.763. + +![Sequence diagram showing call flow for a mobile terminated, PSTN originated call. Lifelines: UE, VMSC, VLR, HLR, IN. The process starts with an Incoming Call from IN to HLR (SRI (MSISDNk)). HLR sends PRN (no BC) to VLR. VLR sends (MSRN) to HLR. HLR sends (MSRN) to IN. IN sends IAM (MSRN) to VMSC. VMSC sends SIFICSU (MSRN) to VLR. VLR sends Comp. Call (no BC) to VMSC. VMSC sends Setup (no BC, Backup BC) to UE. UE sends Call Conf. (BC) to VMSC. VMSC sends ANM (BC') to IN. Call numbers (1), (2), (3) are indicated next to the final messages.](7e1c9b51e067a48cd0fcc9748d8bd8d8_img.jpg) + +``` + +sequenceDiagram + participant IN as IN + participant HLR as HLR + participant VLR as VLR + participant VMSC as VMSC + participant UE as UE + + Note right of IN: Incoming Call + IN->>HLR: SRI (MSISDNk) + HLR->>VLR: PRN (no BC) + VLR-->>HLR: (MSRN) + HLR-->>IN: (MSRN) + IN->>VMSC: IAM (MSRN) + VMSC->>VLR: SIFICSU (MSRN) + VLR-->>VMSC: Comp. Call (no BC) + VMSC->>UE: Setup (no BC, Backup BC) + UE-->>VMSC: Call Conf. (BC) + Note right of VMSC: ..... + VMSC->>IN: ANM (BC') + Note right of IN: (3) + Note right of VMSC: (1) + Note right of VMSC: (2) + +``` + +Sequence diagram showing call flow for a mobile terminated, PSTN originated call. Lifelines: UE, VMSC, VLR, HLR, IN. The process starts with an Incoming Call from IN to HLR (SRI (MSISDNk)). HLR sends PRN (no BC) to VLR. VLR sends (MSRN) to HLR. HLR sends (MSRN) to IN. IN sends IAM (MSRN) to VMSC. VMSC sends SIFICSU (MSRN) to VLR. VLR sends Comp. Call (no BC) to VMSC. VMSC sends Setup (no BC, Backup BC) to UE. UE sends Call Conf. (BC) to VMSC. VMSC sends ANM (BC') to IN. Call numbers (1), (2), (3) are indicated next to the final messages. + +- NOTE: (1) This BC is derived from information stored in the UE, according to its configuration. The UE may also use the information provided in the Backup BC. + (2) The Backup BC may be included if the BC is missing. + (3) The VMSC may map the PLMN BC (BC) into an ISDN BC (BC') according to the rules defined in table 7A. + (4) Abbreviations: see figure 2. + +**Figure 3: Call Flow for a mobile terminated, PSTN originated call where the compatibility information provided are not exhaustive for deducing a PLMN Bearer Service; HLR uses single MSISDN numbers (no corresponding BC stored). Per call MSRN allocation** + +### 9.2.3 Transparent service support + +The protocol stacks for transparent services are specified in 3GPP TS 43.010 and in Clause 11a.3. + +In Iu mode, the transparent services are based in the Iu User Plane protocol specified in 3GPP TS 25.415. + +In A/Gb mode the rate adaptation scheme shall be utilized on the RAN to MSC link as identified in 3GPP TS 48.020. The transcoding function will generate the 64 kbit/s rate adapted format utilizing the 8 and 16 kbit/s intermediate data rates. The MSC to MSC/IWF link (e.g. in the case of handover) will utilize the same 64 kbit/s rate adaptation scheme as that indicated in 3GPP TS 48.020. + +For the transparent service support the MSC/IWF will select the modem and speed based on the Compatibility information contained in either the call set-up or call confirmed message reference subclauses 9.2.1 and 9.2.2. Where the modem type indicated is one of the multi-speed versions, e.g. V.32, then the MSC/IWF will restrict the modem to the speed indicated in the call set-up and call confirmed message, respectively, i.e. will inhibit the modem from changing speed, irrespective of the conditions, error rate, encountered on the PSTN link. This scenario is also applicable for the use of "autobauding" modems, in that only the specifically requested modem type and speed will be selected at the MSC/IWF (however Facsimile Group 3 can use channel mode modify). + +#### 9.2.3.1 Structure of the MSC/IWF for Iu mode + +The transmission towards the RNC is based on AAL2. The Iu UP is used in the transparent mode. + +![Figure 4: Structure of MSC/IWF for Iu mode. A diagram showing a vertical stack of three boxes: 'Iu UP', 'AAL2', and 'ATM'. An arrow points from the 'Iu UP' box to a 'MODEM' box, which then has an arrow pointing to the right.](2734e7f9be3e1dc046f14be2e6c9a085_img.jpg) + +Figure 4: Structure of MSC/IWF for Iu mode. A diagram showing a vertical stack of three boxes: 'Iu UP', 'AAL2', and 'ATM'. An arrow points from the 'Iu UP' box to a 'MODEM' box, which then has an arrow pointing to the right. + +Figure 4: Structure of MSC/IWF + +#### 9.2.3.2 Structure of the MSC/IWF for A/Gb mode + +The rate adaptation process is a reverse of that provided in the Terminal Adaptation function of the UE. The rate adaptation RA1 is based on the ITU-T Recommendation V.110 80 bit frame for TCH/F2.4, TCH/F4.8 and TCH/F9.6 and on A-TRAU frame for TCH/F14.4. 3GPP TS 44.021 and 3GPP TS 48.020, respectively, refer to the rate adaptation mechanisms to be provided. For multislot configurations refer to 3GPP TS 43.010. + +NOTE: From MSC/IWF's perspective a TCH/F28.8 EDGE configuration is identical to a multislot 2×TCH/F14.4 configuration. + +![Figure 5: Rate adaptation schematic. A diagram showing the flow of data from an MSC through an IWF to a MODEM and then to a PSTN. Inside the IWF, there are three rate adaptation stages: RA2 (64 kbit/s, 2^k*8 kbit/s), RA1 (2^k*8 kbit/s, 2^n*600 bit/s), and RA0 (Stop bit). Arrows show the data path through these stages into the MODEM.](303fadfb9def251d1575d6221199b158_img.jpg) + +Figure 5: Rate adaptation schematic. A diagram showing the flow of data from an MSC through an IWF to a MODEM and then to a PSTN. Inside the IWF, there are three rate adaptation stages: RA2 (64 kbit/s, 2^k\*8 kbit/s), RA1 (2^k\*8 kbit/s, 2^n\*600 bit/s), and RA0 (Stop bit). Arrows show the data path through these stages into the MODEM. + +Figure 5: Rate adaptation schematic + +In case of asynchronous bearer services and the facsimile teleservices in the transparent mode, the IWF shall disregard the value of bits E4, E5, E6 and E7 in the data transmission phase. + +#### 9.2.3.3 Mapping of signalling UE/MSC/IWF to modem interface requirements + +This process also is a reverse of the function provided in the Terminal Adaptation function of the UE for the mapping of DTE/DCE signalling information to Dm channel and in band signalling information. See 3GPP TS 27.002 and 3GPP TS 27.003. + +![Figure 6: Signalling mapping schematic. A diagram showing two boxes: '(Dm or) inband signalling functions' on the left and 'V-series DCE functions' on the right. Two arrows labeled 'Mapping' connect them, one pointing from left to right and another from right to left.](ced309874aec0546651b0976d5030a42_img.jpg) + +Figure 6: Signalling mapping schematic. A diagram showing two boxes: '(Dm or) inband signalling functions' on the left and 'V-series DCE functions' on the right. Two arrows labeled 'Mapping' connect them, one pointing from left to right and another from right to left. + +Figure 6: Signalling mapping schematic + +Status bits SA, SB and X can be used to convey channel control information associated with the data bits in the data transfer state. Table 5 shows the mapping scheme between the V.24 circuit numbers corresponding to the V-series DCE + +functions and the status bits for the transparent mode. It also shows how the unused status bits should be handled. It is derived from the General Mapping scheme described in annex B. A binary 0 corresponds to the ON condition, a binary 1 to the OFF condition. + +The transport of these status bits by the various channel codings is described in 3GPP TS 44.021 and 3GPP TS 48.020 for A/Gb mode. For Iu mode refer to Clause 11a. + +NOTE Although the interface to the modem is described in terms of V.24 interchange circuit functions, this does not imply that such circuits need to be physically realised. + +**Table 5: Mapping scheme at the IWF for the transparent mode** + +| Mapping direction: UE to IWF | Mapping direction: IWF to UE | Signal at IWF modem interface or condition within the IWF | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------|-----------------------------------------------------------| +| always ON (note 1) | | CT 105 | +| | to status bit X | CT 106 | +| | not mapped (note 5) | CT 107 | +| not mapped (note 6) | | CT 108 | +| | to status bit SB | CT 109 | +| always ON (note 2) | | CT 133 | +| from status bit SA (note 3) | | ignored by IWF | +| from status bit SB (note 1) | | ignored by IWF | +| from status bit X (note 4) | | ignored by IWF | +| | to status bit SA (note 3) | always ON | +| NOTE 1: The SB bit towards the IWF, according to the General Mapping (annex B), could be used to carry CT 105 from the mobile DTE to the modem in the IWF. However, CT 105 should always be ON at the DTE interface in the data transfer state since only duplex operation is supported. Also, many DTEs use the connector pin assigned to CT 105 for CT 133. Therefore, CT 105 shall always be set to ON at the IWF modem during the data transfer state. | | | +| NOTE 2: CT 133 is not mapped since there is no flow control in transparent mode. | | | +| NOTE 3: The SA bits in both directions are available only with certain channel codings. Therefore, for maximum compatibility, they should not be mapped. | | | +| NOTE 4: The X bit towards the IWF is not mapped since there is no flow control in transparent mode. | | | +| NOTE 5: CT 107 is not used by the IWF. | | | +| NOTE 6: CT 108 is used in the call setup and answering processes. | | | + +In general it is not required for the modem in the MSC/IWF to support a "remote looping" request from a modem in the PSTN. In addition the invocation of a "remote looping" request from the mobile subscriber to a modem in the PSTN need not be supported (see also 3GPP TS 27.001). Specific test loops for mobile subscribers to contact may be provided at the network operators discretion. + +#### 9.2.3.4 Establishment of end-to-end terminal synchronizations + +Prior to exposing the traffic channel of a PLMN connection to transmission of user data, the controlling entities of the connection shall assure of the availability of the traffic channel. This is done by a so called synchronizations process: + +- starting on the indication of "physical connection established" resulting from the PLMN-inherent outband signalling procedure. This indication is given: + - for MOC: on sending the CONNECT message; + - for MTC: on sending the CONNECT ACKNOWLEDGE message; + - for mobile initiated in-call modification: on sending the MODIFY COMPLETE message (which is sent after reception of the ASSIGNMENT COMPLETE or RAB ASSIGNMENT RESPONSE message); and + - for network initiated in-call modification: on reception of the ASSIGNMENT COMPLETE or RAB ASSIGNMENT RESPONSE message; + +- ending by indicating the successful execution of this process to the controlling entity, which then takes care of the further use of the inband information (data, status). + +Network interworking within an MSC/IWF is concerned with the terminating side (to the UE) and the transit side (to the fixed network) of a connection. Both sides have to be treated individually related to the synchronizations process. + +##### 9.2.3.4.1 Terminating side (towards the UE) + +###### 9.2.3.4.1.1 Traffic channel types TCH/F4.8 and TCH/F9.6 for A/Gb mode + +With respect to the terminating side the procedure is as follows: + +- sending of synchronizations pattern 1/OFF (all data bits "1"/all status bits "OFF") to the UE using the RA1/RA2 rate adaptation function. In multislot transparent operation, the synchronisation pattern sent is 1/OFF with the exception of the bit positions S1, first X, S3, and S4 which contain the substream number and multiframe alignment pattern (see 3GPP TS 44.021); +- searching for detection of the synchronizations pattern from the UE within valid V.110 frames, and in multislot operation, also searching for the multiframe alignment pattern "0000 1001 0110 0111 1100 0110 1110 101" (see 3GPP TS 44.021) in bit position S4 and substream numbers in bit positions S1, first X, and S3. This implies that the E1, E2 and E3 bit of the V.110 frame shall be checked for the appropriate user rate in order to distinguish the synchronization pattern from the RAN idle data frame; +- timer T (= 500 ms) is started for each of the allocated traffic channel(s) of the call on receipt of the synchronizations pattern from the UE; +- when the frame alignment pattern and, in case of multislot operation, the multiframe alignment pattern have been recognized as a steady state, the MSC/IWF continues sending the synchronizations patterns to the UE until a timer T expires. + +###### 9.2.3.4.1.2 Traffic channel type TCH/F14.4 for A/Gb mode + +With respect to the terminating side the procedure is as follows: + +- sending A-TRAU frames with the data rate set in the bits C1-C4 (TS 48.020) and data bits set to one, sending the multiframe structure with the alignment pattern (bit M1) and with the status bits OFF (bit M2) and, in a multislot case, sending substream numbers (bit M2); +- searching for the detection of the multiframe alignment pattern "0000 1001 0110 0111 1100 0110 1110 101" (TS 44.021) in the bit M1 and, in a multislot case, searching for substream numbers in the bit M2. (Any 5 bit sequence in the multiframe alignment pattern is unique, i.e. the multiframe alignment can take place by recognition of five successive M1 bits); +- timer T (= 500 ms) is started for each of the allocated traffic channel(s) of the call on receipt of the synchronizations pattern from the UE; +- when the frame alignment pattern and the multiframe alignment pattern have been recognized as a steady state, the MSC/IWF continues sending the synchronizations patterns to the UE until a timer T expires. + +###### 9.2.3.4.1.3 User Plane for Iu mode + +The IWF does not send any frame down link until the modem connection has been established and the modems have synchronised. Thereafter the IWF through connects, mapping data from the fixed network side onto frames that are sent toward the UE, and mapping data in the received frames to the fixed network side. + +##### 9.2.3.4.2 Transit side (towards the fixed network) + +With respect to the transit side the procedure is as follows: + +- at the start of timer T for each of the allocated traffic channel(s) of the call, circuit 108 to the selected modem associated with the connection will be switched from the "OFF" to "ON" condition, thus initiating the establishment of the modem connection. In the case of mobile originated calls, this initiates the auto calling sequence and after signalling, calling tone according to V.25 shall be generated by the modem in the IWF; +- the interchange circuits towards the modem (with the exception of CT108) are held in the OFF condition until timer T expires, when they are switched to ON; + +- from this time, after the expiration of the timer T of every allocated traffic channel, the information on CT106 and CT109 from the IWF Modem are directly mapped to the SB and X bits toward the UE. For TCH/F14.4 the SB and X bits are mapped to the M2 multiframe bits according to 3GPP TS 44.021. The IWF is allowed to map CT104 to the data bits sent towards the UE and to map data bits received from the UE to CT103. + +#### 9.2.3.5 Network Independent Clocking (NIC) + +The network independent clocking function applies only to A/Gb mode. It is invoked by the VMSC/IWF when the service requested (MO or MT) is 3,1 kHz Ex PLMN and synchronous. The above rule applies irrespective of the information contained in the 3GPP TS 24.008 setup message regarding NIC. For all other services NIC is not used. + +Within the PLMN the coding of the values for bits associated with NIC is specified in 3GPP TS 44.021 and 3GPP TS 48.020. In the forward (transmitting) direction the multiframes shall be coded in exact accordance with that specified in those specifications. Bit E6 is set to "1" in alternate modified V.110 frames at the transmitter. However, the use of this bit at the receiver for monitoring frame synchronization, or any other purpose, is not specified and is left to the discretion of the implementer. + +A "perfect linear block Code" is used in C1-C5, whose error correction properties may be utilized in the receiver, in order to ensure reliable operation of NIC. + +The NIC sending function shall recognize when the difference between the applicable clock speed of the PLMN and the interface speed generates a positive or negative whole bit requirement. When this positive or negative condition occurs, the NIC codewords specified in 3GPP TS 44.021 are used to transport this condition to the receiving NIC function. Transmission of the codeword shall clear the positive or negative condition related to that codeword at the sending function. The sending function shall not send more than one positive or negative compensation within a contiguous period of time corresponding to 10 000 user data bits minus the maximum NIC code framing delay (e.g. in the case of TCH/F2.4, TCH/F4.8 or TCH/F9.6, the number of user data bits necessary to make up an even number of V.110 frames between compensation). NIC compensation is coded in two V.110 frames in the case of TCH/F2.4, TCH/F4.8 or TCH/F9.6 and in one multiframe in the case of TCH/F14.4. This results from the requirements to compensate for maximum clock differences of $\pm 100$ parts per million. If the receiving function receives NIC compensations in the average more often than a contiguous period of time corresponding to 10000 user data bits, there is no guarantee that data will not be lost. + +The NIC receiving function shall provide the capability to support the compensation requirements of the sending function. This compensation is managed by manipulating the clock speed of the interface, within the standard constraints of that interface. + +Overall, the compensation functions shall be capable of managing clock tolerances of $\pm 100$ parts per million. + +Action on loss of synchronization. + +If five consecutive NIC multiframes in the V.110 frame have incorrect framing bit values in E7 or if the A-TRAU multiframe synchronisation is lost, the receiver shall stop applying clocking compensation to the received data. Resynchronization will be attempted and compensation will resume when synchronization is achieved. + +### 9.2.4 Non-transparent service support + +The protocol stacks for non-transparent services are specified in 3GPP TS 43.010 and in Clause 11a.2. Both of the systems use the Radio Link Protocol (RLP) specified in 3GPP TS 24.022. + +In Iu mode, the non-transparent services are based in the Iu User Plane protocol specified in 3GPP TS 25.415. + +In A/Gb mode the corresponding necessary support concerning the rate adaptation scheme shall be utilized on the RAN-MSC link as identified in 3GPP TS 48.020. + +For the non-transparent service support the MSC/IWF will select the modem and speed based on the Compatibility information contained in either the call set-up or call confirmed message, reference subclauses 9.2.1 and 9.2.2. Where the Modem Type indicated is autobauding type 1, the MSC/IWF may select any speed and modem type according to what it can negotiate with the remote modem. In this case User Rate and Fixed Network User Rate, if present, has no meaning. + +#### 9.2.4.1 Structure of the MSC/IWF for Iu mode + +The transmission towards the RNC is based on AAL2. The Iu UP is used in the support mode. The RLP/L2R extends to the UE. + +![Diagram showing the protocol stack for MSC/IWF in Iu mode. The stack consists of four layers: RLP/L2R (top, split into RLP and L2R), Iu UP, AAL2, and ATM (bottom). The RLP/L2R layer is connected to a MODEM block on the right. The ATM layer has an input line from the left.](f0a97d0d3818a253c1d2a009966081b1_img.jpg) + +Diagram showing the protocol stack for MSC/IWF in Iu mode. The stack consists of four layers: RLP/L2R (top, split into RLP and L2R), Iu UP, AAL2, and ATM (bottom). The RLP/L2R layer is connected to a MODEM block on the right. The ATM layer has an input line from the left. + +**Figure 7: Structure of MSC/IWF** + +#### 9.2.4.2 Structure of the MSC/IWF for A/Gb mode + +The rate adaptation process will be the same as for the transparent case (see figure 5), except that a TCH/F43.2 channel coding is also supported. From MSC/IWF's perspective a TCH/F43.2 EDGE configuration is identical to a multislot 3×TCH/F14.4 configuration. + +3GPP TS 43.010 identifies the protocol layer structures for the non-transparent case, the physical layer to the PSTN is provided by means of a modem. + +#### 9.2.4.3 Re-constitution of user data + +3GPP TS 24.022 refers to the frame of user data in the radio link protocol. The layer 2 relay functions in the UE and the MSC/IWF (identified in 3GPP TS 43.010) contain the mechanism for packing and unpacking the user data into the L2R protocol data units. + +#### 9.2.4.4 Layer 2 relay functionality + +Specific functionality is required of the L2R dependant upon the service which is being requested to be supported. The selection of the appropriate L2R function will be determined by the MSC/IWF on the basis of the bearer capability information signalled in either the call set-up request, or call confirmation messages. The prime information element being transparent or non transparent service indication. In addition the particular L2R function will be selected on the basis of the users layer 2 indication - type of protocol to be terminated and mode of flow control to be applied (see appropriate clauses of the 3GPP TS 27 series). + +The specific interaction between the L2R function and the RLP function and the L2R frame structure will be the same as that detailed in the annex to the appropriate 3GPP TS 27 series. + +#### 9.2.4.5 In band signalling mapping flow control + +This entails the L2R function providing the means of controlling and responding to flow control functions of the modem plus any synchronization requirements related to flow control. For asynchronous services a specific rule applies for flow control (see 3GPP TS 27.001). + +The flow control function chosen will be dependent upon the information contained or not contained in the "user information layer 2" information element of the PLMN BC received from the UE. + +If flow control is provided, irrespective of the type used the L2R function shall: + +- provide immediate indication of flow control to the fixed network on receipt of flow control request from the UE; and/or +- provide immediate indication of flow control to the UE on receipt of flow control request from the fixed network i.e. in the next available L2R status octet to be transmitted. + +Where in-band (X-on/X-off) flow control is in use, then the X-on/X-off characters will not be passed across the radio interface. + +For outband flow control refer to subclause 9.2.4.9. + +If no flow control is provided, the involved end systems are responsible for performing in-band flow control on their own by taking into account the buffer capacity of the MSC/IWF stated below. + +##### 9.2.4.5.1 Conditions requiring flow control towards the fixed network + +The L2R function will initiate flow control - if flow control is present - in the following circumstances: + +- 1) the transmit buffer reaches a preset threshold (BACK PRESSURE); +- 2) the L2R function receives an explicit "flow control active" indication. + +No flow control initiation/removal will take place at the L2R function and loss of data may occur if no flow control is provided. + +On removal of buffer congestion or receipt of L2R "flow control inactive" the flow control will be removed. + +##### 9.2.4.5.2 Conditions requiring flow control towards the UE + +The L2R function will transmit to the UE an explicit "flow control active indication" if flow control is provided in the following circumstances: + +- 1) if the receive buffer from the radio side reaches a preset threshold (BACK PRESSURE); +- 2) if a flow control indication is received from the fixed network customer. On receipt of this flow control indication, transmission of data from the receive buffers towards the fixed network terminal is halted. + +On removal of the buffer congestion or fixed network flow control indication, the L2R function will send a "flow control inactive" indication towards the UE. In addition, for the fixed network indication, transmission of data from the receive buffers will be restarted. + +If no flow control is provided at the L2R function, no flow control initiation/removal will take place by the MSC/IWF. Data might be lost without any indication by the MSC/IWF to the end systems involved. + +#### 9.2.4.6 Data buffers + +##### 9.2.4.6.1 Transmit buffers (towards UE) + +Incoming data from the fixed network customer shall be buffered such that if the MSC/IWF is unable to transfer data over the radio path the data is not lost. + +The buffer shall be capable of holding the data. Its size is up to the implementers. When the buffer is half full flow control towards the fixed network shall be initiated if flow control is provided as per subclause 9.2.4.5.1. + +##### 9.2.4.6.2 Receive buffers (from UE) + +Incoming data from the UE is buffered such that if the fixed network terminal is unable to accept the data then it is not lost. + +The buffer shall be capable of holding the data. Its size is up to the implementers. When the buffer becomes half full, the L2R function will send a "flow control active" indication towards the UE if flow control is provided at the L2R function, as per subclause 9.2.4.5.2. + +#### 9.2.4.7 Transportation of the Break condition + +The "BREAK" condition shall be recognized by the L2R function and passed immediately to the UE. The L2R will generate a "BREAK" condition towards the fixed network on receipt of a break indication from the MS. The action of the "BREAK" on the L2R transmit and receive and the length of the "BREAK" signal to be generated towards the fixed network is described in 3GPP TS 27.002. + +#### 9.2.4.8 In band signalling mapping modem status information + +Status information is carried between the modem in the IWF and the terminal adaptation function in the UE by the L2R function. The L2RCOP entity transfers interface status information between L2Rs via the status octets SA, SB and X in L2RCOP-PDUs (3GPP TS 27.002). Table 6 shows the mapping scheme between the V.24 circuit numbers corresponding to the V-series DCE functions and the status bits for the non-transparent mode. It also shows how the unused status bits should be handled. It is derived from the general mapping scheme described in annex B. A binary 0 corresponds to the ON condition, a binary 1 to the OFF condition. + +NOTE: Although the interface to the modem is described in terms of V.24 interchange circuit functions, this does not imply that such circuits need to be physically realised. + +**Table 6: Mapping scheme at the IWF for the non-transparent mode** + +| Mapping direction: UE to IWF | Mapping direction: IWF to UE | Signal at IWF modem interface or condition within the IWF | +|------------------------------|------------------------------|-----------------------------------------------------------| +| always ON (note 1) | | CT 105 | +| | to status bit X (notes 4, 7) | CT 106 (note 7) | +| | not mapped (note 5) | CT 107 | +| not mapped (note 6) | | CT 108 | +| | to status bit SB | CT 109 | +| from status bit X (note 8) | | CT 133 (notes 3, 8) | +| from status bit SA (note 2) | | ignored by IWF | +| from status bit SB (note 1) | | ignored by IWF | +| | to status bit SA (note 2) | always ON | + +NOTE 1: The SB bit towards the IWF, according to the General Mapping (annex B), could be used to carry CT 105 from the mobile DTE to the modem in the IWF. However, CT 105 should always be ON at the DTE interface in the data transfer state since only duplex operation is supported. Also, many DTEs use the connector pin assigned to CT 105 for CT 133. Therefore, CT 105 shall always be set to ON at the IWF modem during the data transfer state. + +NOTE 2: The SA bits (both directions) are not mapped since CTs 107 and 108 are handled locally (notes 5 and 6). + +NOTE 3: The condition of CT 133 (or other flow control mechanism) may also be affected by the state of the L2R transmit buffer (towards the UE) in the IWF and the state of RLP (RR/RNR). + +NOTE 4: The condition of status bit X towards the UE may also be affected by the state of the L2R receive buffer (from the UE) in the IWF. + +NOTE 5: CT 107 is not used by the IWF. + +NOTE 6: CT 108 is used in the call setup and answering processes. + +NOTE 7: For inband flow control, CT 106 is not mapped and the status bit X towards the UE is controlled by the reception of XON and XOFF characters from the modem. + +NOTE 8: For inband flow control, changes in the condition of the status bit X from the UE result in the sending of XON or XOFF to the modem. CT 133 is always set to ON. + +#### 9.2.4.9 Support of out-band flow control + +Out-band flow control in case of the asynchronous bearer service requires V.42 functionality in the modems in the MSC/IWF and the fixed network. + +If this functionality is requested by the UE but cannot be provided by the MSC/IWF or the remote (fixed network) modem for any reason, the call shall be supported without V.42 functionality (fall back to the non-error correction mode according to ITU-T Recommendation V.42). + +This implies that no flow control initiation/removal (refer to subclause 9.2.4.5.1) is possible towards the fixed network. In this case the L2R transmit buffers in the IWF (towards the UE, refer to subclause 9.2.4.6.1) shall overbridge temporary throughput problems on the radio interface and the case where the UE initiates flow control. The IWF however shall release the connection if an overflow of these buffers occurs. + +#### 9.2.4.10 Establishment of end-to-end terminal synchronizations + +Prior to exposing the traffic channel of a PLMN connection to transmission of user data, the controlling entities of the connection shall assure of the availability of the traffic channel. This is done by a so called synchronization process: + +- starting on the indication of "physical connection established" resulting from the PLMN-inherent outband signalling procedure. This indication is given: + - for MOC: on sending the CONNECT message; + - for MTC: on sending the CONNECT ACKNOWLEDGE message; + - for mobile initiated in-call modification: on sending the MODIFY COMPLETE message (which is sent after reception of the ASSIGNMENT COMPLETE or RAB ASSIGNMENT RESPONSE message); and + - for network initiated in-call modification: on reception of the ASSIGNMENT COMPLETE or RAB ASSIGNMENT RESPONSE message; +- ending by indicating the successful execution of this process to the controlling entity, which then takes care of the further use of the in-band information (data, status). + +Network interworking within an MSC/IWF is concerned with the terminating side (to the UE) and the transit side (to the fixed network) of a connection. Both sides shall be treated individually related to the synchronization process. + +##### 9.2.4.10.1 Terminating side (towards the UE) + +With respect to the terminating side the procedure in A/Gb mode is as follows: + +- reception of V.110 or A-TRAU frames on all allocated traffic channels for the call is required before the MSC/IWF shall reply with an RLP-UA frame to the MT's RLP link establishment request (if the MSC/IWF initiates the RLP link establishment, reception of V.110 frames or A-TRAU on all allocated traffic channels for the call shall be detected first); +- waiting for the RLP link establishment by the MT (in addition the MSC/IWF may initiate the RLP establishment). + +In Iu mode at the IWF, the synchronisation of modems on the transit network is performed after establishment of the physical connection. The RLP establishment may be initiated by the IWF, but is normally initiated by the UE. If the modems synchronise before the RLP has been established, the IWF stores the information received from the other modem in the L2R buffers. + +##### 9.2.4.10.2 Transit side (towards the fixed network) + +Depending upon implementation - CT108 will be turned ON to enable the autocalling/autoanswering function of the selected modem either when the RLP has been established or in parallel to RLP establishment. If CT 108 is turned ON in parallel to the RLP establishment, the modem connection may be established before the RLP is established. In this case, data received from the transit side during RLP establishment shall be stored within the L2R buffers until the RLP establishment at the terminating side has been finished. When the RLP has been established, the information from/to the RLP including status changes will be mapped by the L2R entity applicable to the particular bearer capability. After signalling, for MO calls, calling tone according to V.25 shall be generated by the modem in the IWF. + +#### 9.2.4.11 Data compression + +When data compression is invoked within a non-transparent bearer service, interworking to the fixed network is realized as follows. + +The PLMN BC is used to indicate the interworking modem type and user rate. The modems shall try to negotiate data compression and flow control. If negotiation of data compression fails in the fixed network, the call continues with data compression between UE and IWF only. + +#### 9.2.4.12 Service level up and down grading + +Service level up and down grading is only applicable for A/Gb mode and GERAN Iu mode. If the value of the RLP parameter "UP signalling" is negotiated to 1, the IWF shall send a suggestion to the UE to initiate an upgrading whenever the following condition holds: + +The IWF: + +- 1) is receiving user data from the fixed network side at a higher rate than the current AIUR; or + +- 2) in symmetrical calls only, can send user data towards the fixed network side at a higher rate than the current AIUR. + +When the above condition does not hold, the IWF sets the value of the UP bit continuously to 0. When the condition above does hold, the IWF indicates the number of traffic channels to upgrade by, by sending that number of 1s between two consecutive 0s in the UP bit sequence. This indication is not repeated since the FCS protects it. For instance, if the current number of traffic channels is two and an upgrading to four traffic channels is suggested, the UP bit sequence shall be ..01100... How the IWF detects the condition and additional details for setting and resetting of the UP bit, e.g., hysteresis levels, may depend on implementation. + +NOTE: From MSC/IWF's perspective a TCH/F28.8 or TCH/F43.2 EDGE configuration is identical to a multislot $2 \times \text{TCH/F14.4}$ or $3 \times \text{TCH/F14.4}$ configuration. In this case, rather than suggesting the number of channels to add, the IWF suggests a number of 14.4 substreams to add and therefore a factor of $\frac{1}{2}$ or $\frac{1}{3}$ shall be applied to the suggested increase when the assigned up link channel is TCH/F28.8 or TCH/F43.2 respectively. + +### 9.2.5 DTE/DCE interface (Filtering) + +The DTEs taken into account for the PLMN at the UE side conform to ITU-T's DTE/DCE interface specifications, which assume basically an error-free environment, i.e.: + +- limited distance, point-to-point local interconnection of the interface circuits for data and status; +- steady state signalling. + +The envisaged use of these DTE's in the PLMN environment leads to the exposure of these "interconnections" - which may, in the ISDN case, lead to the ISDN Rate Adaptation rather than to a Modem in the MSC/IWF - to the PLMN Radio Channel. To assure proper operation even under these conditions appropriate measures shall be taken. In the "non-transparent case" the RLP satisfies the requirement for both data and status lines. In the "transparent" case, the: + +- data line aspects shall be dealt with end-to-end between the users; while +- status line aspects are of concern to the network which are dealt with in the following. + +The use of the channel control information for the remote control of the DTE/DCE control interchange-circuits between the UE and the MSC/IWF (the conveyance of which is supported by the rate adaptation scheme adopted for PLMN application) requires alignment to the particular transmission occurrences in the traffic channel to be taken into account within the PLMN. In principle this can be best achieved by: + +- relying only on the PLMN outband signalling as far as connection control is concerned; +- eliminating the dependence upon the transmission of channel control information via the radio link. + +Support for this strategy is given to a certain extent by the confinement of PLMN data connections to: + +- full duplex operation (no turning round of the connection is required); +- switched service (demand access); +- mapping of connection-control relevant conditions of the DTE/DCE control interchange-circuits to/from outband PLMN signalling according to 3GPP TS 24.008 after successful traffic channel synchronization; +- flow control by a network entity supported only in non-transparent mode; +- support of connections with the same user data rate only (no TA to TA end-to-end flow control in case of transparent mode). + +The only DTE/DCE control interchange-circuit conditions, which actually are not covered by the above confinements, are the indications of readiness for data transmission, i.e. CT106/109 in case of V.-series interface and I-circuit of X.-series interface. As the effect of a condition change of the afore-mentioned DTE/DCE interchange-circuits depends on the: + +- phase within the course of the connection; +- direction of change (ON-OFF or OFF-ON). + +The required precaution to be applied (Filtering) shall be determined individually in view of: + +- function deduced from the change; +- resilience of the connection needed; +- error condition possibly invoked due to a delay in performing the condition change of the control interchange circuit; +- potential loss of performance in connection usage. + +The details of the filtering function are laid down in 3GPP TS 27- series. Filtering of channel control information is only relevant at the UE side in the transparent mode of operation. + +## 9.3 Interworking Alternate Speech / Facsimile Group 3 Calls + +### 9.3.1 General + +The procedure for the alternate speech/facsimile group 3 services is invoked at UE-MSC link during the call set-up phase. This service is invoked by indication of repeated bearer capability information elements in the setup message and/or call confirmed message respectively (preceded by a repeat indicator "circular"), one indicating speech and the other indicating facsimile group 3. The facsimile service requested will be indicated by the information transfer capability "facsimile group 3", as for a normal single call. The bearer capability first indicated i.e. speech or facsimile group 3 determines the first selection required of the network by the subscriber. Depending on the type of service requested and direction of call establishment (MO/MT, see relevant clauses of 3GPP TS 27 series) low layer and high layer capabilities may also be included. The MSC/IWF will perform both compatibility checking and subscription checking on both sets of capabilities as for normal data calls. If either the subscription check or the compatibility check fails then the call will be rejected. The only exception to this is when TS61/TS62 negotiation takes place, see 3GPP TS 27.001. + +The applicable rules for provision of supplementary services are laid down in 3GPP TS 22.004. + +The "speech" phase of the call, when invoked is handled by the transcoder and will utilize normal telephony teleservice interworking requirements and mobile network capabilities. This includes any requirements for echo cancellers etc. as indicated in subclause 9.1. The "facsimile group 3" phase of the call, when invoked, shall utilize the appropriate data interworking capability (IWF including modem) and shall use the transparent mobile network capability in A/Gb mode or the non-transparent mobile network capability in UTRAN Iu mode. + +The network shall provide, for service and operational reasons, a rapid and reliable changeover of capability upon request from the mobile user. This changeover may involve the disabling, by-passing or introduction of particular network functions (e.g. speech coder, modem etc.) and change of the channel configuration on the radio interface. This changeover is initiated on the receipt of the "MODIFY" message (see 3GPP TS 24.008) from the UE. The network itself will not initiate a changeover. + +### 9.3.2 Mobile originated PSTN terminated calls + +The call is set up in the normal manner (but with repeated bearer capability information elements as described in subclause 9.3.1 and handled by the MSC/IWF as indicated in the general clause. + +### 9.3.3 PSTN originated mobile terminated calls + +The call set up request for this particular service is performed in a similar manner to that indicated in subclause 9.2 for normal PSTN originated calls. + +When multiple MSISDNs are used by the HLR ("Multi-numbering scheme"), one PLMN BC-IE with the ITC value set to "alternate speech/facsimile group 3, starting with speech" is passed to the VLR in the MAP operation "provide roaming number". The VLR stores this information against the MSRN. + +When the call arrives at the visited MSC this information is retrieved from the VLR and sent to the UE in the setup message as defined in 3GPP TS 27.001. + +If the ITC of the PLMN BC-IE retrieved from the VLR has the value "alternate speech/facsimile group 3, starting with speech" this PLMN BC-IE shall be mapped to two PLMN BC-IEs (preceded by a repeat indicator "circular"), one + +representing speech, the other representing facsimile group 3. The order in which these two PLMN BC-IEs are sent towards the UE, in the setup message, is a network option. + +In order to allow auto answering mode for the facsimile phase (i.e. the call starts automatically with the facsimile phase), the UE can reflect back to MSC the dual Bearer Capability in the Call Confirm message with the BC elements interchanged to those in the original Call Set-up message (i.e. facsimile element first or negotiate to facsimile only, see subclause 9.2.2 and 3GPP TS 27.001). In all other aspects it is handled as indicated for mobile originated. + +NOTE: However, the PLMN specific parameters "connection element" and "radio channel requirements" of the retrieved PLMN BC-IE may be modified, or added in line with the principles identified in subclause 9.2.2. + +When a single MSISDN is allocated to the subscriber ("single numbering scheme"), the call is handled as described in case b) of subclause 9.2.2. In the "call confirmed" message, however, two PLMN BC-IEs are preceded by a repeat indicator "circular", with the first PLMN BC-IE indicating the initial phase of the connection. + +### 9.3.4 BICC network architecture + +In a BICC network architecture the following procedures apply for both mobile originated and mobile terminated alternate speech/facsimile group 3 calls: + +The PLMN BC-IE value of ITC equal to "alternate speech/facsimile group 3, starting with speech" shall not be used in the H.248 signalling towards the MGW. Instead, the MGW terminations shall be configured for the speech portion of the call using the Acocodec property. + +To switch to fax mode, the PLMNBC property with ITC indicating "facsimile group 3" shall be applied on appropriate terminations, as detailed in Clause 11a.1.3, to insert the MGW IWF and configure the fax call. Usual procedures to setup a CSD call is followed as described TS 29.232 [82]. + +Similarly, to switch from fax to speech mode, the PLMNBC property shall be removed and the terminations shall be re-configured for the speech portion of the call using the Acocodec property. + +## 9.4 3G-H.324/M calls over 3,1kHz audio + +In case of 3G-H.324/M calls over 3.1kHz audio, the IWF shall provide the V.34 modem modulation and the V.8 procedure with the indication of H.324 support in the call function category of the V.8 handshaking. H.223 and H.245 flow is not terminated in the modem function. + +The performance of V.8bis by the modem function is FFS. + +### 9.4.1 Mobile originated multimedia call + +#### 9.4.1.1 Call setup + +The setup message sent by the UE contains either a multimedia BC-IE indicating a multimedia only call request (i.e. no fallback to speech allowed) or both a speech BC-IE and a 3.1kHz multimedia BC-IE to indicate the support of a fallback to speech (see 3GPP TS 27.001 and 3GPP TS 24.008). + +The MSC shall not accept a requested service to which the user has no subscription. On the condition the user has the required subscriptions (i.e. to multimedia and/or speech) the following applies: + +- in case of a multimedia only BC-IE the MSC may accept the setup as such or with modifications sent to the UE in the call proceeding message (see 3GPP TS 27.001); +- in case of both a speech BC-IE and a 3.1kHz multimedia BC-IE the MSC may either accept the possibility of a fallback to speech by responding with two BC-IEs or turn the call to a speech call by sending only a speech BC-IE in the call proceeding message or turn the call to a multimedia only call by sending only a multimedia BC-IE in the call proceeding message (See 3GPP TS 27.001). + +The IWF V.34 modem shall initiate the ITU-T Recommendation V.8 handshaking and indicate the support of H.324/M in the call function category of the V.8 handshaking. If the called party's modem does not indicate a H.324 support in its V.8 inband signalling response, the IWF may clear the call. If the called party responds with a modem answering tone but there is no V.8 response at all, the IWF shall clear the call. + +If FNUR = 33.6 kbit/s is agreed on in the setup, the IWF shall configure its V.34 modem to operate in automode with an upper data rate limit of 33.6 kbit/s and a lower data rate limit of 28.8 kbit/s. If the modems handshake to 31.2 kbit/s or 28.8 kbit/s, the MSC shall initiate a MODIFY message (see 3GPP TS 24.008) to indicate the new data rate to the UE. HDLC flag stuffing or the stuffing mode defined in ITU-T Recommendation H.223 (Annexes A, B and C) shall be used to adapt the 31.2 kbit/s or 28.8 kbit/s data rate to the 33.6 kbit/s traffic channel between the UE and the IWF. In order to be able to use the correct stuffing pattern, the IWF shall detect the stuffing mode patterns exchanged between the multimedia terminals after the traffic channel setup (see ITU-T Recommendation H.324). The IWF may start the stuffing immediately after the detection of the used method. In downlink stuffing the IWF inserts stuffing patterns between the H.223 frames. In uplink stuffing the IWF removes stuffing patterns from between the H.223 frames received from the UE. If the UE responds with a MODIFY REJECT message, the MSC shall clear the call. + +#### 9.4.1.2 Fallback to speech after setup + +If the MSC has accepted the possibility of a fallback to speech and the IWF modem does not recognize the answering tone of the called modem within the expiration of a timer started at the reception of the answer message, the MSC IWF shall initiate an In Call Modification procedure (see 3GPP TS 24.008) in order to fall back to a speech mode. As a result of the procedure the IWF resource shall be released and a speech channel shall be set up between the calling UE and the fixed network. If the fallback fails e.g. due to a failing In Call Modification procedure, the IWF shall clear the call. + +A recommended minimum value for the timer is 3 seconds (see ITU-T Recommendation V.25). + +### 9.4.2 Mobile terminated multimedia call + +#### 9.4.2.1 Call setup + +If the user has a subscription to both the multimedia bearer service and the speech teleservice and if the network supports both services and the fallback functionality, the MSC shall send both a multimedia BC-IE and a speech BC-IE in the setup message to the user equipment. If the user has a subscription only to the multimedia bearer service the MSC shall send only a multimedia BC-IE. + +In case of both a speech BC-IE and a 3,1 kHz multimedia BC-IE in the setup the user equipment may either accept the possibility of a fallback to speech by responding with two BC-IEs or turn the call to a speech call by sending only a speech BC-IE in the call confirmed message or to a multimedia only call (i.e. no fallback to speech allowed) by sending only a multimedia BC-IE in the call confirmed message. In case of a multimedia only BC-IE in the setup the UE may accept the setup as such or with modifications sent to the MSC in the call confirmed message. + +If no service definition is available in the network, the MSC shall send no BC-IE(s) to the user equipment in the call setup. The MSC shall analyse the received BC-IE(s) and optionally perform a subscription check to the multimedia and/or speech service(s) requested by the user equipment in the call confirmed message and shall not accept a requested service rejected by the subscription check. + +The IWF V.34 modem shall await the ITU-T Recommendation V.8 handshaking to be initiated by the calling party's modem and shall recognize the support of H.324 in the call function category of the incoming V.8 handshaking. If the calling party's modem does not indicate a H.324 support in its V.8 inband signalling, the IWF may clear the call. If the calling modem tries to handshake another than V.34 modem scheme, the IWF shall clear the call. + +If FNUR = 33.6 kbit/s is agreed on in the setup, the IWF shall configure its V.34 modem to operate in automode with an upper data rate limit of 33.6 kbit/s and a lower data rate limit of 28.8 kbit/s. If the modems handshake to 31.2 or 28.8 kbit/s, the MSC shall initiate a MODIFY message (see 3GPP TS 24.008) to indicate the new data rate to the UE. HDLC flag stuffing or the stuffing mode defined in ITU-T Recommendation H.223 (Annexes A, B and C) shall be used to adapt the 31.2 or 28.8 kbit/s data rate to the 33.6 kbit/s traffic channel between the UE and the IWF. In order to be able to use the correct stuffing pattern, the IWF shall detect the stuffing mode patterns exchanged between the multimedia terminals after the traffic channel setup (see ITU-T Recommendation H.324). The IWF may start the stuffing immediately after the detection of the used method. In downlink stuffing the IWF inserts stuffing patterns between the H.223 frames. In uplink stuffing the IWF removes stuffing patterns from between the H.223 frames received from the UE. If the UE responds with a MODIFY REJECT message, the MSC shall clear the call. + +#### 9.4.2.2 Fallback to speech after setup + +If the MSC supports a fallback to speech and the user has a subscription to the speech service and the user equipment accepts the possibility of a fallback to speech in the call confirmed message and the IWF modem does not recognize a call tone nor a V.8 Call Indication nor a V.8 Call Menu within the expiration of a timer started at the sending of the ANSam answer tone (i.e. the calling party is not a V.34 modem), the IWF shall initiate an In Call Modification + +procedure (see 3GPP TS 24.008) in order to fall back to a speech mode. As a result of the procedure the IWF resource shall be released and a speech channel shall be set up between the called UE and the fixed network. If the fallback fails e.g. due to a missing subscription to speech or a failing In Call Modification procedure, the IWF shall clear the call. + +A recommended minimum timer value is 3 seconds (see ITU-T Recommendation V.8). + +### 9.4.3 Seamless data rate change + +If the modems change the data rate during an ongoing multimedia call (using the ITU-T Recommendation V.34 seamless data rate change mechanism), the MSC shall initiate a MODIFY message (see 3GPP TS 24.008) to indicate the new data rate to the UE. HDLC flag stuffing or the stuffing mode defined in ITU-T Recommendation H.223 (Annexes A, B and C) shall be used to adapt the 31.2 or 28.8 kbit/s data rate to the 33.6 kbit/s traffic channel between the UE and the IWF. The stuffing pattern found out during the traffic channel setup (see subclauses Call setup) is used. The IWF may start the stuffing immediately after the detection of the data rate change by the modems. + +--- + +## 10 Interworking to the ISDN + +The interworking to the ISDN is specified on the principle of the network supporting standardized associated signalling protocol as outlined in clause 6, i.e. DSS1 and ISUP. An ISDN not complying with this definition differs - for the purpose of the present document - in that it does not support the compatibility information to that degree necessary for deducing a PLMN Basic Service. These networks will find their reflection in the following where those implications are to be set out. + +The calling address sent in a mobile originated call to the ISDN is always the basic MSISDN even if the ISDN user shall use a different MSISDN (multi numbering scheme, see 9.2.2 case a) for a mobile terminated call (call back) as only the basic MSISDN is available at the VLR (see 3GPP TS 29.002). + +The scope of this clause is to describe the handling of the content of the Information Elements where "content" is understood to be the value of the parameter fields of the Information Elements, namely BC-IE, HLC and LLC, after the length indicator. For the transport of these Information Elements within the PLMN refer to 3GPP TS 29.002. + +The handling of multislot, 14.4kbit/s, EDGE and Iu Mode related parameters of the call control signalling and the applicability of single- or multislot configurations (refer to 3GPP TS 48.020 and 3GPP TS 44.021) is the same as for the PSTN interworking cases. + +### 10.1 Speech Calls + +Since at the interworking point the transcoder provides for A-law or $\mu$ -law (PCS-1900) PCM at 64 kbit/s, no particular interworking is required. It is anticipated that the ISDN Teleservice Telephony and ISDN Bearer Service speech, respectively would be used. Transmission aspects are covered in 3GPP TS 43.050. Any further requirements are a national matter. + +### 10.2 Data Calls + +In this case it is assumed that the ISDN bearer service 3,1 kHz audio shall only be interworked by means of a modem pool in the PLMN. If a network operator provides this facility, then the MSC/IWF operation will be similar to that described for interworking to the PSTN. + +Where the bearer capability information indicates that the call is a circuit switched unrestricted digital call, then the MSC/IWF shall select the appropriate rate adapted ISDN and PLMN bearer services. + +#### 10.2.1 Network interworking mobile originated + +Low layer compatibility checking of the mobile originated call is carried out by the MSC/IWF to determine the appropriate bearer service selection in the ISDN. This will entail the MSC/IWF in mapping appropriately the PLMN BC-IE to the ISDN BC-IE (bearer capability information element). If it is not possible for the MSC/IWF to provide a bearer service match, then the MSC/IWF shall fail the call and indicate the reason to the user. + +The UE shall provide further compatibility information (LLC/HLC-IEs) if required for defining end-to-end compatibility. + +As well as compatibility checking, subscription checking should be performed. + +The selection of the MSC/IWF will be by means of the bearer capability information within the call set up message. The mobile subscriber shall be able to select the unrestricted digital capability, which the MSC/IWF will map to the same capability in the ISDN call set up message. If an interworking point is encountered within the ISDN which does not support this service request, then either a call release message including an appropriate error cause or progress message is returned to the PLMN, indicating that the ISDN network is unable to support the service requested. In the case of a call release message the network shall release the call. In the case of progress message the network releases the call or forwards it (see 3GPP TS 24.008) to the mobile which will release the call. + +## 10.2.2 Network interworking mobile terminated + +### 10.2.2.1 General + +This subclause describes the interworking of calls where the calling subscriber can communicate ISDN compatibility information with exhaustive contents for deducing a PLMN Basic Service to a PLMN (gateway MSC/interrogating node) i.e. by means of ISDN signalling. + +The GMSC shall perform a mapping of the received Basic Service Information for the transport to the HLR, for details of this transport refer to 3GPP TS 29.002. + +Compatibility checking of the low layers of the ISDN originated call is carried out by the MSC/IWF to determine the appropriate bearer service selection in the PLMN. This will entail the MSC/IWF in mapping appropriately the ISDN BC/LLC-IE to the PLMN BC-IE. + +As well as compatibility checking, subscription checking should be performed. If either the subscription check or the compatibility check fails then the call will be rejected. + +For ISDN originated calls it will not be possible to signal mobile specific requirements e.g. transparent/non transparent, full/half rate channel. Therefore the MSC/IWF shall select a default setting appropriate to the visited PLMN's network capabilities. In general it will be beneficial, where a network supports both full and half rate channels and transparent/non transparent capabilities, to indicate so in the appropriate PLMN BC field of 3GPP TS 24.008. The mobile subscriber has the option to indicate in the call confirmation message a change to this default setting according to the rules specified in 3GPP TS 27.001. The appropriate MSC/IWF shall be selected on the basis of this requirement. + +### 10.2.2.2 Functions in GMSC + +At call Set-up, the interrogating node passes in the "send routing information" to the HLR, the ISDN BC, LLC and HLC received in the initial address message. The coding of these parameters shall comply with Q.931 (05/98). For MT calls, and for backward compatibility purposes only, the mapping of the modem type according to ETS 300-102-1 (12/90) shall also be accepted, see note 12 of table 7B. + +The information possibly signaled backwards from the VMSC to the GMSC contained in the access transport parameter of the Answer message (ANM) can be used to perform service related functions (e.g. accounting) at the GMSC. + +### 10.2.2.3 Functions in HLR + +According to the contents of the Compatibility Information, i.e. the ISDN BC, LLC and HLC received, the HLR applies one of the following: + +- 1) No ISDN BC is received, or one from which a PLMN Basic Service cannot be deduced (i.e. with the information Transfer Capability field set to "3,1 kHz audio" but without any associated modem type1 in the ISDN BC and LLC, or without HLC indication of group 3 facsimile). Two cases shall be considered: + - a) The called MSISDN has a corresponding PLMN BC stored in the HLR (see 9.2.2.1); then the service attached to this number in the HLR tables is applicable and the corresponding PLMN BC is passed to the VLR in the "Provide Roaming Number" request. See figure 8; + - b) The called MSISDN has no corresponding PLMN BC stored in the HLR (see 9.2.2.2). In this case no PLMN BC is passed to the VLR in the "Provide Roaming Number" request. +- 2) Compatibility Information is received from which a PLMN Basic Service can be deduced, i.e. the ITC field in the ISDN BC is "unrestricted digital" and the fields for the applicable user layer 1 protocol and user rate (except + +--- + +1 "Modem type" in connection with the ITC value "3,1 kHz audio" means hereafter that either an ISDN BC modem type value is present or the autobauding modem function is indicated (see note 16 of table 7B) + +for the 64kbit/s case, see Note 22 Table 7B) are available (in either the ISDN BC or the LLC), or the ITC field is "3,1 kHz audio", and a modem type, user rate, etc. is indicated but the HLC does not indicate "facsimile group 3". The received ISDN BC (and possibly LLC plus HLC) is then considered applicable regardless of the kind of MSISDN received (PLMN BC associated or not) and either the equivalent PLMN BC or the original ISDN BC/LLC is sent to the VLR. In both cases the originally received HLC may also be sent to the VLR; see figure 9. + +As an exception to this the BC stored in the HLR is regarded as valid if one of the following cases applies: + +- If ITC = UDI/RDI and User Rate = 32 kbit/s /56 kbit/s and User information layer 1 protocol = V.110, I.460/X.30 and the stored BC indicates FTM, PIAFS or Multimedia. +- If ITC = 3,1 kHz audio and User Rate = 28.8 kbit/s and Modem Type = V.34 and the stored BC indicates Multimedia. + +When the HLR interworks with a GSM phase 1 VPLMN (VLR/VMSC), then the HLR shall convert the ISDN BC to the equivalent PLMN BC, and forward it to the VLR. In this case the LLC cannot be forwarded. + +- 3) Compatibility Information is received from which the PLMN Teleservice category Facsimile transmission can be deduced, i.e. the ITC field in the ISDN BC is "3,1kHz audio" and the HLC indicates "facsimile group 3" (see figure 9). The following two cases shall be considered: + - a) The called MSISDN has a corresponding PLMN BC stored in the HLR (indicating either TS 61 or TS 62). In this case the service attached to the MSISDN in the HLR tables is applicable and the corresponding PLMN BC is passed to the VLR in the "Provide Roaming Number" request; see also subclause 10.3.1.3; + - b) The called MSISDN has no corresponding PLMN BC stored in the HLR. In this case the HLR shall forward the appropriate PLMN BC to the VLR in line with the subscriber's subscription to Teleservice TS 61 or TS 62. + +For TS 61 the value of the PLMN BC parameter "Information Transfer Capability" shall be set to "alternate speech/facsimile group 3, starting with speech". + +In both cases the HLC should be passed to the VLR in the "Provide Roaming Number" request. + +Alternatively the HLR may forward the originally received ISDN/LLC/HLC, when interworking with a GSM or later phase 2 VLR + +- 4) If the Compatibility Information received does not allow the HLR to deduce a PLMN Bearer Service, i.e. the ITC field in the ISDN BC is "unrestricted digital", but without the fields indicating the applicable user layer 1 protocol, user rate, etc. (in either the ISDN BC or the ISDN LLC), then the call is managed as for a UDI call according to subclause 9.2.2, i.e. either the "multi numbering" or "single numbering" scenario is applied depending on which capability is provided by the home PLMN/HLR. +- 5) Compatibility information is received, the ITC field in the ISDN BC is "speech" and this value differs from the ITC field in the PLMN BC stored in the HLR. Then the PLMN BC stored in the HLR is considered applicable and shall be sent to the VLR. + +If the HLR supports the option to return the MAP "GSM Bearer Capability" to the GMSC in the MAP "Send Routing Information" response, it shall pass the PLMN-BC stored in the HLR if the latter is considered applicable as per the preceding rules. Otherwise no MAP "GSM Bearer Capability" shall be returned. This requirement shall apply irrespectively of whether the MAP "Send Routing Information" response contains a MAP "MSRN", "GMSC Camel Subscription Info", "Forwarding Data" or not. As an exception, to avoid transferring twice the MAP "GSM Bearer Capability" for a call involving two MAP "Send Routing Information" procedures to the HLR, the HLR should not include the MAP "GSM Bearer Capability" in the MAP "Send Routing Information" response if the MAP "Send Routing Information" request contains the MAP "Suppress T-CSI" IE. + +#### 10.2.2.4 Functions in VMSC + +When the incoming call arrives, the VMSC attempts to derive a PLMN basic service from the information received in the IAM, and requests information from the VLR to handle the call. In general, the LLC and HLC are sent with the PLMN BC to the UE at call set-up. In particular, however the following rules apply: + +- 1) If the Initial Address Message (IAM) contains no ISDN BC and no PLMN or ISDN BC/LLC/HLC was retrieved from the VLR, the call is handled as in subclause 9.2.2.2. + +- 2) If there is no ISDN BC in the IAM but a PLMN or ISDN BC/LLC/HLC was retrieved from the VLR, the PLMN or ISDN BC/LLC/HLC retrieved from the VLR applies. +- 3) If there is an ISDN BC in the IAM with the ITC field set to "3,1 kHz audio" but without any associated modem type or indication of facsimile group 3 in the HLC, the PLMN or ISDN BC/LLC/HLC retrieved from the VLR is considered as applicable when it exists. If no PLMN or ISDN BC is retrieved from the VLR, the call is handled as in subclause 9.2.2.2. +- 4) If there is an ISDN BC in the IAM with the ITC field set to "unrestricted digital information" and the fields for the applicable user layer 1 protocol and user rate (except for the 64kbit/s case; see note 22 to table 7B) are available (either in the ISDN BC or ISDN LLC), or if 3,1 kHz audio and a modem type is indicated, this ISDN BC is applicable regardless of what has been retrieved from the VLR. In this case the ISDN BC shall be mapped to an appropriate PLMN BC (refer to table 7B). + +As an exception to this the BC retrieved from the VLR is sent to the UE if one of the following applies: + +If ITC = UDI/RDI and User Rate = 32 kbit/s /56 kbit/s and User information layer 1 protocol = V.110, I.460/X.30 and the BC retrieved from the VLR indicates FTM, PIAFS or Multimedia. + +If ITC = 3,1 kHz audio and User Rate = 28,8 kbit/s and Modem Type = V.34 and the BC retrieved from the VLR indicates Multimedia. + +- 5) If there is an ISDN BC in the IAM with the ITC field set to "3,1kHz audio" and there is an HLC indicating "facsimile group 3", the PLMN BC retrieved from the VLR is applicable when it exists. If a PLMN BC with the parameter "information transfer capability" set to "alternate speech/facsimile group 3, starting with speech" (i.e. TS 61) is retrieved from the VLR, this shall be mapped to two PLMN BC-IEs preceded by a repeat indicator, one representing speech, the other representing facsimile group 3. + +For TS 61, the order in which the two PLMN BC-IEs are sent towards the UE in the setup message is a network option. + +- 6) If there is an ISDN BC in the IAM with the ITC field set to "unrestricted digital information" but without applicable "user layer 1 protocol" and "user rate", etc. fields, in either the ISDN BC or the ISDN LLC, then the PLMN or ISDN BC/LLC retrieved from the VLR is applicable, if available, otherwise subclause 9.2.2.2 applies. +- 7) If there is an ISDN BC in the IAM with the ITC field set to "Speech" and this value differs from the ITC field of the BC retrieved from the VLR for this call, then the BC/LLC/HLC retrieved from the VLR is considered applicable. If no PLMN or ISDN BC is retrieved from the VLR, the call is handled as in subclause 9.2.2.2. + +In all cases where the VMSC retrieves a PLMN BC from the VLR, the VMSC may add or modify PLMN-specific parameters in the PLMN BC, as described in subclause 9.2.2, before sending the PLMN BC-IE towards the UE. + +In all cases when no PLMN or ISDN BC is retrieved from the VLR and no ISDN Compatibility information allowing deduction of a PLMN Bearer Service is available, then no PLMN BC is inserted by the VMSC and subclause 9.2.2.2 applies. + +The mapping between PLMN and ISDN BCs is shown in table 7. + +The UE may negotiate parameters with the MSC according to the rules defined in 3GPP TS 27.001. If the UE proposes to the network to modify the User Rate as well as the correlated parameters Modem Type and Intermediate Rate in the call confirmed message, the network may accept or release the call (see 3GPP TS 27.001). For multislot, 14.4kbit/s, EDGE and Iu Mode operations, the UE may also propose to the network to modify the Fixed Network User Rate and Other Modem Type parameters (see 3GPP TS 27.001). In case a transparent service is used, the call shall be released. For a non-transparent service with flow control, the MSC/IWF shall use towards the fixed network the unmodified "fixed network user rate" and shall use the "wanted air interface user rate" or the modified "fixed network user rate" towards the user equipment. + +The VMSC may map the received PLMN BC into an ISDN BC according to the rules defined in table 7A. This ISDN BC can be transported together with possibly available LLC and HLC in the access transport parameter of the Answer message (ANM) according to ITU-T Q.763. + +#### 10.2.2.4A Functions in VLR + +When the VLR receives from the VMSC a request for information to handle an incoming call, it performs two functions: + +- 1) It determines the basic service which applies for the call, according to the following principles: + - a) If the basic service received in the request from the VMSC was the same as the basic service indicated by the compatibility information received in the "Provide Roaming Number" request, the VLR applies that basic service. + - b) If the basic service received in the request from the VMSC was Telephony but the compatibility information received in the "Provide Roaming Number" request indicated a basic service different from Telephony, the VLR applies the basic service derived from the compatibility information received in the "Provide Roaming Number" request. + - c) If the basic service received in the request from the VMSC was Facsimile Group 3 and the compatibility information received in the "Provide Roaming Number" request indicated Alternate Speech and Facsimile Group 3, the VLR applies the basic service Alternate Speech and Facsimile Group 3. + - d) If the basic service received in the request from the VMSC was Telephony and no compatibility information was received in the "Provide Roaming Number" request, the VLR applies the basic service Telephony. + - e) If the basic service received in the request from the VMSC was Facsimile Group 3 but no compatibility information was received in the "Provide Roaming Number" request, the VLR checks the subscription information stored in its database, and applies the appropriate subscribed basic service (Facsimile Group 3 or Alternate Speech and Facsimile Group 3). + - f) If the basic service received in the request from the VMSC was anything except Telephony or Facsimile Group 3, the VLR applies the basic service received in the request from the VMSC, regardless of any information received in the "Provide Roaming Number" request or stored subscription information. + - g) If no basic service was received in the request from the VMSC but compatibility information was received in the "Provide Roaming Number" request, the VLR applies the basic service derived from the compatibility information received in the "Provide Roaming Number" request. + - h) If no basic service was received in the request from the VMSC and no compatibility information was received in the "Provide Roaming Number" request, the VLR applies the basic service determined by the network operator, taking account of the subscribed basic services. +- 2) It returns compatibility information (PLMN BC or ISDN BC, and possibly ISDN HLC and ISDN LLC, according to the following principles: + - a) If the request from the VMSC included a basic service Facsimile Group 3, the VLR checks the subscription information stored in its database, and returns the appropriate compatibility information according to the subscribed basic service: + - i) A PLMN BC with the parameter "information transfer capability" set to "alternate speech/facsimile group 3, starting with speech" (i.e. TS 61) if the subscribed basic service is Alternate Speech and Facsimile Group 3; + - ii) A PLMN BC with the parameter "information transfer capability" set to " facsimile group 3" (i.e. TS 62) if the subscribed basic service is Facsimile Group 3. + - b) If the request from the VMSC did not include a basic service Facsimile Group 3 and compatibility information was received in the "Provide Roaming Number" request, the VLR processes the compatibility information received in the "Provide Roaming Number" request: + - i) If the compatibility information received in the "Provide Roaming Number" request consisted of an ISDN BC/LLC/HLC the VLR maps this to an appropriate PLMN BC as shown in table 7B. + - ii) If the compatibility information received in the "Provide Roaming Number" request consisted of a PLMN BC, possibly with an ISDN LLC/HLC, the VLR retains the PLMN BC + +- c) If the request from the VMSC did not include a basic service Facsimile Group 3 and no compatibility information was received in the "Provide Roaming Number" request, the VLR sends no compatibility information to the VMSC. + +## 10.2.2.5 Call Flows + +![Sequence diagram showing call flow for a mobile terminated, ISDN originated call. Lifelines: UE, VMSC, VLR, HLR, IN. The sequence starts with an IAM from IN to HLR, followed by SRI, PRN, and MSRN messages. The VMSC sends a Setup message to the UE, which responds with Call Conf. and Connect. The VMSC then sends an ANM to the IN. The diagram is annotated with (1), (2), and (3) on the right side.](ddee3e67e0dfc22e25188fa635a19558_img.jpg) + +``` + +sequenceDiagram + participant IN + participant HLR + participant VLR + participant VMSC + participant UE + + Note right of IN: (1) + IN->>HLR: IAM (3,1 kHz, MSISDNk) + HLR->>VLR: SRI (3,1 kHz, MSISDNk) + VLR->>HLR: PRN (BCgk) + HLR->>VLR: MSRN + VLR->>IN: MSRN + IN->>VLR: IAM (3,1 kHz, MSRN) + VLR->>VLR: SIFICSU (MSRN) + VLR->>VLR: Comp. Call (BC' gk) + VMSC->>UE: Setup (BC' gk) + Note right of UE: (2) + UE->>VLR: Call Conf. (BC''gk) + Note right of UE: (3) + UE->>VLR: Connect + VLR->>IN: ANM (BC'''gk) + +``` + +Sequence diagram showing call flow for a mobile terminated, ISDN originated call. Lifelines: UE, VMSC, VLR, HLR, IN. The sequence starts with an IAM from IN to HLR, followed by SRI, PRN, and MSRN messages. The VMSC sends a Setup message to the UE, which responds with Call Conf. and Connect. The VMSC then sends an ANM to the IN. The diagram is annotated with (1), (2), and (3) on the right side. + +- NOTE: (1) Some parameters of BCgk may be provided/modified according to the MSC's capabilities/preferences. See subclause 9.2.2. + (2) In the "Call Confirm" message, the UE may modify some parameters of the PLMN BC. See subclause 9.2.2. + (3) The VMSC may map the PLMN BC (BC''gk) into an ISDN BC (BC'''gk) according to the rules defined in table 7A + (4) Abbreviations: see figure 2. + +**Figure 8: Call Flow for a mobile terminated, ISDN originated call** + where compatibility information provided are not exhaustive for deducing a PLMN Bearer Service, but Information Transfer Capability = 3,1 kHz audio, no modem type and no HLC IE indicating facsimile group 3 HLR stores PLMN BC against MSISDN number multi-numbering scheme + +![Sequence diagram showing call flow for a mobile terminated, ISDN originated call between UE, VMSC, VLR, HLR, and IN.](32ff77da4286b58c4778033acaa10836_img.jpg) + +``` + +sequenceDiagram + participant UE + participant VMSC + participant VLR + participant HLR + participant IN + + Note right of IN: IAM +(LLC HLC BCij) +(6) + IN->>HLR: SRI + Note right of HLR: (LLC HLC BCij) + HLR->>VLR: PRN +(GSM BCgj/HLC or BCij/LLC/HLC) + Note right of VLR: (1) +(6) + VLR->>HLR: (MSRN) + HLR->>IN: (MSRN) + Note right of IN: (2) + IN->>VMSC: IAM +(BC'ij, MSRN) + Note right of VMSC: (3) + VMSC->>VLR: SIFICSU +(MSRN) + VLR->>VMSC: Comp. Call +(GSM BCgj/HLC or BCij/LLC/HLC) + Note right of VMSC: (4) + VMSC->>UE: Setup +(BC'gj, LLC, HLC) + Note right of UE: (5) + UE->>VMSC: Call Conf. +(BC''gj, LLC, HLC) + VMSC->>UE: Connect + Note over UE, VMSC: ..... + VMSC->>IN: ANM +(BC'''gj, LLC, HLC) + Note right of IN: (7) + +``` + +Sequence diagram showing call flow for a mobile terminated, ISDN originated call between UE, VMSC, VLR, HLR, and IN. + +- NOTES: +- (1) BCij denotes ISDN BC\*; BCgj is the corresponding PLMN BC. + - (2) Assumes signalling capabilities permit the transfer of BC between IN and VMSC. If this is not the case, the VLR uses the stored BC/LLC/HLC. + - (3) BC'ij denotes BCij as maybe modified by intervening networks. + - (4) Some parameters of BCgj may be provided/modified according to the MSC's capabilities/preferences. See subclause 9.2.2. + - (5) In the "Call Confirm" message, the UE may modify some parameters of the BC. See subclause 9.2.2. + - (6) For details on how the BC, HLC, and LLC are transported, refer to 3GPP TS 29.002. +\* HLC and LLC refers to ISDN values. + - (7) The VMSC may map the PLMN BC (BC''gj, LLC, HLC) into an ISDN BC (BC'''gj, LLC, HLC) according to the rules defined in table 7A + - (8) Abbreviations: see figure 2. + +**Figure 9: Call Flow for a mobile terminated, ISDN originated call where compatibility information provided are sufficient information to deduce a PLMN Bearer Service or Information Transfer Capability = 3,1 kHz audio with HLC IE indicating facsimile group 3** + +### 10.2.2.6 Mapping Functions + +The following tables (7A + 7B) show that only the ISDN BC is used for mapping (exceptions are indicated). + +NOTE: The ISDN/PLMN BC-IE mapping shall be performed as specified in tables 7A and 7B. This shall be done to allow setup of a compatible end-to-end connection between two UEs or one UE and an ISDN terminal. + +In the following tables 7A and 7B the comparison is drawn between parameters in the PLMN call set up request message and that of the ISDN call set up request message. In some cases no comparable values are available and these will be marked as such. In these cases reference will need to be made to the table of network interworking in 3GPP TS 29.007 to identify the appropriate choice. In some cases it is not necessary to support a particular option, and in this case those parameters will be annotated appropriately. + +The PLMN parameters and values are as in 3GPP TS 24.008 in combination as in 3GPP TS 27.001. The ISDN parameters and values are as in Q.931 (05/98). + +**Table 7A: Comparable setting of parameters in PLMN and ISDN: Mobile Originated** + +| Octet | PLMN BC parameter value | Octet | ISDN BC parameter value | +|-------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 1 | Bearer Capability IEI | 1 | Bearer Capability IEI | +| 2 | Length of BC contents | 2 | Length of BC contents | +| 3
#7..6 | Radio channel requirement
half rate channel
full rate channel
dual, full, rate preferred
dual, half rate preferred | | No comparable field | +| 3
#5 | Coding Standard
GSM standard coding | 3
#7..6 | Coding Standard
CCITT standardized coding | +| 3
#4 | Transfer mode
circuit mode
packet mode (note 7) | 4
#7..6 | Transfer mode
circuit mode
packet mode | +| 3
#3..1 | Information transfer capability
speech
unrestricted digital
3,1 kHz audio ex PLMN
facsimile group 3 (note 1)
other ITC (see octet 5a) | 3
#5..1 | Information transfer capability
speech
unrestricted digital
3,1 kHz audio
3,1 kHz audio
no comparable value | +| 5a
#7..6 | Other ITC
restricted digital | | (note 18) | +| 4
#7 | Compression (note 14)
data compression allowed
data compression not allowed | | No comparable field | +| 4
#6..5 | Structure
SDU integrity
unstructured | 4a
#7..5 | Structure (note 4) | +| 4
#4 | Duplex mode
half duplex
full duplex | 5d
#7 | Duplex mode
half duplex
full duplex | +| 4
#3 | Configuration
point to point | 4a
#4..3 | Configuration (note 4) | +| 4
#1 | Establishment
demand | 4a
#2..1 | Establishment (note 4) | +| 4 | NIRR (note 12)
no meaning
Data $\leq$ 4.8kbit/s, FR nt,
6kbit/s radio interface is requested | | No comparable field | +| 5
#5..4 | Rate adaptation
no rate adaptation (note 2)
V.110, I.460/X.30 rate adaptation

CCITT X.31 flag stuffing (note 25)

No comparable value(note 11)
No comparable value(note 11)

No comparable value(note 11)

other rate adaptation (see octet 5a) | 5
#5..1 | User information layer 1 protocol
no comparable value
CCITT standardized rate adaption
V.110, I.460/X.30
(note 25)
Recommendation G.711 $\mu$ -law
Recommendation G.711 A-law (note 3)
Recommendation G.721 32 kbit/s
ADPCM and I.460
No comparable value | +| 5a
#5..4 | Other rate adaptation
V.120 (note 17)
PIAFS (note 27)
H.223 & H.245 | | No comparable value

H.223 & H.245 (note 26) | +| 5
#3..1 | Signalling access protocol
I.440/I.450
X.21 (note 24)
X.28, ded.PAD, indiv.NUI (note 24)
X.28, ded PAD, univ.NUI (note 24)
X.28, non-ded PAD (note 24)
X.32 (note 24) | | No comparable field | +| 6
#1 | Synchronous/asynchronous
synchronous
asynchronous | 5a
#7 | Synchronous/asynchronous
synchronous
asynchronous | +| 6
#5..2 | User info. layer 1 protocol
default layer 1 protocol | 5
#5..1 | User info. layer 1 protocol
see section under rate adaptation for
3GPP TS 24.008 above | + +| Octet | PLMN BC parameter value | Octet | ISDN BC parameter value | +|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 6a
#7 | Number of stop bits
1 bit
2 bits | 5c
#7..6 | Number of stop bits
1 bit
2 bits | +| 6a
#6 | Negotiation
In band neg. not possible
no comparable value | 5a
#6 | Negotiation
In band neg. not possible
In band neg. possible (note 10) | +| 6a
#5 | Number of data bits
7 bits
8 bits | 5c
#5..4 | Number of data bits excluding parity if present
7 bits
8 bits | +| 6a
#4..1 | User rate
0.3 kbit/s
1.2 kbit/s
2.4 kbit/s
4.8 kbit/s
9.6 kbit/s
12 kbit/s (note 7)
1.2 kbit/s / 75 bit/s (note 24)
any value
no comparable value | 5a
#5..1 | User rate
0.3 kbit/s
1.2 kbit/s
2.4 kbit/s
4.8 kbit/s
9.6 kbit/s
12 kbit/s
75 bit/s / 1.2 kbit/s
19.2 kbit/s (note 14)
Ebites or inband negotiation (note 10) | +| 6b
#7..6 | Intermediate rate
8 kbit/s
16 kbit/s
any value | 5b
#7..6 | Intermediate rate (note 13)
8 kbit/s or not used
16 kbit/s or not used
32 kbit/s or not used (note 14) | +| 6b
#5 | NIC on Tx
does not require
requires (note7) | 5b
#5b | NIC on Tx
does not require
requires (note 8) | +| 6b
#4 | NIC on Rx
cannot accept
can accept (note 7) | 5b
#4 | NIC on Rx
cannot accept
can accept (note 8) | +| 6b
#3..1 | Parity information
odd
even
none
forced to 0
forced to 1 | 5c
#3..1 | Parity information
odd
even
none
forced to 0
forced to 1 | +| 6c
#7..6 | Connection element
transparent
non-transparent (RLP)
both, transp. preferred
both, non-transp. preferred | | No comparable field | +| 6c
#5..1 | Modem type
none
V.21
V.22
V.22bis
V.23 (note 24)
V.26ter
V.32
modem for undef. interface
autobauding type 1 | 5d
#6..1 | Modem type
no comparable value (note 5)
V.21
V.22
V.22bis
V.23
V.26ter
V.32
No comparable value (note 5)
No comparable value (note 5, note 10) | +| 7
#5..1 | User info. layer 2 protocol
X.25 link level (note 24)
ISO 6429, codeset 0
COPnoFICt
videotex profile 1 (note 7)
X.75 layer 2 modified (CAPI) (note 24) | 6 | User info.layer 2 prot. (note 6)
X.25 link level
no comparable value
no comparable value
no comparable value
X.25 link level | + +| Octet | PLMN BC parameter value | Octet | ISDN BC parameter value | +|-------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 6d
#5..1 | Fixed network user rate (note 15)
FNUR not applicable (note 7)
9,6 kbit/s
12 kbit/s (note 7)
14,4 kbit/s
19,2 kbit/s
28,8 kbit/s
32,0 kbit/s
33,6 kbit/s
38,4 kbit/s
48,0 kbit/s
56,0 kbit/s
64,0 kbit/s | 5a
#5..1 | User rate
no comparable value
9,6 kbit/s
12 kbit/s
14,4 kbit/s
19,2 kbit/s
28,8 kbit/s
32,0 kbit/s
no comparable value
38,4 kbit/s
48,0 kbit/s
56,0 kbit/s
no comparable value (note 16) | +| 6e
#3..1 | Maximum number of traffic channels
1 TCH
2 TCH
3 TCH
4 TCH
5 TCH
6 TCH
7 TCH (note 7)
8 TCH (note 7) | | No comparable field | +| 6f
#4..1 | Wanted air interface user rate (note 23)
air interface user rate not applicable (note 7)
9,6 kbit/s
14,4 kbit/s
19,2 kbit/s
28,8 kbit/s
38,4 kbit/s
43,2 kbit/s
57,6 kbit/s
interpreted by the network as 38.4 kbit/s (note 7) | | No comparable field | +| 6d
#7..6 | Other modem type (note 15)
No other modem type
V.34 | 5d
#6..1 | Modem type
no comparable value
V.34 | +| 6e
#7..4 | Acceptable channel coding(s)
TCH/F4.8 acceptable (note 19)
TCH/F9.6 acceptable
TCH/F14.4 acceptable | | No comparable field | +| 6f
#7..5 | User initiated modification indicator (note 23)
User initiated modification not required
User initiated modification upto 1
TCH/F may be requested
User initiated modification upto 2
TCH/F may be requested
User initiated modification upto 3
TCH/F may be requested
User initiated modification upto 4
TCH/F may be requested | | No comparable field | +| 6g
#7..5 | Acceptable channel coding(s) (note 20)
TCH/F28.8 acceptable
TCH/F32.0 acceptable
TCH/F43.2 acceptable (note 22) | | No comparable field | +| 6g
#4..3 | Asymmetry preference indication (Note 23)
no preference
up link biased asymmetry preference
down link biased asymmetry preference | | No comparable field | + +The application rules for coding the information elements ISDN-BC/LLC/HLC as set out in ETR 018 and Q.931 (05/98) shall apply. + +Other field values in the ISDN BC-IE not supported in 3GPP TS 24.008 are: + +Information transfer rate: In this case default 64 kbit/s is selected. + +Flow control on transmission: + +Flow control on reception: This shall be selected if outband flow control applies. Outband flow control is indicated by the absence of the UIL2P parameter for non-transparent connections. + +User information layer 3 protocol: Octet 7 shall not be sent unless specific application rules are given for particular cases (to be defined by PLMN). End-to-end significant User Information layer 3 protocol shall be sent by LLC. + +Notes regarding particular entries in table 7A: + +NOTE 1: If the PLMN BC "Information Transfer Capability" indicates "Facsimile group 3" and only a single PLMN BC is contained in the call set-up request then this shall be mapped to an ISDN BC with: + +- coding standard: CCITT; +- information transfer capability: 3,1 kHz audio; +- transfer mode: circuit; +- information transfer rate: 64 kbit/s; +- user layer 1 protocol: G711 A-law or $\mu$ -law (PCS-1900); and +- if an HLC is not present, the network will insert a "Facsimile group 2/3" HLC; +- if an HLC element is present, the network will pass it through unmodified. + +If the PLMN BC "Information Transfer Capability" indicates "Facsimile group 3" and two PLMN BCs are contained in the call set-up request, then the same ISDN BC as mentioned above is created. If the first PLMN BC indicates "facsimile group 3" an HLC "facsimile group 2/3" will be inserted by the network (if not received from the UE). However if the first PLMN BC indicates "speech", the network will not send a HLC, irrespective where a HLC was received from the UE or not. + +NOTE 2: This value is present in combination with information transfer capability parameter value "3,1 kHz audio Ex PLMN" or "facsimile group 3" and will therefore be mapped to the value "Recommendation G.711 A-law" or "Recommendation G.711 $\mu$ -law" (PCS-1900) of the Q.931 (05/98) parameter user layer 1 protocol (see note 3). + +NOTE 3: The value "Recommendation G.711 A-law" or "Recommendation G.711 $\mu$ -law" (PCS-1900) applies only when the Q.931 (05/98) parameter information transfer capability indicates "3,1 kHz audio" or "speech". + +NOTE 4: When interworking with an ISDN according to ETS 300 102-1 octets 4a and 4b shall not be included because default values apply. In an ISDN according to Q.931 (05/98) these octets no more exist. + +NOTE 5: In this case octet 5d shall not be included. + +NOTE 6: Octet 6 shall not be sent unless specific application rules are given for a particular case (PLMN specified). End-to-end significant user information layer 2 protocol shall be sent by LLC. + +NOTE 7: Not used for currently defined Bearer Services and Teleservices. + +NOTE 8: These values will only be set if the "Information Transfer Capability" indicates "3,1 kHz audio", synchronous data transmission is used and octet 5b of the ISDN BC is present. + +NOTE 9: (VOID). + +NOTE 10: The PLMN BC-IE parameter value "autobauding modem type 1" will be mapped to the ISDN BC-IE parameter values "inband negotiation possible" and "user rate indicated by E-bits specified in ITU-T Recommendation I.460 or may be negotiated inband" (octet 5a of ISDN BC-IE). If data compression is used, high speed modems, like V.32bis, V.34 and/or V.90 may be used in the IWF. Autobauding may also be used to support user rates less than 9.6 kbit/s towards the PSTN. + +NOTE 11: The ITC value of the PLMN BC-IE "speech", "3,1 kHz audio Ex PLMN" will indicate these requirements. + +NOTE 12: For the use of NIRR see 3GPP TS 27.001. + +NOTE 13: The value of the Intermediate Rate field of the ISDN Bearer Capability information element shall only depend on the values of the User Rate and the Information Transfer Capability in the same information element. The correspondence is: + +Intermediate Rate = not used if User Rate > than 19.2 kbit/s. + Intermediate Rate = 32 kbit/s if User Rate = 19,2 kbit/s or 14.4 kbit/s. + Intermediate Rate = 16 kbit/s if User Rate = 9,6 kbit/s. + Intermediate Rate = 8 kbit/s otherwise. + +For Audio calls the value of the Intermediate Rate may be set to "not used". + +NOTE 14: If compression is supported by the MSC and "data compression allowed" is indicated, then the ISDN user rate for UDI calls shall be set as follows. If the parameter "FNUR" is present the ISDN user rate shall be set to this value. Otherwise the PLMN user rate shall be mapped to an equal or any higher ISDN user rate value (for V.110 the highest ISDN user rate shall be 19,2 kbit/s). The Intermediate Rate shall be set to an appropriate value.(see subclause 10.2.4.11). + +For "3,1 kHz audio" the modem shall try to negotiate data compression and flow control (see subclause 9.2.4.11). For "autobauding type 1" high speed modems may be used (see note 10). + +NOTE 15: User rate of the PLMN -BC is overridden by the fixed network user rate of the PLMN BC-IE if available. When the MT indicates „autobauding", „modem for undefined interface" or „none", the other modem type shall be set to „no other modem type"; any other value of the modem type is overridden by the other modem type value (see 3GPP TS 27.001). In Iu mode, if octet 6d is not present in the PLMN BC, the MSC shall reject the call. The support of user rates lower than 9.6 kbit/s in Iu mode are only possible in the scope of autobauding (see note 10). + +NOTE 16: In the case Other rate adaptation = H.223 & H.245 the ISDN BC-IE shall be coded as follows: + +Coding standard: ITU-T + Information Transfer capability: UDI + Transfer mode: circuit + Information transfer rate: 64 kbit/s + User information layer 1 protocol: H.223 & H.245 + +In all the other cases the ISDN-BC will consist of the octets 1 to 4 only, coded: + +Coding standard: CCITT + Information Transfer capability: UDI + Transfer mode: circuit + Information transfer rate: 64 kbit/s + +NOTE 17: V.120 interworking is selected. + +If an LLC element is not present, the network will insert an LLC. If an LLC is present it may be modified. The PLMN -BC parameters negotiated with the UE shall be mapped to the LLC parameters. The LLC parameter Rate Adaptation will be set to "V.120". + +When interworking with unrestricted 64 kbit/s networks the ISDN BC shall be coded according to note 16. + +NOTE 18: When the MSC is directly connected to a restricted 64 kbit/s network, the ISDN BC-IE is coded with an ITC = RDI. + +When indirectly interworking with a restricted 64 kbit/s network the ISDN BC-IE shall be coded according to ETR 018, as shown below: + +| | | +|------------------------------------|----------------------------------| +| Coding standard: | CCITT | +| Information Transfer capability: | UDI | +| Transfer mode: | circuit | +| Information transfer rate: | 64 kbit/s | +| User information layer 1 protocol: | V.110/X.30 | +| Synchronous/Asynchronous: | synchronous | +| Negotiation: | In-band negotiation not possible | +| User rate: | 56 kbit/s | + +If an LLC element is not present, the network will insert an LLC. If an LLC is present it may be modified. The PLMN -BC parameters negotiated with the UE shall be mapped to the LLC parameters according to the rules in this table. The LLC parameter Information Transfer Capability will be set to „restricted digital“ + +NOTE 19: If the UE signals an ACC containing TCH/F4.8 only and the network does not support TCH/F4.8 channel coding, then the MSC may act as if TCH/F9.6 were included in the ACC. + +NOTE 20: Extension of the 'Acceptable channel codings' field in octet 6e if EDGE channel codings are supported. + +NOTE 21: Void + +NOTE 22: Only applicable for non-transparent services. + +NOTE 23: This parameter shall be included if EDGE channel codings are indicated in ACC. In cases where this parameter would not otherwise be included, the value is set to 'Air interface user rate not applicable' or 'User initiated modification not requested' or 'No preference'. + +NOTE 24: This value was used by services defined for former PLMN releases and does not need to be supported. + +NOTE 25: The case of FTM is identified by Rate adaptation in the PLMN BC-IE set to "CCITT X.31 flag stuffing", Connection element set to "non-transparent", and Synchronous/asynchronous set to "asynchronous". The MSC applies one of the following alternatives: + +1) IF FNUR=64 kbit/s + +- the ISDN BC-IE shall be coded as follows: + +| | | +|----------------------------------|-----------| +| Coding standard: | ITU-T | +| Information Transfer capability: | UDI | +| Transfer mode: | circuit | +| Information transfer rate: | 64 kbit/s | + +- the LLC-IE shall be coded according to ETR 018 as follows: + +| | | +|------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------| +| Coding standard: | ITU-T | +| Information Transfer capability: | UDI | +| Transfer mode: | circuit | +| Information transfer rate: | 64 kbit/s | +| User information layer 1 protocol: | (CCITT standardized rate adaptation X.31 HDLC flag stuffing) (note: the absence of octet 5 indicates that HDLC flag stuffing applies) | +| User information layer 2 protocol: | Recommendation X.25, link layer | +| User information layer 3 protocol: | Recommendation X.25, packet layer | + +If user information layer 1 protocol is indicated by absence of octet 5 user information layer 2/3 protocol are also absent. + +2) If FNUR=56 kbit/s and the MSC is directly connected to a restricted 64 kbit/s network: + +- the ISDN BC-IE shall be coded as follows: + +| | | +|----------------------------------|-----------| +| Coding standard: | ITU-T | +| Information Transfer capability: | RDI | +| Transfer mode: | circuit | +| Information transfer rate: | 64 kbit/s | + +- the LLC-IE shall be coded as follows: + +| | | +|------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------| +| Coding standard: | ITU-T | +| Information Transfer capability: | RDI | +| Transfer mode: | circuit | +| Information transfer rate: | 64 kbit/s | +| User information layer 1 protocol: | (CCITT standardized rate adaptation X.31 HDLC flag stuffing) (note: the absence of octet 5 indicates that HDLC flag stuffing applies) | +| User information layer 2 protocol: | Recommendation X.25, link layer | +| User information layer 3 protocol: | Recommendation X.25, packet layer | + +If user information layer 1 protocol is indicated by absence of octet 5 user information layer 2/3 protocol are also absent. + +3) If FNUR=56 kbit/s and the MSC is indirectly interworking with a restricted 64 kbit/s network: + +- the ISDN BC-IE shall be coded according to ETR 018, as shown below: + +| | | +|------------------------------------|----------------------------------| +| Coding standard: | ITU-T | +| Information Transfer capability: | UDI | +| Transfer mode: | circuit | +| Information transfer rate: | 64 kbit/s | +| User information layer 1 protocol: | V.110/X.30 | +| Synchronous/Asynchronous: | synchronous | +| Negotiation: | In-band negotiation not possible | +| User rate: | 56 kbit/s | + +- If an LLC element is not present, the network will insert an LLC. If an LLC is present it may be modified. The PLMN -BC parameters negotiated with the MS shall be mapped to the LLC parameters according to the rules in this table. The LLC parameter Information Transfer Capability will be set to „restricted digital" and the LLC parameter User information layer 1 protocol will be set to “X.31 flag stuffing”. + +NOTE 26: If FNUR=64 kbit/s the ISDN BC-IE shall be coded as follows: + +| | | +|------------------------------------|-----------------| +| Coding standard: | ITU-T | +| Information Transfer capability: | UDI | +| Transfer mode: | circuit | +| Information transfer rate: | 64 kbit/s | +| User information layer 1 protocol: | H.223 and H.245 | + +If FNUR=56 kbit/s the ISDN BC-IE shall be coded as in note 18. + +If FNUR=32 kbit/s the ISDN BC-IE shall be coded as follows: + +| | | +|------------------------------------|----------------------------------| +| Coding standard: | ITU-T | +| Information Transfer capability: | UDI | +| Transfer mode: | circuit | +| Information transfer rate: | 64 kbit/s | +| User information layer 1 protocol: | V.110, I.460 & X.30 | +| Synchronous/Asynchronous: | synchronous | +| Negotiation: | In-band negotiation not possible | +| User rate: | 32 kbit/s | + +If FNUR=28.8 kbit/s the ISDN BC-IE shall be coded as follows: + +| | | +|------------------------------------|----------------------------------| +| Coding standard: | ITU-T | +| Information Transfer capability: | 3,1 kHz Audio | +| Transfer mode: | circuit | +| Information transfer rate: | 64 kbit/s | +| User information layer 1 protocol: | G.711 A-law or $\mu$ -law | +| Synchronous/Asynchronous: | synchronous | +| Negotiation: | In-band negotiation not possible | +| Modem type: | V.34 | +| User rate: | 28.8 kbit/s | + +If FNUR=33.6 kbit/s the ISDN BC-IE shall be coded as follows: + +| | | +|------------------------------------|---------------------------| +| Coding standard: | ITU-T | +| Information Transfer capability: | 3,1 kHz Audio | +| Transfer mode: | circuit | +| Information transfer rate: | 64 kbit/s | +| User information layer 1 protocol: | G.711 A-law or $\mu$ -law | + +NOTE 27: If FNUR=32 kbit/s the ISDN BC-IE shall be coded for PIAFS as follows: + +| | | +|------------------------------------|----------------------------------| +| Coding standard: | ITU-T | +| Information Transfer capability: | UDI | +| Transfer mode: | circuit | +| Information transfer rate: | 64 kbit/s | +| User information layer 1 protocol: | V.110, I.460 and X.30 | +| Synchronous/Asynchronous: | synchronous | +| Negotiation: | In-band negotiation not possible | +| User rate: | 32 kbit/s | + +If FNUR=64 kbit/s the ISDN BC-IE shall be coded for PIAFS as in note 16. + +**Table 7B: Comparable setting of parameters in PLMN and ISDN: Mobile Terminated** + +| Octet | ISDN BC parameter value | Octet | PLMN BC parameter value | +|-------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 1 | Bearer Capability IEI | 1 | Bearer Capability IEI | +| 2 | Length of BC contents | 2 | Length of BC contents | +| | no comparable field | 3
#7..6 | Radio channel requirement
full rate channel (these bits are spare in the network to UE direction) | +| 3
#7..6 | Coding standard
CCITT standardized coding | 3
#5 | Coding standard
GSM standardized coding | +| 3
#5..1 | Information transfer capability
speech
unrestricted digital
3,1 kHz audio
no comparable value
no comparable value
7 kHz audio
video
(note 23) | 3
#3..1 | Information transfer capability
speech
unrestricted digital
3,1 kHz audio ex PLMN (note2)
facsimile group 3 (note 3)
other ITC (see octet 5a)
not supported
not supported | +| | | 5a
#7..6 | Other ITC
restricted digital | +| 4
#7..6 | Transfer mode
circuit mode
packet mode | 3
#4 | Transfer mode
circuit mode
not supported | +| 4
#5..1 | Information transfer rate
64 kbit/s | | no comparable field | +| | No comparable field | 4
#7 | Compression (note 18)
data compression possible
data compression not possible | +| | No comparable field (note 4) | (4) 4
#6..5 | Structure (note 9)
SDU integrity
unstructured | +| 4a
#4..3 | No comparable field (note 4) | 4
#3 | Configuration
point-to-point (note 5) | +| | No comparable field | 4
#2 | NIRR (note 17)
No meaning
Data $\leq$ 4.8 kbit/s, FR nt,
6 kbit/s radio interface requested | +| 4a
#2..1 | No comparable field (note 4) | 4
#1 | Establishment
demand (note 5) | +| 4b
#7..6 | | | | +| 4b
#5..1 | | | | +| 5
#5..1 | User information layer 1 protocol
no comparable value
CCITT V.110, I.460 / X.30
G.711 A-law
CCITT X.31 flag stuffing
no comparable value

No comparable value

H.221 & H.242(note 28)
H.223 & H.245 | 5
#5..4 | Rate adaption
no rate adaption (note 11)
V.110, I.460/X.30 rate adaption
no comparable value
not supported
other rate adaption (see octet 5a) | +| | | 5a
#5..4 | Other rate adaptation
V.120 (note 24)
PIAFS
H.223 & H.245
H.223 & H.245 | +| | no comparable field | 5
#3..1 | Signalling access protocol
I.440/I.450
X.21 (note 26)
X.28, ded.PAD, indiv.NUI (note 26)
X.28, ded.PAD, univ.NUI (note 26)
X.28, non-ded.PAD (note 26)
X.32 (note 26) | +| | any of the above values | 6
#5..2 | User information layer 1 protocol
default layer 1 protocol | +| 5a
#7 | Synchronous / asynchronous
synchronous
asynchronous | 6
#1 | Synchronous/asynchronous
synchronous
asynchronous | +| 5a
#6 | Negotiation
not possible
inband neg, possible (note 16) | 6a
#6 | Negotiation
not possible
no comparable value | + +| Octet | ISDN BC parameter value | Octet | PLMN BC parameter value | +|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 5a
#5..1 | User rate
0,3 kbit/s
1,2 kbit/s
2,4 kbit/s
4,8 kbit/s
9,6 kbit/s
12 kbit/s
rate is indicated by Ebit as specified in rec. I.460
0,6 kbit/s
3,6 kbit/s
7,2 kbit/s
8 kbit/s
14,4 kbit/s
16 kbit/s
19.2 kbit/s
28.8 kbit/s
32 kbit/s
38.4 kbit/s
48 kbit/s
56 kbit/s
57.6 kbit/s
0,1345 kbit/s
0,1 kbit/s
75 bit/s / 1,2 kbit/s
1,2 kbit/s / 75 bit/s
0,110 kbit/s
0,2 kbit/s | 6a
#4..1 | User rate (note 18 and 29)
0,3 kbit/s
1,2 kbit/s
2,4 kbit/s
4,8 kbit/s
9,6 kbit/s
12 kbit/s (note 13)
(note 16)

not supported
not supported
not supported
not supported
(note 20)
not supported
(note 20)
(note 20)
(note 20)
(note 20)
(note 20)
not supported
not supported
not supported
not supported
not supported
not supported
not supported | +| 5b
#7..6 | Intermediate rate
not used (note 19)
8 kbit/s
16 kbit/s
32 kbit/s | 6b
#7..6 | Intermediate rate (note 6) (note 18)
8 or 16 kbit/s
8 kbit/s
16 kbit/s | +| 5b
#5 | NIC on Tx (note 14)
does not require
requires | 6b
#5 | NIC on Tx
does not require
requires (note 13) | +| 5b
#4 | NIC on Rx (note 14)
cannot accept
can accept | 6b
#4 | NIC on Rx
cannot accept
can accept (note 13) | +| 5b
#3 | Flow control on Tx (note 15)
Not Required
Required | | no comparable field | +| 5b
#2 | Flow control on Rx (note 15)
Cannot Accept
Accept | | no comparable field | +| 5c
#7..6 | Number of stop bits
1 bit
2 bits
not used
1.5 bits | 6a
#7 | Number of stop bits
1 bit
2 bits
no comparable value
not supported | +| 5c
#5..4 | Number of data bits
7 bits
8 bits
not used
5 bits | 6a
#5 | Number of data bits
7 bits
8 bits
no comparable value
not supported | +| 5c
#3..1 | Parity information
odd
even
none
forced to 0
forced to 1 | 6b
#3..1 | Parity information
odd
even
none
forced to 0
forced to 1 | +| | no comparable field | 6c
#7..6 | Connection element (note 1)
transparent
non-transparent (RLP)
both, transp. preferred
both, non-transp preferred | + +| Octet | ISDN BC parameter value | Octet | PLMN BC parameter value | +|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 5d
#7 | Duplex mode
half duplex
full duplex | 4
#4 | Duplex mode
half duplex (note 13)
full duplex (note 5) | +| 5d
#6..1 | Modem type
reserved
V.21
V.22
V.22bis
V.23
V.26ter
V.32
V.26
V.26bis
V.27
V.27bis
V.29

no comparable value | 6c
#5..1 | Modem type (note 12)
none (note 7)
V.21
V.22
V.22bis
not supported
V.26ter
V.32
not supported
not supported
not supported
not supported
not supported

autobauding type 1 (note 16) | +| 5a
#5..1 | User rate
no comparable value
9,6 kbit/s
14,4 kbit/s
19,2 kbit/s
28,8 kbit/s
32,0 kbit/s
38,4 kbit/s
48 kbit/s
56 kbit/s
no comparable value | 6d
#5..1 | Fixed network user rate (note 20)
FNUR not applicable
9,6 kbit/s
14,4 kbit/s
19,2 kbit/s
28,8 kbit/s
32,0 kbit/s (note 27)
38,4 kbit/s
48,0 kbit/s
56,0 kbit/s
64,0 kbit/s (note 22) | +| | Modem type
no comparable value (note 21)
V.34 | 6d
#7..6 | Other modem type
No other modem type
V.34 | +| | No comparable field | 6f
#7..5 | User initiated modification indicator (note 1) (note 25)
User initiated modification not required
User initiated modification upto 1
TCH/F may be requested
User initiated modification upto 2
TCH/F may be requested
User initiated modification upto 3
TCH/F may be requested
User initiated modification upto 4
TCH/F may be requested | +| 6
#5..1 | User information layer 2 protocol (note 10)
Q.921 (I.441)
X.25, link level
no comparable value | 7 | User information layer 2 protocol (note 8)
no comparable value
not supported
ISO 6429, codeset 0 | +| 7 | User information layer 3 protocol (note 10)
Q.931 (I.451)
X.25, packet level | |

not supported
not supported | + +## General notes: + +- 1) Other ISDN BC parameter values than those listed in the table, if indicated in the BC-IE, will be rejected by clearing the call, exception see mapping note 4. +- 2) Only the PLMN BC parameter values listed in the table may be generated (comparable values) during a mobile-terminated call by mapping the ISDN BC parameter values, exception see (10). +- 3) According to Q.931 (05/98) and 3GPP TS 24.008, respectively, the octets are counted from 1 to n onwards; the bit position in a particular octet is indicated by #x..y, with {x,y} = 1..8 (bit 1 is the least and bit 8 the most significant bit). + +- 4) If octets 5 to 5d of the ISDN BC are absent but present in the LLC, the LLC octets should apply for the mapping as indicated above. For V.120 interworking (see note 24) these LLC octets shall apply. +- 5) If within the ISDN BC the parameters information transfer capability indicates "3,1 kHz audio" and user layer 1 protocol indicates "G711 A-law" or "G.711 $\mu$ -law" (PCS-1900) but no modem type is available and the HLC does not indicate "facsimile group 3", octets 5 to 5d of the LLC, if available, apply for the above mapping procedure. +- 6) The number of octets which shall be encoded for the PLMN BC-IE must comply to encoding rules in 3GPP TS 24.008 and the combination of the different parameter values shall be in accordance to 3GPP TS 27.001. + +Notes regarding particular entries in table 7B: + +- 1) This PLMN parameter value is inserted according to user rate requirements and network capabilities / preferences. +- 2) This PLMN parameter value is inserted, if the information transfer capability in ISDN BC is "3,1kHz audio" and a comparable modem type is specified. +- 3) This PLMN parameter value is inserted, if the information transfer capability is "3,1 kHz audio" and the content of the HLC-IE, if any, indicates "facsimile group 2/3", (for details refer to subclause 10.2.2.3 case 3 for HLR action and subclause 10.2.2.4 case 5 for VMSC action). Note that via MAP the value "alternate speech/facsimile group 3 - starting with speech" shall be used, when TS 61 applies. +- 4) When interworking with an ISDN according to ETS 300 102-1, octets 4a and 4b may be present. The values are ignored and PLMN values are set according to notes 5 and 9. +- 5) This PLMN parameter value is inserted if the comparable ISDN parameter value is missing. +- 6) The value of the Intermediate Rate field of the PLMN Bearer Capability information element shall only depend on the value of the user rate in the same information element. If the connection element is "transparent", the value is 16 kbit/s, if the user rate is 9.6 or 12 kbit/s, and 8 kbit/s otherwise. For any other connection element setting the value is 16 kbit/s. +- 7) This PLMN BC parameter value is inserted, if the PLMN BC parameter "Information Transfer Capability" indicates "Unrestricted digital information", "facsimile group 3" or "alternate speech/facsimile group 3, starting with speech". +- 8) Where the network indicates "asynchronous" and connection elements "non-transparent", "both, transparent preferred" or "both, non-transparent preferred" , then the PLMN BC should be forwarded without parameter user information layer 2 protocol, see also (10). +- 9) The PLMN parameter value shall be set to "unstructured" where the network indicates connection element "transparent". Where the network indicates connection elements "non transparent" "both, transparent preferred" or "both, non transparent preferred" the value of the parameter structure shall be set to "SDU Integrity". +- 10) Mapping of parameter values of this octet to PLMN BC parameters and values are subject to specific application rules, i.e. unless otherwise explicitly stated in an appropriate TS mapping to PLMN BC parameters shall not take place. +- 11) This value shall be used when the value of the PLMN BC parameter "Information Transfer Capability" indicates the value "3,1 kHz audio ex PLMN", "facsimile group 3" or "alternate speech/facsimile group 3, starting with speech" which is reserved for MAP operations. +- 12) The modem encoding of both Q.931 (05/98) and ETS 300 102-1 version 1 shall be accepted and mapped according to 3GPP TS 24.008. +- 13) Value not used for currently defined bearer services and Teleservices. +- 14) NIC is only supported in A/Gb mode for "3,1 kHz Ex PLMN audio" interworking with synchronous data transmission. +- 15) Because the required flow control mechanism can not be indicated to the UE (refer to 3GPP TS 27.001), the network shall check if the flow control mechanism selected by the UE and indicated in the CALL CONFIRMED message suits to the requirements requested by the ISDN terminal adaptor. If there is a mismatch the call shall be released in the IWF. + +Because an asymmetric flow control mechanism (with respect to transmitting and receiving side) is not supported in the PLMN, the different values of the ISDN BC-IE parameters "flow control on Tx" and "flow control on Rx" shall be interpreted in the following way: + +- "Flow control on Rx" set to "accepted" matches with "outband flow control", irrespective of the value of the parameter "flow control on Tx". + - "Flow control on Rx" set to "not accepted" and "flow control on Tx" set to "not required" matches with "inband flow control" and "no flow control". + - where "Flow control on Rx" is set to "not accepted" and "flow control on Tx" to "required" the call shall be released by the IWF. +- 16) If 3,1 kHz audio interworking "inband negotiation possible" is indicated and the parameter user rate is set to "rate is indicated by E bits specified in Recommendation I.460 or may be negotiated inband" the user rate in the PLMN BC-IE shall be set according to a network preferred value. If ISDN-BC parameter modem type is present, its value shall be ignored. The PLMN BC parameter modem type shall be set according to the user rate for connection element "transparent" and to "autobauding type 1" for connection element "non transparent", "both, transparent preferred" or "both, non transparent preferred". If data compression is used, high speed modems, like V.32bis, V.34 and/or V.90 may be used in the IWF. Autobauding may also be used to support user rates less than 9.6 kbit/s towards the PSTN. + +For unrestricted digital interworking the call shall be rejected if these values are indicated. + +If the PLMN-BC parameter modem type indicates "autobauding type 1" or "none", then the PLMN-BC parameter other modem type shall be set to "no other modem type". + +- 17) For the use of NIRR see 3GPP TS 27.001. The VMSC shall set this parameter dependent upon its capabilities and preferences. +- 18) If compression is supported by the MSC, the value "data compression possible" may be set. Depending on the capabilities of the MSC, the user rate value and the intermediate rate value is set to an appropriate value. +- 19) Only applicable if the parameter ISDN-BC ITC indicates "3,1 kHz audio" and for "UDI" calls if User Rate > "19,2 kbit/s". +- 20) The user rate of the PLMN BC is set to the value for the fall-back bearer service. If the user equipment does not support the fixed network user rate (i.e. the call confirmation message does not contain the fixed network user rate parameter), the network may release the call for a transparent connection element. +- 21) The modem type parameter of the PLMN -BC is taken into account, only. +- 22) If no LLC is received and the ISDN-BC received consists of octets 1 to 4 only, coded: + +| | | +|----------------------------------|----------| +| Coding standard: | CCITT | +| Information Transfer capability: | UDI | +| Transfer mode: | circuit | +| Information transfer rate: | 64kbit/s | + +the following PLMN -BC parameters, shall be set to: + +| | | +|--------------------------|--------------------------------------------------------| +| fixed network user rate: | 64 kbit/s | +| connection element: | transparent
bothNT or bothT (If IWF supports PIAFS) | + +The other parameters of the PLMN -BC shall be set to values indicating a fall-back service. + +If an LLC indicating UIL1P=X.31 (either explicitly or implicitly by octet 5 missing) is received and the ISDN-BC received consists of 1 to 4 only, coded: + +| | | +|----------------------------------|----------| +| Coding standard: | ITU-T | +| Information Transfer capability: | UDI | +| Transfer mode: | circuit | +| Information transfer rate: | 64kbit/s | + +the following PLMN BC parameters, shall be set to: + +| | | +|--------------------------|-----------------| +| fixed network user rate: | 64 kbit/s | +| connection element: | non-transparent | +| Synchronous/Asynchronous | asynchronous | + +all other parameters shall be set according to 3GPP TS 27.001 to indicate FTM. + +If an LLC indicating UIL1P=X.31 (either explicitly or implicitly by octet 5 missing) is received and the ISDN-BC received consists of 1 to 4 only, coded: + +| | | +|----------------------------------|----------| +| Coding standard: | ITU-T | +| Information Transfer capability: | RDI | +| Transfer mode: | circuit | +| Information transfer rate: | 64kbit/s | + +the following PLMN BC parameters, shall be set to: + +| | | +|--------------------------|-----------------| +| fixed network user rate: | 56 kbit/s | +| connection element: | non-transparent | +| Synchronous/Asynchronous | asynchronous | + +all other parameters shall be set according to 3GPP TS 27.001 to indicate FTM. + +23) When the MSC is directly connected to a restricted 64 kbit/s network, the ISDN BC-IE is coded with an ITC = RDI. + +An ISDN BC-IE, as specified in ETR 018 and shown below, shall be taken to indicate that interworking with an indirectly connected restricted 64 kbit/s network is required: + +| | | +|------------------------------------|----------------------------------| +| Coding standard: | CCITT | +| Information Transfer capability: | UDI | +| Transfer mode: | circuit | +| Information transfer rate: | 64 kbit/s | +| User information layer 1 protocol: | V.110/X.30 | +| Synchronous/Asynchronous: | synchronous | +| Negotiation: | In-band negotiation not possible | +| User rate: | 56 kbit/s | + +In this case the PLMN BC parameter Information Transfer Capability is set to „Other ITC" and Other ITC parameter is set to „restricted digital". If ISDN LLC exists, all the corresponding fields in the PLMN BC shall be derived from the ISDN LLC. Otherwise, the corresponding fields in the PLMN BC shall be derived from the ISDN BC. In the above both case, Connection element is set as follows. + +| | | +|---------------------|-----------------------------------------------------------------| +| Connection element: | transparent | +| | bothNT or bothT (If IWF supports FTM) and LLC does not indicate | +| | User information layer 1 protocol = "X.31 flag stuffing") | +| | non-transparent (if IWF supports FTM and LLC indicates | +| | User information layer 1 protocol = "X.31 flag stuffing") | + +24) V.120 interworking is required if the ISDN LLC parameter User Information Layer 1 Protocol is set to „V.120". In this case the PLMN BC parameter Rate Adaptation is set to „Other rate adaptation" and Other Rate Adaptation parameter is set to „V.120". All the corresponding fields in the PLMN BC shall be derived from the ISDN LLC. + +25) This parameter is only included for non-transparent multislot connections. + +26) This value was used by services defined for former PLMN releases and does not need to be supported. + +27) Following BC parameters in SETUP message shall be set to: + +| | | +|-------------------------|-------------------------------------------------------------| +| Fixed network user rate | 32 kbit/s | +| Connection element | transparent (for multimedia) | +| | bothNT or bothT (If IWF supports PIAFS, UTRAN Iu mode only) | + +- 28) UIL1P is set to "H.221 & H.242" or "H.223 & H.245" by H.324/I. If UIL1P is set to "H.221 and H.242", this should be mapped to "H.223 & H.245". +- 29) In Iu mode, if the User Rate of the ISDN BC is less than 9,6 kbit/s and the Connection Element is mapped to "NT", then FNUR is fixed to 9,6 kbit/s. + +### 10.2.2.7 Creation of Backup Bearer Capability Information Element + +If the VMSC is not able to send a PLMN BC to the MS/UE for mobile terminated calls, it may include all available information in the Backup BC information element (Backup BC IE) of the call set-up message. + +In the following table 7C the comparison is drawn between parameters in the ISDN call set up request message and that of the PLMN call set up request message. In some cases no comparable values are available and these will be marked as such. In some cases it is not necessary to support a particular option, and in this case those parameters will be annotated appropriately. + +The PLMN parameters and values shall as in 3GPP TS 24.008 in combination as in 3GPP TS 27.001. The ISDN parameters and values are as in Q.931 (05/98). + +**Table 7C: Setting of parameters in Backup BC IE** + +| Octet | ISDN BC / LLC parameter value | Octet | BACKUP BC parameter value | +|-------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 1 | Bearer Capability IEI | 1 | Bearer Capability IEI | +| 2 | Length of BC contents | 2 | Length of BC contents | +| | no comparable field | 3
#7..6 | Radio channel requirement
full rate channel (these bits are spare) | +| 3
#7..6 | Coding standard
CCITT standardized coding | 3
#5 | Coding standard
GSM standardized coding | +| 3
#5..1 | Information transfer capability
speech
unrestricted digital
3,1 kHz audio
no comparable value
no comparable value
7 kHz audio
video
(note 23) | 3
#3..1 | Information transfer capability
speech
unrestricted digital
3,1 kHz audio ex PLMN (note2)
facsimile group 3 (note 3)
other ITC (see octet 5a)
not supported
not supported | +| | | 5a
#7..6 | Other ITC
restricted digital | +| 4
#7..6 | Transfer mode
circuit mode
packet mode | 3
#4 | Transfer mode
circuit mode
not supported | +| | no comparable field | 4
#7 | Compression (note 18)
data compression not possible | +| 4a
#7..5 | no comparable field (note 4) | (4) 4
#6..5 | Structure (note 9)
SDU integrity
unstructured | +| 4a
#4..3 | no comparable field (note 4) | 4
#3 | Configuration
point-to-point (note 5) | +| | no comparable field | 4
#2 | NIRR (note 17)
No meaning | +| 4a
#2..1 | no comparable field (note 4) | 4
#1 | Establishment
demand (note 5) | +| 5
#5..1 | User information layer 1 protocol
no comparable value
CCITT V.110, I.460 / X.30
G.711 A-law
CCITT X.31 flag stuffing
no comparable value

H.221 & H.242 (note 28)
H.223 & H.245 | 5
#5..4 | Rate adaption
no rate adaption (note 11)
V.110, I.460/X.30 rate adaption
no comparable value
not supported
other rate adaption (see octet 5a) | +| | | 5a
#5..4 | Other rate adaptation
H.223 & H.245
H.223 & H.245 | +| | no comparable field | 5
#3..1 | Signalling access protocol
I.440/I.450 | +| | any of the above values | 6
#5..2 | User information layer 1 protocol
default layer 1 protocol | +| 5a
#7 | Synchronous / asynchronous (note 30)
synchronous
asynchronous | 6
#1 | Synchronous/asynchronous
synchronous
asynchronous | +| 5a
#6 | Negotiation
not possible
inband neg, possible (note 16) | 6a
#6 | Negotiation
not possible (note 5)
no comparable value | + +| Octet | ISDN BC / LLC parameter value | Octet | BACKUP BC parameter value | +|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 5a
#5..1 | User rate
0,3 kbit/s
1,2 kbit/s
2,4 kbit/s
4,8 kbit/s
9,6 kbit/s
12 kbit/s
rate is indicated by Ebit as specified in rec.
1.460
0,6 kbit/s
3,6 kbit/s
7,2 kbit/s
8 kbit/s
14,4 kbit/s
16 kbit/s
19.2 kbit/s
28.8 kbit/s
32 kbit/s
38.4 kbit/s
48 kbit/s
56 kbit/s
57.6 kbit/s
0,1345 kbit/s
0,1 kbit/s
75 bit/s / 1,2 kbit/s
1,2 kbit/s / 75 bit/s
0,110 kbit/s
0,2 kbit/s
no comparable value | 6a
#4..1 | User rate (note 29)
0,3 kbit/s
1,2 kbit/s
2,4 kbit/s
4,8 kbit/s
9,6 kbit/s
12 kbit/s (note 13)
(note 16)

not supported
not supported
not supported
not supported
(note 20)
not supported
(note 20)
(note 20)
(note 20)
(note 20)
(note 20)
not supported
not supported
not supported
not supported
not supported
not supported
not supported
unknown | +| 5b
#7..6 | Intermediate rate
any value | 6b
#7..6 | Intermediate rate (note 6)
8 kbit/s
16 kbit/s | +| 5b
#5 | NIC on Tx (note 14)
does not require
requires | 6b
#5 | NIC on Tx
does not require (note 5)
requires (note 13) | +| 5b
#4 | NIC on Rx (note 14)
cannot accept
can accept | 6b
#4 | NIC on Rx
cannot accept (note 5)
can accept (note 13) | +| 5c
#7..6 | Number of stop bits
1 bit
2 bits
not used
1.5 bits | 6a
#7 | Number of stop bits
1 bit (note 5)
2 bits
no comparable value
not supported | +| 5c
#5..4 | Number of data bits
7 bits
8 bits
not used
5 bits | 6a
#5 | Number of data bits
7 bits
8 bits (note 5)
no comparable value
not supported | +| 5c
#3..1 | Parity information
odd
even
none
forced to 0
forced to 1 | 6b
#3..1 | Parity information
odd
even
none (note 5)
forced to 0
forced to 1 | +| | no comparable field | 6c
#7..6 | Connection element (note 1)
transparent
non-transparent (RLP)
both, transp. preferred
both, non-transp preferred | +| 5d
#7 | Duplex mode
half duplex
full duplex | 4
#4 | Duplex mode
half duplex (note 13)
full duplex (note 5) | + +| Octet | ISDN BC / LLC parameter value | Octet | BACKUP BC parameter value | +|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 5d
#6..1 | Modem type
reserved
V.21
V.22
V.22bis
V.23
V.26ter
V.32
V.26
V.26bis
V.27
V.27bis
V.29

no comparable value | 6c
#5..1 | Modem type (note 12)
none (note 7)
V.21
V.22
V.22bis
not supported
V.26ter
V.32
not supported
not supported
not supported
not supported
not supported

autobauding type 1 (note 16) | +| 5a
#5..1 | User rate
no comparable value
9,6 kbit/s
14,4 kbit/s
19,2 kbit/s
28,8 kbit/s
32,0 kbit/s
38,4 kbit/s
48 kbit/s
56 kbit/s
no comparable value | 6d
#5..1 | Fixed network user rate (note 20)
FNUR not applicable / unknown
9,6 kbit/s
14,4 kbit/s
19,2 kbit/s
28,8 kbit/s
32,0 kbit/s (note 27)
38,4 kbit/s
48,0 kbit/s
56,0 kbit/s
64,0 kbit/s (note 22) | +| | Modem type
no comparable value (note 21)
V.34

no comparable field | 6d
#7..6 | Other modem type
No other modem type
V.34 | +| | no comparable field | 6e
#7..6 | Acceptable channel codings
spare | +| | no comparable field | 6e
#5..1 | Maximum number of traffic channels
spare | +| | No comparable field | 6f
#7..5 | User initiated modification indicator (note 1) (note 25)
User initiated modification not required
User initiated modification upto 1
TCH/F may be requested
User initiated modification upto 2
TCH/F may be requested
User initiated modification upto 3
TCH/F may be requested
User initiated modification upto 4
TCH/F may be requested | +| | no comparable field | 6f
#4..1 | Wanted air interface user rate
spare | +| | no comparable field | 6g
#7..5 | Acceptable channel codings extended
spare | +| | no comparable field | 6g
#4..3 | Asymmetry indications
spare | +| 6
#5..1 | User information layer 2 protocol (note 10)
Q.921 (I.441)
X.25, link level
no comparable value
no comparable value | 7 | User information layer 2 protocol (note 8)
no comparable value
not supported
ISO 6429, codeset 0
unknown | + +General notes: + +- 1) Only the PLMN BC parameter values listed in the table may be generated (comparable values) during a mobile-terminated call by mapping the ISDN BC parameter values, exception see (10). + +- 2) According to Q.931 (05/98) and 3GPP TS 24.008, respectively, the octets are counted from 1 to n onwards; the bit position in a particular octet is indicated by #x.y, with {x,y} = 1..8 (bit 1 is the least and bit 8 the most significant bit). +- 3) If octets of the ISDN BC are absent but present in the LLC, the LLC octets should apply for the mapping. +- 4) The number of octets which shall be encoded for the Backup BC-IE must comply to encoding rules in 3GPP TS 24.008 and the combination of the different parameter values shall be in accordance to 3GPP TS 27.001 with the modification that some parameters may be absent, if a whole octet is absent, and some parameters may get values defined for the Backup BC only. However, parameter values that are valid for both the PLMN BC and the Backup BC shall not be in contradiction to 3GPP TS 27.001. + +Notes regarding particular entries in table 7C: + +- 1) This PLMN parameter value is inserted according to user rate requirements and network capabilities / preferences. +- 2) This PLMN parameter value is inserted, if the information transfer capability in ISDN BC is "3,1kHz audio" and a comparable modem type is specified. +- 3) This PLMN parameter value is inserted, if the information transfer capability is "3,1 kHz audio" and the content of the HLC-IE, if any, indicates "facsimile group 2/3", (for details refer to subclause 10.2.2.3 case 3 for HLR action and subclause 10.2.2.4 case 5 for VMSC action). +- 4) When interworking with an ISDN according to ETS 300 102-1, octets 4a and 4b may be present. The values are ignored and PLMN values are set according to notes 5 and 9. +- 5) This PLMN parameter value is inserted if the comparable ISDN parameter value is missing. +- 6) The value of the Intermediate Rate field of the PLMN Bearer Capability information element shall only depend on the value of the user rate in the same information element. If the connection element is "transparent", the value is 16 kbit/s, if the user rate is 9.6 or 12 kbit/s, and 8 kbit/s otherwise. For any other connection element setting the value is 16 kbit/s. If the user rate value is "unknown" any value can be used, it has to be ignored by the UE +- 7) This PLMN BC parameter value is inserted, if the PLMN BC parameter "Information Transfer Capability" indicates "Unrestricted digital information "or "facsimile group 3". +- 8) Where the network indicates "asynchronous" and connection elements "non-transparent", "both, transparent preferred" or "both, non-transparent preferred" , then the PLMN BC should be forwarded without parameter user information layer 2 protocol, see also (10). +- 9) The PLMN parameter value shall be set to "unstructured" where the network indicates connection element "transparent". Where the network indicates connection elements "non transparent" "both, transparent preferred" or "both, non transparent preferred" the value of the parameter structure shall be set to "SDU Integrity". +- 10) Mapping of parameter values of this octet to PLMN BC parameters and values are subject to specific application rules, i.e. unless otherwise explicitly stated in an appropriate TS mapping to PLMN BC parameters shall not take place. +- 11) This value shall be used when the value of the PLMN BC parameter "Information Transfer Capability" indicates the value "3,1 kHz audio ex PLMN" or "facsimile group 3". +- 12) The modem encoding of both Q.931 (05/98) and ETS 300 102-1 version 1 shall be accepted and mapped according to 3GPP TS 24.008. +- 13) Value not used for currently defined bearer services and Teleservices. +- 14) NIC is only supported in A/Gb mode for "3,1 kHz Ex PLMN audio" interworking with synchronous data transmission. +- 15) void. +- 16) If 3,1 kHz audio interworking "inband negotiation possible" is indicated and the parameter user rate is set to "rate is indicated by E bits specified in Recommendation I.460 or may be negotiated inband" the user rate in the PLMN BC-IE shall be set according to a network preferred value. If ISDN-BC parameter modem type is present, + +its value shall be ignored. The PLMN-BC parameter modem type shall be set according to the user rate for connection element "transparent" and to "autobauding type 1" for connection element "non transparent", "both, transparent preferred" or "both, non transparent preferred". If data compression is used, high speed modems, like V.32bis, V.34 and/or V.90 may be used in the IWF. Autobauding may also be used to support user rates less than 9.6 kbit/s towards the PSTN. + +For unrestricted digital interworking the call shall be rejected if these values are indicated. + +If the PLMN-BC parameter modem type indicates "autobauding type 1" or "none", then the PLMN-BC parameter other modem type shall be set to "no other modem type". + +17) An indication of NIRR is not possible in the Backup BC because it has to be negotiated by parameter values in the PLMN BC. + +18) An indication of compression is not possible in the Backup BC because it has to be negotiated by parameter values in the PLMN BC. + +19) void. + +20) The user rate of the PLMN BC is set to the value for the fall-back bearer service. If the user equipment does not support the fixed network user rate (i.e. the call confirmation message does not contain the fixed network user rate parameter), the network may release the call for a transparent connection element. + +21) The modem type parameter of the PLMN -BC is taken into account, only. + +22) If no LLC is received and the ISDN-BC received consists of octets 1 to 4 only, coded: + +| | | +|----------------------------------|----------| +| Coding standard: | CCITT | +| Information Transfer capability: | UDI | +| Transfer mode: | circuit | +| Information transfer rate: | 64kbit/s | + +the following PLMN -BC parameters, shall be set to: + +| | | +|--------------------------|---------------------------------------| +| fixed network user rate: | 64 kbit/s | +| connection element: | transparent | +| | bothNT or bothT (If IWF supports FTM) | + +The other parameters of the PLMN -BC shall be set to values indicating a fall-back service. + +23) When the MSC is directly connected to a restricted 64 kbit/s network, the ISDN BC-IE is coded with an ITC = RDI. + +An ISDN BC-IE, as specified in ETR 018 and shown below, shall be taken to indicate that interworking with an indirectly connected restricted 64 kbit/s network is required: + +| | | +|------------------------------------|----------------------------------| +| Coding standard: | CCITT | +| Information Transfer capability: | UDI | +| Transfer mode: | circuit | +| Information transfer rate: | 64 kbit/s | +| User information layer 1 protocol: | V.110/X.30 | +| Synchronous/Asynchronous: | synchronous | +| Negotiation: | In-band negotiation not possible | +| User rate: | 56 kbit/s | + +In this case the PLMN BC parameter Information Transfer Capability is set to „Other ITC" and Other ITC parameter is set to „restricted digital". If ISDN LLC exists, all the corresponding fields in the PLMN BC shall be derived from the ISDN LLC. Otherwise, the corresponding fields in the PLMN BC shall be derived from the ISDN BC. In the above both case, Connection element is set as follows. + +| | | +|---------------------|---------------------------------------| +| Connection element: | transparent | +| | bothNT or bothT (If IWF supports FTM) | + +24) Void. + +25) This parameter is only included for non-transparent multislot connections. + +26) This value was used by services defined for former PLMN releases and does not need to be supported. + +27) Following BC parameters in SETUP message shall be set to: + +| | | +|-------------------------|------------------------------| +| Fixed network user rate | 32 kbit/s | +| Connection element | transparent (for multimedia) | + +28) UIL1P is set to "H.221 & H.242" or "H.223 & H.245" by H.324/I. If UIL1P is set to "H.221 and H.242", this should be mapped to "H.223 & H.245". + +29) In Iu mode, if the User Rate of the ISDN BC is less than 9,6 kbit/s and the Connection Element is mapped to "NT", then FNUR is fixed to 9,6 kbit/s. + +30) If this parameter value is missing, the Backup BC shall not contain parameter octets 6 and higher. + +### 10.2.3 Transparent service support + +The protocol stacks for transparent services are specified in 3GPP TS 43.010 and in Clause 11a.3. + +In Iu mode, the transparent services are based in the Iu User Plane protocol specified in 3GPP TS 25.415. + +In A/Gb mode identifies the rate adaptation scheme shall be utilized on the RAN to MSC link as identified in 3GPP TS 48.020. The transcoding function will generate the 64 kbit/s rate adapted format utilizing the 8 and 16 kbit/s intermediate data rates. The MSC - MSC/IWF will utilize the same rate adaptation scheme as that indicated in 3GPP TS 48.020, i.e. adapted to 64 kbit/s. + +#### 10.2.3.1 Structure of the MSC/IWF for Iu mode + +The transmission towards the RNC is based on AAL2. The Iu UP is used in the transparent mode. + +![Diagram showing the structure of the MSC/IWF for Iu mode. On the left, a vertical stack of three boxes labeled 'Iu UP', 'AAL2', and 'ATM' is shown. Lines from each of these boxes point to a central 'MODEM' box. From the 'MODEM' box, a line points to a 'CODEC' box, which outputs '3.1kHz audio'. From the 'ATM' box, another line points to an 'ISDN TA function' box, which outputs '64 kbit/s unrestricted or 56 kbit/s restricted'. A third line from the 'ATM' box points directly to an output labeled '64 kbit/s unrestricted or 56 kbit/s restricted'.](29a9cd1cb2a960eb91dbf79aab5d8668_img.jpg) + +Diagram showing the structure of the MSC/IWF for Iu mode. On the left, a vertical stack of three boxes labeled 'Iu UP', 'AAL2', and 'ATM' is shown. Lines from each of these boxes point to a central 'MODEM' box. From the 'MODEM' box, a line points to a 'CODEC' box, which outputs '3.1kHz audio'. From the 'ATM' box, another line points to an 'ISDN TA function' box, which outputs '64 kbit/s unrestricted or 56 kbit/s restricted'. A third line from the 'ATM' box points directly to an output labeled '64 kbit/s unrestricted or 56 kbit/s restricted'. + +**Figure 10: Structure of the MSC/IWF (transparent)** + +#### 10.2.3.2 Structure of the MSC/IWF for A/Gb mode + +When interworking to the unrestricted digital bearer service rate adaptation according to ITU-T Recommendation V.110 will be necessary within the MSC/IWF. For multislot, TCH/F14.4 or EDGE operations MSC/IWF shall adapt the data stream as defined in 3GPP TS 44.021 and 3GPP TS 48.020. + +NOTE: From the perspective of MSC/IWF, a TCH/F28.8 EDGE configuration is identical to a multislot 2×TCH/F14.4 configuration. + +When interworking to the 3,1 kHz audio service, then the same process as for the PSTN case is necessary (section 9.2.3.2). + +![Figure 11: Structure of the MSC/IWF (transparent). The diagram shows three RA units (RA0, RA1, RA2) on the left. RA0 is connected to a MODEM block via a 'data' line. RA1 is connected to an ISDN TA function block via a 'status' line. RA2 is connected to a line labeled '64 kbit/s unrestricted or 56 kbit/s restricted'. The MODEM block is connected to a CODEC block, which outputs '3.1 kHz audio'. The ISDN TA function block outputs '64 kbit/s unrestricted or 56 kbit/s restricted'.](0f6e3cdce0f01d6ccceabcced508bb5b_img.jpg) + +Figure 11: Structure of the MSC/IWF (transparent). The diagram shows three RA units (RA0, RA1, RA2) on the left. RA0 is connected to a MODEM block via a 'data' line. RA1 is connected to an ISDN TA function block via a 'status' line. RA2 is connected to a line labeled '64 kbit/s unrestricted or 56 kbit/s restricted'. The MODEM block is connected to a CODEC block, which outputs '3.1 kHz audio'. The ISDN TA function block outputs '64 kbit/s unrestricted or 56 kbit/s restricted'. + +**Figure 11: Structure of the MSC/IWF (transparent)** + +### 10.2.3.3 Mapping of signalling UE/MSC/IWF to modem or ISDN (V.110) TA-function interface requirements + +For the 3,1 kHz audio interworking case see subclause 9.2.3.3. + +Status bits SA, SB and X can be used to convey channel control information associated with the data bits in the data transfer state. Table 8 shows the mapping scheme between the V.24 circuit numbers corresponding to the V-series DCE functions and the status bits for the transparent mode. It also shows how the unused status bits should be handled. It is derived from the General Mapping scheme described in annex B. A binary 0 corresponds to the ON condition, a binary 1 to the OFF condition. + +The transport of these status bits by the various channel codings is described in 3GPP TS 44.021 and 48.020 for A/Gb mode. For Iu mode refer to 3GPP Clause 11a. + +**NOTE** Although the interface to the ISDN TA function is described in terms of V.24 interchange circuit functions, this does not imply that such circuits need to be physically realised. + +**Table 8: Mapping scheme at the IWF for the transparent mode** + +| Mapping direction: UE to IWF | Mapping direction: IWF to UE | Signal at IWF ISDN TA interface or condition within the IWF | +|------------------------------|------------------------------|-------------------------------------------------------------| +| always ON (note 1) | | CT 105 | +| | to status bit X | CT 106 | +| | not mapped (note 5) | CT 107 | +| not mapped (note 6) | | CT 108 | +| | to status bit SB | CT 109 | +| always ON (note 2) | | CT 133 | +| from status bit SA (note 3) | | ignored by IWF | +| from status bit SB (note 1) | | ignored by IWF | +| from status bit X (note 4) | | ignored by IWF | +| | to status bit SA (note 3) | always ON | + +NOTE 1: The SB bit towards the IWF, according to the General Mapping (annex B), could be used to carry CT 105 from the mobile DTE to the ISDN TA function in the IWF. However, CT 105 should always be ON at the DTE interface in the data transfer state since only duplex operation is supported. Also, many DTEs use the connector pin assigned to CT 105 for CT 133. Therefore, CT 105 shall always be set to ON at the IWF ISDN TA function during the data transfer state. + +NOTE 2: CT 133 is not mapped since there is no flow control in transparent mode. + +NOTE 3: The SA bits in both directions are available only with certain channel codings. Therefore, for maximum compatibility, they should not be mapped. + +NOTE 4: The X bit towards the IWF is not mapped since there is no flow control in transparent mode. + +NOTE 5: CT 107 is not used by the IWF. + +NOTE 6: CT 108 is used in the call setup and answering processes. + +### 10.2.3.4 Establishment of end-to-end terminal synchronizations + +Prior to exposing the traffic channel of a PLMN connection to transmission of user data, the controlling entities of the connection shall assure of the availability of the traffic channel. This is done by a so called synchronizations process: + +- starting on the indication of "physical connection established" resulting from the PLMN-inherent outband signalling procedure This indication is given: + - for MOC: on sending the CONNECT message; + - for MTC: on sending the CONNECT ACKNOWLEDGE message; + - for mobile initiated in-call modification: on sending the MODIFY COMPLETE message (which is sent after reception of the ASSIGNMENT COMPLETE or RAB ASSIGNMENT RESPONSE message); and + - for network initiated in-call modification: on reception of the ASSIGNMENT COMPLETE or RAB ASSIGNMENT RESPONSE message; +- ending by indicating the successful execution of this process to the controlling entity, which then takes care of the further use of the inband information (data, status). + +Network interworking within an MSC/IWF is concerned with the terminating side (to the UE) and the transit side (to the fixed network) of a connection. Both sides shall be treated individually related to the synchronizations process. + +#### 10.2.3.4.1 Terminating side (towards the UE) + +##### 10.2.3.4.1.1 Traffic channel types TCH/F4.8 and TCH/F9.6 in A/Gb mode + +With respect to the terminating side the procedure is as follows: + +- sending of synchronizations pattern 1/OFF (all data bits "1"/all status bits "OFF") to the UE using the RA1/RA2 rate adaptation function. In multislot transparent operation, the synchronisation pattern sent is 1/OFF with the exception of the bit positions S1, first X, S3, and S4 which contain the substream number and multiframe alignment pattern (see 3GPP TS 44.021); +- searching for detection of the synchronizations pattern from the UE within valid V.110 frames, and in multislot operation, also searching for the multiframe alignment pattern "0000 1001 0110 0111 1100 0110 1110 101" (see 3GPP TS 44.021) in bit position S4 and substream numbers in bit positions S1, first X, and S3. This implies that the E1, E2 and E3 bit of the V.110 frame shall be checked for the appropriate user rate in order to distinguish the synchronization pattern from the RAN idle data frame. +- Timer T (= 500 ms) is started for each of the allocated traffic channel(s) of the call on receipt of the synchronizations pattern from the UE. +- When the frame alignment pattern and, in case of multislot operation, the multiframe alignment pattern have been recognized as a steady state, the MSC/IWF continues sending the synchronizations patterns to the UE until a timer T expires. + +##### 10.2.3.4.1.2 Traffic channel type TCH/F14.4 for A/Gb mode + +With respect to the terminating side the procedure is as follows: + +- Sending A-TRAU frames with the data rate set in the bits C1-C4 (TS 48.020) and data bits set to one, sending the multiframe structure with the alignment pattern (bit M1) and with the status bits OFF (bit M2) and, in a multislot case, sending substream numbers (bit M2). +- Searching for the detection of the multiframe alignment pattern ,,0000 1001 0110 0111 1100 0110 1110 101" (TS 44.021) in the bit M1 and, in a multislot case, searching for substream numbers in the bit M2. (Any 5 bit sequence in the multiframe alignment pattern is unique, i.e. the multiframe alignment can take place by recognition of five successive M1 bits). +- Timer T (= 500 ms) is started for each of the allocated traffic channel(s) of the call on receipt of the synchronizations pattern from the UE. +- When the frame alignment pattern and the multiframe alignment pattern have been recognized as a steady state, the MSC/IWF continues sending the synchronizations patterns to the UE until a timer T expires. + +#### 10.2.3.4.1.3 User Plane for Iu mode + +The procedures are the same as for the modem case, but, depending on implementation, the IWF may through connect before the fixed network leg has been synchronised. + +#### 10.2.3.4.2 Transit side (towards the fixed network). + +In case of interworking to the ISDN "3,1 kHz audio" bearer service the synchronization process is as for the PSTN interworking case (see subclause 9.2.3.4.2). + +In case of V.110 interworking to the ISDN unrestricted digital bearer service the following synchronization process shall be performed. + +The interchange circuits towards the V.110 ISDN TA function are held in the OFF condition until timer T expires, when they are switched to ON. + +From this time, after the expiration of the timer T of every allocated traffic channel, the information on CT106 and CT109 from the IWF V.110 ISDN TA function are directly mapped to the X and SB bits, respectively, towards the UE. For TCH/F14.4 the X and SB bits are mapped to the M2 multiframe bits according to 3GPP TS 44.021. Circuit 108 to the selected V.110 ISDN TA function associated with the connection will be switched from the "OFF" to "ON" condition, thus initiating the synchronization process on the fixed network according to ITU-T Recommendation V.110. The IWF is allowed to map CT 104 to the data bits sent towards the UE and to map data bits received from the UE to CT 103. + +#### 10.2.3.5 Network independent Clocking (NIC) + +Due to the incompatibility between the ISDN and the PLMN requirements for NIC interworking is not provided between these two formats. As such no NIC function is required in providing interworking to the ISDN. In this case, the IWF shall disregard the value of bits E4, E5, E6 and E7 in the data transmission phase. + +### 10.2.4 Non-transparent service support + +The protocol stacks for non-transparent services are specified in 3GPP TS 43.010 and in Clause 11a.2. Both of the systems use the Radio Link Protocol (RLP) specified in 3GPP TS 24.022. + +In Iu mode, the non-transparent services are based in the Iu User Plane protocol specified in 3GPP TS 25.415. + +In A/Gb mode the corresponding necessary support concerning the rate adaptation scheme shall be utilized on the RAN-MSC link as identified in 3GPP TS 48.020. + +For the non-transparent service support the MSC/IWF will select the modem and speed based on the Compatibility information contained in either the call set-up or call confirmed message, reference subclauses 9.2.1 and 9.2.2. Where the Modem Type indicated is autobauding type 1, the MSC/IWF may select any speed and modem type according to what it can negotiate with the remote modem. In this case User Rate and Fixed Network User Rate, if present, has no meaning. + +#### 10.2.4.1 Structure of the MSC/IWF for Iu mode + +The transmission towards the RNC is based on AAL2. The Iu UP is used in the support mode. The RLP/L2R extends to the UE. + +![Diagram showing the structure of the MSC/IWF for Iu mode. On the left, a stack of protocols is shown: L2R (containing RLP), Iu UP, AAL2, and ATM. An arrow labeled 'Data and status' points from the L2R/RDP boundary to two parallel blocks: MODEM and ISDN TA function. The MODEM block connects to a CODEC block, which outputs '3.1 kHz audio'. The ISDN TA function block outputs '64 kbit/s unrestricted or 56 kbit/s restricted'.](659f4d3d272deea8021d0bb2e22465fd_img.jpg) + +1) not applicable for PIAFS + +Diagram showing the structure of the MSC/IWF for Iu mode. On the left, a stack of protocols is shown: L2R (containing RLP), Iu UP, AAL2, and ATM. An arrow labeled 'Data and status' points from the L2R/RDP boundary to two parallel blocks: MODEM and ISDN TA function. The MODEM block connects to a CODEC block, which outputs '3.1 kHz audio'. The ISDN TA function block outputs '64 kbit/s unrestricted or 56 kbit/s restricted'. + +**Figure 12: Structure of the MSC/IWF (non-transparent)** + +### 10.2.4.2 Structure of the MSC/IWF for A/Gb mode + +The rate adaptation process will be the same as for the transparent case, except that a TCH/F43.2 channel coding is also supported. From MSC/IWF's perspective a TCH/F43.2 EDGE configuration is identical to a multislot 3×TCH/F14.4 configuration. + +3GPP TS 43.010 identifies the protocol layer structure for the non-transparent case, the MSC/IWF provides the inverse of the action in the UE terminal adaptation function. For a multislot configuration refer to 3GPP TS 43.010. + +The V.110, V.120 and PIAFS ISDN TA (terminal adapter) functions provide the same functionality and operational behaviour as fixed ISDN terminal adapters that conform to the corresponding ITU-T Recommendations (V.110 or V.120). + +![Figure 13: Structure of the MSC/IWF (non-transparent). The diagram shows a central block labeled 'L2R' with 'RLP' inside. Below it is 'RA1', which is connected to 'RA2'. To the right of the L2R block is a 'MODEM' block, which is connected to a 'CODEC' block, which outputs '3.1 kHz audio'. Below the MODEM block is an 'ISDN TA function' block, which outputs '64 kbit/s unrestricted or restricted'. A line labeled 'Data and status' connects the L2R block to both the MODEM and the ISDN TA function blocks.](1399c76ef88f22b70d05ed3f781d3c48_img.jpg) + +``` + +graph TD + subgraph L2R [L2R] + RLP[RLP] + end + L2R --- RA1[RA1] + RA1 --- RA2[RA2] + L2R --- MODEM[MODEM] + L2R --- ISDN_TA[ISDN TA function] + MODEM --- CODEC[CODEC] + CODEC --- Audio[3.1 kHz audio] + ISDN_TA --- ISDN_Out[64 kbit/s unrestricted or restricted] + L2R -.-> DS[Data and status] + DS -.-> MODEM + DS -.-> ISDN_TA + +``` + +Figure 13: Structure of the MSC/IWF (non-transparent). The diagram shows a central block labeled 'L2R' with 'RLP' inside. Below it is 'RA1', which is connected to 'RA2'. To the right of the L2R block is a 'MODEM' block, which is connected to a 'CODEC' block, which outputs '3.1 kHz audio'. Below the MODEM block is an 'ISDN TA function' block, which outputs '64 kbit/s unrestricted or restricted'. A line labeled 'Data and status' connects the L2R block to both the MODEM and the ISDN TA function blocks. + +Figure 13: Structure of the MSC/IWF (non-transparent) + +### 10.2.4.3 Re-constitution of user data + +3GPP TS 24.022 refers to the frame of user data in the radio link protocol. The layer 2 relay functions in the UE and the MSC/IWF (identified in 3GPP TS 43.010 and 3GPP TS 23.202 [90]) contain the mechanism for packing and unpacking the user data into the L2R protocol data units. + +### 10.2.4.4 Layer 2 relay functionality + +Specific functionality is required on the L2R dependant upon the service which is being requested to be supported. The selection of the appropriate L2R function will be determined by the MSC/IWF on the basis of the bearer capability information signalled in the call set-up request, or call confirmation message. The prime information element being transparent or non transparent service indication. In addition the particular L2R function - type of protocol to be terminated and mode of flow control to be applied (see appropriate subclauses in 3GPP TS 27 series) - will be selected on the basis of the user's layer 2 indication. + +The specific interaction between the L2R function and the RLP function and the L2R frame structure will be the same as that detailed in the Annex to the appropriate 3GPP TS 27 series. + +### 10.2.4.5 In band signalling mapping flow control + +This entails the L2R function providing the means of controlling and responding to flow control function of the modem (or in the rate adapted frame) plus any synchronizations requirements related to flow control. For asynchronous services a specific rule applies for flow control (see 3GPP TS 27.001). + +In case of interworking to the ISDN "3,1kHz audio" bearer service the flow control process is as for the PSTN interworking case (see subclause 9.2.4.5). In case of interworking to the ISDN unrestricted digital bearer service the following procedures apply: + +The flow control function chosen will be dependent upon the availability of the "user information layer 2" information element of the PLMN BC and if available its value. + +For V.110 interworking, outband flow control will be by means of the "X" bit in the V.110 frame to the ISDN. + +For V.120 interworking, outband flow control shall be as follows. In Multiple frame acknowledged mode the functions of the data link control sublayer (send RNR or withhold update of the sequence state variable V(R)) shall be used. In Unacknowledged mode the RR bit in the Control State octet shall be used. + +For PIAFS interworking, outband flow control shall be as follows. The functions of the data link control sublayer (withhold update of the frame number) shall be used. + +If flow control is provided irrespective of the type used, the L2R function shall: + +- a) provide immediate indication of flow control to the fixed network on receipt of flow control request from the UE; and/or +- b) provide immediate indication of flow control to the UE on receipt of flow control request from the fixed network i.e. in the next available L2R status octet to be transmitted. + +Where in band (X-on/X-off) flow control is in use, then the X-on/X-off characters will not be passed across the radio interface. + +If no flow control is provided the involved end systems are responsible for performing in-band flow control on their own by taking into account the buffer capacity of the MSC/IWF as stated below. + +#### 10.2.4.5.1 Conditions requiring flow control - if flow control is provided - towards the fixed network + +The L2R function will initiate flow control in the following circumstances: + +- 1) the transmit buffer to the radio side reaches a preset threshold (BACK PRESSURE); +- 2) the L2R function receives a "flow control active" indication. + +On removal of buffer congestion or receipt of L2R "flow control inactive" the flow control will be removed. + +No flow initiation/removal will take place at the L2R function and loss of data may occur, if no flow control is provided. + +#### 10.2.4.5.2 Conditions requiring flow control towards the UE + +The L2R function will transmit to the UE a "flow control active indication", if flow control is provided, in the following circumstances: + +- 1) if the receive buffer from the radio side reaches a preset threshold (BACK PRESSURE); +- 2) if a flow control indication is received from the fixed network customer. On receipt of this flow control indication, transmission of data from the receive buffers towards the fixed network terminal is halted. + +On removal of the buffer congestion or fixed network flow control indication, the L2R function will send a "flow control inactive" indication towards the UE. In addition, for the fixed network indication, transmission of data from the receive buffers will be restarted. + +If no flow control is provided at the L2R function, no flow control initiation/removal will take place by the MSC/IWF. Data might be lost without any indication by the MSC/IWF to the end systems involved. + +#### 10.2.4.6 Data buffers + +##### 10.2.4.6.1 Transmit buffers (towards UE) + +Incoming data from the fixed network customer shall be buffered such that if the MSC/IWF is unable to transfer data over the radio path the data is not lost. + +The buffer shall be capable of holding the data. Its size is up to the implementers. When the buffer is half full flow control towards the fixed network shall be initiated if flow control is provided as per subclause 10.2.4.5.1. + +##### 10.2.4.6.2 Receive buffers (from UE) + +Incoming data from the UE is buffered such that if the fixed network terminal is unable to accept the data then it is not lost. + +The buffer shall be capable of holding the data. Its size is up to the implementers. When the buffer becomes half full, the L2R function will send a "flow control active" indication towards the UE if flow control is provided at the L2R function, as per subclause 10.2.4.5.2. + +#### 10.2.4.7 BREAK Indication + +The BREAK indication is managed as detailed in subclause 9.2.4.7. + +When V.120 rate adaptation is being used in protocol sensitive asynchronous mode on the ISDN, the L2R break condition shall map on to the BR bit of the V.120 header octet. + +#### 10.2.4.8 Signalling mapping of modem or ISDN (V.110, V.120 or PIAFS) TA-function status information + +Status information is carried between the modem or ISDN (V.110, V.120 or PIAFS) TA-function in the IWF and the terminal adaption function in the UE by the L2R function. The L2RCOP entity transfers interface status information between L2Rs via the status octets SA, SB and X in L2RCOP-PDUs (3GPP TS 27.002). Table 9 shows the mapping scheme between the V.24 circuit numbers corresponding to the V-series DCE functions and the status bits for the non-transparent mode. It also shows how the unused status bits should be handled. It is derived from the General Mapping scheme described in annex B. A binary 0 corresponds to the ON condition, a binary 1 to the OFF condition. + +NOTE. Although the interface to the ISDN TA function is described in terms of V.24 interchange circuit functions, this does not imply that such circuits need to be physically realised. + +**Table 9: Mapping scheme at the IWF for the non-transparent mode** + +| Mapping direction: UE to IWF | Mapping direction: IWF to UE | Signal at IWF ISDN TA interface or condition within the IWF | +|------------------------------|------------------------------|-------------------------------------------------------------| +| always ON (note 1) | | CT 105 | +| | to status bit X (notes 4, 7) | CT 106 (note 7) | +| | not mapped (note 5) | CT 107 | +| not mapped (note 6) | | CT 108 | +| | to status bit SB | CT 109 | +| from status bit X (note 8) | | CT 133 (notes 3, 8) | +| from status bit SA (note 2) | | ignored by IWF | +| from status bit SB (note 1) | | ignored by IWF | +| | to status bit SA (note 2) | always ON | + +NOTE 1: The SB bit towards the IWF, according to the General Mapping (annex B), could be used to carry CT 105 from the mobile DTE to the ISDN TA function in the IWF. However, CT 105 should always be ON at the mobile DTE interface in the data transfer state since only duplex operation is supported. Also, many DTEs use the connector pin assigned to CT 105 for CT 133. Therefore, CT 105 shall always be set to ON at the ISDN TA function during the data transfer state. + +NOTE 2: The SA bits (both directions) are not mapped since CTs 107 and 108 are handled locally (notes 5, 6). + +NOTE 3: The condition of CT 133 (or other flow control mechanism) may also be affected by the state of the L2R transmit buffer (towards the UE) in the IWF and the state of RLP (RR/RNR). + +NOTE 4: The condition of status bit X towards the UE may also be affected by the state of the L2R receive buffer in the IWF (from the UE). + +NOTE 5: CT 107 is not used by the IWF. + +NOTE 6: CT 108 is used in the call setup and answering processes. + +NOTE 7: For inband flow control, CT 106 is not mapped and the status bit X towards the UE is controlled by the reception of XON and XOFF characters from the ISDN TA function. + +NOTE 8: For inband flow control, changes in the condition of the status bit X from the UE result in the sending of XON or XOFF to the ISDN TA function. CT 133 is always set to ON. + +#### 10.2.4.9 Support of out-band flow control + +Out-band flow control in the case of V.110 rate adaption requires V.110 TA to TA "end-to-end flow control" as defined therein. If this functionality is requested by UE but cannot be supported by the MSC/IWF for any reason (refer also to note 15 of table 7B) the call pending shall be released. + +For V.120 interworking, outband flow control shall be as follows. In Multiple frame acknowledged mode the functions of the data link control sublayer (send RNR or withhold update of the sequence state variable V(R)) shall be used. In Unacknowledged mode the RR bit in the Control State octet shall be used. + +#### 10.2.4.10 Synchronizations + +In case of interworking to the ISDN "3,1kHz audio" bearer service the synchronization process is as for the PSTN interworking case (see subclause 9.2.3.4). In case of interworking to the ISDN unrestricted digital bearer service the following synchronization process shall be performed: + +##### 10.2.4.10.1 V.110 and V.120 Frame synchronizations + +The ISDN frame synchronizations will need to be mapped to the frame synchronizations utilized on the MSC/IWF to MSC link. + +##### 10.2.4.10.2 RLP Frame start indication + +The frame start indication is defined in 3GPP TS 48.020. Link establishment and frame error recovery are defined in 3GPP TS 24.022. + +##### 10.2.4.10.3 L2R Frame synchronizations + +The synchronizations of user data and its interaction between the L2R function and RLP function are defined in 3GPP TS 27 series. + +##### 10.2.4.10.4 Establishment of end-to-end terminal synchronizations + +Prior to exposing the traffic channel of a PLMN connection to transmission of user data, the controlling entities of the connection shall assure of the availability of the traffic channel. This is done by a so called synchronization process: + +- starting on the indication of "physical connection established" resulting from the PLMN-inherent outband signalling procedure This indication is : +- for MOC: on sending the CONNECT message; +- for MTC: on sending the CONNECT ACKNOWLEDGE message; +- for mobile initiated in-call modification: on sending the MODIFY COMPLETE message (which is sent after reception of the ASSIGNMENT COMPLETE or RAB ASSIGNMENT RESPONSE message); and +- for network initiated in-call modification: on reception of the ASSIGNMENT COMPLETE or RAB ASSIGNMENT RESPONSE message; +- ending by indicating the successful execution of this process to the controlling entity, which then takes care of the further use of the in-band information (data, status). + +Network interworking within an MSC/IWF is concerned with the terminating side (to the UE) and the transit side (to the fixed network) of a connection. Both sides shall be treated individually related to the synchronization process. + +###### 10.2.4.10.4.1 Terminating side (towards the UE) + +The procedures are the same as for the modem case. + +###### 10.2.4.10.4.2 Transit side (towards the fixed network) + +Depending upon implementation, the synchronization of the V.110 or V.120 rate adaptation protocol on the ISDN transit network may be performed either after RLP establishment or in parallel to the RLP establishment. In case of the parallel establishment, data received from the transit side during RLP establishment shall be stored within the L2R buffers until the RLP establishment at the terminating side has been finished. When the RLP has been established and on recognizing frame alignment the information from/to the RLP is mapped by the L2R entity applicable to this particular bearer capability. + +For V.110 rate adaptation on the ISDN, the synchronization process consists of sending the V.110 frame structure and looking for incoming frame synchronization according to the procedures in ITU-T Recommendation V.110. + +For V.120 rate adaptation the following applies. In Multiple frame acknowledged mode, data (I frames) may be sent following an exchange of SABME and UA in the traffic channel. In Unacknowledged mode, data (UI frames) may be sent immediately after an ISUP CONNECT or CONNECT COMPLETE message has been received on the ISDN signalling channel. Optionally, an XID exchange may take place in the traffic channel to verify link integrity. + +Note. V.120 allows UI frames to be sent in Multiple frame acknowledged mode at any time in addition to I frames. Whilst the IWF shall not follow this procedure when sending frames, such a sequence of I and UI frames may be received by the IWF. Although not specified in V.120, it is recommended that the IWF should deliver to the UE, the contents of the sequence of I and UI frames in the order in which they are received. + +For PIAFS rate adaptation the following applies. Data frame is sent following an exchange of initial negotiation and control frame in the traffic channel. + +#### 10.2.4.11 Data compression + +When data compression is invoked within a non-transparent bearer service, interworking to the ISDN is realized by mapping the PLMN user rate to at least the same user rate in the ISDN. When the ISDN user rate is the same flow control will ensure data integrity, but the overall performance will be slow. When the ISDN user rate is higher the overall performance may be faster. + +#### 10.2.4.12 Additional aspects of V.120 Interworking + +V.120 rate adaptation may be invoked with asynchronous services only. V.120 is applicable to both UDI and RDI connections. + +##### 10.2.4.12.1 V.120 Signalling parameters + +The signalling parameters relevant to V.120 will be carried in the ISDN LLC and PLMN BC and PLMN LLC information elements. The mapping of the parameter values takes place in the MSC/IWF. + +For mobile terminated calls both single-numbering and multi-numbering scenarios may apply, as defined in subclause 9.2.2. The HLR shall not store an ISDN LLC with the MSISDN. + +##### 10.2.4.12.2 V.120 Protocol parameters + +The following restrictions apply for the parameters relevant for V.120: + +- BS 20 NT will use the protocol sensitive asynchronous mode. As a consequence, the rate adaption header shall always be present. +- Only the default logical link will be established, i.e. the LLI negotiation value is "Default, LLI=256 only". +- V.120 recommends the use of the multiple frame acknowledged information transfer procedure for the protocol sensitive mode of operation. +- The IWF shall use the default value for the V.120 window size and the default value for the maximum transmit information field size. It shall be able to receive frames with the default maximum size. + +NOTE: V.120 does not specify the values for these and other HDLC-related parameters directly. They are specified in Q.922 (1992) section 5.9. The information field includes the V.120 terminal adaption data field, the rate adaption header and the header extension (Control State octet), if present. + +##### 10.2.4.12.3 Data compression on the ISDN + +Whilst V.110 rate adaptation does not support standardized data compression, V.42bis data compression may be used with V.120 protocol sensitive asynchronous mode. This is described in V.120 (10/96) annex C. + +##### 10.2.4.12.4 Use of the V.120 Control State (header extension) octet + +The bits in the V.120 Control State octet are not used for the control of V.24 interface circuits. In unacknowledged mode the RR bit in the Control State octet is used to carry flow control information between the peer terminal adaption protocol entities. In acknowledged mode the Control State octet is not required. + +## 10.2.4.13 Interworking with restricted 64 kbit/s networks + +### 10.2.4.13.1 Rate adaptation + +Both V.110 and V.120 rate adaption protocols may be used on a restricted 64 kbit/s network. + +For V.110 rate adaption, the procedure is described in ITU-T Recommendation I.464. The RA2 function shall set the 8th bit of each octet in the 64 kbit/s stream to binary 1. A consequence of this is that the highest permitted intermediate rate is 32 kbit/s. At the receiver, the 8th bit shall be ignored. + +Rec. V.120 states that the user data shall be rate adapted to 56 kbit/s by using only the first 7 bits of each octet in the 64 kbit/s stream. The 8th bit shall be set to binary 1. At the receiver, the 8th bit shall be ignored. + +### 10.2.4.13.2 MSC - ISDN signalling + +When interworking indirectly with restricted 64 kbit/s networks the ISDN BC information element shall be coded according to ETR 018 (as shown in the notes to tables 7A and 7B). The information corresponding to the PLMN BC-IE shall be communicated in the ISDN LLC-IE which shall be provided by the UE for mobile originated calls. + +In the case of direct interworking, an ITC = RDI in the PLMN BC-IE maps on to an ITC = RDI in the ISDN BC-IE for both MO and MT calls. + +## 10.2.4.14 Service level up and down grading + +Text in 9.2.4.12 applies here as well. + +## 10.2.4.15 Interworking in Frame Tunneling Mode + +Figure 14 below shows the protocol stack used for FTM. The interface between the two asynchronous-synchronous conversion functions in the IWF and the remote terminal adapter (TA) is a 64 kbit/s UDI or a 56 kbit/s RDI connection. X.31 flag stuffing is used to adapt the rate between the two conversion functions. Data transparency is provided through bit stuffing. + +![Figure 14: The FTM protocol stack diagram. The diagram shows three main components: a Terminal Adapter (TAF) on the left, a Mobile Switching Center/Interworking Function (MSC/IWF) in the center, and a remote terminal adapter (TA) on the right. The TAF contains a 'Higher layer (e.g., PPP)' connected to a 'D L2RCOP C' block, which is connected to an 'RLP' block, which is connected to an 'L1' block. The MSC/IWF contains an 'L2RCOP D C' block connected to an 'RLP' block, which is connected to a 'Conv' block. The 'Conv' block is split into 'A-HDLC' and 'S-HDLC' sections. The TA on the right contains a 'Higher layer (e.g., PPP)' connected to a 'Conv' block, which is split into 'S-HDLC' and 'A-HDLC' sections. A red double-headed arrow connects the 'Higher layer (e.g., PPP)' blocks in the TAF and the TA. The 'L1' block in the TAF is connected to the 'A-HDLC' section of the 'Conv' block in the MSC/IWF. The 'S-HDLC' section of the 'Conv' block in the MSC/IWF is connected to the 'S-HDLC' section of the 'Conv' block in the TA.](24a27d17656bcf0ee131539f2bbb34cd_img.jpg) + +Figure 14: The FTM protocol stack diagram. The diagram shows three main components: a Terminal Adapter (TAF) on the left, a Mobile Switching Center/Interworking Function (MSC/IWF) in the center, and a remote terminal adapter (TA) on the right. The TAF contains a 'Higher layer (e.g., PPP)' connected to a 'D L2RCOP C' block, which is connected to an 'RLP' block, which is connected to an 'L1' block. The MSC/IWF contains an 'L2RCOP D C' block connected to an 'RLP' block, which is connected to a 'Conv' block. The 'Conv' block is split into 'A-HDLC' and 'S-HDLC' sections. The TA on the right contains a 'Higher layer (e.g., PPP)' connected to a 'Conv' block, which is split into 'S-HDLC' and 'A-HDLC' sections. A red double-headed arrow connects the 'Higher layer (e.g., PPP)' blocks in the TAF and the TA. The 'L1' block in the TAF is connected to the 'A-HDLC' section of the 'Conv' block in the MSC/IWF. The 'S-HDLC' section of the 'Conv' block in the MSC/IWF is connected to the 'S-HDLC' section of the 'Conv' block in the TA. + +Figure 14: The FTM protocol stack + +Data compression between the TAF and the IWF is optionally applied. The asynchronous to synchronous HDLC conversion follows from ISO/IEC 3309[48]. + +A particular aspect of the asynchronous HDLC protocol is the provision of control character transparency. This means that flags (0x7E) and the control escape character (0x7D) are escaped, by insertion of the control escape character in front of the character to be escaped, and that the 6th bit of the escaped character is complemented (i.e., the escaped character is XOR'ed with 0x20). ISO/IEC 3309[48] allows additional control characters to be escaped by prior agreement or negotiation between the peer entities. For instance, in PPP [49], a negotiation procedure is defined using an Asynchronous Control Character Map (ACCM). By examining the contents of the HDLC frames that pass through it, the IWF shall identify whether the higher layer protocol is PPP, in which case, it shall detect and interpret the ACCM negotiation result. If PPP is used, the conversion function in the IWF shall apply a default ACCM until another is negotiated. + +### 10.2.4.16 Additional aspects of PIAFS Interworking + +PIAFS has several U-Plane protocol suites, but "Data Transmission Protocol (fixed rate)"[50] is only applied for UTRAN Iu mode in consideration of simplicity. Details of frame structure and retransmission procedure etc. conform to reference [50]. + +In case of 32kbit/s mode, IWF performs rate adaptation based on I.460 for fixed network. + +In case of 64 kbit/s mode, restriction on throughput may be caused by (the maximum frame length of 572bits in RLP). + +## 10.2.5 DTE/DCE interface (Filtering) + +This is described in section 9.2.5. + +# 10.3 Interworking Alternate speech facsimile group 3 calls + +## 10.3.1 Alternate speech data bearer interworking + +### 10.3.1.1 General + +The procedure for the alternate speech/facsimile group 3 service is invoked at the UE-MSC link during the call set-up phase. This service is invoked by indication of repeated bearer capability information elements in the setup message and/or call confirmed message, respectively (preceded by a repeat indicator "circular"), one indicating speech and the other indicating "facsimile group 3" plus user rate etc., as for normal single calls. The bearer capability first indicated i.e. speech or facsimile determines the first selection required of the network by the subscriber. Depending on the type of service requested and direction of call establishment (MO/MT, see relevant clauses of the 3GPP TS 27 series) low layer and high layer capabilities may also be included. The MSC/IWF will perform both compatibility checking and subscription checking for mobile originated calls and optionally for mobile terminated calls (single numbering scheme) on both sets of capabilities as for normal data calls. If either the subscription check or the compatibility check fails then the call shall be rejected. The only exception to this is when TS61/TS62 negotiation takes place, see 3GPP TS 27.001. + +As regards the supplementary services the application rules are laid down in 3GPP TS 22.004. + +The speech phase of the call, when invoked, is handled by the transcoder and will utilize the normal telephony teleservice interworking requirements and mobile network capabilities. The Facsimile group 3 phase of the call, when invoked, shall utilize the appropriate data interworking capability (e.g. IWF) and shall use the transparent mobile network capability in A/Gb mode or the non-transparent mobile network capability in UTRAN Iu mode. + +The network shall provide, for service and operational reasons, a rapid and reliable changeover of capability upon request from the mobile user. This changeover may involve the disabling, by-passing or introduction of particular network functions (e.g. speech coder, modem etc.) and change of the channel configuration on the radio interface. This changeover is initiated on the receipt of the "MODIFY" message (see 3GPP TS 24.008) from the UE. The network itself will not initiate a changeover. + +### 10.3.1.2 Mobile originated ISDN terminated + +If one bearer capability information element indicates the ITC value "facsimile group 3", the call set up is as for the PSTN case. Interworking is provided to the ISDN bearer service 3,1 kHz audio for the whole connection, including the speech phase. The MODIFY message (see 3GPP TS 24.008) will be generated by the mobile subscriber. This message is not transmitted to the ISDN, i.e. no outband correlation between the user on the fixed network and the mobile user will be possible. In this instance it is necessary for change of network capabilities to be carried out in the mobile network. + +### 10.3.1.3 ISDN originated mobile terminated + +In principle this is handled as for a normal ISDN originated call. + +However when the calling user indicates an ISDN BC-IE with an ITC value "3,1 kHz audio" and an HLC "facsimile group 3", i.e. the call arrives at the PLMN with compatibility information allowing for deducing the Teleservice "Facsimile transmission", the call setup is as described in subclause 10.2.2.3 case 3 in the HLR, and subclause 10.2.2.4 case 5 in the VMSC. + +In the information transfer phase the call is dealt with as indicated in the previous paragraph. + +## 10.4 3G-H.324/M calls over UDI/RDI + +3G-H.324/M calls provide UDI/RDI (e.g. 32 kbit/s transparent data, 56 kbit/s transparent data or 64 kbit/s transparent data). H.223 and H.245 flow is not terminated in the MSC. + +3G-H.324 calls over 64 kbit/s transparent data and 56kbit/s transparent data can be connected to H.324/I calls over UDI/RDI. H.223 protocol is transparent to IWF. + +In case of 3G-H.324M calls over 32 kbit/s, IWF which performs rate adaptation between 64kbit/s and 32kbit/s is used. Rate adaptation is based on ITU-T Recommendation I.460. + +The Service Change and Fallback functionality for UDI/RDI multimedia calls is described in 3GPP TS 23.172 [83]. + +The support of IWF which transcodes the multiplexes and the content of control, audio, video and data in MSC is FFS. + +### 10.4.1 Mobile originated multimedia call + +#### 10.4.1.1 Call setup + +The setup message sent by the UE contains either a multimedia BC-IE indicating a multimedia only call request (*i.e.* no fallback / service change allowed) or both a speech BC-IE and a multimedia BC-IE to indicate the support of fallback and service change (see 3GPP TS 27.001 [43] and 3GPP TS 24.008 [40]). + +The MSC shall not accept a requested service to which the user is not provisioned for. Provided that the user is provisioned for the BS30 bearer service – and/or speech the following applies : + +- in case of a multimedia only BC-IE, the MSC shall either accept the setup as such or with modifications sent to the UE in the call proceeding message (see 3GPP TS 27.001 [43]) ; +- in case of both a speech BC-IE and a multimedia BC-IE in either order, the MSC shall either accept the possibility of fallback or service change by responding with the two BC-IEs in the same order as received, in the reverse order (relayed from terminating user), or turn the call to a speech call by sending only a speech BC-IE in the call proceeding message, or turn the call to a multimedia only call by sending only the multimedia BC-IE in the call proceeding message (see 3GPP TS 27.001 [43]). +- in case of a multimedia BC-IE with FNUR = 32 kbit/s and a speech BC-IE, the MSC shall reply with only a multimedia BC-IE in the call proceeding message (see 3GPP TS 23.172 [83]). + +#### 10.4.1.2 Fallback after setup + +If the MSC has accepted the possibility of a fallback and service change, and the transit network or the terminating side does not allow one of the bearers, the MSC shall initiate an In-Call Modification procedure (see 3GPP TS 24.008 [40]) in order to fallback to the allowed mode. As a result of the procedure, the radio and network resources are modified and the relevant channel is set up between the calling UE and the fixed network. If the fallback fails, *e.g.* due to an unsuccessful In-Call Modification procedure, the MSC shall clear the call. + +#### 10.4.1.3 User initiated service change after setup + +If the MSC has accepted the possibility of a service change and the user initiates an In-Call Modification procedure (see 3GPP TS 24.008 [40]) in order to change the service either from speech to multimedia or vice-versa, the MSC shall invoke the service change as an In-Call Modification procedure. As a result of the procedure, the radio and core network resources are modified in order to comply with the requested service change. + +## 10.4.2 Mobile terminated multimedia call + +### 10.4.2.1 Call setup + +If the user is provisioned to use both the transparent bearer service (for multimedia) and the speech teleservice, and if the network supports both services and the service change functionality, the MSC shall send both a multimedia BC-IE and a speech BC-IE in the setup message to the mobile station. In case the MSC receives a multimedia call, the multimedia BC-IE is prioritised (first BC). In case the MSC receives a speech call, the speech BC is prioritised. + +If the user is provisioned to use only the transparent bearer service and if the network supports the multimedia service, the MSC shall only send a multimedia BC-IE, which results in a fallback to multimedia if the call was a speech call. + +If the user is provisioned to use only the speech teleservice, the MSC shall only send a speech BC-IE, which results in a fallback to speech if the call was a multimedia call. + +In case both a speech BC-IE and a multimedia BC-IE are included in the setup message, the mobile station shall either accept the service change capability by responding with two BC-IEs in the same or reversed order, or turn the call to a speech call by sending only a speech BC-IE in the call confirmed message, or to a multimedia only call (*i.e.* no service change allowed) by sending only a multimedia BC-IE in the call confirmed message. + +In case of a multimedia only BC-IE in the setup, the UE may accept the setup as such or with modifications sent to the MSC in the call confirmed message. + +#### 10.4.2.2 User initiated service change after setup + +If the MSC supports the possibility of a service change and the user initiates an In-Call Modification procedure (see 3GPP TS 24.008 [40]) in order to change the service either from speech to multimedia or vice-versa, the MSC shall invoke the service change as an In-Call Modification procedure. As a result of the procedure, the radio and core network resources are modified in order to comply with the requested service change. + +--- + +## 11 Interworking between A/Gb mode MSC and Iu mode MSC + +### 11.0 Signalling issues + +#### 11.0.1 Loss of BC Information during Handover from A/Gb mode to UTRAN Iu mode + +In the case of inter-MSC handover from A/Gb mode to UTRAN Iu mode, the serving A/Gb mode MSC/VLR sends a MAP message Prepare Handover carrying the BSSMAP message Handover Request. This message includes the parameter Channel Type, indicating whether radio resources are to be allocated for speech or data (parameter 'Speech or data indicator') and, among other data, the type of data service (transparent/non transparent) and the user rates (both included in the parameter 'Data rate and transparency indicator'). + +As no other bearer capability related parameters are received, it is not possible to distinguish between any other services than 'speech', 'data transparent' and 'data non-transparent'. + +The mapping into QoS radio access parameters would be done as described in 3GPP TS 27.001[86], annex B, subclause B.1.13., limited to the services 'speech', 'data, non-transparent' and 'data, transparent'. + +#### 11.0.2 Handover from UTRAN Iu mode to A/Gb mode + +In case a UTRAN Iu mode call is set up in the CN, the BC IE parameters are mapped into QoS RAB parameters at call setup. + +If the CN has to perform a handover towards A/Gb mode, the non-anchor MSC needs to perform an assignment based on GSM traffic channel parameters. + +In case of handover from UTRAN Iu mode to A/Gb mode, the anchor MSC maps the BC IE parameters into A/Gb mode traffic channel parameters. This requires that the BC IE is coded according to A/Gb mode protocol requirements, *i.e.* all those parameters ignored in UTRAN Iu mode should nevertheless be correctly specified by the UE in order to perform a handover to A/Gb mode. + +#### 11.0.3 Loss of BC Information during Handover from A/Gb mode to GERAN Iu mode + +Subclause 11.0.1 applies also to handover from A/Gb mode to GERAN Iu mode. + +Additionally, the serving A/Gb mode MSC/VLR will include the parameter GERAN Classmark in the MAP message Prepare Handover, if this parameter is available. The GERAN Classmark, which indicates the capabilities of the BSS in the target cell (e.g. allowed channel codings and maximum number of traffic channels), shall be taken into account by the target MSC when it performs the mapping into QoS radio access parameters. + +### 11.0.4 Handover from GERAN Iu mode to A/Gb mode + +Subclause 11.0.2 applies also to handover from GERAN Iu mode to A/Gb mode. + +NOTE: The protocol requirements for the coding of the BC IE according to GERAN Iu mode are the same as for A/Gb mode, i.e. all those parameters needed in order to perform a handover to A/Gb mode are available. + +### 11.0.5 Handover from UTRAN Iu mode to GERAN Iu mode + +The serving UTRAN Iu mode MSC/VLR will send a MAP message Prepare Handover carrying the RANAP message Relocation Request. When setting the QoS RAB parameters in the RANAP message Relocation Request, the serving UTRAN Iu mode MSC/VLR shall take into account: + +- the GERAN Classmark of the target cell, if this parameter is available; +- the allowed channel codings and the maximum number of traffic channels from the BC IE, if the serving MSC is the anchor MSC; and +- the allowed radio interface rates (included in the parameter Channel Type), if the serving MSC is not the anchor MSC. + +This requires that the BC IE is coded according to GERAN Iu mode protocol requirements, i.e. all those parameters ignored in UTRAN Iu mode should nevertheless be correctly specified by the UE in order to perform a handover to GERAN Iu mode. Furthermore, it requires that the anchor MSC maps the BC IE parameters into A/Gb mode traffic channel parameters and includes the parameter Channel Type in the MAP message Prepare Handover also for basic handover to UTRAN Iu mode. + +### 11.0.6 Handover from GERAN Iu mode to UTRAN Iu mode + +The serving GERAN Iu mode MSC/VLR will send a MAP message Prepare Handover carrying the RANAP message Relocation Request. When setting the QoS RAB parameters in the RANAP message Relocation Request, the serving GERAN Iu mode MSC/VLR shall take the mode of the target cell into account. (See 3GPP TS 27.001[86], annex B, subclause B.1.13. For non-transparent services, some of the RAB Subflow Combination bit rates are supported in GERAN Iu mode, but not in UTRAN Iu mode.) + +## 11.1 Handover to A/Gb mode MSC + +After a handover from an Iu mode MSC or an A/Gb mode MSC to an A/Gb mode MSC the user plane between the anchor MSC and the visited MSC shall comply to: + +- the standard A-interface protocols if both MSCs are connected via a TDM interface, i.e.: + - A-TRAU or modified V.110 frames as defined in 3GPP TS 44.021 [27] and 3GPP TS 48.020 [28]; + - up to four 16kbit/s substreams are multiplexed in one 64kbit/s channel (Split/Combine function and Multiplexing function as defined in 3GPP TS 44.021 [27] and 3GPP TS 48.020 [28]). +- the Nb UP protocol if the anchor MSC or MGW and the visited MSC or MGW are connected via an ATM transport interface or IP transport interface in a BICC based CS CN. The NbUP shall be configured in support mode, the data is transported in a 64 kbit/s bit stream, formatted in SDUs of 40 octets and transmitted every 5 ms, in accordance with Annex P of ITU-T Recommendation I.366.2 [81]. PDU type 0 is used, i.e., payload CRC is applied. This is needed for the framing to be handled the same for all transports but the Frame Quality Classification control shall be ignored (3GUP property Delivery Of Erroneous SDUs = yes) and therefore interim nodes shall only pass on the CRC. The data is encoded between MSC-B/MGW-B (non-Anchor) and MSC-A/MGW-A (Anchor) as for the TDM case. Furthermore, Clause 11a.1.3 is applicable. +- the CLEARMODE payload type, see IETF RFC 4040 [92], within RTP/IP if SIP-I over Nc is deployed in the CN. The data is transported in a 64 kbit/s bit stream. The data is encoded between MSC-B/MGW-B (non-Anchor) and MSC-A/MGW-A (Anchor) as for the TDM case. Furthermore, Clause 11a.1.3 is applicable. + +## 11.2 Handover from A/Gb mode MSC to UTRAN Iu mode MSC + +After a handover from an A/Gb mode MSC to an UTRAN Iu mode MSC the user plane between the anchor MSC and the visited MSC shall comply to: + +- the A-TRAU' protocol if both MSCs are connected via a TDM interface except for FNUR = 32 kbit/s (ITC = UDI), FNUR = 56 kbit/s (ITC=RDI) and FNUR = 64 kbit/s (ITC=UDI). For these exceptions a plain 64 kbit/s channel is used between the MSCs. +- the Nb UP protocol if the anchor MSC or MGW and the visited MSC or MGW are connected via an ATM transport interface or IP transport interface in a BICC based CS CN. The NbUP shall be configured in support mode, the data is transported in a 64 kbit/s bit stream, formatted in SDUs of 40 octets and transmitted every 5 ms, in accordance with Annex P of ITU-T Recommendation I.366.2 [81]. PDU type 0 is used, i.e., payload CRC is applied. This is needed for the framing to be handled the same for all transports but the Frame Quality Classification control shall be ignored (3GUP property Delivery Of Erroneous SDUs = yes) and therefore interim nodes shall only pass on the CRC. The data is encoded between MSC-B/MGW-B (non-Anchor) and MSC-A/MGW-A (Anchor) as for the TDM case (A-TRAU' protocol or plain 64kbits/s). Furthermore, Clause 11a.1.3 is applicable. +- the CLEARMODE payload type, see IETF RFC 4040 [92], within RTP/IP if SIP-I over Nc is deployed in the CN. The data is transported in a 64 kbit/s bit stream. The data is encoded between MSC-B/MGW-B (non-Anchor) and MSC-A/MGW-A (Anchor) as for the TDM case. Furthermore, Clause 11a.1.3 is applicable. + +## 11.3 Handover from A/Gb mode MSC to GERAN Iu mode MSC + +### 11.3.1 User plane for transparent services + +After a handover from a GERAN A/Gb mode MSC to a GERAN Iu mode MSC the user plane for transparent services between the anchor MSC and the visited MSC shall comply to: + +- the A-TRAU' protocol except for FNUR = 32 kbit/s (ITC = UDI), FNUR = 56 kbit/s (ITC=RDI) and FNUR = 64 kbit/s (ITC = UDI). For these exceptions a plain 64 kbit/s channel is used between the MSCs. The rate adaptation between 64 kbit/s and 32 kbit/s is based on ITU-T Recommendation I.460. +- the Nb UP protocol if the anchor MSC or MGW and the visited MSC or MGW are connected via an ATM transport interface or IP transport interface in a BICC based CS CN. The NbUP shall be configured in support mode, the data is transported in a 64 kbit/s bit stream, formatted in SDUs of 40 octets and transmitted every 5 ms, in accordance with Annex P of ITU-T Recommendation I.366.2 [81]. PDU type 0 is used, i.e., payload CRC is applied. This is needed for the framing to be handled the same for all transports but the Frame Quality Classification control shall be ignored (3GUP property Delivery Of Erroneous SDUs = yes) and therefore interim nodes shall only pass on the CRC. The data is encoded between MSC-B/MGW-B (non-Anchor) and MSC-A/MGW-A (Anchor) as for the TDM case (A-TRAU' protocol or plain 64kbits/s). Furthermore, Clause 11a.1.3 is applicable. +- the CLEARMODE payload type, see IETF RFC 4040 [92], within RTP/IP if SIP-I over Nc is deployed in the CN. The data is transported in a 64 kbit/s bit stream. The data is encoded between MSC-B/MGW-B (non-Anchor) and MSC-A/MGW-A (Anchor) as for the TDM case. Furthermore, Clause 11a.1.3 is applicable. + +### 11.3.2 User plane for non-transparent services + +After a handover from a GERAN A/Gb mode MSC to a GERAN Iu mode MSC the user plane for transparent services between the anchor MSC and the visited MSC shall comply to: + +- the A-TRAU'' protocol as defined below for the RAB subflows with 12 kbit/s, 24 kbit/s, 36 kbit/s and 48 kbit/s and the A-TRAU' protocol for the RAB subflows with 14,4 kbit/s, 28,8 kbit/s, 43,2 kbit/s and 57,6 kbit/s, if both MSCs are connected via a TDM interface. +- the Nb UP protocol if the anchor MSC or MGW and the visited MSC or MGW are connected via an ATM transport interface or IP transport interface in a BICC based CS CN. The NbUP shall be configured in support mode, the data is transported in a 64 kbit/s bit stream, formatted in SDUs of 40 octets and transmitted every 5 ms, in accordance with Annex P of ITU-T Recommendation I.366.2 [81]. PDU type 0 is used, i.e., payload CRC is applied. This is needed for the framing to be handled the same for all transports but the Frame Quality Classification control shall be ignored (3GUP property Delivery Of Erroneous SDUs = yes) and therefore + +interim nodes shall only pass on the CRC. The data is encoded between MSC-B/MGW-B (non-Anchor) and MSC-A/MGW-A (Anchor) as for the TDM case (A-TRAU'' or A-TRAU' protocol). Furthermore, Clause 11a.1.3 is applicable. + +- the CLEARMODE payload type, see IETF RFC 4040 [92], within RTP/IP if SIP-I over Nc is deployed in the CN. The data is transported in a 64 kbit/s bit stream. The data is encoded between MSC-B/MGW-B (non-Anchor) and MSC-A/MGW-A (Anchor) as for the TDM case. Furthermore, Clause 11a.1.3 is applicable + +## 11.4 Handover within Iu mode PLMNs + +After a handover from an Iu mode MSC to a UTRAN Iu mode MSC the user plane between the anchor MSC or MGW and the visited MSC or MGW shall comply to: + +- the A-TRAU' protocol if both MSCs are connected via a TDM interface except for the transparent case FNUR = 32 kbit/s (ITC = UDI or RDI), FNUR = 56 kbit/s (ITC=RDI) and FNUR = 64 kbit/s (ITC=UDI). For these exceptions a plain 64 kbit/s channel is used between the MSCs. The rate adaptation between 64 kbit/s and 32 kbit/s is based on ITU-T Recommendation I.460 [2]. +- the Nb UP protocol if the anchor MSC or MGW and the visited MSC or MGW are connected via an ATM transport interface or IP transport interface in a BICC based CS CN. The NbUP shall be configured in support mode, the data is transported in a 64 kbit/s bit stream, formatted in SDUs of 40 octets and transmitted every 5 ms, in accordance with Annex P of ITU-T Recommendation I.366.2 [81]. PDU type 0 is used, i.e., payload CRC is applied. This is needed for the framing to be handled the same for all transports but the Frame Quality Classification control shall be ignored (3GUP property Delivery Of Erroneous SDUs = yes) and therefore interim nodes shall only pass on the CRC. The data is encoded between MSC-B/MGW-B (non-Anchor) and MSC-A/MGW-A (Anchor) as for the TDM case (A-TRAU' protocol or plain 64kbits/s). +- the CLEARMODE payload type, see IETF RFC 4040 [92], within RTP/IP if SIP-I over Nc is deployed in the CN. The data is transported in a 64 kbit/s bit stream. The data is encoded between MSC-B/MGW-B (non-Anchor) and MSC-A/MGW-A (Anchor) as for the TDM case. Furthermore, Clause 11a.1.3 is applicable. + +After a handover from an Iu mode MSC to a GERAN Iu mode MSC the user plane between the anchor MSC or MGW and the visited MSC or MGW shall comply to + +- the A-TRAU' or A-TRAU'' protocol or a plain 64 kbit/s channel if both MSC are connected via a TDM interface. The A-TRAU' protocol shall be used for transparent services except for the transparent cases FNUR = 32 kbit/s (ITC = UDI), FNUR = 56 kbit/s (ITC=RDI) and FNUR = 64 kbit/s (ITC=UDI). For these exceptions a plain 64 kbit/s channel is used between the MSCs. The rate adaptation between 64kbit/s and 32kbit/s is based on ITU-T Recommendation I.460. For non-transparent services, the A-TRAU'' protocol shall be used for the RAB subflows with 12 kbit/s, 24 kbit/s, 36 kbit/s and 48 kbit/s and the A-TRAU' protocol shall be used for the RAB subflows with 14,4 kbit/s, 28,8 kbit/s, 43,2 kbit/s and 57,6 kbit/s. +- the Nb UP protocol if the anchor MSC or MGW and the visited MSC or MGW are connected via an ATM transport interface or IP transport interface in a BICC based CS CN. The NbUP shall be configured in support mode, the data is transported in a 64 kbit/s bit stream, formatted in SDUs of 40 octets and transmitted every 5 ms, in accordance with Annex P of ITU-T Recommendation I.366.2 [81]. PDU type 0 is used, i.e., payload CRC is applied. This is needed for the framing to be handled the same for all transports but the Frame Quality Classification control shall be ignored (3GUP property Delivery Of Erroneous SDUs = yes) and therefore interim nodes shall only pass on the CRC. The data is encoded between MSC-B/MGW-B (non-Anchor) and MSC-A/MGW-A (Anchor) as for the TDM case (A-TRAU'' protocol, A-TRAU' protocol or plain 64kbits/s). Furthermore, Clause 11a.1.3 is applicable. +- the CLEARMODE payload type, see IETF RFC 4040 [92], within RTP/IP if SIP-I over Nc is deployed in the CN. The data is transported in a 64 kbit/s bit stream. The data is encoded between MSC-B/MGW-B (non-Anchor) and MSC-A/MGW-A (Anchor) as for the TDM case. Furthermore, Clause 11a.1.3 is applicable + +## 11.5 Handover for 56kbit/s + +The FNUR = 56 kbit/s in transparent mode can be supported in A/Gb mode by two configurations: + +1. without IWF with the following channel codings + - 2\*TCH/F32.0 + +- 5\*TCH/F9.6 +- 2. with IWF with the following channel coding + - 4\*TCH/F14.4 + +The FNUR = 56 kbit/s in transparent mode is supported in Iu mode by a configuration without IWF only. Therefore handover for 56kbit/s in transparent mode between Iu mode MSC and A/Gb mode can be supported only for configurations without IWF. + +**Note:** Handover between configurations with and without IWF are also not supported within A/Gb mode. + +## 11.6 Void + +# 11a Transport Protocols + +## 11a.1 Core Network + +### 11a.1.0 Overview + +The Nb UP protocol is used to transport user data in BICC based Core Network, see 3GPP TS 29.415 [80]. + +The RTP protocol is used to transport user data in SIP-I based Core Network, see 3GPP TS 29.414 [93]. The CLEARMODE payload type shall be applied, see IETF RFC 4040 [92] for 64k data. + +Figures 16 and 16a below show the different cases to consider: + +1. Transport on the access side of the IWF +2. Transport beyond the IWF, i.e., between the IWF and the fixed network + +![Figure 16: Transport of data within the BICC based Core Network. The diagram shows three MGW (Media Gateway) units connected via Nb interfaces. The first MGW contains a Relay Function and two UP (User Plane) components: Iu UP and Nb UP. The second MGW contains an IWF (Interworking Function) and two Nb UP components. The third MGW contains a single Nb UP component and a TDM (Time Division Multiplex) component. All three MGWs are connected to a common Transport Layer. The first MGW is connected to the Transport Layer via its Iu UP and Nb UP components. The second MGW is connected to the Transport Layer via its Nb UP components. The third MGW is connected to the Transport Layer via its Nb UP component. The Nb interfaces are shown as vertical dashed lines between the MGWs.](05da2a3257316bbf6f448a830dc0380a_img.jpg) + +Figure 16: Transport of data within the BICC based Core Network. The diagram shows three MGW (Media Gateway) units connected via Nb interfaces. The first MGW contains a Relay Function and two UP (User Plane) components: Iu UP and Nb UP. The second MGW contains an IWF (Interworking Function) and two Nb UP components. The third MGW contains a single Nb UP component and a TDM (Time Division Multiplex) component. All three MGWs are connected to a common Transport Layer. The first MGW is connected to the Transport Layer via its Iu UP and Nb UP components. The second MGW is connected to the Transport Layer via its Nb UP components. The third MGW is connected to the Transport Layer via its Nb UP component. The Nb interfaces are shown as vertical dashed lines between the MGWs. + +**Figure 16: Transport of data within the BICC based Core Network** + +![Figure 16a: Transport of data within the SIP-I based Core Network. The diagram shows three MGW (Media Gateway) units connected via Nb interfaces. The first MGW contains a Framing Protocol Interworking function and two UP components: Iu UP and CLEARMODE/RTP. The second MGW contains an IWF (Interworking Function) and two CLEARMODE/RTP components. The third MGW contains a single CLEARMODE/RTP component and a TDM (Time Division Multiplex) component. All three MGWs are connected to a common Transport Layer. The first MGW is connected to the Transport Layer via its Iu UP and CLEARMODE/RTP components. The second MGW is connected to the Transport Layer via its CLEARMODE/RTP components. The third MGW is connected to the Transport Layer via its CLEARMODE/RTP component. The Nb interfaces are shown as vertical dashed lines between the MGWs.](190217f95ce423a68d4a144cbd9df011_img.jpg) + +Figure 16a: Transport of data within the SIP-I based Core Network. The diagram shows three MGW (Media Gateway) units connected via Nb interfaces. The first MGW contains a Framing Protocol Interworking function and two UP components: Iu UP and CLEARMODE/RTP. The second MGW contains an IWF (Interworking Function) and two CLEARMODE/RTP components. The third MGW contains a single CLEARMODE/RTP component and a TDM (Time Division Multiplex) component. All three MGWs are connected to a common Transport Layer. The first MGW is connected to the Transport Layer via its Iu UP and CLEARMODE/RTP components. The second MGW is connected to the Transport Layer via its CLEARMODE/RTP components. The third MGW is connected to the Transport Layer via its CLEARMODE/RTP component. The Nb interfaces are shown as vertical dashed lines between the MGWs. + +**Figure 16a: Transport of data within the SIP-I based Core Network** + +### 11a.1.1 Void + +### 11a.1.2 Transport beyond the IWF + +#### 11a.1.2.1 UDI and RDI + +The data is transported in a 64 kbit/s bit stream, formatted in SDUs of 40 octets and transmitted every 5 ms, in accordance with Annex P of ITU-T Recommendation I.366.2 [81]. For BICC based CS CN, PDU type 0 is used, i.e., payload CRC is applied. + +At the border between the CN and the fixed (ISDN) network, for BICC based CS CN conversion between Nb UP and TDM shall be applied. For SIP-I based CS CN conversion between "CLEARMODE" payload type and TDM shall be applied. In case of RDI interworking, the 56 kbit/s RDI bit stream is transmitted within the CN as 64 kbit/s bit stream where the last bit of each octet is ignored. For this reason the octet alignment shall be preserved in the SDUs transported in the CN. + +#### 11a.1.2.2 Modem + +The modem signals are PCM encoded and transported on a 64 kbit/s bit stream. The transmission is otherwise identical to the UDI/RDI case, see Section 11a.1.2.1 + +### 11a.1.3 Transport on the access side of the IWF + +#### 11a.1.3.0 Inter MSC-Relocation + +After inter-MSC relocation, Clause 11 is applicable. + +Furthermore, for the BICC based CS CN the Nb UP is used in support mode, for SIP-I CLEARMODE/RTP shall be used; all interim Server nodes are assumed not to be aware of the relocation case – i.e. receive BICC IAM with same information as for connections beyond the IWF (Clause 11a.1.2). + +Figure 17 indicates the relevant connections, where MSC-A/MGW-A are the Anchor nodes and MSC-B/MGW-B are the Non-Anchor nodes. The CSD MGW Termination Properties for the terminations in Figure 17 shall be used as described in Tables 16 and 17. + +![Figure 17: Bearer Independent connections for Inter-MSC SRNS Relocation. The diagram shows a network architecture for inter-MSC SRNS relocation. At the top, MSC-A and MSC-B are connected via a MAP interface. MSC-A is connected to MGW-A via a BICC interface (T0). MGW-A is connected to an 'Other party' via T0 and to an IWF via T1 (Iu/A). The IWF is connected to RNC-A/BSC-A. MGW-A is also connected to MGW-T via Nb (T2). MGW-T is connected to another MGW-T via Nb (T3). The second MGW-T is connected to MGW-B via Nb (T4). MGW-B is connected to RNC-B/BSC-B via T8 (Iu/A). Servers are connected between MSC-A and MSC-B via BICC/ISUP interfaces (T5, T6).](f59ced6eaab3181501fc23fdfb52297e_img.jpg) + +Figure 17: Bearer Independent connections for Inter-MSC SRNS Relocation. The diagram shows a network architecture for inter-MSC SRNS relocation. At the top, MSC-A and MSC-B are connected via a MAP interface. MSC-A is connected to MGW-A via a BICC interface (T0). MGW-A is connected to an 'Other party' via T0 and to an IWF via T1 (Iu/A). The IWF is connected to RNC-A/BSC-A. MGW-A is also connected to MGW-T via Nb (T2). MGW-T is connected to another MGW-T via Nb (T3). The second MGW-T is connected to MGW-B via Nb (T4). MGW-B is connected to RNC-B/BSC-B via T8 (Iu/A). Servers are connected between MSC-A and MSC-B via BICC/ISUP interfaces (T5, T6). + +**Figure 17: Bearer Independent connections for Inter-MSC SRNS Relocation** + +The Iu UP for BICC based CS CN shall be initialised on each Nb leg in a forward direction (regardless if Forward Bearer or Backward Bearer procedures are used), i.e. in the direction of the IAM. For further details see TS 23.205 [83]. + +When setting up the call leg towards MSC-B, the anchor node MSC-A shall request an UDI bearer in out-of-band signalling. For UDI/RDI multimedia calls with fallback and service change according to 3GPP TS 23.172 [17], the anchor node MSC-A shall negotiate the multimedia dummy codec as specified in 3GPP TS 23.153 [91]. + +Figure 18 shows the scenario where the IWF resides in a MGW directly interfacing an Iu or A interface, as encountered e.g. before an inter-MSC handover. The CSD MGW Termination Properties for the terminations in Figure 18 shall be used as described in Tables 16 and 17. + +![Figure 18: IWF in MGW interfacing Iu or A interface. The diagram shows a vertical stack of three boxes. The top box is labeled 'MSC-A'. A line connects it to the middle box, labeled 'MGW-A'. To the left of the MGW-A box, there is a label 'Other party' with an arrow pointing left from the MGW-A box. Above the arrow is the label 'T0'. Below the MGW-A box, there is a label 'IWF' with a small black square next to it. A line connects the MGW-A box to the bottom box, labeled 'RNC-A / BSC-A'. To the right of this line, there are labels 'T1' and 'Iu/A'.](4dd5f00d74e7db5bbb2d011609bcc43d_img.jpg) + +Figure 18: IWF in MGW interfacing Iu or A interface. The diagram shows a vertical stack of three boxes. The top box is labeled 'MSC-A'. A line connects it to the middle box, labeled 'MGW-A'. To the left of the MGW-A box, there is a label 'Other party' with an arrow pointing left from the MGW-A box. Above the arrow is the label 'T0'. Below the MGW-A box, there is a label 'IWF' with a small black square next to it. A line connects the MGW-A box to the bottom box, labeled 'RNC-A / BSC-A'. To the right of this line, there are labels 'T1' and 'Iu/A'. + +**Figure 18: IWF in MGW interfacing Iu or A interface** + +#### 11a.1.3.0a Several MGWs controlled by same MSC server + +In other cases than inter-MSC relocation where the IWF is not interfacing an Iu UP layer protocol entity, the following bullets are applicable (For example, an MSC-server may control two MGWs and route the call through both, as one MGW interfaces Iu and the other one hosts the user plane part of the IWF): + +- If the access network uses A/Gb mode, the same transport as described in Clause 11.1 shall be applied. +- If the access network uses Iu mode, the same transport as described in Clause 11.4 shall be applied. + +Furthermore, for BICC CS CN the Nb UP is used in support mode. + +Figure 19 indicates the relevant connections, where MGW-A is where the IWF resides. The CSD MGW Termination Properties for the terminations in Figure 19 shall be used as described in Tables 16 and 17. + +![Figure 19: Transport on the access side of the IWF if the same MSC server controls one MGW A hosting the IWF and another MGW B interfacing the radio access network. The diagram shows a top box labeled 'MSC'. Two lines connect it to two middle boxes: 'MGW-A' and 'MGW-B'. The line to MGW-A is labeled 'T0' and 'T2'. The line to MGW-B is labeled 'T7'. To the left of MGW-A, there is a label 'Other party' with an arrow pointing left from the MGW-A box. Above the arrow is the label 'T0'. Below the MGW-A box, there is a label 'IWF' with a small black square next to it. A horizontal line labeled 'Nb' connects MGW-A and MGW-B. Below MGW-B, a line connects it to a bottom box labeled 'RNC-B / BSC-B'. To the right of this line, there are labels 'T8' and 'Iu/A'.](7fe4241eea8865aa6d2686d711c13ba6_img.jpg) + +Figure 19: Transport on the access side of the IWF if the same MSC server controls one MGW A hosting the IWF and another MGW B interfacing the radio access network. The diagram shows a top box labeled 'MSC'. Two lines connect it to two middle boxes: 'MGW-A' and 'MGW-B'. The line to MGW-A is labeled 'T0' and 'T2'. The line to MGW-B is labeled 'T7'. To the left of MGW-A, there is a label 'Other party' with an arrow pointing left from the MGW-A box. Above the arrow is the label 'T0'. Below the MGW-A box, there is a label 'IWF' with a small black square next to it. A horizontal line labeled 'Nb' connects MGW-A and MGW-B. Below MGW-B, a line connects it to a bottom box labeled 'RNC-B / BSC-B'. To the right of this line, there are labels 'T8' and 'Iu/A'. + +**Figure 19: Transport on the access side of the IWF if the same MSC server controls one MGW A hosting the IWF and another MGW B interfacing the radio access network** + +The MSC server selects the direction of the IuUP initialisation if BICC based CS CN. + +### 11a.1.3.1 Non-Transparent CSD + +**Table 16: Non-Transparent CSD MGW Termination Properties For Inter-MSC SRNS Relocation** + +| Termination Packages/Parameters | MSC-A | | | | MSC-B | | | Intermediate Nodes | +|---------------------------------|-----------------------------------------------------|---------|----------------|--------------------------|--------------------------|--------------|----------------|--------------------------| +| | T0 | T1 (lu) | T1 (A) | T2 | T7 | T8 (lu) | T8 (A) | T3, T4, T5, T6 | +| TMR | TMR (NOTE 5) | - | - | UDI (NOTE 3) | UDI | UDI (NOTE 7) | UDI (NOTE 3) | UDI | +| threeegcsd:plmnb | - | PLMN BC | PLMN BC | PLMN BC | - | - | - | - | +| threegup:interface | CN (NOTE 2) | RAN | - | CN (NOTE 2) | CN (NOTE 2) | RAN | - | CN (NOTE 2) | +| threegup:initdir | (NOTE 2) (NOTE 4) | IN | - | OUT (NOTE 2) (NOTE 6) | IN (NOTE 2) (NOTE 6) | OUT | - | IN (NOTE 2) | +| threegup:mode | Support (NOTE 2) | support | - | Support (NOTE 2) | Support (NOTE 2) | support | - | Support (NOTE 2) | +| threeegcsde:bitrate | - | - | - | - | - | BITRATE | - | - | +| threeegcsd:gsmchancod | - | - | GSM CC | GSM CC (NOTE 1) | - | - | - | - | +| IP Interface Type | NboIP(NOTE 8) | - | AoIP (NOTE 9) | NboIP(NOTE 8) | NboIP(NOTE 8) | - | AoIP (NOTE 9) | NboIP(NOTE 8) | +| Payload Type | CLEARMODE [92], G711 [1,x], or T.38 [y,z] (NOTE 11) | - | AoIP (NOTE 10) | CLEARMODE [92] (NOTE 11) | CLEARMODE [92] (NOTE 11) | - | AoIP (NOTE 10) | CLEARMODE [92] (NOTE 11) | + +NOTE 1: GSM CC shall only be provided if T8 is an A interface. GSM CC shall not be provided if T8 is an lu interface. + +NOTE 2: Only applicable for a BICC network. + +NOTE 3: Optional + +NOTE 4: Value depends on call direction: IN if terminating call, OUT if originating call. + +NOTE 5: TMR is set according to the value received from ISDN/BICC signalling. In addition, a received USI may be supplied. If no TMR value from ISDN/BICC signalling is available, but the MSC determines with the help of PLMN\_BCs exchanged with the UE that the call is a data call, it shall supply a value derived from the PLMN\_BC. + +NOTE 6: If several MGWs are controlled by the same MSC server, the server may also select the other value. + +NOTE 7: For a data rate of 64 kbit/s, TMR "UDI" may be supplied. For other data rates, TMR "UDI" shall not be sent. + +NOTE 8: The parameter may be supplied with value "NboIP" for a termination towards a SIP-I based CS CN. For termination towards a BICC based CS CN, the parameter shall not be supplied. + +NOTE 9: For an A interface with TDM transport, the IP interface type shall not be supplied. For an A interface with IP transport, the value "AoIP" may be supplied as IP interface type. + +NOTE 10: For an A interface with TDM transport, the Payload Type shall not be supplied. For an A interface with IP transport, CLEARMODE (see IETF RFC 4040 [92]) or Redundant RTP payload for Audio Data as specified in IETF RFC 2198 [94] encapsulating the CLEARMODE payload shall be supplied as payload type. + +NOTE 11: The parameter shall be supplied for a termination towards a SIP-I based CS CN. For terminations towards a BICC based CS CN, the parameter shall not be supplied. + +### 11a.1.3.2 Transparent CSD + +**Table 17: Transparent CSD MGW Termination Properties For Inter-MSC SRNS Relocation** + +| Termination Packages/Parameters | MSC-A | | | | MSC-B | | | Intermediate Nodes | +|---------------------------------|-----------------------------------------|------------------|----------------|------------------------|----------------------|------------------|----------------|---------------------| +| | T0 | T1 (iu) | T1 (A) | T2 | T7 | T8 (iu) | T8 (A) | T3, T4, T5, T6 | +| TMR | TMR (NOTE 6) | - | - | UDI (NOTE 4) (NOTE 10) | UDI (NOTE 10) | UDI (NOTE 8) | UDI (NOTE 4) | UDI | +| threegcd:plmnb | - | PLMN_BC (NOTE 9) | PLMN_BC | PLMN_BC (NOTE 10) | - | - | - | - | +| threegup:interface | CN (NOTE 3) | RAN | - | CN (NOTE 3) | CN (NOTE 3) | RAN | - | CN (NOTE 3) | +| threegup:mode | (NOTE 3) Support | transparent | - | Support (NOTE 3) | Support (NOTE 3) | transparent | - | Support (NOTE 3) | +| threegup:initdir | (NOTE 3) (NOTE 5) | - | - | OUT (NOTE 3) (NOTE 7) | IN (NOTE 3) (NOTE 7) | - | - | IN (NOTE 3) | +| threegcden:bitrate | - | - | - | - | - | BITRATE (NOTE 1) | - | - | +| threegcd:gsmchancod | - | - | GSM CC | GSM CC (NOTE 2) | - | - | - | - | +| IP Interface Type | NboIP(NOTE 11) | - | AoIP(NOTE 12) | NboIP(NOTE 11) | NboIP(NOTE 11) | - | AoIP (NOTE 12) | NboIP(NOTE 11) | +| Payload Type | CLEARMODE [92] or G.711 [1,x] (NOTE 14) | - | AoIP (NOTE 13) | CLEARMODE (NOTE 14) | CLEARMODE (NOTE 14) | - | AoIP (NOTE 13) | CLEARMODE (NOTE 14) | + +- NOTE 1: This is optional if rate is 64kb/s. In this case no rate adaptation is required. +- NOTE 2: GSM CC shall only be provided if T8 is an A interface. GSM CC shall not be provided if T8 is an Iu interface. +- NOTE 3: Only applicable for a BICC network. +- NOTE 4: Optional +- NOTE 5: Value depends on call direction: IN if terminating call, OUT if originating call. +- NOTE 6: TMR is set according to the value received from ISDN/BICC signalling. In addition, a received USI may be supplied. If no TMR value from ISDN/BICC signalling is available, but the MSC determines with the help of PLMN\_BCs exchanged with the UE that the call is a data call, it shall supply a value derived from the PLMN\_BC. +- NOTE 7: If several MGWs are controlled by the same MSC server, the server may also select the other value. +- NOTE 8: For a data rate of 64 kbit/s, TMR "UDI" may be supplied. For other data rates, TMR "UDI" shall not be sent. +- NOTE 9: For a SCUDIF multimedia call, the MuMe codec shall be configured instead. +- NOTE 10: For a SCUDIF multimedia call, the MuMe codec shall be configured instead in case of BICC termination. +- NOTE 11: The parameter may be supplied with value " NbIoP" for a termination towards a SIP-I based CS CN. For terminations towards a BICC based CS CN, the parameter shall not be supplied. +- NOTE 12: For an A interface with TDM transport, the IP interface type shall not be supplied. For an A interface with IP transport, the value "AoIP" may be supplied as IP interface type. +- NOTE 13: For an A interface with TDM transport, the Payload Type shall not be supplied. For an A interface with IP transport, CLEARMODE (see IETF RFC 4040 [92]) or Redundant RTP payload for Audio Data as specified in IETF RFC 2198 [94] encapsulating the CLEARMODE payload shall be supplied as payload type. +- NOTE 14: The payload type parameter shall be supplied for a termination towards a SIP-I based CS CN. For terminations towards a BICC based CS CN, the parameter shall not be supplied. + +## 11a.2 NT services + +### 11a.2.1 Iu interface and Nb interface at access side of IWF in a BICC based CS CN + +On the Iu interface and if TDM or SIP-I is not used in the CN between the access network and the IWF, this paragraph is applicable, except for the Nb interface in the case of inter-MSC relocation. The Iu and Nb user planes are used in support mode, see 3GPP TS 25.415 [42] and 3GPP TS 29.415 [80]. Each SDU corresponds to one RLP frame and, consequently, is 576 bits long. In GERAN Iu mode another SDU size of 480 bits is possible. It carries two RLP frames of 240 bits and is used if TCH/F9.6 is used in GERAN. Each SDU is transported in one Iu or Nb UP PDU of Type 1. In UTRAN Iu mode, the range of RAB Subflow Combination bit rate values is 14,4 kbit/s, 28,8 kbit/s, 57,6 kbit/s, limited by the maximum bit rate, and varies with the transmission period on the Uu interface, which is 40 ms, 20 ms or 10 ms. In GERAN Iu mode these values are valid if TCH/F14.4, TCH/28.8 or TCH/F43.2 is used. In addition GERAN Iu mode has a RAB Subflow Combination bit rate of 43,2 kbit/s with a transmission period of 13½ ms. If TCH/F9.6 is used, the range of RAB Subflow Combination bit rate values is 12 kbit/s, 24 kbit/s, 36 kbit/s, 48 kbit/s, limited by the maximum bit rate, and varies with the transmission period on the Um interface, which is 40 ms, 20 ms, 13½ ms or 10 ms. A change in the transmission period is signalled to the IWF through the Iu and Nb UP protocols. The Iu or Nb UP primitive Iu- or Nb-UP-DATA-REQUEST is invoked each time an RLP frame is ready to be sent from the IWF towards the UE. DTX indication is not used. + +The following table shows the connection between the RAB subflow combination bit rate and the AIUR. + +**Table 18: Connection between the RAB subflow combination bit rate and AIUR for Non-Transparent CSD Services** + +| RAB subflow combination bit rate | AIUR | Used number of traffic channels and channel coding for GERAN Iu mode | Comment | +|-------------------------------------------------------------------------------------|-------------|----------------------------------------------------------------------|----------| +| 57,6 kbit/s | 57,6 kbit/s | 4xTCH/F14.4, 2xTCH/F28.8 | (Note 1) | +| 43,2 kbit/s | 43,2 kbit/s | 3xTCH/F14.4, 1xTCH/F43.2 | (Note 2) | +| 48 kbit/s | 38,4 kbit/s | 4xTCH/F9.6 | (Note 2) | +| 36 kbit/s | 28,8 kbit/s | 3xTCH/F9.6 | (Note 2) | +| 28,8 kbit/s | 28,8 kbit/s | 2xTCH/F14.4, 1xTCH/F28.8 | (Note 1) | +| 24 kbit/s | 19,2 kbit/s | 2xTCH/F9.6 | (Note 2) | +| 14,4 kbit/s | 14,4 kbit/s | 1xTCH/F14.4 | (Note 1) | +| 12 kbit/s | 9,6 kbit/s | 1xTCH/F9.6 | (Note 2) | +| NOTE 1: RAB subflow combination bit rate is used in UTRAN Iu mode and GERAN Iu mode | | | | +| NOTE 2: RAB subflow combination bit rate is only used in GERAN Iu mode | | | | + +### 11a.2.2 Nb interface at access side of IWF in a BICC based CS CN for Inter-MSC relocation + +For Inter-MSC relocation this paragraph is applicable for the Nb interface in BICC based CS CN between the access network and the IWF. The Nb UP protocol is applied in support mode and the SDU size is 320 bits, transmitted every 5 ms. PDU type 0 is used. The data within the PDU is encoded as A-TRAU' and A-TRAU" frames. + +### 11a.2.3 Nb interface at network side of IWF in a BICC based CS CN + +If TDM is not used, then between the IWF and the fixed network (ISDN or PSTN), for the BICC based CS CN the Nb UP protocol is applied in support mode and the SDU size is 320 bits, transmitted every 5 ms. PDU type 0 is used. + +### 11a.2.4 Nb interface at access side of IWF in a SIP-I based CS CN + +The CLEARMODE RTP payload type shall be used with a framing period of 20 msec. The data within the CLEARMODE RTP payload type shall be transported in a 64 kbit/s bit stream and shall be encoded as for the TDM case of the A interface. + +### 11a.2.5 Nb interface at network side of IWF in a SIP-I based CS CN + +For non-transparent CSD calls CLEARMODE [92] shall be supported in addition to G.711 [1,x] as RTP payload type. + +NOTE: G.711 will only be used if an offerer is not able to determine whether a call is a data call or a speech call. + +For facsimile calls T.38 [y,z] may be supported in addition to G.711. + +For SCUDIF (see TS 23.172 [83]), the "vnd.3gpp.clearmode" RTP payload type (see Annex C) shall be used. + +The negotiation of payload types is described in Clause 15. + +## 11a.2.6 A interface with IP transport + +The CLEARMODE RTP payload type (see IETF RFC 4040[92]) or Redundant RTP payload for Audio Data as specified in IETF RFC 2198 [94] encapsulating the CLEARMODE payload shall be used. Transport without redundancy shall be supported. Transport with redundancy may be supported. Only the redundancy level 2 and level 3 are applicable on the AoIP interface. + +Note: The redundancy level is signalled from the MSC server by the Mc interface as negotiated between the MSC server with the BSC. + +The data within the CLEARMODE RTP payload type shall be transported with a framing period of 20 ms in a 64 kbit/s bit stream and shall be encoded as for the TDM case of the A interface. + +## 11a.3 T services + +### 11a.3.0 Iu interface + +On the Iu interface, the Iu UP is used in transparent mode, see 3GPP TS 25.415 [42]. The payload of the Iu and Nb frames will consist of user data bits only for synchronous data, and RA0 synchronous bit streams for asynchronous data. + +On the Iu interfaces, the payload (SDU) size is fixed, determined by the bit rate. Following table shows SDU sizes. AAL2 is used. The AAL2 SSCS layer shall be supported for segmentation and re-assembly. + +**Table 19: SDU sizes for Transparent CSD Services at Iu interface** + +| Bit rate | SDU size (= RLC PDU payload size) | +|--------------|-----------------------------------| +| 28.8 kbit/s | 576 bits | +| 33.6 kbit/s | 672 bits | +| 32 kbit/s | 640 bits | +| 56/64 kbit/s | 640 bits | + +The primitive Iu-UP \_UNIT-DATA-REQUEST is invoked at regular intervals in order to have a constant bit rate (every SDU). + +### 11a.3.0a Nb interface in BICC based CS CN + +If TDM is not used at the Nb interface, then the Nb UP protocol is applied in support mode and the SDU size is 320 bits, transmitted every 5 ms. PDU type 0 is used. + +### 11a.3.1 Avoidance of delay at RNC + +The TTI-to-CPS Packet packaging delay can be avoided by choosing the length of the CPS packet payload so that the payloads of an integer number of CPS Packets fill one TTI. The contents of the whole TTI can be sent further towards the MSC immediately after the reception without waiting for the next TTI. + +### 11a.3.2 Recovery from the loss of ATM cells + +The ATM cell loss rate is estimated to be very small (less than $10^{-6}$ ... $10^{-8}$ ), the quality of transmission being comparable to that of a high quality ISDN. + +The following happens if a cell is lost (see ITU-T Recommendation I.363.2 [87]): + +- At least one CPS packet is distorted. +- The distorted CPS packet(s) is/are discarded by the receiver. + +- If only one CPS packet is discarded, the upper layer can identify the event by the UUI/SSSAR sequence number, and consequently insert a fill sequence of the length of a CPS payload field to the correct place in the bit stream. ITU-T Recommendation I.366.1[88] (SSSAR) describes that UUI takes value between 0 and 26 for final data and value 27 for more data, but UUI should take value 26 for final data considering compatibility with other SSCS specifications. When UUI works as sequence number by repetition of 27 and 26, CPS packet payload size is equal to half a SDU size. This CPS packet payload size also satisfies the requirement described in subclause 6.2.1. CPS packet payload size is set by ITU-T Recommendation Q.2630.1 [89] over Iu interface. +- If more than one CPS packets are discarded, the upper layer can identify the event by monitoring the buffer level at the ATM/TDM interface or by monitoring the reception of CPS packets with a timer. (The modulo 2 sequence number cannot indicate the loss of two consecutive CPS packets). The following figures apply for the 40 octet payload field. +- Worst case: 2 packets lost $\Rightarrow 2 \times 40$ octets $\times 8$ bits/octet : 64 kbit/s = 10 ms, i.e. buffer level decreased by 80 octets. +- Consequently, recovery with fill inserted in the correct place is possible, if the ATM cell jitter (i.e. transmission delay variation) is less than 5 ms. With a bigger jitter fill may be inserted in a wrong place in the TDM bit stream. + +### 11a.3.3 A interface with IP transport + +The CLEARMODE RTP payload type (see IETF RFC 4040[92]) or Redundant RTP payload for Audio Data as specified in IETF RFC 2198 [94] encapsulating the CLEARMODE payload shall be used. Transport without redundancy shall be supported. Transport with redundancy may be supported. Only the redundancy level 2 and level 3 are applicable on the AoIP interface. + +Note: The redundancy level is signalled from the MSC server by the Mc interface as negotiated between the MSC server with the BSC. + +The data within the CLEARMODE RTP payload type shall be transported with a framing period of 20 ms in a 64 kbit/s bit stream and shall be encoded as for the TDM case of the A interface. + +### 11a.3.4 Nb interface at access side of IWF in a SIP-I based CS CN + +The CLEARMODE RTP payload type shall be used with a framing period of 20 msecs. The data within the CLEARMODE RTP payload type shall be transported in a 64 kbit/s bit stream and shall be encoded as for the TDM case of the A interface. + +### 11a.3.5 Nb interface at network side of IWF in a SIP-I based CS CN + +CLEARMODE [92] shall be supported in addition to G.711 [1,x] as RTP payload types. + +The negotiation of payload types is described in Clause 15. + +--- + +## 12 Frame Synchronization + +Potentially two links are involved in the MSC/IWF regarding the need for frame synchronization, i.e. the link towards the UE and the link towards the fixed network. The links towards the UE are covered by 3GPP TS 48.020 and 48.060 for A/Gb mode and 3GPP TS 25.415 for Iu mode. For the link towards the fixed network, the appropriate sections of ITU-T Recommendation V-series modem, V.110, V.120 and PIAFS Recommendations apply. + +## 12.1 Initial frame synchronization + +### 12.1.1 Terminating side (towards the UE) + +In Iu mode, the terminating side is not synchronous. + +In A/Gb mode, for transparent/non-transparent and interworking to the PSTN or ISDN the interface to the RAN is managed as follows. As soon as the outband signalling exchange indicates that the traffic channel is available the MSC/IWF will start sending frames with the frame contents set as indicated in subclause 9.2.3.4.1 towards the RAN. The MSC/IWF will seek to attain V.110 or A-TRAU frame synchronization on the incoming data from the RAN. V.110 synchronization will be considered to be completed in line with the procedures described in subclause 9.2.3.4.1.1. A-TRAU frame synchronization will be considered to be completed in line with the procedures described in subclause 9.2.3.4.1.2. The incoming data will only be considered valid once the frame synchronization procedure defined in subclause 9.2.3.4.1 is complete. For non-transparent interworking to the PSTN or ISDN, the procedures described in subclause 9.2.4.10.1 shall be followed. + +### 12.1.2 Transit side (towards the fixed network) + +#### 12.1.2.1 Interworking to the PSTN + +In the case of interworking to the PSTN the procedures for initial synchronization for the transparent services are covered in subclause 9.2.3.4.2 and the non-transparent services in subclause 9.2.4.10.2. + +#### 12.1.2.2 Interworking to the ISDN + +In the case of interworking to the ISDN the procedures for initial synchronization for the transparent services are covered in subclause 10.2.3.4.2 and the non-transparent services in subclause 10.2.4.10.2. + +## 12.2 Action on loss of frame synchronization + +The IWF should attempt to recover synchronization as described in the following subsections. If the resynchronization attempt fails, the IWF may clear the call. + +### 12.2.1 Loss on the transit side (towards the fixed network) + +If loss of frame synchronization is detected from the fixed network in line with the procedures specified in the ITU-T or PIAFS recommendation applicable to the type of interworking (V.110, V.120, PIAFS or V-series modem), then re-synchronization is initiated in line with the procedures specified in that recommendation. No change of behaviour of the MSC/IWF on the RAN/MSC link is necessary. + +### 12.2.2 Loss on the terminating side (towards the UE) + +In Iu mode, the terminating side is not synchronous, so loss of synchronisation is not possible. For T services, frames may be lost or arrive irregularly, which handling is implementation dependent. + +In A/Gb mode, if the MSC/IWF detects a loss of frame synchronisation on one or more substreams on the RAN/MSC link, the MSC/IWF initiates a re-synchronisation on the substreams in question as specified in the following. + +The MSC/IWF shall detect a loss of V.110 frame synchronisation in line with the rules specified in ITU-T Recommendation V.110. The MSC/IWF shall detect a loss of A-TRAU frame synchronisation when an A-TRAU frame has been received with at least one error in the synchronisation pattern (ref 3GPP TS 48.020). + +If loss of synchronization is detected on the RAN/MSC link then a re-synchronization process should be initiated. However for this link to the RAN it is only necessary to search for the frame alignment pattern incoming from the RAN. In the case of A-TRAU the synchronisation shall take care of the multiframe alignment according to subclause 9.2.3.4.1.2 and the MSC/IWF shall set the control bit UFE (Uplink Frame Error, see 3GPP TS 48.020) in the next downlink A-TRAU frame to indicate the framing error to the RAN. + +There shall be no action regarding the outgoing frame towards the RAN, other than to continue sending the rate adapted frames made up of the incoming data from the fixed network. During the re-synchronization process data shall continue to be sent towards the fixed network via the modem or ISDN (V.110, V.120, or PIAFS) TA-function as if the frame synchronization were still available. The mapping of the status bits is unchanged during re-synchronization. + +Once synchronization has been re-attained the RLP will recover any possible loss of data on the RAN/MSC link in the case of non-transparent services. The indication of UFE will be stopped in the case of A-TRAU. + +## 13 Call Clearing + +When a call is to be cleared, the MSC/IWF shall handle both the links, towards the UE as well as towards the fixed network. + +At the link towards the UE out-band (3GPP TS 24.008) signalling shall be used. Changes in the in-band status bits shall not be used to signal call clearing. + +At the link towards the fixed network, the clearing procedures appropriate to the fixed network shall be used, together with any additional procedures described in the ITU-T Recommendation applicable to the type of interworking (V.110, V.120, PIAFS or V-series modem). + +## 14 The A-TRAU Framing Protocols + +### 14.1 A-TRAU' Protocol + +The A-TRAU' protocol is defined as follows: + +- A-TRAU' frames are transmitted in regular intervals of 10ms; +- an A-TRAU' frame consists of two consecutive A-TRAU frames (as defined in 3GPP TS 48.020 [28]) each with a length of 320 bit; +- the A-TRAU' protocol is used on a plain 64 kbit/s channel without substreams; +- the same A-TRAU' format is used for the transparent and non-transparent transmission mode; +- in transparent mode the number of data bits in an A-TRAU' frame depend on the user rate only, each user rate corresponds to a fixed number of data bits (see below); +- in non-transparent mode A-TRAU' frames contain always complete RLP frames, rate adaptation is performed by means of the M2 bit; +- the M1-bit is used to identify 1st and 2nd frame in both transmission modes. + +#### 14.1.1 Frame layout for the different transparent user rates + +The number of data bits in an A-TRAU' frame depend on the user rate only, each user rate corresponds to a fixed number of data bits in an A-TRAU' frame. + +**Table 20: A-TRAU' frame layout for transparent user rate** + +| Date Rate | Number of data bits per A-TRAU' frame | +|-------------|---------------------------------------| +| 33.6 kbit/s | 336 | +| 28.8 kbit/s | 288 | + +The data bits are inserted in the A-TRAU' frame starting with D1 of Data field 1 of the first A-TRAU frame. The unused bits are filled with binary '1'. + +#### 14.1.2 A-TRAU' frame format + +One A-TRAU' frame consists of two consecutive A-TRAU frames. Figure 20 shows the format of one A-TRAU frame. + +| Octet number | bit number | | | | | | | | | +|--------------|------------|-----------|-----------|-----------|-----------|-----------|-----------|-----------|---------------------| +| | 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | | +| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | | +| 1 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | | +| 2 | 1 | C1 | C2 | C3 | C4 | C5 | M1 | M2 | | +| 3 | Z1 | D1 | D2 | D3 | D4 | D5 | D6 | D7 | | +| 4 | D8 | D9 | D10 | D11 | D12 | D13 | D14 | D15 | 36 bit data field 1 | +| 5 | D16 | D17 | D18 | D19 | D20 | D21 | D22 | D23 | | +| 6 | D24 | D25 | D26 | D27 | D28 | D29 | D30 | D31 | | +| 7 | D32 | D33 | D34 | D35 | D36 | Z2 | D1 | D2 | | +| 8 | D3 | D4 | D5 | D6 | D7 | D8 | D9 | D10 | | +| 9 | D11 | D12 | D13 | D14 | D15 | D16 | D17 | D18 | 36 bit data field 2 | +| 10 | D19 | D20 | D21 | D22 | D23 | D24 | D25 | D26 | | +| 11 | D27 | D28 | D29 | D30 | D31 | D32 | D33 | D34 | | +| 12 | D35 | D36 | Z3 | D1 | D2 | D3 | D4 | D5 | | +| 13 | D6 | D7 | D8 | D9 | D10 | D11 | D12 | D13 | | +| 14 | D14 | D15 | D16 | D17 | D18 | D19 | D20 | D21 | 36 bit data field 3 | +| 15 | D22 | D23 | D24 | D25 | D26 | D27 | D28 | D29 | | +| 16 | D30 | D31 | D32 | D33 | D34 | D35 | D36 | Z4 | | +| 17 | D1 | D2 | D3 | D4 | D5 | D6 | D7 | D8 | | +| 18 | D9 | D10 | D11 | D12 | D13 | D14 | D15 | D16 | 36 bit data field 4 | +| 19 | D17 | D18 | D19 | D20 | D21 | D22 | D23 | D24 | | +| 20 | D25 | D26 | D27 | D28 | D29 | D30 | D31 | D32 | | +| 21 | D33 | D34 | D35 | D36 | Z5 | D1 | D2 | D3 | | +| 22 | D4 | D5 | D6 | D7 | D8 | D9 | D10 | D11 | | +| 23 | D12 | D13 | D14 | D15 | D16 | D17 | D18 | D19 | 36 bit data field 5 | +| 24 | D20 | D21 | D22 | D23 | D24 | D25 | D26 | D27 | | +| 25 | D28 | D29 | D30 | D31 | D32 | D33 | D34 | D35 | | +| 26 | D36 | Z6 | D1 | D2 | D3 | D4 | D5 | D6 | | +| 27 | D7 | D8 | D9 | D10 | D11 | D12 | D13 | D14 | | +| 28 | D15 | D16 | D17 | D18 | D19 | D20 | D21 | D22 | 36 bit data field 6 | +| 29 | D23 | D24 | D25 | D26 | D27 | D28 | D29 | D30 | | +| 30 | D31 | D32 | D33 | D34 | D35 | D36 | Z7 | D1 | | +| 31 | D2 | D3 | D4 | D5 | D6 | D7 | D8 | D9 | | +| 32 | D10 | D11 | D12 | D13 | D14 | D15 | D16 | D17 | | +| 33 | D18 | D19 | D20 | D21 | D22 | D23 | D24 | D25 | 36 bit data field 7 | +| 34 | D26 | D27 | D28 | D29 | D30 | D31 | D32 | D33 | | +| 35 | D34 | D35 | D36 | Z8 | D1 | D2 | D3 | D4 | | +| 36 | D5 | D6 | D7 | D8 | D9 | D10 | D11 | D12 | | +| 37 | D13 | D14 | D15 | D16 | D17 | D18 | D19 | D20 | 36 bit data field 8 | +| 38 | D21 | D22 | D23 | D24 | D25 | D26 | D27 | D28 | | +| 39 | D29 | D30 | D31 | D32 | D33 | D34 | D35 | D36 | | + +Figure 20: A-TRAU 320 bit frame + +**Data Bits (Dxx):** + +The 288 data bits of an A-TRAU frame are divided in eight fields of 36 bits. + +**Control bits (C Bits):****C1 to C4:** + +The Control bits C1 to C4 define the used data rate. C1 to C4 in the first A-TRAU frame indicate the data rate in send direction. + +C1 to C4 in the second A-TRAU frame indicate the used data rate in backward direction. This is required for Rate Control that is required in uplink direction. For details on Rate Control see 3GPP TS 25.415 [42]. + +**Table 21: A-TRAU' control bits** + +| C1 | C2 | C3 | C4 | Radio Interface User Rate | +|----|----|----|----|---------------------------| +| 1 | 0 | 1 | 1 | 57,6 kbit/s | +| 1 | 0 | 0 | 1 | 43,2 kbit/s | +| 1 | 0 | 1 | 0 | 33,6 kbit/s | +| 1 | 0 | 0 | 0 | 28,8 kbit/s | +| 0 | 1 | 1 | 1 | 14,4 kbit/s | + +**C5:** + +C5 is not used, it is set to binary '1'. + +**Bit M1:** + +An A-TRAU' frame is made of two consecutive A-TRAU which build the transport container for 576 data bits. Bit M1 is used to determine the order of the A-TRAU frames within an A-TRAU' frame. + +The two M1 bits are referred to as the Frame Start Identifier. The FSI value is 01. These values are assigned to the M1 bit as shown below: + +**Table 22: Frame Start Identifier** + +| | M1 bit | +|---------------------|--------| +| First A-TRAU frame | 0 | +| Second A-TRAU frame | 1 | + +**Bit M2:** + +The M2 bit is used to indicate 'valid' A-TRAU' frames. The M2 bit in both of the two consecutive A-TRAU frames relating to an A-TRAU' frame shall have the same value. + +Transparent mode: + +In transparent mode M2 is clamped to binary '0'. + +Non-transparent mode: + +In non-transparent mode M2 is used for DTX. If DTX is applied, M2 is set to binary '1'. If DTX is not to be applied, M2 bit is set to binary '0'. The DTX handling is used in both directions for rate adaptation purpose. This means that the sending entity will insert 'fill RLP-frames' with DTX set to binary '1' in case no RLP-frame is available. + +Fill frames are also sent in order to adapt the RLP transmission frequency to the AIUR. The ratio between RLP frames and 'fill' RLP frames is defined in the following table: + +**Table 23: RLP transmission frequency** + +| AIUR | Ratio between RLP and 'fill' RLP frames | +|-------------|-------------------------------------------| +| 57.6 kbit/s | Only valid frames | +| 43.2 kbit/s | 3 valid frame followed by 1 'fill' frame | +| 28.8 kbit/s | 1 valid frame followed by 1 'fill' frame | +| 14.4 kbit/s | 1 valid frame followed by 3 'fill' frames | + +**Z bits:** + +The bits Zi are used for Framing Pattern Substitution mechanism. This mechanism is defined in 3GPP TS 48.020 [28]. + +**Mapping of A-TRAU' frames to PCM time slots:** + +A-TRAU' frames shall be mapped octet aligned to PCM time slots. I.e. bit number 0 to 7 of each octet of an A-TRAU' frame shall be mapped to bit number 0 to 7 of the PCM time slot. + +## 14.2 A-TRAU" Protocol + +The RLP frame length of 240 bit shall be used. For the transfer of this RLP frame length the A-TRAU" protocol is introduced. An A-TRAU" frame has the same layout as the A-TRAU' frame and contains two A-TRAU frames. + +One RLP frame with the length of 240 bit is contained in one A-TRAU frame. The A-TRAU" protocol is only used for the non-transparent services. + +In Figure 21, the format of the A-TRAU frame for the RLP frame length of 240 is shown. + +| Octet number | Bit number | | | | | | | | | +|--------------|------------|-----------|-----------|-----------|-----------|-----------|-----------|-----------|---------------------| +| | 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | | +| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | | +| 1 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | | +| 2 | 1 | C1 | C2 | C3 | C4 | C5 | M1 | M2 | | +| 3 | Z1 | D1 | D2 | D3 | D4 | D5 | D6 | D7 | | +| 4 | D8 | D9 | D10 | D11 | D12 | D13 | D14 | D15 | 36 bit data field 1 | +| 5 | D16 | D17 | D18 | D19 | D20 | D21 | D22 | D23 | | +| 6 | D24 | D25 | D26 | D27 | D28 | D29 | D30 | D31 | | +| 7 | D32 | D33 | D34 | D35 | D36 | Z2 | D1 | D2 | | +| 8 | D3 | D4 | D5 | D6 | D7 | D8 | D9 | D10 | | +| 9 | D11 | D12 | D13 | D14 | D15 | D16 | D17 | D18 | 36 bit data field 2 | +| 10 | D19 | D20 | D21 | D22 | D23 | D24 | D25 | D26 | | +| 11 | D27 | D28 | D29 | D30 | D31 | D32 | D33 | D34 | | +| 12 | D35 | D36 | Z3 | D1 | D2 | D3 | D4 | D5 | | +| 13 | D6 | D7 | D8 | D9 | D10 | D11 | D12 | D13 | | +| 14 | D14 | D15 | D16 | D17 | D18 | D19 | D20 | D21 | 36 bit data field 3 | +| 15 | D22 | D23 | D24 | D25 | D26 | D27 | D28 | D29 | | +| 16 | D30 | D31 | D32 | D33 | D34 | D35 | D36 | Z4 | | +| 17 | D1 | D2 | D3 | D4 | D5 | D6 | D7 | D8 | | +| 18 | D9 | D10 | D11 | D12 | D13 | D14 | D15 | D16 | 36 bit data field 4 | +| 19 | D17 | D18 | D19 | D20 | D21 | D22 | D23 | D24 | | +| 20 | D25 | D26 | D27 | D28 | D29 | D30 | D31 | D32 | | +| 21 | D33 | D34 | D35 | D36 | Z5 | D1 | D2 | D3 | | +| 22 | D4 | D5 | D6 | D7 | D8 | D9 | D10 | D11 | | +| 23 | D12 | D13 | D14 | D15 | D16 | D17 | D18 | D19 | 36 bit data field 5 | +| 24 | D20 | D21 | D22 | D23 | D24 | D25 | D26 | D27 | | +| 25 | D28 | D29 | D30 | D31 | D32 | D33 | D34 | D35 | | +| 26 | D36 | Z6 | D1 | D2 | D3 | D4 | D5 | D6 | | +| 27 | D7 | D8 | D9 | D10 | D11 | D12 | D13 | D14 | | +| 28 | D15 | D16 | D17 | D18 | D19 | D20 | D21 | D22 | 36 bit data field 6 | +| 29 | D23 | D24 | D25 | D26 | D27 | D28 | D29 | D30 | | +| 30 | D31 | D32 | D33 | D34 | D35 | D36 | Z7 | D1 | | +| 31 | D2 | D3 | D4 | D5 | D6 | D7 | D8 | D9 | | +| 32 | D10 | D11 | D12 | D13 | D14 | D15 | D16 | D17 | | +| 33 | D18 | D19 | D20 | D21 | D22 | D23 | D24 | D25 | 36 bit data field 7 | +| 34 | D26 | D27 | D28 | D29 | D30 | D31 | D32 | D33 | | +| 35 | D34 | D35 | D36 | Z8 | D1 | D2 | D3 | D4 | | +| 36 | D5 | D6 | D7 | D8 | D9 | D10 | D11 | D12 | | +| 37 | D13 | D14 | D15 | D16 | D17 | D18 | D19 | D20 | 36 bit data field 8 | +| 38 | D21 | D22 | D23 | D24 | D25 | D26 | D27 | D28 | | +| 39 | D29 | D30 | D31 | D32 | D33 | D34 | D35 | D36 | | + +Figure 21: Use of A-TRAU frame for RLP frame size of 240 bits + +### Data Bits (Dxx): + +The 288 data bits of an A-TRAU frame are divided in eight fields of 36 bits. + +Only 240 data bits will be used. The data bits D25 ... D 26 of the data field 7 and the data bits D1 ... D36 of the data field 8 are set to '1' in of transfer of 240 bit long RLP frames. + +### Control bits (C Bits): + +#### C1 to C4: + +The Control bits C1 to C4 define the used data rate. C1 to C4 in the first A-TRAU frame indicate the data rate in send direction. + +C1 to C4 in the second A-TRAU frame indicate the used data rate in backward direction. This is required for Rate Control in uplink direction. + +**Table 24: A-TRAU control bits for A-TRAU"** + +| C1 | C2 | C3 | C4 | Radio Interface User Rate | +|----|----|----|----|---------------------------| +| 1 | 0 | 0 | 0 | 28,8 kbit/s | +| 0 | 1 | 1 | 0 | 38,4 kbit/s | +| 0 | 1 | 0 | 1 | 19,2 kbit/s | +| 0 | 1 | 0 | 0 | 9,6 kbit/s | + +#### C5: + +The C5 bit indicates that the A-TRAU" protocol is used and one A-TRAU frame contains one RLP frame with the length of 240 bit. In this case C5 is set binary '0'. + +#### Bit M1: + +For A-TRAU" the M1 bit in each A-TRAU frame is always set to 1. + +#### Bit M2: + +A-TRAU" protocol is only used in non-transparent mode. + +The M2 is used for DTX. If DTX is applied, M2 is set to binary '1'. If DTX is not to be applied, M2 bit is set to binary '0'. The DTX handling is used in both directions for rate adaptation purpose. This means that the sending entity will insert 'fill RLP-frames' with DTX set to binary '1' in case no RLP-frame is available. + +Fill frames are also sent in order to adapt the RLP transmission frequency to the AIUR. The ratio between RLP frames and 'fill' RLP frames is defined in the following table for the A-TRAU" protocol: + +**Table 25: RLP transmission frequency** + +| AIUR | Ratio between RLP and 'fill' RLP frames | +|-------------|-----------------------------------------------------------------------------------------------------------------------| +| 38,4 kbit/s | Each A-TRAU frame is valid | +| 28,8 kbit/s | An A-TRAU" frame with two valid frames is followed by an A-TRAU" frame containing one valid frame and one fill frame. | +| 19,2 kbit/s | Each A-TRAU" frame contains one valid frame and one fill frame. | +| 9,6 kbit/s | An A-TRAU" frame with one valid frame and one fill frame is followed by an A-TRAU" frame containing two fill frames | + +#### Z bits: + +The bits Zi are used for Framing Pattern Substitution mechanism. This mechanism is defined in 3GPP TS 48.020 [28]. + +#### Mapping of A-TRAU" frames to PCM time slots: + +A-TRAU" frames shall be mapped octet aligned to PCM time slots. I.e. bit number 0 to 7 of each octet of an A-TRAU" frame shall be mapped to bit number 0 to 7 of the PCM time slot. + +--- + +## 15 RTP Payload Type Negotiation for Data Calls within a SIP-I based CS Core Network + +### 15.1 RTP payload type negotiation at access side of IWF + +For any data call, the SDP offer shall contain a single m-line with only the CLEARMODE payload type (see IETF RFC4040 [92]). In addition, the ISUP IAM encapsulated in the INVITE to set up the corresponding call leg shall contain TMR UDI. + +### 15.2 RTP payload type negotiation at network side of IWF + +If a call is determined to be a data call other than facsimile or Modem (i.e. TMR "UDI") by the offerer, the SDP offer shall contain a single m-line with only the CLEARMODE payload type (see IETF RFC 4040 [92]). + +If a call is determined to be a facsimile or Modem call by the offerer, the SDP offer shall contain an m-line including only the PCM codec. For facsimile, the offer may include an additional m-line including the t38 payload type (see ITU-T Recommendation T.38 [96] and IETF RFC 3362 [97]). + +If an offerer is not able to determine if a call is a data call or a speech call (TMR "3.1 kHz Audio"), it shall only offer speech codec(s) including the PCM codec. If the PCM codec is offered in combination with other speech codecs, the OoBTC procedures in Clauses 6.12 and 9.3 of TS 23.153 [91] are applicable, + +For SCUDIF (see TS 23.172 [83]), the "vnd.3gpp.clearmode" RTP payload type (see Annex C) shall be offered together with speech codec(s) in a single SDP m-line. The OoBTC procedures in Clause 9.3 of TS 23.153 [91] are applicable. + +## Annex A (informative): SDLs + +The following SDLs are intended to assist in the interpretation of the text in subclause 10.2.2 and are not intended to indicate implementation requirements. Therefore these SDLs are informative only. + +![SDL Diagram: Procedure DataFlow_HLR Sheet 1(1)](a320e67b369bfde4a5fa360b100da55c_img.jpg) + +**Procedure DataFlow\_HLR**Sheet 1(1) + +Detailed description of the SDL diagram logic + +The diagram starts with 'Send Routing Information' from GMSC. It branches based on 'ISDN-BC Present?'. +If No, it checks 'MSISDN has PLMN-BC'. +If Yes, it branches into ITC checks: 'ITC= Speech?', 'ITC= 3.1kHz?', and 'ITC= UDI?'. +Various paths lead to 'Provide Roaming Number' actions, some including PLMN-BC/HLC or ISDN-BC/LLC/HLC, and some referencing specific notes in Section 10.2.2.3 HLR. +A specific exception box notes: 'In exception to this the BC stored in the HLR is regarded valid if one of the following cases applies: If ITC = UDI/RDI and User Rate = 32 kbit/s / 56 kbit/s and User information layer 1 protocol = V.110, I.460/X.30 and the stored BC indicates FTM, PIAFS or Multimedia. If ITC = 3.1 kHz audio and User Rate = 28.8 kbit/s and Modem Type = V.34 and the stored BC indicates Multimedia.' + +Note: The SDLs presented here are indicative of the procedures in section 10.2.2 and are therefore informative only. + +SDL Diagram: Procedure DataFlow\_HLR Sheet 1(1) + +**Figure A.1 (Sheet 1 of 1): Procedures in the HLR** + +Procedure DataFlow\_MSC\_VLR + +![Flowchart for Procedure DataFlow_MSC_VLR showing logic for ISDN-BC, ITC, and VLR stored BC checks to determine SETUP BC parameters.](a0eb8d30ac11ba97b2733c187b89ff22_img.jpg) + +``` + +graph TD + Start(["Initial Address Message" from GMSC]) --> Q1{ISDN-BC Present?} + Q1 -- yes --> Q2{ITC= Speech?} + Q1 -- no --> Q3{VLR has stored BC?} + + Q2 -- yes --> Q4{ISDN ITC field = PLMN ITC field?} + Q2 -- no --> Q5{ITC= 3.1 KHz?} + + Q4 -- yes --> Ref1[Ref Section 10.2.2 VMSC Note 7] + Ref1 --> Action1["* SETUP* BC derived from IAM (BC/HLC/LLC)"] + + Q4 -- no --> Ref2[Ref Section 10.2.2 VMSC Note 7] + Ref2 --> Action2["* SETUP* BC uses VLR (BC/LLC/HLC)"] + + Q3 -- yes --> Ref3[Ref Section 10.2.2 VLR Note 2,3&6] + Ref3 --> Action3["* SETUP* BC uses VLR (BC/LLC/HLC)"] + + Q3 -- no --> Ref4[Ref Section 10.2.2 VLR Note 1,3&6] + Ref4 --> Action4["* SETUP* BC is NOT present"] + + Q5 -- yes --> Q6{HLC= FAX?} + Q5 -- no --> Q7{ITC= UDI?} + + Q6 -- yes --> Q8{VLR has stored BC?} + Q6 -- no --> Q7 + + Q8 -- yes --> Ref5[Ref Section 10.2.2 VMSC Note 5] + Ref5 --> Action5["* SETUP* BC uses stored VLR (BC/LLC/HLC)"] + + Q8 -- no --> Ref6[Ref Section 10.2.2 VMSC Note 5] + Ref6 --> Action6["* SETUP* BC generated dependent upon Subscription to FAX TS61 or TS62"] + + Q7 -- yes --> Q9{ISDN-BC or LLC has User Rate? (except for the 64kbit/s case)} + Q7 -- no --> Error[ERROR in IAM (BC)] + + Q9 -- yes --> Ref7[Ref Section 10.2.2 GMSC Note 4] + Ref7 --> Action7["* SETUP* BC derived from IAM (BC/HLC/LLC)"] + + Q9 -- no --> Node1((1)) + Node1 --> Q3 + + Note1[In exception to this the BC stored in the VLR is received and send to the MS if one of the following cases apply: +If ITC = UDI/RDI and User Rate = 32 kbit/s / 56 kbit/s and User Information Layer 1 protocol = V.110, I.460/X.30 and the stored BC indicates FTM, PIAFS or Multimedia. +If ITC = 3.1 kHz audio and User Rate = 28.8 kbit/s and Modem Type = V.34 and the stored BC indicates Multimedia.] + + Note2[Note: The SDLs presented here are indicative of the procedure in section 10.2.2 and are therefore informative only.] + +``` + +Flowchart for Procedure DataFlow\_MSC\_VLR showing logic for ISDN-BC, ITC, and VLR stored BC checks to determine SETUP BC parameters. + +Figure A.2 (Sheet 1 of 1): Procedures in the MSC/VLR + +## Annex B (informative): General mapping of V.24 circuits to channel status bits + +In the data transfer state, status bits SA, SB and X can be used to convey channel control information associated with the data bits. Table C1 shows the general mapping scheme between the V.24 circuit numbers and the status bits in the IWF. A binary 0 corresponds to the ON condition, a binary 1 to the OFF condition. The specific mappings for the various PLMN bearer types are given elsewhere in the present document. + +Since the V.24 circuits that are outputs from a DCE are inputs to a DTE (and vice versa), this mapping is the reverse of that used in the MT (3GPP TS 27.002, 3GPP TS 27.003). + +For example, CT 109 is an output from the modem in the IWF and maps on to SB towards the MT. In the MT, SB is mapped on to CT 109 which is an input to the attached DTE. + +**Table B1: General mapping scheme at the IWF** + +| Status bit
direction: UE to IWF | Status bit
direction: IWF to UE | Signal at IWF modem
interface | +|------------------------------------|------------------------------------|----------------------------------| +| SB | | 105 (note 3) | +| | X (note 1) | 106 | +| | SA | 107 | +| SA | | 108 | +| | SB | 109 | +| X | | 133 (notes 2 and 3) | + +NOTE 1: The condition of X towards the UE may also be affected by the state of any transmit buffer in the IWF. + +NOTE 2: The condition of CT 133 towards the modem may also be affected by the state of any receive buffer in the IWF or layer 2 flow control condition between the MT and IWF. + +NOTE 3: CT105 and CT133 are assigned to the same connector pin on both the standard 25 pin connector (ISO/IEC 2110 [78]) and the commonly used 9 pin connector (annex B). When this pin is used for CT133 at the DTE/MT interface then on the MT side of the interface CT 105 is treated as being always in the ON condition. SB towards the IWF will therefore also always be ON. Similarly, when this pin is being used for CT105 then on the MT side of the interface CT 133 is treated as being always in the ON condition. X towards the IWF will therefore also always be ON. As circuit 133 is used only in duplex operation and circuit 105 is used only in half duplex operation (which is not supported by the PLMN) there should be no conflict. + +## Annex C (normative): RTP payload type for SCUDIF in SIP-I based CS core network + +### C.1 Scope + +This Annex defines the "vnd.3gpp.clearmode" RTP payload type which shall be used within SDP (see IETF RFC 4566 [98]) to denote the 3G-324.M and the 3G-324.M2 "dummy codecs" defined to indicate a multimedia call for SCUDIF in 3GPP TS 23.172 [83]. Procedures for the codec negotiation applying these codecs are defined in 3GPP TS 23.172 [83] and in Clause 15.2 + +### C.2 RTP payload Type definition + +The "vnd.3gpp.clearmode" RTP payload type shall have the same PDU format and contents as defined for the Clearmode RTP payload type in IETF RFC 4040 [92]. + +The "vnd.3gpp.clearmode" RTP payload type shall be an "audio" media type. + +In addition to the optional "ptime" and "maxptime" parameters, which shall have the same meaning as specified for the Clearmode RTP payload type in IETF RFC 4040 [92], the following additional optional MIME parameter is defined: + +"network-initiated-service-change": + +This parameter shall be supplied for the "3G-324.M2" codec defined in 3GPP TS 23.172 [83]. It shall be omitted for the "3G-324.M" codec defined in 3GPP TS 23.172 [83]. No values shall be supplied for this parameter. + +### C.3 Describing the RTP payload Type in SDP + +The "vnd.3gpp.clearmode" RTP payload shall be described in SDP (see IETF RFC 4566 [98]) as follows. + +- The MIME type ("audio") shall be used in the SDP "m=" line as the media name +- A dynamic RTP payload type number shall be used in the SDP "m=" line. +- The meaning of the dynamic RTP payload type number shall be described by supplying "vnd.3gpp.clearmode" as MIME subtype within an SDP "rtpmap" attribute. +- If supplied, the optional parameter "ptime" shall be encoded as "ptime" SDP attribute. +- If supplied, the optional parameter "maxptime" shall be encoded as "maxptime" SDP attribute. +- If supplied, the optional parameter "network-initiated-service-change" shall be encoded within the "fmtp" SDP attribute. No values for the parameter shall be supplied. + +### C.4 SDP Offer-Answer considerations + +The "network-initiated-service-change" is a declarative parameter. If an "vnd.3gpp.clearmode" RTP payload type with an associated "network-initiated-service-change" parameter is included in an SDP "m="-line in an SDP offer, this RTP payload type shall either be rejected by excluding it from the "m="-line in the SDP answer, or the RTP payload type shall be included in the answer and the associated "network-initiated-service-change" parameter shall then be supplied in the answer. + +### C.5 SDP Example + +The following example shows an SDP offer during the setup of a SCUDIF call, where Multimedia is the preferred encoding and the network initiated service change is supported. AMR and PCM are offered as speech codecs for a fallback. + +``` +m=audio 12345 RTP/AVP 97 98 99 0 +a=rtpmap:97 vnd.3gpp.clearmode/8000 +a=rtpmap:98 vnd.3gpp.clearmode/8000 +a=fmtp:98 network-initiated-service-change +a=rtpmap:99 AMR/8000/1 +a=3gOoBTC +``` + +--- + +## Annex D (informative): + +### IANA registration information for RTP payload types for SCUDIF in SIP-I based CS core network + +#### D.1 Introduction + +This Annex provides information required for the registration of the "vnd.3gpp.clearmode" RTP payload type at IANA. + +NOTE: Such an IANA registration has not been performed. + +## D.2 IANA Registration information + +### D.2.1 Media Type Name + +audio + +### D.2.2 Subtype Name + +vnd.3gpp.clearmode + +### D.2.3 Required parameters + +none + +### D.2.4 Optional parameters + +"ptime" gives the length of time in milliseconds represented by the media in a packet, as described in RFC 4566 [98]. + +"maxptime" represents the maximum amount of media, which can be encapsulated in each packet, expressed as time in milliseconds, as described in IETF RFC 4566 [98]. + +"network-initiated-service-change" denotes if a network initiated service change is supported or applied. It shall be used according to the rules in 3GPP TS 29.007 and 3GPP TS 23.172 [83]. No values shall be supplied for this parameter + +### D.2.5 Encoding considerations + +Framed encoding. + +### D.2.6 Security considerations + +See Section 6 of RFC 4040 [92] + +### D.2.7 Interoperability considerations + +none + +### D.2.8 Published specification + +3GPP TS 29.007. + +### D.2.9 Applications which use this media type + +Service change and UDI/RDI Fallback (SCUDIF), as defined in 3GPP TS 23.172 [83] + +### D.2.10 Additional information + +This type is only defined for transfer via RTP. + +#### D.2.10.1 Magic number(s) + +none + +#### D.2.10.2 File extension(s) + +none + +#### D.2.10.3 Macintosh File Type Code(s) + +none + +#### D.2.10.2 Object Identifier(s) or OID(s) + +none + +## D.2.11 Intended usage + +Limited use. + +This RTP payload type will only be applied within a 3GPP SIP-I based circuit switched core network, as specified in 3GPP TS 23.231 [99] + +## D.2.12 Other Information/General Comment + +none + +## D.2.13 Person to contact for further information + +3GPP Specifications Manager + +[3gppContact@etsi.org](mailto:3gppContact@etsi.org) + +--- + +## Annex E (informative): Change history + +| Change history | | | | | | | | +|-----------------------|--------------|-----------------|-----------|------------|------------------------------------------------------------------------------------------|------------|------------| +| Date | TSG # | TSG Doc. | CR | Rev | Subject/Comment | Old | New | +| 1999-04 | | | | | 09.07 Transferred to 3GPP CN3 | 7.1.0 | | +| | CN#03 | | | | Approved at CN#03 | | 3.0.0 | +| | CN#04 | | 001 | | Introduction of EDGE channel codings into the specifications | 3.0.0 | 3.1.0 | +| | CN#05 | | 002 | | R99 Service Clean-up | 3.1.0 | 3.2.0 | +| | CN#05 | | 003 | | EDGE related corrections | 3.1.0 | 3.2.0 | +| | CN#05 | | 004 | | EDGE Asymmetric channel coding | 3.1.0 | 3.2.0 | +| | CN#06 | | 006 | | R99 service clean up | 3.2.0 | 3.3.0 | +| | CN#06 | | 007 | | Correction of intermediate rate values | 3.2.0 | 3.3.0 | +| | CN#06 | | 008 | | Introduction of Frame Tunnelling Mode | 3.2.0 | 3.3.0 | +| | CN#06 | | 009 | | Updates for UMTS | 3.2.0 | 3.3.0 | +| | CN#06 | | 010 | | Introduction of PIAFS and enhancement of processing at mobile terminated call | 3.2.0 | 3.3.0 | +| | CN#06 | | 011 | | Multimedia call | 3.2.0 | 3.3.0 | +| | CN#07 | | 012 | | Change of reference from ETS 300102-1 to Q.931 | 3.3.0 | 3.4.0 | +| | CN#07 | | 013 | | Handover between GSM and UMTS | 3.3.0 | 3.4.0 | +| | CN#07 | | 014 | | Changes to support fallback to speech in a circuit switched multimedia call set-up | 3.3.0 | 3.4.0 | +| | CN#08 | | 015 | | Handover between 3G MSCs | 3.4.0 | 3.5.0 | +| | CN#08 | | 016 | | Rejection of lower user rates | 3.4.0 | 3.5.0 | +| | CN#08 | | 017 | | Fax | 3.4.0 | 3.5.0 | +| | CN#08 | | 018 | | Clarification of the VMSC behaviour in case of interworking | 3.4.0 | 3.5.0 | +| | CN#08 | | 019 | | Handover between 3G MSCs (Clarification for 56 and 64 kbit/s) | 3.4.0 | 3.5.0 | +| | CN#08 | | 020 | | ISDN TA function in case of bit transparent 56 kbit/s (RDI) and 64 kbit/s (UDI) | 3.4.0 | 3.5.0 | +| | CN#08 | | 021 | | 33.6 kbit/s for multimedia | 3.4.0 | 3.5.0 | +| | CN#09 | | 022 | | Transparent 32 kbit/s data rate with I.460 rate adaptation | 3.5.0 | 4.0.0 | +| | CN#09 | | 025 | | Correction of incomplete part related to the introduction of UMTS NT-RT FAX | 3.5.0 | 4.0.0 | +| | CN#09 | | 026 | | 3.1 kHz multimedia at 33.6 kbit/s | 3.5.0 | 4.0.0 | +| | CN#09 | | 028 | | Clarification related to RCR | 3.5.0 | 4.0.0 | +| | CN#09 | | 029 | | 32 kbit/s UDI/RDI multimedia | 3.5.0 | 4.0.0 | +| | CN#10 | | 032 | | Handover for 56kbit/s | 4.0.0 | 4.1.0 | +| | CN#10 | | 033 | | Removal of BS 30 NT | 4.0.0 | 4.1.0 | +| | CN#11 | | 035 | | A-TRAU' Correction | 4.1.0 | 4.2.0 | +| | CN#11 | | 037 | | A-TRAU' Synchronization | 4.1.0 | 4.2.0 | +| | CN#11 | | 038 | | Removal of FAX NT in GSM from Rel-4 | 4.1.0 | 4.2.0 | +| | CN#11 | | 039 | | Introduction of Nb UP | 4.1.0 | 4.2.0 | +| 2001-12 | CN#14 | NP-010571 | 043 | | Removal of Shared IWF | 4.2.0 | 4.3.0 | +| 2001-12 | CN#14 | NP-010574 | 045 | | SDU size for transparent data at 33.6 kbit/s | 4.2.0 | 4.3.0 | +| 2001-12 | CN#14 | NP-010604 | 044 | 3 | New terminology required by TSG GERAN | 4.3.0 | 5.0.0 | +| 2002-03 | CN#15 | NP-020084 | 049 | 1 | Mobile terminated call with single numbering scheme | 5.0.0 | 5.1.0 | +| 2002-06 | CN#16 | NP-020169 | 046 | 6 | Service change and fallback for UDI/RDI multimedia calls | 5.1.0 | 5.2.0 | +| 2002-06 | CN#16 | NP-020172 | 048 | 1 | Clarification to VMSC/HLR logic for modem/facsimile calls which are signalled as Speech. | 5.1.0 | 5.2.0 | +| 2002-06 | CN#16 | NP-020172 | 052 | 1 | Signalling of FTN calls | 5.1.0 | 5.2.0 | +| 2002-09 | CN#17 | NP-020406 | 055 | 1 | Handling of CSD calls and Inter-MSC Relocation | 5.2.0 | 5.3.0 | +| 2002-09 | CN#17 | NP-020407 | 053 | 3 | Determining the basic service for MT calls | 5.2.0 | 5.3.0 | +| 2002-12 | CN#18 | NP-020617 | 056 | 1 | CS Data Services (including HSCSD and EDGE) for GERAN Iu mode | 5.3.0 | 5.4.0 | +| 2002-12 | CN#18 | NP-020616 | 058 | 1 | Use of Iu UP in support mode for transparent data services at the Nb interface | 5.3.0 | 5.4.0 | +| 2002-12 | CN#18 | NP-020615 | 059 | | Correction on mapping of BC-IE | 5.3.0 | 5.4.0 | +| 2002-12 | CN#18 | NP-020619 | 060 | 3 | Mobile originating BC handling for SCUDIF calls | 5.3.0 | 5.4.0 | +| 2003-03 | CN#19 | NP-030076 | 065 | | Correction of erroneous implemented CR | 5.4.0 | 5.5.0 | +| 2003-03 | CN#19 | NP-030076 | 067 | 1 | Use of Nb UP protocol after inter-MSC handover | 5.4.0 | 5.5.0 | +| 2003-06 | CN#20 | NP-030201 | 070 | | Negotiation of fixed network user rate (FNUR) | 5.5.0 | 5.6.0 | +| 2003-06 | CN#20 | NP-030201 | 071 | 1 | Use of single or multislot configurations | 5.5.0 | 5.6.0 | +| 2003-06 | CN#20 | NP-030203 | 073 | 1 | Subscription check after Call Confirmed | 5.5.0 | 5.6.0 | +| 2003-09 | CN#21 | NP-030328 | 080 | 2 | Interpretation of "no BC-IE in CALL PROC/CONF messages" | 5.6.0 | 5.7.0 | + +| Change history | | | | | | | | +|-----------------------|--------------|-----------------|-----------|------------|-------------------------------------------------------------------------------------|------------|------------| +| Date | TSG # | TSG Doc. | CR | Rev | Subject/Comment | Old | New | +| 2003-09 | CN#21 | NP-030329 | 081 | 1 | Alignment of negotiation rules with 27.001 | 5.6.0 | 5.7.0 | +| 2003-09 | CN#21 | NP-030327 | 084 | 2 | Clarification of Handover description | 5.6.0 | 5.7.0 | +| 2003-12 | CN#22 | NP-030455 | 089 | 4 | Backward signalling of service information between VMSC and GMSC for MTC | 5.7.0 | 5.8.0 | +| 2004-03 | CN#23 | NP-040082 | 096 | | Signalling of LLC and HLC | 5.8.0 | 5.9.0 | +| 2004-06 | CN#24 | NP-040239 | 099 | 1 | Addition of network initiated in-call modification | 5.9.0 | 5.10.0 | +| 2004-12 | CN#26 | NP-040587 | 106 | 1 | Transfer of information from TR 23.910 | 5.10.0 | 6.0.0 | +| 2005-03 | CN#27 | NP-050099 | 109 | 3 | Nb transport for handover between UMTS and GSM | 6.0.0 | 6.1.0 | +| 2005-09 | CP#29 | CP-050375 | 121 | 1 | CSD MGW Termination Properties For Inter-MSC SRNS Relocation | 6.1.0 | 6.2.0 | +| 2005-09 | CP#29 | CP-050380 | 125 | 1 | Correction of References | 6.1.0 | 6.2.0 | +| 2005-09 | CP#29 | CP-050386 | 114 | 2 | CS data Mobile Terminating calls from PSTN | 6.2.0 | 7.0.0 | +| 2005-12 | CP#30 | CP-050506 | 134 | 2 | Correction to transport at access side of IWF | 7.0.0 | 7.1.0 | +| 2005-12 | CP#30 | CP-050507 | 135 | 1 | Corrections to the A-TRAU' and A-TRAU" descriptions | 7.0.0 | 7.1.0 | +| 2006-03 | CP#31 | CP-060053 | 139 | 1 | Clarification of the speech followed by fax case in an splitted (BICC) architecture | 7.1.0 | 7.2.0 | +| 2006-06 | CP#32 | CP-060218 | 145 | 3 | Multimedia & CSD calls | 7.2.0 | 7.3.0 | +| 2008-05 | CP#40 | CP-080300 | 147 | 2 | GSM Bearer Capability in SRI-Ack | 7.3.0 | 7.4.0 | +| 2008-09 | CP#41 | CP-080566 | 148 | 2 | Update to TS 29.007 for SIP-I | 7.4.0 | 8.0.0 | +| 2008-12 | CP#42 | CP-080764 | 149 | 6 | AoIP impacts to Mc parameters | 8.0.0 | 8.1.0 | +| 2008-12 | CP#42 | CP-080754 | 150 | 5 | Data call transport at network side of IWF for SIP-I based CS CN | 8.0.0 | 8.1.0 | +| 2008-12 | CP#42 | CP-080754 | 151 | 1 | RTP payload types for SCUDIF | 8.0.0 | 8.1.0 | +| 2009-12 | CP#46 | | | | Automatic upgrade from previous Release | 8.1.0 | 9.0.0 | +| 2010-09 | CP#49 | CP-100549 | 152 | 1 | Correcting unspecific external reference | 9.0.0 | 9.1.0 | +| 2011-03 | CP#51 | | | | Automatic upgrade from previous Release version 9.1.0 | 9.1.0 | 10.0.0 | +| 2012-09 | CP#57 | | | | Automatic upgrade from previous Release version 10.0.0 | 10.0.0 | 11.0.0 | + +| Change history | | | | | | | | +|-----------------------|----------------|-------------|-----------|------------|------------|------------------------------|--------------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2018-12 | CT #82 | CP-183121 | 0156 | 1 | A | Correction of Editor's Notes | 11.1.0 | \ No newline at end of file diff --git a/marked/Rel-11/29_series/29010/04c7ffb4a475a374f52b88704ecd295f_img.jpg b/marked/Rel-11/29_series/29010/04c7ffb4a475a374f52b88704ecd295f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4e0aa578823cba5ca9a5c4c76b131284cf1e397c --- /dev/null +++ b/marked/Rel-11/29_series/29010/04c7ffb4a475a374f52b88704ecd295f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7a3832bd100b7d065b1fd1d64179579a087bc7183fbd1d0c6fc2160e87293c83 +size 44060 diff --git a/marked/Rel-11/29_series/29010/05eb72d372e4bf78e3d6a64949d77bcc_img.jpg b/marked/Rel-11/29_series/29010/05eb72d372e4bf78e3d6a64949d77bcc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..56eaceadc534643e29ead869024daf1315de2c0a --- /dev/null +++ b/marked/Rel-11/29_series/29010/05eb72d372e4bf78e3d6a64949d77bcc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c18f738750b90704071db2e3c10532fff41406e58698bd5a2fb1d446edb7721e +size 44512 diff --git a/marked/Rel-11/29_series/29010/080a7af02bc47cf21ebfae4e0be39745_img.jpg b/marked/Rel-11/29_series/29010/080a7af02bc47cf21ebfae4e0be39745_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..07bed5ccf05b25784ba72243266e3317c94cf1d6 --- /dev/null +++ b/marked/Rel-11/29_series/29010/080a7af02bc47cf21ebfae4e0be39745_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f54291cea958d1259162a3f7df1ac745e9cc7e2d1f941732a95764cd3800cbd5 +size 25925 diff --git a/marked/Rel-11/29_series/29010/0a73b03fba21af142d619a9a662e6490_img.jpg b/marked/Rel-11/29_series/29010/0a73b03fba21af142d619a9a662e6490_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e4750ac7f3adf9b37cea7de955f60b38df37be42 --- /dev/null +++ b/marked/Rel-11/29_series/29010/0a73b03fba21af142d619a9a662e6490_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2d6c1b913f159b78b6b3ebf055cd46bd631cd00da92aac1fa84ea988b4ee3099 +size 48665 diff --git a/marked/Rel-11/29_series/29010/0c88b98a59dd5d549fed7b13c0ca6536_img.jpg b/marked/Rel-11/29_series/29010/0c88b98a59dd5d549fed7b13c0ca6536_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3b661ad99a74cc9ea0029da37f73d39ae02518f2 --- /dev/null +++ b/marked/Rel-11/29_series/29010/0c88b98a59dd5d549fed7b13c0ca6536_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1efe08f18877905a43375a08207b7d20cd21cdd4269d66b7175a3a290273538b +size 45197 diff --git a/marked/Rel-11/29_series/29010/0d0897dd7f03672d186db9d56ea0d6f5_img.jpg b/marked/Rel-11/29_series/29010/0d0897dd7f03672d186db9d56ea0d6f5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..77db486c852765b46317e1d02dfebfd3f4d784e0 --- /dev/null +++ b/marked/Rel-11/29_series/29010/0d0897dd7f03672d186db9d56ea0d6f5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a1d30308335678b5881ccdb2a11637c5c6860750512ebd4f41fecc95b7836469 +size 45118 diff --git a/marked/Rel-11/29_series/29010/0de91e9b714369b312bf3ab1853301ac_img.jpg b/marked/Rel-11/29_series/29010/0de91e9b714369b312bf3ab1853301ac_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a7a2783a2919ac5460bd880a0e5f011eec0ea928 --- /dev/null +++ b/marked/Rel-11/29_series/29010/0de91e9b714369b312bf3ab1853301ac_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c09b6e6285ded107a7c2843c34a3f06cfb8ad7431d3dee0fddfc6165b3902562 +size 135911 diff --git a/marked/Rel-11/29_series/29010/0ff19975027a3c5177519975f9af055f_img.jpg b/marked/Rel-11/29_series/29010/0ff19975027a3c5177519975f9af055f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..364b4e67ae0c291676ca4874aadb1582035a2bf0 --- /dev/null +++ b/marked/Rel-11/29_series/29010/0ff19975027a3c5177519975f9af055f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6daf289e3ddc2bb379e181f0031ac935a1daa01dddbd5152941c7e98ccd104c2 +size 58670 diff --git a/marked/Rel-11/29_series/29010/114902bbeea56bda01b64b43fad41920_img.jpg b/marked/Rel-11/29_series/29010/114902bbeea56bda01b64b43fad41920_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c4001c7963747c7b4932d1f1ff6800421b0725d6 --- /dev/null +++ b/marked/Rel-11/29_series/29010/114902bbeea56bda01b64b43fad41920_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3f233d949fe43bc2a138abf5dcc5b95981bb77c0b8a538e2527504d62c649972 +size 52612 diff --git a/marked/Rel-11/29_series/29010/17431d8b59408f09df7552d8bdbaa015_img.jpg b/marked/Rel-11/29_series/29010/17431d8b59408f09df7552d8bdbaa015_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..862b6071b8796b05c7758ef1714340c4301ab362 --- /dev/null +++ b/marked/Rel-11/29_series/29010/17431d8b59408f09df7552d8bdbaa015_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e616872ad24dbf208a2eb5bb73e1d885000eabaddefa5c590879d6ca7e1b18bc +size 97253 diff --git a/marked/Rel-11/29_series/29010/17a1ba23b641c01871b08f0a4f08ef48_img.jpg b/marked/Rel-11/29_series/29010/17a1ba23b641c01871b08f0a4f08ef48_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..67e55eebc1356eb186f99a320723e56ff7d2b12d --- /dev/null +++ b/marked/Rel-11/29_series/29010/17a1ba23b641c01871b08f0a4f08ef48_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d4555a4e954c0943e8415e02ff73f1fc313dbfcd626c98671fef4a654e7df3fd +size 23980 diff --git a/marked/Rel-11/29_series/29010/1878426572e3fcbc4483578a685d7c7d_img.jpg b/marked/Rel-11/29_series/29010/1878426572e3fcbc4483578a685d7c7d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d773341de218f445f8a8127818c4503c9867b014 --- /dev/null +++ b/marked/Rel-11/29_series/29010/1878426572e3fcbc4483578a685d7c7d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:96e711143ff88e7ee8e297b591ca39d01a03f0aca1939db0a21a1a05bb663401 +size 18750 diff --git a/marked/Rel-11/29_series/29010/18e519d1f91133e080347562f681dfb5_img.jpg b/marked/Rel-11/29_series/29010/18e519d1f91133e080347562f681dfb5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..61179dc388f6ecec08d7674a577770940f76cc83 --- /dev/null +++ b/marked/Rel-11/29_series/29010/18e519d1f91133e080347562f681dfb5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c8a2bf19e0de69e2fac323a10f5306852b3fafea3b4a1e8e3a495ba771458114 +size 37095 diff --git a/marked/Rel-11/29_series/29010/199a8b4c5c620006757a17e930769566_img.jpg b/marked/Rel-11/29_series/29010/199a8b4c5c620006757a17e930769566_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a233d662761b8202f29953496dd97defb7c4e634 --- /dev/null +++ b/marked/Rel-11/29_series/29010/199a8b4c5c620006757a17e930769566_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6752c90326bb7f9b8a034c95525d43276c3d156849bd00f4b669bcf2c1cda3a9 +size 57594 diff --git a/marked/Rel-11/29_series/29010/19a5f0db57a21a0e82a7f326083e96fd_img.jpg b/marked/Rel-11/29_series/29010/19a5f0db57a21a0e82a7f326083e96fd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3a269af66d24533e92072fcc2c0d47bccfd654fe --- /dev/null +++ b/marked/Rel-11/29_series/29010/19a5f0db57a21a0e82a7f326083e96fd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:226ec0ec0f72d901ea93ff62676aff18d399874fc5d47c1111286fe8e198d749 +size 29481 diff --git a/marked/Rel-11/29_series/29010/20809e79dee38f3d6e03e1ad565a9cf5_img.jpg b/marked/Rel-11/29_series/29010/20809e79dee38f3d6e03e1ad565a9cf5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..405bc3a4e26b28bed6b1452cef199d97f83f9138 --- /dev/null +++ b/marked/Rel-11/29_series/29010/20809e79dee38f3d6e03e1ad565a9cf5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8f8834d5ddedee216e3867f07c4c4fc3c407ef4dae561fce400077b6d2bcb3e1 +size 37060 diff --git a/marked/Rel-11/29_series/29010/20cb2d2cc18d663dc1b82453c67250bb_img.jpg b/marked/Rel-11/29_series/29010/20cb2d2cc18d663dc1b82453c67250bb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9c9f9df931bca705e1547da1b31ae2e1eb06689e --- /dev/null +++ b/marked/Rel-11/29_series/29010/20cb2d2cc18d663dc1b82453c67250bb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b210fb44a239f3f85277db774943bfe235236d40e5a359b52e6566cfdfb210ca +size 46573 diff --git a/marked/Rel-11/29_series/29010/2119293733c74fc64de88aefd597f4bb_img.jpg b/marked/Rel-11/29_series/29010/2119293733c74fc64de88aefd597f4bb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..563845f7cb9358a09741a73ff1274046bb929344 --- /dev/null +++ b/marked/Rel-11/29_series/29010/2119293733c74fc64de88aefd597f4bb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6a55a66c652dd3d6f87a42b7041a9545b6fc0f779a4d85d2eb17f2bc7740278c +size 55593 diff --git a/marked/Rel-11/29_series/29010/215165a27ad7d72bd39fdf55a3cb7486_img.jpg b/marked/Rel-11/29_series/29010/215165a27ad7d72bd39fdf55a3cb7486_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2a3ae006e7287bb465ddce43ddea9abc08aa8121 --- /dev/null +++ b/marked/Rel-11/29_series/29010/215165a27ad7d72bd39fdf55a3cb7486_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:475386e82a572a8f35f9c113456f8792c0aad364ce51fe87286466fb2244aa69 +size 32862 diff --git a/marked/Rel-11/29_series/29010/23cb65390082ab306c15bd3d8196135e_img.jpg b/marked/Rel-11/29_series/29010/23cb65390082ab306c15bd3d8196135e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..40f032dc44739dfaacbb2f104f3d9f822891b44c --- /dev/null +++ b/marked/Rel-11/29_series/29010/23cb65390082ab306c15bd3d8196135e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f54fccb52bc230cf717e8ea56aa6dab6c99232309719b2f1771b7021d3f74145 +size 49744 diff --git a/marked/Rel-11/29_series/29010/245166735676c675f98f535bc4c6f0a1_img.jpg b/marked/Rel-11/29_series/29010/245166735676c675f98f535bc4c6f0a1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..000646966a73c7a843ba8c8bc3a5f5222144576b --- /dev/null +++ b/marked/Rel-11/29_series/29010/245166735676c675f98f535bc4c6f0a1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c4deec613f92ae44310af8e519976c081e30cb1b9ccebc55aeebff13d5206710 +size 127941 diff --git a/marked/Rel-11/29_series/29010/24a89bcaba787f2bc1721356480a4a01_img.jpg b/marked/Rel-11/29_series/29010/24a89bcaba787f2bc1721356480a4a01_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..631da4e9500f7d85bfaed77a15325f321f8b6cf7 --- /dev/null +++ b/marked/Rel-11/29_series/29010/24a89bcaba787f2bc1721356480a4a01_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ee21c9f39535a3cfef92cdc26853f4bdcc2170cfaf099d7288cd79f199e0cc0a +size 33136 diff --git a/marked/Rel-11/29_series/29010/24c9e038a791677ed33100667b64f7e6_img.jpg b/marked/Rel-11/29_series/29010/24c9e038a791677ed33100667b64f7e6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..703ce168965c4e89de15aaa621b14a8945907b5a --- /dev/null +++ b/marked/Rel-11/29_series/29010/24c9e038a791677ed33100667b64f7e6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4f72981b97cbe07c6a7f352dd5ed915fca06e7de30ee17c447373e9063e9bbc9 +size 45222 diff --git a/marked/Rel-11/29_series/29010/26d664119ad25250780f554633444e54_img.jpg b/marked/Rel-11/29_series/29010/26d664119ad25250780f554633444e54_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d6ce6aa97d5f8fb2ec827605de7baab9969b758f --- /dev/null +++ b/marked/Rel-11/29_series/29010/26d664119ad25250780f554633444e54_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2322ab8713b03a02e1f8396283bcafdfae6674f40ee01cb46e2f03267902dcf2 +size 30624 diff --git a/marked/Rel-11/29_series/29010/276d5f4022bc6b9e4687f9ba4fc7594c_img.jpg b/marked/Rel-11/29_series/29010/276d5f4022bc6b9e4687f9ba4fc7594c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4bbd00431dbbbf6f9e1fa70c47e60aed3591338b --- /dev/null +++ b/marked/Rel-11/29_series/29010/276d5f4022bc6b9e4687f9ba4fc7594c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:76f4d31413ff8302b64d66665c21c3c9a89abd42f0032b71bead293a613cdeb8 +size 98436 diff --git a/marked/Rel-11/29_series/29010/27b06ec9f42b5d727a2630f61a5f1861_img.jpg b/marked/Rel-11/29_series/29010/27b06ec9f42b5d727a2630f61a5f1861_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6a9f2303222cef09bba1c8f42357e1727e29027c --- /dev/null +++ b/marked/Rel-11/29_series/29010/27b06ec9f42b5d727a2630f61a5f1861_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:abaa20c1e6b54bad143053f77532ea12cec3da86cb1324701694b64ac7f6be5b +size 9457 diff --git a/marked/Rel-11/29_series/29010/28d75f39a24203712ee907b32cf0bbe5_img.jpg b/marked/Rel-11/29_series/29010/28d75f39a24203712ee907b32cf0bbe5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e9e9ac4601775c309cfac3ee66459c5c63c8fbba --- /dev/null +++ b/marked/Rel-11/29_series/29010/28d75f39a24203712ee907b32cf0bbe5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e98a5131c794b82b4b99d922bcde76b39f0ea33256ca484564bb84e1615392d9 +size 27987 diff --git a/marked/Rel-11/29_series/29010/2fc2e531b3b3c695cca497516ec79f20_img.jpg b/marked/Rel-11/29_series/29010/2fc2e531b3b3c695cca497516ec79f20_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..593206d11be0805c50a5f2bb061affc5fc84414a --- /dev/null +++ b/marked/Rel-11/29_series/29010/2fc2e531b3b3c695cca497516ec79f20_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7e4874d2c078566163995194f1d9158fcb435ca3ca48982bc2424be54245ae2d +size 33017 diff --git a/marked/Rel-11/29_series/29010/30fe9e9487585118063341332e802e98_img.jpg b/marked/Rel-11/29_series/29010/30fe9e9487585118063341332e802e98_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..635e35d8df1b0f7d808aaf03136e41f9a55f8fd0 --- /dev/null +++ b/marked/Rel-11/29_series/29010/30fe9e9487585118063341332e802e98_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:524dd1ce4df7c939d58504f32964d9df74e54702c46a4d81fcc0f5ddbd4d7853 +size 38794 diff --git a/marked/Rel-11/29_series/29010/33f3814facff778a2f6b279c59535a2a_img.jpg b/marked/Rel-11/29_series/29010/33f3814facff778a2f6b279c59535a2a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b6bf628511d18f1dd0748593b11763e2cbbf686b --- /dev/null +++ b/marked/Rel-11/29_series/29010/33f3814facff778a2f6b279c59535a2a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:37e8d7e0cf293d189d68cbd1032787bb1821cb21e70caa7f636b98425a2071a7 +size 33468 diff --git a/marked/Rel-11/29_series/29010/3442f31a562d1ef45bfa18b18a6a1ddc_img.jpg b/marked/Rel-11/29_series/29010/3442f31a562d1ef45bfa18b18a6a1ddc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0fb5fa1eb4d9b0bf65bd9753007d328fa27e452e --- /dev/null +++ b/marked/Rel-11/29_series/29010/3442f31a562d1ef45bfa18b18a6a1ddc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a927d883873e0a1dac38241f97184e54989e2db17654104fe357b93611170fa6 +size 29131 diff --git a/marked/Rel-11/29_series/29010/36f34fd6230a53db267c1df3089ebbe2_img.jpg b/marked/Rel-11/29_series/29010/36f34fd6230a53db267c1df3089ebbe2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3063adaeb3dfd7961e778e170b6cbc293d4d018d --- /dev/null +++ b/marked/Rel-11/29_series/29010/36f34fd6230a53db267c1df3089ebbe2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2603fe8ea017e55e1cbd4ad42617cf2259a3b9298dda39ef4768020d4b0d2f4f +size 129151 diff --git a/marked/Rel-11/29_series/29010/3750b0149a6380885998ab3ca6a8787c_img.jpg b/marked/Rel-11/29_series/29010/3750b0149a6380885998ab3ca6a8787c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d37641929a4d285e738afa49c7d2df49d7554d6a --- /dev/null +++ b/marked/Rel-11/29_series/29010/3750b0149a6380885998ab3ca6a8787c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e801e1683c5e740bda0645b263d01c4247399ffaa86cc3d6680200ee09f5821d +size 52022 diff --git a/marked/Rel-11/29_series/29010/392a79ccd95e682ccd08f35ab2e64144_img.jpg b/marked/Rel-11/29_series/29010/392a79ccd95e682ccd08f35ab2e64144_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a7f3236b10f0a353e8828cf269777ec852078496 --- /dev/null +++ b/marked/Rel-11/29_series/29010/392a79ccd95e682ccd08f35ab2e64144_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ad9afbb526f9833c3291a1fc0d586c85199c5caa13238d4415c73d7b87ce92b6 +size 20451 diff --git a/marked/Rel-11/29_series/29010/3f09464f0a8ac9446981a53f9b78df2c_img.jpg b/marked/Rel-11/29_series/29010/3f09464f0a8ac9446981a53f9b78df2c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..45f1fc3a9c20a0c36d98cb947652b4cdd0717786 --- /dev/null +++ b/marked/Rel-11/29_series/29010/3f09464f0a8ac9446981a53f9b78df2c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4099637f0cf9fe184e30055cc0c342da8ded79d50b8dee1f33ee00cf349542be +size 26811 diff --git a/marked/Rel-11/29_series/29010/4430c1d8e78ac97fda782321410349a9_img.jpg b/marked/Rel-11/29_series/29010/4430c1d8e78ac97fda782321410349a9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8cddfaddb0307108e358d0ff43ae60ca88f416eb --- /dev/null +++ b/marked/Rel-11/29_series/29010/4430c1d8e78ac97fda782321410349a9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6509fa13b39e5ffbf3045826ea61233430ea0b40163a70503ecf237c032f8438 +size 36841 diff --git a/marked/Rel-11/29_series/29010/4540c7355b250cb891be0b54b0ba25c7_img.jpg b/marked/Rel-11/29_series/29010/4540c7355b250cb891be0b54b0ba25c7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3ecec7c9c6906ab0395858f8c3ca0da57882becc --- /dev/null +++ b/marked/Rel-11/29_series/29010/4540c7355b250cb891be0b54b0ba25c7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5e8cc900a52e1a7e1c92418ab133554670f8aafe21e9424d8fa29c37cfbe2981 +size 46757 diff --git a/marked/Rel-11/29_series/29010/48952b53cfa7fc5afa57e46ca69abe1a_img.jpg b/marked/Rel-11/29_series/29010/48952b53cfa7fc5afa57e46ca69abe1a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1e4ff227cf7ff3e4ab5be5752bbf13ad2d299424 --- /dev/null +++ b/marked/Rel-11/29_series/29010/48952b53cfa7fc5afa57e46ca69abe1a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8b0dd7e8def82bc649daf623a0e2bbb822d06f9653c90f2f39827fa749f123d2 +size 31309 diff --git a/marked/Rel-11/29_series/29010/49fe8fe978c0f7e73112d231feb377eb_img.jpg b/marked/Rel-11/29_series/29010/49fe8fe978c0f7e73112d231feb377eb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e9cf87cc32f5e6e1f8b1af2e6e5b0c3504dc7dd0 --- /dev/null +++ b/marked/Rel-11/29_series/29010/49fe8fe978c0f7e73112d231feb377eb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:01fe9d2c3379305a8a14d107dc98d6e331a4a53256eb7da98f3e809a6e769eae +size 29645 diff --git a/marked/Rel-11/29_series/29010/4a94ebc4d41217ce3083a255bfb9c538_img.jpg b/marked/Rel-11/29_series/29010/4a94ebc4d41217ce3083a255bfb9c538_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6d3916f143fdb1fef2918a44a8e4c76310982ab5 --- /dev/null +++ b/marked/Rel-11/29_series/29010/4a94ebc4d41217ce3083a255bfb9c538_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2fb1e9f6ab3c522e2c2f30fd112be9ceff4c8d08b163d4530f911340196e7051 +size 32669 diff --git a/marked/Rel-11/29_series/29010/4e85fe330de2c4f5eea6de4b2a53c77f_img.jpg b/marked/Rel-11/29_series/29010/4e85fe330de2c4f5eea6de4b2a53c77f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6825d90a5b6ed92005b7c14ed121f3c241337fa2 --- /dev/null +++ b/marked/Rel-11/29_series/29010/4e85fe330de2c4f5eea6de4b2a53c77f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e484558e24ed9eb16bcf4c59e7ca6ac87d82ff88b23a2cb2fbc0b2c5fdac0e4e +size 20799 diff --git a/marked/Rel-11/29_series/29010/508bc574df81fa8d3027a374f6d155fc_img.jpg b/marked/Rel-11/29_series/29010/508bc574df81fa8d3027a374f6d155fc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7b7e7248deee98d0bd7c7f61284357e27850d57c --- /dev/null +++ b/marked/Rel-11/29_series/29010/508bc574df81fa8d3027a374f6d155fc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6d8b16b913e2b5a9a8342165df366edc63cd12670b3fa20c77bf259d63ef7fdb +size 48899 diff --git a/marked/Rel-11/29_series/29010/5152ddc7d77f41ae1eaf931aaac810eb_img.jpg b/marked/Rel-11/29_series/29010/5152ddc7d77f41ae1eaf931aaac810eb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e918e380144cc8b1424e2e86dc3ff1e235fd47e1 --- /dev/null +++ b/marked/Rel-11/29_series/29010/5152ddc7d77f41ae1eaf931aaac810eb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:637e661ee66e2e5cb455309bf598c5212f545a13851c38ecb50a6fae13183048 +size 30696 diff --git a/marked/Rel-11/29_series/29010/54159e6d8f5ecc73ad262758e3a60677_img.jpg b/marked/Rel-11/29_series/29010/54159e6d8f5ecc73ad262758e3a60677_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..560938cfaa67482762ccf8869abdd100d90b2d85 --- /dev/null +++ b/marked/Rel-11/29_series/29010/54159e6d8f5ecc73ad262758e3a60677_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:67e98054fbefb07e0c2688901ff85bfb80b0608f97168409e33a3e6bf1bcfb3a +size 52271 diff --git a/marked/Rel-11/29_series/29010/55136bc716146672fc680fa05989f1d2_img.jpg b/marked/Rel-11/29_series/29010/55136bc716146672fc680fa05989f1d2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fd613d0e65f6e2933e5baca74b70554cd7d059f3 --- /dev/null +++ b/marked/Rel-11/29_series/29010/55136bc716146672fc680fa05989f1d2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:dd0531434741a0a58ff83f582a2ad481e0f2d06f708a17cd960f4c39cc8b55bc +size 30709 diff --git a/marked/Rel-11/29_series/29010/5879500ca01e1a2521654beff6c289a4_img.jpg b/marked/Rel-11/29_series/29010/5879500ca01e1a2521654beff6c289a4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cf0a905544c64f2f6dd4e1a422e9e9b89b0b914d --- /dev/null +++ b/marked/Rel-11/29_series/29010/5879500ca01e1a2521654beff6c289a4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8e48bff75055a1067ef1e6a08c0e25725b4f7e3a592fad51e255101b3914b7eb +size 39140 diff --git a/marked/Rel-11/29_series/29010/5c3dd31372f59e15250f0ab1613ca485_img.jpg b/marked/Rel-11/29_series/29010/5c3dd31372f59e15250f0ab1613ca485_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..be85abc60566cac2b563dd09ed034b7d1a6a51e7 --- /dev/null +++ b/marked/Rel-11/29_series/29010/5c3dd31372f59e15250f0ab1613ca485_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a45dfc568543aacf0ce2e9c948a3ca882a780209b84775935a6c0daaba5d9774 +size 26555 diff --git a/marked/Rel-11/29_series/29010/6116b1a533010c170fc526ec513ba0b8_img.jpg b/marked/Rel-11/29_series/29010/6116b1a533010c170fc526ec513ba0b8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..243a2db72acfa5149d852f4fd0b8cb87a64dfec8 --- /dev/null +++ b/marked/Rel-11/29_series/29010/6116b1a533010c170fc526ec513ba0b8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fcb471df5b460abf35cb71e3b8d2407541da7a4f9f0826cdd07fbe77861a1068 +size 42641 diff --git a/marked/Rel-11/29_series/29010/61a7f401eb46fe99a71f27bc37493f04_img.jpg b/marked/Rel-11/29_series/29010/61a7f401eb46fe99a71f27bc37493f04_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d611ca15c35d2523757704b99d0633f2b987ef66 --- /dev/null +++ b/marked/Rel-11/29_series/29010/61a7f401eb46fe99a71f27bc37493f04_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cb0d49f34e6b45b1a0cb9b35dac66d3071c2a653ce0bb4d3c878cd7caf658895 +size 28822 diff --git a/marked/Rel-11/29_series/29010/64cda8ce20067bc360ce2f3a5c9352b7_img.jpg b/marked/Rel-11/29_series/29010/64cda8ce20067bc360ce2f3a5c9352b7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..89133d0b1e90bf5e513db2ff8cecc5bbfcf5c86f --- /dev/null +++ b/marked/Rel-11/29_series/29010/64cda8ce20067bc360ce2f3a5c9352b7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9644a8f6d69400b2a48ddac84996646f4ba3c6de9dd866eb3bdda137b9cc8e7c +size 23175 diff --git a/marked/Rel-11/29_series/29010/65e8c0628536d6d4245e9ab46ba070c3_img.jpg b/marked/Rel-11/29_series/29010/65e8c0628536d6d4245e9ab46ba070c3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2d0628d4efd118e808b92f4298a0f82696d95dc1 --- /dev/null +++ b/marked/Rel-11/29_series/29010/65e8c0628536d6d4245e9ab46ba070c3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4baa6b197ca7470e52247209e4113579d174a7d787858557ac6d3d24347689af +size 20198 diff --git a/marked/Rel-11/29_series/29010/67d03c9e89620d73e3786c869e559752_img.jpg b/marked/Rel-11/29_series/29010/67d03c9e89620d73e3786c869e559752_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a38c1d92099ff422bfca93e1d024a72a28554976 --- /dev/null +++ b/marked/Rel-11/29_series/29010/67d03c9e89620d73e3786c869e559752_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:980b5f82c3e54a7d1d9915c9b6fcf1967cd35cfde38880124e8496ab0e53bbb8 +size 47603 diff --git a/marked/Rel-11/29_series/29010/6a9873d74d8a4e1b6b5ff8d6199cd006_img.jpg b/marked/Rel-11/29_series/29010/6a9873d74d8a4e1b6b5ff8d6199cd006_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..aacf27ca4fa3adf82a458621180f59139c85e46a --- /dev/null +++ b/marked/Rel-11/29_series/29010/6a9873d74d8a4e1b6b5ff8d6199cd006_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7fc38bc7aecb0956cb5015533cff7a27d13bbd1ed6381858f92e61135a8ed036 +size 30226 diff --git a/marked/Rel-11/29_series/29010/6bc05e56e8453678a84fa6bdba3fd903_img.jpg b/marked/Rel-11/29_series/29010/6bc05e56e8453678a84fa6bdba3fd903_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6da11c8c94af6e739298b0ed7f3d6624b101bda6 --- /dev/null +++ b/marked/Rel-11/29_series/29010/6bc05e56e8453678a84fa6bdba3fd903_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6bad78e992c326c5a133711d1373ee056612251cc14df1e340c5ba5e74458448 +size 134147 diff --git a/marked/Rel-11/29_series/29010/6e15fc9ea763541c5913d26f85072ae1_img.jpg b/marked/Rel-11/29_series/29010/6e15fc9ea763541c5913d26f85072ae1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7c34f7425e888f2aacba0def795741cd9269ddf9 --- /dev/null +++ b/marked/Rel-11/29_series/29010/6e15fc9ea763541c5913d26f85072ae1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3e5014bdea7f5df9435e4812957e7f99e4000fd305ab35e7396173563fa0382c +size 40580 diff --git a/marked/Rel-11/29_series/29010/71a22f206329906db6e3860c7ff8c796_img.jpg b/marked/Rel-11/29_series/29010/71a22f206329906db6e3860c7ff8c796_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cb6b7bf1bee5359ab67d939e197ebb2524567fae --- /dev/null +++ b/marked/Rel-11/29_series/29010/71a22f206329906db6e3860c7ff8c796_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3c4e3ed490fd2fe22ecec57d1ee729e8e7c218f2a8ea4b939efbda78367ba113 +size 52126 diff --git a/marked/Rel-11/29_series/29010/71b0a68b4dd64961465d2b0e790538de_img.jpg b/marked/Rel-11/29_series/29010/71b0a68b4dd64961465d2b0e790538de_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f0c74fe769fc45b6195644264a1e2adbb98fcf8b --- /dev/null +++ b/marked/Rel-11/29_series/29010/71b0a68b4dd64961465d2b0e790538de_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1b0011ea42785ef8fca1ad6c9a398d54e4630d8a936ad11648d4c5536e8f4b44 +size 49949 diff --git a/marked/Rel-11/29_series/29010/728ce58d1dcdbbbd39b97904271326ca_img.jpg b/marked/Rel-11/29_series/29010/728ce58d1dcdbbbd39b97904271326ca_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d40b0782c09dc729ebf2e7883cfb285666039186 --- /dev/null +++ b/marked/Rel-11/29_series/29010/728ce58d1dcdbbbd39b97904271326ca_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0c327e8d7834942526cb8e5e64a3a9e39f51e5afab2fb38eb7cf1d430e17af96 +size 41267 diff --git a/marked/Rel-11/29_series/29010/745261f385368efa3f2259c8681874e9_img.jpg b/marked/Rel-11/29_series/29010/745261f385368efa3f2259c8681874e9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..687cfb382c7d8c5b4a92dc5bae071bd6c3489baa --- /dev/null +++ b/marked/Rel-11/29_series/29010/745261f385368efa3f2259c8681874e9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:82cea555c93434decb1e76f3edbff03c7488e3d1a8d573a2a7932dac15de3a46 +size 26208 diff --git a/marked/Rel-11/29_series/29010/74b540f71bcf10a8a66b2f01ea8c08ec_img.jpg b/marked/Rel-11/29_series/29010/74b540f71bcf10a8a66b2f01ea8c08ec_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a05c85d1c178e141016dc3a064d12fb111d190b9 --- /dev/null +++ b/marked/Rel-11/29_series/29010/74b540f71bcf10a8a66b2f01ea8c08ec_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:29c734fd07baca31dd339b310902ef897fd584296afba0e40646919cbd3f2c4e +size 27719 diff --git a/marked/Rel-11/29_series/29010/79e1709a7317ead45379cbb8ff3ba802_img.jpg b/marked/Rel-11/29_series/29010/79e1709a7317ead45379cbb8ff3ba802_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fe73975fe570f7abe535c2a2b2973ad8097148b5 --- /dev/null +++ b/marked/Rel-11/29_series/29010/79e1709a7317ead45379cbb8ff3ba802_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:44751202caf4baa9ada5c8cd84f7215304d5c978cb43ad1cde061cd3a5e5f53e +size 162385 diff --git a/marked/Rel-11/29_series/29010/7b2d685b805535c1e94aee1365753b92_img.jpg b/marked/Rel-11/29_series/29010/7b2d685b805535c1e94aee1365753b92_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..01bfe2160d93b152cb9c47d3fcfd1abbccba6ede --- /dev/null +++ b/marked/Rel-11/29_series/29010/7b2d685b805535c1e94aee1365753b92_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7805e43b2613f178b5a870b42306e60e35ad3ac391c4292d972cd303af6e98af +size 26593 diff --git a/marked/Rel-11/29_series/29010/7d2d1d3870cd224c4430d19334557716_img.jpg b/marked/Rel-11/29_series/29010/7d2d1d3870cd224c4430d19334557716_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..47be8750e108c17d9a460fd6bb806defda145018 --- /dev/null +++ b/marked/Rel-11/29_series/29010/7d2d1d3870cd224c4430d19334557716_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:95dae2b4f26b1013adaae0c4fa5fb8f70deeab468ad68e2ae6b8099debbb8147 +size 29417 diff --git a/marked/Rel-11/29_series/29010/8307f6b04df072c9332f9987e034272c_img.jpg b/marked/Rel-11/29_series/29010/8307f6b04df072c9332f9987e034272c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..95550621ac017b0f416137649b11714e393214fe --- /dev/null +++ b/marked/Rel-11/29_series/29010/8307f6b04df072c9332f9987e034272c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:dcda18b83b90558fd699240a0d193ac2d2cc0c97d5ba38aa23f97fa651523403 +size 178812 diff --git a/marked/Rel-11/29_series/29010/83c2ebae8819e9cdca7eb157a13ee26a_img.jpg b/marked/Rel-11/29_series/29010/83c2ebae8819e9cdca7eb157a13ee26a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2605b81ab1029ba7bb2a676d6eb52cde93a6688c --- /dev/null +++ b/marked/Rel-11/29_series/29010/83c2ebae8819e9cdca7eb157a13ee26a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bb76ba3e561148ce16495b0b1d1cfbd535369de474721692f6d8a899d2d5840c +size 24806 diff --git a/marked/Rel-11/29_series/29010/848073118eebfdbfdb9a60e3923fe0b3_img.jpg b/marked/Rel-11/29_series/29010/848073118eebfdbfdb9a60e3923fe0b3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4ec3a957fc6abadd72291fcfc6842a074a0ebc14 --- /dev/null +++ b/marked/Rel-11/29_series/29010/848073118eebfdbfdb9a60e3923fe0b3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d37858aa73abc670421bc6a0f52392c8e4c8007d1ecd2a9be8f8805aa8e8f73a +size 27881 diff --git a/marked/Rel-11/29_series/29010/8d325fc12b494e42c9ea7ed2a7f327a6_img.jpg b/marked/Rel-11/29_series/29010/8d325fc12b494e42c9ea7ed2a7f327a6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..35cf9b1a98a21c795d9e7dc8ba13143420ba7642 --- /dev/null +++ b/marked/Rel-11/29_series/29010/8d325fc12b494e42c9ea7ed2a7f327a6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a9736dde25c9ab5d530e30a1c24128cfd6c6c4bf01e9af8f9e62303c07b9627c +size 45006 diff --git a/marked/Rel-11/29_series/29010/8d66c9c295023a1380f9986d3663bb1e_img.jpg b/marked/Rel-11/29_series/29010/8d66c9c295023a1380f9986d3663bb1e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..aeba961ba157e749833315743bd34bc86c08bf9e --- /dev/null +++ b/marked/Rel-11/29_series/29010/8d66c9c295023a1380f9986d3663bb1e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5e0362a91821b7c859bc89e2b83f1edb4ac08312ae51031f3003dd5e69e61d6a +size 28777 diff --git a/marked/Rel-11/29_series/29010/8e80de0cac529b2c3775d677c5203133_img.jpg b/marked/Rel-11/29_series/29010/8e80de0cac529b2c3775d677c5203133_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2a58b3b5f750f899e2d05033e6d69435b8ab4cc5 --- /dev/null +++ b/marked/Rel-11/29_series/29010/8e80de0cac529b2c3775d677c5203133_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7ad54ed3587850381f4805a83c70df6215c4f4063a3a9647bcc2d6a080efcffc +size 31616 diff --git a/marked/Rel-11/29_series/29010/8f8caebe58364416a2eda21039d8c7bf_img.jpg b/marked/Rel-11/29_series/29010/8f8caebe58364416a2eda21039d8c7bf_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..837009b501e083e36d4835a4283ec4f540b67e2b --- /dev/null +++ b/marked/Rel-11/29_series/29010/8f8caebe58364416a2eda21039d8c7bf_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c905cd837974a80ffe1b290c7f3b38724014ac56b2d939abd4628faa4113c601 +size 49506 diff --git a/marked/Rel-11/29_series/29010/90ddb84c323b956e2d50a54d3f870566_img.jpg b/marked/Rel-11/29_series/29010/90ddb84c323b956e2d50a54d3f870566_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5e69350237153397882640cda5074ee683e2f02a --- /dev/null +++ b/marked/Rel-11/29_series/29010/90ddb84c323b956e2d50a54d3f870566_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b3811830dc012e8936db6040c64279f5c61fbe4fa162956c6797cda2a0cd5dc2 +size 24366 diff --git a/marked/Rel-11/29_series/29010/910aca984b27c368361b38751ab5eea6_img.jpg b/marked/Rel-11/29_series/29010/910aca984b27c368361b38751ab5eea6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..83c805b0e93a94e0f860e799f3fe5eb3f062be4b --- /dev/null +++ b/marked/Rel-11/29_series/29010/910aca984b27c368361b38751ab5eea6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8d1c2d34f0818ff1bace9dac354c3eb61dde8d120eebef17f0149514c862843e +size 17560 diff --git a/marked/Rel-11/29_series/29010/91134b9a38d7f73f03375473e7b706f9_img.jpg b/marked/Rel-11/29_series/29010/91134b9a38d7f73f03375473e7b706f9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6c5e41d5b66cea5dd2dce4a960ffd53af294b7e5 --- /dev/null +++ b/marked/Rel-11/29_series/29010/91134b9a38d7f73f03375473e7b706f9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fdf9ed048f25b9c611a0a17c5cf7a7b5f913dc10ed75764fb98d15fd9c2af121 +size 32270 diff --git a/marked/Rel-11/29_series/29010/9252ccfbbe9e34cb108f0060f2b563f1_img.jpg b/marked/Rel-11/29_series/29010/9252ccfbbe9e34cb108f0060f2b563f1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..549a45de9004062153f851b0339d3e8dfaf2c15d --- /dev/null +++ b/marked/Rel-11/29_series/29010/9252ccfbbe9e34cb108f0060f2b563f1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:78d38b33b90c184081f39fcffe450f16cdd9c82e2cb130813a595b5b582b457c +size 167562 diff --git a/marked/Rel-11/29_series/29010/94fd137860c16c8dfd75512f10161fe8_img.jpg b/marked/Rel-11/29_series/29010/94fd137860c16c8dfd75512f10161fe8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7b758c3cec36d8191d30a8a218bdf21f45ce9576 --- /dev/null +++ b/marked/Rel-11/29_series/29010/94fd137860c16c8dfd75512f10161fe8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:278bab7c97c27013c6f3591d7c9c2227e628adf9ca19a8fc20bb8df8aa0c6bca +size 50352 diff --git a/marked/Rel-11/29_series/29010/967e98a12645f89cb4a7620f42bf8c2e_img.jpg b/marked/Rel-11/29_series/29010/967e98a12645f89cb4a7620f42bf8c2e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f06a08842eab35e16ae639bcf96de447badd355d --- /dev/null +++ b/marked/Rel-11/29_series/29010/967e98a12645f89cb4a7620f42bf8c2e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ebe3d81d1e78a20b7e6b5c68e597bf2ec739b014caf0acc619c8b6abb430f69d +size 30288 diff --git a/marked/Rel-11/29_series/29010/9b1ec0090070bdf52ea28763b8d52477_img.jpg b/marked/Rel-11/29_series/29010/9b1ec0090070bdf52ea28763b8d52477_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..10a2bd7c380d311550ec52c50845ad11b8edef6e --- /dev/null +++ b/marked/Rel-11/29_series/29010/9b1ec0090070bdf52ea28763b8d52477_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:270d0257263577e5c34255c7b02f63a77f53e24010afc7ba0d9b355b5d18e415 +size 44984 diff --git a/marked/Rel-11/29_series/29010/9b9262a549828579ab904148450734f6_img.jpg b/marked/Rel-11/29_series/29010/9b9262a549828579ab904148450734f6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c50653eed8d5b1471312dc4436a30145d0e8e443 --- /dev/null +++ b/marked/Rel-11/29_series/29010/9b9262a549828579ab904148450734f6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0c4551b0c2f23bc179e3a0f6988f54847465a1277c06f7d525f01d5e2cd6c5be +size 47261 diff --git a/marked/Rel-11/29_series/29010/9cb54072e43a6b6717eb16036a7640a2_img.jpg b/marked/Rel-11/29_series/29010/9cb54072e43a6b6717eb16036a7640a2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9f0dbf67dffc04364224a1083ee9ff988da3dd98 --- /dev/null +++ b/marked/Rel-11/29_series/29010/9cb54072e43a6b6717eb16036a7640a2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fe8e2f6bc5138bf03c8c8d19a738bd7d72cefb0c36aca11fd352c78643540612 +size 37374 diff --git a/marked/Rel-11/29_series/29010/9cbc1ebd80813fc36e499f7d70ed6881_img.jpg b/marked/Rel-11/29_series/29010/9cbc1ebd80813fc36e499f7d70ed6881_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2b5614147f1962fcdac5613d4bcadcb723cf7520 --- /dev/null +++ b/marked/Rel-11/29_series/29010/9cbc1ebd80813fc36e499f7d70ed6881_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:35c9eeab050734fc75c9cf01a0bbc126a867f94009e4aa873a7917d8550d597e +size 45333 diff --git a/marked/Rel-11/29_series/29010/9f9fdebeade37ad92fdd68d6ea9f58ce_img.jpg b/marked/Rel-11/29_series/29010/9f9fdebeade37ad92fdd68d6ea9f58ce_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..218e72df02789bd571e52efcdc85d96ca37a5094 --- /dev/null +++ b/marked/Rel-11/29_series/29010/9f9fdebeade37ad92fdd68d6ea9f58ce_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:eebd4957f665afdd3bada5d115acb23a8fc87614900458dc623d4a5781b81c04 +size 124932 diff --git a/marked/Rel-11/29_series/29010/a0739aaf13fa5a632d4faa830f6b2708_img.jpg b/marked/Rel-11/29_series/29010/a0739aaf13fa5a632d4faa830f6b2708_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..40ab3a9b735d550be9fa778083b393ae10cc6362 --- /dev/null +++ b/marked/Rel-11/29_series/29010/a0739aaf13fa5a632d4faa830f6b2708_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f8235b05258679556d4bcbb69123bb0897105b9a8a6c0288f2ea543c701d86e3 +size 29114 diff --git a/marked/Rel-11/29_series/29010/a0b72ad654428ce2b44766f24928643e_img.jpg b/marked/Rel-11/29_series/29010/a0b72ad654428ce2b44766f24928643e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..049eb227094672e4af8b49b6c65b09d6dcc68c6e --- /dev/null +++ b/marked/Rel-11/29_series/29010/a0b72ad654428ce2b44766f24928643e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:30293fe330851d90ca29aa72ffc341b266bf925bda5d55a1da5d4dfb8fa754cd +size 20022 diff --git a/marked/Rel-11/29_series/29010/a0e8fe7862a6d7341faf5dac275277cc_img.jpg b/marked/Rel-11/29_series/29010/a0e8fe7862a6d7341faf5dac275277cc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7b40d18abb7b0f0b35371db24e9f50ab0ce56632 --- /dev/null +++ b/marked/Rel-11/29_series/29010/a0e8fe7862a6d7341faf5dac275277cc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2481c2132ae8a0cd9d32322ddae6ab689cf4221fa589ea951adbe96263fa6a97 +size 45215 diff --git a/marked/Rel-11/29_series/29010/a2bbc82e5c6132b0870bd70f6657f919_img.jpg b/marked/Rel-11/29_series/29010/a2bbc82e5c6132b0870bd70f6657f919_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fcb9eea5b319182bfd05c857c5274774a31dc1b1 --- /dev/null +++ b/marked/Rel-11/29_series/29010/a2bbc82e5c6132b0870bd70f6657f919_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9739df5b29dc19b37a521c0e8a49bebf93717214f0fff173991905ad60345e05 +size 46334 diff --git a/marked/Rel-11/29_series/29010/a3b3abbf6d0b18f3dd4a83680b5e3e42_img.jpg b/marked/Rel-11/29_series/29010/a3b3abbf6d0b18f3dd4a83680b5e3e42_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..36604b758c78a085538c4d1cc00191200ccbe4ad --- /dev/null +++ b/marked/Rel-11/29_series/29010/a3b3abbf6d0b18f3dd4a83680b5e3e42_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:48ae851cb1995ea933ac4ce9130e3a53a284d6a8d55e1d02a04ca2c5a0376112 +size 36561 diff --git a/marked/Rel-11/29_series/29010/a4b963a07cc368283154762c4b156fe7_img.jpg b/marked/Rel-11/29_series/29010/a4b963a07cc368283154762c4b156fe7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e864aea11b8881e91709515ad6ea83be0f098431 --- /dev/null +++ b/marked/Rel-11/29_series/29010/a4b963a07cc368283154762c4b156fe7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ed4ff4f762a50e352ae395c60601acc3b1e2b0a7cf9497802a860e2176146c26 +size 71193 diff --git a/marked/Rel-11/29_series/29010/a5404b7275b06497eecf9b5883604753_img.jpg b/marked/Rel-11/29_series/29010/a5404b7275b06497eecf9b5883604753_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..86418b0ff05f3cf45f6e837de3b90d35f1438068 --- /dev/null +++ b/marked/Rel-11/29_series/29010/a5404b7275b06497eecf9b5883604753_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b9d184af4a209a868119a7da2049f68df311b312ad342c755f8d6b5b80ff192a +size 98583 diff --git a/marked/Rel-11/29_series/29010/a5b9392ecb96e6b5e0b4ee0664210f72_img.jpg b/marked/Rel-11/29_series/29010/a5b9392ecb96e6b5e0b4ee0664210f72_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1342af02b15841eaaf81dcc82c57e93e7a93b7b1 --- /dev/null +++ b/marked/Rel-11/29_series/29010/a5b9392ecb96e6b5e0b4ee0664210f72_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:39b879907fff4e9f0fdfc0db2b7e2c44c449885336ecfcd1abb361512f3f3867 +size 38612 diff --git a/marked/Rel-11/29_series/29010/a7450c80e88ad3f6ca1427ad84020998_img.jpg b/marked/Rel-11/29_series/29010/a7450c80e88ad3f6ca1427ad84020998_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b7b704f694ec010bd1f6e6caa3fcee307da5b128 --- /dev/null +++ b/marked/Rel-11/29_series/29010/a7450c80e88ad3f6ca1427ad84020998_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1af1dd91e7d42ac589679c48aac4c3a6edbf9d0b5ea0807da2f16c27f0985171 +size 96537 diff --git a/marked/Rel-11/29_series/29010/a82bc78bff7fbefef1c0fb744365f957_img.jpg b/marked/Rel-11/29_series/29010/a82bc78bff7fbefef1c0fb744365f957_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e6608fe04ea0327b78fe2043b99034e905560d4b --- /dev/null +++ b/marked/Rel-11/29_series/29010/a82bc78bff7fbefef1c0fb744365f957_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0534420c95bad731e4d2685d3ed7f928ef6995aa7abccaa488fbfebabe8cf4e3 +size 21537 diff --git a/marked/Rel-11/29_series/29010/adc652b19ecea71dd56a9f5821ae7cc0_img.jpg b/marked/Rel-11/29_series/29010/adc652b19ecea71dd56a9f5821ae7cc0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c0bd50bdc39001a7167cad9efeba5494a06c175b --- /dev/null +++ b/marked/Rel-11/29_series/29010/adc652b19ecea71dd56a9f5821ae7cc0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:52e33f710694deb15aaf0dde8921ac0055f82b3d6af2f0bd643938ea1aab47b5 +size 35794 diff --git a/marked/Rel-11/29_series/29010/ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg b/marked/Rel-11/29_series/29010/ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b8c9f6772cb8efd56866d62ce8a01cd82178a7a1 --- /dev/null +++ b/marked/Rel-11/29_series/29010/ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9e88c084b2687d9b7f8fe7c918c4f164cd4c13de31aff81e3ebec449c7796bc4 +size 44355 diff --git a/marked/Rel-11/29_series/29010/b34c69e1ec326b01c3a485b27b1df5f6_img.jpg b/marked/Rel-11/29_series/29010/b34c69e1ec326b01c3a485b27b1df5f6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cff7fb4056eb33989bf683aaf7b6b17d22704c68 --- /dev/null +++ b/marked/Rel-11/29_series/29010/b34c69e1ec326b01c3a485b27b1df5f6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3bbd70824ecb49f470c0ff56d714dcd0f0bdda09853b1b0d9bc58bc5b74da15e +size 30972 diff --git a/marked/Rel-11/29_series/29010/b3cd59f24a21fab4cd8ac6fe743ab3a9_img.jpg b/marked/Rel-11/29_series/29010/b3cd59f24a21fab4cd8ac6fe743ab3a9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..839bd180d59b4752c7b56241df72bdc918bd3f2a --- /dev/null +++ b/marked/Rel-11/29_series/29010/b3cd59f24a21fab4cd8ac6fe743ab3a9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7f5c8bde28ee18b99cc34b94eea766f3defbfb672e8f02f86557d1343262fcc4 +size 27490 diff --git a/marked/Rel-11/29_series/29010/b432c6c13fa4f8bb90f5fb9060ef3bcd_img.jpg b/marked/Rel-11/29_series/29010/b432c6c13fa4f8bb90f5fb9060ef3bcd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..11d6540b7203ac310d1718e0ea7eb5afc06df5d0 --- /dev/null +++ b/marked/Rel-11/29_series/29010/b432c6c13fa4f8bb90f5fb9060ef3bcd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9b73115a05606daff70cf9547e4372a096e8de1aa5361b77dc317cdb18d3c1ce +size 21131 diff --git a/marked/Rel-11/29_series/29010/b4f6d3668f7e851eaff07ccf26001623_img.jpg b/marked/Rel-11/29_series/29010/b4f6d3668f7e851eaff07ccf26001623_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d953871639e6c7823a2b4b5f16032a02447e88fa --- /dev/null +++ b/marked/Rel-11/29_series/29010/b4f6d3668f7e851eaff07ccf26001623_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:28afddbfa7cd1f02605590a492662a34b22ce75c8527eed40fadfde73b92b25e +size 47627 diff --git a/marked/Rel-11/29_series/29010/b5335262987c819d7f71ce40f99cb71b_img.jpg b/marked/Rel-11/29_series/29010/b5335262987c819d7f71ce40f99cb71b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b3c0657672511d73e6bd11bb231dc5d38106c711 --- /dev/null +++ b/marked/Rel-11/29_series/29010/b5335262987c819d7f71ce40f99cb71b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cb3ac49ab5ee29599159c12aa8c82533bbbfdfec84902a9737f4c9089ff466f6 +size 69405 diff --git a/marked/Rel-11/29_series/29010/b904ac2472cab80892d1e783e6230d6e_img.jpg b/marked/Rel-11/29_series/29010/b904ac2472cab80892d1e783e6230d6e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..48852fe36fe6870587460fa563c382c125f08eb6 --- /dev/null +++ b/marked/Rel-11/29_series/29010/b904ac2472cab80892d1e783e6230d6e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5038f97a695fea1b82b022b6eb7b0e9f8d600ceb364d34f38694589ed81fdbee +size 51820 diff --git a/marked/Rel-11/29_series/29010/b996d5a6408db9c4b3ac3aafd2ef44cf_img.jpg b/marked/Rel-11/29_series/29010/b996d5a6408db9c4b3ac3aafd2ef44cf_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0f8e9cdd3385d451b88f4edfce98f94c39f97430 --- /dev/null +++ b/marked/Rel-11/29_series/29010/b996d5a6408db9c4b3ac3aafd2ef44cf_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:68958b937f5b1def770edcbcfb33be9232a68483ce59df50f4040f1102830a0c +size 18586 diff --git a/marked/Rel-11/29_series/29010/bb3354f497635d15bef873577125c48d_img.jpg b/marked/Rel-11/29_series/29010/bb3354f497635d15bef873577125c48d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e3a5be895ea6b9ce051a92e69527887614ef1a3a --- /dev/null +++ b/marked/Rel-11/29_series/29010/bb3354f497635d15bef873577125c48d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:882a0a761294d23f79096fb7ce6854cac8e53210346a7c809a572d113793c42a +size 16640 diff --git a/marked/Rel-11/29_series/29010/bdd96f20e71f079cad85240efb3d3f24_img.jpg b/marked/Rel-11/29_series/29010/bdd96f20e71f079cad85240efb3d3f24_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1cac8751f1c5c59e3590deae682423f2bf9d774b --- /dev/null +++ b/marked/Rel-11/29_series/29010/bdd96f20e71f079cad85240efb3d3f24_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1be813881aeb3dadccb6e0dc8fff222e580c892c6e6da90df411ca7700bde843 +size 27233 diff --git a/marked/Rel-11/29_series/29010/bfc7918b689a38bc811276e0cc69477e_img.jpg b/marked/Rel-11/29_series/29010/bfc7918b689a38bc811276e0cc69477e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2f23220c8d649001e4ff23e64766be6356414462 --- /dev/null +++ b/marked/Rel-11/29_series/29010/bfc7918b689a38bc811276e0cc69477e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5fed8c5796a24b3849009c8576d9a988205801aabc1cd9529bd22738747e7374 +size 124305 diff --git a/marked/Rel-11/29_series/29010/c0ca823603794512478906b302176bca_img.jpg b/marked/Rel-11/29_series/29010/c0ca823603794512478906b302176bca_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..67b5bdc235e1b16efc449c6e22c7c6b7373a406d --- /dev/null +++ b/marked/Rel-11/29_series/29010/c0ca823603794512478906b302176bca_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3a0e903b702e02b98fc91c20b68335e60051441c38a9258950ea0be27d3dc80b +size 89353 diff --git a/marked/Rel-11/29_series/29010/c0f4777175572d5c52cae16fdddd70be_img.jpg b/marked/Rel-11/29_series/29010/c0f4777175572d5c52cae16fdddd70be_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..07a6ca29494d6de5b40ea5b0ae3fd673d70fd463 --- /dev/null +++ b/marked/Rel-11/29_series/29010/c0f4777175572d5c52cae16fdddd70be_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d931676c68f425b8338633d707b5bb7ca6f9194667faa18b85ce99458fc76442 +size 38175 diff --git a/marked/Rel-11/29_series/29010/c1278da91cbcabe32628e589ebc47418_img.jpg b/marked/Rel-11/29_series/29010/c1278da91cbcabe32628e589ebc47418_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e37400a5ec21582b7557da7aad61dc8d46295ff7 --- /dev/null +++ b/marked/Rel-11/29_series/29010/c1278da91cbcabe32628e589ebc47418_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f763e8c7198e0d0cc79773ad203f2686e06584007698676e31b65dfb86b548b9 +size 16940 diff --git a/marked/Rel-11/29_series/29010/c6e0b9030f9fb81435eaf9cb71532614_img.jpg b/marked/Rel-11/29_series/29010/c6e0b9030f9fb81435eaf9cb71532614_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..69acc9b8b3b1ff60cdbeadc84fe786354281b577 --- /dev/null +++ b/marked/Rel-11/29_series/29010/c6e0b9030f9fb81435eaf9cb71532614_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:496f719642a3faca9a0560e8ac47733c5e0af7d429b977644107264d57e41cae +size 19816 diff --git a/marked/Rel-11/29_series/29010/cc7baa8e5118f4b42c01166637c738ea_img.jpg b/marked/Rel-11/29_series/29010/cc7baa8e5118f4b42c01166637c738ea_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f52cfb09a35e317fa48c8a0802bc499872506a13 --- /dev/null +++ b/marked/Rel-11/29_series/29010/cc7baa8e5118f4b42c01166637c738ea_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:48d9ac2697eebe5b13185e094bbcd3630bd9b1237a5f2ad501ea6968bc63296d +size 121808 diff --git a/marked/Rel-11/29_series/29010/d04c50badc78d5ba47bf4e352af4a754_img.jpg b/marked/Rel-11/29_series/29010/d04c50badc78d5ba47bf4e352af4a754_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1334d3d6012025d03a992eab264f712f088d3bdf --- /dev/null +++ b/marked/Rel-11/29_series/29010/d04c50badc78d5ba47bf4e352af4a754_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e37893e15edc6d4e6e7ee00d9c9559d7568152b321b7d4b2a9a7e3cb99ec22b0 +size 90028 diff --git a/marked/Rel-11/29_series/29010/d15e2d3e8dd9157eb7f0cc120097484a_img.jpg b/marked/Rel-11/29_series/29010/d15e2d3e8dd9157eb7f0cc120097484a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..869b66602877be18cf05cb2eae66b6f7a7b3e02b --- /dev/null +++ b/marked/Rel-11/29_series/29010/d15e2d3e8dd9157eb7f0cc120097484a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ce7f7c3eef5304eef5d5334f6b657f3ac50d7046e2bd6aebc6c46151a8cc8e0a +size 27251 diff --git a/marked/Rel-11/29_series/29010/d3b5eac55166fc428a223bba5c46961b_img.jpg b/marked/Rel-11/29_series/29010/d3b5eac55166fc428a223bba5c46961b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..22af9b2da4875bff62861c26d1eff81e2f1bffaa --- /dev/null +++ b/marked/Rel-11/29_series/29010/d3b5eac55166fc428a223bba5c46961b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6fe4749ffcb27165418345292a8dc2029aab98860dac796657d5ef5dc317b117 +size 44378 diff --git a/marked/Rel-11/29_series/29010/d5661c3661190c44429a1a75f61d7550_img.jpg b/marked/Rel-11/29_series/29010/d5661c3661190c44429a1a75f61d7550_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0ec4d6828fa6f000e62dc9182ba8a37838cc7c2b --- /dev/null +++ b/marked/Rel-11/29_series/29010/d5661c3661190c44429a1a75f61d7550_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ee0df41efe2f636076df754a405aafb233cf164b5159d1ad462dc4a0e4e0fa04 +size 28871 diff --git a/marked/Rel-11/29_series/29010/da85343976fdbb19f866d9ddbdad0eae_img.jpg b/marked/Rel-11/29_series/29010/da85343976fdbb19f866d9ddbdad0eae_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..abc209ba6905faabf31a9f563c56387bc7155e9e --- /dev/null +++ b/marked/Rel-11/29_series/29010/da85343976fdbb19f866d9ddbdad0eae_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5fdf58c5d108fff28c0f4e1f98e1deb05fbcca5ec82fa2d1df30731266335191 +size 122232 diff --git a/marked/Rel-11/29_series/29010/daa4a6fa7e2ba1954258f86b4928eb32_img.jpg b/marked/Rel-11/29_series/29010/daa4a6fa7e2ba1954258f86b4928eb32_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5c15c04097e34473068a86c0f19ed445c190cecb --- /dev/null +++ b/marked/Rel-11/29_series/29010/daa4a6fa7e2ba1954258f86b4928eb32_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:45662ea75546a908ae50075b45ce6e6c3fce75fe57931b7c7b0944117d97ce4d +size 76941 diff --git a/marked/Rel-11/29_series/29010/db5deafdae53dbc7d5972957f708c691_img.jpg b/marked/Rel-11/29_series/29010/db5deafdae53dbc7d5972957f708c691_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..15194c47bd7df5fc527dd77e9e32b04c94f2404b --- /dev/null +++ b/marked/Rel-11/29_series/29010/db5deafdae53dbc7d5972957f708c691_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:096635d988cb9a15b0b47f8e244dfdf9341133af7bd99038a90af85c247df445 +size 79661 diff --git a/marked/Rel-11/29_series/29010/dbd4bab54b57e8d1abf80e3de6471130_img.jpg b/marked/Rel-11/29_series/29010/dbd4bab54b57e8d1abf80e3de6471130_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c1c943fbde356ac90da41e83cfb28ec5be28ba0f --- /dev/null +++ b/marked/Rel-11/29_series/29010/dbd4bab54b57e8d1abf80e3de6471130_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2a86993b25874261f6e64e450ac5ad79f3e663a19b211ea41153b8dca64375d5 +size 35066 diff --git a/marked/Rel-11/29_series/29010/dd5771673aececa53d42ece89218299d_img.jpg b/marked/Rel-11/29_series/29010/dd5771673aececa53d42ece89218299d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d5e922b6dc05024951dd22f3100cbb755158bb0a --- /dev/null +++ b/marked/Rel-11/29_series/29010/dd5771673aececa53d42ece89218299d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f7d3669d117ad870a4741fdf088cf73be24525d3d9756e777867a521563bffb5 +size 17345 diff --git a/marked/Rel-11/29_series/29010/ddfa5b18550d1a022a941e3c31843814_img.jpg b/marked/Rel-11/29_series/29010/ddfa5b18550d1a022a941e3c31843814_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..49e4176269faca0140b2466ca29d9346869935a3 --- /dev/null +++ b/marked/Rel-11/29_series/29010/ddfa5b18550d1a022a941e3c31843814_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:00992b0d6bb9f91ca432bdb82a0392b71f7c08c523b30fc8f85130d074df64e4 +size 57783 diff --git a/marked/Rel-11/29_series/29010/de63e4b6d8b0aa76b85e1fe3236eac27_img.jpg b/marked/Rel-11/29_series/29010/de63e4b6d8b0aa76b85e1fe3236eac27_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..46547b8613717f8843427b666cb250e8605cb617 --- /dev/null +++ b/marked/Rel-11/29_series/29010/de63e4b6d8b0aa76b85e1fe3236eac27_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ae4c39e7e0f0f35d1450398d0ed241a47bbf41e9716ab3e50ce8705911757ccf +size 156379 diff --git a/marked/Rel-11/29_series/29010/df1966d80c74bc127f159a48f38b13ee_img.jpg b/marked/Rel-11/29_series/29010/df1966d80c74bc127f159a48f38b13ee_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..99f4f8e5c2eb0e7aade0680b1c378b4e9d825290 --- /dev/null +++ b/marked/Rel-11/29_series/29010/df1966d80c74bc127f159a48f38b13ee_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5bf43734a89ef37b4661705911503186104005e1bdad11038208302fd22407b4 +size 73205 diff --git a/marked/Rel-11/29_series/29010/e18841eb4a995df8354a793459e12fd0_img.jpg b/marked/Rel-11/29_series/29010/e18841eb4a995df8354a793459e12fd0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..865d3757db1a34ab8a36195177dcbfd6a9e6ab03 --- /dev/null +++ b/marked/Rel-11/29_series/29010/e18841eb4a995df8354a793459e12fd0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f89747295c4763920442b7ec0a9a4329680124fa99aa1b568e6308a2824e7b09 +size 87296 diff --git a/marked/Rel-11/29_series/29010/e3dd59b6fd27059890be0e0397bdd467_img.jpg b/marked/Rel-11/29_series/29010/e3dd59b6fd27059890be0e0397bdd467_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..94c186606cbd07c8d5a713506d548f4ff77b1275 --- /dev/null +++ b/marked/Rel-11/29_series/29010/e3dd59b6fd27059890be0e0397bdd467_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9511f757ab3b40fe5061530101cecab509ef6693fe94728c55022406183919d1 +size 112140 diff --git a/marked/Rel-11/29_series/29010/e7010c66da16316c2935dfbbef5056b3_img.jpg b/marked/Rel-11/29_series/29010/e7010c66da16316c2935dfbbef5056b3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8d76200a25fc1f8312e45f7fb9ec62f194f7d85a --- /dev/null +++ b/marked/Rel-11/29_series/29010/e7010c66da16316c2935dfbbef5056b3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:34eeae20830400b200a0debcca72b8c4d1b3d5aa3fdc0e0adea63f80076e46b8 +size 39038 diff --git a/marked/Rel-11/29_series/29010/e90b25c8d90cadc3f76c376701cf27ed_img.jpg b/marked/Rel-11/29_series/29010/e90b25c8d90cadc3f76c376701cf27ed_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f47eb264510b3f812369963046bf181690f2524a --- /dev/null +++ b/marked/Rel-11/29_series/29010/e90b25c8d90cadc3f76c376701cf27ed_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cb05fb61ae717730147c47f244996691db62c53a65dcfd172b8557c7e616a709 +size 25266 diff --git a/marked/Rel-11/29_series/29010/e9b43ac020435f8121e8592f31afdc52_img.jpg b/marked/Rel-11/29_series/29010/e9b43ac020435f8121e8592f31afdc52_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ecf1459311896aa8b7af1ac5268d2119c4b465cb --- /dev/null +++ b/marked/Rel-11/29_series/29010/e9b43ac020435f8121e8592f31afdc52_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8b99392d4f0162af1b6a6d87cfd9960a5a5d87fca45e7c73347a68639cd56eee +size 45344 diff --git a/marked/Rel-11/29_series/29010/ea4fd10a9a501c602f2bea0f7f711877_img.jpg b/marked/Rel-11/29_series/29010/ea4fd10a9a501c602f2bea0f7f711877_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e22c15fff426254bb0f38e859bdbd1665effd627 --- /dev/null +++ b/marked/Rel-11/29_series/29010/ea4fd10a9a501c602f2bea0f7f711877_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:15075a1688eabf31bd5d8ae93186f1f4cd44862769b1c6ee6b3024479fd42f10 +size 26391 diff --git a/marked/Rel-11/29_series/29010/ec035e97a11ce40541dec6d88d54c7cb_img.jpg b/marked/Rel-11/29_series/29010/ec035e97a11ce40541dec6d88d54c7cb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1b96256c4301f00f490cbe9417e5e31e005c8837 --- /dev/null +++ b/marked/Rel-11/29_series/29010/ec035e97a11ce40541dec6d88d54c7cb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:36352c50d158f28f2f35570660fe656d74310898554369873bed7a8f370eb8b6 +size 26410 diff --git a/marked/Rel-11/29_series/29010/f0b7aaa539a2f77c98d53ed6c1c2366b_img.jpg b/marked/Rel-11/29_series/29010/f0b7aaa539a2f77c98d53ed6c1c2366b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..45ad107b963de442562ac99be4881776ae76a9a2 --- /dev/null +++ b/marked/Rel-11/29_series/29010/f0b7aaa539a2f77c98d53ed6c1c2366b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:76f19f1aae41d729b074836b010a7b68c0b127c72694d141385f827df65443b8 +size 40713 diff --git a/marked/Rel-11/29_series/29010/f1ba1e68228ebd4c3109371574a723e6_img.jpg b/marked/Rel-11/29_series/29010/f1ba1e68228ebd4c3109371574a723e6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..24d176b82e56f67d62ecc07a55dd64bac3078b33 --- /dev/null +++ b/marked/Rel-11/29_series/29010/f1ba1e68228ebd4c3109371574a723e6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:48baecafa61c71466bfa6595e454d2208f3f6fe372fe976b5d2af5a91941951f +size 130152 diff --git a/marked/Rel-11/29_series/29010/f1de68a4cbb9b92a1c0ffd919bbd199c_img.jpg b/marked/Rel-11/29_series/29010/f1de68a4cbb9b92a1c0ffd919bbd199c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7279d2935843cfeddbb0ca1e8d42a9cf6773afcb --- /dev/null +++ b/marked/Rel-11/29_series/29010/f1de68a4cbb9b92a1c0ffd919bbd199c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4e0eb1e39ef851efb1d0e760ac3bca9f8874362f47e31dc5dafb6bf033f4d07f +size 46310 diff --git a/marked/Rel-11/29_series/29010/f43d225d8fed2845b8d7e5afecbfe636_img.jpg b/marked/Rel-11/29_series/29010/f43d225d8fed2845b8d7e5afecbfe636_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..dd562a517d4f0ebb8858b7687c545384cd8b1caf --- /dev/null +++ b/marked/Rel-11/29_series/29010/f43d225d8fed2845b8d7e5afecbfe636_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:40da7ea18ff21bc5edac6c46d8494dc8d37ba56296fa06d6052fbbcc4bc37f33 +size 48441 diff --git a/marked/Rel-11/29_series/29010/f52f816ab28ff4b4a9d12c6c94fbd41c_img.jpg b/marked/Rel-11/29_series/29010/f52f816ab28ff4b4a9d12c6c94fbd41c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3170a82635297e2744f7994a18a8beb2d52db998 --- /dev/null +++ b/marked/Rel-11/29_series/29010/f52f816ab28ff4b4a9d12c6c94fbd41c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5d6f8671499d1e654a603f528a784c76c978e4b44463b3a99e4fcb5166436516 +size 18212 diff --git a/marked/Rel-11/29_series/29010/fc3e2b49a9f850951570e502393b697f_img.jpg b/marked/Rel-11/29_series/29010/fc3e2b49a9f850951570e502393b697f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6e406816d1fc78b6c3e771cf9667f084fea362b7 --- /dev/null +++ b/marked/Rel-11/29_series/29010/fc3e2b49a9f850951570e502393b697f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:190244defe3bcbefbd8ffee3e8d9af8232123142950d6ecb888e8c4bbeb5c378 +size 85537 diff --git a/marked/Rel-11/29_series/29010/ff0952ef692c9d960ce5f6708bcc9711_img.jpg b/marked/Rel-11/29_series/29010/ff0952ef692c9d960ce5f6708bcc9711_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..82f9f321927b7cc01646fe9c590bd435cbcf1a95 --- /dev/null +++ b/marked/Rel-11/29_series/29010/ff0952ef692c9d960ce5f6708bcc9711_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:297fdd57dcfa875d263b87f4626adac8e3ea5a0dc126ad682678c9da9d665352 +size 36538 diff --git a/marked/Rel-11/29_series/29010/ff5f89b660edddb67971d7d3d4ce87ef_img.jpg b/marked/Rel-11/29_series/29010/ff5f89b660edddb67971d7d3d4ce87ef_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bd59eab12554c437a877a77c8fd466bc1e609173 --- /dev/null +++ b/marked/Rel-11/29_series/29010/ff5f89b660edddb67971d7d3d4ce87ef_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:20817bb2e90da25fd26fd57dbd111800b328cc486bcc4e5563748cbaa3f2d90c +size 29347 diff --git a/marked/Rel-11/29_series/29010/raw.md b/marked/Rel-11/29_series/29010/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..5a71053ec3ce57c06922ee884043648e33cfdada --- /dev/null +++ b/marked/Rel-11/29_series/29010/raw.md @@ -0,0 +1,6203 @@ + + + + +**Error:** + +**2** + +**Error: Reference source not** + +# Contents + +| | | +|-------------------------------------------------------------------------------------------------|----| +| Foreword..... | 6 | +| 1 Scope..... | 7 | +| 1.1 References..... | 7 | +| 1.2 Abbreviations..... | 8 | +| 1.3 Definitions..... | 8 | +| 2 Classification of interworking cases..... | 9 | +| 2.1 Transparent procedures..... | 9 | +| 2.2 Non-transparent procedures..... | 9 | +| 3 Interworking in the MSC, Transparent case..... | 9 | +| 3.1 General..... | 9 | +| 3.2 Routeing area updating..... | 12 | +| 3.3 Authentication..... | 13 | +| 3.4 Retrieval of the IMSI from the MS..... | 14 | +| 3.5 Reallocation of TMSI..... | 15 | +| 3.6 Retrieval of the IMEI from the MS..... | 15 | +| 3.7 Tracing subscriber activity..... | 16 | +| 3.8 Location update..... | 17 | +| 4 Interworking in the MSC, Non-transparent cases..... | 18 | +| 4.1 General..... | 18 | +| 4.2 Outgoing call set-up (MS originating call)..... | 18 | +| 4.3 Incoming call set-up (MS terminating call)..... | 22 | +| 4.4 Cipher mode setting..... | 24 | +| 4.5 Inter-MSC Handover..... | 24 | +| 4.5.1 Basic Inter-MSC Handover..... | 25 | +| 4.5.2 Subsequent Inter-MSC Handover back to MSC-A..... | 30 | +| 4.5.3 Subsequent Inter-MSC Handover to third MSC..... | 34 | +| 4.5.4 BSSAP Messages transfer on E-Interface..... | 37 | +| 4.5.5 Processing in MSC-B, and information transfer on E-interface..... | 38 | +| 4.5.5.1 Encryption Information..... | 39 | +| 4.5.5.2 Channel Type..... | 39 | +| 4.5.5.3 Classmark..... | 40 | +| 4.5.5.4 Downlink DTX-Flag..... | 40 | +| 4.5.5.5 Priority..... | 41 | +| 4.5.5.6 MSC/BSC-Invoke Trace Information Elements..... | 41 | +| 4.5.5.7 LSA Identifier List..... | 41 | +| 4.5.5.8 Selected UMTS Algorithm..... | 41 | +| 4.5.5.9 Allowed UMTS Algorithms..... | 41 | +| 4.5.5.10 BSSMAP Service Handover..... | 42 | +| 4.5.5.11 RANAP Service Handover..... | 42 | +| 4.5.5.12 SNA Access Information..... | 42 | +| 4.5.5.13 UESBI..... | 43 | +| 4.5.5.14 Alternative Channel Type..... | 43 | +| 4.5.5.15 Trace parameters..... | 43 | +| 4.5.6 Overview of the Technical Specifications GSM interworking for the Inter-MSC Handover..... | 43 | +| 4.6 Inter-MSC Handover (UMTS to GSM)..... | 45 | +| 4.6.1 Basic Inter-MSC Handover..... | 45 | +| 4.6.2 Subsequent Inter-MSC Handover from 3G-MSC-B back to MSC-A..... | 50 | +| 4.6.3 Subsequent Inter-MSC Handover to third MSC..... | 54 | +| 4.6.4 BSSAP Messages transfer on E-Interface..... | 58 | +| 4.6.5 Processing in MSC-B, and information transfer on E-interface..... | 58 | +| 4.6.6 Cause Code Mapping..... | 58 | +| 4.7 Inter-MSC Handover (GSM to UMTS)..... | 60 | +| 4.7.1 Basic Inter-MSC Handover..... | 60 | +| 4.7.2 Subsequent Inter-MSC Handover from MSC-B back to 3G_MSC-A..... | 66 | +| 4.7.3 Subsequent Inter-MSC Handover to third MSC..... | 71 | +| 4.7.4 BSSAP Messages transfer on E-Interface..... | 73 | + +| | | | +|----------|----------------------------------------------------------------------------------------------|-----| +| 4.7.4.1 | Assignment..... | 73 | +| 4.7.4.2 | Cipher Mode Control..... | 74 | +| 4.7.4.3 | Location Reporting Control..... | 75 | +| 4.7.5 | Processing in 3G_MSC-B, and information transfer on E-interface..... | 75 | +| 4.7.5.1 | Encryption Information..... | 76 | +| 4.7.5.2 | Channel Type..... | 76 | +| 4.7.5.3 | Classmark..... | 76 | +| 4.7.5.4 | Priority..... | 76 | +| 4.7.5.5 | MSC-Invoke Trace Information Elements..... | 77 | +| 4.7.5.6 | Selected UMTS Algorithm..... | 77 | +| 4.7.5.7 | Allowed UMTS Algorithms..... | 77 | +| 4.7.5.8 | BSSMAP Service Handover..... | 78 | +| 4.7.5.9 | RANAP Service Handover..... | 78 | +| 4.7.5.10 | GERAN Classmark..... | 78 | +| 4.7.5.11 | SNA Access Information..... | 79 | +| 4.7.5.12 | UESBI..... | 79 | +| 4.7.5.13 | Alternative Channel Type..... | 79 | +| 4.7.5.14 | Trace parameters..... | 79 | +| 4.7.6 | Cause Code Mapping..... | 80 | +| 4.8 | Inter-MSC Relocation..... | 83 | +| 4.8.1 | Basic Inter-MSC Relocation..... | 83 | +| 4.8.2 | Subsequent Inter-MSC Relocation back to 3G_MSC-A..... | 88 | +| 4.8.3 | Subsequent Inter-MSC Relocation to third MSC..... | 92 | +| 4.8.4 | RANAP Messages transfer on E-Interface..... | 95 | +| 4.8.5 | Processing in 3G_MSC-B, and information transfer on E-interface..... | 96 | +| 4.8.5.1 | Integrity Protection Information..... | 96 | +| 4.8.5.2 | Encryption Information..... | 97 | +| 4.8.5.3 | RAB Parameters..... | 97 | +| 4.8.5.4 | Channel Type..... | 98 | +| 4.8.5.5 | Selected GSM Algorithm..... | 98 | +| 4.8.5.6 | Allowed GSM Algorithms..... | 98 | +| 4.8.5.7 | Chosen Channel..... | 99 | +| 4.8.5.8 | BSSMAP Service Handover..... | 99 | +| 4.8.5.9 | RANAP Service Handover..... | 99 | +| 4.8.5.10 | GERAN Classmark..... | 99 | +| 4.8.5.11 | SNA Access Information..... | 100 | +| 4.8.5.12 | UESBI..... | 100 | +| 4.8.5.13 | Alternative RAB Parameters Value..... | 100 | +| 4.8.5.14 | Trace parameters..... | 101 | +| 4.8.6 | Overview of the Technical Specifications 3GPP interworking for the Inter-MSC Relocation..... | 101 | +| 4.9 | Location Services..... | 103 | +| 4.9.1 | Completed Location Acquisition..... | 103 | +| 4.9.1.1 | Inter-MSC Handover (GSM to GSM)..... | 103 | +| 4.9.1.2 | Inter-MSC Handover (GSM to UMTS)..... | 104 | +| 4.9.1.3 | Inter-MSC Handover (UMTS to GSM)..... | 106 | +| 4.9.1.4 | Inter-MSC SRNS Relocation..... | 107 | +| 4.9.2 | Cause Code Mapping..... | 110 | +| 4.9.2.1 | Inter-MSC Handover (GSM to GSM)..... | 110 | +| 4.9.2.2 | Inter-MSC Handover (GSM to UMTS)..... | 110 | +| 4.9.2.3 | Inter-MSC Handover (UMTS to GSM)..... | 111 | +| 4.9.2.4 | Inter-MSC SRNS Relocation..... | 111 | +| 4.9.3 | Aborted Location Acquisition..... | 111 | +| 4.9.3.1 | Inter-MSC Handover (GSM to GSM)..... | 111 | +| 4.9.3.2 | Inter-MSC Handover (GSM to UMTS)..... | 112 | +| 4.9.3.3 | Inter-MSC Handover (UMTS to GSM)..... | 114 | +| 4.9.3.4 | Inter-MSC SRNS Relocation..... | 115 | +| 4.9.4 | Request of Assistance Data or De-ciphering Keys: Successful Case..... | 118 | +| 4.9.4.1 | Inter-MSC Handover (GSM to GSM)..... | 118 | +| 4.9.4.2 | Inter-MSC Handover (GSM to UMTS)..... | 119 | +| 4.9.4.3 | Inter-MSC Handover (UMTS to GSM)..... | 122 | +| 4.9.4.4 | Inter-MSC SRNS Relocation..... | 123 | + +| | | | +|------------------------|-------------------------------------------------------------------------------|-----| +| 4.9.5 | Request of Assistance Data or De-ciphering Keys: Failure Case..... | 127 | +| 4.9.5.1 | Inter-MSC Handover (GSM to GSM)..... | 127 | +| 4.9.5.2 | Inter-MSC Handover (GSM to UMTS)..... | 128 | +| 4.9.5.3 | Inter-MSC Handover (UMTS to GSM)..... | 129 | +| 4.9.5.4 | Inter-MSC SRNS Relocation..... | 130 | +| 4.9.6 | Abort of Request of Assistance Data or De-ciphering Keys:..... | 132 | +| 4.9.6.1 | Inter-MSC Handover (GSM to GSM)..... | 132 | +| 4.9.6.2 | Inter-MSC Handover (GSM to UMTS)..... | 134 | +| 4.9.6.3 | Inter-MSC Handover (UMTS to GSM)..... | 135 | +| 4.9.6.4 | Inter-MSC SRNS Relocation..... | 135 | +| 4.10 | Single Radio Voice Call Continuity (SRVCC)..... | 135 | +| 4.10.1 | General..... | 135 | +| 4.10.2 | SRVCC Handover from UTRAN (HSPA) to GERAN..... | 135 | +| 4.10.3 | SRVCC Handover from UTRAN (HSPA) to UTRAN..... | 135 | +| 4.10.4 | SRVCC Handover from E-UTRAN to GERAN..... | 135 | +| 4.10.5 | SRVCC Handover from E-UTRAN to UTRAN..... | 135 | +| 5 | Interworking in the MME..... | 136 | +| 5.1 | General..... | 136 | +| 5.2 | Void..... | 136 | +| 5.3 | Interworking between RANAP protocol messages and SIAP protocol messages..... | 136 | +| 5.4 | Interworking between BSSGP protocol messages and SIAP protocol messages..... | 137 | +| 6 | Interworking in the S4-SGSN..... | 139 | +| 6.1 | General..... | 139 | +| 6.2 | Interworking between RANAP protocol messages and SIAP protocol messages..... | 139 | +| 6.3 | Interworking between BSSGP protocol messages and SIAP protocol messages..... | 140 | +| 6.4 | Interworking between BSSGP protocol messages and RANAP protocol messages..... | 141 | +| Annex A (informative): | Change history..... | 143 | + +# --- Foreword + +This Technical Specification (TS) has been produced by the 3rd Generation Partnership Project (3GPP). + +The present document specifies Information element mapping between Mobile Station - Base Station System (MS - BSS) and Base Station System - Mobile-services Switching Centre (BSS - MSC) Signalling procedures and the Mobile Application Part (MAP) within the digital cellular telecommunications system. + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +# 1 Scope + +The scope of the present document is: + +- i) to provide a detailed specification for the interworking between information elements contained in layer 3 messages sent on the MS- MSC interface (Call Control and Mobility Management parts of 3GPP TS 24.008 [4]) and parameters contained in MAP services sent over the MSC-VLR interface (3GPP TS 29.002 [9]) where the MSC acts as a transparent relay of information; +- ii) to provide a detailed specification for the interworking between information elements contained in BSSMAP messages sent on the BSC- MSC interface (3GPP TS 48.008 [12]) and parameters contained in MAP services sent over the MSC-VLR interface (3GPP TS 29.002 [9]) where the MSC acts as a transparent relay of information; +- iii) to provide a detailed specification for the interworking between information elements contained in BSSMAP messages (3GPP TS 48.008 [12]) and RANAP ((3GPP TS 25.413 [7])); +- iv) to provide a detailed specification for the interworking as in i) and ii) above when the MSC also processes the information; +- v) to provide a detailed specification for the interworking between information elements contained in layer 3 messages sent on the MS-SGSN interface (GPRS mobility part of 3GPP TS 24.008 [4]) and parameters contained in MAP services sent over the SGSN-HLR interface (3GPP TS 29.002 [9]); +- vi) to provide a detailed specification for the interworking between information elements contained in RANAP messages sent on the SGSN-RNC interface (3GPP TS 25.413 [7]) and parameters contained in SIAP messages sent on the MME-eNodeB interface (3GPP TS 36.413 [21]); +- vii) to provide a detailed specification for the interworking between information elements contained in BSSMAP messages (3GPP TS 48.008 [12]) or RANAP messages (3GPP TS 25.413 [7]) during SRVCC handovers. + +Interworking for supplementary services is given in 3GPP TS 29.011 [11]. Interworking for the short message service is given in 3GPP TS 23.040 [3] and 3GPP TS 24.011. Interworking between the call control signalling of 3GPP TS 24.008 [4] and the PSTN/ISDN is given in GSM 09.03 [13], 3GPP TS 29.007 [10] and 3GPP TS 49.008 [14] [14]. Interworking between the 'A' and 'E' interfaces for inter-MSC handover signalling is given in 3GPP TS 29.007 [10] and 3GPP TS 49.008 [14] [14]. + +## 1.1 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. +- For a specific reference, subsequent revisions do not apply. +- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. + +- [1] 3GPP TS 21.905: "3G Vocabulary". +- [2] 3GPP TS 23.009: "Handover procedures". +- [3] 3GPP TS 23.040: "Technical realization of the Short Message Service (SMS) Point to Point (PP)". +- [4] 3GPP TS 24.008: "Mobile Radio Interface Layer 3 specification; Core Network Protocols-Stage 3". +- [5] 3GPP TS 24.010: "Mobile radio interface layer 3 Supplementary services specification - General aspects". + +- [6] 3GPP TS 24.011: "Point-to-Point (PP) Short Message Service (SMS) support on mobile radio interface". +- [7] 3GPP TS 25.413: "Iu interface RANAP signalling". +- [8] 3GPP TS 27.001: " General on Terminal Adaptation Functions (TAF) for Mobile Stations (MS)". +- [9] 3GPP TS 29.002: "Mobile Application Part (MAP) specification". +- [10] 3GPP TS 29.007: "General requirements on interworking between the Public Land Mobile Network (PLMN) and the Integrated Services Digital Network (ISDN) or Public Switched Telephone Network (PSTN)". +- [11] 3GPP TS 29.011: "Digital cellular telecommunications system (Phase 2+); Signalling interworking for supplementary services". +- [12] 3GPP TS 48.008: " Mobile Switching Centre - Base Station System (MSC - BSS) interface Layer 3 specification". +- [13] GSM 09.03: "Digital cellular telecommunications system (Phase 2+); Signalling requirements on interworking between the Integrated Services Digital Network (ISDN) or Public Switched Telephone Network (PSTN) and the Public Land Mobile Network (PLMN)". +- [14] 3GPP TS 49.008 [14]: "Digital cellular telecommunications system (Phase 2+); Application of the Base Station System Application Part (BSSAP) on the E-interface". +- [15] 3GPP TS 29.108: "Application of the Radio Access Network Application Part (RANAP) on the E-interface" +- [16] 3GPP TS 23.271: "Functional stage 2 description of LCS" +- [17] 3GPP TS 43.051: "Technical Specification Group GSM/EDGE; Radio Access Network; Overall description - Stage 2". +- [18] 3GPP TS 23.012: "Location management procedures". +- [19] Void. +- [20] 3GPP TS 24.301: "Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS)". +- [21] 3GPP TS 36.413: "Evolved Universal Terrestrial Radio Access Network E-UTRAN; S1 Application Protocol (S1AP)". +- [22] 3GPP TS 23.401: " General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ". +- [23] 3GPP TS 29.060: "GPRS Tunnelling Protocol (GTP) across the Gn and Gp interface". +- [24] 3GPP TS 48.018: " Base Station System (BSS) -Serving GPRS Support Node (SGSN); BSS GPRS Protocol (BSSGP)". +- [25] 3GPP TS 29.280: "3GPP EPS Sv interface (MME to MSC) for SRVCC". + +## 1.2 Abbreviations + +Abbreviations used in the present document are listed in 3GPP TS 21.905 [1]. + +## 1.3 Definitions + +The following terms are used in this Technical Specification: + +**A/Gb mode:** mode of operation of the MS when connected to the Core Network via GERAN and the A and/or Gb interfaces. Throughout this specification the term GSM refers to GERAN A/Gb mode. + +**Iu mode:** mode of operation of the MS when connected to the Core Network via GERAN or UTRAN and the Iu interface. Throughout this specification the term UMTS refers to UTRAN or GERAN Iu mode. + +# --- 2 Classification of interworking cases + +## 2.1 Transparent procedures + +The following MSC procedures require transparent mapping of access protocol information elements into MAP parameters and vice versa (see 3GPP TS 29.002 [9] for definitions and the use of the procedures): + +- location update; +- forward new TMSI; +- provide IMSI; +- obtain IMEI; +- check IMEI; +- authenticate; +- trace subscriber activity. + +## 2.2 Non-transparent procedures + +Procedures in this class require processing in the MSC and information element mapping. These procedures include those related to: + +- outgoing call set-up; +- incoming call set-up; +- handover; +- cipher mode setting; +- location services. + +# --- 3 Interworking in the MSC, Transparent case + +## 3.1 General + +When the MSC receives a forward message from the BSS (possibly forwarded transparently from the MS), it will invoke the desired MAP service and establish a cross reference between the BSSAP procedure and the MAP procedure in order to return the result of the operation to the BSS (which may forward it transparently to the MS. The cross reference is deleted when the MSC terminates the MAP procedure. + +Positive or negative results of the MAP procedure are returned in the appropriate BSSAP message. + +The parameters of the forward BSSAP message are mapped by a one-to-one mapping into the parameters of the MAP service. However, in some cases parameters received on the radio path may be suppressed at the MSC because they are related to another protocol entity, e.g. information related to RR-management may be included in MM-management messages. Similarly, parameters received in the (positive) MAP service response are mapped one-to-one into parameters of the corresponding backward BSSAP message. + +A negative outcome, as carried in various MAP services (MAP specific service response, MAP\_U\_ABORT, MAP\_P\_ABORT, MAP\_NOTICE and premature MAP\_CLOSE, see 3GPP TS 29.002 [9] for definitions) is mapped into a cause value in the required backward BSSAP message. In this case several negative results of MAP may be mapped into the same BSSAP cause value, i.e. without discrimination between these negative results. + +NOTE: For O & M purposes, the MAP procedure entity in the MSC may require a more detailed overview of negative results than the MS. + +These principles are illustrated in figure 1. + +![Figure 1: Illustration of mapping principles in the MSC. The diagram shows three examples of message mapping between 24.008 (48.008) and MAP service messages. 1. Forward message: A 24.008 (48.008) forward message containing an information element is mapped one-to-one to a MAP service request containing a parameter. 2. Positive ack: A 24.008 (48.008) positive ack containing an information element is mapped one-to-one to a MAP service response containing a parameter. 3. Negative cause: A 24.008 (48.008) negative cause containing a cause is mapped one-to-one or many-to-one to a negative response containing a cause.](daa4a6fa7e2ba1954258f86b4928eb32_img.jpg) + +``` + +24.008 (48.008) MAP service +forward message request +-----> -----> ++-----+ +-----+ +|information element| |parameter| ++-----+ +-----+ + +----->-----> + one-to-one + mapping + +positive ack MAP service +-----< response ++-----+ +-----+ +|information element| |parameter| ++-----+ +-----+ + +-----<-----< + one-to-one + mapping + +negative cause negative +-----< response ++-----+ +-----+ +| cause | | cause | ++-----+ +-----+ + +-----<-----< + one-to-one or many-to-one + mapping + +``` + +Figure 1: Illustration of mapping principles in the MSC. The diagram shows three examples of message mapping between 24.008 (48.008) and MAP service messages. 1. Forward message: A 24.008 (48.008) forward message containing an information element is mapped one-to-one to a MAP service request containing a parameter. 2. Positive ack: A 24.008 (48.008) positive ack containing an information element is mapped one-to-one to a MAP service response containing a parameter. 3. Negative cause: A 24.008 (48.008) negative cause containing a cause is mapped one-to-one or many-to-one to a negative response containing a cause. + +**Figure 1: Illustration of mapping principles in the MSC** + +For each of the transparent operations listed in subclause 2.1, the following format is used to show the mapping. + +| | 24.008 or 48.008 | 29.002 | Notes | +|-----------------|--------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------|-------| +| Forward message | MS/BSS to MSC
message name
information element 1 <--->
information element 2 <---> | MSC to VLR
MAP service request
parameter 1 <--->
parameter 2 <---> | | +| Positive result | MSC to MS/BSS
message name
information element 1 <--->
information element 2 <---> | VLR to MSC
positive response
parameter 1 <--->
parameter 2 <---> | | +| Negative result | MSC to MS/BSS
message name
cause 1 <--->
cause 2 <--->
cause 3 <--->
cause 3 <--->
cause 3 <---> | VLR to MSC
negative response
cause 1 <--->
cause 2 <--->
MAP U/P ABORT <--->
MAP NOTICE <--->
MAP CLOSE <---> | | + +Equivalent mapping principles apply for operations invoked by the VLR towards the BSS/MS. However, negative results are generally not received from the BSS/MS but are generated in the MSC. Therefore, for such operations the interworking for negative results is not normally shown. + +## 3.2 Routeing area updating + +| | 24.008 | 29.002 | Notes | +|------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------| +| Forward message | GMM (ROUTEING AREA UPDATE REQUEST)
MS classmark 1
MS classmark 4
GPRS Ciphering key seq number
Mobile station identity
Old routeing area identification | MAP UPDATE GPRS LOCATION-request -
-
-
IMSI
- | | +| Positive results | GMM (ROUTEING AREA UPDATE ACCEPT)
Routeing area identification
Mobile station identity
C Mobile station
C Reject: IMSI unknown in HLR
C Reject: MSC temporarily not reachable | MAP UPDATE GPRS LOCATION-response
-
-
-
- | 1
2
3
4 | +| Negative results | GMM (ROUTEING AREA UPDATE REJECT)
Network failure
GPRS services not allowed in this PLMN
GPRS services not allowed
GPRS services and non GPRS services not allowed
C GPRS services not allowed
C GPRS services and non-GPRS services not allowed
MS identity cannot be derived by the network
GPRS services not allowed in this PLMN
LA not allowed
Roaming not allowed in this LA
No Suitable cells in location area
GPRS services not allowed in this PLMN
GPRS services not allowed in this PLMN
C GPRS services not allowed in this PLMN
No Suitable cells in location area
Illegal MS
Illegal ME
Network failure
Network failure
Network failure
Network failure | Unknown HLR
Unknown subscriber (no GPRS subscription)
Unknown subscriber (IMSI unknown)
Unknown subscriber (no GPRS subscription)
Unknown subscriber (IMSI unknown)
-
Roaming not allowed: PLMN not allowed
-
-
-
Operator determined barring
-
-
Additional roaming not allowed: Supported RAT Types not allowed
-
-
System Failure
Unexpected data value
MAP U/P ABORT
MAP_NOTICE | 5
6
7
8
9
10
11
12
12
12
13 | + +![Diagram showing a sequence of events: Network failure and MAP_CLOSE, separated by a dashed line with vertical end caps.](27b06ec9f42b5d727a2630f61a5f1861_img.jpg) + +----- | Network failure                      MAP\_CLOSE                      | ----- + +Diagram showing a sequence of events: Network failure and MAP\_CLOSE, separated by a dashed line with vertical end caps. + +- NOTE 1: The mobile station identity is inserted by the SGSN if the SGSN wants to deallocate or re-allocate a P-TMSI. If the SGSN wants to deallocate the P-TMSI it shall include the IMSI. If the SGSN wants to re-allocate the P-TMSI it shall include the new P-TMSI. If a P-TMSI is included, the MS shall respond with a ROUTING AREA UPDATE COMPLETE message. +- NOTE 2: The mobile station identity is inserted by the SGSN if it is received in a BSSAP+ LOCATION UPDATE ACCEPT message from the VLR. If a TMSI is included, the MS shall respond with a ROUTING AREA UPDATE COMPLETE message. Only used in the Combined Routing and Location Area procedure. +- NOTE 3: This reject cause is inserted on the positive response by the SGSN if the SGSN receives a BSSAP+ LOCATION UPDATE REJECT message from the VLR indicating in the reject cause IMSI unknown in HLR. Only used in the Combined Routing and Location Area procedure. +- NOTE 4: This reject cause is inserted on the positive response by the SGSN if the SGSN does not receive any response from the VLR to a previous BSSAP+ LOCATION UPDATE REQUEST message. Only used in the Combined Routing and Location Area procedure. +- NOTE 5: The Unknown RA error is only generated as a result of incorrect information being inserted by the BSS. +- NOTE 6: The HLR shall send Unknown subscriber with diagnostic value No GPRS subscription if the HLR indicates that there is an error in the type of subscription (i.e. SGSN requests service for a non-GPRS only subscriber). The HLR may also send this error in the MAP SEND AUTHENTICATION INFO RESPONSE message. +- NOTE 7: The HLR shall send Unknown subscriber with diagnostic value IMSI unknown if the HLR indicates that the IMSI provided by the SGSN is unknown. +- NOTE 8: The HLR shall send Unknown subscriber with diagnostic value No GPRS subscription if the HLR indicates that there is an error in the type of subscription (i.e. SGSN requests service for a non-GPRS only subscriber). Used in the Combined Routing and Location Area procedure. The HLR may also send this error in the MAP SEND AUTHENTICATION INFO RESPONSE message. +- NOTE 9: This reject cause is inserted if the SGSN receives a MAP GPRS UPDATE LOCATION negative response message indicating IMSI unknown. Used in the Combined Routing and Location Area procedure. +- NOTE 10: This reject cause is inserted if the SGSN does not receive any response from the old SGSN to a previous SGSN CONTEXT REQUEST message. +- NOTE 11: The "No Suitable cells in location area" error is generated when the MS has access to only part of the PLMN e.g. due to Administrative Restriction of Subscribers' Access, but where there may also be suitable location areas available. The MS retries on another location area. The recommended cause due to Administrative Restriction of Subscriber's Access is "No Suitable Cells in Location Area", but cause "Roaming Not Allowed in this LA" may also be used, based on operator configuration. +- NOTE 12: This reject cause is inserted if the SGSN receives in MAP INSERT SUBSCRIBER DATA message an indication of Roaming restricted in SGSN due to unsupported feature. +- NOTE 13: Other reject causes than "no Suitable cells in location area" can be used (e.g. "Roaming not allowed in this location area"). +- NOTE 14: The cause "LA not allowed" shall be sent only if the HLR indicates that due to subscription to a "regionally restricted service" the MS is not allowed to operate in the location area. + +## 3.3 Authentication + +The message flow for the authentication procedure is shown in figure 2. + +![Sequence diagram of the authentication operation between MS, MSC, and VLR. The MSC sends an AUTHENTICATION REQUEST to the MS. The MS responds with an AUTHENTICATION RESPONSE. The MSC then sends a MAP_AUTHENTICATE request to the VLR. The VLR responds with a MAP_AUTHENTICATE response or a MAP_U/P_ABORT message.](ff0952ef692c9d960ce5f6708bcc9711_img.jpg) + +``` + +sequenceDiagram + participant MS + participant MSC + participant VLR + Note left of MSC: AUTHENTICATION REQUEST + MSC->>MS: AUTHENTICATION REQUEST + Note right of MS: AUTHENTICATION RESPONSE + MS->>MSC: AUTHENTICATION RESPONSE + Note left of MSC: MAP_AUTHENTICATE request + MSC->>VLR: MAP_AUTHENTICATE request + Note right of VLR: MAP_AUTHENTICATE response or MAP_U/P_ABORT + VLR->>MSC: MAP_AUTHENTICATE response or MAP_U/P_ABORT + +``` + +Sequence diagram of the authentication operation between MS, MSC, and VLR. The MSC sends an AUTHENTICATION REQUEST to the MS. The MS responds with an AUTHENTICATION RESPONSE. The MSC then sends a MAP\_AUTHENTICATE request to the VLR. The VLR responds with a MAP\_AUTHENTICATE response or a MAP\_U/P\_ABORT message. + +Figure 2: Authentication operation + +The MSC can only act on a MAP\_AUTHENTICATE request if an RR connection exists with the MS. If such a connection does not exist, the MSC shall terminate the MAP procedure with a MAP\_U\_ABORT. The same applies if the MS does not respond to an AUTHENTICATION REQUEST message. + +| | 24.008 | 29.002 | Notes | +|-----------------|------------------------------------------------------------|------------------------------------------|-------| +| Forward message | AUTHENTICATION REQUEST
RAND
Ciphering key seq number | MAP_AUTHENTICATE request
RAND
CKSN | | +| Backward result | AUTHENTICATION REQUEST
SRES | MAP_AUTHENTICATE response
SRES | | + +If the SRES parameter does not match the value stored in the VLR, then the ongoing MAP procedure shall be terminated with a cause 'illegal subscriber'. This shall cause the MSC to send an AUTHENTICATION REJECT message. + +## 3.4 Retrieval of the IMSI from the MS + +The VLR may request open identification of an MS with a MAP\_PROVIDE\_IMSI request. + +The mapping of information elements is as follows: + +| | 24.008 | 29.002 | Notes | +|-----------------|------------------------------------------------|---------------------------|-------| +| Forward message | IDENTITY REQUEST
Identity type set to: IMSI | MAP_PROVIDE_IMSI request | 1 | +| Backward result | IDENTITY RESPONSE
Mobile Identity (IMSI) | MAP_PROVIDE_IMSI response | | + +NOTE 1: The INVOKE does not carry any parameters. The identity type is inferred from the invoke name. + +The MSC shall return a MAP\_PROVIDE\_IMSI response with user error "absent subscriber" if: + +- there is no RR connection with the MS when the MAP service request is received; +- there is no response from the MS. + +## 3.5 Reallocation of TMSI + +This operation is invoked by the VLR. The MAP\_FORWARD\_NEW\_TMSI request contains the new TMSI which is forwarded to the MS in the TMSI REALLOCATION COMMAND. When the MS acknowledges the receipt of the new TMSI, the MSC will return a MAP\_FORWARD\_NEW\_TMSI response to the VLR. + +If there is no radio connection to the MS when the MSC receives the MAP service request, the MSC shall ignore the message. + +| | 24.008 | 29.002 | Notes | +|-----------------|------------------------------------------------------------------------------|-------------------------------------------|-------| +| Forward message | TMSI REALLOCATION COMMAND
Mobile identity
Location area identification | MAP_FORWARD_NEW_TMSI request
TMSI
- | | +| Backward result | TMSI REALLOCATION COMPLETE | MAP_FORWARD_NEW_TMSI response | | + +## 3.6 Retrieval of the IMEI from the MS + +The VLR may use the MAP\_OBTAIN\_IMEI service to request the MS to supply its IMEI, or may use the MAP\_CHECK\_IMEI service to request the MSC to check the MS's IMEI. For either MAP service the BSSAP signalling is the same. + +The mapping of information elements is as follows: + +| | 24.008 | 29.002 | Notes | +|-----------------|----------------------------------------------------|---------------------------------------------------------------------|---------------| +| Forward message | IDENTITY REQUEST
Identity type
set to: IMEI | (MAP_CHECK_IMEI request
or
(MAP_OBTAIN_IMEI request |

1 | +| Backward result | IDENTITY RESPONSE

Mobile Identity
(IMEI) | (MAP_CHECK_IMEI response
or
(MAP_OBTAIN_IMEI response
IMEI |


2 | + +NOTE 1: The MAP service request does not carry any parameters. The identity type is inferred from the service name. + +NOTE 2: If the MAP\_CHECK\_IMEI service was used, the MSC also returns the equipment status to the VLR in the MAP\_CHECK\_IMEI response, after a successful dialogue with the EIR using the IMEI received from the MS. + +The MSC shall terminate the MAP dialogue with the VLR using a MAP\_U\_ABORT if: + +- there is no RR connection with the MS when the MAP service request is received; +- there is no response from the MS. + +NOTE: The MSC can also obtain the IMEI from a phase 2 MS by including appropriate information in the BSSMAP Cipher Mode Command. + +## 3.7 Tracing subscriber activity + +The VLR may request the MSC and/or BSS to record data about the current transaction with an MS. + +| | 48.008 | 29.002 | Notes | +|-----------------|--------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------|-------| +| Forward message | MSC INVOKE TRACE
Trace type
TriggerId
Trace reference
TransactionId
Mobile identity(IMSI)
Mobile identity(IMEI)
OMCId | MAP TRACE SUBSCRIBER
ACTIVITY request _
Trace type
Trace reference
IMSI
IMEI
OMCId | | +| Backward result | none | none | | + +NOTE 1: The VLR may provide either an IMSI or IMEI, but not both. + +## 3.8 Location update + +| | 24.008 | 29.002 | Notes | +|------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------| +| Forward message | MM (LOCATION UPDATING
REQUEST)
Location area id
Mobile identity
Mobile station
classmark 1
Mobile station
classmark 2
Ciphering key
seq number
Location update
type | MAP_UPDATE LOCATION_
request _
IMSI
- | | +| Positive results | MM (LOCATION
UPDATING ACCEPT)
Location area identity
Mobile identity
Follow on proceed | MAP_UPDATE LOCATION
response
- | | +| Negative results | MM (LOCATION
UPDATING REJECT)
IMSI unknown in HLR
PLMN not allowed
LA not allowed
Roaming not
allowed in this LA
No Suitable cells in
location area
PLMN not allowed

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

BSSMAP information elements | SUBSEQUENT HANDOVER request

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

equipment failure
equipment failure

equipment failure
equipment failure

CLEAR COMMAND

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

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

RANAP information elements:

MS Classmark 2
Source Id
Target Id
Cause
MS Classmark 3 | MAP PREPARE

SUBSEQUENT HANDOVER request

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

BSSMAP information elements:

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

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

RANAP information elements:
L3 information | MAP PREPARE

SUBSEQUENT HANDOVER response
-AN-APDU(
QUEUING INDICATION
or HANDOVER REQUEST
ACKNOWLEDGE or
HANDOVER FAILURE)

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

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

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

Iu RELEASE COMMAND

Relocation Cancelled MAP CLOSE
Relocation Cancelled MAP U/P -ABORT | MAP PREPARE SUBSEQUENT HANDOVER response | 3 | + +NOTE 1: The mapping of cause code values between BSSMAP and RANAP is FFS. + +NOTE 2: The response to the Prepare-Subsequent-Handover request can include in its AN-APDU parameter, identifying the 3GPP TS 48.006 protocol, a BSSMAP QUEUING INDICATION, or a BSSMAP HANDOVER REQUEST ACKNOWLEDGE or a BSSMAP HANDOVER FAILURE. + +In the first case, 3G-MSC-B shall wait for the radio resources allocation response from MSC-A, transmitted to 3G-MSC-B as described in subclause 4.5.4. + +In the second case, the positive result triggers in 3G-MSC-B the sending on Iu-Interface of the RELOCATION COMMAND. + +In the third case, the positive result triggers in 3G-MSC-B the sending of the RELOCATION PREPARATION FAILURE. + +NOTE 3: The possible sending of the RELOCATION PREPARATION FAILURE message is described in 3GPP TS 25.413 [7]. + +The interworking between Send End Signal Result and HANDOVER COMPLETE in MSC-A is as follows: + +| | 48.008 | 29.002 | Notes | +|-----------------|-------------------|------------------------------|-------| +| Forward message | HANDOVER COMPLETE | MAP SEND END SIGNAL response | | +| Positive result | | | | +| Negative result | | MAP U/P -ABORT | 1 | + +NOTE: The abortion of the dialogue ends the handover procedure with 3G-MSC-B. + +### 4.6.3 Subsequent Inter-MSC Handover to third MSC + +When a Mobile Station is being handed over to a third MSC, the procedure (described in 3GPP TS 23.009 [2]) does require one specific interworking case in MSC-A between E-Interface from 3G-MSC-B and E-Interface from MSC-B' other than the combination of the ones described in subclauses 4.6.1 and 4.6.2. + +![Sequence diagram for Subsequent Inter-MSC Handover to third MSC (MSC-B') initiation. The diagram shows four lifelines: RNS-A, 3G-MSC-B, MSC-A, and MSC-B'. The sequence starts with RNS-A sending a RELOCATION REQUIRED message to 3G-MSC-B. 3G-MSC-B then sends a MAP PREPARE SUBSEQUENT HANDOVER request to MSC-A. MSC-A sends a MAP PREPARE HANDOVER request to MSC-B'. MSC-B' contains a sub-diagram showing internal components: Possib. Alloc. of ho. number VLR-B and BSS-B', with a HANDOVER REQUEST message being processed within it.](ddfa5b18550d1a022a941e3c31843814_img.jpg) + +``` + +sequenceDiagram + participant RNS-A + participant 3G-MSC-B + participant MSC-A + participant MSC-B' + Note right of MSC-B': Possib. Alloc. of ho. number VLR-B + Note right of MSC-B': BSS-B' + RNS-A->>3G-MSC-B: RELOCATION REQUIRED + 3G-MSC-B->>MSC-A: MAP PREPARE SUBSEQUENT HANDOVER request + MSC-A->>MSC-B': MAP PREPARE HANDOVER request + Note right of MSC-B': HANDOVER REQUEST + +``` + +Sequence diagram for Subsequent Inter-MSC Handover to third MSC (MSC-B') initiation. The diagram shows four lifelines: RNS-A, 3G-MSC-B, MSC-A, and MSC-B'. The sequence starts with RNS-A sending a RELOCATION REQUIRED message to 3G-MSC-B. 3G-MSC-B then sends a MAP PREPARE SUBSEQUENT HANDOVER request to MSC-A. MSC-A sends a MAP PREPARE HANDOVER request to MSC-B'. MSC-B' contains a sub-diagram showing internal components: Possib. Alloc. of ho. number VLR-B and BSS-B', with a HANDOVER REQUEST message being processed within it. + +Figure 32: Signalling for Subsequent Inter-MSC Handover to third MSC (MSC-B') initiation + +Possible Positive outcomes: + +- successful radio resources allocation: + +Error: + +53 + +Error: Reference source not + +![Sequence diagram for inter-MSC handover with an error condition. Lifelines: RNS-A, 3G-MSC-B, MSC-A, MSC-B', BSS-B'. The sequence starts with a RELOCATION COMMAND from RNS-A to 3G-MSC-B. 3G-MSC-B sends a MAP PREPARE SUBSEQUENT HANDOVER response to MSC-A. MSC-A sends a MAP PREPARE HANDOVER response to MSC-B'. MSC-B' sends a HANDOVER REQUEST to BSS-B'. BSS-B' responds with HANDOVER ACKNOWLEDGE to MSC-B'. Finally, MSC-B' sends a RELOCATION COMMAND to RNS-A.](a0e8fe7862a6d7341faf5dac275277cc_img.jpg) + +``` + +sequenceDiagram + participant RNS-A + participant 3G-MSC-B + participant MSC-A + participant MSC-B' + participant BSS-B' + Note right of MSC-B': Error: Reference source not + RNS-A->>3G-MSC-B: RELOCATION COMMAND + 3G-MSC-B-->>MSC-A: MAP PREPARE SUBSEQUENT HANDOVER response + MSC-A-->>MSC-B': MAP PREPARE HANDOVER response + MSC-B'->>BSS-B': HANDOVER REQUEST + BSS-B'-->>MSC-B': HANDOVER ACKNOWLEDGE + MSC-B'-->>RNS-A: RELOCATION COMMAND + +``` + +Sequence diagram for inter-MSC handover with an error condition. Lifelines: RNS-A, 3G-MSC-B, MSC-A, MSC-B', BSS-B'. The sequence starts with a RELOCATION COMMAND from RNS-A to 3G-MSC-B. 3G-MSC-B sends a MAP PREPARE SUBSEQUENT HANDOVER response to MSC-A. MSC-A sends a MAP PREPARE HANDOVER response to MSC-B'. MSC-B' sends a HANDOVER REQUEST to BSS-B'. BSS-B' responds with HANDOVER ACKNOWLEDGE to MSC-B'. Finally, MSC-B' sends a RELOCATION COMMAND to RNS-A. + +b) radio resources allocation queued and successful handover number allocation, if performed. Later successful radio resources allocation indication: + +![Sequence diagram for inter-MSC handover with radio resource queuing. Lifelines: RNS-A, 3G-MSC-B, MSC-A, MSC-B', BSS-B'. The sequence starts with a RELOCATION COMMAND from RNS-A to 3G-MSC-B. 3G-MSC-B sends a MAP PREPARE SUBSEQUENT HANDOVER response to MSC-A. MSC-A sends a MAP PREPARE HANDOVER response to MSC-B'. MSC-B' sends a QUEUING INDICAT. to BSS-B'. MSC-B' then sends a HANDOVER REQUEST to BSS-B'. BSS-B' responds with HANDOVER ACKNOWLEDGE to MSC-B'. MSC-B' sends a MAP PROCESS ACCESS SIGNALLING request to MSC-A. MSC-A sends a MAP FORWARD ACCESS SIGNALLING request to 3G-MSC-B. Finally, 3G-MSC-B sends a RELOCATION COMMAND to RNS-A.](df1966d80c74bc127f159a48f38b13ee_img.jpg) + +``` + +sequenceDiagram + participant RNS-A + participant 3G-MSC-B + participant MSC-A + participant MSC-B' + participant BSS-B' + RNS-A->>3G-MSC-B: RELOCATION COMMAND + 3G-MSC-B-->>MSC-A: MAP PREPARE SUBSEQUENT HANDOVER response + MSC-A-->>MSC-B': MAP PREPARE HANDOVER response + MSC-B'-->>BSS-B': QUEUING INDICAT. + MSC-B'->>BSS-B': HANDOVER REQUEST + BSS-B'-->>MSC-B': HANDOVER ACKNOWLEDGE + MSC-B'-->>MSC-A: MAP PROCESS ACCESS SIGNALLING request + MSC-A-->>3G-MSC-B: MAP FORWARD ACCESS SIGNALLING request + 3G-MSC-B-->>RNS-A: RELOCATION COMMAND + +``` + +Sequence diagram for inter-MSC handover with radio resource queuing. Lifelines: RNS-A, 3G-MSC-B, MSC-A, MSC-B', BSS-B'. The sequence starts with a RELOCATION COMMAND from RNS-A to 3G-MSC-B. 3G-MSC-B sends a MAP PREPARE SUBSEQUENT HANDOVER response to MSC-A. MSC-A sends a MAP PREPARE HANDOVER response to MSC-B'. MSC-B' sends a QUEUING INDICAT. to BSS-B'. MSC-B' then sends a HANDOVER REQUEST to BSS-B'. BSS-B' responds with HANDOVER ACKNOWLEDGE to MSC-B'. MSC-B' sends a MAP PROCESS ACCESS SIGNALLING request to MSC-A. MSC-A sends a MAP FORWARD ACCESS SIGNALLING request to 3G-MSC-B. Finally, 3G-MSC-B sends a RELOCATION COMMAND to RNS-A. + +Figure 33: Signalling for Subsequent Inter-MSC Handover to third MSC (MSC-B') execution (Positive outcome) + +Possible Negative outcomes: + +c) user error detected, or component rejection or dialogue abortion performed by MSC-B': + +![](0a73b03fba21af142d619a9a662e6490_img.jpg) + +``` + +sequenceDiagram + participant RNS-A + participant 3G-MSC-B + participant MSC-A + participant MSC-B' + participant BSS-B' + + MSC-A->>MSC-B': MAP PREPARE HANDOVER + MSC-B'-->>MSC-A: response negative result + MSC-A-->>MSC-B': MAP CLOSE + MSC-A->>MSC-B': MAP U/P -ABORT + 3G-MSC-B->>MSC-A: MAP PREPARE SUBSEQUENT + MSC-A-->>3G-MSC-B: HANDOVER response negative result + 3G-MSC-B-->>RNS-A: RELOCATION PREPARATION FAILURE (Note 1) + +``` + +d) radio resources allocation failure: + +![](508bc574df81fa8d3027a374f6d155fc_img.jpg) + +``` + +sequenceDiagram + participant RNS-A + participant 3G-MSC-B + participant MSC-A + participant MSC-B' + participant BSS-B' + + BSS-B'->>MSC-B': HANDOVER FAILURE + MSC-B'-->>MSC-A: MAP PREPARE HANDOVER response + MSC-A-->>3G-MSC-B: HANDOVER response + 3G-MSC-B->>MSC-A: MAP PREPARE SUBSEQUENT + 3G-MSC-B-->>RNS-A: RELOCATION PREPARATION FAILURE (Note 1) + +``` + +e) radio resources allocation queued and successful handover number allocation (if performed). Later unsuccessful radio resources allocation: + +![](db5deafdae53dbc7d5972957f708c691_img.jpg) + +``` + +sequenceDiagram + participant RNS-A + participant 3G-MSC-B + participant MSC-A + participant MSC-B' + participant BSS-B' + + BSS-B'->>MSC-B': QUEUING INDICAT. + MSC-B'-->>MSC-A: MAP PREPARE HANDOVER response + MSC-A-->>3G-MSC-B: HANDOVER response + 3G-MSC-B->>MSC-A: MAP PREPARE SUBSEQUENT + BSS-B'->>MSC-B': HANDOVER FAILURE + MSC-A->>MSC-B': MAP PROCESS ACCESS SIGNALLING request + 3G-MSC-B->>MSC-A: MAP FORWARD ACCESS SIGNALLING request + 3G-MSC-B-->>RNS-A: RELOCATION PREPARATION FAILURE (Note 1) + +``` + +**Figure 34: Signalling for Subsequent Inter-MSC Handover to third MSC (MSC-B') execution (Negative outcome)** + +NOTE 1: Possible rejection of the handover because of the negative outcome of MAP or BSSMAP procedure. + +Positive outcome: + +![Sequence diagram for Figure 35: Positive outcome of Subsequent Inter-MSC Handover to third MSC (MSC-B') completion.](18e519d1f91133e080347562f681dfb5_img.jpg) + +``` + +sequenceDiagram + participant RNS-A + participant 3G-MSC-B + participant MSC-A + participant MSC-B' + participant BSS-B' + + Note right of RNS-A: IU-RELEASE COMMAND + RNS-A->>3G-MSC-B: IU-RELEASE COMMAND + 3G-MSC-B->>MSC-A: MAP SEND END SIGNAL response + MSC-A->>MSC-B': MAP SEND END SIGNAL + MSC-B'->>BSS-B': HANDOVER COMPLETE + +``` + +Sequence diagram for Figure 35: Positive outcome of Subsequent Inter-MSC Handover to third MSC (MSC-B') completion. + +**Figure 35: Signalling for Subsequent Inter-MSC Handover to third MSC (MSC-B') completion (Successful completion of the procedure)** + +Negative outcome: + +![Sequence diagram for Figure 36: Negative outcome of Subsequent Inter-MSC Handover to third MSC (MSC-B') completion.](71b0a68b4dd64961465d2b0e790538de_img.jpg) + +``` + +sequenceDiagram + participant RNS-A + participant 3G-MSC-B + participant MSC-A + participant MSC-B' + participant BSS-B' + + Note right of RNS-A: RELOCATION CANCEL + RNS-A->>3G-MSC-B: RELOCATION CANCEL + 3G-MSC-B->>MSC-A: MAP PROCESS ACCESS SIGNALLING request (Note 1) + MSC-A->>MSC-B': MAP U -ABORT + MSC-B'->>BSS-B': CLEAR COMMAND + Note right of RNS-A: RELOCATION CANCEL ACK + RNS-A->>3G-MSC-B: RELOCATION CANCEL ACK + +``` + +Sequence diagram for Figure 36: Negative outcome of Subsequent Inter-MSC Handover to third MSC (MSC-B') completion. + +**Figure 36: Signalling for Subsequent Inter-MSC Handover to third MSC (MSC-B') completion (Unsuccessful completion of the procedure)** + +NOTE 1: Specific interworking case detailed below. + +The specific interworking case in MSC-A compared to the subclauses 4.5.1 and 4.5.2 occurs between HANDOVER FAILURE encapsulated in a Process Access Signalling from 3G-MSC-B and the abortion of the dialogue with MSC-B' in the case of a reversion to old channel of the MS: + +| | 29.002 | 29.002 | Notes | +|-----------------|----------------------------------------------------------------|----------------|-------| +| Forward message | MAP PROCESS-SIGNALLING request
-AN-APDU ( HANDOVER FAILURE) | MAP U -ABORT | 1 | +| Positive result | | | | +| Negative result | | MAP U/P -ABORT | 2 | + +NOTE 1: The abortion of the dialogue triggers in MSC-B' the clearing of the circuit connection with MSC-A, if any, and of the Resources between MSC-B' and BSS-B'. The abortion of the dialogue ends the handover procedure with MSC-B'. + +NOTE 2: The abortion of the dialogue ends the handover procedure with 3G-MSC-B. + +### 4.6.4 BSSAP Messages transfer on E-Interface + +The handling is described in chapter 4.5.4. + +### 4.6.5 Processing in MSC-B, and information transfer on E-interface + +The handling is described in chapter 4.5.5. + +### 4.6.6 Cause Code Mapping + +When a Mobile Station is handed over between UMTS and GSM, a mapping of the cause codes used in the RANAP and the BSSMAP protocols is needed. The mapping described here is applicable to the BSSMAP protocol even when used inside MAP in the E-interface. + +The mapping between the cause codes received in RANAP Relocation Required and the cause codes sent in BSSMAP Handover Request is as follows: + +| 25.413 | 48.008 | Notes | +|-----------------------------------------|------------------------------|-------| +| RELOCATION REQUIRED | HANDOVER REQUEST | | +| -Time critical relocation | -'uplink quality' | | +| -Resource optimisation relocation | -Traffic | | +| -Relocation desirable for radio reasons | -Better cell | | +| -Directed retry | -Directed retry | | +| -Reduce Load in serving cell | -Reduce Load in serving cell | | +| -Any other value | -Better cell | | + +The mapping between the cause codes received in RANAP Relocation Cancel and the cause codes sent in BSSMAP Clear Command is as follows: + +| 25.413 | 48.008 | Notes | +|-----------------------------------|----------------------------------------------------|-------| +| RELOCATION CANCEL | CLEAR COMMAND | | +| -Trelcprepeexpiry | -Radio interface failure, reversion to old channel | | +| -Interaction with other procedure | -Radio interface failure, reversion to old channel | | +| -Any other value | -Radio interface failure, reversion to old channel | | + +The mapping between the cause codes received in BSSMAP Handover Failure and the cause codes sent in RANAP Relocation Preparation Failure is as follows: + +| 48.008 | 25.413 | Notes | +|-----------------------------------------------------------------|-------------------------------------------------------------------|-------| +| HANDOVER FAILURE | RELOCATION PREP. FAILURE | | +| -Ciphering algorithm not supported | -Requested ciphering and/or integrity protection is not supported | | +| -Circuit pool mismatch | | 1 | +| -Equipment failure | -Relocation failure in Target CN/RNC or target system | | +| -Invalid message contents | -Abstract Syntax Error | | +| -No radio resource available | -No Radio Resources Available in Target Cell | | +| -O and M intervention | -O and M intervention | 2 | +| -Radio interface failure, reversion to old channel | | | +| -Radio interface message failure | -Relocation failure in Target CN/RNC or target system | | +| -Requested speech version unavailable | -Relocation failure in Target CN/RNC or target system | | +| -Requested terrestrial resource unavailable | -Relocation failure in Target CN/RNC or target system | | +| -Requested transcoding/rate adaption unavailable | -Relocation failure in Target CN/RNC or target system | | +| -Switch circuit pool | | 1 | +| -Terrestrial circuit already allocated | -Relocation failure in Target CN/RNC or target system | | +| -Traffic load in the target cell higher than in the source cell | -Traffic load in the target cell higher than in the source cell | | +| -Any other value | -Relocation failure in Target CN/RNC or target system | | + +NOTE 1: Cause code not used at inter-system handover. + +NOTE 2: Cause code not applicable to this traffic case. + +The mapping between the cause codes received in BSSMAP Clear Request and the cause codes sent in RANAP Iu Release Request is as follows: + +| 48.008 | 25.413 | Notes | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------| +| CLEAR REQUEST | IU RELEASE REQUEST | | +| | | | + +## 4.7 Inter-MSC Handover (GSM to UMTS) + +The general principles of the handover procedures are given in 3GPP TS 23.009 [2]. 3GPP TS 29.010 gives the necessary information for interworking between the 3GPP TS 25.413 [7] RANAP protocol, GSM handover procedures and the 3GPP TS 29.002 [9] MAP protocol. The RANAP protocol is used between the RNS and the 3G\_MSC. + +The following four principles apply for the Inter-MSC handover GSM to UMTS: + +The BSSMAP parameters required for Inter-MSC handover GSM to UMTS are generated as in GSM. + +Received RANAP parameters, e.g. cause code or transparent container, are mapped to the appropriate BSSMAP parameters, e.g. cause code or Handover command. + +The RANAP parameters required for Inter-MSC handover GSM to UMTS are generated from received or stored GSM parameters. + +When new parameters need to be added for transfer on the E-interface, the principles stated in the beginning of subclause 4.5 shall be followed. + +### 4.7.1 Basic Inter-MSC Handover + +When a Mobile Station is handed over between two MSCs, the establishment of a connection between them (described in 3GPP TS 23.009 [2]) requires interworking between A-Interface, Iu-Interface and E-Interface. + +The signalling at initiation, execution and completion of the Basic Inter-MSC handover procedure is shown in figures 37 to 42 with both possible positive or negative outcomes. + +Additionally figure 37b shows the possible interworking when the trace related message is transparently transferred on the E-Interface at Basic Inter-MSC Handover initiation. + +![Sequence diagram for Basic Inter-MSC Handover initiation (no trace related messages transferred).](c0f4777175572d5c52cae16fdddd70be_img.jpg) + +``` + +sequenceDiagram + participant BSS-A + participant MSC-A + participant 3G-MSC-B + participant RNS-B + + Note left of BSS-A: HANDOVER REQUIRED + BSS-A-->>MSC-A: HANDOVER REQUIRED + MSC-A-->>3G-MSC-B: MAP_PREPARE HANDOVER request + Note right of 3G-MSC-B: Possible Alloc. of a handover no. in the VLR-B + 3G-MSC-B-->>RNS-B: RELOCATION REQUEST + +``` + +Sequence diagram for Basic Inter-MSC Handover initiation (no trace related messages transferred). + +**Figure 37a: Signalling for Basic Inter-MSC Handover initiation (no trace related messages transferred)** + +![Sequence diagram for Figure 37b: Signalling for Basic Inter-MSC Handover initiation (CN invoke trace message transferred).](9b1ec0090070bdf52ea28763b8d52477_img.jpg) + +``` + +sequenceDiagram + participant BSS-A + participant MSC-A as MSC-A (*) + participant 3G-MSC-B + participant RNS-B + BSS-A->>MSC-A: HANDOVER REQUIRED + MSC-A->>3G-MSC-B: MAP PREPARE HANDOVER request (**) + Note right of 3G-MSC-B: Possible Alloc. +of a handover +no. in the VLR-B + 3G-MSC-B->>RNS-B: RELOCATION REQUEST + 3G-MSC-B->>RNS-B: CN INVOKE TRACE (***) + +``` + +Sequence diagram for Figure 37b: Signalling for Basic Inter-MSC Handover initiation (CN invoke trace message transferred). + +**Figure 37b: Signalling for Basic Inter-MSC Handover initiation (CN invoke trace message transferred)** + +(\*): Tracing invocation has been received from VLR. + +(\*\*): In that case, HANDOVER REQUEST and MSC INVOKE TRACE messages are included within the AN-apdu parameter. + +(\*\*\*): CN INVOKE TRACE is forwarded to RNS-B if supported by 3G\_MSC-B. + +Possible Positive outcomes: successful radio resources allocation and handover number allocation (if performed): + +![Sequence diagram for Figure 38: Signalling for Basic Inter-MSC Handover execution (Positive outcome).](30fe9e9487585118063341332e802e98_img.jpg) + +``` + +sequenceDiagram + participant BSS-A + participant MSC-A + participant 3G-MSC-B + participant RNS-B + 3G-MSC-B->>RNS-B: RELOCATION REQUEST + RNS-B-->>3G-MSC-B: ACKNOWLEDGE + 3G-MSC-B->>RNS-B: LOCATION REPORTING CONTROL + 3G-MSC-B->>MSC-A: MAP PREPARE HANDOVER response + MSC-A->>BSS-A: HANDOVER COMMAND + +``` + +Sequence diagram for Figure 38: Signalling for Basic Inter-MSC Handover execution (Positive outcome). + +**Figure 38: Signalling for Basic Inter-MSC Handover execution (Positive outcome)** + +Possible Negative outcomes: + +a) user error detected, or handover number allocation unsuccessful (if performed), or component rejection or dialogue abortion performed by 3G\_MSC-B: + +![Sequence diagram for Negative outcome (a): user error or dialogue abortion.](48952b53cfa7fc5afa57e46ca69abe1a_img.jpg) + +``` + +sequenceDiagram + participant BSS-A + participant MSC-A + participant 3G-MSC-B + participant RNS-B + 3G-MSC-B->>MSC-A: MAP PREPARE HANDOVER response negative result, MAP CLOSE + 3G-MSC-B->>MSC-A: MAP U/P-ABORT + MSC-A->>BSS-A: HANDOVER REQUIRED REJECT (Note 1) + +``` + +Sequence diagram for Negative outcome (a): user error or dialogue abortion. + +b) radio resources allocation failure: + +![Sequence diagram for Figure 39 (part 1) showing a handover rejection. Lifelines: BSS-A, MSC-A, 3G-MSC-B, RNS-B. RNS-B sends 'RELOCATION FAILURE' to 3G-MSC-B. MSC-A sends 'MAP PREPARE HANDOVER' to 3G-MSC-B. 3G-MSC-B returns 'response' to MSC-A. MSC-A then sends 'HANDOVER REQUIRED' to BSS-A. BSS-A responds with 'REJECT (Note 1)'.](b34c69e1ec326b01c3a485b27b1df5f6_img.jpg) + +``` + +sequenceDiagram + participant BSS-A + participant MSC-A + participant 3G-MSC-B + participant RNS-B + RNS-B-->>3G-MSC-B: RELOCATION FAILURE + MSC-A->>3G-MSC-B: MAP PREPARE HANDOVER + 3G-MSC-B-->>MSC-A: response + MSC-A->>BSS-A: HANDOVER REQUIRED + BSS-A-->>MSC-A: REJECT (Note 1) + +``` + +Sequence diagram for Figure 39 (part 1) showing a handover rejection. Lifelines: BSS-A, MSC-A, 3G-MSC-B, RNS-B. RNS-B sends 'RELOCATION FAILURE' to 3G-MSC-B. MSC-A sends 'MAP PREPARE HANDOVER' to 3G-MSC-B. 3G-MSC-B returns 'response' to MSC-A. MSC-A then sends 'HANDOVER REQUIRED' to BSS-A. BSS-A responds with 'REJECT (Note 1)'. + +c) unsuccessful handover execution (Reversion to the old radio resources): + +![Sequence diagram for Figure 39 (part 2) showing an unsuccessful handover execution. Lifelines: BSS-A, MSC-A, 3G-MSC-B, RNS-B. BSS-A sends 'HANDOVER FAILURE' to MSC-A. MSC-A sends 'MAP U -ABORT' to 3G-MSC-B. 3G-MSC-B sends 'IU RELEASE COMMAND' to RNS-B.](848073118eebfdbfdb9a60e3923fe0b3_img.jpg) + +``` + +sequenceDiagram + participant BSS-A + participant MSC-A + participant 3G-MSC-B + participant RNS-B + BSS-A->>MSC-A: HANDOVER + BSS-A-->>MSC-A: FAILURE + MSC-A->>3G-MSC-B: MAP U -ABORT + 3G-MSC-B->>RNS-B: IU RELEASE COMMAND + +``` + +Sequence diagram for Figure 39 (part 2) showing an unsuccessful handover execution. Lifelines: BSS-A, MSC-A, 3G-MSC-B, RNS-B. BSS-A sends 'HANDOVER FAILURE' to MSC-A. MSC-A sends 'MAP U -ABORT' to 3G-MSC-B. 3G-MSC-B sends 'IU RELEASE COMMAND' to RNS-B. + +**Figure 39: Signalling for Basic Inter-MSC Handover execution (Negative outcomes)** + +NOTE 1: Possible rejection of the handover because of the negative outcome of MAP or RANAP procedure. + +![Sequence diagram for Figure 40 showing handover completion. Lifelines: BSS-A, MSC-A, 3G-MSC-B, RNS-B. RNS-B sends 'RELOCATION COMPLETE' to 3G-MSC-B. MSC-A sends 'MAP SEND END SIGNAL request' to 3G-MSC-B. 3G-MSC-B sends 'CLEAR COMMAND' to BSS-A.](e90b25c8d90cadc3f76c376701cf27ed_img.jpg) + +``` + +sequenceDiagram + participant BSS-A + participant MSC-A + participant 3G-MSC-B + participant RNS-B + RNS-B-->>3G-MSC-B: RELOCATION COMPLETE + MSC-A->>3G-MSC-B: MAP SEND END SIGNAL request + 3G-MSC-B-->>BSS-A: CLEAR COMMAND + +``` + +Sequence diagram for Figure 40 showing handover completion. Lifelines: BSS-A, MSC-A, 3G-MSC-B, RNS-B. RNS-B sends 'RELOCATION COMPLETE' to 3G-MSC-B. MSC-A sends 'MAP SEND END SIGNAL request' to 3G-MSC-B. 3G-MSC-B sends 'CLEAR COMMAND' to BSS-A. + +**Figure 40: Signalling for Basic Inter-MSC Handover completion** + +Positive outcome: + +![Sequence diagram for Figure 41 showing a positive handover completion. Lifelines: BSS-A, MSC-A, 3G-MSC-B, RNS-B. MSC-A sends 'MAP SEND END SIGNAL' to 3G-MSC-B. 3G-MSC-B returns 'response' to MSC-A. 3G-MSC-B then sends 'IU RELEASE COMMAND (Note 2)' to RNS-B.](ec035e97a11ce40541dec6d88d54c7cb_img.jpg) + +``` + +sequenceDiagram + participant BSS-A + participant MSC-A + participant 3G-MSC-B + participant RNS-B + MSC-A->>3G-MSC-B: MAP SEND END SIGNAL + 3G-MSC-B-->>MSC-A: response + 3G-MSC-B->>RNS-B: IU RELEASE COMMAND + Note over 3G-MSC-B,RNS-B: (Note 2) + +``` + +Sequence diagram for Figure 41 showing a positive handover completion. Lifelines: BSS-A, MSC-A, 3G-MSC-B, RNS-B. MSC-A sends 'MAP SEND END SIGNAL' to 3G-MSC-B. 3G-MSC-B returns 'response' to MSC-A. 3G-MSC-B then sends 'IU RELEASE COMMAND (Note 2)' to RNS-B. + +**Figure 41: Signalling for Basic Inter-MSC Handover completion (Positive outcome)** + +Negative outcome: + +![Sequence diagram for Figure 42 showing a negative handover completion. Lifelines: BSS-A, MSC-A, 3G-MSC-B, RNS-B. MSC-A sends 'MAP U/P -ABORT' to 3G-MSC-B. 3G-MSC-B sends 'IU RELEASE COMMAND' to RNS-B.](910aca984b27c368361b38751ab5eea6_img.jpg) + +``` + +sequenceDiagram + participant BSS-A + participant MSC-A + participant 3G-MSC-B + participant RNS-B + MSC-A->>3G-MSC-B: MAP U/P -ABORT + 3G-MSC-B->>RNS-B: IU RELEASE COMMAND + +``` + +Sequence diagram for Figure 42 showing a negative handover completion. Lifelines: BSS-A, MSC-A, 3G-MSC-B, RNS-B. MSC-A sends 'MAP U/P -ABORT' to 3G-MSC-B. 3G-MSC-B sends 'IU RELEASE COMMAND' to RNS-B. + +**Figure 42: Signalling for Basic Inter-MSC Handover completion (Negative outcome)** + +NOTE 2: From interworking between MAP and RANAP point of view, when the call is released. + +![Sequence diagram showing signalling for updating of anchor MSC after change of location in RNS. Lifelines: BSS-A, MSC-A, 3G-MSC-B, RNS-B. MSC-A sends MAP PROCESS ACCESS <-----> SIGNALLING to 3G-MSC-B. 3G-MSC-B sends LOCATION REPORT to RNS-B.](65e8c0628536d6d4245e9ab46ba070c3_img.jpg) + +``` + +sequenceDiagram + participant BSS-A + participant MSC-A + participant 3G-MSC-B + participant RNS-B + MSC-A->>3G-MSC-B: MAP PROCESS ACCESS <-----> SIGNALLING + 3G-MSC-B->>RNS-B: LOCATION REPORT + +``` + +Sequence diagram showing signalling for updating of anchor MSC after change of location in RNS. Lifelines: BSS-A, MSC-A, 3G-MSC-B, RNS-B. MSC-A sends MAP PROCESS ACCESS <-----> SIGNALLING to 3G-MSC-B. 3G-MSC-B sends LOCATION REPORT to RNS-B. + +**Figure 42a: Signalling for updating of anchor MSC after change of location in RNS** + +The handover procedure is normally triggered by BSS-A by sending a HANDOVER REQUIRED message on A-Interface to MSC-A. The invocation of the Basic Inter-MSC handover procedure is performed and controlled by MSC-A. The sending of the MAP Prepare-Handover request to 3G\_MSC-B is triggered in MSC-A upon receipt of the HANDOVER REQUIRED message. The identity of the target RNC where the call is to be handed over in 3G\_MSC-B area, provided in the HANDOVER REQUIRED message in the information element Cell Identifier List (Preferred), is mapped to the target RNC Id MAP parameter and the HANDOVER REQUEST message is encapsulated in the an-APDU MAP parameter of the Prepare-Handover MAP request. 3G\_MSC-B can invoke another operation towards the VLR-B (allocation of the handover number described in 3GPP TS 29.002 [9]). + +Additionally, if tracing activity has been invoked, the trace related message can be transferred on the E-Interface encapsulated in the an-APDU MAP parameter of the Prepare-Handover Request. If transferred, one complete trace related message at a time shall be included in the an-APDU MAP parameter after the HANDOVER REQUEST message. Note: UMTS supports only CN initiated tracing. + +The interworking between Prepare Handover and HANDOVER REQUIRED is as follows: + +| | 48.008 | 29.002 | Notes | +|-----------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------| +| Forward message | HANDOVER REQUIRED

BSSMAP information elements

GERAN classmark | MAP PREPARE HANDOVER request

-ho-NumberNotRequired
-target RNC Id
-IMSI
-Integrity protection info
-Encryption info
-an-APDU(
HANDOVER REQUEST,
MSC INVOKE TRACE)
-GERAN classmark | 1

2

3

4

7 | +| Positive result | | MAP PREPARE HANDOVER response

-handover number
-an-APDU(
HANDOVER REQUEST
ACKNOWLEDGE or
HANDOVER FAILURE) | 5 | +| Negative result | HANDOVER REQUIRED REJECT

equipment failure
equipment failure

equipment failure
equipment failure

equipment failure
equipment failure | MAP PREPARE HANDOVER

System Failure
No Handover Number available
UnexpectedDataValue
Data Missing

MAP CLOSE
MAP U/P -ABORT | 6 | + +NOTE 1: The ho-NumberNotRequired parameter is included by MSC-A, when MSC-A decides not to use any circuit connection with 3G\_MSC-B. No handover number shall be present in the positive result. Any negative response from 3G\_MSC-B shall not be due to handover number allocation problem. + +NOTE 2: Integrity protection information, encryption information and IMSI parameters are included by MSC-A, only when the MSC-A uses 29.002 as per release 99. These IEs are not included if the MSC-A is R98 or earlier. + +NOTE 3: The process performed on the BSSMAP information elements received in the HANDOVER REQUIRED message is described in the 3GPP TS 48.008 [12]. + +NOTE 4: The process performed on the BSSMAP information elements received in the MSC INVOKE TRACE message is described in subclause 4.5.5.6. + +NOTE 5: The response to the Prepare-Handover request can include in its an-APDU parameter, identifying the 3GPP TS 48.006 protocol, either a BSSMAP HANDOVER REQUEST ACKNOWLEDGE or a BSSMAP HANDOVER FAILURE. + +In the first case, the positive result triggers in MSC-A the sending on A-Interface of the HANDOVER COMMAND. + +In the second case, the positive result triggers in MSC-A optionally the sending of the HANDOVER REQUIRED REJECT. + +(The possible sending of the HANDOVER REQUIRED REJECT message upon receipt of the HANDOVER FAILURE is out of the scope of 3GPP TS 29.010 and lies in 3GPP TS 48.008 [12]). + +NOTE 6: The possible sending of the HANDOVER REQUIRED REJECT message is described in 3GPP TS 48.008 [12]. + +NOTE 7: If the GERAN Classmark was not received with the HANDOVER REQUIRED message initiating the handover, MSC-A shall include any previously received GERAN Classmark. See 3GPP TS 43.051 [17]. + +The interworking between Prepare Handover and RELOCATION REQUEST in 3G\_MSC-B is as follows: + +| | 29.002 | 25.413 | Notes | +|-----------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------| +| Forward message | MAP PREPARE HANDOVER request
- ho-NumberNotRequired
- target RNC Id
- IMSI
- Integrity protection info
- Encryption info
- RANAP service handover
- UESBI
- an-APDU(
HANDOVER REQUEST,
MSC INVOKE TRACE)

BSSMAP information elements:

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

RANAP information elements:

RAB parameters
Cause
sRNC to tRNC container
SNA Access Information

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




1




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

BSSMAP information elements:

Layer 3 info | RELOCATION REQUEST ACK

RANAP information elements:

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

GERAN classmark | RELOCATION FAILURE

RANAP information elements:

GERAN classmark |






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

BSSMAP information elements

GERAN classmark | SUBSEQUENT HANDOVER request

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



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

equipment failure
equipment failure

equipment failure
equipment failure

CLEAR COMMAND

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



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

BSSMAP information elements:

Cause
sRNC to tRNC container | RELOCATION REQUEST

RANAP information elements:

Cause
sRNC to tRNC container

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

BSSMAP information elements:

Layer 3 info | RELOCATION REQUEST ACK

RANAP information elements:

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

BSSMAP information elements:

GERAN classmark | RELOCATION FAILURE

RANAP information elements:

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

BSSMAP information elements:

Channel Type | RAB ASSIGNMENT REQ

Service handover

RANAP information elements:

RAB parameters | | +| Positive result | MAP PREPARE HANDOVER request
-an-APDU( ASSIGNMENT COMPLETE

or
ASSIGNMENT FAILURE)

BSSMAP information elements:

Cause | RAB ASSIGNMENT RESPONSE (positive result)
RAB ASSIGNMENT RESPONSE (negative result)

RANAP information elements:

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

BSSMAP information
elements:

Encryption information | SECURITY MODE CMD

RANAP information
elements:

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

BSSMAP information
elements:

Encryption information

Cause | SECURITY MODE
COMPLETE
SECURITY MODE
REJECT

RANAP information
elements:

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

RANAP information
elements:

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

-an-APDU(
HANDOVER PERFORMED)

BSSMAP information
elements:

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

RANAP information elements

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


2
4 | +| Positive result | MAP PREPARE HANDOVER response

RELOCATION COMMAND

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

Unspecified failure
Unspecified failure

Unspecified failure
Unspecified failure

Unspecified failure
Unspecified failure | MAP PREPARE HANDOVER

System Failure
No Handover Number
available
UnexpectedDataValue
Data Missing

MAP CLOSE
MAP U/P -ABORT | | + +NOTE 1: The RANAP information elements are already stored in 3G\_MSC. + +The ho-NumberNotRequired parameter is included by 3G\_MSC-A, when 3G\_MSC-A decides not to use any circuit connection with 3G\_MSC-B. No relocation numbers shall be present in the positive result. Any negative response from 3G\_MSC-B shall not be due to relocation number allocation problem. + +NOTE 2: The process performed on the RANAP information elements received in the RELOCATION REQUIRED message is described in the 3GPP TS 25.413 [7]. + +NOTE 3: The response to the Prepare-Handover request can include in its an-APDU parameter, identifying the 3GPP TS 25.413 [7] protocol, either a RANAP RELOCATION REQUEST ACKNOWLEDGE or a RANAP RELOCATION FAILURE. + +In the first case, the positive result triggers in 3G\_MSC-A the sending on Iu-Interface of the RELOCATION CMD. + +In the second case, the positive result triggers in 3G\_MSC-A the sending of the RELOCATION PREP FAILURE. + +NOTE 4: If the GERAN Classmark was not received with the RELOCATION REQUIRED message initiating the relocation, 3G\_MSC-A shall include any previously received GERAN Classmark. See 3GPP TS 43.051 [17]. + +The interworking between Send End Signal and RELOCATION COMPLETE in 3G\_MSC-B is as follows: + +| | 25.413 | 29.002 | Notes | +|-----------------|----------------------------------------------------------|--------------------------------|-------| +| Forward message | RELOCATION COMPLETE MAP SEND END SIGNAL request | -an-APDU(
RELOCATION COMPL) | | +| Positive result | IU RELEASE COMMAND
-Normal release | MAP SEND END SIGNAL response | 1 | +| Negative result | IU RELEASE COMMAND
-Normal release
-Normal release | MAP CLOSE
MAP U/P -ABORT | 2 | + +NOTE 1: The positive empty result triggers the clearing of the Radio Resources on the Iu-Interface and the release of the SCCP connection between 3G\_MSC-B and RNS-B. If a circuit connection is used between 3G\_MSC-A and 3G\_MSC-B, the 'Normal release' clearing cause shall only be given to RNS-B when 3G\_MSC-B has received a clearing indication on its circuit connection with 3G\_MSC-A. + +NOTE 2: The abortion of the dialogue or the rejection of the component triggers in 3G\_MSC-B the clearing of its circuit connection with 3G\_MSC-A, if any, of the Radio Resources on the Iu-Interface and the release of the SCCP connection between 3G\_MSC-B and RNS-B. + +The interworking between Send End Signal and IU RELEASE COMMAND in 3G\_MSC-A is as follows: + +| | 29.002 | 25.413 | Notes | +|-----------------|-----------------------------------|----------------------------|-------| +| Forward message | MAP SEND END SIGNAL request | IU RELEASE COMMAND | | +| Positive result | -an-APDU(
RELOCATION COMPLETE) | - Successful
Relocation | | +| Negative result | | | | + +The interworking between RELOCATION CANCEL in case of relocation cancelled and User Abort in 3G\_MSC-A is as follows: + +| | 25.413 | 29.002 | Notes | +|-----------------|---------------------------|-----------------------------------|-------| +| Forward message | RELOCATION CANCEL | MAP U -ABORT | | +| Positive result | - Relocation
cancelled | RELOCATION CANCEL ACKNOWLEDGEMENT | | +| Negative result | | | | + +### 4.8.2 Subsequent Inter-MSC Relocation back to 3G\_MSC-A + +When a Mobile Station is being relocated back to 3G\_MSC-A, the procedure (described in TS 23.009) requires interworking between Iu-Interface and E-Interface. + +The signalling at initiation, execution and completion of the Subsequent Inter-MSC relocation procedure is shown in figures 55 to 59. + +![Sequence diagram for Figure 55: Signalling for Subsequent Inter-MSC Relocation back to 3G_MSC-A initiation. Lifelines: RNS-A, 3G-MSC-B, 3G-MSC-A, RNS-B. RNS-A sends RELOCATION REQUIRED to 3G-MSC-B. 3G-MSC-B sends MAP PREPARE SUBSEQUENT HANDOVER request to 3G-MSC-A. 3G-MSC-A sends RELOCATION REQUEST to RNS-B.](49fe8fe978c0f7e73112d231feb377eb_img.jpg) + +``` + +sequenceDiagram + participant RNS-A + participant 3G-MSC-B + participant 3G-MSC-A + participant RNS-B + Note left of RNS-A: Error: Reference source not + RNS-A->>3G-MSC-B: RELOCATION REQUIRED + 3G-MSC-B->>3G-MSC-A: MAP PREPARE SUBSEQUENT HANDOVER request + 3G-MSC-A->>RNS-B: RELOCATION REQUEST + +``` + +Sequence diagram for Figure 55: Signalling for Subsequent Inter-MSC Relocation back to 3G\_MSC-A initiation. Lifelines: RNS-A, 3G-MSC-B, 3G-MSC-A, RNS-B. RNS-A sends RELOCATION REQUIRED to 3G-MSC-B. 3G-MSC-B sends MAP PREPARE SUBSEQUENT HANDOVER request to 3G-MSC-A. 3G-MSC-A sends RELOCATION REQUEST to RNS-B. + +**Figure 55: Signalling for Subsequent Inter-MSC Relocation back to 3G\_MSC-A initiation** + +Possible Positive outcomes: successful radio resources allocation: + +![Sequence diagram for Figure 56: Signalling for Subsequent Inter-MSC Relocation back to 3G_MSC-A execution (Positive outcome). Lifelines: RNS-A, 3G-MSC-B, 3G-MSC-A, RNS-B. 3G-MSC-A sends RELOCATION REQUEST to RNS-B. RNS-B sends ACKNOWLEDGE to 3G-MSC-A. 3G-MSC-A sends MAP PREPARE SUBSEQUENT HANDOVER response to 3G-MSC-B. 3G-MSC-B sends RELOCATION COMMAND to RNS-A.](2fc2e531b3b3c695cca497516ec79f20_img.jpg) + +``` + +sequenceDiagram + participant RNS-A + participant 3G-MSC-B + participant 3G-MSC-A + participant RNS-B + 3G-MSC-A->>RNS-B: RELOCATION REQUEST + RNS-B-->>3G-MSC-A: ACKNOWLEDGE + 3G-MSC-A->>3G-MSC-B: MAP PREPARE SUBSEQUENT HANDOVER response + 3G-MSC-B->>RNS-A: RELOCATION COMMAND + +``` + +Sequence diagram for Figure 56: Signalling for Subsequent Inter-MSC Relocation back to 3G\_MSC-A execution (Positive outcome). Lifelines: RNS-A, 3G-MSC-B, 3G-MSC-A, RNS-B. 3G-MSC-A sends RELOCATION REQUEST to RNS-B. RNS-B sends ACKNOWLEDGE to 3G-MSC-A. 3G-MSC-A sends MAP PREPARE SUBSEQUENT HANDOVER response to 3G-MSC-B. 3G-MSC-B sends RELOCATION COMMAND to RNS-A. + +**Figure 56: Signalling for Subsequent Inter-MSC Relocation back to 3G\_MSC-A execution (Positive outcome)** + +Possible Negative outcomes: + +a) user error detected, or component rejection or dialogue abortion performed by 3G\_MSC-A: + +![Sequence diagram for negative outcome a): Lifelines: RNS-A, 3G-MSC-B, 3G-MSC-A, RNS-B. 3G-MSC-B sends MAP PREPARE SUBSEQUENT HANDOVER to 3G-MSC-A. 3G-MSC-A sends response negative result to 3G-MSC-B. 3G-MSC-B sends RELOCATION PREP FAILURE (Note 1) to RNS-A.](d15e2d3e8dd9157eb7f0cc120097484a_img.jpg) + +``` + +sequenceDiagram + participant RNS-A + participant 3G-MSC-B + participant 3G-MSC-A + participant RNS-B + 3G-MSC-B->>3G-MSC-A: MAP PREPARE SUBSEQUENT HANDOVER + 3G-MSC-A-->>3G-MSC-B: response negative result + 3G-MSC-B->>RNS-A: RELOCATION PREP FAILURE (Note 1) + +``` + +Sequence diagram for negative outcome a): Lifelines: RNS-A, 3G-MSC-B, 3G-MSC-A, RNS-B. 3G-MSC-B sends MAP PREPARE SUBSEQUENT HANDOVER to 3G-MSC-A. 3G-MSC-A sends response negative result to 3G-MSC-B. 3G-MSC-B sends RELOCATION PREP FAILURE (Note 1) to RNS-A. + +b) component rejection or dialogue abortion performed by 3G\_MSC-A: + +![Sequence diagram for negative outcome b): Lifelines: RNS-A, 3G-MSC-B, 3G-MSC-A, RNS-B. 3G-MSC-A sends MAP CLOSE, MAP U/P ABORT to 3G-MSC-B. 3G-MSC-B sends IU RELEASE COMMAND to RNS-A.](a0b72ad654428ce2b44766f24928643e_img.jpg) + +``` + +sequenceDiagram + participant RNS-A + participant 3G-MSC-B + participant 3G-MSC-A + participant RNS-B + 3G-MSC-A->>3G-MSC-B: MAP CLOSE, MAP U/P ABORT + 3G-MSC-B->>RNS-A: IU RELEASE COMMAND + +``` + +Sequence diagram for negative outcome b): Lifelines: RNS-A, 3G-MSC-B, 3G-MSC-A, RNS-B. 3G-MSC-A sends MAP CLOSE, MAP U/P ABORT to 3G-MSC-B. 3G-MSC-B sends IU RELEASE COMMAND to RNS-A. + +c) radio resources allocation failure: + +![Sequence diagram for negative outcome c): Lifelines: RNS-A, 3G-MSC-B, 3G-MSC-A, RNS-B. 3G-MSC-B sends MAP PREPARE SUBSEQUENT HANDOVER response to 3G-MSC-A. 3G-MSC-A sends RELOCATION FAILURE to RNS-B. 3G-MSC-A sends RELOCATION PREP FAILURE to 3G-MSC-B. 3G-MSC-B sends RELOCATION PREP FAILURE to RNS-A.](d5661c3661190c44429a1a75f61d7550_img.jpg) + +``` + +sequenceDiagram + participant RNS-A + participant 3G-MSC-B + participant 3G-MSC-A + participant RNS-B + 3G-MSC-B->>3G-MSC-A: MAP PREPARE SUBSEQUENT HANDOVER response + 3G-MSC-A->>RNS-B: RELOCATION FAILURE + 3G-MSC-A->>3G-MSC-B: RELOCATION PREP FAILURE + 3G-MSC-B->>RNS-A: RELOCATION PREP FAILURE + +``` + +Sequence diagram for negative outcome c): Lifelines: RNS-A, 3G-MSC-B, 3G-MSC-A, RNS-B. 3G-MSC-B sends MAP PREPARE SUBSEQUENT HANDOVER response to 3G-MSC-A. 3G-MSC-A sends RELOCATION FAILURE to RNS-B. 3G-MSC-A sends RELOCATION PREP FAILURE to 3G-MSC-B. 3G-MSC-B sends RELOCATION PREP FAILURE to RNS-A. + +d) radio resources allocation partial failure (3G\_MSC-A decides to reject the relocation): + +![Sequence diagram for negative outcome d): Lifelines: RNS-A, 3G-MSC-B, 3G-MSC-A, RNS-B. 3G-MSC-A sends RELOCATION REQUEST to RNS-B. RNS-B sends ACK to 3G-MSC-A. 3G-MSC-A sends MAP PREPARE SUBSEQUENT HANDOVER response to 3G-MSC-B. 3G-MSC-B sends RELOCATION PREP FAILURE to RNS-A.](6a9873d74d8a4e1b6b5ff8d6199cd006_img.jpg) + +``` + +sequenceDiagram + participant RNS-A + participant 3G-MSC-B + participant 3G-MSC-A + participant RNS-B + 3G-MSC-A->>RNS-B: RELOCATION REQUEST + RNS-B-->>3G-MSC-A: ACK + 3G-MSC-A->>3G-MSC-B: MAP PREPARE SUBSEQUENT HANDOVER response + 3G-MSC-B->>RNS-A: RELOCATION PREP FAILURE + +``` + +Sequence diagram for negative outcome d): Lifelines: RNS-A, 3G-MSC-B, 3G-MSC-A, RNS-B. 3G-MSC-A sends RELOCATION REQUEST to RNS-B. RNS-B sends ACK to 3G-MSC-A. 3G-MSC-A sends MAP PREPARE SUBSEQUENT HANDOVER response to 3G-MSC-B. 3G-MSC-B sends RELOCATION PREP FAILURE to RNS-A. + +e) unsuccessful relocation execution (relocation cancelled): + +![Sequence diagram for Figure 57: Signalling for Subsequent Inter- MSC Relocation back to 3G_MSC-A execution (Negative outcome).](8f8caebe58364416a2eda21039d8c7bf_img.jpg) + +``` + +sequenceDiagram + participant RNS-A + participant 3G-MSC-B + participant 3G-MSC-A + participant RNS-B + Note left of RNS-A: e) unsuccessful relocation execution (relocation cancelled): + RNS-A->>3G-MSC-B: RELOCATION + RNS-A->>3G-MSC-B: CANCEL + 3G-MSC-B->>3G-MSC-A: MAP PROCESS ACCESS + 3G-MSC-B->>3G-MSC-A: SIGNALING request + 3G-MSC-A->>RNS-B: IU RELEASE COMMAND + 3G-MSC-A->>RNS-B: IU RELEASE COMPLETE + 3G-MSC-A->>3G-MSC-B: MAP FORWARD ACCESS + 3G-MSC-A->>3G-MSC-B: SIGNALING request + 3G-MSC-B->>RNS-A: RELOCATION + 3G-MSC-B->>RNS-A: CANCEL ACK + +``` + +Sequence diagram for Figure 57: Signalling for Subsequent Inter- MSC Relocation back to 3G\_MSC-A execution (Negative outcome). + +**Figure 57: Signalling for Subsequent Inter- MSC Relocation back to 3G\_MSC-A execution (Negative outcome)** + +![Sequence diagram for Figure 58: Signalling for Subsequent Inter- MSC Relocation back to 3G_MSC-A completion (Successful completion of the procedure).](b3cd59f24a21fab4cd8ac6fe743ab3a9_img.jpg) + +``` + +sequenceDiagram + participant RNS-A + participant 3G-MSC-B + participant 3G-MSC-A + participant RNS-B + 3G-MSC-B->>3G-MSC-A: MAP SEND END SIGNAL + 3G-MSC-B->>3G-MSC-A: response + 3G-MSC-A->>RNS-B: RELOCATION + 3G-MSC-A->>RNS-B: COMPLETE + 3G-MSC-A->>3G-MSC-B: IU RELEASE CMD + +``` + +Sequence diagram for Figure 58: Signalling for Subsequent Inter- MSC Relocation back to 3G\_MSC-A completion (Successful completion of the procedure). + +**Figure 58: Signalling for Subsequent Inter- MSC Relocation back to 3G\_MSC-A completion (Successful completion of the procedure)** + +NOTE: Positive outcome case shown in figure 53. + +![Sequence diagram for Figure 59: Signalling for Subsequent Inter- MSC Relocation back to 3G_MSC-A completion (Unsuccessful completion of the procedure).](c6e0b9030f9fb81435eaf9cb71532614_img.jpg) + +``` + +sequenceDiagram + participant RNS-A + participant 3G-MSC-B + participant 3G-MSC-A + participant RNS-B + 3G-MSC-B->>3G-MSC-A: MAP U/P -ABORT + 3G-MSC-A->>RNS-B: IU RELEASE COMMAND + Note right of RNS-B: (Note 1) + +``` + +Sequence diagram for Figure 59: Signalling for Subsequent Inter- MSC Relocation back to 3G\_MSC-A completion (Unsuccessful completion of the procedure). + +**Figure 59: Signalling for Subsequent Inter- MSC Relocation back to 3G\_MSC-A completion (Unsuccessful completion of the procedure)** + +NOTE: Abnormal end of the procedure that triggers the clearing of all resources in 3G\_MSC-B. + +The interworking between Prepare Subsequent Handover and RELOCATION REQUIRED is as follows: + +| | 25.413 | 29.002 | Notes | +|-----------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------|--------| +| Forward message | REL. REQUIRED
RANAP information elements
GERAN classmark | MAP PREPARE SUBSEQUENT HANDOVER request
-target MSC number
-target RNC Id
-an-APDU( RELOCATION REQ)
-GERAN classmark | 1
3 | +| Positive result | RELOCATION CMD.
RELOCATION PREP FAILURE | MAP PREPARE SUBSEQUENT HANDOVER response
-an-APDU( RELOCATION REQUEST ACKNOWLEDGE or RELOCATION FAILURE) | 2 | +| Negative result | REL. PREP. FAILURE
Unspecified failure
Unspecified failure
Unspecified failure
Unspecified failure
Iu RELEASE COMMAND
Unspecified failure
Unspecified failure | MAP PREPARE SUBSEQUENT HANDOVER response
Unknown MSC
Subsequent Handover Failure
UnexpectedDataValue
Data Missing
MAP CLOSE
MAP U/P -ABORT | | + +NOTE 1: The processing performed on the RANAP information elements received in the RELOCATION REQUIRED message is out of the scope of the present document. The target MSC number is provided to 3G\_MSC-A by 3G\_MSC-B based on the information received from RNS-B. + +NOTE 2: The response to the Prepare-Subsequent-Handover request can include in its an-APDU parameter, identifying the 3GPP TS 25.413 [7] protocol, a RANAP RELOCATION REQUEST ACKNOWLEDGE or a RANAP RELOCATION FAILURE. + +NOTE 3: If the GERAN Classmark was not received with the RELOCATION REQUIRED message initiating the relocation, MSC-B shall include any previously received GERAN Classmark. See 3GPP TS 43.051 [17]. + +In the first case, the positive result triggers in 3G\_MSC-B the sending on Iu-Interface of the RELOCATION COMMAND. + +In the second case, the positive result triggers in 3G\_MSC-B the sending of the RELOCATION PREPARATION FAILURE. + +The interworking between RELOCATION CANCEL and MAP Process Signalling Request in 3G\_MSC-A is as follows: + +| | 29.002 | 25.413 | Notes | +|-----------------|-----------------------------------------------------------------------|---------------------|-------| +| Forward message | MAP PROCESS-SIGNALLING request
-an-APDU(
RELOCATION CANCEL) | IU RELEASE COMMAND | | +| Positive result | MAP FORWARD-SIGNALLING request
-an-APDU(
RELOCATION CANCEL ACK) | IU RELEASE COMPLETE | | +| Negative result | | | | + +The interworking between RELOCATION CANCEL and MAP Process Signalling Request in 3G\_MSC-B is as follows: + +| | 25.413 | 29.002 | Notes | +|-----------------|-----------------------|-----------------------------------------------------------------------|-------| +| Forward message | RELOCATION CANCEL | MAP PROCESS-SIGNALLING request
-an-APDU(
RELOCATION CANCEL) | | +| Positive result | RELOCATION CANCEL ACK | MAP FORWARD-SIGNALLING request
-an-APDU(
RELOCATION CANCEL ACK) | | +| Negative result | | | | + +The interworking between Send End Signal Result and RELOCATION COMPLETE in 3G\_MSC-A is as follows: + +| | 25.413 | 29.002 | Notes | +|-----------------|---------------------|------------------------------|-------| +| Forward message | RELOCATION COMPLETE | MAP SEND END SIGNAL response | | +| Positive result | | | | +| Negative result | | MAP U/P -ABORT | 1 | + +NOTE: The abortion of the dialogue ends the relocation procedure with 3G\_MSC-B. + +### 4.8.3 Subsequent Inter-MSC Relocation to third MSC + +When a Mobile Station is being relocated to a third MSC, the procedure (described in 3GPP TS 23.009 [2]) does require one specific interworking case in 3G\_MSC-A (figure 64) between E-Interface from 3G\_MSC-B and E-Interface from 3G\_MSC-B' other than the combination of the ones described in the subclause 4.8.1 and 4.8.2. + +Error: + +91 + +Error: Reference source not + +![Sequence diagram for Figure 60: Signalling for Subsequent Inter-MSC Relocation to third MSC (3G_MSC-B') initiation. Lifelines: RNS-A, 3G-MSC-B, 3G-MSC-A, 3G-MSC-B'. RNS-A sends RELOCATION REQUIRED to 3G-MSC-B. 3G-MSC-B sends MAP PREPARE SUBSEQUENT HANDOVER request to 3G-MSC-A. 3G-MSC-A sends MAP PREPARE HANDOVER request to 3G-MSC-B'. 3G-MSC-B' has a box for 'Possib. Alloc. of relo number VLR-B' and sends RELOCATION REQUEST to RNS-B'.](3750b0149a6380885998ab3ca6a8787c_img.jpg) + +``` + +sequenceDiagram + participant RNS-A + participant 3G-MSC-B + participant 3G-MSC-A + participant 3G-MSC-B' + participant RNS-B' + RNS-A->>3G-MSC-B: RELOCATION REQUIRED + 3G-MSC-B->>3G-MSC-A: MAP PREPARE SUBSEQUENT HANDOVER request + 3G-MSC-A->>3G-MSC-B': MAP PREPARE HANDOVER request + Note right of 3G-MSC-B': Possib. Alloc. of relo number VLR-B' + 3G-MSC-B'->>RNS-B': RELOCATION REQUEST + +``` + +Sequence diagram for Figure 60: Signalling for Subsequent Inter-MSC Relocation to third MSC (3G\_MSC-B') initiation. Lifelines: RNS-A, 3G-MSC-B, 3G-MSC-A, 3G-MSC-B'. RNS-A sends RELOCATION REQUIRED to 3G-MSC-B. 3G-MSC-B sends MAP PREPARE SUBSEQUENT HANDOVER request to 3G-MSC-A. 3G-MSC-A sends MAP PREPARE HANDOVER request to 3G-MSC-B'. 3G-MSC-B' has a box for 'Possib. Alloc. of relo number VLR-B' and sends RELOCATION REQUEST to RNS-B'. + +Figure 60: Signalling for Subsequent Inter-MSC Relocation to third MSC (3G\_MSC-B') initiation + +Possible Positive outcomes: successful radio resources allocation: + +![Sequence diagram for Figure 61: Signalling for Subsequent Inter-MSC Relocation to third MSC (3G_MSC-B') execution (Positive outcome). Lifelines: RNS-A, 3G-MSC-B, 3G-MSC-A, 3G-MSC-B', RNS-B'. RNS-B' sends RELOCATION REQUEST ACKNOWLEDGE to 3G-MSC-B'. 3G-MSC-B' sends MAP PREPARE HANDOVER response to 3G-MSC-A. 3G-MSC-A sends MAP PREPARE SUBSEQUENT HANDOVER response to 3G-MSC-B. 3G-MSC-B sends RELOCATION COMMAND to RNS-A.](a2bbc82e5c6132b0870bd70f6657f919_img.jpg) + +``` + +sequenceDiagram + participant RNS-A + participant 3G-MSC-B + participant 3G-MSC-A + participant 3G-MSC-B' + participant RNS-B' + RNS-B'-->>3G-MSC-B': RELOCATION REQUEST ACKNOWLEDGE + 3G-MSC-B'-->>3G-MSC-A: MAP PREPARE HANDOVER response + 3G-MSC-A-->>3G-MSC-B: MAP PREPARE SUBSEQUENT HANDOVER response + 3G-MSC-B-->>RNS-A: RELOCATION COMMAND + +``` + +Sequence diagram for Figure 61: Signalling for Subsequent Inter-MSC Relocation to third MSC (3G\_MSC-B') execution (Positive outcome). Lifelines: RNS-A, 3G-MSC-B, 3G-MSC-A, 3G-MSC-B', RNS-B'. RNS-B' sends RELOCATION REQUEST ACKNOWLEDGE to 3G-MSC-B'. 3G-MSC-B' sends MAP PREPARE HANDOVER response to 3G-MSC-A. 3G-MSC-A sends MAP PREPARE SUBSEQUENT HANDOVER response to 3G-MSC-B. 3G-MSC-B sends RELOCATION COMMAND to RNS-A. + +Figure 61: Signalling for Subsequent Inter-MSC Relocation to third MSC (3G\_MSC-B') execution (Positive outcome) + +Possible Negative outcomes: + +a) user error detected, or component rejection or dialogue abortion performed by 3G\_MSC-B': + +![Sequence diagram for Figure 61 negative outcome. Lifelines: RNS-A, 3G-MSC-B, 3G-MSC-A, 3G-MSC-B', RNS-B'. 3G-MSC-B' sends MAP PREPARE HANDOVER response negative result, MAP CLOSE, and MAP U/P -ABORT to 3G-MSC-A. 3G-MSC-A sends MAP PREPARE SUBSEQUENT HANDOVER response negative result to 3G-MSC-B. 3G-MSC-B sends RELOCATION PREPARATION FAILURE to RNS-A.](f43d225d8fed2845b8d7e5afecbfe636_img.jpg) + +``` + +sequenceDiagram + participant RNS-A + participant 3G-MSC-B + participant 3G-MSC-A + participant 3G-MSC-B' + participant RNS-B' + 3G-MSC-B'-->>3G-MSC-A: MAP PREPARE HANDOVER response negative result + 3G-MSC-B'-->>3G-MSC-A: MAP CLOSE + 3G-MSC-B'-->>3G-MSC-A: MAP U/P -ABORT + 3G-MSC-A-->>3G-MSC-B: MAP PREPARE SUBSEQUENT HANDOVER response negative result + 3G-MSC-B-->>RNS-A: RELOCATION PREPARATION FAILURE + +``` + +Sequence diagram for Figure 61 negative outcome. Lifelines: RNS-A, 3G-MSC-B, 3G-MSC-A, 3G-MSC-B', RNS-B'. 3G-MSC-B' sends MAP PREPARE HANDOVER response negative result, MAP CLOSE, and MAP U/P -ABORT to 3G-MSC-A. 3G-MSC-A sends MAP PREPARE SUBSEQUENT HANDOVER response negative result to 3G-MSC-B. 3G-MSC-B sends RELOCATION PREPARATION FAILURE to RNS-A. + +b) radio resources allocation failure: + +![Sequence diagram for Figure 62 (Negative outcome) showing a radio resource allocation failure during inter-MSC relocation.](f1de68a4cbb9b92a1c0ffd919bbd199c_img.jpg) + +``` + +sequenceDiagram + participant RNS-A + participant 3G-MSC-B + participant 3G-MSC-A + participant 3G-MSC-B_prime as 3G-MSC-B' + participant RNS-B_prime as RNS-B' + + Note right of RNS-A: RELOCATION PREPARATION FAILURE + RNS-A->>3G-MSC-B: RELOCATION PREPARATION FAILURE + 3G-MSC-B->>3G-MSC-A: MAP PREPARE SUBSEQUENT HANDOVER response + 3G-MSC-A->>3G-MSC-B_prime: MAP PREPARE HANDOVER + 3G-MSC-B_prime->>RNS-B_prime: RELOCATION FAILURE + +``` + +Sequence diagram for Figure 62 (Negative outcome) showing a radio resource allocation failure during inter-MSC relocation. + +c) radio resources allocation partial failure (3G\_MSC-A decides to reject the relocation): + +![Sequence diagram for Figure 62 (Partial failure) showing 3G_MSC-A rejecting the relocation.](4540c7355b250cb891be0b54b0ba25c7_img.jpg) + +``` + +sequenceDiagram + participant RNS-A + participant 3G-MSC-B + participant 3G-MSC-A + participant 3G-MSC-B_prime as 3G-MSC-B' + participant RNS-B_prime as RNS-B' + + Note right of RNS-A: RELOCATION PREPARATION FAILURE + RNS-A->>3G-MSC-B: RELOCATION PREPARATION FAILURE + 3G-MSC-B->>3G-MSC-A: MAP PREPARE SUBSEQUENT HANDOVER response + 3G-MSC-A->>3G-MSC-B_prime: MAP PREPARE HANDOVER + 3G-MSC-B_prime->>RNS-B_prime: REQ ACK + Note right of 3G-MSC-A: (Rejects relocation) + +``` + +Sequence diagram for Figure 62 (Partial failure) showing 3G\_MSC-A rejecting the relocation. + +**Figure 62: Signalling for Subsequent Inter-MSC Relocation to third MSC (3G\_MSC-B') execution (Negative outcome)** + +Positive outcome: + +![Sequence diagram for Figure 63 (Successful completion) showing the successful completion of the inter-MSC relocation procedure.](6116b1a533010c170fc526ec513ba0b8_img.jpg) + +``` + +sequenceDiagram + participant RNS-A + participant 3G-MSC-B + participant 3G-MSC-A + participant 3G-MSC-B_prime as 3G-MSC-B' + participant RNS-B_prime as RNS-B' + + Note right of RNS-A: IU RELEASE COMMAND + RNS-A->>3G-MSC-B: IU RELEASE COMMAND + 3G-MSC-B->>3G-MSC-A: MAP SEND END SIGNAL response + 3G-MSC-A->>3G-MSC-B_prime: MAP SEND END SIGNAL request + 3G-MSC-B_prime->>RNS-B_prime: RELOCATION COMPLETE + +``` + +Sequence diagram for Figure 63 (Successful completion) showing the successful completion of the inter-MSC relocation procedure. + +**Figure 63: Signalling for Subsequent Inter-MSC Relocation to third MSC (3G\_MSC-B') completion (Successful completion of the procedure)** + +Negative outcome: + +![Sequence diagram showing the negative outcome of a relocation procedure. Lifelines: RNS-A, 3G-MSC-B, 3G-MSC-A, 3G-MSC-B', and RNS-B'. The sequence starts with RNS-A sending RELOCATION CANCEL to 3G-MSC-B. 3G-MSC-B sends MAP PROCESS ACCESS and SIGNALING request (Note 1) to 3G-MSC-A. 3G-MSC-A sends MAP U -ABORT to 3G-MSC-B'. 3G-MSC-B' sends IU RELEASE COMMAND to RNS-B'. 3G-MSC-B sends RELOCATION CANCEL ACK to RNS-A.](114902bbeea56bda01b64b43fad41920_img.jpg) + +``` + +sequenceDiagram + participant RNS-A + participant 3G-MSC-B + participant 3G-MSC-A + participant 3G-MSC-B' + participant RNS-B' + + Note left of RNS-A: Negative outcome: + RNS-A->>3G-MSC-B: RELOCATION CANCEL + 3G-MSC-B->>3G-MSC-A: MAP PROCESS ACCESS +SIGNALING request (Note 1) + 3G-MSC-A->>3G-MSC-B': MAP U -ABORT + 3G-MSC-B'->>RNS-B': IU RELEASE COMMAND + 3G-MSC-B->>RNS-A: RELOCATION CANCEL ACK + +``` + +Sequence diagram showing the negative outcome of a relocation procedure. Lifelines: RNS-A, 3G-MSC-B, 3G-MSC-A, 3G-MSC-B', and RNS-B'. The sequence starts with RNS-A sending RELOCATION CANCEL to 3G-MSC-B. 3G-MSC-B sends MAP PROCESS ACCESS and SIGNALING request (Note 1) to 3G-MSC-A. 3G-MSC-A sends MAP U -ABORT to 3G-MSC-B'. 3G-MSC-B' sends IU RELEASE COMMAND to RNS-B'. 3G-MSC-B sends RELOCATION CANCEL ACK to RNS-A. + +**Figure 64: Signalling for Subsequent Inter-MSC Relocation to third MSC (3G\_MSC-B') completion (Unsuccessful completion of the procedure)** + +NOTE: Specific interworking case detailed below. + +The specific interworking case in 3G\_MSC-A compared to the subclauses 4.8.1 and 4.8.2 occurs between RELOCATION FAILURE encapsulated in a Process Access Signalling from 3G\_MSC-B and the abortion of the dialogue with 3G\_MSC-B' in the case of relocation cancelled: + +| | 29.002 | 29.002 | Notes | +|-----------------|----------------------------------------------------------------------|----------------|-------| +| Forward message | MAP PROCESS-SIGNALING request
-an-APDU(
RELOCATION CANCEL) | MAP U -ABORT | 1 | +| Positive result | MAP FORWARD-SIGNALING request
-an-APDU(
RELOCATION CANCEL ACK) | | | +| Negative result | | MAP U/P -ABORT | 2 | + +NOTE 1: The abortion of the dialogue triggers in 3G\_MSC-B' the clearing of the circuit connection with 3G\_MSC-A, if any, and of the Resources between 3G\_MSC-B' and RNS-B'. The abortion of the dialogue ends the relocation procedure with 3G\_MSC-B'. + +NOTE 2: The abortion of the dialogue ends the relocation procedure with 3G\_MSC-B. + +### 4.8.4 RANAP Messages transfer on E-Interface + +The following mapping applies to the encapsulation performed in 3G\_MSC-A. + +| | 25.413 | 29.002 | Notes | +|-----------------|----------------|---------------------------------------|-------| +| Forward message | RANAP messages | MAP FORWARD ACCESS SIGNALLING request | 1 | +| Positive result | | -an-APDU (RANAP messages) | 2 | +| Negative result | | MAP CLOSE
MAP U/P -ABORT | | + +NOTE 1: Complete RANAP messages to be sent on 3G\_MSC-B - RNS-B interface are embedded into the an-APDU parameter. + +NOTE 2: The Return Result does not apply. If 3G\_MSC-B returns a message, this message will arrive in an Invoke: Process Access Signalling. + +The following mapping applies to the encapsulation performed in 3G\_MSC-B. + +| | 25.413 | 29.002 | Notes | +|-----------------|-------------------------------------------|---------------------------------------|-------| +| Forward message | RANAP messages | MAP PROCESS ACCESS SIGNALLING request | 1 | +| Positive result | | -an-APDU (RANAP messages) | 2 | +| Negative result | IU RELEASE COMMAND
Unspecified failure | MAP CLOSE
MAP U/P -ABORT | 3 | + +NOTE 1: Complete RANAP messages to be sent to 3G\_MSC-A are embedded into the an-APDU parameter. + +NOTE 2: The Return Result does not apply. If 3G\_MSC-A returns a message, this message will arrive in an Invoke: Forward Access Signalling. + +NOTE 3: The abortion of the dialogue triggers the clearing of the circuit connection with 3G\_MSC-A, if any, of the Radio Resources on the Iu-Interface and the release of the SCCP connection between 3G\_MSC-B and RNS-B. The clearing of the Radio Resources (the clearing indication received from RNS-B is transmitted to 3G\_MSC-A) or the loss of the SCCP connection between 3G\_MSC-B and RNS-B, triggers in 3G\_MSC-B the abortion of the dialogue on the E-Interface and the clearing of the circuit connection with 3G\_MSC-A, if any. + +### 4.8.5 Processing in 3G\_MSC-B, and information transfer on E-interface + +The following parameters require processing (e.g. to store the parameter, to internally generate the parameter) in 3G\_MSC-B. The relevant RANAP procedures are mentioned to ease the comprehension, their detailed description is the scope of the TS 25.413. Each RANAP message being transferred on E-interface shall use the mechanisms given in subclause 4.8.4 and is described in TS 25.413. + +#### 4.8.5.1 Integrity Protection Information + +A sequence of possible integrity protection algorithms can be sent to an RNS in Security Mode Command or Relocation Request. The RNS chooses one of the listed algorithms and reports this back to the 3G\_MSC in Security Mode Complete or Relocation Request Acknowledge respectively. + +3G\_MSC-B shall remove algorithms not allowed by 3G\_MSC-B from the list of algorithms received from 3G\_MSC-A before forwarding it to the RNS. The modified list of algorithms, the integrity protection key and the chosen algorithm shall be stored by 3G\_MSC-B. + +Transfer of Information: + +If integrity protection has not been performed before Inter-MSC Relocation, this will be controlled by 3G\_MSC-A after the completion of Inter-MSC Relocation. + +Integrity protection control towards 3G\_MSC-B: + +- If Integrity protection has been performed before Inter-MSC Relocation: + - - in the Relocation Request RANAP message (information included). +- The Relocation Request Acknowledge should in this case contain the indication of the chosen algorithm. +- If Integrity protection has NOT been performed before Inter-MSC Relocation: + - - in the Security Mode Command procedure between 3G\_MSC-A and 3G\_MSC-B. + +#### 4.8.5.2 Encryption Information + +A sequence of possible encryption algorithms can be sent to an RNS in Security Mode Command or Relocation Request. The RNS chooses one of the listed algorithms and reports this back to the 3G\_MSC in Security Mode Complete or Relocation Request Acknowledge respectively. + +3G\_MSC-B shall remove algorithms not allowed by MSC-B from the list of algorithms received from 3G\_MSC-A before forwarding it to the RNS. The modified list of algorithms, the ciphering key and the chosen algorithm shall be stored by 3G\_MSC-B, and the chosen value sent to 3G\_MSC-A. + +Transfer of Information: + +If ciphering has not been performed before Inter-MSC Relocation, this will be controlled by 3G\_MSC-A after the completion of Inter-MSC Relocation. + +Ciphering control towards 3G\_MSC-B: + +- If Ciphering has been performed before Inter-MSC Relocation: + - - in the Relocation Request RANAP message (information included). +- The Relocation Request Acknowledge should in this case contain the indication of the chosen algorithm. +- If Ciphering has NOT been performed before Inter-MSC Relocation: + - - in the Security Mode Command procedure between 3G\_MSC-A and 3G\_MSC-B. + +#### 4.8.5.3 RAB Parameters + +The parameters shall be stored by 3G\_MSC-B to be used at internal Relocation in 3G\_MSC-B. + +Transfer of information: + +- Received by 3G\_MSC-B from 3G\_MSC-A in: + - The Relocation Request RANAP message. + - If a new type of resource is to be assigned after Inter-MSC Relocation, this can be made with: + - The RAB Assignment Request RANAP message. + +#### 4.8.5.4 Channel Type + +Channel Type is GSM information that is required in BSSMAP Handover Request and BSSMAP Assignment Request, and it shall be provided by 3G\_MSC-A. 3G\_MSC-B needs this information in case of an intra-MSC UMTS to GSM handover after an inter-MSC relocation and subsequent assignment procedures. The Channel Type derived from the Bearer Capability that is available in 3G\_MSC-A. This mapping is described in 3GPP TS 27.001 [8]. Therefore + +3G\_MSC-A must provide this information in case of an inter-MSC relocation. The Radio Resource Information IE in the MAP Prepare Handover message refers to the Channel Type GSM information. + +Channel Type shall be stored by 3G\_MSC-B. + +Transfer of information: + +- Received by 3G\_MSC-B from 3G\_MSC-A in: + - The Prepare Handover Request MAP message. + - The Forward Access Signalling Request message. + +#### 4.8.5.5 Selected GSM Algorithm + +After inter-MSC relocation, the 3G\_MSC-B can perform intra-MSC UMTS to GSM handover. A sequence of possible encryption algorithms, received from the 3G\_MSC-A, can be sent to an BSS in Handover Request or in Cipher Mode Command in case of cipher mode setting after intra-MSC-B handover from UMTS to GSM. The BSS chooses one of the listed algorithms and reports this back to the 3G\_MSC in Handover Request Acknowledge or Cipher Mode Complete respectively. The MSC-B provides the Selected GSM algorithm information to the MSC-A. The Selected GSM algorithms IE in the MAP Process Access Signalling Request message refers to the Algorithm identifier octet in the Chosen Encryption Algorithm GSM information. + +The chosen algorithm shall be stored by 3G\_MSC-B, and sent to 3G\_MSC-A. + +Transfer of Information: + +If ciphering has not been performed before Inter-MSC Relocation, this will be controlled by 3G\_MSC-A after the completion of Inter-MSC Relocation. + +If Ciphering has been performed before Inter-MSC Relocation, Selected GSM algorithm information is received by 3G\_MSC-A from 3G\_MSC-B in: + +- The Handover Performed BSSMAP message. + - If Ciphering has NOT been performed before Intra-MSC-B handover from UMTS to GSM after Inter-MSC Relocation, Selected GSM algorithm information is received by 3G\_MSC-A from 3G\_MSC-B in: +- The Process Access Signalling Request MAP message. + +#### 4.8.5.6 Allowed GSM Algorithms + +Allowed GSM algorithms is GSM information that is required in BSSMAP Handover Request and BSSMAP Cipher Mode Command, and shall be provided by 3G\_MSC-A. 3G\_MSC-B needs this information in case of an intra-MSC UMTS to GSM handover and in subsequent ciphering mode setting, after an inter-MSC relocation. Therefore 3G\_MSC-A must provide this information in case of an inter-MSC relocation. The Allowed GSM algorithms IE in the MAP Prepare Handover and in the MAP Forward Access Signalling Request messages refers to the Algorithm identifier octet in the Permitted Algorithms GSM information. + +Allowed GSM algorithms shall be stored by 3G\_MSC-B. + +Transfer of information: + +If ciphering has not been performed before Inter-MSC Relocation, this will be controlled by 3G\_MSC-A after the completion of Inter-MSC Relocation. + +Ciphering control towards 3G\_MSC-B: + +- If Ciphering has been performed before Inter-MSC Relocation: +- The Prepare Handover Request MAP message. + - If Ciphering has NOT been performed before Inter-MSC Relocation: + +- The Forward Access Signalling Request MAP message. + +#### 4.8.5.7 Chosen Channel + +BSSMAP Assignment Request may give the BSS some freedom in the selection of radio resource (for instance channel rate selection, speech version selection etc.). Chosen Channel and/or Speech Version is reported back to 3G\_MSC-B in BSSMAP Assignment Complete. The Chosen Radio Resource Information IE in the MAP Prepare Handover Response and Process Access Signalling Request messages refers to the Chosen Channel and/or Speech Version GSM information. + +The Channel Type and the characteristics of the chosen channel shall be stored by 3G\_MSC-B, and the Chosen Channel and/or Speech Version information elements shall be transferred to MSC-A or 3G\_MSC-A. + +Transfer of information: + +- Received by MSC-A or 3G\_MSC-A from 3G\_MSC-B in: + - The Prepare Handover Response MAP message + - The Process Access Signalling request MAP message + +#### 4.8.5.8 BSSMAP Service Handover + +This information shall be stored by 3G\_MSC-B and sent to a BSS in Handover Request, when 3G\_MSC-B performs handover to GSM. + +Transfer of information: + +The BSSMAP Service Handover information is transferred to 3G\_MSC-B in: + +- the Prepare Handover Request MAP message. + +If a new assignment of a TCH after an inter-MSC relocation is to be performed, the BSSMAP Service Handover information is transferred to 3G\_MSC-B in: + +- the Forward Access Signalling Request MAP message +- and sent by 3G\_MSC-B to the BSS in the Assignment Request BSSMAP message. + +#### 4.8.5.9 RANAP Service Handover + +This information shall be stored by 3G\_MSC-B and sent to an RNS in Relocation Request during the basic inter-MSC relocation or when 3G\_MSC-B performs a subsequent intra-MSC relocation or handover to UMTS. + +Transfer of information: + +The RANAP Service Handover information is transferred to 3G\_MSC-B in: + +- the Relocation Request RANAP message. + +If a new assignment of a Radio Access Bearer after an inter-MSC relocation is to be performed, the information is transferred to 3G\_MSC-B in: + +- the RANAP RAB Assignment procedure. + +#### 4.8.5.10 GERAN Classmark + +The GERAN Classmark shall be stored by 3G\_MSC-B and can be received from MSC-A, from the serving BSS or serving RNS, or from the target RNS. The GERAN Classmark shall be used together with other parameters, e.g. the Channel Type, for selecting a service and for generating RAB parameters for relocation to GERAN Iu-mode, subsequent relocation or handover to GERAN Iu-mode, and RAB (re-)assignment when the MS is in GERAN Iu-mode. + +Transfer of Information due to GERAN Classmark received from MSC-A: + +Received by 3G\_MSC-B in: + +- - the Prepare Handover Request MAP message. + +Transfer of Information due to GERAN Classmark received from the serving RNS: + +Received by 3G\_MSC-B in: + +- the Handover Required BSSMAP message; +- the Relocation Required RANAP message; +- the Initial UE RANAP message; or +- the RAB Assignment Response RANAP message. + +Transfer of Information due to GERAN Classmark received from the target RNS: + +Received by 3G\_MSC-B in: + +- the Relocation Failure RANAP message. + +#### 4.8.5.11 SNA Access Information + +This information shall be stored by 3G\_MSC-B and sent to an RNS in the Relocation Request message when 3G\_MSC-B performs handover to UMTS. + +Transfer of information: + +The SNA Access Information is transferred to 3G\_MSC-B in: + +- the Relocation Request RANAP message encapsulated in the Prepare Handover request MAP message. + +#### 4.8.5.12 UESBI + +This information shall be stored by 3G\_MSC-B and sent to an RNS in Relocation Request during the basic inter-MSC relocation or when 3G\_MSC-B performs a subsequent intra-MSC relocation or handover to UMTS. + +Transfer of information: + +The UESBI information is transferred to 3G\_MSC-B in: + +- the Relocation Request RANAP message. + +#### 4.8.5.13 Alternative RAB Parameters Value + +This information shall be stored by 3G\_MSC-B and sent to an RNS in Relocation Request during the basic inter-MSC relocation or when 3G\_MSC-B performs a subsequent intra-MSC relocation or handover to UMTS. + +Transfer of information: + +The Alternative RAB Parameters Value information is transferred to 3G\_MSC-B in: + +- the Relocation Request RANAP message. + +If an assignment of a Radio Access Bearer after an inter-MSC relocation is to be performed, the information is transferred to 3G\_MSC-B in: + +- the RAB Assignment Request RANAP message. + +#### 4.8.5.14 Trace parameters + +This information shall be stored by 3G\_MSC-B and 3G\_MSC-B shall use this information for trace activation for MSC-S, MGW, RNC or BSC. + +Transfer of information: + +The Trace Parameter List information for MSC-S, MGW and BSC tracing is transferred to 3G\_MSC-B in: + +- - the Prepare Handover Request MAP message. + +The Trace Propagation Parameter information for RNC tracing is transferred to 3G\_MSC-B in: + +- - the CN Invoke Trace RANAP message. + +### 4.8.6 Overview of the Technical Specifications 3GPP interworking for the Inter-MSC Relocation + +![Protocol stack diagram for UMTS showing layers like RRC, CM, MM, MAP/E, TCAP, SCCP, and MTP across RNS-A, 3G-MSC-A, 3G-MSC-B, RNS-B, and MS components.](de63e4b6d8b0aa76b85e1fe3236eac27_img.jpg) + +The diagram illustrates the protocol stack for a UMTS system, showing the interaction between various network elements. At the top, the PSTN/ISDN and UMTS domains are indicated. The main components shown are RNS-A, 3G-MSC-A, 3G-MSC-B, RNS-B, and MS. The protocol layers are stacked vertically within each component. RNS-A and RNS-B contain RRC, CM, MM, and RR layers. 3G-MSC-A and 3G-MSC-B contain CM, MM, RR, MAP/E, TCAP, SCCP, and MTP layers. The MS contains CM, MM, and RR layers. Interfaces are shown between RNS-A and 3G-MSC-A (25.413), 3G-MSC-A and 3G-MSC-B (25.413), 3G-MSC-B and RNS-B (25.413), and between the RNS/MS and the core network (24.008, 29.010, 29.002, 23.009). Vertical arrows indicate signaling paths between layers within a component. + +Protocol stack diagram for UMTS showing layers like RRC, CM, MM, MAP/E, TCAP, SCCP, and MTP across RNS-A, 3G-MSC-A, 3G-MSC-B, RNS-B, and MS components. + +Remark: The RRC interface and the link layer protocols being out of the scope of this Specification are not shown here. + +## 4.9 Location Services + +The general principles of the location services procedures are given in Technical Specification 3GPP TS 23.271 [16]. + +3GPP TS 29.010 gives the necessary information for interworking between the 3GPP TS 25.413 [7] RANAP protocol and the 3GPP TS 48.008 [12] BSSMAP protocol. The interworking is necessary for positioning requests issued after a completed GSM to UMTS inter system handover. BSSMAP messages carried by MAP over the E-interface must be mapped by the non-anchor 3G-MSC into the corresponding RANAP messages to be sent over the Iu-interface and vice versa. For Inter-MSC GSM to GSM Handover and Inter-MSC UMTS to UMTS SRNS Relocation no mapping between the 3GPP TS 25.413 [7] RANAP protocol and the 3GPP TS 48.008 [12] BSSMAP protocol is necessary, but only the interworking with the MAP protocol over the E-interface needs to be described. + +### 4.9.1 Completed Location Acquisition + +#### 4.9.1.1 Inter-MSC Handover (GSM to GSM) + +After a successful Inter-MSC handover, any positioning request received by the anchor MSC via the MAP message Provide Subscriber Location triggers the BSSMAP procedure Location Acquisition described in 3GPP TS 48.008 [12]. For handover this procedure is executed according to GSM 3GPP TS 49.008 [14] with the anchor MSC playing the role of the MSC and the non anchor MSC playing the role of the BSS. + +The needed BSSMAP signalling is sent over the E-interface encapsulated in the MAP messages Process Access Signalling and Forward Access Signalling. + +At the non anchor MSC the BSSMAP messages received from the anchor MSC are forwarded to the BSS, and the BSSMAP messages received from the BSS are sent over the E-interface to the anchor MSC. + +The signalling for a completed Location Acquisition procedure is shown in figures 65a. + +![Sequence diagram for a completed Location Acquisition procedure. Lifelines: GMLC, MSC-A, MSC-B, BSS-B. The sequence starts with GMLC sending MAP PROVIDE SUBSCRIBER LOCATION to MSC-A. MSC-A sends MAP FORWARD ACCESS SIGNALLING to MSC-B, containing an an-APDU (PERFORM LOCATION REQUEST). MSC-B sends a dashed PERFORM LOCATION REQUEST to BSS-B. A box labeled 'Positioning is performed' is shown between MSC-B and BSS-B. MSC-B then sends a dashed PERFORM LOCATION RESPONSE back to BSS-B. MSC-B sends MAP PROCESS ACCESS SIGNALLING to MSC-A, containing an an-APDU (PERFORM LOCATION RESPONSE). Finally, GMLC receives a dashed MAP PROVIDE SUBSCRIBER LOCATION res from MSC-A.](c0ca823603794512478906b302176bca_img.jpg) + +``` + +sequenceDiagram + participant GMLC + participant MSC-A + participant MSC-B + participant BSS-B + + Note right of GMLC: Error: Reference source not + GMLC->>MSC-A: MAP PROVIDE SUBSCRIBER LOCATION + MSC-A->>MSC-B: MAP FORWARD ACCESS SIGNALLING +-an-APDU (PERFORM LOCATION REQUEST) + MSC-B->>BSS-B: PERFORM LOCATION REQUEST + Note right of BSS-B: Positioning is performed + BSS-B-->>MSC-B: PERFORM LOCATION RESPONSE + MSC-B->>MSC-A: MAP PROCESS ACCESS SIGNALLING +-an-APDU (PERFORM LOCATION RESPONSE) + MSC-A-->>GMLC: MAP PROVIDE SUBSCRIBER LOCATION res + +``` + +Sequence diagram for a completed Location Acquisition procedure. Lifelines: GMLC, MSC-A, MSC-B, BSS-B. The sequence starts with GMLC sending MAP PROVIDE SUBSCRIBER LOCATION to MSC-A. MSC-A sends MAP FORWARD ACCESS SIGNALLING to MSC-B, containing an an-APDU (PERFORM LOCATION REQUEST). MSC-B sends a dashed PERFORM LOCATION REQUEST to BSS-B. A box labeled 'Positioning is performed' is shown between MSC-B and BSS-B. MSC-B then sends a dashed PERFORM LOCATION RESPONSE back to BSS-B. MSC-B sends MAP PROCESS ACCESS SIGNALLING to MSC-A, containing an an-APDU (PERFORM LOCATION RESPONSE). Finally, GMLC receives a dashed MAP PROVIDE SUBSCRIBER LOCATION res from MSC-A. + +**Figure 65a: Signalling for a completed Location Acquisition procedure** + +After the inter-MSC handover, the MSC-B can perform intra-MSC GSM to UMTS handover. Any positioning request received by the anchor MSC after completion of the intra-MSC GSM to UMTS handover is handled as for Inter-MSC Handover GSM to UMTS (see section 4.9.1.2). + +#### 4.9.1.2 Inter-MSC Handover (GSM to UMTS) + +After a successful Inter-MSC GSM to UMTS inter system handover, any positioning request received by the anchor MSC via the MAP message Provide Subscriber Location triggers the BSSMAP procedure Location Acquisition described in 3GPP TS 48.008 [12]. For handover this procedure is executed according to 3GPP TS 49.008 [14] with the anchor MSC playing the role of the MSC and the non anchor 3G MSC playing the role of the BSS. + +The needed BSSMAP signalling is sent over the E-interface encapsulated in the MAP messages Process Access Signalling and Forward Access Signalling. + +At the non anchor 3G MSC the BSSMAP messages received from the anchor MSC are mapped into the corresponding RANAP messages to be sent to the RNS, and the received RANAP messages are mapped into the corresponding BSSMAP messages to be sent over the E-interface to the anchor MSC. + +The signalling for a completed Location Acquisition procedure is shown in figures 65b. + +![Sequence diagram showing signalling for a completed Location Acquisition procedure between GMLC, MSC-A, 3G-MSC-B, and RNS-B.](fc3e2b49a9f850951570e502393b697f_img.jpg) + +``` +sequenceDiagram + participant GMLC + participant MSC-A + participant 3G-MSC-B + participant RNS-B + + Note right of GMLC: Error: Reference source not + GMLC->>MSC-A: MAP PROVIDE SUBSCRIBER LOCATION + MSC-A->>3G-MSC-B: MAP FORWARD ACCESS SIGNALLING + Note right of 3G-MSC-B: -an-APDU( PERFORM LOCATION REQUEST) + 3G-MSC-B->>RNS-B: LOCATION REPORTING CONTROL + Note right of RNS-B: Positioning is performed + RNS-B->>3G-MSC-B: LOCATION REPORT + 3G-MSC-B->>MSC-A: MAP PROCESS ACCESS SIGNALLING + Note right of MSC-A: -an-APDU( PERFORM LOCATION RESPONSE) + MSC-A->>GMLC: MAP PROVIDE SUBSCRIBER LOCATION res +``` + +The sequence diagram illustrates the signalling for a completed Location Acquisition procedure. It involves four main entities: GMLC, MSC-A, 3G-MSC-B, and RNS-B. The process begins with GMLC sending a 'MAP PROVIDE SUBSCRIBER LOCATION' message to MSC-A. MSC-A responds with 'MAP FORWARD ACCESS SIGNALLING' to 3G-MSC-B, which includes an '-an-APDU( PERFORM LOCATION REQUEST)'. 3G-MSC-B then sends a 'LOCATION REPORTING CONTROL' message to RNS-B. RNS-B performs positioning and returns a 'LOCATION REPORT' to 3G-MSC-B. 3G-MSC-B sends 'MAP PROCESS ACCESS SIGNALLING' back to MSC-A, containing an '-an-APDU( PERFORM LOCATION RESPONSE)'. Finally, MSC-A sends a 'MAP PROVIDE SUBSCRIBER LOCATION res' message back to GMLC. A note on the right side of the GMLC lifeline indicates 'Error: Reference source not'. A dashed box around the 'Positioning is performed' message indicates a specific step in the RNS-B entity. + +Sequence diagram showing signalling for a completed Location Acquisition procedure between GMLC, MSC-A, 3G-MSC-B, and RNS-B. + +Figure 65b: Signalling for a completed Location Acquisition procedure + +The interworking between the BSSMAP location acquisition messages in MAP and the RANAP location reporting messages is as follows: + +| | 29.002 | 25.413 | Notes | +|-----------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------|-------| +| Forward message | MAP FORWARD ACCESS SIG.
request

-an-APDU(
PERFORM LOCATION REQUEST)

BSSMAP information elements:      RANAP information elements:

Location Type                              Request Type
>Current Geographic                  >Event = Direct
Location                                      >Report Area =
Geo. Coord.

Cell Identifier                              ----
Classmark Inf. Type3                  ----
LCS Client Type                          ----
Chosen Channel                          ----
LCS Priority                              ----
LCS QoS                                      Request Type
>Horizontal Accuracy                  >Accuracy Code

GPS Assistance Data                  ----
APDU                                          ---- | | 1 | +| Result | MAP PROCESS ACCESS SIG.
request
-an-APDU(
PERFORM LOCATION RESPONSE)

BSSMAP information elements:      RANAP information elements:

Location Estimate                      Area Identity
>Geographical Area
Positioning Data                      ----
Deciphering Keys                    ----
LCS Cause                              Cause
----                                          Request Type | | | + +NOTE 1: All other Location Type possibilities are not supported by UMTS positioning + +After the inter-MSC GSM to UMTS handover, the 3G MSC-B can perform intra-MSC UMTS to GSM handover. Any positioning request received by the anchor MSC after completion of the intra-MSC UMTS to GSM handover is handled as for Inter-MSC Handover GSM to GSM (see section 4.9.1.1). + +#### 4.9.1.3 Inter-MSC Handover (UMTS to GSM) + +After a successful Inter-MSC UMTS to GSM inter system handover, any positioning request received by the anchor 3G-MSC via the MAP message Provide Subscriber Location triggers the BSSMAP procedure Location Acquisition described in 3GPP TS 48.008 [12]. For handover this procedure is executed according to 3GPP TS 49.008 [14] with the anchor 3G-MSC playing the role of the 3G-MSC and the non anchor MSC playing the role of the BSS. + +The needed BSSMAP signalling is sent over the E-interface encapsulated in the MAP messages Process Access Signalling and Forward Access Signalling. + +At the non anchor MSC the BSSMAP messages received from the anchor 3G-MSC are forwarded to the BSS, and the BSSMAP messages received from the BSS are sent over the E-interface to the anchor 3G-MSC. + +The signalling for a completed Location Acquisition procedure is shown in figures 65c. + +![Sequence diagram for a completed Location Acquisition procedure. Lifelines: GMLC, 3G-MSC-A, MSC-B, and BSS-B. The procedure involves MAP messages and RANAP signaling between these entities.](d04c50badc78d5ba47bf4e352af4a754_img.jpg) + +``` + +sequenceDiagram + participant GMLC + participant 3G-MSC-A + participant MSC-B + participant BSS-B + + Note right of GMLC: Error: Reference source not + GMLC->>3G-MSC-A: MAP PROVIDE SUBSCRIBER LOCATION + 3G-MSC-A->>MSC-B: MAP FORWARD ACCESS SIGNALLING +-an-APDU (PERFORM LOCATION REQUEST) + MSC-B->>BSS-B: PERFORM LOCATION REQUEST + Note right of BSS-B: Positioning is performed + BSS-B->>MSC-B: PERFORM LOCATION RESPONSE + MSC-B->>3G-MSC-A: MAP PROCESS ACCESS SIGNALLING +-an-APDU (PERFORM LOCATION RESPONSE) + 3G-MSC-A->>GMLC: MAP PROVIDE SUBSCRIBER LOCATION res + +``` + +Sequence diagram for a completed Location Acquisition procedure. Lifelines: GMLC, 3G-MSC-A, MSC-B, and BSS-B. The procedure involves MAP messages and RANAP signaling between these entities. + +**Figure 65c: Signalling for a completed Location Acquisition procedure** + +After the inter-MSC UMTS to GSM handover, the 3G MSC-B can perform intra-MSC GSM to UMTS handover. Any positioning request received by the anchor 3G MSC after completion of the intra-MSC GSM to UMTS handover is handled as for Inter-MSC Handover GSM to UMTS (see section 4.9.1.2). + +#### 4.9.1.4 Inter-MSC SRNS Relocation + +After a successful Inter-MSC SRNS Relocation, any positioning request received by the anchor 3G-MSC via the MAP message Provide Subscriber Location triggers the RANAP procedure Location Reporting Control described in TS 25.413. For handover this procedure is executed according to 23.009 with the anchor 3G-MSC playing the role of the 3G-MSC and the non anchor 3G-MSC playing the role of the RNS. + +The needed RANAP signalling is sent over the E-interface encapsulated in the MAP messages Process Access Signalling and Forward Access Signalling. + +At the non anchor 3G-MSC the RANAP messages received from the anchor 3G-MSC are forwarded to the RNS, and the RANAP messages received from the RNS are sent over the E-interface to the anchor 3G-MSC. + +The signalling for a completed Location Acquisition procedure is shown in figures 65d. + +![Sequence diagram showing signalling for a completed Location Acquisition procedure between GMLC, 3G-MSC-A, 3G-MSC-B, and RNS-B.](e18841eb4a995df8354a793459e12fd0_img.jpg) + +``` +sequenceDiagram + participant GMLC + participant 3G-MSC-A + participant 3G-MSC-B + participant RNS-B + + Note right of GMLC: Error: Reference source not + GMLC->>3G-MSC-A: MAP PROVIDE SUBSCRIBER LOCATION + 3G-MSC-A->>3G-MSC-B: MAP FORWARD ACCESS SIGNALLING + Note right of 3G-MSC-A: -an-APDU ( LOCATION REPORTING CONTROL) + 3G-MSC-B->>RNS-B: LOCATION REPORTING CONTROL + Note right of RNS-B: Positioning is performed + RNS-B->>3G-MSC-B: LOCATION REPORT + 3G-MSC-B->>3G-MSC-A: MAP PROCESS ACCESS SIGNALLING + Note right of 3G-MSC-B: -an-APDU ( LOCATION REPORT) + 3G-MSC-A->>GMLC: MAP PROVIDE SUBSCRIBER LOCATION res +``` + +The diagram illustrates the signalling sequence for a completed Location Acquisition procedure. It involves four main entities: GMLC, 3G-MSC-A, 3G-MSC-B, and RNS-B. The sequence begins with GMLC sending a 'MAP PROVIDE SUBSCRIBER LOCATION' message to 3G-MSC-A. 3G-MSC-A responds with 'MAP FORWARD ACCESS SIGNALLING' to 3G-MSC-B, which includes an '-an-APDU ( LOCATION REPORTING CONTROL)'. 3G-MSC-B then sends a 'LOCATION REPORTING CONTROL' message to RNS-B. RNS-B performs positioning and returns a 'LOCATION REPORT' to 3G-MSC-B. 3G-MSC-B processes this with 'MAP PROCESS ACCESS SIGNALLING' and an '-an-APDU ( LOCATION REPORT)' before finally sending a 'MAP PROVIDE SUBSCRIBER LOCATION res' response back to GMLC. A note on the right side of the GMLC lifeline indicates 'Error: Reference source not'. + +Sequence diagram showing signalling for a completed Location Acquisition procedure between GMLC, 3G-MSC-A, 3G-MSC-B, and RNS-B. + +Figure 65d: Signalling for a completed Location Acquisition procedure + +After the inter-MSC SRNS Relocation, the 3G MSC-B can perform intra-MSC UMTS to GSM handover. Any positioning request received by the anchor 3G MSC after completion of the intra-MSC UMTS to GSM requires that at the non anchor 3G MSC the received RANAP messages are mapped into the corresponding BSSMAP messages to be sent to the BSS, and the received BSSMAP messages are mapped into the corresponding RANAP messages to be sent over the E-interface to the anchor 3G-MSC. + +The signalling for a completed Location Acquisition procedure is shown in figures 65e. + +![Sequence diagram showing signalling for a completed Location Acquisition procedure between GMLC, 3G-MSC-A, 3G-MSC-B, and BSS-B.](199a8b4c5c620006757a17e930769566_img.jpg) + +``` +sequenceDiagram + participant GMLC + participant 3G-MSC-A + participant 3G-MSC-B + participant BSS-B + + Note left of GMLC: MAP PROVIDE SUBSCRIBER LOCATION + GMLC-->>3G-MSC-A: MAP FORWARD ACCESS SIGNALLING + Note right of 3G-MSC-A: -an-APDU( LOCATION REPORTING CONTROL) + 3G-MSC-A-->>3G-MSC-B: + Note right of 3G-MSC-B: PERFORM LOCATION REQUEST + 3G-MSC-B-->>BSS-B: + Note right of BSS-B: Positioning is performed + BSS-B-->>3G-MSC-B: + Note right of 3G-MSC-B: PERFORM LOCATION RESPONSE + 3G-MSC-B-->>3G-MSC-A: MAP PROCESS ACCESS SIGNALLING + Note right of 3G-MSC-A: -an-APDU( LOCATION REPORT) + 3G-MSC-A-->>GMLC: + Note left of GMLC: MAP PROVIDE SUBSCRIBER LOCATION res +``` + +The diagram illustrates the signalling flow for a completed Location Acquisition procedure. It involves four main entities: GMLC, 3G-MSC-A, 3G-MSC-B, and BSS-B. The sequence starts with GMLC sending a 'MAP PROVIDE SUBSCRIBER LOCATION' message to 3G-MSC-A. 3G-MSC-A responds with 'MAP FORWARD ACCESS SIGNALLING', which contains an '-an-APDU( LOCATION REPORTING CONTROL)'. This message is then forwarded to 3G-MSC-B. 3G-MSC-B sends a 'PERFORM LOCATION REQUEST' to BSS-B. BSS-B performs the positioning and returns a response. 3G-MSC-B then sends a 'PERFORM LOCATION RESPONSE' back to 3G-MSC-A. 3G-MSC-A processes this with 'MAP PROCESS ACCESS SIGNALLING', containing an '-an-APDU( LOCATION REPORT)'. Finally, 3G-MSC-A sends a 'MAP PROVIDE SUBSCRIBER LOCATION res' back to GMLC. + +Sequence diagram showing signalling for a completed Location Acquisition procedure between GMLC, 3G-MSC-A, 3G-MSC-B, and BSS-B. + +Figure 65e: Signalling for a completed Location Acquisition procedure + +the interworking between the RANAP messages encapsulated in MAP and the BSSMAP messages is as follows: + +| | 29.002 | 48.008 | Notes | +|-----------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------|-------| +| Forward message | MAP FORWARD ACCESS SIG.
request

-an-APDU(
LOCATION REPORTING CONTROL)

RANAP information elements:

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

Request Type
>Accuracy Code | PERFORM LOCATION REQUEST


BSSMAP information elements:

Location Type
>Current Geographic Location

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

-an-APDU(
LOCATION REPORT)

RANAP information elements:

Area Identity
>Geographical Area

Cause
Request Type | PERFORM LOCATION RESPONSE


BSSMAP information elements:

Location Estimate

LCS Cause
---- | | + +### 4.9.2 Cause Code Mapping + +#### 4.9.2.1 Inter-MSC Handover (GSM to GSM) + +When a mobile station is handed over from GSM to GSM, no mapping of cause codes is required. The MSC shall use the cause codes specified in 3GPP TS 48.008 [12]. + +After the inter-MSC handover, the MSC-B can perform intra-MSC GSM to UMTS handover. A mapping of the cause codes used in the RANAP and the BSSMAP protocols is needed after completion of the intra-MSC GSM to UMTS handover and is the same as for Inter-MSC Handover GSM to UMTS (see section 4.9.2.2).. + +#### 4.9.2.2 Inter-MSC Handover (GSM to UMTS) + +When a Mobile Station is handed over between GSM and UMTS, a mapping of the cause codes used in the RANAP and the BSSMAP protocols is needed. The mapping described here is applicable to the BSSMAP protocol even when used inside MAP in the E-interface. + +The mapping between the cause codes received in RANAP Location Report and the LCS cause codes sent in BSSMAP Perform Location Response is as follows: + +| 25.413 | 48.008 | Notes | +|---------------------------------------|---------------------------|-------| +| LOCATION REPORT | PERFORM LOCATION RESPONSE | | +| - Requested Report Type not Supported | - Position method failure | | +| - Requested Information not Available | - Position method failure | | +| - all other cause codes | - System Failure | | + +After the inter-MSC GSM to UMTS handover, the 3G MSC-B can perform intra-MSC UMTS to GSM handover. No mapping of cause codes is required after completion of the intra-MSC UMTS to GSM handover as for Inter-MSC Handover GSM to GSM (see section 4.9.2.1). + +#### 4.9.2.3 Inter-MSC Handover (UMTS to GSM) + +When a mobile station is handed over from UMTS to GSM, no mapping of cause codes is required. The 3G-MSC shall use the cause codes specified in 3GPP TS 48.008 [12]. + +After the inter-MSC UMTS to GSM handover, the 3G MSC-B can perform intra-MSC GSM to UMTS handover. A mapping of the cause codes used in the RANAP and the BSSMAP protocols is needed after completion of the intra-MSC GSM to UMTS handover and is the same as for Inter-MSC Handover GSM to UMTS (see section 4.9.2.2)... + +#### 4.9.2.4 Inter-MSC SRNS Relocation + +When a mobile station is handed over from UMTS to UMTS, no mapping of cause codes is required. Both 3G-MSCs shall use the cause codes specified in TS 25.413. + +After the inter-MSC SRNS Relocation, the 3G MSC-B can perform intra-MSC UMTS to GSM handover. A mapping of the cause codes used in the RANAP and the BSSMAP protocols is needed after completion of the intra-MSC UMTS to GSM handover. + +The mapping between the cause codes received in BSSMAP Perform Location Response and the LCS cause codes sent in RANAP Location Report is as follows: + +| 48.008 | 25.413 | Notes | +|---------------------------------------------|---------------------------------------|-------| +| PERFORM LOCATION RESPONSE | LOCATION REPORT | | +| - Position method failure | - Requested Report Type not Supported | | +| - System Failure | - Unspecified Failure | | +| - Protocol Error | - Unspecified Failure | | +| - Data missing in position request | - Unspecified Failure | | +| - Unexpected data value in position request | - Unspecified Failure | | +| - Target MS Unreachable | - Unspecified Failure | | +| - Location request aborted | - Unspecified Failure | | +| - Facility not supported | - Requested Report Type not Supported | | +| - Inter-BSC Handover Ongoing | - Unspecified Failure | | +| - Intra-BSC Handover Complete | - Unspecified Failure | | +| - Congestion | - Unspecified Failure | | +| - Unspecified | - Unspecified Failure | | + +### 4.9.3 Aborted Location Acquisition + +#### 4.9.3.1 Inter-MSC Handover (GSM to GSM) + +When for any reason the on going location acquisition procedure needs to be aborted, the anchor MSC sends the BSSMAP message Perform Location Abort over the E-interface. + +Figure 66a shows the signalling for an aborted Location Acquisition procedure. + +![Sequence diagram showing signalling for an aborted Location Acquisition procedure between GMLC, MSC-A, MSC-B, and BSS-B.](a5404b7275b06497eecf9b5883604753_img.jpg) + +``` +sequenceDiagram + participant GMLC + participant MSC-A + participant MSC-B + participant BSS-B + + Note left of GMLC: Error: Reference source not + GMLC->>MSC-A: MAP PROVIDE SUBSCRIBER LOCATION + MSC-A->>MSC-B: MAP FORWARD ACCESS SIGNALLING + Note right of MSC-A: -an-APDU( PERFORM LOCATION REQUEST) + MSC-B->>BSS-B: PERFORM LOCATION REQUEST + Note right of MSC-A: MAP FORWARD ACCESS SIGNALLING + Note right of MSC-A: -an-APDU( PERFORM LOCATION ABORT) + MSC-B->>BSS-B: PERFORM LOCATION ABORT + BSS-B->>MSC-B: PERFORM LOCATION RESPONSE + MSC-B->>MSC-A: MAP PROCESS ACCESS SIGNALLING + Note right of MSC-A: -an-APDU( PERFORM LOCATION RESPONSE) +``` + +The sequence diagram illustrates the signalling for an aborted Location Acquisition procedure. It involves four participants: GMLC, MSC-A, MSC-B, and BSS-B. The sequence of messages is as follows: 1. GMLC sends a 'MAP PROVIDE SUBSCRIBER LOCATION' message to MSC-A. 2. MSC-A sends a 'MAP FORWARD ACCESS SIGNALLING' message to MSC-B, containing an 'an-APDU( PERFORM LOCATION REQUEST)'. 3. MSC-B sends a 'PERFORM LOCATION REQUEST' message to BSS-B. 4. MSC-A sends another 'MAP FORWARD ACCESS SIGNALLING' message to MSC-B, containing an 'an-APDU( PERFORM LOCATION ABORT)'. 5. MSC-B sends a 'PERFORM LOCATION ABORT' message to BSS-B. 6. BSS-B sends a 'PERFORM LOCATION RESPONSE' message back to MSC-B. 7. MSC-B sends a 'MAP PROCESS ACCESS SIGNALLING' message to MSC-A, containing an 'an-APDU( PERFORM LOCATION RESPONSE)'. + +Sequence diagram showing signalling for an aborted Location Acquisition procedure between GMLC, MSC-A, MSC-B, and BSS-B. + +Figure 66a: Signalling for an aborted Location Acquisition procedure + +After the inter-MSC handover, the MSC-B can perform intra-MSC GSM to UMTS handover. A positioning request that needs to be aborted by the anchor MSC after completion of the intra-MSC GSM to UMTS handover is handled as for Inter-MSC Handover GSM to UMTS (see section 4.9.3.2). + +#### 4.9.3.2 Inter-MSC Handover (GSM to UMTS) + +When for any reason the on going location acquisition procedure needs to be aborted, the anchor MSC sends the BSSMAP message Perform Location Abort over the E-interface. + +Figure 66b shows the signalling for an aborted Location Acquisition procedure. + +![Sequence diagram showing signalling for an aborted Location Acquisition procedure between GMLC, MSC-A, 3G-MSC-B, and RNS-B.](a7450c80e88ad3f6ca1427ad84020998_img.jpg) + +``` +sequenceDiagram + participant GMLC + participant MSC-A + participant 3G-MSC-B + participant RNS-B + + Note left of GMLC: MAP PROVIDE SUBSCRIBER LOCATION + GMLC-->>MSC-A: MAP FORWARD ACCESS SIGNALLING + Note right of MSC-A: -an-APDU( PERFORM LOCATION REQUEST) + MSC-A-->>3G-MSC-B: MAP FORWARD ACCESS SIGNALLING + Note right of 3G-MSC-B: LOCATION REPORTING CONTROL + 3G-MSC-B-->>RNS-B: LOCATION REPORTING CONTROL + Note right of RNS-B: LOCATION REPORT + RNS-B-->>3G-MSC-B: LOCATION REPORT + Note right of 3G-MSC-B: MAP PROCESS ACCESS SIGNALLING + 3G-MSC-B-->>MSC-A: MAP PROCESS ACCESS SIGNALLING + Note right of MSC-A: -an-APDU( PERFORM LOCATION RESPONSE) +``` + +The sequence diagram illustrates the signalling for an aborted Location Acquisition procedure. It involves four participants: GMLC, MSC-A, 3G-MSC-B, and RNS-B. The process begins with GMLC sending a 'MAP PROVIDE SUBSCRIBER LOCATION' message to MSC-A. MSC-A responds with 'MAP FORWARD ACCESS SIGNALLING' containing an '-an-APDU( PERFORM LOCATION REQUEST)'. This is forwarded by 3G-MSC-B to RNS-B via 'LOCATION REPORTING CONTROL'. RNS-B sends a 'LOCATION REPORT' back to 3G-MSC-B. 3G-MSC-B then sends 'MAP PROCESS ACCESS SIGNALLING' back to MSC-A, which contains an '-an-APDU( PERFORM LOCATION RESPONSE)'. + +Sequence diagram showing signalling for an aborted Location Acquisition procedure between GMLC, MSC-A, 3G-MSC-B, and RNS-B. + +**Figure 66b: Signalling for an aborted Location Acquisition procedure** + +The interworking between the BSSMAP location acquisition messages in MAP and the RANAP location reporting messages is as follows: + +| | 29.002 | 25.413 | Notes | +|-----------------|----------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------|-------| +| Forward message | MAP FORWARD ACCESS SIG.
request

-an-APDU(
PERFORM LOCATION ABORT)

BSSMAP information elements:

LCS Cause | LOCATION REPORTING CONTROL

RANAP information elements:

Request Type
>Event = Stop
>Report Area =
Geo. Coord. | | +| Result | MAP PROCESS ACCESS SIG.
request
-an-APDU(
PERFORM LOCATION RESPONSE)

BSSMAP information elements:

----
LCS Cause
---- | LOCATION REPORT

RANAP information elements:

Cause | 1 | + +NOTE 1: PERFORM LOCATION RESPONSE with LCS cause shall be generated by 3G-MSC-B. + +After the inter-MSC GSM to UMTS handover, the 3G MSC-B can perform intra-MSC UMTS to GSM handover. A positioning request that needs to be aborted by the anchor MSC after completion of the intra-MSC UMTS to GSM handover is handled as for Inter-MSC Handover GSM to GSM (see section 4.9.3.1). + +#### 4.9.3.3 Inter-MSC Handover (UMTS to GSM) + +When for any reason the on going location acquisition procedure needs to be aborted, the anchor 3G-MSC sends the BSSMAP message Perform Location Abort over the E-interface. + +Figure 66c shows the signalling for an aborted Location Acquisition procedure. + +![Sequence diagram showing signalling for an aborted Location Acquisition procedure between GMLC, 3G-MSC-A, MSC-B, and BSS-B.](17431d8b59408f09df7552d8bdbaa015_img.jpg) + +``` +sequenceDiagram + participant GMLC + participant 3G-MSC-A + participant MSC-B + participant BSS-B + + GMLC->>3G-MSC-A: MAP PROVIDE SUBSCRIBER LOCATION + 3G-MSC-A->>MSC-B: MAP FORWARD ACCESS SIGNALLING +-an-APDU( PERFORM LOCATION REQUEST) + MSC-B->>BSS-B: PERFORM LOCATION REQUEST + 3G-MSC-A->>MSC-B: MAP FORWARD ACCESS SIGNALLING +-an-APDU( PERFORM LOCATION ABORT) + MSC-B->>BSS-B: PERFORM LOCATION ABORT + BSS-B-->>MSC-B: PERFORM LOCATION RESPONSE + MSC-B-->>3G-MSC-A: MAP PROCESS ACCESS SIGNALLING +-an-APDU( PERFORM LOCATION RESPONSE) +``` + +The sequence diagram illustrates the signalling for an aborted Location Acquisition procedure. It involves four participants: GMLC, 3G-MSC-A, MSC-B, and BSS-B. The process begins with GMLC sending a MAP PROVIDE SUBSCRIBER LOCATION message to 3G-MSC-A. 3G-MSC-A then sends a MAP FORWARD ACCESS SIGNALLING message containing an -an-APDU( PERFORM LOCATION REQUEST) to MSC-B. MSC-B forwards the PERFORM LOCATION REQUEST to BSS-B. Later, 3G-MSC-A sends another MAP FORWARD ACCESS SIGNALLING message containing an -an-APDU( PERFORM LOCATION ABORT) to MSC-B, which then sends a PERFORM LOCATION ABORT to BSS-B. BSS-B responds to MSC-B with a PERFORM LOCATION RESPONSE. Finally, MSC-B sends a MAP PROCESS ACCESS SIGNALLING message containing an -an-APDU( PERFORM LOCATION RESPONSE) back to 3G-MSC-A. + +Sequence diagram showing signalling for an aborted Location Acquisition procedure between GMLC, 3G-MSC-A, MSC-B, and BSS-B. + +**Figure 66c: Signalling for an aborted Location Acquisition procedure** + +After the inter-MSC UMTS to GSM handover, the 3G MSC-B can perform intra-MSC GSM to UMTS handover. A positioning request that needs to be aborted by the anchor 3G MSC after completion of the intra-MSC GSM to UMTS handover is handled as for Inter-MSC Handover GSM to UMTS (see section 4.9.3.2).. + +#### 4.9.3.4 Inter-MSC SRNS Relocation + +When for any reason the on going location acquisition procedure needs to be aborted, the anchor 3G-MSC sends the RANAP message Location Reporting Control over the E-interface. + +**Figure 66d shows the signalling for an aborted Location Acquisition procedure.**![Sequence diagram showing signalling for an aborted Location Acquisition procedure between GMLC, 3G-MSC-A, 3G-MSC-B, and RNS-B.](276d5f4022bc6b9e4687f9ba4fc7594c_img.jpg) + +``` +sequenceDiagram + participant GMLC + participant 3G-MSC-A + participant 3G-MSC-B + participant RNS-B + + Note left of GMLC: MAP PROVIDE SUBSCRIBER LOCATION + GMLC-->>3G-MSC-A: MAP FORWARD ACCESS SIGNALLING + Note right of 3G-MSC-A: -an-APDU ( LOCATION REPORTING CONTROL) + 3G-MSC-A-->>3G-MSC-B: MAP FORWARD ACCESS SIGNALLING + Note right of 3G-MSC-B: LOCATION REPORTING CONTROL + 3G-MSC-B-->>RNS-B: LOCATION REPORTING CONTROL + Note right of 3G-MSC-B: LOCATION REPORTING CONTROL = STOP DIRECT + RNS-B-->>3G-MSC-B: LOCATION REPORT + 3G-MSC-B-->>3G-MSC-A: MAP PROCESS ACCESS SIGNALLING + Note right of 3G-MSC-A: -an-APDU ( LOCATION REPORT) +``` + +The diagram illustrates the signalling sequence for an aborted Location Acquisition procedure. It involves four entities: GMLC, 3G-MSC-A, 3G-MSC-B, and RNS-B. The sequence starts with GMLC sending a MAP PROVIDE SUBSCRIBER LOCATION message to 3G-MSC-A. 3G-MSC-A then sends a MAP FORWARD ACCESS SIGNALLING message to 3G-MSC-B, containing an -an-APDU with LOCATION REPORTING CONTROL. 3G-MSC-B receives this and sends a LOCATION REPORTING CONTROL message to RNS-B. 3G-MSC-B also sends a MAP FORWARD ACCESS SIGNALLING message to 3G-MSC-A, containing an -an-APDU with LOCATION REPORTING CONTROL = STOP. RNS-B receives the LOCATION REPORTING CONTROL message and sends a LOCATION REPORT message back to 3G-MSC-B. 3G-MSC-B then sends a MAP PROCESS ACCESS SIGNALLING message to 3G-MSC-A, containing an -an-APDU with LOCATION REPORT. + +Sequence diagram showing signalling for an aborted Location Acquisition procedure between GMLC, 3G-MSC-A, 3G-MSC-B, and RNS-B. + +**Figure 66d: Signalling for an aborted Location Acquisition procedure** + +After the inter-MSC SRNS Relocation, the 3G MSC-B can perform intra-MSC UMTS to GSM handover. A positioning request that needs to be aborted by the anchor 3G MSC after completion of the intra-MSC UMTS to GSM requires that at the non anchor 3G MSC the received RANAP messages are mapped into the corresponding BSSMAP messages to be sent to the BSS, and the received BSSMAP messages are mapped into the corresponding RANAP messages to be sent over the E-interface to the anchor 3G-MSC. + +The signalling for a completed Location Acquisition procedure is shown in figures 65e. + +![Sequence diagram showing signalling for an aborted Location Acquisition procedure between GMLC, 3G-MSC-A, 3G-MSC-B, and BSS-B.](54159e6d8f5ecc73ad262758e3a60677_img.jpg) + +``` + +sequenceDiagram + participant GMLC + participant 3G-MSC-A + participant 3G-MSC-B + participant BSS-B + + Note over GMLC: MAP PROVIDE +SUBSCRIBER +LOCATION + GMLC->>3G-MSC-A: + 3G-MSC-A->>3G-MSC-B: MAP FORWARD ACCESS +SIGNALLING + Note right of 3G-MSC-A: -an-APDU( +LOCATION REPORTING +CONTROL) + 3G-MSC-B->>BSS-B: + BSS-B-->>3G-MSC-B: PERFORM LOCATION +ABORT + 3G-MSC-B->>BSS-B: + BSS-B-->>3G-MSC-B: PERFORM LOCATION +RESPONSE + 3G-MSC-B->>3G-MSC-A: MAP PROCESS ACCESS +SIGNALLING + Note right of 3G-MSC-A: -an-APDU( +LOCATION REPORT) + 3G-MSC-A->>GMLC: + Note over GMLC: MAP PROVIDE +SUBSCRIBER +LOCATION res + +``` + +The sequence diagram illustrates the signalling for an aborted Location Acquisition procedure. It involves four entities: GMLC, 3G-MSC-A, 3G-MSC-B, and BSS-B. The process begins with a MAP PROVIDE SUBSCRIBER LOCATION request at the GMLC. A message is sent to 3G-MSC-A, which then sends a MAP FORWARD ACCESS SIGNALLING message to 3G-MSC-B, containing an encapsulated -an-APDU (LOCATION REPORTING CONTROL). 3G-MSC-B communicates with BSS-B. BSS-B initiates an abort with PERFORM LOCATION ABORT. After a subsequent exchange, BSS-B sends a PERFORM LOCATION RESPONSE. 3G-MSC-B then sends a MAP PROCESS ACCESS SIGNALLING message back to 3G-MSC-A, containing an encapsulated -an-APDU (LOCATION REPORT). Finally, 3G-MSC-A sends a MAP PROVIDE SUBSCRIBER LOCATION res back to the GMLC. + +Sequence diagram showing signalling for an aborted Location Acquisition procedure between GMLC, 3G-MSC-A, 3G-MSC-B, and BSS-B. + +**Figure 65e: Signalling for an aborted Location Acquisition procedure** + +the interworking between the RANAP messages encapsulated in MAP and the BSSMAP messages is as follows: + +| | 29.002 | 48.008 | Notes | +|-----------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------|-------| +| Forward message | MAP FORWARD ACCESS SIG.
request

-an-APDU(
LOCATION REPORTING CONTROL)

RANAP information elements:

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


BSSMAP information elements:

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

-an-APDU(
LOCATION REPORT)

RANAP information elements:

Cause
>Unspecified
Failure | PERFORM LOCATION
RESPONSE


BSSMAP information elements:

LCS Cause
> Location request
aborted | | + +### 4.9.4 Request of Assistance Data or De-ciphering Keys: Successful Case + +#### 4.9.4.1 Inter-MSC Handover (GSM to GSM) + +After a successful Inter-MSC handover, any request of Assistance Data or De-ciphering keys received by the non anchor MSC via the DTAP message LCS-MOLR is forwarded to the anchor MSC by encapsulating the DTAP message into the MAP messages Process Access Signalling. The anchor MSC triggers the BSSMAP procedure Location Acquisition described in 3G TS 48.008. For handover this procedure is executed according to 3G TS 49.008 with the anchor MSC playing the role of the MSC and the non anchor MSC playing the role of the BSS. + +The needed BSSMAP signalling is sent over the E-interface encapsulated in the MAP messages Process Access Signalling and Forward Access Signalling. + +At the non anchor MSC the BSSMAP messages received from the anchor MSC are forwarded to the BSS, and the BSSMAP messages received from the BSS are sent over the E-interface to the anchor MSC. + +Once the BSSMAP procedure has been completed, the anchor MSC sends the DTAP message LCS-MOLR Response encapsulated in the MAP message Forward Access Signalling to the non anchor MSC, which relays it to the MS. + +The signalling for a completed request of Assistance Data or De-ciphering Keys is shown in figures 67a. + +![Sequence diagram showing signalling for the request of Assistance Data or De-ciphering Keys between MSC-A, MSC-B, BSS-B, and MS.](cc7baa8e5118f4b42c01166637c738ea_img.jpg) + +``` + +sequenceDiagram + participant MSC-A + participant MSC-B + participant BSS-B + participant MS + + Note right of MSC-B: LCS-MOLR + MSC-B-->MS: LCS-MOLR + Note left of MSC-A: MAP PROCESS ACCESS SIGNALLING + MSC-A-->MSC-B: -an-APDU(LCS-MOLR) + Note left of MSC-A: MAP FORWARD ACCESS SIGNALLING + MSC-A-->MSC-B: -an-APDU(PERFORM LOCATION REQUEST) + MSC-B-->BSS-B: PERFORM LOCATION REQUEST + Note right of BSS-B: If Assistance Data were requested then Delivery of Assistance Data to MS + MSC-B-->MSC-A: PERFORM LOCATION RESPONSE + Note left of MSC-A: MAP PROCESS ACCESS SIGNALLING + MSC-A-->MSC-B: -an-APDU(PERFORM LOCATION RESPONSE) + Note left of MSC-A: MAP FORWARD ACCESS SIGNALLING + MSC-A-->MSC-B: -an-APDU(LCS-MOLR Response) + MSC-B-->MS: LCS-MOLR Response + +``` + +The sequence diagram illustrates the signalling process for requesting assistance data or de-ciphering keys. It involves four participants: MSC-A, MSC-B, BSS-B, and MS. The sequence starts with MSC-B sending an LCS-MOLR message to the MS. MSC-A then sends a MAP PROCESS ACCESS SIGNALLING message to MSC-B containing an -an-APDU(LCS-MOLR). Next, MSC-A sends a MAP FORWARD ACCESS SIGNALLING message to MSC-B containing an -an-APDU(PERFORM LOCATION REQUEST). MSC-B then sends a PERFORM LOCATION REQUEST message to BSS-B. A conditional block labeled 'If Assistance Data were requested then Delivery of Assistance Data to MS' is shown between BSS-B and the MS. MSC-B then sends a PERFORM LOCATION RESPONSE message to MSC-A. MSC-A responds with a MAP PROCESS ACCESS SIGNALLING message containing an -an-APDU(PERFORM LOCATION RESPONSE). Finally, MSC-A sends a MAP FORWARD ACCESS SIGNALLING message to MSC-B containing an -an-APDU(LCS-MOLR Response), and MSC-B sends an LCS-MOLR Response message to the MS. + +Sequence diagram showing signalling for the request of Assistance Data or De-ciphering Keys between MSC-A, MSC-B, BSS-B, and MS. + +**Figure 67a: Signalling for the request of Assistance Data or De-ciphering Keys** + +After the inter-MSC handover, the MSC-B can perform intra-MSC GSM to UMTS handover. Any request for Assistance Data or De-ciphering keys received after completion of the intra-MSC GSM to UMTS handover is handled as for Inter-MSC Handover GSM to UMTS (see section 4.9.4.2). + +#### 4.9.4.2 Inter-MSC Handover (GSM to UMTS) + +After a successful Inter-MSC GSM to UMTS inter system handover, any request of Assistance Data or De-ciphering keys received by the non-anchor 3G MSC via the DTAP message LCS-MOLR is forwarded to the anchor MSC by encapsulating the DTAP message into the MAP messages Process Access Signalling. The anchor MSC triggers the BSSMAP procedure Location Acquisition described in 3G TS 48.008. For handover this procedure is executed according to 3G TS 49.008 with the anchor MSC playing the role of the MSC and the non anchor 3G MSC playing the role of the BSS. + +The needed BSSMAP signalling is sent over the E-interface encapsulated in the MAP messages Process Access Signalling and Forward Access Signalling. + +At the non-anchor 3G MSC the received BSSMAP messages are mapped into the corresponding RANAP messages to be sent to the RNS, and the received RANAP messages are mapped into the corresponding BSSMAP messages to be sent over the E-interface to the anchor MSC. + +Once the BSSMAP procedure has been completed, the anchor MSC sends the DTAP message LCS-MOLR Response encapsulated in the MAP message Forward Access Signalling to the non anchor 3G MSC, which relays it to the UE. + +The signalling for a completed request of Assistance Data or De-ciphering Keys is shown in figures 67b. + +![Sequence diagram showing signalling for the request of Assistance Data or De-ciphering Keys between MSC-A, 3G MSC-B, RNS-B, and UE.](bfc7918b689a38bc811276e0cc69477e_img.jpg) + +``` + +sequenceDiagram + participant MSC-A + participant 3G MSC-B + participant RNS-B + participant UE + + Note left of 3G MSC-B: LCS-MOLR + 3G MSC-B-->UE: LCS-MOLR + MSC-A->>3G MSC-B: MAP PROCESS ACCESS SIGNALLING + Note right of 3G MSC-B: -an-APDU (LCS-MOLR) + 3G MSC-B-->>MSC-A: MAP FORWARD ACCESS SIGNALLING + Note right of 3G MSC-B: -an-APDU (PERFORM LOCATION REQUEST) + 3G MSC-B-->>RNS-B: LOCATION RELATED DATA REQUEST + Note right of RNS-B: If Assistance Data were requested then Delivery of Assistance Data to UE + RNS-B-->>3G MSC-B: LOCATION RELATED DATA RESPONSE + MSC-A->>3G MSC-B: MAP PROCESS ACCESS SIGNALLING + Note right of 3G MSC-B: -an-APDU (PERFORM LOCATION RESPONSE) + 3G MSC-B-->>MSC-A: MAP FORWARD ACCESS SIGNALLING + Note right of 3G MSC-B: -an-APDU (LCS-MOLR Response) + 3G MSC-B-->>UE: LCS-MOLR Response + +``` + +The sequence diagram illustrates the signalling flow for requesting assistance data or de-ciphering keys. It involves four entities: MSC-A (Anchor MSC), 3G MSC-B (Non-anchor 3G MSC), RNS-B (Radio Network Subsystem), and UE (User Equipment). The process begins with 3G MSC-B sending an LCS-MOLR message to the UE. MSC-A then sends a MAP PROCESS ACCESS SIGNALLING message to 3G MSC-B, encapsulating an -an-APDU (LCS-MOLR). 3G MSC-B responds with a MAP FORWARD ACCESS SIGNALLING message to MSC-A, encapsulating an -an-APDU (PERFORM LOCATION REQUEST). 3G MSC-B then sends a LOCATION RELATED DATA REQUEST to RNS-B. A conditional block indicates that if assistance data was requested, it is delivered to the UE. RNS-B sends a LOCATION RELATED DATA RESPONSE back to 3G MSC-B. MSC-A then sends another MAP PROCESS ACCESS SIGNALLING message to 3G MSC-B, encapsulating an -an-APDU (PERFORM LOCATION RESPONSE). 3G MSC-B responds with a MAP FORWARD ACCESS SIGNALLING message to MSC-A, encapsulating an -an-APDU (LCS-MOLR Response). Finally, 3G MSC-B sends an LCS-MOLR Response message to the UE. + +Sequence diagram showing signalling for the request of Assistance Data or De-ciphering Keys between MSC-A, 3G MSC-B, RNS-B, and UE. + +**Figure 67b: Signalling for the request of Assistance Data or De-ciphering Keys** + +When the UE requires the delivery of Assistance Data for the GPS Assisted positioning method, the interworking between the BSSMAP messages encapsulated in MAP and the RANAP messages is as follows: + +| | 29.002 | 25.413 | Notes | +|-----------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------| +| Forward message | MAP FORWARD ACCESS SIG.
request

-an-APDU(
PERFORM LOCATION REQUEST)

BSSMAP information elements:
Location Type.
Location Information
> location assistance
info for target MS
Location Type.
Positioning Method
> Assisted GPS

GPS Assistance Data | LOCATION RELATED
DATA REQUEST



RANAP information elements:
Requested Location
Related Data Type
>Dedicated Assistance
Data for Assisted GPS


Requested GPS
Assistance Data | 1 | +| Result | MAP PROCESS ACCESS SIG.
request
-an-APDU(
PERFORM LOCATION RESPONSE)

BSSMAP information elements: | LOCATION RELATED
DATA RESPONSE


RANAP information elements: | 2 | + +NOTE 1: All other Positioning Method possibilities are not supported by UMTS when Location Information is "location assistance information" for the target MS. + +NOTE 2: The absence of the Cause IE in the RANAP message Location Related Data Response is an indication that the requested assistance data has been successfully delivered to the UE.. + +If the UE requires the delivery of Assistance Data for an UMTS specific method, then the anchor MSC cannot forward the request to the non anchor 3G MSC, and replies with the error "System" to the LCS-MOLR message. + +If the anchor MSC sends a request for assistance data for a GSM specific method in BSSMAP Perform Location Request encapsulated in MAP Forward Access Signalling, then the non anchor 3G MSC replies immediately by generating and encapsulating BSSMAP Perform Location Response with Cause "System Failure" in MAP Process Access Signalling. This traffic case can happen if an LCS-MOLR had been received in the anchor MSC before the initiation of the handover procedure. + +When the UE requires the delivery of De-ciphering Keys for the GPS Assisted positioning method, the interworking between the BSSMAP messages encapsulated in MAP and the RANAP messages is as follows: + +| | 29.002 | 25.413 | Notes | +|-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------|-------| +| Forward message | MAP FORWARD ACCESS SIG.
request

-an-APDU(
PERFORM LOCATION REQUEST)

BSSMAP information elements:      RANAP information elements:

Location Type.                      Requested Location
Location Information              Related Data Type
> deciphering keys              > Deciphering Keys
for broadcast                      for Assisted GPS
assistance data
for the target MS

Location Type.
Positioning Method
> Assisted GPS | | 1 | +| Result | MAP PROCESS ACCESS SIG.
request

-an-APDU(
PERFORM LOCATION RESPONSE)

BSSMAP information elements:      RANAP information elements:

Deciphering Keys                  Broadcast Assistance
Data Deciphering Keys | | | + +NOTE 1: All other Positioning Method possibilities are not supported by UMTS when Location Information is "deciphering keys for broadcast assistance data for the target MS". + +If the UE requires the delivery of De-ciphering Keys for an UMTS specific method, then the anchor MSC cannot forward the request to the non anchor 3G MSC, and replies with the error "System" to the LCS-MOLR message. + +If the anchor MSC sends a request for De-ciphering Keys for a GSM specific method in BSSMAP Perform Location Request encapsulated in MAP Forward Access Signalling, then the non anchor 3G MSC replies immediately by generating and encapsulating BSSMAP Perform Location Response with Cause "System Failure" in MAP Process Access Signalling. This traffic case can happen if an LCS-MOLR had been received in the anchor MSC before the initiation of the handover procedure. + +After the inter-MSC GSM to UMTS handover, the 3G MSC-B can perform intra-MSC UMTS to GSM handover. Any request for Assistance Data or De-ciphering keys received after completion of the intra-MSC UMTS to GSM handover is handled as for Inter-MSC Handover GSM to GSM (see section 4.9.4.1). + +#### 4.9.4.3 Inter-MSC Handover (UMTS to GSM) + +After a successful Inter-MSC UMTS to GSM inter system handover, any request of Assistance Data or De-ciphering keys received by the non-anchor MSC via the DTAP message LCS-MOLR is forwarded to the anchor 3G MSC by encapsulating the DTAP message into the MAP messages Process Access Signalling. The anchor 3G MSC triggers the BSSMAP procedure Location Acquisition described in 3G TS 48.008. For handover this procedure is executed according to 3G TS 49.008 with the anchor 3G MSC playing the role of the MSC and the non-anchor MSC playing the role of the BSS. + +The needed BSSMAP signalling is sent over the E-interface encapsulated in the MAP messages Process Access Signalling and Forward Access Signalling. + +At the non-anchor MSC the BSSMAP messages received from the anchor 3G MSC are forwarded to the BSS, and the BSSMAP messages received from the BSS are sent over the E-interface to the anchor 3G MSC. + +Once the BSSMAP procedure has been completed, the anchor 3G MSC sends the DTAP message LCS-MOLR Response encapsulated in the MAP message Forward Access Signalling to the non-anchor MSC, which relays it to the UE. + +The signalling for a completed request of Assistance Data or De-ciphering Keys is shown in figures 67c. + +![Sequence diagram showing signalling for the request of Assistance Data or De-ciphering Keys between 3G MSC-A, MSC-B, BSS-B, and MS.](da85343976fdbb19f866d9ddbdad0eae_img.jpg) + +``` + +sequenceDiagram + participant 3G MSC-A + participant MSC-B + participant BSS-B + participant MS + + Note right of MSC-B: LCS-MOLR + MSC-B-->MS: LCS-MOLR + Note left of MSC-B: MAP PROCESS ACCESS SIGNALLING + MSC-A->>MSC-B: -an-APDU(LCS-MOLR) + Note left of MSC-B: MAP FORWARD ACCESS SIGNALLING + MSC-B->>BSS-B: -an-APDU( PERFORM LOCATION REQUEST) + Note right of BSS-B: PERFORM LOCATION REQUEST + BSS-B-->MS: + Note right of MS: If Assistance Data were requested then Delivery of Assistance Data to MS + Note left of MSC-B: PERFORM LOCATION RESPONSE + MSC-B-->MSC-A: + Note left of MSC-B: MAP PROCESS ACCESS SIGNALLING + MSC-A->>MSC-B: -an-APDU( PERFORM LOCATION RESPONSE) + Note left of MSC-B: MAP FORWARD ACCESS SIGNALLING + MSC-B->>BSS-B: -an-APDU( LCS-MOLR Response) + Note right of MSC-B: LCS-MOLR Response + MSC-B-->MS: + +``` + +The sequence diagram illustrates the signalling process for requesting assistance data or de-ciphering keys. It involves four main entities: 3G MSC-A, MSC-B, BSS-B, and MS. The process begins with MSC-B sending an LCS-MOLR message to the MS. Then, 3G MSC-A sends a MAP PROCESS ACCESS SIGNALLING message to MSC-B, encapsulating an -an-APDU(LCS-MOLR). Next, 3G MSC-A sends a MAP FORWARD ACCESS SIGNALLING message to MSC-B, encapsulating an -an-APDU( PERFORM LOCATION REQUEST). MSC-B then sends a PERFORM LOCATION REQUEST message to BSS-B. BSS-B sends a message to the MS, and a conditional block indicates that if assistance data was requested, it is delivered to the MS. BSS-B then sends a PERFORM LOCATION RESPONSE message to MSC-B. MSC-B sends a MAP PROCESS ACCESS SIGNALLING message to 3G MSC-A, encapsulating an -an-APDU( PERFORM LOCATION RESPONSE). Finally, 3G MSC-A sends a MAP FORWARD ACCESS SIGNALLING message to MSC-B, encapsulating an -an-APDU( LCS-MOLR Response), and MSC-B sends an LCS-MOLR Response message to the MS. + +Sequence diagram showing signalling for the request of Assistance Data or De-ciphering Keys between 3G MSC-A, MSC-B, BSS-B, and MS. + +**Figure 67c: Signalling for the request of Assistance Data or De-ciphering Keys** + +After the inter-MSC UMTS to GSM handover, the 3G MSC-B can perform intra-MSC GSM to UMTS handover. Any request for Assistance Data or De-ciphering keys received after completion of the intra-MSC GSM to UMTS handover is handled as for Inter-MSC Handover GSM to UMTS (see section 4.9.4.2).. + +#### 4.9.4.4 Inter-MSC SRNS Relocation + +After a successful Inter-MSC SRNS Relocation , any request of Assistance Data or De-ciphering keys received by the non anchor 3G MSC via the DTAP message LCS-MOLR is forwarded to the anchor 3G MSC by encapsulating the DTAP message into the MAP messages Process Access Signalling. The anchor 3G MSC triggers the RANAP procedure Location Related Data described in TS 25.413. For handover this procedure is executed according to 23.009 with the anchor 3G-MSC playing the role of the 3G-MSC and the non anchor 3G-MSC playing the role of the RNS. + +The needed RANAP signalling is sent over the E-interface encapsulated in the MAP messages Process Access Signalling and Forward Access Signalling. + +At the non anchor 3G MSC the RANAP messages received from the anchor 3G MSC are forwarded to the RNS, and the RANAP messages received from the RNS are sent over the E-interface to the anchor 3G MSC. + +Once the RANAP procedure has been completed, the anchor 3G MSC sends the DTAP message LCS-MOLR Response encapsulated in the MAP message Forward Access Signalling to the non anchor 3G MSC, which relays it to the UE. + +The signalling for a completed request of Assistance Data or De-ciphering Keys is shown in figures 67d. + +![Sequence diagram showing signalling for Assistance Data or De-ciphering Keys between 3G MSC-A, 3G MSC-B, RNS-B, and UE.](9f9fdebeade37ad92fdd68d6ea9f58ce_img.jpg) + +``` + +sequenceDiagram + participant A as 3G MSC-A + participant B as 3G MSC-B + participant R as RNS-B + participant U as UE + + U-->>B: LCS-MOLR + Note over A: MAP PROCESS ACCESS +SIGNALLING + B-->>A: -an-APDU (LCS-MOLR) + Note over A: MAP FORWARD ACCESS +SIGNALLING + A-->>B: -an-APDU (LOCATION RELATED +DATA REQUEST) + B-->>R: LOCATION RELATED DATA REQUEST + Note over R,U: If Assistance Data were requested then +Delivery of Assistance Data to UE + R-->>B: LOCATION RELATED DATA RESPONSE + Note over A: MAP PROCESS ACCESS +SIGNALLING + B-->>A: -an-APDU (LOCATION RELATED +DATA RESPONSE) + Note over A: MAP FORWARD ACCESS +SIGNALLING + A-->>B: -an-APDU (LCS-MOLR Response) + B-->>U: LCS-MOLR Response + +``` + +Sequence diagram showing signalling for Assistance Data or De-ciphering Keys between 3G MSC-A, 3G MSC-B, RNS-B, and UE. + +**Figure 67d: Signalling for the request of Assistance Data or De-ciphering Keys** + +After the inter-MSC SRNS Relocation, the 3G MSC-B can perform intra-MSC UMTS to GSM handover. Any request for Assistance Data or De-ciphering keys received after completion of the intra-MSC UMTS to GSM requires that at the non anchor 3G MSC the received RANAP messages are mapped into the corresponding BSSMAP messages to be sent to the + +BSS, and the received BSSMAP messages are mapped into the corresponding RANAP messages to be sent over the E-interface to the anchor 3G-MSC. The signalling for a completed request of Assistance Data or De-ciphering Keys in this traffic case is shown in figures 67e. + +![Sequence diagram showing signalling for the request of Assistance Data or De-ciphering Keys between 3G MSC-A, 3G MSC-B, BSS-B, and UE.](f1ba1e68228ebd4c3109371574a723e6_img.jpg) + +``` + +sequenceDiagram + participant 3G MSC-A + participant 3G MSC-B + participant BSS-B + participant UE + + Note left of 3G MSC-A: MAP PROCESS ACCESS SIGNALLING + 3G MSC-A->>3G MSC-B: -an-APDU(LCS-MOLR) + Note left of 3G MSC-A: MAP FORWARD ACCESS SIGNALLING + 3G MSC-A->>3G MSC-B: -an-APDU(LOCATION RELATED DATA REQUEST) + 3G MSC-B->>BSS-B: PERFORM LOCATION REQUEST + Note right of BSS-B: If Assistance Data were requested then Delivery of Assistance Data to MS + BSS-B->>3G MSC-B: PERFORM LOCATION RESPONSE + Note left of 3G MSC-A: MAP PROCESS ACCESS SIGNALLING + 3G MSC-B->>3G MSC-A: -an-APDU(LOCATION RELATED DATA RESPONSE) + Note left of 3G MSC-A: MAP FORWARD ACCESS SIGNALLING + 3G MSC-B->>3G MSC-A: -an-APDU(LCS-MOLR Response) + 3G MSC-B->>UE: LCS-MOLR Response + +``` + +Sequence diagram showing signalling for the request of Assistance Data or De-ciphering Keys between 3G MSC-A, 3G MSC-B, BSS-B, and UE. + +**Figure 67e: Signalling for the request of Assistance Data or De-ciphering Keys** + +When the UE requires the delivery of Assistance Data for the GPS Assisted positioning method, the interworking between the RANAP messages encapsulated in MAP and the BSSMAP messages is as follows: + +| | 29.002 | 48.008 | Notes | +|-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------| +| Forward message | MAP FORWARD ACCESS SIG.
request

-an-APDU(
LOCATION RELATED
DATA REQUEST)

RANAP information
elements:

Requested Location
Related Data Type
> Dedicated Assistance
Data for Assisted
GPS

Requested GPS
Assistance Data | PERFORM LOCATION
REQUEST

BSSMAP information
elements:

Location Type.
Location Information
> location assistance 1
info for target MS
Location Type.
Positioning Method
> Assisted GPS

GPS Assistance Data | | +| Result | MAP PROCESS ACCESS SIG.
request

-an-APDU(
LOCATION RELATED
DATA RESPONSE)

RANAP information
elements: | PERFORM LOCATION
RESPONSE

BSSMAP information
elements: | 2 | + +NOTE 1: All other Positioning Method possibilities are not supported by GSM when Location Information is "deciphering keys for broadcast assistance data for the target MS". + +NOTE 2: The absence of the Cause IE in the BSSMAP message Perform Location Response is an indication that the requested assistance data has been successfully delivered to the UE.. + +If the UE requires the delivery of Assistance Data for a GSM specific method, then the anchor 3G-MSC cannot forward the request to the non anchor 3G MSC, and replies with the error "System" to the LCS-MOLR message. + +If the anchor 3G MSC sends a request for Assistance Data for an UMTS specific method in RANAP Location Related Data Request encapsulated in MAP Forward Access Signalling, then the non anchor 3G MSC replies immediately by generating and encapsulating RANAP Location Related Data Failure with Cause "Unspecified Failure" in MAP Process Access Signalling. This traffic case can happen if an LCS-MOLR had been received in the anchor MSC before the initiation of the intra-MSC handover procedure. + +When the UE requires the delivery of De-ciphering Keys for the GPS Assisted positioning method, the interworking between the RANAP messages encapsulated in MAP and the BSSMAP messages is as follows: + +| | 29.002 | 48.008 | Notes | +|-----------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------| +| Forward message | MAP FORWARD ACCESS SIG.
request

-an-APDU(
LOCATION RELATED
DATA REQUEST)

RANAP information
elements:

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


BSSMAP information
elements:

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

-an-APDU(
LOCATION RELATED
DATA RESPONSE)

RANAP information
elements:

Broadcast Assistance
Data Deciphering Keys | PERFORM LOCATION
RESPONSE


BSSMAP information
elements:

Deciphering Keys | | + +NOTE 1: All other Positioning Method possibilities are not supported by GSM when Location Information is "deciphering keys for broadcast assistance data for the target MS". + +If the UE requires the delivery of De-ciphering Keys for a GSM specific method, then the anchor 3G-MSC cannot forward the request to the non anchor 3G MSC, and replies with the error "System" to the LCS-MOLR message. + +If the anchor 3G MSC sends a request for De-ciphering Keys for an UMTS specific method in RANAP Location Related Data Request encapsulated in MAP Forward Access Signalling, then the non anchor 3G MSC replies immediately by generating and encapsulating RANAP Location Related Data Failure with Cause "Unspecified Failure" in MAP Process Access Signalling. This traffic case can happen if an LCS-MOLR had been received in the anchor MSC before the initiation of the intra-MSC handover procedure. + +### 4.9.5 Request of Assistance Data or De-ciphering Keys: Failure Case + +#### 4.9.5.1 Inter-MSC Handover (GSM to GSM) + +After a successful Inter-MSC handover, any request of Assistance Data or De-ciphering keys received by the non anchor MSC via the DTAP message LCS-MOLR is handled as described in section 4.9.4.1. + +If the request fails, either because the BSS-B cannot return the requested De-ciphering Keys to the anchor MSC or cannot deliver the required Assistance Data to the MS, the signalling is the same as for the successful case and is shown in figure 67a. + +After the inter-MSC handover, the MSC-B can perform intra-MSC GSM to UMTS handover. Any request for Assistance Data or De-ciphering keys received after completion of the intra-MSC GSM to UMTS handover is handled as for Inter-MSC Handover GSM to UMTS (see section 4.9.4.2). + +If the request fails the signalling is the same as for the failure case for Inter-MSC Handover GSM to UMTS (see section 4.9.5.2) + +#### 4.9.5.2 Inter-MSC Handover (GSM to UMTS) + +After a successful Inter-MSC GSM to UMTS handover, any request of Assistance Data or De-ciphering keys received by the non anchor 3G MSC via the DTAP message LCS-MOLR is handled as described in section 4.9.4.2. + +If the request fails, either because BSS-B cannot return the requested De-ciphering Keys to the anchor MSC or because BSS-B cannot deliver the required Assistance Data to the MS, the signalling is as shown in figure 68a. + +![Sequence diagram showing signalling for a failed request of Assistance Data or De-ciphering Keys between MSC-A, 3G MSC-B, RNS-B, and UE.](6bc05e56e8453678a84fa6bdba3fd903_img.jpg) + +``` + +sequenceDiagram + participant MSC-A + participant 3G MSC-B + participant RNS-B + participant UE + + Note left of MSC-A: MAP PROCESS ACCESS SIGNALLING + MSC-A->>3G MSC-B: -an-APDU(LCS-MOLR) + Note left of MSC-A: MAP FORWARD ACCESS SIGNALLING + 3G MSC-B->>RNS-B: LOCATION RELATED DATA REQUEST + Note right of RNS-B: If Assistance Data were requested then Delivery of Assistance Data to UE + RNS-B-->>3G MSC-B: LOCATION RELATED DATA FAILURE + Note left of MSC-A: MAP PROCESS ACCESS SIGNALLING + 3G MSC-B->>MSC-A: -an-APDU(PERFORM LOCATION RESPONSE) + Note left of MSC-A: MAP FORWARD ACCESS SIGNALLING + MSC-A->>3G MSC-B: -an-APDU(LCS-MOLR Response) + 3G MSC-B-->>UE: LCS-MOLR Response + +``` + +Sequence diagram showing signalling for a failed request of Assistance Data or De-ciphering Keys between MSC-A, 3G MSC-B, RNS-B, and UE. + +**Figure 68a: Signalling for a failed request of Assistance Data or De-ciphering Keys** + +When the delivery to the UE of Assistance Data for the GPS Assisted positioning method fails, the interworking between the BSSMAP messages encapsulated in MAP and the RANAP messages is as follows: + +| | 29.002 | 25.413 | Notes | +|-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------|-------| +| Forward message | "For the forward messages please refer to the corresponding table in section 4.9.4.2" | | | +| Result | 
 MAP PROCESS ACCESS SIG.        LOCATION RELATED       request                        DATA FAILURE -an-APDU(   PERFORM LOCATION RESPONSE)  BSSMAP information             RANAP information       elements:                      elements:    LCS Cause                      Cause   > System Failure               > Dedicated Assistance                                    Data Not Available
| | | + +When the RNS-B cannot satisfy the request for De-ciphering Keys, the interworking between the BSSMAP messages encapsulated in MAP and the RANAP messages is as follows: + +| | 29.002 | 25.413 | Notes | +|-----------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------|-------| +| Forward message | "For the forward messages please refer to the corresponding table in section 4.9.4.2" | | | +| Result | 
 MAP PROCESS ACCESS SIG.        LOCATION RELATED       request                        DATA FAILURE -an-APDU(   PERFORM LOCATION RESPONSE)  BSSMAP information             RANAP information       elements:                      elements:    LCS Cause                      Cause   > System Failure               > Deciphering Keys                                    Not Available
| | | + +After the inter-MSC GSM to UMTS handover, the 3G MSC-B can perform intra-MSC UMTS to GSM handover. Any request for Assistance Data or De-ciphering keys received after completion of the intra-MSC UMTS to GSM handover is handled as for Inter-MSC Handover GSM to GSM (see section 4.9.4.1). + +If the request fails the signalling is the same as for the failure case for Inter-MSC Handover GSM to GSM (see section 4.9.5.1) + +#### 4.9.5.3 Inter-MSC Handover (UMTS to GSM) + +After a successful Inter-MSC UMTS to GSM handover, any request of Assistance Data or De-ciphering keys received by the non anchor MSC via the DTAP message LCS-MOLR is handled as described in section 4.9.4.3. + +If the request fails, either because the BSS-B cannot return the requested De-ciphering Keys to the anchor 3G MSC or BSS-B cannot deliver the required Assistance Data to the MS, the signalling is the same as for the successful case and is shown in figure 67c. + +After the inter-MSC UMTS to GSM handover, the 3G MSC-B can perform intra-MSC GSM to UMTS handover. Any request for Assistance Data or De-ciphering keys received after completion of the intra-MSC GSM to UMTS handover is handled as for Inter-MSC Handover GSM to UMTS (see section 4.9.4.2).. + +If the request fails the signalling is the same as for the failure case for Inter-MSC Handover GSM to UMTS (see section 4.9.5.2) + +#### 4.9.5.4 Inter-MSC SRNS Relocation + +After a successful Inter-MSC SRNS Relocation , any request of Assistance Data or De-ciphering keys received by the non anchor 3G MSC via the DTAP message LCS-MOLR is handled as described in section 4.9.4.4. + +If the request fails, either because the RNS-B cannot return the requested De-ciphering Keys to the anchor 3G MSC or RNS-B cannot deliver the required Assistance Data to the MS, the signalling is shown in figure 68b. + +![Sequence diagram showing signalling for the request of Assistance Data or De-ciphering Keys. Lifelines: 3G MSC-A, 3G MSC-B, RNS-B, UE. The sequence starts with an LCS-MOLR message from UE to 3G MSC-B. 3G MSC-B then sends a MAP PROCESS ACCESS SIGNALING message to 3G MSC-A with an -an-APDU (LCS-MOLR). 3G MSC-A sends a MAP FORWARD ACCESS SIGNALING message to 3G MSC-B with an -an-APDU (LOCATION RELATED DATA REQUEST). 3G MSC-B sends a LOCATION RELATED DATA REQUEST to RNS-B. RNS-B has a self-call box 'If Assistance Data were requested then Delivery of Assistance Data to UE'. RNS-B then sends a LOCATION RELATED DATA FAILURE back to 3G MSC-B. 3G MSC-B sends a MAP PROCESS ACCESS SIGNALING message to 3G MSC-A with an -an-APDU (LOCATION RELATED DATA FAILURE). 3G MSC-A sends a MAP FORWARD ACCESS SIGNALING message to 3G MSC-B with an -an-APDU (LCS-MOLR Response). Finally, 3G MSC-B sends an LCS-MOLR Response to the UE.](0de91e9b714369b312bf3ab1853301ac_img.jpg) + +``` + +sequenceDiagram + participant UE + participant 3G_MSC_B as 3G MSC-B + participant 3G_MSC_A as 3G MSC-A + participant RNS_B as RNS-B + + Note left of 3G_MSC_A: MAP PROCESS ACCESS SIGNALING + UE->>3G_MSC_B: LCS-MOLR + Note left of 3G_MSC_A: -an-APDU (LCS-MOLR) + 3G_MSC_B->>3G_MSC_A: MAP FORWARD ACCESS SIGNALING + Note left of 3G_MSC_A: -an-APDU (LOCATION RELATED DATA REQUEST) + 3G_MSC_B->>RNS_B: LOCATION RELATED DATA REQUEST + Note right of RNS_B: If Assistance Data were requested then Delivery of Assistance Data to UE + RNS_B->>3G_MSC_B: LOCATION RELATED DATA FAILURE + Note left of 3G_MSC_A: MAP PROCESS ACCESS SIGNALING + Note left of 3G_MSC_A: -an-APDU (LOCATION RELATED DATA FAILURE) + 3G_MSC_B->>3G_MSC_A: MAP FORWARD ACCESS SIGNALING + Note left of 3G_MSC_A: -an-APDU (LCS-MOLR Response) + 3G_MSC_B->>UE: LCS-MOLR Response + +``` + +Sequence diagram showing signalling for the request of Assistance Data or De-ciphering Keys. Lifelines: 3G MSC-A, 3G MSC-B, RNS-B, UE. The sequence starts with an LCS-MOLR message from UE to 3G MSC-B. 3G MSC-B then sends a MAP PROCESS ACCESS SIGNALING message to 3G MSC-A with an -an-APDU (LCS-MOLR). 3G MSC-A sends a MAP FORWARD ACCESS SIGNALING message to 3G MSC-B with an -an-APDU (LOCATION RELATED DATA REQUEST). 3G MSC-B sends a LOCATION RELATED DATA REQUEST to RNS-B. RNS-B has a self-call box 'If Assistance Data were requested then Delivery of Assistance Data to UE'. RNS-B then sends a LOCATION RELATED DATA FAILURE back to 3G MSC-B. 3G MSC-B sends a MAP PROCESS ACCESS SIGNALING message to 3G MSC-A with an -an-APDU (LOCATION RELATED DATA FAILURE). 3G MSC-A sends a MAP FORWARD ACCESS SIGNALING message to 3G MSC-B with an -an-APDU (LCS-MOLR Response). Finally, 3G MSC-B sends an LCS-MOLR Response to the UE. + +**Figure 68b: Signalling for the request of Assistance Data or De-ciphering Keys** + +After the inter-MSC SRNS Relocation, the 3G MSC-B can perform intra-MSC UMTS to GSM handover. Any request for Assistance Data or De-ciphering keys received after completion of the intra-MSC UMTS to GSM requires that at the non anchor 3G MSC the received RANAP messages are mapped into the corresponding BSSMAP messages to be sent to the BSS, and the received BSSMAP messages are mapped into the corresponding RANAP messages to be sent over the E-interface to the anchor 3G-MSC. + +If the request fails, either because the BSS-B cannot return the requested De-ciphering Keys to the anchor 3G MSC or BSS-B cannot deliver the required Assistance Data to the MS, the signalling is as shown in figure 68c. + +![Sequence diagram showing signalling for the request of Assistance Data or De-ciphering Keys between 3G MSC-A, 3G MSC-B, BSS-B, and UE.](36f34fd6230a53db267c1df3089ebbe2_img.jpg) + +``` + +sequenceDiagram + participant 3G MSC-A + participant 3G MSC-B + participant BSS-B + participant UE + + Note left of 3G MSC-A: MAP PROCESS ACCESS SIGNALLING + 3G MSC-A->>3G MSC-B: -an-APDU (LCS-MOLR) + Note left of 3G MSC-A: MAP FORWARD ACCESS SIGNALLING + 3G MSC-A->>3G MSC-B: -an-APDU (LOCATION RELATED DATA REQUEST) + 3G MSC-B->>BSS-B: PERFORM LOCATION REQUEST + Note right of BSS-B: If Assistance Data were requested then Delivery of Assistance Data to MS + BSS-B-->>3G MSC-B: PERFORM LOCATION RESPONSE + Note left of 3G MSC-A: MAP PROCESS ACCESS SIGNALLING + 3G MSC-B->>3G MSC-A: -an-APDU (LOCATION RELATED DATA FAILURE) + Note left of 3G MSC-A: MAP FORWARD ACCESS SIGNALLING + 3G MSC-B->>3G MSC-A: -an-APDU (LCS-MOLR Response) + 3G MSC-B-->>UE: LCS-MOLR Response + +``` + +Sequence diagram showing signalling for the request of Assistance Data or De-ciphering Keys between 3G MSC-A, 3G MSC-B, BSS-B, and UE. + +Figure 68c: Signalling for the request of Assistance Data or De-ciphering Keys + +After the inter-MSC SRNS Relocation, the 3G MSC-B can perform intra-MSC UMTS to GSM handover. Any request for Assistance Data or De-ciphering keys received after completion of the intra-MSC UMTS to GSM requires that at the non anchor 3G MSC the received RANAP messages are mapped into the corresponding BSSMAP messages to be sent to the BSS, and the received BSSMAP messages are mapped into the corresponding RANAP messages to be sent over the E-interface to the anchor 3G-MSC. + +When the UE requires the delivery of Assistance Data for the GPS Assisted positioning method, the interworking between the RANAP messages encapsulated in MAP and the BSSMAP messages is as follows: + +| | 29.002 | 48.008 | Notes | +|-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------|-------| +| Forward message | "For the forward messages please refer to the corresponding table in section 4.9.4.4" | | | +| Result | 
MAP PROCESS ACCESS SIG.      PERFORM LOCATION       request                      RESPONSE -an-APDU(   LOCATION RELATED   DATA FAILURE)  RANAP information            BSSMAP information       elements:                    elements:  Cause                        LCS Cause   > Dedicated Assistance       > <any value>     Data Not Available
| | | + +When the UE requires the delivery of De-ciphering Keys for the GPS Assisted positioning method, the interworking between the RANAP messages encapsulated in MAP and the BSSMAP messages is as follows: + +| | 29.002 | 48.008 | Notes | +|-----------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------|-------| +| Forward message | "For the forward messages please refer to the corresponding table in section 4.9.4.4" | | | +| Result | 
MAP PROCESS ACCESS SIG.      PERFORM LOCATION       request                      RESPONSE -an-APDU(   LOCATION RELATED   DATA FAILURE)  RANAP information            BSSMAP information       elements:                    elements:  Cause                        LCS Cause   > Deciphering Keys           > <any value>     Not Available
| | | + +### 4.9.6 Abort of Request of Assistance Data or De-ciphering Keys: + +#### 4.9.6.1 Inter-MSC Handover (GSM to GSM) + +After a successful Inter-MSC handover, any request of Assistance Data or De-ciphering keys received by the non anchor MSC via the DTAP message LCS-MOLR is handled as described in section 4.9.4.1. + +If the request is aborted by the anchor MSC the signalling is as shown in figure 69a. + +![Sequence diagram showing signalling for the abortion of a request for Assistance Data or De-ciphering Keys between MSC-A, MSC-B, BSS-B, and MS.](245166735676c675f98f535bc4c6f0a1_img.jpg) + +``` + +sequenceDiagram + participant MSC-A + participant MSC-B + participant BSS-B + participant MS + + Note left of MSC-A: Error: Reference source not + MSC-B->>MS: LCS-MOLR + Note left of MSC-A: MAP PROCESS ACCESS SIGNALLING + MSC-A->>MSC-B: -an-APDU(LCS-MOLR) + Note left of MSC-A: MAP FORWARD ACCESS SIGNALLING + MSC-A->>MSC-B: -an-APDU(PERFORM LOCATION REQUEST) + MSC-B->>BSS-B: + Note left of BSS-B: PERFORM LOCATION REQUEST + Note left of MSC-A: MAP FORWARD ACCESS SIGNALLING + MSC-A->>MSC-B: -an-APDU(PERFORM LOCATION ABORT) + MSC-B->>BSS-B: + Note left of BSS-B: PERFORM LOCATION ABORT + MSC-B->>MS: + Note left of BSS-B: PERFORM LOCATION RESPONSE + Note left of MSC-A: MAP PROCESS ACCESS SIGNALLING + MSC-A->>MSC-B: -an-APDU(PERFORM LOCATION RESPONSE) + Note left of MSC-A: MAP FORWARD ACCESS SIGNALLING + MSC-A->>MSC-B: -an-APDU(LCS-MOLR Response) + MSC-B->>MS: LCS-MOLR Response + +``` + +Sequence diagram showing signalling for the abortion of a request for Assistance Data or De-ciphering Keys between MSC-A, MSC-B, BSS-B, and MS. + +**Figure 69a: Signalling for the abortion of a request for Assistance Data or De-ciphering Keys** + +After the inter-MSC handover, the MSC-B can perform intra-MSC GSM to UMTS handover. Any request for Assistance Data or De-ciphering keys received after completion of the intra-MSC GSM to UMTS handover is handled as for Inter-MSC Handover GSM to UMTS (see section 4.9.4.2). + +If the request is aborted the signalling is the same as for the abortion case for Inter-MSC Handover GSM to UMTS (see section 4.9.6.2) + +#### 4.9.6.2 Inter-MSC Handover (GSM to UMTS) + +After a successful Inter-MSC GSM to UMTS handover, any request of Assistance Data or De-ciphering keys received by the non anchor MSC via the DTAP message LCS-MOLR is handled as described in section 4.9.4.1. + +If the request is aborted by the anchor MSC the signalling is as shown in figure 69b. + +![Sequence diagram showing the signalling for the abortion of the request for Assistance Data or De-ciphering Keys. The diagram involves four entities: MSC-A, 3G MSC-B, RNS-B, and UE. The sequence starts with a dashed arrow from UE to 3G MSC-B labeled 'LCS-MOLR'. MSC-A sends a 'MAP PROCESS ACCESS SIGNALLING' message to 3G MSC-B with an '-an-APDU(LCS-MOLR)'. 3G MSC-B then sends a 'MAP FORWARD ACCESS SIGNALLING' message to MSC-A with an '-an-APDU(PERFORM LOCATION REQUEST)'. MSC-A sends a 'MAP FORWARD ACCESS SIGNALLING' message to 3G MSC-B with an '-an-APDU(PERFORM LOCATION ABORT)'. 3G MSC-B sends a dashed arrow to RNS-B, followed by a 'LOCATION RELATED DATA REQUEST' message. RNS-B sends a dashed arrow back to 3G MSC-B. 3G MSC-B sends a 'MAP PROCESS ACCESS SIGNALLING' message to MSC-A with an '-an-APDU(PERFORM LOCATION RESPONSE)'. MSC-A sends a 'MAP FORWARD ACCESS SIGNALLING' message to 3G MSC-B with an '-an-APDU(LCS-MOLR Response)'. Finally, 3G MSC-B sends a dashed arrow to UE labeled 'LCS-MOLR Response'.](e3dd59b6fd27059890be0e0397bdd467_img.jpg) + +``` + +sequenceDiagram + participant MSC-A + participant 3G MSC-B + participant RNS-B + participant UE + + Note left of MSC-A: MAP PROCESS ACCESS SIGNALLING + UE-->>3G MSC-B: LCS-MOLR + MSC-A->>3G MSC-B: MAP PROCESS ACCESS SIGNALLING + Note left of MSC-A: -an-APDU(LCS-MOLR) + 3G MSC-B->>MSC-A: MAP FORWARD ACCESS SIGNALLING + Note left of 3G MSC-B: -an-APDU(PERFORM LOCATION REQUEST) + MSC-A->>3G MSC-B: MAP FORWARD ACCESS SIGNALLING + Note left of MSC-A: -an-APDU(PERFORM LOCATION ABORT) + 3G MSC-B-->>RNS-B: + Note right of 3G MSC-B: LOCATION RELATED DATA REQUEST + RNS-B-->>3G MSC-B: + 3G MSC-B->>MSC-A: MAP PROCESS ACCESS SIGNALLING + Note left of 3G MSC-B: -an-APDU(PERFORM LOCATION RESPONSE) + MSC-A->>3G MSC-B: MAP FORWARD ACCESS SIGNALLING + Note left of MSC-A: -an-APDU(LCS-MOLR Response) + 3G MSC-B-->>UE: LCS-MOLR Response + +``` + +Sequence diagram showing the signalling for the abortion of the request for Assistance Data or De-ciphering Keys. The diagram involves four entities: MSC-A, 3G MSC-B, RNS-B, and UE. The sequence starts with a dashed arrow from UE to 3G MSC-B labeled 'LCS-MOLR'. MSC-A sends a 'MAP PROCESS ACCESS SIGNALLING' message to 3G MSC-B with an '-an-APDU(LCS-MOLR)'. 3G MSC-B then sends a 'MAP FORWARD ACCESS SIGNALLING' message to MSC-A with an '-an-APDU(PERFORM LOCATION REQUEST)'. MSC-A sends a 'MAP FORWARD ACCESS SIGNALLING' message to 3G MSC-B with an '-an-APDU(PERFORM LOCATION ABORT)'. 3G MSC-B sends a dashed arrow to RNS-B, followed by a 'LOCATION RELATED DATA REQUEST' message. RNS-B sends a dashed arrow back to 3G MSC-B. 3G MSC-B sends a 'MAP PROCESS ACCESS SIGNALLING' message to MSC-A with an '-an-APDU(PERFORM LOCATION RESPONSE)'. MSC-A sends a 'MAP FORWARD ACCESS SIGNALLING' message to 3G MSC-B with an '-an-APDU(LCS-MOLR Response)'. Finally, 3G MSC-B sends a dashed arrow to UE labeled 'LCS-MOLR Response'. + +**Figure 69b: Signalling for the abortion of the request for Assistance Data or De-ciphering Keys** + +There's no interworking between the BSSMAP Perform Location Abort and any RANAP message since it is not possible to abort a request for Assistance Data or De-ciphering Keys with RANAP. The BSSMAP message Perform Location Response is generated by the non-anchor 3G MSC. + +After the inter-MSC GSM to UMTS handover, the 3G MSC-B can perform intra-MSC UMTS to GSM handover. Any request for Assistance Data or De-ciphering keys received after completion of the intra-MSC UMTS to GSM handover is handled as for Inter-MSC Handover GSM to GSM (see section 4.9.4.1). + +If the request is aborted the signalling is the same as for the abortion case for Inter-MSC Handover GSM to GSM (see section 4.9.6.1) + +#### 4.9.6.3 Inter-MSC Handover (UMTS to GSM) + +After a successful Inter-MSC UMTS to GSM handover, any request of Assistance Data or De-ciphering keys received by the non anchor MSC via the DTAP message LCS-MOLR is handled as described in section 4.9.4.3. + +If the request is aborted by the anchor 3G MSC the signalling is the same as for the abortion for Inter-MSC GSM to GSM handover and is shown in figure 69a. + +After the inter-MSC UMTS to GSM handover, the 3G MSC-B can perform intra-MSC GSM to UMTS handover. Any request for Assistance Data or De-ciphering keys received after completion of the intra-MSC GSM to UMTS handover is handled as for Inter-MSC Handover GSM to UMTS (see section 4.9.4.2).. + +If the request is aborted the signalling is the same as for the abortion case for Inter-MSC Handover GSM to UMTS (see section 4.9.6.2) + +#### 4.9.6.4 Inter-MSC SRNS Relocation + +After a successful Inter-MSC SRNS Relocation , any request of Assistance Data or De-ciphering keys received by the non anchor 3G MSC via the DTAP message LCS-MOLR is handled as described in section 4.9.4.4. + +The request cannot be aborted by the 3G anchor MSC since RANAP does not support abortion of a request for Assistance Data or De-Ciphering Keys. + +## 4.10 Single Radio Voice Call Continuity (SRVCC) + +### 4.10.1 General + +The general principles of the SRVCC handover procedures are specified in 3GPP TS 23.009 [2]. This clause provides a detailed specification for the interworking performed by the MSC Server enhanced for SRVCC. It defines in particular the encoding of RANAP and BSSMAP cause values to avoid different encodings in different implementations. + +### 4.10.2 SRVCC Handover from UTRAN (HSPA) to GERAN + +#### Encoding of the cause code sent in BSSMAP Handover Request: + +When it receives the SRVCC PS to CS Request message from the SGSN (see 3GPP TS 29.280 [25]), the MSC Server enhanced for SRVCC shall set the BSSMAP Cause to the value 'Uplink quality' in the Handover Request message. + +### 4.10.3 SRVCC Handover from UTRAN (HSPA) to UTRAN + +#### Encoding of the cause code sent in RANAP Relocation Request: + +When it receives the SRVCC PS to CS Request message from the SGSN (see 3GPP TS 29.280 [25]), the MSC Server enhanced for SRVCC shall set the RANAP Cause to the value 'Time critical Relocation ' in the Relocation Request message. + +### 4.10.4 SRVCC Handover from E-UTRAN to GERAN + +#### Encoding of the cause code sent in BSSMAP Handover Request: + +When it receives the SRVCC PS to CS Request message from the MME (see 3GPP TS 29.280 [25]), the MSC Server enhanced for SRVCC shall set the BSSMAP Cause to the value 'Uplink quality' in the Handover Request message. + +### 4.10.5 SRVCC Handover from E-UTRAN to UTRAN + +#### Encoding of the cause code sent in RANAP Relocation Request: + +When it receives the SRVCC PS to CS Request message from the MME (see 3GPP TS 29.280 [25]), the MSC Server enhanced for SRVCC shall set the RANAP Cause to the value 'Time critical Relocation ' in the Relocation Request message. + +# 5 Interworking in the MME + +## 5.1 General + +This subclause provides a detailed specification for the interworking performed by the MME. + +## 5.2 Void + +## 5.3 Interworking between RANAP protocol messages and S1AP protocol messages + +This subclause defines a mapping of RANAP and S1AP cause values used in connection with inter RAT Handover to avoid different mappings in different implementations. + +### Inter RAT Handover from UTRAN to LTE: + +Table 5.3.1 defines a cause value mapping performed by the MME when the MME receives the Forward Relocation Request message from the S4-SGSN. + +**Table 5.3.1: Cause value mapping from RANAP Cause to S1AP Cause** + +| 25.413 [7] | | 36.413 [21] | | +|-----------------------------------|----------------------------------|-------------------------------|--------------------------------------| +| RELOCATION REQUIRED (RANAP Cause) | | HANDOVER REQUEST (S1AP Cause) | | +| Group | Value | Group | Value | +| Radio Network Layer Cause | Time critical Relocation | Radio Network Layer Cause | Time critical handover | +| Radio Network Layer Cause | Resource Optimisation Relocation | Radio Network Layer Cause | Resource optimisation handover | +| Radio Network Layer Cause | Reduce Load in Serving Cell | Radio Network Layer Cause | Reduce load in serving cell | +| Any other value | | Radio Network Layer Cause | Handover Desirable for Radio Reasons | + +For inter RAT handover from UTRAN served by Gn/Gp-SGSN to LTE, the MME maps the RANAP cause in the GTPv1 Forward Relocation Request message to an S1AP cause as per Table 5.3.1. The MME sends this S1AP cause in the S1AP Handover Request message to the eNodeB. + +For inter RAT handover from UTRAN served by Gn/Gp-SGSN to LTE, if the handover fails in the LTE access, the MME maps the S1AP cause in the S1AP Handover Failure message to a RANAP cause by using the mapping in Table 6.2.1. The MME uses the RANAP cause in the GTPv1 Forward Relocation Response message to the Gn/Gp-SGSN. + +### Inter RAT Handover from LTE to UTRAN: + +The table 5.3.2 defines a cause value mapping performed by the MME when the MME receives the Forward Relocation Response message from the S4-SGSN. This mapping is only needed if the inter RAT Handover failed in UTRAN. + +**Table 5.3.2: Cause value mapping from RANAP Cause to S1AP Cause for failure case** + +| 25.413 [7] | | 36.413 [21] | | +|----------------------------------|---------------------------------------------|-------------------------------------------|---------------------------------------------| +| RELOCATION FAILURE (RANAP Cause) | | HANDOVER PREPARATION FAILURE (S1AP Cause) | | +| Group | Value | Group | Value | +| Radio Network Layer Cause | No Radio Resources Available in Target Cell | Radio Network Layer Cause | No Radio Resources Available in Target Cell | + +| | | | | +|---------------------------|--------------------------------------------------------------------------|---------------------------|-----------------------------------------------------------------| +| Radio Network Layer Cause | Requested Ciphering and/or Integrity Protection algorithms not supported | Radio Network Layer Cause | Encryption and/or integrity protection algorithms not supported | +| Radio Network Layer Cause | Traffic Load In The Target Cell Higher Than In The Source Cell | Radio Network Layer Cause | No Radio Resources Available in Target Cell | +| Miscellaneous Cause | O&M Intervention | Miscellaneous Cause | O&M Intervention | +| Any other value | | Radio Network Layer Cause | Handover Failure In Target EPC/eNB Or Target System | + +For inter RAT handover from LTE to UTRAN served by Gn/Gp-SGSN, the MME maps the S1AP cause in S1AP Handover Required message to a RANAP cause by using the mapping in Table 6.2.2. The MME uses this RANAP cause in the GTPv1 Forward Relocation Request message to the Gn/Gp-SGSN. + +For inter RAT handover from LTE to UTRAN served by Gn/Gp-SGSN, if the handover fails in the UTRAN access, the MME maps the RANAP cause received in the GTPv1 Forward Relocation Response message to an S1AP cause as per Table 5.3.2. The MME sends this S1AP cause in the S1AP Handover Preparation Failure message to the eNodeB. + +## 5.4 Interworking between BSSGP protocol messages and S1AP protocol messages + +This subclause defines a mapping of BSSGP and S1AP cause values used in connection with inter RAT Handover to avoid different mappings in different implementations. + +### Inter RAT Handover from GERAN to LTE: + +Table 5.4.1 defines a cause value mapping performed by the MME when the MME receives the GTPv2 Forward Relocation Request message from the S4-SGSN or the GTPv1 Forward Relocation Request message from Gn/Gp-SGSN (as per Annex D of 3GPP TS 23.401[22]). + +NOTE1: The mapping in Table 5.4.1 has been derived based on Table 15.1 in 3GPP TS 29.060 [23] and Table 5.3.1 in this specification. + +**Table 5.4.1: Cause value mapping from BSSGP Cause to S1AP Cause** + +| 48.018 [24] | 36.413 [21] | | +|------------------------------------|-------------------------------|------------------------| +| PS HANDOVER REQUIRED (BSSGP Cause) | HANDOVER REQUEST (S1AP Cause) | | +| Value | Group | Value | +| Uplink quality | Radio Network Layer Cause | Time critical handover | +| Uplink strength | Radio Network Layer Cause | Time critical handover | +| Downlink quality | Radio Network Layer Cause | Time critical handover | +| Downlink strength | Radio Network Layer Cause | Time critical handover | +| Distance | Radio Network Layer Cause | Time critical handover | + +| | | | +|-------------------------|---------------------------|--------------------------------------| +| Traffic | Radio Network Layer Cause | Resource optimisation handover | +| Cell traffic congestion | Radio Network Layer Cause | Reduce load in serving cell | +| Any other value | Radio Network Layer Cause | Handover Desirable for Radio Reasons | + +For inter RAT handover from GERAN served by Gn/Gp-SGSN to LTE, if the handover fails in the LTE access, the MME maps the S1AP cause in S1AP Handover Failure message to a RANAP cause by using the mapping in Table 6.2.1. The MME uses the RANAP cause in the GTPv1 Forward Relocation Response message to the Gn/Gp-SGSN. The Gn/Gp-SGSN maps the RANAP cause to a BSSGP cause as per Table 15.2 in 3GPP TS 29.060 [23] and sends this BSSGP cause in the BSSGP PS Handover Required Nack message. + +### Inter RAT Handover from LTE to GERAN: + +Table 5.4.2 defines a cause value mapping performed by the MME when the MME receives the GTPv2 Forward Relocation Response message from the S4-SGSN or the GTPv1 Forward Relocation Response message from the Gn/Gp-SGSN (as per Annex D of 3GPP TS 23.401[22]). This mapping is only needed if the inter RAT Handover failed in GERAN. + +NOTE2: The mapping in Table 5.4.2 has been derived based on Table 15.4 in 3GPP TS 29.060 [23] and Table 5.3.2 in this specification. + +**Table 5.4.2: Cause value mapping from BSSGP Cause to S1AP Cause for failure case** + +| 48.018 [24] | 36.413 [21] | | +|-------------------------------------------|----------------------------------------------|-----------------------------------------------------| +| PS HANDOVER REQUEST NACK
(BSSGP Cause) | HANDOVER PREPARATION FAILURE
(S1AP Cause) | | +| Value | Group | Value | +| Cell traffic congestion | Radio Network Layer Cause | No Radio Resources Available in Target Cell | +| O&M intervention | Miscellaneous Cause | O&M Intervention | +| Any other value | Radio Network Layer Cause | Handover Failure In Target EPC/eNB Or Target System | + +For inter RAT handover from LTE to GERAN served by Gn/Gp-SGSN, the MME maps the S1AP cause in S1AP Handover Required message to a RANAP cause by using the mapping in Table 6.2.2. The MME uses the RANAP cause in the GTPv1 Forward Relocation Request message to the Gn/Gp-SGSN. The Gn/Gp-SGSN maps the RANAP cause to a BSSGP cause as per Table 15.3 in 3GPP TS 29.060 [23] and sends this BSSGP cause in the BSSGP PS Handover Request message. + +# 6 Interworking in the S4-SGSN + +## 6.1 General + +This subclause provides a detailed specification for the interworking performed by the S4-SGSN. + +## 6.2 Interworking between RANAP protocol messages and S1AP protocol messages + +This subclause defines a mapping of RANAP and S1AP cause values used in connection with inter RAT Handover to avoid different mappings in different implementations. + +### Inter RAT Handover from UTRAN to LTE: + +The table 6.2.1 defines a cause value mapping performed by the S4-SGSN when the S4-SGSN receives the Forward Relocation Response message from the MME. This mapping is only needed if the inter RAT Handover failed in LTE. + +**Table 6.2.1: Cause value mapping from S1AP Cause to RANAP Cause for failure case** + +| 36.413 [21] | | 25.413 [7] | | +|--------------------------------------|-----------------------------------------------------------------|-----------------------------------------------------|--------------------------------------------------------------------------| +| HANDOVER FAILURE (S1AP Cause) | | RELOCATION PREPARATION FAILURE (RANAP Cause) | | +| Group | Value | Group | Value | +| Radio Network Layer Cause | No Radio Resources Available in Target Cell | Radio Network Layer Cause | No Radio Resources Available in Target Cell | +| Radio Network Layer Cause | Encryption and/or integrity protection algorithms not supported | Radio Network Layer Cause | Requested Ciphering and/or Integrity Protection algorithms not supported | +| Miscellaneous Cause | O&M Intervention | Miscellaneous Cause | O&M Intervention | +| Any other value | | Radio Network Layer Cause | Relocation Failure in Target CN/RNC or Target System | + +### Inter RAT Handover from LTE to UTRAN: + +Table 6.2.2 defines a cause value mapping performed by the S4-SGSN when the S4-SGSN receives the Forward Relocation Request message from the MME. + +**Table 6.2.2: Cause value mapping from S1AP Cause to RANAP Cause** + +| 36.413 [21] | | 25.413 [7] | | +|---------------------------------------|--------------------------------------|-----------------------------------------|----------------------------------------| +| HANDOVER REQUIRED (S1AP Cause) | | RELOCATION REQUEST (RANAP Cause) | | +| Group | Value | Group | Value | +| Radio Network Layer Cause | Handover Desirable for Radio Reasons | Radio Network Layer Cause | Relocation Desirable for Radio Reasons | +| Radio Network Layer Cause | Time Critical Handover | Radio Network Layer Cause | Time critical Relocation | +| Radio Network Layer Cause | Reduce Load in Serving Cell | Radio Network Layer Cause | Reduce Load in Serving Cell | +| Any other value | | Radio Network Layer Cause | Resource Optimized Relocation | + +## 6.3 Interworking between BSSGP protocol messages and S1AP protocol messages + +This subclause defines a mapping of BSSGP and S1AP cause values used in connection with inter RAT Handover to avoid different mappings in different implementations. + +### Inter RAT Handover from GERAN to LTE: + +Table 6.3.1 defines a cause value mapping performed by the S4-SGSN when the S4-SGSN receives the GTPv2 Forward Relocation Response message from the MME. + +NOTE1: The mapping in Table 6.3.1 has been derived based on Table 6.2.1 in this specification and Table 15.2 in 3GPP TS 29.060 [23]. + +**Table 6.3.1: Cause value mapping from S1AP Cause to BSSGP Cause for failure case** + +| 36.413 [21] | | 48.018 [24] | +|-------------------------------|-----------------------------------------------------------------|--------------------------------------------------------------------------| +| HANDOVER FAILURE (S1AP Cause) | | PS HANDOVER REQUIRED NACK (BSSGP Cause) | +| Group | Value | Value | +| Radio Network Layer Cause | No Radio Resources Available in Target Cell | Cell traffic congestion | +| Radio Network Layer Cause | Encryption and/or integrity protection algorithms not supported | Requested ciphering and/or integrity protection algorithms not supported | +| Miscellaneous Cause | O&M Intervention | O&M Intervention | +| Any other value | | Relocation failure in target system | + +### Inter RAT Handover from LTE to GERAN: + +Table 6.3.2 defines a cause value mapping performed by the S4-SGSN when the S4-SGSN receives the GTPv2 Forward Relocation Request message from the MME. + +NOTE2: The mapping in Table 6.3.2 has been derived based on Table 6.2.2 in this specification and Table 15.3 in 3GPP TS 29.060 [23]. + +**Table 6.3.2: Cause value mapping from S1AP Cause to BSSGP Cause** + +| 36.413 [21] | | 48.018 [24] | +|--------------------------------|--------------------------------------|-----------------------------------| +| HANDOVER REQUIRED (S1AP Cause) | | PS HANDOVER REQUEST (BSSGP Cause) | +| Group | Value | Value | +| Radio Network Layer Cause | Handover Desirable for Radio Reasons | Better cell | +| Radio Network Layer Cause | Time Critical Handover | Time critical relocation | +| Radio Network Layer Cause | Reduce Load in Serving Cell | Cell traffic congestion | +| Any other value | | Traffic | + +## 6.4 Interworking between BSSGP protocol messages and RANAP protocol messages + +For the mapping of BSSGP and RANAP cause values used in connection with inter RAT Handover between GERAN and UTRAN, the mapping tables in Section 15 in 3GPP TS 29.060 [23] applies. The mapping is performed by the target S4-SGSN. + +# --- Annex A (informative): Change history + +| Change history | | | | | | | +|----------------|-----------|---------|-------|---------|-------------|----------------------------------------------------------------------------------------| +| TSG CN# | Spec | Version | CR | | New Version | Subject/Comment | +| Sept 1999 | GSM 09.10 | 7.0.0 | | | | Transferred to 3GPP CN | +| CN#04 | 29.010 | | | R99 | 3.0.0 | Approved by mail exploder at CN#04 | +| CN#06 | 29.010 | 3.0.0 | 001 | R99 | 3.1.0 | UMTS / GSM Interworking | +| CN#06 | 29.010 | 3.0.0 | 002 | R99 | 3.1.0 | Addition of LSA Information message | +| CN#07 | 29.010 | 3.1.0 | 003r1 | R99 | 3.2.0 | UMTS / GSM Interworking | +| CN#07 | 29.010 | 3.1.0 | 004r1 | R99 | 3.2.0 | GSM / UMTS Interworking | +| CN#07 | 29.010 | 3.1.0 | 005 | R99 | 3.2.0 | UMTS/UMTS Handover | +| CN#09 | 29.010 | 3.2.0 | 006r1 | R99 | 3.3.0 | Clarification of use of Radio Resource Information | +| CN#09 | 29.010 | 3.2.0 | 007r1 | R99 | 3.3.0 | Corrections and updates to align with current R99 specs | +| CN#10 | 29.010 | 3.3.0 | 008 | R99 | 3.4.0 | GSM to 3G Handover: Location Reporting in 3G_MSC-B | +| CN#10 | 29.010 | 3.3.0 | 009 | R99 | 3.4.0 | GSM to 3G Handover: Chosen IEs in Handover Request Ack | +| CN#10 | 29.010 | 3.3.0 | 010 | R99 | 3.4.0 | GSM to 3G Handover: MAP parameter Target Cell ID | +| CN#10 | 29.010 | 3.3.0 | 011r1 | R99 | 3.4.0 | GSM/UMTS Interworking: Mapping of cause codes | +| CN#11 | 29.010 | 3.4.0 | 012 | R99 | 3.5.0 | GSM to UMTS handover: addition of MAP parameter Target RNC ID | +| CN#11 | 29.010 | 3.4.0 | 013 | R99 | 3.5.0 | Inter MSC relocation: addition of MAP parameter Target RNC ID | +| CN#11 | 29.010 | 3.4.0 | 014 | R99 | 3.5.0 | Roaming restrictions for GPRS service | +| CN#11 | 29.010 | 3.4.0 | 015 | R99 | 3.5.0 | Alignment of cause mapping for 08.08 and 25.413 (Directed Retry) | +| CN#11 | 29.010 | 3.4.0 | 016 | R99 | 3.5.0 | UMTS to GSM Directed Retry cause code mapping | +| CN#11 | 29.010 | 3.4.0 | 017 | R99 | 3.5.0 | Mapping of unknown HLR error to access interface cause code | +| CN#11 | 29.010 | 3.5.0 | | Rel-4 | 4.0.0 | Version increased from R99 to Rel-4 | +| CN#12 | 29.010 | 4.0.0 | 020r1 | Rel-4 | 4.1.0 | Addition of selected UMTS algorithm indication to the handover procedures | +| CN#12 | 29.010 | 4.0.0 | 022r1 | Rel-4 | 4.1.0 | Addition of selected GSM algorithm indication to the handover procedures | +| CN#12 | 29.010 | 4.0.0 | 024r1 | Rel-4 | 4.1.0 | Addition of allowed UMTS algorithms indication to the handover procedures | +| CN#12 | 29.010 | 4.0.0 | 026r1 | Rel-4 | 4.1.0 | Addition of allowed GSM algorithms indication to the handover procedures | +| CN#12 | 29.010 | 4.0.0 | 028r1 | Rel-4 | 4.1.0 | Addition of GSM channel type and GSM chosen channel indications to handover procedures | +| CN#12 | 29.010 | 4.0.0 | 030 | Rel-4 | 4.1.0 | Partial Roaming – restriction by Location area | +| CN#12 | 29.010 | 4.0.0 | 031 | Rel-4 | 4.1.0 | Mapping between RANAP and BSSMAP for Location Services | +| CN#12 | 29.010 | 4.0.0 | 034r1 | Rel-4 | 4.1.0 | Mapping between RANAP and BSSMAP for Location Services | +| CN#14 | 29.010 | 4.1.0 | 036r2 | Rel-4 | 4.2.0 | LCS/HO Location Reporting – GSM to GSM, UMTS to GSM and UMTS to UMTS | +| CN#14 | 29.010 | 4.1.0 | 040 | Rel-4 | 4.2.0 | Global replace of BSS-APDU with AN-APDU | +| CN#14 | 29.010 | 4.1.0 | 047 | Rel-4 | 4.2.0 | Removal of deleted MAP operations | +| CN#16 | 29.010 | 4.2.0 | 048r1 | Rel-4 | 4.3.0 | LCS: Mapping BSSMAP-RANAP for request of assistance data on E interface | +| CN#16 | 29.010 | 4.2.0 | 051r1 | Rel-4 | 4.3.0 | LCS: clarification of mapping for Location Acquisition | +| CN#16 | 29.010 | 4.2.0 | 052 | Rel-4 | 4.3.0 | Check of NAM and Requesting Node Type on receipt of SendAuthenticationInfo | +| CN#16 | 29.010 | 4.2.0 | 054r1 | Rel-4 | 4.3.0 | Addition of Service Handover parameters to MAP Handover messages | +| CN#16 | 29.010 | 4.3.0 | | Rel-5 | 5.0.0 | Version 5.0.0 created after CN#16. | +| CN#17 | 29.010 | 5.0.0 | 060 | Rel-5 | 5.1.0 | Introduction of GERAN Iu-mode | + +| Change history | | | | | | | +|----------------|--------|---------|--------|---------|-------------|-------------------------------------------------------------------------------------------------------------| +| TSG CN# | Spec | Version | CR | | New Version | Subject/Comment | +| CN#17 | 29.010 | 5.0.0 | 069r2 | Rel-5 | 5.1.0 | Addition of an error mapping table for MAP Update Location operation | +| CN#17 | 29.010 | 5.0.0 | 075 | Rel-5 | 5.1.0 | Support for Shared Network in connected mode (using encapsulated BSSAP transport of SNA access information) | +| CN#18 | 29.010 | 5.1.0 | 073r1 | Rel-5 | 5.2.0 | LCS: Adding missing parameter mapping to assistance data request procedure after inter-MSC SRNS Relocation | +| CN#18 | 29.010 | 5.1.0 | 077 | Rel-5 | 5.2.0 | Correction on the use of "User Failure" error for LCS-MOLR operation | +| CN#18 | 29.010 | 5.1.0 | 078 | Rel-5 | 5.2.0 | Interworking between security mode procedure and relocation | +| CN#18 | 29.010 | 5.1.0 | 084r3 | Rel-5 | 5.2.0 | Correction to the Service Handover parameters | +| CN#20 | 29.010 | 5.2.0 | 088 | Rel-5 | 5.3.0 | Correction of LCS cause mapping between RANAP and BSSMAP | +| CN#20 | 29.010 | 5.2.0 | 089r1 | Rel-5 | 5.3.0 | Handling of UE-specific behaviour data in the relay MSC | +| CN#20 | 29.010 | 5.2.0 | 090 | Rel-5 | 5.3.0 | Handling of UE-specific behaviour data in the relay MSC | +| July 2003 | 29.010 | 5.3.0 | | Rel-5 | 5.3.1 | Implemented CR 29.010-090 removed | +| CN#21 | 29.010 | 5.3.1 | 091 | Rel-5 | 5.4.0 | Addition of Early UE specific cause code mapping | +| CN#21 | 29.010 | 5.4.0 | 092r2 | Rel-6 | 6.0.0 | Information transfer at MAP-E interface during inter MSC handover/relocation | +| CN#22 | 29.010 | 6.0.0 | 095 | Rel-6 | 6.1.0 | Wrong message appears in message flow | +| CN#23 | 29.010 | 6.1.0 | 100r1 | Rel-6 | 6.2.0 | Correction of inter system handover cause mapping | +| CN#23 | 29.010 | 6.1.0 | 101r1 | Rel-6 | 6.2.0 | Include administrative restriction subscription parameter | +| CN#23 | 29.010 | 6.1.0 | 103r2 | Rel-6 | 6.2.0 | Change to cause code mappings | +| CN#24 | 29.010 | 6.2.0 | 106r3 | Rel-6 | 6.3.0 | Removing of non-existing error indications from Location update mappings | +| CN#24 | 29.010 | 6.2.0 | 107 | Rel-6 | 6.3.0 | Addition of cause code mapping for BSSAP Clear Request and RANAP Iu Release Request | +| CN#25 | 29.010 | 6.3.0 | 108r2 | Rel-6 | 6.4.0 | Addition of cause code mapping to the routing area update procedure | +| CN#25 | 29.010 | 6.3.0 | 110 | Rel-6 | 6.4.0 | Addition of cause code mapping for inter-system handover | +| CN#27 | 29.010 | 6.4.0 | 112 | Rel-6 | 6.5.0 | Correction of partly implemented CR108 | +| CT#28 | 29.010 | 6.5.0 | 111r2 | Rel-6 | 6.6.0 | Full RANAP support of network initiated SCUDIF | +| CT#29 | 29.010 | 6.6.0 | 115 | Rel-6 | 6.7.0 | Correction of cause code mapping for the routing area update procedure | +| CT#31 | 29.010 | 6.7.0 | 0118 | Rel-6 | 6.8.0 | Addition of UMTS Trace parameters to handover procedure | +| CT#31 | 29.010 | 6.8.0 | 0117r2 | Rel-7 | 7.0.0 | Addition of new cause "Additional roaming not allowed " in RAU and LAU | +| CT#32 | 29.010 | 7.0.0 | 0119r2 | Rel-7 | 7.1.0 | Use of cause #12 in VPLMNs | +| CT#32 | 29.010 | 7.0.0 | 0121 | Rel-7 | 7.1.0 | Alignment of Cause Mapping | +| CT#42 | 29.010 | 7.1.0 | | Rel-8 | 8.0.0 | Upgraded unchanged from Rel-7 | +| CT#46 | 29.010 | 8.0.0 | 124r2 | Rel-8 | 8.1.0 | Addition of missing cause code mapping for EPC | +| CT#46 | 29.010 | 8.1.0 | 0125r1 | Rel-9 | 9.0.0 | RANAP Cause and S1AP Cause mapping | +| CT#48 | 29.010 | 9.0.0 | 0126r1 | Rel-9 | 9.1.0 | Removal of MME mapping between Diameter error codes and NAS CC's | +| CT#50 | 29.010 | 9.1.0 | 0128r1 | Rel-9 | 9.2.0 | Missing BSSGP/RANAP/S1AP Cause Code mapping for IRAT Handover | +| CT#50 | 29.010 | 9.2.0 | 0130r1 | Rel-10 | 10.0.0 | Wrong Reference for BSSMAP messages | +| CT#52 | 29.010 | 10.0.0 | 0132r2 | Rel-10 | 10.1.0 | BSSMAP/RANAP/S1AP Cause Code mapping for SRVCC Handover | +| CT#53 | 29.010 | 10.1.0 | 0134 | Rel-10 | 10.2.0 | Algorithm list handling in MSC-B | + +| Change history | | | | | | | +|----------------|--------|---------|--------|---------|-------------|-------------------------------------------------------| +| TSG CN# | Spec | Version | CR | | New Version | Subject/Comment | +| Jan 2012 | 29.010 | 10.2.0 | | | 10.2.1 | Editorial corrections in section 5 and 6. | +| CT#56 | 29.010 | 10.2.1 | 0135 | Rel-11 | 11.0.0 | Regional Subscription and CSG Information Propagation | +| CT#63 | 29.010 | 11.0.0 | 0136r2 | Rel-11 | 11.1.0 | Error mapping for "Data Missing" | \ No newline at end of file diff --git a/marked/Rel-11/29_series/29011/04dc3838022e96d8d5548bb1b777b38c_img.jpg b/marked/Rel-11/29_series/29011/04dc3838022e96d8d5548bb1b777b38c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3ce20707656e4d7e56d7520c35ab3a810236353b --- /dev/null +++ b/marked/Rel-11/29_series/29011/04dc3838022e96d8d5548bb1b777b38c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7ac05e1b07c9e5e2bbe26e88e90ab9544ea8715e88a5e1bbe97e1dcd660f6558 +size 18674 diff --git a/marked/Rel-11/29_series/29011/08441fa90c5fd11994626f662ac13f19_img.jpg b/marked/Rel-11/29_series/29011/08441fa90c5fd11994626f662ac13f19_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6c001056c433d1b9452022f89f736362d966fca6 --- /dev/null +++ b/marked/Rel-11/29_series/29011/08441fa90c5fd11994626f662ac13f19_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7003ce8dc6e2dcaa04ecea9587457b03b20be1eb6fb8e49df216b944b601d536 +size 28744 diff --git a/marked/Rel-11/29_series/29011/1c140ee5d1a87186977da94a96bfa700_img.jpg b/marked/Rel-11/29_series/29011/1c140ee5d1a87186977da94a96bfa700_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..618bbfb5dd13f96b26ab6f5b03d92d1af05d0e34 --- /dev/null +++ b/marked/Rel-11/29_series/29011/1c140ee5d1a87186977da94a96bfa700_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:06c147dfcd20c879c7018b5768d72337d162da9d22be73a284eb09ac6ac506f5 +size 45563 diff --git a/marked/Rel-11/29_series/29011/26d664119ad25250780f554633444e54_img.jpg b/marked/Rel-11/29_series/29011/26d664119ad25250780f554633444e54_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1d66b648bebe381460160e5466f752979326edb8 --- /dev/null +++ b/marked/Rel-11/29_series/29011/26d664119ad25250780f554633444e54_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:eedac8416c95a9c31c43a2a8aa41a2a2e0e4e317ccf7287ae89c5ed1d749a7cb +size 15244 diff --git a/marked/Rel-11/29_series/29011/2734e7f9be3e1dc046f14be2e6c9a085_img.jpg b/marked/Rel-11/29_series/29011/2734e7f9be3e1dc046f14be2e6c9a085_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5e55ae6af8997c844416f7d8a6563faceb12e385 --- /dev/null +++ b/marked/Rel-11/29_series/29011/2734e7f9be3e1dc046f14be2e6c9a085_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f84e2a66721ba84c33ebf5476dd66b104b581c25a9f70bdda78f05304acd405d +size 15288 diff --git a/marked/Rel-11/29_series/29011/35127fe87029df6f5f0b2ee85f6193f1_img.jpg b/marked/Rel-11/29_series/29011/35127fe87029df6f5f0b2ee85f6193f1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d0388f4224e36548632ce1a341e2bfe950e87ae5 --- /dev/null +++ b/marked/Rel-11/29_series/29011/35127fe87029df6f5f0b2ee85f6193f1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e8f1750f30f97bd1f7c3fc89668fb51c8192eb2520100596608a5ed11171a52c +size 53128 diff --git a/marked/Rel-11/29_series/29011/356eb99ab9489bbd647223390a913903_img.jpg b/marked/Rel-11/29_series/29011/356eb99ab9489bbd647223390a913903_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3c5aa59423b4bd5ba6f718af4358fd335e6c2a6a --- /dev/null +++ b/marked/Rel-11/29_series/29011/356eb99ab9489bbd647223390a913903_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:75ac8673f3bb274e4770121c8ad713ced2e2d829dabe19cc42797091a8dc0602 +size 62283 diff --git a/marked/Rel-11/29_series/29011/43837b056625d3d6ce615e4c02f163bb_img.jpg b/marked/Rel-11/29_series/29011/43837b056625d3d6ce615e4c02f163bb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..223bb1123381cafd16e2039482cfb218635b72fc --- /dev/null +++ b/marked/Rel-11/29_series/29011/43837b056625d3d6ce615e4c02f163bb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e56419b0ba15d5eef525553cfd0d0d7b5d93d067674985c564d5358e780f8118 +size 37318 diff --git a/marked/Rel-11/29_series/29011/4636adff5682a064f0ae5f13a1d464a6_img.jpg b/marked/Rel-11/29_series/29011/4636adff5682a064f0ae5f13a1d464a6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1a957c33c02f2b91121ff2e9744eb7ad31fdb5ef --- /dev/null +++ b/marked/Rel-11/29_series/29011/4636adff5682a064f0ae5f13a1d464a6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:04ec48c255d0d645e0dc9f1b86cac1ae442ac4aae6849b6cf9eabe72100f3a11 +size 15865 diff --git a/marked/Rel-11/29_series/29011/4b87467ad9642943235f48f7d4b59449_img.jpg b/marked/Rel-11/29_series/29011/4b87467ad9642943235f48f7d4b59449_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5b344b9e4e31a22d26ce4191daef5a3cda8cfc62 --- /dev/null +++ b/marked/Rel-11/29_series/29011/4b87467ad9642943235f48f7d4b59449_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3c242d4f1184ea646d7d7b501828835c48b457cc146327ecf841ffe605a246d8 +size 20628 diff --git a/marked/Rel-11/29_series/29011/4cc7cdce3d498d8b0ba033a9be24ade5_img.jpg b/marked/Rel-11/29_series/29011/4cc7cdce3d498d8b0ba033a9be24ade5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..26d59be0737fb6c965103911792d5313886a1c8f --- /dev/null +++ b/marked/Rel-11/29_series/29011/4cc7cdce3d498d8b0ba033a9be24ade5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e90407ed8a17db7e2281b7e23c424cb751a546dda49dbc48e3efb9e6bf8030ff +size 41137 diff --git a/marked/Rel-11/29_series/29011/55a593259a0749ce342bd5eac2ba6b58_img.jpg b/marked/Rel-11/29_series/29011/55a593259a0749ce342bd5eac2ba6b58_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ede3b400abb12b8d410df4e7eacbc482b004e3e1 --- /dev/null +++ b/marked/Rel-11/29_series/29011/55a593259a0749ce342bd5eac2ba6b58_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a46fd8a1dba22026080c873d54034f48525d9d57df0aba323f48f6298b1ec3a8 +size 23222 diff --git a/marked/Rel-11/29_series/29011/5a95b187de0044da69b7322e04761b86_img.jpg b/marked/Rel-11/29_series/29011/5a95b187de0044da69b7322e04761b86_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f8cd3349bd9058720e97257c1c323b62e9124383 --- /dev/null +++ b/marked/Rel-11/29_series/29011/5a95b187de0044da69b7322e04761b86_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a85fec3d4ee625609df00036304e9e6eb5f4c5273d66a8c089255dd64f05de58 +size 22876 diff --git a/marked/Rel-11/29_series/29011/7b8b192e2853ef28d28eff0241ebe86b_img.jpg b/marked/Rel-11/29_series/29011/7b8b192e2853ef28d28eff0241ebe86b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7fdcce64e81108847f6ac298388dd86acc41f898 --- /dev/null +++ b/marked/Rel-11/29_series/29011/7b8b192e2853ef28d28eff0241ebe86b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ca6cefef23812339ddea326caa4f75c1b2646c2df63f67b55689117e9cada3f5 +size 16956 diff --git a/marked/Rel-11/29_series/29011/7e670a2b556b53ea9002dfff3a420e08_img.jpg b/marked/Rel-11/29_series/29011/7e670a2b556b53ea9002dfff3a420e08_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bee9e18333cabec0c8d6a36f768a75e783836439 --- /dev/null +++ b/marked/Rel-11/29_series/29011/7e670a2b556b53ea9002dfff3a420e08_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:aa7487b46b904d8a994fc1aefe90fae4fa96bc0628e4bc0c2dfff83d600b4b66 +size 22743 diff --git a/marked/Rel-11/29_series/29011/8592a32c2fdf17c1e562f0ba6b7e8e1a_img.jpg b/marked/Rel-11/29_series/29011/8592a32c2fdf17c1e562f0ba6b7e8e1a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4d664e83725986dbca1e62c43049e06d57659d00 --- /dev/null +++ b/marked/Rel-11/29_series/29011/8592a32c2fdf17c1e562f0ba6b7e8e1a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7151dc12ee3354ba9ded64f2d6f2c2230d6c7d22cb6d6a2daffd4b52d50174aa +size 29367 diff --git a/marked/Rel-11/29_series/29011/88a6d9692a52989caa6b208a1ba70dc0_img.jpg b/marked/Rel-11/29_series/29011/88a6d9692a52989caa6b208a1ba70dc0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8dedb73bfc3fd5a48266dd909a05812fa26ea2a1 --- /dev/null +++ b/marked/Rel-11/29_series/29011/88a6d9692a52989caa6b208a1ba70dc0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c2578576bf60852bf2912a4c794ad61ff98bfce46e0d5ca64671088e69021060 +size 20368 diff --git a/marked/Rel-11/29_series/29011/9167fa5ebcb66516d1bbb421ec9bba7b_img.jpg b/marked/Rel-11/29_series/29011/9167fa5ebcb66516d1bbb421ec9bba7b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0c6386a48643e1469e821f214d87d74b56c0992c --- /dev/null +++ b/marked/Rel-11/29_series/29011/9167fa5ebcb66516d1bbb421ec9bba7b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:769597653904e861c869ada8acaf1c19698028d7c441091973518362365c0c53 +size 19840 diff --git a/marked/Rel-11/29_series/29011/93c223896503daf410cb8b742e7a6fae_img.jpg b/marked/Rel-11/29_series/29011/93c223896503daf410cb8b742e7a6fae_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8c216906dc71961b90f16d48e4a7d85b56cf5c46 --- /dev/null +++ b/marked/Rel-11/29_series/29011/93c223896503daf410cb8b742e7a6fae_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:413e367bfe34427902166a23a00228f88d36d7898990d1f97541833e8c71714d +size 18471 diff --git a/marked/Rel-11/29_series/29011/95cd9f56a54683029052b8c644228506_img.jpg b/marked/Rel-11/29_series/29011/95cd9f56a54683029052b8c644228506_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0cea5744814bbb57cf6091efe98029bfb0cbd1aa --- /dev/null +++ b/marked/Rel-11/29_series/29011/95cd9f56a54683029052b8c644228506_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6448b79428bb7a2efa7eafa1fd254f5c7df40da0a771804474817034449804aa +size 11926 diff --git a/marked/Rel-11/29_series/29011/9b686adccf125267a013fa25721231a3_img.jpg b/marked/Rel-11/29_series/29011/9b686adccf125267a013fa25721231a3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..dfd767bce6c7cd353267dce5145b0e2c2fa50cae --- /dev/null +++ b/marked/Rel-11/29_series/29011/9b686adccf125267a013fa25721231a3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8c54a43f32677f24f4bc87d79b23d5f28e70a3a6813fe2ee28e5e2ccf27c0c80 +size 22446 diff --git a/marked/Rel-11/29_series/29011/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg b/marked/Rel-11/29_series/29011/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7b96affa007db6bfbd01376852f8ef022a7fe6e1 --- /dev/null +++ b/marked/Rel-11/29_series/29011/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:723cb6da45c7815b78579da1ac4f1802c679940dfc39659ee54b7598fbaee412 +size 37429 diff --git a/marked/Rel-11/29_series/29011/a51105b2031bad93b818b82f071c6add_img.jpg b/marked/Rel-11/29_series/29011/a51105b2031bad93b818b82f071c6add_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d9d77968fe3aaa78e8cb008c7fcf6ac66f4d9e72 --- /dev/null +++ b/marked/Rel-11/29_series/29011/a51105b2031bad93b818b82f071c6add_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7989a835f500e1017cd954e034bd035a7fb885340ff49140645f546a14127166 +size 17777 diff --git a/marked/Rel-11/29_series/29011/b3c108e7145f2017957569d06ea359cb_img.jpg b/marked/Rel-11/29_series/29011/b3c108e7145f2017957569d06ea359cb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..34d80c92dffd22b5d13e763348aaad87ff6e92e8 --- /dev/null +++ b/marked/Rel-11/29_series/29011/b3c108e7145f2017957569d06ea359cb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7860f96ca97cd1a291a2f57795f96dd9f338388bfdb0d1ad6bac18f9e42e9b4e +size 25649 diff --git a/marked/Rel-11/29_series/29011/b90144cfbb81a2d610d920240fda689d_img.jpg b/marked/Rel-11/29_series/29011/b90144cfbb81a2d610d920240fda689d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7ffbd712a7793f901340401897299062fe2655f5 --- /dev/null +++ b/marked/Rel-11/29_series/29011/b90144cfbb81a2d610d920240fda689d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c9d1a8d76111f9c183c6cefa5280339a57af336ae48dd771c8369cfa5ec2c217 +size 46787 diff --git a/marked/Rel-11/29_series/29011/bd57a547bec253d4179e5c4491c53dbb_img.jpg b/marked/Rel-11/29_series/29011/bd57a547bec253d4179e5c4491c53dbb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..435013ad21102eb941dfeaecf4f2eb11e52400cb --- /dev/null +++ b/marked/Rel-11/29_series/29011/bd57a547bec253d4179e5c4491c53dbb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c14bb9f645cc8920a89b4e6642b5e1b18b3ed473fa27a6e5042191d9a1041074 +size 26600 diff --git a/marked/Rel-11/29_series/29011/bdfe4e1058d1a0e14bb838771b57254c_img.jpg b/marked/Rel-11/29_series/29011/bdfe4e1058d1a0e14bb838771b57254c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1166235a84cfd625be43ebc7758b82ebecba2e36 --- /dev/null +++ b/marked/Rel-11/29_series/29011/bdfe4e1058d1a0e14bb838771b57254c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5540761bc5cbcf5fabbe859d0aa938c124a41114594c6569e37325b5cc19947a +size 6514 diff --git a/marked/Rel-11/29_series/29011/bffdddb47fced140f8d17fdc2a29f592_img.jpg b/marked/Rel-11/29_series/29011/bffdddb47fced140f8d17fdc2a29f592_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ad29aaf7c0f93bf520ac72a3472c37bb3079273e --- /dev/null +++ b/marked/Rel-11/29_series/29011/bffdddb47fced140f8d17fdc2a29f592_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3213dce149b84d5f41c5a5a40231e74ba69c95e1523105788487ca4b364c677f +size 27924 diff --git a/marked/Rel-11/29_series/29011/c036e2540a94b31357ceb0002f0cacab_img.jpg b/marked/Rel-11/29_series/29011/c036e2540a94b31357ceb0002f0cacab_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9882b2cf0edd3a4b3d6fb3be33c144aa848dd6b9 --- /dev/null +++ b/marked/Rel-11/29_series/29011/c036e2540a94b31357ceb0002f0cacab_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f5bffac69238e6c9151ee9469e72cca583919232657131d28db66887a48e5dd0 +size 28201 diff --git a/marked/Rel-11/29_series/29011/cce70c739081f63a6af83dc9483f98ce_img.jpg b/marked/Rel-11/29_series/29011/cce70c739081f63a6af83dc9483f98ce_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..81809b567ceb2ad7c72d99f7a5efaaa3c524f3f6 --- /dev/null +++ b/marked/Rel-11/29_series/29011/cce70c739081f63a6af83dc9483f98ce_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:eccd8aaca8053a26c4975200ae16916b8a7e320f6e2f1012355ac610670c83d9 +size 26979 diff --git a/marked/Rel-11/29_series/29011/cdd4dfacab004e9979caed3fffea69e5_img.jpg b/marked/Rel-11/29_series/29011/cdd4dfacab004e9979caed3fffea69e5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ac593bc8653ac900f0c8c078672f2cb2392fed18 --- /dev/null +++ b/marked/Rel-11/29_series/29011/cdd4dfacab004e9979caed3fffea69e5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7f4b7ade369fefff1b878252cf9c7b1aab67fc12f08b81e107b9d9f3c78a6a3c +size 16690 diff --git a/marked/Rel-11/29_series/29011/d9c0a780cd22626253dab4aa41699e2f_img.jpg b/marked/Rel-11/29_series/29011/d9c0a780cd22626253dab4aa41699e2f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..07564bbfbd0ed32bf12864d212d6d980ba28751b --- /dev/null +++ b/marked/Rel-11/29_series/29011/d9c0a780cd22626253dab4aa41699e2f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ddc7c8f537fa80ece10053a0ecfac1d9a30b5894067da58a070c009b7153c27a +size 41024 diff --git a/marked/Rel-11/29_series/29011/e4c6fa93821e3546ee9fcae897ae2771_img.jpg b/marked/Rel-11/29_series/29011/e4c6fa93821e3546ee9fcae897ae2771_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..21d0521c71b8b2047f01f6e285ad0e83f2a32315 --- /dev/null +++ b/marked/Rel-11/29_series/29011/e4c6fa93821e3546ee9fcae897ae2771_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d317def2911c5039b7de89467d76b72feb37ca6ef7a960260173686c84d88225 +size 12763 diff --git a/marked/Rel-11/29_series/29011/e518bff13dc73675afd211dbea636c29_img.jpg b/marked/Rel-11/29_series/29011/e518bff13dc73675afd211dbea636c29_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9fd4f97abfc55ee0699c9dbfa8067ef0e5341737 --- /dev/null +++ b/marked/Rel-11/29_series/29011/e518bff13dc73675afd211dbea636c29_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:288467bd9421b4f009ee7c8d361163a8aeb81f9278754f960bd6b2782aae0418 +size 30093 diff --git a/marked/Rel-11/29_series/29011/e58a867750e4ae01604318506b79df7a_img.jpg b/marked/Rel-11/29_series/29011/e58a867750e4ae01604318506b79df7a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..dc94bbc0863f72abf279144d224cf76463b79498 --- /dev/null +++ b/marked/Rel-11/29_series/29011/e58a867750e4ae01604318506b79df7a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c7c79973c84c08cb906066113867e283cbba6618ca33eb98be10a61603b65751 +size 23214 diff --git a/marked/Rel-11/29_series/29011/f68a5f1f8845159744eff3e0e786731e_img.jpg b/marked/Rel-11/29_series/29011/f68a5f1f8845159744eff3e0e786731e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b3e01ab5fe9457b116241a7602ba346198b33d55 --- /dev/null +++ b/marked/Rel-11/29_series/29011/f68a5f1f8845159744eff3e0e786731e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d8394a5c0dc434def4c13135ef6c4d07a797cddbf3ad7d105e86f2eb11472898 +size 36657 diff --git a/marked/Rel-11/29_series/29011/raw.md b/marked/Rel-11/29_series/29011/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..bd0b322490ff03518d717a29055205da557124be --- /dev/null +++ b/marked/Rel-11/29_series/29011/raw.md @@ -0,0 +1,1499 @@ + + + + + + +# Contents + +| | | +|---------------------------------------------------------------------------------------------------------|----| +| Foreword ..... | 5 | +| 1 Scope..... | 6 | +| 1.1 Normative references ..... | 6 | +| 1.2 Definitions and abbreviations..... | 7 | +| 2 Introduction..... | 8 | +| 2.1 MSC/VLR procedures for handling supplementary service signalling received over the A-interface..... | 8 | +| 2.2 MSC/VLR procedures for handling supplementary service signalling received over the D-interface..... | 8 | +| 3 SS version negotiation ..... | 8 | +| 3.1 Call related supplementary services interworking..... | 8 | +| 3.2 Call independent supplementary services interworking..... | 8 | +| 4 Mapping between TC transaction sublayer messages and layer 3 radio path messages..... | 9 | +| 4.1 D-interface to A-interface mapping ..... | 9 | +| 4.2 A-interface to D-interface mapping ..... | 9 | +| 4.3 Procedures ..... | 10 | +| 5 Call related supplementary services management ..... | 10 | +| 5.1 SS management in connection establishment phase ..... | 10 | +| 5.1.1 Line Identification services ..... | 10 | +| 5.1.1.1 Calling Line Identification Presentation (CLIP)..... | 11 | +| 5.1.1.2 Calling Line Identification Restriction (CLIR) ..... | 11 | +| 5.1.1.3 Connected Line Identification Presentation (COLP)..... | 11 | +| 5.1.1.4 Connected Line Identification Restriction (COLR)..... | 12 | +| 5.1.2 Call Forwarding services..... | 12 | +| 5.1.2.1 Notification to served mobile subscriber..... | 12 | +| 5.1.3 Call Waiting service (CW)..... | 12 | +| 5.1.3.1 Offering a waiting call ..... | 12 | +| 5.1.3.2 Notification of waiting call to calling subscriber..... | 13 | +| 5.1.4 Closed User Group service (CUG)..... | 13 | +| 5.1.4.1 Explicit invocation of a CUG call..... | 13 | +| 5.1.4.2 Notification of CUG invocation to served MS ..... | 14 | +| 5.1.4.3 Notification of rejection of CUG invocation to served MS..... | 14 | +| 5.1.4.4 Notification of CUG invocation to terminating MS ..... | 15 | +| 5.1.5 Advice of Charge services..... | 16 | +| 5.1.5.1 Notification of Charging information to served MS, mobile originated call..... | 16 | +| 5.1.5.2 Notification of Charging information to served MS, mobile terminated call..... | 16 | +| 5.1.6 Call Barring services ..... | 17 | +| 5.1.6.1 Barring of outgoing calls ..... | 17 | +| 5.1.6.2 Barring of incoming calls ..... | 17 | +| 5.1.7 CCBS call outcome ..... | 18 | +| 5.2 SS Management in stable connection state ..... | 18 | +| 5.2.1 Call Forwarding services..... | 18 | +| 5.2.1.1 Notification of invocation of CFB to served mobile subscriber..... | 18 | +| 5.2.2 Call Hold service (HOLD) ..... | 19 | +| 5.2.3 Multi Party service (MPTY)..... | 20 | +| 5.2.4 Advice of Charge services..... | 20 | +| 5.2.5 Explicit Call Transfer service (ECT)..... | 21 | +| 5.3 SS Management in disconnecting phase ..... | 21 | +| 5.3.1 Call Forwarding services..... | 22 | +| 5.3.2 CCBS Request Activation ..... | 22 | +| 5.3.3 Call Deflection service ..... | 23 | +| 5.3.3.1 Call Deflection Operation Request..... | 23 | +| 5.3.3.2 Call Deflection Operation Response..... | 23 | +| 6 Call independent supplementary services management..... | 24 | +| 6.1 MS initiated SS Management..... | 24 | +| 6.1.1 Connection establishment phase..... | 24 | +| 6.1.2 Connection established..... | 25 | + +6.1.3 Connection release.....26 +6.2 Network initiated SS Management .....26 +6.2.1 Connection establishment phase.....26 +6.2.2 Connection established.....26 +6.2.3 Connection release.....27 +6.2.4 ForwardCheckSSIndication.....27 +6.2.5 CCBS Recall.....27 +6.2.6 CCBS Monitoring.....28 +6.3 Mapping of Operation Codes, Error Codes, Parameter Tags and Parameter Contents .....29 +6.3.1 Operation codes .....29 +6.3.2 Error codes.....29 +6.3.3 Parameter tags and parameter values.....29 +Annex A (informative): Change history.....30 + +# --- Foreword + +This Technical Specification has been produced by the 3GPP. + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of this TS, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version 3.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 Indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the specification; + +# --- 1 Scope + +The scope of this Technical Specification is to provide a detailed specification for interworking between the A interface protocol and the Mobile Application Part for handling of supplementary services. The MAP interfaces of interest are the B-, C-, D- and E-interfaces. + +The A-, C-, D- and E-interfaces are physical interfaces while the B-interface is an internal interface defined for modelling purposes. Information relating to the modelling interface is not normative in this specification. + +Supplementary service signalling may be passed by the MSC/VLR between the A- and E-interfaces after inter-MSC handover. This procedure is transparent as far as supplementary services are concerned therefore interworking concerning this process is not described in this specification. + +Clause 2 describes general procedures for interworking between the A- and D- physical interfaces. + +Clause 3 describes the general procedures for the SS version negotiation. + +Clause 4 describes the mapping of layer 3 radio path messages with Transaction Capabilities (TC) transaction sublayer messages for interworking between the A- and D- physical interfaces. + +Clause 5 describes specific interworking procedures for all interfaces relating to call related SS activity. + +Clause 6 describes specific interworking procedures for all interfaces relating to call independent SS activity. Clause 6 also covers the interworking between the MAP User (see 3GPP TS 29.002) and the SS handling functions of the network entities (see 3GPP TS 24.010 and 3GPP TS 24.080). + +Reference is made to the following Technical Specifications: + +- 3GPP TS 22.004 and 3GPP TS 22.08x and 3GPP TS 22.09x-series, for definition of supplementary services; +- 3GPP TS 23.011, 3GPP TS 23.08x and 3GPP TS 23.09x-series, for technical realisation of supplementary services; +- 3GPP TS 24.010, 3GPP TS 24.080, 3GPP TS 24.08x and 3GPP TS 24.09x-series, for radio path signalling procedures for supplementary services; +- 3GPP TS 29.002 (MAP). + +## 1.1 Normative references + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. +- For a specific reference, subsequent revisions do not apply. +- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. + +- [1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications". +- [2] 3GPP TS 22.004: "General on supplementary services". +- [3] 3GPP TS 22.024: "Description of Charge Advice Information (CAI)". +- [4] 3GPP TS 22.082: "Call Forwarding (CF) supplementary services - Stage 1". +- [5] 3GPP TS 22.086: "Advice of Charge (AoC) supplementary services - Stage 1". +- [6] 3GPP TS 22.093: "Completion of Calls to Busy Subscriber - Stage 1". + +- [7] 3GPP TS 23.011: "Technical realization of supplementary services". +- [8] 3GPP TS 23.086: "Advice of Charge (AoC) supplementary services - Stage 2". +- [9] 3GPP TS 23.093: "Completion of Calls to Busy Subscriber - Stage 2". +- [10] 3GPP TS 24.008: "Mobile radio interface layer 3 specification". +- [11] 3GPP TS 24.010: "Mobile radio interface layer 3 Supplementary services specification General aspects". +- [12] 3GPP TS 24.072: "Call Deflection supplementary service - Stage 3". +- [13] 3GPP TS 24.080: "Mobile radio interface layer 3 supplementary services specification Formats and coding". +- [14] 3GPP TS 24.081: "Line identification supplementary services - Stage 3". +- [15] 3GPP TS 24.082: "Call Forwarding (CF) supplementary services - Stage 3". +- [16] 3GPP TS 24.083: "Call Waiting (CW) and Call Hold (HOLD) supplementary services - Stage 3". +- [17] 3GPP TS 24.084: "Multi Party (MPTY) supplementary services - Stage 3". +- [18] 3GPP TS 24.085: "Closed User Group (CUG) supplementary services - Stage 3". +- [19] 3GPP TS 24.086: "Advice of Charge (AoC) supplementary services - Stage 3". +- [20] 3GPP TS 24.088: "Call Barring (CB) supplementary services - Stage 3". +- [21] 3GPP TS 24.090: "Unstructured supplementary services operation - Stage 3". +- [22] 3GPP TS 24.091: "Explicit Call Transfer (ECT) supplementary services - Stage 3". +- [23] 3GPP TS 24.093: "Completion of Calls to Busy Subscriber - Stage 3". +- [24] 3GPP TS 29.002: "Mobile Application Part (MAP) specification". +- [25] 3GPP TS 29.010: "Information element mapping between Mobile Station - Base Station System and BSS - Mobile-services Switching Centre (MS - BSS - MSC) Signalling procedures and the Mobile Application Part (MAP)". +- [26] 3GPP TS 23.088: "Call Barring (CB) Supplementary Service; Stage 2". + +## 1.2 Definitions and abbreviations + +Abbreviations used in this specification are listed in 3GPP TR 21.905. + +# --- 2 Introduction + +This clause describes general procedure at the MSC/VLR for SS interworking between the A- and D-interfaces. + +## 2.1 MSC/VLR procedures for handling supplementary service signalling received over the A-interface + +Upon receipt of supplementary service signalling on the A-interface, the MSC/VLR shall: + +- perform any internal SS checks or procedures appropriate to the signal (see clauses 4 and 5); +- if necessary request access to the HLR over the D-interface using the procedures defined in this specification and MAP, 3GPP TS 29.002; + +- use the version indicator received from the MS to set up the right AC context name towards the HLR (see clause 3). The version indicator is described in 3GPP TS 24.010 and 3GPP TS 24.080. AC names are defined in 3GPP TS 29.002; +- perform mapping between layer 3 messages on the radio path and TC transaction sublayer messages as required (see clause 3). + +## 2.2 MSC/VLR procedures for handling supplementary service signalling received over the D-interface + +Upon receipt of supplementary service signalling on the D-interface, the MSC/VLR shall: + +- perform any internal SS checks or procedures appropriate to the signal (see clauses 4 and 5); +- handle any information elements according to the screening indicator procedure as described in 3GPP TS 24.010; +- perform mapping between TC transaction sublayer messages and layer 3 messages on the radio path as required (see clause 3). + +# --- 3 SS version negotiation + +This clause describes the general procedures for the call related and call independent supplementary services version negotiation. + +## 3.1 Call related supplementary services interworking + +No interworking identified. + +## 3.2 Call independent supplementary services interworking + +On receipt of the REGISTER message from the MS, the MSC/VLR will include the appropriate AC name in the dialogue control portion of the BEGIN message based on the following rules: + +- if no version indicator is present, no AC name is included in the BEGIN message towards the HLR (no AC name indicates "version1"); +- if the version indicator is less or equal to the highest AC name the MSC/VLR and HLR both support, the "dialogue" will be handled according to the AC name corresponding to the version indicator and to the SS operation received; +- if the version indicator is greater than the highest commonly supported AC name within the network (MSC/VLR, HLR), the "dialogue" will be handled according to this highest AC name if the request from the MS can also be fulfilled with this version of the "dialogue". + +The selection of the highest commonly supported AC name by the network is described in 3GPP TS 29.002. + +It should be noted that unknown parameters of the extension field within the Facility Information Element shall be forwarded to a phase 2 HLR according to the Extensibility rules as defined in 3GPP TS 29.002. They may be discarded when sent to a phase 1 HLR. + +According to this version of the standards, the highest AC name is "version3". + +The description method employed in the clauses 4 to 6 is tabled showing the mapping of parameter values. The exact values of the parameters and parameter tags can be found in the referenced specifications. + +# 4 Mapping between TC transaction sublayer messages and layer 3 radio path messages + +This clause describes the mapping of TC transaction sublayer messages to layer 3 radio path messages over the external interfaces. The precise coding of these messages is given in other technical specifications. + +## 4.1 D-interface to A-interface mapping + +Table 4.1 shows the mapping of TC transaction sublayer messages to layer 3 messages on the radio path. + +**Table 4.1: Mapping of TC transaction sublayer messages to layer 3 radio path messages** + +| TC transaction sublayer message | Layer 3 radio path message | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------| +| BEGIN | REGISTER (note 1) | +| CONTINUE (note 2) | FACILITY/REGISTER (note 3) | +| END (note 2) | RELEASE COMPLETE/REGISTER (note 3) | +| ABORT (note 2) | RELEASE COMPLETE | +| NOTE 1: AC name is not mapped to a version indicator.
NOTE 2: The user information field if present is discarded.
NOTE 3: A CONTINUE or END is mapped to REGISTER if a new transaction has to be established. | | + +## 4.2 A-interface to D-interface mapping + +Table 4.2 shows the mapping of layer 3 radio path messages to TC transaction sublayer messages. + +**Table 4.2: Mapping of layer 3 radio path messages to TC transaction sublayer messages** + +| Layer 3 radio path message | TC transaction sublayer message | +|----------------------------------------------------------|---------------------------------| +| REGISTER | BEGIN (note) | +| FACILITY | CONTINUE | +| RELEASE COMPLETE | END | +| NOTE: The right AC name shall be included, see clause 3. | | + +## 4.3 Procedures + +The mapping from TC Transaction Sublayer messages to Layer 3 radio path messages must include a replacement of the tag and length of the Component Portion in the Transaction Sublayer message with the Information element identifier and length of the Facility Information Element for the Layer 3 message. Similarly for the reverse mapping. However, if a version indicator is received an AC name will be provided in the BEGIN message, see clause 3. + +All transaction sublayer messages, except the ABORT message, will normally contain one or more components. If components are included, the conversion algorithm described below applies. If a message does not contain a component, then the corresponding message is also sent without a component: messages shall not be withheld by the interworking function. + +For call independent SS operations each message shall only contain a single component. If a message contains more than one component then a RELEASE COMPLETE message with the cause "Facility rejected" (see 3GPP TS 24.008) and without any component shall be sent on the radio path (see 3GPP TS 24.010). + +TC Transaction sublayer messages can also contain a dialogue portion. If a user-information is received within this dialogue portion, it will not be conveyed in a Layer 3 radio path message. + +If an ABORT message is received in TC, a RELEASE COMPLETE message is to be sent on the radio path. The RELEASE COMPLETE message shall not contain any component. If a cause is to be provided to the MS, one of the cause codes of 3GPP TS 24.008 shall be used. + +If an ABORT message with a dialogue portion indicating "version fallback" (e.g. the cause "AC-not-supported") is received in TC then, if the MSC does not re-attempt the "dialogue" (e.g. by using a different AC name), it shall send a RELEASE COMPLETE to the MS with the cause "Facility rejected" (see 3GPP TS 24.008) and without any component. + +If an END message with a dialogue portion indicating "dialogue refused" is received in TC then the MSC shall send a RELEASE COMPLETE to the MS with the cause "Facility rejected" (see 3GPP TS 24.008) and without any component. + +If a layer 3 radio path message or a component in the layer 3 radio path message is rejected by the MSC, the MSC shall: + +- return a RELEASE COMPLETE message to the MS. If the reject condition is not associated with a component, one of the cause codes of 3GPP TS 24.008 shall be inserted, as described below. If it is a component (except a REJECT component), a REJECT component with the appropriate problem code shall be inserted in the RELEASE COMPLETE message, as described below. If the reject condition concerns a REJECT component the RELEASE COMPLETE message may be empty; +- terminate the transaction with the VLR by use of an ABORT message. + +If a dialogue cannot be established with the HLR because no common AC name is available then the MSC shall send a RELEASE COMPLETE to the MS with the cause "Facility rejected". + +# 5 Call related supplementary services management + +## 5.1 SS management in connection establishment phase + +When a CM connection is being set up between an MS and an MSC, setting up of a connection between the MSC and the VLR to request access proceeds as for normal call set-up (see 3GPP TS 29.002). Moreover, the MSC will also assess the capabilities of the MS according to the screening indicator (see 3GPP TS 24.010 and 3GPP TS 24.080). As the call set-up proceeds, the following supplementary services may apply: + +### 5.1.1 Line Identification services + +These supplementary services (described in 3GPP TS 24.081) require interworking in the MSC between both 3GPP TS 24.008, MAP (3GPP TS 29.002) and the fixed network protocol, see also 3GPP TS 29.010. + +#### 5.1.1.1 Calling Line Identification Presentation (CLIP) + +The signalling at invocation of the CLIP supplementary service is shown in figure 5.1. + +![Sequence diagram showing signalling for CLIP supplementary service between MS, MSC, and VLR.](55a593259a0749ce342bd5eac2ba6b58_img.jpg) + +``` + +sequenceDiagram + participant MS + participant MSC + participant VLR + Note left of MS: MS + Note left of MSC: MSC + Note left of VLR: VLR + MSC->>VLR: SEND INFORMATION FOR INCOMING CALL SETUP + VLR-->>MSC: COMPLETE CALL + MSC-->>MS: SETUP + +``` + +The diagram illustrates the signalling sequence for the CLIP supplementary service. It involves three entities: MS (Mobile Station), MSC (Mobile Switching Center), and VLR (Visitor Location Register). The sequence of messages is as follows: + + +- The MSC sends a **SEND INFORMATION FOR INCOMING CALL SETUP** message to the VLR. +- The VLR responds with a **COMPLETE CALL** message to the MSC. +- Finally, the MSC sends a **SETUP** message to the MS. + +Sequence diagram showing signalling for CLIP supplementary service between MS, MSC, and VLR. + +**Figure 5.1: Signalling for CLIP supplementary service** + +When a call terminates at a mobile subscriber, the MSC obtains information on what supplementary services are active by analysing the SS-Data parameter in the MAP\_COMPLETE\_CALL service primitive on the B-interface. If this parameter indicates that the CLIP service is provided (and CLIR is not indicated in the incoming call set-up message from the PSTN), then the number of the calling subscriber (if received in the incoming call set-up) shall be mapped onto the Calling Party BCD number parameter in the SETUP message sent to the mobile. Exact values of the parameter and parameter tags are indicated in 3GPP TS 24.080 and 3GPP TS 24.081. + +#### 5.1.1.2 Calling Line Identification Restriction (CLIR) + +The signalling at invocation of the CLIR supplementary service is shown in figure 5.2. + +![Sequence diagram for CLIR supplementary service showing MS, MSC, and VLR entities. The MS sends a SETUP message to the MSC. The MSC sends a SEND INFORMATION FOR OUTGOING CALL SETUP message to the VLR. The VLR sends a COMPLETE CALL message back to the MSC.](7e670a2b556b53ea9002dfff3a420e08_img.jpg) + +``` + +sequenceDiagram + participant MS + participant MSC + participant VLR + MS->>MSC: SETUP + MSC->>VLR: SEND INFORMATION FOR OUTGOING CALL SETUP + VLR-->>MSC: COMPLETE CALL + +``` + +Sequence diagram for CLIR supplementary service showing MS, MSC, and VLR entities. The MS sends a SETUP message to the MSC. The MSC sends a SEND INFORMATION FOR OUTGOING CALL SETUP message to the VLR. The VLR sends a COMPLETE CALL message back to the MSC. + +**Figure 5.2: Signalling for CLIR supplementary service** + +When a call originates at a mobile subscriber, the MSC obtains information on what supplementary services are active by analysing the SS-Data parameter in the MAP\_COMPLETE\_CALL service primitive on the B-interface. If this parameter indicates that the CLIR service is provided and if the CLIR service shall be invoked (according to the presentation mode and possible subscriber request), then this information is indicated in the initial address message sent using the fixed network protocol (if possible). + +If this parameter indicates that the CLIR service is not provided and the calling subscriber has attempted to invoke CLIR, then the call set-up shall be rejected as defined in 3GPP TS 24.081. + +#### 5.1.1.3 Connected Line Identification Presentation (COLP) + +The signalling at invocation of the COLP supplementary service is shown in figure 5.3. + +![Sequence diagram for COLP supplementary service showing MS, MSC, and VLR entities. The MS sends a SETUP message to the MSC. The MSC sends a SEND INFORMATION FOR OUTGOING CALL SETUP message to the VLR. The VLR sends a COMPLETE CALL message back to the MSC. The MSC then sends a CONNECT message to the MS.](b3c108e7145f2017957569d06ea359cb_img.jpg) + +``` + +sequenceDiagram + participant MS + participant MSC + participant VLR + MS->>MSC: SETUP + MSC->>VLR: SEND INFORMATION FOR OUTGOING CALL SETUP + VLR-->>MSC: COMPLETE CALL + MSC-->>MS: CONNECT + +``` + +Sequence diagram for COLP supplementary service showing MS, MSC, and VLR entities. The MS sends a SETUP message to the MSC. The MSC sends a SEND INFORMATION FOR OUTGOING CALL SETUP message to the VLR. The VLR sends a COMPLETE CALL message back to the MSC. The MSC then sends a CONNECT message to the MS. + +**Figure 5.3: Signalling for COLP supplementary service** + +When a call originates at a mobile subscriber, the MSC obtains information on what supplementary services are active by analysing the SS-Data parameter in the MAP\_COMPLETE\_CALL service primitive on the B-interface. If this parameter indicates that the COLP service is provided, then if the connected line identity is made available by the terminating network (i.e. no interworking or presentation restrictions apply) then the connected number is passed to the calling mobile subscriber in the ConnectedNumber parameter in the CONNECT message. + +#### 5.1.1.4 Connected Line Identification Restriction (COLR) + +The signalling at invocation of the COLR supplementary service is shown in figure 5.4. + +![Sequence diagram for COLR supplementary service showing MS, MSC, and VLR entities. The MSC sends a SEND INFORMATION FOR INCOMING CALL SETUP message to the VLR. The VLR sends a COMPLETE CALL message back to the MSC. The MSC then sends a SETUP message to the MS.](e58a867750e4ae01604318506b79df7a_img.jpg) + +``` + +sequenceDiagram + participant MS + participant MSC + participant VLR + MSC->>VLR: SEND INFORMATION FOR INCOMING CALL SETUP + VLR-->>MSC: COMPLETE CALL + MSC-->>MS: SETUP + +``` + +Sequence diagram for COLR supplementary service showing MS, MSC, and VLR entities. The MSC sends a SEND INFORMATION FOR INCOMING CALL SETUP message to the VLR. The VLR sends a COMPLETE CALL message back to the MSC. The MSC then sends a SETUP message to the MS. + +**Figure 5.4: Signalling for COLR supplementary service** + +When a call terminates at a mobile subscriber, the MSC obtains information on what supplementary services are active by analysing the SS-Data parameter in the MAP\_COMPLETE\_CALL service primitive on the B-interface. If this parameter indicates that the COLR service is provided, then this information is sent to the originating network using the fixed network protocol (if possible). + +### 5.1.2 Call Forwarding services + +#### 5.1.2.1 Notification to served mobile subscriber + +As described in 3GPP TS 22.082, when a subscriber has any (set of) Call Forwarding service(s) active, a notification of this fact is sent to the MS at mobile originated call set-up from the served mobile subscriber. The signalling for this notification is shown in figure 5.5. + +![Figure 5.5: Signalling for notification of invocation of Call Forwarding supplementary service. The diagram shows three entities: MS, MSC, and VLR. The MS sends a SETUP message to the MSC. The MSC sends a SEND INFORMATION FOR OUTGOING CALL SETUP message to the VLR. The VLR sends a COMPLETE CALL message back to the MSC. The MSC then sends an ALERTING/CONNECT/FACILITY message back to the MS.](08441fa90c5fd11994626f662ac13f19_img.jpg) + +``` + +sequenceDiagram + participant MS + participant MSC + participant VLR + MS->>MSC: SETUP + MSC->>VLR: SEND INFORMATION FOR OUTGOING CALL SETUP + VLR-->>MSC: COMPLETE CALL + MSC-->>MS: ALERTING/CONNECT/FACILITY + +``` + +Figure 5.5: Signalling for notification of invocation of Call Forwarding supplementary service. The diagram shows three entities: MS, MSC, and VLR. The MS sends a SETUP message to the MSC. The MSC sends a SEND INFORMATION FOR OUTGOING CALL SETUP message to the VLR. The VLR sends a COMPLETE CALL message back to the MSC. The MSC then sends an ALERTING/CONNECT/FACILITY message back to the MS. + +**Figure 5.5: Signalling for notification of invocation of Call Forwarding supplementary service** + +The MSC obtains information on what supplementary services are active by analysing the SS-Data parameter in the MAP\_COMPLETE\_CALL service primitive on the B-interface. If this parameter indicates that a call forwarding service is active, then any of the ALERTING, CONNECT or FACILITY messages may be used to convey the required NotifySS operation in a Facility information element. Exact values of the parameter and parameter tags are indicated in 3GPP TS 24.080 and 3GPP TS 24.082. + +### 5.1.3 Call Waiting service (CW) + +#### 5.1.3.1 Offering a waiting call + +The signalling for this situation is shown in figure 5.6. + +![Figure 5.6: Signalling for setting up a waiting call. The diagram shows three entities: MS, MSC, and VLR. The MSC sends a SEND INFORMATION FOR INCOMING CALL SETUP message to the VLR. The VLR sends a PROCESS CW message back to the MSC. The MSC then sends a SETUP message back to the MS.](5a95b187de0044da69b7322e04761b86_img.jpg) + +``` + +sequenceDiagram + participant MS + participant MSC + participant VLR + MSC->>VLR: SEND INFORMATION FOR INCOMING CALL SETUP + VLR-->>MSC: PROCESS CW + MSC-->>MS: SETUP + +``` + +Figure 5.6: Signalling for setting up a waiting call. The diagram shows three entities: MS, MSC, and VLR. The MSC sends a SEND INFORMATION FOR INCOMING CALL SETUP message to the VLR. The VLR sends a PROCESS CW message back to the MSC. The MSC then sends a SETUP message back to the MS. + +**Figure 5.6: Signalling for setting up a waiting call** + +A waiting call is offered to a busy MS using a normal SETUP message including a "Signal" information element with value #7 (call waiting tone on), as described in 3GPP TS 24.083. This is the required MSC behaviour if it has received a MAP\_PROCESS\_CALL\_WAITING service primitive as a response to a MAP\_SEND\_INFO\_FOR\_INCOMING\_CALL service primitive on the B-interface. Exact values of the parameter and parameter tag are indicated in 3GPP TS 24.008. + +#### 5.1.3.2 Notification of waiting call to calling subscriber + +The signalling for this notification is shown in figure 5.7. + +![Figure 5.7: Signalling for notification of waiting call to calling subscriber. The diagram shows two entities: MS and MSC. The MSC sends an ALERTING message to the MS.](bdfe4e1058d1a0e14bb838771b57254c_img.jpg) + +``` + +sequenceDiagram + participant MS + participant MSC + MSC-->>MS: ALERTING + +``` + +Figure 5.7: Signalling for notification of waiting call to calling subscriber. The diagram shows two entities: MS and MSC. The MSC sends an ALERTING message to the MS. + +**Figure 5.7: Signalling for notification of waiting call to calling subscriber** + +If there are no network interworking limitations between the originating and destination MSCs, then the calling MS receives notification of his waiting call as follows: A Facility Information element in the ALERTING message includes a NotifySS operation with the following parameters: + +- SS-Code parameter indicates "callWaiting"; +- CallIsWaitingIndicator parameter indicates "callIsWaiting". + +Exact values of the parameter and parameter tags are indicated in 3GPP TS 24.080 and 3GPP TS 24.083. + +### 5.1.4 Closed User Group service (CUG) + +#### 5.1.4.1 Explicit invocation of a CUG call + +The signalling for this situation is shown in figure 5.8. + +![Figure 5.8: Signalling at explicit invocation of a CUG call. The diagram shows three entities: MS, MSC, and VLR. The MS sends a SETUP message to the MSC. The MSC then sends a SEND INFORMATION FOR OUTGOING CALL SETUP message to the VLR.](4636adff5682a064f0ae5f13a1d464a6_img.jpg) + +``` + +sequenceDiagram + participant MS + participant MSC + participant VLR + Note left of MS: MS + Note left of MSC: MSC + Note left of VLR: VLR + MS->>MSC: SETUP + MSC->>VLR: SEND INFORMATION FOR OUTGOING CALL SETUP + +``` + +Figure 5.8: Signalling at explicit invocation of a CUG call. The diagram shows three entities: MS, MSC, and VLR. The MS sends a SETUP message to the MSC. The MSC then sends a SEND INFORMATION FOR OUTGOING CALL SETUP message to the VLR. + +**Figure 5.8: Signalling at explicit invocation of a CUG call** + +When a subscriber to the CUG supplementary service sets up a call, an explicit invocation involves transport of a ForwardCUG-Info operation in a Facility information element in the SETUP message. Parameter mapping between the air-interface SETUP message and the B-interface MAP\_SEND\_INFO\_FOR\_OUTGOING\_CALL service primitive shall take place in the MSC. Exact values of the parameter and parameter tags are indicated in 3GPP TS 24.080 and 3GPP TS 24.085. The parameter tags and values are mapped as follows: + +**Table 5.1: Mapping of parameter names and values for explicit invocation of a CUG call** + +| 3GPP TS 24.080 parameter name | 3GPP TS 29.002 parameter name | +|-------------------------------|-------------------------------| +| cug-Index | cug-Index | +| suppressPrefCUG | suppressPrefCUG | +| suppressOA | suppressOutgoingAccess | + +#### 5.1.4.2 Notification of CUG invocation to served MS + +The signalling for this situation is shown in figure 5.9. + +![Figure 5.9: Signalling flow for notification of CUG invocation to served MS. The diagram shows three entities: MS, MSC, and VLR. The MSC sends a SEND INFORMATION FOR INCOMING CALL SETUP message to the VLR. The VLR then sends a COMPLETE CALL message back to the MSC. Finally, the MSC sends a CALL PROCEEDING/FACILITY message to the MS.](cce70c739081f63a6af83dc9483f98ce_img.jpg) + +``` + +sequenceDiagram + participant MS + participant MSC + participant VLR + Note left of MSC: MSC + Note left of VLR: VLR + MSC->>VLR: SEND INFORMATION FOR INCOMING CALL SETUP + VLR->>MSC: COMPLETE CALL + MSC->>MS: CALL PROCEEDING/FACILITY + +``` + +Figure 5.9: Signalling flow for notification of CUG invocation to served MS. The diagram shows three entities: MS, MSC, and VLR. The MSC sends a SEND INFORMATION FOR INCOMING CALL SETUP message to the VLR. The VLR then sends a COMPLETE CALL message back to the MSC. Finally, the MSC sends a CALL PROCEEDING/FACILITY message to the MS. + +**Figure 5.9: Signalling flow for notification of CUG invocation to served MS** + +The network may indicate to the MS that a CUG has been invoked for the outgoing call by sending a NotifySS operation in the Facility information element in the FACILITY or CALL PROCEEDING message towards MSs. The parameter to be included in this operation (cug-Index) is obtained from the MAP\_COMPLETE\_CALL service primitive. Exact values of the parameter and parameter tags are indicated in 3GPP TS 24.080 and 3GPP TS 24.085. + +#### 5.1.4.3 Notification of rejection of CUG invocation to served MS + +The signalling for this situation is shown in figure 5.10. + +![Figure 5.10: Signalling flow for notification of rejection of CUG invocation to served MS. The diagram shows three vertical lifelines: MS, MSC, and VLR. The sequence of messages is: 1. MS sends a SETUP message to MSC. 2. MSC sends a SEND INFORMATION FOR OUTGOING CALL SETUP message to VLR. 3. VLR sends a SEND INFORMATION FOR OUTGOING CALL SETUP ERROR message back to MSC. 4. MSC sends a DISCONNECT/RELEASE/RELEASE COMPLETE message back to MS.](a33da0f14e456f92539ce3e9b7d81f9a_img.jpg) + +``` + +sequenceDiagram + participant MS + participant MSC + participant VLR + Note left of MS: MS + MS->>MSC: SETUP + Note right of MSC: MSC + MSC->>VLR: SEND INFORMATION FOR OUTGOING CALL SETUP + Note right of VLR: VLR + VLR-->>MSC: SEND INFORMATION FOR OUTGOING CALL SETUP ERROR + MSC-->>MS: DISCONNECT/ +RELEASE/ +RELEASE COMPLETE + +``` + +Figure 5.10: Signalling flow for notification of rejection of CUG invocation to served MS. The diagram shows three vertical lifelines: MS, MSC, and VLR. The sequence of messages is: 1. MS sends a SETUP message to MSC. 2. MSC sends a SEND INFORMATION FOR OUTGOING CALL SETUP message to VLR. 3. VLR sends a SEND INFORMATION FOR OUTGOING CALL SETUP ERROR message back to MSC. 4. MSC sends a DISCONNECT/RELEASE/RELEASE COMPLETE message back to MS. + +**Figure 5.10: Signalling flow for notification of rejection of CUG invocation to served MS** + +When an attempted CUG call is rejected for CUG related reasons, mapping of parameter values take places in order to inform the MSa of the failure in the DISCONNECT, RELEASE or RELEASE COMPLETE message. If the call is rejected by the serving VLR, a mapping of errors received on the B-interface (as response to MAP\_SEND\_INFO\_FOR\_OUTGOING\_CALL) to diagnostics (in the diagnostics field of the Facility Rejected cause value) must be performed. The mapping from error code to diagnostic is as follows (detailed values of tags, cause values and diagnostics are found in 3GPP TS 29.002, 3GPP TS 24.008, and 3GPP TS 24.080 respectively): + +**Table 5.2: Mapping of 3GPP TS 29.002 error causes to diagnostics at notification of rejection of CUG invocation to served MS** + +| 3GPP TS 29.002 error cause | Facility rejected #29 diagnostic field | +|---------------------------------------------|-------------------------------------------------| +| outgoingCallsBarredWithinCUG | Outgoing calls barred within the CUG | +| noCUG-Selected | No CUG selected | +| unknownCUG-Index | Unknown CUG index | +| indexIncompatibleWith RequestedBasicService | Index incompatible with requested basic service | + +If there are no network interworking restrictions (i.e. originating MSC = gateway MSC = terminating MSC), interworking between MAP and the air-interface takes place also for rejection of CUG calls by terminating end. The signalling for this situation is shown in figure 5.11. + +![Figure 5.11: Signalling flow for notification of rejection of CUG invocation from terminating end. The diagram shows three vertical lifelines: MSa, MSC, and HLR. The sequence of messages is: 1. MSC sends a SEND ROUTING INFO / SEND ROUTING INFO SMS (for MSb) message to HLR. 2. HLR sends a SEND ROUTING INFO message back to MSC. 3. MSC sends a DISCONNECT/RELEASE/RELEASE COMPLETE message back to MSa.](c036e2540a94b31357ceb0002f0cacab_img.jpg) + +``` + +sequenceDiagram + participant MSa + participant MSC + participant HLR + Note left of MSC: MSa + MSC->>HLR: SEND ROUTING INFO/ +SEND ROUTING INFO SMS +(for MSb) + Note right of HLR: HLR + HLR-->>MSC: SEND ROUTING INFO + MSC-->>MSa: DISCONNECT/ +RELEASE/ +RELEASE COMPLETE + +``` + +Figure 5.11: Signalling flow for notification of rejection of CUG invocation from terminating end. The diagram shows three vertical lifelines: MSa, MSC, and HLR. The sequence of messages is: 1. MSC sends a SEND ROUTING INFO / SEND ROUTING INFO SMS (for MSb) message to HLR. 2. HLR sends a SEND ROUTING INFO message back to MSC. 3. MSC sends a DISCONNECT/RELEASE/RELEASE COMPLETE message back to MSa. + +**Figure 5.11: Signalling flow for notification of rejection of CUG invocation from terminating end** + +The mapping from error code to diagnostic is as follows (detailed values of tags, cause values and diagnostics are found in 3GPP TS 29.002, 3GPP TS 24.008, and 3GPP TS 24.080 respectively): + +**Table 5.3: Mapping of 3GPP TS 29.002 error causes to cause values at notification of rejection by terminating end** + +| 3GPP TS 29.002 error cause | Cause information element (cause value) | +|-----------------------------------|-------------------------------------------------------------------------| +| calledPartySSInteractionViolation | Facility Rejected #29,
Diagnostic = CUG call failure,
unspecified | +| incomingCallsBarredWithinCUG | Incoming calls barred within the CUG #55 | +| subscriberNotMemberOfCUG | User not a member of CUG #87 | + +requestedBasicServiceViolatesCUG-Constraints + +Facility Rejected #29 + +#### 5.1.4.4 Notification of CUG invocation to terminating MS + +The signalling for this situation is shown in figure 5.12. + +![Figure 5.12: Signalling flow for notification of CUG invocation to terminating end. The diagram shows three lifelines: MS, MSC, and VLR. The sequence of messages is: 1. MSC sends 'SEND INFORMATION FOR INCOMING CALL SETUP' to VLR. 2. VLR sends 'COMPLETE CALL/ PROCESS CALL WAITING' back to MSC. 3. MSC sends 'SETUP' to MS.](bffdddb47fced140f8d17fdc2a29f592_img.jpg) + +``` + +sequenceDiagram + participant MS + participant MSC + participant VLR + MSC->>VLR: SEND INFORMATION FOR INCOMING CALL SETUP + VLR-->>MSC: COMPLETE CALL/ PROCESS CALL WAITING + MSC-->>MS: SETUP + +``` + +Figure 5.12: Signalling flow for notification of CUG invocation to terminating end. The diagram shows three lifelines: MS, MSC, and VLR. The sequence of messages is: 1. MSC sends 'SEND INFORMATION FOR INCOMING CALL SETUP' to VLR. 2. VLR sends 'COMPLETE CALL/ PROCESS CALL WAITING' back to MSC. 3. MSC sends 'SETUP' to MS. + +**Figure 5.12: Signalling flow for notification of CUG invocation to terminating end** + +When a CUG call arrives at the terminating end, the CUG index associated with the invoked CUG may be passed to the mobile station. The *cug-Index* parameter is obtained from the fixed network connection establishment request message, or if no fixed network protocol is involved (i.e. originating = terminating MSC), it is obtained from the *MAP\_COMPLETE\_CALL* or *MAP\_PROCESS\_CALL\_WAITING* service primitive. Its value is mapped onto the *cug-Index* parameter in the *NotifySS* operation in the *Facility Information* element of the *SETUP* message on the air-interface. Exact values of the parameter and parameter tags are indicated in 3GPP TS 24.080 and 3GPP TS 24.085. + +### 5.1.5 Advice of Charge services + +#### 5.1.5.1 Notification of Charging information to served MS, mobile originated call + +The signalling for this situation is shown in figure 5.13. + +![Figure 5.13: Signalling flow for notification of Mobile originated Charging Information to served MS. The diagram shows three lifelines: MSa, MSC, and VLR. The sequence of messages is: 1. VLR sends 'COMPLETE CALL' to MSC. 2. MSC sends 'CONNECT/ FACILITY' to MSa.](e4c6fa93821e3546ee9fcae897ae2771_img.jpg) + +``` + +sequenceDiagram + participant MSa + participant MSC + participant VLR + VLR-->>MSC: COMPLETE CALL + MSC-->>MSa: CONNECT/ FACILITY + +``` + +Figure 5.13: Signalling flow for notification of Mobile originated Charging Information to served MS. The diagram shows three lifelines: MSa, MSC, and VLR. The sequence of messages is: 1. VLR sends 'COMPLETE CALL' to MSC. 2. MSC sends 'CONNECT/ FACILITY' to MSa. + +**Figure 5.13: Signalling flow for notification of Mobile originated Charging Information to served MS** + +The network may indicate charging information to the MS at mobile originated call set-up. The MSC knows charging information is applicable due to the inclusion of an *SS-Code* indicating *Advice Of Charge Charging* or *Advice Of Charge Information* in the *MAP\_COMPLETE\_CALL* service indication from the VLR. This parameter's value is mapped onto the *SS-Code* parameter in the *ForwardChargeAdvice* operation which is to be sent to the MS together with the relevant charging parameters. The *ForwardChargeAdvice* operation shall be sent in the facility information element of either the *CONNECT* or the *FACILITY* message. Exact values of the parameter and parameter tags are indicated in 3GPP TS 24.080 and 3GPP TS 24.085. + +#### 5.1.5.2 Notification of Charging information to served MS, mobile terminated call + +The signalling for this situation is shown in figure 5.14. + +![Figure 5.14: Signalling flow for notification of Mobile terminated Charging Information to served MS. The diagram shows three lifelines: MSb, MSC, and VLR. The sequence of messages is: 1. VLR sends 'COMPLETE CALL' to MSC. 2. MSC sends 'FACILITY' to MSb.](95cd9f56a54683029052b8c644228506_img.jpg) + +``` + +sequenceDiagram + participant MSb + participant MSC + participant VLR + VLR-->>MSC: COMPLETE CALL + MSC-->>MSb: FACILITY + +``` + +Figure 5.14: Signalling flow for notification of Mobile terminated Charging Information to served MS. The diagram shows three lifelines: MSb, MSC, and VLR. The sequence of messages is: 1. VLR sends 'COMPLETE CALL' to MSC. 2. MSC sends 'FACILITY' to MSb. + +**Figure 5.14: Signalling flow for notification of Mobile terminated Charging Information to served MS** + +The network may indicate charging information to the MS at mobile terminated call set-up. The MSC knows charging information is applicable due to the inclusion of an SS-Code indicating Advice Of Charge Charging or Advice of Charge Information in the SS-Data parameter included in the MAP\_COMPLETE\_CALL service indication from the VLR. This parameter's value is mapped onto the SS-Code parameter in the ForwardChargeAdvice operation which is to be sent to the MS together with the relevant charging parameters. The ForwardChargeAdvice operation shall be sent in the facility information element of the FACILITY message. Exact values of the parameter and parameter tags are indicated in 3GPP TS 24.080 and 3GPP TS 24.085. + +### 5.1.6 Call Barring services + +These supplementary services (described in 3GPP TS 24.088) require the following interworking in the MSC: + +#### 5.1.6.1 Barring of outgoing calls + +The signalling for this situation is shown in figure 5.15. + +![Figure 5.15: Signalling flow for barring of an outgoing call. The diagram shows three vertical lifelines: MS, MSC, and VLR. The MS sends a RELEASE COMPLETE message to the MSC. The MSC sends a SEND INFORMATION FOR OUTGOING CALL SETUP / SEND INFORMATION FOR MOBILE ORIGINATED SMS message to the VLR. The VLR responds with a SEND INFORMATION FOR OUTGOING CALL SETUP ERROR / SEND INFORMATION FOR MOBILE ORIGINATED SMS ERROR / ERROR message to the MSC. The MSC then sends a RELEASE COMPLETE message back to the MS.](b90144cfbb81a2d610d920240fda689d_img.jpg) + +``` + +sequenceDiagram + participant MS + participant MSC + participant VLR + Note left of MS: RELEASE COMPLETE + MSC->>VLR: SEND INFORMATION FOR OUTGOING CALL SETUP / +SEND INFORMATION FOR MOBILE ORIGINATED SMS + VLR-->>MSC: SEND INFORMATION FOR OUTGOING CALL SETUP ERROR / +SEND INFORMATION FOR MOBILE ORIGINATED SMS ERROR / +ERROR + MSC-->>MS: RELEASE COMPLETE + +``` + +Figure 5.15: Signalling flow for barring of an outgoing call. The diagram shows three vertical lifelines: MS, MSC, and VLR. The MS sends a RELEASE COMPLETE message to the MSC. The MSC sends a SEND INFORMATION FOR OUTGOING CALL SETUP / SEND INFORMATION FOR MOBILE ORIGINATED SMS message to the VLR. The VLR responds with a SEND INFORMATION FOR OUTGOING CALL SETUP ERROR / SEND INFORMATION FOR MOBILE ORIGINATED SMS ERROR / ERROR message to the MSC. The MSC then sends a RELEASE COMPLETE message back to the MS. + +Figure 5.15: Signalling flow for barring of an outgoing call + +If the error code "CallBarred" is received as a response to the MAP\_SEND\_INFO\_FOR\_OUTGOING\_CALL or MAP\_SEND\_INFO\_FOR\_MO\_SMS service primitives on the B-interface, then a RELEASE COMPLETE message with a NotifySS operation shall be sent to the originating MS, as described in 3GPP TS 24.088. The mapping of 3GPP TS 29.002 callBarringCause to 3GPP TS 24.008 cause values is shown in table 5.4. Exact values of the parameter and parameter tags are indicated in 3GPP TS 24.080, 3GPP TS 24.088 and 3GPP TS 24.008. + +Table 5.4: Mapping of 3GPP TS 29.002 callBarringCause to 3GPP TS 24.008 cause values at barring of outgoing call + +| 3GPP TS 29.002 callBarringCause | 3GPP TS 24.008 Cause value | +|---------------------------------|---------------------------------| +| barringServiceActive | #31: Normal Unspecified | +| operatorBarring | #8: Operator Determined Barring | +| (None) | #21: Call Rejected | + +#### 5.1.6.2 Barring of incoming calls + +The signalling for this situation is shown in figure 5.16. + +![Figure 5.16: Signalling flow for barring of an incoming call. The diagram shows three vertical lifelines: MSa, GMSC, and HLRb. The GMSC sends a SEND ROUTING INFO / SEND ROUTING INFO_SMS (for MSb) message to the HLRb. The HLRb responds with a SEND ROUTING INFO / ERROR message to the GMSC. The GMSC then sends a DISCONNECT / RELEASE / RELEASE COMPLETE message to the MSa.](e518bff13dc73675afd211dbea636c29_img.jpg) + +``` + +sequenceDiagram + participant MSa + participant GMSC + participant HLRb + GMSC->>HLRb: SEND ROUTING INFO / +SEND ROUTING INFO_SMS +(for MSb) + HLRb-->>GMSC: SEND ROUTING INFO / +ERROR + GMSC-->>MSa: DISCONNECT / +RELEASE / +RELEASE COMPLETE + +``` + +Figure 5.16: Signalling flow for barring of an incoming call. The diagram shows three vertical lifelines: MSa, GMSC, and HLRb. The GMSC sends a SEND ROUTING INFO / SEND ROUTING INFO\_SMS (for MSb) message to the HLRb. The HLRb responds with a SEND ROUTING INFO / ERROR message to the GMSC. The GMSC then sends a DISCONNECT / RELEASE / RELEASE COMPLETE message to the MSa. + +Figure 5.16: Signalling flow for barring of an incoming call + +If the error code "CallBarred" is received as a response to the MAP\_SEND\_ROUTING\_INFO or MAP\_SEND\_ROUTING\_INFO\_FOR\_SM service primitives on the D-interface, then if no network interworking limitations apply, a NotifySS operation shall be sent to the originating MS in the first clearing message, as described in 3GPP TS 24.088. The mapping of 3GPP TS 29.002 error causes to 3GPP TS 24.008 cause values is shown in table 5.5. Exact values of the parameter and parameter tags are indicated in 3GPP TS 24.080, 3GPP TS 24.088 and 3GPP TS 24.008. + +**Table 5.5: Mapping of 3GPP TS 29.002 error causes to cause values at barring of incoming call** + +| 3GPP TS 29.002 error cause | Cause value | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------| +| barringServiceActive | #21: Call Rejected | +| operatorBarring | #21: Call Rejected | +| anonymousCallRejection | #31: Normal, unspecified (NOTE) | +| (None) | #21: Call Rejected | +| NOTE: The GMSC will play an announcement towards the calling user to signal that the call is rejected due to anonymous call rejection. See 3GPP TS 23.088 [26]. | | + +### 5.1.7 CCBS call outcome + +For the purpose of monitoring the destination B (the target of a CCBS request activated by subscriber A), the HLR on the B-side needs to know the outcome of a CCBS call. A CCBS call is a call being set-up after acceptance of a recall (indication to subscriber A that B is idle). Thus, in case of a CCBS call, on receipt of call related messages from the MS, the MSC shall send (via the VLR) the MAP\_STATUS\_REPORT to the HLR. + +![Sequence diagram showing signalling for CCBS call outcome between MS, MSC, VLR, and HLR.](43837b056625d3d6ce615e4c02f163bb_img.jpg) + +``` + +sequenceDiagram + participant MS + participant MSC + participant VLR + participant HLR + + Note left of MS: MS + Note left of MSC: MSC + Note left of VLR: VLR + Note left of HLR: HLR + + MS->>MSC: SETUP + Note right of MSC: CONNECT/ +ALERTING/ +DISCONNECT/ +RELEASE/ +RELEASE +COMPLETE + MSC->>MS: CONNECT/ +ALERTING/ +DISCONNECT/ +RELEASE/ +RELEASE +COMPLETE + MSC->>VLR: CCBS CALL DELIVERY + VLR->>HLR: STATUS_REPORT + +``` + +Sequence diagram showing signalling for CCBS call outcome between MS, MSC, VLR, and HLR. + +**Figure 5.16a: Signalling for CCBS call outcome** + +The CONNECT or ALERTING messages imply that the call establishment has been successful. Then the value of the Outcome information element in the MAP\_STATUS\_REPORT is set to success. + +The DISCONNECT and RELEASE are, in this case, error messages and can contain different causes (e.g. *Call Rejected* or *User Busy*). The MSC translates the message and/or the cause received into the proper value for the Outcome information element (*Failure* or *Busy*). + +Exact coding and values of the messages and parameter tags can be found in 3GPP TS 24.008 and 3GPP TS 29.002. + +## 5.2 SS Management in stable connection state + +When a stable CM connection is set up between a mobile station and the network, the following supplementary services may apply: + +### 5.2.1 Call Forwarding services + +#### 5.2.1.1 Notification of invocation of CFB to served mobile subscriber + +As described in 3GPP TS 22.082, when the Call Forwarding on MS Busy service is invoked by the network, a notification of this fact may be sent to the MS. The signalling for the situation when the user is NDUB is shown in figure 5.17. Note that if the subscriber is not NDUB, this notification does not apply. + +![Figure 5.17: Signalling for notification of invocation of CFB supplementary service. The diagram shows three vertical lifelines: MS, MSC, and VLR. The sequence of messages is: 1. MSC sends 'SEND INFORMATION FOR INCOMING CALL SETUP' to VLR. 2. VLR sends 'COMPLETE CALL' back to MSC. 3. MSC sends 'FACILITY' to MS. A label 'NDUB established' is placed between the MSC and MS lifelines.](8592a32c2fdf17c1e562f0ba6b7e8e1a_img.jpg) + +``` + +sequenceDiagram + participant MS + participant MSC + participant VLR + Note right of MSC: NDUB established + MSC->>VLR: SEND INFORMATION FOR INCOMING CALL SETUP + VLR-->>MSC: COMPLETE CALL + MSC-->>MS: FACILITY + +``` + +Figure 5.17: Signalling for notification of invocation of CFB supplementary service. The diagram shows three vertical lifelines: MS, MSC, and VLR. The sequence of messages is: 1. MSC sends 'SEND INFORMATION FOR INCOMING CALL SETUP' to VLR. 2. VLR sends 'COMPLETE CALL' back to MSC. 3. MSC sends 'FACILITY' to MS. A label 'NDUB established' is placed between the MSC and MS lifelines. + +**Figure 5.17: Signalling for notification of invocation of CFB supplementary service** + +The MSC obtains information on what supplementary services are active by analysing the SS-Data parameter in the MAP\_COMPLETE\_CALL service primitive on the B-interface. If this parameter indicates that CFB is active, then the FACILITY message may be used to convey the required NotifySS operation in a Facility information element. Exact values of the parameter and parameter tags are indicated in 3GPP TS 24.080 and 3GPP TS 24.082. + +### 5.2.2 Call Hold service (HOLD) + +As described in 3GPP TS 24.083, an MS can at any time during the active phase of a call signal invocation of the Call Hold supplementary service towards the network. This is done by use of the HOLD message (defined in 3GPP TS 24.080). When the MSC receives such a message, it requests access to the VLR and sends the MAP\_INVOKE\_SS service primitive to the VLR (as described in 3GPP TS 29.002). The interworking function triggers this behaviour by sending an internal MAP\_INVOKE\_SS signal to the MAP Service User of the MSC, indicating the following parameter values: + +- SS-Code = Call Hold; +- BS-Code = Basic service of the on-going call. + +The signalling for this situation is shown in figure 5.18. Exact values of the parameter and parameter tags are indicated in 3GPP TS 24.080, 3GPP TS 24.083 and 3GPP TS 29.002. + +![Figure 5.18: Signalling flow at invocation of Call Hold supplementary service. The diagram shows three vertical lifelines: MS, MSC, and VLR. The sequence of messages is: 1. MS sends 'HOLD' to MSC. 2. MSC sends 'INVOKESS' to VLR. 3. VLR sends 'INVOKESS ACK' back to MSC. 4. MSC sends 'HOLD ACK/HOLD REJ' back to MS.](7b8b192e2853ef28d28eff0241ebe86b_img.jpg) + +``` + +sequenceDiagram + participant MS + participant MSC + participant VLR + MS->>MSC: HOLD + MSC->>VLR: INVOKESS + VLR-->>MSC: INVOKESS ACK + MSC-->>MS: HOLD ACK/HOLD REJ + +``` + +Figure 5.18: Signalling flow at invocation of Call Hold supplementary service. The diagram shows three vertical lifelines: MS, MSC, and VLR. The sequence of messages is: 1. MS sends 'HOLD' to MSC. 2. MSC sends 'INVOKESS' to VLR. 3. VLR sends 'INVOKESS ACK' back to MSC. 4. MSC sends 'HOLD ACK/HOLD REJ' back to MS. + +**Figure 5.18: Signalling flow at invocation of Call Hold supplementary service** + +If the A\_INVOKE\_SS signal from the MAP Service User in the MSC is empty, the HOLD ACKNOWLEDGE message is returned to the MS. If it refers to an error, the mapping of error causes takes place according to table 5.6. Exact values of the parameter tags are indicated in 3GPP TS 24.080 and 3GPP TS 29.002. + +**Table 5.6: Mapping of 3GPP TS 29.002 operation errors to 3GPP TS 24.080 HOLD REJECT causes** + +| 3GPP TS 29.002 operation error | 3GPP TS 24.080 HOLD REJECT cause | +|--------------------------------|--------------------------------------------| +| SystemFailure | #63: Service/Option not available | +| DataMissing | #100: Invalid Information Element contents | +| UnexpectedDataValue | #100: Invalid Info. element contents | +| CallBarred | #29: Facility Rejected | +| IllegalSS-Operation | #50: Requested Facility not subscribed | +| SS-ErrorStatus | #50: Requested facility not subscribed | +| SS-NotAvailable | #69: Requested facility not implemented | + +Note that Call Retrieval requires no communication on the B-interface, and thus no interworking requirements have been identified. + +### 5.2.3 Multi Party service (MPTY) + +As described in 3GPP TS 24.084, an MS can at any time during the active phase of a call signal invocation of the Multi Party supplementary service towards the network. This is done by including a BuildMPTY operation (defined in 3GPP TS 24.080) in a FACILITY message. When the MSC receives such a request, it requests access to the VLR and sends the MAP\_INVOKE\_SS service primitive to the VLR (as described in 3GPP TS 29.002). The interworking function triggers this behaviour by sending an internal MAP\_INVOKE\_SS signal to the MAP Service User of the MSC, indicating the following parameter values: + +- SS-Code = MPTY; +- BS-Code = Basic Service Code of the on-going calls. + +Note that the MSC does not allow the MPTY to be invoked if the two calls are not telephony calls. + +The signalling for this situation is shown in figure 5.19. + +![Sequence diagram showing the signalling flow for Multi Party supplementary service invocation. The diagram involves three entities: MS, MSC, and VLR. The MS sends a 'buildMPTY' message to the MSC. The MSC sends an 'INVOKESS' message to the VLR. The VLR returns an 'INVOKESS ACK' message to the MSC. Finally, the MSC sends a return 'buildMPTY' message to the MS.](cdd4dfacab004e9979caed3fffea69e5_img.jpg) + +``` + +sequenceDiagram + participant MS + participant MSC + participant VLR + Note left of MS: MS + Note left of MSC: MSC + Note left of VLR: VLR + MS->>MSC: buildMPTY + MSC->>VLR: INVOKESS + VLR-->>MSC: INVOKESS ACK + MSC-->>MS: buildMPTY + +``` + +Sequence diagram showing the signalling flow for Multi Party supplementary service invocation. The diagram involves three entities: MS, MSC, and VLR. The MS sends a 'buildMPTY' message to the MSC. The MSC sends an 'INVOKESS' message to the VLR. The VLR returns an 'INVOKESS ACK' message to the MSC. Finally, the MSC sends a return 'buildMPTY' message to the MS. + +Figure 5.19: Signalling flow at invocation of Multi Party supplementary service + +If the A\_INVOKE\_SS signal from the MAP Service User in the MSC is empty, the BuildMPTY return result is returned to the MS in a FACILITY message. If it refers to an error, the mapping of errors takes place according to table 5.7. + +**Table 5.7: Mapping of 3GPP TS 29.002 operation errors to 3GPP TS 24.080 BuildMPTY errors** + +| 3GPP TS 29.002 operation error | 3GPP TS 24.080 BuildMPTY error | +|--------------------------------|--------------------------------| +| SystemFailure | SystemFailure | +| DataMissing | SystemFailure | +| UnexpectedDataValue | SystemFailure | +| CallBarred | IllegalSS-Operation | +| IllegalSS-Operation | IllegalSS-Operation | +| SS-ErrorStatus | SS-ErrorStatus | +| SS-NotAvailable | SS-NotAvailable | + +Note that Holding, Retrieving and Splitting a multi party requires no communication on the B-interface, and thus no interworking requirements have been identified. + +### 5.2.4 Advice of Charge services + +**Notification of Charging information to served MS during the call** + +The network may indicate revised charging parameters (as required according to 3GPP TS 22.024, 3GPP TS 22.086, 3GPP TS 23.086 and 3GPP TS 24.086) to the MS during a call. The parameters are forwarded to MSs using the ForwardChargeAdvice operation in the facility information element of the FACILITY message. Exact values of the parameter and parameter tags are indicated in 3GPP TS 24.080 and 3GPP TS 24.085. + +### 5.2.5 Explicit Call Transfer service (ECT) + +As described in 3GPP TS 24.091, an MS can at any time during the active phase of a call signal invocation of the Explicit Call Transfer supplementary service towards the network. This is done by including a ExplicitCT operation (defined in 3GPP TS 24.080) in a FACILITY message. When the MSC receives such a request, it requests access to the VLR and sends the MAP\_INVOKE\_SS service primitive to the VLR (as described in 3GPP TS 29.002). The interworking function triggers this behaviour by sending an internal MAP\_INVOKE\_SS signal to the MAP Service User of the MSC, indicating the following parameter values: + +- SS-Code = ect; +- BS-Code = Basic Service Code of the on-going calls. + +Note that the MSC does not allow the ECT to be invoked if the two calls are not telephony calls. + +The signalling for this situation is shown in the following figure 5.21. + +![Figure 5.21: Signalling flow at invocation of Explicit Call Transfer supplementary service. The diagram shows three vertical dashed lines representing the MS, MSC, and VLR. The MS sends an 'explicitCT' message to the MSC. The MSC sends an 'INVOKESS' message to the VLR. The VLR sends an 'INVOKESS ACK' message back to the MSC. The MSC then sends an 'explicitCT' message back to the MS.](a51105b2031bad93b818b82f071c6add_img.jpg) + +``` + +sequenceDiagram + participant MS + participant MSC + participant VLR + Note left of MS: MS + Note left of MSC: MSC + Note left of VLR: VLR + MS->>MSC: explicitCT + MSC->>VLR: INVOKESS + VLR-->>MSC: INVOKESS ACK + MSC-->>MS: explicitCT + +``` + +Figure 5.21: Signalling flow at invocation of Explicit Call Transfer supplementary service. The diagram shows three vertical dashed lines representing the MS, MSC, and VLR. The MS sends an 'explicitCT' message to the MSC. The MSC sends an 'INVOKESS' message to the VLR. The VLR sends an 'INVOKESS ACK' message back to the MSC. The MSC then sends an 'explicitCT' message back to the MS. + +**Figure 5.21: Signalling flow at invocation of Explicit Call Transfer supplementary service** + +If the A\_INVOKE\_SS signal from the MAP Service User in the MSC is empty, the ExplicitCT return result is returned to the MS in a DISCONNECT/RELEASE/RELEASE COMPLETE message. If it refers to an error, the mapping of errors takes place according to table 5.8. + +**Table 5.7: Mapping of 3GPP TS 29.002 operation errors to 3GPP TS 24.080 ExplicitCT errors** + +| 3GPP TS 29.002 operation error | 3GPP TS 24.080 ExplicitCT error | +|--------------------------------|---------------------------------| +| SystemFailure | SystemFailure | +| DataMissing | SystemFailure | +| UnexpectedDataValue | SystemFailure | +| CallBarred | CallBarred | +| IllegalSS-Operation | IllegalSS-Operation | +| SS-ErrorStatus | SS-ErrorStatus | +| SS-NotAvailable | SS-NotAvailable | + +## 5.3 SS Management in disconnecting phase + +When a CM connection is being released, the following supplementary services may apply: + +### 5.3.1 Call Forwarding services + +#### Notification of invocation of CFNRy to served mobile subscriber + +As described in 3GPP TS 22.082, when the Call Forwarding on No Reply service is invoked by the network, a notification of this fact may be sent to the MS as the call attempt is disconnected. The signalling for this situation is shown in figure 5.20. + +![Sequence diagram for CFNRy notification showing interactions between MS, MSC, and VLR.](4cc7cdce3d498d8b0ba033a9be24ade5_img.jpg) + +``` + +sequenceDiagram + participant MS + participant MSC + participant VLR + Note right of MSC: NRCT Timeout + MSC->>VLR: SEND INFORMATION FOR INCOMING CALL SETUP + VLR-->>MSC: COMPLETE CALL + MSC-->>MS: SETUP + Note left of MSC: ... + Note left of MSC: FACILITY/ +DISCONNECT +RELEASE/ +RELEASE COMPLETE + MSC-->>MS: FACILITY/ +DISCONNECT +RELEASE/ +RELEASE COMPLETE + +``` + +Sequence diagram for CFNRy notification showing interactions between MS, MSC, and VLR. + +**Figure 5.20: Signalling for notification of invocation of CFNRy supplementary service** + +The MSC obtains information on what supplementary services are active by analysing the SS-Data parameter in the MAP\_COMPLETE\_CALL service primitive on the B-interface. If this parameter indicates that CFNRy is active, then if required, either one of the DISCONNECT, RELEASE, RELEASE COMPLETE or FACILITY messages may be used to convey the required NotifySS operation in a Facility information element. Exact values of the parameter and parameter tags are indicated in 3GPP TS 24.080 and 3GPP TS 24.082. + +### 5.3.2 CCBS Request Activation + +As described in 3GPP TS 22.093, when subscriber A encounters a busy destination B, subscriber A can request the CCBS supplementary service (i.e. activate a CCBS request against destination B). + +The signalling for this situation is shown in figure 5.21. + +![Sequence diagram for CCBS Request Activation showing interactions between MS, MSC, VLR, and HLR.](35127fe87029df6f5f0b2ee85f6193f1_img.jpg) + +``` + +sequenceDiagram + participant MS + participant MSC + participant VLR + participant HLR + MS-->>MSC: DISCONNECT + MS->>MSC: RELEASE + MSC->>VLR: CCBS REQUEST + VLR->>HLR: REGISTER_CC_ENTRY + HLR-->>VLR: REGISTER_CC +ENTRY_ACK + HLR-->>VLR: REGISTER_CC +ENTRY_ERROR + VLR-->>MSC: CCBS REQUEST ERROR +CCBS REQUEST ACK + MSC-->>MS: RELEASE COMPLETE + +``` + +Sequence diagram for CCBS Request Activation showing interactions between MS, MSC, VLR, and HLR. + +**Figure 5.21: Signalling for CCBS Request Activation** + +The MS request the activation of CCBS in a Facility information element of a RELEASE message in response to a DISCONNECT message containing the diagnostic *CCBS is possible* and the Allowed Actions information element set to *Recall is possible*. Then, the MSC transmits the request in an Invoke component together with the call information towards the VLR in a CCBS\_REQUEST message on the B-interface. The VLR forwards it in a MAP\_REGISTER\_CC\_ENTRY on the D-interface. + +The outcome of the activation is sent back by the HLR in a MAP\_REGISTER\_CC\_ENTRY\_ACK or a MAP\_REGISTER\_CC\_ENTRY\_ERROR message. This outcome is subsequently mapped and inserted in the Facility information element of the RELEASE COMPLETE message from the MSC to the MS. + +Exact values of the parameters and parameter tags are indicated in 3GPP TS 24.008, 3GPP TS 24.080, 3GPP TS 24.093 and 3GPP TS 29.002. + +### 5.3.3 Call Deflection service + +#### 5.3.3.1 Call Deflection Operation Request + +As described in 3GPP TS 24.072, a MS may signal invocation of the Call Deflection supplementary service for a mobile terminated call at any time after call confirmation until the call is accepted. + +The signalling for this situation is shown in figure 5.22. + +![Sequence diagram for Figure 5.22: Signalling of a Call Deflection Request. The diagram shows three lifelines: MS, MSC, and VLR. The MS sends a DISCONNECT message to the MSC. The MSC then sends a COMPLETE CALL ERROR / PROCESS CALL WAITING ERROR message to the VLR.](04dc3838022e96d8d5548bb1b777b38c_img.jpg) + +``` + +sequenceDiagram + participant MS + participant MSC + participant VLR + Note left of MS: MS + MS->>MSC: DISCONNECT + Note right of MSC: MSC + MSC->>VLR: COMPLETE CALL ERROR / PROCESS CALL WAITING ERROR + Note right of VLR: VLR + +``` + +Sequence diagram for Figure 5.22: Signalling of a Call Deflection Request. The diagram shows three lifelines: MS, MSC, and VLR. The MS sends a DISCONNECT message to the MSC. The MSC then sends a COMPLETE CALL ERROR / PROCESS CALL WAITING ERROR message to the VLR. + +**Figure 5.22: Signalling of a Call Deflection Request** + +The MS requests Invocation of Call Deflection by including a CallDeflection operation (defined in 3GPP TS 24.080) in a DISCONNECT message. The parameters of the CallDeflection operation of the DISCONNECT message shall be transferred by the MSC to the VLR with the B-interface COMPLETE\_CALL\_ERROR or PROCESS\_CALL\_WAITING\_ERROR message. + +#### 5.3.3.2 Call Deflection Operation Response + +##### Optimal Routeing of late call forwarding is not invoked + +The signalling for this situation is shown in figure 5.23. + +![Sequence diagram for Figure 5.23: Mapping of Call Deflection Response without SOR. The diagram shows three lifelines: MS, MSC, and VLR. The MSC sends a COMPLETE CALL ERROR / PROCESS CALL WAITING ERROR message to the VLR. The VLR responds with a SEND INFORMATION FOR INCOMING CALL SETUP ACK / SEND INFORMATION FOR INCOMING CALL SETUP ERROR message to the MSC. The MSC then sends a RELEASE message to the MS.](f68a5f1f8845159744eff3e0e786731e_img.jpg) + +``` + +sequenceDiagram + participant MS + participant MSC + participant VLR + Note left of MS: MS + Note right of MSC: MSC + MSC->>VLR: COMPLETE CALL ERROR / PROCESS CALL WAITING ERROR + Note right of VLR: VLR + VLR->>MSC: SEND INFORMATION FOR INCOMING CALL SETUP ACK / +SEND INFORMATION FOR INCOMING CALL SETUP ERROR + Note right of MSC: MSC + MSC->>MS: RELEASE + Note left of MS: MS + +``` + +Sequence diagram for Figure 5.23: Mapping of Call Deflection Response without SOR. The diagram shows three lifelines: MS, MSC, and VLR. The MSC sends a COMPLETE CALL ERROR / PROCESS CALL WAITING ERROR message to the VLR. The VLR responds with a SEND INFORMATION FOR INCOMING CALL SETUP ACK / SEND INFORMATION FOR INCOMING CALL SETUP ERROR message to the MSC. The MSC then sends a RELEASE message to the MS. + +**Figure 5.23: Mapping of Call Deflection Response without SOR** + +The MSC shall send a CallDeflection return result to the MS if the SEND\_INFO\_FOR\_INCOMING\_CALL\_ACK message is received from the VLR and the invocation of Optimal Routeing is not requested. The MSC shall send a CallDeflection return error to the MS if a SEND\_INFORMATION\_FOR\_INCOMING\_CALL\_SETUP\_ERROR message is received from the VLR. The MSC shall obtain the value of the CallDeflection error from the error received in the SEND\_INFORMATION\_FOR\_INCOMING\_CALL\_SETUP\_ERROR message. + +##### Optimal Routeing of late call forwarding is invoked: + +The signalling for this situation is shown in figure 5.24. + +![Sequence diagram for Figure 5.24: Mapping of Call Deflection Response in case of SOR. The diagram shows four lifelines: MS, MSC, VLR, and GMSC. The sequence of messages is: 1. MSC sends 'SEND INFORMATION FOR INCOMING CALL SETUP ACK' to VLR. 2. MSC sends 'RESUME CALL HANDLING' to GMSC. 3. GMSC sends 'RESUME CALL HANDLING ACK / RESUME CALL HANDLING ERROR' back to MSC. 4. MSC sends 'RELEASE' to MS.](d9c0a780cd22626253dab4aa41699e2f_img.jpg) + +``` + +sequenceDiagram + participant MS + participant MSC + participant VLR + participant GMSC + MSC->>VLR: SEND INFORMATION FOR INCOMING CALL SETUP ACK + MSC->>GMSC: RESUME CALL HANDLING + GMSC-->>MSC: RESUME CALL HANDLING ACK / RESUME CALL HANDLING ERROR + MSC-->>MS: RELEASE + +``` + +Sequence diagram for Figure 5.24: Mapping of Call Deflection Response in case of SOR. The diagram shows four lifelines: MS, MSC, VLR, and GMSC. The sequence of messages is: 1. MSC sends 'SEND INFORMATION FOR INCOMING CALL SETUP ACK' to VLR. 2. MSC sends 'RESUME CALL HANDLING' to GMSC. 3. GMSC sends 'RESUME CALL HANDLING ACK / RESUME CALL HANDLING ERROR' back to MSC. 4. MSC sends 'RELEASE' to MS. + +**Figure 5.24: Mapping of Call Deflection Response in case of SOR** + +If for a Call Deflection Request Optimal Routeing of late call forwarding is invoked the MSC shall send a CallDeflection return result to the MS if the MAP\_RESUME\_CALL\_HANDLING\_ACK is received from the GMSC. If a MAP\_RESUME\_CALL\_HANDLING\_ERROR message with error "ForwardingFailed" is received from the GMSC the MSC shall send a CallDeflection return error "ForwardingFailed" to the MS. Reception of other errors than "ForwardingFailed" in the MAP\_RESUME\_CALL\_HANDLING\_ERROR message shall lead to local processing in the MSC. + +Exact values of the parameters and parameter tags are indicated in 3GPP TS 24.080 and 3GPP TS 29.002. + +# 6 Call independent supplementary services management + +## 6.1 MS initiated SS Management + +### 6.1.1 Connection establishment phase + +Call independent supplementary service management takes place on a separate, dedicated CM connection between the mobile station and the MSC. When a request to open such a connection arrives at the MSC, the MSC will request access permission from the VLR, as described in 3GPP TS 29.002. It will also assess the capabilities of the MS according to the screening indicator, as described in 3GPP TS 24.010 and 3GPP TS 24.080. The signalling for this situation is shown in figure 6.1. + +![Sequence diagram for Figure 6.1: Signalling flow for SS connection establishment. The diagram shows three lifelines: MS, MSC, and MAP User in MSC. The sequence of messages is: 1. MS sends 'CM service request (CM service type = SS Activation)' to MSC. 2. MSC sends 'A CM_SERV_REQ (CM service_type = SS Activation)' to MAP User in MSC.](bd57a547bec253d4179e5c4491c53dbb_img.jpg) + +``` + +sequenceDiagram + participant MS + participant MSC + participant MAP User in MSC + MS->>MSC: CM service request (CM service type = SS Activation) + MSC->>MAP User in MSC: A CM_SERV_REQ (CM service_type = SS Activation) + +``` + +Sequence diagram for Figure 6.1: Signalling flow for SS connection establishment. The diagram shows three lifelines: MS, MSC, and MAP User in MSC. The sequence of messages is: 1. MS sends 'CM service request (CM service type = SS Activation)' to MSC. 2. MSC sends 'A CM\_SERV\_REQ (CM service\_type = SS Activation)' to MAP User in MSC. + +**Figure 6.1: Signalling flow for SS connection establishment** + +### 6.1.2 Connection established + +At this stage of the connection, the version negotiation mechanism will be invoked as described in clause 3. The abstract definition of the protocol used for call independent SS operations is imported directly from 3GPP TS 29.002 into 3GPP TS 24.080. + +The signalling for invocation of a supplementary service operation is shown in figure 6.2, while figure 6.3 shows the signalling for returning the result of the supplementary service operation. Tables 6.1 and 6.2 show the mapping of 3GPP TS 24.080 operation codes to MAP service primitives, and vice versa respectively. The detailed mapping of the contents of the facility information elements to the service primitives triggering the MAP user are described in subclause 6.3. + +![Figure 6.2: Signalling flow for SS operation invocation. The diagram shows three entities: MS, MSC, and MAP User in MSC. The MS sends a REGISTER/FACILITY (SS OPERATION) message to the MSC. The MSC then sends an SS_SERVICE_PRIMITIVE REQ message to the MAP User in MSC.](4b87467ad9642943235f48f7d4b59449_img.jpg) + +``` + +sequenceDiagram + participant MS + participant MSC + participant MAP User in MSC + MS->>MSC: REGISTER/FACILITY (SS OPERATION) + MSC->>MAP User in MSC: SS_SERVICE_PRIMITIVE REQ + +``` + +Figure 6.2: Signalling flow for SS operation invocation. The diagram shows three entities: MS, MSC, and MAP User in MSC. The MS sends a REGISTER/FACILITY (SS OPERATION) message to the MSC. The MSC then sends an SS\_SERVICE\_PRIMITIVE REQ message to the MAP User in MSC. + +**Figure 6.2: Signalling flow for SS operation invocation** + +Choice of service primitive on the basis of received facility information element is as follows: + +**Table 6.1: Mapping of 3GPP TS 24.080 operations to 3GPP TS 29.002 service primitives** + +| Facility information element operation | Service primitive for MAP Service user | +|----------------------------------------|----------------------------------------| +| RegisterSS | A REGISTER SS | +| EraseSS | A ERASE SS | +| ActivateSS | A ACTIVATE SS | +| DeactivateSS | A DEACTIVATE SS | +| InterrogateSS | A INTERROGATE SS | +| RegisterPassword | A REGISTER PASSWORD | +| ProcessUnstructuredSS-Request | A PROCESS UNSTRUCTURED SS REQUEST | +| EraseCC-Entry | A ERASE CC ENTRY | + +![Figure 6.3: Signalling flow for SS operation return result. The diagram shows three entities: MS, MSC, and MAP User in MSC. The MSC sends a REGISTER/FACILITY (SS OPERATION) message to the MS. The MAP User in MSC sends an SS_SERVICE_PRIMITIVE CNF message to the MSC.](9167fa5ebcb66516d1bbb421ec9bba7b_img.jpg) + +``` + +sequenceDiagram + participant MS + participant MSC + participant MAP User in MSC + MSC->>MS: REGISTER/FACILITY (SS OPERATION) + MAP User in MSC->>MSC: SS_SERVICE_PRIMITIVE CNF + +``` + +Figure 6.3: Signalling flow for SS operation return result. The diagram shows three entities: MS, MSC, and MAP User in MSC. The MSC sends a REGISTER/FACILITY (SS OPERATION) message to the MS. The MAP User in MSC sends an SS\_SERVICE\_PRIMITIVE CNF message to the MSC. + +**Figure 6.3: Signalling flow for SS operation return result** + +Choice of facility information element on the basis of received service primitive is as follows: + +**Table 6.2: Mapping of 3GPP TS 29.002 service primitives to 3GPP TS 24.080 operations** + +| Service primitive for MAP Service user | Facility information element operation | +|----------------------------------------|----------------------------------------| +| A REGISTER SS | RegisterSS | +| A ERASE SS | EraseSS | +| A ACTIVATE SS | ActivateSS | +| A DEACTIVATE SS | DeactivateSS | +| A INTERROGATE SS | InterrogateSS | +| A REGISTER PASSWORD | RegisterPassword | +| A PROCESS UNSTRUCTURED SS REQUEST | ProcessUnstructuredSS-Request | +| A UNSTRUCTURED SS REQUEST | UnstructuredSS-Request | +| A UNSTRUCTURED SS NOTIFY | ProcessUnstructuredSS-Notify | +| A GET PASSWORD | GetPassword | +| A REGISTER CC ENTRY | AccessRegisterCCEntry | +| A ERASE CC ENTRY | EraseCCEntry | + +### 6.1.3 Connection release + +A supplementary service control connection is usually released by the network. The signalling for this situation is shown in figure 6.4. + +![Figure 6.4: Signalling flow for SS connection release by the network. The diagram shows three lifelines: MS, MSC, and MAP User in MSC. The MSC sends a RELEASE COMPLETE message to the MS. The MAP User in MSC sends an A_CM_REL_COMP message to the MSC.](26d664119ad25250780f554633444e54_img.jpg) + +``` + +sequenceDiagram + participant MS + participant MSC + participant MAP User in MSC + Note left of MS: + Note right of MAP User in MSC: + MSC->>MS: RELEASE COMPLETE + MAP User in MSC-->>MSC: A_CM_REL_COMP + +``` + +Figure 6.4: Signalling flow for SS connection release by the network. The diagram shows three lifelines: MS, MSC, and MAP User in MSC. The MSC sends a RELEASE COMPLETE message to the MS. The MAP User in MSC sends an A\_CM\_REL\_COMP message to the MSC. + +**Figure 6.4: Signalling flow for SS connection release by the network** + +However, in exceptional circumstances, the MS may request release of the connection. The signalling for this situation is shown in figure 6.5. + +![Figure 6.5: Signalling flow for SS connection release by the MS. The diagram shows three lifelines: MS, MSC, and MAP User in MSC. The MS sends a RELEASE COMPLETE message to the MSC. The MSC sends an A_CM_SERV_REL message to the MAP User in MSC.](2734e7f9be3e1dc046f14be2e6c9a085_img.jpg) + +``` + +sequenceDiagram + participant MS + participant MSC + participant MAP User in MSC + Note left of MS: + Note right of MAP User in MSC: + MS->>MSC: RELEASE COMPLETE + MSC-->>MAP User in MSC: A_CM_SERV_REL + +``` + +Figure 6.5: Signalling flow for SS connection release by the MS. The diagram shows three lifelines: MS, MSC, and MAP User in MSC. The MS sends a RELEASE COMPLETE message to the MSC. The MSC sends an A\_CM\_SERV\_REL message to the MAP User in MSC. + +**Figure 6.5: Signalling flow for SS connection release by the MS** + +## 6.2 Network initiated SS Management + +### 6.2.1 Connection establishment phase + +Call independent supplementary service management takes place on a separate, dedicated CM connection between the mobile station and the MSC. The MSC may need to open a connection towards the MS (as described in 3GPP TS 24.008) to send the Network initiated SS operation to the MS. Detailed mapping rules are described in subclause 6.3. + +### 6.2.2 Connection established + +The abstract definition of the protocol used for call independent SS operations is imported directly from 3GPP TS 29.002 into 3GPP TS 24.080. + +The signalling for invocation of a Network initiated SS operation is shown in figure 6.6, while figure 6.7 shows the signalling for returning the result of supplementary service operation. + +Choice of facility information element on the basis of received service primitive is described in table 6.2. + +![Figure 6.6: Signalling flow for Network Initiated SS operation invocation. The diagram shows three lifelines: MS, MSC, and MAP User in MSC. The MAP User in MSC sends an SS_SERVICE PRIMITIVE REQ message to the MSC. The MSC sends a REGISTER/FACILITY (SS OPERATION) message to the MS.](88a6d9692a52989caa6b208a1ba70dc0_img.jpg) + +``` + +sequenceDiagram + participant MS + participant MSC + participant MAP User in MSC + Note left of MS: + Note right of MAP User in MSC: + MAP User in MSC-->>MSC: SS_SERVICE PRIMITIVE REQ + MSC->>MS: REGISTER/FACILITY (SS OPERATION) + +``` + +Figure 6.6: Signalling flow for Network Initiated SS operation invocation. The diagram shows three lifelines: MS, MSC, and MAP User in MSC. The MAP User in MSC sends an SS\_SERVICE PRIMITIVE REQ message to the MSC. The MSC sends a REGISTER/FACILITY (SS OPERATION) message to the MS. + +**Figure 6.6: Signalling flow for Network Initiated SS operation invocation** + +Choice of service primitive on the basis of received facility information element is described in table 6.2. + +![Figure 6.7: Signalling flow for Network Initiated SS operation return result. The diagram shows three lifelines: MS, MSC, and MAP User in MSC. The MS sends a FACILITY (SS OPERATION) message to the MSC. The MSC sends an SS_SERVICE PRIMITIVE CNF message to the MAP User in MSC.](93c223896503daf410cb8b742e7a6fae_img.jpg) + +``` + +sequenceDiagram + participant MS + participant MSC + participant MAP User in MSC + Note left of MS: + Note right of MAP User in MSC: + MS->>MSC: FACILITY (SS OPERATION) + MSC-->>MAP User in MSC: SS_SERVICE PRIMITIVE CNF + +``` + +Figure 6.7: Signalling flow for Network Initiated SS operation return result. The diagram shows three lifelines: MS, MSC, and MAP User in MSC. The MS sends a FACILITY (SS OPERATION) message to the MSC. The MSC sends an SS\_SERVICE PRIMITIVE CNF message to the MAP User in MSC. + +**Figure 6.7: Signalling flow for Network Initiated SS operation return result** + +### 6.2.3 Connection release + +A Network initiated SS connection is usually released by the network. The signalling for this situation is shown in figure 6.4. + +However, in exceptional circumstances, the MS may request release of the connection. The signalling for this situation is shown in figure 6.5. + +### 6.2.4 ForwardCheckSSIndication + +When a mobile station first makes contact with the network after there has been a HLR restart, an indication may be sent by the HLR to the MS to inform of possible unintended consequences with respect to supplementary services. This indication is a separate service in the MAP (MAP\_FORWARD\_CHECK\_SS\_INDICATION service), and the abstract definition of its operation (ForwardCheckSSIndication) is imported into the 3GPP TS 24.080 protocol. + +Upon receipt of ForwardCheckSSIndication from the VLR, the MSC shall create a new call independent SS transaction and then send ForwardCheckSSIndication (see 3GPP TS 24.010). + +The MSC is only required to deliver ForwardCheckSSIndication if there is an active RR connection to the MS. The network shall not page the MS in order to deliver ForwardCheckSSIndication. + +![Sequence diagram for ForwardCheckSSIndication showing the flow of messages between MS, MSC, VLR, and HLR.](9b686adccf125267a013fa25721231a3_img.jpg) + +``` + +sequenceDiagram + participant MS + participant MSC + participant VLR + participant HLR + Note right of HLR: ForwardCheckSSInd. + HLR-->>VLR: ForwardCheckSSInd. + Note right of VLR: ForwardCheckSSInd. + VLR-->>MSC: ForwardCheckSSInd. + Note right of MSC: ForwardCheckSSInd. + MSC-->>MS: ForwardCheckSSInd. + +``` + +Sequence diagram for ForwardCheckSSIndication showing the flow of messages between MS, MSC, VLR, and HLR. + +Figure 6.8: ForwardCheckSSIndication + +### 6.2.5 CCBS Recall + +As described in 3GPP TS 22.093, when destination B, target of a CCBS request activated by subscriber A, becomes idle, the network shall automatically recall subscriber A. When subscriber A accepts the recall, the network will automatically generate a CCBS call to destination B. + +The signalling for this situation is shown in figure 6.9. + +![Sequence diagram for CCBS Recall showing the flow of messages between MS, MSC, VLR, and HLR.](1c140ee5d1a87186977da94a96bfa700_img.jpg) + +``` + +sequenceDiagram + participant MS + participant MSC + participant VLR + participant HLR + Note right of HLR: REMOTE_USER_FREE + HLR-->>VLR: REMOTE_USER_FREE + Note right of VLR: CCBS RUF + VLR-->>MSC: CCBS RUF + Note right of MSC: CM SERVICE PROMPT + MSC-->>MS: CM SERVICE PROMPT + Note right of MS: ... Procedure defined in 3GPP TS 24.093 ... + Note right of MS: SETUP + MS-->>MSC: SETUP + Note right of MSC: CCBS RUF ACK + MSC-->>VLR: CCBS RUF ACK + Note right of VLR: REMOTE_USER_FREE_ACK + VLR-->>HLR: REMOTE_USER_FREE_ACK + +``` + +Sequence diagram for CCBS Recall showing the flow of messages between MS, MSC, VLR, and HLR. + +Figure 6.9: Signalling for CCBS Recall + +The indication of destination B idle is sent in the MAP\_REMOTE\_USER\_FREE service primitive. It is transmitted on the D-interface and relayed on the B-interface. Then, the recall procedure starts with the establishment of a CC connection initiated by the network with the CM SERVICE PROMPT message. The following exchange of message concerns only the A-interface and is not described here since it is already done in 3GPP TS 24.093. + +The acceptance of the recall by the user is implicit in the SETUP message sent by the MS to the MSC. This message contains the call information previously sent to the MS and the indication that the call in its establishment phase is a CCBS call. The MSC informs the HLR of this acceptance by sending a MAP\_REMOTE\_USER\_FREE\_ACK message on the B-interface and further on the D-interface. + +In case an error occurs (e.g. *MS not reachable* or *Incompatible terminal*), at any time of the recall procedure (i.e. just after the error has been received), the MSC shall send the *MAP\_REMOTE\_USER\_FREE\_ERROR* with the appropriate value for the Error information element. + +Exact values of the parameters and parameter tags are indicated in 3GPP TS 24.008, 3GPP TS 24.093 and 3GPP TS 29.002. + +### 6.2.6 CCBS Monitoring + +The monitoring process is initiated by the network. It is started on the B-side as soon as subscriber B becomes a target of a CCBS request. It is started on the A-side when subscriber A is found to be busy or suspends a request while being offered a recall. Since the status of a subscriber is linked to its activity, a message sent by the MS to the MSC may lead to the transmission of a message containing the new status on the D-interface (i.e. the *MAP\_STATUS\_REPORT* service primitive). This message contains a Status information element which can take the value *Idle*, *Not Reachable* or *Not Idle*. + +Several situations might occur, they are described in the figure 6.10. + +![Sequence diagram showing signalling for CCBS Monitoring between MS, MSC, VLR, and HLR. The diagram illustrates four scenarios (a, b, c, d) where different messages from the MS lead to a STATUS REPORT from the VLR to the HLR via the MSC.](356eb99ab9489bbd647223390a913903_img.jpg) + +``` + +sequenceDiagram + participant MS + participant MSC + participant VLR + participant HLR + + Note left of MS: a. + MS->>MSC: CM SERVICE REQUEST + MSC->>VLR: MS ACTIVITY + VLR->>HLR: STATUS REPORT + + Note left of MS: b. + MS->>MSC: IMSI DETACH + MSC->>VLR: DETACH IMSI + VLR->>HLR: STATUS REPORT + + Note left of MS: c. + MS->>MSC: RELEASE + MSC->>VLR: CALL END + VLR->>HLR: STATUS REPORT + + Note left of MS: d. + MS->>MSC: SETUP + MSC->>VLR: NOT IDLE + VLR->>HLR: STATUS REPORT + +``` + +Sequence diagram showing signalling for CCBS Monitoring between MS, MSC, VLR, and HLR. The diagram illustrates four scenarios (a, b, c, d) where different messages from the MS lead to a STATUS REPORT from the VLR to the HLR via the MSC. + +**Figure 6.10: Signalling for CCBS Monitoring** + +For all these situations (from a to d), the transmission of the *MAP\_STATUS\_REPORT* service primitive depends on the possible change of status of the MS. The detailed behaviour of this procedure is described in 3GPP TS 23.093. + +Exact coding and values of the messages are indicated in 3GPP TS 24.008 and 3GPP TS 29.002. + +## 6.3 Mapping of Operation Codes, Error Codes, Parameter Tags and Parameter Contents + +### 6.3.1 Operation codes + +The same operation codes are used for equivalent operations in 3GPP TS 24.080 and 3GPP TS 29.002 for call independent supplementary service management. + +### 6.3.2 Error codes + +For call independent supplementary service management, the same error codes are used for equivalent error types in 3GPP TS 24.080 and 3GPP TS 29.002. + +The RETURN ERROR components are also constructed in the same way on both sides of the interface. + +### 6.3.3 Parameter tags and parameter values + +The same parameter tags and parameter values are used for equivalent parameters in 3GPP TS 24.080 and 3GPP TS 29.002. + +# --- Annex A (informative): Change history + +| Change history | | | | | | | +|----------------|-----------|---------|------|---------|-------------|--------------------------------| +| TSG CN# | Spec | Version | CR | | New Version | Subject/Comment | +| Apr 1999 | GSM 09.11 | 7.0.0 | | | | Transferred to 3GPP CN1 | +| CN#03 | 29.011 | | | R99 | 3.0.0 | Approved at CN#03 | +| CN#11 | 29.011 | 3.0.0 | | Rel-4 | 4.0.0 | Approved at CN#11 | +| CN#16 | 29.011 | 4.0.0 | | Rel-4 | 4.0.1 | References updated | +| CN#16 | 29.011 | 4.0.1 | | Rel-5 | 5.0.0 | Rel-5 created after CN#16 | +| CN#26 | 29.011 | 5.0.0 | | Rel-6 | 6.0.0 | Rel-6 created after CN#26 | +| CT#36 | 29.011 | 6.0.0 | | Rel-7 | 7.0.0 | Upgraded unchanged from Rel-6 | +| CT#42 | 29.011 | 7.0.0 | | Rel-8 | 8.0.0 | Upgraded unchanged from Rel-7 | +| 2009-12 | 29.011 | 8.0.0 | - | Rel-9 | 9.0.0 | Update to Rel-9 version (MCC) | +| 2011-03 | 29.011 | 9.0.0 | - | Rel-10 | 10.0.0 | Update to Rel-10 version (MCC) | +| 2011-12 | 29.011 | 10.0.0 | 0001 | Rel-11 | 11.0.0 | Cause code mapping | \ No newline at end of file diff --git a/marked/Rel-11/29_series/29013/08441fa90c5fd11994626f662ac13f19_img.jpg b/marked/Rel-11/29_series/29013/08441fa90c5fd11994626f662ac13f19_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e5068d93ab0e92150c9456705d96716c444b5b23 --- /dev/null +++ b/marked/Rel-11/29_series/29013/08441fa90c5fd11994626f662ac13f19_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2ece6a7a7b4f2643427b45ed0461a3f51bff85bfcf784cc71312c977fb2435b0 +size 26092 diff --git a/marked/Rel-11/29_series/29013/16152cf1d84aea10848758f51a91ff6a_img.jpg b/marked/Rel-11/29_series/29013/16152cf1d84aea10848758f51a91ff6a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..603d4dec4de6ee15ce1edfe0e104fec7779f7158 --- /dev/null +++ b/marked/Rel-11/29_series/29013/16152cf1d84aea10848758f51a91ff6a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6c55147c0341f0fdbc71a4a6c837ee8248a326c34288a765e2c690f99a9ad315 +size 26415 diff --git a/marked/Rel-11/29_series/29013/16c1175b5f05a4b55e6d396fc51b15b3_img.jpg b/marked/Rel-11/29_series/29013/16c1175b5f05a4b55e6d396fc51b15b3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8fa110749bf1299a59d4d0af1ac9011f4fb3a2c7 --- /dev/null +++ b/marked/Rel-11/29_series/29013/16c1175b5f05a4b55e6d396fc51b15b3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ae5fbbe72aa8f28bdfcdf6889c8c07c7390e783d0cfa6004bcd6a029e9c6e7c1 +size 29941 diff --git a/marked/Rel-11/29_series/29013/3ad00ce93ad9dea9ee0f47535e5355e6_img.jpg b/marked/Rel-11/29_series/29013/3ad00ce93ad9dea9ee0f47535e5355e6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..658f4d79c95f49bf44405be6e11ad8a574a425c8 --- /dev/null +++ b/marked/Rel-11/29_series/29013/3ad00ce93ad9dea9ee0f47535e5355e6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c99a24715bd3e8143dce8be9d3c035d9e62d1c35cc47bba0457e862289fb8f5f +size 27444 diff --git a/marked/Rel-11/29_series/29013/5dfc130b129ace4df375839020a5700d_img.jpg b/marked/Rel-11/29_series/29013/5dfc130b129ace4df375839020a5700d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6638c8f61077a323224c2218b48ab8fd535dc9e6 --- /dev/null +++ b/marked/Rel-11/29_series/29013/5dfc130b129ace4df375839020a5700d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:73861ee4fa270f71d54a9fc777ac262b546900a7bca516eee99a2a608e0ebd6d +size 31429 diff --git a/marked/Rel-11/29_series/29013/6f341f415ee0f8c724e5d6daeb1e9b4a_img.jpg b/marked/Rel-11/29_series/29013/6f341f415ee0f8c724e5d6daeb1e9b4a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fdd3853c8b7e5e5d9893b629177bbbf155f77f6d --- /dev/null +++ b/marked/Rel-11/29_series/29013/6f341f415ee0f8c724e5d6daeb1e9b4a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d5c4906782340231a3bd67a3e1f452cd1c4878e8bb006eb8e91f6398d49a897d +size 26873 diff --git a/marked/Rel-11/29_series/29013/70de8885bd7de15723aaad5eb5c5febf_img.jpg b/marked/Rel-11/29_series/29013/70de8885bd7de15723aaad5eb5c5febf_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d5eebd4fffe59a6f2d64bce1f1b6ae766d04a2ab --- /dev/null +++ b/marked/Rel-11/29_series/29013/70de8885bd7de15723aaad5eb5c5febf_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2a004660c560a2630736533823b46aeff9981771f64a02727cda79a65f49c828 +size 31684 diff --git a/marked/Rel-11/29_series/29013/75f0cb39f1cd165dfe4a6aa6c4d9388d_img.jpg b/marked/Rel-11/29_series/29013/75f0cb39f1cd165dfe4a6aa6c4d9388d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..98a7e1b8557f7720757f59f5731d583ff235f801 --- /dev/null +++ b/marked/Rel-11/29_series/29013/75f0cb39f1cd165dfe4a6aa6c4d9388d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9829eb38c4533e675941904990a42adaa602210e38f4ac9ba26d0355ce374fda +size 27561 diff --git a/marked/Rel-11/29_series/29013/7e670a2b556b53ea9002dfff3a420e08_img.jpg b/marked/Rel-11/29_series/29013/7e670a2b556b53ea9002dfff3a420e08_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cadcf87f5d54350bf774d0fb149d0e4e44af815e --- /dev/null +++ b/marked/Rel-11/29_series/29013/7e670a2b556b53ea9002dfff3a420e08_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6a24491827488407772a618850519c97606f9e73cd54a495ee706e4bda6cea84 +size 24661 diff --git a/marked/Rel-11/29_series/29013/997233d405f0d4b89ddeb7683e047f66_img.jpg b/marked/Rel-11/29_series/29013/997233d405f0d4b89ddeb7683e047f66_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4260c3fafe7faeea977f74499770ed5e2cc634ce --- /dev/null +++ b/marked/Rel-11/29_series/29013/997233d405f0d4b89ddeb7683e047f66_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:088fa4c58774f00415a5bb61f390b550a2493943c2523553ec6fe46829cc4e9b +size 62680 diff --git a/marked/Rel-11/29_series/29013/a234352dfaccdc24745c88eef7724cc6_img.jpg b/marked/Rel-11/29_series/29013/a234352dfaccdc24745c88eef7724cc6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..62d21a58416fac9448507dbc69e2d6e4fbec8974 --- /dev/null +++ b/marked/Rel-11/29_series/29013/a234352dfaccdc24745c88eef7724cc6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8d0343f554b3c7457e7b612c13ba714aedc8310af358dbfe23350a59f65641d4 +size 24785 diff --git a/marked/Rel-11/29_series/29013/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg b/marked/Rel-11/29_series/29013/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..588788e8e61be10f4395990b8cf5fde7d0b9f6ca --- /dev/null +++ b/marked/Rel-11/29_series/29013/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fe188d3a7a8796b0c9ed02a73eaa45d2d1d0e05495c11d7b906641a1d45351d6 +size 20213 diff --git a/marked/Rel-11/29_series/29013/b3c108e7145f2017957569d06ea359cb_img.jpg b/marked/Rel-11/29_series/29013/b3c108e7145f2017957569d06ea359cb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4dfe7cf3847d523aebc38b85dda1db3e37592a02 --- /dev/null +++ b/marked/Rel-11/29_series/29013/b3c108e7145f2017957569d06ea359cb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:015f760b5d4575708d3dfbdb7c9254ad7ca6cca13c54e4a8f89dcfb5dae592e7 +size 26617 diff --git a/marked/Rel-11/29_series/29013/d17f75945bbb3feb84a153ecfedb9b81_img.jpg b/marked/Rel-11/29_series/29013/d17f75945bbb3feb84a153ecfedb9b81_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bafc1faa430a0aadff0eebccb03a02fd46019d3b --- /dev/null +++ b/marked/Rel-11/29_series/29013/d17f75945bbb3feb84a153ecfedb9b81_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0425bace708c7af313ef2b0db90e10521e0f455e49522ad22f091efcb7c8fe3d +size 28360 diff --git a/marked/Rel-11/29_series/29013/df82d77a0d2637cbf2da9ea920a554fa_img.jpg b/marked/Rel-11/29_series/29013/df82d77a0d2637cbf2da9ea920a554fa_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4cc07318661790527e0e489b2e63f0dac232827c --- /dev/null +++ b/marked/Rel-11/29_series/29013/df82d77a0d2637cbf2da9ea920a554fa_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:542e4f306f177798aa61182a7f5c19623a6244ffa378d09c0486ccde22a31725 +size 29243 diff --git a/marked/Rel-11/29_series/29013/ea37ab05b033e59cfdf7b074161aaf5a_img.jpg b/marked/Rel-11/29_series/29013/ea37ab05b033e59cfdf7b074161aaf5a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4d75124e9a58836fe37c8b0aa6c7eb191da12a14 --- /dev/null +++ b/marked/Rel-11/29_series/29013/ea37ab05b033e59cfdf7b074161aaf5a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1724262709aa237d2c9fc4e5051f5fc4bc5a4dbbc2a6d6cb8df8b0b62611f94d +size 7981 diff --git a/marked/Rel-11/29_series/29013/raw.md b/marked/Rel-11/29_series/29013/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..ce0c028ac5fc7e3092a2d6e3a5c1276ab0828d29 --- /dev/null +++ b/marked/Rel-11/29_series/29013/raw.md @@ -0,0 +1,698 @@ + + + + + + +# Contents + +| | | +|---------------------------------------------------------------------------|----| +| Foreword ..... | 4 | +| 1 Scope..... | 4 | +| 2 References..... | 5 | +| 3 Definitions and abbreviations ..... | 5 | +| 3.1 Definitions..... | 5 | +| 3.2 Abbreviations ..... | 5 | +| 4 General..... | 6 | +| 4.1 GSM CCBS Architecture Overview ..... | 6 | +| 4.2 GSM CCBS - ISDN CCBS ASE Interworking Overview ..... | 7 | +| 4.3 Overview on the use of CCBS procedures and parameters values ..... | 8 | +| 4.4 Mapping between MAP and SSAP application layer messages ..... | 8 | +| 4.4.1 MAP D-interface to SSAP interface mapping in HLR A..... | 8 | +| 4.4.2 SSAP interface to MAP D-interface interface mapping in HLR A..... | 8 | +| 5 Mapping between MAP message parameters and SSAP message parameters..... | 9 | +| 5.1 CCBS Request Invocation..... | 9 | +| 5.1.1 Encoding of called party subaddress information ..... | 11 | +| 5.2 CCBS Request Result..... | 11 | +| 5.3 CCBS Request Error ..... | 12 | +| 6 Dialogue handling on the SSAP interface..... | 13 | +| 6.1 Dialogue Beginning..... | 13 | +| 6.1.1 CCBS Request Invocation..... | 13 | +| 6.2 Dialogue Continuation ..... | 13 | +| 6.2.1 CCBS Request Result..... | 13 | +| 6.2.2 CCBS Remote User Free Invocation..... | 14 | +| 6.2.3 CCBS Suspend Invocation ..... | 14 | +| 6.2.4 CCBS Resume Invocation..... | 15 | +| 6.3 Dialogue End..... | 15 | +| 6.3.1 Normal dialogue end ..... | 15 | +| 6.3.2 CCBS Cancel Invocation (from A-side)..... | 16 | +| 6.3.3 CCBS Cancel Invocation (from B-side)..... | 16 | +| 6.3.4 CCBS Request Error..... | 17 | +| 7 Addressing of SCCP layer messages on the SSAP interface..... | 17 | +| 7.1 Use of SCCP..... | 17 | +| 7.2 Addressing of messages at the originating PLMN..... | 17 | +| 7.2.1 TC-BEGIN message from the originating network HLR..... | 17 | +| 7.2.2 TC-CONTINUE, TC-END messages from the originating network HLR ..... | 18 | +| 7.3 Addressing of messages at the destination PLMN..... | 18 | +| 7.3.1 TC-CONTINUE, TC-END messages from the destination network HLR ..... | 18 | +| 7.4 Number formats of the SCCP address parameters..... | 19 | +| 7.4.1 Originating PLMN..... | 19 | +| 7.4.2 Destination PLMN..... | 19 | +| Annex A (informative): Change history..... | 20 | + +# --- Foreword + +This Technical Specification has been produced by the 3GPP. + +This TS provides a detailed specification for interworking between the ISDN Supplementary Services ASE protocol and the Mobile Application Part (MAP) D interface protocol for handling of supplementary services within the 3GPP system. + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of this TS, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version 3.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 Indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the specification; + +# --- 1 Scope + +The scope of the present document is to provide a specification for interworking between the ISDN Application Service Element (ASE) protocol for supplementary services and the Mobile Application Part (MAP) protocol on MAP D-interface protocol for handling of supplementary services within the digital cellular telecommunications system (Phase 2+). This version of the specification includes the interworking for the Call Completion to Busy Subscriber (CCBS) service between the ISDN CCBS-ASE and MAP. + +The MAP protocol for CCBS service is specified in GSM 09.02. The ISDN CCBS-ASE protocol is specified in ETS 300 356-18. The ISDN CCBS-ASE protocol is also commonly referred to as the SSAP protocol in GSM 03.93. This specification clarifies the interworking within the HLR between these protocols for the Call Completion to Busy Subscriber (CCBS) service. + +Clause 4 describes the mapping between MAP application layer messages and SSAP application layer messages. + +Clause 5 describes the mapping between MAP message parameters and SSAP message parameters. + +Clause 6 describes the dialogue handling on the SSAP interface. + +Clause 7 describes the SCCP layer addressing for messages on the SSAP interface. + +# --- 2 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. +- For a specific reference, subsequent revisions do not apply. +- For a non-specific reference, the latest version applies. + +- [1] GSM 01.04: "Digital cellular telecommunications system (Phase 2+); Abbreviations and acronyms". +- [2] GSM 02.93: "Digital cellular telecommunications system (Phase 2+); Completion of calls to busy subscriber (CCBS) supplementary services - Stage 1". +- [3] GSM 03.93: "Digital cellular telecommunications system (Phase 2+); Technical Realisation of Completion of Calls to Busy Subscriber (CCBS); Stage 2". +- [4] GSM 04.80: "Digital cellular telecommunications system (Phase 2+); Mobile radio interface layer 3 supplementary services specification Formats and coding". +- [5] GSM 04.93: "Digital cellular telecommunications system (Phase 2+); Technical Realisation of Completion of Calls to Busy Subscriber (CCBS); Stage 3". +- [6] GSM 09.02 "Digital cellular telecommunications system (Phase 2+); Mobile Application Part (MAP) specification". +- [7] GSM 09.07 : "Digital cellular telecommunications system (Phase 2+); General requirements on interworking between the Public Land Mobile Network (PLMN) and the Integrated Services Digital Network (ISDN) or Public Switched Telephone Network (PSTN)". +- [8] ETS 300 102-1 (1990): "Integrated Services Digital Network (ISDN); User-network interface layer 3 specifications for basic call control". +- [9] ETS 300 356-18: "ISDN User Part (ISUP) version 2 for the international interface: Part 18: Completion of Calls to Busy Subscriber (CCBS) supplementary service". +- [10] ETS 300 358: "Integrated Services Digital Network (ISDN); Completion of Calls to Busy Subscriber (CCBS) supplementary service; Functional capabilities and information flows". + +# --- 3 Definitions and abbreviations + +## 3.1 Definitions + +For the purposes of this specification, the following definitions apply: + +**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). The terms CCBS-ASE defined in ETS 300 356-18 for the ISDN CCBS service and SSAP defined in GSM 03.93 are the same and are used interchangeably in this specification. The SSAP interface is between the originating network entities (HLR A, OLE) and the destination network entities (HLR B, DLE). + +## 3.2 Abbreviations + +Abbreviations used in this specification are listed in GSM 01.04. + +For the purposes of this specification, the following abbreviations apply: + +| | | +|------|----------------------------------------| +| ASE | Application Service Element | +| CCBS | Call Completion to Busy Subscriber | +| DLE | Destination Local Exchange | +| ISDN | Integrated Services Digital Network | +| MAP | Mobile Application Part | +| OLE | Originating Local Exchange | +| SCCP | Signalling Connection Control Part | +| SSAP | Supplementary Service Application Part | +| TC | Transaction Capabilities | + +# --- 4 General + +## 4.1 GSM CCBS Architecture Overview + +The stage 1 of the CCBS service is defined in GSM 02.93. + +The network architecture to support the CCBS service in GSM networks is defined in GSM 03.93. For convenience, the architecture is shown again in this specification. Figure 4.1.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 (see ETS 300 356-18) 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 (see ETS 300 356-18) are performed via the SSAP protocol, which is signalled on the following interfaces: + +HLR A - HLR B; + +HLR A - DLE; + +OLE - HLR B. + +This specification only describes the MAP - SSAP protocol interworking. + +![Architectural overview diagram showing the interworking between an Originating Network and a Destination Network via a central Transit Network(s).](997233d405f0d4b89ddeb7683e047f66_img.jpg) + +The diagram illustrates the architectural overview of interworking between an Originating Network and a Destination Network through a central Transit Network(s). The diagram is divided into two main sections: Originating Network (left) and Destination Network (right), both connected to a central cloud labeled 'TRANSIT NETWORK(S)'. + +- Originating Network (Left):** + - A 'Fixed Network' block contains an 'OLE' (Office Line Equipment) connected to the Transit Network via 'ISUP' and 'SSAP' protocols. + - A 'Mobile Network' block contains 'HLR A' (Home Location Register), 'VLR A' (Visitor Location Register), and 'VMSC A' (Visited Mobile Switching Center). 'HLR A' is connected to the Transit Network via 'SSAP'. 'VLR A' is connected to 'HLR A' and 'VMSC A'. 'VMSC A' is connected to the Transit Network via 'ISUP'. +- Destination Network (Right):** + - A 'Fixed Network' block contains a 'DLE' (Data Link Equipment) connected to the Transit Network via 'ISUP' and 'SSAP' protocols. + - A 'Mobile Network' block contains 'HLR B' (Home Location Register), 'VLR B' (Visitor Location Register), and 'VMSC B' (Visited Mobile Switching Center). 'HLR B' is connected to the Transit Network via 'SSAP'. 'VLR B' is connected to 'HLR B' and 'VMSC B'. 'VMSC B' is connected to the Transit Network via 'ISUP'. + - There is also a 'GMSC B' (Gateway Mobile Switching Center) connected to the Transit Network via 'ISUP'. 'GMSC B' is connected to 'VLR B' via a 'MAP' (Mobile Application Part) protocol. + +Architectural overview diagram showing the interworking between an Originating Network and a Destination Network via a central Transit Network(s). + +Figure 4.1: Architectural overview showing common point of interworking + +## 4.2 GSM CCBS - ISDN CCBS ASE Interworking Overview + +The non-call related signalling procedures for CCBS between the originating network and the destination network are defined in ETS 300 356-18 as the ISDN CCBS-ASE. The GSM network also uses these signalling procedures for CCBS without any changes. The ISDN CCBS ASE protocol is supported in GSM networks in the HLR A (originating network) and HLR B (destination network). Therefore no protocol interworking for ISDN CCBS-ASE is needed for the CCBS service between GSM networks and ISDN networks. + +In GSM networks, the CCBS functionality is distributed across several network entities (see GSM 03.93) including the HLR, VLR, MSC and the MS. The HLR shall provide any necessary signalling interworking between the MAP protocol for call completion services on the MAP D-interface (between the VLR and the HLR) and ISDN CCBS-ASE protocol between the originating and destination networks. + +The MAP protocol for CCBS service is specified in GSM 09.02. The ISDN CCBS-ASE protocol is specified in ETS 300 356-18. This specification clarifies the interworking within the HLR between these protocols. + +## 4.3 Overview on the use of CCBS procedures and parameters values + +A GSM subscriber can roam while there is an active CCBS request. The called party address (MSISDN) information is used to initiate a dialogue with the destination network on the SSAP interface. The dialogue on the SSAP interface is opened and maintained while there is an active CCBS request (see ETS 300 356-18). However, the dialogues on the MAP D interface can be closed and reopened as necessary (see GSM 09.02 and GSM 03.93) and use the IMSI information for addressing. + +## 4.4 Mapping between MAP and SSAP application layer messages + +The mapping of MAP messages on the D interface and SSAP messages between the originating and destination networks is described. The precise coding of these messages is given in GSM 09.02 and ETS 300 356-18. + +### 4.4.1 MAP D-interface to SSAP interface mapping in HLR A + +**Table 4.1: Mapping of GSM 09.02 (MAP) operations to ETS 300 356-18 (SSAP) operations** + +| MAP OPERATIONS | SSAP OPERATIONS | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------| +| RegisterCCEntry | CcbsRequest | +| EraseCCEntry/ A GSM 03.93 Event (note 1) | CcbsCancel | +| RemoteUserFree Result/
RemoteUserFree Error/
A GSM 03.93 Event (note 2) | CcbsSuspend | +| StatusReport/
A GSM 03.93 Event (note 3) | CcbsResume | +| NOTE 1 This event may be local to HLR A. See GSM 03.93 for a dynamic description of possible events in HLR A leading to a CCBS request being cancelled. The SSAP CcbsCancel operation can include a cause code parameter; this shall be set to the appropriate value corresponding to the actual dynamic event by HLR A (e.g. cCBS-T3-Timeout, cCBS-T4-Timeout). | | +| NOTE 2 This event may be local to HLR A. See GSM 03.93 for a dynamic description of possible events in HLR A leading to a CCBS request being suspended. | | +| NOTE 3 This event may be local to HLR A. See GSM 03.93 for a dynamic description of possible events in HLR A leading to a CCBS request being resumed. | | + +### 4.4.2 SSAP interface to MAP D-interface interface mapping in HLR A + +| SSAP OPERATIONS | MAP OPERATIONS | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------| +| CcbsRequest Result | RegisterCCEntry Result | +| CcbsRequest Error | RegisterCCEntry Error | +| RemoteUserFree | RemoteUserFree | +| CcbsCancel | SetReportingState/A GSM 03.93 Event (note 1) | +| NOTE 1 This event may be local to HLR A. See GSM 03.93 for a dynamic description of possible events in HLR A resulting from a CCBS request being cancelled. The SSAP CcbsCancel operation can include a cause code parameter(e.g. cCBS-T7-Timeout, cCBS-T9-Timeout). | | + +# 5 Mapping between MAP message parameters and SSAP message parameters + +The mapping between MAP message parameters and SSAP message parameters is described. The precise coding of these messages is given in GSM 09.02 and ETS 300 356-18. + +The following messages on the SSAP interface do not contain any parameters: + +- RemoteUserFree; +- Suspend; +- Resume. + +## 5.1 CCBS Request Invocation + +![Sequence diagram showing the signalling flow for CCBS Request Invocation between VLRA, HLRA, and DESTINATION NETWORK B.](a234352dfaccdc24745c88eef7724cc6_img.jpg) + +The diagram illustrates the signalling flow for CCBS Request Invocation across three entities: VLRA, HLRA, and DESTINATION NETWORK B. Each entity is represented by a vertical dashed line with a '+' at the top. The sequence of messages is as follows: 1. A dashed arrow points from VLRA to HLRA, labeled 'RegisterCCEntry' and 'TC-BEGIN'. 2. A dashed arrow points from HLRA to DESTINATION NETWORK B, labeled 'CcbsRequest' and 'TC-BEGIN'. + +Sequence diagram showing the signalling flow for CCBS Request Invocation between VLRA, HLRA, and DESTINATION NETWORK B. + +Figure 5.1: Signalling flow for CCBS Request Invocation + +**Table 5.1: Mapping of CCBS Request Invocation parameters** + +| RegisterCCEntry PARAMETERS | CcbsRequest PARAMETERS | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------| +| ss-Code | not present | +| ccbs-Feature | | +| - b-subscriberSubaddress (note 1) | accessTransportParameter (note 2) | +| translatedB-Number | calledPartyNumber (note 3) | +| serviceIndicator | not present | +| callInfo | not present | +| networkSignallInfo
- ISDN BC Tag, Length, Content (note 4) | userServiceInf | +| networkSignallInfo
- HLC Tag, Length, Content (note 5) | accessTransportParameter (note 2) | +| networkSignallInfo
- LLC Tag, Length, Content (note 6) | accessTransportParameter (note 2) | +| not present | retainSupported (note 7) | +| not present | callingPartyNumber (note 8) | +| not present | userServiceInfPrime (note 9) | +| NOTE 1 CCBS-Feature contains the b-subscriberSubaddress parameter which is the called party subaddress. The GSM HLR A shall map the called party subaddress into the accessTransportParameter if received from the VLR. The entire called party subaddress information (i.e. called party subaddress IEI, LENGTH and CONTENT ) is mapped into the accessTransportParameter. See subclause 5.1.1. for details of the required encoding. | | +| NOTE 2 The CcbsRequest contains only one accessTransportParameter. This parameter contains information on the ISDN HLC, LLC and Subaddress. | | +| NOTE 3 The calledParty Number shall be in the international E.164 format. | | +| NOTE 4 The networkSignallInfo contains three information elements ISDN BC, HLC, LLC. The structure of this is defined in GSM 09.02 and the content in GSM 09.07. The ISDN BC information element CONTENT (i.e. without ISDN BC TAG, LENGTH ) is mapped into the userServiceInf parameter. | | +| NOTE 5 The networkSignallInfo contains three information elements ISDN BC, HLC, LLC. The structure of this is defined in GSM 09.02 and the content in GSM 09.07. The entire ISDN HLC information element (i.e. ISDN HLC TAG, LENGTH and CONTENT ) is mapped into the accessTransportParameter. | | +| NOTE 6 The networkSignallInfo contains three information elements ISDN BC, HLC, LLC. The structure of this is defined in GSM 09.02 and the content in GSM 09.07. The entire ISDN LLC information element (i.e. ISDN LLC TAG, LENGTH and CONTENT ) is mapped into the accessTransportParameter. | | +| NOTE 7 This information is local to the HLR A. This information element shall be coded by HLR A to reflect whether it supports CCBS Retention capability. | | +| NOTE 8 This information is local to HLR A. The HLR A provides callingPartyNumber if CLIR was not invoked (See the serviceIndicator parameter in GSM 09.02 and GSM 03.93). If sent, the A subscriber's identity shall be the Basic MSISDN (i.e. the main MSISDN) and shall be in the international E.164 format. | | +| NOTE 9 The GSM HLR A shall not send the userServiceInfPrime | | + +### 5.1.1 Encoding of called party subaddress information + +The CCBS-Feature parameter is received from the VLR and it may include the b-subscriberSubaddress parameter as defined in GSM 09.02. The Called Party Subaddress information requires additional processing in HLR to ensure correct encoding of this information on the SSAP interface. The HLR shall add two octets to the ISDN-SubaddressString received from the VLR as indicated in figure 5.2. + +![](7e670a2b556b53ea9002dfff3a420e08_img.jpg) + +| | +|--------------------------------------------------------------------------| +| Called Party Subaddress IEI
(See ETS 300 102-1)
0111 0001 (note 1) | +| Length of the called party address
contents (note 2) | +| ISDN-SubaddressString
(See GSM 09.02)

(note 3) | + +NOTE 1 Called Party Subaddress Information Element Identifier (IEI) is defined by ETS 300 102-1. Its value is "01110001". This information is not sent from the VLR and has to be derived locally in the HLR for interworking purposes. + +NOTE 2 This information has to be derived locally in the HLR for interworking purposes. + +NOTE 3 This information is sent by the VLR. The ISDN-SubaddressString contents is defined in GSM 09.02. + +**Figure 5.2: Encoding of Called Party Subaddress information** + +## 5.2 CCBS Request Result + +![Signalling flow diagram for CCBS Request Result showing interactions between VLRA, HLRA, and DESTINATION NETWORK B.](b3c108e7145f2017957569d06ea359cb_img.jpg) + +``` + +sequenceDiagram + participant VLRA + participant HLRA + participant DN as DESTINATION NETWORK B + DN-->>HLRA: CcbsRequest-Result + Note over DN,HLRA: TC-CONTINUE + HLRA-->>VLRA: RegisterCCEntry-Result + Note over HLRA,VLRA: TC-END + +``` + +Signalling flow diagram for CCBS Request Result showing interactions between VLRA, HLRA, and DESTINATION NETWORK B. + +**Figure 5.3: Signalling flow for CCBS Request Result** + +**Table 5.2: Mapping of CCBS Request Result parameters** + +| CcbsRequest_ Result PARAMETERS | RegisterCCEntry_ Result PARAMETERS | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------| +| retainSupported (note 1) | not present | +| not present | ccbs-Feature (note 2) | +| NOTE 1 This information is associated with each CCBS Request and indicates whether CCBS Retention is supported by the destination B network (see GSM 03.93). | | +| NOTE 2 This information is local to the HLR A. Some of information contained in ccbs-Feature (e.g. ccbs-index) is allocated by the HLR A. The ccbs-Feature information is sent to the MS (see GSM 03.93, GSM 04.93). | | + +## 5.3 CCBS Request Error + +![Signalling flow diagram for CCBS Request Error. It shows three vertical lifelines: VLRA, HLRA, and DESTINATION NETWORK B. The sequence starts with a request from VLRA to HLRA. An error message 'CcbsRequest-Error' is sent from DESTINATION NETWORK B to HLRA. HLRA then sends a 'RegisterCCEntry-Error' message back to VLRA. Both error messages are followed by a 'TC-END' indicator.](08441fa90c5fd11994626f662ac13f19_img.jpg) + +``` + +sequenceDiagram + participant VLRA + participant HLRA + participant DESTINATION_NETWORK_B as DESTINATION NETWORK B + Note left of VLRA: +--+\n | |\n | |\n Note right of DESTINATION_NETWORK_B: +--+\n | |\n | |\n DESTINATION_NETWORK_B->>HLRA: CcbsRequest-Error + Note right of HLRA: TC-END + HLRA->>VLRA: RegisterCCEntry-Error + Note right of VLRA: TC-END + +``` + +Signalling flow diagram for CCBS Request Error. It shows three vertical lifelines: VLRA, HLRA, and DESTINATION NETWORK B. The sequence starts with a request from VLRA to HLRA. An error message 'CcbsRequest-Error' is sent from DESTINATION NETWORK B to HLRA. HLRA then sends a 'RegisterCCEntry-Error' message back to VLRA. Both error messages are followed by a 'TC-END' indicator. + +**Figure 5.4: Signalling flow for CCBS Request Error****Table 5.3: Mapping of CCBS Request Error parameters** + +| CcbsRequest_ Error PARAMETERS | RegisterCCEntry_ Error PARAMETERS | +|----------------------------------------------------------------------------------------------------------------------|------------------------------------------| +| shortTermDenial/ longTermDenial (note 1) | shortTermDenial/ longTermDenial (note 2) | +| NOTE 1 For coding of these User Errors see ETS 300 356-18. | | +| NOTE 2 For coding of these User Errors see GSM 09.02. This information is sent to the MS (see GSM 04.93, GSM 04.80). | | + +# 6 Dialogue handling on the SSAP interface + +The dialogue handling on the SSAP interface and the mapping between the corresponding TC transaction sublayer messages on the MAP D and SSAP interfaces is described. The diagrams show the general principle of dialogue handling. Specific message flows depend on the dynamics of the application in the network elements, see GSM 03.93 and GSM 09.02. + +## 6.1 Dialogue Beginning + +### 6.1.1 CCBS Request Invocation + +![Sequence diagram showing the signalling flow for CCBS REQUEST INVOCATION between VLRA, HLRA, and DESTINATION NETWORK B.](3ad00ce93ad9dea9ee0f47535e5355e6_img.jpg) + +``` + + VLRA HLRA DESTINATION + NETWORK B + +-+ +-+ +-+ + | | | | | | + | | RegisterCCEntry | | | | + | |---------------------->| | | | + | | TC-BEGIN | | | | + | | | | CcbsRequest | | + | | | |-------------------->| | + | | | | TC-BEGIN | | + | | | | SCCP | | + +-+ +-+ +-+ + +``` + +Sequence diagram showing the signalling flow for CCBS REQUEST INVOCATION between VLRA, HLRA, and DESTINATION NETWORK B. + +Figure 6.1: Signalling flow for CCBS REQUEST INVOCATION + +The CCBS Request invocation is carried by TC-BEGIN. The SCCP addressing parameters on the SSAP interface shall be as shown in table 7.1. + +## 6.2 Dialogue Continuation + +### 6.2.1 CCBS Request Result + +![Sequence diagram showing the signalling flow for CCBS Request Result between VLRA, HLRA, and DESTINATION NETWORK B.](5dfc130b129ace4df375839020a5700d_img.jpg) + +``` + + VLRA HLRA DESTINATION + NETWORK B + +-+ +-+ +-+ + | | | | | | + | | | | CcbsRequest-Result | | + | | | |<---------------------| | + | | | | TC-CONTINUE | | + | | | | SCCP | | + | | | | | | + | | RegisterCCEntry-Result| | | | + | |<----------------------| | | | + | | TC-END | | | | + +-+ +-+ +-+ + +``` + +Sequence diagram showing the signalling flow for CCBS Request Result between VLRA, HLRA, and DESTINATION NETWORK B. + +Figure 6.2: Signalling flow for CCBS Request Result + +The CCBS Request Result is carried by TC-CONTINUE. The SCCP addressing parameters on the SSAP interface shall be as shown in table 7.3. + +### 6.2.2 CCBS Remote User Free Invocation + +![Sequence diagram showing the entities for CCBS Remote User Free Invocation: VLRA, HLRA, and DESTINATION NETWORK B.](ea37ab05b033e59cfdf7b074161aaf5a_img.jpg) + +``` + + VLRA HLRA DESTINATION + NETWORK B + +-+ +-+ +-+ + | | | | | | + +``` + +Sequence diagram showing the entities for CCBS Remote User Free Invocation: VLRA, HLRA, and DESTINATION NETWORK B. + +![Sequence diagram for Remote User Free Invocation. It shows two lifelines. The left lifeline sends a RemoteUserFree message with TC-BEGIN to the right lifeline. The right lifeline responds with a RemoteUserFree message containing TC-CONTINUE and SCCP.](a33da0f14e456f92539ce3e9b7d81f9a_img.jpg) + +``` + +sequenceDiagram + participant Left + participant Right + Note left of Left: Error! No + Note right of Right: Error! No text of specified style in + Left->>Right: RemoteUserFree
TC-BEGIN + Right-->>Left: RemoteUserFree
TC-CONTINUE
SCCP + +``` + +Sequence diagram for Remote User Free Invocation. It shows two lifelines. The left lifeline sends a RemoteUserFree message with TC-BEGIN to the right lifeline. The right lifeline responds with a RemoteUserFree message containing TC-CONTINUE and SCCP. + +**Figure 6.3: Signalling flow for Remote User Free Invocation** + +The CCBS Remote User Free Invocation is carried by TC-CONTINUE. The SCCP addressing parameters on the SSAP interface shall be as shown in table 7.3. + +### 6.2.3 CCBS Suspend Invocation + +![Sequence diagram for CCBS Suspend Invocation (RemoteUserFree_Result). It shows three lifelines: VLRA, HLRA, and DESTINATION NETWORK B. VLRA sends RemoteUserFree-Result and TC-END to HLRA. HLRA then sends CcbsSuspend (note 1) and TC-CONTINUE SCCP to DESTINATION NETWORK B.](16c1175b5f05a4b55e6d396fc51b15b3_img.jpg) + +``` + +sequenceDiagram + participant VLRA + participant HLRA + participant DESTINATION_NETWORK_B as DESTINATION NETWORK B + VLRA->>HLRA: RemoteUserFree-Result
TC-END + HLRA->>DESTINATION_NETWORK_B: CcbsSuspend (note 1)
TC-CONTINUE
SCCP + +``` + +Sequence diagram for CCBS Suspend Invocation (RemoteUserFree\_Result). It shows three lifelines: VLRA, HLRA, and DESTINATION NETWORK B. VLRA sends RemoteUserFree-Result and TC-END to HLRA. HLRA then sends CcbsSuspend (note 1) and TC-CONTINUE SCCP to DESTINATION NETWORK B. + +NOTE 1 For conditions leading to a request being suspended, see GSM 03.93 + +**Figure 6.4: Signalling flow for CCBS Suspend Invocation (RemoteUserFree\_Result)** + +![Sequence diagram for CCBS Suspend Invocation (RemoteUserFree_Error). It shows three lifelines: VLRA, HLRA, and DESTINATION NETWORK B. VLRA sends RemoteUserFree-Error and TC-END to HLRA. HLRA then sends CcbsSuspend (note 1) and TC-CONTINUE SCCP to DESTINATION NETWORK B.](d17f75945bbb3feb84a153ecfedb9b81_img.jpg) + +``` + +sequenceDiagram + participant VLRA + participant HLRA + participant DESTINATION_NETWORK_B as DESTINATION NETWORK B + VLRA->>HLRA: RemoteUserFree-Error
TC-END + HLRA->>DESTINATION_NETWORK_B: CcbsSuspend (note 1)
TC-CONTINUE
SCCP + +``` + +Sequence diagram for CCBS Suspend Invocation (RemoteUserFree\_Error). It shows three lifelines: VLRA, HLRA, and DESTINATION NETWORK B. VLRA sends RemoteUserFree-Error and TC-END to HLRA. HLRA then sends CcbsSuspend (note 1) and TC-CONTINUE SCCP to DESTINATION NETWORK B. + +NOTE 1 For conditions leading to a request being suspended, see GSM 03.93 + +**Figure 6.5: Signalling flow for CCBS Suspend Invocation (RemoteUserFree\_Error)** + +The CCBS Suspend Invocation is carried by TC-CONTINUE. The SCCP addressing parameters on the SSAP interface shall be as shown in table 7.2 + +### 6.2.4 CCBS Resume Invocation + +![Sequence diagram for CCBS Resume Invocation showing messages StatusReport, TC-BEGIN, CcbsResume, TC-CONTINUE, and SCCP between VLRA, HLRA, and DESTINATION NETWORK B.](75f0cb39f1cd165dfe4a6aa6c4d9388d_img.jpg) + +``` + +sequenceDiagram + participant VLRA + participant HLRA + participant DESTINATION_NETWORK_B as DESTINATION NETWORK B + Note left of VLRA: +--+\n | |\n +--+\n VLRA->>HLRA: StatusReport\n Note right of HLRA: +--+\n | |\n +--+\n HLRA->>DESTINATION_NETWORK_B: CcbsResume (note 1)\n Note right of DESTINATION_NETWORK_B: +--+\n | |\n +--+\n +``` + +Sequence diagram for CCBS Resume Invocation showing messages StatusReport, TC-BEGIN, CcbsResume, TC-CONTINUE, and SCCP between VLRA, HLRA, and DESTINATION NETWORK B. + +NOTE 1 For conditions leading to a request being resumed, see GSM 03.93 + +**Figure 6.6: Signalling flow for CCBS Resume Invocation** + +The CCBS Resume Invocation is carried by TC-CONTINUE. The SCCP addressing parameters on the SSAP interface shall be as shown in table 7.2. + +## 6.3 Dialogue End + +### 6.3.1 Normal dialogue end + +![Sequence diagram for Normal dialogue end showing messages SetReportingState, TC-BEGIN, No component primitive, TC-END, and SCCP between VLRA, HLRA, and DESTINATION NETWORK B.](70de8885bd7de15723aaad5eb5c5febf_img.jpg) + +``` + +sequenceDiagram + participant VLRA + participant HLRA + participant DESTINATION_NETWORK_B as DESTINATION NETWORK B + Note left of VLRA: +--+\n | |\n +--+\n VLRA->>HLRA: SetReportingState (note 1)\n Note right of HLRA: +--+\n | |\n +--+\n DESTINATION_NETWORK_B->>HLRA: No component primitive\n Note right of DESTINATION_NETWORK_B: +--+\n | |\n +--+\n HLRA->>VLRA: TC-END\n Note right of VLRA: TC-BEGIN\n +``` + +Sequence diagram for Normal dialogue end showing messages SetReportingState, TC-BEGIN, No component primitive, TC-END, and SCCP between VLRA, HLRA, and DESTINATION NETWORK B. + +NOTE 1 If the monitoring function is active in VLR A and all outstanding CCBS Requests have been deactivated, the HLR A sends SetReportingState to deactivate the monitoring function (see GSM 03.93). + +**Figure 6.7: Signalling flow for normal dialogue end** + +The normal ending of CCBS dialogue from the B-side is carried by TC-END. The SCCP addressing parameters on the SSAP interface shall be as shown in table 7.3. + +### 6.3.2 CCBS Cancel Invocation (from A-side) + +![Sequence diagram for CCBS Cancel Invocation from A-side](16152cf1d84aea10848758f51a91ff6a_img.jpg) + +``` +sequenceDiagram + participant VLRA + participant HLRA + participant DN as DESTINATION NETWORK B + Note left of VLRA: (note 1) + VLRA->>HLRA: EraseCCEntry + Note right of HLRA: (note 1) + HLRA->>DN: CcbsCancel + Note right of DN: (note 1) +``` + +The diagram illustrates the signalling flow for CCBS Cancel Invocation from the A-side. It involves three entities: VLRA, HLRA, and DESTINATION NETWORK B. The sequence of messages is as follows: VLRA sends an 'EraseCCEntry' message to HLRA, accompanied by 'TC-BEGIN'. HLRA then sends a 'CcbsCancel' message to DESTINATION NETWORK B, accompanied by 'TC-END' and 'SCCP'. Both the 'EraseCCEntry' and 'CcbsCancel' messages are associated with 'note 1'. + +Sequence diagram for CCBS Cancel Invocation from A-side + +NOTE 1 Where all outstanding CCBS Requests have been deactivated, CCBS Cancel is sent to each corresponding Destination Network B with the appropriate Destination Network B E.164 Called Party Address (see GSM 03.93, GSM 04.93). + +**Figure 6.8: Signalling flow for CCBS Cancel Invocation (from A-side)** + +The CCBS Cancel Invocation from the A-side is carried by TC-END. The SCCP addressing parameters on the SSAP interface shall be as shown in table 7.2. + +### 6.3.3 CCBS Cancel Invocation (from B-side) + +![Sequence diagram for CCBS Cancel Invocation from B-side](6f341f415ee0f8c724e5d6daeb1e9b4a_img.jpg) + +``` +sequenceDiagram + participant VLRA + participant HLRA + participant DN as DESTINATION NETWORK B + Note right of DN: (note 1) + DN->>HLRA: CcbsCancel + Note right of HLRA: (note 1) + HLRA->>VLRA: SetReportingState + Note left of VLRA: (note 1) +``` + +The diagram illustrates the signalling flow for CCBS Cancel Invocation from the B-side. It involves three entities: VLRA, HLRA, and DESTINATION NETWORK B. The sequence of messages is as follows: DESTINATION NETWORK B sends a 'CcbsCancel' message to HLRA, accompanied by 'TC-END' and 'SCCP'. HLRA then sends a 'SetReportingState' message to VLRA, accompanied by 'TC-BEGIN'. Both the 'CcbsCancel' and 'SetReportingState' messages are associated with 'note 1'. + +Sequence diagram for CCBS Cancel Invocation from B-side + +NOTE 1: If the monitoring function is active in VLR A and all outstanding CCBS Requests have been deactivated, the HLR A sends SetReportingState to deactivate the monitoring function (see GSM 03.93). + +**Figure 6.9: Signalling flow for CCBS Cancel Invocation (from B-side)** + +The CCBS Cancel Invocation from the B-side is carried by TC-END. The SCCP addressing parameters on the SSAP interface shall be as shown in table 7.3. + +### 6.3.4 CCBS Request Error + +![Sequence diagram showing signalling flow for CCBS Request Error between VLRA, HLRA, and DESTINATION NETWORK B. The diagram shows two error messages: RegisterCCEntry-Error from DESTINATION NETWORK B to VLRA, and CcbsRequest-Error from DESTINATION NETWORK B to HLRA. Both messages include TC-END and SCCP components.](df82d77a0d2637cbf2da9ea920a554fa_img.jpg) + +``` + +sequenceDiagram + participant VLRA + participant HLRA + participant DESTINATION_NETWORK_B as DESTINATION NETWORK B + Note right of DESTINATION_NETWORK_B: RegisterCCEntry-Error + DESTINATION_NETWORK_B-->>VLRA: RegisterCCEntry-Error + Note right of DESTINATION_NETWORK_B: CcbsRequest-Error + DESTINATION_NETWORK_B-->>HLRA: CcbsRequest-Error + +``` + +Sequence diagram showing signalling flow for CCBS Request Error between VLRA, HLRA, and DESTINATION NETWORK B. The diagram shows two error messages: RegisterCCEntry-Error from DESTINATION NETWORK B to VLRA, and CcbsRequest-Error from DESTINATION NETWORK B to HLRA. Both messages include TC-END and SCCP components. + +Figure 6.10: Signalling flow for CCBS Request Error + +The CCBS Request Error is carried by TC-END. The SCCP addressing parameters on the SSAP interface shall be as shown in table 7.3. + +# 7 Addressing of SCCP layer messages on the SSAP interface + +The SCCP layer addressing for messages on the SSAP interface is described. + +## 7.1 Use of SCCP + +Clarifications and restrictions on the use and coding of the main SCCP parameters impacted by CCBS on the SSAP interface are indicated. See ETS 300 356-18 and the associated references for the full specification on the use of SCCP on the SSAP interface. The SCCP routeing on the SSAP interface shall be based on the Global Title (GT) translation mechanism as for routeing on the international interface. GT addressing shall be used for inter and intra PLMN signalling. This allows any impact of other network features e.g. Mobile Number Portability to be minimised. + +## 7.2 Addressing of messages at the originating PLMN + +### 7.2.1 TC-BEGIN message from the originating network HLR + +The relevant SCCP parameters in the first message from the HLR A transporting TC-BEGIN are shown in table 7.1. All other SCCP parameters shall be as indicated in ETS 300 356-18. + +**Table 7.1: SCCP parameters used by HLR A for TC-BEGIN** + +| SCCP PARAMETERS for the message transporting TC-BEGIN | PARAMETER VALUE | +|--------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CdPA-Called Party Address | E.164 number of the Called Party. This may be in either international or national E.164 format, see subclause 7.4.1. It is derived from the translatedB-Number parameter which is available from the CCBS application in HLRA, see RegisterCCEntry in GSM 09.02. | +| CgPA-Calling Party Address | E.164 number of HLR A. This may be in either international or national E.164 format, see subclause 7.4.1. | +| SSN- Subsystem Number | 0000 1011
(See ETS 300 356-18) | +| TT- Translation Type | 0001 0001
(See ETS 300 356-18) | +| Other SCCP Parameters | See ETS 300 356-18 | + +### 7.2.2 TC-CONTINUE, TC-END messages from the originating network HLR + +The relevant SCCP parameters in the subsequent messages from the HLR A transporting TC-CONTINUE and TC-END are shown in table 7.2. All other SCCP parameters shall be as indicated in ETS 300 356-18. + +**Table 7.2: SCCP parameters used by HLR A for TC-CONTINUE, TC-END** + +| SCCP PARAMETERS for the message transporting TC-CONTINUE, TC-END | PARAMETER VALUE | +|-------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CdPA-Called Party Address | The Called Party Address is the E.164 address of the calling entity in the destination network that was received in the first response message from the destination network (note 1). | +| CgPA-Calling Party Address | E.164 number of HLR A. This may be in either international or national E.164 format as used in the message transporting TC-BEGIN, see subclause 7.4.1. | +| SSN- Subsystem Number | 0000 1011
(See ETS 300 356-18) | +| TT- Translation Type | 0001 0001
(See ETS 300 356-18) | +| Other SCCP Parameters | See ETS 300 356-18 | +| NOTE 1 | If the destination network is a GSM PLMN, this is E.164 number of HLR B. | + +## 7.3 Addressing of messages at the destination PLMN + +### 7.3.1 TC-CONTINUE, TC-END messages from the destination network HLR + +The relevant SCCP parameters in the first and subsequent messages from the HLR B transporting TC-CONTINUE and TC-END are shown in table 7.3. All other SCCP parameters shall be as indicated in ETS 300 356-18. + +**Table 7.3: SCCP parameters for TC-CONTINUE, TC-END used by HLR B** + +| SCCP PARAMETERS for the message transporting TC-CONTINUE, TC-END | PARAMETER VALUE | +|-------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CdPA-Called Party Address | The Called Party Address is the E.164 address of the calling entity in the originating network that was received in the first message transporting TC-BEGIN from the originating network (note 1). | +| CgPA-Calling Party Address | E.164 number of HLR B. This may be in either international or national E.164 format, see subclause 7.4.2 (note 2) | +| SSN- Subsystem Number | 0000 1011
(See ETS 300 356-18) | +| TT- Translation Type | 0001 0001
(See ETS 300 356-18) | +| Other SCCP Parameters | See ETS 300 356-18 | +| NOTE 1 | If the originating network is a GSM PLMN, this is E.164 number of HLR A. | +| NOTE 2 | The E.164 number of HLR B is used as this allows any impact of other network features to be minimised. | + +## 7.4 parameters + +### Number formats of the SCCP address + +The Called and Calling Party Address information in SCCP should be in international E.164 format. Optionally national format E.164 addresses may be used in SCCP for routing of national traffic. For this, the HLR has to modify the addresses which are in international E.164 format to a national E.164 format. If a national format E.164 option is used, all involved network nodes in a given country (i.e. the originating network, any transit networks and the destination network) need support that option. As negotiation is not possible, the option selected by the originating network shall determine the addressing used for all messages which are a part of a single dialogue. + +### 7.4.1 + +#### Originating PLMN + +The Called and Calling Party Address information in SCCP should be in international E.164 format. + +The originating network HLR A may use the SCCP Called Party Address in national E.164 format if the called destination (as indicated by the translatedB-number) is in the same country as HLR A. + +The originating network HLR A may use the SCCP Calling Party Address in national E.164 format if the called destination (as indicated by the translatedB-number) is in the same country as HLR A. + +The originating network HLR A shall ensure that the SCCP Called and Calling Party Addresses are either both in international format or national format. + +### 7.4.2 + +### Destination PLMN + +The Called and Calling Party Address information in SCCP should be in international E.164 format. + +The destination network HLR B may use the SCCP Called Party Address in national E.164 format if the originating network is in the same country as HLR B. + +The destination network HLR B may use the SCCP Calling Party Address in national E.164 format if the originating network is in the same country as HLR B. + +The destination network HLR B shall ensure that the SCCP Called and Calling Party Addresses are either both in international format or national format. + +# Annex A (informative): Change history + +| Change history | | | | | | | +|----------------|--------|---------|------|---------|-------------|--------------------------------| +| TSG SA# | Spec | Version | CR | | New Version | Subject/Comment | +| CN#04 | 29.013 | | | R99 | 3.0.0 | Approved at CN#04 | +| CN#11 | 29.013 | 3.0.0 | | Rel-4 | 4.0.0 | Approved at CN#11 | +| CN#16 | 29.013 | 4.0.0 | | Rel-4 | 4.0.1 | References updated | +| CN#16 | 29.013 | 4.0.1 | | Rel-5 | 5.0.0 | Rel-5 created after CN#16 | +| CN#26 | 29.013 | 5.0.0 | | Rel-6 | 6.0.0 | Rel-6 created after CN#26 | +| CT#36 | 29.013 | 6.0.0 | | Rel-7 | 7.0.0 | Upgraded unchanged from Rel-6 | +| CT#42 | 29.013 | 7.0.0 | | Rel-8 | 8.0.0 | Upgraded unchanged from Rel-7 | +| CT#46 | 29.013 | 8.0.0 | 0006 | Rel-8 | 8.1.0 | ISDN BC mapping | +| CT#46 | 29.013 | 8.1.0 | | Rel-9 | 9.0.0 | Upgraded unchanged from Rel-8 | +| 2011-03 | 29.013 | 9.0.0 | - | Rel-10 | 10.0.0 | Update to Rel-10 version (MCC) | +| 2012-09 | 29.013 | 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/29_series/29016/c9d8a18a6137ad054b841d7a614afb48_img.jpg b/marked/Rel-11/29_series/29016/c9d8a18a6137ad054b841d7a614afb48_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0eb369c53aef7559592cf69395bd87670a072363 --- /dev/null +++ b/marked/Rel-11/29_series/29016/c9d8a18a6137ad054b841d7a614afb48_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e0ded5af96640efed03fa42a290b1d932b779fb4be985dd7e345ddbfc4c0743a +size 10031 diff --git a/marked/Rel-11/29_series/29016/raw.md b/marked/Rel-11/29_series/29016/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..d310b113739ecd0f1199a50a61a4905dd8a44ede --- /dev/null +++ b/marked/Rel-11/29_series/29016/raw.md @@ -0,0 +1,642 @@ + + + + + + +# --- Contents + +| | | +|-------------------------------------------------------------------------------|----| +| Foreword ..... | 4 | +| Introduction ..... | 4 | +| 1 Scope..... | 5 | +| 2 References..... | 5 | +| 2.1 Normative references ..... | 5 | +| 2.2 Informative references..... | 6 | +| 3 Definitions, symbols and abbreviations ..... | 7 | +| 4 Configuration of the Gs interface..... | 7 | +| 4.1 Use of Protocol Stacks ..... | 7 | +| 5 Conformance to message transfer part (MTP)..... | 7 | +| 5.1 General ..... | 7 | +| 5.2 MTP Level 1..... | 8 | +| 5.3 MTP Level 2..... | 8 | +| 5.3.1 MTP Level 2 for E1 Interface..... | 8 | +| 5.3.2 MTP Level 2 for T1 Interface..... | 8 | +| 5.4 MTP Level 3..... | 8 | +| 5.4.1 MTP Level 3 for E1 Interface..... | 8 | +| 5.4.1.1 General clauses ..... | 9 | +| 5.4.1.2 Configuration dependent clauses ..... | 9 | +| 5.4.1.3 Informative clauses ..... | 11 | +| 5.4.2 MTP Level 3 for T1 Interface..... | 12 | +| 5.4.2.1 General clauses ..... | 12 | +| 5.4.2.2 Configuration dependent clauses ..... | 13 | +| 5.4.2.3 Informative clauses ..... | 15 | +| 6 Conformance to SCCP ..... | 16 | +| 6.1 Overview ..... | 16 | +| 6.2 SCCP Primitives..... | 16 | +| 6.2.1 SCCP Primitives for E1 Interface (ITU Recommendation Q.711) ..... | 16 | +| 6.2.2 SCCP Primitives for T1 Interface (ANSI Standards T1.112.1) ..... | 16 | +| 6.3 SCCP messages..... | 17 | +| 6.3.1 SCCP messages for E1 Interface (ITU Recommendation Q.712)..... | 17 | +| 6.3.2 SCCP messages for T1 Interface (ANSI Standards T1.112.2)..... | 17 | +| 6.4 SCCP formats and codes..... | 18 | +| 6.4.1 SCCP format and codes for E1 Interface (ITU Recommendation Q.713) ..... | 18 | +| 6.4.2 SCCP format and codes for T1 Interface (ANSI Standards T1.112.3) ..... | 18 | +| 6.5 SCCP procedures..... | 19 | +| 6.5.1 SCCP procedures for E1 Interface (ITU Recommendation Q.714) ..... | 19 | +| 6.5.2 SCCP procedures for T1 Interface (ANSI Standards T1.112.4) ..... | 19 | +| 7 Use of the SCCP (E1/T1 Interface)..... | 20 | +| Annex A (informative): Change history..... | 21 | + +# --- Foreword + +This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP). + +The present document provides a mechanism giving reliable transfer of signalling messages between the Serving GPRS Support Node (SGSN) and the data base of a Visitors Location Register (VLR) for co-ordination between GSM circuit switched services and GSM packet data services within the 3GPP system. + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 Indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the specification; + +# --- Introduction + +The present document specifies or references the necessary information to provide a reliable transfer of signalling messages between the Serving GPRS Support Node (SGSN) and the Visitors Location Register (VLR). This reliable transfer of messages is provided by the Network Service Part (NSP) of the Signalling System No 7 (SS7). This document specifies or references the subset of MTP and SCCP to be used in the Gs interface. + +# --- 1 Scope + +The present document specifies or references the subset of MTP and SCCP which is used for the reliable transport of BSSAP+ messages in the Gs interface. The present document references the 3GPP TS 29.202 which specifies alternative transport layers that can be applied instead of the MTP. The present document also specifies the SCCP addressing capabilities to be provided in the Gs interface. + +The present document is divided into two main parts, clause 5 dealing with the use of MTP and clauses 6 and 7 dealing with the use of SCCP. + +Clause 5 of the present document deals with the subset of the MTP that is required between an SGSN and a VLR. It is intended that this implementation of MTP is compatible with a full MTP implementation. Clause 4 references the 3GPP TS 29.202 which specifies alternatives to the MTP. + +The SCCP is used to provide message routing between the SGSN and the VLR. The SCCP routing principles specified in the present document allow to connect one SGSN to several VLR. No segmentation at SCCP level is needed on the Gs interface. Only SCCP class 0 is used on the Gs interface. Clauses 6 and 7 identify the SCCP subset that should be used between an SGSN and an VLR. + +# --- 2 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. +- For a specific reference, subsequent revisions do not apply. +- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. + +## 2.1 Normative references + +- [1] Void. +- [1a] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications". +- [2] 3GPP TS 22.060: "General Packet Radio Service (GPRS); Service description; Stage 1". +- [3] 3GPP TS 23.003: "Numbering, addressing and identification". +- [4] 3GPP TS 43.022: "Functions related to Mobile Station (MS) in idle mode and group receive mode". +- [5] 3GPP TS 23.060: "General Packet Radio Service (GPRS); Service description; Stage 2". +- [6] 3GPP TS 48.006: "Signalling transport mechanism specification for the Base Station System - Mobile-services Switching Centre (BSS - MSC) interface". +- [7] 3GPP TS 48.008: "Mobile-services Switching Centre - Base Station System (MSC - BSS) interface; Layer 3 specification". +- [8] 3GPP TS 48.018: "General Packet Radio Service (GPRS); Base Station System (BSS) - Serving GPRS Support Node (SGSN); BSS GPRS Protocol (BSSGP)". +- [9] 3GPP TS 29.002: "Mobile Application Part (MAP) specification". +- [10] 3GPP TS 49.008: "Application of the Base Station System Application Part (BSSAP) on the E-interface". + +- [11] 3GPP TS 29.018: "General Packet Radio Service (GPRS); Serving GPRS Support Node (SGSN) - Visitors Location Register (VLR); Gs interface Layer 3 specification". +- [12] ITU-T Recommendation E.164: "The international public telecommunication numbering plan". +- [13] ITU-T Recommendation Q.711: "Functional description of the signalling connection control part". +- [14] ITU-T Recommendation Q.712: "Definition and function of signalling connection control part messages". +- [15] ITU-T Recommendation Q.713: "Signalling connection control part formats and codes". +- [16] ITU-T Recommendation Q.714: "Signalling connection control part procedures". +- [17] ITU-T Recommendation Q.702: "Signalling data link". +- [18] ITU-T Recommendation Q.703: "Signalling link". +- [19] ITU-T Recommendation Q.704: "Signalling network functions and messages". +- [20] ITU-T Recommendation Q.707: "Testing and maintenance". +- [21] ANSI T1.111 (1996):"Signalling System No. 7 (SS7); Message Transfer Part". +- [22] ANSI T1.112 (1996): "Signalling System No. 7 (SS7); Signalling Connection Control Part Functional Description". +- [41] 3GPP TS 29.202: "Signalling System No. 7 (SS7) signalling transport in core network; Stage 3". + +## 2.2 Informative references + +- [23] 3GPP TS 22.001: "Principles of telecommunication services supported by a GSM Public Land Mobile Network (PLMN)". +- [24] 3GPP TS 22.002: "Circuit Bearer Services (BS) supported by a Public Land Mobile Network (PLMN)". +- [25] 3GPP TS 22.003: "Circuit Teleservices supported by a Public Land Mobile Network (PLMN)". +- [26] Void. +- [27] Void. +- [28] 3GPP TS 43.064: "Overall description of the GPRS Radio interface; Stage 2". +- [29] 3GPP TS 24.002: "GSM - UMTS Public Land Mobile Network (PLMN) access reference configuration". +- [30] 3GPP TS 24.007: "Mobile radio interface signalling layer 3; General aspects". +- [31] 3GPP TS 24.008: "Mobile radio interface layer 3 specification; Core network protocols; Stage 3". +- [32] 3GPP TS 44.065: "Mobile Station (MS) - Serving GPRS Support Node (SGSN); Subnetwork Dependent Convergence Protocol (SNDCP)". +- [33] 3GPP TS 48.060: "Inband control of remote transcoders and rate adaptors for Enhanced Full Rate (EFR) and full rate traffic channels." +- [34] 3GPP TS 29.060: "General Packet Radio Service (GPRS); GPRS Tunnelling Protocol (GTP) across the Gn and Gp Interface". +- [35] 3GPP TS 29.061: "Interworking between the Public Land Mobile Network (PLMN) supporting Packet Based services and Packet Data Networks (PDN)". +- [36] Void. +- [37] Void. + +- [38] Void. +- [39] Void. +- [40] Void. + +# --- 3 Definitions, symbols and abbreviations + +Unless listed below, the definitions, symbols and abbreviations are listed in 3GPP TR 21.905 and 3GPP TS 23.060. + +# --- 4 Configuration of the Gs interface + +The Gs interface connects the Serving GPRS Support Node (SGSN) to the Visitors Location Register (VLR). This interface is defined in the 64 kbit/s for E1 interface and for 64 kbit/s or 56 kbit/s for T1 interface boundary of an SGSN to a VLR or of a VLR to an SGSN. The configuration of the Gs interface shall not impose any restriction on the number of VLRs or SGSNs to be connected by the Gs interface. The Gs interface definition shall support an early implementation of GPRS when one SGSN may be connected to several VLRs or a more mature implementation when several SGSNs may be connected to one VLR. Therefore the interface shall support the use of an STP. + +The level of resilience in the Gs interface is determined by the operator, however it is recommended that the operator considers the use of more than one multiplex system between the SGSN and the VLR. Each multiplex system should be used to carry one signalling link and routing diversity should be provided among the signalling links to increase the resilience of the system. + +## 4.1 Use of Protocol Stacks + +BSSAP+ shall be transported over SCCP and the transport layers specified in 3GPP TS 29.202. The protocol stack is shown in figure 4.1. + +When MTP is used to transport BSSAP+ then the conformance rules specified in clause 5 shall apply. + +![](c9d8a18a6137ad054b841d7a614afb48_img.jpg) + +| | +|----------------------------------------------------| +| BSSAP+ | +| SCCP | +| Transport layers as specified in
3GPP TS 29.202 | + +**Figure 4.1: Protocol stack for the transportation of BSSAP+** + +# --- 5 Conformance to message transfer part (MTP) + +## 5.1 General + +The MTP functions as specified in ITU-T Recommendations Q.702, Q.703, Q.704 and Q.707 for E1 interface and ANSI T1.111 Recommendations for the T1 interface are applicable. However, the following subclauses provide a minimum set of MTP requirements that shall be implemented at a SGSN or VLR to support the functionality required by the BSSAP+ protocol in the Gs interface. The set of exceptions and modifications to those recommendations maintain compatibility with the implementation of a full specification of the MTP. The ITU-T recommendations for E1 interface and ANSI recommendation for T1 interface concerning the MTP shall be taken as requirements unless covered by a statement in the present document. + +## 5.2 MTP Level 1 + +The MTP level 1 exceptions and modifications to ITU-T Recommendation Q.702 and ANSI T1.111 Recommendation can be found in 3GPP TS 48.006 subclause 3.2. + +## 5.3 MTP Level 2 + +### 5.3.1 MTP Level 2 for E1 Interface + +The MTP level 2 exceptions and modifications to ITU-T Recommendation Q.703 are listed below. + +- ITU-T Recommendation Q.703, subclause 1.4: + - Only the basic error correction protocol is required. +- ITU-T Recommendation Q.703, clause 6: + - Not applicable, only basic error correction is required. +- ITU-T Recommendation Q.703, clause 7: + - Both the SGSN and the VLR may apply the emergency proving period or the normal proving period in the initial alignment procedure. If all the signalling links between the two entities are unavailable then the SGSN or the VLR shall apply the emergency proving period until one signalling link becomes available. +- ITU-T Recommendation Q.703, clause 8: + - The processor outage status indicator shall be recognised at the SGSN and the VLR and the procedures defined in ITU-T Recommendation Q.703 clause 8 supported. The SGSN and the VLR should support the generation of the processor outage indication towards the peer entity if this is appropriate. + +### 5.3.2 MTP Level 2 for T1 Interface + +The MTP level 2 exceptions and modifications to ANSI T1.111.3 are listed below. + +- ANSI T1.111.3, subclause 1.4: + - Only the basic error correction protocol is required (subclause 1.4.3 is not required). +- ANSI T1.111.3, clause 6: + - Not applicable, only basic error correction is required. +- ANSI T1.111.3, clause 7: + - Both the SGSN and the VLR may apply the emergency proving period or the normal proving period in the initial alignment procedure. If all the signalling links between the two entities are unavailable the SGSN or the VLR shall apply the emergency proving period until one signalling link becomes available. +- ANSI T1.111.3, clause 8: + - The processor outage status indicator shall be recognised at the SGSN and the procedures defined in ANSI T1.111.3 clause 8 supported. The SGSN and the VLR shall support the generation of the processor outage indication towards the peer entity if this is appropriate. + +## 5.4 MTP Level 3 + +### 5.4.1 MTP Level 3 for E1 Interface + +The Gs interface may be configured as a point to point interface or may use an intermediate SS7 network. In this last case an SGSN or a VLR may act always as end points of the Gs interface (SP functionality) or may be configured to act as a transfer point between a VLR and an SGSN (SP and STP functionality). The MTP level 3 exceptions and modifications to ITU-T Recommendation Q.704 are listed regarding whether the SGSN and the VLR are connected by a point to point link or are configured to act as SPs in an SS7 network or if they support STP functionality. + +Subclause 5.4.1.1 applies to all configurations of the Gs interface. In subclause 5.4.1.2 the exceptions and modifications to ITU-T Recommendation Q.704 are listed depending upon the configuration of the Gs interface, whether it is a point to point interface or the SGSN and VLR act as an SP only or as SP and STP. Subclause 5.4.1.3 provides points of clarification about the ITU-T Recommendation Q.704. + +#### 5.4.1.1 General clauses + +The MTP level 3 exceptions and modifications to ITU-T Recommendation Q.704 regardless of whether the SGSN supports STP functionality are listed below. + +- ITU-T Recommendation Q.704, subclause 2.3.5: + - Either of the two methods of congestion control is acceptable. The most appropriate method is dependent on national ITU-T No. 7 implementations. +- ITU-T Recommendation Q.704, subclause 2.4: + - The signalling point code for an SGSN may be included in the national signalling point code scheme or in a separate signalling network. +- ITU-T Recommendation Q.704, subclause 3.8.2: + - There are two acceptable methods of congestion control defined in ITU-T Recommendation Q.704, in subclauses 3.8.2.1 a) and b). The most appropriate method is dependent on national ITU-T No. 7 implementations. Each administration should specify its congestion threshold setting algorithm and nodal congestion abatement procedures at system procurement. +- ITU-T Recommendation Q.704, clause 12: + - Only basic link management procedures are required. +- ITU-T Recommendation Q.704, subclause 14.2.1: + - Since all messages are passed using the SCCP, the service indicator for Gs interface operation will be: + + +| | | | | | +|------|---|---|---|---| +| bits | D | C | B | A | +| | 0 | 0 | 1 | 1 | +- ITU-T Recommendation Q.704, subclause 14.2.2: + - The sub service field for Gs interface operation will always be set to one of the following values: + + +| | | | | +|------|---|---|------------------| +| bits | D | C | | +| | 1 | 0 | national network | +| | 1 | 1 | local network | +- ITU-T Recommendation Q.704, clause 15: + - The formats and codes listed are only relevant to the messages that are required, i.e. those not excluded in the rest of this recommendation. + +#### 5.4.1.2 Configuration dependent clauses + +The MTP level 3 exceptions and modifications to ITU-T Recommendation Q.704 are permitted if the SGSN or the VLR does not support STP functionality are listed below. + +- ITU-T Recommendation Q.704, subclause 1.1.2: + - If the Gs interface is configured as a point to point interface, then there will be no signalling network management features which need to be considered. +- ITU-T Recommendation Q.704, clause 2: + - If STP functionality is not required the discrimination function of the MTP used for GPRS application can be significantly simplified. + +NOTE: If the implementation of this interface is for point to point application the routing function within the MTP will be present to select the point code appropriate to the parent VLR. + +- ITU-T Recommendation Q.704, subclause 2.3: + - If the implementation of the Gs interface is point to point, load sharing between linksets is not required since there will only be one linkset between SGSN and VLR. +- ITU-T Recommendation Q.704, subclause 2.4: + - At an SGSN or VLR that does not implement STP functionality, only messages with a correctly checking DPC will be accepted. Others will be discarded. It is recommended that discarding a message because of an incorrectly set point code causes an incident report to be generated. +- ITU-T Recommendation Q.704, subclause 3.1.3 c): + - In a point to point configuration there is no requirement for signalling route management. +- ITU-T Recommendation Q.704, subclause 3.3.2.3: + - In a point to point configuration there is no requirement for signalling route management. +- ITU-T Recommendation Q.704, subclause 3.3.3.3: + - In a point to point configuration there is no requirement for signalling route management. +- ITU-T Recommendation Q.704, subclause 3.3.4.3: + - In a point to point configuration there is no requirement for signalling route management. +- ITU-T Recommendation Q.704, subclause 3.4.3: + - Not applicable if no STP functionality is implemented by the SGSN or the VLR. +- ITU-T Recommendation Q.704, subclause 3.5.3: + - Not applicable if no STP functionality is implemented by the SGSN or the VLR. +- ITU-T Recommendation Q.704, subclause 3.8.5.2: + - The signalling-route-set-congestion-test procedure is not required. +- ITU-T Recommendation Q.704, subclause 4.1.2: + - In a point to point configuration signalling routes are not applicable. +- ITU-T Recommendation Q.704, subclause 4.2: + - The normal routing situation in a point to point configuration will be that there are 1 or more signalling links available between a SGSN and VLR, these will constitute a link set. They will be run in a load sharing mode and changeover, changeback procedures will be supported between these signalling links. + - The normal routing situation if more than one route is available between the SGSN and the VLR will be that the load sharing, changeover and changeback procedures would be provided between signalling links within the same signalling linkset and between signalling linksets. +- ITU-T Recommendation Q.704, subclause 4.3.3: + - There will be no alternative linkset in a point to point configuration of the Gs interface. +- ITU-T Recommendation Q.704, subclause 4.4.3: + - Not applicable in a point to point configuration of the Gs interface. +- ITU-T Recommendation Q.704, subclause 4.5: + - Not applicable in a point to point configuration of the Gs interface. +- ITU-T Recommendation Q.704, subclause 4.6: + - Not applicable in a point to point configuration of the Gs interface. + +- ITU-T Recommendation Q.704, subclause 4.7: + - Not applicable in a point to point configuration of the Gs interface. +- ITU-T Recommendation Q.704, clause 5: + - Changeover between link sets is not applicable in a point to point configuration of the Gs interface. +- ITU-T Recommendation Q.704, clause 6: + - Changeback between link sets is not applicable in a point to point configuration of the Gs interface. +- ITU-T Recommendation Q.704, clause 7: + - Forced re-routing is not applicable if there is only one signalling route existing between SGSN and VLR in a point to point configuration of the Gs interface. +- ITU-T Recommendation Q.704, clause 8: + - Not applicable if there is only one signalling route existing between SGSN and VLR in a point to point configuration of the Gs interface. +- ITU-T Recommendation Q.704, subclause 13.2: + - The transfer prohibited function is not applicable if the SGSN or the VLR does not support STP functionality. At the reception of a TFP message, the SGSN or VLR acting as SP shall process the message. +- ITU-T Recommendation Q.704, subclause 13.3: + - The transfer allowed function is not applicable if the SGSN or the VLR does not support STP functionality. At the reception of a TFA-message, the SGSN or VLR acting as SP shall process the message. +- ITU-T Recommendation Q.704, subclause 13.4: + - The transfer restricted function is not applicable if the SGSN or the VLR does not support STP functionality. At the reception of the TFR message, the SGSN or VLR acting as SP shall process the message. +- ITU-T Recommendation Q.704, subclause 13.5: + - The signalling-route-set-test procedure is not applicable. +- ITU-T Recommendation Q.704, subclauses 13.6, 13.7 and 13.8: + - The transfer controlled function is not applicable if the SGSN or the VLR does not support STP functionality. At the reception of TFC message, the SGSN or VLR acting as SP shall process the message. +- ITU-T Recommendation Q.704, subclause 13.9: + - The signalling route-set-congestion-test function is not required. + - At the reception of signalling-route-set-congestion-test message no action is required by the receiving entity. + +#### 5.4.1.3 Informative clauses + +A list of clarifications to ITU-T Recommendation Q.704 are listed below. + +- ITU-T Recommendation Q.704, subclause 2.3.4: + - The load sharing procedures shall allow any value of the SLC field in the MTP3 network management messages that are not related to a specific signalling link. This allows compatibility between blue book implementations where only the 0000 value is used and white book implementations where load sharing may be applicable to network management messages +- ITU-T Recommendation Q.704, subclause 3.4.1: + - It should be noted that for point to point working, the signalling route will become unavailable when the associated link set fails. + +- ITU-T Recommendation Q.704, subclause 3.4.2: + - It should be noted that for point to point working, the signalling route will become available when the associated link set is restored. +- ITU-T Recommendation Q.704, subclause 3.5.1: + - It should be noted that for point to point working the procedures used in connection with signalling route unavailability will be those specified for signalling route set unavailability in ITU-T Recommendation Q.704 subclause 11.2.1. +- ITU-T Recommendation Q.704, subclause 3.5.2: + - It should be noted that for point to point interworking the procedures used in connection with signalling route availability will be those specified for signalling route set availability in ITU-T Recommendation Q.704 subclause 11.2.2. +- ITU-T Recommendation Q.704, clause 9: + - The SGSN and the MSC/VLR shall implement the restart procedures specified in ITU-T Recommendation Q.704 (03/1993) MTP3. The restart procedure specified in ITU-T Recommendation Q.704 (11/1988) MTP3 shall not be used. +- ITU-T Recommendation Q.704, clause 11: + - It should be noted that for point to point working the signalling route set will consist of one associated signalling route only. + +### 5.4.2 MTP Level 3 for T1 Interface + +The Gs interface may be configured as a point to point interface or may use an intermediate SS7 network. In this last case an SGSN or a VLR may act always as end points of the Gs interface (SP functionality) or may be configured to act as an transfer point between a VLR and an SGSN (SP and STP functionality). The MTP level 3 exceptions and modifications to ANSI T1.111.4 are listed regarding whether the SGSN and the VLR are connected by a point to point link or are configured to act as SPs in an SS7 network or if they support STP functionality. + +Subclause 5.4.2.1 applies to all configurations of the Gs interface. In subclause 5.4.2.2 the exceptions and modifications to ANSI T1.111.4 are listed depending upon the configuration of the Gs interface, whether it is a point to point interface or the SGSN and VLR act as an SP only or SP and STP. Subclause 5.4.2.3 provides points of clarification about the ANSI T1.111.4. + +#### 5.4.2.1 General clauses + +The MTP level 3 exceptions and modifications to ANSI T1.111.4 regardless of whether the SGSN supports STP functionality are listed below. + +- ANSI T1.111.4, subclause 2.3.5: + - Support of ANSI specific Signalling Link Congestion Control as specified in this subclause is required. +- ANSI T1.111.4, subclause 2.4: + - The signalling point code for an SGSN may be included in the national signalling point code scheme or in a separate signalling network. +- ANSI T1.111.4, subclause 3.8.2: + - Support of ANSI specific Network Congestion as defined in this subclause is required. +- ANSI T1.111.4, clause 12: + - Only basic link management procedures are required. +- ANSI T1.111.4, subclause 14.2.1: + - Since all messages are passed using the SCCP, the service indicator for Gs interface operation will be: + +| | | | | | +|------|---|---|---|---| +| bits | D | C | B | A | +| | 0 | 0 | 1 | 1 | + +- ANSI T1.111.4, subclause 14.2.2: + - The sub service field for Gs interface operation will always be set to one of the following values: + + +| | | | +|------|---|---| +| bits | D | C | +| | 1 | 0 | + + national network +- ANSI T1.111.4, clause 15: + - The formats and codes listed are only relevant to the messages that are required. + +#### 5.4.2.2 Configuration dependent clauses + +The MTP level 3 exceptions and modifications to ANSI T1.111.4 are permitted if the SGSN or the VLR does not support STP functionality are listed below. + +- ANSI T1.111.4, subclause 1.1.2: + - If the Gs interface is configured as point to point interface, i.e., it does not support STP function, then the signalling transfer point network management features are not required. +- ANSI T1.111.4, clause 2: + - If STP function is not required, then the discrimination functions of the MTP used for GPRS application can be significantly simplified. + +NOTE: If the implementation of this interface is for point to point application the routing function within the MTP will be present to select the point code appropriate to the parent VLR. + +- ANSI T1.111.4, subclause 2.3: + - If the implementation of the Gs interface is point to point, load sharing between linksets is not required since there will only be one linkset between SGSN and VLR. +- ANSI T1.111.4, subclause 2.4: + - At the SGSN or VLR that does not implement STP functionality, only messages with a correctly checking DPC will be accepted. Other messages will be discarded. It is recommended that when messages are discarded because of an incorrectly set point code, an incident report should be generated. +- ANSI T1.111.4, subclause 3.1.3 (3): + - In a point to point configuration, there is no requirement for signalling route management. +- ANSI T1.111.4, subclause 3.3.2.3: + - In a point to point configuration, there is no requirement for signalling route management. +- ANSI T1.111.4, subclause 3.3.3.3: + - In a point to point configuration, there is no requirement for signalling route management. +- ANSI T1.111.4, subclause 3.3.4.3: + - In a point to point configuration, there is no requirement for signalling route management. +- ANSI T1.111.4, subclause 3.4.3: + - Not applicable if no STP functionality is implemented in SGSN or VLR. +- ANSI T1.111.4, subclause 3.5.3: + - Not applicable if no STP functionality is implemented in SGSN or VLR. + +- ANSI T1.111.4, subclause 3.8.5.2: + - The signalling-route-set-congestion-test procedure is not required. +- ANSI T1.111.4, subclause 4.1.2: + - In a point to point configuration signalling routes are not applicable. +- ANSI T1.111.4, subclause 4.2: + - The normal routing situation in a point to point configuration will be that there are 1 or more signalling links available between a SGSN and VLR, these will constitute a link set. They will run in a load sharing mode and changeover, changeback procedures will be supported between these signalling links. + - The normal routing situation if more than one route is available between the SGSN and the VLR will be that the load sharing, changeover and changeback procedures would be provided between signalling links within the same signalling linkset and between signalling linksets. +- ANSI T1.111.4, subclause 4.3.3: + - There will be no alternative linkset in a point to point configuration of the Gs interface. +- ANSI T1.111.4, subclause 4.4.3: + - Not applicable in a point to point configuration of the Gs interface. +- ANSI T1.111.4, subclause 4.5: + - Not applicable in a point to point configuration of the Gs interface. +- ANSI T1.111.4, subclause 4.6: + - Not applicable in a point to point configuration of the Gs interface. +- ANSI T1.111.4, subclause 4.7: + - Not applicable in a point to point configuration of the Gs interface. +- ANSI T1.111.4, clause 5: + - Changeover between link sets is not applicable in a point to point configuration of the Gs interface. +- ANSI T1.111.4, clause 6: + - Changeback between link sets is not applicable in a point to point configuration of the Gs interface. +- ANSI T1.111.4, clause 7: + - Forced re-routing is not applicable since there is only one signalling route existing between SGSN and VLR in a point to point configuration of the Gs interface. +- ANSI T1.111.4, clause 8: + - Not applicable since there is only one signalling route existing between SGSN and VLR in a point to point configuration of the Gs interface. +- ANSI T1.111.4, subclause 13.2: + - The transfer prohibited function is not applicable if the SGSN does not support STP functionality. At the reception of a TFP message, the SGSN or VLR acting as SP shall process the message. +- ANSI T1.111.4, subclause 13.3: + - The transfer allowed function is not applicable if the SGSN does not support STP functionality. At the reception of a TFA-message, the SGSN or VLR acting as SP shall process the message. +- ANSI T1.111.4, subclause 13.4: + +- The transfer restricted function is not applicable if the SGSN does not support STP functionality. At the reception of the TFR message the SGSN or VLR acting as SP shall process the message. +- ANSI T1.111.4, subclause 13.5: + - The signalling-route-set-test procedure is not applicable. +- ANSI T1.111.4, subclauses 13.6, 13.7 and 13.8: + - The transfer controlled function is not applicable if the SGSN does not support STP functionality. At the reception of TFC message, the SGSN or VLR acting as SP shall process the message. +- ANSI T1.111.4, subclause 13.9: + - The signalling route-set-congestion-test function is not applicable. At the reception of signalling-route-set-congestion-test message no action is taken by the receiving entity. + +#### 5.4.2.3 Informative clauses + +A list of clarifications to ANSI Recommendation T1.111.4 are listed below. + +- ANSI T1.111.4, subclause 2.3.4: + - The load sharing procedures shall allow any value of the SLS field in the MTP3 network management messages that are not related to a specific signalling link or a default value of 00000000 should be used. +- ANSI T1.111.4, subclause 3.4.1: + - For point to point working, the signalling route will become unavailable when the associated link set fails. +- ANSI T1.111.4, subclause 3.4.2: + - For point to point working, the signalling route will become available when the associated link set is restored. +- ANSI T1.111.4, subclause 3.5.1: + - For point to point working, the procedures used in connection with signalling route unavailability will be those specified for signalling route set unavailability in ANSI Recommendation T1.111.4 subclause 11.2.1. +- ANSI T1.111.4, subclause 3.5.2: + - For point to point working, the procedures used in connection with signalling route availability will be those specified for signalling route set availability in ANSI Recommendation T1.111.4 subclause 11.2.2. +- ANSI T1.111.4, clause 9: + - The SGSN and the MSC/VLR shall implement the restart procedures specified in ANSI T1.111.4. +- ANSI T1.111.4, clause 11: + - For point to point working, the signalling route set will consist of one associated signalling route only. + +# --- 6 Conformance to SCCP + +## 6.1 Overview + +The purpose of this clause is to identify the subset of the SCCP functions which are necessary to provide addressing, error detection and segmentation facilities in the Gs interface. If this subset of SCCP functions is implemented, compatibility with a full ITU-T or ANSI SCCP shall be maintained. Only the needs of the user of SCCP (refer to 3GPP TS 29.018) are taken into account in this clause: the operations and maintenance requirements about SCCP functions are outside the scope of the present document. + +No SCCP translation function is required in the VLR or the SGSN between the national and the local MTP. The Destination Point Code and Subsystem Number would allow direct routing by the local SCCP and MTP. Global Title + +addressing is supported on the Gs interface to provide flexibility in the addressing scheme implementation (note that the SGSN is assigned a global title in order to communicate with an HLR across an inter PLMN boundary). + +Only connectionless class 0 SCCP services are used on the Gs interface. These simplifications are applicable to the signalling between an SGSN and a VLR in GSM PLMNs. + +The minimum set of SCCP functions which apply are specified in the ITU-T Recommendations Q.711, Q.712, Q.713 and Q.714, for E1 interface and ANSI T1.112 for T1 interface with the qualifications specified in this Recommendation. + +## 6.2 SCCP Primitives + +### 6.2.1 SCCP Primitives for E1 Interface (ITU Recommendation Q.711) + +- ITU-T Recommendation Q.711, clause 1: + - No SCCP connection-oriented services are used. +- ITU-T Recommendation Q.711, clause 2: + - No SCCP connection-oriented services are used. Only connectionless class 0 is used. +- ITU-T Recommendation Q.711, subclause 2.1: + - Not applicable. +- ITU-T Recommendation Q.711, subclause 4.1: + - Connection-oriented functions are not applicable + +### 6.2.2 SCCP Primitives for T1 Interface (ANSI Standards T1.112.1) + +- ANSI T1.112.1, clause 1: + - No SCCP connection-oriented services are used. +- ANSI T1.112.1, clause 2: + - No SCCP connection-oriented services are used. Only connectionless class 0. +- ANSI T1.112.1, subclause 2.1: + - Not applicable. +- ANSI T1.112.1, subclause 4.1: + - Connection-oriented functions are not applicable. + +## 6.3 SCCP messages + +### 6.3.1 SCCP messages for E1 Interface (ITU Recommendation Q.712) + +- ITU-T Recommendation Q.712, subclauses 1.1 to 1.14: + - Messages not used. +- ITU-T Recommendation Q.712, subclause 1.16: + - The Subsystem-Out-Of-Service-Grant (SOG) message is not used. +- ITU-T Recommendation Q.712, subclause 1.17: + - The Subsystem-Out-Of-Service-Request (SOR) message is not used. +- ITU-T Recommendation Q.712, subclauses 2.4, 2.6, 2.7, 2.9, 2.11, 2.12, 2.13, 2.14, 2.16 and 2.17: + - Parameters not used. + +### 6.3.2 SCCP messages for T1 Interface (ANSI Standards T1.112.2) + +- ANSI T1.112.2, subclauses 2.1 to 2.14: + - Messages not used. +- ANSI T1.112.2, subclause 3.4: + - The Subsystem-Out-Of-Service-Request (SOR) message is not used. +- ANSI T1.112.2, subclause 3.5: + - The Subsystem-Out-Of-Service-Grant (SOG) message is not used. +- ANSI T1.112.2, subclause 3.6: + - The Subsystem-Backup Routing (SBR) (Optional) message is not used. +- ANSI T1.112.2, subclause 3.7: + - The Subsystem-Normal Routing (SNR) (Optional) message is not used. +- ANSI T1.112.2, subclause 3.8: + - The Subsystem-Routing Status Test (SRT) (Optional) message is not used. +- ANSI T1.112.2, subclauses 4.2, 4.4, 4.6, 4.7, 4.10, 4.11, 4.12, 4.13, 4.15, 4.16, 4.17, 4.18 and 4.19: + - Parameters not used. + +## 6.4 SCCP formats and codes + +### 6.4.1 SCCP format and codes for E1 Interface (ITU Recommendation Q.713) + +- ITU-T Recommendation Q.713, subclause 3.4: + - The called party address shall include the appropriate sub system number. All other aspects of SCCP addressing are network specific. +- ITU-T Recommendation Q.713, subclause 3.4.2.2: + - SSN value: + - This is a national network concern. Different SSN values can be allocated for SGSN and VLR. +- ITU-T Recommendation Q.713, subclause 3.5: + - The calling party address shall include the appropriate sub system number. All other aspects of SCCP addressing are network specific. +- ITU-T Recommendation Q.713, subclause 3.6: + - Protocol class: the classes 1, 2 and 3 are not used. +- ITU-T Recommendation Q.713, subclauses 3.7 3.8, 3.9, 3.10, 3.11, 3.13, 3.14 and 3.15: + - Parameters not used. +- ITU-T Recommendation Q.713, subclauses 4.2 to 4.9 and 4.12 to 4.17: + - Messages not used. +- ITU-T Recommendation Q.713, subclause 5.1.1: + - SOR and SOG not needed. + +### 6.4.2 SCCP format and codes for T1 Interface (ANSI Standards T1.112.3) + +- ANSI T1.112.3, subclause 3.4: + - The called party address shall include the appropriate sub system number. All other aspects of SCCP addressing are network specific. +- ANSI T1.112.3, subclause 3.4.2.1: + - The SSN values are a national network concern. Different SSN values can be allocated for SGSN and VLR. +- ANSI T1.112.3, subclause 3.5: + - The calling party address shall include the appropriate sub-system number. All other aspects of SCCP addressing are network specific. +- ANSI T1.112.3, subclause 3.6: + - Protocol class: the classes 2 and 3 are not used. +- ANSI T1.112.3, subclauses 3.7, 3.8, 3.9, 3.10, 3.11, 3.13, 3.14 and 3.15: + - Parameters not used. +- ANSI T1.112.3, subclauses 4.2 to 4.9 and 4.12 to 4.17: + - Messages not used. +- ANSI T1.112.3, subclause 5.1.1: + - SOR, SNR, SRT, SBR, and SOG not needed. + +## 6.5 SCCP procedures + +### 6.5.1 SCCP procedures for E1 Interface (ITU Recommendation Q.714) + +- ITU-T Recommendation Q.714, subclauses 1.1.2 and 1.1.3: + - Protocol classes 2 and 3 not used. + - Connection-oriented services are not used. +- ITU-T Recommendation Q.714, subclause 1.2: + - Connection-oriented services are not used. +- ITU-T Recommendation Q.714, subclause 1.3: + - Protocol class 1 not used. +- ITU-T Recommendation Q.714, subclause 2.1: + - The two basic categories of addresses for connectionless messages are used. +- ITU-T Recommendation Q.714, subclause 2.2 and 2.3: + - No connection-oriented message is used. +- ITU-T Recommendation Q.714, clause 3: + - Connection-oriented procedures are not used. +- ITU-T Recommendation Q.714, clause 5: + - Only those messages and procedures relating to non-replicated subsystems or nodes are required. + +### 6.5.2 SCCP procedures for T1 Interface (ANSI Standards T1.112.4) + +- ANSI T1.112.4, subclauses 1.1.2 and 1.1.3: + - Protocol classes 2 and 3 not used. + - Connection-oriented services are not used. +- ANSI T1.112.4, subclause 1.2: + - Connection-oriented services are not used. +- ANSI T1.112.4, subclause 1.3: + - Protocol class 1 is not used. +- ANSI T1.112.4, subclause 2.1: + - The two basic categories of addresses for connectionless messages are used. +- ANSI T1.112.4, subclause 2.2 and 2.3: + - No connection-oriented message is used. +- ANSI T1.112.4, clause 3: + - Connection-oriented procedures not used. +- ANSI T1.112.4, clause 5: + - Only those messages and procedures relating to non-replicated subsystems or nodes are required. + +# --- 7 Use of the SCCP (E1/T1 Interface) + +The underlying transport stack and the SCCP are used to support signalling messages between the SGSN and the MSC. The BSSAP+ protocol specified in 3GPP TS 29.018 is the user of the SCCP. 3GPP TS 29.018 only uses the services of the class 0 of the SCCP. + +The Gs interface connects an SGSN to a VLR within the same PLMN. The use of point codes or global titles is allowed for routing of SCCP messages. + +The format and coding of address parameters carried by the SCCP for routing purpose shall comply with ITU-T Recommendation Q.713 for E1 interface and ANSI T1.112.3 T1 interface with the following restrictions: + +- The called party address shall include: + - an SSN (see subclause 6.4.1 E1 interface and subclause 6.4.2 for T1 interface); + - all other aspects of the SCCP signalling are specified in 3GPP TS 29.002. +- The calling party address shall include: + - an SSN (see subclause 6.4.1 E1 interface and subclause 6.4.2 for T1 interface); + - all other aspects of the SCCP signalling are specified in 3GPP TS 29.002. + +When an SCCP message is sent, the Called Party Address is derived from the Called Address of the N-UNITDATA-REQUEST primitive issued by the local SCCP user. + +When an SCCP message is received, the Calling Address within the N-UNITDATA-INDICATION primitive is derived from the Calling Party Address of the SCCP UNITDATA message received. + +Only address information belonging to the E.164 numbering plan is allowed to be included as Global Title in the Called and Calling Party Address. The SGSN and the VLR store the address of the other entity using the format received in the Calling Party Address field or the address information received in the application part of the message. + +# Annex A (informative): Change history + +| Change history | | | | | | | +|----------------|-----------|---------|----|---------|-------------|-------------------------| +| TSG CN# | Spec | Version | CR | | New Version | Subject/Comment | +| Apr 1999 | GSM 09.16 | 7.0.0 | | | | Transferred to 3GPP CN1 | +| CN#03 | 29.016 | | | | 3.0.0 | Approved at CN#03 | + +| TSG Meeting | TSG Doc number | TSG WG doc number | CR | Rev | Ph | Cat | Vers Old | Vers New | Subject | Date | +|-------------|----------------|-------------------|-----|-----|--------|-----|----------|----------|---------------------------------------------------------------------|---------| +| NP-09 | NP-000441 | N1-001017 | 004 | 1 | R99 | F | 3.0.0 | 3.1.0 | Different SSNs for SGSN and VLR | 09-2000 | +| NP-11 | NP-0100150 | N1-010459 | 005 | 1 | Rel-4 | C | 3.1.0 | 4.0.0 | BSSAP+ over IP according to SIGTRAN | 03-2001 | +| NP-16 | NP-020224 | N1-021326 | 006 | | Rel-4 | F | 4.0.0 | 4.1.0 | Various clean-up of wrong references | 06-2002 | +| NP-16 | | | | | Rel-5 | | 4.1.0 | 5.0.0 | CN plenary decision to make this 3GPP TS 29.016 also for Release 5. | 06-2002 | +| NP-26 | | | | | Rel-6 | | 5.0.0 | 6.0.0 | Rel-6 published after CN#26 | 12-2004 | +| | | | | | Rel-7 | | 6.0.0 | 7.0.0 | CN plenary decision to make this 3GPP TS 29.016 also for Release 7. | 06-2007 | +| | | | | | Rel-8 | | 7.0.0 | 8.0.0 | Upgrade to Rel-8 (CT#42) | 12-2008 | +| | | | | | Rel-9 | | 8.0.0 | 9.0.0 | Upgrade to Rel-9 (CT#46) | 12-2009 | +| | | | | | Rel-10 | | 9.0.0 | 10.0.0 | Upgrade to Rel-10 (CT#51) | 03-2011 | +| | | | | | Rel-11 | | 10.0.0 | 11.0.0 | Upgrade to Rel-11 (CT#57) | 09-2012 | \ No newline at end of file diff --git a/marked/Rel-11/29_series/29018/27b06ec9f42b5d727a2630f61a5f1861_img.jpg b/marked/Rel-11/29_series/29018/27b06ec9f42b5d727a2630f61a5f1861_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..dc00fe71c08986436c9cc32b73622f023b0f20b1 --- /dev/null +++ b/marked/Rel-11/29_series/29018/27b06ec9f42b5d727a2630f61a5f1861_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f25ca54825ba37feba6c989346ad8dd873c1ebf82aef7b26ee71ac1fc6c0412a +size 84181 diff --git a/marked/Rel-11/29_series/29018/2e399449b7f62d40167a65ca88888917_img.jpg b/marked/Rel-11/29_series/29018/2e399449b7f62d40167a65ca88888917_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..02917f9ae8f54fdeffe06023179b840a485484f6 --- /dev/null +++ b/marked/Rel-11/29_series/29018/2e399449b7f62d40167a65ca88888917_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9481a54d7c2f1b0c8e83b6a47ae1fe7c9c13e0eb3b63c5d527bc4c42c83b2f90 +size 92432 diff --git a/marked/Rel-11/29_series/29018/raw.md b/marked/Rel-11/29_series/29018/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..e277ae17b9f2fb313f7703587726406ee61f9431 --- /dev/null +++ b/marked/Rel-11/29_series/29018/raw.md @@ -0,0 +1,2435 @@ + + + + + + +# --- Contents + +| | | +|------------------------------------------------------------------|----| +| Foreword ..... | 7 | +| Introduction ..... | 7 | +| 1 Scope..... | 8 | +| 2 References..... | 8 | +| 2.1 Normative references ..... | 8 | +| 2.2 Informative references..... | 9 | +| 3 Definitions, symbols and abbreviations ..... | 10 | +| 4 Description of the association between a VLR and an SGSN ..... | 11 | +| 4.1 Association at the VLR ..... | 11 | +| 4.1.1 States at the VLR..... | 11 | +| 4.2 Association at the SGSN..... | 12 | +| 4.2.1 MM context variables at the SGSN..... | 12 | +| 4.2.2 States at the SGSN..... | 13 | +| 5 Paging for non-GPRS services procedure..... | 13 | +| 5.1 General description ..... | 13 | +| 5.2 Procedures in the VLR ..... | 13 | +| 5.2.1 Paging Initiation ..... | 14 | +| 5.2.2 Paging Response..... | 14 | +| 5.2.3 Paging Failure..... | 14 | +| 5.2.4 MS unreachable ..... | 14 | +| 5.3 Procedures in the SGSN..... | 14 | +| 6 Location Update for non-GPRS services procedure ..... | 15 | +| 6.1 General description ..... | 15 | +| 6.2 Procedures in the SGSN..... | 16 | +| 6.2.1 Location Update Initiation..... | 17 | +| 6.2.2 Location Update Response ..... | 18 | +| 6.2.3 Location Update Failure ..... | 19 | +| 6.2.4 Abnormal cases ..... | 19 | +| 6.3 Procedures in the VLR ..... | 19 | +| 6.3.1 Location Update Response ..... | 20 | +| 6.3.2 Location Update Failure ..... | 20 | +| 6.3.3 TMSI reallocation procedure..... | 20 | +| 6.3.4 Abnormal cases ..... | 20 | +| 7 Non-GPRS alert procedure ..... | 22 | +| 7.1 General description ..... | 22 | +| 7.2 Procedures in the VLR ..... | 22 | +| 7.2.1 Alert Initiation ..... | 22 | +| 7.2.2 Alert Response..... | 22 | +| 7.2.3 Alert failure ..... | 22 | +| 7.2.4 Alert Indication..... | 22 | +| 7.2.5 Abnormal cases ..... | 22 | +| 7.3 Procedures in the SGSN..... | 22 | +| 7.3.1 Alert response..... | 22 | +| 7.3.2 Alert failure ..... | 22 | +| 7.3.3 Alert indication..... | 22 | +| 8 Explicit IMSI detach from GPRS services procedure ..... | 23 | +| 8.1 General description ..... | 23 | +| 8.2 Procedures in the SGSN..... | 23 | +| 8.2.1 Explicit GPRS detach initiation..... | 23 | +| 8.2.2 Explicit GPRS detach Response..... | 23 | +| 8.2.3 Abnormal cases ..... | 24 | +| 8.3 Procedures in the VLR ..... | 24 | + +| | | | +|----------|-------------------------------------------------------------|----| +| 9 | Explicit IMSI detach from non-GPRS services procedure ..... | 24 | +| 9.1 | General description ..... | 24 | +| 9.2 | Procedures in the SGSN ..... | 24 | +| 9.2.1 | Explicit IMSI detach initiation ..... | 24 | +| 9.2.2 | Explicit IMSI detach Response ..... | 24 | +| 9.2.3 | Abnormal cases ..... | 24 | +| 9.3 | Procedures in the VLR ..... | 25 | +| 10 | Implicit IMSI detach from non-GPRS services procedure ..... | 25 | +| 10.1 | General description ..... | 25 | +| 10.2 | Procedures in the SGSN ..... | 25 | +| 10.3 | Procedures in the VLR ..... | 26 | +| 11 | VLR failure procedure ..... | 26 | +| 11.1 | General description ..... | 26 | +| 11.2 | Procedures in the VLR ..... | 26 | +| 11.2.1 | VLR Reset Initiation ..... | 26 | +| 11.2.2 | VLR Reset Response ..... | 26 | +| 11.2.3 | Abnormal cases ..... | 26 | +| 11.3 | Procedures in the SGSN ..... | 26 | +| 11.3.1 | VLR fails with restart ..... | 26 | +| 11.3.2 | VLR fails without restart ..... | 27 | +| 12 | SGSN failure procedure ..... | 27 | +| 12.1 | General description ..... | 27 | +| 12.2 | Procedures in the SGSN ..... | 27 | +| 12.2.1 | SGSN Reset Initiation ..... | 27 | +| 12.2.2 | SGSN Reset Response ..... | 27 | +| 12.2.3 | Abnormal cases ..... | 27 | +| 12.3 | Procedures in the VLR ..... | 28 | +| 13 | HLR failure ..... | 28 | +| 13.1 | General description ..... | 28 | +| 13.2 | Procedures in the SGSN ..... | 28 | +| 14 | MS Information procedure ..... | 28 | +| 14.1 | General description ..... | 28 | +| 14.2 | Procedures in the VLR ..... | 28 | +| 14.3 | Procedures in the SGSN ..... | 29 | +| 15 | MM information procedure ..... | 29 | +| 15.1 | General description ..... | 29 | +| 15.2 | Procedures in the VLR ..... | 29 | +| 15.3 | Procedures in the SGSN ..... | 29 | +| 16 | Error Handling and Future Compatibility ..... | 30 | +| 16.1 | General ..... | 30 | +| 16.2 | Message too short ..... | 30 | +| 16.3 | Unknown or unforeseen message type ..... | 30 | +| 16.4 | Missing mandatory information element ..... | 31 | +| 16.5 | IEs unknown or unforeseen in the message ..... | 31 | +| 16.6 | Out of sequence IEs ..... | 31 | +| 16.7 | Repeated IEs ..... | 31 | +| 16.8 | Syntactically incorrect mandatory IE ..... | 31 | +| 16.9 | Syntactically incorrect optional IEs ..... | 31 | +| 16.10 | Conditional IE errors ..... | 31 | +| 16.11 | IEs with semantically incorrect contents ..... | 31 | +| 17 | Message functional definitions and contents ..... | 32 | +| 17.1 | Message Contents ..... | 32 | +| 17.1.1 | BSSAP+-ALERT-ACK message ..... | 32 | +| 17.1.2 | BSSAP+-ALERT-REJECT message ..... | 32 | +| 17.1.2.1 | Gs Cause ..... | 32 | +| 17.1.3 | BSSAP+-ALERT-REQUEST message ..... | 32 | +| 17.1.4 | BSSAP+-DOWNLINK-TUNNEL-REQUEST message ..... | 32 | + +| | | | +|-----------|-----------------------------------------------------|----| +| 17.1.5 | BSSAP+-GPRS-DETACH-ACK message ..... | 33 | +| 17.1.6 | BSSAP+-GPRS-DETACH-INDICATION message ..... | 33 | +| 17.1.6.1 | Cell global identity (A/Gb mode only) ..... | 33 | +| 17.1.6.2 | Service area identification (Iu mode only) ..... | 33 | +| 17.1.7 | BSSAP+-IMSI-DETACH-ACK message ..... | 33 | +| 17.1.8 | BSSAP+-IMSI-DETACH-INDICATION message ..... | 34 | +| 17.1.8.1 | Cell global identity (A/Gb mode only) ..... | 34 | +| 17.1.8.2 | Location information age ..... | 34 | +| 17.1.8.3 | Service area identification (Iu mode only) ..... | 34 | +| 17.1.9 | BSSAP+-LOCATION-UPDATE-ACCEPT message ..... | 34 | +| 17.1.9.1 | New TMSI, or IMSI ..... | 35 | +| 17.1.10 | BSSAP+-LOCATION-UPDATE-REJECT message ..... | 35 | +| 17.1.10.1 | Message definition ..... | 35 | +| 17.1.10.2 | Location area identifier ..... | 35 | +| 17.1.11 | BSSAP+-LOCATION-UPDATE-REQUEST message ..... | 35 | +| 17.1.11.1 | Old location area identifier ..... | 36 | +| 17.1.11.2 | New cell global identity ..... | 36 | +| 17.1.11.3 | TMSI status ..... | 36 | +| 17.1.11.4 | Mobile station classmark ..... | 36 | +| 17.1.11.5 | New service area identification ..... | 36 | +| 17.1.11.6 | IMEISV ..... | 36 | +| 17.1.11.7 | TMSI based NRI container ..... | 36 | +| 17.1.11.8 | Selected CN operator ..... | 36 | +| 17.1.12 | BSSAP+-MM-INFORMATION-REQUEST ..... | 36 | +| 17.1.12.1 | MM information ..... | 37 | +| 17.1.13 | BSSAP+-MOBILE-STATUS message ..... | 37 | +| 17.1.13.1 | IMSI ..... | 37 | +| 17.1.14 | BSSAP+-MS-ACTIVITY-INDICATION message ..... | 37 | +| 17.1.14.1 | Cell global identity (A/Gb mode only) ..... | 37 | +| 17.1.14.2 | Service area identification (Iu mode only) ..... | 37 | +| 17.1.15 | BSSAP+-MS-INFORMATION-REQUEST message ..... | 37 | +| 17.1.16 | BSSAP+-MS-INFORMATION-RESPONSE message ..... | 38 | +| 17.1.16.1 | IMEI ..... | 38 | +| 17.1.16.2 | IMIESV ..... | 38 | +| 17.1.16.3 | Cell global identity (A/Gb mode only) ..... | 38 | +| 17.1.16.4 | Location information age ..... | 38 | +| 17.1.16.5 | Mobile station state ..... | 38 | +| 17.1.16.6 | TMSI ..... | 38 | +| 17.1.16.7 | Service area identification (Iu mode only) ..... | 39 | +| 17.1.17 | BSSAP+-MS-UNREACHABLE message ..... | 39 | +| 17.1.17.1 | Gs Cause ..... | 39 | +| 17.1.18 | BSSAP+-PAGING-REJECT message ..... | 39 | +| 17.1.19 | BSSAP+-PAGING-REQUEST message ..... | 39 | +| 17.1.19.1 | TMSI ..... | 40 | +| 17.1.19.2 | Location area identifier ..... | 40 | +| 17.1.19.3 | Channel needed ..... | 40 | +| 17.1.19.4 | eMLPP priority ..... | 40 | +| 17.1.19.5 | Global CN-Id ..... | 40 | +| 17.1.20 | BSSAP+-RESET-ACK message ..... | 40 | +| 17.1.20.1 | SGSN number ..... | 41 | +| 17.1.20.2 | VLR number ..... | 41 | +| 17.1.21 | BSSAP+-RESET-INDICATION message ..... | 41 | +| 17.1.21.1 | SGSN number ..... | 41 | +| 17.1.21.2 | VLR number ..... | 41 | +| 17.1.22 | BSSAP+-TMSI-REALLOCATION-COMPLETE message ..... | 41 | +| 17.1.22.1 | Cell global identity (A/Gb mode only) ..... | 41 | +| 17.1.22.2 | Service area identification (Iu mode only) ..... | 42 | +| 17.1.23 | BSSAP+-UPLINK-TUNNEL-REQUEST message ..... | 42 | +| 18 | Message format and information element coding ..... | 43 | +| 18.1 | Overview ..... | 43 | +| 18.2 | Message type ..... | 43 | + +| | | | +|------------------------|----------------------------------------------------|----| +| 18.3 | Information Element Identifiers ..... | 44 | +| 18.3a | Length indicator ..... | 44 | +| 18.4 | Information elements..... | 44 | +| 18.4.1 | Cell global identity ..... | 44 | +| 18.4.2 | Channel needed ..... | 45 | +| 18.4.3 | Downlink Tunnel Payload Control and Info ..... | 45 | +| 18.4.4 | eMLPP Priority..... | 45 | +| 18.4.5 | Erroneous message ..... | 46 | +| 18.4.6 | GPRS location update type..... | 46 | +| 18.4.7 | Gs cause..... | 46 | +| 18.4.8 | IMEI ..... | 47 | +| 18.4.9 | IMEISV ..... | 47 | +| 18.4.10 | IMSI..... | 48 | +| 18.4.11 | IMSI detach from GPRS service type ..... | 48 | +| 18.4.12 | IMSI detach from non-GPRS service type..... | 49 | +| 18.4.13 | Information requested..... | 49 | +| 18.4.14 | Location area identifier..... | 50 | +| 18.4.15 | Location information age ..... | 50 | +| 18.4.16 | MM information ..... | 51 | +| 18.4.17 | Mobile identity ..... | 51 | +| 18.4.18 | Mobile station classmark 1 ..... | 51 | +| 18.4.19 | Mobile station state..... | 52 | +| 18.4.20 | PTMSI ..... | 52 | +| 18.4.21 | Reject cause..... | 53 | +| 18.4.21b | Service Area Identification..... | 53 | +| 18.4.22 | SGSN number..... | 53 | +| 18.4.23 | TMSI..... | 53 | +| 18.4.24 | TMSI status ..... | 54 | +| 18.4.25 | Uplink Tunnel Payload Control and Info ..... | 54 | +| 18.4.26 | VLR number..... | 54 | +| 18.4.27 | Global CN-Id..... | 55 | +| 18.4.28 | TMSI based NRI container..... | 55 | +| 18.4.29 | Selected CN operator..... | 55 | +| 19 | List of system variables..... | 56 | +| 19.1 | Timers..... | 56 | +| 19.2 | Retry counters ..... | 57 | +| 20 | Procedures for Tunnelling Non-GSM Signalling ..... | 57 | +| 20.1 | Procedures in the non-GSM MSC/VLR..... | 57 | +| 20.2 | Procedures in the SGSN ..... | 57 | +| Annex A (informative): | Change history..... | 59 | + +# --- Foreword + +This Technical Specification (TS) has been produced by the 3rd Generation Partnership Project (3GPP). + +The present document specifies procedures used between the Serving GPRS Support Node (SGSN) and the Visitors Location Register (VLR) for co-ordination between GSM circuit switched services and GSM packet data services within the 3GPP system. + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +# --- Introduction + +The present document specifies or references the procedures to provide co-ordination between the GSM circuit switched services controlled at the Visitors Location Register (VLR) and the GSM packet switched services controlled at the Serving GPRS Support Node (SGSN). The procedures specified in the present document are intended to optimise the use of the resources when an MS supports both GSM circuit switched services and GSM packet switched services. + +# --- 1 Scope + +The present document specifies or references procedures used on the Serving GPRS Support Node (SGSN) to Visitors Location Register (VLR) interface for interoperability between GSM circuit switched services and GSM packet data services. + +The present document specifies the layer 3 messages and procedures on the Gs interface to allow coordination between databases and to relay certain messages related to GSM circuit switched services over the GPRS subsystem. + +The functional split between VLR and SGSN is defined in 3GPP TS 23.060 [8]. The required procedures between VLR and SGSN are defined in detail in the present document. + +# --- 2 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. +- For a specific reference, subsequent revisions do not apply. +- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. + +## 2.1 Normative references + +- [1] [Void] +- [1a] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications". +- [2] [Void] +- [3] [Void] +- [4] [Void] +- [5] 3GPP TS 23.003: "Numbering, addressing and identification". +- [6] 3GPP TS 23.007: "Restoration procedures". +- [6a] 3GPP TS 23.018: "Basic Call Handling; Technical realization". +- [7] [Void] +- [8] 3GPP TS 23.060: "General Packet Radio Service (GPRS); Service description; Stage 2". +- [9] [Void] +- [10] [Void] +- [11] 3GPP TS 24.008: "Mobile radio interface Layer 3 specification; Core network protocols; Stage 3". +- [11a] 3GPP TS 44.018: "Mobile radio interface layer 3 specification; Radio Resource Control Protocol". +- [12] 3GPP TS 44.064: "Mobile Station - Serving GPRS Support Node (MS-SGSN) Logical Link Control (LLC) layer specification". +- [13] [Void] +- [14] 3GPP TS 48.008: "Mobile-services Switching Centre - Base Station System (MSC-BSS) interface; Layer 3 specification". + +- [15] 3GPP TS 48.018: "Base Station System (BSS) - Serving GPRS Support Node (SGSN); BSS GPRS Protocol (BSSGP)". +- [16] [Void] +- [17] 3GPP TS 29.002: "Mobile Application Part (MAP) specification". +- [18] [Void] +- [19] [Void] +- [20] [Void] +- [21] [Void] +- [22] 3GPP TS 25.413: "UTRAN Iu interface RANAP signalling". +- [23] 3GPP TS 23.195: "Provision of UE Specific Behaviour Information to Network Entities". +- [23A] 3GPP TS 22.101: "Service Principles". +- [24] 3GPP TS 23.251: "Network sharing; Architecture and functional description". +- [25] 3GPP TS 32.422: "Subscriber and equipment trace; Trace control and Configuration Management (CM)". +- [26] 3GPP TS 23.236: "Intra-domain connection of Radio Access Network (RAN) nodes to multiple Core Network (CN) nodes". +- [27] 3GPP TS 29.118: "Mobility Management Entity (MME) - Visitor Location Register (VLR) SGs interface specification". +- [28] 3GPP TS 29.272: "MME and SGSN Related Interfaces Based on Diameter Protocol". + +## 2.2 Informative references + +- [22A] [Void] +- [23B] [Void] +- [24] [Void] +- [25] [Void] +- [26] [Void] +- [27] [Void] +- [28] [Void] +- [29] [Void] +- [30] [Void] +- [31] [Void] +- [32] [Void] +- [33] [Void] +- [34] [Void] +- [35] [Void] +- [36] [Void] +- [37] [Void] + +| | | +|------|--------------------------------------------------------------------------------------| +| [38] | [Void] | +| [39] | [Void] | +| [40] | [Void] | +| [41] | [Void] | +| [42] | [Void] | +| [43] | [Void] | +| [44] | [Void] | +| [45] | [Void] | +| [46] | [Void] | +| [47] | [Void] | +| [48] | [Void] | +| [49] | [Void] | +| [50] | [Void] | +| [51] | [Void] | +| [52] | [Void] | +| [53] | [Void] | +| [54] | [Void] | +| [55] | [Void] | +| [56] | [Void] | +| [57] | [Void] | +| [58] | [Void] | +| [59] | [Void] | +| [60] | [Void] | +| [61] | [Void] | +| [62] | [Void] | +| [63] | [Void] | +| [64] | ITU-T Recommendation Q.714 (03/93): "Signalling connection control part procedures". | +| [65] | [Void] | +| [66] | [Void] | + +# --- 3 Definitions, symbols and abbreviations + +For the purposes of the present document the definitions, symbols and abbreviations given in 3GPP TR 21.905 [1a] and in 3GPP TS 23.060 [8] apply. Additionally the following terms and definitions of 3GPP TS 23.251 [24] apply: + +**Common PLMN** + +**Gateway core network (GWCN)** + +**Non-supporting UE** + +**Supporting UE** + +# --- 4 Description of the association between a VLR and an SGSN + +The Gs interface connects the databases in the MSC/VLR and the SGSN. The procedures described in the present document are used to co-ordinate the location information of MSs that are IMSI attached to both GPRS and non-GPRS services. The Gs interface is also used to convey some circuit switched related procedures via the SGSN. + +The basis for the interworking between a VLR and an SGSN is the existence of an association between those entities per MS. An association consists of the SGSN storing the number of the VLR serving the MS for circuit switched services and the VLR storing the number of the SGSN serving the MS for packet switched services. The association is only applicable to MSs in class-A mode of operation and MSs in class-B mode of operation. The Gs association is not applicable if the subscriber data indicates that the MS has subscription for packet only. The Gs association is also not applicable if the MS requests only for GPRS services and "SMS-only service" and SMS service is to be provided by the SGSN based on conditions specified in 3GPP TS 23.060 [8]. + +All the messages described in the present document use the SCCP class 0 connectionless service. + +When the return option in SCCP is used and the sender receives an N\_NOTICE indication from SCCP, the sending entity shall report to the Operation and Maintenance system (see ITU-T Recommendation Q.714 [64]). + +The behaviour of the VLR and the SGSN entities related to the Gs interface are defined by the state of the association for an MS. Individual states per association, i.e. per MS in class-A mode of operation and MS in class-B mode of operation, are held at both the VLR and the SGSN. + +## 4.1 Association at the VLR + +The states associated to the Gs interface in the VLR are specified in this clause. The state diagram at the VLR is shown in figure 4.1. The state diagram does not include the message error handling specified in clause 16. + +### 4.1.1 States at the VLR + +#### Gs-NULL + +There is no association with an SGSN for the MS and therefore the VLR considers that the MS is IMSI detached for GPRS services. In this state no BSSAP+-MS-INFORMATION-REQUEST or BSSAP+-MM-INFORMATION-REQUEST messages are sent to the SGSN. The VLR may initiate paging on the Gs interface if the 'Confirmed by Radio Contact' restoration indicator in the VLR is set to 'false' (see 3GPP TS 23.007 [6]). Any message from the SGSN is ignored apart from the BSSAP+-LOCATION-UPDATE-REQUEST message, the BSSAP+-GPRS-DETACH-INDICATION message and the BSSAP+-IMSI-DETACH-INDICATION message. + +#### LA-UPDATE PRESENT + +The VLR has received a BSSAP+-LOCATION-UPDATE-REQUEST message from the SGSN. In this state the VLR may be waiting for the outcome of the Update Location procedure from the HLR. The VLR shall send BSSAP+-PAGING-REQUEST messages to MSs in class-A and MSs in class-B mode of operation via only the Gs interface. + +#### Gs-ASSOCIATED + +The VLR considers that the MS is attached to both GPRS and non-GPRS services. In this state the VLR sends BSSAP+-PAGING-REQUEST messages to MSs in class-A mode of operation and and MSs in class-B mode of operation via only the Gs interface. The VLR can perform the MS Identification procedure and the MM information procedure. + +![State transition diagram at the VLR showing transitions between Gs-NULL, LA-UPDATE PRESENT, and Gs-ASSOCIATED states based on network signals.](27b06ec9f42b5d727a2630f61a5f1861_img.jpg) + +``` + +stateDiagram-v2 + direction TB + FromOne: From one of the three states (at the VLR) + GsNULL: Gs-NULL + LAUpdate: LA-UPDATE PRESENT + GsAssoc: Gs-ASSOCIATED + + FromOne --> GsNULL : Reset received from the SGSN + FromOne --> GsNULL : VLR failure + FromOne --> GsNULL : Detach indication received from the SGSN or the MS + FromOne --> GsNULL : Location Update Request received from the MS via the A interface or via the Iu-CS interface, or from the MME via the SGs interface + + GsNULL --> GsNULL : Paging failure received + GsNULL --> GsNULL : Location Update Request received from the SGSN + GsNULL --> GsNULL : Send Paging + GsNULL --> LAUpdate : Send Location Update Reject + + LAUpdate --> GsNULL : Paging Failure or Alert Failure received + LAUpdate --> LAUpdate : Send Paging + LAUpdate --> GsAssoc : Location Update Request received from the SGSN + LAUpdate --> GsNULL : Send Location Update Accept + + GsAssoc --> GsNULL : BSSAP+-MS-UNREACHABLE message received + GsAssoc --> GsAssoc : TMSI Reallocation received + GsAssoc --> GsAssoc : Send Paging + GsAssoc --> GsNULL : Send Location Update Accept + +``` + +The diagram illustrates the state transitions for a VLR based on various network events. It features three main states: **Gs-NULL**, **LA-UPDATE PRESENT**, and **Gs-ASSOCIATED**. An entry point labeled "From one of the three states (at the VLR)" leads to **Gs-NULL** via several triggers including Reset from SGSN, VLR failure, Detach indications, or Location Update Requests from MS/MME. **Gs-NULL** can transition to **LA-UPDATE PRESENT** upon sending a Location Update Reject. **LA-UPDATE PRESENT** can transition to **Gs-ASSOCIATED** upon receiving a Location Update Request from the SGSN, or back to **Gs-NULL** upon Paging/Alert failure or sending a Location Update Accept. **Gs-ASSOCIATED** can transition back to **Gs-NULL** upon receiving a BSSAP+-MS-UNREACHABLE message or sending a Location Update Accept. + +State transition diagram at the VLR showing transitions between Gs-NULL, LA-UPDATE PRESENT, and Gs-ASSOCIATED states based on network signals. + +NOTE: Receipt of a BSSAP+-RESET-INDICATION message from the SGSN may change or not the state of the Gs interface of all the associations associated to the restarted SGSN, see subclause 12.3. + +**Figure 4.1/3GPP TS 29.018: State diagram at the VLR** + +## 4.2 Association at the SGSN + +The states and MM context variables associated to the Gs interface in the SGSN are specified in this clause. The state diagram at the SGSN is shown in figure 4.2. The state diagram does not include the message error handling specified in clause 16. + +### 4.2.1 MM context variables at the SGSN + +VLR-Reliable: Boolean + +Set to *'false'* when the SGSN has received a reset indication from the VLR. The SGSN may request to the MS, upon reception of the next routing area update (either periodic routing area update or combined routing and location area update) procedure, to re-attach to non-GPRS services if the MS is still IMSI attached to non-GPRS services. Alternatively the SGSN may upon reception of a combined routing and location area update request or a periodic routing area update from a MS that is still attached for non-GPRS service, perform immediately the location update for non-GPRS services procedure. + +EMM Combined UE Waiting Flag: Boolean + +Set to *'true'* when ISR is activated and: + +- the SGSN receives a Detach Notification indicating "Local Detach" for an MS which supports EMM Combined procedures from the associated MME; or +- the SGSN receives the request from the Serving GW for deactivating the last PDP context for an MS which supports EMM Combined procedures. + +On the fifth expiry of timer T3322 described as T3322 time-out in 3GPP TS 24.008 [11], the EMM Combined UE Waiting Flag shall be deactivated if it is activated. + +SGSN-Reset: Boolean + +Set to *'true'* when the SGSN restarts after a failure. The 'SGSN-Reset' variable is unique within an SGSN and it applies to all the MM context stored in the SGSN. + +### 4.2.2 States at the SGSN + +#### Gs-NULL + +There is no association with a VLR for the MS and therefore the SGSN considers that the MS is IMSI detached of non-GPRS services. In this state the SGSN accepts BSSAP+-PAGING-REQUEST messages to MSs only if the 'SGSN-Reset' restoration indicator in the SGSN is set to 'true'. + +#### LA-UPDATE Requested + +The SGSN has sent a BSSAP+-LOCATION-UPDATE-REQUEST message to the VLR. In this state the SGSN waits for the outcome of the Location Update for non-GPRS procedure at the VLR before sending the response to the MS. In this state the SGSN accepts BSSAP+-PAGING-REQUEST messages. + +#### Gs-ASSOCIATED + +The SGSN stores an association for that MS. In this state the SGSN performs the Location Update for non-GPRS services procedure towards the VLR for MSs in class-A and MSs in class-B mode of operation, e.g. when the MS moves to a new LA. All conditions describing when to trigger the location update for non-GPRS services procedure are listed in subclause 6.2.1. + +![State diagram at the SGSN showing transitions between Gs-NULL, LA-UPDATE Requested, and Gs-ASSOCIATED states.](2e399449b7f62d40167a65ca88888917_img.jpg) + +``` + +stateDiagram-v2 + [*] --> Gs-NULL : From one of the three States (at the SGSN) + Gs-NULL --> Gs-NULL : Send any detach indication (to the VLR) + Gs-NULL --> Gs-NULL : SGSN failure + Gs-NULL --> LA-UPDATE Requested : Send Location Area Update Request (to the VLR) + LA-UPDATE Requested --> Gs-NULL : Location Area Update Reject received + LA-UPDATE Requested --> Gs-ASSOCIATED : Location Area Update Accept received + Gs-NULL --> Gs-ASSOCIATED : Normal Routing Area Update Request Received from the MS + Gs-NULL --> Gs-ASSOCIATED : Combined routing area update request received from the MS with conditions listed in subclause 6.2.1. + Gs-NULL --> Gs-ASSOCIATED : Periodic routing area update request received from the MS with conditions listed in subclause 6.2.1. + Gs-ASSOCIATED --> Gs-NULL : Send BSSAP+-MS-UNREACHABLE message + Gs-ASSOCIATED --> Gs-NULL : Send TMSI Reallocation + Gs-ASSOCIATED --> Gs-NULL : Set VLR_reliable=true (whether SGSN_reset=true or not) + Gs-ASSOCIATED --> Gs-NULL : (Any other cases) Combined routing area or periodic routing area update request received from the MS + Gs-ASSOCIATED --> Gs-NULL : Paging received + LA-UPDATE Requested --> Gs-NULL : Paging received + +``` + +The diagram illustrates the state transitions at the SGSN. It starts with an initial state leading to Gs-NULL. From Gs-NULL, transitions occur to LA-UPDATE Requested (via 'Send Location Area Update Request (to the VLR)') and to Gs-ASSOCIATED (via 'Normal Routing Area Update Request Received from the MS', 'Combined routing area update request received from the MS with conditions listed in subclause 6.2.1.', or 'Periodic routing area update request received from the MS with conditions listed in subclause 6.2.1.'). Transitions back to Gs-NULL occur from LA-UPDATE Requested (via 'Location Area Update Reject received' or 'Paging received') and from Gs-ASSOCIATED (via 'Send BSSAP+-MS-UNREACHABLE message', 'Send TMSI Reallocation', 'Set VLR\_reliable=true (whether SGSN\_reset=true or not)', '(Any other cases) Combined routing area or periodic routing area update request received from the MS', or 'Paging received'). Self-loops on Gs-NULL and LA-UPDATE Requested handle 'Paging received'. A 'SGSN failure' self-loop exists on Gs-NULL. A 'Send any detach indication (to the VLR)' self-loop also exists on Gs-NULL. + +State diagram at the SGSN showing transitions between Gs-NULL, LA-UPDATE Requested, and Gs-ASSOCIATED states. + +Figure 4.2/3GPP TS 29.018: State diagram at the SGSN + +# 5 Paging for non-GPRS services procedure + +## 5.1 General description + +This procedure is used by the VLR to send a BSSAP+-PAGING-REQUEST message to an MS via the GPRS service. This procedure applies to MSs that are simultaneously IMSI attached for GPRS services and non-GPRS services. The procedure can be performed simultaneously with any other procedure at the Gs interface. + +## 5.2 Procedures in the VLR + +The VLR shall handle the timers, queuing and retransmission for sending the BSSAP+-PAGING-REQUEST message on the Gs interface in the same way that it handles the sending of a PAGING message on the A or Iu-CS interface. + +### 5.2.1 Paging Initiation + +When a VLR has to page a GPRS MS it shall check whether the MSC has an SCCP connection for that MS. If no SCCP connection exists the VLR checks the state of the association to an SGSN and the value of the restoration indicators for that MS. The VLR sends BSSAP+-PAGING-REQUEST messages to the SGSN if the state of the association for the MS is Gs-ASSOCIATED, LA-UPDATE-PRESENT or if the state of the association is Gs-NULL and the 'Confirmed by Radio Contact' restoration indicator is set to 'false'. The sending of the BSSAP+-PAGING-REQUEST message does not change the state of the association with the SGSN. + +If the 'Confirmed by Radio Contact' restoration indicator is set to 'true', the VLR shall include the Location area identifier IE into the BSSAP+-PAGING-REQUEST message, otherwise (i.e. after a VLR failure) the Location area identifier IE shall not be included. When sending the BSSAP+-PAGING-REQUEST message, the VLR shall start timer T5. + +If the state of the association is Gs-NULL and the restoration indicator 'Confirmed by Radio Contact' is set to 'false', the VLR shall also perform a search procedure as specified in 3GPP TS 23.018 [6a]. + +While domain specific access control of the PS domain is ongoing the VLR shall be configured to send paging messages on the Gs, A and Iu-CS interfaces. The VLR may apply implementation specific rules for sending the paging on the A and Iu-CS interfaces; e.g. paging on the A and Iu-CS interfaces may be limited to cases when the GPRS MS did not respond to a first paging on Gs interface. + +### 5.2.2 Paging Response + +The VLR stops the paging procedure on expiry of timer T5 or on receipt of an SCCP connection establishment containing the Initial L3 message from the MS via the A or Iu-CS interface. + +If the paging response is received from a location area which differs from the one stored in the VLR, the VLR shall move the Gs association to the Gs-NULL state after the MS has been authenticated successfully. + +### 5.2.3 Paging Failure + +On receipt of a BSSAP+-PAGING-REJECT message before the timer T5 expires, the VLR stops timer T5, the association is moved to the Gs-NULL state and within this state the association is marked with the contents of the Gs Cause IE. + +### 5.2.4 MS unreachable + +On receipt of a BSSAP+-MS-UNREACHABLE message before the timer T5 expires, the VLR stops timer T5 and the paging procedure for that paging request towards the SGSN is stopped. The state of the association at the VLR is not changed. + +## 5.3 Procedures in the SGSN + +The SGSN accepts BSSAP+-PAGING-REQUEST messages in any state of the association apart from Gs-NULL. Nevertheless the SGSN also accepts BSSAP+-PAGING-REQUEST messages in the Gs-NULL state if the 'SGSN-Reset' restoration indicator at the SGSN is set to 'true'. When an SGSN receives a BSSAP+-PAGING-REQUEST message from a VLR, the SGSN shall first check if the MS is known by the SGSN. The handling of the paging request depends on the state of the association and the MM context variables at the SGSN: + +- a) The MS is known and the restoration indicator 'SGSN-Reset' at the SGSN is set to 'false': + - If the MS is considered to be IMSI attached for GPRS and non-GPRS services (i.e. the association is not in the state Gs-NULL), the SGSN shall page the MS based on the location information stored in the SGSN. If the location area stored in the SGSN differs from the one received in the BSSAP+-PAGING-REQUEST message, the SGSN shall use the IMSI to page the MS. If the BSSAP+-PAGING-REQUEST message does not include the Location area identifier information element, the SGSN may set the "VLR-Reliable" MM context variable to "false". + - If the MS is marked as IMSI detached for GPRS services or IMSI (implicitly or explicitly) detached for non-GPRS services (i.e. the state of the association is Gs-NULL), the SGSN shall return a BSSAP+-PAGING-REJECT message to that VLR indicating in the Gs Cause IE the detach circumstance ('IMSI detached for + +GPRS services', 'IMSI detached for non-GPRS services' or 'IMSI implicitly detached for non-GPRS services'). + +- If the MS is marked as unreachable (i.e. the PPF flag is set to 'false') the SGSN shall return a BSSAP+-MS-UNREACHABLE message to that VLR indicating in the Gs Cause IE 'MS unreachable'. The state of the association does not change at the SGSN. +- b) The MS is known and the restoration indicator 'SGSN-Reset' at the SGSN is set to 'true': +- If the BSSAP+-PAGING-REQUEST message includes the Location area identifier IE, the SGSN shall page the MS in all the routeing areas served by the SGSN that are included in the location area indicated in the Location area identifier IE. + - If the BSSAP+-PAGING-REQUEST message does not include the Location area identifier IE, the SGSN may page in all the routeing areas served by the SGSN that are also served by the sending VLR. +- NOTE 1: The SGSN can handle the paging request as a) for the purpose of optimization if the MS is known. +- c) The MS is not known and the restoration indicator 'SGSN-Reset' at the SGSN is set to 'false': +- The SGSN shall return a BSSAP+-PAGING-REJECT message to that VLR indicating in the Gs Cause IE 'IMSI unknown'. +- d) The MS is not known and the restoration indicator 'SGSN-Reset' at the SGSN is set to 'true': +- If the VLR provides the Location area identifier IE, the SGSN shall page within the location area indicated by the VLR. Otherwise the SGSN may page in all the routeing areas served by the SGSN that are also served by the sending VLR. + +If the SGSN accepts the paging request, the SGSN shall process the BSSAP+-PAGING-REQUEST message before sending the message on the Gb interface. The result of the processing on the BSSAP+-PAGING-REQUEST message is the PAGING CS message (see 3GPP TS 48.018 [15]) sent on the Gb interface. + +The SGSN shall not retransmit the PAGING CS message. + +If within a location area there are cells that do not support GPRS services, the SGSN shall group these cells under a 'null RA'. The SGSN will perform the paging procedure described above within both the RA(s) derived from the location information and the 'null RA(s)' of the corresponding location area(s) (see 3GPP TS 24.008 [11]). + +NOTE 2: The eMLPP priority information element relates to relative priorities within the paged MS and not to the priority in the sending of PAGING CS messages by the BSS. + +# --- 6 Location Update for non-GPRS services procedure + +## 6.1 General description + +The location update for non-GPRS services procedure is a general procedure used by MSs in class-A mode of operation and MSs in class-B mode of operation. This procedure is not performed if: + +- the subscriber data indicates that the MS has subscription for packet only; +- the MS indicates SMS only and the HLR indicates "SMS in SGSN Support" and the SGSN supports SMS services. + +NOTE: For the cases specified above, the registration with a VLR is not required and the SGSN does not initiate the location update for non-GPRS services procedure. + +This procedure allows MSs and network to perform: + +- Combined IMSI attach for GPRS and non-GPRS services; +- IMSI attach for non-GPRS services if the MS is already IMSI attached for GPRS services; +- IMSI attach for GPRS services indication to the VLR if the MS is already IMSI attached for non-GPRS services; + +- Normal Location Update procedure to the VLR if the MS is IMSI attached for both GPRS and non-GPRS services; +- Reallocation of TMSI to an MS. + +The Location Update for non-GPRS services procedures in the Gs interface is always started as a consequence of a direct action by the MS. The combined routing area update procedure is further specified in 3GPP TS 23.060 [8] and 3GPP TS 24.008 [11]. + +The Location Update for non-GPRS services procedure is used by the SGSN to forward to the VLR those parts of the combined routing area update or IMSI attach procedure which belong to the non-GPRS services. This means that non-GPRS related requests which are included in the combined request, are sent from the SGSN to the VLR. The procedure is also used by the SGSN to indicate to the VLR when an IMSI attach to GPRS services has been performed by an MS that was already IMSI attached to non-GPRS services. The SGSN may also forward a BSSAP+-TMSI-REALLOCATION-COMPLETE message from the MS to the VLR. + +The VLR shall acknowledge the BSSAP+-LOCATION-UPDATE-REQUEST message. When the VLR processes the request it does not perform authentication because it relies on the SGSN's security functions. + +When an MS is IMSI attached for GPRS and non-GPRS services, any implicit detach timer in the VLR shall be stopped. Instead the Paging Proceed Flag in the SGSN is used to determine the likely availability of the MS to the network. Upon reception of the periodic Routeing Area Update message the SGSN does not report to the VLR, and the state of the association at the SGSN is not changed. When the MS performs a detach only from the GPRS system, and the VLR's implicit detach timer is not already running, the GPRS detach indication to the VLR shall cause the VLR's implicit detach timer to be restarted from its initial value. + +If the SGSN performs an implicit detach for both GPRS and non-GPRS traffic, then the SGSN shall indicate to the VLR a BSSAP+-IMSI-DETACH-INDICATION message with cause 'Implicit SGSN initiated IMSI detach from GPRS and non-GPRS service', as further described in clause 'Implicit IMSI detach from non-GPRS service procedure' (the implicit IMSI detach message indicates that the MS is unavailable for both GPRS and non-GPRS services). + +The IMSI attach for GPRS services to the VLR, when the MS is already IMSI attached for non-GPRS services, is requested by the MS sending a combined IMSI attach for GPRS and non-GPRS services message to the SGSN, as further specified in 3GPP TS 23.060 [8] and 3GPP TS 24.008 [11]. + +## 6.2 Procedures in the SGSN + +The location update for non-GPRS services is initiated with a combined routing area update procedure or a IMSI/GPRS attach procedure. On receipt of an ATTACH REQUEST message or ROUTING AREA UPDATE REQUEST message from the MS, the SGSN shall handle the GPRS related request as specified in 3GPP TS 24.008 [11]. + +When the SGSN receives the MAP-INSERT-SUBSCRIBER-DATA message containing subscription data from the HLR, the SGSN determines whether it needs to perform location update for non-GPRS services procedure. For the cases identified below, the SGSN sends response message to the MS without starting the location update for non-GPRS services procedure: + +- if the Network Access Mode (NAM) subscription data indicates that the MS has subscription for packet only (see 3GPP TS 29.272 [28]); or +- if the combined attach or routing area update procedure indicates that the MS has requested for GPRS services and "SMS-only service" (see 3GPP TS 24.008 [11]) and the HLR indicates "SMS in SGSN Support" and the SGSN supports SMS services. + +Otherwise, the SGSN shall start the location update for non-GPRS services procedure and wait for the outcome of both location update procedures towards the VLR and the HLR before sending the response message to the MS (see 3GPP TS 24.008 [11]). + +Upon reception of the periodic Routeing Area Update message, if the EMM Combined UE Waiting Flag is 'true', the SGSN shall perform network-initiated GPRS detach procedure with the detach type IE indicating "IMSI detach" as specified in 3GPP TS 24.008 [11]. + +### 6.2.1 Location Update Initiation + +If timer T6-1 is not running, the SGSN shall start the Location Update for non-GPRS service procedure when it receives from the MS: + +- an Attach request indicating combined IMSI and GPRS attach; +- an Attach request indicating GPRS attach while IMSI attached; +- a Combined Routeing and Location Area Update request indicating IMSI attach; +- a Combined Routeing and Location Area Update request indicating that the Location Area has changed; +- a Combined Routeing and Location Area Update request if the MS Network Capability IE indicates that EMM Combined procedures are supported by the MS; +- a Combined Routeing and Location Area Update request, if the state of the association is Gs-NULL; or +- a Combined Routeing and Location Area Update request when the SGSN serving the MS has changed. + +If timer T6-1 is not running, the SGSN may start the Location Update for non-GPRS service procedure when it receives from the MS: + +- a Combined Routeing and Location Area Update request or a periodic Routeing Area Update, if the 'VLR-Reliable' MM context variable for the MS is set to 'false' (see section 11.3). + +For networks not supporting the feature 'Intra Domain Connection of RAN Nodes to Multiple CN Nodes' the number of the VLR is derived from the RAI where the MS is camping. For networks supporting the feature 'Intra Domain Connection of RAN Nodes to Multiple CN Nodes', the VLR number is derived as described in 3GPP TS 23.236 [26]. The SGSN starts Timer T6-1. The BSSAP+-LOCATION-UPDATE-REQUEST message includes the Old location area identifier. If the SGSN received the Old location area identification from the MS and the network supports S1 mode, the SGSN includes the Old location area identification received from the MS as the Old location area identifier. If the SGSN did not receive the Old location area identification from the MS or if the network does not support S1 mode, the SGSN derives the Old location area identifier from the Old routing area identification received in the ROUTING AREA UPDATING REQUEST message (see 3GPP TS 24.008 [11]). The SGSN shall also include the new Location Area Identifier where the MS is currently camping. The new LAI is derived from the RAI. + +If the VLR is configured for gateway core network (GWCN), the SGSN shall select a core network operator as specified in 3GPP TS 23.251 [24] and proceed as follows: + +- For supporting UEs, the SGSN includes the PLMN identity of the selected core network operator in the New cell global identity information element. +- For non-supporting UEs, the SGSN includes the selected core network operator in the Selected CN operator information element in the BSSAP+-LOCATION-UPDATE-REQUEST message, and the common PLMN in the New cell global identity information element. + +In networks supporting the feature 'Intra Domain Connection of RAN Nodes to Multiple CN Nodes' (3GPP TS 23.236 [26]), if the TMSI based NRI container is not received from the MS, and the SGSN determines that the serving VLR of the MS is changed, the SGSN shall include in the Old location area identifier a specific LAI value which is not broadcasted in the network and not associated with any VLR. + +NOTE 1: The SGSN determines that the serving VLR of the MS is changed when the Gs association changes from one serving VLR to a different one, or based on implementation dependent criteria. + +NOTE 2: When the VLR receives the BSSAP+-LOCATION-UPDATE-REQUEST message with the specific LAI value, the VLR retrieves the MM context of the MS from the HLR. + +In networks supporting the feature 'Intra Domain Connection of RAN Nodes to Multiple CN Nodes', the SGSN shall support load re-distribution of MSs to another VLR than the current one as follows: + +When the SGSN receives a periodic Routeing Area Update request or a Combined Routeing and Location Area Update request, the SGSN shall check whether for this MS there is an association to a VLR for which load re-distribution has been initiated in the SGSN by O&M. If yes, the SGSN derives the new VLR number as + +described in 3GPP TS 23.236 [26]. The SGSN shall then send the BSSAP+-LOCATION-UPDATE-REQUEST message to the new selected VLR. + +The BSSAP+-LOCATION-UPDATE-REQUEST message includes the type of location update performed by the MS in the GPRS location update type IE. If the MS has performed a combined attach request or a combined routing and location area update request with IMSI attach, the SGSN indicates 'IMSI attach', otherwise the SGSN indicates 'Normal location update'. + +The BSSAP+-LOCATION-UPDATE-REQUEST message shall include the TMSI status if received from the MS. + +The SGSN shall include the TMSI based NRI container in the BSSAP+-LOCATION-UPDATE-REQUEST message if received from the MS. + +If the SGSN supports the "Provision of UE Specific Behaviour Information to Network Entities" (see 3GPP TS 23.195 [23]), or the "Automatic Device Detection" (see 3GPP TS 22.101 [23A]) or the "Trace for Management Based Activation/Deactivation" (see 3GPP TS 32.422 [25]), the BSSAP+-LOCATION-UPDATE-REQUEST message shall include the IMEISV. + +If timer T6-1 is running: + +If the SGSN receives from the MS: + +- an Attach request indicating combined IMSI and GPRS attach; +- an Attach request indicating GPRS attach while IMSI attached; or +- a Combined Routeing and Location Area Update request with or without IMSI attach. + +Then: + +- if the new LAI is the same as in the outstanding request, the SGSN shall not process this new request and shall wait for the VLR's response to the ongoing procedure; or +- if the new LAI is different but is in the same VLR as the outstanding request: + - any response from the VLR to the outstanding request is ignored; + - Timer T6-1 shall be stopped and reset; and + - The SGSN shall start the Location Update for non-GPRS service procedure; or +- if the new LAI is different, and is in a different VLR to the outstanding request: + - any response from the previously addressed VLR to the outstanding request is ignored; + - Timer T6-1 shall be stopped and reset; and + - the SGSN shall start the Location Update for non-GPRS service procedure. + +When the SGSN receives from the MS a Routeing Area Update request and the SGSN serving the MS has changed, the SGSN shall stop and reset timer T6-1. + +### 6.2.2 Location Update Response + +If the SGSN receives a BSSAP+-LOCATION-UPDATE-ACCEPT message from the VLR, the SGSN shall: + +stop timer T6-1; and + +- move the state of the association to Gs-ASSOCIATED; +- set the the MM context variable 'VLR-Reliable' to 'true'; +- set the the MM context variable 'EMM Combined UE Waiting Flag' to 'false'; and +- indicate to the MS the acceptance of the VLR to the Location Update procedure. The message to the MS includes the Routeing Area Identity, from which the MS is able to extract the location area identity for which the location update procedure succeeded (see 3GPP TS 24.008 [11]). + +The SGSN shall wait for the outcome of the Location Update for non-GPRS service procedure towards the VLR before sending a response to location update procedure to the MS. Any Reject cause that needs to be reported to the MS is specified in 3GPP TS 24.008 [11]. + +If the VLR included the Mobile Identity IE in the BSSAP+-LOCATION-UPDATE-ACCEPT message, the SGSN shall forward the information received to the MS. If the Mobile Identity IE contains a new TMSI it will cause the MS to perform a TMSI reallocation procedure, while an IMSI causes the MS to deallocate its TMSI. In case a new TMSI was allocated for the MS the SGSN shall send to the VLR the BSSAP+-TMSI-REALLOCATION-COMPLETE message when the SGSN receives Attach Complete or the the Routeing Area Complete message from the MS. + +### 6.2.3 Location Update Failure + +If the SGSN receives a BSSAP+-LOCATION-UPDATE-REJECT message from the VLR, the SGSN shall: + +- stop timer T6-1; +- move the state of the association to Gs-NULL; and +- indicate to the MS the rejection of the VLR of the Location Update procedure as specified in 3GPP TS 24.008 [11]. The Reject cause value sent by the VLR shall be forwarded to the MS. + +### 6.2.4 Abnormal cases + +If timer T6-1 expires, the SGSN shall abort the Location Update for non-GPRS service procedure and indicate this to the MS with the Reject cause value 'MSC temporarily not reachable'. The state of the association to the VLR shall be Gs-NULL. + +If the SGSN receives a BSSAP+-LOCATION-UPDATE-ACCEPT message and timer T6-1 is not running then: + +- if timer T8 is running (see clause 8), the message shall be ignored; +- if timer T9 is running (see clause 9), the message shall be ignored; or +- if timers T8 and T9 are not running: + - if the state of the association to the VLR is GS-ASSOCIATED, the message shall be ignored; or + - if the state of the association to the VLR is different than GS-ASSOCIATED, the message shall be treated as a message incompatible with the protocol state of the SGSN (see clause 16.3). + +## 6.3 Procedures in the VLR + +When a VLR receives a BSSAP+-LOCATION-UPDATE-REQUEST message it checks whether the IMSI is known. If the IMSI is not known the VLR retrieves the MM context of the MS from the HLR. + +In networks supporting the feature 'Intra Domain Connection of RAN Nodes to Multiple CN Nodes' (3GPP TS 23.236 [26]), if the TMSI based NRI container is received in the BSSAP+-LOCATION-UPDATE-REQUEST message, the VLR derives the NRI value. If the NRI value is not allocated by the VLR, the VLR retrieves the MM context of the UE from the HSS. + +When the VLR is configured for gateway core network (GWCN), the VLR shall select the serving core network operator as follows: + +- If the Selected CN operator information element is received in the BSSAP+-LOCATION-UPDATE-REQUEST message, the VLR shall select the serving core network operator as specified in the Selected CN operator information element; +- If the Selected CN operator information element is not received in the BSSAP+-LOCATION-UPDATE-REQUEST message and the PLMN identity included in the New cell global identity information element identifies a core network operator, the VLR shall select the serving core network operator as specified in the New cell global identity information element; +- Otherwise, the VLR selects the serving core network operator based on local policies. + +For a VLR supporting the "Provision of UE Specific Behaviour Information to Network Entities" (see 3GPP TS 23.195 [23]) the following applies: + +- The VLR shall store the IMEISV value received in the BSSAP+-LOCATION-UPDATE-REQUEST message in the MM context for that MS. +- If the VLR receives a BSSAP+-LOCATION-UPDATE-REQUEST message without IMEISV information element, the MSC/VLR shall request the IMEISV from the MS at the next Iu-CS or A interface connection establishment. + +### 6.3.1 Location Update Response + +If the Location Update is accepted by the VLR and, if necessary by the HLR, the VLR shall: + +- move the association to the Gs-ASSOCIATED state; +- set the restoration indicator 'Confirmed by Radio Contact' to 'true'; +- update the association by storing the SGSN number included in the BSSAP+-LOCATION-UPDATE-REQUEST message; and +- send a BSSAP+-LOCATION-UPDATE-ACCEPT message to the sending SGSN. This message includes the Location Area Identification received in the new Cell Global Identity IE in the previous BSSAP+-LOCATION-UPDATE-REQUEST message. + +### 6.3.2 Location Update Failure + +If the Location Update is rejected by the VLR it shall: + +- Send a BSSAP+-LOCATION-UPDATE-REJECT message to the SGSN with the appropriate reject cause as indicated in 3GPP TS 24.008 [11] and indicate to the SGSN the Location area identifier received in the corresponding BSSAP+-LOCATION-UPDATE-REQUEST message; and +- Move the association from any state to Gs-NULL. + +### 6.3.3 TMSI reallocation procedure + +If the VLR decides to reallocate the TMSI to the MS it shall include the new TMSI in the BSSAP+-LOCATION-UPDATE-ACCEPT message. If the VLR decides to deallocate the TMSI of the MS it shall include the IMSI of the MS in the BSSAP+-LOCATION-UPDATE-ACCEPT message. After sending the BSSAP+-LOCATION-UPDATE-ACCEPT message with a new TMSI the VLR starts timer T6-2. + +NOTE: In the BSSAP+-LOCATION-UPDATE-REQUEST the SGSN may indicate, that there is no valid TMSI available in the MS. This information may be used by the VLR to decide whether to reallocate a new TMSI to the MS. + +Upon receipt of the BSSAP+-TMSI-REALLOCATION-COMPLETE message, the VLR stops the timer T6-2 and considers the new TMSI as valid. + +If an IMSI was sent to the MS, the VLR considers the old TMSI as deleted. + +If no BSSAP+-TMSI-REALLOCATION-COMPLETE message is received by the VLR before the timer T6-2 expires, the VLR aborts the TMSI reallocation procedure. The VLR shall consider old TMSI occupied until the new TMSI is used in a subsequent A/Iu message, or for an implementation dependent time. The VLR may still perform the TMSI reallocation procedure via the A or Iu-CS interface. The outcome of the TMSI reallocation procedure does not change the state of the association. The VLR uses the IMSI or the new TMSI or, if available, the old TMSI for paging. + +### 6.3.4 Abnormal cases + +The following abnormal cases can be identified: + +- i) MM signalling via the A or Iu-CS interface + +If the VLR receives a Location Update request or an IMSI detach indication from the MS by the A or Iu-CS interface when the state of the association in the VLR is not Gs-NULL, the VLR shall move the state of the association to Gs-NULL. + +#### ii) Additional Location Update Request + +If the state of the association in the VLR is in the LA-UPDATE PRESENT state and a BSSAP+-LOCATION-UPDATE-REQUEST message is received, then: + +- If the message is from the same SGSN and indicates the same New Location Area as the outstanding location update request, then this additional BSSAP+-LOCATION-UPDATE-REQUEST message shall be ignored; +- If the message is from the same SGSN but indicates a different New Location Area to the outstanding location update request, then this additional BSSAP+-LOCATION-UPDATE-REQUEST message shall be treated and the VLR shall not send any response to the previous BSSAP+-LOCATION-UPDATE-REQUEST message; or +- If the message is from a different SGSN (indicating either the same or different New Location Area) to the outstanding location update request, then this additional BSSAP+-LOCATION-UPDATE-REQUEST message shall be treated and the VLR shall not send any response to the previous BSSAP+-LOCATION-UPDATE-REQUEST message. + +#### iii) Detach signalling from SGSN + +If the state of the association in the VLR is in the LA-UPDATE PRESENT state and either a BSSAP+-GPRS-DETACH-INDICATION or a BSSAP+-IMSI-DETACH-INDICATION message is received, then, the Location Update for non-GPRS services procedure shall be abandoned in the VLR (neither a BSSAP+-LOCATION-UPDATE-ACCEPT nor a BSSAP+-LOCATION-UPDATE-REJECT messages is sent) and the further actions described in clauses 8 or 9 or 10 are followed. + +#### iv) Signalling via SGs interface + +If the VLR receives for a UE a SGsAP+-LOCATION-UPDATE-REQUEST message (as defined in 3GPP TS 29.118 [27]) from an MME when the state of the association for this UE in the VLR is not Gs-NULL, the VLR shall move the state of the association to Gs-NULL. + +#### v) New Location Update Request during TMSI reallocation procedure + +If the VLR receives a BSSAP+-LOCATION-UPDATE-REQUEST message while T6-2 is running, the VLR shall stop timer T6-2, abort the TMSI reallocation procedure and proceed with the new location update for non-GPRS services procedure. If the VLR needs to page the MS during the new location update for non-GPRS services procedure, the VLR uses the IMSI or the new TMSI from the aborted TMSI reallocation procedure or, if available, the old TMSI for paging. + +#### vi) Reset signalling from SGSN + +If the state of the association in the VLR is in the LA-UPDATE PRESENT state and a BSSAP+-RESET-INDICATION message is received from the SGSN, then, the Location Update for non-GPRS services procedure shall be abandoned in the VLR (neither a BSSAP+-LOCATION-UPDATE-ACCEPT nor a BSSAP+-LOCATION-UPDATE-REJECT messages is sent) and the further actions described in clause 12 are followed. + +# --- 7 Non-GPRS alert procedure + +## 7.1 General description + +This procedure is used by the VLR to request from an SGSN an indication when activity (either signalling or data transmission) from an MS is detected. This procedure can be invoked at any time by the VLR. The BSSAP+-ALERT-REQUEST message shall be acknowledged by the SGSN. + +## 7.2 Procedures in the VLR + +### 7.2.1 Alert Initiation + +The VLR may start the Non-GPRS alert procedure at any time. When the VLR wants to request to an SGSN that further activity from an MS shall be reported by the SGSN, the VLR shall send an BSSAP+-ALERT-REQUEST message to that SGSN. The VLR starts timer T7 when the BSSAP+-ALERT-REQUEST message is sent. + +### 7.2.2 Alert Response + +When a BSSAP+-ALERT-ACK message is received, the VLR shall stop the timer T7. The state of the association is not changed. + +### 7.2.3 Alert failure + +If a BSSAP+-ALERT-REJECT message is received, the VLR shall stop the timer T7, move the state of the association to Gs-NULL and within this state the association is marked with the contents of the Gs Cause IE. + +### 7.2.4 Alert Indication + +The VLR shall not change the state of the association upon reception of an BSSAP+-MS-ACTIVITY-INDICATION message. + +### 7.2.5 Abnormal cases + +If no BSSAP+-ALERT-ACK message is received before the timer T7 expires, the VLR shall retransmit the BSSAP+-ALERT-REQUEST message a maximum of N7 times. If no BSSAP+-ALERT-ACK message is received after that, a report shall be made to the O&M system. The state of the association is not changed. + +## 7.3 Procedures in the SGSN + +### 7.3.1 Alert response + +The SGSN may receive a BSSAP+-ALERT-REQUEST message at any state of the association. Upon receipt of an BSSAP+-ALERT-REQUEST message from the VLR and if the IMSI is known in the SGSN, the SGSN shall reply with a BSSAP+-ALERT-ACK message and set the NGAF. + +### 7.3.2 Alert failure + +If a BSSAP+-ALERT-REQUEST message is received for an IMSI that is unknown at the SGSN, the SGSN shall return a BSSAP+-ALERT-REJECT message to the VLR indicating the Gs Cause IE value 'IMSI unknown'. + +### 7.3.3 Alert indication + +The SGSN shall report to the VLR upon detection of any activity (either signalling or data) from the MS if the NGAF is set. If the SGSN detects GPRS signalling that leads to a procedure towards the VLR, the SGSN shall follow this procedure and reset the NGAF. If the SGSN detects activity that does not lead to any procedure towards the VLR, the SGSN shall send an BSSAP+-MS-ACTIVITY-INDICATION message towards the VLR and reset the NGAF. + +# 8 Explicit IMSI detach from GPRS services procedure + +## 8.1 General description + +This procedure is used by the SGSN to indicate to the VLR that the MS has been IMSI detached from GPRS service and therefore the association between the SGSN and the VLR has to be deactivated. This procedure only applies to MSs that are not in the Gs-NULL state at the SGSN. The procedures specified in this clause apply to GPRS detach indication initiated by the MS or by the network as specified in 3GPP TS 23.060 [8]. + +The procedure is also used by the SGSN to indicate to the VLR when a combined Routing and Location Area Update procedure has been rejected by the SGSN. + +The procedure is also used by the SGSN to indicate to the VLR when a periodic Routing Area Update procedure has been rejected by the SGSN for an MS for which a Gs association exists. + +The Explicit IMSI detach from GPRS services procedure aborts any other ongoing procedure related to this MS on the Gs interface in the SGSN and in the VLR. + +The VLR and the MS should be synchronised as to whether the PBCCH or the BCCH is used, for any of the subsequent paging. In order to achieve this, the SGSN shall attempt to inform the VLR about the detach event by using a retry scheme if the initial delivery of the BSSAP+-GPRS-DETACH-INDICATION message fails. + +## 8.2 Procedures in the SGSN + +### 8.2.1 Explicit GPRS detach initiation + +The SGSN shall send a BSSAP+-GPRS-DETACH-INDICATION message to a VLR if: + +- The SGSN receives a GPRS only detach from the MS; +- The SGSN performs network-initiated GPRS detach procedure; +- The combined Routing and Location Area Update procedure is rejected at the SGSN; or +- The periodic Routing Area Update procedure is rejected at the SGSN for an MS for which a Gs association exists. + +If the SGSN receives a Detach Request from an MS and the state of the association to a VLR for that MS is not Gs-NULL, the SGSN shall check the detach type indicated in the message. If the MS is indicating GPRS detach the SGSN shall send a BSSAP+-GPRS-DETACH-INDICATION message to the VLR indicating 'MS initiated IMSI detach from GPRS service'. + +If the SGSN decides to perform a network-initiated GPRS detach and the state of the association to a VLR for that MS is not Gs-NULL, the SGSN shall send a BSSAP+-GPRS-DETACH-INDICATION message to the VLR indicating 'Network initiated IMSI detach from GPRS service'. + +If the combined Routing and Location Area Update procedure or periodic Routing Area Update procedure is rejected at the SGSN for an MS with an association state different from Gs-NULL, the SGSN shall send a BSSAP+-GPRS-DETACH-INDICATION to the VLR indicating 'GPRS services not allowed'. The SGSN then sends, for example, a Routing Area Update Reject message as specified in 3GPP TS 24.008 [11]. + +After the sending of the BSSAP+-GPRS-DETACH-INDICATION message, the SGSN shall move the state of the association to Gs-NULL. The SGSN shall start timer T8 upon transmission of the BSSAP+-GPRS-DETACH-INDICATION message and if timer T6-1 is running, timer T6-1 shall be stopped and reset. + +### 8.2.2 Explicit GPRS detach Response + +If the SGSN receives a BSSAP+-GPRS-DETACH-ACK message from the VLR, the SGSN shall stop timer T8. The SGSN shall not wait for the reception of the BSSAP+-GPRS-DETACH-ACK message before sending (if needed) the confirmation of the detach to the MS. + +### 8.2.3 Abnormal cases + +If no BSSAP+-GPRS-DETACH-ACK message is received by the SGSN to a previous BSSAP+-GPRS-DETACH-INDICATION message before timer T8 expires, the SGSN shall repeat the BSSAP+-GPRS-DETACH-INDICATION message a maximum of N8 times. If no BSSAP+-GPRS-DETACH-ACK message is received after that, a report shall be made to the O&M system. The state of the association during the acknowledgement procedure remains Gs-NULL. + +## 8.3 Procedures in the VLR + +When a VLR receives a BSSAP+-GPRS-DETACH-INDICATION message, the VLR shall send a BSSAP+-GPRS-DETACH-ACK message to the sending SGSN. The state of the association for the MS shall be moved from any state to Gs-NULL. The VLR marks the association as 'IMSI detached for GPRS services' with the reason indicated in the IMSI detach from GPRS service type IE. + +If the VLR's implicit detach timer is not running then, the VLR shall set and restart the implicit detach timer upon reception of a BSSAP+-GPRS-DETACH-INDICATION message. If the VLR's implicit detach timer is running (ie the state of the association was already Gs-NULL) then, the reception of a BSSAP+-GPRS-DETACH-INDICATION message shall not affect the VLR's implicit detach timer. + +# --- 9 Explicit IMSI detach from non-GPRS services procedure + +## 9.1 General description + +This procedure is used by the SGSN to indicate to the VLR that the MS has performed IMSI detach from non-GPRS services and therefore the association between the SGSN and the VLR has to be deactivated. This procedure only applies to MSs that are not in the Gs-NULL state at the SGSN. The procedures specified in this clause only apply to IMSI detach or combined IMSI and GPRS detach requests. + +The explicit IMSI detach from non-GPRS services procedure aborts any other ongoing procedure related to this MS on the Gs interface in the SGSN and in the VLR. + +The VLR and the MS should be synchronised as to whether the PBCCH or the BCCH is used, for any of the subsequent paging. In order to achieve this, the SGSN shall attempt to inform the VLR about the detach event by using a retry scheme if the initial delivery of the BSSAP+-IMSI-DETACH-INDICATION message fails. + +## 9.2 Procedures in the SGSN + +### 9.2.1 Explicit IMSI detach initiation + +When an SGSN receives a Detach Request from an MS which is not in the Gs-NULL state, it shall check the detach type indicated. If the MS is indicating IMSI detach or combined IMSI and GPRS detach the SGSN shall send an BSSAP+-IMSI-DETACH-INDICATION message to the VLR indicating 'Explicit MS initiated IMSI detach from non-GPRS service' or 'Combined explicit MS initiated IMSI detach from GPRS and non-GPRS services'. + +After the sending of the BSSAP+-IMSI-DETACH-INDICATION message to the VLR, the SGSN shall move the state of the association to Gs-NULL. The SGSN shall start timer T9 upon transmission of the BSSAP+-IMSI-DETACH-INDICATION message and if timer T6-1 is running, timer T6-1 shall be stopped and reset.. + +### 9.2.2 Explicit IMSI detach Response + +If the SGSN receives a BSSAP+-IMSI-DETACH-ACK message from the VLR, the SGSN shall stop timer T9. If the detach type received from the MS indicated IMSI only detach or combined IMSI and GPRS detach not due to switch off, the SGSN shall wait for the reception of the BSSAP+-IMSI-DETACH-ACK message before sending the confirmation of the detach to the MS. + +### 9.2.3 Abnormal cases + +- i) with switch off + +If the SGSN sent a BSSAP+-IMSI-DETACH-INDICATION message for a combined IMSI and GPRS detach due to switch off and timer T9 expires, the SGSN shall repeat the BSSAP+-IMSI-DETACH-INDICATION message a maximum of N9 times. + +ii) with no switch off + +If the SGSN sent a BSSAP+-IMSI-DETACH-INDICATION message for a IMSI only detach or a combined IMSI and GPRS detach not due to switch off and timer T9 expires, the SGSN shall repeat the BSSAP+-IMSI-DETACH-INDICATION message a maximum of N9 times. If no BSSAP+-IMSI-DETACH-ACK is received after that the SGSN shall send the confirmation of the detach to the MS. + +## 9.3 Procedures in the VLR + +When a VLR receives an BSSAP+-IMSI-DETACH-INDICATION message, the VLR shall send an BSSAP+-IMSI-DETACH-ACK message to the sending SGSN. The state of the association for the MS shall be moved from any state to Gs-NULL. If the BSSAP+-IMSI-DETACH-INDICATION message indicated 'Explicit MS initiated IMSI detach from non-GPRS service', the VLR marks the association as 'IMSI detached for non-GPRS services'. If the BSSAP+-IMSI-DETACH-INDICATION message indicated 'Combined explicit MS initiated IMSI detach from GPRS and non-GPRS services', the VLR marks the association as 'IMSI detached for GPRS and non-GPRS services'. The VLR shall mark the MS as detached. + +# --- 10 Implicit IMSI detach from non-GPRS services procedure + +## 10.1 General description + +This procedure is used by the SGSN to indicate when an internal SGSN timer mechanism has caused the SGSN to delete the GMM context of an MS or mark its GMM context as detached. This procedure only applies to MSs that are not in the Gs-NULL state at the SGSN. + +The implicit IMSI detach from non-GPRS services procedure aborts any other ongoing procedure related to this MS on the Gs interface in the SGSN and in the VLR. + +The VLR and the MS should be synchronised as to whether the PBCCH or the BCCH is used, for any of the subsequent paging. In order to achieve this, the SGSN shall attempt to inform the VLR about the detach event by using a retry scheme if the initial delivery of the BSSAP+-IMSI-DETACH-INDICATION message fails. + +## 10.2 Procedures in the SGSN + +When the implicit IMSI detach from non-GPRS services procedure is started for an MS by the above mentioned internal SGSN timer mechanism, the SGSN shall send a BSSAP+-IMSI-DETACH-INDICATION message to the VLR indicating 'Implicit SGSN initiated IMSI detach from GPRS and non-GPRS service'. + +After the sending of the BSSAP+-IMSI-DETACH-INDICATION message, the SGSN shall move the state of the association to Gs-NULL. The SGSN shall start timer T10 upon transmission of the BSSAP+-IMSI-DETACH-INDICATION message. + +If the SGSN receives a BSSAP+-IMSI-DETACH-ACK message from the VLR, the SGSN shall stop timer T10. + +If no BSSAP+-IMSI-DETACH-ACK message is received by the SGSN to a previous BSSAP+-IMSI-DETACH-INDICATION message before timer T10 expires, the SGSN shall repeat the BSSAP+-IMSI-DETACH-INDICATION message a maximum of N10 times. The state of the association during the acknowledgement procedure remains Gs-NULL. + +## 10.3 Procedures in the VLR + +When a VLR receives the BSSAP+-IMSI-DETACH-INDICATION message, the VLR shall send an BSSAP+-IMSI-DETACH-ACK message to the sending SGSN. In addition, if the state of the Gs association is not Gs-NULL, the VLR proceeds as follows: + +- The VLR shall move the state of the association for the MS to Gs-NULL. If the VLR does not have a signalling connection for the MS, the VLR shall mark the MS as detached. Additionally, the VLR marks the association as 'IMSI implicitly detached for GPRS and non-GPRS services'. + +# --- 11 VLR failure procedure + +## 11.1 General description + +This procedure is used by the VLR to inform the associated SGSNs about the recovery from an internal failure that has affected the association with the SGSNs when the VLR fails with restart. + +The VLR recovery procedure shall be handled in such a way that the signalling load on the VLR and SGSN does not create any overload problem. + +This procedure is also used by the SGSNs with a Gs association to a failed VLR in the VLR pool to perform the restoration for CS services for the affected MSs when the VLR fails without restart or fails for a long duration. + +## 11.2 Procedures in the VLR + +### 11.2.1 VLR Reset Initiation + +In the event of a failure at the VLR which has resulted in the loss of SGSN association information on some MSs, the VLR shall move from any state to the Gs-NULL state for these MSs. The VLR shall also set the 'Confirmed by Radio Contact' restoration indicator to 'false' (see 3GPP TS 23.007 [6]) for affected MSs. The VLR shall not send any BSSAP+- MS-INFORMATION-REQUEST or BSSAP+-MM-INFORMATION-REQUEST messages to MSs with the SGSN association in the Gs-NULL state. + +When the VLR restarts a BSSAP+-RESET-INDICATION message shall be sent to all the SGSNs connected to the VLR by the Gs interface. This message indicates to the SGSN that for the MSs with an association to that VLR, the association is no longer reliable. The VLR shall also start timer T11. + +### 11.2.2 VLR Reset Response + +Upon receipt of a BSSAP+-RESET-ACK message, the VLR shall stop the timer T11. + +### 11.2.3 Abnormal cases + +If the VLR does not receive a BSSAP+-RESET-ACK message from that SGSN before the T11 timer expires, the VLR shall retransmit the BSSAP+-RESET-INDICATION message. The retransmission is repeated a maximum of N11 times. If no BSSAP+-RESET-ACK is received after that a report shall be made to the O&M system. + +## 11.3 Procedures in the SGSN + +### 11.3.1 VLR fails with restart + +Upon receipt of a BSSAP+-RESET-INDICATION message from the VLR, the SGSN is informed that all the associations with that VLR for all the MSs registered in the SGSN are no longer reliable because the VLR may have lost information about the state of the MSs and during the failure the VLR may have missed signalling messages. The SGSN shall set the 'VLR-Reliable' MM context variable to 'false'. The detach procedures for deleting the association are still applicable (clauses 8, 9 and 10). If the 'VLR-Reliable' MM context variable is set to 'false', upon reception of a combined routeing and location area update request or a periodic routeing area update request from the MS that is attached for non-GPRS service, the SGSN may request the MS to re-attach for non-GPRS services as specified in 3GPP TS 24.008 [11], or may alternatively immediately perform the location update for non-GPRS services procedure towards the VLR as described in clause 6. + +The SGSN sends a BSSAP+-RESET-ACK message to the VLR. + +### 11.3.2 VLR fails without restart + +If the SGSN detects that the VLR serving the MS is no longer in service and the SGSN supports restoration for CS services via an alternative VLR as defined in 3GPP TS 23.007 [6], upon reception of a combined routeing area update request or periodic routeing area update request from the MS that is attached to the VLR not in service, the SGSN may: + +- request the MS to re-attach for non-GPRS services as specified in 3GPP TS 24.008 [11] and then select an alternative VLR that is in service for the MS during the subsequent combined routeing area update procedure, before performing the location update for non-GPRS services procedure towards the selected VLR as described in clause 6; or +- select an alternative VLR that is in service for the MS and immediately perform the location update for non-GPRS services procedure towards the selected VLR as described in clause 6. + +NOTE: How an SGSN detects that a VLR is no longer in service is implementation dependent. + +# --- 12 SGSN failure procedure + +## 12.1 General description + +This procedure is used by the SGSN to inform the associated VLRs about the recovery from an internal failure that has affected the association with the VLRs. + +The SGSN recovery procedure shall be handled in such a way that the signalling load on the VLR and SGSN does not create any overload problem. + +## 12.2 Procedures in the SGSN + +### 12.2.1 SGSN Reset Initiation + +In the event of a failure at the SGSN which has resulted in the loss of VLR association information on some MSs, the SGSN shall move from any state to the Gs-NULL state for these affected MSs. The SGSN shall also set the 'SGSN-Reset' MM context variable to 'true' and start the timer T12-1. When the timer T12-1 expires the 'SGSN-Reset' MM context variable is set to 'false'. The value of the timer T12-1 shall be longer than the periodic routing area update timer at the SGSN. + +A BSSAP+-RESET-INDICATION message may be sent to all the VLRs connected to the SGSN by Gs interfaces. The BSSAP+-RESET-INDICATION message indicates to the VLR that all the associations with that particular SGSN for all the MSs registered in the VLR are no longer reliable. The normal procedures for updating the association are still applicable (clauses 6, 8, 9 and 10). The SGSN shall also start timer T12-2. + +If no BSSAP+-RESET-INDICATION is sent, the SGSN shall move from any state to the Gs-NULL state only the associations of the MSs affected by the loss of VLR association information. + +NOTE: The option to not send any BSSAP+-RESET-INDICATION message to all the VLRs connected to the SGSN by Gs interfaces reduces subsequent paging signalling initiated by VLRs by avoiding a complete search of the MS on the entire VLR area. + +### 12.2.2 SGSN Reset Response + +Upon receipt of a BSSAP+-RESET-ACK message, the SGSN shall stop the timer T12-2. + +### 12.2.3 Abnormal cases + +If the SGSN does not receive a BSSAP+-RESET-ACK message from that VLR before the T12-2 timer expires, the SGSN shall retransmit the BSSAP+-RESET-INDICATION message. The retransmission is repeated a maximum of N12 times. If no BSSAP+-RESET-ACK is received after a report shall be to made the O&M system. + +## 12.3 Procedures in the VLR + +Upon receipt of a BSSAP+-RESET-INDICATION message from the SGSN, the VLR is informed that all the associations with that SGSN for all the MSs registered in the SGSN are no longer reliable because the SGSN may have lost information about the state of the MSs for that VLR and during the failure the SGSN may have missed signalling messages. The VLR shall either: + +- set the 'Confirmed by Radio Contact' restoration indicator to 'false' in all the associations containing the restarted SGSN and set the state of all the Gs associations containing the restarted SGSN to the Gs-NULL state; or +- keep the 'Confirmed by Radio Contact' restoration indication and the state of all the Gs associations containing the restarted SGSN unchanged. + +NOTE: The option to not set the 'Confirmed by Radio Contact' restoration indicator to 'false' in all the associations containing the restarted SGSN reduces subsequent paging signalling the VLR can initiate by avoiding a complete search of the MS on the entire VLR area. + +The VLR shall then send a BSSAP+-RESET-ACK message to the SGSN. + +If the 'Confirmed by Radio Contact' restoration indicator is 'false' the VLR may send paging messages on the Gs, A and Iu-CS interfaces. + +# --- 13 HLR failure + +This clause describes the SGSN behaviour towards the VLR as a consequence of an HLR reset. + +## 13.1 General description + +In the case of an HLR failure, the HLR informs the associated SGSNs about the recovery from an internal failure that has affected the association with the SGSNs according to the HLR reset procedure specified in 3GPP TS 29.002 [17]. + +This information is used in the SGSN to trigger the VLR to perform a location update towards the HLR in order to restore the HLR subscriber data. + +## 13.2 Procedures in the SGSN + +Upon receipt of a HLR reset indication from the HLR, the SGSN shall set the NGAF for all registered MSs in the SGSN for which a valid MSC/VLR-association exists. + +Upon detection of any activity (either signalling or data) from the MS, the SGSN shall report to the VLR if the NGAF is set for this MS. If the SGSN detects GPRS signalling that leads to a procedure towards the VLR, the SGSN shall follow this procedure and reset the NGAF. If the SGSN detects activity that does not lead to any procedure towards the VLR, the SGSN shall send an BSSAP+-MS-ACTIVITY-INDICATION message towards the VLR and reset the NGAF. The activity indication may be delayed by the SGSN for a maximum operator-configuration depending time period to avoid high signalling load. + +# --- 14 MS Information procedure + +## 14.1 General description + +The MS Information procedure is used by the VLR to request specific parameters about the MS. If the target MS for an MS Information procedure or a Provide Subscriber Info procedure (see 3GPP TS 23.018 [6a] and 3GPP TS 29.002 [17]) is GPRS attached (i.e. the state of the association to Gs-ASSOCIATED) the VLR may decide to perform the procedure via GPRS. The outcome of the MS Information procedure does not change the state of the association at the VLR or SGSN. + +## 14.2 Procedures in the VLR + +If the target MS for the MS information procedure is GPRS attached and the state of the association for the MS Gs-ASSOCIATED, the VLR may initiate the MS information procedure by transferring a BSSAP+-MS-INFORMATION- + +REQUEST message to the SGSN. If the state of the association is LA-UPDATE PRESENT, the VLR shall wait until this state is exited. The VLR starts the timer T14. The BSSAP+-MS-INFORMATION-REQUEST message specifies the requested information parameters in the Information requested information element. + +Upon receipt of a BSSAP+-MS-INFORMATION-RESPONSE the VLR shall stop timer T14. If no BSSAP+-MS-INFORMATION-RESPONSE for that MS is received before the expiry of timer T14 the VLR shall stop the Gs interface MS information procedure. The VLR may perform other actions to obtain the information about the MS (e.g. retry, or send a DTAP IDENTITY REQUEST message on the A interface). + +## 14.3 Procedures in the SGSN + +The SGSN shall examine the type of information that is requested and if it is stored in its database shall use this information in its response to the VLR. The BSSAP+-MS-INFORMATION-RESPONSE message contains the information parameters as requested by the VLR. In A/Gb mode, the Mobile location information indicates a request for Cell Global Identity and Location information age. In Iu mode, the Mobile location information indicates a request for Service Area Identification and Location information age. In this case, the SGSN shall use the Location Report Control procedure (see 3GPP TS 25.413 [22]) in order to retrieve the SA. + +If the SGSN receives an Information requested information element containing a 'not supported' value, then the value part of the Mobile station state information element in the BSSAP+-MS-INFORMATION-RESPONSE message shall be set to 'Information requested not supported'. + +If the information is not locally available and it is a request for mobile identity information, the SGSN forwards the IDENTITY REQUEST message to the MS indicated in the message unless the GPRS activities of the MS are suspended. Upon receipt of the IDENTITY RESPONSE message from the MS, the SGSN shall send a BSSAP+-MS-INFORMATION-RESPONSE message. The BSSAP+-MS-INFORMATION-RESPONSE message contains the information parameters as requested by the VLR. If the GPRS activities of the MS are suspended the SGSN shall return a BSSAP+-MS-INFORMATION-RESPONSE message indicating in the Mobile station state IE 'SUSPENDED'. If the requested information is not available or obtainable at the SGSN, the SGSN shall return a BSSAP+-MS-INFORMATION-RESPONSE message to the VLR without the requested information. The SGSN should include the Mobile station state IE in all BSSAP+-MS-INFORMATION-RESPONSE messages. + +If the IMSI is not known at the SGSN, the SGSN shall return a BSSAP+-MS-INFORMATION-RESPONSE message indicating in the Mobile station state IE 'IMSI unknown'. + +# --- 15 MM information procedure + +## 15.1 General description + +The MM information procedure may be performed by the VLR via GPRS if the target MS for the MM information procedure is IMSI attached to both GPRS and non-GPRS services (i.e. the state of the association is Gs-ASSOCIATED). The outcome of the MM Information procedure does not change the state of the association at the VLR or SGSN. + +## 15.2 Procedures in the VLR + +If the target MS for the MM information procedure is GPRS attached class A or B MS, the state of the association is Gs-ASSOCIATED, the VLR may initiate the MM information procedure by transferring a BSSAP+-MM-INFORMATION-REQUEST message to the SGSN. + +## 15.3 Procedures in the SGSN + +If the state of the association at the SGSN is not Gs-NULL, and the network only spans one time zone, the SGSN shall keep the information elements in the MM information unchanged. + +NOTE: For the determination of the number of time zones, both CS and PS domain are taken into account. + +If the network spans more than one time zone, the SGSN shall check and update the contents of the MM information information element as follows: + +- if Network Daylight Saving Time has been included in the MM information, then the SGSN shall discard the Network Daylight Saving Time; +- if Local Time Zone has been included in the MM information, then the SGSN shall replace the Local Time Zone with the Local Time Zone applicable for this MS. In addition, if the local time zone in the SGSN has been adjusted for daylight saving time, the SGSN shall indicate this by including the value used for adjustment in Network Daylight Saving Time IE in the MM information; +- if Universal time and local time zone has been included in the MM information, then the SGSN shall replace it with the Universal time and local time zone applicable for this MS. In addition, if the local time zone in the SGSN has been adjusted for daylight saving time, the SGSN shall indicate this by including the value used for adjustment in Network Daylight Saving Time IE in the MM information; and +- other information elements in the MM information are kept unchanged. + +The SGSN shall then send the resultant MM-INFORMATION message to the MS indicated. + +# --- 16 Error Handling and Future Compatibility + +## 16.1 General + +This clause specifies procedures for the handling of unknown, unforeseen, and erroneous protocol data by the receiving entity. These procedures are called "error handling procedures", but in addition to providing recovery mechanisms for error situations they define a compatibility mechanism for future extensions of the protocol. + +In this clause the following terminology is used: + +- an IE is defined to be syntactically incorrect in a message if it contains at least one value defined as "reserved", or if its value part violates coding rules. However, it is not a syntactical error that an IE specifies in its Length Indicator a greater length than defined in the relevant clause; and +- a message is defined to have semantically incorrect contents if it contains information which, possibly dependant on the state of the receiver, is in contradiction to the resources of the receiver and/or to the procedural part of 3GPP TS 29.018. + +When a receiving entity detects the need to send a BSSAP+-MOBILE-STATUS message (see errors detailed below), the entity shall copy the IMSI IE value (if included) of the incorrect message to the IMSI IE on the BSSAP+-MOBILE-STATUS message. The message in error is also included in the BSSAP+-MOBILE-STATUS message. Both the receiving and the sending entity shall abandon the procedure related to the incorrect message and return to the state from where the procedure related to the incorrect message was started. + +A BSSAP+-MOBILE-STATUS message shall not be sent in response to a received BSSAP+-MOBILE-STATUS message. + +Both the receiving and the sending entity shall inform the O&M entity upon sending or receiving a BSSAP+-MOBILE-STATUS message. + +The next clauses in this clause shall be applied in order of precedence. + +## 16.2 Message too short + +When a message is received that is too short to contain a complete message type information element, that message shall be ignored. + +## 16.3 Unknown or unforeseen message type + +If a message is received with a message type not defined or not implemented by the receiver it shall ignore the message. A BSSAP+-MOBILE-STATUS message with the Gs Cause Value set to "message unknown" and the Erroneous message IE containing the received message shall be returned. + +If a message is received that is not compatible with the protocol state, a BSSAP+-MOBILE-STATUS message with the Gs Cause Value set to "message not compatible with the protocol state" and the erroneous message shall be returned. + +If a message is received that is not defined to be received by that entity (i.e. the message is sent in the wrong direction) it shall be treated as unknown message and the message shall be ignored. A BSSAP+-MOBILE-STATUS message with the Gs Cause Value set to "message unknown" and the Erroneous message IE containing the received message shall be returned. + +## 16.4 Missing mandatory information element + +When on receipt of a message, and a "missing mandatory IE" error is diagnosed, the receiver shall ignore the message and return a BSSAP+-MOBILE-STATUS message with the Gs Cause Value set to "missing mandatory information element" and shall return the Erroneous message information element containing the received message. + +## 16.5 IEs unknown or unforeseen in the message + +All IEs unknown or unforeseen in a message shall be ignored. + +## 16.6 Out of sequence IEs + +All IEs that are out of sequence shall be ignored. + +## 16.7 Repeated IEs + +If an information element with format T, TV, or TLV is repeated in a message in which repetition of the information element is not specified, only the contents of the information element appearing first shall be handled and all subsequent repetitions of the information element shall be ignored. When repetition of information elements is specified, only the contents of specified repeated information elements shall be handled. If the limit on repetition of information elements is exceeded, the contents of information elements appearing first up to the limit of repetitions shall be handled and all subsequent repetitions of the information element shall be ignored. + +## 16.8 Syntactically incorrect mandatory IE. + +On receipt of a message which contains a syntactically incorrect mandatory IE, the receiver shall ignore the message and return a BSSAP+-MOBILE-STATUS message with the Gs Cause Value set to "invalid mandatory information" and shall return the Erroneous message information element containing the received message. + +## 16.9 Syntactically incorrect optional IEs + +All optional IEs that are syntactically incorrect in a message shall be treated as not present in the message. + +## 16.10 Conditional IE errors + +When a VLR or SGSN receives a message and diagnoses a "missing conditional IE" error or an "unexpected conditional IE" error or when it receives a message containing at least one syntactically incorrect conditional IE which is required to be present in the message, a VLR or SGSN shall ignore the message and return a BSSAP+-MOBILE-STATUS message with the Gs Cause Value set to "conditional IE error" and shall return the Erroneous message information element containing the received message. + +When a VLR or SGSN receives a message containing a syntactically incorrect conditional IE which is not required to be present in the message, nor required to be absent in the message, then a VLR or SGSN shall ignore that IE. + +## 16.11 IEs with semantically incorrect contents + +When an IE with semantically incorrect contents is received, the foreseen reactions of the procedural part of 3GPP TS 29.018 are performed. + +If however no such reactions are specified, the receiving entity shall ignore that IE and treat the rest of the message. If, because this IE was ignored, the rest of the message can no longer be handled then the receiving entity shall return a BSSAP+-MOBILE-STATUS message with the Gs Cause Value set to "semantically incorrect message" and shall return the Erroneous message information element containing the received message. + +# 17 Message functional definitions and contents + +This clause defines the structure of the messages that are sent between the SGSN and the VLR. + +## 17.1 Message Contents + +### 17.1.1 BSSAP+-ALERT-ACK message + +This message is sent by the SGSN to the VLR to acknowledge a previous BSSAP+-ALERT-REQUEST message. + +**Table 17.1.1/3GPP TS 29.018: BSSAP+-ALERT-ACK message content** + +| Information Element | Type/Reference | Presence | Format | Length | +|---------------------|----------------------|----------|--------|--------| +| Message type | Message type
18.2 | M | V | 1 | +| IMSI | IMSI
18.4.10 | M | TLV | 6-10 | + +### 17.1.2 BSSAP+-ALERT-REJECT message + +This message is sent from the SGSN to the VLR to indicate that the SGSN could not identify the IMSI indicated in the BSSAP+-ALERT-Request message. + +**Table 17.1.2/3GPP TS 29.018: BSSAP+-ALERT-REJECT message content** + +| Information Element | Type/Reference | Presence | Format | Length | +|---------------------|----------------------|----------|--------|--------| +| Message type | Message type
18.2 | M | V | 1 | +| IMSI | IMSI
18.4.10 | M | TLV | 6-10 | +| Gs Cause | Gs Cause
18.4.7 | M | TLV | 3 | + +#### 17.1.2.1 Gs Cause + +The value part which is typically sent for this information element in this message is 'IMSI unknown'. + +### 17.1.3 BSSAP+-ALERT-REQUEST message + +This message is sent by the VLR to the SGSN to request an indication when next activity from the MS is detected. + +**Table 17.1.3/3GPP TS 29.018: BSSAP+-ALERT-REQUEST message content** + +| Information Element | Type/Reference | Presence | Format | Length | +|---------------------|----------------------|----------|--------|--------| +| Message type | Message type
18.2 | M | V | 1 | +| IMSI | IMSI
18.4.10 | M | TLV | 6-10 | + +### 17.1.4 BSSAP+-DOWNLINK-TUNNEL-REQUEST message + +This message is sent from the non-GSM MSC/VLR to the SGSN to convey a tunneling payload to the MS identified by the specified IMSI. + +**Table 17.1.4/3GPP TS 29.018: BSSAP+-DOWNLINK-TUNNEL-REQUEST message content** + +| Information Element | Type/Reference | Presence | Format | Length | +|------------------------------------------|----------------------------------------------------|----------|--------|--------| +| Message type | Message type
18.2 | M | V | 1 | +| IMSI | IMSI
18.4.10 | M | TLV | 6-10 | +| VLR number | VLR number
18.4.26 | M | TLV | 5-11 | +| Downlink Tunnel Payload Control and Info | Downlink Tunnel Payload Control and Info
18.4.3 | M | TLV | 3-223 | + +### 17.1.5 BSSAP+-GPRS-DETACH-ACK message + +This message is sent by the VLR to the SGSN to acknowledge a previous BSSAP+-GPRS-DETACH-Indication message. + +**Table 17.1.5/3GPP TS 29.018: BSSAP+-GPRS-DETACH-ACK message content** + +| Information Element | Type/Reference | Presence | Format | Length | +|---------------------|----------------------|----------|--------|--------| +| Message type | Message type
18.2 | M | V | 1 | +| IMSI | IMSI
18.4.10 | M | TLV | 6-10 | + +### 17.1.6 BSSAP+-GPRS-DETACH-INDICATION message + +This message is sent by the SGSN to the VLR to indicate a GPRS detach performed from the MS or the SGSN. The type of detach is indicated in the IMSI detach from GPRS service type IE. + +**Table 17.1.6/3GPP TS 29.018: BSSAP+-GPRS-DETACH-INDICATION message content** + +| Information Element | Type/Reference | Presence | Format | Length | +|------------------------------------|-----------------------------------------------|----------|--------|--------| +| Message type | Message type
18.2 | M | V | 1 | +| IMSI | IMSI
18.4.10 | M | TLV | 6-10 | +| SGSN number | SGSN number
18.4.22 | M | TLV | 5-11 | +| IMSI detach from GPRS service type | IMSI detach from GPRS service type
18.4.11 | M | TLV | 3 | +| Cell global identity | Cell global identity
18.4.1 | O | TLV | 10 | +| Service area identification | Service area identification
18.4.21b | O | TLV | 9 | + +#### 17.1.6.1 Cell global identity (A/Gb mode only) + +In A/Gb mode, the SGSN shall include the Cell global identity where the mobile was in the last radio contact. + +#### 17.1.6.2 Service area identification (Iu mode only) + +In Iu mode, the SGSN should include the Service area identification where the mobile was in the last radio contact. + +### 17.1.7 BSSAP+-IMSI-DETACH-ACK message + +This message is sent by the VLR to the SGSN to acknowledge a previous BSSAP+-IMSI-DETACH-Indication message. + +**Table 17.1.7/3GPP TS 29.018: BSSAP+-IMSI-DETACH-ACK message content** + +| Information Element | Type/Reference | Presence | Format | Length | +|---------------------|----------------------|----------|--------|--------| +| Message type | Message type
18.2 | M | V | 1 | +| IMSI | IMSI
18.4.10 | M | TLV | 6-10 | + +### 17.1.8 BSSAP+-IMSI-DETACH-INDICATION message + +This message is sent by the SGSN to the VLR to indicate an IMSI detach performed from the MS. The type of detach is indicated in the IMSI detach from non-GPRS service type IE. + +**Table 17.1.8/3GPP TS 29.018: BSSAP+-IMSI-DETACH-INDICATION message content** + +| Information Element | Type/Reference | Presence | Format | Length | +|----------------------------------------|---------------------------------------------------|----------|--------|--------| +| Message type | Message type
18.2 | M | V | 1 | +| IMSI | IMSI
18.4.10 | M | TLV | 6-10 | +| SGSN number | SGSN number
18.4.22 | M | TLV | 5-11 | +| IMSI detach from non-GPRS service type | IMSI detach from non-GPRS service type
18.4.12 | M | TLV | 3 | +| Cell global identity | Cell global identity
18.4.1 | O | TLV | 10 | +| Location information age | Location information age
18.4.15 | O | TLV | 4 | +| Service area identification | Service area identification
18.4.21b | O | TLV | 9 | + +#### 17.1.8.1 Cell global identity (A/Gb mode only) + +In A/Gb mode, the SGSN shall include the Cell global identity where the mobile was in the last radio contact. + +#### 17.1.8.2 Location information age + +If the detach is due to implicit detach and the Cell global identity is available, then the SGSN should include the Location information age. + +#### 17.1.8.3 Service area identification (Iu mode only) + +In Iu mode, the SGSN should include the Service area identification where the mobile was in the last radio contact. + +### 17.1.9 BSSAP+-LOCATION-UPDATE-ACCEPT message + +This message is sent by the VLR to the SGSN to indicate that update or IMSI attach in the VLR has been completed. + +**Table 17.1.9/3GPP TS 29.018: BSSAP+-LOCATION-UPDATE-ACCEPT message content** + +| Information Element | Type/Reference | Presence | Format | Length | +|--------------------------|-------------------------------------|----------|--------|--------| +| Message type | Message type
18.2 | M | V | 1 | +| IMSI | IMSI
18.4.10 | M | TLV | 6-10 | +| Location area identifier | Location area identifier
18.4.14 | M | TLV | 7 | +| New TMSI, or IMSI | Mobile identity
18.4.17 | O | TLV | 6-10 | + +#### 17.1.9.1 New TMSI, or IMSI + +This information element represents the identity to be used for (and then by) the MS. + +If this information element is an IMSI, then the mobile station is not allocated any TMSI (and deletes any TMSI accordingly). If this information element is a TMSI, then the mobile station will use this TMSI as the new temporary identity (the MS deletes its old TMSI and stores the new TMSI). If neither a TMSI nor an IMSI are included in this information element, the old TMSI, if any available, will be kept. + +### 17.1.10 BSSAP+-LOCATION-UPDATE-REJECT message + +#### 17.1.10.1 Message definition + +This message is sent by the VLR to the SGSN to indicate that location update or IMSI attach has failed. + +**Table 17.1.10/3GPP TS 29.018: BSSAP+-LOCATION-UPDATE-REJECT message content** + +| Information Element | Type/Reference | Presence | Format | Length | +|--------------------------|-------------------------------------|----------|--------|--------| +| Message type | Message type
18.2 | M | V | 1 | +| IMSI | IMSI
18.4.10 | M | TLV | 6-10 | +| Reject cause | Reject cause
18.4.21 | M | TLV | 3 | +| Location area identifier | Location area identifier
18.4.14 | O | TLV | 7 | + +#### 17.1.10.2 Location area identifier + +The VLR shall include this information element. + +### 17.1.11 BSSAP+-LOCATION-UPDATE-REQUEST message + +This message is sent by the SGSN to the VLR either to request update of its location file (normal update) or to request IMSI attach. + +**Table 17.1.11/3GPP TS 29.018: BSSAP+-LOCATION-UPDATE-REQUEST message content** + +| Information Element | Type/Reference | Presence | Format | Length | +|---------------------------------|-----------------------------------------|----------|--------|--------| +| Message type | Message type
18.2 | M | V | 1 | +| IMSI | IMSI
18.4.10 | M | TLV | 6-10 | +| SGSN number | SGSN number
18.4.22 | M | TLV | 5-11 | +| Update type | GPRS location update type
18.4.6 | M | TLV | 3 | +| New Cell global identity | Cell global identity
18.4.1 | M | TLV | 10 | +| Mobile station classmark | Mobile station classmark 1
18.4.18 | M | TLV | 3 | +| Old location area identifier | Location area identifier
18.4.14 | O | TLV | 7 | +| TMSI status | TMSI status
18.4.24 | O | TLV | 3 | +| New service area identification | Service area identification
18.4.21b | O | TLV | 9 | +| IMEISV | IMEISV
18.4.9 | O | TLV | 10 | +| TMSI based NRI container | TMSI based NRI container
18.4.28 | O | TLV | 4 | +| Selected CN operator | Selected CN operator
18.4.29 | O | TLV | 5 | + +#### 17.1.11.1 Old location area identifier + +This information element should be included. + +#### 17.1.11.2 New cell global identity + +In A/Gb mode, the cell global identity which shall be included is the one where the MS is in the current radio contact. + +In Iu mode, the cell global identity which shall be included indicates where the MS is in the current location area. The cell identity part of this information shall be ignored by the VLR. + +In a shared network, the PLMN identity contained in the cell global identity shall be the PLMN identity of the selected core network operator (see 3GPP TS 23.251 [24]). + +#### 17.1.11.3 TMSI status + +This information element shall be included if the TMSI status received in the ATTACH REQUEST or ROUTING AREA UPDATING REQUEST message from the MS indicates, that no valid TMSI is available in the MS. + +#### 17.1.11.4 Mobile station classmark + +This information element does not serve any useful purpose, but shall be included for reasons of compatibility with earlier versions of the protocol. To ease interworking with old VLR equipment, the SGSN shall encode the contents of this information element as: revision level 'GSM phase 2', 'early classmark sending supported', 'encryption algorithm A5/1 supported', and RF power capability 'class 1'. + +#### 17.1.11.5 New service area identification + +In Iu mode, the service area identification which should be included is the one where the MS is in the current radio contact. + +In a shared network, the PLMN identity contained in the service area identification shall be the PLMN identity of the selected core network operator (see 3GPP TS 23.251 [24]). + +#### 17.1.11.6 IMEISV + +This information element shall be included, if the SGSN supports the "Provision of UE Specific Behaviour Information to Network Entities" or the "Automatic Device Detection", or the "Trace for Management Based Activation/Deactivation". + +#### 17.1.11.7 TMSI based NRI container + +This information element shall be included if the TMSI based NRI container has been received in the ATTACH REQUEST or ROUTING AREA UPDATING REQUEST message from the MS. + +#### 17.1.11.8 Selected CN operator + +This information element shall be included for the non-supporting UE if the network is configured to support gateway core network (GWCN). + +### 17.1.12 BSSAP+-MM-INFORMATION-REQUEST + +This message is sent by the VLR to the SGSN to provide the MS with subscriber specific information. + +**Table 17.1.12/3GPP TS 29.018: BSSAP+-MM-INFORMATION-REQUEST message content** + +| Information Element | Type/Reference | Presence | Format | Length | +|---------------------|---------------------------|----------|--------|--------| +| Message type | Message type
18.2 | M | V | 1 | +| IMSI | IMSI
18.4.10 | M | TLV | 6-10 | +| MM information | MM information
18.4.16 | O | TLV | 3-n | + +#### 17.1.12.1 MM information + +This information element should be included in this message. + +### 17.1.13 BSSAP+-MOBILE-STATUS message + +This message is sent by both the SGSN or the VLR to indicate an error. + +**Table 17.1.13/3GPP TS 29.018: BSSAP+-MOBILE-STATUS message content** + +| Information Element | Type/Reference | Presence | Format | Length | +|---------------------|-----------------------------|----------|--------|--------| +| Message type | Message type
18.2 | M | V | 1 | +| IMSI | IMSI
18.4.10 | O | TLV | 6-10 | +| Gs Cause | Gs Cause
18.4.7 | M | TLV | 3 | +| Erroneous message | Erroneous message
18.4.5 | M | TLV | 3-n | + +#### 17.1.13.1 IMSI + +If the MS is identified by the IMSI, then this information element shall be included. + +### 17.1.14 BSSAP+-MS-ACTIVITY-INDICATION message + +This message is sent by the SGSN to the VLR to indicate that activity from an MS has been detected. + +**Table 17.1.14/3GPP TS 29.018: BSSAP+-MS-ACTIVITY-INDICATION message content** + +| Information Element | Type/Reference | Presence | Format | Length | +|-----------------------------|-----------------------------------------|----------|--------|--------| +| Message type | Message type
18.2 | M | V | 1 | +| IMSI | IMSI
18.4.10 | M | TLV | 6-10 | +| Cell global identity | Cell global identity
18.4.1 | O | TLV | 10 | +| Service area identification | Service area identification
18.4.21b | O | TLV | 9 | + +#### 17.1.14.1 Cell global identity (A/Gb mode only) + +In A/Gb mode, the SGSN shall include the cell global identity where the MS was in the last radio contact. + +#### 17.1.14.2 Service area identification (Iu mode only) + +In Iu mode, the SGSN should include the Service area identification where the mobile was in the last radio contact. + +### 17.1.15 BSSAP+-MS-INFORMATION-REQUEST message + +This message is sent from the VLR to the SGSN to request information associated with the indicated IMSI. The type of information requested is specified in the Information requested IE. + +**Table 17.1.15/3GPP TS 29.018: BSSAP+-MS-INFORMATION-REQUEST message content** + +| Information Element | Type/Reference | Presence | Format | Length | +|-----------------------|----------------------------------|----------|--------|--------| +| Message type | Message type
18.2 | M | V | 1 | +| IMSI | IMSI
18.4.10 | M | TLV | 6-10 | +| Information requested | Information requested
18.4.13 | M | TLV | 3 | + +### 17.1.16 BSSAP+-MS-INFORMATION-RESPONSE message + +This message is sent from the SGSN to the VLR as a response to a previous BSSAP+-MS-INFORMATION-REQUEST message. (At least one of the requested identities shall be sent). + +**Table 17.1.16/3GPP TS 29.018: BSSAP+-MS-INFORMATION-RESPONSE message content** + +| Information Element | Type/Reference | Presence | Format | Length | +|-----------------------------|-----------------------------------------|----------|--------|--------| +| Message type | Message type
18.2 | M | V | 1 | +| IMSI | IMSI
18.4.10 | M | TLV | 6-10 | +| TMSI | TMSI
18.4.23 | O | TLV | 6 | +| PTMSI | PTMSI
18.4.20 | O | TLV | 6 | +| IMEI | IMEI
18.4.8 | O | TLV | 10 | +| IMEISV | IMEISV
18.4.9 | O | TLV | 10 | +| Cell global identity | Cell global identity
18.4.1 | O | TLV | 10 | +| Location information age | Location information age
18.4.15 | O | TLV | 4 | +| Mobile station state | Mobile station state
18.4.19 | O | TLV | 3 | +| Service area identification | Service area identification
18.4.21b | O | TLV | 9 | + +#### 17.1.16.1 IMEI + +This information element should be included if it was requested in the BSSAP+-MS-INFORMATION-REQUEST message and if this information is obtainable. + +#### 17.1.16.2 IMIESV + +This information element should be included if it was requested in the BSSAP+-MS-INFORMATION-REQUEST message and if this information is obtainable. + +#### 17.1.16.3 Cell global identity (A/Gb mode only) + +In A/Gb mode, cell global identity where the MS was in the last radio contact. + +This information element should be included if it was requested in the BSSAP+-MS-INFORMATION-REQUEST message and if this information is obtainable. + +#### 17.1.16.4 Location information age + +Time in minutes since the MS last established a radio transaction. + +This information element should be included if it was requested in the BSSAP+-MS-INFORMATION-REQUEST message and if this information is obtainable. + +#### 17.1.16.5 Mobile station state + +This information element should be included in this message, irrespective of the information requested. + +#### 17.1.16.6 TMSI + +This information element should be included if it was requested in the BSSAP+-MS-INFORMATION-REQUEST message and if this information is obtainable. + +#### 17.1.16.7 Service area identification (Iu mode only) + +In Iu mode, service area identification where the MS was in the last radio contact. + +This information element should be included if it was requested in the BSSAP+-MS-INFORMATION-REQUEST message and if this information is obtainable. + +### 17.1.17 BSSAP+-MS-UNREACHABLE message + +This message is sent from the SGSN to the VLR to indicate that, for example, paging could not be performed because the MS is marked as unreachable at the SGSN. + +**Table 17.1.17/3GPP TS 29.018: BSSAP+-MS-UNREACHABLE message content** + +| Information Element | Type/Reference | Presence | Format | Length | +|---------------------|----------------------|----------|--------|--------| +| Message type | Message type
18.2 | M | V | 1 | +| IMSI | IMSI
18.4.10 | M | TLV | 6-10 | +| Gs Cause | Gs Cause
18.4.7 | M | TLV | 3 | + +#### 17.1.17.1 Gs Cause + +The value part which is typically sent for this information element in this message is 'MS unreachable'. + +### 17.1.18 BSSAP+-PAGING-REJECT message + +This message is sent from the SGSN to the VLR to indicate that the delivery of a previous BSSAP+-PAGING-REQUEST message has failed. + +**Table 17.1.18/3GPP TS 29.018: BSSAP+-PAGING-REJECT message content** + +| Information Element | Type/Reference | Presence | Format | Length | +|---------------------|----------------------|----------|--------|--------| +| Message type | Message type
18.2 | M | V | 1 | +| IMSI | IMSI
18.4.10 | M | TLV | 6-10 | +| Gs Cause | Gs Cause
18.4.7 | M | TLV | 3 | + +### 17.1.19 BSSAP+-PAGING-REQUEST message + +This message is sent from the VLR to the SGSN and contains sufficient information to allow the paging message to be transmitted by the correct cells at the correct time. + +**Table 17.1.19/3GPP TS 29.018: BSSAP+-PAGING\_REQUEST message content** + +| Information Element | Type/Reference | Presence | Format | Length | +|--------------------------|-------------------------------------|----------|--------|--------| +| Message type | Message type
18.2 | M | V | 1 | +| IMSI | IMSI
18.4.10 | M | TLV | 6-10 | +| VLR number | VLR number
18.4.26 | M | TLV | 5-11 | +| TMSI | TMSI
18.4.23 | O | TLV | 6 | +| Location area identifier | Location area identifier
18.4.14 | O | TLV | 7 | +| Channel needed | Channel needed
18.4.2 | O | TLV | 3 | +| eMLPP Priority | eMLPP Priority
18.4.4 | O | TLV | 3 | +| Global CN-Id | Global CN-Id
18.4.27 | O | TLV | 7 | + +#### 17.1.19.1 TMSI + +This element is omitted in the exceptional case where the IMSI is used instead of the TMSI as a paging address at the radio interface. + +#### 17.1.19.2 Location area identifier + +If the location area identifier is not included, then the SGSN shall page the MS in all the cells served by the VLR and the SGSN, unless the SGSN has reliable information about the location of the MS. + +#### 17.1.19.3 Channel needed + +If the Channel needed Information Element is not present, then the default value is assumed to be "any channel". + +#### 17.1.19.4 eMLPP priority + +This information element may be included when the subscriber has a subscription for eMLPP. + +#### 17.1.19.5 Global CN-Id + +If the network supports the Intra Domain Connection of RAN Nodes to multiple CN Nodes functionality, this information element shall be included when MSC/VLR initiates paging by IMSI, via the Gs interface. + +### 17.1.20 BSSAP+-RESET-ACK message + +This message is sent from the SGSN or the VLR to acknowledge a previous BSSAP+-RESET-INDICATION message. This message indicates that all the associations to the VLR or the SGSN have been marked as invalid. + +The sending entity (either SGSN or VLR) includes its identity in the BSSAP+-RESET-ACK message. + +**Table 17.1.20/3GPP TS 29.018: BSSAP+-RESET-ACK message content** + +| Information Element | Type/Reference | Presence | Format | Length | +|---------------------|------------------------|----------|--------|--------| +| Message type | Message type
18.2 | M | V | 1 | +| SGSN number | SGSN number
18.4.22 | C | TLV | 5-11 | +| VLR number | VLR number
18.4.26 | C | TLV | 5-11 | + +#### 17.1.20.1 SGSN number + +If the SGSN is the sending entity, then it shall indicate its address by including its SGSN number Information Element. Otherwise (i.e. if the VLR is the sending entity), then the SGSN number Information Element shall not be included. + +#### 17.1.20.2 VLR number + +If the VLR is the sending entity, then it shall indicate its address by including its VLR number Information Element. Otherwise (i.e. if the SGSN is the sending entity), then the VLR number Information Element shall not be included. + +### 17.1.21 BSSAP+-RESET-INDICATION message + +This message is sent from the VLR to the SGSN to indicate that a failure in the VLR has occurred and all the associations to the VLR shall be marked as invalid. + +This message is also sent from the SGSN to the VLR to indicate that a failure in the SGSN has occurred and all the associations to the SGSN shall be marked as invalid. + +The sending entity (either SGSN or VLR) includes its identity in the BSSAP+-RESET-INDICATION message. + +**Table 17.1.21/3GPP TS 29.018: BSSAP+-RESET-INDICATION message content** + +| Information Element | Type/Reference | Presence | Format | Length | +|---------------------|------------------------|----------|--------|--------| +| Message type | Message type
18.2 | M | V | 1 | +| SGSN number | SGSN number
18.4.22 | C | TLV | 5-11 | +| VLR number | VLR number
18.4.26 | C | TLV | 5-11 | + +#### 17.1.21.1 SGSN number + +If the SGSN is the sending entity, then it shall indicate its address by including its SGSN number Information Element. Otherwise (i.e. if the VLR is the sending entity), then the SGSN number Information Element shall not be included. + +#### 17.1.21.2 VLR number + +If the VLR is the sending entity, then it shall indicate its address by including its VLR number Information Element. Otherwise (i.e. if the SGSN is the sending entity), then the VLR number Information Element shall not be included. + +### 17.1.22 BSSAP+-TMSI-REALLOCATION-COMPLETE message + +This message is sent by the SGSN to the VLR to indicate that TMSI reallocation on the MS has been successfully completed. + +**Table 17.1.22/3GPP TS 29.018: BSSAP+-TMSI-REALLOCATION-COMPLETE message content** + +| Information Element | Type/Reference | Presence | Format | Length | +|-----------------------------|-----------------------------------------|----------|--------|--------| +| Message type | Message type
18.2 | M | V | 1 | +| IMSI | IMSI
18.4.10 | M | TLV | 6-10 | +| Cell global identity | Cell global identity
18.4.1 | O | TLV | 10 | +| Service area identification | Service area identification
18.4.21b | O | TLV | 9 | + +#### 17.1.22.1 Cell global identity (A/Gb mode only) + +The SGSN shall include the cell global identity where the Mobile Station was in the last radio contact. + +#### 17.1.22.2 Service area identification (Iu mode only) + +In Iu mode, the SGSN should include the Service area identification where the mobile was in the last radio contact. + +### 17.1.23 BSSAP+-UPLINK-TUNNEL-REQUEST message + +This message is sent from the SGSN to the non-GSM MSC/VLR to convey the tunneling payload received from the MS identified by the specified IMSI. + +**Table 17.1.23/3GPP TS 29.018: BSSAP+-UPLINK-TUNNEL-REQUEST message content** + +| Information Element | Type/Reference | Presence | Format | Length | +|----------------------------------------|---------------------------------------------------|----------|--------|--------| +| Message type | Message type
18.2 | M | V | 1 | +| IMSI | IMSI
18.4.10 | M | TLV | 6-10 | +| SGSN number | SGSN number
18.4.22 | M | TLV | 5-11 | +| Uplink Tunnel Payload Control and Info | Uplink Tunnel Payload Control and Info
18.4.25 | M | TLV | 3-223 | + +# 18 Message format and information element coding + +This clause specifies the coding of the Information Elements used in by the BSSAP+ protocol. The spare bits in the coding of an IE shall be set to zero by the sender and shall be ignored by the receiver. + +All unassigned codes (whether omitted or explicitly *Unassigned* in the text) shall be treated as unknown (see clause 16). + +## 18.1 Overview + +## 18.2 Message type + +Message type uniquely identifies the message being sent. It is a single octet element, mandatory in all messages. + +**Table 18.2/3GPP TS 29.018: Message type information element** + +| 8 7 6 5 4 3 2 1 | Message type | Reference | +|------------------------------------------|---------------------------------------------------------|-----------| +| 0 0 0 0 0 0 0 0 | Unassigned : treated as an unknown Message type. | 18 and 16 | +| 0 0 0 0 0 0 0 1 | BSSAP+-PAGING-REQUEST | 17.1.19 | +| 0 0 0 0 0 0 1 0 | BSSAP+-PAGING-REJECT | 17.1.18 | +| 0 0 0 0 0 0 1 1
to
0 0 0 0 0 1 1 0 | Unassigned : treated as an unknown Message type. | 18 and 16 | +| 0 0 0 0 0 1 1 1 | BSSAP+-DOWNLINK-TUNNEL-REQUEST | 17.1.4 | +| 0 0 0 0 1 0 0 0 | BSSAP+-UPLINK-TUNNEL-REQUEST | 17.1.23 | +| 0 0 0 0 1 0 0 1 | BSSAP+-LOCATION-UPDATE-REQUEST | 17.1.11 | +| 0 0 0 0 1 0 1 0 | BSSAP+-LOCATION-UPDATE-ACCEPT | 17.1.9 | +| 0 0 0 0 1 0 1 1 | BSSAP+-LOCATION-UPDATE-REJECT | 17.1.10 | +| 0 0 0 0 1 1 0 0 | BSSAP+-TMSI-REALLOCATION-COMPLETE | 17.1.22 | +| 0 0 0 0 1 1 0 1 | BSSAP+-ALERT-REQUEST | 17.1.3 | +| 0 0 0 0 1 1 1 0 | BSSAP+-ALERT-ACK | 17.1.1 | +| 0 0 0 0 1 1 1 1 | BSSAP+-ALERT-REJECT | 17.1.2 | +| 0 0 0 1 0 0 0 0 | BSSAP+-MS-ACTIVITY-INDICATION | 17.1.14 | +| 0 0 0 1 0 0 0 1 | BSSAP+-GPRS-DETACH-INDICATION | 17.1.6 | +| 0 0 0 1 0 0 1 0 | BSSAP+-GPRS-DETACH-ACK | 17.1.5 | +| 0 0 0 1 0 0 1 1 | BSSAP+-IMSI-DETACH-INDICATION | 17.1.8 | +| 0 0 0 1 0 1 0 0 | BSSAP+-IMSI-DETACH-ACK | 17.1.7 | +| 0 0 0 1 0 1 0 1 | BSSAP+-RESET-INDICATION | 17.1.21 | +| 0 0 0 1 0 1 1 0 | BSSAP+-RESET-ACK | 17.1.20 | +| 0 0 0 1 0 1 1 1 | BSSAP+-MS-INFORMATION-REQUEST | 17.1.15 | +| 0 0 0 1 1 0 0 0 | BSSAP+-MS-INFORMATION-RESPONSE | 17.1.16 | +| 0 0 0 1 1 0 0 1 | Unassigned : treated as an unknown Message type. | 18 and 16 | +| 0 0 0 1 1 0 1 0 | BSSAP+-MM-INFORMATION-REQUEST | 17.1.12 | +| 0 0 0 1 1 1 0 1 | BSSAP+-MOBILE-STATUS | 17.1.13 | +| 0 0 0 1 1 1 1 0 | Unassigned : treated as an unknown Message type. | 18 and 16 | +| 0 0 0 1 1 1 1 1 | BSSAP+-MS-UNREACHABLE | 17.1.17 | + +## 18.3 Information Element Identifiers + +The next list shows the coding of the Information Element Identifiers used in the present document. + +**Table 18.3/3GPP TS 29.018: Information Element Identifier coding** + +| 8 7 6 5 4 3 2 1 | Information element | Reference | +|------------------------------------------|-----------------------------------------------|-----------| +| 0 0 0 0 0 0 0 1 | IMSI | 18.4.10 | +| 0 0 0 0 0 1 0 | VLR number | 18.4.26 | +| 0 0 0 0 0 1 1 | TMSI | 18.4.23 | +| 0 0 0 0 1 0 0 | Location area identifier | 18.4.14 | +| 0 0 0 0 1 0 1 | Channel Needed | 18.4.2 | +| 0 0 0 0 1 1 0 | eMLPP Priority | 18.4.4 | +| 0 0 0 0 1 1 1 | TMSI status | 18.4.24 | +| 0 0 0 1 0 0 0 | Gs cause | 18.4.7 | +| 0 0 0 1 0 0 1 | SGSN number | 18.4.22 | +| 0 0 0 1 0 1 0 | GPRS location update type | 18.4.6 | +| 0 0 0 1 0 1 1 | Global CN-Id | 18.4.27 | +| 0 0 0 1 1 0 0 | Unassigned: treated as an unknown IEI. | 18 and 16 | +| 0 0 0 1 1 0 1 | Mobile station classmark 1 | 18.4.18 | +| 0 0 0 1 1 1 0 | Mobile identity | 18.4.17 | +| 0 0 0 1 1 1 1 | Reject cause | 18.4.21 | +| 0 0 1 0 0 0 0 | IMSI detach from GPRS service type | 18.4.11 | +| 0 0 1 0 0 0 1 | IMSI detach from non-GPRS service type | 18.4.12 | +| 0 0 1 0 0 1 0 | Information requested | 18.4.13 | +| 0 0 1 0 0 1 1 | PTMSI | 18.4.20 | +| 0 0 1 0 1 0 0 | IMEI | 18.4.8 | +| 0 0 1 0 1 0 1 | IMEISV | 18.4.9 | +| 0 0 1 0 1 1 0 | Unassigned: treated as an unknown IEI. | 18 and 16 | +| 0 0 1 0 1 1 1 | MM information | 18.4.16 | +| 0 0 1 1 0 0 0 | Cell Global Identity | 18.4.1 | +| 0 0 1 1 0 0 1 | Location information age | 18.4.15 | +| 0 0 1 1 0 1 0 | Mobile station state | 18.4.19 | +| 0 0 1 1 0 1 1 | Erroneous message | 18.4.5 | +| 0 0 1 1 1 0 0 | Downlink Tunnel Payload Control and Info | 18.4.3 | +| 0 0 1 1 1 0 1 | Uplink Tunnel Payload Control and Info | 18.4.25 | +| 0 0 1 1 1 1 0 | Service Area Identification | 18.4.21b | +| 0 0 1 1 1 1 1 | TMSI based NRI container | 18.4.28 | +| 0 0 1 0 0 0 0 0
to
1 1 1 1 1 1 1 1 | Unassigned: treated as an unknown IEI. | 18 and 16 | + +## 18.3a Length indicator + +The length indicator of the information elements consists of one octet and contains the binary encoding of the number of octets of the value part in the information elements. + +## 18.4 Information elements + +### 18.4.1 Cell global identity + +This information element uniquely identifies one cell. + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---|---|---|---|---|---|---| +| Octet 1 | IEI | | | | | | | | +| Octet 2 | Length indicator | | | | | | | | +| Octet 3
to
Octet 10 | The rest of the information element is coded as the value part of the cell global id IE defined in 3GPP TS 48.018 [15] (not including 3GPP TS 48.018 IEI and 3GPP TS 48.018 length indicator). | | | | | | | | + +Figure 18.4.1/3GPP TS 29.018: Cell global identity IE + +### 18.4.2 Channel needed + +The purpose of the *Channel Needed* information element is to indicate which type of channel is needed for the transaction linked to the paging procedure. + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|---------|-------------------------------------------------------------------------------------------------------------------------------------------|---|---|---|---|---|---|---| +| Octet 1 | IEI | | | | | | | | +| Octet 2 | Length indicator | | | | | | | | +| Octet 3 | The rest of the information element is coded as the IEI part and the value part of the Channel Needed IE defined in 3GPP TS 44.018 [11a]. | | | | | | | | + +Figure 18.4.2/3GPP TS 29.018: Channel needed IE + +### 18.4.3 Downlink Tunnel Payload Control and Info + +This information element is used to convey the payload of octets to be delivered to the identified mobile. + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|--------------------------|------------------|----------------------------|---|---|---|-----------------|---|---| +| Octet 1 | IEI | | | | | | | | +| Octet 2 | Length indicator | | | | | | | | +| Octet 3 | Spare | TOM Protocol Discriminator | | | E | Tunnel Priority | | | +| Octet 4
to
Octet n | Tunnel payload | | | | | | | | + +TOM Protocol Discriminator: Identifies the protocol using tunnelling of non-GSM signalling. For coding, see 3GPP TS 44.064 [12]. + +E: Cipher Request. When set to 1 indicates that the SGSN shall cipher the payload, when set to 0 indicates that the SGSN shall not cipher the payload. + +Tunnel Priority: Indicates the priority of the Tunnel Payload. For coding, see table 20.1: Association between Tunnel Priority and LLC SAPs. + +Figure 18.4.3/3GPP TS 29.018: Downlink Tunnel Payload Control and Info IE + +### 18.4.4 eMLPP Priority + +This element indicates the eMLPP-Priority. + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|---------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---|---|---|---|---|---|---| +| Octet 1 | IEI | | | | | | | | +| Octet 2 | Length indicator | | | | | | | | +| Octet 3 | The rest of the information element is coded as the value part of the eMLPP-Priority IE defined in 3GPP TS 48.008 [14] (not including 3GPP TS 48.008 IEI and 3GPP TS 48.008 length indicator). | | | | | | | | + +Figure 18.4.4/3GPP TS 29.018: eMLPP Priority IE + +### 18.4.5 Erroneous message + +The Erroneous message IE is a TLV IE that encapsulates the message in error. + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|-------------------------|------------------------------------------------------------------------------------------------------------------------------|---|---|---|---|---|---|---| +| Octet 1 | IEI | | | | | | | | +| Octet 2 | Length indicator | | | | | | | | +| Octet 3
-
Octet n | Erroneous message including the message type. | | | | | | | | +| NOTE: | If the size of the erroneous message including the message type exceeded 255 octets, only the first 255 octets are included. | | | | | | | | + +Figure 18.4.5/3GPP TS 29.018: Erroneous message IE + +### 18.4.6 GPRS location update type + +The purpose of the GPRS location update type information element is to indicate to the VLR whether an IMSI attach or a normal location update has been performed by the MS. + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|---------|---------------------------------|---|---|---|---|---|---|---| +| Octet 1 | IEI | | | | | | | | +| Octet 2 | Length indicator | | | | | | | | +| Octet 3 | GPRS location update type value | | | | | | | | + +Figure 18.4.6/3GPP TS 29.018: GPRS location update type IE + +Table 18.4.6/3GPP TS 29.018: GPRS location update type IE value part + +| | | +|-------------------------------------------|---------------------------------------------------------------------------------------------------| +| GPRS location update type value (octet 3) | | +| Bits | | +| 8 7 6 5 4 3 2 1 | | +| 0 0 0 0 0 0 0 0 | Shall not be sent in this version of the protocol. If received, shall be treated as '00000010'. | +| 0 0 0 0 0 0 0 1 | IMSI attach | +| 0 0 0 0 0 0 1 0 | Normal location update | +| 0 0 0 0 0 0 1 1 | Shall not be sent in this version of the protocol. If received, to shall be treated as 00000010'. | +| To | | +| 1 1 1 1 1 1 1 1 | | + +### 18.4.7 Gs cause + +The purpose of the value part of the Gs Cause information element is to indicate an error to the receiving entity. This could be a protocol data error or to indicate to the VLR the reason why a paging procedure could not be performed. + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|---------|------------------|---|---|---|---|---|---|---| +| Octet 1 | IEI | | | | | | | | +| Octet 2 | Length indicator | | | | | | | | +| Octet 3 | Gs Cause value | | | | | | | | + +Figure 18.4.7/3GPP TS 29.018: Gs Cause IE + +**Table 18.4.7/3GPP TS 29.018: Gs Cause IE value part** + +| Gs Cause value (octet 3) | | +|--------------------------|-------------------------------------------------------------| +| Bits | | +| 8 7 6 5 4 3 2 1 | | +| 0 0 0 0 0 0 0 0 | Normal, unspecified in this version of the protocol. | +| 0 0 0 0 0 0 0 1 | IMSI detached for GPRS services | +| 0 0 0 0 0 0 1 0 | IMSI detached for GPRS and non-GPRS services | +| 0 0 0 0 0 0 1 1 | IMSI unknown | +| 0 0 0 0 0 1 0 0 | IMSI detached for non-GPRS services | +| 0 0 0 0 0 1 0 1 | IMSI implicitly detached for non-GPRS services | +| 0 0 0 0 0 1 1 0 | MS unreachable | +| 0 0 0 0 0 1 1 1 | Message not compatible with the protocol state | +| 0 0 0 0 1 0 0 0 | Missing mandatory information element | +| 0 0 0 0 1 0 0 1 | Invalid mandatory information | +| 0 0 0 0 1 0 1 0 | Conditional IE error | +| 0 0 0 0 1 0 1 1 | Semantically incorrect message | +| 0 0 0 0 1 1 0 0 | Message unknown | +| 0 0 0 0 1 1 0 1 | Address error | +| 0 0 0 0 1 1 1 0 | TOM functionality not supported | +| 0 0 0 0 1 1 1 1 | Ciphering request cannot be accommodated | +| 0 0 0 1 0 0 0 0 | Normal, unspecified in this version of the protocol | +| to | | +| 1 1 1 1 1 1 1 1 | | + +NOTE: '*Normal, unspecified*' has the same meaning than in 3GPP TS 24.008 [11], informative Annex H (UMTS specific cause values for call control). It is used to report a normal event, and should not be interpreted as syntactically incorrect nor unknown if received. + +### 18.4.8 IMEI + +The IMEI is coded as a sequence of BCD digits, compressed two into each octet. The IMEI consists of 15 digits (see 3GPP TS 23.003 [5]). + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|-----------------|------------------|---|---|---|----------|---|---|---| +| octet 1 | IEI | | | | | | | | +| octet 2 | length indicator | | | | | | | | +| octet 3 | digit 2 | | | | digit 1 | | | | +| octet 4 | digit 4 | | | | digit 3 | | | | +| octet 5 | digit 6 | | | | digit 5 | | | | +| octet 6 | digit 8 | | | | digit 7 | | | | +| octet 7 | digit 10 | | | | digit 9 | | | | +| octet 8 | digit 12 | | | | digit 11 | | | | +| octet 9 | digit 14 | | | | digit 13 | | | | +| octet 10 | 1 | 1 | 1 | 1 | 0 | 0 | 0 | 0 | + +**Figure 18.4.8/3GPP TS 29.018: IMEI IE** + +### 18.4.9 IMEISV + +The IMEISV is coded as a sequence of BCD digits, compressed two into each octet. The IMEISV consists of 16 digits (see 3GPP TS 23.003 [5]). + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|----------|------------------|---|---|---|----------|---|---|---| +| octet 1 | IEI | | | | | | | | +| octet 2 | length indicator | | | | | | | | +| octet 3 | digit 2 | | | | digit 1 | | | | +| octet 4 | digit 4 | | | | digit 3 | | | | +| octet 5 | digit 6 | | | | digit 5 | | | | +| octet 6 | digit 8 | | | | digit 7 | | | | +| octet 7 | digit 10 | | | | digit 9 | | | | +| octet 8 | digit 12 | | | | digit 11 | | | | +| octet 9 | digit 14 | | | | digit 13 | | | | +| octet 10 | digit 16 | | | | digit 15 | | | | + +Figure 18.4.9/3GPP TS 29.018: IMEISV IE + +### 18.4.10 IMSI + +The IMSI is coded as a sequence of BCD digits, compressed two into each octet. This is a variable length element, and includes a length indicator. The IMSI is defined in 3GPP TS 23.003 [5]. It shall not exceed 15 digits (see 3GPP TS 23.003 [5]). + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|-----------|------------------|---|---|---|--------------|---|---|---| +| Octet 1 | IEI | | | | | | | | +| Octet 2 | Length indicator | | | | | | | | +| Octet 3 | IMSI digit 1 | | | | * parity | 0 | 0 | 1 | +| Octet 4 | IMSI digit 3 | | | | IMSI digit 2 | | | | +| Octet 4+x | IMSI digit i+1 | | | | IMSI digit i | | | | + +Figure 18.4.10/3GPP TS 29.018: IMSI IE + +Where $x = (i-2)/2$ and $i$ is always even + +- \* The value of the parity bit (bit 4 in octet 3) indicates: + +- 0 Even number of IMSI digits; +- 1 Odd number of IMSI digits; + +If the number of IMSI digits is even then bits 5 to 8 of the last octet shall be filled with an end mark coded as 1111. + +### 18.4.11 IMSI detach from GPRS service type + +The purpose of the IMSI detach from GPRS service type information element is to indicate to the VLR the type of IMSI detach from GPRS service performed by the MS or the SGSN. + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|---------|------------------------------------------|---|---|---|---|---|---|---| +| Octet 1 | IEI | | | | | | | | +| Octet 2 | Length indicator | | | | | | | | +| Octet 3 | IMSI detach from GPRS service type value | | | | | | | | + +Figure 18.4.11/3GPP TS 29.018: IMSI detach from GPRS service type IE + +**Table 18.4.11/3GPP TS 29.018: IMSI detach from GPRS service type IE value part** + +| | | +|----------------------------------------------------|-------------------------------------------------------------------| +| IMSI detach from GPRS service type value (octet 3) | | +| Bits | | +| 8 7 6 5 4 3 2 1 | | +| 0 0 0 0 0 0 0 0 | Interpreted as reserved in this version of the protocol | +| 0 0 0 0 0 0 0 1 | Network initiated IMSI detach from GPRS service | +| 0 0 0 0 0 1 0 | MS initiated IMSI detach from GPRS service | +| 0 0 0 0 0 1 1 | GPRS services not allowed | +| 0 0 0 0 1 0 0 | to Interpreted as reserved in this version of the protocol | +| 1 1 1 1 1 1 1 | | + +### 18.4.12 IMSI detach from non-GPRS service type + +The purpose of the IMSI detach from non-GPRS service type information element is to indicate to the VLR if the type of IMSI detach from non-GPRS service was explicitly performed by the MS or implicitly performed by the SGSN. + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|----------------|----------------------------------------------|---|---|---|---|---|---|---| +| Octet 1 | IEI | | | | | | | | +| Octet 2 | Length indicator | | | | | | | | +| Octet 3 | IMSI detach from non-GPRS service type value | | | | | | | | + +**Figure 18.4.12/3GPP TS 29.018: IMSI detach from non-GPRS service type IE****Table 18.4.12/3GPP TS 29.018: IMSI detach from non-GPRS service type IE value part** + +| | | +|--------------------------------------------------------|----------------------------------------------------------------------------| +| IMSI detach from non-GPRS service type value (octet 3) | | +| Bits | | +| 8 7 6 5 4 3 2 1 | | +| 0 0 0 0 0 0 0 0 | Interpreted as reserved in this version of the protocol | +| 0 0 0 0 0 0 0 1 | Explicit MS initiated IMSI detach from non-GPRS service | +| 0 0 0 0 0 1 0 | Combined explicit MS initiated IMSI detach from GPRS and non-GPRS services | +| 0 0 0 0 0 1 1 | Implicit SGSN initiated IMSI detach from GPRS and non-GPRS services | +| 0 0 0 0 1 0 0 | to Interpreted as reserved in this version of the protocol | +| 1 1 1 1 1 1 1 | | + +### 18.4.13 Information requested + +The Information requested IE is a TLV IE that indicates to the SGSN the type of information requested by the VLR. The coding of the V field is as follows. + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|----------------|-----------------------------|---|---|---|---|---|---|---| +| Octet 1 | IEI | | | | | | | | +| Octet 2 | Length indicator | | | | | | | | +| Octet 3 | Information requested value | | | | | | | | + +**Figure 18.4.13/3GPP TS 29.018: Information requested IE** + +**Table 18.4.13/3GPP TS 29.018: Information requested IE value part** + +| Information requested value (octet 3) | | +|---------------------------------------|----------------------------------------------------------------------| +| Bits | | +| 8 7 6 5 4 3 2 1 | | +| 0 0 0 0 0 0 0 0 | Interpreted as Not supported in this version of the protocol. | +| 0 0 0 0 0 0 0 1 | PTMSI | +| 0 0 0 0 0 0 1 0 | IMEI | +| 0 0 0 0 0 0 1 1 | IMEISV | +| 0 0 0 0 0 1 0 0 | PTMSI and IMEI | +| 0 0 0 0 0 1 0 1 | PTMSI and IMEISV | +| 0 0 0 0 0 1 1 0 | IMEI and IMEISV | +| 0 0 0 0 0 1 1 1 | PTMSI, IMEI, and IMEISV | +| 0 0 0 0 1 0 0 0 | Mobile location information | +| 0 0 0 0 1 0 0 1 | TMSI | +| 0 0 0 0 1 0 1 0 | Interpreted as Not supported in this version of the protocol. | +| to | | +| 1 1 1 1 1 1 1 1 | | + +NOTE: The behaviour of the receiver in the case of a *Not supported* value is described in clause 14.3, *Procedures in the SGSN*. + +### 18.4.14 Location area identifier + +This element uniquely identifies one Location Area. + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|-------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---|---|---|---|---|---|---| +| Octet 1 | IEI | | | | | | | | +| Octet 2 | Length Indicator | | | | | | | | +| Octet 3
-
Octet 7 | The rest of the information element is coded as the value part of the location area identifier IE defined in 3GPP TS 48.018 [15] (not including 3GPP TS 48.018 IEI and 3GPP TS 48.018 length indicator). | | | | | | | | + +**Figure 18.4.14/3GPP TS 29.018: Location area identifier IE** + +### 18.4.15 Location information age + +The Location information age IE is a TLV IE that indicates the elapsed time in minutes since the last network contact of the mobile station. + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|--------------------|--------------------------------------------------------------------------------------------------------------------|---|---|---|---|---|---|---| +| Octet 1 | IEI | | | | | | | | +| Octet 2 | Length indicator | | | | | | | | +| Octet 3
Octet 4 | The rest of the IE is coded as the value part of the AgeOfLocationInformation as specified in 3GPP TS 29.002 [17]. | | | | | | | | + +**Figure 18.4.15/3GPP TS 29.018: Location information age IE** + +### 18.4.16 MM information + +The MM information IE is a TLV IE that encapsulates the user information that the SGSN forwards to the MS. + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|---------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---|---|---|---|---|---|---| +| Octet 1 | IEI | | | | | | | | +| Octet 2 | Length Indicator | | | | | | | | +| Octet 3
–
Octet n | User information: This field is composed of one or more of the information elements of the MM information message as defined in 3GPP TS 24.008 [11], excluding the Protocol discriminator, Skip indicator and Message type. This field includes the IEI and length indicator of the other information elements. | | | | | | | | + +**Figure 18.4.16/3GPP TS 29.018: MM information IE** + +### 18.4.17 Mobile identity + +The purpose of the *Mobile identity* information element is to provide either: + +- The International Mobile Subscriber Identity (IMSI); +- The Temporary Mobile Subscriber Identity (TMSI); +- The International Mobile Equipment Identity (IMEI); or +- The International Mobile Equipment Identity together with the Software Version number (IMEISV). + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|---------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---|---|---|---|---|---|---| +| Octet 1 | IEI | | | | | | | | +| Octet 2 | Length Indicator | | | | | | | | +| Octet 3
–
Octet n | The rest of the information element is coded as the value part of the mobile identity IE defined in 3GPP TS 24.008 [11] (not including 3GPP TS 24.008 IEI and 3GPP TS 24.008 length indicator). | | | | | | | | + +**Figure 18.4.17/3GPP TS 29.018: Mobile identity IE** + +### 18.4.18 Mobile station classmark 1 + +The purpose of the *Mobile Station Classmark 1* information element is to provide the network with information concerning aspects of high priority of the mobile station equipment. + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|---|---|---|---|---|---|---| +| Octet 1 | IEI | | | | | | | | +| Octet 2 | Length indicator | | | | | | | | +| Octet 3 | The rest of the information element is coded as the value part of the mobile station classmark 1 IE defined in 3GPP TS 24.008 [11] (not including 3GPP TS 24.008 IEI) | | | | | | | | + +**Figure 18.4.18/3GPP TS 29.018: Mobile station classmark 1 IE** + +### 18.4.19 Mobile station state + +The Mobile station state IE is a TLV IE that indicates to the VLR the GMM and GSM states of the MS in the SGSN. The coding of the V field is as follows. + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|----------------|----------------------------|---|---|---|---|---|---|---| +| Octet 1 | IEI | | | | | | | | +| Octet 2 | Length indicator | | | | | | | | +| Octet 3 | Mobile station state value | | | | | | | | + +**Figure 18.4.19/3GPP TS 29.018: Mobile station state IE** + +**Table 18.4.19/3GPP TS 29.018: Mobile station state IE value part** + +| Mobile station state value (octet 3) | | | +|--------------------------------------|---|----------------------------------------------------------------------------------------------------------------------| +| Bits | | | +| 8 | 7 | 6 5 4 3 2 1 | +| 0 | 0 | 0 0 0 0 0 0 IDLE or PMM-DETACHED | +| 0 | 0 | 0 0 0 0 0 1 STANDBY or PMM-IDLE, 0 PDP contexts active | +| 0 | 0 | 0 0 0 0 1 0 STANDBY or PMM-IDLE, 1 or more PDP contexts active | +| 0 | 0 | 0 0 0 0 1 1 SUSPENDED, 0 PDP contexts active | +| 0 | 0 | 0 0 0 1 0 0 SUSPENDED, 1 or more PDP contexts active | +| 0 | 0 | 0 0 0 1 0 1 READY or PMM-CONNECTED, 0 PDP contexts active | +| 0 | 0 | 0 0 0 1 1 0 READY or PMM-CONNECTED, 1 or more PDP contexts active | +| 0 | 0 | 0 0 0 1 1 1 IMSI unknown | +| 0 | 0 | 0 0 0 1 0 0 Information requested not supported | +| 0 | 0 | 0 0 0 1 0 1 Shall not be sent in this version of the protocol.
to
If received, shall be treated as '00001000'. | +| 1 | 1 | 1 1 1 1 1 1 | + +### 18.4.20 PTMSI + +The PTMSI consists of 4 octets. It can be coded using a full hexadecimal representation (see 3GPP TS 23.003 [5]). + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|----------------|------------------|---|---|---|---|---|---|---| +| octet 1 | IEI | | | | | | | | +| octet 2 | length indicator | | | | | | | | +| octet 3 | PTMSI octet 1 | | | | | | | | +| octet 4 | PTMSI octet 2 | | | | | | | | +| octet 5 | PTMSI octet 3 | | | | | | | | +| octet 6 | PTMSI octet 4 | | | | | | | | + +**Figure 18.4.20/3GPP TS 29.018: PTMSI IE** + +### 18.4.21 Reject cause + +The purpose of the *Reject Cause* information element is to indicate the reason why a request from the mobile station is rejected by the network. + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|----------------|---------------------------------------------------------------------------------------------------------------------------------------------------------|---|---|---|---|---|---|---| +| Octet 1 | IEI | | | | | | | | +| Octet 2 | Length Indicator | | | | | | | | +| Octet 3 | The rest of the information element is coded as the value part of the reject cause IE defined in 3GPP TS 24.008 [11], not including 3GPP TS 24.008 IEI. | | | | | | | | + +Figure 18.4.21/3GPP TS 29.018: Reject cause IE + +### 18.4.21b Service Area Identification + +This information element uniquely identifies one service area. + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|-----------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---|---|---|---|---|---|---| +| Octet 1 | IEI | | | | | | | | +| Octet 2 | Length indicator | | | | | | | | +| Octet 3
to
Octet 9 | The rest of the information element is coded as the the value part of the SAI IE defined in 3GPP TS 25.413 [22] (not including 3GPP TS 25.413 IEI and 3GPP TS 25.413 length indicator). | | | | | | | | + +Figure 18.4.27/3GPP TS 29.018: Service Area Identification IE + +### 18.4.22 SGSN number + +The SGSN number is coded as a sequence of TBCD digits (as specified in 3GPP TS 29.002 [17]), compressed two into each octet. The Number is in international E.164 format as indicated by Octet 3 which coding is specified in 3GPP TS 29.002 [17]. This is a variable length information element, and includes a length indicator. The value part of the SGSN number information element (not including IEI, Length indicator and Octet 3) shall not exceed 15 digits. + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|----------------|------------------|---|---|---|---------|---|---|---| +| Octet 1 | IEI | | | | | | | | +| Octet 2 | Length indicator | | | | | | | | +| Octet 3 | 1 | 0 | 0 | 1 | 0 | 0 | 0 | 1 | +| Octet 4 | digit 2 | | | | digit 1 | | | | +| Octet n | digit i+1 | | | | digit i | | | | + +Figure 18.4.22/3GPP TS 29.018: SGSN number IE + +### 18.4.23 TMSI + +The TMSI consists of 4 octets. It can be coded using a full hexadecimal representation (see 3GPP TS 23.003 [5]). + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|----------------|------------------|---|---|---|---|---|---|---| +| octet 1 | IEI | | | | | | | | +| octet 2 | length indicator | | | | | | | | +| octet 3 | TMSI octet 1 | | | | | | | | +| octet 4 | TMSI octet 2 | | | | | | | | +| octet 5 | TMSI octet 3 | | | | | | | | +| octet 6 | TMSI octet 4 | | | | | | | | + +Figure 18.4.23/3GPP TS 29.018: TMSI IE + +### 18.4.24 TMSI status + +The purpose of the TMSI status information element is to indicate to the VLR whether a valid TMSI is available in the MS. + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|---------|------------------|---|---|---|---|---|---|-----------| +| Octet 1 | IEI | | | | | | | | +| Octet 2 | Length indicator | | | | | | | | +| Octet 3 | Spare | | | | | | | TMSI flag | + +Figure 18.4.24/3GPP TS 29.018: TMSI status IE + +Table 18.4.24/3GPP TS 29.018: TMSI status IE value part + +| | +|------------------------------------------------------------------| +| TMSI flag (octet 3) | +| Bit | +| 1 | +| 0 no valid TMSI available | +| 1 valid TMSI available | +| Bits 2-8 in octet 3 are spare and shall be coded all equal to 0. | + +### 18.4.25 Uplink Tunnel Payload Control and Info + +This information element is used to convey the payload of octets received from the mobile to the appropriate non-GSM MSC/VLR. + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|--------------------------|------------------|----------------------------|---|---|---|-----------------|---|---| +| Octet 1 | IEI | | | | | | | | +| Octet 2 | Length indicator | | | | | | | | +| Octet 3 | Spare | TOM Protocol Discriminator | | | E | Tunnel Priority | | | +| Octet 4
to
Octet n | Tunnel payload | | | | | | | | + +TOM Protocol Discriminator: Identifies the protocol using tunnelling of non-GSM signalling. For coding, see 3GPP TS 44.064 [12]. + +E: Cipher Request. When set to 1 indicates that the SGSN received the payload in ciphered form, when set to 0 indicates that the SGSN did not receive the payload in ciphered form. + +Tunnel Priority: Indicates the priority of the Tunnel Payload. For coding, see Table 20.1: Association between Tunnel Priority and LLC SAPs. + +Figure 18.4.25/3GPP TS 29.018: Uplink Tunnel Payload Control and Info IE + +### 18.4.26 VLR number + +The VLR number is coded as a sequence of TBCD digits (as specified in 3GPP TS 29.002 [17]), compressed two into each octet. The Number is in international E.164 format as indicated by Octet 3 which coding is specified in 3GPP TS 29.002 [17]. This is a variable length information element, and includes a length indicator. The value part of the VLR number information element (not including IEI, length indicator and Octet 3), shall not exceed 15 digits. + +**Table 18.4.26/3GPP TS 29.018: VLR number IE** + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|----------------|------------------|---|---|---|---------|---|---|---| +| Octet 1 | IEI | | | | | | | | +| Octet 2 | Length indicator | | | | | | | | +| Octet 3 | 1 | 0 | 0 | 1 | 0 | 0 | 0 | 1 | +| Octet 4 | digit 2 | | | | digit 1 | | | | +| Octet n | digit i+1 | | | | digit i | | | | + +### 18.4.27 Global CN-Id + +The Global CN-Id consists of a PLMN-Id and a CN-Id, see 3GPP TS 23.003 [5]. The PLMN-Id consists of MCC and MNC coded according to Location Area Identification in 3GPP TS 24.008 [11]. The CN-Id is an integer defined by O&M. The least significant bit of the CN-Id field is bit 1 of octet 7 and the most significant bit is bit 8 of octet 6. If the CN-Id does not fill the field reserved for it, the rest of the bits are set to '0'. + +**Table 18.4.27/3GPP TS 29.018: Global CN-Id IE** + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|----------------|------------------------------------------------------------------------------------------------------------------------------------------------------|---|---|---|---|---|---|---| +| Octet 1 | IEI | | | | | | | | +| Octet 2 | Length indicator | | | | | | | | +| Octet 3 | PLMN-Id
Coded as octets 2 to 4 of the Location Area Identification IE, defined in 3GPP TS 24.008 [11] (not including 3GPP TS 24.008 IEI and LAC). | | | | | | | | +| Octet 4 | | | | | | | | | +| Octet 5 | | | | | | | | | +| Octet 6 | CN-Id (INTEGER 0..4095) | | | | | | | | +| Octet 7 | | | | | | | | | + +### 18.4.28 TMSI based NRI container + +The purpose of the TMSI based NRI container information element is to allow the VLR to determine whether the MS has performed inter VLR mobility or intra VLR mobility when the VLR holds a current registration of the UE that could also exist at another VLR. + +The TMSI based NRI container value consists of 10 bits which correspond to bits 23 to 14 of the valid TMSI (3GPP TS 23.236 [26]). + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|----------------|-------------------------------------------------------------------------------------------------------------------------------------------|---|---|---|---|---|---|---| +| Octet 1 | IEI | | | | | | | | +| Octet 2 | Length Indicator | | | | | | | | +| Octet 3 | The rest of the information element is coded as the value part of the Network resource identifier container IE defined in 3GPP TS 24.008. | | | | | | | | +| Octet 4 | | | | | | | | | + +**Figure 18.4.28/3GPP TS 29.018: TMSI based NRI container IE** + +### 18.4.29 Selected CN operator + +The selected CN operator information element indicates the selected core network operator by the SGSN for the non-supporting UE when CS domain is configured for gateway core network (GWCN). The selected CN operator information element is coded as shown in figure 18.4.29. + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|----------------|-------------------------------------------------------------------------------------------------------------------------------------------|---|---|---|---|---|---|---| +| Octet 1 | IEI | | | | | | | | +| Octet 2 | Length indicator | | | | | | | | +| Octet 3 | Coded as octets 2 to 4 of the Location Area Identification IE, defined in 3GPP TS 24.008 [11] (not including 3GPP TS 24.008 IEI and LAC). | | | | | | | | +| Octet 5 | | | | | | | | | + +Figure 18.4.29/3GPP TS 29.018: Selected CN operator information element + +# 19 List of system variables + +## 19.1 Timers + +This clause lists the management timers specified for the operation of the BSSAP+ protocol. All the implementation shall support the range of values specified below. The specific value of the timers shall be under the control of the operator. + +Table 19.1/3GPP TS 29.018: Management Timers + +| Timer name | Default value | Timer range | Granularity | Notes | Relation to other timers | +|------------|---------------|----------------|-------------|-------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| T5 | - | 2 s to 20 s | 100 ms | Guards the Paging procedure at the VLR. | Value is correlated to DRX parameter Split PG CYCLE (max possible = 16 s)
Default should be set acc. to max split cycle supported by the SGSN (operator choice) | +| T6-1 | - | 10 s to 90 s | 1 s | Guards the Location Update procedure. | It should be higher than 2 times the maximum transmission time in the Gs interface, plus the supervision timer of the Update Location procedure [3GPP TS 29.002 [17]] | +| T6-2 | 40 s | 5 s to 60 s | 1 s | Guards the TMSI reallocation procedure. | It should be higher than 2 times the maximum transmission time in the Gs interface, plus 4 times T3350 [3GPP TS 24.008 [11]] | +| T7 | 4 s | 1 s to 30 s | 1 s | Guards the Non-GPRS alert procedure. | None. | +| T8 | 4 s | 1 s to 30 s | 1 s | Guards the Explicit IMSI detach from GPRS services procedure. | None. | +| T9 | 4 s | 1-30 s | 1 s | Guards the Explicit IMSI detach from non-GPRS services procedure. | None. | +| T10 | 4 s | 1-30 s | 1 s | Guards the Implicit IMSI detach from non-GPRS services procedure. | None. | +| T11 | 4 s | 1-120 s | 1 s | Guards the VLR reset procedure. | None. | +| T12-1 | - | 8 - 60x384+8 s | 1 min | Controls the resetting of the 'SGSN-Reset' variable. | It should be longer than the longest Periodic RAU timer running on the SGSN, plus the transmission delay on the radio interface. | +| T12-2 | 4 s | 1-120 s | 1 sec | Guards the SGSN reset procedure. | None. | +| T14 | - | 4-36 s | 1 s | Guards the MS Information procedure. | None | + +NOTE: The Default value is the recommended value. + +## 19.2 Retry counters + +This clause lists the management retry counters specified for the operation of the BSSAP+ protocol. The values indicated are recommended values. + +**Table 19.2/3GPP TS 29.018: Management Retry counters** + +| Retry mnemonic | Retry value | Notes | +|----------------|-------------|-------------------| +| N7 | 2 | Recommended value | +| N8 | 2 | Recommended value | +| N9 | 2 | Recommended value | +| N10 | 2 | Recommended value | +| N11 | 2 | Recommended value | +| N12 | 2 | Recommended value | + +# --- 20 Procedures for Tunnelling Non-GSM Signalling + +This procedure is used to tunnel non-GSM signalling messages between an MS and a non-GSM MSC/VLR. + +## 20.1 Procedures in the non-GSM MSC/VLR + +When the non-GSM MSC/VLR has a message to be tunnelled to an MS, whose Gs state is not Gs-NULL, it shall send a BSSAP+-DOWNLINK-TUNNEL-REQUEST message to the SGSN associated with the MS. If LLC ciphering is required, the cipher request field E shall be set to 1. The Tunnel Priority field for the payload shall be set as required. On receiving a BSSAP+-UPLINK-TUNNEL-REQUEST message from an SGSN, the action taken by the non-GSM MSC/VLR is technology dependent. + +## 20.2 Procedures in the SGSN + +A message received by the SGSN from an MS or sent by the SGSN to an MS on one of the Tunneling of Messages (TOM) LLC SAPs is called a *TOM Protocol Envelope* (see 3GPP TS 44.064 [12]). The *TOM Protocol Envelope* is composed of the *TOM Protocol Header* immediately followed by a *Message Capsule*. + +Upon receipt of a *TOM Protocol Envelope* with a *TOM Protocol Header* indicating the presence of one or more non-GSM signalling messages, the SGSN shall determine the non-GSM MSC/VLR to which the *Message Capsule* in the *TOM Protocol Envelope* shall be forwarded. The SGSN shall make this determination based upon the RAI of the MS, the *TOM Protocol Discriminator* field in the *TOM Protocol Header*, and *TOM Protocol Discriminator* specific information in the remaining octets (if any) in the *TOM Protocol Header*. The SGSN shall then forward a BSSAP+-UPLINK-TUNNEL-REQUEST message to the selected non-GSM MSC/VLR with the received *Message Capsule* in the *Tunnel Payload* field. The *Protocol Discriminator* field in the BSSAP+-UPLINK-TUNNEL-REQUEST message shall be set based on the *TOM Protocol Discriminator* in the *TOM Protocol Envelope*. *Tunnel Priority* field in the BSSAP+-UPLINK-TUNNEL-REQUEST message shall be set based on the LLC SAP on which the *TOM Protocol Envelope* was received. The E field shall be set to 1 if the *TOM Protocol Envelope* was received by the LLC in ciphered form, otherwise it shall be set to 0. + +Upon receipt of a BSSAP+-DOWNLINK-TUNNEL-REQUEST message from a non-GSM MSC/VLR, the SGSN shall construct a *TOM Protocol Envelope* by mapping the *Tunnel Payload* field to the *Message Capsule* portion of the *TOM Protocol Envelope*. The *TOM Protocol Header* shall be constructed based on the *Protocol Discriminator* in the BSSAP+-DOWNLINK-TUNNEL-REQUEST message. The SGSN shall then send the *TOM Protocol Envelope* to the MS on a specific LLC SAP. That LLC SAP shall be determined by the *Tunnel Priority* field in the BSSAP+-DOWNLINK-TUNNEL-REQUEST message. LLC ciphering shall be enabled or disabled based upon the value of the *E* field in this message. If the SGSN is unable to send the *TOM Protocol Envelope* to the indicated MS for any reason, including the inability to accommodate the ciphering request as indicated in the BSSAP+-DOWNLINK-TUNNEL-REQUEST message, then it shall send a BSSAP+-MOBILE-STATUS message to the non-GSM MSC/VLR with an appropriate *Gs Cause* code. + +The association between the LLC SAPs and the *Tunnel Priority* shall be as in the following table, where 00 is top-most priority and 11 is lowest priority. + +**Table 20.1: Association between Tunnel Priority and LLC SAPs** + +| Tunnel Priority | LLC SAP | +|------------------------|----------------| +| 00 | TOM2 | +| 01 | Not defined | +| 10 | TOM8 | +| 11 | Not defined | + +# --- Annex A (informative): Change history + +| TSG CN# | Spec | Version | CR | New Version | Subject | Comment/TSG doc#/Date | +|----------|------------|---------|-------|-------------|--------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------| +| Apr 1999 | GSM 29.018 | 6.3.0 | | | | Transferred to 3GPP CN1 | +| CN#03 | 29.018 | | | 3.0.0 | | Approved at CN#03 | +| CN#4 | 29.018 | 3.0.0 | 001 | 3.1.0 | | Approved CN#4 | +| CN#5 | 29.018 | 3.1.0 | 001 | 3.2.0 | Gs Interface Changes to Support Tunnelling of non-GSM Messages | CR 001 were not implemented correctly in v 3.1.0, | +| CN#5 | 29.018 | 3.1.0 | 002 | 3.2.0 | Clarification of the null RA and other corrections. | CR 002 were not implemented correctly in v 3.1.0, | +| CN#5 | 29.018 | 3.1.0 | 003 | 3.2.0 | TMSI requested by the MSC through the Gs interface | CR 003 were not implemented correctly in v 3.1.0, | +| CN#5 | 29.018 | 3.1.0 | 005 | 3.2.0 | TMSI status indication | Approved in CN#5 as CR001r1, NP-99268 | +| CN#5 | 29.018 | 3.1.0 | 006 | 3.2.0 | Explicit IMSI detach, abnormal case SGSN side | Approved in CN#5 as CR002, NP-99268 | +| CN#5 | 29.018 | 3.1.0 | 004 | 3.2.0 | Clarify that no acknowledgement is made for TMSI deallocation | | +| CN#7 | 29.018 | 3.2.0 | 003r2 | 3.3.0 | SGSN reaction upon a RAU request after VLR failure | NP-000091 | +| CN#7 | 29.018 | 3.2.0 | 007r3 | 3.3.0 | Introduction of the Service Area Identification | NP-000101 | +| CN#7 | 29.018 | 3.2.0 | 009 | 3.3.0 | Encoding of MS classmark in LUP Request | NP-000091 | +| CN#9 | 29.018 | 3.3.0 | 010 | 3.4.0 | Reject cause in case of expiry of T6-1 | NP- 000441/ N1-000911 | +| | 29.018 | 3.4.0 | | 3.4.1 | | editorial correction of misimplementation of CR010. A single quote is missing in the cause value in clause 6.2.4 | +| CN#10 | 29.018 | 3.4.1 | 011 | 3.5.0 | Terminology corrections | Cat F, WI=TEI, NP-000674/N1-001267
Also the specification reference name is changed to 3GPP TS. | +| CN#11 | 29.018 | 3.5.0 | 012r1 | 3.6.0 | Correction of length indication for Uplink and Downlink Tunnel Request message | NP-010126
03-2001 | +| CN#11 | 29.018 | 3.6.0 | | 4.0.0 | | Decision made in TSG CN#11 plenary to issue Rel-4 version of the present document
03-2001 | +| CN#13 | 29.018 | 4.0.0 | 014 | 4.1.0 | Clarify that no acknowledgement is made for TMSI deallocation | Cat A, WI=GPRS, NP-010491 / N1-011170
09-2001 | +| CN#13 | 29.018 | 4.0.0 | 016 | 4.1.0 | Explicit IMSI detach, abnormal case SGSN side | Cat A, WI=GPRS, NP-010491 / N1-011172
09-2001 | +| CN#13 | 29.018 | 4.0.0 | 018 | 4.1.0 | Correction of the length of the Service Area Identification | Cat A, WI=GSM/UMTS Interworking, NP-010494 / N1-011174
09-2001 | +| CN#14 | 29.018 | 4.1.0 | 020 | 4.2.0 | Clarification of the periodic routing area update procedure | Cat A, WI=GPRS, NP-010646/ N1-011452
12-2001 | +| CN#14 | 29.018 | 4.1.0 | 023 | 4.2.0 | Correction of the Location Update for non-GPRS service procedure | Cat A, WI=TEI, NP-010653/ N1-011809
12-2001 | +| CN#14 | 29.018 | 4.2.0 | 024r1 | 5.0.0 | Introduction of Global CN-ID definition | Cat C, WI=IUFLEX, NP-010659/ N1-011992
12-2001 | +| CN#14 | 29.018 | 4.2.0 | 025r1 | 5.0.0 | Intra-Domain Connection of RAN Nodes to Multiple CN Nodes | Cat C, WI=IUFLEX, NP-010659/ N1-011981
12-2001 | + +| TSG CN# | Spec | Version | CR | New Version | Subject | Comment/TSG doc#/Date | +|---------|--------|---------|--------|-------------|-------------------------------------------------------------------------------------|---------------------------------------------------------------| +| CN#15 | 29.018 | 5.0.0 | 028 | 5.1.0 | Addition of Mobile Station States for UMTS | Cat A, WI=GSM/UMTS interworking, NP-020037/ N1-020201 03-2002 | +| CN#16 | 29.018 | 5.1.0 | 031 | 5.2.0 | Various clean-up of wrong references, as eg 24.008 instead of 44.018 | Cat A, WI=TEI4, NP-020224/ N1-020855 06-2002 | +| CN#18 | 29.018 | 5.2.0 | 032 | 5.3.0 | Clarification of the coding of the Global CN-Id | Cat F, WI=IUFLEX, NP-020571/ N1-021978 12-2002 | +| CN#20 | 29.018 | 5.3.0 | 033 | 5.4.0 | Addition of IMEISV to BSSAP+- LOCATION-UPDATE-REQUEST message | Cat F, WI= LATE_UE, NP-030283/ N1-030709 06-2003 | +| CN#21 | 29.018 | 5.4.0 | 038 | 5.5.0 | Aligning IMEI in 29.018 with 23.003 | Cat A, WI= TEI NP-030405 / N1-031041 09-2003 | +| CN#21 | 29.018 | 5.4.0 | 039 | 5.5.0 | Aligning IMEI in 29.018 with 23.003 | Cat F, WI= LATE_UE NP-030417 / N1-031120 09-2003 | +| CN#24 | 29.018 | 5.5.0 | 041r2 | 6.0.0 | Addition of IMEISV to Update Location Procedure for ADD function | Cat B, WI= TEI6, NP-040203 / N1-040920 06-2004 | +| CN#25 | 29.018 | 6.0.0 | 042r2 | 6.1.0 | Transfer of selected core network operator identity across Gs interface | Cat B, WI= NTShar, NP-040375/N1-041615 09-2004 | +| CN#27 | 29.018 | 6.1.0 | 043r2 | 6.2.0 | Management Based Activation Impacts | NP-050084/N1-050396, WI= OEM-Trace, Cat B 03-2005 | +| CP-29 | 29.018 | 6.2.0 | 044r3 | 7.0.0 | SGSN Gs behaviour in VLR reset situations | CP-050366/C1-051202, WI=TEI7, Cat F 09-2005 | +| CP-30 | 29.018 | 7.0.0 | 046r3 | 7.1.0 | Introduction of load re-distribution on the Gs interface | CP-050557, WI=IUFLEX, Cat A, 12-2005 | +| CP-31 | 29.018 | 7.1.0 | 048 | 7.2.0 | Paging during PS domain specific access control | CP-060114, WI=ACBOP, Cat A, 03-2006 | +| CP-34 | 29.018 | 7.2.0 | 050 | 7.3.0 | Correction of paging during PS Domain Specific Access Control (DSAC) | CP-0602121, WI=ACBOP, Cat A, 11-2006 | +| CP-41 | 29.018 | 7.3.0 | | 8.0.0 | Upgrade to Rel-8 | 09-2008 | +| CP-41 | 29.018 | 7.3.0 | | 8.0.0 | Correction of IE references in BSSAP+ messages for IMSI DETACH and GPRS DETACH | CP-080536, WI=TEI8, Cat F, 09-2008 | +| CP-42 | 29.018 | 8.0.0 | 052 | 8.1.0 | Interactions between Gs and SGs | CP-080867, WI=SAES-CSFB, Cat B, 12-2008 | +| CP-43 | 29.018 | 8.1.0 | 0053r2 | 8.2.0 | Clarifications of CSFB paging procedure in SGSN | CP-080159, WI=TEI8, Cat F, 03-2009 | +| CP-46 | 29.018 | 8.2.0 | 0055r1 | 9.0.0 | Paging signalling optimization after SGSN failure | CP-090922, WI=TEI9, Cat B, 12-2009 | +| CP-46 | 29.018 | 8.2.0 | 0056r1 | 9.0.0 | Paging clarifications | CP-090922, WI=TEI9, Cat F, 12-2009 | +| CP-49 | 29.018 | 9.0.0 | 0058r2 | 10.0.0 | SGSN State Diagram Correction | CP-100518, WI=TEI10, CAT F, 09-2010 | +| CP-49 | 29.018 | 9.0.0 | 0060r1 | 10.0.0 | Length of erroneous message | CP-100518, WI=TEI10, CAT F, 09-2010 | +| CP-49 | 29.018 | 9.0.0 | 0061r2 | 10.0.0 | Data Restoration and Gs Association Recovery | CP-100518, WI=TEI10, CAT F, 09-2010 | +| CP-49 | 29.018 | 9.0.0 | 0065 | 10.0.0 | Behavior of the recipient upon receipt of an erroneous BSSAP+-Mobile-Status message | CP-100518, WI=TEI10, CAT F, 09-2010 | +| CP-49 | 29.018 | 9.0.0 | 0063r6 | 10.0.0 | Add Timezone IE in Location Update Request | CP-100575, WI=TEI10, CAT F, 09-2010 | +| CP-50 | 29.018 | 10.0.0 | 0059r2 | 10.1.0 | SGSN Failure Handling | CP-100763, WI=TEI10, CAT F, 12-2010 | + +| TSG CN# | Spec | Version | CR | New Version | Subject | Comment/TSG doc#/Date | +|---------|--------|---------|--------|-------------|---------------------------------------------------------------------------------------------|-----------------------------------------------| +| CP-50 | 29.018 | 10.0.0 | 0064r2 | 10.1.0 | VLR Failure Handling | CP-100763, WI=TEI10, CAT F, 12-2010 | +| CP-50 | 29.018 | 10.0.0 | 0066r3 | 10.1.0 | Adding location area identity to Gs BSSAP+location update reject message | CP-100763, WI=TEI10, CAT F, 12-2010 | +| CP-50 | 29.018 | 10.0.0 | 0069r1 | 10.1.0 | Update of SGSN conditions for sending Location Update to VLR | CP-100763, WI=SAES-CSFB, CAT A, 12-2010 | +| CP-50 | 29.018 | 10.0.0 | 0070r3 | 10.1.0 | DST, Universal time and local time zone handling at the SGSN | CP-100763, WI=TEI10, CAT F, 12-2010 | +| CP-50 | 29.018 | 10.0.0 | 0071 | 10.1.0 | Paging or signaling via lu interface | CP-100763, WI=TEI10, CAT F, 12-2010 | +| CP-51 | 29.018 | 10.1.0 | 0073r1 | 10.2.0 | Explicit IMSI detach from GPRS services triggered by PRAU reject | CP-110197, WI=TEI10, CAT F, 03-2011 | +| CP-51 | 29.018 | 10.1.0 | 0074r2 | 10.2.0 | Implicit detach handling for GPRS and non-GPRS services | CP-110197, WI=TEI10, CAT F, 03-2011 | +| CP-51 | 29.018 | 10.1.0 | 0075 | 10.2.0 | Timer handling in detach response | CP-110197, WI=TEI10, CAT F, 03-2011 | +| CP-51 | 29.018 | 10.1.0 | 0076 | 10.2.0 | Correction on GPRS detach cause | CP-110197, WI=TEI10, CAT F, 03-2011 | +| CP-51 | 29.018 | 10.1.0 | 0077 | 10.2.0 | VLR behavior in Gs NULL state | CP-110197, WI=TEI10, CAT F, 03-2011 | +| CP-52 | 29.018 | 10.2.0 | 0079r1 | 10.3.0 | Detach handling for Implicit IMSI detach from non-GPRS services | CP-110464, WI=TEI10, CAT F, 06-2011 | +| CP-52 | 29.018 | 10.2.0 | 0081r1 | 10.3.0 | Updating IMSI detach flag during explicit IMSI detach for non-GPRS services | CP-110464, WI=TEI10, CAT F, 06-2011 | +| CP-52 | 29.018 | 10.2.0 | 0084 | 10.3.0 | SGSN states corrections | CP-110466, WI=TEI10, CAT F, 06-2011 | +| CP-53 | 29.018 | 10.3.0 | 0080r3 | 10.4.0 | New Location Update Request during TMSI reallocation procedure | CP-110683, WI=TEI10, CAT F, 09-2011 | +| CP-53 | 29.018 | 10.3.0 | 0086r1 | 10.4.0 | Correction on detach in SGs-NULL state for non-GPRS service | CP-110682, WI=TEI10, CAT F, 09-2011 | +| CP-53 | 29.018 | 10.4.0 | 0082r3 | 11.0.0 | Abnormal case for Gs location update procedure | CP-110694, WI=TEI11, CAT F, 09-2011 | +| CP-53 | 29.018 | 10.4.0 | 0088 | 11.0.0 | References update | CP-110695, WI=TEI11, CAT F, 09-2011 | +| CP-54 | 29.018 | 11.0.0 | 0092r4 | 11.1.0 | Old LAI in Gs interface | CP-110915, WI=SAES-CSFB, CAT A, 12-2011 | +| CP-55 | 29.018 | 11.1.0 | 0094r1 | 11.2.0 | Correct the behaviors of the VLR during the implicit IMSI detach procedure | CP-120125, WI=TEI11, CAT F, 03-2012 | +| CP-56 | 29.018 | 11.2.0 | 0100r1 | 11.3.0 | Gs update SGSN receiving Detach Notification from MME | CP-120293, WI=SAES-CSFB, CAT A, 06-2012 | +| CP-56 | 29.018 | 11.2.0 | 0101r3 | 11.3.0 | Gs Support for MSC in Pool to avoid dual VLR registration | CP-120309, WI=TEI11, CAT F, 06-2012 | +| CP-56 | 29.018 | 11.2.0 | 0105r3 | 11.3.0 | Check of NAM to avoid unnecessary signalling and misalignment with stage 2 | CP-120309, WI=TEI11, CAT F, 06-2012 | +| CP-57 | 29.018 | 11.3.0 | 0107r2 | 11.4.0 | Avoiding dual VLR registration for legacy UEs | CP-120584, WI=TEI11, Cat F, 09-2012 | +| CP-57 | 29.018 | 11.3.0 | 0112r1 | 11.4.0 | EMM Combined UE Waiting Flag set for IMSI detach triggered by last PDP context deactivation | CP-120572, WI=SAES-CSFB, Cat A, 09-2012 | +| CP-57 | 29.018 | 11.3.0 | 0095r7 | 11.4.0 | SMS-only Support for PS-only Subscription | CP-120650, WI=SIMTC-PS Only, Cat B, 09-2012 | +| CP-58 | 29.018 | 11.4.0 | 0113r3 | 11.5.0 | Handling of VLR failure without restart | CP-120807, WI=SAES2-CSFB, Cat B, 12-2012 | +| CP-59 | 29.018 | 11.5.0 | 0115 | 11.6.0 | Gs Interface applicability in case of SMS in SGSN | CP-130108, WI=SIMTC-PS Only, Cat F, 03-2013 | +| CP-59 | 29.018 | 11.5.0 | 0116r1 | 11.6.0 | CS domain operator selection in GWCN | CP-130123, WI=Full_MOCN-GERAN, Cat F, 03-2013 | +| CP-62 | 29.018 | 11.6.0 | 0130r3 | 11.7.0 | UE paging after TMSI reallocation procedure abort | CP-130745, WI=TEI11, Cat F, 12-2013 | + diff --git a/marked/Rel-11/29_series/29078/1a85642ed2356d183ce598f2c8b3ee8b_img.jpg b/marked/Rel-11/29_series/29078/1a85642ed2356d183ce598f2c8b3ee8b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5708e0996cfc438176288550b58f239db4ea85d8 --- /dev/null +++ b/marked/Rel-11/29_series/29078/1a85642ed2356d183ce598f2c8b3ee8b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:78fe13204e51f67cacd8735ae1fb7bf61670d04fc2fbd1f29eefb4f52356382f +size 28986 diff --git a/marked/Rel-11/29_series/29078/3da1a07cb87051bf616c9876db958cf0_img.jpg b/marked/Rel-11/29_series/29078/3da1a07cb87051bf616c9876db958cf0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c4a955abd676645984d6f2f80b0f6924036aeaeb --- /dev/null +++ b/marked/Rel-11/29_series/29078/3da1a07cb87051bf616c9876db958cf0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1bfc7ce9353f7e7ff12afb994fa8ad7a7c339107af2ffb76291757fdd5344494 +size 15703 diff --git a/marked/Rel-11/29_series/29078/552ca016af3d6240648ab5a2cad97f60_img.jpg b/marked/Rel-11/29_series/29078/552ca016af3d6240648ab5a2cad97f60_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..63d0ebb722f1961d9d469eebd58ffd3f4891a110 --- /dev/null +++ b/marked/Rel-11/29_series/29078/552ca016af3d6240648ab5a2cad97f60_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:12a9696282ec3794e74c9b4d3e562462e52b11d5fc95e9d9ca832fc7bfb2d786 +size 39713 diff --git a/marked/Rel-11/29_series/29078/5793a44ffdadd039928e2f9fe6daae06_img.jpg b/marked/Rel-11/29_series/29078/5793a44ffdadd039928e2f9fe6daae06_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ea8608e1db7be837273b95e32d13ac5afef95994 --- /dev/null +++ b/marked/Rel-11/29_series/29078/5793a44ffdadd039928e2f9fe6daae06_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3e4019e0c5bd740dcc4555f277ba4f688cca488ae943d9bc8adaa75c5f3bd95e +size 18250 diff --git a/marked/Rel-11/29_series/29078/75e4b78ee25f885d73120e3066a5253e_img.jpg b/marked/Rel-11/29_series/29078/75e4b78ee25f885d73120e3066a5253e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5c697dab77b8ee5fabe347d95ce93ac3fbb70d3b --- /dev/null +++ b/marked/Rel-11/29_series/29078/75e4b78ee25f885d73120e3066a5253e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e515cae3ca872687b64e142698736dda11b30b3bb035bb0757ff78661819f378 +size 17601 diff --git a/marked/Rel-11/29_series/29078/79e1709a7317ead45379cbb8ff3ba802_img.jpg b/marked/Rel-11/29_series/29078/79e1709a7317ead45379cbb8ff3ba802_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..235c530b3002b4ba809d2adf90fff4d97bb5d449 --- /dev/null +++ b/marked/Rel-11/29_series/29078/79e1709a7317ead45379cbb8ff3ba802_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cdce930de22bef5282b17022803b68448bc40b901e739410093d3c9417505328 +size 26109 diff --git a/marked/Rel-11/29_series/29078/90ddb84c323b956e2d50a54d3f870566_img.jpg b/marked/Rel-11/29_series/29078/90ddb84c323b956e2d50a54d3f870566_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..574e6509f982f62b376519c0a4e0fc06a9e357f1 --- /dev/null +++ b/marked/Rel-11/29_series/29078/90ddb84c323b956e2d50a54d3f870566_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e05bfc63874ab24cfdd440e2a8438f598a805f889388bd69e7d9ca77bf357066 +size 82175 diff --git a/marked/Rel-11/29_series/29078/a24e89a6fe9bb70c83f8bf5202baba95_img.jpg b/marked/Rel-11/29_series/29078/a24e89a6fe9bb70c83f8bf5202baba95_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a4c81b9c3c4b4b2cd425de13505845de2664dfb4 --- /dev/null +++ b/marked/Rel-11/29_series/29078/a24e89a6fe9bb70c83f8bf5202baba95_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:689d2936b49dd0e6b21392f71f508baca1b106750e526e64814ba46075eda8ae +size 39286 diff --git a/marked/Rel-11/29_series/29078/b2ea162a0f53d5e0504b7d28346e0754_img.jpg b/marked/Rel-11/29_series/29078/b2ea162a0f53d5e0504b7d28346e0754_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..72e6718e31297768d5e279b1fabc203bd2d1b8f4 --- /dev/null +++ b/marked/Rel-11/29_series/29078/b2ea162a0f53d5e0504b7d28346e0754_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a69dbea4d9dbca99fd550317c1d34e72c406110b514cb13b41e4944a8a189404 +size 23164 diff --git a/marked/Rel-11/29_series/29078/d9c0a780cd22626253dab4aa41699e2f_img.jpg b/marked/Rel-11/29_series/29078/d9c0a780cd22626253dab4aa41699e2f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..507fa4d4e3764973a764bf7c494671b3c32fbcda --- /dev/null +++ b/marked/Rel-11/29_series/29078/d9c0a780cd22626253dab4aa41699e2f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:80884669a6d6e9e0fbef7e02148cf239e0bb679a722750f550dc12c2f9a84655 +size 18894 diff --git a/marked/Rel-11/29_series/29078/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg b/marked/Rel-11/29_series/29078/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1a3a988631dc824795162e099cf93b01e531dec2 --- /dev/null +++ b/marked/Rel-11/29_series/29078/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cd9127c2c6291a581bd93310083a098c6b69f35fa7280ee20ce6ec750a89478c +size 25720 diff --git a/marked/Rel-11/29_series/29078/eb03559a4d92ea9ebd63ea9be663c50a_img.jpg b/marked/Rel-11/29_series/29078/eb03559a4d92ea9ebd63ea9be663c50a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0da0eee53f7f5178959e83211e04d9a6e276ead3 --- /dev/null +++ b/marked/Rel-11/29_series/29078/eb03559a4d92ea9ebd63ea9be663c50a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:995801185f4c65e128ea79ad0b311fddb199c20654f3837ac3d89471bee40fa1 +size 14937 diff --git a/marked/Rel-11/29_series/29078/f7d969388c4f7e30cd04a061314bfa0e_img.jpg b/marked/Rel-11/29_series/29078/f7d969388c4f7e30cd04a061314bfa0e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..520dc5b99326308fba18f1d378b71bac8b000cff --- /dev/null +++ b/marked/Rel-11/29_series/29078/f7d969388c4f7e30cd04a061314bfa0e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:54a09fde5401308d91b3ef05277eb3a9e5b0080aaf421b08b507e2b5f62766f5 +size 39815 diff --git a/marked/Rel-11/29_series/29078/raw.md b/marked/Rel-11/29_series/29078/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..86b93f9c87e2f96b6f9c94a0e55af45d871ed526 --- /dev/null +++ b/marked/Rel-11/29_series/29078/raw.md @@ -0,0 +1,13208 @@ + + + + +**Error:** + +**2** + +**Error: Reference source not** + +# Contents + +| | | +|--------------------------------------------------------------------------------------------------------------|----| +| Foreword..... | 14 | +| 1 Scope..... | 15 | +| 2 References..... | 15 | +| 2.1 Specifications used for IMPORTS for CAP..... | 17 | +| 3 Abbreviations..... | 18 | +| 4 Interface specification for telecommunication services..... | 19 | +| 4.1 General..... | 19 | +| 4.1.1 Definition methodology..... | 19 | +| 4.1.2 Example physical scenarios..... | 20 | +| 4.1.3 CAP protocol architecture..... | 26 | +| 4.1.4 Compatibility mechanisms used for CAP..... | 27 | +| 4.1.4.1 Introduction..... | 27 | +| 4.1.4.2 Definition of CAP compatibility mechanisms..... | 28 | +| 4.1.4.2.1 Compatibility mechanism for interworking of CAP with ETSI CS2 Core INAP and ITU-T Q.1228 INAP..... | 28 | +| 4.1.4.2.2 Procedures for major additions to CAP..... | 28 | +| 4.1.4.2.3 Procedures for minor additions to CAP..... | 28 | +| 4.1.4.2.4 Procedures for inclusion of network specific additions to CAP..... | 28 | +| 4.1.5 Definition and usage of LegID..... | 28 | +| 4.1.5.1 Definition of LegID..... | 28 | +| 4.1.5.2 Allocation of LegID..... | 29 | +| 4.2 SACF/MACF rules..... | 29 | +| 4.2.1 Reflection of TC AC..... | 29 | +| 4.2.2 Sequential/parallel execution of operations..... | 29 | +| 5 Common CAP Types..... | 29 | +| 5.1 Data types..... | 29 | +| 5.2 Error types..... | 49 | +| 5.3 Operation codes..... | 51 | +| 5.4 Error codes..... | 53 | +| 5.5 Classes..... | 53 | +| 5.6 Object Identifiers (IDs)..... | 57 | +| 5.7 User Abort Data..... | 60 | +| 6 Circuit Switched Call Control..... | 61 | +| 6.1 gsmSSF/CCF - gsmSCF Interface..... | 61 | +| 6.1.1 Operations and arguments..... | 61 | +| 6.1.2 gsmSSF/gsmSCF packages, contracts and ACs..... | 73 | +| 6.1.2.1 gsmSSF/gsmSCF ASN.1 module..... | 73 | +| 6.2 gsmSCF/gsmSRF interface..... | 81 | +| 6.2.1 gsmSCF/gsmSRF operations and arguments..... | 81 | +| 6.2.2 gsmSRF/gsmSCF contracts, packages and ACs..... | 83 | +| 6.2.2.1 gsmSRF/gsmSCF ASN.1 modules..... | 83 | +| 7 SMS Control..... | 85 | +| 7.1 SMS operations and arguments..... | 85 | +| 7.1.1 Operation timers..... | 89 | +| 7.2 SMS contracts, packages and ACs..... | 89 | +| 7.2.1 smsSSF/gsmSCF ASN.1 module..... | 89 | +| 8 GPRS Control..... | 92 | +| 8.1 gsmSCF/gprsSSF operations and arguments..... | 92 | +| 8.1.1 GPRS Reference Number..... | 97 | +| 8.1.2 Operation timers..... | 98 | +| 8.2 gsmSCF/gprsSSF contracts, packages and ACs..... | 99 | +| 8.2.1 gprsSSF/gsmSCF ASN.1 module..... | 99 | + +| | | | +|------------|--------------------------------------------------|-----| +| 9 | Application Entity procedures..... | 102 | +| 10 | Error procedures..... | 103 | +| 10.1 | Operation related error procedures..... | 103 | +| 10.1.1 | Canceled..... | 103 | +| 10.1.1.1 | General Description..... | 103 | +| 10.1.1.1.1 | Error description..... | 103 | +| 10.1.1.2 | Operations gsmSCF $\textcircled{/}$ gsmSRF..... | 103 | +| 10.1.2 | CancelFailed..... | 104 | +| 10.1.2.1 | General description..... | 104 | +| 10.1.2.1.1 | Error description..... | 104 | +| 10.1.2.2 | Operations gsmSCF $\textcircled{/}$ gsmSRF..... | 104 | +| 10.1.3 | ETCFailed..... | 104 | +| 10.1.3.1 | General description..... | 104 | +| 10.1.3.1.1 | Error description..... | 104 | +| 10.1.3.2 | Operations gsmSCF $\textcircled{/}$ gsmSSF..... | 104 | +| 10.1.4 | ImproperCallerResponse..... | 105 | +| 10.1.4.1 | General description..... | 105 | +| 10.1.4.1.1 | Error description..... | 105 | +| 10.1.4.2 | Operations gsmSCF $\textcircled{/}$ gsmSRF..... | 105 | +| 10.1.5 | MissingCustomerRecord..... | 105 | +| 10.1.5.1 | General description..... | 105 | +| 10.1.5.1.1 | Error description..... | 105 | +| 10.1.5.2 | Operations gsmSSF $\textcircled{/}$ gsmSCF..... | 105 | +| 10.1.5.3 | Operations gsmSRF $\textcircled{/}$ gsmSCF..... | 106 | +| 10.1.5.4 | Operations smsSSF $\textcircled{/}$ gsmSCF..... | 106 | +| 10.1.5.5 | Operations gprsSSF $\textcircled{/}$ gsmSCF..... | 106 | +| 10.1.6 | MissingParameter..... | 107 | +| 10.1.6.1 | General description..... | 107 | +| 10.1.6.1.1 | Error description..... | 107 | +| 10.1.6.2 | Operations gsmSCF $\textcircled{/}$ gsmSSF..... | 107 | +| 10.1.6.3 | Operations gsmSSF $\textcircled{/}$ gsmSCF..... | 107 | +| 10.1.6.4 | Operations gsmSCF $\textcircled{/}$ gsmSRF..... | 107 | +| 10.1.6.5 | Operations gsmSRF $\textcircled{/}$ gsmSCF..... | 108 | +| 10.1.6.6 | Operations smsSSF $\textcircled{/}$ gsmSCF..... | 108 | +| 10.1.6.7 | Operations gsmSCF $\textcircled{/}$ smsSSF..... | 108 | +| 10.1.6.8 | Operations gprsSSF $\textcircled{/}$ gsmSCF..... | 108 | +| 10.1.6.9 | Operations gsmSCF $\textcircled{/}$ gprsSSF..... | 109 | +| 10.1.7 | ParameterOutOfRange..... | 109 | +| 10.1.7.1 | General description..... | 109 | +| 10.1.7.1.1 | Error description..... | 109 | +| 10.1.7.2 | Operations gsmSCF $\textcircled{/}$ gsmSSF..... | 109 | +| 10.1.7.3 | Operations gsmSSF $\textcircled{/}$ gsmSCF..... | 109 | +| 10.1.7.4 | Operations gsmSCF $\textcircled{/}$ gsmSRF..... | 109 | +| 10.1.7.5 | Operations smsSSF $\textcircled{/}$ gsmSCF..... | 109 | +| 10.1.7.6 | Operations gsmSCF $\textcircled{/}$ smsSSF..... | 109 | +| 10.1.7.7 | Operations gprsSSF $\textcircled{/}$ gsmSCF..... | 109 | +| 10.1.7.8 | Operations gsmSCF $\textcircled{/}$ gprsSSF..... | 110 | +| 10.1.8 | RequestedInfoError..... | 110 | +| 10.1.8.1 | General description..... | 110 | +| 10.1.8.1.1 | Error description..... | 110 | +| 10.1.8.2 | Operations gsmSCF $\textcircled{/}$ gsmSSF..... | 110 | +| 10.1.9 | SystemFailure..... | 110 | +| 10.1.9.1 | General description..... | 110 | +| 10.1.9.1.1 | Error description..... | 110 | +| 10.1.9.2 | Operations gsmSCF $\textcircled{/}$ gsmSSF..... | 110 | +| 10.1.9.3 | Operations gsmSSF $\textcircled{/}$ gsmSCF..... | 110 | + +| | | | +|-------------|-------------------------------------------------------------------------------------------------|-----| +| 10.1.9.4 | Operations gsmSCF $\textcircled{/}$ gsmSRF..... | 110 | +| 10.1.9.5 | Operations gsmSRF $\textcircled{/}$ gsmSCF..... | 110 | +| 10.1.9.6 | Operations smsSSF $\textcircled{/}$ gsmSCF..... | 110 | +| 10.1.9.7 | Operations gsmSCF $\textcircled{/}$ smsSSF..... | 110 | +| 10.1.9.8 | Operations gprsSSF $\textcircled{/}$ gsmSCF..... | 110 | +| 10.1.9.9 | Operations gsmSCF $\textcircled{/}$ gprsSSF..... | 111 | +| 10.1.10 | TaskRefused..... | 111 | +| 10.1.10.1 | General description..... | 111 | +| 10.1.10.1.1 | Error description..... | 111 | +| 10.1.10.2 | Operations gsmSCF $\textcircled{/}$ gsmSSF..... | 111 | +| 10.1.10.3 | Operations gsmSSF $\textcircled{/}$ gsmSCF..... | 111 | +| 10.1.10.4 | Operations gsmSCF $\textcircled{/}$ gsmSRF..... | 111 | +| 10.1.10.5 | Operations gsmSRF $\textcircled{/}$ gsmSCF..... | 111 | +| 10.1.10.6 | Operations smsSSF $\textcircled{/}$ gsmSCF..... | 111 | +| 10.1.10.7 | Operations gsmSCF $\textcircled{/}$ smsSSF..... | 111 | +| 10.1.10.8 | Operations gprsSSF $\textcircled{/}$ gsmSCF..... | 111 | +| 10.1.10.9 | Operations gsmSCF $\textcircled{/}$ gprsSSF..... | 111 | +| 10.1.11 | UnavailableResource..... | 112 | +| 10.1.11.1 | General description..... | 112 | +| 10.1.11.1.1 | Error description..... | 112 | +| 10.1.11.2 | Operations gsmSCF $\textcircled{/}$ gsmSRF..... | 112 | +| 10.1.12 | UnexpectedComponentSequence..... | 112 | +| 10.1.12.1 | General description..... | 112 | +| 10.1.12.1.1 | Error description..... | 112 | +| 10.1.12.2 | Operations gsmSCF $\textcircled{/}$ gsmSSF..... | 112 | +| 10.1.12.3 | Operations gsmSSF $\textcircled{/}$ gsmSCF..... | 112 | +| 10.1.12.4 | Operations gsmSCF $\textcircled{/}$ gsmSRF (applicable for direct gsmSCF-gsmSRF case only)..... | 112 | +| 10.1.12.5 | Operations gsmSRF $\textcircled{/}$ gsmSCF..... | 112 | +| 10.1.12.6 | Operations smsSSF $\textcircled{/}$ gsmSCF..... | 113 | +| 10.1.12.7 | Operations gsmSCF $\textcircled{/}$ smsSSF..... | 113 | +| 10.1.12.8 | Operations gprsSSF $\textcircled{/}$ gsmSCF..... | 113 | +| 10.1.12.9 | Operations gsmSCF $\textcircled{/}$ gprsSSF..... | 113 | +| 10.1.13 | UnexpectedDataValue..... | 113 | +| 10.1.13.1 | General description..... | 113 | +| 10.1.13.1.1 | Error description..... | 113 | +| 10.1.13.2 | Operations gsmSCF $\textcircled{/}$ gsmSSF..... | 113 | +| 10.1.13.3 | Operations gsmSSF $\textcircled{/}$ gsmSCF..... | 113 | +| 10.1.13.4 | Operations gsmSCF $\textcircled{/}$ gsmSRF..... | 113 | +| 10.1.13.5 | Operations gsmSRF $\textcircled{/}$ gsmSCF..... | 113 | +| 10.1.13.6 | Operations smsSSF $\textcircled{/}$ gsmSCF..... | 114 | +| 10.1.13.7 | Operations gsmSCF $\textcircled{/}$ smsSSF..... | 114 | +| 10.1.13.8 | Operations gprsSSF $\textcircled{/}$ gsmSCF..... | 114 | +| 10.1.13.9 | Operations gsmSCF $\textcircled{/}$ gprsSSF..... | 114 | +| 10.1.14 | UnexpectedParameter..... | 114 | +| 10.1.14.1 | General description..... | 114 | +| 10.1.14.1.1 | Error description..... | 114 | +| 10.1.14.2 | Operations gsmSCF $\textcircled{/}$ gsmSSF..... | 114 | +| 10.1.14.3 | Operations gsmSSF $\textcircled{/}$ gsmSCF..... | 114 | +| 10.1.14.4 | Operations gsmSCF $\textcircled{/}$ gsmSRF..... | 114 | +| 10.1.14.5 | Operations gsmSRF $\textcircled{/}$ gsmSCF..... | 114 | +| 10.1.14.6 | Operations smsSSF $\textcircled{/}$ gsmSCF..... | 114 | +| 10.1.14.7 | Operations gsmSCF $\textcircled{/}$ smsSSF..... | 114 | +| 10.1.14.8 | Operations gprsSSF $\textcircled{/}$ gsmSCF..... | 114 | +| 10.1.14.9 | Operations gsmSCF $\textcircled{/}$ gprsSSF..... | 115 | + +| | | | +|-------------|----------------------------------------------------------------------|-----| +| 10.1.15 | UnknownLegID..... | 115 | +| 10.1.15.1 | General description..... | 115 | +| 10.1.15.1.1 | Error description..... | 115 | +| 10.1.15.2 | Operations gsmSCF ⌂ gsmSSF..... | 115 | +| 10.1.16 | UnknownCSID..... | 115 | +| 10.1.16.1 | General description..... | 115 | +| 10.1.16.1.1 | Error description..... | 115 | +| 10.1.16.2 | Operations gsmSCF ⌂ gsmSSF..... | 115 | +| 10.1.17 | UnknownPDPID..... | 115 | +| 10.1.17.1 | General description..... | 115 | +| 10.1.17.1.1 | Error description..... | 115 | +| 10.1.17.2 | Operations gprsSSF ⌂ gsmSCF..... | 115 | +| 10.1.17.3 | Operations gsmSCF ⌂ gprsSSF..... | 115 | +| 10.2 | Entity related error procedures..... | 115 | +| 10.2.1 | Expiration of Tssf..... | 116 | +| 10.2.1.1 | General description..... | 116 | +| 10.2.1.1.1 | Error description..... | 116 | +| 10.2.1.2 | Procedures gsmSSF ⌂ gsmSCF..... | 116 | +| 10.2.1.3 | Procedures gprsSSF ⌂ gsmSCF..... | 116 | +| 10.2.1.4 | Procedures smsSSF ⌂ gsmSCF..... | 116 | +| 10.2.2 | Expiration of Tsrf..... | 117 | +| 10.2.2.1 | General Description..... | 117 | +| 10.2.2.1.1 | Error description..... | 117 | +| 10.2.2.2 | Procedures description..... | 117 | +| 11 | Detailed operation procedures for circuit switched call control..... | 117 | +| 11.1 | ActivityTest procedure..... | 117 | +| 11.1.1 | General description..... | 117 | +| 11.1.1.1 | Parameters..... | 117 | +| 11.1.2 | Responding entity (gsmSSF, gsmSRF or assist gsmSSF)..... | 117 | +| 11.1.2.1 | Normal procedure..... | 117 | +| 11.1.2.2 | Error handling..... | 118 | +| 11.2 | ApplyCharging procedure..... | 118 | +| 11.2.1 | General description..... | 118 | +| 11.2.1.1 | Parameters..... | 118 | +| 11.2.2 | Responding entity (gsmSSF)..... | 119 | +| 11.2.2.1 | Normal procedure..... | 119 | +| 11.2.2.2 | Error handling..... | 120 | +| 11.3 | ApplyChargingReport procedure..... | 120 | +| 11.3.1 | General description..... | 120 | +| 11.3.1.1 | Parameters..... | 121 | +| 11.3.2 | Invoking entity (gsmSSF)..... | 122 | +| 11.3.2.1 | Normal procedure..... | 122 | +| 11.3.2.2 | Error handling..... | 122 | +| 11.4 | AssistRequestInstructions procedure..... | 122 | +| 11.4.1 | General description..... | 122 | +| 11.4.1.1 | Parameters..... | 122 | +| 11.4.2 | Invoking entity (gsmSSF/gsmSRF)..... | 123 | +| 11.4.2.1 | Normal procedure..... | 123 | +| 11.4.2.2 | Error handling..... | 123 | +| 11.5 | CallGap procedure..... | 123 | +| 11.5.1 | General description..... | 123 | +| 11.5.1.1 | Parameters..... | 123 | +| 11.5.2 | Responding entity (gsmSSF)..... | 125 | +| 11.5.2.1 | Normal procedure..... | 125 | +| 11.5.2.2 | Error handling..... | 127 | +| 11.6 | CallInformationReport procedure..... | 127 | +| 11.6.1 | General description..... | 127 | +| 11.6.1.1 | Parameters..... | 127 | +| 11.6.2 | Invoking entity (gsmSSF)..... | 127 | + +| | | | +|-----------|--------------------------------------------------------|-----| +| 11.6.2.1 | Normal procedure..... | 127 | +| 11.6.2.2 | Error handling..... | 128 | +| 11.7 | CallInformationRequest procedure..... | 128 | +| 11.7.1 | General description..... | 128 | +| 11.7.1.1 | Parameters..... | 128 | +| 11.7.2 | Responding entity (gsmSSF)..... | 128 | +| 11.7.2.1 | Normal procedure..... | 128 | +| 11.7.2.2 | Error handling..... | 129 | +| 11.8 | Cancel procedure..... | 129 | +| 11.8.1 | General description..... | 129 | +| 11.8.1.1 | Parameters..... | 129 | +| 11.8.2 | Responding entity (gsmSRF)..... | 129 | +| 11.8.2.1 | Normal procedure..... | 129 | +| 11.8.2.2 | Error handling..... | 130 | +| 11.8.3 | Responding entity (gsmSSF)..... | 130 | +| 11.8.3.1 | Normal procedure..... | 130 | +| 11.8.3.2 | Error handling..... | 130 | +| 11.8A | CollectInformation Procedure..... | 130 | +| 11.8A.1 | General description..... | 130 | +| 11.8A.1.1 | Parameters..... | 130 | +| 11.8A.2 | Responding entity (gsmSSF)..... | 130 | +| 11.8A.2.1 | Normal procedure..... | 130 | +| 11.8A.2.2 | Error handling..... | 131 | +| 11.9 | Connect procedure..... | 131 | +| 11.9.1 | General description..... | 131 | +| 11.9.1.1 | Parameters..... | 131 | +| 11.9.2 | Responding entity (gsmSSF)..... | 132 | +| 11.9.2.1 | Normal procedure..... | 132 | +| 11.9.2.2 | Error handling..... | 133 | +| 11.10 | ConnectToResource procedure..... | 133 | +| 11.10.1 | General description..... | 133 | +| 11.10.1.1 | Parameters..... | 133 | +| 11.10.2 | Responding entity (gsmSSF)..... | 133 | +| 11.10.2.1 | Normal procedure..... | 133 | +| 11.10.2.2 | Error handling..... | 134 | +| 11.11 | Continue procedure..... | 134 | +| 11.11.1 | General description..... | 134 | +| 11.11.1.1 | Parameters..... | 134 | +| 11.11.2 | Responding entity (gsmSSF)..... | 134 | +| 11.11.2.1 | Normal procedure..... | 134 | +| 11.11.2.2 | Error handling..... | 134 | +| 11.12 | ContinueWithArgument Procedure..... | 134 | +| 11.12.1 | General description..... | 134 | +| 11.12.1.1 | Parameters..... | 135 | +| 11.12.2 | Responding entity (gsmSSF)..... | 136 | +| 11.12.2.1 | Normal procedure..... | 136 | +| 11.12.2.2 | Error handling..... | 136 | +| 11.13 | DisconnectForwardConnection procedure..... | 136 | +| 11.13.1 | General Description..... | 136 | +| 11.13.1.1 | Parameters..... | 136 | +| 11.13.2 | Responding entity (gsmSSF)..... | 137 | +| 11.13.2.1 | Normal procedure..... | 137 | +| 11.13.2.2 | Error handling..... | 137 | +| 11.14 | DisconnectForwardConnectionWithArgument procedure..... | 137 | +| 11.14.1 | General Description..... | 137 | +| 11.14.1.1 | Parameters..... | 137 | +| 11.14.2 | Responding entity (gsmSSF)..... | 137 | +| 11.14.2.1 | Normal procedure..... | 137 | +| 11.14.2.2 | Error handling..... | 138 | +| 11.15 | DisconnectLeg procedure..... | 138 | +| 11.15.1 | General Description..... | 138 | + +| | | | +|-------------|---------------------------------------------|-----| +| 11.15.1.1 | Parameters..... | 138 | +| 11.15.2 | Responding entity (gsmSSF)..... | 138 | +| 11.15.2.1 | Normal procedure..... | 138 | +| 11.15.2.2 | Error handling..... | 139 | +| 11.16 | EntityReleased procedure..... | 139 | +| 11.16.1 | General Description..... | 139 | +| 11.16.1.1 | Parameters..... | 139 | +| 11.16.2 | Invoking entity (gsmSSF)..... | 139 | +| 11.16.2.1 | Normal procedure..... | 139 | +| 11.16.2.2 | Error handling..... | 139 | +| 11.17 | EstablishTemporaryConnection procedure..... | 140 | +| 11.17.1 | General Description..... | 140 | +| 11.17.1.1 | Parameters..... | 140 | +| 11.17.2 | Responding entity (gsmSSF)..... | 141 | +| 11.17.2.1 | Normal procedure..... | 141 | +| 11.17.2.2 | Error handling..... | 141 | +| 11.18 | EventReportBCSM procedure..... | 141 | +| 11.18.1 | General description..... | 141 | +| 11.18.1.1 | Parameters..... | 141 | +| 11.18.2 | Invoking entity (gsmSSF)..... | 143 | +| 11.18.2.1 | Normal procedure..... | 143 | +| 11.18.2.2 | Error handling..... | 143 | +| 11.19 | FurnishChargingInformation procedure..... | 144 | +| 11.19.1 | General description..... | 144 | +| 11.19.1.1 | Parameters..... | 144 | +| 11.19.2 | Responding entity (gsmSSF)..... | 144 | +| 11.19.2.1 | Normal procedure..... | 144 | +| 11.19.2.2 | Error handling..... | 145 | +| 11.20 | InitialDP procedure..... | 145 | +| 11.20.1 | General description..... | 145 | +| 11.20.1.1 | Parameters..... | 145 | +| 11.20.2 | Invoking entity (gsmSSF)..... | 148 | +| 11.20.2.1 | Normal procedure..... | 148 | +| 11.20.2.2 | Error handling..... | 149 | +| 11.21 | InitiateCallAttempt procedure..... | 149 | +| 11.21.1 | General Description..... | 149 | +| 11.21.1.1 | Parameters..... | 149 | +| 11.21.1.1.1 | Argument Parameters..... | 149 | +| 11.21.1.1.2 | Result Parameters..... | 149 | +| 11.21.2 | Responding entity (gsmSSF)..... | 150 | +| 11.21.2.1 | Normal procedure..... | 150 | +| 11.21.2.2 | Error handling..... | 150 | +| 11.22 | MoveLeg procedure..... | 150 | +| 11.22.1 | General Description..... | 150 | +| 11.22.1.1 | Parameters..... | 150 | +| 11.22.2 | Responding entity (gsmSSF)..... | 150 | +| 11.22.2.1 | Normal procedure..... | 150 | +| 11.22.2.2 | Error handling..... | 151 | +| 11.23 | PlayAnnouncement procedure..... | 151 | +| 11.23.1 | General description..... | 151 | +| 11.23.1.1 | Parameters..... | 151 | +| 11.23.2 | Responding entity (gsmSRF)..... | 152 | +| 11.23.2.1 | Normal procedure..... | 152 | +| 11.23.2.2 | Error handling..... | 153 | +| 11.24 | PlayTone procedure..... | 153 | +| 11.24.1 | General description..... | 153 | +| 11.24.1.1 | Parameters..... | 153 | +| 11.24.2 | Responding entity (gsmSSF)..... | 153 | +| 11.24.2.1 | Normal procedure..... | 153 | +| 11.24.2.2 | Error handling..... | 154 | +| 11.25 | PromptAndCollectUserInfo procedure..... | 154 | + +| | | | +|-----------|----------------------------------------------------|-----| +| 11.25.1 | General description..... | 154 | +| 11.25.1.1 | Parameters..... | 154 | +| 11.25.2 | Responding entity (gsmSRF)..... | 157 | +| 11.25.2.1 | Normal procedure..... | 157 | +| 11.25.2.2 | Error handling..... | 157 | +| 11.26 | ReleaseCall procedure..... | 158 | +| 11.26.1 | General description..... | 158 | +| 11.26.1.1 | Parameters..... | 158 | +| 11.26.2 | Responding entity (gsmSSF)..... | 158 | +| 11.26.2.1 | Normal procedure..... | 158 | +| 11.26.2.2 | Error handling..... | 158 | +| 11.27 | RequestReportBCSMEVENT procedure..... | 158 | +| 11.27.1 | General description..... | 158 | +| 11.27.1.1 | Parameters..... | 159 | +| 11.27.2 | Responding entity (gsmSSF)..... | 160 | +| 11.27.2.1 | Normal procedure..... | 160 | +| 11.27.2.2 | Error handling..... | 160 | +| 11.28 | ResetTimer procedure..... | 160 | +| 11.28.1 | General description..... | 160 | +| 11.28.1.1 | Parameters..... | 161 | +| 11.28.2 | Responding entity (gsmSSF)..... | 161 | +| 11.28.2.1 | Normal procedure..... | 161 | +| 11.28.2.2 | Error handling..... | 161 | +| 11.29 | SendChargingInformation procedure..... | 161 | +| 11.29.1 | General description..... | 161 | +| 11.29.1.1 | Parameters..... | 161 | +| 11.29.2 | Responding entity (gsmSSF)..... | 162 | +| 11.29.2.1 | Normal procedure..... | 162 | +| 11.29.2.2 | Error handling..... | 163 | +| 11.30 | SpecializedResourceReport procedure..... | 163 | +| 11.30.1 | General description..... | 163 | +| 11.30.1.1 | Parameters..... | 163 | +| 11.30.2 | Invoking entity (gsmSRF)..... | 163 | +| 11.30.2.1 | Normal procedure..... | 163 | +| 11.30.2.2 | Error handling..... | 164 | +| 11.31 | SplitLeg Procedure..... | 164 | +| 11.31.1 | General Description..... | 164 | +| 11.31.1.1 | Parameters..... | 164 | +| 11.31.2 | Responding entity (gsmSSF)..... | 164 | +| 11.31.2.1 | Normal procedure..... | 164 | +| 11.31.2.2 | Error handling..... | 164 | +| 12 | Detailed operation procedures for SMS control..... | 165 | +| 12.1 | ConnectSMS procedure..... | 165 | +| 12.1.1 | General description..... | 165 | +| 12.1.1.1 | Parameters..... | 165 | +| 12.1.2 | Responding entity (smsSSF)..... | 165 | +| 12.1.2.1 | Normal procedure..... | 165 | +| 12.1.2.2 | Error handling..... | 166 | +| 12.2 | ContinueSMS procedure..... | 166 | +| 12.2.1 | General description..... | 166 | +| 12.2.1.1 | Parameters..... | 166 | +| 12.2.2 | Responding entity (smsSSF)..... | 166 | +| 12.2.2.1 | Normal procedure..... | 166 | +| 12.2.2.2 | Error handling..... | 166 | +| 12.3 | EventReportSMS procedure..... | 166 | +| 12.3.1 | General description..... | 166 | +| 12.3.1.1 | Parameters..... | 166 | +| 12.3.2 | Invoking entity (smsSSF)..... | 167 | +| 12.3.2.1 | Normal procedure..... | 167 | +| 12.3.2.2 | Error handling..... | 167 | +| 12.4 | FurnishChargingInformationSMS procedure..... | 167 | + +| | | | +|----------|-----------------------------------------------------|-----| +| 12.4.1 | General description..... | 167 | +| 12.4.1.1 | Parameters..... | 167 | +| 12.4.2 | Responding entity (smsSSF)..... | 168 | +| 12.4.2.1 | Normal procedure..... | 168 | +| 12.4.2.2 | Error handling..... | 168 | +| 12.5 | InitialDPSMS procedure..... | 168 | +| 12.5.1 | General description..... | 168 | +| 12.5.1.1 | Parameters..... | 168 | +| 12.5.2 | Invoking entity (smsSSF)..... | 169 | +| 12.5.2.1 | Normal procedure..... | 169 | +| 12.5.2.2 | Error handling..... | 170 | +| 12.6 | ReleaseSMS procedure..... | 170 | +| 12.6.1 | General description..... | 170 | +| 12.6.1.1 | Parameters..... | 170 | +| 12.6.2 | Responding entity (smsSSF)..... | 170 | +| 12.6.2.1 | Normal procedure..... | 170 | +| 12.6.2.2 | Error handling..... | 170 | +| 12.7 | RequestReportSMSEvent procedure..... | 170 | +| 12.7.1 | General description..... | 170 | +| 12.7.1.1 | Parameters..... | 171 | +| 12.7.2 | Responding entity (smsSSF)..... | 171 | +| 12.7.2.1 | Normal procedure..... | 171 | +| 12.7.2.2 | Error handling..... | 171 | +| 12.8 | ResetTimerSMS procedure..... | 171 | +| 12.8.1 | General description..... | 171 | +| 12.8.1.1 | Parameters..... | 171 | +| 12.8.2 | Responding entity (smsSSF)..... | 172 | +| 12.8.2.1 | Normal procedure..... | 172 | +| 12.8.2.2 | Error handling..... | 172 | +| 13 | Detailed operation procedures for GPRS control..... | 172 | +| 13.1 | ActivityTestGPRS procedure..... | 172 | +| 13.1.1 | General description..... | 172 | +| 13.1.1.1 | Parameters..... | 172 | +| 13.1.2 | Responding entity (gprsSSF)..... | 172 | +| 13.1.2.1 | Normal procedure..... | 172 | +| 13.1.2.2 | Error handling..... | 173 | +| 13.2 | ApplyChargingGPRS procedure..... | 173 | +| 13.2.1 | General description..... | 173 | +| 13.2.1.1 | Parameters..... | 173 | +| 13.2.2 | Responding entity (gprsSSF)..... | 173 | +| 13.2.2.1 | Normal procedure..... | 173 | +| 13.2.2.2 | Error handling..... | 174 | +| 13.3 | ApplyChargingReportGPRS procedure..... | 174 | +| 13.3.1 | General description..... | 174 | +| 13.3.1.1 | Parameters..... | 174 | +| 13.3.2 | Invoking entity (gprsSSF)..... | 176 | +| 13.3.2.1 | Normal procedure..... | 176 | +| 13.3.2.2 | Error handling..... | 176 | +| 13.4 | CancelGPRS procedure..... | 177 | +| 13.4.1 | General description..... | 177 | +| 13.4.1.1 | Parameters..... | 177 | +| 13.4.2 | Responding entity (gprsSSF)..... | 177 | +| 13.4.2.1 | Normal procedure..... | 177 | +| 13.4.2.2 | Error handling..... | 177 | +| 13.5 | ConnectGPRS procedure..... | 177 | +| 13.5.1 | General description..... | 177 | +| 13.5.1.1 | Parameters..... | 177 | +| 13.5.2 | Responding entity (gprsSSF)..... | 178 | +| 13.5.2.1 | Normal procedure..... | 178 | +| 13.5.2.2 | Error handling..... | 178 | +| 13.6 | ContinueGPRS procedure..... | 178 | + +| | | | +|------------|-----------------------------------------------|-----| +| 13.6.1 | General description..... | 178 | +| 13.6.1.1 | Parameters..... | 178 | +| 13.6.2 | Responding entity (gprsSSF)..... | 178 | +| 13.6.2.1 | Normal procedure..... | 178 | +| 13.6.2.2 | Error handling..... | 179 | +| 13.7 | EntityReleasedGPRS procedure..... | 179 | +| 13.7.1 | General description..... | 179 | +| 13.7.1.1 | Parameters..... | 179 | +| 13.7.2 | Invoking entity (gprsSSF)..... | 179 | +| 13.7.2.1 | Normal procedure..... | 179 | +| 13.7.2.2 | Error handling..... | 179 | +| 13.8 | EventReportGPRS procedure..... | 180 | +| 13.8.1 | General description..... | 180 | +| 13.8.1.1 | Parameters..... | 180 | +| 13.8.2 | Invoking entity (gprsSSF)..... | 181 | +| 13.8.2.1 | Normal procedure..... | 181 | +| 13.8.2.2 | Error handling..... | 181 | +| 13.9 | FurnishChargingInformationGPRS procedure..... | 181 | +| 13.9.1 | General description..... | 181 | +| 13.9.1.1 | Parameters..... | 181 | +| 13.9.2 | Responding entity (gprsSSF)..... | 182 | +| 13.9.2.1 | Normal procedure..... | 182 | +| 13.9.2.2 | Error handling..... | 182 | +| 13.10 | InitialDPGPRS procedure..... | 182 | +| 13.10.1 | General description..... | 182 | +| 13.10.1.1 | Parameters..... | 182 | +| 13.10.2 | Invoking entity (gprsSSF)..... | 183 | +| 13.10.2.1 | Normal procedure..... | 183 | +| 13.10.2.2 | Error handling..... | 184 | +| 13.11 | ReleaseGPRS procedure..... | 184 | +| 13.11.1 | General description..... | 184 | +| 13.11.1.1 | Parameters..... | 184 | +| 13.11.2 | Responding entity (gprsSSF)..... | 184 | +| 13.11.2.1 | Normal procedure..... | 184 | +| 13.11.2.2 | Error handling..... | 185 | +| 13.12 | RequestReportGPRSEvent procedure..... | 185 | +| 13.12.1 | General description..... | 185 | +| 13.12.1.1 | Parameters..... | 185 | +| 13.12.2 | Responding entity (gprsSSF)..... | 185 | +| 13.12.2.1 | Normal procedure..... | 185 | +| 13.12.2.2 | Error handling..... | 186 | +| 13.13 | ResetTimerGPRS procedure..... | 186 | +| 13.13.1 | General description..... | 186 | +| 13.13.1.1 | Parameters..... | 186 | +| 13.13.2 | Responding entity (gprsSSF)..... | 186 | +| 13.13.2.1 | Normal procedure..... | 186 | +| 13.13.2.2 | Error handling..... | 186 | +| 13.14 | SendChargingInformationGPRS Procedure..... | 186 | +| 13.14.1 | General description..... | 186 | +| 13.14.1.1 | Parameters..... | 186 | +| 13.14.2 | Responding Entity (gprsSSF)..... | 187 | +| 13.14.2.1 | Normal Procedure..... | 187 | +| 13.14.2.2 | Error handling..... | 187 | +| 14 | Services assumed from lower layers..... | 188 | +| 14.1 | Services assumed from TC..... | 188 | +| 14.1.1 | Common procedures..... | 188 | +| 14.1.1.1 | Normal procedures..... | 188 | +| 14.1.1.2 | Abnormal procedures..... | 189 | +| 14.1.1.3 | Dialogue handling..... | 190 | +| 14.1.1.3.1 | Dialogue establishment..... | 190 | +| 14.1.1.3.2 | Dialogue continuation..... | 191 | + +| | | | +|--------------|-------------------------------------------------|-----| +| 14.1.1.3.3 | Dialogue termination..... | 191 | +| 14.1.1.3.4 | User abort..... | 191 | +| 14.1.1.3.5 | Provider abort..... | 192 | +| 14.1.1.3.6 | Mapping to TC dialogue primitives..... | 192 | +| 14.1.1.3.7 | Default mapping to TC dialogue parameters..... | 193 | +| 14.1.1.4 | Component handling..... | 193 | +| 14.1.1.4.1 | Procedures for CAP Operations..... | 193 | +| 14.1.1.4.2 | Mapping to TC component primitives..... | 195 | +| 14.1.1.4.3 | Default mapping to TC component parameters..... | 196 | +| 14.1.2 | gsmSSF-gsmSCF interfaces..... | 197 | +| 14.1.2.1 | Normal procedures..... | 197 | +| 14.1.2.1.1 | gsmSSF-to-gsmSCF messages..... | 197 | +| 14.1.2.1.2 | gsmSCF-to-gsmSSF messages..... | 198 | +| 14.1.2.1.3 | smsSSF -to-gsmSCF SMS related messages..... | 198 | +| 14.1.2.1.4 | gsmSCF-to-smsSSF SMS related messages..... | 199 | +| 14.1.2.1.5 | Use of dialogue handling services..... | 199 | +| 14.1.2.2 | Abnormal procedures..... | 199 | +| 14.1.2.2.1 | gsmSCF-to-gsmSSF/gsmSRF messages..... | 199 | +| 14.1.2.2.2 | gsmSSF/gsmSRF/ -to-gsmSCF messages..... | 199 | +| 14.1.2.2.3 | gsmSCF-to-smsSSF SMS related messages..... | 200 | +| 14.1.2.2.4 | smsSSF-to-gsmSCF SMS related messages..... | 200 | +| 14.1.2.2.5 | Use of dialogue handling services..... | 200 | +| 14.1.2.3 | Dialogue handling..... | 201 | +| 14.1.2.3.1 | Dialogue establishment..... | 201 | +| 14.1.2.3.2 | Dialogue continuation..... | 201 | +| 14.1.2.3.3 | Dialogue termination..... | 201 | +| 14.1.2.3.4 | User abort..... | 201 | +| 14.1.2.3.5 | Provider abort..... | 201 | +| 14.1.2.3.6 | Mapping to TC dialogue primitives..... | 201 | +| 14.1.2.4 | Component Handling..... | 201 | +| 14.1.2.4.1 | Procedures for CAP Operations..... | 201 | +| 14.1.2.4.2 | Mapping to TC component parameters..... | 201 | +| 14.1.3 | gsmSCF-gsmSRF interface..... | 202 | +| 14.1.3.1 | Normal procedures..... | 202 | +| 14.1.3.1.1 | gsmSCF-to/from-gsmSRF messages..... | 202 | +| 14.1.3.1.2 | Abnormal procedures..... | 202 | +| 14.1.3.1.3 | Dialogue handling..... | 202 | +| 14.1.3.1.3.1 | Dialogue establishment..... | 202 | +| 14.1.3.1.3.2 | Dialogue continuation..... | 202 | +| 14.1.3.1.3.3 | Dialogue termination..... | 202 | +| 14.1.3.1.3.4 | User abort..... | 202 | +| 14.1.3.1.3.5 | Provider abort..... | 202 | +| 14.1.3.1.3.6 | Mapping to TC dialogue primitives..... | 202 | +| 14.1.3.2 | Component handling..... | 203 | +| 14.1.3.2.1 | Procedures for CAP Operations..... | 203 | +| 14.1.3.2.2 | Mapping to TC component parameters..... | 203 | +| 14.1.4 | gprsSSF-gsmSCF interface..... | 203 | +| 14.1.4.1 | Normal procedures..... | 203 | +| 14.1.4.1.1 | TC-dialogues and relationships..... | 203 | +| 14.1.4.1.2 | Use of the GPRS Reference..... | 203 | +| 14.1.4.1.3 | gprsSSF-to-gsmSCF messages..... | 204 | +| 14.1.4.1.4 | gsmSCF-to-gprsSSF messages..... | 205 | +| 14.1.4.2 | Abnormal procedures..... | 205 | +| 14.1.4.2.1 | gsmSCF-to-gprsSSF messages..... | 205 | +| 14.1.4.2.2 | gprsSSF-to-gsmSCF messages..... | 206 | +| 14.1.4.2.3 | Default GPRS Handling..... | 206 | +| 14.2 | Services assumed from SCCP..... | 206 | +| 14.2.1 | Normal procedures..... | 207 | +| 14.2.2 | Service functions from SCCP..... | 207 | +| 14.2.2.1 | SCCP connectionless services..... | 207 | +| 14.2.2.1.1 | Sub-System Number (SSN)..... | 207 | + +| | | | +|-------------------------------|---------------------------------------------------------------------------|------------| +| 14.2.2.1.2 | Addressing..... | 207 | +| 14.2.2.1.3 | Sequence control..... | 211 | +| 14.2.2.1.4 | Return on error..... | 211 | +| 14.2.2.1.5 | Segmentation / reassembly..... | 211 | +| 14.2.2.1.6 | Congestion control..... | 211 | +| 14.2.2.2 | SCCP connection oriented services..... | 211 | +| 14.2.2.3 | SCCP management..... | 212 | +| Annex A (normative): | Mapping between CAP and ISUP..... | 213 | +| A.1 | InitialDP operation..... | 213 | +| A.1.1 | EventReportBCSM Operation..... | 214 | +| A.2 | ContinueWithArgument operation..... | 214 | +| A.3 | Connect operation..... | 214 | +| A.4 | AssistRequestInstructions operation..... | 217 | +| A.5 | ConnectToResource operation..... | 217 | +| A.6 | EstablishTemporaryConnection operation..... | 218 | +| A.7 | ReleaseCall operation..... | 219 | +| A.8 | InitiateCallAttempt operation..... | 219 | +| Annex B (normative): | Mapping between CAP and MAP and mapping between CAP and SM-CP..... | 220 | +| B.1 | Mapping between CAP and MAP..... | 220 | +| B.1.1 | MO-SMS..... | 220 | +| B.1.1.1 | ConnectSMS operation..... | 220 | +| B.1.1.2 | EventReportSMS operation..... | 220 | +| B.1.2 | MT-SMS..... | 221 | +| B.1.2.1 | InitialDPSMS operation (MT-SMS)..... | 221 | +| B.1.2.2 | ReleaseSMS operation (MT-SMS)..... | 221 | +| B.2 | Mapping between CAP and SM-CP..... | 221 | +| B.2.1 | MO-SMS..... | 221 | +| B.2.1.1 | InitialDPSMS operation..... | 221 | +| B.2.1.2 | ReleaseSMS operation..... | 222 | +| B.2.2 | MT-SMS..... | 222 | +| B.2.2.1 | ConnectSMS operation..... | 222 | +| B.2.2.2 | EentReportSMS operation..... | 222 | +| Annex C (informative): | Change history..... | 223 | + +--- + +## Foreword + +This Technical Specification (TS) has been produced by the 3rd Generation Partnership Project (3GPP). + +The present document identifies the 3G system specifications for Rel-5. + +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 CAMEL Application Part (CAP) supporting the fourth phase of the network feature Customized Applications for Mobile network Enhanced Logic. CAP is based on a sub-set of the ETSI Core INAP CS-2 as specified by ETSI EN 301 140-1 [26]. Descriptions and definitions provided by ETSI EN 301 140-1 [26] are directly referenced by this standard in the case no additions or clarifications are needed for the use in the CAP. + +# 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] EN 302 646-1 v7 (3GPP TS 09.12 Phase 2+): "Application of ISDN User Part (ISUP) version 2 for the ISDN-Public Land Mobile Network (PLMN) signalling interface; Part 1: Protocol specification". +- [2] 3GPP TS 22.024: "Description of Charge Advice Information (CAI)". +- [3] 3GPP TS 22.078: "Customised Applications for Mobile network Enhanced Logic (CAMEL); Service description, Stage 1". +- [4] 3GPP TS 22.115: "Service Aspects Charging and Billing". +- [5] 3GPP TS 23.003: "Numbering, addressing and identification". +- [6] 3GPP TS 23.040: "Technical realization of the Short Message Service (SMS); Point-to-Point (PP)". +- [7] 3GPP TS 23.078: " Customised Applications for Mobile network Enhanced Logic (CAMEL) Phase 3 - Stage 2". +- [8] 3GPP TS 23.079: "Support of Optimal Routeing (SOR); Technical realization". +- [9] 3GPP TS 24.008: "Digital cellular telecommunications system (Phase 2+); Mobile radio interface layer 3 specification (3GPP TS 24.008)". +- [10] 3GPP TS 24.011: "Point-to-Point (PP) Short Message Service (SMS); support on mobile radio interface". +- [11] 3GPP TS 29.002: "Digital cellular telecommunications system (Phase 2+); Mobile Application Part (MAP) specification (3GPP TS 29.002)". +- [12] 3GPP TS 29.060: "General Packet Radio Service (GPRS); GPRS Tunnelling Protocol (GTP) across the Gn and Gp Interface". +- [13] 3GPP TS 32.250: "Telecommunication Management; Charging Circuit Switched (CS) domain". +- [14] 3GPP TS 32.251: "Telecommunication Management; Charging Packet Switched (PS) domain". +- [15] 3GPP TS 23.038: "Alphabets and language-specific information". +- [16] 3GPP TS 23.172: "Technical realisation of Circuit Switched (CS) multimedia service UDI/RDI fallback and service modification; Stage 2". +- [17] – [20] (Void) + +- [21] ETSI ES 201 296: "Integrated Services Digital Network (ISDN); Signalling System No.7; ISDN User Part (ISUP); Signalling aspects of charging". +- [22] ETSI ETS 300 287-1: "Integrated Services Digital Network (ISDN); Signalling System No.7; Transaction Capabilities (TC) version 2; Part 1: Protocol specification [ITU-T Recommendations Q.771 to Q.775 (1993), modified]". +- [23] ETSI EN 300 356-1: "Integrated Services Digital Network (ISDN); Signalling System No.7; ISDN User Part (ISUP) version 3 for the international interface; Part 1: Basic services [ITU-T Recommendations Q.761 to Q.764 (1997), modified]". +- [24] ETSI ETS 300 374-1: "Intelligent Network (IN); Intelligent Network Capability Set 1 (CS1); Core Intelligent Network Application Protocol (INAP); Part 1: Protocol specification". +- [25] ETSI EN 300 403-1: "Integrated Services Digital Network (ISDN); Digital Subscriber Signalling System No. one (DSS1) protocol; Signalling network layer for circuit-mode basic call control; Part 1: Protocol specification [ITU-T Recommendation Q.931 (1993), modified]". +- [26] ETSI EN 301 140-5: "Intelligent Network (IN); Intelligent Network Application Protocol (INAP); Capability Set 2 (CS2); Part 1: Protocol Specification". +- [27] – [40] (Void) +- [41] ITU-T Recommendation Q.71: "ISDN circuit mode switched bearer services". +- [42] ITU-T Recommendation Q.713: "Specifications of Signalling System No.7; SCCP formats and codes". +- [43] ITU-T Recommendation Q.714: "Specifications of Signalling System No.7; Signalling Connection Control Part procedures". +- [44] ITU-T Recommendation Q.762: "General function of messages and signals of the ISDN user part of signalling system no.7". +- [45] ITU-T Recommendation Q.763: "Formats and codes of the ISDN user part of Signalling System No.7". +- [46] ITU-T Recommendation Q.773: "Specifications of Signalling System No.7; Transaction capabilities formats and encoding". +- [47] ITU-T Recommendation Q.850: "Usage of cause and location in the digital subscriber signalling system no.1 and the signalling system no.7 ISDN user part". +- [48] ITU-T Recommendation Q.932: "Digital subscriber Signalling System No.1 (DSS 1) - Generic procedures for the control of ISDN supplementary services". +- [49] ITU-T Recommendation Q.1218: "Interface Recommendation for Intelligent Network CS-1". +- [50] ITU-T Recommendation Q.1224: "Distributed functional plane for intelligent network CS2". +- [51] ITU-T Recommendation Q.1228: "Interface ITU-T Recommendation for intelligent network CS2". +- [52] ITU-T Recommendation Q.1400: "Architecture framework for the development of signalling and organization, administration and maintenance protocols using OSI principles". +- [53] ITU-T Recommendation X.680: "Information technology - Abstract Syntax Notation One (ASN.1): Specification of basic notation". +- [54] ITU-T Recommendation X.681: "Information technology – Abstract Syntax Notation One (ASN.1): Information object specification". +- [55] ITU-T Recommendation X.682: "Information technology – Abstract Syntax Notation One (ASN.1): Parameterization of ASN.1 specifications". +- [56] ITU-T Recommendation X.683: "Information technology – Abstract Syntax Notation One (ASN.1): Constraint specification". + +- [57] ITU-T Recommendation X.690: "ASN.1 encoding rules: Specification of Basic Encoding Rules (BER), Canonical Encoding Rules (CER) and Distinguished Encoding Rules (DER)". +- [58] ITU-T Recommendation X.880: "Data networks and open system communication - Open System Interconnection - Service definitions - Remote operations: Concepts, model and notation". +- [59] ITU-T Recommendation X.881: "Data networks and open system communication - Open System Interconnection - Service definitions - Remote operations: OSI Realizations – Remote Operations Service Element (ROSE) service definition". +- [60] ITU-T Recommendation X.882: "Data networks and open system communication - Open System Interconnection - Service definitions - Remote operations: OSI Realizations – Remote Operations Service Element (ROSE) protocol specification". +- [61] – [80] (Void) +- [81] ISO 9545 (1989): "Information technology - Open Systems Interconnection - Application Layer structure". +- [82] – [90] (Void) +- [91] ANSI T1.112-1996: "American National Standards for Telecommunications- Signalling System Number 7 (SS7) - Signalling Connection Control Part (SCCP)". +- [92] ANSI T1.113-1995: "American National Standards for Telecommunications- Signalling System Number 7 (SS7) - ISDN User Part". +- [93] 3GPP TS 23.060: "General Packet Radio Service (GPRS) Description; Stage 2". + +## 2.1 Specifications used for IMPORTS for CAP + +The following table lists the modules from which CAP V4 imports. For each module, the table indicates in which formal specification this module can be found. + +**Table 2-1: Module IMPORTS specifications** + +| Module Name | Specification | Ref | +|---------------------------------------------------------------------------------------------------------------------------------------------------------|----------------|------| +| CS1-DataTypes {itu-t(0) identified-organization(4) etsi(0) mobileDomain(0) umts-network(1) modules(3) cs1-datatypes(2) version1(0)} | ETS 300 374-1 | [24] | +| CS2-datatypes {itu-t(0) identified-organization(4) etsi(0) mobileDomain(0) umts-network(1) modules(3) in-cs2-datatypes (0) version1(0)} | EN 301 140-1 | [26] | +| MAP-CommonDataTypes {itu-t(0) identified-organization(4) etsi(0) mobileDomain(0) gsm-Network(1) modules(3) map-CommonDataTypes(18) version12(12)} | 3GPP TS 29.002 | [11] | +| MAP-MS-DataTypes {itu-t(0) identified-organization(4) etsi(0) mobileDomain(0) gsm-Network(1) modules(3) map-MS-DataTypes(11) version12(12)} | 3GPP TS 29.002 | [11] | +| MAP-CH-DataTypes {itu-t(0) identified-organization(4) etsi(0) mobileDomain(0) gsm-Network(1) modules(3) map-CH-DataTypes(13) version12(12)} | 3GPP TS 29.002 | [11] | +| MAP-ExtensionDataTypes {itu-t(0) identified-organization(4) etsi(0) mobileDomain(0) gsm-Network(1) modules(3) map-ExtensionDataTypes(21) version12(12)} | 3GPP TS 29.002 | [11] | +| TCAPMessages {itu-t recommendation q 773 modules(2) messages(1) version3(3)} | ITU-T Q.773 | [46] | +| Remote-Operations-Information-Objects {joint-iso-itu-t remote-operations(4) informationObjects(5) version1(0)} | ITU-T X.880 | [58] | +| TC-Notation-Extensions {itu-t recommendation q 775 modules(2) notation-extension (4) version1(1)} | ETS 300 287-1 | [22] | + +## 3 Abbreviations + +For the purposes of the present document, the following abbreviations apply: + +| | | +|----|---------------------| +| AC | Application Context | +| AE | Application Entity | + +| | | +|---------|----------------------------------------------------------------------------------| +| AEI | Application Entity Invocation | +| APDU | Application Protocol Data Unit | +| ASE | Application Service Element | +| ASN.1 | Abstract Syntax Notation One | +| BCSM | Basic Call State Model | +| CAP | CAMEL Application Part | +| CCF | Call Control Function | +| CCITT | International Telegraph and Telephone Consultative Committee | +| CPH | Call Party Handling | +| CS1 | Capability Set 1 | +| CS2 | Capability Set 2 | +| CS | Call Segment | +| | Circuit Switched | +| CSA | Call Segment Association | +| CSG | Closed Subscriber Group | +| CSG ID | Closed Subscriber Group Identity | +| CSI | CAMEL Subscription Information | +| CSID | Call Segment (followed by an identification Number e.g. CSID1) | +| DP | Detection Point | +| DSS1 | Digital Subscriber Signalling System No. One | +| EDP | Event Detection Point | +| EDP-N | Event Detection Point - Notification | +| EDP-R | Event Detection Point - Request | +| EDS | Enhanced Dialled Services | +| FE | Functional Entity | +| FEAM | Functional Entity Access Manager | +| ffs | for further study | +| FSM | Finite State Model | +| gprsSSF | GPRS Service Switching Function | +| gsmSCF | GSM Service Control Function | +| gsmSRF | GSM Specialized Resource Function | +| gsmSSF | GSM Service Switching Function | +| GT | Global Title | +| ID | Identifier | +| IN | Intelligent Network | +| INAP | Intelligent Network Application Protocol | +| IP | Intelligent Peripheral | +| ISDN | Integrated Services Digital Network | +| ISUP | ISDN User Part | +| ITU-T | International Telecommunication Union – Telecommunication Standardization Sector | +| LE | Local Exchange | +| MACF | Multiple Association Control Function | +| MO | Mobile Originated | +| MS | Mobile Station | +| MSC | Mobile services Switching Centre | +| MT | Mobile Terminated | +| MTP | Message Transfer Part | +| NA | North American | +| O-BCSM | Originating BCSM | +| PDU | Protocol Data Unit | +| PE | Physical Entity | +| PIA | Point In Association | +| PIC | Point In Call | +| PLMN | Public Land Mobile Network | +| PSTN | Public Switched Telecommunication Network | +| ROS | Remote Operations Service | +| ROSE | ROS Element | +| SACF | Single Association Control Function | +| SAO | Single Association Object | +| SCCP | Signalling Connection Control Part | +| SCP | Service Control Point | + +| | | +|--------|--------------------------------------------------| +| SDL | System Description Language | +| SL | Service Logic | +| SLP | Service Logic Program | +| SLPI | Service Logic Program Instance | +| SM | Short Message | +| SM-CP | Short Message Control Protocol | +| SMS | Short Message Service | +| SMSC | Short Message Service Centre | +| smsSSF | Short Message Service Service Switching Function | +| SMF | Service Management Function | +| SRME | gsmSRF Management Entity | +| SRSM | gsmSRF Call State Model | +| SS7 | Signalling System no. 7 | +| smsSSF | SMS Service Switching Function | +| SSME | gsmSSF Management Entity | +| SSN | Sub-System Number | +| SSP | Service Switching Point | +| T-BCSM | Terminating BCSM | +| TC | Transaction Capabilities | +| TCAP | Transaction Capabilities Application Part | +| TDP | Trigger Detection Point | +| TDP-R | Trigger Detection Point - Request | + +--- + +## 4 Interface specification for telecommunication services + +### 4.1 General + +#### 4.1.1 Definition methodology + +The definition of the protocol can be split into three sections: + +- the definition of the Single Association Control Function (SACF)/Multiple Association Control Function (MACF) rules for the protocol; +- the definition of the operations transferred between entities; +- the definition of the actions taken at each entity. + +The SACF/MACF rules are defined in prose. The operation definitions are in Abstract Syntax Notation One (ASN.1). For details on ASN.1 refer to ITU-T Recommendation X.680 [53] and ITU-T Recommendation X.681 [54]. The actions are defined in terms of state transition diagrams. Further guidance on the actions to be performed on receipt of an operation can be gained from the description of the relevant information flow in ITU-T Recommendation Q.1224 [50]. + +The CAMEL Application Part (CAP) is a ROS Element (ROSE) user protocol. Refer to ITU-T Recommendation X.880 [58], ITU-T Recommendation X.881 [59] and ITU-T Recommendation X.882 [60] for Remote Operations. The ROSE protocol is contained within the component sublayer of Transaction Capabilities Application Part (TCAP) (see ETS 300 287-1 [22]) and Digital Subscriber Signalling System No One (DSS1) (see ITU-T Recommendation Q.932 [48]). At present, the ROSE Application Protocol Data Units (APDUs) are conveyed in transaction sublayer messages in Signalling System no. 7 (SS7) and in the EN 300 403-1 [25] REGISTER, FACILITY and call control messages in DSS1. Other supporting protocols may be added at a later date. + +The CAP (as a ROSE user) and the ROSE protocol are specified in ASN.1, as defined in ITU-T Recommendation X.680 [53], ITU-T Recommendation X.681 [54], ITU-T Recommendation X.682 [55] and ITU-T Recommendation X.683 [56]. The encoding of the resulting Protocol Data Units (PDUs) shall be done in accordance with the Basic Encoding Rules as defined in ITU-T Recommendation X.690 [57]. + +### 4.1.2 Example physical scenarios + +The reader is referred to Intelligent Network Capability Set 1 (CS1) Core INAP [24] for details of the example physical scenarios. + +![Diagram of Scenario 1: Direct Path to IP. An SCP box contains an SCF box. Below it, an SSP box contains an SSF box. To the right, an IP box is above an SRF box. Lines connect SCF to SSF, SCF to SRF, and SSF to SRF. A label 'ISUP' is placed between the SSF and SRF boxes.](3da1a07cb87051bf616c9876db958cf0_img.jpg) + +Diagram of Scenario 1: Direct Path to IP. An SCP box contains an SCF box. Below it, an SSP box contains an SSF box. To the right, an IP box is above an SRF box. Lines connect SCF to SSF, SCF to SRF, and SSF to SRF. A label 'ISUP' is placed between the SSF and SRF boxes. + +Scenario 1, Direct Path to IP (Ref. CS1 cases b) & d)). + +Figure 4-1/1: Scenarios + +![Diagram of Scenario 2: Connection to IP via an assisting SSP. An SCP box contains an SCF box. On the left, an 'Initiating SSP' box contains an SSF box. On the right, an 'Assisting SSP' box contains an 'SSF relay' box and an 'SRF' box. An 'IP' label is above the SRF box. Lines connect SCF to SSF, SCF to SSF relay, and SSF relay to SRF. A label 'ISUP' is placed between the SSF and SSF relay boxes.](1a85642ed2356d183ce598f2c8b3ee8b_img.jpg) + +Diagram of Scenario 2: Connection to IP via an assisting SSP. An SCP box contains an SCF box. On the left, an 'Initiating SSP' box contains an SSF box. On the right, an 'Assisting SSP' box contains an 'SSF relay' box and an 'SRF' box. An 'IP' label is above the SRF box. Lines connect SCF to SSF, SCF to SSF relay, and SSF relay to SRF. A label 'ISUP' is placed between the SSF and SSF relay boxes. + +Figure 4-1/2: Scenarios + +![Diagram of Scenario 2a: Connection to IP via an assisting gsmSSF with relay function. An SCP box contains a gsmSCF box. On the left, an 'InitiatingSSP' box contains a gsmSSF box and a 'CCF in MSC' box. On the right, an 'AssistingSSP' box contains a gsmSSF box, a 'CCF in MSC' box, and a gsmSRF box. Lines connect gsmSCF to gsmSSF (InitiatingSSP), gsmSCF to gsmSSF (AssistingSSP), and gsmSSF (AssistingSSP) to gsmSRF. A label 'ISUP' is between the gsmSSF boxes, and a label 'internal' is between the gsmSSF and gsmSRF boxes in the AssistingSSP.](552ca016af3d6240648ab5a2cad97f60_img.jpg) + +Diagram of Scenario 2a: Connection to IP via an assisting gsmSSF with relay function. An SCP box contains a gsmSCF box. On the left, an 'InitiatingSSP' box contains a gsmSSF box and a 'CCF in MSC' box. On the right, an 'AssistingSSP' box contains a gsmSSF box, a 'CCF in MSC' box, and a gsmSRF box. Lines connect gsmSCF to gsmSSF (InitiatingSSP), gsmSCF to gsmSSF (AssistingSSP), and gsmSSF (AssistingSSP) to gsmSRF. A label 'ISUP' is between the gsmSSF boxes, and a label 'internal' is between the gsmSSF and gsmSRF boxes in the AssistingSSP. + +Scenario 2a, Connection to IP via an assisting gsmSSF with relay function; IP co-located with assisting gsmSSF (Ref. CS1 case c)). + +Figure 4-1/3: Scenarios + +![Diagram of Figure 4-1/4: Scenarios. It shows an SCP box containing an SCF box. Below it, an Initiating SSP box contains an SSF box, and an Assisting SSP box contains an SSF relay box. These two are connected by a line labeled ISUP. The SSF relay box is connected to an IP box containing an SRF box.](79e1709a7317ead45379cbb8ff3ba802_img.jpg) + +Diagram of Figure 4-1/4: Scenarios. It shows an SCP box containing an SCF box. Below it, an Initiating SSP box contains an SSF box, and an Assisting SSP box contains an SSF relay box. These two are connected by a line labeled ISUP. The SSF relay box is connected to an IP box containing an SRF box. + +Figure 4-1/4: Scenarios + +![Diagram of Figure 4-1/5: Scenarios. It shows an SCP box containing a gsmSCF box. Below it, an Initiating SSP box contains a gsmSSF box and a CCF in MSC box. An Assisting SSP box contains a gsmSSF box and a CCF in MSC box. These two are connected by a line labeled ISUP. The Assisting SSP box is connected to an IP box containing a gsmSRF box via lines labeled ISUP and DSSI.](a24e89a6fe9bb70c83f8bf5202baba95_img.jpg) + +Diagram of Figure 4-1/5: Scenarios. It shows an SCP box containing a gsmSCF box. Below it, an Initiating SSP box contains a gsmSSF box and a CCF in MSC box. An Assisting SSP box contains a gsmSSF box and a CCF in MSC box. These two are connected by a line labeled ISUP. The Assisting SSP box is connected to an IP box containing a gsmSRF box via lines labeled ISUP and DSSI. + +Figure 4-1/5: Scenarios + +Scenario 2b: Connection to IP via an assisting gsmSSF with relay function; IP not co-located with ssisting gsmSSF (Ref CS1 case c)). + +![Diagram of Figure 4-1/6: Scenarios. It shows an SCP box containing an SCF box. Below it, an SSP box contains an SSF relay box. The SSF relay box is connected to an IP box containing an SRF box.](75e4b78ee25f885d73120e3066a5253e_img.jpg) + +Diagram of Figure 4-1/6: Scenarios. It shows an SCP box containing an SCF box. Below it, an SSP box contains an SSF relay box. The SSF relay box is connected to an IP box containing an SRF box. + +Figure 4-1/6: Scenarios + +![Diagram of Figure 4-7: Scenarios. It shows an SCP box containing a gsmSCF oval. Below it is an SSP box (dashed border) containing a gsmSSF oval, a CCF in MSC oval, and a gsmSRF oval. Lines connect gsmSCF to gsmSSF, gsmSSF to CCF in MSC, and CCF in MSC to gsmSRF. The connection between CCF in MSC and gsmSRF is labeled 'internal'.](e180f2b5fcbe8001554a7c0677cd3f82_img.jpg) + +Diagram of Figure 4-7: Scenarios. It shows an SCP box containing a gsmSCF oval. Below it is an SSP box (dashed border) containing a gsmSSF oval, a CCF in MSC oval, and a gsmSRF oval. Lines connect gsmSCF to gsmSSF, gsmSSF to CCF in MSC, and CCF in MSC to gsmSRF. The connection between CCF in MSC and gsmSRF is labeled 'internal'. + +Scenario 3, Connection to IP with relay function; IP co-located with gsmSSF (Ref CS1 case a)). + +Figure 4-7: Scenarios + +![Diagram of Figure 4-1/8: Scenarios. It shows an Initiating SSP box connected to an SSF Relay box. The SSF Relay box is connected to an SRF box via a line labeled 'ISUP or D channel'. Above the SSF Relay box is an SCF box. The SRF box is connected to an IP box.](5793a44ffdadd039928e2f9fe6daae06_img.jpg) + +Diagram of Figure 4-1/8: Scenarios. It shows an Initiating SSP box connected to an SSF Relay box. The SSF Relay box is connected to an SRF box via a line labeled 'ISUP or D channel'. Above the SSF Relay box is an SCF box. The SRF box is connected to an IP box. + +Figure 4-1/8: Scenarios + +![Diagram of Figure 4-1/9: Scenarios. It shows an SCP box containing a gsmSCF oval. Below it is an SSP box containing a gsmSSF oval and a CCF in MSC oval. A line connects gsmSCF to gsmSSF. The gsmSSF oval is connected to a gsmSRF oval inside an IP box via two lines labeled 'ISUP' and 'DSSI'.](b2ea162a0f53d5e0504b7d28346e0754_img.jpg) + +Diagram of Figure 4-1/9: Scenarios. It shows an SCP box containing a gsmSCF oval. Below it is an SSP box containing a gsmSSF oval and a CCF in MSC oval. A line connects gsmSCF to gsmSSF. The gsmSSF oval is connected to a gsmSRF oval inside an IP box via two lines labeled 'ISUP' and 'DSSI'. + +Scenario 4, Connection to IP with relay function; IP not co-located with gsmSSF (Ref CS1 case a)). + +Figure 4-1/9: Scenarios + +![Diagram of Figure 4-1/10: Scenarios. It shows an SCP box containing an SCF box. A line connects the SCF box to an SSF box inside an SGSN box. The SSF box is connected to a GGSN box via a line labeled GTP. There is a small empty box above the GGSN box.](eb03559a4d92ea9ebd63ea9be663c50a_img.jpg) + +Diagram of Figure 4-1/10: Scenarios. It shows an SCP box containing an SCF box. A line connects the SCF box to an SSF box inside an SGSN box. The SSF box is connected to a GGSN box via a line labeled GTP. There is a small empty box above the GGSN box. + +Figure 4-1/10: Scenarios + +![Diagram of Figure 4-1/11: Scenarios. It shows an SCP box containing a gsmSCF box. A line connects the gsmSCF box to an SGSN box. Inside the SGSN box is a gprsSSF box. The gprsSSF box is connected to a GGSN box via a line labeled GTP. There is a small empty box above the GGSN box.](d9c0a780cd22626253dab4aa41699e2f_img.jpg) + +Diagram of Figure 4-1/11: Scenarios. It shows an SCP box containing a gsmSCF box. A line connects the gsmSCF box to an SGSN box. Inside the SGSN box is a gprsSSF box. The gprsSSF box is connected to a GGSN box via a line labeled GTP. There is a small empty box above the GGSN box. + +Scenario 5, GPRS interworking. No connection to IP. + +Figure 4-1/11: Scenarios + +The following table summarises the scenarios and corresponding interface connections that shall be supported by the CAP protocol. The following terms used in the table are defined as follows: + +- Basic: Fully defined in CAP and may be used between any two network operators supporting CAP. +- Bilateral: Additional clarifications of CAP capabilities between network operators and/or equipment vendors are necessary in order for CAP to be used between any two network operators supporting CAP. +- Direct: This refers to the case where CAP Operations are exchanged between the gsmSRF and the gsmSCF via a transaction-level relationship established directly between the gsmSRF and the gsmSCF. +- Relay: This refers to the case where CAP Operations are exchanged between the gsmSRF and the gsmSCF via two transaction-layer relationships. These relationships are: + - a) - gsmSCF to/from gsmSSF; + - b) - gsmSSF to/from gsmSRF. + +The gsmSSF sends operations it receives from the gsmSCF to the gsmSRF, and operations it receives from the gsmSRF to the gsmSCF. This is done without unpacking (and thus processing) of the relayed operations. + +The gsmSSF function referred to in the table is always located in an MSC or GMSC. + +The gprsSSF function referred to in the table is always located in an SGSN. + +Table 4-1 + +| Scenario | Interface Support | | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------|-----------------------|---------------------------------|------------------------------------------------------------------------------------------|---------------------------------| +| | GsmSSF to/from gsmSCF | gsmSSF to/from gsmSRF | gsmSSF to/from assisting gsmSSF | gsmSRF to/from gsmSCF | assisting gsmSSF to/from gsmSCF | +| Scenario 1

gsmSRF in IP connected to gsmSSF in MSC or GMSC via ISUP and accessed by gsmSCF through direct Signalling System No.7 Connection | See Note 1 | See Note 2 | - | See Notes 3 and 6.

For gsmSRF in VPLMN see Note 4; For gsmSRF in HPLMN see note 5 | - | +| Scenario 2a

assisting gsmSSF in MSC or GMSC connected to gsmSSF in MSC or GMSC via ISUP. Assisting gsmSSF is accessed by gsmSCF through direct Signalling System No.7 Connection.

gsmSRF is co-located with assisting gsmSSF and accessed (by gsmSCF) by relay via assisting gsmSSF over an internal nodal interface | See Note 1
For gsmSRF in VPLMN see Notes 4 and 6; For gsmSRF in HPLMN see note 5 and 6 | - | See Note 2 | - | See Note 3 | +| Scenario 2b

assisting gsmSSF in MSC or GMSC connected to gsmSSF in MSC or GMSC via ISUP. Assisting gsmSSF is accessed by gsmSCF through direct Signalling System No.7 Connection

gsmSRF is in IP connected to assisting gsmSSF and accessed (by gsmSCF) by relay through ISUP or DSS1 via assisting gsmSSF | See Note 1

See Notes 4 and 6 | See Notes 4 and 6 | See Note 2 | - | See Note 3 | +| Scenario 3

gsmSRF is co-located with a gsmSSF in an MSC or GMSC and accessed by relay via gsmSSF over an internal nodal interface | For gsmSRF in VPLMN see Notes 4; For gsmSRF in HPLMN see notes 5 and 6 | - | - | - | - | +| Scenario 4

gsmSRF in IP connected to gsmSSF and accessed by gsmSCF by relay through ISUP or DSS1 via gsmSSF | See Notes 4 and 6 | See Notes 4 and 6 | - | - | - | + +NOTE 1: Basic for establishment of interface when CorrelationID and SCFiD are transferred in the AssistingSSPIPRoutingAddress. Bilateral when CorrelationID and SCFiD are transferred by other means than in the AssistingSSPIPRoutingAddress. + +NOTE 2: Basic for establishment of interface when CorrelationID and SCFiD are transferred in the Called Party Number. Bilateral when CorrelationID and SCFiD are transferred by other means than in the Called Party Number. + +NOTE 3: Basic when the full Called Party Number received in VPLMN or HPLMN is transferred on its own in the AssistRequestInstructions operation CorrelationID parameter to a gsmSCF in HPLMN. + +Bilateral when CorrelationID is extracted from Called Party Number in HPLMN or VPLMN and transferred on its own in AssistRequestInstructions CorrelationID field to a gsmSCF in HPLMN. + +NOTE 4: Bilateral for the playing of announcements via elementaryMessageIDs and variableMessages, playing of tones and the collection of DTMF digits. + +NOTE 5: Basic for the playing of announcements via elementaryMessageIDs and variableMessages, playing of tones and the collection of DTMF digits. + +NOTE 6: Bilateral for the playing of announcements via text to speech translation, translation of DTMF digits via speech to caller and the translation of voice to digits. + +#### 4.1.3 CAP protocol architecture + +Many of the terms used in the present subclause are based on the OSI application layer structure as defined in ISO 9545 (1989) [81]. + +The CAP protocol architecture is illustrated in figure 4-2. + +A Physical Entity (PE) has either single interactions (case a) or multiple co-ordinated interactions (case b) with another PE. + +In case (a), SACF provides a co-ordination function in using Application Service Elements (ASEs), which includes the ordering of operations supported by ASE(s), in the order of received primitives. The Single Association Object (SAO) represents the SACF plus a set of ASEs to be used over a single interaction between a pair of PEs. + +In case (b), MACF provides a co-ordinating function among several SAO's, each of which interacts with an SAO in a remote PE. + +Each ASE supports one or more operations. Description of each operation is tied with the action of corresponding Functional Entity (FE) modelling. For FE modelling, refer to ITU-T Recommendation Q.1224 [50] and clause 11 of the present document. Each operation is specified using the OPERATION macro described in figure 4-3. + +![Diagram illustrating the CAP protocol architecture for two cases: Multiple coordinated interactions (case b) and Single interaction (case a).](f7d969388c4f7e30cd04a061314bfa0e_img.jpg) + +The diagram illustrates the CAP protocol architecture for two cases: + +- Multiple coordinated interactions case b:** + - An **Application process** block is at the top. + - Below it is a **MACF** block. + - Below the MACF block are two **SAO** (Single Association Object) blocks, each containing a sub-block with **S A C F** and **A S E's** (Application Service Elements). + - Below each SAO block is a **TCAP** block. + - Below the TCAP blocks is an **SCCP** block. + - At the bottom is an **MTP** block. +- Single interaction case a:** + - An **Application process** block is at the top. + - Below it is a single **SAO** block, containing a sub-block with **S A C F** and **A S E's**. + - Below the SAO block is a **TCAP** block. + - Below the TCAP block is an **SCCP** block. + - At the bottom is an **MTP** block. + +Diagram illustrating the CAP protocol architecture for two cases: Multiple coordinated interactions (case b) and Single interaction (case a). + +NOTE: CAP is the collection of all specifications in ASEs. + +**Figure 4-2: CAP protocol architecture** + +![Diagram illustrating the operation description for INAP User ASEs and TCAP ASE.](90ddb84c323b956e2d50a54d3f870566_img.jpg) + +The diagram illustrates the operation description for INAP User ASEs and TCAP ASE. + +**INAP User ASEs** + +The INAP User ASEs box contains the following elements: + +- xyz OPERATION +- ARGUMENT {Parameter1, Parameter2,...} +- RESULT {Parameter1, Parameter2,...} +- LINKED {operation3, operation4,...} +- ERRORS {error1, error2...} +- error1 ERROR +- PARAMETER {Parameter6, Parameter7,...} +- etc + +To the right of the INAP User ASEs box, there is a double-headed arrow labeled "to peer" pointing to a list of elements: + +- Operations +- Results +- Errors + +**TCAP ASE** + +The TCAP ASE box contains two sub-layers: + +- COMPONENT SUB-LAYER +- TRANSACTION SUB-LAYER + +To the right of the TCAP ASE box, there are two double-headed arrows labeled "to peer" pointing to lists of elements: + +- For the COMPONENT SUB-LAYER: INVOKE, RETURN RESULT, RETURN ERROR, REJECT +- For the TRANSACTION SUB-LAYER: BEGIN, CONTINUE, END, ABORT, UNIDIRECTIONAL + +Below the TCAP ASE box, there is a double-headed arrow pointing to the text: CONNECTIONLESS SCCP + +Diagram illustrating the operation description for INAP User ASEs and TCAP ASE. + +**Figure 4-3: Operation description** + +#### 4.1.4 Compatibility mechanisms used for CAP + +##### 4.1.4.1 Introduction + +The present subclause specifies the compatibility mechanisms that shall be used for CAP. + +Two major categories of compatibility are handled by these mechanisms: + +- compatibility with the ITU-T Recommendation Q.1228 [51] version of CS2 INAP and the specification EN 301 140-1 version of CS2 INAP [26]; +- compatibility with future versions of CAP. + +The second category has three subcategories of compatibility dealt with within the present subclause: + +- Minor changes to CAP in future versions of CAP: +A minor change can be defined as a change of a functionality which is not essential for the requested IN service. Where it is a modification of an existing function, it is acceptable that the addressed function is executed in either the older or the modified variant. If the change is purely additional, then it is acceptable that it is not executed at all and that the peer Application Entity (AE) need not know about the effects of the change. For minor changes, a new Application Context is not required. +- Major changes to CAP in future versions of CAP: +A major change can be defined as a change of a functionality which is essential for the requested IN service. Where it is a modification of an existing function, both application entities shall have a shared knowledge about the addressed functional variant. If the change is purely additional and one of the application entities does not support the additional functionality, then the requested IN service will not be provided. For major changes, a new Application Context is required. + +- Network-specific changes to CAP: + +These additions may be of either the major or minor type for a service. No new Application Context is expected to be defined for this type of change. At the time of definition of these network-specific changes to CAP, the additions would not be expected to be included in identical form in future versions of CAP. + +#### 4.1.4.2 Definition of CAP compatibility mechanisms + +##### 4.1.4.2.1 Compatibility mechanism for interworking of CAP with ETSI CS2 Core INAP and ITU-T Q.1228 INAP + +On receipt of an operation according to ITU-T Recommendation Q.1228 [51] or an operation according to ETSI EN 301 140-1 [26], which is not part of the CAP or is part of the CAP but which contains parameters which are not part of the CAP: + +- the gsmSSF, gsmSCF, assisting gsmSSF and gsmSRF shall apply the normal error handling for unknown operations or parameters, i.e. the normal error handling procedures as specified in clause 10 shall be followed. + +Tagging of CAP additions to ITU-T Recommendation Q.1228 [51] and ETSI EN 301 140-1 [26] are specified from 50 to 59. + +##### 4.1.4.2.2 Procedures for major additions to CAP + +In order to support the introduction of major functional changes, the protocol allows a synchronisation between the two applications with regard to which functionality is to be performed. This synchronisation takes place before the new function is invoked in either application entity, in order to avoid complicated fall-back procedures. + +##### 4.1.4.2.3 Procedures for minor additions to CAP + +The extension mechanism marker shall be used for future standardised minor additions to CAP. This mechanism implements extensions by including an "extensions marker" in the type definition. The extensions are expressed by optional fields that are placed after the marker. When an entity receives unrecognised parameters that occur after the extension marker, they are ignored. Refer to ITU-T Recommendation X.680 [53] for further details on the extension mechanism. + +##### 4.1.4.2.4 Procedures for inclusion of network specific additions to CAP + +This mechanism is based on the ability to explicitly declare fields of any type via the Macro facility in ASN.1 at the outermost level of a type definition. It works by defining an "ExtensionField" that is placed within the type definition. This extension field is defined as a set of extensions, where an extension can contain any type. Each extension is associated with an identification that unambiguously identifies the extension. Refer to ITU-T Recommendation Q.1400 [52] for a definition of this mechanism. + +#### 4.1.5 Definition and usage of LegID + +##### 4.1.5.1 Definition of LegID + +In CAP V4, two types of LegID may be exchanged between the gsmSCF and the gsmSSF. These are: + +- Sending Side LegID; and +- Receiving Side LegID. + +Sending Side LegID is always used in operations sent from the gsmSCF to the gsmSSF, and Receiving Side LegID is always used in operations sent from the gsmSSF to the gsmSCF. + +##### 4.1.5.2 Allocation of LegID + +For all operations containing a LegID: + +- LegID = 1 shall always refer to the Calling Party, more specifically that party in the call present when InitialDP is sent to the gsmSCF; +- LegID = 2 shall always refer to a Called Party, more specifically a party in the call created as a result of the InitialDP operation, followed by the Connect, Continue or ContinueWithArgument operation. + +- LegID > 2 shall always refer to a Called Party, more specifically a party in the call created as a result of the InitiateCallAttempt operation, followed by the ContinueWithArgument operation. + +## 4.2 SACF/MACF rules + +### 4.2.1 Reflection of TC AC + +TC AC negotiation rules require that the proposed AC, if acceptable, is reflected in the first backwards message. + +NOTE: If the gsmSSF, gprsSSF or smsSSF provides an AC which is not acceptable to the gsmSCF, then an alternate AC shall not be returned. If the AC presented to the gsmSCF is not acceptable, then this is most probably due to an error in subscriber data provisioning or an error at the gsmSSF, gprsSSF or smsSSF. + +### 4.2.2 Sequential/parallel execution of operations + +In some cases it may be necessary to distinguish whether operations should be performed sequentially or in parallel (synchronised). Operations which may be synchronised are: + +- charging operations; may be synchronised with any other operation(s). + +The method of indicating to the receiving entity that operations should be synchronised is to transmit these operations in a single TC message. If one of the operations identified above shall not be executed until the execution of another operation has progressed to a certain extent or has finished, then the sending PE shall control this by sending the operations in two separate TC messages. + +This method does not imply that all operations sent in a single TC message shall be executed simultaneously, but that where it could make sense to do so (in the situations identified above) the operations should be synchronised. + +In the case of inconsistency between the above-mentioned generic rules and the FE-specific rules, as specified in clause 9, the FE-specific rules take precedence over the generic rules. + +## 5 Common CAP Types + +### 5.1 Data types + +``` +CAP-datatypes {itu-t(0) identified-organization(4) etsi(0) mobileDomain(0) umts-network(1) +modules(3) cap-datatypes(52) version8(7)} +``` + +``` +DEFINITIONS IMPLICIT TAGS ::= BEGIN +``` + +``` +IMPORTS +``` + +``` +Duration, +Integer4, +Interval, +LegID, +ServiceKey +``` + +``` +FROM CS1-DataTypes {itu-t(0) identified-organization(4) etsi(0) inDomain(1) in-network(1) +modules(0) cs1-datatypes(2) version1(0)} +``` + +``` +BothwayThroughConnectionInd, +CriticalityType, +MiscCallInfo +``` + +``` +FROM CS2-datatypes {itu-t(0) identified-organization(4) etsi(0) inDomain(1) in-network(1) +cs2(20) modules(0) in-cs2-datatypes(0) version1(0)} +``` + +``` +AddressString, +CellGlobalIdOrServiceAreaIdFixedLength, +Ext-BasicServiceCode, +IMSI, +ISDN-AddressString, +LAIFixedLength, +NAEA-CIC +``` + +``` +FROM MAP-CommonDataTypes {itu-t(0) identified-organization(4) etsi(0) mobileDomain(0)} +``` + +``` + +gsm-Network(1) modules(3) map-CommonDataTypes(18) version12(12)} + + Ext-QoS-Subscribed, + Ext2-QoS-Subscribed, + Ext3-QoS-Subscribed, + GeographicalInformation, + GSN-Address, + LocationInformation, + LSAIdentity, + QoS-Subscribed, + RAIdentity, + SubscriberState, + GPRSChargingID +FROM MAP-MS-DataTypes {itu-t(0) identified-organization(4) etsi(0) mobileDomain(0) +gsm-Network(1) modules(3) map-MS-DataTypes(11) version12(12)} + + CallReferenceNumber, + SuppressionOfAnnouncement +FROM MAP-CH-DataTypes {itu-t(0) identified-organization(4) etsi(0) mobileDomain(0) +gsm-Network(1) modules(3) map-CH-DataTypes(13) version12(12)} + + tc-Messages, + classes +FROM CAP-object-identifiers {itu-t(0) identified-organization(4) etsi(0) mobileDomain(0) +umts-network(1) modules(3) cap-object-identifiers(100) version8(7)} + + EXTENSION, + PARAMETERS-BOUND, + SupportedExtensions +FROM CAP-classes classes + + ExtensionContainer +FROM MAP-ExtensionDataTypes {itu-t(0) identified-organization(4) etsi(0) mobileDomain(0) +gsm-Network(1) modules(3) map-ExtensionDataTypes(21) version12(12)} + +; + +AccessPointName {PARAMETERS-BOUND : bound} ::= OCTET STRING (SIZE( + bound.&minAccessPointNameLength .. bound.&maxAccessPointNameLength)) +-- Indicates the AccessPointName, refer to 3GPP TS 24.008 [9] for the encoding. +-- It shall be coded as in the value part defined in 3GPP TS 24.008, +-- i.e. the 3GPP TS 24.008 IEI and 3GPP TS 24.008 octet length indicator +-- shall not be included. + +AChBillingChargingCharacteristics {PARAMETERS-BOUND : bound} ::= OCTET STRING (SIZE + (bound.&minAChBillingChargingLength .. bound.&maxAChBillingChargingLength)) + (CONSTRAINED BY {-- shall be the result of the BER-encoded value of the type -- + CAMEL-AChBillingChargingCharacteristics {bound}}) +-- The AChBillingChargingCharacteristics parameter specifies the charging related information +-- to be provided by the gsmSSF and the conditions on which this information has to be reported +-- back to the gsmSCF with the ApplyChargingReport operation. The value of the +-- AChBillingChargingCharacteristics of type OCTET STRING carries a value of the ASN.1 data type: +-- CAMEL-AChBillingChargingCharacteristics. The normal encoding rules are used to encode this +-- value. +-- The violation of the UserDefinedConstraint shall be handled as an ASN.1 syntax error. + +AChChargingAddress {PARAMETERS-BOUND : bound} ::= CHOICE { + legID [2] LegID, + srfConnection [50] CallSegmentID {bound} +} + +AdditionalCallingPartyNumber {PARAMETERS-BOUND : bound} ::= Digits {bound} +-- Indicates the Additional Calling Party Number. + +AlertingPattern ::= OCTET STRING (SIZE(3)) +-- Indicates a specific pattern that is used to alert a subscriber +-- (e.g. distinctive ringing, tones, etc.). + +``` + +- The encoding of the last octet of this parameter is as defined in 3GPP TS 29.002 [11]. +- Only the trailing OCTET is used, the remaining OCTETS shall be sent as NULL (zero) +- The receiving side shall ignore the leading two OCTETS. + +``` +AOCBeforeAnswer ::= SEQUENCE { + aOCInitial [0] CAI-GSM0224, + aOCSubsequent [1] AOCSubsequent OPTIONAL +} +``` + +``` +AOCGPRS ::= SEQUENCE { + aOCInitial [0] CAI-GSM0224, + aOCSubsequent [1] AOCSubsequent OPTIONAL +} +``` + +``` +AOCSubsequent ::= SEQUENCE { + CAI-GSM0224 [0] CAI-GSM0224 , + tariffSwitchInterval [1] INTEGER (1..86400) OPTIONAL +} +``` + +– tariffSwitchInterval is measured in 1 second units + +``` +AppendFreeFormatData ::= ENUMERATED { + overwrite(0), + append (1) +} +``` + +ApplicationTimer ::= INTEGER (0..2047) + +– Used by the gsmSCF to set a timer in the gsmSSF. The timer is in seconds. + +AssistingSSIPRoutingAddress {PARAMETERS-BOUND : bound} ::= Digits {bound} + +– Indicates the destination address of the gsmSRF for the assist procedure. + +``` +AudibleIndicator ::= CHOICE { + tone BOOLEAN, + burstList [1] BurstList +} +``` + +``` +BackwardServiceInteractionInd ::= SEQUENCE { + conferenceTreatmentIndicator [1] OCTET STRING (SIZE(1)) OPTIONAL, + -- acceptConferenceRequest 'xxxx xx01'B + -- rejectConferenceRequest 'xxxx xx10'B + -- if absent from Connect or ContinueWithArgument, + -- then CAMEL service does not affect conference treatment + callCompletionTreatmentIndicator [2] OCTET STRING (SIZE(1)) OPTIONAL, + -- acceptCallCompletionServiceRequest 'xxxx xx01'B, + -- rejectCallCompletionServiceRequest 'xxxx xx10'B + -- if absent from Connect or ContinueWithArgument, + -- then CAMEL service does not affect call completion treatment + ... +} +``` + +``` +BasicGapCriteria {PARAMETERS-BOUND : bound} ::= CHOICE { + calledAddressValue [0] Digits {bound}, + gapOnService [2] GapOnService, + calledAddressAndService [29] SEQUENCE { + calledAddressValue [0] Digits {bound}, + serviceKey [1] ServiceKey, + ... + }, + callingAddressAndService [30] SEQUENCE { + callingAddressValue [0] Digits {bound}, + serviceKey [1] ServiceKey, + ... + } +} +``` + +- Both calledAddressValue and callingAddressValue can be +- incomplete numbers, in the sense that a limited amount of digits can be given. + +- For the handling of numbers starting with the same digit string refer to the detailed procedure of the CallGap operation + +``` +BCSMEvent{PARAMETERS-BOUND : bound} ::= SEQUENCE { + eventTypeBCSM [0] EventTypeBCSM, + monitorMode [1] MonitorMode, + legID [2] LegID OPTIONAL, + dpSpecificCriteria [30] DpSpecificCriteria {bound} OPTIONAL, + automaticRearm [50] NULL OPTIONAL, + ... +} +``` + +- Indicates the BCSM Event information for monitoring. + +``` +BCSM-Failure {PARAMETERS-BOUND : bound} ::= SEQUENCE { + legID [0] LegID OPTIONAL, + cause [2] Cause {bound} OPTIONAL, + ... +} +``` + +``` +BearerCapability {PARAMETERS-BOUND : bound} ::= CHOICE { + bearerCap [0] OCTET STRING (SIZE(2..bound.&maxBearerCapabilityLength)) +} +``` + +- Indicates the type of bearer capability connection to the user. For bearerCap, the ISUP User +- Service Information, ETSI EN 300 356-1 [23] +- encoding shall be used. + +``` +Burst ::= SEQUENCE { + numberOfBursts [0] INTEGER (1..3) DEFAULT 1, + burstInterval [1] INTEGER (1..1200) DEFAULT 2, + numberOfTonesInBurst [2] INTEGER (1..3) DEFAULT 3, + toneDuration [3] INTEGER (1..20) DEFAULT 2, + toneInterval [4] INTEGER (1..20) DEFAULT 2, + ... +} +``` + +- burstInterval, toneDuration and toneInterval are measured in 100 millisecond units + +``` +BurstList ::= SEQUENCE { + warningPeriod [0] INTEGER (1..1200) DEFAULT 30, + bursts [1] Burst, + ... +} +``` + +- warningPeriod is measured in 1 second units. + +``` +CAI-GSM0224 ::= SEQUENCE { + e1 [0] INTEGER (0..8191) OPTIONAL, + e2 [1] INTEGER (0..8191) OPTIONAL, + e3 [2] INTEGER (0..8191) OPTIONAL, + e4 [3] INTEGER (0..8191) OPTIONAL, + e5 [4] INTEGER (0..8191) OPTIONAL, + e6 [5] INTEGER (0..8191) OPTIONAL, + e7 [6] INTEGER (0..8191) OPTIONAL +} +``` + +- Indicates Charge Advice Information to the Mobile Station. For information regarding +- parameter usage, refer to 3GPP TS 22.024 [2]. + +``` +CalledPartyBCDNumber {PARAMETERS-BOUND : bound} ::= OCTET STRING (SIZE( + bound.&minCalledPartyBCDNumberLength .. bound.&maxCalledPartyBCDNumberLength)) +``` + +- Indicates the Called Party Number, including service selection information. +- Refer to 3GPP TS 24.008 [9] for encoding. +- This data type carries only the 'type of number', 'numbering plan +- identification' and 'number digit' fields defined in 3GPP TS 24.008 [9]; +- it does not carry the 'called party BCD number IEI' or 'length of called +- party BCD number contents'. +- In the context of the DestinationSubscriberNumber field in ConnectSMSArg or +- InitialDPSMSArg, a CalledPartyBCDNumber may also contain an alphanumeric +- character string. In this case, type-of-number '101'B is used, in accordance +- with 3GPP TS 23.040 [6]. The address is coded in accordance with the +- GSM 7-bit default alphabet definition and the SMS packing rules + +-- as specified in 3GPP TS 23.038 [15] in this case. + +CalledPartyNumber {PARAMETERS-BOUND : bound} ::= OCTET STRING (SIZE( + bound.&minCalledPartyNumberLength .. bound.&maxCalledPartyNumberLength)) + -- Indicates the Called Party Number. Refer to ETS EN 300 356-1 [23] for encoding. + +-- A CalledPartyNumber may contain national-specific values of the *Nature Of Address indicator*. The filling-in of the national-specific *Nature Of Address indicator* values shall be done in accordance with the national ISUP of the gsmSSF country, e.g. + -- ANSI T1.113-1995 [92]. + -- In terms of ETS EN 300 356-1 [23], the *Destination Address Field* is not present if the *destination address length* is set to zero. This is the case e.g. when the ANSI ISUP *Nature Of Address indicator* indicates *no number present, operator requested* (1110100) or *no number present, cut-through call to carrier* (1110101). + -- See also see 3GPP TS 23.078 [7]. + +CallingPartyNumber {PARAMETERS-BOUND : bound} ::= OCTET STRING (SIZE( + bound.&minCallingPartyNumberLength .. bound.&maxCallingPartyNumberLength)) + -- Indicates the Calling Party Number. Refer to ETS EN 300 356-1 [23] for encoding. + +CallResult {PARAMETERS-BOUND : bound} ::= OCTET STRING (SIZE( + bound.&minCallResultLength .. bound.&maxCallResultLength)) + (CONSTRAINED BY {-- shall be the result of the BER-encoded value of type - + CAMEL-CallResult {bound}}) + -- The violation of the UserDefinedConstraint shall be handled as an ASN.1 syntax error. + +-- This parameter provides the gsmSCF with the charging related information previously requested + -- using the ApplyCharging operation. This shall include the partyToCharge parameter as + -- received in the related ApplyCharging operation to correlate the result to the request + +CallSegmentFailure {PARAMETERS-BOUND : bound} ::= SEQUENCE { + callSegmentID [0] CallSegmentID {bound} OPTIONAL, + cause [2] Cause {bound} OPTIONAL, + ... + } + +CallSegmentID {PARAMETERS-BOUND : bound} ::= INTEGER (1..bound.&numOfCSs) + +CallSegmentToCancel {PARAMETERS-BOUND : bound} ::= SEQUENCE { + invokeID [0] InvokeID OPTIONAL, + callSegmentID [1] CallSegmentID {bound} OPTIONAL, + ... + } + +CAMEL-AChBillingChargingCharacteristics {PARAMETERS-BOUND : bound} ::= CHOICE { + timeDurationCharging [0] SEQUENCE { + maxCallPeriodDuration [0] INTEGER (1..864000), + releaseIfDurationExceeded [1] BOOLEAN DEFAULT FALSE, + tariffSwitchInterval [2] INTEGER (1..86400) OPTIONAL, + audibleIndicator [3] AudibleIndicator DEFAULT tone: FALSE, + extensions [4] Extensions {bound} OPTIONAL, + ... + } + } + +-- tariffSwitchInterval is measured in 1 second units. + -- maxCallPeriodDuration is measured in 100 millisecond units + +CAMEL-CallResult {PARAMETERS-BOUND : bound} ::= CHOICE { + timeDurationChargingResult [0] SEQUENCE { + partyToCharge [0] ReceivingSideID, + timeInformation [1] TimeInformation, + legActive [2] BOOLEAN DEFAULT TRUE, + callLegReleasedAtTcpExpiry [3] NULL OPTIONAL, + extensions [4] Extensions {bound} OPTIONAL, + aChChargingAddress [5] AChChargingAddress {bound} + DEFAULT legID:receivingSideID:leg1, + +``` + + ... + } +} + +``` + +CAMEL-FCIBillingChargingCharacteristics {PARAMETERS-BOUND : bound} ::= CHOICE{ + +``` + + fCIBCCCAMELsequence1 [0] SEQUENCE { + freeFormatData [0] OCTET STRING (SIZE( + bound.&minFCIBillingChargingDataLength .. bound.&maxFCIBillingChargingDataLength)), + partyToCharge [1] SendingSideID DEFAULT sendingSideID: leg1, + appendFreeFormatData [2] AppendFreeFormatData DEFAULT overwrite, + ... + } +} + +``` + +CAMEL-FCIGPRSBillingChargingCharacteristics {PARAMETERS-BOUND : bound} ::= SEQUENCE{ + +``` + + fCIBCCCAMELsequence1 [0] SEQUENCE { + freeFormatData [0] OCTET STRING (SIZE( + bound.&minFCIBillingChargingDataLength .. bound.&maxFCIBillingChargingDataLength)), + pDPID [1] PDPID OPTIONAL, + appendFreeFormatData [2] AppendFreeFormatData DEFAULT overwrite, + ... + } +} + +``` + +CAMEL-FCISMSBillingChargingCharacteristics {PARAMETERS-BOUND : bound} ::= CHOICE{ + +``` + + fCIBCCCAMELsequence1 [0] SEQUENCE { + freeFormatData [0] OCTET STRING (SIZE( + bound.&minFCIBillingChargingDataLength .. bound.&maxFCIBillingChargingDataLength)), + appendFreeFormatData [1] AppendFreeFormatData DEFAULT overwrite + } +} + +``` + +CAMEL-SCIBillingChargingCharacteristics ::= CHOICE { + +``` + + aOCBeforeAnswer [0] AOCBeforeAnswer, + aOCAfterAnswer [1] AOCS subsequent, + aOC-extension [2] CAMEL-SCIBillingChargingCharacteristicsAlt +} + +``` + +CAMEL-SCIBillingChargingCharacteristicsAlt ::= SEQUENCE { + +``` + + ... +} + +``` + +-- This datatype is for extension in future releases. + +CAMEL-SCIGPRSBillingChargingCharacteristics ::= SEQUENCE { + +``` + + aOCGPRS [0] AOCGPRS, + pDPID [1] PDPID OPTIONAL, + ... +} + +``` + +Carrier {PARAMETERS-BOUND : bound} ::= OCTET STRING (SIZE( + bound.&minCarrierLength .. bound.&maxCarrierLength)) + +– This parameter is used for North America (na) only. + +– It contains the carrier selection field (first octet) followed by Carrier ID + +– information (North America (na)). + +– The Carrier selection is one octet and is encoded as: + +| | | +|------------|---------------------------------------------------------------------------------------------------------------------------| +| – 00000000 | No indication | +| – 00000001 | Selected carrier identification code (CIC) pre subscribed and not input by calling party | +| – | | +| – 00000010 | Selected carrier identification code (CIC) pre subscribed and input by calling party | +| – | | +| – 00000011 | Selected carrier identification code (CIC) pre subscribed, no indication of whether input by calling party (undetermined) | +| – | | +| – 00000100 | Selected carrier identification code (CIC) not pre subscribed and input by calling party | +| – | | + +- 00000101 +- to            Spare +- 11111110 +- 11111111       Reserved + +-- Refer to ANSI T1.113-1995 [92] for encoding of na carrier ID information (3 octets). + +``` + +Cause {PARAMETERS-BOUND : bound} ::= OCTET STRING (SIZE( + bound.&minCauseLength .. bound.&maxCauseLength)) + +``` + +- Indicates the cause for interface related information. +- Refer to ETSI EN 300 356-1 [23] Cause parameter for encoding. +- For the use of cause and location values refer to ITU-T Recommendation Q.850 [47] +- Shall always include the cause value and shall also include the diagnostics field, +- if available. + +``` + +CGEncountered ::= ENUMERATED { + noCGEncountered (0), + manualCGEncountered (1), + scpOverload (2) +} + +``` + +-- Indicates the type of automatic call gapping encountered, if any. + +``` + +ChangeOfPositionControlInfo {PARAMETERS-BOUND : bound} ::= SEQUENCE SIZE +(1..bound.&numOfChangeOfPositionControlInfo) OF ChangeOfLocation {bound} + +``` + +``` + +ChangeOfLocation {PARAMETERS-BOUND : bound} ::= CHOICE { + cellGlobalId [0] CellGlobalIdOrServiceAreaIdFixedLength, + serviceAreaId [1] CellGlobalIdOrServiceAreaIdFixedLength, + locationAreaId [2] LAIFixedLength, + inter-SystemHandOver [3] NULL, + inter-PLMNHandOver [4] NULL, + inter-MSCHandOver [5] NULL, + changeOfLocationAlt [6] ChangeOfLocationAlt {bound} +} + +``` + +- The cellGlobalId shall contain a Cell Global Identification. +- The serviceAreaId shall contain a Service Area Identification. + +``` + +ChangeOfLocationAlt {PARAMETERS-BOUND : bound} ::= SEQUENCE { + ... +} + +``` + +``` + +ChargeIndicator ::= OCTET STRING (SIZE (1)) + +``` + +- As specified in ITU-T Recommendation Q.763 as follows: +- no indication  'xxxx xx00'B +- no charge      'xxxx xx01'B +- charge         'xxxx xx10'B +- spare          'xxxx xx11'B +- Sending entity shall fill the upper six bits with '0's. +- Receiving entity shall ignore the upper six bits. + +``` + +ChargeNumber {PARAMETERS-BOUND : bound} ::= LocationNumber {bound} + +``` + +- Information sent in either direction indicating the chargeable number for the call and +- consisting of the odd/even indicator, nature of address indicator, numbering plan indicator, +- and address signals. + + + +- Uses the LocationNumber format which is based on the Location Number format as defined +- in ITU-T Recommendation Q.763 [45]. +- For example, the ChargeNumber may be a third party number to which a call is billed for +- the 3rd party billing service. In this case, the calling party may request operator assistance +- to charge the call to, for example, their home number. + + + +- For NA, this parameter uniquely identifies the chargeable number for a call sent into a North +- American long distance carrier. It transports the ChargeNumber Parameter Field as defined in +- ANSI T1.113-1995 [92]. This provides +- 1 octet for the nature of address indicator field, plus + +- - 1 octet for a numbering plan field, plus +- - up to 5 octets for the address signal (up to 10 digits) +- The Charge Number in ANSI T1.113-1995 [92] normally contains a 10 digit national number within +- the North American Numbering Plan (NANP); longer (e.g. international) charge numbers are not +- supported in ANSI T1.113-1995 [92]. + +ChargingCharacteristics ::= CHOICE { + +maxTransferredVolume [0] INTEGER (1..4294967295), +maxElapsedTime [1] INTEGER (1..86400) +} + +- maxTransferredVolume is measured in number of bytes +- maxElapsedTime is measured in seconds + +ChargingResult ::= CHOICE { + +transferredVolume [0] TransferredVolume, +elapsedTime [1] ElapsedTime +} + +ChargingRollOver ::= CHOICE { + +transferredVolumeRollOver [0] TransferredVolumeRollOver, +elapsedTimeRollOver [1] ElapsedTimeRollOver +} + +- *transferredVolumeRollOver* shall be reported if ApplyChargingReportGPRS reports volume and +- a roll-over has occurred in one or more volume counters. Otherwise, it shall be absent. +- *elapsedTimeRollOver* shall be reported if ApplyChargingReportGPRS reports duration and +- a roll-over has occurred in one or more duration counters. Otherwise, it shall be absent. + +CollectedDigits ::= SEQUENCE { + +minimumNbOfDigits [0] INTEGER (1..30) DEFAULT 1, +maximumNbOfDigits [1] INTEGER (1..30), +endOfReplyDigit [2] OCTET STRING (SIZE (1..2)) OPTIONAL, +cancelDigit [3] OCTET STRING (SIZE (1..2)) OPTIONAL, +startDigit [4] OCTET STRING (SIZE (1..2)) OPTIONAL, +firstDigitTimeOut [5] INTEGER (1..127) OPTIONAL, +interDigitTimeOut [6] INTEGER (1..127) OPTIONAL, +errorTreatment [7] ErrorTreatment DEFAULT stdErrorAndInfo, +interruptableAnnInd [8] BOOLEAN DEFAULT TRUE, +voiceInformation [9] BOOLEAN DEFAULT FALSE, +voiceBack [10] BOOLEAN DEFAULT FALSE +} + +- The use of voiceBack and the support of voice recognition via voiceInformation +- is network operator specific. +- The endOfReplyDigit, cancelDigit, and startDigit parameters have been +- designated as OCTET STRING, and are to be encoded as BCD, one digit per octet +- only, contained in the four least significant bits of each OCTET. The following encoding shall +- be applied for the non-decimal characters: +- 1011 (\*), 1100 (#). +- The usage is service dependent. +- firstDigitTimeOut and interDigitTimeOut are measured in seconds. + +CollectedInfo ::= CHOICE { + +collectedDigits [0] CollectedDigits +} + +ConnectedNumberTreatmentInd ::= ENUMERATED { + +noINImpact (0), +presentationRestricted (1), +presentCalledINNumber (2), +presentCallINNumberRestricted (3) +} + +- This parameter is used to suppress or to display the connected number. + +ControlType ::= ENUMERATED { + +sCPOverloaded (0), + +``` + + manuallyInitiated (1) + } + +``` + +``` + +CompoundCriteria {PARAMETERS-BOUND : bound} ::= SEQUENCE { + basicGapCriteria [0] BasicGapCriteria {bound}, + scfID [1] ScfID {bound} OPTIONAL +} + +``` + +CorrelationID {PARAMETERS-BOUND : bound} ::= Digits {bound} + – used by gsmSCF for correlation with a previous operation. + +DateAndTime ::= OCTET STRING (SIZE(7)) + – DateAndTime is BCD encoded. The year digit indicating millenium occupies bits + – 0-3 of the first octet, and the year digit indicating century occupies bits + – 4-7 of the first octet. + – The year digit indicating decade occupies bits 0-3 of the second octet, + – whilst the digit indicating the year within the decade occupies bits 4-7 of + – the second octet. + – The most significant month digit occupies bits 0-3 of the third octet, + – and the least significant month digit occupies bits 4-7 of the third octet. + – The most significant day digit occupies bits 0-3 of the fourth octet, + – and the least significant day digit occupies bits 4-7 of the fourth octet. + – The most significant hours digit occupies bits 0-3 of the fifth octet, + – and the least significant digit occupies bits 4-7 of the fifth octet. + – The most significant minutes digit occupies bits 0-3 of the sixth octet, + – and the least significant digit occupies bits 4-7 of the sixth octet. + – The most significant seconds digit occupies bits 0-3 of the seventh octet, + – and the least seconds significant digit occupies bits 4-7 of the seventh octet. + – For the encoding of digits in an octet, refer to the timeAndtimezone parameter. + +DestinationRoutingAddress {PARAMETERS-BOUND : bound} ::= SEQUENCE SIZE(1) OF + CalledPartyNumber {bound} + – Indicates the Called Party Number. + +Digits {PARAMETERS-BOUND : bound} ::= OCTET STRING (SIZE( + bound.&minDigitsLength .. bound.&maxDigitsLength)) + – Indicates the address signalling digits. + – Refer to ETSI EN 300 356-1 [23] Generic Number & Generic Digits parameters for encoding. + – The coding of the subfields 'NumberQualifier' in Generic Number and 'TypeOfDigits' in + – Generic Digits are irrelevant to the CAP; + – the ASN.1 tags are sufficient to identify the parameter. + – The ISUP format does not allow to exclude these subfields, + – therefore the value is network operator specific. + – + – The following parameters shall use Generic Number: + – - AdditionalCallingPartyNumber for InitialDP + – - AssistingSSPIPRoutingAddress for EstablishTemporaryConnection + – - CorrelationID for AssistRequestInstructions + – - CalledAddressValue for all occurrences, CallingAddressValue for all occurrences. + – + – The following parameters shall use Generic Digits: + – - CorrelationID in EstablishTemporaryConnection + – - number in VariablePart + – - digitsResponse in ReceivedInformationArg + – - midCallEvents in oMidCallSpecificInfo and tMidCallSpecificInfo + – + – In the digitsResponse and midCalEvents, the digits may also include the '\*', '#', + – a, b, c and d digits by using the IA5 character encoding scheme. If the BCD even or + – BCD odd encoding scheme is used, then the following encoding shall be applied for the + – non-decimal characters: 1011 (\*), 1100 (#). + – + – AssistingSSPIPRoutingAddress in EstablishTemporaryConnection and CorrelationID in + – AssistRequestInstructions may contain a Hex B digit as address signal. Refer to + – Annex A.6 for the usage of the Hex B digit. + – + +- Note that when CorrelationID is transported in Generic Digits, then the digits shall +- always be BCD encoded. + +``` + +DpSpecificCriteria {PARAMETERS-BOUND : bound} ::= CHOICE { + applicationTimer [1] ApplicationTimer, + midCallControlInfo [2] MidCallControlInfo, + dpSpecificCriteriaAlt [3] DpSpecificCriteriaAlt {bound} +} +-- Exception handling: reception of DpSpecificCriteriaAlt shall be treated like +-- reception of no DpSpecificCriteria. +-- The gsmSCF may set a timer in the gsmSSF for the No_Answer event. +-- If the user does not answer the call within the allotted time, +-- then the gsmSSF reports the event to the gsmSCF. +-- The gsmSCF may define a criterion for the detection of DTMF digits during a call. +-- The gsmSCF may define other criteria in the dpSpecificCriteriaAlt alternative +-- in future releases. + +``` + +``` + +DpSpecificCriteriaAlt {PARAMETERS-BOUND : bound} ::= SEQUENCE { + ... + changeOfPositionControlInfo [0] ChangeOfPositionControlInfo {bound} + numberOfDigits [1] NumberOfDigits OPTIONAL, + interDigitTimeout [2] INTEGER (1..127) OPTIONAL +} +-- interDigitTimeout duration in seconds. + +``` + +``` + +DpSpecificInfoAlt {PARAMETERS-BOUND : bound} ::= SEQUENCE { + ... + oServiceChangeSpecificInfo [0] SEQUENCE { + ext-basicServiceCode [0] Ext-BasicServiceCode OPTIONAL, + ..., + initiatorOfServiceChange [1] InitiatorOfServiceChange OPTIONAL, + natureOfServiceChange [2] NatureOfServiceChange OPTIONAL + } + tServiceChangeSpecificInfo [1] SEQUENCE { + ext-basicServiceCode [0] Ext-BasicServiceCode OPTIONAL, + ..., + initiatorOfServiceChange [1] InitiatorOfServiceChange OPTIONAL, + natureOfServiceChange [2] NatureOfServiceChange OPTIONAL + } + collectedInfoSpecificInfo [2] SEQUENCE { + calledPartyNumber [0] CalledPartyNumber OPTIONAL, + ... + } +} +-- This datatype is for extension in future releases. + +``` + +``` + +ElapsedTime ::= CHOICE { + timeGPRSIfNoTariffSwitch [0] INTEGER (0..86400), + timeGPRSIfTariffSwitch [1] SEQUENCE { + timeGPRSSinceLastTariffSwitch [0] INTEGER (0..86400), + timeGPRSTariffSwitchInterval [1] INTEGER (0..86400) OPTIONAL + } +} +-- timeGPRSIfNoTariffSwitch is measured in seconds +-- timeGPRSSinceLastTariffSwitch and timeGPRSTariffSwitchInterval are measured in seconds + +``` + +``` + +ElapsedTimeRollOver ::= CHOICE { + rO-TimeGPRSIfNoTariffSwitch [0] INTEGER (0..255), + rO-TimeGPRSIfTariffSwitch [1] SEQUENCE { + rO-TimeGPRSSinceLastTariffSwitch [0] INTEGER (0..255) OPTIONAL, + rO-TimeGPRSTariffSwitchInterval [1] INTEGER (0..255) OPTIONAL + } +} +-- rO-TimeGPRSIfNoTariffSwitch, rO-TimeGPRSSinceLastTariffSwitch and +-- rO-TimeGPRSTariffSwitchInterval +-- present counters indicating the number of parameter range rollovers. + +``` + +``` + +EndUserAddress {PARAMETERS-BOUND: bound} ::= SEQUENCE { + pDPTypeOrganization [0] OCTET STRING (SIZE(1)), + pDPTypeNumber [1] OCTET STRING (SIZE(1)), + pDPAddress [2] OCTET STRING (SIZE( + bound.&minPDPAddressLength .. bound.&maxPDPAddressLength)) + OPTIONAL +} +-- Indicates the EndUserAddress, refer to 3GPP TS 29.060 [12] for the encoding. +-- The pDPTypeOrganization shall use the least significant 4 bits of the octet encoded. +-- The sender of this parameter shall set the most significant 4 bits of the octet to 1. +-- The receiver of this parameter shall ignore the most significant 4 bits of this octet. + +ErrorTreatment ::= ENUMERATED { + stdErrorAndInfo (0), + help (1), + repeatPrompt (2) +} +-- stdErrorAndInfo means returning the 'ImproperCallerResponse' error in the event of an error +-- condition during collection of user info. + +EventSpecificInformationBCSM {PARAMETERS-BOUND : bound} ::= CHOICE { + routeSelectFailureSpecificInfo [2] SEQUENCE { + failureCause [0] Cause {bound} + OPTIONAL, + ... + }, + oCalledPartyBusySpecificInfo [3] SEQUENCE { + busyCause [0] Cause {bound} + OPTIONAL, + ... + }, + oNoAnswerSpecificInfo [4] SEQUENCE { + -- no specific info defined -- + ... + }, + oAnswerSpecificInfo [5] SEQUENCE { + destinationAddress [50] CalledPartyNumber {bound} + OPTIONAL, + or-Call [51] NULL + OPTIONAL, + forwardedCall [52] NULL + OPTIONAL, + chargeIndicator [53] ChargeIndicator + OPTIONAL, + ext-basicServiceCode [54] Ext-BasicServiceCode + OPTIONAL, + ext-basicServiceCode2 [55] Ext-BasicServiceCode + OPTIONAL, + ... + }, + oMidCallSpecificInfo [6] SEQUENCE { + midCallEvents [1] CHOICE { + dTMFDigitsCompleted [3] Digits {bound}, + dTMFDigitsTimeout [4] Digits {bound} + } + OPTIONAL, + ... + }, + oDisconnectSpecificInfo [7] SEQUENCE { + releaseCause [0] Cause {bound} + OPTIONAL, + ... + }, + tBusySpecificInfo [8] SEQUENCE { + busyCause [0] Cause {bound} + OPTIONAL, + callForwarded [50] NULL + OPTIONAL, + routeNotPermitted [51] NULL + OPTIONAL, + forwardingDestinationNumber [52] CalledPartyNumber {bound} + OPTIONAL, + ... + }, + tNoAnswerSpecificInfo [9] SEQUENCE { + callForwarded [50] NULL + OPTIONAL, + forwardingDestinationNumber [52] CalledPartyNumber {bound} + OPTIONAL, + ... + }, + tAnswerSpecificInfo [10] SEQUENCE { + destinationAddress [50] CalledPartyNumber {bound} + OPTIONAL, + } +} + +``` + +``` + + or-Call [51] NULL OPTIONAL, + forwardedCall [52] NULL OPTIONAL, + chargeIndicator [53] ChargeIndicator OPTIONAL, + ext-basicServiceCode [54] Ext-BasicServiceCode OPTIONAL, + ext-basicServiceCode2 [55] Ext-BasicServiceCode OPTIONAL, + ... + }, + tMidCallSpecificInfo [11] SEQUENCE { + midCallEvents [1] CHOICE { + dTMFDigitsCompleted [3] Digits {bound}, + dTMFDigitsTimeOut [4] Digits {bound} + } OPTIONAL, + ... + }, + tDisconnectSpecificInfo [12] SEQUENCE { + releaseCause [0] Cause {bound} OPTIONAL, + ... + }, + oTermSeizedSpecificInfo [13] SEQUENCE { + locationInformation [50] LocationInformation OPTIONAL, + ... + }, + callAcceptedSpecificInfo [20] SEQUENCE { + locationInformation [50] LocationInformation OPTIONAL, + ... + }, + oAbandonSpecificInfo [21] SEQUENCE { + routeNotPermitted [50] NULL OPTIONAL, + ... + }, + oChangeOfPositionSpecificInfo [50] SEQUENCE { + locationInformation [50] LocationInformation OPTIONAL, + ..., + metDPCriteriaList [51] MetDPCriteriaList {bound} OPTIONAL + }, + tChangeOfPositionSpecificInfo [51] SEQUENCE { + locationInformation [50] LocationInformation OPTIONAL, + ..., + metDPCriteriaList [51] MetDPCriteriaList {bound} OPTIONAL + }, + dpSpecificInfoAlt [52] DpSpecificInfoAlt {bound} +} + +``` + +-- Indicates the call related information specific to the event. + +``` + +EventSpecificInformationSMS ::= CHOICE { + o-smsFailureSpecificInfo [0] SEQUENCE { + failureCause [0] MO-SMSCause OPTIONAL, + ... + }, + o-smsSubmissionSpecificInfo [1] SEQUENCE { + -- no specific info defined-- + ... + }, + t-smsFailureSpecificInfo [2] SEQUENCE { + failureCause [0] MT-SMSCause OPTIONAL, + ... + }, + t-smsDeliverySpecificInfo [3] SEQUENCE { + -- no specific info defined-- + ... + } +} + +``` + +``` + +EventTypeBCSM ::= ENUMERATED { + collectedInfo (2), + analyzedInformation (3), + routeSelectFailure (4), + oCalledPartyBusy (5), + +``` + +``` + + oNoAnswer (6), + oAnswer (7), + oMidCall (8), + oDisconnect (9), + oAbandon (10), + termAttemptAuthorized (12), + tBusy (13), + tNoAnswer (14), + tAnswer (15), + tMidCall (16), + tDisconnect (17), + tAbandon (18), + oTermSeized (19), + callAccepted (27), + oChangeOfPosition (50), + tChangeOfPosition (51), + ..., + oServiceChange (52), + tServiceChange (53) + } + +``` + +- Indicates the BCSM detection point event. +- Values analyzedInformation and termAttemptAuthorized may be used +- for TDPs only. +- Exception handling: reception of an unrecognized value shall be treated +- like reception of no detection point. + +``` + +EventTypeSMS ::= ENUMERATED { + sms-CollectedInfo (1), + o-smsFailure (2), + o-smsSubmission (3), + sms-DeliveryRequested (11), + t-smsFailure (12), + t-smsDelivery (13) +} + +``` + +- Values sms-CollectedInfo and sms-DeliveryRequested may be used for TDPs only. + +Extensions {PARAMETERS-BOUND : bound} ::= SEQUENCE SIZE (1..bound.&numOfExtensions) OF ExtensionField + +``` + +ExtensionField ::= SEQUENCE { + type EXTENSION.&id ({SupportedExtensions}), + -- shall identify the value of an EXTENSION type + criticality CriticalityType DEFAULT ignore, + value [1] EXTENSION.&ExtensionType ({SupportedExtensions}@{type}), + ... +} + +``` + +- This parameter indicates an extension of an argument data type. +- Its content is network operator specific + +``` + +FCIBillingChargingCharacteristics {PARAMETERS-BOUND : bound} ::= OCTET STRING (SIZE( + bound.&minFCIBillingChargingLength .. bound.&maxFCIBillingChargingLength)) + (CONSTRAINED BY {-- shall be the result of the BER-encoded value of type -- + CAMEL-FCIBillingChargingCharacteristics {bound}}) + +``` + +- This parameter indicates the billing and/or charging characteristics. +- The violation of the UserDefinedConstraint shall be handled as an ASN.1 syntax error. + +``` + +FCIGPRSBillingChargingCharacteristics {PARAMETERS-BOUND : bound} ::= OCTET STRING (SIZE( + bound.&minFCIBillingChargingLength .. bound.&maxFCIBillingChargingLength)) + (CONSTRAINED BY {-- shall be the result of the BER-encoded value of type -- + CAMEL-FCIGPRSBillingChargingCharacteristics {bound}}) + +``` + +- This parameter indicates the GPRS billing and/or charging characteristics. +- The violation of the UserDefinedConstraint shall be handled as an ASN.1 syntax error. + +``` + +FCISMSBillingChargingCharacteristics {PARAMETERS-BOUND : bound} ::= OCTET STRING (SIZE( + bound.&minFCIBillingChargingLength .. bound.&maxFCIBillingChargingLength)) + (CONSTRAINED BY {-- shall be the result of the BER-encoded value of type -- + CAMEL-FCISMSBillingChargingCharacteristics {bound}}) + +``` + +- This parameter indicates the SMS billing and/or charging characteristics. +- The violation of the UserDefinedConstraint shall be handled as an ASN.1 syntax error. + +``` + +ForwardServiceInteractionInd ::= SEQUENCE { + conferenceTreatmentIndicator [1] OCTET STRING (SIZE(1)) OPTIONAL, + -- acceptConferenceRequest 'xxxx xx01'B + -- rejectConferenceRequest 'xxxx xx10'B + -- if absent from Connect or ContinueWithArgument, + -- then CAMEL service does not affect conference treatment + callDiversionTreatmentIndicator [2] OCTET STRING (SIZE(1)) OPTIONAL, + -- callDiversionAllowed 'xxxx xx01'B + -- callDiversionNotAllowed 'xxxx xx10'B + -- if absent from Connect or ContinueWithArgument, + -- then CAMEL service does not affect call diversion treatment + callingPartyRestrictionIndicator [4] OCTET STRING (SIZE(1)) OPTIONAL, + -- noINImpact 'xxxx xx01'B + -- presentationRestricted 'xxxx xx10'B + -- if absent from Connect or ContinueWithArgument, + -- then CAMEL service does not affect calling party restriction treatment + ... +} + +GapCriteria {PARAMETERS-BOUND : bound} ::= CHOICE { + basicGapCriteria BasicGapCriteria {bound}, + compoundGapCriteria CompoundCriteria {bound} +} + +GapIndicators ::= SEQUENCE { + duration [0] Duration, + gapInterval [1] Interval, + ... +} + +-- Indicates the call gapping characteristics. +-- No call gapping when gapInterval equals 0. + +GapOnService ::= SEQUENCE { + serviceKey [0] ServiceKey, + ... +} + +GapTreatment {PARAMETERS-BOUND : bound} ::= CHOICE { + informationToSend [0] InformationToSend {bound}, + releaseCause [1] Cause {bound} +} + +-- The default value for Cause is the same as in ISUP. + +GenericNumber {PARAMETERS-BOUND : bound} ::= OCTET STRING (SIZE( + bound.&minGenericNumberLength .. bound.&maxGenericNumberLength)) +-- Indicates a generic number. Refer to ETSI EN 300 356-1 [23] Generic number for encoding. + +GenericNumbers {PARAMETERS-BOUND : bound} ::= SET SIZE(1..bound.&numOfGenericNumbers) OF GenericNumber +{bound} + +GPRS-QoS ::= CHOICE { + short-QoS-format [0] QoS-Subscribed, + long-QoS-format [1] Ext-QoS-Subscribed +} + +-- Short-QoS-format shall be sent for QoS in pre GSM release 99 format. +-- Long-QoS-format shall be sent for QoS in GSM release 99 (and beyond) format. +-- Which of the two QoS formats shall be sent is determined by which QoS +-- format is available in the SGSN at the time of sending. +-- Refer to 3GPP TS 29.002 [11] for encoding details of QoS-Subscribed and +-- Ext-QoS-Subscribed. + +GPRS-QoS-Extension ::= SEQUENCE { + supplement-to-long-QoS-format [0] Ext2-QoS-Subscribed, + ... +} + +``` + +``` + + additionalSupplement [1] Ext3-QoS-Subscribed OPTIONAL +} + +``` + +GPRSCause {PARAMETERS-BOUND : bound} ::= OCTET STRING (SIZE + (bound.&minGPRSCauseLength .. bound.&maxGPRSCauseLength)) + -- Shall only include the cause value. + +- 00000000 Unspecified +- All other values shall be interpreted as 'Unspecified'. +- +- This parameter indicates the cause for CAP interface related information. +- The GPRSCause mapping to/from GTP cause values specified in the 3GPP TS 29.060 [12] and +- to/from 3GPP TS 24.008 [9] GMM cause and SM cause values are outside scope of this document. + +``` + +GPRSEvent ::= SEQUENCE { + gPRSEventType [0] GPRSEventType, + monitorMode [1] MonitorMode +} + +``` + +- Indicates the GPRS event information for monitoring. + +GPRSEventSpecificInformation {PARAMETERS-BOUND : bound} ::= CHOICE { + +``` + + attachChangeOfPositionSpecificInformation + [0] SEQUENCE { + locationInformationGPRS [0] LocationInformationGPRS OPTIONAL, + ... + }, + + pdp-ContextchangeOfPositionSpecificInformation + [1] SEQUENCE { + accessPointName [0] AccessPointName {bound} OPTIONAL, + chargingID [1] GPRSChargingID OPTIONAL, + locationInformationGPRS [2] LocationInformationGPRS OPTIONAL, + endUserAddress [3] EndUserAddress {bound} OPTIONAL, + qualityOfService [4] QualityOfService OPTIONAL, + timeAndTimeZone [5] TimeAndTimezone {bound} OPTIONAL, + ..., + gGSNAddress [6] GSN-Address OPTIONAL + }, + + detachSpecificInformation [2] SEQUENCE { + initiatingEntity [0] InitiatingEntity OPTIONAL, + ..., + routeingAreaUpdate [1] NULL OPTIONAL + }, + + disconnectSpecificInformation [3] SEQUENCE { + initiatingEntity [0] InitiatingEntity OPTIONAL, + ..., + routeingAreaUpdate [1] NULL OPTIONAL + }, + + pDPContextEstablishmentSpecificInformation + [4] SEQUENCE { + accessPointName [0] AccessPointName {bound} OPTIONAL, + endUserAddress [1] EndUserAddress {bound} OPTIONAL, + qualityOfService [2] QualityOfService OPTIONAL, + locationInformationGPRS [3] LocationInformationGPRS OPTIONAL, + timeAndTimeZone [4] TimeAndTimezone {bound} OPTIONAL, + pDPInitiationType [5] PDPInitiationType OPTIONAL, + ..., + secondaryPDP-context [6] NULL OPTIONAL + }, + + pDPContextEstablishmentAcknowledgementSpecificInformation + [5] SEQUENCE { + +``` + +``` + + accessPointName [0] AccessPointName {bound} OPTIONAL, + chargingID [1] GPRSChargingID OPTIONAL, + endUserAddress [2] EndUserAddress {bound} OPTIONAL, + qualityOfService [3] QualityOfService OPTIONAL, + locationInformationGPRS [4] LocationInformationGPRS OPTIONAL, + timeAndTimeZone [5] TimeAndTimeZone {bound} OPTIONAL, + ..., + gGSNAddress [6] GSN-Address OPTIONAL + } +} + +``` + +``` + +GPRSEventType ::= ENUMERATED { + attach (1), + attachChangeOfPosition (2), + detached (3), + pdp-ContextEstablishment (11), + pdp-ContextEstablishmentAcknowledgement (12), + disconnect (13), + pdp-ContextChangeOfPosition (14) +} + +``` + +``` + +InbandInfo {PARAMETERS-BOUND : bound} ::= SEQUENCE { + messageID [0] MessageID {bound}, + numberOfRepetitions [1] INTEGER (1..127) OPTIONAL, + duration [2] INTEGER (0..32767) OPTIONAL, + interval [3] INTEGER (0..32767) OPTIONAL, + ... +} + +``` + +- Interval is the time in seconds between each repeated announcement. Duration is the total +- amount of time in seconds, including repetitions and intervals. +- The end of announcement is either the end of duration or numberOfRepetitions, +- whatever comes first. +- duration with value 0 indicates infinite duration + +``` + +InformationToSend {PARAMETERS-BOUND : bound} ::= CHOICE { + inbandInfo [0] InbandInfo {bound}, + tone [1] Tone +} + +``` + +``` + +InitiatingEntity ::= ENUMERATED { + mobileStation (0), + sgsn (1), + hlr (2), + ggsn (3) +} + +``` + +``` + +InitiatorOfServiceChange ::= ENUMERATED { + a-side (0), + b-side (1) +} + +``` + +``` + +InvokeID ::= INTEGER (-128..127) + +``` + +``` + +IPRoutingAddress {PARAMETERS-BOUND : bound} ::= CalledPartyNumber {bound} +-- Indicates the routing address for the IP. + +``` + +``` + +IPSSPCapabilities {PARAMETERS-BOUND : bound} ::= OCTET STRING (SIZE( + bound.&minIPSSPCapabilitiesLength .. bound.&maxIPSSPCapabilitiesLength)) +-- Indicates the gsmSRF resources available. The parameter has two parts, a standard and a +-- bilateral part. The standard part indicates capabilities defined as optional in CAP +-- that shall be recognised (but not necessarily supported) by a gsmSCF. The bilateral +-- part contains further information that is not specified in this standard, but which is set +-- according to bilateral agreements between network operators and/or equipment vendors. +-- The last octet of the standard part is indicated by bit 7 being set to 0, otherwise Bit 7 of +-- a standard part octet is set to 1 indicating that the standard part continues in the following + +``` + +– octet. Coding is as follows: + +| | | | +|-----------------|-------|------------------------------------------------------------| +| – Octet 1 | | Standard Part for CAP | +| – Bit | Value | Meaning | +| – 0 | 0 | IPRoutingAddress not supported | +| – | 1 | IPRoutingAddress supported | +| – 1 | 0 | VoiceBack not supported | +| – | 1 | VoiceBack supported | +| – 2 | 0 | VoiceInformation not supported, via speech recognition | +| – | 1 | VoiceInformation supported, via speech recognition | +| – 3 | 0 | VoiceInformation not supported, via voice recognition | +| – | 1 | VoiceInformation supported, via voice recognition | +| – 4 | 0 | Generation of voice announcements from Text not supported | +| – | 1 | Generation of voice announcements from Text supported | +| – 5 | - | Reserved | +| – 6 | - | Reserved | +| – 7 | 0 | End of standard part | +| – | 1 | This value is reserved in CAP | +| – | | | +| – Octets 2 to 4 | | Bilateral Part: Network operator/equipment vendor specific | + +``` +LegOrCallSegment {PARAMETERS-BOUND : bound} ::= CHOICE { + callSegmentID [0] CallSegmentID {bound}, + legID [1] LegID +} +``` + +LegType ::= OCTET STRING (SIZE(1)) + +leg1 LegType ::= '01'H + +leg2 LegType ::= '02'H + +``` +LocationInformationGPRS ::= SEQUENCE { + cellGlobalIdOrServiceAreaIdOrLAI [0] OCTET STRING (SIZE(5..7)) OPTIONAL, + routeingAreaIdentity [1] RAIdentity OPTIONAL, + geographicalInformation [2] GeographicalInformation OPTIONAL, + sgsn-Number [3] ISDN-AddressString OPTIONAL, + selectedLSAIdentity [4] LSAIdentity OPTIONAL, + extensionContainer [5] ExtensionContainer OPTIONAL, + ..., + sai-Present [6] NULL OPTIONAL, + userCSGInformation [7] UserCSGInformation OPTIONAL +} +``` + +– cellGlobalIdOrServiceAreaIdOrLAI shall contain the value part of the + +– CellGlobalIdOrServiceAreaIdFixedLength type or the LAIFixedLength type (i.e. excluding tags + +– and lengths) as defined in 3GPP TS 29.002 [13]. + +– sai-Present indicates that the cellGlobalIdOrServiceAreaIdOrLAI parameter contains + +– a Service Area Identity. + +– UserCSGInformation contains the CSG ID, Access mode, and the CSG Membership Indication in the + +-- case the Access mode is Hybrid Mode, as defined in 3GPP TS 23.060 [93]. + +``` +LocationNumber {PARAMETERS-BOUND : bound} ::= OCTET STRING (SIZE ( + bound.&minLocationNumberLength .. bound.&maxLocationNumberLength)) +``` + +– Indicates the Location Number for the calling party. + +– Refer to ETSI EN 300 356-1 [23] for encoding. + +``` +LowLayerCompatibility {PARAMETERS-BOUND : bound} ::= OCTET STRING (SIZE ( + bound.&minLowLayerCompatibilityLength .. bound.&maxLowLayerCompatibilityLength)) +``` + +– indicates the LowLayerCompatibility for the calling party. + +– Refer to 3GPP TS 24.008 [9] for encoding. + +– It shall be coded as in the value part defined in 3GPP TS 24.008. + +-- i.e. the 3GPP TS 24.008 IEI and 3GPP TS 24.008 octet length indicator + +-- shall not be included. + +``` +MessageID {PARAMETERS-BOUND : bound} ::= CHOICE { + elementaryMessageID [0] Integer4, + text [1] SEQUENCE { + messageContent [0] IA5String (SIZE( + bound.&minMessageContentLength .. bound.&maxMessageContentLength)), +``` + +``` + + attributes [1] OCTET STRING (SIZE( + bound.&minAttributesLength .. bound.&maxAttributesLength)) OPTIONAL + }, + elementaryMessageIDs [29] SEQUENCE SIZE (1.. bound.&numOfMessageIDs) OF Integer4, + variableMessage [30] SEQUENCE { + elementaryMessageID [0] Integer4, + variableParts [1] SEQUENCE SIZE (1..5) OF VariablePart {bound} + } +} + +``` + +– Use of the text parameter is network operator/equipment vendor specific. + +MetDPCriteriaList {PARAMETERS-BOUND : bound} ::= SEQUENCE SIZE (1..bound.&numOfChangeOfPositionControlInfo) OF MetDPCriterion {bound} + +``` + +MetDPCriterion {PARAMETERS-BOUND : bound} ::= CHOICE { + enteringCellGlobalId [0] CellGlobalIdOrServiceAreaIdFixedLength, + leavingCellGlobalId [1] CellGlobalIdOrServiceAreaIdFixedLength, + enteringServiceAreaId [2] CellGlobalIdOrServiceAreaIdFixedLength, + leavingServiceAreaId [3] CellGlobalIdOrServiceAreaIdFixedLength, + enteringLocationAreaId [4] LAIFixedLength, + leavingLocationAreaId [5] LAIFixedLength, + inter-SystemHandOverToUMTS [6] NULL, + inter-SystemHandOverToGSM [7] NULL, + inter-PLMNHandOver [8] NULL, + inter-MSCHandOver [9] NULL, + metDPCriterionAlt [10] MetDPCriterionAlt {bound} +} + +``` + +– The enteringCellGlobalId and leavingCellGlobalId shall contain a Cell Global Identification. + +– The enteringServiceAreaId and leavingServiceAreaId shall contain a Service Area Identification. + +MetDPCriterionAlt {PARAMETERS-BOUND : bound} ::= SEQUENCE { + +``` + + ... +} + +``` + +``` + +MidCallControlInfo ::= SEQUENCE { + minimumNumberOfDigits [0] INTEGER (1..30) DEFAULT 1, + maximumNumberOfDigits [1] INTEGER (1..30) DEFAULT 30, + endOfReplyDigit [2] OCTET STRING (SIZE (1..2)) OPTIONAL, + cancelDigit [3] OCTET STRING (SIZE (1..2)) OPTIONAL, + startDigit [4] OCTET STRING (SIZE (1..2)) OPTIONAL, + interDigitTimeout [6] INTEGER (1..127) DEFAULT 10, + ... +} + +``` + +-- + +-- minimumNumberOfDigits specifies the minimum number of digits that shall be collected + +-- maximumNumberOfDigits specifies the maximum number of digits that shall be collected + +-- endOfReplyDigit specifies the digit string that denotes the end of the digits to be collected. + +-- cancelDigit specifies the digit string that indicates that the input shall be erased and digit collection shall start afresh. + +-- startDigit specifies the digit string that denotes the start of the digits to be collected. + +-- interDigitTimeout specifies the maximum duration in seconds between successive digits. + +-- + +-- endOfReplyDigit, cancelDigit and startDigit shall contain digits in the range 0..9, '\*' and '#' only. The collected digits string, reported to the gsmSCF, shall include the endOfReplyDigit and the startDigit, if present. + +-- + +-- endOfReplyDigit, cancelDigit and startDigit shall be encoded as BCD digits. Each octet shall contain one BCD digit, in the 4 least significant bits of each octet. + +-- The following encoding shall be used for the over-decadic digits: 1011 (\*), 1100 (#). + +``` + +MonitorMode ::= ENUMERATED { + interrupted (0), + notifyAndContinue (1), + transparent (2) +} + +``` + +– Indicates the event is relayed and/or processed by the SSP. + +– Transparent means that the gsmSSF or gprsSSF does not notify the gsmSCF of the event. + +-- For the use of this parameter refer to the procedure descriptions in clause 11. + +-- For the RequestNotificationCharging operation, 'interrupted' shall not be used in MonitorMode. + +MO-SMSCause ::= ENUMERATED { + +| | | +|---------------------------|------| +| systemFailure | (0), | +| unexpectedDataValue | (1), | +| facilityNotSupported | (2), | +| sM-DeliveryFailure | (3), | +| releaseFromRadioInterface | (4) | + +} + +-- MO SMS error values which are reported to gsmSCF. + +-- Most of these values are received from the SMSC as a response to + +-- MO-ForwardSM operation. + +MT-SMSCause ::= OCTET STRING (SIZE (1)) + +-- This variable is sent to the gsmSCF for a Short Message delivery failure + +-- notification. + +-- If the delivery failure is due to RP-ERROR RPDU received from the MS, + +-- then MT-SMSCause shall be set to the RP-Cause component in the RP-ERROR RPDU. + +-- Refer to 3GPP TS 24.011 [10] for the encoding of RP-Cause values. + +-- Otherwise, if the delivery failure is due to internal failure in the MSC or SGSN + +-- or time-out from the MS, then MT-SMSCause shall be set to 'Protocol error, + +-- unspecified', as defined in 3GPP TS 24.011 [10]. + +NAOliInfo ::= OCTET STRING (SIZE (1)) + +-- NA Oli information takes the same value as defined in ANSI T1.113-1995 [92] + +-- e.g. '3D'H - Decimal value 61 - Cellular Service (Type 1) + +-- '3E'H - Decimal value 62 - Cellular Service (Type 2) + +-- '3F'H - Decimal value 63 - Cellular Service (roaming) + +NatureOfServiceChange ::= ENUMERATED { + +| | | +|------------------|------| +| userInitiated | (0), | +| networkInitiated | (1) | + +} + +NumberOfDigits ::= INTEGER (1..255) + +-- Indicates the number of digits to be collected. + +OCSIApplicable ::= NULL + +-- Indicates that the Originating CAMEL Subscription Information, if present, shall be + +-- applied on the outgoing call leg created with a Connect operation. For the use of this + +-- parameter see 3GPP TS 23.078 [7]. + +OriginalCalledPartyID {PARAMETERS-BOUND : bound} ::= OCTET STRING (SIZE( + +bound.&minOriginalCalledPartyIDLength .. bound.&maxOriginalCalledPartyIDLength)) + +-- Indicates the original called number. Refer to ETSI EN 300 356-1 [23] Original Called Number + +-- for encoding. + +PDPID ::= OCTET STRING (SIZE (1)) + +-- PDP Identifier is a counter used to identify a specific PDP Context within a control + +-- relationship between gprsSSF and gsmSCF. + +PDPInitiationType ::= ENUMERATED { + +| | | +|------------------|------| +| mSInitiated | (0), | +| networkInitiated | (1) | + +} + +QualityOfService ::= SEQUENCE { + +| | | | | +|--------------------------|-----|--------------------|-----------| +| requested-QoS | [0] | GPRS-QoS | OPTIONAL, | +| subscribed-QoS | [1] | GPRS-QoS | OPTIONAL, | +| negotiated-QoS | [2] | GPRS-QoS | OPTIONAL, | +| .... | | | | +| requested-QoS-Extension | [3] | GPRS-QoS-Extension | OPTIONAL, | +| subscribed-QoS-Extension | [4] | GPRS-QoS-Extension | OPTIONAL, | +| negotiated-QoS-Extension | [5] | GPRS-QoS-Extension | OPTIONAL | + +} + +ReceivingSideID ::= CHOICE { + +| | | | +|-----------------|-----|---------| +| receivingSideID | [1] | LegType | +|-----------------|-----|---------| + +} + +– used to identify LegID in operations sent from gsmSSF to gsmSCF + +RedirectingPartyID {PARAMETERS-BOUND : bound} ::= OCTET STRING (SIZE ( + bound.&minRedirectingPartyIDLength .. bound.&maxRedirectingPartyIDLength)) + +– Indicates redirecting number. + +– Refer to ETSI EN 300 356-1 [23] Redirecting number for encoding. + +RequestedInformationList {PARAMETERS-BOUND : bound} ::= SEQUENCE SIZE (1.. numOfInfoItems) OF RequestedInformation {bound} + +RequestedInformationTypeList ::= SEQUENCE SIZE (1.. numOfInfoItems) OF RequestedInformationType + +RequestedInformation {PARAMETERS-BOUND : bound} ::= SEQUENCE { + requestedInformationType [0] RequestedInformationType, + requestedInformationValue [1] RequestedInformationValue {bound}, + ... + } + +RequestedInformationType ::= ENUMERATED { + callAttemptElapsedTime (0), + callStopTime (1), + callConnectedElapsedTime (2), + releaseCause (30) + } + +RequestedInformationValue {PARAMETERS-BOUND : bound} ::= CHOICE { + callAttemptElapsedTimeValue [0] INTEGER (0..255), + callStopTimeValue [1] DateAndTime, + callConnectedElapsedTimeValue [2] Integer4, + releaseCauseValue [30] Cause {bound} + } + +– The callAttemptElapsedTimeValue is specified in seconds. The unit for the + +– callConnectedElapsedTimeValue is 100 milliseconds + +RPCause ::= OCTET STRING (SIZE (1)) + +– RP cause according to 3GPP TS 24.011 [10] or 3GPP TS 29.002 [11]. + +– GsmSCF shall send this cause in the ReleaseSMS operation. + +-- For a MO-SMS service, the MSC or SGSN shall send the RP Cause to the originating MS. + +-- It shall be used to overwrite the RP-Cause element in the RP-ERROR RPDU. + +-- For a MT-SMS service, the MSC or SGSN shall send the RP Cause to the sending SMS-GMSC. + +-- It shall be used to overwrite the RP-Cause element in the RP-ERROR RPDU. + +ScfID {PARAMETERS-BOUND : bound} ::= OCTET STRING (SIZE( + bound.&minScfIDLength .. bound.&maxScfIDLength)) + +– format and length of ScfID is defined by the network operator. + +– Indicates the gsmSCF identity. + +SCIBillingChargingCharacteristics {PARAMETERS-BOUND : bound} ::= OCTET STRING (SIZE ( + bound.&minSCIBillingChargingLength .. bound.&maxSCIBillingChargingLength)) + (CONSTRAINED BY {– shall be the result of the BER-encoded value of type – + CAMEL-SCIBillingChargingCharacteristics}) + +– Indicates AOC information to be sent to a Mobile Station + +– The violation of the UserDefinedConstraint shall be handled as an ASN.1 syntax error. + +SCIGPRSBillingChargingCharacteristics {PARAMETERS-BOUND : bound} ::= OCTET STRING (SIZE ( + bound.&minSCIBillingChargingLength .. bound.&maxSCIBillingChargingLength)) + (CONSTRAINED BY {– shall be the result of the BER-encoded value of type – + CAMEL-SCIGPRSBillingChargingCharacteristics}) + +– Indicates AOC information to be sent to a Mobile Station + +– The violation of the UserDefinedConstraint shall be handled as an ASN.1 syntax error. + +SendingSideID ::= CHOICE {sendingSideID [0] LegType} + +– used to identify LegID in operations sent from gsmSCF to gsmSSF + +ServiceInteractionIndicatorsTwo ::= SEQUENCE { + +``` + +forwardServiceInteractionInd [0] ForwardServiceInteractionInd OPTIONAL, +-- applicable to operations InitialDP, Connect and ContinueWithArgument. +backwardServiceInteractionInd [1] BackwardServiceInteractionInd OPTIONAL, +-- applicable to operations Connect and ContinueWithArgument. +bothwayThroughConnectionInd [2] BothwayThroughConnectionInd OPTIONAL, +-- applicable to ConnectToResource and EstablishTemporaryConnection +connectedNumberTreatmentInd [4] ConnectedNumberTreatmentInd OPTIONAL, +-- applicable to Connect and ContinueWithArgument +nonCUGCall [13] NULL OPTIONAL, +-- applicable to Connect and ContinueWithArgument +-- indicates that no parameters for CUG shall be used for the call (i.e. the call shall +-- be a non-CUG call). +-- If not present, it indicates one of three things: +-- a) continue with modified CUG information (when one or more of either CUG Interlock Code +-- and Outgoing Access Indicator are present), or +-- b) continue with original CUG information (when neither CUG Interlock Code or Outgoing +-- Access Indicator are present), i.e. no IN impact. +-- c) continue with the original non-CUG call. +holdTreatmentIndicator [50] OCTET STRING (SIZE(1)) OPTIONAL, +-- applicable to InitialDP, Connect and ContinueWithArgument +-- acceptHoldRequest 'xxxx xx01'B +-- rejectHoldRequest 'xxxx xx10'B +-- if absent from Connect or ContinueWithArgument, +-- then CAMEL service does not affect call hold treatment +cwTreatmentIndicator [51] OCTET STRING (SIZE(1)) OPTIONAL, +-- applicable to InitialDP, Connect and ContinueWithArgument +-- acceptCw 'xxxx xx01'B +-- rejectCw 'xxxx xx10'B +-- if absent from Connect or ContinueWithArgument, +-- then CAMEL service does not affect call waiting treatment +ectTreatmentIndicator [52] OCTET STRING (SIZE(1)) OPTIONAL, +-- applicable to InitialDP, Connect and ContinueWithArgument +-- acceptEctRequest 'xxxx xx01'B +-- rejectEctRequest 'xxxx xx10'B +-- if absent from Connect or ContinueWithArgument, +-- then CAMEL service does not affect explicit call transfer treatment +... +} + +``` + +SGSNCapabilities ::= OCTET STRING (SIZE (1)) + +-- Indicates the SGSN capabilities. The coding of the parameter is as follows: + +| Bit | Value | Meaning | +|-----|-------|---------------------------------| +| 0 | 0 | AoC not supported by SGSN | +| | 1 | AoC supported by SGSN | +| 1 | - | This bit is reserved in CAP V.3 | +| 2 | - | This bit is reserved in CAP V.3 | +| 3 | - | This bit is reserved in CAP V.3 | +| 4 | - | This bit is reserved in CAP V.3 | +| 5 | - | This bit is reserved in CAP V.3 | +| 6 | - | This bit is reserved in CAP V.3 | +| 7 | - | This bit is reserved in CAP V.3 | + +SMS-AddressString ::= AddressString (SIZE (1 .. maxSMS-AddressStringLength)) + +-- This data type is used to transport CallingPartyNumber for MT-SMS. + +-- If this data type is used for MO-SMS, then the maximum number of digits shall be 16. + +-- An SMS-AddressString may contain an alphanumeric character string. In this + +-- case, a nature of address indicator '101'B is used, in accordance with + +-- 3GPP TS 23.040 [6]. The address is coded in accordance with the GSM 7-bit + +-- default alphabet definition and the SMS packing rules as specified in + +-- 3GPP TS 23.038 [15] in this case. + +maxSMS-AddressStringLength INTEGER ::= 11 + +``` + +SMSEvent ::= SEQUENCE { + eventTypeSMS [0] EventTypeSMS, + +``` + +``` + + monitorMode [1] MonitorMode + } + +``` + +``` + +TariffSwitchInterval ::= INTEGER (1 .. 86400) +-- TariffSwitchInterval is measured in 1 second units + +``` + +``` + +TimeAndTimezone {PARAMETERS-BOUND : bound} ::= OCTET STRING (SIZE( + bound.&minTimeAndTimezoneLength .. bound.&maxTimeAndTimezoneLength)) +-- Indicates the time and timezone, relative to GMT. This parameter is BCD encoded. +-- The year digit indicating millenium occupies bits 0-3 of the first octet, and the year +-- digit indicating century occupies bits 4-7 of the first octet. +-- The year digit indicating decade occupies bits 0-3 of the second octet, whilst the digit +-- indicating the year within the decade occupies bits 4-7 of the second octet. +-- The most significant month digit occupies bits 0-3 of the third octet, and the least +-- significant month digit occupies bits 4-7 of the third octet. +-- The most significant day digit occupies bits 0-3 of the fourth octet, and the least +-- significant day digit occupies bits 4-7 of the fourth octet. +-- The most significant hours digit occupies bits 0-3 of the fifth octet, and the least +-- significant hours digit occupies bits 4-7 of the fifth octet. +-- The most significant minutes digit occupies bits 0-3 of the sixth octet, and the least +-- significant minutes digit occupies bits 4-7 of the sixth octet. +-- The most significant seconds digit occupies bits 0-3 of the seventh octet, and the least +-- significant seconds digit occupies bits 4-7 of the seventh octet. +-- +-- The timezone information occupies the eighth octet. For the encoding of Timezone refer to +-- 3GPP TS 23.040 [6]. +-- +-- The BCD digits are packed and encoded as follows: +-- +-- Bit 7 6 5 4 | 3 2 1 0 +-- 2nd digit | 1st digit Octet 1 +-- 3rd digit | 4th digit Octet 2 +-- .. | .. .. +-- nth digit | n-1th digit Octet m +-- +-- 0000 digit 0 +-- 0001 digit 1 +-- 0010 digit 2 +-- 0011 digit 3 +-- 0100 digit 4 +-- 0101 digit 5 +-- 0110 digit 6 +-- 0111 digit 7 +-- 1000 digit 8 +-- 1001 digit 9 +-- 1010 spare +-- 1011 spare +-- 1100 spare +-- 1101 spare +-- 1110 spare +-- 1111 spare +-- +-- where the leftmost bit of the digit is either bit 7 or bit 3 of the octet. + +``` + +``` + +TimeIfNoTariffSwitch ::= INTEGER(0..864000) +-- TimeIfNoTariffSwitch is measured in 100 millisecond intervals + +``` + +``` + +TimeIfTariffSwitch ::= SEQUENCE { + timeSinceTariffSwitch [0] INTEGER(0..864000), + tariffSwitchInterval [1] INTEGER(1..864000) OPTIONAL +} +-- timeSinceTariffSwitch and tariffSwitchInterval are measured in 100 millisecond intervals + +``` + +``` + +TimeInformation ::= CHOICE { + timeIfNoTariffSwitch [0] TimeIfNoTariffSwitch, + +``` + +timeIfTariffSwitch [1] TimeIfTariffSwitch + +} + +– Indicates call duration information + +TimerID ::= ENUMERATED { + +tssf (0) + +} + +– Indicates the timer to be reset. + +TimerValue ::= Integer4 + +– Indicates the timer value (in seconds). + +Tone ::= SEQUENCE { + +toneID [0] Integer4, + +duration [1] Integer4 OPTIONAL, + +... + +} + +– The duration specifies the length of the tone in seconds, value 0 indicates infinite duration. + +TPDataCodingScheme ::= OCTET STRING (SIZE (1)) + +– TP Data Coding Scheme according to 3GPP TS 23.040 [6] + +TPProtocolIdentifier ::= OCTET STRING (SIZE (1)) + +– indicates the protocol used above the SM-Transfer Layer as specified in 3GPP TS 23.040 [6]. + +TPShortMessageSpecificInfo ::= OCTET STRING (SIZE (1)) + +– contains the 1st octet of the applicable TPDU or the SMS-COMMAND TPDU as specified in + +– 3GPP TS 23.040 [6]. + +TPValidityPeriod ::= OCTET STRING (SIZE (1..7)) + +– indicates the length of the validity period or the absolute time of the validity + +– period termination as specified in 3GPP TS 23.040 [6]. + +– the length of ValidityPeriod is either 1 octet or 7 octets + +TransferredVolume ::= CHOICE { + +volumeIfNoTariffSwitch [0] INTEGER (0..4294967295), + +volumeIfTariffSwitch [1] SEQUENCE { + +volumeSinceLastTariffSwitch [0] INTEGER (0..4294967295), + +volumeTariffSwitchInterval [1] INTEGER (0..4294967295) OPTIONAL + +} + +} + +– volumeIfNoTariffSwitch, volumeSinceLastTariffSwitch and volumeTariffSwitchInterval + +– are measured in bytes. + +TransferredVolumeRollOver ::= CHOICE { + +rO-VolumeIfNoTariffSwitch [0] INTEGER (0..255), + +rO-VolumeIfTariffSwitch [1] SEQUENCE { + +rO-VolumeSinceLastTariffSwitch [0] INTEGER (0..255) OPTIONAL, + +rO-VolumeTariffSwitchInterval [1] INTEGER (0..255) OPTIONAL + +} + +} + +– rO-VolumeIfNoTariffSwitch, rO-VolumeSinceLastTariffSwitch and rO-VolumeTariffSwitchInterval + +– present counters indicating the number of parameter range rollovers. + +UnavailableNetworkResource ::= ENUMERATED { + +unavailableResources (0), + +componentFailure (1), + +basicCallProcessingException (2), + +resourceStatusFailure (3), + +endUserFailure (4) + +} + +– Indicates the network resource that failed. + +VariablePart {PARAMETERS-BOUND : bound} ::= CHOICE { + +integer [0] Integer4, + +``` + +number [1] Digits {bound}, -- Generic digits +time [2] OCTET STRING (SIZE(2)), -- HH: MM, BCD coded +date [3] OCTET STRING (SIZE(4)), -- YYYYMMDD, BCD coded +price [4] OCTET STRING (SIZE(4)) +} +-- Indicates the variable part of the message. Time is BCD encoded. +-- The most significant hours digit occupies bits 0-3 of the first octet, and the least +-- significant digit occupies bits 4-7 of the first octet. The most significant minutes digit +-- occupies bits 0-3 of the second octet, and the least significant digit occupies bits 4-7 +-- of the second octet. +-- +-- Date is BCD encoded. The year digit indicating millenium occupies bits 0-3 of the first octet, +-- and the year digit indicating century occupies bits 4-7 of the first octet. The year digit +-- indicating decade occupies bits 0-3 of the second octet, whilst the digit indicating the year +-- within the decade occupies bits 4-7 of the second octet. +-- The most significant month digit occupies bits 0-3 of the third octet, and the least +-- significant month digit occupies bits 4-7 of the third octet. The most significant day digit +-- occupies bits 0-3 of the fourth octet, and the least significant day digit occupies bits 4-7 +-- of the fourth octet. +-- Price is BCD encoded. The digit indicating hundreds of thousands occupies bits 0-3 of the +-- first octet, and the digit indicating tens of thousands occupies bits 4-7 of the first octet. +-- The digit indicating thousands occupies bits 0-3 of the second octet, whilst the digit +-- indicating hundreds occupies bits 4-7 of the second octet. The digit indicating tens occupies +-- bits 0-3 of the third octet, and the digit indicating 0 to 9 occupies bits 4-7 of the third +-- octet. The tenths digit occupies bits 0-3 of the fourth octet, and the hundredths digit +-- occupies bits 4-7 of the fourth octet. +-- +-- For the encoding of digits in an octet, refer to the timeAndtimezone parameter + +-- The Defintion of range of constants follows +numOfInfoItems INTEGER ::= 4 + +``` + +END + +## 5.2 Error types + +``` + +CAP-errorTypes { itu-t(0) identified-organization(4) etsi(0) mobileDomain(0) umts-network(1) +modules(3) cap-errorTypes(51) version8(7) } + +-- This module contains the type definitions for the CAP Error Types. +-- Where a parameter of type CHOICE is tagged with a specific tag value, the tag is automatically +-- replaced with an EXPLICIT tag of the same value. + +DEFINITIONS IMPLICIT TAGS ::= BEGIN + +IMPORTS + + ros-InformationObjects, + datatypes, + errorcodes + +FROM CAP-object-identifiers { itu-t(0) identified-organization(4) etsi(0) mobileDomain(0) +umts-network(1) modules(3) cap-object-identifiers(100) version8(7) } + + ERROR + +FROM Remote-Operations-Information-Objects ros-InformationObjects + + InvokeID, + UnavailableNetworkResource + +FROM CAP-datatypes datatypes + + errcode-canceled, + errcode-cancelFailed, + errcode-eTCFailed, + errcode-improperCallerResponse, + errcode-missingCustomerRecord, + errcode-missingParameter, + errcode-parameterOutOfRange, + errcode-requestedInfoError, + errcode-systemFailure, + +``` + +``` + + errcode-taskRefused, + errcode-unavailableResource, + errcode-unexpectedComponentSequence, + errcode-unexpectedDataValue, + errcode-unexpectedParameter, + errcode-unknownLegID, + errcode-unknownCSID, + errcode-unknownPDPID +FROM CAP-errorcodes errorcodes + +; + +-- TYPE DEFINITION FOR CAP ERROR TYPES FOLLOWS + +canceled ERROR ::= { + CODE errcode-canceled +} +-- The operation has been canceled. + +cancelFailed ERROR ::= { + PARAMETER SEQUENCE { + problem [0] ENUMERATED { + unknownOperation (0), + tooLate (1), + operationNotCancellable (2) + }, + operation [1] InvokeID, + ... + } + CODE errcode-cancelFailed +} +-- The operation failed to be canceled. + +eTCFailed ERROR ::= { + CODE errcode-eTCFailed +} +-- The establish temporary connection failed. + +improperCallerResponse ERROR ::= { + CODE errcode-improperCallerResponse +} +-- The caller response was not as expected. + +missingCustomerRecord ERROR ::= { + CODE errcode-missingCustomerRecord +} +-- The Service Logic Program could not be found in the gsmSCF. + +missingParameter ERROR ::= { + CODE errcode-missingParameter +} +-- An expected optional parameter was not received. + +parameterOutOfRange ERROR ::= { + CODE errcode-parameterOutOfRange +} +-- The parameter was not as expected (e.g. missing or out of range). + +requestedInfoError ERROR ::= { + PARAMETER ENUMERATED { + unknownRequestedInfo (1), + requestedInfoNotAvailable (2) + } + CODE errcode-requestedInfoError +} +-- The requested information cannot be found. + +systemFailure ERROR ::= { + PARAMETER UnavailableNetworkResource + CODE errcode-systemFailure +} +-- The operation could not be completed due to a system failure at the serving physical entity. + +taskRefused ERROR ::= { + PARAMETER ENUMERATED { + generic (0), + unobtainable (1), + congestion (2) + } +} + +``` + +``` + + } + CODE errcode-taskRefused + } +-- An entity normally capable of the task requested cannot or chooses not to perform the task at +-- this time. This includes error situations like congestion and unobtainable address as used in +-- e.g. the connect operation.) + +unavailableResource ERROR ::= { + CODE errcode-unavailableResource +} +-- A requested resource is not available at the serving entity. + +unexpectedComponentSequence ERROR ::= { + CODE errcode-unexpectedComponentSequence +} +-- An incorrect sequence of Components was received (e.g. 'DisconnectForwardConnection' +-- followed by 'PlayAnnouncement'). + +unexpectedDataValue ERROR ::= { + CODE errcode-unexpectedDataValue +} +-- The data value was not as expected (e.g. route number expected but billing number received) + +unexpectedParameter ERROR ::= { + CODE errcode-unexpectedParameter +} +-- A parameter received was not expected. + +unknownLegID ERROR ::= { + CODE errcode-unknownLegID +} +-- Leg not known to the gsmSSF. + +unknownCSID ERROR ::= { + CODE errcode-unknownCSID +} +-- Call Segment not known to the gsmSSF. + +unknownPDPID ERROR ::= { + CODE errcode-unknownPDPID +} +-- PDPID not known by the receiving entity. + +END + +``` + +## 5.3 Operation codes + +CAP-operationcodes { itu-t(0) identified-organization(4) etsi(0) mobileDomain(0) umts-network(1) modules(3) cap-operationcodes(53) version8(7) } + +DEFINITIONS ::= BEGIN + +IMPORTS + +ros-InformationObjects + FROM CAP-object-identifiers { itu-t(0) identified-organization(4) etsi(0) mobileDomain(0) umts-network(1) modules(3) cap-object-identifiers(100) version8(7) } + +Code + FROM Remote-Operations-Information-Objects ros-InformationObjects + +; + +-- the operations are grouped by the identified operation packages. + +``` + +-- gsmSCF activation Package + opcode-initialDP Code ::= local: 0 +-- gsmSCF/gsmSRF activation of assist Package + opcode-assistRequestInstructions Code ::= local: 16 +-- Assist connection establishment Package + opcode-establishTemporaryConnection Code ::= local: 17 +-- Generic disconnect resource Package + opcode-disconnectForwardConnection Code ::= local: 18 + opcode-dFCWithArgument Code ::= local: 86 +-- Non-assisted connection establishment Package + +``` + +``` + + opcode-connectToResource Code ::= local: 19 +-- Connect Package (elementary gsmSSF function) + opcode-connect Code ::= local: 20 +-- Call handling Package (elementary gsmSSF function) + opcode-releaseCall Code ::= local: 22 +-- BCSM Event handling Package + opcode-requestReportBCSMEVENT Code ::= local: 23 + opcode-eventReportBCSM Code ::= local: 24 +-- gsmSSF call processing Package + opcode-collectInformation Code ::= local: 27 + opcode-continue Code ::= local: 31 +-- gsmSCF call initiation Package + opcode-initiateCallAttempt Code ::= local: 32 +-- Timer Package + opcode-resetTimer Code ::= local: 33 +-- Billing Package + opcode-furnishChargingInformation Code ::= local: 34 +-- Charging Package + opcode-applyCharging Code ::= local: 35 + opcode-applyChargingReport Code ::= local: 36 +-- Traffic management Package + opcode-callGap Code ::= local: 41 +-- Call report Package + opcode-callInformationReport Code ::= local: 44 + opcode-callInformationRequest Code ::= local: 45 +-- Signalling control Package + opcode-sendChargingInformation Code ::= local: 46 +-- Specialized resource control Package + opcode-playAnnouncement Code ::= local: 47 + opcode-promptAndCollectUserInfo Code ::= local: 48 + opcode-specializedResourceReport Code ::= local: 49 +-- Cancel Package + opcode-cancel Code ::= local: 53 +-- Activity Test Package + opcode-activityTest Code ::= local: 55 +-- CPH Response Package + opcode-continueWithArgument Code ::= local: 88 + opcode-disconnectLeg Code ::= local: 90 + opcode-moveLeg Code ::= local: 93 + opcode-splitLeg Code ::= local: 95 +-- Exception Inform Package + opcode-entityReleased Code ::= local: 96 +-- Play Tone Package + opcode-playTone Code ::= local: 97 + +-- Sms Activation Package + opcode-initialDPSMS Code ::= local: 60 +-- Sms Billing Package + opcode-furnishChargingInformationSMS Code ::= local: 61 +-- Sms Connect Package + opcode-connectSMS Code ::= local: 62 +-- Sms Event Handling Package + opcode-requestReportSMSEVENT Code ::= local: 63 + opcode-eventReportSMS Code ::= local: 64 +-- Sms Processing Package + opcode-continueSMS Code ::= local: 65 +-- Sms Release Package + opcode-releaseSMS Code ::= local: 66 +-- Sms Timer Package + opcode-resetTimerSMS Code ::= local: 67 + +-- Gprs Activity Test Package + opcode-activityTestGPRS Code ::= local: 70 +-- Gprs Charging Package + opcode-applyChargingGPRS Code ::= local: 71 + opcode-applyChargingReportGPRS Code ::= local: 72 +-- Gprs Cancel Package + opcode-cancelGPRS Code ::= local: 73 +-- Gprs Connect Package + opcode-connectGPRS Code ::= local: 74 +-- Gprs Processing Package + opcode-continueGPRS Code ::= local: 75 +-- Gprs Exception Information Package + opcode-entityReleasedGPRS Code ::= local: 76 +-- Gprs Billing Package + opcode-furnishChargingInformationGPRS Code ::= local: 77 +-- Gprs Scf Activation Package + opcode-initialDPGPRS Code ::= local: 78 + +``` + +``` + +-- Gprs Release Package + opcode-releaseGPRS Code ::= local: 79 +-- Gprs Event Handling Package + opcode-eventReportGPRS Code ::= local: 80 + opcode-requestReportGPRSEvent Code ::= local: 81 +-- Gprs Timer Package + opcode-resetTimerGPRS Code ::= local: 82 +-- Gprs Charge Advice Package + opcode-sendChargingInformationGPRS Code ::= local: 83 + +END + +``` + +## 5.4 Error codes + +``` + +CAP-errorcodes {itu-t(0) identified-organization(4) etsi(0) mobileDomain(0) umts-network(1) +modules(3) cap-errorcodes(57) version8(7)} + +``` + +``` + +DEFINITIONS ::= BEGIN + +``` + +``` + +IMPORTS + +``` + +``` + + ros-InformationObjects +FROM CAP-object-identifiers {itu-t(0) identified-organization(4) etsi(0) mobileDomain(0) +umts-network(1) modules(3) cap-object-identifiers(100) version8(7)} + +``` + +``` + + Code +FROM Remote-Operations-Information-Objects ros-InformationObjects + +; + +``` + +``` + +errcode-canceled Code ::= local: 0 +errcode-cancelFailed Code ::= local: 1 +errcode-eTCFailed Code ::= local: 3 +errcode-improperCallerResponse Code ::= local: 4 +errcode-missingCustomerRecord Code ::= local: 6 +errcode-missingParameter Code ::= local: 7 +errcode-parameterOutOfRange Code ::= local: 8 +errcode-requestedInfoError Code ::= local: 10 +errcode-systemFailure Code ::= local: 11 +errcode-taskRefused Code ::= local: 12 +errcode-unavailableResource Code ::= local: 13 +errcode-unexpectedComponentSequence Code ::= local: 14 +errcode-unexpectedDataValue Code ::= local: 15 +errcode-unexpectedParameter Code ::= local: 16 +errcode-unknownLegID Code ::= local: 17 +errcode-unknownPDPID Code ::= local: 50 +errcode-unknownCSID Code ::= local: 51 + +``` + +``` + +END + +``` + +## 5.5 Classes + +``` + +CAP-classes {itu-t(0) identified-organization(4) etsi(0) mobileDomain(0) umts-network(1) +modules(3) cap-classes(54) version8(7)} + +``` + +``` + +DEFINITIONS ::= BEGIN + +``` + +``` + +IMPORTS + +``` + +``` + + ROS-OBJECT-CLASS, + Code +FROM Remote-Operations-Information-Objects ros-InformationObjects + +``` + +``` + + id-rosObject-gprsSSF, + id-rosObject-gsmSRF, + id-rosObject-gsmSSF, + id-rosObject-smsSSF-V3, + id-rosObject-smsSSF-V4, + ros-InformationObjects, + gsmSSF-gsmSCF-Protocol, + gsmSCF-gsmSRF-Protocol, + smsSSF-gsmSCF-Protocol, + gprsSSF-gsmSCF-Protocol + +``` + +``` + +FROM CAP-object-identifiers {itu-t(0) identified-organization(4) etsi(0) mobileDomain(0) +umts-network(1) modules(3) cap-object-identifiers(100) version8(7)} + + capSsfToScfGeneric, + capAssistHandoffssfToScf, + capScfToSsfGeneric +FROM CAP-gsmSSF-gsmSCF-pkgs-contracts-acss gsmSSF-gsmSCF-Protocol + + gsmSRF-gsmSCF-contract +FROM CAP-gsmSCF-gsmSRF-pkgs-contracts-acss gsmSCF-gsmSRF-Protocol + + cap3SMS, + cap4SMS +FROM CAP-smsSSF-gsmSCF-pkgs-contracts-acss smsSSF-gsmSCF-Protocol + + capGprsSsfToScf, + capGsmScfToGprsSsf +FROM CAP-gprsSSF-gsmSCF-pkgs-contracts-acss gprsSSF-gsmSCF-Protocol + + CriticalityType +FROM CS2-datatypes {itu-t(0) identified-organization(4) etsi(0) inDomain(1) in-network(1) cs2(20) +modules(0) in-cs2-datatypes(0) version1(0)} + +; + +gsmSSF ROS-OBJECT-CLASS ::= { + INITIATES {capSsfToScfGeneric| + capAssistHandoffssfToScf} + RESPONDS {capScfToSsfGeneric} + ID id-rosObject-gsmSSF} +-- The Rel-6 'gsmSSF' definition uses the Rel-6 capSsfToScfGeneric, capAssistHandoffssfToScf +-- and capScfToSsfGeneric CONTRACT definitions. + +gsmSRF ROS-OBJECT-CLASS ::= { + INITIATES {gsmSRF-gsmSCF-contract} + ID id-rosObject-gsmSRF} +-- The Rel-6 'gsmSRF' definition uses the Rel-6 gsmSRF-gsmSCF-contract CONTRACT definition. + +smsSSF-V3 ROS-OBJECT-CLASS ::= { + INITIATES {cap3SMS} + ID id-rosObject-smsSSF-V3} +-- The Rel-6 'smsSSF-V3' definition uses the Rel-6 cap3SMS CONTRACT definition. The smsSSF-V3 +-- ROS-OBJECT-CLASS is used for MO SMS control. + +smsSSF-V4 ROS-OBJECT-CLASS ::= { + INITIATES {cap4SMS} + ID id-rosObject-smsSSF-V4} +-- The Rel-6 'smsSSF-V4' definition uses the Rel-6 cap4SMS CONTRACT definition. The smsSSF-V4 +-- ROS-OBJECT-CLASS is used for MT SMS control. + +gprsSSF ROS-OBJECT-CLASS ::= { + INITIATES {capGprsSsfToScf} + RESPONDS {capGsmScfToGprsSsf} + ID id-rosObject-gprsSSF} +-- The Rel-6 'gprsSSF' definition uses the Rel-6 capGprsSsfToGsmScf and capGsmScfToGprsSsf +-- CONTRACT definitions. + +EXTENSION ::= CLASS { + &ExtensionType, + &criticality CriticalityType DEFAULT ignore, + &id Code} + +WITH SYNTAX { + EXTENSION-SYNTAX &ExtensionType + CRITICALITY &criticality + IDENTIFIED BY &id +} +-- Only value Global OBJECT IDENTIFIER is used for &id; +-- Only the value ignore (0) is used for &criticality. + +-- Example of addition of an extension named 'Some Network Specific Indicator' of type +-- BOOLEAN, with criticality 'ignore' and identified by global Object Identifier. +-- +-- Example of definition using the above information object class: +-- +-- SomeNetworkSpecificIndicator EXTENSION ::= { + +``` + +``` + +- EXTENSION-SYNTAX BOOLEAN +- CRITICALITY ignore +- IDENTIFIED BY global : {itu-t(0) identified-organization(4) organisation(0) gsm(1) +- capextension(2) } +- } + +-- Example of transfer syntax, using the ExtensionField datatype as specified in clause 5. +-- Assuming the value of the extension is set to TRUE, the extensions parameter becomes +-- a Sequence of type {itu-t(0) identified-organization(4) organisation(0) gsm(1) +-- capextension(2) }, criticality ENUMERATED ::= ignore(0) and value [1] EXPLICIT BOOLEAN +-- ::= TRUE. +-- +-- Use of ITU-T Recommendation Q.1400 [52] defined Extension is for further study. +-- In addition the extension mechanism marker is used to identify the future minor additions +-- to CAP. + +firstExtension EXTENSION ::= { + EXTENSION-SYNTAX NULL + CRITICALITY ignore + IDENTIFIED BY global : {itu-t(0) identified-organization(4) organisation(0) gsm(1) + capextension(2) } +} +-- firstExtension is just an example. + +SupportedExtensions EXTENSION ::= {firstExtension, ... +-- full set of network operator extensions -- +} +-- SupportedExtension is the full set of the network operator extensions. + +PARAMETERS-BOUND ::= CLASS { + &minAccessPointNameLength INTEGER, + &maxAccessPointNameLength INTEGER, + &minACHBillingChargingLength INTEGER, + &maxACHBillingChargingLength INTEGER, + &minAttributesLength INTEGER, + &maxAttributesLength INTEGER, + &maxBearerCapabilityLength INTEGER, + &minCalledPartyBCDNumberLength INTEGER, + &maxCalledPartyBCDNumberLength INTEGER, + &minCalledPartyNumberLength INTEGER, + &maxCalledPartyNumberLength INTEGER, + &minCallingPartyNumberLength INTEGER, + &maxCallingPartyNumberLength INTEGER, + &minCallResultLength INTEGER, + &maxCallResultLength INTEGER, + &minCarrierLength INTEGER, + &maxCarrierLength INTEGER, + &minCauseLength INTEGER, + &maxCauseLength INTEGER, + &minDigitsLength INTEGER, + &maxDigitsLength INTEGER, + &minFCIBillingChargingDataLength INTEGER, + &maxFCIBillingChargingDataLength INTEGER, + &minFCIBillingChargingLength INTEGER, + &maxFCIBillingChargingLength INTEGER, + &minGenericNumberLength INTEGER, + &maxGenericNumberLength INTEGER, + &minGPRSCauseLength INTEGER, + &maxGPRSCauseLength INTEGER, + &minIPSSPCapabilitiesLength INTEGER, + &maxIPSSPCapabilitiesLength INTEGER, + &minLocationNumberLength INTEGER, + &maxLocationNumberLength INTEGER, + &minLowLayerCompatibilityLength INTEGER, + &maxLowLayerCompatibilityLength INTEGER, + &minMessageContentLength INTEGER, + &maxMessageContentLength INTEGER, + &minOriginalCalledPartyIDLength INTEGER, + &maxOriginalCalledPartyIDLength INTEGER, + &minPDPAddressLength INTEGER, + &maxPDPAddressLength INTEGER, + &minRedirectingPartyIDLength INTEGER, + &maxRedirectingPartyIDLength INTEGER, + &minScfIDLength INTEGER, + &maxScfIDLength INTEGER, + &minSCIBillingChargingLength INTEGER, +} + +``` + +``` + + &maxSCIBillingChargingLength INTEGER, + &minTimeAndTimezoneLength INTEGER, + &maxTimeAndTimezoneLength INTEGER, + &numOfBCSMEvents INTEGER, + &numOfChangeOfPositionControlInfo INTEGER, + &numOfCSSs INTEGER, + &numOfSMSEvents INTEGER, + &numOfGPRSEvents INTEGER, + &numOfExtensions INTEGER, + &numOfGenericNumbers INTEGER, + &numOfMessageIDs INTEGER} + +WITH SYNTAX { + MINIMUM-FOR-ACCESS-POINT-NAME &minAccessPointNameLength + MAXIMUM-FOR-ACCESS-POINT-NAME &maxAccessPointNameLength + MINIMUM-FOR-ACH-BILLING-CHARGING &minAChBillingChargingLength + MAXIMUM-FOR-ACH-BILLING-CHARGING &maxAChBillingChargingLength + MINIMUM-FOR-ATTRIBUTES &minAttributesLength + MAXIMUM-FOR-ATTRIBUTES &maxAttributesLength + MAXIMUM-FOR-BEARER-CAPABILITY &maxBearerCapabilityLength + MINIMUM-FOR-CALLED-PARTY-BCD-NUMBER &minCalledPartyBCDNumberLength + MAXIMUM-FOR-CALLED-PARTY-BCD-NUMBER &maxCalledPartyBCDNumberLength + MINIMUM-FOR-CALLED-PARTY-NUMBER &minCalledPartyNumberLength + MAXIMUM-FOR-CALLED-PARTY-NUMBER &maxCalledPartyNumberLength + MINIMUM-FOR-CALLING-PARTY-NUMBER &minCallingPartyNumberLength + MAXIMUM-FOR-CALLING-PARTY-NUMBER &maxCallingPartyNumberLength + MINIMUM-FOR-CALL-RESULT &minCallResultLength + MAXIMUM-FOR-CALL-RESULT &maxCallResultLength + MINIMUM-FOR-CARRIER &minCarrierLength + MAXIMUM-FOR-CARRIER &maxCarrierLength + MINIMUM-FOR-CAUSE &minCauseLength + MAXIMUM-FOR-CAUSE &maxCauseLength + MINIMUM-FOR-DIGITS &minDigitsLength + MAXIMUM-FOR-DIGITS &maxDigitsLength + MINIMUM-FOR-FCI-BILLING-CHARGING-DATA &minFCIBillingChargingDataLength + MAXIMUM-FOR-FCI-BILLING-CHARGING-DATA &maxFCIBillingChargingDataLength + MINIMUM-FOR-FCI-BILLING-CHARGING &minFCIBillingChargingLength + MAXIMUM-FOR-FCI-BILLING-CHARGING &maxFCIBillingChargingLength + MINIMUM-FOR-GENERIC-NUMBER &minGenericNumberLength + MAXIMUM-FOR-GENERIC-NUMBER &maxGenericNumberLength + MINIMUM-FOR-GPRS-CAUSE-LENGTH &minGPRSCauseLength + MAXIMUM-FOR-GPRS-CAUSE-LENGTH &maxGPRSCauseLength + MINIMUM-FOR-IP-SSP-CAPABILITIES &minIPSSPCapabilitiesLength + MAXIMUM-FOR-IP-SSP-CAPABILITIES &maxIPSSPCapabilitiesLength + MINIMUM-FOR-LOCATION-NUMBER &minLocationNumberLength + MAXIMUM-FOR-LOCATION-NUMBER &maxLocationNumberLength + MINIMUM-FOR-LOW-LAYER-COMPATIBILITY &minLowLayerCompatibilityLength + MAXIMUM-FOR-LOW-LAYER-COMPATIBILITY &maxLowLayerCompatibilityLength + MINIMUM-FOR-MESSAGE-CONTENT &minMessageContentLength + MAXIMUM-FOR-MESSAGE-CONTENT &maxMessageContentLength + MINIMUM-FOR-ORIGINAL-CALLED-PARTY-ID &minOriginalCalledPartyIDLength + MAXIMUM-FOR-ORIGINAL-CALLED-PARTY-ID &maxOriginalCalledPartyIDLength + MINIMUM-FOR-PDP-ADDRESS-LENGTH &minPDPAddressLength + MAXIMUM-FOR-PDP-ADDRESS-LENGTH &maxPDPAddressLength + MINIMUM-FOR-REDIRECTING-ID &minRedirectingPartyIDLength + MAXIMUM-FOR-REDIRECTING-ID &maxRedirectingPartyIDLength + MINIMUM-FOR-GSMSCF-ID &minScfIDLength + MAXIMUM-FOR-GSMSCF-ID &maxScfIDLength + MINIMUM-FOR-SCI-BILLING-CHARGING &minSCIBillingChargingLength + MAXIMUM-FOR-SCI-BILLING-CHARGING &maxSCIBillingChargingLength + MINIMUM-FOR-TIME-AND-TIMEZONE &minTimeAndTimezoneLength + MAXIMUM-FOR-TIME-AND-TIMEZONE &maxTimeAndTimezoneLength + NUM-OF-BCSM-EVENT &numOfBCSMEvents + NUM-OF-CHANGE-OF-POSITION-CONTROL-INFO &numOfChangeOfPositionControlInfo + NUM-OF-CSS &numOfCSSs + NUM-OF-SMS-EVENTS &numOfSMSEvents + NUM-OF-GPRS-EVENTS &numOfGPRSEvents + NUM-OF-EXTENSIONS &numOfExtensions + NUM-OF-GENERIC-NUMBERS &numOfGenericNumbers + NUM-OF-MESSAGE-IDS &numOfMessageIDs} + +cAPSpecificBoundSet PARAMETERS-BOUND ::= { + MINIMUM-FOR-ACCESS-POINT-NAME 1 + MAXIMUM-FOR-ACCESS-POINT-NAME 100 + MINIMUM-FOR-ACH-BILLING-CHARGING 5 + MAXIMUM-FOR-ACH-BILLING-CHARGING 177 + MINIMUM-FOR-ATTRIBUTES 2 +} + +``` + +``` + +MAXIMUM-FOR-ATTRIBUTES 10 +MAXIMUM-FOR-BEARER-CAPABILITY 11 +MINIMUM-FOR-CALLED-PARTY-BCD-NUMBER 1 +MAXIMUM-FOR-CALLED-PARTY-BCD-NUMBER 41 +MINIMUM-FOR-CALLED-PARTY-NUMBER 2 +MAXIMUM-FOR-CALLED-PARTY-NUMBER 18 +MINIMUM-FOR-CALLING-PARTY-NUMBER 2 +MAXIMUM-FOR-CALLING-PARTY-NUMBER 10 +MINIMUM-FOR-CALL-RESULT 12 +MAXIMUM-FOR-CALL-RESULT 193 +MINIMUM-FOR-CARRIER 4 +MAXIMUM-FOR-CARRIER 4 +MINIMUM-FOR-CAUSE 2 +MAXIMUM-FOR-CAUSE 32 +MINIMUM-FOR-DIGITS 2 +MAXIMUM-FOR-DIGITS 16 +MINIMUM-FOR-FCI-BILLING-CHARGING-DATA 1 +MAXIMUM-FOR-FCI-BILLING-CHARGING-DATA 160 +MINIMUM-FOR-FCI-BILLING-CHARGING 5 +MAXIMUM-FOR-FCI-BILLING-CHARGING 225 +MINIMUM-FOR-GENERIC-NUMBER 3 +MAXIMUM-FOR-GENERIC-NUMBER 11 +MINIMUM-FOR-GPRS-CAUSE-LENGTH 1 +MAXIMUM-FOR-GPRS-CAUSE-LENGTH 1 +MINIMUM-FOR-IP-SSP-CAPABILITIES 1 +MAXIMUM-FOR-IP-SSP-CAPABILITIES 4 +MINIMUM-FOR-LOCATION-NUMBER 2 +MAXIMUM-FOR-LOCATION-NUMBER 10 +MINIMUM-FOR-LOW-LAYER-COMPATIBILITY 1 +MAXIMUM-FOR-LOW-LAYER-COMPATIBILITY 16 +MINIMUM-FOR-MESSAGE-CONTENT 1 +MAXIMUM-FOR-MESSAGE-CONTENT 127 +MINIMUM-FOR-ORIGINAL-CALLED-PARTY-ID 2 +MAXIMUM-FOR-ORIGINAL-CALLED-PARTY-ID 10 +MINIMUM-FOR-PDP-ADDRESS-LENGTH 1 +MAXIMUM-FOR-PDP-ADDRESS-LENGTH 63 +MINIMUM-FOR-REDIRECTING-ID 2 +MAXIMUM-FOR-REDIRECTING-ID 10 +MINIMUM-FOR-GSMSCF-ID 2 +MAXIMUM-FOR-GSMSCF-ID 25 +-- maximum length of the ScfID shall be 10 unless the operator defined format +-- of the ScfID requires a higher maximum length +MINIMUM-FOR-SCI-BILLING-CHARGING 4 +MAXIMUM-FOR-SCI-BILLING-CHARGING 225 +MINIMUM-FOR-TIME-AND-TIMEZONE 8 +MAXIMUM-FOR-TIME-AND-TIMEZONE 8 +NUM-OF-BCSM-EVENT 30 +NUM-OF-CHANGE-OF-POSITION-CONTROL-INFO 10 +NUM-OF-CSS 127 +NUM-OF-SMS-EVENTS 10 +NUM-OF-GPRS-EVENTS 10 +NUM-OF-EXTENSIONS 10 +NUM-OF-GENERIC-NUMBERS 5 +NUM-OF-MESSAGE-IDS 16} + +``` + +END + +## 5.6 Object Identifiers (IDs) + +``` + +CAP-object-identifiers {itu-t(0) identified-organization(4) etsi(0) mobileDomain(0) +umts-network(1) modules(3) cap-object-identifiers(100) version8(7)} + +``` + +``` + +DEFINITIONS ::= BEGIN + +``` + +``` + +-- This module assigns object identifiers for Modules, Packages, Contracts and ACs +-- used by CAP + +``` + +``` + +-- For Modules from TC, ROS, +tc-Messages OBJECT IDENTIFIER ::= +{itu-t recommendation q 773 modules(2) messages(1) version3(3)} + +``` + +``` + +tc-NotationExtensions OBJECT IDENTIFIER ::= +{itu-t recommendation q 775 modules(2) notation-extension (4) version1(1)} + +``` + +``` +ros-InformationObjects OBJECT IDENTIFIER ::= + {joint-iso-itu-t remote-operations(4) informationObjects(5) version1(0)} + +-- For CAP Modules +datatypes OBJECT IDENTIFIER ::= + {itu-t(0) identified-organization(4) etsi(0) mobileDomain(0) umts-network(1) modules(3) + cap-datatypes(52) version8(7)} + +errortypes OBJECT IDENTIFIER ::= + {itu-t(0) identified-organization(4) etsi(0) mobileDomain(0) umts-network(1) modules(3) + cap-errortypes(51) version8(7)} + +operationcodes OBJECT IDENTIFIER ::= + {itu-t(0) identified-organization(4) etsi(0) mobileDomain(0) umts-network(1) modules(3) + cap-operationcodes(53) version8(7)} + +errorcodes OBJECT IDENTIFIER ::= + {itu-t(0) identified-organization(4) etsi(0) mobileDomain(0) umts-network(1) modules(3) + cap-errorcodes(57) version8(7)} + +classes OBJECT IDENTIFIER ::= + {itu-t(0) identified-organization(4) etsi(0) mobileDomain(0) umts-network(1) modules(3) + cap-classes(54) version8(7)} + +gsmSSF-gsmSCF-Operations OBJECT IDENTIFIER ::= + {itu-t(0) identified-organization(4) etsi(0) mobileDomain(0) umts-network(1) modules(3) + cap-gsmSSF-gsmSCF-ops-args(101) version8(7)} +-- The Object Identifier 'gsmSSF-gsmSCF-Operations' is updated to version8(7) in Rel-6, so +-- other modules can IMPORT Rel-6 Operation definitions related to call control. + +gsmSSF-gsmSCF-Protocol OBJECT IDENTIFIER ::= + {itu-t(0) identified-organization(4) etsi(0) mobileDomain(0) umts-network(1) modules(3) + cap-gsmSSF-gsmSCF-pkgs-contracts-ac(102) version8(7)} +-- The Object Identifier 'gsmSSF-gsmSCF-Protocol' is updated to version8(7) in Rel-6, so +-- other modules can IMPORT Rel-6 Protocol definitions related to call control. + +gsmSCF-gsmSRF-Operations OBJECT IDENTIFIER ::= + {itu-t(0) identified-organization(4) etsi(0) mobileDomain(0) umts-network(1) modules(3) + cap-gsmSCF-gsmSRF-ops-args(103) version8(7)} +-- The Object Identifier 'gsmSCF-gsmSRF-Operations' is updated to version8(7) in Rel-6, so +-- other modules can IMPORT Rel-6 Operation definitions related to gsmSRF control. + +gsmSCF-gsmSRF-Protocol OBJECT IDENTIFIER ::= + {itu-t(0) identified-organization(4) etsi(0) mobileDomain(0) umts-network(1) modules(3) + cap-gsmSRF-gsmSRF-pkgs-contracts-ac(104) version8(7)} +-- The Object Identifier 'gsmSCF-gsmSRF-Protocol' is updated to version8(7) in Rel-6, so +-- other modules can IMPORT Rel-6 Protocol definitions related to gsmSRF control. + +sms-Operations OBJECT IDENTIFIER ::= + {itu-t(0) identified-organization(4) etsi(0) mobileDomain(0) umts-network(1) modules(3) + cap-SMS-ops-args(105) version8(7)} +-- The Object Identifier 'sms-Operations' is updated to version8(7) in Rel-6, so other +-- modules can IMPORT Rel-6 Operation definitions related to SMS control. + +smsSSF-gsmSCF-Protocol OBJECT IDENTIFIER ::= + {itu-t(0) identified-organization(4) etsi(0) mobileDomain(0) umts-network(1) modules(3) + cap-smsSSF-gsmSCF-pkgs-contracts-ac(106) version8(7)} +-- The Object Identifier 'smsSSF-gsmSCF-Protocol' is updated to version8(7) in Rel-6, so +-- other modules can IMPORT Rel-6 Protocol definitions related to SMS control. + +gprsSSF-gsmSCF-Operations OBJECT IDENTIFIER ::= + {itu-t(0) identified-organization(4) etsi(0) mobileDomain(0) umts-network(1) modules(3) + cap-GPRS-ops-args(107) version8(7)} +-- The Object Identifier 'gprsSSF-gsmSCF-Operations' is updated to version8(7) in Rel-6, so +-- other modules can IMPORT Rel-6 Operation definitions related to GPRS control. + +gprsSSF-gsmSCF-Protocol OBJECT IDENTIFIER ::= + {itu-t(0) identified-organization(4) etsi(0) mobileDomain(0) umts-network(1) modules(3) + cap-gprsSSF-gsmSCF-pkgs-contracts-ac(108) version8(7)} +-- The Object Identifier 'gprsSSF-gsmSCF-Protocol' is updated to version8(7) in Rel-6, so +-- other modules can IMPORT Rel-6 Protocol definitions related to GPRS control. + +id-CAP OBJECT IDENTIFIER ::= + {itu-t(0) identified-organization(4) etsi(0) mobileDomain(0) + umts-network(1) cap4(22)} +``` + +``` + +id-CAP3 OBJECT IDENTIFIER ::= +{itu-t(0) identified-organization(4) etsi(0) mobileDomain(0) +umts-network(1) cap3(20)} + +id-CAPOE OBJECT IDENTIFIER ::= +{itu-t(0) identified-organization(4) etsi(0) mobileDomain(0) +umts-network(1) cap4OE(23)} + +id-CAP3OE OBJECT IDENTIFIER ::= +{itu-t(0) identified-organization(4) etsi(0) mobileDomain(0) +umts-network(1) cap3OE(21)} + +id-ac OBJECT IDENTIFIER ::= {id-CAP ac(3) } +id-acE OBJECT IDENTIFIER ::= {id-CAPOE ac(3) } +id-ac3E OBJECT IDENTIFIER ::= {id-CAP3OEac(3)} +id-as OBJECT IDENTIFIER ::= {id-CAP as(5) } +id-asE OBJECT IDENTIFIER ::= {id-CAPOE as(5) } +id-rosObject OBJECT IDENTIFIER ::= {id-CAP rosObject(25) } +id-contract OBJECT IDENTIFIER ::= {id-CAP contract(26) } +id-contract3 OBJECT IDENTIFIER ::= {id-CAP3 contract(26)} +id-contractE OBJECT IDENTIFIER ::= {id-CAPOE contract(26) } +id-package OBJECT IDENTIFIER ::= {id-CAP package(27) } +id-packageE OBJECT IDENTIFIER ::= {id-CAPOE package(27) } + +-- for ac, as, rosObject, contract and package, the values are identical to ITU-T Recommendation +-- Q.1218 [49] + +-- ROS Objects + +id-rosObject-gsmSCF OBJECT IDENTIFIER ::= {id-rosObject 4} +id-rosObject-gsmSSF OBJECT IDENTIFIER ::= {id-rosObject 5} +id-rosObject-gsmSRF OBJECT IDENTIFIER ::= {id-rosObject 6} +id-rosObject-gprsSSF OBJECT IDENTIFIER ::= {id-rosObject 7} +id-rosObject-smsssf-V3 OBJECT IDENTIFIER ::= {id-rosObject 8} +id-rosObject-smsssf-V4 OBJECT IDENTIFIER ::= {id-rosObject 9} + +-- Application Contexts + +-- gsmSSF/gsmSCF AC +id-ac-CAP-gsmSSF-scfGenericAC OBJECT IDENTIFIER ::= {id-acE 4} +id-ac-CAP-gsmSSF-scfAssistHandoffAC OBJECT IDENTIFIER ::= {id-acE 6} +id-ac-CAP-scf-gsmSSFGenericAC OBJECT IDENTIFIER ::= {id-acE 8} + +-- gsmSRF/gsmSCF AC +id-ac-gsmSRF-gsmSCF OBJECT IDENTIFIER ::= {id-ac 14} + +-- gprsSSF/gsmSCF AC +id-ac-CAP-gprsSSF-gsmSCF-AC OBJECT IDENTIFIER ::= {id-ac3E 50} +id-ac-CAP-gsmSCF-gprsSSF-AC OBJECT IDENTIFIER ::= {id-ac3E 51} + +-- gprsSSF/gsmSCF or gsmSSF/gsmSCF AC +id-ac-cap3-sms-AC OBJECT IDENTIFIER ::= {id-ac3E 61} +id-ac-cap4-sms-AC OBJECT IDENTIFIER ::= {id-acE 61} + +-- Contracts + +-- gsmSSF/gsmSCF Contracts +id-CAPSSfToScfGeneric OBJECT IDENTIFIER ::= {id-contractE 3} +id-CAPAssistHandoffssfToScf OBJECT IDENTIFIER ::= {id-contractE 5} +id-CAPScfToSsfGeneric OBJECT IDENTIFIER ::= {id-contractE 6} + +-- gsmSRF/gsmSCF Contracts +id-contract-gsmSRF-gsmSCF OBJECT IDENTIFIER ::= {id-contract 13} + +-- gprsSSF/gsmSCF Contracts +id-capGprsSsfToGsmScf OBJECT IDENTIFIER ::= {id-contract 14} +id-capGsmScfToGprsSsf OBJECT IDENTIFIER ::= {id-contract 15} + +-- gprsSSF/gsmSCF or gsmSSF/gsmSCF Contracts +id-cap3SmsSsfToGsmScf OBJECT IDENTIFIER ::= {id-contract3 16} +id-cap4SmsSsfToGsmScf OBJECT IDENTIFIER ::= {id-contract 16} + +``` + +## -- Operation Packages + +## -- gsmSSF/gsmSCF Operation Packages + +| | | +|-----------------------------------------------|----------------------------------------| +| id-package-scfActivation | OBJECT IDENTIFIER ::= {id-package 11} | +| id-package-gsmSRF-scfActivationOfAssist | OBJECT IDENTIFIER ::= {id-package 15} | +| id-package-assistConnectionEstablishment | OBJECT IDENTIFIER ::= {id-package 16} | +| id-package-genericDisconnectResource | OBJECT IDENTIFIER ::= {id-package 17} | +| id-package-nonAssistedConnectionEstablishment | OBJECT IDENTIFIER ::= {id-package 18} | +| id-package-connect | OBJECT IDENTIFIER ::= {id-package 19} | +| id-package-callHandling | OBJECT IDENTIFIER ::= {id-packageE 20} | +| id-package-bcsmEventHandling | OBJECT IDENTIFIER ::= {id-package 21} | +| id-package-ssfCallProcessing | OBJECT IDENTIFIER ::= {id-packageE 24} | +| id-package-scfCallInitiation | OBJECT IDENTIFIER ::= {id-package 25} | +| id-package-timer | OBJECT IDENTIFIER ::= {id-package 26} | +| id-package-billing | OBJECT IDENTIFIER ::= {id-package 27} | +| id-package-charging | OBJECT IDENTIFIER ::= {id-package 28} | +| id-package-trafficManagement | OBJECT IDENTIFIER ::= {id-package 29} | +| id-package-callReport | OBJECT IDENTIFIER ::= {id-package 32} | +| id-package-signallingControl | OBJECT IDENTIFIER ::= {id-package 33} | +| id-package-activityTest | OBJECT IDENTIFIER ::= {id-package 34} | +| id-package-cancel | OBJECT IDENTIFIER ::= {id-packageE 36} | +| id-package-cphResponse | OBJECT IDENTIFIER ::= {id-package 37} | +| id-package-exceptionInform | OBJECT IDENTIFIER ::= {id-package 38} | +| id-package-playTone | OBJECT IDENTIFIER ::= {id-package 39} | + +## -- gsmSRF/gsmSCF Operation Packages + +| | | +|---------------------------------------|---------------------------------------| +| id-package-specializedResourceControl | OBJECT IDENTIFIER ::= {id-package 42} | +| id-package-gsmSRF-scfCancel | OBJECT IDENTIFIER ::= {id-package 43} | + +## -- gprsSSF/gsmSCF Operation Packages + +| | | +|-------------------------------------|---------------------------------------| +| id-package-gprsContinue | OBJECT IDENTIFIER ::= {id-package 49} | +| id-package-gprsExceptionInformation | OBJECT IDENTIFIER ::= {id-package 50} | +| id-package-gprsScfActivation | OBJECT IDENTIFIER ::= {id-package 51} | +| id-package-gprsConnect | OBJECT IDENTIFIER ::= {id-package 52} | +| id-package-gprsRelease | OBJECT IDENTIFIER ::= {id-package 53} | +| id-package-gprsEventHandling | OBJECT IDENTIFIER ::= {id-package 54} | +| id-package-gprsTimer | OBJECT IDENTIFIER ::= {id-package 55} | +| id-package-gprsBilling | OBJECT IDENTIFIER ::= {id-package 56} | +| id-package-gprsCharging | OBJECT IDENTIFIER ::= {id-package 57} | +| id-package-gprsActivityTest | OBJECT IDENTIFIER ::= {id-package 58} | +| id-package-gprsCancel | OBJECT IDENTIFIER ::= {id-package 59} | +| id-package-gprsChargeAdvice | OBJECT IDENTIFIER ::= {id-package 60} | + +## -- gprsSSF/gsmSCF or gsmSSF/gsmSCF Operation Packages + +| | | +|-----------------------------|---------------------------------------| +| id-package-smsActivation | OBJECT IDENTIFIER ::= {id-package 61} | +| id-package-smsConnect | OBJECT IDENTIFIER ::= {id-package 62} | +| id-package-smsContinue | OBJECT IDENTIFIER ::= {id-package 63} | +| id-package-smsRelease | OBJECT IDENTIFIER ::= {id-package 64} | +| id-package-smsEventHandling | OBJECT IDENTIFIER ::= {id-package 65} | +| id-package-smsBilling | OBJECT IDENTIFIER ::= {id-package 66} | +| id-package-smsTimer | OBJECT IDENTIFIER ::= {id-package 67} | + +## -- Abstract Syntaxes + +## -- gsmSSF/gsmSCF Abstract Syntaxes + +| | | +|----------------------------------|----------------------------------| +| id-as-gsmSSF-scfGenericAS | OBJECT IDENTIFIER ::= {id-asE 4} | +| id-as-assistHandoff-gsmSSF-scfAS | OBJECT IDENTIFIER ::= {id-asE 6} | +| id-as-scf-gsmSSFGenericAS | OBJECT IDENTIFIER ::= {id-asE 7} | + +## -- gsmSRF/gsmSCF Abstract Syntaxes + +| | | +|---------------------------|----------------------------------| +| id-as-basic-gsmSRF-gsmSCF | OBJECT IDENTIFIER ::= {id-as 14} | +|---------------------------|----------------------------------| + +## -- gprsSSF/gsmSCF Abstract Syntaxes + +| | | +|-------------------------|----------------------------------| +| id-as-gprsSSF-gsmSCF-AS | OBJECT IDENTIFIER ::= {id-as 50} | +| id-as-gsmSCF-gprsSSF-AS | OBJECT IDENTIFIER ::= {id-as 51} | + +## -- gprsSSF/gsmSCF or gsmSSF/gsmSCF Abstract Syntaxes + +| | | +|------------------------|----------------------------------| +| id-as-smsSSF-gsmSCF-AS | OBJECT IDENTIFIER ::= {id-as 61} | +|------------------------|----------------------------------| + +END + +## 5.7 User Abort Data + +CAP-U-ABORT-Data {itu-t(0) identified-organization(4) etsi(0) mobileDomain(0) umts-network(1) modules(3) cap-u-abort-data(110) version8(7)} + +DEFINITIONS ::= BEGIN + +id-CAP-U-ABORT-Reason OBJECT IDENTIFIER ::= {itu-t(0) identified-organization(4) etsi(0) mobileDomain(0) umts-Network(1) as(1) cap-u-abort-reason(2) version3(2)} + +cap-U-ABORT-Reason-Abstract-Syntax ABSTRACT-SYNTAX ::= {CAP-U-ABORT-REASON IDENTIFIED BY id-CAP-U-ABORT-Reason} + +CAP-U-ABORT-REASON ::= ENUMERATED { + +no-reason-given (1), + application-timer-expired (2), + not-allowed-procedures (3), + abnormal-processing (4), + congestion (5), + invalid-reference (6), + missing-reference (7), + overlapping-dialogue (8) + } + +-- application-timer-expired shall be set when application timer (e.g. Tssf) is expired. + -- not-allowed-procedures shall be set when received signal is not allowed in CAP procedures. + -- For example, when a class 4 operation is received from the gsmSCF and the operation is not allowed in gsmSSF FSM. (gsmSSF FSM cannot continue state transition). (e.g. ReleaseCall operation received in Waiting for End of Temporary Connection state.) + -- abnormal-processing shall be set when abnormal procedures occur at entity action. + -- congestion shall be set when requested resource is unavailable due to congestion at TC user (CAP) level. + -- invalid-reference shall be set if the received destinationReference is unknown or for a known destination Reference the received originationReference does not match with the stored originationReference. + -- This abort reason is used for CAP defined GPRS-ReferenceNumber. + -- missing-reference shall be set when the destinationReference or the originationReference is absent in the received message but is required to be present according to the procedures in subclause 14.1.7. + -- This abort reason is used for CAP defined GPRS-ReferenceNumber. + -- overlapping-dialogue shall be used by the gprsSSF to indicate to the gsmSCF that a specific instance already has a TC dialogue open. This error cause is typically obtained when both the gsmSCF and gprsSSF open a new dialogue at the same time. + -- no-reason-given shall be set when any other reasons above do not apply + END — of CAP-U-ABORT-Data + +## 6 Circuit Switched Call Control + +### 6.1 gsmSSF/CCF - gsmSCF Interface + +#### 6.1.1 Operations and arguments + +CAP-gsmSSF-gsmSCF-ops-args {itu-t(0) identified-organization(4) etsi(0) mobileDomain(0) umts-network(1) modules(3) cap-gsmSSF-gsmSCF-ops-args(101) version8(7)} + +DEFINITIONS IMPLICIT TAGS ::= BEGIN + +-- This module contains the operations and operation arguments used for the + -- gsmSSF - gsmSCF interface, for the control of circuit switched calls. + -- The table in subclause 2.1 lists the specifications that contain the modules + -- that are used by CAP. + +IMPORTS + +``` +errortypes, +datatypes, +operationcodes, +classes, +tc-Messages, +ros-InformationObjects +FROM CAP-object-identifiers {itu-t(0) identified-organization(4) etsi(0) mobileDomain(0) +umts-network(1) modules(3) cap-object-identifiers(100) version8(7)} + +OPERATION +FROM Remote-Operations-Information-Objects ros-InformationObjects + +CallingPartysCategory, +HighLayerCompatibility, +LegID, +RedirectionInformation, +ServiceKey +FROM CS1-DataTypes {itu-t(0) identified-organization(4) etsi(0) inDomain(1) in-network(1) +modules(0) cs1-datatypes(2) version1(0)} + +MiscCallInfo +FROM CS2-datatypes {itu-t(0) identified-organization(4) etsi(0) inDomain(1) in-network(1) +cs2(20) modules(0) in-cs2-datatypes(0) version1(0)} + +Ext-BasicServiceCode, +IMEI, +IMSI, +ISDN-AddressString +FROM MAP-CommonDataTypes {itu-t(0) identified-organization(4) etsi(0) mobileDomain(0) +gsm-Network(1) modules(3) map-CommonDataTypes(18) version12(12)} + +CUG-Index, +CUG-Interlock, +CUG-Info, +LocationInformation, +MS-Classmark2, +SubscriberState, +SupportedCamelPhases, +OfferedCamel4Functionalities +FROM MAP-MS-DataTypes {itu-t(0) identified-organization(4) etsi(0) mobileDomain(0) +gsm-Network(1) modules(3) map-MS-DataTypes(11) version12(12)} + +CallReferenceNumber, +SuppressionOfAnnouncement, +UU-Data +FROM MAP-CH-DataTypes {itu-t(0) identified-organization(4) etsi(0) mobileDomain(0) +gsm-Network(1) modules(3) map-CH-DataTypes(13) version12(12)} + +PARAMETERS-BOUND +FROM CAP-classes classes + +opcode-activityTest, +opcode-applyCharging, +opcode-applyChargingReport, +opcode-assistRequestInstructions, +opcode-callGap, +opcode-callInformationReport, +opcode-callInformationRequest, +opcode-cancel, +opcode-collectInformation, +opcode-connect, +opcode-connectToResource, +opcode-continue, +opcode-continueWithArgument, +opcode-disconnectForwardConnection, +opcode-dFCWithArgument, +opcode-disconnectLeg, +opcode-entityReleased, +opcode-establishTemporaryConnection, +opcode-eventReportBCSM, +opcode-furnishChargingInformation, +opcode-initialDP, +opcode-initiateCallAttempt, +opcode-moveLeg, +opcode-playTone, +opcode-releaseCall, +opcode-requestReportBCSMEvent, +``` + +``` +opcode-resetTimer, +opcode-sendChargingInformation, +opcode-splitLeg +FROM CAP-operationcodes operationcodes +-- The CAP Operation identifiers for CAP V4 in Rel-6 are the same as the CAP Operation +-- identifiers for CAP V4 in Rel-5. + +AChBillingChargingCharacteristics {}, +AdditionalCallingPartyNumber {}, +AlertingPattern, +AChChargingAddress {}, +AssistingSSPIPRoutingAddress {}, +BCSMEVENT {}, +BCSM-Failure, +BearerCapability {}, +Burst, +CalledPartyNumber {}, +CalledPartyBCDNumber {}, +CallingPartyNumber {}, +CallResult {}, +CallSegmentID {}, +CallSegmentToCancel {}, +CallSegmentFailure {}, +Carrier, +Cause {}, +CGEncountered, +ChargeNumber {}, +ControlType, +CorrelationID {}, +DestinationRoutingAddress {}, +EventSpecificInformationBCSM {}, +EventTypeBCSM, +Extensions {}, +FCIBillingChargingCharacteristics {}, +GapCriteria {}, +GapIndicators, +GapTreatment, +GenericNumbers {}, +InvokeID, +IPRoutingAddress {}, +IPSSPCapabilities {}, +leg1, +leg2, +LegOrCallSegment {}, +LocationNumber {}, +LowLayerCompatibility {}, +MonitorMode, +NAOLiInfo, +OCSIApplicable, +OriginalCalledPartyID {}, +ReceivingSideID, +RedirectingPartyID {}, +RequestedInformationList {}, +RequestedInformationTypeList, +ScfID {}, +SCIBillingChargingCharacteristics {}, +SendingSideID, +ServiceInteractionIndicatorsTwo, +TimeAndTimezone {}, +TimerID, +TimerValue +FROM CAP-datatypes datatypes +-- For Rel-6, the CAP-datatypes module is updated to version8(7); Object Identifier 'datatypes' +-- is also updated to version8(7). As a result, the present module uses Rel-6 data type definitions. + +cancelFailed, +eTCFailed, +missingCustomerRecord, +missingParameter, +parameterOutOfRange, +requestedInfoError, +systemFailure, +taskRefused, +unexpectedComponentSequence, +unexpectedDataValue, +unexpectedParameter, +unknownLegID, +unknownCSID +``` + +``` + +FROM CAP-errorTypes errorTypes +-- For Rel-6, the CAP-errorTypes module is updated to version8(7); Object Identifier +-- 'errorTypes' is also updated to version8(7). As a result, the present module uses Rel-6 +-- error type definitions. + +; + +activityTest OPERATION ::= { + RETURN RESULT TRUE + CODE opcode-activityTest} +-- Direction: gsmSCF -> gsmSSF, Timer: Tat +-- This operation is used to check for the continued existence of a relationship +-- between the gsmSCF and gsmSSF, assist gsmSSF or gsmSRF. If the relationship is +-- still in existence, then the gsmSSF will respond. If no reply is received, +-- then the gsmSCF will assume that the gsmSSF, assist gsmSSF or gsmSRF has failed +-- in some way. + +applyCharging {PARAMETERS-BOUND : bound} OPERATION ::= { + ARGUMENT ApplyChargingArg {bound} + RETURN RESULT FALSE + ERRORS {missingParameter | + unexpectedComponentSequence | + unexpectedParameter | + unexpectedDataValue | + parameterOutOfRange | + systemFailure | + taskRefused | + unknownLegID | + unknownCSID} + CODE opcode-applyCharging} +-- Direction: gsmSCF -> gsmSSF, Timer: Tac +-- This operation is used for interacting from the gsmSCF with the gsmSSF charging mechanisms. +-- The ApplyChargingReport operation provides the feedback from the gsmSSF to the gsmSCF. + +ApplyChargingArg {PARAMETERS-BOUND : bound} ::= SEQUENCE { + aChBillingChargingCharacteristics [0] AChBillingChargingCharacteristics {bound}, + partyToCharge [2] SendingSideID DEFAULT sendingSideID : leg1, + extensions [3] Extensions {bound} OPTIONAL, + aChChargingAddress [50] AChChargingAddress {bound} + DEFAULT legID:sendingSideID:leg1, + ... +} + +-- The partyToCharge parameter indicates the party in the call to which the ApplyCharging operation +-- shall be applied. + +applyChargingReport {PARAMETERS-BOUND : bound} OPERATION ::= { + ARGUMENT ApplyChargingReportArg {bound} + RETURN RESULT FALSE + ERRORS {missingParameter | + unexpectedComponentSequence | + unexpectedParameter | + unexpectedDataValue | + unknownCSID | + unknownLegID | + parameterOutOfRange | + systemFailure | + taskRefused} + CODE opcode-applyChargingReport} +-- Direction: gsmSSF -> gsmSCF, Timer: Tacr +-- This operation is used by the gsmSSF to report to the gsmSCF the occurrence of a +-- specific charging event as requested by the gsmSCF using the ApplyCharging operation. + +ApplyChargingReportArg {PARAMETERS-BOUND : bound} ::= CallResult {bound} + +assistRequestInstructions {PARAMETERS-BOUND : bound} OPERATION ::= { + ARGUMENT AssistRequestInstructionsArg {bound} + RETURN RESULT FALSE + ERRORS {missingCustomerRecord | + missingParameter | + systemFailure | + taskRefused | + unexpectedComponentSequence | + unexpectedDataValue | + unexpectedParameter} + CODE opcode-assistRequestInstructions} +-- Direction: gsmSSF -> gsmSCF or gsmSRF -> gsmSCF, Timer: Tari + +``` + +``` + +-- This operation is used when there is an assist procedure and may be +-- sent by the gsmSSF or gsmSRF to the gsmSCF. This operation is sent by the +-- assisting gsmSSF to gsmSCF, when the initiating gsmSSF has set up a connection to +-- the gsmSRF or to the assisting gsmSSF as a result of receiving an +-- EstablishTemporaryConnection from +-- the gsmSCF. +-- Refer to clause 11 for a description of the procedures associated with this operation. + +AssistRequestInstructionsArg {PARAMETERS-BOUND : bound} ::= SEQUENCE { + correlationID [0] CorrelationID {bound}, + iPSSPCapabilities [2] IPSSPCapabilities {bound}, + extensions [3] Extensions {bound} OPTIONAL, + ... +} + +-- OPTIONAL denotes network operator specific use. The value of the correlationID may be the +-- Called Party Number supplied by the initiating gsmSSF. + +callGap {PARAMETERS-BOUND : bound} OPERATION ::= { + ARGUMENT CallGapArg {bound} + RETURN RESULT FALSE + ALWAYS RESPONDS FALSE + CODE opcode-callGap} +-- Direction: gsmSCF -> gsmSSF, Timer: Tcg +-- This operation is used to request the gsmSSF to reduce the rate at which specific service +-- requests are sent to the gsmSCF. + +CallGapArg {PARAMETERS-BOUND : bound} ::= SEQUENCE { + gapCriteria [0] GapCriteria {bound}, + gapIndicators [1] GapIndicators, + controlType [2] ControlType OPTIONAL, + gapTreatment [3] GapTreatment {bound} OPTIONAL, + extensions [4] Extensions {bound} OPTIONAL, + ... +} + +-- OPTIONAL denotes network operator optional. If gapTreatment is not present, then the gsmSSF will +-- use a default treatment depending on network operator implementation. + +callInformationReport {PARAMETERS-BOUND : bound} OPERATION ::= { + ARGUMENT CallInformationReportArg {bound} + RETURN RESULT FALSE + ALWAYS RESPONDS FALSE + CODE opcode-callInformationReport} +-- Direction: gsmSSF -> gsmSCF, Timer: Tcirp +-- This operation is used to send specific call information for a single call party to the gsmSCF as +-- requested by the gsmSCF in a previous CallInformationRequest. + +CallInformationReportArg {PARAMETERS-BOUND : bound} ::= SEQUENCE { + requestedInformationList [0] RequestedInformationList {bound}, + extensions [2] Extensions {bound} OPTIONAL, + legID [3] ReceivingSideID DEFAULT receivingSideID:leg2, + ... +} + +callInformationRequest {PARAMETERS-BOUND : bound} OPERATION ::= { + ARGUMENT CallInformationRequestArg {bound} + RETURN RESULT FALSE + ERRORS {missingParameter | + parameterOutOfRange | + requestedInfoError | + systemFailure | + taskRefused | + unexpectedComponentSequence | + unexpectedDataValue | + unexpectedParameter | + unknownLegID} + CODE opcode-callInformationRequest} +-- Direction: gsmSCF -> gsmSSF, Timer: Tcirq +-- This operation is used to request the gsmSSF to record specific information about a single +-- call party and report it to the gsmSCF (with a CallInformationReport operation). + +CallInformationRequestArg {PARAMETERS-BOUND : bound} ::= SEQUENCE { + requestedInformationTypeList [0] RequestedInformationTypeList, + extensions [2] Extensions {bound} OPTIONAL, + legID [3] SendingSideID DEFAULT sendingSideID:leg2, + ... +} + +-- OPTIONAL denotes network operator optional. + +``` + +``` + +cancel {PARAMETERS-BOUND : bound} OPERATION ::= { + ARGUMENT CancelArg {bound} + RETURN RESULT FALSE + ERRORS {cancelFailed | + missingParameter | + taskRefused | + unknownCSID} + CODE opcode-cancel} +-- Direction: gsmSCF -> gsmSSF, or gsmSCF -> gsmSRF, Timer: Tcan +-- This operation cancels the correlated previous operation or all previous requests. The following +-- operations can be canceled: PlayAnnouncement, PromptAndCollectUserInformation. + +CancelArg {PARAMETERS-BOUND : bound} ::= CHOICE { + invokeID [0] InvokeID, + allRequests [1] NULL, + callSegmentToCancel [2] CallSegmentToCancel {bound} +} +-- The InvokeID has the same value as that which was used for the operation to be cancelled. + +collectInformation {PARAMETERS-BOUND : bound} OPERATION ::= { + ARGUMENT CollectInformationArg {bound} + RETURN RESULT FALSE + ERRORS {missingParameter | + parameterOutOfRange | + SystemFailure | + TaskRefused | + UnexpectedComponentSequence | + UnexpectedDataValue | + UnexpectedParameter} + CODE opcode-collectInformation} +-- Direction: gsmSCF-> gsmSSF, Timer: Tci +-- This operation is used to request the gsmSSF to perform the call +-- processing actions to prompt a calling party for additional digits. + +CollectInformationArg {PARAMETERS-BOUND : bound} ::= SEQUENCE{ + extensions [0] Extensions {bound} OPTIONAL, + ... +} + +connect {PARAMETERS-BOUND : bound} OPERATION ::= { + ARGUMENT ConnectArg {bound} + RETURN RESULT FALSE + ERRORS {missingParameter | + parameterOutOfRange | + systemFailure | + taskRefused | + unexpectedComponentSequence | + unexpectedDataValue | + unexpectedParameter | + unknownLegID} + CODE opcode-connect} +-- Direction: gsmSCF-> gsmSSF, Timer: Tcon +-- This operation is used to request the gsmSSF to perform the call processing actions +-- to route or forward a call to a specified destination. + +ConnectArg {PARAMETERS-BOUND : bound} ::= SEQUENCE { + destinationRoutingAddress [0] DestinationRoutingAddress {bound}, + alertingPattern [1] AlertingPattern OPTIONAL, + originalCalledPartyID [6] OriginalCalledPartyID {bound} OPTIONAL, + extensions [10] Extensions {bound} OPTIONAL, + carrier [11] Carrier {bound} OPTIONAL, + callingPartysCategory [28] CallingPartysCategory OPTIONAL, + redirectingPartyID [29] RedirectingPartyID {bound} OPTIONAL, + redirectionInformation [30] RedirectionInformation OPTIONAL, + genericNumbers [14] GenericNumbers {bound} OPTIONAL, + serviceInteractionIndicatorsTwo [15] ServiceInteractionIndicatorsTwo OPTIONAL, + chargeNumber [19] ChargeNumber {bound} OPTIONAL, + legToBeConnected [21] LegID OPTIONAL, + cug-Interlock [31] CUG-Interlock OPTIONAL, + cug-OutgoingAccess [32] NULL OPTIONAL, + suppressionOfAnnouncement [55] SuppressionOfAnnouncement OPTIONAL, + oCSIApplicable [56] OCSIApplicable OPTIONAL, + naOliInfo [57] NAOLiInfo OPTIONAL, + bor-InterrogationRequested [58] NULL OPTIONAL, + ... / + suppress-N-CSI [59] NULL OPTIONAL +} +-- na-Info is included at the discretion of the gsmSCF operator. + +``` + +``` + +connectToResource {PARAMETERS-BOUND : bound} OPERATION ::= { + ARGUMENT ConnectToResourceArg {bound} + RETURN RESULT FALSE + ERRORS {missingParameter | + systemFailure | + taskRefused | + unexpectedComponentSequence | + unexpectedDataValue | + unexpectedParameter | + unknownCSID} + CODE opcode-connectToResource} +-- Direction: gsmSCF -> gsmSSF, Timer: Tctr +-- This operation is used to connect a call segment from the gsmSSF to the +-- gsmSRF. + +ConnectToResourceArg {PARAMETERS-BOUND : bound} ::= SEQUENCE { + resourceAddress CHOICE { + ipRoutingAddress [0] IPRoutingAddress {bound}, + none [3] NULL + }, + extensions [4] Extensions {bound} OPTIONAL, + serviceInteractionIndicatorsTwo [7] ServiceInteractionIndicatorsTwo OPTIONAL, + callSegmentID [50] CallSegmentID {bound} OPTIONAL, + ... +} + +continue OPERATION ::= { + RETURN RESULT FALSE + ALWAYS RESPONDS FALSE + CODE opcode-continue} +-- Direction: gsmSCF -> gsmSSF, Timer: Tcue +-- This operation is used to request the gsmSSF to proceed with call processing at the +-- DP at which it previously suspended call processing to await gsmSCF instructions +-- (i.e. proceed to the next point in call in the BCSM). The gsmSSF continues call +-- processing without substituting new data from gsmSCF. + +continueWithArgument {PARAMETERS-BOUND : bound} OPERATION ::= { + ARGUMENT ContinueWithArgumentArg {bound} + RETURN RESULT FALSE + ERRORS {missingParameter | + parameterOutOfRange | + unexpectedComponentSequence | + unexpectedDataValue | + unexpectedParameter | + unknownLegID | + unknownCSID} + CODE opcode-continueWithArgument} +-- Direction: gsmSCF -> gsmSSF, Timer: Tcwa +-- This operation is used to request the gsmSSF to proceed with call processing at the +-- DP at which it previously suspended call processing to await gsmSCF instructions +-- (i.e. proceed to the next point in call in the BCSM). The gsmSSF continues call +-- processing with the modified call setup information as received from the gsmSCF. + +ContinueWithArgumentArg {PARAMETERS-BOUND : bound} ::= SEQUENCE { + alertingPattern [1] AlertingPattern OPTIONAL, + extensions [6] Extensions {bound} OPTIONAL, + serviceInteractionIndicatorsTwo [7] ServiceInteractionIndicatorsTwo OPTIONAL, + callingPartysCategory [12] CallingPartysCategory OPTIONAL, + genericNumbers [16] GenericNumbers {bound} OPTIONAL, + cug-Interlock [17] CUG-Interlock OPTIONAL, + cug-OutgoingAccess [18] NULL OPTIONAL, + chargeNumber [50] ChargeNumber {bound} OPTIONAL, + carrier [52] Carrier {bound} OPTIONAL, + suppressionOfAnnouncement [55] SuppressionOfAnnouncement OPTIONAL, + naOliInfo [56] NAOLiInfo OPTIONAL, + bor-InterrogationRequested [57] NULL OPTIONAL, + suppress-O-CSI [58] NULL OPTIONAL, + continueWithArgumentArgExtension [59] ContinueWithArgumentArgExtension {bound} OPTIONAL, + ... +} + +ContinueWithArgumentArgExtension {PARAMETERS-BOUND : bound} ::= SEQUENCE { + suppress-D-CSI [0] NULL OPTIONAL, + suppress-N-CSI [1] NULL OPTIONAL, + suppressOutgoingCallBarring [2] NULL OPTIONAL, + legOrCallSegment [3] LegOrCallSegment {bound} OPTIONAL, + ... +} + +``` + +``` + + } + + disconnectForwardConnection OPERATION ::= { + RETURN RESULT FALSE + ERRORS {systemFailure | + taskRefused | + unexpectedComponentSequence} + CODE opcode-disconnectForwardConnection} + -- Direction: gsmSCF -> gsmSSF, Timer: Tdfc + -- This operation is used to disconnect a forward temporary connection or a connection to a + -- resource. Refer to clause 11 for a description of the procedures associated with this operation. + + disconnectForwardConnectionWithArgument {PARAMETERS-BOUND : bound} OPERATION ::= { + ARGUMENT DisconnectForwardConnectionWithArgumentArg {bound} + RETURN RESULT FALSE + ERRORS {missingParameter | + systemFailure | + taskRefused | + unexpectedComponentSequence | + unexpectedDataValue | + unexpectedParameter | + unknownCSID} + CODE opcode-dFCWithArgument} + -- Direction gsmSCF -> gsmSSF, Timer Tdfcwa + -- This operation is used to disconnect a forward temporary connection or a connection to a + -- resource. Refer to clause 11 for a description of the procedures associated with this operation. + + DisconnectForwardConnectionWithArgumentArg {PARAMETERS-BOUND : bound} ::= SEQUENCE { + callSegmentID [1] CallSegmentID {bound} OPTIONAL, + extensions [2] Extensions {bound} OPTIONAL, + ... + } + + disconnectLeg {PARAMETERS-BOUND : bound} OPERATION ::= { + ARGUMENT DisconnectLegArg {bound} + RETURN RESULT TRUE + ERRORS {missingParameter | + systemFailure | + taskRefused | + unexpectedComponentSequence | + unexpectedDataValue | + unexpectedParameter | + unknownLegID} + CODE opcode-disconnectLeg} + -- Direction: gsmSCF -> gsmSSF, Timer Tdl + -- This operation is used by the gsmSCF to release a specific leg associated with the call and + -- retain any other legs not specified in the DisconnectLeg. Refer to clause 11 for a description + -- of the procedures associated with this operation. + + DisconnectLegArg {PARAMETERS-BOUND : bound} ::= SEQUENCE { + legToBeReleased [0] LegID, + releaseCause [1] Cause {bound} OPTIONAL, + extensions [2] Extensions {bound} OPTIONAL, + ... + } + + entityReleased {PARAMETERS-BOUND : bound} OPERATION ::= { + ARGUMENT EntityReleasedArg {bound} + RETURN RESULT FALSE + ALWAYS RESPONDS FALSE + CODE opcode-entityReleased} + -- Direction: gsmSSF -> gsmSCF, Timer: Ter + -- This operation is used by the gsmSSF to inform the gsmSCF of an error or exception + + EntityReleasedArg {PARAMETERS-BOUND : bound} ::= CHOICE { + callSegmentFailure [0] CallSegmentFailure {bound}, + bCSM-Failure [1] BCSM-Failure {bound} + } + + establishTemporaryConnection {PARAMETERS-BOUND : bound} OPERATION ::= { + ARGUMENT EstablishTemporaryConnectionArg {bound} + RETURN RESULT FALSE + ERRORS {eTCFailed | + missingParameter | + systemFailure | + taskRefused | + unexpectedComponentSequence | + +``` + +``` + + unexpectedDataValue | + unexpectedParameter | + unknownCSID} + CODE opcode-establishTemporaryConnection} +-- Direction: gsmSCF -> gsmSSF, Timer: Tetc +-- This operation is used to create a connection to a resource for a limited period +-- of time (e.g. to play an announcement, to collect user information); it implies +-- the use of the assist procedure. Refer to clause 11 for a description of the +-- procedures associated with this operation. + +EstablishTemporaryConnectionArg {PARAMETERS-BOUND : bound} ::= SEQUENCE { + assistingSSIPRoutingAddress [0] AssistingSSIPRoutingAddress {bound}, + correlationID [1] CorrelationID {bound} OPTIONAL, + scfID [3] ScfID {bound} OPTIONAL, + extensions [4] Extensions {bound} OPTIONAL, + carrier [5] Carrier {bound} OPTIONAL, + serviceInteractionIndicatorsTwo [6] ServiceInteractionIndicatorsTwo OPTIONAL, + callSegmentID [7] CallSegmentID {bound} OPTIONAL, + naOliInfo [50] NAOLiInfo OPTIONAL, + chargeNumber [51] ChargeNumber {bound} OPTIONAL, + ... + originalCalledPartyID [52] OriginalCalledPartyID {bound} OPTIONAL, + callingPartyNumber [53] CallingPartyNumber {bound} OPTIONAL +} + +eventReportBCSM {PARAMETERS-BOUND : bound} OPERATION ::= { + ARGUMENT EventReportBCSMArg {bound} + RETURN RESULT FALSE + ALWAYS RESPONDS FALSE + CODE opcode-eventReportBCSM} +-- Direction: gsmSSF -> gsmSCF, Timer: Terb +-- This operation is used to notify the gsmSCF of a call-related event (e.g. BCSM +-- events such as O_Busy or O_No_Answer) previously requested by the gsmSCF in a +-- RequestReportBCSMEVENT operation. + +EventReportBCSMArg {PARAMETERS-BOUND : bound} ::= SEQUENCE { + eventTypeBCSM [0] EventTypeBCSM, + eventSpecificInformationBCSM [2] EventSpecificInformationBCSM {bound} OPTIONAL, + legID [3] ReceivingSideID OPTIONAL, + miscCallInfo [4] MiscCallInfo DEFAULT {messageType request}, + extensions [5] Extensions {bound} OPTIONAL, + ... +} + +furnishChargingInformation {PARAMETERS-BOUND : bound} OPERATION ::= { + ARGUMENT FurnishChargingInformationArg {bound} + RETURN RESULT FALSE + ERRORS {missingParameter | + taskRefused | + unexpectedComponentSequence | + unexpectedDataValue | + unexpectedParameter | + unknownLegID} + CODE opcode-furnishChargingInformation} +-- Direction: gsmSCF -> gsmSSF, Timer: Tfci +-- This operation is used to request the gsmSSF to generate, register a call record +-- or to include some information in the default call record. +-- The registered call record is intended for off line charging of the call. + +FurnishChargingInformationArg {PARAMETERS-BOUND : bound} ::= + FCIBillingChargingCharacteristics{bound} + +initialDP {PARAMETERS-BOUND : bound} OPERATION ::= { + ARGUMENT InitialDPArg {bound} + RETURN RESULT FALSE + ERRORS {missingCustomerRecord | + missingParameter | + parameterOutOfRange | + systemFailure | + taskRefused | + unexpectedComponentSequence | + unexpectedDataValue | + unexpectedParameter} + CODE opcode-initialDP} +-- Direction: gsmSSF -> gsmSCF, Timer: Tidp +-- This operation is used after a TDP to indicate request for service. + +``` + +``` + +InitialDPArg {PARAMETERS-BOUND : bound} ::= SEQUENCE { + serviceKey [0] ServiceKey , + calledPartyNumber [2] CalledPartyNumber {bound} OPTIONAL, + callingPartyNumber [3] CallingPartyNumber {bound} OPTIONAL, + callingPartysCategory [5] CallingPartysCategory OPTIONAL, + cGEncountered [7] CGEncountered OPTIONAL, + iPSSPCapabilities [8] IPSSPCapabilities {bound} OPTIONAL, + locationNumber [10] LocationNumber {bound} OPTIONAL, + originalCalledPartyID [12] OriginalCalledPartyID {bound} OPTIONAL, + extensions [15] Extensions {bound} OPTIONAL, + highLayerCompatibility [23] HighLayerCompatibility OPTIONAL, + additionalCallingPartyNumber [25] AdditionalCallingPartyNumber {bound} OPTIONAL, + bearerCapability [27] BearerCapability {bound} OPTIONAL, + eventTypeBCSM [28] EventTypeBCSM OPTIONAL, + redirectingPartyID [29] RedirectingPartyID {bound} OPTIONAL, + redirectionInformation [30] RedirectionInformation OPTIONAL, + cause [17] Cause {bound} OPTIONAL, + serviceInteractionIndicatorsTwo [32] ServiceInteractionIndicatorsTwo OPTIONAL, + carrier [37] Carrier {bound} OPTIONAL, + cug-Index [45] CUG-Index OPTIONAL, + cug-Interlock [46] CUG-Interlock OPTIONAL, + cug-OutgoingAccess [47] NULL OPTIONAL, + iMSI [50] IMSI OPTIONAL, + subscriberState [51] SubscriberState OPTIONAL, + locationInformation [52] LocationInformation OPTIONAL, + ext-basicServiceCode [53] Ext-BasicServiceCode OPTIONAL, + callReferenceNumber [54] CallReferenceNumber OPTIONAL, + mscAddress [55] ISDN-AddressString OPTIONAL, + calledPartyBCDNumber [56] CalledPartyBCDNumber {bound} OPTIONAL, + timeAndTimezone [57] TimeAndTimezone {bound} OPTIONAL, + callForwardingSS-Pending [58] NULL OPTIONAL, + initialDPArgExtension [59] InitialDPArgExtension {bound} OPTIONAL, + ... +} + +``` + +``` + +InitialDPArgExtension {PARAMETERS-BOUND : bound} ::= SEQUENCE { + gmsCAddress [0] ISDN-AddressString OPTIONAL, + forwardingDestinationNumber [1] CalledPartyNumber {bound} OPTIONAL, + ms-Classmark2 [2] MS-Classmark2 OPTIONAL, + iMEI [3] IMEI OPTIONAL, + supportedCamelPhases [4] SupportedCamelPhases OPTIONAL, + offeredCamel4Functionalities [5] OfferedCamel4Functionalities OPTIONAL, + bearerCapability2 [6] BearerCapability {bound} OPTIONAL, + ext-basicServiceCode2 [7] Ext-BasicServiceCode OPTIONAL, + highLayerCompatibility2 [8] HighLayerCompatibility OPTIONAL, + lowLayerCompatibility [9] LowLayerCompatibility {bound} OPTIONAL, + lowLayerCompatibility2 [10] LowLayerCompatibility {bound} OPTIONAL, + ... + enhancedDialledServicesAllowed [11] NULL OPTIONAL, + uu-Data [12] UU-Data OPTIONAL, + collectInformationAllowed [13] NULL OPTIONAL, + releaseCallArgExtensionAllowed [14] NULL OPTIONAL +} + +``` + +-- If iPSSPCapabilities is not present then this denotes that a colocated gsmSRF is not + -- supported by the gsmSSF. If present, then the gsmSSF supports a colocated gsmSRF capable + -- of playing announcements via elementaryMessageIDs and variableMessages, the playing of + -- tones and the collection of DTMF digits. Other supported capabilities are explicitly + -- detailed in the IPSSPCapabilities parameter itself. + -- Carrier is included at the discretion of the gsmSSF operator. + -- The UserCSGInformation is conveyed in the LocationInformation. **The encoding of the parameter is + -- as defined in 3GPP TS 29.002 [11].** + +``` + +initiateCallAttempt {PARAMETERS-BOUND : bound} OPERATION ::= { + ARGUMENT InitiateCallAttemptArg {bound} + RESULT InitiateCallAttemptRes {bound} + ERRORS {missingParameter | + parameterOutOfRange | + systemFailure | + taskRefused | + unexpectedComponentSequence | + unexpectedDataValue | + unexpectedParameter + } + CODE opcode-initiateCallAttempt} + +``` + +-- Direction: gsmSCF -> gsmSSF, Timer Tica + -- This operation is used to instruct the gsmSSF to create a new call to a call party using the + -- address information provided by the gsmSCF. + +``` + +InitiateCallAttemptArg {PARAMETERS-BOUND : bound} ::= SEQUENCE { + destinationRoutingAddress [0] DestinationRoutingAddress {bound}, + extensions [4] Extensions {bound} OPTIONAL, + legToBeCreated [5] LegID OPTIONAL, + newCallSegment [6] CallSegmentID {bound} OPTIONAL, + callingPartyNumber [30] CallingPartyNumber {bound} OPTIONAL, + callReferenceNumber [51] CallReferenceNumber OPTIONAL, + gsmSCFAddress [52] ISDN-AddressString OPTIONAL, + suppress-T-CSI [53] NULL OPTIONAL, + ... +} + +InitiateCallAttemptRes {PARAMETERS-BOUND : bound} ::= SEQUENCE { + supportedCamelPhases [0] SupportedCamelPhases OPTIONAL, + offeredCamel4Functionalities [1] OfferedCamel4Functionalities OPTIONAL, + extensions [2] Extensions {bound} OPTIONAL, + ..., + releaseCallArgExtensionAllowed [3] NULL OPTIONAL +} + +moveLeg {PARAMETERS-BOUND : bound} OPERATION ::= { + ARGUMENT MoveLegArg {bound} + RETURN RESULT TRUE + ERRORS {missingParameter | + systemFailure | + taskRefused | + unexpectedComponentSequence | + unexpectedDataValue | + unexpectedParameter | + unknownLegID} + CODE opcode-moveLeg + -- Direction: gsmSCF -> gsmSSF, Timer: Tml + -- This operation is used by the gsmSCF to move a leg from one call segment to another call segment + -- within the same call segment association. + +MoveLegArg {PARAMETERS-BOUND : bound} ::= SEQUENCE { + legIDToMove [0] LegID, + extensions [2] Extensions {bound} OPTIONAL, + ... +} + +playTone {PARAMETERS-BOUND : bound} OPERATION ::= { + ARGUMENT PlayToneArg {bound} + RETURN RESULT FALSE + ERRORS {missingParameter | + parameterOutOfRange | + systemFailure | + unexpectedComponentSequence | + unexpectedDataValue | + unexpectedParameter | + unknownLegID | + unknownCSID} + CODE opcode-playTone + -- Direction: gsmSCF -> gsmSSF, Timer: Tpt + -- This operation is used to play tones to either a leg or a call segment using + -- the MSC's tone generator. + +PlayToneArg {PARAMETERS-BOUND : bound} ::= SEQUENCE { + legOrCallSegment [0] LegOrCallSegment {bound}, + bursts [1] Burst, + extensions [2] Extensions {bound} OPTIONAL, + ... +} + +releaseCall {PARAMETERS-BOUND : bound} OPERATION ::= { + ARGUMENT ReleaseCallArg {bound} + RETURN RESULT FALSE + ALWAYS RESPONDS FALSE + CODE opcode-releaseCall + -- Direction: gsmSCF -> gsmSSF, Timer: Trc + -- This operation is used to tear down an existing call at any phase of the call for all parties + -- involved in the call. + +ReleaseCallArg {PARAMETERS-BOUND : bound} ::= CHOICE { + allCallSegments AllCallSegments, + allCallSegmentsWithExtension [2] AllCallSegmentsWithExtension +} + +``` + +``` + + } + +AllCallSegments ::= Cause {bound} +-- A default value of decimal 31 (normal unspecified) shall be given. + +AllCallSegmentsWithExtension ::= SEQUENCE { + allCallSegments [0] AllCallSegments, + extensions [1] Extensions {bound} OPTIONAL +} + +requestReportBCSMEvent {PARAMETERS-BOUND : bound} OPERATION ::= { + ARGUMENT RequestReportBCSMEventArg {bound} + RETURN RESULT FALSE + ERRORS {missingParameter | + parameterOutOfRange | + systemFailure | + taskRefused | + unexpectedComponentSequence | + unexpectedDataValue | + unexpectedParameter | + unknownLegID} + CODE opcode-requestReportBCSMEvent} +-- Direction: gsmSCF -> gsmSSF, Timer: Trrb +-- This operation is used to request the gsmSSF to monitor for a call-related event +-- (e.g. BCSM events such as O_Busy or O_No_Answer) and to send a notification +-- to the gsmSCF when the event is detected. +-- +-- NOTE: +-- Every EDP must be explicitly armed by the gsmSCF via a RequestReportBCSMEvent operation. +-- No implicit arming of EDPs at the gsmSSF after reception of any operation (different +-- from RequestReportBCSMEvent) from the gsmSCF is allowed. + +RequestReportBCSMEventArg {PARAMETERS-BOUND : bound} ::= SEQUENCE { + bcsmEvents [0] SEQUENCE SIZE(1..bound.&numOfBCSMEvents) OF + BCSMEvent {bound}, + extensions [2] Extensions {bound} OPTIONAL, + ... +} +-- Indicates the BCSM related events for notification. + +resetTimer {PARAMETERS-BOUND : bound} OPERATION ::= { + ARGUMENT ResetTimerArg {bound} + RETURN RESULT FALSE + ERRORS {missingParameter | + parameterOutOfRange | + taskRefused | + unexpectedComponentSequence | + unexpectedDataValue | + unexpectedParameter | + unknownCSID} + CODE opcode-resetTimer} +-- Direction: gsmSCF -> gsmSSF, Timer: Trt +-- This operation is used to request the gsmSSF to refresh an application timer in the gsmSSF. + +ResetTimerArg {PARAMETERS-BOUND : bound} ::= SEQUENCE { + timerID [0] TimerID DEFAULT tssf, + timerValue [1] TimerValue, + extensions [2] Extensions {bound} OPTIONAL, + callSegmentID [3] CallSegmentID {bound} OPTIONAL, + ... +} + +sendChargingInformation {PARAMETERS-BOUND : bound} OPERATION ::= { + ARGUMENT SendChargingInformationArg {bound} + RETURN RESULT FALSE + ERRORS {missingParameter | + unexpectedComponentSequence | + unexpectedParameter | + parameterOutOfRange | + systemFailure | + taskRefused | + unexpectedDataValue | + unknownLegID} + CODE opcode-sendChargingInformation} +-- Direction: gsmSCF -> gsmSSF, Timer: Tsci +-- This operation is used to instruct the gsmSSF on the charging information to send by the gsmSSF. +-- The charging information can either be sent back by means of signalling or internal +-- if the gsmSSF is located in the local exchange. In the local exchange + +``` + +-- this information may be used to update the charge meter or to create a standard call record. + +``` +SendChargingInformationArg {PARAMETERS-BOUND : bound} ::= SEQUENCE { + SCIBillingChargingCharacteristics [0] SCIBillingChargingCharacteristics {bound}, + partyToCharge [1] SendingSideID, + extensions [2] Extensions {bound} OPTIONAL, + ... +} +``` + +``` +splitLeg {PARAMETERS-BOUND : bound} OPERATION ::= { + ARGUMENT SplitLegArg {bound} + RETURN RESULT TRUE + ERRORS {missingParameter | + unexpectedComponentSequence | + unexpectedParameter | + unexpectedDataValue | + systemFailure | + taskRefused | + unknownLegID} + CODE opcode-splitLeg} +``` + +-- Direction: gsmSCF -> gsmSSF, Timer Tsl + +-- This operation is used by the gsmSCF to separate a leg from its source call segment and + +-- place it in a new call segment within the same call segment association. + +``` +SplitLegArg {PARAMETERS-BOUND : bound} ::= SEQUENCE { + legToBeSplit [0] LegID, + newCallSegment [1] CallSegmentID {bound} OPTIONAL, + extensions [2] Extensions {bound} OPTIONAL, + ... +} +``` + +END + +The following value ranges apply for operation specific timers in CAP: + +| | | +|---------|------------------| +| short: | 1 s - 10 s | +| medium: | 1 s - 60 s | +| long: | 1 s - 30 minutes | + +Table 6-1 lists all operation timers and the value range for each timer. The definitive value for each operation timer may be network specific and has to be defined by the network operator. + +Table 6-1: Timer value ranges + +| Operation Name | Timer | value range | +|-----------------------------------------|--------------------|-------------| +| ActivityTest | T at | Short | +| ApplyCharging | T ac | Short | +| ApplyChargingReport | T acr | Short | +| AssistRequestInstructions | T ari | Short | +| CollectInformation | T ci | Short | +| CallInformationReport | T cirp | Short | +| CallInformationRequest | T cirq | Short | +| Cancel | T can | Short | +| CallGap | T cg | Short | +| Connect | T con | Short | +| ConnectToResource | T ctr | Short | +| Continue | T cue | Short | +| ContinueWithArgument | T cwa | Short | +| DisconnectForwardConnectionWithArgument | T dfcwa | Short | +| DisconnectLeg | T dl | Short | +| EntityReleased | T er | Short | +| DisconnectForwardConnection | T dfc | Short | +| EstablishTemporaryConnection | T etc | Medium | +| EventReportBCSM | T erb | Short | +| FurnishChargingInformation | T fci | Short | +| InitialDP | T idp | Short | +| InitiateCallAttempt | T ica | Short | +| MoveLeg | T ml | Short | +| PlayTone | T pt | Short | +| ReleaseCall | T rc | Short | +| RequestReportBCSMEVENT | T rrb | Short | +| ResetTimer | T rt | Short | +| SendChargingInformation | T sci | Short | +| SplitLeg | T sl | Short | + +## 6.1.2 gsmSSF/gsmSCF packages, contracts and ACs + +### 6.1.2.1 gsmSSF/gsmSCF ASN.1 module + +``` +CAP-gsmSSF-gsmSCF-pkgs-contracts-ac { itu-t(0) identified-organization(4) etsi(0) mobileDomain(0) +umts-network(1) modules(3) cap-gsmSSF-gsmSCF-pkgs-contracts-ac(102) version8(7) } +``` + +``` +DEFINITIONS ::= BEGIN +``` + +``` +-- This module specifies the Operation Packages, Contracts, Application Contexts +-- and Abstract Syntaxes used for the gsmSSF - gsmSCF interface, for the control of +-- circuit switched calls. +``` + +``` +-- The table in subclause 2.1 lists the specifications that contain the modules +-- that are used by CAP. +``` + +``` +IMPORTS +``` + +``` + PARAMETERS-BOUND, + cAPSpecificBoundSet +FROM CAP-classes classes +-- Elements that exist in cAPSpecificBoundSet in Rel-5 are not changed in Rel-6. As a +-- result, the value range of data type definitions in Rel-5 are not changed in Rel-6. +``` + +``` +CONTRACT, +``` + +``` + + OPERATION-PACKAGE, + OPERATION +FROM Remote-Operations-Information-Objects ros-InformationObjects + + TCMessage {} +FROM TCAPMessages tc-Messages + + APPLICATION-CONTEXT, + dialogue-abstract-syntax +FROM TC-Notation-Extensions tc-NotationExtensions + + activityTest, + applyCharging {}, + applyChargingReport {}, + assistRequestInstructions {}, + callGap {}, + callInformationReport {}, + callInformationRequest {}, + cancel {}, + collectInformation {}, + connect {}, + connectToResource {}, + continue, + continueWithArgument {}, + disconnectForwardConnection, + disconnectForwardConnectionWithArgument {}, + disconnectLeg {}, + entityReleased {}, + establishTemporaryConnection {}, + eventReportBCSM {}, + furnishChargingInformation {}, + initialDP {}, + initiateCallAttempt {}, + moveLeg {}, + playTone {}, + releaseCall {}, + requestReportBCSMEVENT {}, + resetTimer {}, + sendChargingInformation {}, + splitLeg {} +FROM CAP-gsmSSF-gsmSCF-ops-args gsmSSF-gsmSCF-Operations +-- Object Identifier 'gsmSSF-gsmSCF-Operations' is updated to version8(7) in Rel-6. As +-- a result, the present module, 'CAP-gsmSSF-gsmSCF-pkgs-contracts-ac', IMPORTS CAP +-- Operation definitions from CAP-gsmSSF-gsmSCF-ops-args version8(7). Operation +-- definitions are used in the ABSTRACT SYNTAX definitions and in the OPERATION PACKAGE +-- definitions. + + playAnnouncement {}, + promptAndCollectUserInformation {}, + specializedResourceReport +FROM CAP-gsmSCF-gsmSRF-ops-args gsmSCF-gsmSRF-Operations-- Object Identifier 'gsmSCF-gsmSRF- +Operations' is updated to version8(7) in Rel-6. AS +-- a result, the present module, 'CAP-gsmSSF-gsmSCF-pkgs-contracts-ac', IMPORTS CAP +-- Operation definitions from CAP-gsmSCF-gsmSRF-ops-args version8(7). Operation +-- definitions are used in the ABSTRACT SYNTAX definitions and in the OPERATION PACKAGE +-- definitions. + + specializedResourceControlPackage {} +FROM CAP-gsmSCF-gsmSRF-pkgs-contracts-ac gsmSCF-gsmSRF-Protocol +-- Object Identifier 'gsmSCF-gsmSRF-Protocol' is updated to version8(7) in Rel-6. As a +-- result, the present module, 'CAP-gsmSSF-gsmSCF-pkgs-contracts-ac', IMPORTS CAP Operation +-- Package definitions from CAP-gsmSCF-gsmSRF-pkgs-contracts-ac version8(7). Operation +-- Package definitions are used in the CONTRACT definitions. + + id-ac-CAP-gsmSSF-scfGenericAC, + id-ac-CAP-gsmSSF-scfAssistHandoffAC, + id-ac-CAP-scf-gsmSSFGenericAC, +-- The APPLICATION-CONTEXT Identifiers for CAP V4 in Rel-6 are the same as for CAP V4 in Rel-5. + + id-CAPssfToScfGeneric, + id-CAPAssistHandoffssfToScf, + id-CAPScfToSsfGeneric, +-- The CONTRACT Identifiers for CAP V4 in Rel-6 are the same as for CAP V4 in Rel-5. + + id-as-gsmSSF-scfGenericAS, + id-as-scf-gsmSSFGenericAS, + id-as-assistHandoff-gsmSSF-scfAS, +-- The ABSTRACT-SYNTAX Identifiers for CAP V4 in Rel-6 are the same as for CAP V4 in Rel-5. + +``` + +``` + +id-package-scfActivation, +id-package-gsmSRF-scfActivationOfAssist, +id-package-assistConnectionEstablishment, +id-package-genericDisconnectResource, +id-package-nonAssistedConnectionEstablishment, +id-package-connect, +id-package-callHandling, +id-package-bcsmEventHandling, +id-package-ssfCallProcessing, +id-package-scfCallInitiation, +id-package-timer, +id-package-billing, +id-package-charging, +id-package-trafficManagement, +id-package-callReport, +id-package-signallingControl, +id-package-activityTest, +id-package-cancel, +id-package-cphResponse, +id-package-exceptionInform, +id-package-playTone, +-- The OPERATION-PACKAGE Identifiers for CAP V4 in Rel-6 are the same as for CAP V4 in Rel-5. + +classes, +ros-InformationObjects, +tc-Messages, +tc-NotationExtensions, + +gsmSSF-gsmSCF-Operations, +gsmSCF-gsmSRF-Operations, +-- Object Identifiers gsmSSF-gsmSCF-Operations and gsmSCF-gsmSRF-Operations are updated +-- to version8(7) in Rel-6. As a result, the present module, 'CAP-gsmSSF-gsmSCF-pkgs- +-- contracts-ac', IMPORTS Rel-6 versions of the CAP Operation definitions. + +gsmSCF-gsmSRF-Protocol +-- Object Identifier gsmSCF-gsmSRF-Protocol is updated to version8(7) in Rel-6. As a result, +-- the present module IMPORTS Rel-6 versions of the CAP Operation Package definitions. + +FROM CAP-object-identifiers {itu-t(0) identified-organization(4) etsi(0) mobileDomain(0) +umts-network(1) modules(3) cap-object-identifiers(100) version8(7)}; + +-- Application Contexts + +-- CAP V4 Rel-5 and CAP V4 Rel-6 use the same Application Context version. The CONTRACT +-- and ABSTRACT SYNTAXES for the call control related Application Contexts, however, are +-- defined in Rel-6. This is needed to use parameter definitions that are defined in Rel-6. + +-- Refer to ITU-T Recommendation Q.775 for the formal definition of APPLICATION-CONTEXT. +-- The structured DIALOGUE MODE is defined in ITU-T Recommendation Q.771; the +-- dialogue-abstract-syntax ABSTRACT SYNTAX is defined in ITU-T Recommendation Q.775. + +capsf-scfGenericAC APPLICATION-CONTEXT ::= { + CONTRACT capSsfToScfGeneric + DIALOGUE MODE structured + ABSTRACT SYNTAXES {dialogue-abstract-syntax | + gsmSSF-scfGenericAbstractSyntax} + APPLICATION CONTEXT NAME id-ac-CAP-gsmSSF-scfGenericAC} +-- 'capSsfToScfGeneric' and 'gsmSSF-scfGenericAbstractSyntax' are defined in the present +-- module. + +capsf-scfAssistHandoffAC APPLICATION-CONTEXT ::= { + CONTRACT capAssistHandoffssfToScf + DIALOGUE MODE structured + ABSTRACT SYNTAXES {dialogue-abstract-syntax | + assistHandoff-gsmSSF-scfAbstractSyntax} + APPLICATION CONTEXT NAME id-ac-CAP-gsmSSF-scfAssistHandoffAC} +-- 'capAssistHandoffssfToScf' and 'assistHandoff-gsmSSF-scfAbstractSyntax' are defined in +-- the present module. + +capsf-ssfGenericAC APPLICATION-CONTEXT ::= { + CONTRACT capScfToSsfGeneric + DIALOGUE MODE structured + ABSTRACT SYNTAXES {dialogue-abstract-syntax | + scf-gsmSSFGenericAbstractSyntax} + APPLICATION CONTEXT NAME id-ac-CAP-scf-gsmSSFGenericAC} +-- 'capScfToSsfGeneric' and 'scf-gsmSSFGenericAbstractSyntax' are defined in the present +-- module. + +``` + +``` + +-- Contracts +-- The CONTRACT definitions are updated for Rel-6, due to the fact that the individual +-- OPERATION-PACKAGE definitions are updated in Rel-6. + +capSsfToScfGeneric CONTRACT ::= { +-- dialogue initiated by gsmSSF with InitialDP Operation + INITIATOR CONSUMER OF {exceptionInformPackage {CAPSpecificBoundSet} | + scfActivationPackage {CAPSpecificBoundSet}} + RESPONDER CONSUMER OF {activityTestPackage | + assistConnectionEstablishmentPackage {CAPSpecificBoundSet} | + bcsmeventHandlingPackage {CAPSpecificBoundSet} | + billingPackage {CAPSpecificBoundSet} | + callHandlingPackage {CAPSpecificBoundSet} | + callReportPackage {CAPSpecificBoundSet} | + cancelPackage {CAPSpecificBoundSet} | + chargingPackage {CAPSpecificBoundSet} | + connectPackage {CAPSpecificBoundSet} | + cphResponsePackage {CAPSpecificBoundSet} | + genericDisconnectResourcePackage {CAPSpecificBoundSet} | + nonAssistedConnectionEstablishmentPackage {CAPSpecificBoundSet} | + playTonePackage {CAPSpecificBoundSet} | + signallingControlPackage {CAPSpecificBoundSet} | + specializedResourceControlPackage {CAPSpecificBoundSet} | + ssfCallProcessingPackage {CAPSpecificBoundSet} | + timerPackage {CAPSpecificBoundSet} | + trafficManagementPackage {CAPSpecificBoundSet} | + scfCallInitiationPackage {CAPSpecificBoundSet}} + ID id-CAPSSfToScfGeneric +-- The OPERATION-PACKAGES are defined in the present module, except for +-- specializedResourceControlPackage, which is defined in CAP-gsmSCF-gsmSRF-pkgs-contracts-ac. + +capAssistHandoffssfToScf CONTRACT ::= { +-- dialogue initiated by gsmSSF with AssistRequestInstructions + INITIATOR CONSUMER OF {gsmSRF-scfActivationOfAssistPackage {CAPSpecificBoundSet}} + RESPONDER CONSUMER OF {activityTestPackage | + cancelPackage {CAPSpecificBoundSet} | + genericDisconnectResourcePackage {CAPSpecificBoundSet} | + nonAssistedConnectionEstablishmentPackage {CAPSpecificBoundSet} | + specializedResourceControlPackage {CAPSpecificBoundSet} | + timerPackage {CAPSpecificBoundSet}} + ID id-CAPAssistHandoffssfToScf +-- The OPERATION-PACKAGES are defined in the present module, except for +-- specializedResourceControlPackage, which is defined in CAP-gsmSCF-gsmSRF-pkgs-contracts-ac. + +capScfToSsfGeneric CONTRACT ::= { +-- dialogue initiated by gsmSCF with InitiateCallAttempt, Generic Case + INITIATOR CONSUMER OF {activityTestPackage | + assistConnectionEstablishmentPackage {CAPSpecificBoundSet} | + bcsmeventHandlingPackage {CAPSpecificBoundSet} | + billingPackage {CAPSpecificBoundSet} | + callHandlingPackage {CAPSpecificBoundSet} | + callReportPackage {CAPSpecificBoundSet} | + cancelPackage {CAPSpecificBoundSet} | + chargingPackage {CAPSpecificBoundSet} | + connectPackage {CAPSpecificBoundSet} | + cphResponsePackage {CAPSpecificBoundSet} | + genericDisconnectResourcePackage {CAPSpecificBoundSet} | + nonAssistedConnectionEstablishmentPackage {CAPSpecificBoundSet} | + playTonePackage {CAPSpecificBoundSet} | + scfCallInitiationPackage {CAPSpecificBoundSet} | + specializedResourceControlPackage {CAPSpecificBoundSet} | + ssfCallProcessingPackage {CAPSpecificBoundSet} | + timerPackage {CAPSpecificBoundSet}} + RESPONDER CONSUMER OF {exceptionInformPackage {CAPSpecificBoundSet}} + ID id-CAPScfToSsfGeneric +-- The OPERATION-PACKAGES are defined in the present module, except for +-- specializedResourceControlPackage, which is defined in CAP-gsmSCF-gsmSRF-pkgs-contracts-ac. + +-- Operation Packages +-- The OPERATION-PACKAGE definitions are updated for Rel-6, due to the fact that the individual +-- OPERATION definitions are updated in Rel-6. The OPERATION definitions are IMPORTED from +-- CAP-gsmSSF-gsmSCF-ops-args and from CAP-gsmSCF-gsmSRF-ops-args. + +scfActivationPackage {PARAMETERS-BOUND : bound} OPERATION-PACKAGE ::= { + CONSUMER INVOKE {initialDP {bound}} + ID id-package-scfActivation} + +``` + +``` +gsmSRF-scfActivationOfAssistPackage {PARAMETERS-BOUND : bound} OPERATION-PACKAGE ::= { + CONSUMER INVOKES {assistRequestInstructions {bound}} + ID id-package-gsmSRF-scfActivationOfAssist} + +assistConnectionEstablishmentPackage {PARAMETERS-BOUND : bound} OPERATION-PACKAGE ::= { + CONSUMER INVOKES {establishTemporaryConnection {bound}} + ID id-package-assistConnectionEstablishment} + +genericDisconnectResourcePackage {PARAMETERS-BOUND : bound} OPERATION-PACKAGE ::= { + CONSUMER INVOKES {disconnectForwardConnection | + disconnectForwardConnectionWithArgument {bound}} + ID id-package-genericDisconnectResource} + +nonAssistedConnectionEstablishmentPackage {PARAMETERS-BOUND : bound} OPERATION-PACKAGE ::= { + CONSUMER INVOKES {connectToResource {bound}} + ID id-package-nonAssistedConnectionEstablishment} + +connectPackage {PARAMETERS-BOUND : bound} OPERATION-PACKAGE ::= { + CONSUMER INVOKES {connect {bound}} + ID id-package-connect} + +callHandlingPackage {PARAMETERS-BOUND : bound} OPERATION-PACKAGE ::= { + CONSUMER INVOKES {releaseCall {bound}} + ID id-package-callHandling} + +bcsmEventHandlingPackage {PARAMETERS-BOUND : bound} OPERATION-PACKAGE ::= { + CONSUMER INVOKES {requestReportBCSMEVENT {bound}} + SUPPLIER INVOKES {eventReportBCSM {bound}} + ID id-package-bcsmEventHandling} + +ssfCallProcessingPackage {PARAMETERS-BOUND : bound} OPERATION-PACKAGE ::= { + CONSUMER INVOKES {collectInformation | continueWithArgument {bound} | continue} + ID id-package-ssfCallProcessing} + +scfCallInitiationPackage {PARAMETERS-BOUND : bound} OPERATION-PACKAGE ::= { + CONSUMER INVOKES {initiateCallAttempt {bound}} + ID id-package-scfCallInitiation} + +timerPackage {PARAMETERS-BOUND : bound} OPERATION-PACKAGE ::= { + CONSUMER INVOKES {resetTimer {bound}} + ID id-package-timer} + +billingPackage {PARAMETERS-BOUND : bound} OPERATION-PACKAGE ::= { + CONSUMER INVOKES {furnishChargingInformation {bound}} + ID id-package-billing} + +chargingPackage {PARAMETERS-BOUND : bound} OPERATION-PACKAGE ::= { + CONSUMER INVOKES {applyCharging {bound}} + SUPPLIER INVOKES {applyChargingReport {bound}} + ID id-package-charging} + +trafficManagementPackage {PARAMETERS-BOUND : bound} OPERATION-PACKAGE ::= { + CONSUMER INVOKES {callGap {bound}} + ID id-package-trafficManagement} + +callReportPackage {PARAMETERS-BOUND : bound} OPERATION-PACKAGE ::= { + CONSUMER INVOKES {callInformationRequest {bound}} + SUPPLIER INVOKES {callInformationReport {bound}} + ID id-package-callReport} + +signallingControlPackage {PARAMETERS-BOUND : bound} OPERATION-PACKAGE ::= { + CONSUMER INVOKES {sendChargingInformation {bound}} + ID id-package-signallingControl} + +activityTestPackage OPERATION-PACKAGE ::= { + CONSUMER INVOKES {activityTest} + ID id-package-activityTest} + +cancelPackage {PARAMETERS-BOUND : bound} OPERATION-PACKAGE ::= { + CONSUMER INVOKES {cancel {bound}} + ID id-package-cancel} + +cphResponsePackage {PARAMETERS-BOUND : bound} OPERATION-PACKAGE ::= { + CONSUMER INVOKES {continueWithArgument {bound} | + disconnectLeg {bound} | + moveLeg {bound} | + splitLeg {bound}} + ID id-package-cphResponse} +``` + +``` + +exceptionInformPackage {PARAMETERS-BOUND : bound} OPERATION-PACKAGE ::= { + CONSUMER INVOKES {entityReleased {bound}} + ID id-package-exceptionInform} + +playTonePackage {PARAMETERS-BOUND : bound} OPERATION-PACKAGE ::= { + CONSUMER INVOKES {playTone {bound}} + ID id-package-playTone} + +-- Abstract Syntaxes + +-- SsfToScfGenericInvokable and SsfToScfGenericReturnable use OPERATION definitions with +-- version8(7). As a result, GenericSSF-gsmSCF-PDUs uses version8(7) OPERATION definitions. +-- As a subsequent result, gsmSSF-scfGenericAbstractSyntax uses version8(7) OPERATION +-- definitions. That ABSTRACT-SYNTAX is used in the capssf-scfGenericAC APPLICATION-CONTEXT +-- definition (CAP from gsmSSF to gsmSCF). + +gsmSSF-scfGenericAbstractSyntax ABSTRACT-SYNTAX ::= { + GenericSSF-gsmSCF-PDUs + IDENTIFIED BY id-as-gsmSSF-scfGenericAS} +-- 'GenericSSF-gsmSCF-PDUs' is defined in the present module. + +GenericSSF-gsmSCF-PDUs ::= TCMessage {{SsfToScfGenericInvokable}, + {SsfToScfGenericReturnable}} +-- 'SsfToScfGenericInvokable' and 'SsfToScfGenericReturnable' are defined in the present module. + +SsfToScfGenericInvokable OPERATION ::= { + activityTest | + applyCharging {cAPSpecificBoundSet} | + applyChargingReport {cAPSpecificBoundSet} | + callInformationReport {cAPSpecificBoundSet} | + callInformationRequest {cAPSpecificBoundSet} | + cancel {cAPSpecificBoundSet} | + connect {cAPSpecificBoundSet} | + continueWithArgument {cAPSpecificBoundSet} | + connectToResource {cAPSpecificBoundSet} | + collectInformation | + disconnectForwardConnection | + disconnectForwardConnectionWithArgument {cAPSpecificBoundSet} | + disconnectLeg {cAPSpecificBoundSet} | + entityReleased {cAPSpecificBoundSet} | + establishTemporaryConnection {cAPSpecificBoundSet} | + eventReportBCSM {cAPSpecificBoundSet} | + furnishChargingInformation {cAPSpecificBoundSet} | + initialDP {cAPSpecificBoundSet} | + initiateCallAttempt {cAPSpecificBoundSet} | + moveLeg {cAPSpecificBoundSet} | + releaseCall {cAPSpecificBoundSet} | + requestReportBCSMEVENT {cAPSpecificBoundSet} | + resetTimer {cAPSpecificBoundSet} | + sendChargingInformation {cAPSpecificBoundSet} | + splitLeg {cAPSpecificBoundSet} | + playAnnouncement {cAPSpecificBoundSet} | + playTone {cAPSpecificBoundSet} | + promptAndCollectUserInfo {cAPSpecificBoundSet} | + specializedResourceReport +} +-- The OPERATION definitions are IMPORTED from CAP-gsmSSF-gsmSCF-ops-args and from +-- CAP-gsmSCF-gsmSRF-ops-args. + +SsfToScfGenericReturnable OPERATION ::= { + activityTest | + applyCharging {cAPSpecificBoundSet} | + applyChargingReport {cAPSpecificBoundSet} | + callGap {cAPSpecificBoundSet} | + callInformationRequest {cAPSpecificBoundSet} | + cancel {cAPSpecificBoundSet} | + connect {cAPSpecificBoundSet} | + connectToResource {cAPSpecificBoundSet} | + collectInformation | + continue | + continueWithArgument {cAPSpecificBoundSet} | + disconnectForwardConnection | + disconnectForwardConnectionWithArgument {cAPSpecificBoundSet} | + disconnectLeg {cAPSpecificBoundSet} | + entityReleased {cAPSpecificBoundSet} | + establishTemporaryConnection {cAPSpecificBoundSet} | +} + +``` + +``` + + furnishChargingInformation {cAPSSpecificBoundSet} | + initialDP {cAPSSpecificBoundSet} | + initiateCallAttempt {cAPSSpecificBoundSet} | + moveLeg {cAPSSpecificBoundSet} | + releaseCall {cAPSSpecificBoundSet} | + requestReportBCSMEvent {cAPSSpecificBoundSet} | + resetTimer {cAPSSpecificBoundSet} | + sendChargingInformation {cAPSSpecificBoundSet} | + splitLeg {cAPSSpecificBoundSet} | + playAnnouncement {cAPSSpecificBoundSet} | + playTone {cAPSSpecificBoundSet} | + promptAndCollectUserInformation {cAPSSpecificBoundSet} + } +-- The OPERATION definitions are IMPORTED from CAP-gsmSSF-gsmSCF-ops-args and from +-- CAP-gsmSCF-gsmSRF-ops-args. + +-- AssistHandoffssfToScfInvokable and AssistHandoffssfToScfReturnable use OPERATION definitions +-- with version8(7). As a result, AssistHandoffssf-gsmSCF-PDUs uses version8(7) OPERATION +-- definitions. As a subsequent result, assistHandoff-gsmSSF-scfAbstractSyntax uses version8(7) +-- OPERATION definitions. That ABSTRACT-SYNTAX is used in the capssf-scfAssistHandoffAC +-- APPLICATION-CONTEXT definition (CAP from assist gsmSSF to gsmSCF). + +assistHandoff-gsmSSF-scfAbstractSyntax ABSTRACT-SYNTAX ::= { + AssistHandoffssf-gsmSCF-PDUs + IDENTIFIED BY id-as-assistHandoff-gsmSSF-scfAS} +-- 'AssistHandoffssf-gsmSCF-PDUs' is defined in the present module. + +AssistHandoffssf-gsmSCF-PDUs ::= TCMessage {{AssistHandoffssfToScfInvokable}, + {AssistHandoffssfToScfReturnable}} +-- 'AssistHandoffssfToScfInvokable' and 'AssistHandoffssfToScfReturnable' are defined in the +-- present module. + +AssistHandoffssfToScfInvokable OPERATION ::= { + activityTest | + assistRequestInstructions {cAPSSpecificBoundSet} | + cancel {cAPSSpecificBoundSet} | + connectToResource {cAPSSpecificBoundSet} | + disconnectForwardConnection | + playAnnouncement {cAPSSpecificBoundSet} | + promptAndCollectUserInformation {cAPSSpecificBoundSet} | + resetTimer {cAPSSpecificBoundSet} | + specializedResourceReport + } +-- The OPERATION definitions are IMPORTED from CAP-gsmSSF-gsmSCF-ops-args and from +-- CAP-gsmSCF-gsmSRF-ops-args. + +AssistHandoffssfToScfReturnable OPERATION ::= { + activityTest | + assistRequestInstructions {cAPSSpecificBoundSet} | + cancel {cAPSSpecificBoundSet} | + connectToResource {cAPSSpecificBoundSet} | + disconnectForwardConnection | + playAnnouncement {cAPSSpecificBoundSet} | + promptAndCollectUserInformation {cAPSSpecificBoundSet} | + resetTimer {cAPSSpecificBoundSet} + } +-- The OPERATION definitions are IMPORTED from CAP-gsmSSF-gsmSCF-ops-args and from +-- CAP-gsmSCF-gsmSRF-ops-args. + +-- ScfToSsfGenericInvokable and ScfToSsfGenericReturnable use OPERATION definitions +-- with version8(7). As a result, GenericSCF-gsmSSF-PDUs uses version8(7) OPERATION +-- definitions. As a subsequent result, scf-gsmSSFGenericAbstractSyntax uses version8(7) +-- OPERATION definitions. That ABSTRACT-SYNTAX is used in the capscf-ssfGenericAC +-- APPLICATION-CONTEXT definition (CAP from gsmSCF to gsmSSF). + +scf-gsmSSFGenericAbstractSyntax ABSTRACT-SYNTAX ::= { + GenericSCF-gsmSSF-PDUs + IDENTIFIED BY id-as-scf-gsmSSFGenericAS} +-- 'GenericSCF-gsmSSF-PDUs' is defined in the present module. + +GenericSCF-gsmSSF-PDUs ::= TCMessage {{ScfToSsfGenericInvokable}, + {ScfToSsfGenericReturnable}} +-- 'ScfToSsfGenericInvokable' and 'ScfToSsfGenericReturnable' are defined in the +-- present module. + +ScfToSsfGenericInvokable OPERATION ::= { + activityTest | + applyCharging {cAPSSpecificBoundSet} | +``` + +``` + + applyChargingReport {cAPSpecificBoundSet} | + callInformationRequest {cAPSpecificBoundSet} | + cancel {cAPSpecificBoundSet} | + collectInformation | + connect {cAPSpecificBoundSet} | + connectToResource {cAPSpecificBoundSet} | + continue | + continueWithArgument {cAPSpecificBoundSet} | + disconnectForwardConnection | + disconnectForwardConnectionWithArgument {cAPSpecificBoundSet} | + disconnectLeg {cAPSpecificBoundSet} | + establishTemporaryConnection {cAPSpecificBoundSet} | + furnishChargingInformation {cAPSpecificBoundSet} | + initiateCallAttempt {cAPSpecificBoundSet} | + moveLeg {cAPSpecificBoundSet} | + playTone {cAPSpecificBoundSet} | + releaseCall {cAPSpecificBoundSet} | + requestReportBCSMEVENT {cAPSpecificBoundSet} | + resetTimer {cAPSpecificBoundSet} | + sendChargingInformation {cAPSpecificBoundSet} | + splitLeg {cAPSpecificBoundSet} | + playAnnouncement {cAPSpecificBoundSet} | + promptAndCollectUserInfo {cAPSpecificBoundSet} + } +-- The OPERATION definitions are IMPORTED from CAP-gsmSSF-gsmSCF-ops-args and from +-- CAP-gsmSCF-gsmSRF-ops-args. + +ScfToSsfGenericReturnable OPERATION ::= { + activityTest | + applyCharging {cAPSpecificBoundSet} | + applyChargingReport {cAPSpecificBoundSet} | + callInformationReport {cAPSpecificBoundSet} | + callInformationRequest {cAPSpecificBoundSet} | + cancel {cAPSpecificBoundSet} | + connect {cAPSpecificBoundSet} | + connectToResource {cAPSpecificBoundSet} | + disconnectForwardConnection | + disconnectForwardConnectionWithArgument {cAPSpecificBoundSet} | + disconnectLeg {cAPSpecificBoundSet} | + entityReleased {cAPSpecificBoundSet} | + establishTemporaryConnection {cAPSpecificBoundSet} | + eventReportBCSM {cAPSpecificBoundSet} | + furnishChargingInformation {cAPSpecificBoundSet} | + initiateCallAttempt {cAPSpecificBoundSet} | + moveLeg {cAPSpecificBoundSet} | + requestReportBCSMEVENT {cAPSpecificBoundSet} | + resetTimer {cAPSpecificBoundSet} | + sendChargingInformation {cAPSpecificBoundSet} | + splitLeg {cAPSpecificBoundSet} | + playAnnouncement {cAPSpecificBoundSet} | + playTone {cAPSpecificBoundSet} | + promptAndCollectUserInfo {cAPSpecificBoundSet} | + specializedResourceReport +} +-- The OPERATION definitions are IMPORTED from CAP-gsmSSF-gsmSCF-ops-args and from +-- CAP-gsmSCF-gsmSRF-ops-args. + +END + +``` + +## 6.2 gsmSCF/gsmSRF interface + +### 6.2.1 gsmSCF/gsmSRF operations and arguments + +``` + +CAP-gsmSCF-gsmSRF-ops-args {itu-t(0) identified-organization(4) etsi(0) mobileDomain(0) +umts-network(1) modules(3) cap-gsmSCF-gsmSRF-ops-args(103) version8(7)} + +``` + +``` + +DEFINITIONS IMPLICIT TAGS ::= BEGIN + +``` + +``` + +-- This module contains the operations and operation arguments used for the +-- gsmSRF - gsmSCF interface, for the control of circuit switched calls. + +-- The table in subclause 2.1 lists the specifications that contain the modules +-- that are used by CAP. + +``` + +``` + +IMPORTS + +``` + +``` + + OPERATION +FROM Remote-Operations-Information-Objects ros-InformationObjects + + opcode-playAnnouncement, + opcode-promptAndCollectUserInfo, + opcode-specializedResourceReport +FROM CAP-operationcodes operationcodes +-- The CAP Operation identifiers for CAP V4 in Rel-6 are the same as the CAP Operation +-- identifiers for CAP V4 in Rel-5. + + CallSegmentID {}, + CollectedInfo, + Digits {}, + Extensions {}, + InformationToSend {} +FROM CAP-datatypes datatypes +-- For Rel-6, the CAP-datatypes module is updated to version8(7); Object Identifier 'datatypes' +-- is also updated to version8(7). As a result, the present module uses Rel-6 data type definitions. + + canceled, + improperCallerResponse, + missingParameter, + parameterOutOfRange, + systemFailure, + taskRefused, + unavailableResource, + unexpectedComponentSequence, + unexpectedDataValue, + unexpectedParameter, + unknownCSID +FROM CAP-errortypes errortypes +-- For Rel-6, the CAP-errortypes module is updated to version8(7); Object Identifier +-- 'errortypes' is also updated to version8(7). As a result, the present module uses Rel-6 +-- error type definitions. + + PARAMETERS-BOUND +FROM CAP-classes classes + + ros-InformationObjects, + operationcodes, + datatypes, + errortypes, + classes +FROM CAP-object-identifiers {itu-t(0) identified-organization(4) etsi(0) mobileDomain(0) +umts-network(1) modules(3) cap-object-identifiers(100) version8(7)} + +; + +playAnnouncement {PARAMETERS-BOUND : bound} OPERATION ::= { + ARGUMENT PlayAnnouncementArg {bound} + RETURN RESULT FALSE + ERRORS {canceled | + missingParameter | + parameterOutOfRange | + systemFailure | + taskRefused | + unexpectedComponentSequence | + unexpectedDataValue | + unexpectedParameter | + unavailableResource | + unknownCSID} + LINKED {specializedResourceReport} + CODE opcode-playAnnouncement} +-- Direction: gsmSCF -> gsmSRF, Timer: Tpa +-- This operation is to be used after Establish Temporary Connection (assist procedure +-- with a second gsmSSF) or a Connect to Resource (no assist) operation. It may be used +-- for inband interaction with a mobile station, or for interaction with an ISDN user. +-- In the former case, the gsmSRF is usually collocated with the gsmSSF for standard +-- tones (congestion tone...) or standard announcements. +-- In the latter case, the gsmSRF is always collocated with the gsmSSF in the switch. +-- Any error is returned to the gsmSCF. The timer associated with this operation must +-- be of a sufficient duration to allow its linked operation to be correctly correlated. + +PlayAnnouncementArg {PARAMETERS-BOUND : bound} ::= SEQUENCE { + informationToSend [0] InformationToSend {bound}, + disconnectFromIPForbidden [1] BOOLEAN DEFAULT TRUE, + requestAnnouncementCompleteNotification [2] BOOLEAN DEFAULT TRUE, +} + +``` + +``` + + extensions [3] Extensions {bound} OPTIONAL, + callSegmentID [5] CallSegmentID {bound} OPTIONAL, + requestAnnouncementStartedNotification [51] BOOLEAN DEFAULT FALSE, + ... +} + +promptAndCollectUserInformation {PARAMETERS-BOUND : bound} OPERATION ::= { + ARGUMENT PromptAndCollectUserInformationArg {bound} + RESULT ReceivedInformationArg {bound} + ERRORS {canceled | + improperCallerResponse | + missingParameter | + parameterOutOfRange | + systemFailure | + taskRefused | + unexpectedComponentSequence | + unavailableResource | + unexpectedDataValue | + unexpectedParameter | + unknownCSID} + LINKED {specializedResourceReport} + CODE opcode-promptAndCollectUserInformation} +-- Direction: gsmSCF -> gsmSRF, Timer: Tpc +-- This operation is used to interact with a user to collect information. + +PromptAndCollectUserInformationArg {PARAMETERS-BOUND : bound} ::= SEQUENCE { + collectedInfo [0] CollectedInfo, + disconnectFromIPForbidden [1] BOOLEAN DEFAULT TRUE, + informationToSend [2] InformationToSend {bound} OPTIONAL, + extensions [3] Extensions {bound} OPTIONAL, + callSegmentID [4] CallSegmentID {bound} OPTIONAL, + requestAnnouncementStartedNotification [51] BOOLEAN DEFAULT FALSE, + ... +} + +ReceivedInformationArg {PARAMETERS-BOUND : bound} ::= CHOICE { + digitsResponse [0] Digits {bound} +} + +specializedResourceReport OPERATION ::= { + ARGUMENT SpecializedResourceReportArg + RETURN RESULT FALSE + ALWAYS RESPONDS FALSE + CODE opcode-specializedResourceReport} +-- Direction: gsmSRF -> gsmSCF, Timer: Tsrr +-- This operation is used as the response to a PlayAnnouncement operation when the announcement +-- completed report indication is set. + +SpecializedResourceReportArg ::= CHOICE { + allAnnouncementsComplete [50] NULL, + firstAnnouncementStarted [51] NULL +} + +END + +``` + +The following value ranges apply for operation specific timers in CAP: + +| | | +|---------|------------------| +| short: | 1 s - 10 s | +| medium: | 1 s - 60 s | +| long: | 1 s - 30 minutes | + +Table 6-2 lists all operation timers and the value range for each timer. The definitive value for each operation timer may be network specific and has to be defined by the network operator. + +**Table 6-2: Operation timers and their value range** + +| Operation Name | Timer | Value range | +|---------------------------------|------------------|-------------| +| PlayAnnouncement | T pa | Long | +| PromptAndCollectUserInformation | T pc | Long | +| SpecializedResourceReport | T srr | Short | + +## 6.2.2 gsmSRF/gsmSCF contracts, packages and ACs + +### 6.2.2.1 gsmSRF/gsmSCF ASN.1 modules + +CAP-gsmSCF-gsmSRF-pkgs-contracts-ac {itu-t(0) identified-organization(4) etsi(0) mobileDomain(0) umts-network(1) modules(3) cap-gsmSCF-gsmSRF-pkgs-contracts-ac(104) version8(7)} + +DEFINITIONS ::= BEGIN + +-- This module specifies the Operation Packages, Contracts, Application Contexts +-- and Abstract Syntaxes used for the gsmSRF – gsmSCF interface, for the control of +-- circuit switched calls. + +-- The table in subclause 2.1 lists the specifications that contain the modules +-- that are used by CAP. + +IMPORTS + +PARAMETERS-BOUND, +cAPSpecificBoundSet + +FROM CAP-classes classes + +-- Elements that exist in cAPSpecificBoundSet in Rel-5 are not changed in Rel-6. As a +-- result, the value range of data type definitions in Rel-5 are not changed in Rel-6. + +CONTRACT, +OPERATION-PACKAGE, +OPERATION + +FROM Remote-Operations-Information-Objects ros-InformationObjects + +TCMessage {} + +FROM TCAPMessages tc-Messages + +APPLICATION-CONTEXT, +dialogue-abstract-syntax + +FROM TC-Notation-Extensions tc-NotationExtensions + +playAnnouncement {}, +promptAndCollectUserInfo {}, +specializedResourceReport + +FROM CAP-gsmSCF-gsmSRF-ops-args gsmSCF-gsmSRF-Operations-- Object Identifier 'gsmSCF-gsmSRF-Operations' is updated to version8(7) in Rel-6. As + +-- a result, the present module, 'CAP-gsmSCF-gsmSRF-pkgs-contracts-ac', IMPORTS CAP +-- Operation definitions from CAP-gsmSCF-gsmSRF-ops-args version8(7). Operation +-- definitions are used in the ABSTRACT SYNTAX definitions and in the OPERATION PACKAGE +-- definitions. + +activityTest, +cancel {}, +assistRequestInstructions {} + +FROM CAP-gsmSSF-gsmSCF-ops-args gsmSSF-gsmSCF-Operations + +-- Object Identifier 'gsmSSF-gsmSCF-Operations' is updated to version8(7) in Rel-6. AS +-- a result, the present module, 'CAP-gsmSCF-gsmSRF-pkgs-contracts-ac', IMPORTS CAP +-- Operation definitions from CAP-gsmSSF-gsmSCF-ops-args version8(7). Operation +-- definitions are used in the ABSTRACT SYNTAX definitions and in the OPERATION PACKAGE +-- definitions. + +gsmSRF-scfActivationOfAssistPackage {} + +FROM CAP-gsmSSF-gsmSCF-pkgs-contracts-ac gsmSSF-gsmSCF-Protocol + +-- Object Identifier 'gsmSSF-gsmSCF-Protocol' is updated to version8(7) in Rel-6. As a +-- result, the present module, 'CAP-gsmSCF-gsmSRF-pkgs-contracts-ac', IMPORTS CAP Operation +-- Package definitions from CAP-gsmSSF-gsmSCF-pkgs-contracts-ac version8(7). Operation +-- Package definitions are used in the CONTRACT definitions. + +id-package-specializedResourceControl, +id-package-activityTest, +id-package-gsmSRF-scfCancel, + +``` + +-- The OPERATION-PACKAGE Identifiers for CAP V4 in Rel-6 are the same as for CAP V4 in Rel-5. + + id-ac-gsmSRF-gsmSCF, +-- The APPLICATION-CONTEXT Identifiers for CAP V4 in Rel-6 are the same as for CAP V4 in Rel-5. + + id-contract-gsmSRF-gsmSCF, +-- The CONTRACT Identifiers for CAP V4 in Rel-6 are the same as for CAP V4 in Rel-5. + + id-as-basic-gsmSRF-gsmSCF, +-- The ABSTRACT-SYNTAX Identifiers for CAP V4 in Rel-6 are the same as for CAP V4 in Rel-5. + + classes, + ros-InformationObjects, + tc-Messages, + tc-NotationExtensions, + + gsmSCF-gsmSRF-Operations, + gsmSSF-gsmSCF-Operations, +-- Object Identifiers gsmSSF-gsmSCF-Operations and gsmSCF-gsmSRF-Operations are updated +-- to version8(7) in Rel-6. As a result, the present module, 'CAP-gsmSCF-gsmSRF-pkgs- +-- contracts-ac', IMPORTS Rel-6 versions of the CAP Operation definitions. + + gsmSSF-gsmSCF-Protocol +-- Object Identifier gsmSSF-gsmSCF-Protocol is updated to version8(7) in Rel-6. As a result, +-- the present module IMPORTS Rel-6 versions of the CAP Operation Package definitions. + +``` + +``` + +FROM CAP-object-identifiers {itu-t(0) identified-organization(4) etsi(0) mobileDomain(0) +umts-network(1) modules(3) cap-object-identifiers(100) version8(7)}; + +``` + +#### -- Application Contexts + +``` + +-- CAP V4 Rel-5 and CAP V4 Rel-6 use the same Application Context version. The CONTRACT +-- and ABSTRACT SYNTAXES for the call control related Application Contexts, however, are +-- defined in Rel-6. This is needed to use parameter definitions that are defined in Rel-6. + +-- Refer to ITU-T Recommendation Q.775 for the formal definition of APPLICATION-CONTEXT. +-- The structured DIALOGUE MODE is defined in ITU-T Recommendation Q.771; the +-- dialogue-abstract-syntax ABSTRACT SYNTAX is defined in ITU-T Recommendation Q.775. + +``` + +``` + +gsmSRF-gsmSCF-ac APPLICATION-CONTEXT ::= { + +``` + +``` + + CONTRACT gsmSRF-gsmSCF-contract + DIALOGUE MODE structured + TERMINATION basic + ABSTRACT SYNTAXES {dialogue-abstract-syntax | + gsmSRF-gsmSCF-abstract-syntax} + APPLICATION CONTEXT NAME id-ac-gsmSRF-gsmSCF} + +``` + +``` + +-- 'gsmSRF-gsmSCF-contract' and 'gsmSRF-gsmSCF-abstract-syntax' are defined in the present +-- module. + +``` + +#### -- Contracts + +``` + +-- The CONTRACT definitions are updated for Rel-6, due to the fact that the individual +-- OPERATION-PACKAGE definitions are updated in Rel-6. + +``` + +``` + +gsmSRF-gsmSCF-contract CONTRACT ::= { + +``` + +``` + + INITIATOR CONSUMER OF {gsmSRF-scfActivationOfAssistPackage {cAPSpecificBoundSet}} + RESPONDER CONSUMER OF {specializedResourceControlPackage {cAPSpecificBoundSet} | + activityTestPackage | + gsmSRF-scfCancelPackage {cAPSpecificBoundSet} } + ID id-contract-gsmSRF-gsmSCF} + +``` + +``` + +-- The OPERATION-PACKAGES are defined in the present module, except for +-- gsmSRF-scfActivationOfAssistPackage, which is defined in CAP-gsmSSF-gsmSCF-pkgs-contracts-ac. + +``` + +#### -- Operation Packages + +``` + +-- The OPERATION-PACKAGE definitions are updated for Rel-6, due to the fact that the individual +-- OPERATION definitions are updated in Rel-6. The OPERATION definitions are IMPORTED from +-- CAP-gsmSSF-gsmSCF-ops-args and from CAP-gsmSCF-gsmSRF-ops-args. + +``` + +``` + +specializedResourceControlPackage {PARAMETERS-BOUND : bound} OPERATION-PACKAGE ::= { + CONSUMER INVOKE {playAnnouncement {bound} | + +``` + +``` + + promptAndCollectUserInformation {bound} +SUPPLIER INVOKE {specializedResourceReport} +ID id-package-specializedResourceControl} + +gsmSRF-scfCancelPackage {PARAMETERS-BOUND : bound} OPERATION-PACKAGE ::= { + CONSUMER INVOKE {cancel {bound}} + ID id-package-gsmSRF-scfCancel} + +activityTestPackage OPERATION-PACKAGE ::= { + CONSUMER INVOKE {activityTest} + ID id-package-activityTest} + +-- Abstract Syntaxes + +-- GsmSRFgsmSCFInvokable and GsmSRFgsmSCFReturnable use OPERATION definitions with +-- version8(7). As a result, BASIC-gsmSRF-gsmSCF-PDUs uses version8(7) OPERATION definitions. +-- As a subsequent result, gsmSRF-gsmSCF-abstract-syntax uses version8(7) OPERATION +-- definitions. That ABSTRACT-SYNTAX is used in the gsmSRF-gsmSCF-ac APPLICATION-CONTEXT +-- definition (CAP from gsmSRF to gsmSCF). + +gsmSRF-gsmSCF-abstract-syntax ABSTRACT-SYNTAX ::= { + BASIC-gsmSRF-gsmSCF-PDUs + IDENTIFIED BY id-as-basic-gsmSRF-gsmSCF} +-- 'BASIC-gsmSRF-gsmSCF-PDUs' is defined in the present module. + +BASIC-gsmSRF-gsmSCF-PDUs ::= TCMessage {{GsmSRFgsmSCFInvokable}, + {GsmSRFgsmSCFReturnable}} +-- 'GsmSRFgsmSCFInvokable' and 'GsmSRFgsmSCFReturnable' are defined in the present module. + +GsmSRFgsmSCFInvokable OPERATION ::= { + activityTest | + assistRequestInstructions {CAPSpecificBoundSet} | + cancel {CAPSpecificBoundSet} | + playAnnouncement {CAPSpecificBoundSet} | + promptAndCollectUserInformation {CAPSpecificBoundSet} | + specializedResourceReport +} +-- The OPERATION definitions are IMPORTED from CAP-gsmSSF-gsmSCF-ops-args and from +-- CAP-gsmSCF-gsmSRF-ops-args. + +GsmSRFgsmSCFReturnable OPERATION ::= { + activityTest | + assistRequestInstructions {CAPSpecificBoundSet} | + cancel {CAPSpecificBoundSet} | + playAnnouncement {CAPSpecificBoundSet} | + promptAndCollectUserInformation {CAPSpecificBoundSet} +} +-- The OPERATION definitions are IMPORTED from CAP-gsmSSF-gsmSCF-ops-args and from +-- CAP-gsmSCF-gsmSRF-ops-args. + +END + +``` + +## 7 SMS Control + +This clause defines the protocol used for CAMEL control of MO SMS and MT SMS. CAMEL control of MO SMS uses version 3 of the application context, and CAMEL control of MT SMS uses version 4 of the application context. + +### 7.1 SMS operations and arguments + +``` + +CAP-SMS-ops-args {itu-t(0) identified-organization(4) etsi(0) mobileDomain(0) umts-network(1) +modules(3) cap-SMS-ops-args(105) version8(7)} +-- The module CAP-SMS-ops-args is updated to version8(7) for Rel-6. The OPERATION definitions +-- are not modified. + +``` + +``` +DEFINITIONS IMPLICIT TAGS::= BEGIN + +-- This module contains the operations and operation arguments used for the +-- smsSSSF- gsmSCF interface, for the control of MO-SMS and MT-SMS. + +-- The table in subclause 2.1 lists the specifications that contain the modules +-- that are used by CAP. + +IMPORTS + + errortypes, + datatypes, + operationcodes, + classes, + ros-InformationObjects, + tc-Messages +FROM CAP-object-identifiers {itu-t(0) identified-organization(4) etsi(0) mobileDomain(0) +umts-network(1) modules(3) cap-object-identifiers(100) version8(7)} + + OPERATION +FROM Remote-Operations-Information-Objects ros-InformationObjects + + ServiceKey +FROM CS1-DataTypes {itu-t(0) identified-organization(4) etsi(0) inDomain(1) in-network(1) +modules(0) cs1-datatypes(2) version1(0)} + + MiscCallInfo +FROM CS2-datatypes {itu-t(0) identified-organization(4) etsi(0) inDomain(1) in-network(1) +cs2(20) modules(0) in-cs2-datatypes (0) version1(0)} + + IMEI, + IMSI, + ISDN-AddressString +FROM MAP-CommonDataTypes {itu-t(0) identified-organization(4) etsi(0) mobileDomain(0) +gsm-Network(1) modules(3) map-CommonDataTypes(18) version12(12)} + + GPRSMSClass, + LocationInformation, + MS-Classmark2 +FROM MAP-MS-DataTypes {itu-t(0) identified-organization(4) etsi(0) mobileDomain(0) +gsm-Network(1) modules(3) map-MS-DataTypes(11) version12(12)} + + PARAMETERS-BOUND +FROM CAP-classes classes + + opcode-connectSMS, + opcode-continueSMS, + opcode-eventReportSMS, + opcode-furnishChargingInformationSMS, + opcode-initialDPSMS, + opcode-releaseSMS, + opcode-requestReportSMSEvent, + opcode-resetTimerSMS +FROM CAP-operationcodes operationcodes +-- The CAP Operation identifiers for CAP V3 and CAP V4 for SMS in Rel-6 are the same as in Rel-5. + + CalledPartyBCDNumber {}, + EventSpecificInformationSMS, + EventTypeSMS, + Extensions {}, + FCISMSBillingChargingCharacteristics, + LocationInformationGPRS, + RPCause, + SMS-AddressString, + SMSEvent, + TimeAndTimezone {}, + TimerID, + TimerValue, + TPDataCodingScheme, + TPProtocolIdentifier, + TPShortMessageSpecificInfo, + TPValidityPeriod +FROM CAP-datatypes datatypes +-- For Rel-6, the CAP-datatypes module is updated to version8(7); Object Identifier 'datatypes' +-- is also updated to version8(7). As a result, the present module uses Rel-6 data type definitions. + + missingCustomerRecord, + missingParameter, +``` + +``` + +parameterOutOfRange, +systemFailure, +taskRefused, +unexpectedComponentSequence, +unexpectedDataValue, +unexpectedParameter +FROM CAP-errortypes errortypes +-- For Rel-6, the CAP-errortypes module is updated to version8(7); Object Identifier +-- 'errortypes' is also updated to version8(7). As a result, the present module uses Rel-6 +-- error type definitions. + +CallReferenceNumber +FROM MAP-CH-DataTypes {itu-t(0) identified-organization(4) etsi(0) mobileDomain(0) +gsm-Network(1) modules(3) map-CH-DataTypes(13) version12(12)} + +; + +connectSMS {PARAMETERS-BOUND : bound} OPERATION ::= { + ARGUMENT ConnectSMSArg {bound} + RETURN RESULT FALSE + ERRORS {missingParameter | + parameterOutOfRange | + systemFailure | + taskRefused | + unexpectedComponentSequence | + unexpectedDataValue | + unexpectedParameter} + CODE opcode-connectSMS} +-- Direction: gsmSCF -> gsmSSF or gprsSSF, Timer: Tconsms +-- This operation is used to request the smsSSF to perform the SMS processing +-- actions to route or forward a short message to a specified destination. + +ConnectSMSArg {PARAMETERS-BOUND : bound} ::= SEQUENCE { + callingPartyNumber [0] SMS-AddressString OPTIONAL, + destinationSubscriberNumber [1] CalledPartyBCDNumber {bound} OPTIONAL, + smSCAddress [2] ISDN-AddressString OPTIONAL, + extensions [10] Extensions {bound} OPTIONAL, + ... +} + +continueSMS OPERATION ::= { + RETURN RESULT FALSE + ALWAYS RESPONDS FALSE + CODE opcode-continueSMS} +-- Direction: gsmSCF -> smsSSF, Timer: Tcuesms +-- This operation is used to request the smsSSF to proceed with +-- Short Message processing at the DP at which it previously suspended +-- Short Message processing to await gsmSCF instructions (i.e. proceed +-- to the next Point in Association in the SMS FSM). The smsSSF +-- continues SMS processing without substituting new data from the gsmSCF. + +eventReportSMS {PARAMETERS-BOUND : bound} OPERATION ::= { + ARGUMENT EventReportSMSArg {bound} + RETURN RESULT FALSE + ALWAYS RESPONDS FALSE + CODE opcode-eventReportSMS} +-- Direction: gsmSSF or gprsSSF -> gsmSCF, Timer: Terbsms +-- This operation is used to notify the gsmSCF of a Short Message related event (FSM events +-- such as submission, delivery or failure) previously requested by the gsmSCF in a +-- RequestReportSMSEvent operation. + +EventReportSMSArg {PARAMETERS-BOUND : bound} ::= SEQUENCE { + eventTypeSMS [0] EventTypeSMS, + eventSpecificInformationSMS [1] EventSpecificInformationSMS OPTIONAL, + miscCallInfo [2] MiscCallInfo DEFAULT {messageType request}, + extensions [10] Extensions {bound} OPTIONAL, + ... +} + +furnishChargingInformationSMS {PARAMETERS-BOUND : bound} OPERATION ::= { + ARGUMENT FurnishChargingInformationSMSArg {bound} + RETURN RESULT FALSE + ERRORS {missingParameter | + taskRefused | + unexpectedComponentSequence | + unexpectedDataValue | + unexpectedParameter} + +``` + +``` + + CODE opcode-furnishChargingInformationSMS} +-- Direction: gsmSCF -> gsmSSF or gprsSSF, Timer: Tfcisms +-- This operation is used to request the smsSSF to generate, register a charging record +-- or to include some information in the default SM record. The registered charging record is +-- intended for off line charging of the Short Message. + +``` + +``` + +FurnishChargingInformationSMSArg {PARAMETERS-BOUND : bound} ::= + FCISMSBillingChargingCharacteristics {bound} + +``` + +``` + +initialDPSMS {PARAMETERS-BOUND : bound} OPERATION ::= { + ARGUMENT InitialDPSMSArg {bound} + RETURN RESULT FALSE + ERRORS {missingCustomerRecord | + missingParameter | + parameterOutOfRange | + systemFailure | + taskRefused | + unexpectedComponentSequence | + unexpectedDataValue | + unexpectedParameter} + CODE opcode-initialDPSMS} +-- Direction: gsmSSF or gprsSSF -> gsmSCF, Timer: Tidpsms +-- This operation is used after a TDP to indicate request for service. + +``` + +``` + +InitialDPSMSArg {PARAMETERS-BOUND : bound} ::= SEQUENCE { + serviceKey [0] ServiceKey, + destinationSubscriberNumber [1] CalledPartyBCDNumber {bound} OPTIONAL, + callingPartyNumber [2] SMS-AddressString OPTIONAL, + eventTypeSMS [3] EventTypeSMS OPTIONAL, + iMSI [4] IMSI OPTIONAL, + locationInformationMSC [5] LocationInformation OPTIONAL, + locationInformationGPRS [6] LocationInformationGPRS OPTIONAL, + sMSCAddress [7] ISDN-AddressString OPTIONAL, + timeAndTimezone [8] TimeAndTimezone {bound} OPTIONAL, + tPShortMessageSpecificInfo [9] TPShortMessageSpecificInfo OPTIONAL, + tPProtocolIdentifier [10] TPProtocolIdentifier OPTIONAL, + tPDataCodingScheme [11] TPDataCodingScheme OPTIONAL, + tPValidityPeriod [12] TPValidityPeriod OPTIONAL, + extensions [13] Extensions {bound} OPTIONAL, + ..., + smsReferenceNumber [14] CallReferenceNumber OPTIONAL, + mscAddress [15] ISDN-AddressString OPTIONAL, + sgsn-Number [16] ISDN-AddressString OPTIONAL, + ms-Classmark2 [17] MS-Classmark2 OPTIONAL, + gPRSMSClass [18] GPRSMSClass OPTIONAL, + iMEI [19] IMEI OPTIONAL, + calledPartyNumber [20] ISDN-AddressString OPTIONAL +} + +``` + +``` + +-- The UserCSGInformation is conveyed in the LocationInformation for CS and LocationInformationGPRS +-- for GPRS. The encoding of the parameter is as defined in 3GPP TS 29.002 [11]. + +``` + +``` + +releaseSMS OPERATION ::= { + ARGUMENT ReleaseSMSArg + RETURN RESULT FALSE + ALWAYS RESPONDS FALSE + CODE opcode-releaseSMS} +-- Direction: gsmSCF -> gsmSSF or gprsSSF, Timer: Trelsms +-- This operation is used to prevent an attempt to submit or deliver a short message. + +``` + +``` + +ReleaseSMSArg ::= RPCause + +``` + +``` + +requestReportSMSEvent {PARAMETERS-BOUND : bound} OPERATION ::= { + ARGUMENT RequestReportSMSEventArg {bound} + RETURN RESULT FALSE + ERRORS {missingParameter | + parameterOutOfRange | + systemFailure | + taskRefused | + unexpectedComponentSequence | + unexpectedDataValue | + unexpectedParameter} + CODE opcode-requestReportSMSEvent} +-- Direction: gsmSCF -> gsmSSF or gprsSSF, Timer: Trrbsms +-- This operation is used to request the gsmSSF or gprsSSF to monitor for a +-- Short Message related event (FSM events such as submission, delivery or failure) +-- and to send a notification to the gsmSCF when the event is detected. + +``` + +``` + +RequestReportSMSEventArg {PARAMETERS-BOUND : bound} ::= SEQUENCE { + smsevents [0] SEQUENCE SIZE (1..bound.&numOfSMSEvents) OF SMSEvent, + extensions [10] Extensions {bound} OPTIONAL, + ... +} +-- Indicates the Short Message related events(s) for notification. + +resetTimerSMS {PARAMETERS-BOUND : bound} OPERATION ::= { + ARGUMENT ResetTimerSMSArg {bound} + RETURN RESULT FALSE + ERRORS {missingParameter | + parameterOutOfRange | + taskRefused | + unexpectedComponentSequence | + unexpectedDataValue | + unexpectedParameter} + CODE opcode-resetTimerSMS} +-- Direction: gsmSCF -> smsSSF, Timer: Trtsms +-- This operation is used to request the smsSSF to refresh an application +-- timer in the smsSSF. + +ResetTimerSMSArg {PARAMETERS-BOUND : bound} ::= SEQUENCE { + timerID [0] TimerID DEFAULT tssf, + timervalue [1] TimerValue, + extensions [2] Extensions {bound} OPTIONAL, + ... +} + +END + +``` + +## 7.1.1 Operation timers + +The following value ranges apply for operation specific timers in CAP: + +short: 1 to 20 seconds; +medium: 1 to 60 seconds; +long: 1 second to 30 minutes. + +Table 7-1 lists all operation timers and the value range for each timer. The definitive value for each operation timer may be network specific and has to be defined by the network operator. + +**Table 7-1: Operation timers and their value range** + +| Operation Name | Timer | Value range | +|-------------------------------|---------------------|-------------| +| ConnectSMS | T consms | Short | +| ContinueSMS | T cuesms | Short | +| EventReportSMS | T erbsms | Short | +| FurnishChargingInformationSMS | T fcisms | Short | +| InitialDPSMS | T idpsms | Short | +| ReleaseSMS | T relsms | Short | +| RequestReportSMSEvent | T rrbsms | Short | +| ResetTimerSMS | T rtsms | Short | + +## 7.2 SMS contracts, packages and ACs + +### 7.2.1 smsSSF/gsmSCF ASN.1 module + +``` + +CAP-smsSSF-gsmSCF-pkgs-contracts-ac {itu-t(0) identified-organization(4) etsi(0) mobileDomain(0) +umts-network(1) modules(3) cap-smsSSF-gsmSCF-pkgs-contracts-ac(106) version8(7)} + +``` + +``` + +DEFINITIONS ::= BEGIN + +``` + +``` + +-- This module specifies the Operation Packages, Contracts, Application Contexts +-- and Abstract Syntaxes used for the smsSSF - gsmSCF interface, for the + +``` + +``` +-- control of MO-SMS and MT-SMS. + +-- The table in subclause 2.1 lists the specifications that contain the modules +-- that are used by CAP. + +IMPORTS + + PARAMETERS-BOUND, + cAPSpecificBoundSet +FROM CAP-classes classes +-- Elements that exist in cAPSpecificBoundSet in Rel-5 are not changed in Rel-6. As a +-- result, the value range of data type definitions in Rel-5 are not changed in Rel-6. + + CONTRACT, + OPERATION-PACKAGE, + OPERATION +FROM Remote-Operations-Information-Objects ros-InformationObjects + + TCMessage {} +FROM TCAPMessages tc-Messages + + APPLICATION-CONTEXT, + dialogue-abstract-syntax +FROM TC-Notation-Extensions tc-NotationExtensions + + connectSMS{}, + continueSMS, + eventReportSMS{}, + furnishChargingInformationSMS{}, + initialDPSMS{}, + releaseSMS, + requestReportSMSEvent{}, + resetTimerSMS{} +FROM CAP-SMS-ops-args sms-Operations +-- Object Identifier 'sms-Operations' is updated to version8(7) in Rel-6. As a result, +-- the present module, 'CAP-smsSSF-gsmSCF-pkgs-contracts-ac', IMPORTS CAP Operation +-- definitions from CAP-SMS-ops-args version8(7). Operation definitions are used in the +-- ABSTRACT SYNTAX definitions and in the OPERATION PACKAGE definitions. + + id-ac-cap3-sms-AC, + id-ac-cap4-sms-AC, +-- The APPLICATION-CONTEXT Identifiers for CAP V3 and CAP V4 for SMS in Rel-6 are the same as +-- in Rel-5. + + id-cap3SmsSsfTogsmScf, + id-cap4SmsSsfTogsmScf, +-- The CONTRACT Identifiers for CAP V3 and CAP V4 for SMS in Rel-6 are the same as in Rel-5. + + id-package-smsActivation, + id-package-smsConnect, + id-package-smsContinue, + id-package-smsRelease, + id-package-smsEventHandling, + id-package-smsBilling, + id-package-smsTimer, +-- The OPERATION-PACKAGE Identifiers for CAP V3 and CAP V4 for SMS in Rel-6 are the same as +-- in Rel-5. + + sms-Operations, +-- Object Identifier sms-Operations is updated to version8(7) in Rel-6. As a result, the present +-- module, 'CAP-smsSSF-gsmSCF-pkgs-contracts-ac', IMPORTS Rel-6 versions of the CAP Operation +-- definitions. + + tc-NotationExtensions, + tc-Messages, + ros-InformationObjects, + classes, + + id-as-smsSSF-gsmSCF-AS +-- The ABSTRACT-SYNTAX Identifiers for CAP V3 and CAP V4 for SMS in Rel-6 are the same as +-- in Rel-5. + +FROM CAP-object-identifiers {itu-t(0) identified-organization(4) ettsi(0) mobileDomain(0) +umts-network(1) modules(3) cap-object-identifiers(100) version8(7)} + +; + +-- Application Contexts +``` + +``` +-- Rel-6 uses the same Application Context versions for SMS as Rel-5. The CONTRACT and ABSTRACT +-- SYNTAXES for SMS are defined in Rel-6. +``` + +``` +-- Refer to ITU-T Recommendation Q.775 for the formal definition of APPLICATION-CONTEXT. +-- The structured DIALOGUE MODE is defined in ITU-T Recommendation Q.771; the +-- dialogue-abstract-syntax ABSTRACT SYNTAX is defined in ITU-T Recommendation Q.775. +``` + +``` +cap3-sms-AC APPLICATION-CONTEXT ::= { +``` + +``` + CONTRACT cap3SMS + DIALOGUE MODE structured + ABSTRACT SYNTAXES {dialogue-abstract-syntax | + sms-AbstractSyntax} + APPLICATION CONTEXT NAME id-ac-cap3-sms-AC} +``` + +``` +-- This application context shall be used for CAMEL support of MO-SMS. +``` + +``` +-- 'cap3SMS' and 'sms-AbstractSyntax' are defined in the present module. +``` + +``` +cap4-sms-AC APPLICATION-CONTEXT ::= { +``` + +``` + CONTRACT cap4SMS + DIALOGUE MODE structured + ABSTRACT SYNTAXES {dialogue-abstract-syntax | + sms-AbstractSyntax} + APPLICATION CONTEXT NAME id-ac-cap4-sms-AC} +``` + +``` +-- This application context shall be used for CAMEL support of MT-SMS. +``` + +``` +-- 'cap4SMS' and 'sms-AbstractSyntax' are defined in the present module. +``` + +``` +-- Contracts +``` + +``` +-- The CONTRACT definitions for SMS in Rel-6 use OPERATION-PACKAGE definitions which are +``` + +``` +-- defined in Rel-6. +``` + +``` +cap3SMS CONTRACT ::= { +``` + +``` +-- dialogue initiated by gprsSSF or gsmSSF with InitialDPSMS Operation +``` + +``` + INITIATOR CONSUMER OF {smsActivationPackage {CAPSpecificBoundSet}} + RESPONDER CONSUMER OF {smsConnectPackage {CAPSpecificBoundSet} | + smsReleasePackage | + smsEventHandlingPackage {CAPSpecificBoundSet} | + smsTimerPackage {CAPSpecificBoundSet} | + smsBillingPackage {CAPSpecificBoundSet} | + smsProcessingPackage} + ID id-cap3SmsSsfTogsmScf} +``` + +``` +-- The OPERATION-PACKAGES are defined in the present module. +``` + +``` +cap4SMS CONTRACT ::= { +``` + +``` +-- dialogue initiated by gprsSSF or gsmSSF with InitialDPSMS Operation +``` + +``` + INITIATOR CONSUMER OF {smsActivationPackage {CAPSpecificBoundSet}} + RESPONDER CONSUMER OF {smsConnectPackage {CAPSpecificBoundSet} | + smsReleasePackage | + smsEventHandlingPackage {CAPSpecificBoundSet} | + smsTimerPackage {CAPSpecificBoundSet} | + smsBillingPackage {CAPSpecificBoundSet} | + smsProcessingPackage } + ID id-cap4SmsSsfTogsmScf} +``` + +``` +-- The OPERATION-PACKAGES are defined in the present module. +``` + +``` +-- Operation Packages +``` + +``` +-- The OPERATION-PACKAGE definitions for SMS in Rel-6 use Operation definitions from Rel-6. The +``` + +``` +-- OPERATION definitions are IMPORTED from CAP-SMS-ops-args. +``` + +``` +smsActivationPackage {PARAMETERS-BOUND : bound} OPERATION-PACKAGE ::= { +``` + +``` + CONSUMER INVOKES {initialDPSMS {bound}} + ID id-package-smsActivation} +``` + +``` +smsConnectPackage {PARAMETERS-BOUND : bound} OPERATION-PACKAGE ::= { +``` + +``` + CONSUMER INVOKES {connectSMS {bound}} + ID id-package-smsConnect} +``` + +``` +smsProcessingPackage OPERATION-PACKAGE ::= { +``` + +``` + CONSUMER INVOKES {continueSMS} + ID id-package-smsContinue} +``` + +``` +smsReleasePackage OPERATION-PACKAGE ::= { +``` + +``` + CONSUMER INVOKES {releaseSMS} +``` + +``` + + ID id-package-smsRelease} + +smsEventHandlingPackage {PARAMETERS-BOUND : bound} OPERATION-PACKAGE ::= { + CONSUMER INVOKES {requestReportSMSEvent {bound}} + SUPPLIER INVOKES {eventReportSMS {bound}} + ID id-package-smsEventHandling} + +smsBillingPackage {PARAMETERS-BOUND : bound} OPERATION-PACKAGE ::= { + CONSUMER INVOKES {furnishChargingInformationSMS {bound}} + ID id-package-smsBilling} + +smsTimerPackage {PARAMETERS-BOUND : bound} OPERATION-PACKAGE ::= { + CONSUMER INVOKES {resetTimerSMS {bound}} + ID id-package-smsTimer} + +-- Abstract Syntaxes + +-- SmsInvokable and SmsReturnable use OPERATION definitions with version8(7). As a result, +-- Generic-sms-PDUs uses version8(7) OPERATION definitions. As a subsequent result, +-- sms-AbstractSyntax uses version8(7) OPERATION definitions. That ABSTRACT-SYNTAX is used +-- in the cap3-sms-AC APPLICATION-CONTEXT definition and in the and cap4-sms-AC APPLICATION- +-- CONTEXT definition (CAP from smsSSF to gsmSCF). + +sms-AbstractSyntax ABSTRACT-SYNTAX ::= { + Generic-sms-PDUs + IDENTIFIED BY id-as-smsSSF-gsmSCF-AS } +-- 'Generic-sms-PDUs' is defined in the present module. + +Generic-sms-PDUs ::= TCMessage {{SmsInvokable}, + {SmsReturnable}} +-- 'SmsInvokable' and 'SmsReturnable' are defined in the present module. + +SmsInvokable OPERATION ::= { + connectSMS {cAPSpecificBoundSet} | + eventReportSMS {cAPSpecificBoundSet} | + furnishChargingInformationSMS {cAPSpecificBoundSet} | + initialDPSMS {cAPSpecificBoundSet} | + requestReportSMSEvent {cAPSpecificBoundSet} | + resetTimerSMS {cAPSpecificBoundSet}} +-- The OPERATION definitions are IMPORTED from CAP-SMS-ops-args version8(7). + +SmsReturnable OPERATION ::= { + connectSMS {cAPSpecificBoundSet} | + continueSMS | + furnishChargingInformationSMS {cAPSpecificBoundSet} | + initialDPSMS {cAPSpecificBoundSet} | + releaseSMS | + requestReportSMSEvent {cAPSpecificBoundSet} | + resetTimerSMS {cAPSpecificBoundSet}} +-- The OPERATION definitions are IMPORTED from CAP-SMS-ops-args version8(7). + +END + +``` + +## 8 GPRS Control + +### 8.1 gsmSCF/gprsSSF operations and arguments + +``` + +CAP-gprsSSF-gsmSCF-ops-args {itu-t(0) identified-organization(4) etsi(0) mobileDomain(0) + umts-network(1) modules(3) cap-GPRS-ops-args(107) version8(7)} +-- Module CAP-gprsSSF-gsmSCF-ops-args is updated to version8(7) for Rel-6. The OPERATION +-- definitions in this module are not modified, compared to Rel-5. + +``` + +``` + +DEFINITIONS IMPLICIT TAGS ::= BEGIN + +``` + +``` + +-- This module contains the operations and operation arguments used for the +-- gprsSSF - gsmSCF interface, for the control of GPRS. + +-- The table in subclause 2.1 lists the specifications that contain the modules +-- that are used by CAP. + +``` + +``` + +IMPORTS + +``` + +``` + + errortypes, + +``` + +``` + datatypes, + operationcodes, + classes, + ros-InformationObjects +FROM CAP-object-identifiers {itu-t(0) identified-organization(4) etsi(0) mobileDomain(0) +umts-network(1) modules(3) cap-object-identifiers(100) version8(7)} + + OPERATION +FROM Remote-Operations-Information-Objects ros-InformationObjects + + ServiceKey +FROM CS1-DataTypes {itu-t(0) identified-organization(4) etsi(0) inDomain(1) in-network(1) +modules(0) cs1-datatypes(2) version1(0)} + + MiscCallInfo +FROM CS2-datatypes {itu-t(0) identified-organization(4) etsi(0) inDomain(1) in-network(1) +cs2(20) modules(0) in-cs2-datatypes(0) version1(0)} + + IMEI, + IMSI, + ISDN-AddressString +FROM MAP-CommonDataTypes {itu-t(0) identified-organization(4) etsi(0) mobileDomain(0) +gsm-Network(1) modules(3) map-CommonDataTypes(18) version12(12)} + + GPRSChargingID, + GPRSMSClass, + GSN-Address, + RAIdentity +FROM MAP-MS-DataTypes {itu-t(0) identified-organization(4) etsi(0) mobileDomain(0) +gsm-Network(1) modules(3) map-MS-DataTypes(11) version12(12)} + + PARAMETERS-BOUND +FROM CAP-classes classes + + opcode-activityTestGPRS, + opcode-applyChargingGPRS, + opcode-applyChargingReportGPRS, + opcode-cancelGPRS, + opcode-connectGPRS, + opcode-continueGPRS, + opcode-entityReleasedGPRS, + opcode-eventReportGPRS, + opcode-furnishChargingInformationGPRS, + opcode-initialDPGPRS, + opcode-releaseGPRS, + opcode-requestReportGPRSEvent, + opcode-resetTimerGPRS, + opcode-sendChargingInformationGPRS +FROM CAP-operationcodes operationcodes +-- The CAP Operation identifiers for CAP V3 for GPRS in Rel-6 are the same as the CAP Operation +-- identifiers for CAP V3 for GPRS in Rel-5. + + AccessPointName {}, + GPRSCause {}, + ChargingCharacteristics, + ChargingResult, + ChargingRollOver, + EndUserAddress, + Extensions, + FCIGPRSBillingChargingCharacteristics, + GPRSEventSpecificInformation {}, + GPRSEvent, + GPRSEventType, + LocationInformationGPRS, + PDPID, + PDPInitiationType, + QualityOfService, + SCIGPRSBillingChargingCharacteristics {}, + SGSNCapabilities, + TimeAndTimezone {}, + TimerID, + TimerValue +FROM CAP-datatypes datatypes +-- For Rel-6, the CAP-datatypes module is updated to version8(7); Object Identifier 'datatypes' +-- is also updated to version8(7). As a result, the present module uses Rel-6 data type definitions. + + missingCustomerRecord, + missingParameter, +``` + +``` + +parameterOutOfRange, +systemFailure, +taskRefused, +unexpectedComponentSequence, +unexpectedDataValue, +unexpectedParameter, +unknownPDPID +FROM CAP-errortypes errortypes +-- For Rel-6, the CAP-errortypes module is updated to version8(7); Object Identifier +-- 'errortypes' is also updated to version8(7). As a result, the present module uses Rel-6 +-- error type definitions. + +; + +activityTestGPRS OPERATION ::= { + RETURN RESULT TRUE + CODE opcode-activityTestGPRS} +-- Direction: gsmSCF -> gprsSSF, Timer: Tatg +-- This operation is used to check for the continued existence of a relationship between the gsmSCF +-- and gprsSSF. If the relationship is still in existence, then the gprsSSF will respond. If no +-- reply is received, then the gsmSCF will assume that the gprsSSF has failed in some way +-- and will take the appropriate action. + +applyChargingGPRS OPERATION ::= { + ARGUMENT ApplyChargingGPRSArg + RETURN RESULT FALSE + ERRORS {missingParameter | + unexpectedComponentSequence | + unexpectedParameter | + unexpectedDataValue | + parameterOutOfRange | + systemFailure | + taskRefused | + unknownPDPID} + CODE opcode-applyChargingGPRS} +-- Direction gsmSCF -> gprsSSF, Timer Tacg +-- This operation is used for interacting from the gsmSCF with the gprsSSF CSE-controlled +-- GPRS session or PDP Context charging mechanism. + +ApplyChargingGPRSArg ::= SEQUENCE { + chargingCharacteristics [0] ChargingCharacteristics, + tariffSwitchInterval [1] INTEGER (1..86400) OPTIONAL, + pdPID [2] PDPID OPTIONAL, + ... +} +-- tariffSwitchInterval is measured in 1 second units. + +applyChargingReportGPRS OPERATION ::= { + ARGUMENT ApplyChargingReportGPRSArg + RETURN RESULT TRUE + ERRORS {missingParameter | + unexpectedComponentSequence | + unexpectedParameter | + unexpectedDataValue | + parameterOutOfRange | + systemFailure | + taskRefused | + unknownPDPID} + CODE opcode-applyChargingReportGPRS} +-- Direction gprsSSF -> gsmSCF, Timer Tacrg +-- The ApplyChargingReportGPRS operation provides the feedback from the gprsSSF to the gsmSCF +-- CSE-controlled GPRS session charging mechanism. + +ApplyChargingReportGPRSArg ::= SEQUENCE { + chargingResult [0] ChargingResult, + qualityOfService [1] QualityOfService OPTIONAL, + active [2] BOOLEAN DEFAULT TRUE, + pdPID [3] PDPID OPTIONAL, + ..., + chargingRollOver [4] ChargingRollOver OPTIONAL +} + +cancelGPRS OPERATION ::= { + ARGUMENT CancelGPRSArg + RETURN RESULT FALSE + ERRORS {missingParameter | + taskRefused | + +``` + +``` + + unknownPDPID} + CODE opcode-cancelGPRS} +-- Direction: gsmSCF -> gprsSSF, Timer: Tcag +-- This generic operation cancels all previous requests, +-- i.e. all EDPs and reports can be cancelled by the gsmSCF. + +CancelGPRSArg ::= SEQUENCE { + pDPID [0] PDPID OPTIONAL, + ... +} + +connectGPRS {PARAMETERS-BOUND: bound} OPERATION ::= { + ARGUMENT ConnectGPRSArg {bound} + RETURN RESULT FALSE + ERRORS {missingParameter | + parameterOutOfRange | + unknownPDPID | + systemFailure | + taskRefused | + unexpectedComponentSequence | + unexpectedDataValue | + unexpectedParameter} + CODE opcode-connectGPRS} +-- Direction: gsmSCF -> gprsSSF, Timer: Tcong +-- This operation is used to modify the Access Point Name used when establishing a PDP Context. + +ConnectGPRSArg {PARAMETERS-BOUND: bound} ::= SEQUENCE { + accessPointName [0] AccessPointName {bound}, + pDPID [1] PDPID OPTIONAL, + ... +} + +continueGPRS OPERATION ::= { + ARGUMENT ContinueGPRSArg + RETURN RESULT FALSE + ERRORS {missingParameter | + unknownPDPID | + unexpectedDataValue} + CODE opcode-continueGPRS} +-- Direction: gsmSCF -> gprsSSF, Timer: Tcueg +-- This operation is used to request the gprsSSF to proceed with processing at the DP at +-- which it previously suspended processing to await gsmSCF instructions (i.e., proceed to +-- the next point in processing in the Attach/Detach state model or PDP Context +-- state model) substituting new data from the gsmSCF. + +ContinueGPRSArg ::= SEQUENCE { + pDPID [0] PDPID OPTIONAL, + ... +} + +entityReleasedGPRS {PARAMETERS-BOUND : bound} OPERATION ::= { + ARGUMENT EntityReleasedGPRSArg {bound} + RETURN RESULT TRUE + ERRORS {missingParameter | + taskRefused | + unknownPDPID} + CODE opcode-entityReleasedGPRS} +-- Direction: gprsSSF -> gsmSCF, Timer: Terg +-- This operation is used when the GPRS Session is detached or a PDP Context is disconnected and +-- the associated event is not armed for reporting. +-- The usage of this operation is independent of the functional entity that initiates the Detach +-- or PDP Context Disconnection and is independent of the cause of the Detach or PDP Context +-- Disconnect. + +EntityReleasedGPRSArg {PARAMETERS-BOUND : bound} ::= SEQUENCE { + gPRSCause [0] GPRSCause {bound}, + pDPID [1] PDPID OPTIONAL, + ... +} + +eventReportGPRS {PARAMETERS-BOUND : bound} OPERATION ::= { + ARGUMENT EventReportGPRSArg {bound} + RETURN RESULT TRUE + ERRORS {unknownPDPID} + CODE opcode-eventReportGPRS} +-- Direction gprsSSF -> gsmSCF, Timer Tereg +-- This operation is used to notify the gsmSCF of a GPRS session or PDP context related + +``` + +``` + +-- events (e.g. PDP context activation) previously requested by the gsmSCF in a +-- RequestReportGPRSOperation. + +EventReportGPRSArg {PARAMETERS-BOUND : bound} ::= SEQUENCE { + gPRSEEventType [0] GPRSEEventType, + miscGPRSInfo [1] MiscCallInfo DEFAULT {messageType request}, + gPRSEventSpecificInformation [2] GPRSEventSpecificInformation {bound} OPTIONAL, + PDPID [3] PDPID OPTIONAL, + ... +} + +furnishChargingInformationGPRS {PARAMETERS-BOUND : bound} OPERATION ::= { + ARGUMENT FurnishChargingInformationGPRSArg {bound} + RETURN RESULT FALSE + ERRORS {missingParameter | + taskRefused | + unexpectedComponentSequence | + unexpectedDataValue | + unexpectedParameter | + unknownPDPID} + CODE opcode-furnishChargingInformationGPRS} +-- Direction: gsmSCF -> gprsSSF, Timer: Tfcig +-- This operation is used to request the gprsSSF to generate, register a logical record or to +-- include some information in the default logical GPRS record. +-- The registered logical record is intended for off line charging of the GPRS session +-- or PDP Context. + +FurnishChargingInformationGPRSArg {PARAMETERS-BOUND : bound} ::= + FCIGPRSBillingChargingCharacteristics{bound} + +initialDPGPRS {PARAMETERS-BOUND : bound} OPERATION ::= { + ARGUMENT InitialDPGPRSArg {bound} + RETURN RESULT FALSE + ERRORS {missingCustomerRecord | + missingParameter | + parameterOutOfRange | + systemFailure | + taskRefused | + unexpectedComponentSequence | + unexpectedDataValue | + unexpectedParameter} + CODE opcode-initialDPGPRS} +-- Direction gprsSSF -> gsmSCF, Timer T_idpg +-- This operation is used by the gprsSSF when a trigger is detected at a DP in the GPRS state +-- machines to request instructions from the gsmSCF + +InitialDPGPRSArg {PARAMETERS-BOUND : bound} ::= SEQUENCE { + serviceKey [0] ServiceKey, + gPRSEEventType [1] GPRSEEventType, + mSISDN [2] ISDN-AddressString, + IMSI [3] IMSI, + timeAndTimeZone [4] TimeAndTimezone {bound}, + gPRSMSClass [5] GPRSMSClass OPTIONAL, + endUserAddress [6] EndUserAddress {bound} OPTIONAL, + qualityOfService [7] QualityOfService OPTIONAL, + accessPointName [8] AccessPointName{bound} OPTIONAL, + routeingAreaIdentity [9] RAIdentity OPTIONAL, + chargingID [10] GPRSChargingID OPTIONAL, + SGSNCapabilities [11] SGSNCapabilities OPTIONAL, + locationInformationGPRS [12] LocationInformationGPRS OPTIONAL, + PDPInitiationType [13] PDPInitiationType OPTIONAL, + extensions [14] Extensions {bound} OPTIONAL, + ... + gGSNAddress [15] GSN-Address OPTIONAL, + secondaryPDP-context [16] NULL OPTIONAL, + iMEI [17] IMEI OPTIONAL +} +-- The RouteingAreaIdentity parameter is not used. +-- The receiving entity shall ignore RouteingAreaIdentity if received. +-- The RouteingAreaIdentity is conveyed in the LocationInformationGPRS parameter. +-- The CSGInformation is conveyed in the LocationInformationGPRS parameter. The encoding of the +-- parameter is as defined in 3GPP TS 29.002 [11]. + +releaseGPRS {PARAMETERS-BOUND : bound} OPERATION ::= { + ARGUMENT ReleaseGPRSArg {bound} + RETURN RESULT FALSE + ERRORS {missingParameter | + taskRefused | + +``` + +``` + + unknownPDPID} + CODE opcode-releaseGPRS} +-- Direction: gsmSCF -> gprsSSF, Timer: Trg +-- This operation is used to tear down an existing GPRS session or PDP Context at any phase. + +ReleaseGPRSArg {PARAMETERS-BOUND : bound} ::= SEQUENCE { + gprsCause [0] GPRSCause {bound}, + pDPID [1] PDPID OPTIONAL, + ... +} + +requestReportGPRSEvent {PARAMETERS-BOUND : bound} OPERATION ::= { + ARGUMENT RequestReportGPRSEventArg {bound} + RETURN RESULT FALSE + ERRORS {missingParameter | + parameterOutOfRange | + systemFailure | + taskRefused | + unexpectedComponentSequence | + unexpectedDataValue | + unexpectedParameter | + unknownPDPID} + CODE opcode-requestReportGPRSEvent} +-- Direction: gsmSCF -> gprsSSF, Timer: Trrqe +-- This operation is used to request the gprsSSF to monitor for an event (e.g., GPRS events +-- such as attach or PDP Context activation), then send a notification back to the +-- gsmSCF when the event is detected. + +RequestReportGPRSEventArg {PARAMETERS-BOUND : bound} ::= SEQUENCE { + gPRSEvent [0] SEQUENCE SIZE (1..bound.&numOfGPRSEvents) OF GPRSEvent, + pDPID [1] PDPID OPTIONAL, + ... +} +-- Indicates the GPRS related events for notification. + +resetTimerGPRS OPERATION ::= { + ARGUMENT ResetTimerGPRSArg + RETURN RESULT FALSE + ERRORS {missingParameter | + parameterOutOfRange | + taskRefused | + unexpectedComponentSequence | + unexpectedDataValue | + unexpectedParameter | + unknownPDPID} + CODE opcode-resetTimerGPRS} +-- Direction: gsmSCF -> gprsSSF, Timer: Trtg +-- This operation is used to request the gprsSSF to refresh an application timer in the gprsSSF. + +ResetTimerGPRSArg ::= SEQUENCE { + timerID [0] TimerID DEFAULT tssf, + timervalue [1] TimerValue, + ... +} + +sendChargingInformationGPRS {PARAMETERS-BOUND: bound} OPERATION ::= { + ARGUMENT SendChargingInformationGPRSArg { bound} + RETURN RESULT FALSE + ERRORS {missingParameter | + unexpectedComponentSequence | + unexpectedParameter | + parameterOutOfRange | + systemFailure | + taskRefused | + unexpectedDataValue | + unknownPDPID} + CODE opcode-sendChargingInformationGPRS} +-- Direction: gsmSCF -> gprsSSF, Timer: Tscig +-- This operation is used to instruct the gprsSSF on the charging information which the +-- gprsSSF shall send to the Mobile Station by means of GSM access signalling. + +SendChargingInformationGPRSArg {PARAMETERS-BOUND: bound} ::= SEQUENCE { + scIGPRSBillingChargingCharacteristics [0] SCIGPRSBillingChargingCharacteristics {bound}, + ... +} + +END + +``` + +### 8.1.1 GPRS Reference Number + +``` + +CAP-GPRS-ReferenceNumber {itu-t(0) identified-organization(4) etsi(0) mobileDomain(0) +umts-network(1) modules(3) cap-dialogueInformation(111) version8(7)} +-- Module CAP-GPRS-ReferenceNumber is updated to version8(7) for Rel-6. The definitions +-- in this module are not modified, compared to Rel-5. + +DEFINITIONS ::= BEGIN + +EXPORTS + id-CAP-GPRS-ReferenceNumber, + cAP-GPRS-ReferenceNumber-Abstract-Syntax; + +IMPORTS + + Integer4 +FROM CS1-DataTypes {itu-t(0) identified-organization(4) etsi(0) inDomain(1) in-network(1) +modules(0) csl-datatypes(2) version1(0)} +; + +id-CAP-GPRS-ReferenceNumber OBJECT IDENTIFIER ::= {itu-t(0) identified-organization(4) etsi(0) +mobileDomain(0) umts-network(1) as(1) cap-GPRS-ReferenceNumber(5) version3(2)} + +CAP-GPRS-ReferenceNumber-Abstract-Syntax ABSTRACT-SYNTAX ::= {CAP-GPRS-ReferenceNumber IDENTIFIED BY +id-CAP-GPRS-ReferenceNumber} + +CAP-GPRS-ReferenceNumber ::= SEQUENCE { + destinationReference [0] Integer4 OPTIONAL, + originationReference [1] Integer4 OPTIONAL +} +-- This parameter is used to identify the relationship between SGSN and the gsmSCF. + +END -- of CAP-GPRS-ReferenceNumber + +``` + +### 8.1.2 Operation timers + +The following value ranges apply for operation specific timers in CAP: + +| | | +|---------|------------------------| +| short: | 1 to 20 seconds; | +| medium: | 1 to 60 seconds; | +| long: | 1 second to 30 minutes | + +Table 8-1 lists all operation timers and the value range for each timer. The definitive value for each operation timer may be network specific and has to be defined by the network operator. + +**Table 8-1: Operation timers and their value range** + +| Operation Name | Timer | value | +|--------------------------------|-------------------|-------| +| ActivityTestGPRST | T atg | Short | +| ApplyChargingGPRS | T acg | Short | +| ApplyChargingReportGPRS | T acrg | Short | +| CancelGPRS | T cag | Short | +| ConnectGPRS | T cong | Short | +| ContinueGPRS | T cueg | Short | +| EntityReleasedGPRS | T erg | Short | +| EventReportGPRS | T ereg | Short | +| FurnishChargingInformationGPRS | T fcig | Short | +| InitialDPGPRS | T idpg | Short | +| ReleaseGPRS | T rg | Short | +| RequestReportGPRSEvent | T rrqe | Short | +| ResetTimerGPRS | T rtg | Short | +| SendChargingInformationGPRS | T scig | Short | + +## 8.2 gsmSCF/gprsSSF contracts, packages and ACs + +### 8.2.1 gprsSSF/gsmSCF ASN.1 module + +``` + +CAP-gprsSSF-gsmSCF-pkgs-contracts-ac { itu-t(0) identified-organization(4) etsi(0) mobileDomain(0) +umts-network(1) modules(3) cap-gprsSSF-gsmSCF-pkgs-contracts-ac(108) version8(7) } +DEFINITIONS ::= BEGIN + +-- This module specifies the Operation Packages, Contracts, Application Contexts +-- and Abstract Syntaxes used for the gprsSSF - gsmSCF interface, for the +-- control of GPRS. + +-- The table in subclause 2.1 lists the specifications that contain the modules +-- that are used by CAP. + +IMPORTS + + PARAMETERS-BOUND, + cAPSpecificBoundSet +FROM CAP-classes classes +-- Elements that exist in cAPSpecificBoundSet in Rel-5 are not changed in Rel-6. As a +-- result, the value range of data type definitions in Rel-5 are not changed in Rel-6. + + CONTRACT, + OPERATION-PACKAGE, + OPERATION +FROM Remote-Operations-Information-Objects ros-InformationObjects + + TCMessage {} +FROM TCAPMessages tc-Messages + + APPLICATION-CONTEXT, + dialogue-abstract-syntax +FROM TC-Notation-Extensions tc-NotationExtensions + + activityTestGPRS, + applyChargingGPRS, + applyChargingReportGPRS, + cancelGPRS, + connectGPRS {}, + continueGPRS, + entityReleasedGPRS {}, + furnishChargingInformationGPRS {}, + initialDPGPRS {}, + releaseGPRS {}, + eventReportGPRS {}, + requestReportGPRSEvent {}, + +``` + +``` + + resetTimerGPRS, + sendChargingInformationGPRS {} +FROM CAP-gprsSSF-gsmSCF-ops-args gprsSSF-gsmSCF-Operations + + id-ac-CAP-gprsSSF-gsmSCF-AC, + id-ac-CAP-gsmSCF-gprsSSF-AC, +-- The APPLICATION-CONTEXT Object Identifiers for CAP V3 for GPRS in Rel-6 are the same as for +-- CAP V3 for GPRS in Rel-5. + + id-capGprsSsfToGsmScf, + id-capGsmScfToGprsSsf, +-- The CONTRACT Object Identifiers for CAP V3 for GPRS are updated in Rel-6. + + id-as-gprsSSF-gsmSCF-AS, + id-as-gsmSCF-gprsSSF-AS, +-- The ABSTRACT-SYNTAX Object Identifiers for CAP V3 for GPRS are updated in Rel-6. + + id-package-gprsScfActivation, + id-package-gprsConnect, + id-package-gprsContinue, + id-package-gprsRelease, + id-package-gprsEventHandling, + id-package-gprsExceptionInformation, + id-package-gprsTimer, + id-package-gprsBilling, + id-package-gprsCharging, + id-package-gprsChargeAdvice, + id-package-gprsActivityTest, + id-package-gprsCancel, +-- The OPERATION-PACKAGE Object Identifiers for CAP V3 for GPRS are updated in Rel-6. + + classes, + ros-InformationObjects, + tc-Messages, + tc-NotationExtensions, + + gprsSSF-gsmSCF-Operations +-- Object Identifier 'gprsSSF-gsmSCF-Operations' is updated for Rel-6. + +FROM CAP-object-identifiers {itu-t(0) identified-organization(4) etsi(0) mobileDomain(0) +umts-network(1) modules(3) cap-object-identifiers(100) version8(7)} + +; + +-- Application Contexts + +-- The APPLICATION-CONTEXT definitions for CAP V3 for GPRS are updated in Rel-6. +-- However, the APPLICATION-CONTEXT definitions for CAP V3 for GPRS in Rel-6 use the same +-- Object Identifier for APPLICATION CONTEXT NAME as CAP V3 for GPRS in Rel-5. + +-- Refer to ITU-T Recommendation Q.775 for the formal definition of APPLICATION-CONTEXT. +-- The structured DIALOGUE MODE is defined in ITU-T Recommendation Q.771; the +-- dialogue-abstract-syntax ABSTRACT SYNTAX is defined in ITU-T Recommendation Q.775. + +cap-gprssf-scfAC APPLICATION-CONTEXT ::= { + CONTRACT capGprsSsfToScf + DIALOGUE MODE structured + ABSTRACT SYNTAXES {dialogue-abstract-syntax | + gprsSSF-gsmSCFAbstractSyntax} + APPLICATION CONTEXT NAME id-ac-CAP-gprsSSF-gsmSCF-AC} +-- 'capGprsSsfToScf' and 'gprsSSF-gsmSCFAbstractSyntax' are defined in the present +-- module. + +cap-gsmscf-gprssfAC APPLICATION-CONTEXT ::= { + CONTRACT capGsmScfToGprsSsf + DIALOGUE MODE structured + ABSTRACT SYNTAXES {dialogue-abstract-syntax | + gsmSCF-gprsSSFAbstractSyntax} + APPLICATION CONTEXT NAME id-ac-CAP-gsmSCF-gprsSSF-AC} +-- 'capGsmScfToGprsSsf' and 'gsmSCF-gprsSSFAbstractSyntax' are defined in the present +-- module. + +-- Contracts +-- The CONTRACT definitions for CAP V3 for GPRS are updated in Rel-6. + +capGprsSsfToScf CONTRACT ::= { +-- dialogue initiated by gprsSSF with InitialDPGPRS, ApplyChargingReportGPRS, + +``` + +``` + +-- EntityReleasedGPRS and EventReportGPRS Operations +INITIATOR CONSUMER OF {gprsScfActivationPackage {cAPSpecificBoundSet} | + {gprsEventHandlingPackage {cAPSpecificBoundSet} | + {gprsChargingPackage | + {gprsExceptionInformationPackage {cAPSpecificBoundSet}}} +RESPONDER CONSUMER OF {gprsConnectPackage {cAPSpecificBoundSet} | + {gprsProcessingPackage | + {gprsReleasePackage {cAPSpecificBoundSet} | + {gprsEventHandlingPackage {cAPSpecificBoundSet} | + {gprsTimerPackage | + {gprsBillingPackage {cAPSpecificBoundSet} | + {gprsChargingPackage | + {gprsCancelPackage | + {gprsChargeAdvicePackage {cAPSpecificBoundSet}}} +ID id-capGprsSsfToGsmScf} +-- The OPERATION-PACKAGES are defined in the present module. + +capGsmScfToGprsSsf CONTRACT ::= { +-- dialogue initiated by gsmSCF with ApplyChargingGPRS, ActivityTestGPRS, +-- CancelGPRS, FurnishChargingInformationGPRS, ReleaseGPRS, +-- RequestReportGPRSEvent and SendChargingInformationGPRS Operations +INITIATOR CONSUMER OF {gprsReleasePackage {cAPSpecificBoundSet} | + {gprsEventHandlingPackage {cAPSpecificBoundSet} | + {gprsBillingPackage {cAPSpecificBoundSet} | + {gprsChargingPackage | + {gprsActivityTestPackage | + {gprsCancelPackage | + {gprsChargeAdvicePackage {cAPSpecificBoundSet}}} +ID id-capGsmScfToGprsSsf} +-- The OPERATION-PACKAGES are defined in the present module. + +-- Operation Packages + +-- The OPERATION-PACKAGE definitions for CAP V3 for GPRS are updated in Rel-6. + +gprsScfActivationPackage {PARAMETERS-BOUND : bound} OPERATION-PACKAGE ::= { +CONSUMER INVOKES {initialDPGPRS {bound}} +ID id-package-gprsScfActivation} + +gprsConnectPackage {PARAMETERS-BOUND : bound} OPERATION-PACKAGE ::= { +CONSUMER INVOKES {connectGPRS {bound}} +ID id-package-gprsConnect} + +gprsProcessingPackage OPERATION-PACKAGE ::= { +CONSUMER INVOKES {continueGPRS } +ID id-package-gprsContinue} + +gprsReleasePackage {PARAMETERS-BOUND : bound} OPERATION-PACKAGE ::= { +CONSUMER INVOKES {releaseGPRS {bound}} +ID id-package-gprsRelease} + +gprsEventHandlingPackage {PARAMETERS-BOUND : bound} OPERATION-PACKAGE ::= { +CONSUMER INVOKES {requestReportGPRSEvent {bound}} +SUPPLIER INVOKES {eventReportGPRS {bound}} +ID id-package-gprsEventHandling} + +gprsExceptionInformationPackage {PARAMETERS-BOUND : bound} OPERATION-PACKAGE ::= { +CONSUMER INVOKES {entityReleasedGPRS {bound}} +ID id-package-gprsExceptionInformation} + +gprsTimerPackage OPERATION-PACKAGE ::= { +CONSUMER INVOKES {resetTimerGPRS } +ID id-package-gprsTimer} + +gprsBillingPackage {PARAMETERS-BOUND : bound} OPERATION-PACKAGE ::= { +CONSUMER INVOKES {furnishChargingInformationGPRS {bound}} +ID id-package-gprsBilling} + +gprsChargingPackage OPERATION-PACKAGE ::= { +CONSUMER INVOKES {applyChargingGPRS} +SUPPLIER INVOKES {applyChargingReportGPRS} +ID id-package-gprsCharging} + +gprsChargeAdvicePackage {PARAMETERS-BOUND : bound} OPERATION-PACKAGE ::= { +CONSUMER INVOKES {sendChargingInformationGPRS {bound}} +ID id-package-gprsChargeAdvice} + +``` + +``` +gprsActivityTestPackage OPERATION-PACKAGE ::= { + CONSUMER INVOKES {activityTestGPRS} + ID id-package-gprsActivityTest} + +gprsCancelPackage OPERATION-PACKAGE ::= { + CONSUMER INVOKES {cancelGPRS } + ID id-package-gprsCancel} + +-- Abstract Syntaxes + +-- The ABSTRACT-SYNTAX definitions for CAP V3 for GPRS are updated in Rel-6. + +gprsSSF-gsmSCFAbstractSyntax ABSTRACT-SYNTAX ::= { + GenericGprsSSF-gsmSCF-PDUs + IDENTIFIED BY id-as-gprsSSF-gsmSCF-AS} +-- 'GenericGprsSSF-gsmSCF-PDUs' is defined in the present module. + +GenericGprsSSF-gsmSCF-PDUs ::= TCMessage {{GprsSsfToGsmScfInvokable}, + {GprsSsfToGsmScfReturnable}} +-- 'GprsSsfToGsmScfInvokable' and 'GprsSsfToGsmScfReturnable' are defined in the present module. + +GprsSsfToGsmScfInvokable OPERATION ::= { + activityTestGPRS | + applyChargingGPRS | + applyChargingReportGPRS | + cancelGPRS | + connectGPRS {cAPSpecificBoundSet} | + entityReleasedGPRS {cAPSpecificBoundSet} | + eventReportGPRS {cAPSpecificBoundSet} | + furnishChargingInformationGPRS {cAPSpecificBoundSet} | + initialDPGPRS {cAPSpecificBoundSet} | + releaseGPRS {cAPSpecificBoundSet} | + requestReportGPRSEvent {cAPSpecificBoundSet} | + resetTimerGPRS | + sendChargingInformationGPRS {cAPSpecificBoundSet}} + +GprsSsfToGsmScfReturnable OPERATION ::= { + activityTestGPRS | + applyChargingGPRS | + applyChargingReportGPRS | + cancelGPRS | + connectGPRS {cAPSpecificBoundSet} | + continueGPRS | + entityReleasedGPRS {cAPSpecificBoundSet} | + furnishChargingInformationGPRS {cAPSpecificBoundSet} | + initialDPGPRS {cAPSpecificBoundSet} | + releaseGPRS {cAPSpecificBoundSet} | + requestReportGPRSEvent {cAPSpecificBoundSet} | + resetTimerGPRS | + sendChargingInformationGPRS {cAPSpecificBoundSet}} + +gsmSCF-gprsSSFAbstractSyntax ABSTRACT-SYNTAX ::= { + GenericGsmSCF-gprsSSF-PDUs + IDENTIFIED BY id-as-gsmSCF-gprsSSF-AS} +-- 'GenericGsmSCF-gprsSSF-PDUs' is defined in the present module. + +GenericGsmSCF-gprsSSF-PDUs ::= TCMessage {{GsmScfToGprsSsfInvokable}, + {GsmScfToGprsSsfReturnable}} +-- 'GsmScfToGprsSsfInvokable' and 'GsmScfToGprsSsfReturnable' are defined in the present module. + +GsmScfToGprsSsfInvokable OPERATION ::= { + activityTestGPRS | + applyChargingGPRS | + cancelGPRS | + furnishChargingInformationGPRS {cAPSpecificBoundSet} | + releaseGPRS {cAPSpecificBoundSet} | + requestReportGPRSEvent {cAPSpecificBoundSet} | + sendChargingInformationGPRS {cAPSpecificBoundSet}} + +GsmScfToGprsSsfReturnable OPERATION ::= { + activityTestGPRS | + applyChargingGPRS | + cancelGPRS | + furnishChargingInformationGPRS {cAPSpecificBoundSet} | + releaseGPRS {cAPSpecificBoundSet} | + requestReportGPRSEvent {cAPSpecificBoundSet} | +``` + +``` +sendChargingInformationGPRS {cAPSpecificBoundSet} +``` + +``` +END +``` + +--- + +## 9 Application Entity procedures + +The description of the application entity procedures for CAMEL Phase 3 can be found in 3GPP TS 23.078 [7]. + +--- + +## 10 Error procedures + +The present clause specifies the generic error procedures for CAP. The error procedure descriptions are divided in two subclauses, subclause 10.1 listing the errors related to CAP Operations and subclause 10.2 listing the errors related to error conditions in the different FEs which are not directly related to the CAP Operations. + +The gsmSSF FSM states, smsSSF FSM states and gprsSSF FSM states which are referred to in the present clause are described in 3GPP TS 23.078 [7]. The CAP Operations PlayAnnouncement, PromptAndCollectUserInfoInformation and SpecializedResourceReport refer to states in the gsmSRF SRSM which are described in ETSI ETS 300 374-1 [24] as well as to states in 3GPP TS 23.078 [7]. + +### 10.1 Operation related error procedures + +The following subclauses specify the generic error handling for the CAP Operation related errors. The errors are defined as Operation Errors in clauses 6, 7 and 8. Errors which have a specific procedure for a CAP Operation are described in clause 11 with the detailed procedure of the related CAP Operation. + +The TC services which are used for reporting CAP Operation Errors are described in subclause 14.1. All Errors which can be detected by the ASN.1 decoder, already may have been detected during the decoding of the TC message and indicated by the TC error indication "MistypedParameter" in the TC-U-Reject. + +#### 10.1.1 Canceled + +##### 10.1.1.1 General Description + +###### 10.1.1.1.1 Error description + +The gsmSRF uses this Error to indicate" to the gsmSCF that the cancellation of a specific CAP Operation, as requested by the gsmSCF, has been successful. The only CAP Operations which may be cancelled are PlayAnnouncement and PromptAndCollectUserInfoInformation. + +##### 10.1.1.2 Operations gsmSCF & gsmSRF + +###### Procedures at responding entity (gsmSRF) + +###### A) Receiving Cancel + +Precondition: SRSM FSM state "User Interaction". +Postcondition: SRSM FSM state "User Interaction". + +If execution of the indicated CAP Operation has not yet started, then the indicated CAP Operation shall be removed from the buffer. If execution of the indicated CAP Operation is in progress, then the execution of that CAP Operation shall be terminated. If the indicated CAP Operation was already executed, then then this causes a failure ("CancelFailed"). + +###### B) Sending Error "Canceled" + +Precondition: SRSM FSM state "User Interaction". +Postcondition: SRSM FSM state "User Interaction". + +After returning the Error "Canceled", the gsmSRF FSM remains in the same state. The execution of the indicated PlayAnnouncement or PromptAndCollectUserInfoInformation CAP Operation is aborted. The gsmSRF shall remain + +connected and the next PlayAnnouncement or PromptAndCollectUserInfo CAP Operation, if available, shall be executed. + +## 10.1.2 CancelFailed + +### 10.1.2.1 General description + +#### 10.1.2.1.1 Error description + +The gsmSRF uses this Error to indicate to the gsmSCF that the cancellation of a specific CAP Operation, as requested by the gsmSCF, was not successful. Possible failure reasons are: + +- 0 "unknownOperation", when the InvokeID of the CAP Operation to cancel is not known to the gsmSRF (this may also happen when the CAP Operation has already been completed); +- 1 "tooLate", when the invokeID is known but the execution of the CAP Operation is in a state in which it cannot be canceled anymore. For instance the announcement is finished but the SpecializedResourceReport has not been sent to the gsmSCF yet. The conditions for the occurrence of failure reason "tooLate" are implementation dependent; +- 2 "operationNotCancellable", when the invokeID points to a CAP Operation that the gsmSCF is not allowed to cancel. + +### 10.1.2.2 Operations gsmSCF $\leftarrow$ gsmSRF + +#### Procedures at responding entity (gsmSRF) + +A) Receiving Cancel. However, the indicated CAP Operation is not known, or has already been executed or may not be cancelled. This causes a failure, "CancelFailed". + +Precondition: SRSM FSM state "User Interaction". + +Postcondition: SRSM FSM state "User Interaction" or +SRSM FSM state "Idle". + +B) Sending Error "CancelFailed" + +Precondition: SRSM FSM state "User Interaction" or +SRSM FSM state "Idle". + +Postcondition: SRSM FSM state "User Interaction" or +SRSM FSM state "Idle". + +After returning the Error "CancelFailed" the gsmSRF FSM remains in the same state. + +## 10.1.3 ETCFailed + +### 10.1.3.1 General description + +#### 10.1.3.1.1 Error description + +The gsmSSF uses this Error to indicate to the gsmSCF that the establishment of a temporary connection to an assisting gsmSSF or gsmSRF was not successful (e.g., receiving a "Backwards Release" after sending an ISUP IAM). + +### 10.1.3.2 Operations gsmSCF $\leftarrow$ gsmSSF + +#### Procedures at responding entity (gsmSSF) + +A gsmSSF receives EstablishTemporaryConnection from a gsmSCF but the establishment of the connection fails, which results in returning the Error "ETCFailed" to the gsmSCF. + +Precondition: gsmSSF FSM state "Waiting\_for\_Instructions". + +Postcondition: gsmSSF FSM state "Waiting\_for\_Instructions". + +No further error treatment. + +## 10.1.4 ImproperCallerResponse + +### 10.1.4.1 General description + +#### 10.1.4.1.1 Error description + +The gsmSRF uses this Error to indicate to the gsmSCF that the format of the user input has been checked by the gsmSRF, but does not correspond to the required format as it was defined in the initiating CAP Operation. + +### 10.1.4.2 Operations gsmSCF $\leftarrow$ gsmSRF + +#### Procedures at responding entity (gsmSRF) + +A) gsmSRF receives PromptAndCollectUserInformation + +Precondition: SRSM FSM state "Connected"; or +SRSM FSM state "User Interaction". + +Postcondition: SRSM FSM state "User Interaction". + +B) format of the user input is not correct, gsmSRF returns ImproperCallerResponse to gsmSCF + +Precondition: SRSM FSM state "User Interaction". + +Postcondition: SRSM FSM state "User Interaction". + +The gsmSRF shall wait for a new CAP Operation from the gsmSCF. This may be a new PromptAndCollectUserInformation or a PlayAnnouncement. + +## 10.1.5 MissingCustomerRecord + +### 10.1.5.1 General description + +#### 10.1.5.1.1 Error description + +The gsmSCF uses this Error to indicate to the gsmSSF, gprsSSF, smsSSF or gsmSRF, that the SLP could not be found in the gsmSCF, because the required customer record does not exist, or the requested SLPI, indicated by the correlationID in "AssistRequestInstructions" does not exist anymore. + +### 10.1.5.2 Operations gsmSSF $\leftarrow$ gsmSCF + +#### Procedures at invoking entity (gsmSSF) + +A) Sending CAP Operation + +Precondition: gsmSSF FSM state "Trigger processing" or +gsmSSF FSM state "Waiting\_for\_Instructions"; in the assisting gsmSSF case. + +Postcondition: gsmSSF FSM state "Waiting\_for\_Instructions". +gsmSSF FSM state "Waiting\_for\_Instructions"; in the assisting gsmSSF case. + +B) gsmSSF receives Error "MissingCustomerRecord" + +Precondition: gsmSSF FSM state "Waiting\_for\_Instructions" or +gsmSSF FSM state "Waiting\_for\_Instructions"; in the assisting gsmSSF case. + +Postcondition: gsmSSF FSM state "Idle" or +gsmSSF FSM state "Idle"; in the assisting gsmSSF case. + +The GMSC or VMSC shall handle the call in accordance with the Default Call Handling parameter of the valid CSI. + +### 10.1.5.3 Operations gsmSRF $\leftarrow$ gsmSCF + +#### Procedures at invoking entity (gsmSRF) + +##### A) Sending CAP Operation + +Precondition: SRSM FSM state "Connected". + +Postcondition: SRSM FSM state "Connected". + +##### B) gsmSRF receives Error "MissingCustomerRecord" + +Precondition: SRSM FSM state "Connected". + +Postcondition: SRSM FSM state "Idle". + +The gsmSRF shall initiate a Disconnect. + +### 10.1.5.4 Operations smsSSF $\leftarrow$ gsmSCF + +#### Procedures at invoking entity (smsSSF) + +##### A) Sending CAP Operation + +Precondition: smsSSF FSM state "Waiting\_for\_Instructions". + +Postcondition: smsSSF FSM state "Waiting\_for\_Instructions". + +##### B) smsSSF receives Error "MissingCustomerRecord" + +Precondition: smsSSF FSM state "Waiting\_for\_Instructions". + +Postcondition: smsSSF FSM state "Idle". + +The VMSC or SGSN shall handle the Short Message in accordance with the Default SMS Handling parameter of the valid CSI. + +### 10.1.5.5 Operations gprsSSF $\leftarrow$ gsmSCF + +#### Procedures at invoking entity (gprsSSF) + +##### A) Sending CAP Operation + +Precondition: gprsSSF FSM state "Waiting\_for\_Instructions". + +Postcondition: gprsSSF FSM state "Waiting\_for\_Instructions". + +##### B) gprsSSF receives Error "MissingCustomerRecord" + +Precondition: gprsSSF FSM state "Waiting\_for\_Instructions". + +Postcondition: gprsSSF FSM state "Idle". + +The SGSN shall handle the GPRS Session or PDP Context in accordance with the Default GPRS Handling parameter of the valid CSI. + +## 10.1.6 MissingParameter + +### 10.1.6.1 General description + +#### 10.1.6.1.1 Error description + +The gsmSCF, gsmSSF, gsmSRF, smsSSF or gprsSSF uses this Error to indicate that there is an error in the received CAP Operation argument. The responding entity cannot start the execution of the requested CAP Operation because the argument is incorrect: an expected optional parameter which is essential for the application is not included in the CAP Operation argument. + +### 10.1.6.2 Operations gsmSCF $\leftarrow$ gsmSSF + +#### Procedures at responding entity (gsmSSF) + +Precondition: (1) gsmSSF FSM appropriate state + (2) gsmSSF FSM Call associated CAP Operation received, appropriate event occurred + (3) gsmSSME FSM appropriate state + (4) gsmSSME FSM Non call associated CAP Operation received, appropriate event + +Postcondition: (1) No gsmSSF FSM transition + (2) gsmSSME FSM transition to the initial state (i.e., before receiving the erroneous CAP Operation) + +The gsmSSF detects the error in the received CAP Operation. The Error parameter "MissingParameter" is returned to inform the gsmSCF of this situation. + +### 10.1.6.3 Operations gsmSSF $\leftarrow$ gsmSCF + +#### Procedures at invoking entity (gsmSSF) + +##### A) Sending CAP Operation + +Precondition: gsmSSF FSM appropriate state + +Postcondition: gsmSSF FSM appropriate state as result of the transfer of the CAP Operation + +##### B) gsmSSF receives Error "MissingParameter" + +Precondition: gsmSSF FSM appropriate state as result of the transfer of any of the CAP Operation + +Postcondition: gsmSSF FSM state "Idle" + +After receiving this Error, the gsmSSF FSM shall return to the state "Idle". The GMSC or VMSC shall handle the call in accordance with the Default Call Handling parameter, valid for this CAMEL dialogue. In the case of an assisting gsmSSF, the temporary connection shall be released by the assisting gsmSSF. + +### 10.1.6.4 Operations gsmSCF $\leftarrow$ gsmSRF + +#### Procedures at responding entity (gsmSRF) + +Precondition: SRSM FSM state "Connected"; or + SRSM FSM state "User Interaction". + +Postcondition: SRSM FSM state "User Interaction". + +The SRSM detects that a required parameter is not present in the CAP Operation argument. The Error parameter "MissingParameter" is returned to inform the gsmSCF of this situation. + +### 10.1.6.5 Operations gsmSRF $\leftarrow$ gsmSCF + +#### Procedures at invoking entity (gsmSRF) + +##### A) Sending CAP Operation + +Precondition: SRSM FSM state "Connected". + +Postcondition: SRSM FSM state "Connected". + +##### B) Receiving Error + +Precondition: SRSM FSM state "Connected". + +Postcondition: SRSM FSM state "Idle". + +The gsmSCF detects the error in the received CAP Operation. The Error parameter "MissingParameter" is used to inform the gsmSRF of this situation. The SL and maintenance functions are informed. The gsmSCF might try another gsmSRF, route the call or release the call (SL dependent). + +### 10.1.6.6 Operations smsSSF $\leftarrow$ gsmSCF + +#### Procedures at invoking entity (smsSSF) + +##### A) Sending CAP Operation + +Precondition: smsSSF FSM state "WaitingForInstructions". + +Postcondition: smsSSF FSM state "WaitingForInstructions". + +##### B) Receiving Error + +Precondition: smsSSF FSM state "WaitingForInstructions". + +Postcondition: smsSSF FSM state "Idle". + +After receiving this error, the smsSSF FSM shall transit to the state "Idle". The SGSN or VMSC shall handle the Short Message in accordance with the Default SMS Handling parameter of the valid CSI. + +### 10.1.6.7 Operations gsmSCF $\leftarrow$ smsSSF + +#### Procedures at responding entity (smsSSF) + +precondition: + +- (1) smsSSF appropriate state. +- (2) smsSSF SMS associated CAP Operation received, appropriate event occurred. + +postcondition: + +- (1) smsSSF transition to the same state. + +The smsSSF detects the error in the received CAP Operation. The Error parameter "MissingParameter" is returned to inform the gsmSCF of this situation. + +### 10.1.6.8 Operations gprsSSF $\leftarrow$ gsmSCF + +#### Procedures at invoking entity (gprsSSF) + +##### A) Sending CAP Operation + +Precondition: gprsSSF FSM state "Waiting\_for\_Instructions". + +Postcondition: gprsSSF FSM state "Waiting\_for\_Instructions". + +##### B) Receiving Error + +Precondition: gprsSSF FSM state "Waiting\_for\_Instructions". + +Postcondition: gprsSSF FSM state "Idle". + +After receiving this error, the gprsSSF FSM shall transits to the state "Idle". The SGSN shall handle the GPRS Session or PDP Context in accordance with the Default GPRS Handling parameter of the valid CSI. + +### 10.1.6.9 Operations gsmSCF $\leftarrow$ gprsSSF + +#### Procedures at responding entity (gprsSSF) + +precondition: + +- (1) gprsSSF appropriate state. +- (2) gprsSSF CAP Operation received, appropriate event occurred. + +postcondition: + +(1) gprsSSF transition to the same state. + +The gprsSSF detects the error in the received CAP Operation. The Error parameter "MissingParameter" is returned to inform the gsmSCF of this situation. + +## 10.1.7 ParameterOutOfRange + +### 10.1.7.1 General description + +#### 10.1.7.1.1 Error description + +The gsmSCF, gsmSSF, gsmSRF, smsSSF or gprsSSF uses this Error to indicate that it cannot start the execution of the requested CAP Operation because an error in a parameter of the CAP Operation argument is detected: a parameter value is out of range. + +#### 10.1.7.2 Operations gsmSCF $\leftarrow$ gsmSSF + +Refer to subclause 10.1.6 MissingParameter for the appropriate error procedures. + +#### 10.1.7.3 Operations gsmSSF $\leftarrow$ gsmSCF + +Refer to subclause 10.1.6 MissingParameter for the appropriate error procedures. + +#### 10.1.7.4 Operations gsmSCF $\leftarrow$ gsmSRF + +Refer to subclause 10.1.6 MissingParameter for the appropriate error procedures. + +#### 10.1.7.5 Operations smsSSF $\leftarrow$ gsmSCF + +Refer to subclause 10.1.6 MissingParameter for the appropriate error procedures. + +#### 10.1.7.6 Operations gsmSCF $\leftarrow$ smsSSF + +Refer to subclause 10.1.6 MissingParameter for the appropriate error procedures. + +#### 10.1.7.7 Operations gprsSSF $\leftarrow$ gsmSCF + +Refer to subclause 10.1.6 MissingParameter for the appropriate error procedures. + +#### 10.1.7.8 Operations gsmSCF $\leftarrow$ gprsSSF + +Refer to subclause 10.1.6 MissingParameter for the appropriate error procedures. + +## 10.1.8 RequestedInfoError + +### 10.1.8.1 General description + +#### 10.1.8.1.1 Error description + +The gsmSSF uses this Error to indicate to the gsmSCF that the information requested in the CallInformationRequest CAP Operation is not known to the gsmSSF or is not available. + +#### 10.1.8.2 Operations gsmSCF $\leftarrow$ gsmSSF + +Refer to subclause 10.1.6 MissingParameter for the appropriate error procedures. + +## 10.1.9 SystemFailure + +### 10.1.9.1 General description + +#### 10.1.9.1.1 Error description + +The gsmSCF, gsmSSF, gsmSRF, smsSSF or gprsSSF uses this error to indicate that it is not able to execute a specific task as requested by a CAP Operation, and recovery is not expected to be completed within the current call instance. + +#### 10.1.9.2 Operations gsmSCF ⌂ gsmSSF + +Refer to subclause 10.1.6 MissingParameter for the appropriate error procedures. + +#### 10.1.9.3 Operations gsmSSF ⌂ gsmSCF + +Refer to subclause 10.1.6 MissingParameter for the appropriate error procedures. + +#### 10.1.9.4 Operations gsmSCF ⌂ gsmSRF + +Refer to subclause 10.1.6 MissingParameter for the appropriate error procedures. + +#### 10.1.9.5 Operations gsmSRF ⌂ gsmSCF + +Refer to subclause 10.1.6 MissingParameter for the appropriate error procedures. + +#### 10.1.9.6 Operations smsSSF ⌂ gsmSCF + +Refer to subclause 10.1.6 MissingParameter for the appropriate error procedures. + +#### 10.1.9.7 Operations gsmSCF ⌂ smsSSF + +Refer to subclause 10.1.6 MissingParameter for the appropriate error procedures. + +#### 10.1.9.8 Operations gprsSSF ⌂ gsmSCF + +Refer to subclause 10.1.6 MissingParameter for the appropriate error procedures. + +#### 10.1.9.9 Operations gsmSCF ⌂ gprsSSF + +Refer to subclause 10.1.6 MissingParameter for the appropriate error procedures. + +## 10.1.10 TaskRefused + +### 10.1.10.1 General description + +#### 10.1.10.1.1 Error description + +The gsmSCF, gsmSSF, gsmSRF, smsSSF or gprsSSF uses this Error to indicate that it is not able to execute a specific task as requested by a CAP Operation, and recovery is expected to be completed within the current call instance. + +If the gsmSSF requests MoveLeg or SplitLeg operations in the gsmSSF while user interaction is in progress in an affected Call Segment, then CAP\_Error (task refused) is returned. + +#### 10.1.10.2 Operations gsmSCF ⌂ gsmSSF + +Refer to subclause 10.1.6 MissingParameter for the appropriate error procedures. + +#### 10.1.10.3 Operations gsmSSF ⌂ gsmSCF + +Refer to subclause 10.1.6 MissingParameter for the appropriate error procedures. + +#### 10.1.10.4 Operations gsmSCF $\leftarrow$ gsmSRF + +Refer to subclause 10.1.6 MissingParameter for the appropriate error procedures. + +#### 10.1.10.5 Operations gsmSRF $\leftarrow$ gsmSCF + +Refer to subclause 10.1.6 MissingParameter for the appropriate error procedures. + +#### 10.1.10.6 Operations smsSSF $\leftarrow$ gsmSCF + +Refer to subclause 10.1.6 MissingParameter for the appropriate error procedures. + +#### 10.1.10.7 Operations gsmSCF $\leftarrow$ smsSSF + +##### **SMS Related** + +Refer to subclause 10.1.6 MissingParameter for the appropriate error procedures. + +#### 10.1.10.8 Operations gprsSSF $\leftarrow$ gsmSCF + +Refer to subclause 10.1.6 MissingParameter for the appropriate error procedures. + +#### 10.1.10.9 Operations gsmSCF $\leftarrow$ gprsSSF + +Refer to subclause 10.1.6 MissingParameter for the appropriate error procedures. + +### 10.1.11 UnavailableResource + +#### 10.1.11.1 General description + +##### 10.1.11.1.1 Error description + +The gsmSRF uses this Error to indicate to the gsmSCF that it is not able to perform its function (i.e., play a certain announcement and/or collect specific user information), and cannot be replaced. A reattempt is not possible. + +#### 10.1.11.2 Operations gsmSCF $\leftarrow$ gsmSRF + +##### **Procedures at responding entity (gsmSRF)** + +A) gsmSRF receiving PlayAnnouncement or PromptAndCollectUserInfoInformation + +Precondition: SRSM FSM state "Connected"; if initial PlayAnnouncement or PromptAndCollectUserInfoInformation; or +SRSM FSM state "User Interaction"; if not initial PlayAnnouncement or PromptAndCollectUserInfoInformation. + +B) gsmSRF is not able to perform its function (and cannot be replaced). The gsmSRF sends the Error "UnavailableResource". + +Precondition: SRSM FSM state "User Interaction". + +Postcondition: SRSM FSM state "User Interaction". + +### 10.1.12 UnexpectedComponentSequence + +#### 10.1.12.1 General description + +##### 10.1.12.1.1 Error description + +The gsmSCF, gsmSSF, gsmSRF, smsSSF or gprsSSF uses this Error to indicate that it cannot start the execution of the requested CAP Operation because a SACF or MACF rule is violated, or the CAP Operation cannot be executed in the current state of the FSM. + +### 10.1.12.2 Operations gsmSCF ← gsmSSF + +In this case the gsmSSF detects the erroneous situation, sends the Error "UnexpectedComponentSequence" and remains in the same state. + +### 10.1.12.3 Operations gsmSSF ← gsmSCF + +If the CAP Operation is sent by an "initiating" gsmSSF in the context of an existing relationship, then the gsmSCF returns the Error parameter. On receiving the error the gsmSSF FSM shall transit to the state "Idle". The VMSC or GMSC shall handle the call in accordance with the Default Call Handling parameter, valid for this CAMEL dialogue. + +### 10.1.12.4 Operations gsmSCF ← gsmSRF (applicable for direct gsmSCF-gsmSRF case only) + +In this case the gsmSRF detects the erroneous situation, sends the Error "UnexpectedComponentSequence" and remains in the same state. + +### 10.1.12.5 Operations gsmSRF ← gsmSCF + +In this case, an error occurs if the gsmSRF has already an established relationship with the gsmSCF and sends the CAP Operation AssistRequestInstructions. The gsmSCF detects the erroneous situation, informs SL and maintenance functions and returns the error parameter. On receiving the Error parameter, the gsmSRF FSM shall transit to the state "Idle" and releases the temporary connection. + +### 10.1.12.6 Operations smsSSF ← gsmSCF + +If the CAP Operation is sent by the smsSSF in the context of an existing relationship, then the gsmSCF returns the Error parameter. On receiving the error, the smsSSF FSM shall transit to the state "Idle". The SGSN or VMSC shall handle the Short Message in accordance with the Default SMS Handling parameter of the valid CSI. + +### 10.1.12.7 Operations gsmSCF ← smsSSF + +In this case the smsSSF detects the erroneous situation, sends the Error "UnexpectedComponentSequence" and remains in the same state. + +### 10.1.12.8 Operations gprsSSF ← gsmSCF + +If the CAP Operation is sent by the gprsSSF in the context of an existing relationship, then the gsmSCF returns the Error parameter. On receiving the error, the gprsSSF FSM shall transit to the state "Idle". The SGSN shall handle the GPRS Session or PDP Context in accordance with the Default GPRS Handling parameter of the valid CSI. + +### 10.1.12.9 Operations gsmSCF ← gprsSSF + +In this case the gprsSSF detects the erroneous situation, sends the Error "UnexpectedComponentSequence" and remains in the same state. + +## 10.1.13 UnexpectedDataValue + +### 10.1.13.1 General description + +#### 10.1.13.1.1 Error description + +The gsmSCF, gsmSSF, gsmSRF, smsSSF or gprsSSF uses this Error to indicate that it cannot execute the requested CAP Operation because a parameter has an unexpected data value. + +Note that this error does not overlap with "ParameterOutOfRange". + +EXAMPLE:    startTime DateAndTime ::= -- value indicating January 32 1993, 12: 15: 01 + +The responding entity does not expect this value and responds with Error "UnexpectedDataValue". + +### 10.1.13.2 Operations gsmSCF $\Leftarrow$ gsmSSF + +Refer to subclause 10.1.6 MissingParameter for the appropriate error procedures. + +### 10.1.13.3 Operations gsmSSF $\Leftarrow$ gsmSCF + +Refer to subclause 10.1.6 MissingParameter for the appropriate error procedures. + +### 10.1.13.4 Operations gsmSCF $\Leftarrow$ gsmSRF + +Refer to subclause 10.1.6 MissingParameter for the appropriate error procedures. + +### 10.1.13.5 Operations gsmSRF $\Leftarrow$ gsmSCF + +Refer to subclause 10.1.6 MissingParameter for the appropriate error procedures. + +### 10.1.13.6 Operations smsSSF $\Leftarrow$ gsmSCF + +Refer to subclause 10.1.6 MissingParameter for the appropriate error procedures. + +### 10.1.13.7 Operations gsmSCF $\Leftarrow$ smsSSF + +Refer to subclause 10.1.6 MissingParameter for the appropriate error procedures. + +### 10.1.13.8 Operations gprsSSF $\Leftarrow$ gsmSCF + +Refer to subclause 10.1.6 MissingParameter for the appropriate error procedures. + +### 10.1.13.9 Operations gsmSCF $\Leftarrow$ gprsSSF + +Refer to subclause 10.1.6 MissingParameter for the appropriate error procedures. + +## 10.1.14 UnexpectedParameter + +### 10.1.14.1 General description + +#### 10.1.14.1.1 Error description + +The gsmSCF, gsmSSF, gsmSRF, smsSSF or gprsSSF uses this Error to indicate that there is an error in the received CAP Operation argument. A valid but unexpected parameter was present in the CAP Operation argument. The presence of this parameter is not consistent with the presence of the other parameters. The responding entity cannot start the execution of the CAP Operation. + +### 10.1.14.2 Operations gsmSCF $\Leftarrow$ gsmSSF + +Refer to subclause 10.1.6 MissingParameter for the appropriate error procedures. + +### 10.1.14.3 Operations gsmSSF $\Leftarrow$ gsmSCF + +Refer to subclause 10.1.6 MissingParameter for the appropriate error procedures. + +### 10.1.14.4 Operations gsmSCF $\Leftarrow$ gsmSRF + +Refer to subclause 10.1.6 MissingParameter for the appropriate error procedures. + +### 10.1.14.5 Operations gsmSRF $\Leftarrow$ gsmSCF + +Refer to subclause 10.1.6 MissingParameter for the appropriate error procedures. + +### 10.1.14.6 Operations smsSSF $\Leftarrow$ gsmSCF + +Refer to subclause 10.1.6 MissingParameter for the appropriate error procedures. + +#### 10.1.14.7 Operations gsmSCF ⌚ smsSSF + +Refer to subclause 10.1.6 MissingParameter for the appropriate error procedures. + +#### 10.1.14.8 Operations gprsSSF ⌚ gsmSCF + +Refer to subclause 10.1.6 MissingParameter for the appropriate error procedures. + +#### 10.1.14.9 Operations gsmSCF ⌚ gprsSSF + +Refer to subclause 10.1.6 MissingParameter for the appropriate error procedures. + +### 10.1.15 UnknownLegID + +#### 10.1.15.1 General description + +##### 10.1.15.1.1 Error description + +The gsmSSF uses this error to indicate to the gsmSCF that a specific leg, indicated by the LegID parameter value in the CAP Operation, is unknown to the gsmSSF. + +#### 10.1.15.2 Operations gsmSCF ⌚ gsmSSF + +Refer to subclause 10.1.6 MissingParameter for the appropriate error procedures. + +### 10.1.16 UnknownCSID + +#### 10.1.16.1 General description + +##### 10.1.16.1.1 Error description + +The gsmSSF uses this error to indicate to the gsmSCF that a specific Call Segment, indicated by the callSegmentID parameter value in the CAP Operation, is unknown to the gsmSSF. + +#### 10.1.16.2 Operations gsmSCF ⌚ gsmSSF + +Refer to subclause 10.1.6 MissingParameter for the appropriate error procedures. + +### 10.1.17 UnknownPDPID + +#### 10.1.17.1 General description + +##### 10.1.17.1.1 Error description + +The gsmSCF or gprsSSF uses this error to indicate that a specific PDP Context, indicated by the PDPIId parameter value in the CAP Operation argument, is unknown to the receiving entity. + +#### 10.1.17.2 Operations gprsSSF ⌚ gsmSCF + +Refer to subclause 10.1.6 MissingParameter for the appropriate error procedures. + +#### 10.1.17.3 Operations gsmSCF ⌚ gprsSSF + +Refer to subclause 10.1.6 MissingParameter for the appropriate error procedures. + +## 10.2 Entity related error procedures + +The following subclauses specify the error handling procedures for the Functional Entity related errors. Since the error situations are not originated by the reception of a CAP Operation, the invoking entity is denoted here as the entity at which the error situation is detected. The responding entity is the entity which receives the error report. + +The TC services used for reporting errors are described in clause 14. + +## 10.2.1 Expiration of Tssf + +### 10.2.1.1 General description + +#### 10.2.1.1.1 Error description + +A timeout has occurred in the gsmSSF, gprsSSF, smsSSF or assisting gsmSSF on the response from the gsmSCF. + +#### 10.2.1.2 Procedures gsmSSF $\leftarrow$ gsmSCF + +##### Procedure at the invoking entity (gsmSSF or assisting gsmSSF) + +Timeout occurs in gsmSSF on Tssf. + +Precondition: gsmSSF FSM state "Waiting\_for\_Instructions"; or + gsmSSF FSM state "Waiting\_for\_end\_of\_User\_Interaction"; or + gsmSSF FSM state "Waiting\_for\_end\_of\_Temporary\_Connection". + +Postcondition: gsmSSF FSM state "Idle". + +The gsmSSF shall abort the TC dialogue and shall transit to the state "Idle". The GMSC or VMSC shall handle the call in accordance with the Default Call Handling parameter, valid for this CAMEL dialogue. For CAMEL dialogues that are established as a result of a CSI, the Default Call Handling parameter is obtained from the CSI. For gsmSCF initiated CAMEL dialogues, the Default Call Handling parameter shall be "ReleaseCall". + +The assisting gsmSSF shall abort the TC dialogue and shall transit to the state "Idle". The assisting gsmSSF shall release the temporary connection. + +#### 10.2.1.3 Procedures gprsSSF $\leftarrow$ gsmSCF + +##### Procedure at the invoking entity (gprsSSF) + +Timeout occurs in gprsSSF on Tssf. + +Precondition: gprsSSF FSM state "Waiting\_for\_Instructions". + +Postcondition: gprsSSF FSM state "Idle". + +The gprsSSF shall abort the TC dialogue and and the GPRS dialogue and shall transit to the state "Idle". The SGSN shall handle the PDP Context in accordance with the Default GPRS Handling parameter of the valid CSI. + +#### 10.2.1.4 Procedures smsSSF $\leftarrow$ gsmSCF + +##### Procedure at the invoking entity (smsSSF) + +Timeout occurs in smsSSF on Tssf. + +Precondition: smsSSF FSM state "Waiting\_for\_Instructions". + +Postcondition: smsSSF FSM state "Idle". + +The smsSSF shall abort the TC dialogue and shall transit to the state "Idle". The MSC or SGSN shall handle the Short Message in accordance with the Default SMS Handling parameter of the valid CSI. + +## 10.2.2 Expiration of Tsrf + +### 10.2.2.1 General Description + +#### 10.2.2.1.1 Error description + +A timeout has occurred in the gsmSRF on the response from the gsmSCF. The procedures for handling this error are described in ETSI ETS 300 374-1 [24]. + +## 10.2.2.2 Procedures description + +The procedures for handling this error are described in ETSI ETS 300 374-1 [24]. + +--- + +# 11 Detailed operation procedures for circuit switched call control + +NOTE: The detailed operation procedures in the present clause which cross reference the gsmSCF FSMs for the pre- and postconditions are for information only. + +NOTE: Where a parameter for a circuit switched call control Operation is marked OPTIONAL in ASN.1, the reader is referred to the conditions for presence for this parameter, specified in the respective Information Flow in 3GPP TS 23.078 [7]. + +## 11.1 ActivityTest procedure + +### 11.1.1 General description + +The gsmSCF uses this operation to check for the continued existence of a relationship between the gsmSCF and the gsmSSF, between the gsmSCF and the gsmSRF or between the gsmSCF and the assist gsmSSF. If the relationship is still in existence, then the receiving entity will respond If the ActivityTest operation timer expires, then the gsmSCF will assume that the receiving entity has failed in some way and will take appropriate action. + +#### 11.1.1.1 Parameters + +None. + +### 11.1.2 Responding entity (gsmSSF, gsmSRF or assist gsmSSF) + +#### 11.1.2.1 Normal procedure + +gsmSSF preconditions: + +- (1) A relationship exists between the gsmSCF and the gsmSSF. +- (2) The gsmSSME FSM is in the state "Idle Management" or in the state "Non-call Associated Treatment". + +gsmSRF or assist gsmSSF preconditions: + +- (1) A relationship exists between the gsmSCF and the gsmSRF or assist gsmSSF. +- (2) The gsmSSME FSM is in the state "Idle Management". + +gsmSSF postconditions: + +- (1) The gsmSSME FSM stays in, or transits to the state "Non-call Associated Treatment". +- (2) If the TC Dialogue ID is active and there is a gsmSSF using the dialogue, then the gsmSSME FSM shall send a Return Result "ActivityTest" to the gsmSCF. If there are no other management activities (e.g. Call Gapping), then the gsmSSME FSM shall transit to the state "Idle Management". Otherwise, the gsmSSME FSM remains in the state "Non-call Associated Treatment". + +If the TC Dialogue ID is not active, then the TC in the gsmSSF will issue a P-Abort. The gsmSSME FSM will in that case not receive the "ActivityTest" indication and thus will not be able to reply. + +gsmSRF or assist gsmSSF postconditions: + +- (1) The gsmSSME FSM transits to the state "Non-call Associated Treatment". +- (2) If the TC Dialogue ID is active and there is a gsmSRF or assist gsmSSF using the dialogue, then the gsmSSME FSM shall send a Return Result "ActivityTest" to the gsmSCF. The gsmSSME FSM then returns to the state "Idle Management". + +If the TC Dialogue ID is not active, then the TC in the gsmSRF or assist gsmSSF will issue a P-Abort. The gsmSSME FSM will in that case not receive the ActivityTest indication and thus will not be able to reply. + +### 11.1.2.2 Error handling + +Operation related error handling is not applicable, due to class 3 operation. + +## 11.2 ApplyCharging procedure + +### 11.2.1 General description + +The gsmSCF uses this operation for interacting with the gsmSSF function: "CSE control of call duration". The ApplyChargingReport operation provides the feedback from the gsmSSF to the gsmSCF. + +The charging scenarios supported by this operation are those given in 3GPP TS 22.078 [3] for "CSE control of call duration". + +#### 11.2.1.1 Parameters + +- aChBillingChargingCharacteristics: + +This parameter specifies a list of parameters required for "CSE control of call duration": + +The list may contain the following parameters: + +- timeDurationCharging: + +This list contains the following parameters: + +- maxCallPeriodDuration: +This parameter specifies the period of time for which a call may progress before an ApplyChargingReport shall be sent to the gsmSCF. +- releaseIfDurationExceeded: +This parameter specifies the action to be taken at the gsmSSF when the duration specified above has been reached. +- audibleIndicator: +This parameter indicates to the gsmSSF that an audible indicator may be played to the served subscriber. This audible indicator may either be a predefined sequence of tones or a sequence defined by the gsmSCF. This parameter shall consist of either tone or burstlist as described below: + - tone: +This parameter indicates that a warning tone shall be played when the pre-defined warning tone timer expires. + - burstlist: +This parameter indicates that a variable sequence of tones shall be played when the gsmSCF-defined warning tone timer expires. This parameter may consist of the following parameters: + - c) - burst: +This parameter indicates the number of bursts that form the burstlist. + - d) - burstInterval: +This parameter indicates the time interval between the successive burst in the burstlist. + - e) - toneInBurst: +This parameter indicates the number of tones to be played in each burst. + - f) - toneDuration: +This parameter indicates the time duration that the tone shall be played for. + +g) - toneInterval: + +This parameter indicates the time interval between successive tones in a burst + +- tariffSwitchInterval (for the CSE control of call duration): + +This parameter indicates the time duration until the next tariff switch for the CSE control of call duration. The measurement of the elapsed tariff switch period shall start immediately after successful execution of this operation. + +- partyToCharge: + +This parameter indicates the party in the call. + +- aChChargingAddress: + +This parameter identifies the call party to which the ApplyCharging operation applies. That is the leg or srfConnection. + +This parameter is a choice of one of the following parameters: + +- legID: + +This parameter indicates that the "CSE control of call duration" is associated to the specified leg. + +or + +- srfConnection: + +This parameter indicates that the "CSE control of call duration" is associated to the Temporary Connection or to the connection to a gsmSRF. + +## 11.2.2 Responding entity (gsmSSF) + +### 11.2.2.1 Normal procedure + +gsmSSF preconditions: + +- (1) A control relationship exists between the gsmSCF and the gsmSSF. +- (2) The gsmSSF FSM is in one of the following states: + +"Waiting\_for\_Instructions"; or +"Waiting\_for\_end\_of\_User\_Interaction"; or +"Waiting\_for\_end\_of\_Temporary\_Connection"; or +"Monitoring". + +gsmSSF postconditions: + +- (1) No gsmSSF FSM state transition. + +On receipt of this operation, the gsmSSF sets the charging data using the information elements included in the operation and acts accordingly. + +If the aChChargingAddress indicates a legID, then: + +The "CSE control of call duration" is associated to the specified leg. If Answer has not already been received on the incoming or outgoing connection (leg) to the Call Party, then the gsmSSF shall start monitoring for the Answer event upon receipt of the ApplyCharging operation. Upon subsequent detection of the Answer event on the outgoing connection charging is started. If the Answer event has occurred on the incoming or outgoing connection already when the ApplyCharging operation is received, then charging starts immediately. + +A precautionary started DELTA measurement shall be taken into account when charging is started. + +For a change in the connection configuration of the legs - on CPH - the particular point in time when the new connection configuration is established shall be taken as Answer time. + +Upon release of the incoming or outgoing connection to the Call Party any indication of Answer event occurred on the incoming or outgoing connection shall be cleared, i.e. set to "Answer event not occurred". + +If the aChChargingAddress indicates a srfConnection, then: + +The "CSE control of call duration" is associated to the Temporary Connection or to the connection to a gsmSRF. If Answer has not already been received on the Temporary Connection, then the gsmSSF will start monitoring for the Answer event upon receipt of the ApplyCharging operation; or, if the gsmSRF is not yet connected, then the gsmSSF will start monitoring for a connection to a gsmSRF. Upon subsequent detection of the Answer event on the Temporary Connection or the subsequent connection to a gsmSRF, charging shall be started. If the Answer event has been received from a Temporary Connection already or if the gsmSRF is already connected when the ApplyCharging operation is received, then charging shall start immediately. + +Upon release of the Temporary Connection any indication of Answer event receipt on the outgoing connection shall be cleared i.e. set to "Answer event not received". Upon end of the connection to a gsmSRF, any indication of the connection to the gsmSRF shall be cleared. + +### 11.2.2.2 Error handling + +"TaskRefused": In addition to the generic error handling noted below, this error shall be indicated when: + +- a previously received call period duration is pending for this leg or srfConnection; +- a tariffSwitchInterval for the "CSE control of call duration" is indicated when a previously received tariffSwitchInterval for the "CSE control of call duration" is pending for the Called Party, the Temporary Connection or the connection to a gsmSRF. + +Generic error handling for the operation related errors is described in clause 10 and the TC services used for reporting operation errors are described in clause 14. + +## 11.3 ApplyChargingReport procedure + +### 11.3.1 General description + +The gsmSSF uses this operation to report charging related information to the gsmSCF as requested by the gsmSCF using the "ApplyCharging" operation. + +For a change in a connection configuration of the legs – on CPH – this operation shall be sent as an indication towards the gsmSCF that the supervision of that part of the connection is finished; i.e. + +- (i) the gsmSCF shall settle the account using the reported duration and +- (ii) the durations reported for subsequent AC/ACR cycles will not be accumulated to the reported duration. + +If Answer is detected by the gsmSSF, then timing of duration shall be started as requested by the ApplyCharging operation. It shall be started independently for a connection to a Called Party, a Temporary Connection and a gsmSRF connection. + +The charging report shall be generated as specified in the 3GPP TS 23.078 [7]. + +The tariff switch mentioned in the following subclause is the tariff switch for "CSE control of call duration" for the connection to which the ApplyChargingReport procedure applies. + +#### 11.3.1.1 Parameters + +- callResult: +This parameter provides the gsmSCF with the charging related information previously requested using the ApplyCharging operation. The "CallResult" is a list and may contain the following parameters: + - timeDurationChargingResult: +This parameter is a list, and can contain the following parameters: + - timeInformation: +This parameter is a choice of the following parameters: + - timeIfNoTariffSwitch: +This parameter shall be present if no tariff switch has occurred since the reception of the first ApplyCharging operation for the connection to the Called Party, Temporary Connection or gsmSRF connection, otherwise it shall be absent. +If Answer was detected for the connection to the Called Party, the Temporary Connection or the gsmSRF connection, then the elapsed time since detection of Answer shall be reported. If answer was + +not detected, then it shall be set to "0". + +For a change in the connection configuration of the legs - on CPH - the particular point in time when the new connection configuration is established shall be taken as Answer time. + +- timeIfTariffSwitch: + +This parameter shall be present if a tariff switch has occurred since the reception of the first ApplyCharging operation for the connection to the Called Party, Temporary Connection or gsmSRF connection, otherwise it shall be absent. + +The parameter may contain the following information: + +h) - timeSinceLastTariffSwitch: + +If Answer was detected for the connection to the Called Party, the Temporary Connection or the gsmSRF connection, then the elapsed time since detection of Answer or the last tariff switch (whichever of these events was last detected) shall be reported. If Answer was not detected, then it shall be set to "0". + +For a change in the connection configuration of the legs - on CPH - the particular point in time when the new connection configuration is established shall be taken as Answer time. + +i) - TariffSwitchInterval (for the "CSE control of call duration"): + +This parameter is present only if a tariff switch has occurred since the detection of Answer for the connection to the Called Party, the temporary connection or the gsmSRF connection in the reported call period. + +The time interval between either the detection of the Answer event or the previous tariff switch (whichever of these events was last detected) and the last tariff switch is reported. + +For a change in the connection configuration of the legs - on CPH - the particular point in time when the new connection configuration is established shall be taken as Answer time. + +- partyToCharge: + +The "partyToCharge" parameter as received in the related ApplyCharging operation or deduced from the default value. This parameter is used by the gsmSCF, to correlate the result to the request. + +- aChChargingAddress: + +The "aChChargingAddress" parameter as received in the related ApplyCharging operation or deduced from the default value. This parameter is used by the gsmSCF, to correlate the result to the request. + +- legActive: + +This parameter indicates whether the leg, the Temporary Connection or the connection to a gsmSRF is still active or has been released. + +- callLegReleasedAtTcpExpiry: + +This parameter indicates that the gsmSSF has released the call leg or the Temporary Connection or SRF connection + +## 11.3.2 Invoking entity (gsmSSF) + +### 11.3.2.1 Normal procedure + +gsmSSF preconditions: + +- (1) A relationship exists between the gsmSSF and the gsmSCF. +- (2) A charging event has been detected that was requested by the gsmSCF via an ApplyCharging operation or a Called Party, Temporary Connection or gsmSRF disconnection event has occurred. + +gsmSSF postconditions: + +- (1) If release of the call has occurred because the allowed call duration has been reached, then: + - All armed EDPs shall be disarmed; + - ApplyChargingReport shall be sent to gsmSCF followed by any pending CallInformationReports; + - The gsmSSF FSM shall transit to the state "Idle". +- (2) If release of the call has occurred but not because the allowed call duration has been reached, then: + +- If there are any armed EDPs or pending reports, then the gsmSSF FSM shall remain in the same state, else; + - The gsmSSF FSM shall transit to the state "Idle". +- (3) else: +- no gsmSSF FSM state transition. + +### 11.3.2.2 Error handling + +Generic error handling for the operation related errors are described in clause 10 and the TC services used for reporting operation errors are described in clause 14. + +## 11.4 AssistRequestInstructions procedure + +### 11.4.1 General description + +This operation may be used by an assist gsmSSF or by a gsmSRF. The operation is sent to the gsmSCF when the assisting gsmSSF or gsmSRF receives an indication from an initiating gsmSSF indicating an assist procedure. + +#### 11.4.1.1 Parameters + +- correlationID: +This parameter is used by the gsmSCF to associate the "AssistRequestInstructions" from the assisting gsmSSF or by a gsmSRF with the request from the initiating gsmSSF. The value of the "correlationID" may be extracted from the digits received from the initiating gsmSSF. +- iPSSPCapabilities: +Indicates which gsmSRF resources are attached, available and supported within: + - the MSC where the assisting gsmSSF resides; or + - the IP where the gsmSRF resides. + +### 11.4.2 Invoking entity (gsmSSF/gsmSRF) + +#### 11.4.2.1 Normal procedure + +assisting gsmSSF or gsmSRF preconditions: + +- (1) An assist indication is detected by the assisting gsmSSF or gsmSRF. + +assisting gsmSSF or gsmSRF postconditions: + +- (1) The assisting gsmSSF FSM is in the state "Waiting\_for\_Instructions" or the gsmSRF FSM is in the state "Connected". + +On receipt of an assist indication from the initiating gsmSSF, the assisting gsmSSF or gsmSRF shall ensure that the required resources are available to invoke an "AssistRequestInstructions" operation in the assist gsmSSF or gsmSRF and shall indicate to the initiating gsmSSF that the call is accepted. The "AssistRequestInstructions" operation is invoked by the assist gsmSSF or gsmSRF after the call, which initiated the assist indication, is accepted. + +#### 11.4.2.2 Error handling + +Generic error handling for the operation related errors are described in clause 10 and the TC services which are used for reporting operation errors are described in clause 14. + +## 11.5 CallGap procedure + +### 11.5.1 General description + +The gsmSCF uses this operation to request the gsmSSF to reduce the rate at which specific service requests are sent to the gsmSCF. This operation may be sent only within a dialogue that has been opened by the gsmSSF by an InitialDP operation. + +### 11.5.1.1 Parameters + +- **gapCriteria:** +This parameter identifies the criteria for a call to be subject to call gapping. It is a choice of the following parameters: "basicGapCriteria" or "compoundGapCriteria": + - **basicGapCriteria:** +This parameter consists of the following parameters: + - **calledAddressValue:** +This parameter indicates that call gapping shall be applied when the leading digits of the dialled number of a call attempt match those specified in "calledAddressValue". The called address is the one received from the current call control. + - **gapOnService:** +This parameter indicates that call gapping shall be applied when the Service Key of a Service initiation attempt matches the Service Key specified in "gapOnService". + - **calledAddressAndService:** +This parameter indicates that call gapping shall be applied when the Service Key of a Service initiation attempt matches the Service Key defined in "calledAddressAndService" and the leading digits of the dialled number of a that call attempt match the dialled digits defined in "calledAddressAndService". The called address is the one received from the current call control. + - **callingAddressAndService:** +This parameter indicates that call gapping shall be applied when the Service Key of a Service initiation attempt matches the Service Key defined in "callingAddressAndService" and the leading digits of the calling party number of that call attempt match the calling party number defined in "callingAddressAndService". In the case of call forwarding the calling address to be gapped shall the redirecting number which is placed in the Initial DP operation. + - **compoundGapCriteria:** +This parameter consists of the following parameters: + - **basicGapCriteria:** +This parameter is as described above. + - **scfID:** +This parameter identifies a gsmSCF. The scfID shall convey the necessary gsmSCF address information (e.g. Global Title) in the network to the requesting gsmSSF. Refer to ITU-T Recommendation Q.713 [42] "calling party address" parameter. The network operator shall decide about the actual mapping of this parameter on the used signalling system. +This parameter indicates the address of the gsmSCF which requests the call gapping. +If scfID is used in an operation that crosses an inter-network boundary, then its encoding must be understood in both networks and if the length is extended beyond 10 bytes this must be supported by both entities; this requires bilateral agreement on the encoding. If this parameter is not available, then the call gapping is not dedicated to a specific gsmSCF. +This parameter is restricted to include a fixed GT address string. + +NOTE: In the case where the GT addresses more than one SCP (e.g. a mated pair), then if one of these physical SCPs enters an overload conditions and issues a CallGap instruction, then the CallGap is applied to all these SCPs. + +- **gapIndicators:** +This parameter indicates the call gapping characteristics. + +- **duration:** +This parameter specifies the total time interval during which call gapping for the specified gap criteria will be active. + +A duration of 0 indicates that call gapping shall be removed. + +A duration of -2 indicates a network specific duration. + +Other values indicate duration in seconds. A duration of -1 shall not be used. + +- gapInterval: +This parameter specifies the minimum time between calls being allowed through. + +An interval of 0 indicates that calls meeting the gap criteria shall not be rejected. + +An interval of -1 indicates that all calls meeting the gap criteria shall be rejected. + +Other values indicate the gap interval in milliseconds. + +- controlType: +This parameter indicates the reason for activating call gapping. + +The "controlType" value "sCPOverloaded" indicates that an automatic congestion detection and control mechanism in the SCP has detected a congestion situation. + +The "controlType" value "manuallyInitiated" indicates that the service, the network management centre or service management centre, or both has detected a congestion situation, or any other situation that requires manually initiated controls. + +NOTE: The controlType "manuallyInitiated" shall have priority over "sCPOverloaded" call gap. Also non-CAMEL controlled traffic control mechanism may apply to an exchange with the gsmSSF functionality. The non-CAMEL controlled traffic control may also have some influence to the CAMEL call. It is therefore recommended to take measures to co-ordinate several traffic control mechanisms. The non-CAMEL controlled traffic control and co-ordination of several traffic control mechanisms are out of the scope of CAP. + +- gapTreatment: +This parameter indicates how calls that were stopped by the call gapping mechanism shall be treated. + +- informationToSend: + +This parameter indicates an announcement or a tone to be sent to the calling party. At the end of information sending, the call shall be released. + +- inbandInfo: +This parameter specifies the inband information to be sent. + +- messageID: +This parameter indicates the message(s) to be sent, it can be one of the following: + +- j) - elementaryMessageID: +This parameter indicates a single announcement. + +- duration: +This parameter indicates the maximum time duration in seconds that the message shall be played or repeated. A value of "0" indicates endless repetition. + +- tone: +This parameter specifies a tone to be sent to the end-user. + +- toneID: +This parameter indicates the tone to be sent. + +- k) - duration: +This parameter indicates the time duration in seconds of the tone. A value of "0" indicates infinite duration. + +- releaseCause: +If the call shall be released, then this parameter indicates a specific cause value to be sent in the release message. See ETSI EN 300 356-1 [23]. + +## 11.5.2 Responding entity (gsmSSF) + +### 11.5.2.1 Normal procedure + +gsmSSF preconditions: + +- (1) Call gapping for gapCriteria is not active; or +Call gapping for gapCriteria is active. +- (2) The gsmSSF FSM is in any state except "Idle" and except "Wait\_For\_Request". + +gsmSSF postconditions: + +- (1) The gsmSSME FSM is in the state "Active". +- (2) Call gapping for gapCriteria is activated; or +Call gapping for gapCriteria is renewed; or +Call gapping for gapCriteria is removed. +- (3) No gsmSSF FSM state transition. + +If there is not already an existing gsmSSME FSM for the gap criteria and gsmSCFAddress provided, then a new gsmSSME FSM shall be created. If no gsmSCFAddress is provided, then this refers in general to the gsmSSME FSM without a gsmSCFAddress. This gsmSSME FSM enters the state "Active" and initialises call gapping for the specified CAMEL calls. The parameters "gapIndicators", "controlType", "gapTreatment" and "gsmSCFAddress" for the indicated gap criteria shall be set as provided by the "CallGap" operation. + +In the case that both "manuallyInitiated" and "sCPOverloaded" call gapping are active for the same "gapCriteria", the manuallyInitiated call gapping shall prevail over the "sCPOverloaded" call gapping. More specifically, the following rules shall be applied in the gsmSSF to manage the priority of different control Types associated with the same "gapCriteria": + +- If a gsmSSME FSM already exists for the "gapCriteria" and the gsmSCFAddress provided, then: + - (1) If the (new) "controlType" equals an existing "controlType", then the new parameters (i.e., "gapIndicators" and "gapTreatment") shall overwrite the existing parameters. + - (2) If the (new) "controlType" is different from the existing "controlType", then the new parameters (i.e., "controlType", "gapIndicators" and "gapTreatment") shall be appended to the appropriate gsmSSME FSM (in addition to the existing parameters). The gsmSSME FSM remains in the state "Active". + +If the gsmSSF meets a TDP, then it shall check if call gapping was initiated for the same gsmSCF as the one currently assigned to this TDP or if call gapping exists with no provided gsmSCFAddress. If neither call gapping was initiated nor exists, then an "InitialDP" operation may be sent. + +The gsmSSF shall check if call gapping was initiated either for the "serviceKey" or for the "calledAddressValue" assigned to this TDP. If this is not the case, then an "InitialDP" operation may be sent. If call gapping was initiated for "calledAddressAndService" or "callingAddressAndService" and the "serviceKey" matches, then a check on the "calledAddressValue" and "callingAddressValue" for active call gapping shall be performed. Otherwise, an "InitialDP" operation may be sent. + +If a call to a controlled number matches one "gapCriteria" only, then the corresponding control is applied. If both "manuallyInitiated" call gapping and "sCPOverload" call gapping controls are active, then only the "manuallyInitiated" call gapping shall be applied. + +If a call matches several active "basicGapCriteria", then the treatment as specified in the CallGap associated with the gapCriteria with the highest priority shall be applied, with the priority being from high to low: + +1. calledAddressAndService or calledAddressValue; +2. callingAddressAndService; +3. gapOnService. + +For example, a call with called number 123456 and ServiceKey = NP matches two CallGaps, one with gapCriteria "CalledAdressValue=123" and another one with gapCriteria "gapOnService=NP". Then the call shall be subject to the control of the service request CallGap with "CalledAdressValue=123". + +In the case that multiple call gapping procedures are active with the same gap criteria, the "manuallyInitiated" call gapping shall prevail over the "sCPOverloaded" call gapping. + +If a call to a controlled called number or from a controlled calling number matches several active "basicGapCriteria " of the same type (in this context "calledAddressAndService" and "calledAddressValue" are seen as one type), then only the "gapCriteria" associated with the longest called party number shall be used, and the corresponding control shall be applied. For example, the codes 1234 and 12345 are under control. Then the call with 123456 is subject to the control on 12345. + +If a call to a controlled called number matches calledAddressAndService and calledAddressValue with the same number length, then calledAddressAndService has priority. Furthermore, if both "manuallyInitiated" and "sCPOverloaded" "controlTypes" are active for this "gapCriteria", then the "manuallyInitiated" control shall be applied. + +If call gapping is performed on a call for a particular service and triggering of this service is allowed, then no other gap criteria shall be applied this service instance. + +Active GapCriteria with assigned scfID shall have higher priority than the other GapCriteria. In the case that an entry with scfID matching the current call exists, all other criteria without scfID shall not be evaluated. + +The matching entries with scfID shall be evaluated in accordance with the priority rules for the basic criteria listed above. + +If call gapping shall be applied and there is no gap interval active, then an "InitialDP" operation may be sent including the "cGEncountered" parameter in accordance with the specified controlType. A new gap interval shall be initiated as indicated by "gapInterval". + +If a gap interval is active, then no "InitialDP" operation shall be sent and the call shall be treated as defined by Default Call Handling of the valid CSI and "gapTreatment". + +If the indicated duration equals "0", then the call gap process shall be stopped. + +If call gapping proceeds, then the gsmSSME FSM remains in the state "Active". Otherwise, the gsmSSME FSM transits to the state "idle". + +## 11.5.2.2 Error handling + +Operation related error handling is not applicable, due to class 4 operation. + +# 11.6 CallInformationReport procedure + +## 11.6.1 General description + +The gsmSSF uses this operation to send specific call information for a single call party to the gsmSCF as requested by the gsmSCF in previous "CallInformationRequest" operation. The report shall be sent at the end of a call party connection which is indicated by one of the events specified below. + +### 11.6.1.1 Parameters + +- requestedInformationList: +The gsmSSF sends the appropriate types and values to the gsmSCF in accordance with the requested information. +- legID: +This parameter indicates the party in the call for which the information has been collected. + +## 11.6.2 Invoking entity (gsmSSF) + +### 11.6.2.1 Normal procedure + +gsmSSF preconditions: + +- (1) The indicated or default party is released from the call or call setup towards the indicated or default party is terminated prematurely. +- (2) Requested call information has been collected. +- (3) "CallInformationReport" is pending due to a previously received "CallInformationRequest" operation. +- (4) A control or a monitor relationship exists between the gsmSCF and the gsmSSF. + +gsmSSF postconditions: + +- (1) If there are no armed EDPs or pending reports, then the gsmSSF FSM shall transit to the state "Idle"; otherwise, the gsmSSF FSM shall remain in the same state. + +If the gsmSSF FSM executes a state transition caused by one of the following events: + +- release for the indicated or default leg; +- abandon for the indicated or default leg; +- Called party Busy or Not Reachable for the indicated or default leg; +- gsmSSF No\_Answer timer expiration for the indicated or default leg; +- route select failure for the indicated or default leg; +- release of call initiated by the gsmSCF (ReleaseCall), + +and "CallInformationRequest" is pending for the indicated or default leg, then one "CallInformationReport" operation shall be sent to the gsmSCF, containing all information requested for that leg. + +If a "CallInformationReport" has been sent to the gsmSCF, then no "CallInformationReport" is pending on that leg, i.e. if a further "CallInformationReport" on that leg is required, for example in the case of follow-on call, then this has to be explicitly requested by the gsmSCF. + +### 11.6.2.2 Error handling + +Operation related error handling is not applicable, due to class 4 operation. + +## 11.7 CallInformationRequest procedure + +### 11.7.1 General description + +The gsmSCF uses this operation to request the gsmSSF to record specific information about a single call party and report it to the gsmSCF using the "CallInformationReport" operation. + +#### 11.7.1.1 Parameters + +- requestedInformationTypeList: +This parameter specifies a list of specific items of information which is requested. The list may contain the following parameters: + - callAttemptElapsedTime: +This parameter indicates the duration between the end of CAP processing of operations initiating call setup ("Connect", "Continue" or "ContinueWithArgument") and the received answer indication from the called party. If the callAttemptElapsedTime is requested for the calling party, then a value of "0" shall be reported by the gsmSSF. + +In the case of unsuccessful call setup, the network event indicating the unsuccessful call setup stops the measurement of "callAttemptElapsedTime". + +- callStopTime: +This parameter indicates the time stamp when the connection is released. +- callConnectedElapsedTime: +This parameter indicates the duration between the received answer indication from the called party and the release of that connection. For the calling party it indicates the duration between the sending of InitialDP and the release of that party. +- releaseCause: +This parameter indicates the release cause for the call. +- legID: +This parameter indicates the party in the call for which the information shall be collected. + +## 11.7.2 Responding entity (gsmSSF) + +### 11.7.2.1 Normal procedure + +gsmSSF preconditions: + +- (1) A control relationship exists between gsmSSF and gsmSCF. +- (2) The gsmSSF FSM is in the state "Waiting\_for\_Instructions". + +gsmSSF postconditions: + +- (1) Requested call information is retained by the gsmSSF. +- (2) No gsmSSF FSM state transition. + +The gsmSSF allocates a record for the indicated or default party and stores the requested information if already available and prepares the recording of information items, that will become available later like for example "callStopTimeValue". + +Call information may be requested for any call party (identified by a legID). + +### 11.7.2.2 Error handling + +Generic error handling for the operation related errors are described in clause 10 and the TC services which are used for reporting operation errors are described in clause 14. + +## 11.8 Cancel procedure + +### 11.8.1 General description + +The gsmSCF uses this operation to request the gsmSRF or gsmSSF to cancel a correlated previous operation. + +The Cancel operation may be used for the following purposes: + +- (1) Cancel may be sent to the gsmSRF to cancel the "PlayAnnouncement" or the "PromptAndCollectUserInfo" operation. The cancellation of the operation is indicated via a respective error indication, "Canceled", to the invoking entity of the cancelled "PlayAnnouncement" or "PromptAndCollectUserInfo" operation. +- (2) Cancel may be sent to the gsmSSF to disarm all armed EDPs and cancel all pending reports. This enables the gsmSSF FSM to transit to the state "Idle". If Cancel is used for this purpose, then the Cancel operation does not specify any specific operation to be cancelled. + +#### 11.8.1.1 Parameters + +- invokeID: +This parameter specifies which operation invocation shall be cancelled, i.e. PromptAndCollectUserInfo or PlayAnnouncement. + +- callSegmentID: +This parameter specifies the Call Segment to which the cancellation of the user interaction operation shall apply. +- allRequests: +This parameter indicates that all armed EDP shall be disarmed and that any pending "ApplyChargingReport" and "CallInformationReport" shall be cancelled. + +## 11.8.2 Responding entity (gsmSRF) + +In the case of Cancel(invokeID), the gsmSRF is the responding entity. In this case, the Cancel operation may also contain the callSegmentID parameter. + +### 11.8.2.1 Normal procedure + +gsmSRF preconditions: + +- (1) A PlayAnnouncement or PromptAndCollectUserInfo operation has been received and the gsmSRF FSM is in the state "User Interaction". + +gsmSRF postconditions: + +- (1) The execution of the PlayAnnouncement or PromptAndCollectUserInfo operation has been aborted and the gsmSRF remains in the state "User Interaction". + +### 11.8.2.2 Error handling + +Generic error handling for the operation related errors are described in clause 10 and the TC services which are used for reporting operation errors are described in clause 14. + +## 11.8.3 Responding entity (gsmSSF) + +In the case of Cancel(allRequests), the gsmSSF is the responding entity. + +### 11.8.3.1 Normal procedure + +gsmSSF preconditions: + +- (1) The gsmSSF FSM is in the state "Waiting\_for\_Instructions" or in the state "Monitoring". + +gsmSSF postconditions: + +- (1) All armed EDPs are disarmed and all pending reports are cancelled. +- (2) If the gsmSSF FSM was in the state "Monitoring", then it shall transit to the state "Idle"; or +If the gsmSSF FSM was in the state "Waiting\_for\_Instructions", then it shall remain in that state. +A subsequent call-processing operation will result in a gsmSSF FSM state transition to the state "Idle". If the call is in the active state, then the gsmSSF shall treat it autonomously as a normal (non-CAMEL) call. + +### 11.8.3.2 Error handling + +Sending of return error on cancel is not applicable in the cancel "allRequests" case. Generic error handling for the operation related errors are described in clause 10 and the TC services which are used for reporting operation errors are described in clause 14. + +## 11.8A CollectInformation Procedure + +### 11.8A.1 General description + +The gsmSCF uses this operation to request the gsmSSF to perform the call processing actions to collect additional digits from the calling party and report it to the gsmSCF. The CollectInformation operation may be used for TO calls in the gsmSSF. The gsmSCF shall arm the Collected\_Info DP as EDP-R before sending this operation. + +### 11.8A.1.1 Parameters + +None + +Note: An operation argument is supported for future extensibility. + +## 11.8A.2 Responding entity (gsmSSF) + +### 11.8A.2.1 Normal procedure + +gsmSSF preconditions: + +- (1) A control relationship exists between the gsmSCF and the gsmSSF; +- (2) Basic call processing has been suspended at CollectedInfo DP or AnalysedInfo DP; +- (3) CollectedInfo DP has been armed as EDP-R; +- (4) The gsmSSF FSM is in the state "Waiting\_for\_Instructions". + +gsmSSF postconditions: + +- (1) The gsmSSF performs the call processing actions to collect additional dialled digits from the calling party; +- (2) The gsmSSF FSM transits to the state "Monitoring"; +- (3) In the O-BCSM, call processing resumes at PIC Collect\_Info or PIC Analyze\_Information. + +### 11.8A.2.2 Error handling + +Generic error handling for the operation related errors are described in clause 10 and the TC services which are used for reporting operation errors are described in clause 14. + +## 11.9 Connect procedure + +### 11.9.1 General description + +The gsmSCF uses this operation to request the gsmSSF to perform the call processing actions to route a call to a specific destination. + +In general all parameters which are provided in a Connect operation to the gsmSSF shall replace the corresponding signalling parameter in the CCF in O-BCSM, in accordance with ETSI ES 201 296 [21] and shall be used for subsequent call processing. The CCF of the T-BCSM shall send corresponding signalling parameters to new call leg without using them in subsequent call processing. Parameters which are not provided by the Connect operation shall retain their value (if already assigned) in the CCF for subsequent call processing. + +#### 11.9.1.1 Parameters + +- destinationRoutingAddress: +This parameter contains the called party numbers towards which the call shall be routed. +- alertingPattern: +This parameter indicates the type of alerting to be applied. It is defined in 3GPP TS 29.002 [11]. +- serviceInteractionIndicatorsTwo: +This parameter contains indicators to resolve interactions between CAMEL based services and network based services. +- callingPartysCategory: +This parameter indicates the type of calling party (e.g., operator, pay phone, ordinary subscriber). +- originalCalledPartyID: +If the call is forwarded by the gsmSCF, then this parameter carries the dialled digits. + +- **redirectingPartyID:** +This parameter indicates the last directory number the call was redirected from. +- **redirectionInformation:** +This parameter contains forwarding related information, such as redirecting counter. +- **genericNumbers:** +This parameter allows the gsmSCF to set the Generic Number parameter used in the network. It is used for transfer of Additional Calling Party Number. +- **suppressionOfAnnouncement:** +This parameter indicates that announcements and tones which are played in the exchange at non-successful call set-up attempts shall be suppressed. +- **oCSIApplicable:** +This parameter indicates to the GMSC/gsmSSF or VMSC/gsmSSF that the Originating CAMEL Subscription Information, if present, shall be applied on the outgoing call leg created with the Connect operation. For the use of this parameter see 3GPP TS 23.078 [7]. +- **Carrier:** +This parameter indicates carrier information. It consists of the carrier selection field followed by the Carrier ID information to be used by gsmSSF for routeing a call to a carrier. + +It contains the following embedded parameters: + +- **carrierSelectionField:** +This parameter indicates how the selected carrier is provided (e.g. pre-subscribed). +- **carrierID:** +This parameter indicates the carrier to use for the call. It contains the digits of the carrier identification code. +- **naOliInfo:** +This parameter contains originating line information which identifies the charged party number type to the carrier. +- **ChargeNumber:** +This parameter contains the number that identifies the entity to be charged for the call. It identifies the chargeable number for the usage of a carrier (applicable on a call sent into a North American long distance carrier). For a definition of this parameter refer to ANSI T1.113-1995 [92]. +- **cug-Interlock:** +This parameter uniquely identifies a CUG within a network. +- **cug-OutgoingAccess:** +This parameter indicates if the calling user has subscribed to the outgoing access inter-CUG accessibility subscription option. +- **bor-InterrogationRequested:** +This parameter indicates that Basic Optimal Routeing is requested for the call. +- **legToBeConnected:** +This parameter indicates the leg to be connected. +- **suppress-N-CSI:** +This parameter indicates that N-CSI shall be suppressed + +## 11.9.2 Responding entity (gsmSSF) + +### 11.9.2.1 Normal procedure + +gsmSSF preconditions: + +- (1) A control relationship exists between the gsmSSF and the gsmSCF. +- (2) Basic call processing has been suspended at a DP. + +- (3) The gsmSSF FSM is in the state "Waiting\_for\_Instructions". + +gsmSSF postconditions: + +- (1) The gsmSSF performs the call processing actions to route the call to the specified destination. +- (2) In the O-BCSM, call processing resumes at PIC Analyze\_Information. + +On receipt of this operation, the gsmSSF performs the following actions: + +- If no EDPs have been armed and neither a CallInformationReport nor an ApplyChargingReport has been requested, then the gsmSSF FSM transits to the state "Idle". Otherwise, the gsmSSF FSM transits to the state "Monitoring". + +The gsmSSF shall not perform any implicit arming or disarming of DPs. + +Statistic counter(s) are not affected. + +### 11.9.2.2 Error handling + +Generic error handling for the operation related errors are described in clause 10 and the TC services which are used for reporting operation errors are described in clause 14. + +## 11.10 ConnectToResource procedure + +### 11.10.1 General description + +The gsmSCF uses this operation to connect a call segment from the gsmSSF to a specialized resource. After successful connection to the gsmSRF, the interaction with the parties in the call segment can take place. The gsmSSF relays all operations for the gsmSRF and all responses from the gsmSRF. + +#### 11.10.1.1 Parameters + +- resourceAddress: +This parameter identifies the physical location of the gsmSRF. It may be one of the following parameters. + - iPRoutingAddress: +This parameter indicates the routeing address to set up a connection towards the gsmSRF. + - none: +This parameter indicates that the call segment shall be connected to a predefined gsmSRF. +- serviceInteractionIndicatorsTwo: +This parameter contains an indicator that is used for the control of the through connection to the Calling Party. + +NOTE The call segment to which the ConnectToResource applies does not have to contain a leg to the calling party. + +The assisting gsmSSF shall always assume that Bothway Throughconnection is required, and hence will ignore this parameter if received. + +- callSegmentId: +This parameter indicates the call segment to which the Connect To Resource procedure applies. + +### 11.10.2 Responding entity (gsmSSF) + +#### 11.10.2.1 Normal procedure + +gsmSSF preconditions: + +- (1) A control relationship exists between the gsmSCF and the gsmSSF. +- (2) The gsmSSF FSM is in the state "Waiting\_for\_Instructions". + +gsmSSF postconditions: + +- (1) The call segment is connected to the gsmSRF. +- (2) A control relationship between the gsmSCF and the gsmSRF is established. +- (3) The gsmSSF FSM transits to the state "Waiting\_for\_end\_of\_User\_Interaction". + +NOTE: The successful connection to the gsmSRF causes a gsmSRF FSM state transition from the state "Idle" to the state "Connected". + +## 11.10.2.2 Error handling + +Generic error handling for the operation related errors are described in clause 10 and the TC services which are used for reporting operation errors are described in clause 14. + +# 11.11 Continue procedure + +## 11.11.1 General description + +The gsmSCF uses this operation to request the gsmSSF to proceed with call processing at the DP at which it previously suspended call processing to await gsmSCF instructions. The gsmSSF continues call processing without substituting new data from the gsmSCF. + +### 11.11.1.1 Parameters + +None. + +## 11.11.2 Responding entity (gsmSSF) + +### 11.11.2.1 Normal procedure + +gsmSSF preconditions: + +- (1) A control relationship exists between the gsmSSF and the gsmSCF. +- (2) Basic call processing has been suspended at any DP. +- (3) The gsmSSF FSM is in the state "Waiting\_for\_Instructions". + +gsmSSF postconditions: + +- (1) BCSM: If the Call Segment has received all the required resumptions then basic call processing continues. +- (2) The gsmSSF FSM remains in the same state unless all resumptions have been received. + +If all resumptions have been received, then: + +- If there are armed EDPs or pending reports and no user interaction is ongoing, then the gsmSSF FSM transits to the state "Monitoring"; or +- If there are no armed EDPs neither pending reports, then the gsmSSF FSM transits to the state "Idle". + +### 11.11.2.2 Error handling + +Operation related error handling is not applicable, due to class 4 operation. + +# 11.12 ContinueWithArgument Procedure + +## 11.12.1 General description + +The gsmSCF uses this operation to request the gsmSSF to proceed with call processing at the DP at which it previously suspended call processing to await gsmSCF instructions. It is also used to provide additional service related information to a User (Called Party or Calling Party) whilst the call processing proceeds. + +In general all parameters which are provided in a ContinueWithArgument operation to the gsmSSF shall replace the corresponding signalling parameter in the CCF, in accordance with ETSI ES 201 296 [21], and shall be used for subsequent call processing. Parameters which are not provided by the ContinueWithArgument operation shall retain their value (if already assigned) in the CCF for subsequent call processing. + +### 11.12.1.1 Parameters + +- legOrCallSegment: +This parameter indicates the leg or Call Segment to which the ContinueWithArgument operation shall apply. +- alertingPattern: +This parameter indicates the type of alerting to be applied. It is defined in 3GPP TS 29.002 [11]. +- serviceInteractionIndicatorsTwo: +This parameter contains indicators that are used to resolve interactions between CAMEL based services and network based services. +- callingPartysCategory: +This parameter indicates the type of calling party (e.g., operator, pay phone, ordinary subscriber). +- genericNumbers: +This parameter allows the gsmSCF to set the Generic Number parameter used in the network. It is used for transfer of Additional Calling Party Number. +- suppressionOfAnnouncement: +This parameter indicates that announcements and tones which are played in the exchange at non-successful call set-up attempts shall be suppressed. +- carrier: +This parameter indicates carrier information. It consists of the carrier selection field followed by the Carrier ID information to be used by gsmSSF for routing a call to a carrier. + +It contains the following embedded parameter: + +- carrierSelectionField: +This parameter indicates how the selected carrier is provided (e.g. pre-subscribed). +- carrierID: +This parameter indicates the carrier to use for the call. It contains the digits of the carrier identification code. +- naOliInfo: +This parameter contains originating line information which identifies the charged party number type to the carrier. +- chargeNumber: +This parameter contains the number that identifies the entity to be charged for the call. It identifies the chargeable number for the usage of a carrier (applicable on a call sent into a North American long distance carrier). For a definition of this parameter refer to ANSI T1.113-1995 [92]. +- cug-Interlock: +This parameter uniquely identifies a CUG within a network. +- cug-OutgoingAccess: +This parameter indicates if the calling user has subscribed to the outgoing access inter-CUG accessibility subscription option. +- bor-InterrogationRequested: +This parameter indicates that Basic Optimal Routing is requested for the call. +- suppress-O-CSI: +This parameter indicates that O-CSI shall be suppressed for the forwarding leg or deflecting leg. +- suppress-D-CSI: +This parameter indicates that D-CSI shall be suppressed for the leg. + +- suppress-N-CSI: +This parameter indicates that N-CSI shall be suppressed for the leg or trunk originated call. +- suppressOutgoingCallBarring: +This parameter indicates that outgoing call barrings shall be suppressed for the leg. + +## 11.12.2 Responding entity (gsmSSF) + +### 11.12.2.1 Normal procedure + +gsmSSF preconditions: + +- (1) A control relationship exists between the gsmSSF and the gsmSCF. +- (2) Basic call processing has been suspended at a DP. +- (3) The gsmSSF FSM is in the state "Waiting\_for\_Instructions". + +gsmSSF postconditions: + +- (1) BCSM: If the Call Segment has received all the required resumptions then basic call processing continues with modified information, +- (2) The gsmSSF FSM remains in the same state unless all resumptions have been received. + +If all resumptions have been received, then: + +- If there are armed EDPs or pending reports and no user interaction is ongoing, then the gsmSSF FSM transits to the state "Monitoring"; or +- If there are no armed EDPs neither pending reports, then the gsmSSF FSM transits to the state "Idle". + +### 11.12.2.2 Error handling + +Generic error handling for the operation related errors are described in clause 10 and the TC services which are used for reporting operation errors are described in clause 14. + +## 11.13 DisconnectForwardConnection procedure + +### 11.13.1 General Description + +The gsmSCF uses this operation for the following two purposes: + +- (1) To clear a connection to a gsmSRF: + +The operation is used to explicitly disconnect a connection to a resource (gsmSRF) established previously with a "ConnectToResource" or an "EstablishTemporaryConnection" operation. It is used for a forward disconnection from the gsmSSF. + +An alternative solution is the backward disconnect from the gsmSRF, controlled by the "DisconnectFromIPForbidden" parameter in the "PlayAnnouncement" and "PromptAndCollectUserInformation" operations. + +- (2) To clear a connection to an assisting gsmSSF: + +The operation is sent to the non-assisting gsmSSF of a pair of gsmSSFs involved in an assist procedure. It is used to disconnect the temporary connection between the initiating gsmSSF and the assisting gsmSSF and the connection between the assisting gsmSSF and its associated gsmSRF. + +The DisconnectForwardConnection operation shall not be used when the CallSegmentID is required. + +### 11.13.1.1 Parameters + +None. + +## 11.13.2 Responding entity (gsmSSF) + +### 11.13.2.1 Normal procedure + +gsmSSF preconditions: + +- (1) The basic call processing has been suspended at a DP. The gsmSSF FSM in the initiating gsmSSF is in the state "Waiting\_for\_end\_of\_User\_Interaction" or in the state "Waiting\_for\_end\_of\_Temporary\_Connection". + +gsmSSF postconditions: + +- (1) The connection to the gsmSRF or assisting gsmSSF is released. +- (2) The gsmSSF FSM is in the state "Waiting\_for\_Instructions". + +The receipt of "DisconnectForwardConnection" results in a disconnection of the assisting gsmSSF or the PE containing the gsmSRF from the call. It does not result in a release of the connection between the gsmSSF and the end-user. + +On receipt of this operation, the gsmSSF shall perform the following actions: + +- The initiating gsmSSF releases the connection to the assisting gsmSSF or the gsmSRF. +- The gsmSSF FSM transits to the state "Waiting\_for\_Instructions". + +NOTE: The successful disconnection to the gsmSRF causes a gsmSRF FSM state transition to the state "Idle". A current order (e.g. "PlayAnnouncement" or "PromptAndCollectUserInformation") is cancelled and any queued order (e.g. "PlayAnnouncement" or "PromptAndCollectUserInformation") is discarded. + +### 11.13.2.2 Error handling + +Generic error handling for the operation related errors are described in clause 10 and the TC services which are used for reporting operation errors are described in clause 14. + +## 11.14 DisconnectForwardConnectionWithArgument procedure + +### 11.14.1 General Description + +The gsmSCF uses this operation to disconnect a connection to a resource (gsmSRF) established previously with a "ConnectToResource" or an "EstablishTemporaryConnection" operation. + +#### 11.14.1.1 Parameters + +- callSegmentID: +This parameter indicates the Call Segment to be disconnected from the resource. + +### 11.14.2 Responding entity (gsmSSF) + +#### 11.14.2.1 Normal procedure + +gsmSSF preconditions: + +- (1) The basic call processing has been suspended at a DP. The CS\_gsmSSF FSM in the initiating gsmSSF is in the state "Waiting\_for\_end\_of\_User\_Interaction" or in the state "Waiting\_for\_end\_of\_Temporary\_Connection". + +gsmSSF postconditions: + +- (1) The connection to the gsmSRF or assisting gsmSSF is released. +- (2) The CS\_gsmSSF FSM transits to the state "Waiting\_for\_Instructions". + +The receipt of "DisconnectForwardConnectionWithArgument" results in disconnecting the PE containing the gsmSRF from the specified Call Segment. It does not result in a release of the connection between the gsmSSF and the end-user. + +On receipt of this operation, the gsmSSF shall perform the following actions: + +- The gsmSSF releases the connection to the assisting gsmSSF or the gsmSRF. +- The gsmSSF FSM transits to the state "Waiting\_for\_Instructions". + +NOTE: The successful disconnection from the gsmSRF causes the gsmSRF to transit to the state "Idle". A current order (e.g. "PlayAnnouncement" or "PromptAndCollectUserInfo") is cancelled and any queued order (e.g. "PlayAnnouncement" or "PromptAndCollectUserInfo") is discarded. + +## 11.14.2.2 Error handling + +Generic error handling for the operation related errors is described in clause 10 and the TC services which are used for reporting operation errors are described in clause 14. + +# 11.15 DisconnectLeg procedure + +## 11.15.1 General Description + +The gsmSCF uses this operation to request the gsmSSF to release a specific leg associated with the call. Any other leg(s) not specified in the Disconnect Leg operation are retained. + +### 11.15.1.1 Parameters + +- legToBeReleased: +This parameter indicates the call leg to be released. +- releaseCause: +This parameter may be used by the MSC for generating specific tones to the party to be released or to fill in the "cause" parameter in the release message. + +## 11.15.2 Responding entity (gsmSSF) + +### 11.15.2.1 Normal procedure + +gsmSSF preconditions: + +- 1) A control relationship exists between the gsmSCF and the gsmSSF; +- 2) User interaction is not in progress in the Call Segment containing the leg to be disconnected. + +gsmSSF postconditions: + +- 1) The gsmSSF performs the call processing actions to release the indicated party. +- 2) Any armed EDPs on that leg shall be disarmed; any pending reports for that leg shall be sent to the gsmSCF. +- 3) If the released leg was the last leg within the Call Segment, then the CS\_gsmSSF FSM for that Call Segment returns to the state "Idle". +- 4) If the leg was the last leg within the call, then the CSA\_gsmSSF FSM returns to the state "Idle". +- 5) If the CS\_gsmSSF FSM for the Call Segment concerned has not returned to the state "Idle", then it transits to the state "Waiting\_for\_Instructions". The remaining BCSM instances within the Call Segment shall transit to the O\_Mid\_Call DP or to the T\_Mid\_Call DP, unless already suspended at a DP. The Mid\_Call EDP shall not be reported for this case. +- 6) A Return Result shall be sent to the gsmSCF immediately after successful execution of this operation. + +### 11.15.2.2 Error handling + +Generic error handling for the operation related errors is described in clause 10, and the TC services which are used for reporting operation errors are described in clause 14. + +## 11.16 EntityReleased procedure + +### 11.16.1 General Description + +The CSA uses this operation to inform the gsmSCF about the release of a logical entity (Call Segment or BCSM) caused by exception or errors. The CSA shall use this operation if this information can not be conveyed in a TC\_ABORT or TC\_END TC message because the TC dialogue has to be maintained for other logical entities (Call Segment or BCSM) in this CSA which are not affected by this error or exception. The CSA shall not use this operation if the last Call Segment in the CSA was released. + +#### 11.16.1.1 Parameters + +This operation consists of a choice of the following parameters: + +- CSFailure: +Indicates that a Call Segment was released. It contains of the following parameters: + - callSegmentID: +This parameter identifies the released Call Segment. + - cause: +This parameter indicates the cause for releasing this Call Segment. The cause may be used by the gsmSCF to decide the further handling of the call. +- BCSMFailure: +This parameter indicates that a leg was released. It consists of the following parameters: + - legID: +This parameter identifies the released leg. + - cause: +This parameter indicates the cause for releasing this BCSM. The cause may be used by the gsmSCF to decide the further handling of the call. + +### 11.16.2 Invoking entity (gsmSSF) + +#### 11.16.2.1 Normal procedure + +CSA\_gsmSSF preconditions: + +- (1) Any CSA\_gsmSSF FSM state except "Idle". + +CSA\_gsmSSF postconditions: + +- + +gsmSSF postconditions: + +- (1) If the released entity was a BCSM (leg), then only the appropriate resources are released. If the released entity was a Call Segment, then the related CS\_gsmSSF FSM returns to the state "Idle". + +#### 11.16.2.2 Error handling + +Generic error handling for the operation related errors is described in clause 10, and the TC services which are used for reporting operation errors are described in clause 14. + +## 11.17 EstablishTemporaryConnection procedure + +### 11.17.1 General Description + +The gsmSCF uses this operation to create a connection between an initiating gsmSSF and an assisting gsmSSF as part of a service assist procedure. It can also be used to create a connection between a gsmSSF and a gsmSRF, for the case where the gsmSRF exists in a separately addressable PE. + +The assistingSSPIPRoutingAddress shall contain routeing digits, a correlationID and a scfID when a temporary connection shall be established between PLMNs and no bilateral agreement exists between the involved network operators to transfer correlationID and SCFiD as separate parameters. + +### 11.17.1.1 Parameters + +- assistingSSPIPRoutingAddress: +This parameter indicates the destination address of the gsmSRF for assist procedure. The "assistingSSPIPRoutingAddress" may contain embedded within it, a "correlationID" and "scfID", but only if "correlationID" and "scfID" are not specified separately. +- correlationID: +This parameter is used by the gsmSCF to associate the "AssistRequestInstructions" from the assisting gsmSSF (or the gsmSRF) with the Request from the initiating gsmSSF. The "correlationID" shall be used only if the correlation id is not embedded in the "assistingSSPIPRoutingAddress". The network operator has to decide about the actual mapping of this parameter on the used signalling system. +- scfID: +This parameter contains the gsmSCF identifier and enables the assisting gsmSSF to identify which gsmSCF the AssistRequestInstructions shall be sent to. +The "scfID" shall be used only if the gsmSCF id is not embedded in the "assistingSSPIPRoutingAddress". The network operator has to decide about the actual mapping of this parameter on the used signalling system. +When ScfID is used in an operation which crosses an internetwork boundary, its encoding must be understood in both networks and if the length is extended beyond 10 bytes this must be supported by both entities; this requires bilateral agreement on the encoding. +- serviceInteractionIndicatorsTwo: +This parameter contains an indicator that is used for the control of the through connection to the Calling Party. +- Carrier: +This parameter contains carrier information. It consists of the carrier selection field followed by the Carrier ID information to be used by gsmSSF for routeing a call to a carrier. + +It contains the following embedded parameter: + +- carrierSelectionField: +This parameter indicates how the selected carrier is provided (e.g. pre-subscribed). +- carrierID: +This parameter indicates the carrier to use for the call. It contains the digits of the carrier identification code. +- naOliInfo: +This parameter contains originating line information which identifies the charged party number type to the carrier. +- chargeNumber: +This parameter contains the number that identifies the entity to be charged for the call. It identifies the chargeable number for the usage of a carrier (applicable on a call sent into a North American long distance carrier). For a definition of this parameter refer to ANSI T1.113-1995 [92]. +- callSegmentID: +This parameter indicates the Call Segment to which the temporary connection shall be established. +- originalCalledPartyID: +This parameter identifies the original called party. +- callingPartyNumber: +This parameter identifies the calling party. + +## 11.17.2 Responding entity (gsmSSF) + +### 11.17.2.1 Normal procedure + +gsmSSF preconditions: + +- (1) The gsmSSF FSM is in the state "Waiting\_for\_Instructions". +- (2) The gsmSSF is not an assisting gsmSSF. + +gsmSSF postconditions: + +- (1) The gsmSSF performs the call processing actions to route the call to the assisting gsmSSF or gsmSRF in accordance with the "assistingSSPIPRoutingAddress" requested by the gsmSCF. +- (2) The gsmSSF FSM transits to the state "Waiting\_for\_end\_of\_Temporary\_Connection". + +On receipt of this operation, the gsmSSF shall perform the following actions: + +- Route the call to assisting gsmSSF or gsmSRF using "assistingSSPIPRoutingAddress"; + +## 11.17.2.2 Error handling + +Until the connection setup has been accepted (refer to ITU-T Recommendation Q.71 [41]) by the assisting gsmSSF or the gsmSRF, all received failure indications from the network on the ETC establishment shall be reported to the gsmSCF as EstablishTemporaryConnection error ETCFailed (e.g., busy, congestion). + +NOTE The operation timer for EstablishTemporaryConnection shall be longer than the maximum allowed time for the signalling procedures to accept the connection. + +Generic error handling for the operation related errors are described in clause 10 and the TC services which are used for reporting operation errors are described in clause 14. + +# 11.18 EventReportBCSM procedure + +## 11.18.1 General description + +The gsmSSF uses this operation to notify the gsmSCF of a call related event previously requested by the gsmSCF in a "RequestReportBCSMEvent" operation. + +### 11.18.1.1 Parameters + +- eventTypeBCSM: +This parameter specifies the type of event that is reported. +- eventSpecificInformationBCSM: +This parameter indicates the call related information specific to the event. + +For Collected\_Info it shall contain the CalledPartyNumber parameter. + +For Route\_Select\_Failure it shall contain the "FailureCause", if available. + +For O\_Busy it shall contain the "BusyCause", if available. + +- If the busy event is triggered by an ISUP release message, then the BusyCause is a copy of the ISUP release cause, for example: Subscriber absent, 20 or User busy, 17. +- If the busy event is triggered by a MAP error, for example: Absent subscriber, received from the HLR, then the MAP cause is mapped to the corresponding ISUP release cause. + +NOTE 1: If no BusyCause is received, then the gsmSCF shall assume busy. + +For T\_Busy it may contain the following parameters, if available. + +- CallForwarded: +This parameter indicates that the busy event is triggered by call forwarding at the GMSC or VMSC. +- ForwardingDestinationNumber: +This parameter indicates the forwarding destination. + +- RouteNotPermitted: +This parameter indicates that the busy event is triggered because call forwarding was not invoked in this GMSC due to the rules of Basic Optimal Routeing. +- BusyCause: + - If the busy event is triggered by an ISUP release message, then the BusyCause is a copy of the ISUP release cause, for example: Subscriber absent, 20 or User busy, 17. + - If the busy event is triggered by a MAP error, for example: Absent subscriber, received from the HLR, then the MAP cause is mapped to the corresponding ISUP release cause. + - If the busy event is triggered by call forwarding or call deflection invocation in the GMSC or VMSC, then the BusyCause will refer to the release cause in accordance with the mapping table in 3GPP TS 23.078 [7]. + - If the busy event is triggered by call forwarding at the GMSC, then the BusyCause reflects the forwarding reason (Subscriber Absent, 20 or User busy, 17). The eventSpecificInformationBCSM shall in that case also contain the CallForwarded indication. + +NOTE 2: If no BusyCause is received, then the gsmSCF shall assume busy. + +For O\_No\_Answer it shall be empty. + +For T\_No\_Answer it may contain the CallForwarded indication and the ForwardingDestinationNumber. + +- If the No\_Answer event is triggered by an ISUP release message or expiry of the CAMEL timer TNRY, then the eventSpecificInformationBCSM shall be empty. +- If the No\_Answer event is triggered by call forwarding at the GMSC or VMSC, then the eventSpecificInformationBCSM shall contain the CallForwarded indication and the ForwardingDestinationNumber. + +For O\_Answer or T\_Answer it shall contain the following information, if available: + +- The destination address for the call; +- The OR indicator, in the case that the call was subject to Basic Optimal Routeing, as specified in 3GPP TS 23.079 [8]; +- The forwarding indicator, in the case that the Call Forwarding Supplementary Service was invoked; +- The charge indicator; +- The Extended Basic Service Code, for SCUDIF calls (see 3GPP TS 23.172 [16]); +- The Extended Basic Service Code 2, for SCUDIF calls (see 3GPP TS 23.172 [16]). + +For O\_Mid\_Call and T\_Mid\_Call it shall contain the detected digit string, in accordance with the criterion defined in the RequestReportBCSMEVENT operation. + +For Call\_Accepted, O\_Term\_Seized, O\_Change\_Of\_Position and T\_Change\_Of\_Position it shall contain the following information: + +- locationInformation: +This parameter indicates the location of the MS. + +For O\_Disconnect and T\_Disconnect it shall contain the "releaseCause", if available. + +For O\_Abandon it may contain the following parameter, if available. + +- routeNotPermitted: +This parameter indicates that the O-Abandon event is triggered because call set up shall not be invoked in this MSC due to the rules of Basic Optimal Routeing. + +For O\_Service\_Change or T\_Service\_Change it may contain the following information: + +- The Extended Basic Service Code, for SCUDIF calls (see 3GPP TS 23.172 [16]) ; +- The initiator of the Service Change; +- The nature of Service Change. +- legID: +This parameter indicates the party in the call for which the event is reported. The gsmSSF shall use the option "receivingSideID" only. +- receivingSideID: +If not included, then the default values for LegID are assumed according to the tables 11-1 and 11-2. + +The "legID" parameter shall always be included for the events O\_Disconnect and T\_Disconnect. +- miscCallInfo: +This parameter indicates Detection Point (DP) related information. +- messageType: +This parameter indicates whether the message is a request, i.e. resulting from a "RequestReportBCSMEEvent" with monitorMode = interrupted, or a notification, i.e. resulting from a "RequestReportBCSMEEvent" with "monitorMode" = "notifyAndContinue". + +## 11.18.2 Invoking entity (gsmSSF) + +### 11.18.2.1 Normal procedure + +gsmSSF preconditions: + +- (1) A control relationship or a monitoring relationship exists between the gsmSSF and the gsmSCF. +- (2) For the O\_Abandon DP and T\_Abandon DP, the gsmSSF FSM is in any state, except "Idle". For other DPs, refer to 3GPP TS 23.078 [7]. +- (3) The BCSM proceeds to an EDP that is armed. + +gsmSSF postconditions: + +- (1) If the message type was notification and there are still armed EDPs or pending reports, then the gsmSSF FSM stays in the state "Monitoring". +- (2) If the message type was notification and there are neither any armed EDPs nor pending reports, then the gsmSSF FSM transits to the state "Idle". +- (3) If the message type was request, then the gsmSSF FSM transits to the state "Waiting\_for\_Instructions". Call processing is interrupted. + +### 11.18.2.2 Error handling + +If the message type is "request" and the Tssf timer expires, then the gsmSSF shall abort the TC dialogue and shall instruct the MSC to treat the call in accordance with the Default Call Handling, valid for this CAMEL dialogue. + +Operation related error handling is not applicable, due to class 4 operation. + +## 11.19 FurnishChargingInformation procedure + +### 11.19.1 General description + +The gsmSCF uses this operation to send charging related information to a logical call record. This logical call record is CAMEL specific. The first FurnishChargingInformation operation of a call leg leads to the generation of a logical call record. The handling of subsequent FurnishChargingInformation operations for a call leg depends on the presence and value of the append free format data parameter in the FurnishChargingInformation operation. For details see 3GPP TS 23.078 [7]. + +If a FurnishChargingInformation operation is received for the called party when the gsmSSF FSM is in the state "Monitoring", or is suspended in one of the following DPs, then the charging information shall be included in the logical call record for the leg that has been or is to be established: + +- Collected\_Info; +- Analysed\_Information; +- O\_Answer; +- Terminating\_Attempt\_Authorised; or +- T\_Answer. + +If a FurnishChargingInformation operation is received for the called party when the gsmSSF is suspended in any other DP, then the charging information shall be included in the logical call record created for the last failed or disconnected called party. + +### 11.19.1.1 Parameters + +- fCIBillingChargingCharacteristics: +This parameter contains the following parameters; +- fCIBCCCAMELsequence1: +This parameter contains the following parameters; +- freeFormatData: +This parameter contains free-format billing and/or charging characteristics; +- partyToCharge: +This parameter indicates the party to bill and/or charge; +- appendFreeFormatData: +This parameter indicates whether previous FurnishChargingInformation free format data is appended or overwritten. Refer to 3GPP TS 23.078 [7] for details on the usage of this parameter. + +## 11.19.2 Responding entity (gsmSSF) + +### 11.19.2.1 Normal procedure + +gsmSSF preconditions: + +- (1) The gsmSSF FSM is in the state + +"Waiting\_for\_Instructions"; or +"Waiting\_for\_end\_of\_User\_Interaction"; or +"Waiting\_for\_end\_of\_Temporary\_Connection"; or +"Monitoring". + +gsmSSF postconditions: + +- (1) No gsmSSF FSM state transition. + +On receipt of this operation the gsmSSF performs actions to create the Logical call record if necessary, and writes the free-format information carried in the operation into the Logical call record. A FurnishChargingInformation operation will create a Logical Call Data Record (CDR) if such a record does not already exist for the indicated leg. Refer to sect. 11.26.1 for the handling in the case of successive FurnishChargingInformation operations for a call leg. + +The Logical CDRs will be associated for a given call into one or more physical CDRs, as specified in 3GPP TS 32.250 [13]. + +A logical call record is output to a physical CDR when a disconnection event is propagated to the call leg associated with it, or when a Connect operation to create a connection to a Follow-on Called Party is received. Successive FurnishChargingInformation operations indicating the calling leg (leg1) may overwrite data from previously received FurnishChargingInformation operation(s) indicating that leg during the entire call or call attempt. Successive + +FurnishChargingInformation operations indicating a called leg (leg2 or higher) may overwrite any previously received data from FurnishChargingInformation operation(s) indicating that called leg until the called leg representing that particular called party number is released from the call. When a new called party is created as a result of a follow-on call, and a FurnishChargingInformation operation indicating the called leg is received, then a new Logical call record shall be created for that call leg, for that portion of the call. From then on, any subsequent FurnishChargingInformation operations for that called party may overwrite the data from any previous FurnishChargingInformation operation(s) for the called leg presenting that particular called party number. Logical call records that have been output already are not affected. + +No Logical call record is output at the end of a user interaction. + +## 11.19.2.2 Error handling + +Generic error handling for the operation related errors are described in clause 10 and the TC services which are used for reporting operation errors are described in clause 14. + +# 11.20 InitialDP procedure + +## 11.20.1 General description + +The gsmSSF uses this operation after detection of a TDP-R in the BCSM, to request the gsmSCF for instructions to complete the call. + +### 11.20.1.1 Parameters + +- **serviceKey:** +This parameter indicates to the gsmSCF the requested IN service. It is used to address the required application/SLP within the gsmSCF; this parameter is not for SCP addressing. +- **calledPartyNumber:** +This parameter contains the number used to identify the called party in the forward direction, i.e. see ETSI EN 300 356-1 [23]. This parameter shall be sent only in the Mobile Terminating, Mobile Forwarding, mobile originating on unsuccessful TDP and trunk originating cases. For the trunk originating case the end of pulsing signal (ST) is included in the calledPartyNumber address signals if it has been received or the MSC has determined that the called number information is complete. +- **callingPartyNumber:** +This parameter carries the calling party number to identify the calling party or the origin of the call. See ETSI EN 300 356-1 [23] Calling Party Number signalling information. +- **callingPartysCategory:** +Indicates the type of calling party (e.g. operator, pay phone, ordinary subscriber). See ETSI EN 300 356-1 [23] Calling Party Category signalling information. +- **locationNumber:** +This parameter is used to convey the geographical area address for mobility services, see ITU-T Recommendation Q.762 [44]. It is used when "callingPartyNumber" does not contain any information about the geographical location of the calling party (e.g., origin dependent routeing when the calling party is a mobile subscriber). +- **originalCalledPartyID:** +If the call has met call forwarding on the route to the gsmSSF, then this parameter carries the dialled digits. Refer to EN 300 356-1[23] Original Called Number signalling information. +- **highLayerCompatibility:** +This parameter indicates the type of the high layer compatibility, which will be used to determine the ISDN - teleservice of a connected ISDN terminal. The highlayerCompatibility can also be transported by ISUP (e.g. within the ATP (see ITU-T Recommendation Q.763 [45]) parameter). +- **additionalCallingPartyNumber:** +The calling party number provided by the access signalling system of the calling user, e.g. provided by a PBX. + +- bearerCapability: +This parameter indicates the type of the bearer capability connection or the transmission medium requirements to the user. It is a network option to select which of the two parameters to be used: + - bearerCap: +This parameter contains the value of the ISUP User Service Information parameter. + +The parameter "bearerCapability" shall be included in the "InitialDP" operation only in the case the ISUP User Service Information parameter is available at the gsmSSF. + +If User Service Information and User Service Information Prime are available at the gsmSSF, then the "bearerCap" shall contain the value of the User Service Information Prime parameter. +- eventTypeBCSM: +This parameter indicates the armed BCSM DP event, resulting in the "InitialDP" operation. +- redirectingPartyID: +This parameter indicates the last directory number the call was redirected from. +- redirectionInformation: +This parameter contains forwarding related information, such as redirecting counter. +See ITU-T Recommendation Q.763 [45] Redirection Information signalling information. +- iPSSPCapabilities: +This parameter indicates which gsmSRF resources supported within the VMSC or GMSC the gsmSSF resides in are attached and available. +- serviceInteractionIndicatorsTwo: +This parameter contains indicators that are used to resolve interactions between CAMEL based services and network based services. +- IMSI: +This parameter contains the IMSI of the mobile subscriber for which the service is invoked. +- subscriberState: +This parameter indicates the state of the mobile subscriber for which the service is invoked. The possible states are "busy", "idle" and "not reachable". +- locationInformation: +This parameter indicates the location of the MS and the age of the information defining the location. +- ext-BasicServiceCode: +This parameter indicates the Basic Service Code. +- callReferenceNumber: +This parameter contains the call reference number assigned to the call by the CCF. +- mscAddress: +This parameter contains the mscId assigned to the MSC. +- gsmAddress: +This parameter contains the gsmId assigned to the GMSC. +- calledPartyBCDNumber: +This parameter contains the number used to identify the called party in the forward direction. It may also include service selection information, including \* and # characters. +- time&Timezone: +This parameter contains the time that the gsmSSF was triggered, and the time zone that the invoking gsmSSF resides in. +- callForwardingSS-Pending: +This parameter indicates that a forwarded-to-number was received and that the call will be forwarded due to the Call Forwarding supplementary service in the GMSC or in the VMSC, unless otherwise instructed by the gsmSCF. + +- carrier: + +This parameter contains carrier information. It consists of the carrier selection field followed by the Carrier ID information associated with the calling subscriber of a mobile originating call or trunk originating call, the called subscriber of a mobile terminating call or the forwarding subscriber of a mobile forwarded call. + +It contains the following embedded parameter: + +- carrierSelectionField: + +This parameter indicates how the selected carrier is provided (e.g. pre-subscribed). + +- carrierID: + +This parameter indicates the carrier to use for the call. It contains the digits of the carrier identification code. + +- cug-Index: + +This parameter is used to select a CUG for an outgoing call at the user, or to indicate an incoming CUG call to the user. + +- cug-Interlock: + +This parameter uniquely identifies a CUG within a network. + +- cug-OutgoingAccess: + +This parameter indicates if the calling user has subscribed to the outgoing access inter-CUG accessibility subscription option. + +- cGEncountered: + +This parameter indicates the type of call gapping the related call has been subjected to, if any. + +- cause: + +This parameter indicates the release cause which triggered the event: + +For Route\_Select\_Failure" it shall contain the "FailureCause", if available. + +For T\_Busy it may contain the following parameters, if available. + +- If the busy event is triggered by an ISUP release message, then the BusyCause shall a copy of the ISUP release cause, for example: Subscriber absent, 20 or User busy, 17. + +- If the busy event is triggered by a MAP error, for example: Absent subscriber, received from the HLR, then the MAP cause is mapped to the corresponding ISUP release cause. + +- If the busy event is triggered by call forwarding invocation in the GMSC or VMSC, then the BusyCause shall refer to the type of the call forwarding service in accordance with the mapping table in 3GPP TS 23.078 [7]. + +- forwardingDestinationNumber: + +This parameter contains the forwarding destination. + +- ms-Classmark2: + +This parameter contains the MS Classmark 2 of the mobile subscriber for which the service is invoked. + +- iMEI: + +This parameter contains the IMEI (with software version) of the mobile subscriber for which the service is invoked. + +- supportedCamelPhases: + +This parameter indicates the CAMEL Phases supported in the GMSC or VMSC which sends this operation. + +- offeredCamel4Functionalities: + +This parameter contains the offered CAMEL phase 4 functionalities. + +- bearerCapability2: + +This parameter indicates the type of the bearer capability connection or the transmission medium requirements to the user. + +- ext-BasicServiceCode2: + +This parameter indicates the Basic Service Code2. + +- highLayerCompatibility2: +This parameter indicates the high layer compatibility2 for a SCUDIF call. +- lowLayerCompatibility: +This parameter indicates the low layer compatibility. +- lowLayerCompatibility2: +This parameter indicates the low layer compatibility2 for a SCUDIF call. +- enhancedDialledServicesAllowed: +This parameter indicates that the gsmSCF may use the Enhanced Dialled Services (EDS) for this call. +- UU-Data: +This parameter contains user-to-user signalling service related information. +- collectInformationAllowed: +This parameter indicates that the gsmSCF may use Collect Information for this call. +- releaseCallArgExtensionAllowed: +This parameter indicates that the gsmSCF may use Extensions in Release Call operation for this call. + +## 11.20.2 Invoking entity (gsmSSF) + +### 11.20.2.1 Normal procedure + +gsmSSF preconditions: + +- (1) An event fulfilling the criteria for the DP being executed has been detected. +- (2) Call gapping and SS7 overload are not in effect for the call. + +gsmSSF postconditions: + +- (1) If the DP was armed as a TDP-R and trigger conditions, if present, are fulfilled, then a control relationship between the gsmSCF and the gsmSSF is established. The gsmSSF FSM transits to the state "Waiting\_for\_Instructions". + +The address of the gsmSCF shall be fetched from the valid CSI. The gsmSSF shall provide all available parameters to the gsmSCF. + +If no triggering takes place, because trigger conditions were not fulfilled, then the gsmSSF shall proceed with call handling without CAMEL Service. + +The gsmSSF application timer Tssf is loaded and started when the gsmSSF sends "InitialDP" for requesting instructions from the gsmSCF. It is used to prevent excessive call suspension time. + +### 11.20.2.2 Error handling + +If the gsmSCF is not accessible, then the call proceeds in accordance with the Default Call Handling parameter in the CSI. + +When Tssf expires, then the gsmSSF shall abort the interaction with the gsmSCF by means of an abort to TC and shall call continue the call in accordance with the Default Call Handling parameter in the valid CSI. + +If the calling party abandons after the sending of "InitialDP" and before the TC dialogue is established, then the gsmSSF shall abort the interaction with the gsmSCF by means of an abort to TC. + +Generic error handling for the operation related errors are described in clause 10 and the TC services which are used for reporting operation errors are described in clause 14. + +## 11.21 InitiateCallAttempt procedure + +### 11.21.1 General Description + +The gsmSCF uses this operation to request the gsmSSF to create a new call leg to one call party using the address information provided by the gsmSCF (e.g. wake-up call). InitiateCallAttempt can also be used to create an additional call party in a new Call Segment within an existing Call Segment Association. In both use cases the gsmSCF shall subsequently arm O\_Answer as an EDP-R and the call failure events (Route\_Select\_Failure, O\_Busy and O\_No\_Answer) as EDP-Rs and/or EDP-Ns, in order to enable the gsmSCF to treat this call appropriately when any of these events is encountered. + +#### 11.21.1.1 Parameters + +##### 11.21.1.1.1 Argument Parameters + +- destinationRouteingAddress: +This parameter contains the called party number towards which the call shall be routed. +- callingPartyNumber: +This parameter identifies which number shall be regarded as the calling party for the created call. +- legToBeCreated: +This parameter indicates the LegID to be assigned to the newly created party. +- newCallSegment: +This parameter indicates the Call Segment ID to be assigned to the newly created Call Segment. +- callReferenceNumber: +This parameter contains the call reference number assigned to the call by the gsmSCF. +- gsmSCFAddress: +This parameter indicates the address of the gsmSCF initiating the operation. +- suppress-T-CSI: +This parameter indicates that the T-CSI for the served subscriber shall be suppressed for this call leg. + +##### 11.21.1.1.2 Result Parameters + +- supportedCamelPhases: +This parameter indicates the CAMEL Phases supported in the gsmSSF which receives this operation. +- offeredCamel4Functionalities: +This parameter contains the offered CAMEL phase 4 functionalities. +- releaseCallArgExtensionAllowed: +This parameter indicates that the gsmSCF may use Extensions in Release Call operation for this call. + +### 11.21.2 Responding entity (gsmSSF) + +#### 11.21.2.1 Normal procedure + +gsmSSF preconditions: + +None. + +gsmSSF postconditions: + +- 1) A new O-BCSM has been created; call processing is suspended. +- 2) A Return Result is sent to the gsmSCF. +- 3) The CS\_gsmSSF FSM transits from the state "Idle" to the state "Waiting\_for\_Instructions". + +All subsequent operations are treated in accordance with their normal procedures. + +### 11.21.2.2 Error handling + +Generic error handling for the operation related errors is described in clause 10, and the TC services which are used for reporting operation errors are described in clause 14. + +## 11.22 MoveLeg procedure + +### 11.22.1 General Description + +The gsmSCF uses this operation to request the gsmSSF to move the leg from its current Call Segment to CSID1. + +#### 11.22.1.1 Parameters + +- legIDToMove: +This parameter indicates the leg that shall be moved. + +### 11.22.2 Responding entity (gsmSSF) + +#### 11.22.2.1 Normal procedure + +gsmSSF preconditions: + +- 1) A control relationship exists between the gsmSCF and the gsmSSF. +- 2) The source BCSM is in the alerting phase or in the active phase. +- 3) The target Call Segment fulfills the following preconditions: + - At least one leg in the target Call Segment has reached the active phase, or + - The original BCSM in the target Call Segment is at Terminating\_Attempt\_Authorised, Analysed\_Information (for EDS only) or Collected\_Info detection point, and the outgoing leg of that BCSM has been disconnected by the gsmSCF, or + - The call was created by the gsmSCF. +- 4) The CS\_gsmSSF FSM for each Call Segment involved is in the state "Waiting\_for\_Instructions" or in the state "Monitoring". +- 5) User Interaction is not in progress in either Call Segment. + +gsmSSF postconditions: + +- 1) The gsmSSF performs the appropriate call processing actions. +- 2) The CS\_gsmSSF FSM for CSID1 transits to the state "Waiting\_for\_Instructions". The BCSM instances within CSID1 transit to the O\_Mid\_Call DP or to the T\_Mid\_Call DP, if not already suspended. The Mid\_Call EDP shall not be reported for this case. +- 3) The CS\_gsmSSF process for the source Call Segment is terminated. +- 4) A Return Result is sent to the gsmSCF immediately after successful execution of this operation. +- 5) A Pending ApplyChargingReport for the source call segment shall be sent to the gsmSCF. + +#### 11.22.2.2 Error handling + +Generic error handling for the operation related errors is described in clause 10, and the TC services which are used for reporting operation errors are described in clause 14. + +## 11.23 PlayAnnouncement procedure + +### 11.23.1 General description + +The gsmSCF uses this operation for inband interaction with a CS user. + +#### 11.23.1.1 Parameters + +- informationToSend: +This parameter indicates an announcement a tone to be sent to the end-user by the gsmSRF. + - inbandInfo: +This parameter specifies the inband information to be sent. + - messageID: +This parameter indicates the message(s) to be sent; this may be one of the following: + - elementaryMessageID: +This parameter indicates a single announcement. + - text: +This parameter indicates a text to be sent. The text shall be transformed to inband information (speech) by the gsmSRF. This parameter consists of two parameters; messageContent and attributes. The attributes of the text parameter may consist of items such as language. + - elementaryMessageIDs: +This parameter specifies a sequence of announcements. + - variableMessage: +This parameter specifies an announcement with one or more variable parts. + - numberOfRepetitions: +This parameter indicates the maximum number of times the message shall be sent to the end-user. + - duration: +This parameter indicates the maximum time duration in seconds that the message shall be played or repeated. A value of "0" indicates endless repetition. + - interval: +This parameter indicates the time interval in seconds between successive messages, i.e. the time between the end of the announcement and the start of the repetition of this announcement. This parameter may be used only when "numberOfRepetitions" is > 1. +- tone: +This parameter specifies a tone to be sent to the end-user. + - toneID: +This parameter indicates the tone to be sent. + - duration: +This parameter indicates the time duration in seconds of the tone to be sent. A value of "0" indicates infinite duration. +- disconnectFromIPForbidden: +This parameter indicates whether the gsmSRF may initiate a disconnection from the gsmSSF after the interaction has been completed. + +If this parameter is TRUE, then the gsmSRF shall not initiate a disconnection. If this parameter is FALSE, then the gsmSRF may initiate a disconnection. +- requestAnnouncementCompleteNotification: +This parameter indicates whether or not a "SpecializedResourceReport" shall be sent to the gsmSCF when all information has been sent. + +- requestAnnouncementStartedNotification: +This parameter indicates whether or not a "SpecializedResourceReport" shall be sent to the gsmSCF when the first announcement or tone has started. +- callSegmentID: +This parameter indicates the Call Segment to which the user interaction shall apply. + +## 11.23.2 Responding entity (gsmSRF) + +### 11.23.2.1 Normal procedure + +gsmSRF preconditions: + +- (1) The SRSM-FSM is in the state "Connected"; if the gsmSRF received previously an operation from the gsmSCF, then the SRSM-FSM is in the state "User Interaction". +- (2) When the first announcement or tone has started and "RequestAnnouncementStartedNotification" is TRUE, then the SRSM shall send a "SpecializedResourceReport" operation, containing the "FirstAnnouncementStarted" parameter, to the gsmSCF. + +gsmSRF postconditions: + +- (1) The gsmSRF sends the information to the user as indicated by "informationToSend". +- (2) The SRSM-FSM transits to the state "User Interaction", or remains in the same state. +- (3) If all information has been sent and "RequestAnnouncementCompleteNotification" is TRUE, then the SRSM shall send a "SpecializedResourceReport" operation, containing the "AllAnnouncementsComplete" parameter, to the gsmSCF. +- (4) If all information has been sent and "disconnectFromIPForbidden" is FALSE, then the SRSM disconnects the gsmSRF from the user. + +The announcement sent to the end-user is ended in the following conditions: + +- if neither "duration" nor "numberOfRepetitions" is specified, then the network specific announcement ending conditions shall apply; or +- if "numberOfRepetitions" is specified, when all repetitions have been sent; or +- if duration is specified, when the duration has expired. The announcement is repeated until this condition is met; or +- if "duration" and "numberOfRepetitions" is specified, when one of both conditions is satisfied (whichever comes first). + +### 11.23.2.2 Error handling + +If a Cancel operation is received before or during the processing of the operation, then that operation shall be cancelled immediately and the error "Canceled" shall be reported to the gsmSCF. + +Generic error handling for the operation related errors are described in clause 10 and the TC services which are used for reporting operation errors are described in clause 14. + +## 11.24 PlayTone procedure + +### 11.24.1 General description + +The gsmSCF uses this operation to instruct the gsmSSF to play tones to a leg or a Call Segment using the MSC's tone generator. + +If a Call Segment is indicated, then the tones shall be played to all active legs in that Call Segment. If a leg is indicated, then the tones shall be played to that leg only. + +### 11.24.1.1 Parameters + +- legOrCallSegment: +This parameter indicates the leg or Call Segment to which the PlayTone operation shall apply. +- bursts: +This parameter indicates the variable sequence of tones to be played and consists of the following parameters: + - numberOfBursts: +This parameter indicates the number of bursts that form the burstlist. + - burstInterval: +This parameter indicates the time interval between successive bursts in a sequence of bursts. + - numberOfTonesInBurst: +This parameter indicates the number of tones to be played in each burst. + - toneDuration: +This parameter indicates the time duration of a single tone in a burst. + - toneInterval: +This parameter indicates the time interval between successive tones in a burst. + +## 11.24.2 Responding entity (gsmSSF) + +### 11.24.2.1 Normal procedure + +gsmSSF preconditions: + +The gsmSSF FSM is in one of the following states: + +"Monitoring"; or +"Waiting\_for\_Instructions". + +If a Call Segment is indicated, then at least one of the legs in that Call Segment is in the active phase. + +gsmSSF postconditions: + +- (1) No gsmSSF FSM state transition. + +### 11.24.2.2 Error handling + +Generic error handling for the operation related errors is described in clause 10 and the TC services used for reporting operation errors are described in clause 14. + +## 11.25 PromptAndCollectUserInfo procedure + +### 11.25.1 General description + +The gsmSCF uses this operation to interact with a call party in order to collect information. + +#### 11.25.1.1 Parameters + +- collectedInfo: + - collectedDigits: + +- minimumNbOfDigits: +This parameter specifies the minimum number of valid digits to be collected. +- maximumNbOfDigits: +This parameter specifies the maximum number of valid digits to be collected. The following applies: +"maximumNbOfDigits" $\geq$ "minimumNbOfDigits". +- endOfReplyDigit: +This parameter indicates the digit string used to signal the end of input. + +In the case that the "maximumNbOfDigits" > "minimumNbOfDigits" the following applies: + +If "endOfReplyDigit" is not present, then the end of input is indicated: + +- l) - when the inter-digit timer expires; or +- m) - when the number of valid digits received equals the "maximumNbOfDigits". + +If "endOfReplyDigit" is present, then the end of input is indicated: + +- n) - when the inter-digit timer expires; or +- o) - when the end of reply digit is received; or +- p) - when the number of valid digits received equals the "maximumNbOfDigits". + +When the end of input is reached, the collected digits are sent from gsmSRF to the gsmSCF, including the "endOfReplyDigit" if received by the gsmSRF. In the case the number of valid digits received is less than the "minimumNbOfDigits" when the inter-digit timer expires or when the end of reply digit is received, the input is considered to be erroneous. + +- cancelDigit: +This parameter indicates the cancel digit string that may be entered by the user to request a retry. All digits already received by the gsmSRF are discarded and the PromptAndCollectUserInformation procedure is performed again, thus e.g. the same announcement to request user information is given to the user and information is collected. If this parameter is not present, then the user is not able to request a retry. +- startDigit: +This parameter indicates the start digit string that indicates the start of the valid digits to be collected. The digits that are received by the gsmSRF before this start digit is received, are discarded and are not considered to be valid. The start digit string itself is considered to be valid digits. + +If this parameter is not present, then all received digits are considered to be valid. + +When the end of input is reached, the collected digits are sent from gsmSRF to the gsmSCF, including the "startDigit" if received by the gsmSRF. + +- firstDigitTimeout: +If this parameter is present, then the first digit shall be received by the gsmSRF before first-digit timer expiration. If the first digit is not received before first-digit timer expiration, then the input is considered to be erroneous. + +If this parameter is not present, then the gsmSRF shall use a default value for the first-digit timer. + +If "startDigit" is present, then the first-digit timer shall be stopped after the start digit is received. If "startDigit" is not present, then the first-digit timer shall be stopped when any digit is received, except when the digit matches the "cancelDigit", if present. + +- interDigitTimeout: + +If this parameter is present, then any subsequent valid or invalid digit shall be received by the gsmSRF before the inter-digit timer expires. As a result of receiving a digit, the inter-digit timer is reset and restarted. + +If a subsequent valid or invalid digit is not received before the inter-digit timer expires and the number of received valid digits is less than "minimumNbOfDigits", then the input is considered to be unsuccessful. + +If a subsequent valid or invalid digit is not received before the inter-digit timer expires and the number of received valid digits is greater than "minimumNbOfDigits" and smaller than or equal to "maximumNbOfDigits", then the input is considered to be successful. + +If the "interDigitTimeout" is not present, then the gsmSRF shall use a default value for the inter-digit timer. + +- errorTreatment: + +This parameter defines what specific action shall be taken by the gsmSRF in the event of error conditions occurring. + +- interruptableAnnInd: + +If this parameter is TRUE, then the announcement shall interrupted after the first valid or invalid digit is received by the gsmSRF. If the announcement is interrupted, then a first-digit timer shall not apply anymore. However, if the announcement has not been interrupted, then the first-digit timer shall be started after the announcement has been finished. + +If this parameter is FALSE, then the announcement shall not be interrupted after the first digit is received by the gsmSRF. The received digits during the announcement are discarded and considered to be invalid. All other specified parameters ("minimumNbOfDigits", "maximumNbOfDigits", "endOfReplyDigit", etc.) do not apply before the announcement has been finished. The first-digit timer shall be started after the announcement has been finished. + +- voiceInformation: + +If this parameter is FALSE, then all valid or invalid digits shall be entered by DTMF. + +If this parameter is TRUE, then the calling user is required to provide all valid or invalid information by speech. The gsmSRF shall perform voice recognition and shall translate the provided information into digits. The end of reply digit(s), if required, shall be provided by speech. + +- voiceBack: + +If this parameter is FALSE, then no voice back information shall be given by the gsmSRF. + +If this parameter is TRUE, then the valid input digits received by the gsmSRF shall be announced back to the calling user immediately after the end of input is received. The invalid input digits will not be announced back to the calling user. The end of reply digit(s) shall not be voiced back to the calling user. + +- disconnectFromIPForbidden: + +This parameter indicates whether the gsmSRF may initiate a disconnection from the gsmSSF after the interaction has been completed. + +If this parameter is TRUE, then the gsmSRF shall not initiate a disconnection. If this parameter is FALSE, then the gsmSRF may initiate a disconnection. + +- informationToSend: + +This parameter indicates an announcement or tone to be sent to the end-user by the gsmSRF. + +- inbandInfo: +This parameter specifies the inband information to be sent. +- messageID: +This parameter indicates the message(s) to be sent,, this may be one of the following: + - elementaryMessageID: +This parameter indicates a single announcement. + - text: +This parameter indicates a text to be sent. The text shall be transformed to inband information (speech) by the gsmSRF. The attributes of text may consist of items such as language. + - elementaryMessageIDs: +This parameter specifies a sequence of announcements. + - variableMessage: +This parameter specifies an announcement with one or more variable parts. +- numberOfRepetitions: +This parameter indicates the maximum number of times the message shall be sent to the end-user. +- duration: +This parameter indicates the maximum time duration in seconds that the message shall be played or repeated. A value of "0" indicates endless repetition. +- interval: +This parameter indicates the time interval between successive messages, i.e. the time between the end of the announcement and the start of the repetition of this announcement. This parameter may be used only when "numberOfRepetitions" > 1. +- tone: +This parameter specifies a tone to be sent to the end-user. + - toneID: +This parameter indicates the tone to be sent. + - duration: +This parameter indicates the time duration in seconds of the tone. A value of "0" indicates infinite duration. +- requestAnnouncementStartedNotification: +This parameter indicate whether or not a "SpecializedResourceReport" shall be sent to the gsmSCF when the first announcement or tone has started. +- callSegmentID: +This parameter indicates the Call Segment to which the user interaction shall apply. + +#### Result Parameter: + +- digitsResponse: +This parameter contains the information collected from the end-user. + +## 11.25.2 Responding entity (gsmSRF) + +### 11.25.2.1 Normal procedure + +#### gsmSRF preconditions: + +- (1) The SRSM-FSM is in the state "Connected"; if the gsmSRF received previously an operation from the gsmSCF, then the SRSM-FSM is in the state "User Interaction". +- (2) If the first announcement or tone has started and "RequestAnnouncementStartedNotification" is TRUE, then the SRSM sends a "SpecializedResourceReport" operation, containing the "FirstAnnouncementStarted" parameter, to the gsmSCF. + +gsmSRF postconditions: + +- (1) The gsmSRF has sent the information to the end-user as indicated by "informationToSend". +- (2) The collected information from the end-user is sent to the gsmSCF as RETURN RESULT of the "PromptAndCollectUserInfoInformation". +- (3) If the "disconnectFromIPForbidden" is FALSE, then the gsmSRF initiates a bearer channel disconnect to the gsmSSF and the SRSM FSM transits to the state "Idle". +- (4) Otherwise, the SRSM FSM transits to the state "User Interaction" or remains in the same state. + +The announcement sent to the end-user is ended in the following conditions: + +- if neither "duration" nor "numberOfRepetitions" is specified, then the network specific announcement ending conditions shall apply; or +- if "numberOfRepetitions" is specified, when all repetitions have been sent; or +- if duration is specified, when the duration has expired. The announcement is repeated until this condition is met; or +- if "duration" and "numberOfRepetitions" is specified, when one of both conditions is satisfied (whichever comes first). + +If the parameter "interruptableAnnInd" is not FALSE and the end-user has responded with a digit during the sending of the announcement, then the above conditions are overruled. In that case, the announcement shall be ended immediately. + +The parameter "errorTreatment" specifies how the gsmSRF shall treat an error. The value "reportErrorToSCF" means that the error shall be reported to the gsmSCF by means of Return Error with "ImproperCallerResponse". The value "help" indicates that no error shall be reported to gsmSCF but assistance shall be given to the end-user in the form of a network dependent default announcement (which may be dependent on the context, i.e. the sent message). The value "repeatPrompt" indicates that no error shall be reported to the gsmSCF but the prompt shall be repeated to the end-user. The error handling procedures related to "help" and "repeatPrompt" shall be done only once per "PromptAndCollectUserInfoInformation" operation. + +NOTE Note on processing "endOfInput" + +The receipt of any "endOfInput" condition (e.g endOfReplyDigit, cancelDigit, firstDigitTimeout, interDigitTimeout) terminates immediately the ongoing input. In other words when e.g an endOfReplyDigit is received, then the receipt of a subsequent cancelDigit will not be processed anymore. + +## 11.25.2.2 Error handling + +If a Cancel operation is received before or during the processing of the operation, then the operation shall be cancelled immediately and the error "Canceled" shall be reported to the gsmSCF. + +Generic error handling for the operation related errors are described in clause 10, the TC services which are used for reporting operation errors are described in clause 14. + +If any of the parameter restrictions are violated (e.g. "minimumNbOfDigits" > "maximumNbOfDigits"), then an operation error has occurred. + +## 11.26 ReleaseCall procedure + +### 11.26.1 General description + +The gsmSCF uses this operation to tear down a call at any phase. + +#### 11.26.1.1 Parameters + +- allCallSegments: +This parameter gives an indication to the gsmSSF about the reason of releasing this specific call. This may be used by gsmSSF for generating specific tones to the different parties in the call or to fill in the "cause" in the release message. +- allCallSegmentsWithExtension: +This parameter gives an indication to the gsmSSF about the reason of releasing this specific call. This may be used by gsmSSF for generating specific tones to the different parties in the call or to fill in the "cause" in the release message. It additionally allows for the sending of the extensions parameter to the gsmSSF. + +### 11.26.2 Responding entity (gsmSSF) + +#### 11.26.2.1 Normal procedure + +gsmSSF preconditions: + +- (1) A control relationship exists between gsmSCF and gsmSSF. +- (2) The gsmSSF FSM is in the state "Waiting\_for\_Instructions" or in the state "Monitoring". + +gsmSSF postconditions: + +- (1) The gsmSSF FSM transits to the state "Idle" after sending any pending "CallInformationReport" or "ApplyChargingReport". All armed EDPs shall be disarmed. All connections and resources related to the call shall be released. + +#### 11.26.2.2 Error handling + +Operation related error handling is not applicable, due to class 4 operation. + +## 11.27 RequestReportBCSMEVENT procedure + +### 11.27.1 General description + +The gsmSCF uses this operation to request the gsmSSF to monitor for a call-related event (e.g., BCSM events such as O\_Busy or O\_No\_Answer) and to send a notification to the gsmSCF when the event is detected. + +The monitoring of more than one event may be requested with a single "RequestReportBCSMEVENT" operation, but each of these requested events will be reported in a separate "EventReportBCSM" operation. + +NOTE: If the RequestReportBCSMEVENT requests arming of the current DP from which the call processing was suspended, then the next occurrence of the DP encountered during BCSM processing will be detected (i.e. not the current one from which the call was suspended). + +The DP arming principle is as follows: + +- The DPs O\_Disconnect and T\_Disconnect can be armed for any or all legs depending on the direction for which events have to be captured. As an example, the O\_Disconnect DP can be armed for leg1 and leg2; in this case, if a release request is received from the A-party, then it will be detected by the O\_Disconnect DP armed for leg1, while a release request from the B-party will be detected by the O\_Disconnect DP armed for leg2. +- The O\_Abandon DP can be armed only for leg1 in the O-BCSM and the T\_Abandon DP can be armed only for leg1 in the T-BCSM. + +- The Collected\_Info DP can be armed only for leg1 in the O-BCSM for TO calls. + +**Table 11-1: DP Arming Table for O-BCSM:** + +| O-BCSM | leg1 | Not leg 1 | Default leg_ID | +|-------------------------|------|-----------|----------------| +| O_Term_Seized DP | - | X | 2 | +| Route_Select_Failure DP | - | X | 2 | +| O_Busy DP | - | X | 2 | +| O_No_Answer DP | - | X | 2 | +| O_Answer DP | - | X | 2 | +| O_Disconnect DP | X | X | -(note 1) | +| O_Abandon DP | X | - | 1 | +| O_Mid_Call | X | - | 1 | +| O_Change_Of_Position | X | - | 1 | +| O_Service_Change | X | - | 1 | +| Collected_Info DP | X | - | 1 | + +Note 1: The "legID" parameter shall be included +Nomenclature: X = Arming Applicable +- = Arming not Applicable + +**Table 11-2: DP Arming Table for T-BCSM:** + +| T-BCSM | leg2 | leg1 | Default Leg ID | +|----------------------|------|------------|----------------| +| Call_Accepted DP | X | - | 2 | +| T_Busy DP | X | - | 2 | +| T_No_Answer DP | X | - | 2 | +| T_Answer DP | X | - | 2 | +| T_Disconnect DP | X | X | -(note 1) | +| T_Abandon DP | - | X (note 2) | 1 | +| T_Mid_Call | X | - | 2 | +| T_Change_Of_Position | X | - | 2 | +| T_Service_Change | X | - | 2 | + +Note 1: The "legID" parameter shall be included +Note 2: T\_Abandon can be armed for leg1 only. +Nomenclature: X = Arming Applicable +- = Arming not Applicable + +### 11.27.1.1 Parameters + +- bcsmevents: +This parameter specifies the event or events of which a report is requested. + - eventTypeBCSM: +This parameter specifies the type of event of which a report is requested. + - monitorMode: +This parameter indicates how the event shall be reported. If the "monitorMode" is "interrupted", then the event shall be reported as a request; if the "monitorMode" is "notifyAndContinue", then the event shall be reported as a notification; if the "monitorMode" is "transparent", then the event shall not be reported. + - legID: +This parameter indicates the party in the call for which the event shall be reported. The gsmSCF shall use the option "sendingSideID" only. + - sendingSideID: +If not included, then the default values for LegID are assumed according to the tables 11-1 and 11-2. +The "legID" parameter shall always be included for the events O\_Disconnect and T\_Disconnect. + - dPSpecificCriteria: +This parameter contains information specific to the EDP that shall be armed. + +- numberOfDigits: +This parameter indicates the number of digits requested for the CollectedInfo event. +- interDigitTimeout: +This parameter indicates the inter-digit timer value for the CollectedInfo event. +- applicationTimer: +This parameter indicates the No\_Answer timer value for the No\_Answer event. If the called party does not answer the call within the allotted time, then the gsmSSF shall report the event to the gsmSCF. This timer shall be shorter than the network No\_Answer timer. +- midCallControlInfo: +This parameter defines the criterion for the detection and reporting of mid-call digits. If this parameter is absent, then the first digit entered shall be reported. +- changeOfPositionControlInfo: +This parameter defines the criterion for the reporting of change of location. If this parameter is absent, then any change of position shall be reported. +- automaticRearm: +This parameter indicates that the gsmSSF shall rearm the DP whenever it is encountered. + +## 11.27.2 Responding entity (gsmSSF) + +### 11.27.2.1 Normal procedure + +gsmSSF preconditions: + +- (1) A control relationship exists between the gsmSSF and the gsmSCF. +- (2) The gsmSSF FSM is in the state "Waiting\_for\_Instructions" or in the state "Monitoring". + +NOTE: In the state "monitoring" only requests to disarm detection points (with MonitorMode set to "Transparent") or to send notifications of events (with MonitorMode set to "NotifyAndContinue") shall be accepted by the gsmSSF. + +gsmSSF postconditions: + +- (1) The requested EDPs are armed or disarmed as indicated. +- (2) Previously requested events are monitored until ended by a transparent monitor mode, until the end of the call, until the EDPs are detected or until the corresponding leg is released. +- (3) The gsmSSF FSM remains in the same state, unless all EDPs have been disarmed and no CallInformationReport or ApplyChargingReport has been requested; in the latter case, the gsmSSF FSM transits to the state "Idle". + +### 11.27.2.2 Error handling + +Generic error handling for the operation related errors are described in clause 10 and the TC services which are used for reporting operation errors are described in clause 14. + +## 11.28 ResetTimer procedure + +### 11.28.1 General description + +The gsmSCF uses this operation to refresh the Tssf application timer, in order to avoid the Tssf time-out at the gsmSSF. + +#### 11.28.1.1 Parameters + +- timerID: +This parameter indicates which timer shall be reset. The only permissible value of this parameter is "tsf". +- timerValue: +This parameter specifies the value to which the timer shall be set. + +- callSegmentID: + +This parameter indicates the Call Segment in the gsmSSF for which the timer shall be reset. + +## 11.28.2 Responding entity (gsmSSF) + +### 11.28.2.1 Normal procedure + +gsmSSF preconditions: + +- (1) Basic call processing has been suspended at a DP. +- (2) The gsmSSF FSM is in the state "Waiting\_for\_Instructions", the state "Waiting\_for\_end\_of\_User\_Interaction" or in the state "Waiting\_for\_end\_of\_Temporary\_Connection". + +gsmSSF postconditions: + +- (1) The Tssf timer is loaded with the value received from the gsmSCF and is restarted. +- (2) No gsmSSF FSM state transition. + +### 11.28.2.2 Error handling + +Generic error handling for the operation related errors are described in clause 10 and the TC services which are used for reporting operation errors are described in clause 14. + +## 11.29 SendChargingInformation procedure + +### 11.29.1 General description + +The gsmSCF uses this operation to instruct the gsmSSF on the Advice of Charge information to be sent by the gsmSSF. The SendChargingInformation operation may be invoked on multiple occasions. + +The SendChargingInformation operation may be used for MO and MT calls in the VMSC. In the case of an MT call, the CSE provided e-parameters are not used by Mobile Station if a call forwarding or follow-on call occurs. + +#### 11.29.1.1 Parameters + +- sCIBillingChargingCharacteristics: + +This parameter is a choice between two lists of information. + +The first list shall be sent only if there is neither an active call leg, nor a Temporary Connection, nor a connection to a gsmSRF. It contains the following parameters: + +- aOCBeforeAnswer: +This is a list of the following information: + - aOCInitial: +This is a set of Charge Advice Information (CAI) elements, as defined in 3GPP TS 22.024 [2]. These CAI elements shall be sent by the gsmSSF to the MS when Answer is detected and a tariff switch for the "CSE control of e-parameters" has not yet occurred. + - aOCSubsequent: +This list may contain the following information: + - cAIElements: +This is a set of Charge Advice Information (CAI) elements, as defined in 3GPP TS 22.024 [2]. These CAI elements shall be sent to the MS when Answer is detected and a tariff switch for the "CSE control of e-parameters" has occurred previously, or when Answer has previously been detected and a tariff switch for the "CSE control of e-parameters" occurs. + - tariffSwitchInterval (for the "CSE control of e-parameters"): +This parameter indicates the time duration until the next tariff switch for the "CSE control of e-parameters". The measurement of the elapsed tariff switch period shall start immediately after successful execution of this operation. + +The second list in the choice shall be sent only if there is an active call leg or a Temporary Connection or a connection to a gsmSRF. It contains the following parameters: + +- aOCAfterAnswer: +This list may contain the following information: + - cAIElements: +This is a set of Charge Advice Information (CAI) elements, as defined in 3GPP TS 22.024 [2]. These CAI elements shall be sent to the MS by the gsmSSF when Answer is detected and a tariff switch for the "CSE control of e-parameters" has occurred previously, or when Answer has previously been detected and a tariff switch for the "CSE control of e-parameters" occurs. + - tariffSwitchInterval (for the "CSE control of e-parameters"): +This parameter indicates the time duration until the next tariff switch for the "CSE control of e-parameters". The measurement of the elapsed tariff switch period shall start immediately after successful execution of this operation. +- legID: +This parameter indicates where the charging information shall be sent. For Mobile Originated calls, only leg 1 shall be used. For Mobile Terminated calls in the VMSC, only the leg of the CAMEL subscriber shall be used. + +## 11.29.2 Responding entity (gsmSSF) + +### 11.29.2.1 Normal procedure + +gsmSSF preconditions: + +- (1) The gsmSSF FSM is in one of the following states: + +"Waiting\_for\_Instructions"; or +"Waiting\_for\_end\_of\_User\_Interaction"; or +"Waiting\_for\_end\_of\_Temporary\_Connection"; or +"Monitoring". + +gsmSSF postconditions: + +- (1) No gsmSSF FSM state transition. + +On receipt of this operation the gsmSSF performs actions to send the Advice of Charge information to the indicated Call Partys MS. + +If Advice of Charge shall be provided to a MS in conjunction with "CSE control of call duration", then the following sequence of operations may be sent by the gsmSCF to the gsmSSF in the following order, in the same TC-CONTINUE TC message: + +one or more ApplyCharging operations; SendChargingInformation operation. + +These operations shall be processed sequentially by the gsmSSF, in the order that they are sent by the gsmSCF. In this case, the parameters TariffSwitchInterval (for the "CSE control of call duration") may be present in any of the ApplyCharging operations and the parameter TariffSwitchInterval (for the "CSE control of e-parameters") may be present in the SendChargingInformation operation. + +The TariffSwitchInterval information received with the ApplyCharging operation shall set or overwrite the tariff switch timer for the "CSE control of call duration" in the gsmSSF and this duration timer shall run from the time of successful operation execution. + +The TariffSwitchInterval information received in the SendChargingInformation operation shall set or overwrite the tariff switch timer for the "CSE control of e-parameters" in the gsmSSF and this duration timer shall run from the time of successful operation execution. + +### 11.29.2.2 Error handling + +Generic error handling for the operation related errors are described in clause 10 and the TC services which are used for reporting operation errors are described in clause 14. + +## 11.30 SpecializedResourceReport procedure + +### 11.30.1 General description + +The gsmSRF uses this operation as a response to a "PlayAnnouncement" operation or a "PromptAndCollectUserInformation" operation. This operation shall be used only when the "requestAnnouncementCompleteNotification" parameter is TRUE or the "requestAnnouncementStartedNotification" parameter is TRUE in the "PlayAnnouncement" operation or the "PromptAndCollectUserInformation". + +#### 11.30.1.1 Parameters + +- allAnnouncementsComplete: +This parameter indicates that all the announcements and tones are complete. +- firstAnnouncementStarted: +This parameter indicates that the first announcement or tone has started. + +### 11.30.2 Invoking entity (gsmSRF) + +#### 11.30.2.1 Normal procedure + +gsmSRF preconditions: + +- (1) The gsmSRF FSM is in the state "User\_Interaction". +- (2) Either: + - (i) The sending of announcements and tones as defined in the "PlayAnnouncement" operation or the "PromptAndCollectUserInformation" operation has started and the parameter "RequestAnnouncementStartedNotification" in the "PlayAnnouncement" or "PromptAndCollectUserInformation" operation is TRUE; or + - (ii) A "PlayAnnouncement" operation has been executed, all announcements and tones have been sent and the parameter "RequestAnnouncementCompleteNotification" in the "PlayAnnouncement" operation is TRUE. + +gsmSRF postconditions: + +- (1) No gsmSRF FSM state transition. +- (2) If the "DisconnectFromIPForbidden" parameter is FALSE, then the gsmSRF initiates a bearer channel disconnect sequence to the gsmSSF using the applicable bearer channel signalling system after sending the "SpecializedResourceReport" operation to the gsmSCF. The gsmSRF transits to the state "Idle". + +#### 11.30.2.2 Error handling + +Operation related error handling is not applicable, due to class 4 operation. + +## 11.31 SplitLeg Procedure + +### 11.31.1 General Description + +The gsmSCF uses this operation to request the gsmSSF to separate one party from the source Call Segment and place it in a new target Call Segment. + +#### 11.31.1.1 Parameters + +- legToBeSplit: +This parameter indicates the party in the call to be split from the source Call Segment. +- newCallSegment: +This parameter indicates the CSID to be assigned to the newly-created Call Segment. + +## 11.31.2 Responding entity (gsmSSF) + +### 11.31.2.1 Normal procedure + +gsmSSF preconditions: + +- 1) A control relationship exists between the gsmSCF and the gsmSSF. +- 2) The CSID1 is either the source Call Segment or the target Call Segment. +- 3) When SplitLeg is used to move a leg into CSID1 (when CSID1 does not exist), then the BCSM for the leg to be split shall be in the alerting phase or in the active phase. + +When SplitLeg is used to split a leg off from CSID1 into a new Call Segment, then the BCSM for the leg to be split shall be in the active phase. + +- 4) User interaction is not in progress in the source Call Segment. + +gsmSSF postconditions: + +- 1) The gsmSSF performs the necessary actions to separate the specified leg from its original Call Segment and place it in a new target Call Segment. +- 2) The CS\_gsmSSF FSM for the new Call Segment transits to the state "Waiting\_for\_Instructions". +- 3) The CS\_gsmSSF FSM for the source Call Segment transits to the state "Waiting\_for\_Instructions". +- 4) The remaining BCSM instances within the source Call Segment transit to the O\_Mid\_Call DP or to the T\_Mid\_Call DP, unless already suspended at a DP. The Mid\_Call EDP shall not be reported for this case. +- 5) A Return Result shall be sent to the gsmSCF immediately after successful execution of this operation. +- 6) A pending ApplyChargingReport for the source call segment shall be sent to the gsmSCF. + +### 11.31.2.2 Error handling + +Generic error handling for the operation related errors is described in clause 10, and the TC services which are used for reporting operation errors are described in clause 14. + +--- + +## 12 Detailed operation procedures for SMS control + +- NOTE: For Short Message processing in a Circuit Switched network, the CAMEL interaction with SMS is done through the MSC/smsSSF. +For Short Message processing in a Packet Switched network, the CAMEL interaction with SMS is done through the SGSN/smsSSF. + +Any reference to the smsSSF applies to both the smsSSF co-located with the MSC and the smsSSF co-located with the SGSN. + +- NOTE Where a parameter for an SMS control Operation is marked OPTIONAL in ASN.1, the reader is referred to the conditions for presence for this parameter, specified in the respective Information Flow in 3GPP TS 23.078 [7]. + +## 12.1 ConnectSMS procedure + +### 12.1.1 General description + +The gsmSCF uses this operation to request the smsSSF to continue Short Message processing, such as routeing a Short Message to a specific destination or delivering a Short Message to the served subscriber, with modified information. + +### 12.1.1.1 Parameters + +- callingPartyNumber: +This parameter allows the gsmSCF to set the Calling Party Number parameter used in the network. It is used for showing the sending party's id (i.e. the originating address) to the receiving party. +- destinationSubscriberNumber: +This parameter contains the destination address to which the Short Message shall be routed by the SMSC. +- smscAddress: +This parameter contains the Short Message Service Centre address towards which the Short Message shall be routed. + +## 12.1.2 Responding entity (smsSSF) + +### 12.1.2.1 Normal procedure + +smsSSF preconditions: + +- (1) Mobile originating Short Message submission or Mobile terminating Short Message delivery attempt has been initiated. +- (2) Short Message processing has been suspended at the DP SMS\_Collected\_Info or at DP SMS\_Delivery\_Requested. +- (3) The smsSSF FSM is in the state "Waiting\_for\_Instructions". + +smsSSF postconditions: + +- (1) The smsSSF performs the Short Message processing actions to route the Short Message to the specified destination or to deliver the Short Message to the served subscriber. + +On receipt of this operation, the smsSSF performs the following actions: + +- if the callingPartyNumber, destinationSubscriberNumber or smscAddress are supplied, then these values shall be used for subsequent processing; +- if no EDPs have been armed, then the smsSSF FSM transits to the state "Idle". Otherwise, the smsSSF FSM transits to the state "Monitoring". + +The smsSSF shall not perform any implicit arming or disarming of DPs. + +Statistic counter(s) are not affected. + +### 12.1.2.2 Error handling + +Generic error handling for the operation related errors is described in clause 10 and the TC services which are used for reporting operation errors are described in clause 14. + +## 12.2 ContinueSMS procedure + +### 12.2.1 General description + +The gsmSCF uses this operation to request the smsSSF to proceed with processing at the DP at which it previously suspended processing to await gsmSCF instructions. The smsSSF continues processing without substituting new data from the gsmSCF. + +### 12.2.1.1 Parameters + +None. + +## 12.2.2 Responding entity (smsSSF) + +### 12.2.2.1 Normal procedure + +smsSSF preconditions: + +- (1) processing has been suspended at any DP. +- (2) The smsSSF FSM is in the state "Waiting\_for\_Instructions". + +smsSSF postconditions: + +- (1) processing continues. +- (2) The smsSSF FSM is in one of the following states: + - State "Monitoring" because at least one EDP was armed; or + - State "Idle" because no EDPs were armed. + +### 12.2.2.2 Error handling + +Operation related error handling is not applicable, due to class 4 operation. + +## 12.3 EventReportSMS procedure + +### 12.3.1 General description + +The smsSSF uses this operation to notify the gsmSCF of a short message related event previously requested by the gsmSCF in a RequestReportSMSEvent operation. + +#### 12.3.1.1 Parameters + +- eventTypeSMS: +This parameter identifies the type of event that is reported. +- eventSpecificInformationSMS: +This parameter contains the Short Message related information specific to the event. + - For O\_SMS\_Failure it shall contain the O-SMSCause, if available. + - For T\_SMS\_Failure it shall contain the T-SMSCause, if available. + - For O\_SMS\_Submitted and for T\_SMS\_Delivery it shall be empty. +- miscCallInfo: +This parameter contains DP related information. + - messageType: +This parameter indicates whether the message is a request, i.e. resulting from a RequestReportSMSEvent with "monitorMode" = "interrupted", or a notification, i.e. resulting from a RequestReportSMSEvent with "monitorMode" = "notifyAndContinue". + +### 12.3.2 Invoking entity (smsSSF) + +#### 12.3.2.1 Normal procedure + +smsSSF preconditions: + +- (1) The smsSSF FSM is in the state "Monitoring"; +- (2) The smsSSF FSM proceeds to an EDP that is armed. + +smsSSF postconditions: + +- (1) The smsSSF has applied implicit disarming of EDPs. +- (2) If message type was notification and there are no more EDPs armed, then the smsSSF FSM transits to the state "Idle". Otherwise, the smsSSF FSM transits to the state "Waiting\_for\_Instructions". + +### 12.3.2.2 Error handling + +Operation related error handling is not applicable, due to class 4 operation. + +## 12.4 FurnishChargingInformationSMS procedure + +### 12.4.1 General description + +The gsmSCF uses this operation to send charging related information to a Logical SMS record. This Logical SMS record is CAMEL specific. The first FurnishChargingInformationSMS operation leads to the generation of a Logical SMS record. Receipt of subsequent FurnishChargingInformationSMS operations shall overwrite or append the contents of the Logical SMS record. + +#### 12.4.1.1 Parameters + +- fCISMSBillingChargingCharacteristics: +This parameter contains the following parameters; +- fCIBCCCAMELsequence1: +This parameter contains the following parameters; +- freeFormatData: +This parameter contains free-format billing and/or charging characteristics. +- appendFreeFormatData: +This parameter indicates whether previous free-format data shall be appended or overwritten. See 3GPP TS 23.078 [7] for details. + +### 12.4.2 Responding entity (smsSSF) + +#### 12.4.2.1 Normal procedure + +smsSSF preconditions: + +- (1) The smsSSF FSM is in the state "Waiting\_for\_Instructions". + +smsSSF postconditions: + +- (1) No smsSSF FSM state transition. + +On receipt of this operation, the smsSSF performs actions to create the Logical SMS record, if a Logical SMS record does not already exist, and writes the free-format information carried in the operation into the Logical SMS record. Subsequent FurnishChargingInformationSMS operations received, by default, will overwrite the free-format data previously written in the Logical SMS record, as specified in 3GPP TS 23.078 [7]. It is also possible to append free format data with subsequent FurnishChargingInformationSMS operations. + +The Logical SMS records will be associated for a given Short Message submission or Short Message delivery with one or more physical CDRs, as specified in 3GPP TS 32.250 [13], 3GPP TS 32.251 [14] and 3GPP TS 22.115 [4]. + +#### 12.4.2.2 Error handling + +Generic error handling for the operation related errors is described in clause 10 and the TC services which are used for reporting operation errors are described in clause 14. + +## 12.5 InitialDPSMS procedure + +### 12.5.1 General description + +The smsSSF uses this operation after detection of a TDP-R in the smsSF FSM, to request the gsmSCF for instructions to complete the Short Message submission to the SMSC or the Short Message delivery to the served subscriber. + +#### 12.5.1.1 Parameters + +- destinationSubscriberNumber: +This parameter carries the ISDN number of the entity receiving the short message or the destination address of the destination subscriber, in an MO-SMS procedure. +- callingPartyNumber: +In an MO-SMS procedure, this parameter carries the MSISDN of the subscriber. In an MT-SMS procedure, this parameter carries the address of the submitter of the short message (i.e. the originating address). +- eventType: +This parameter indicates the armed smSSF FSM DP, resulting in the InitialDPSMS operation. +- iMSI: +IMSI of the mobile subscriber for whom the CAMEL service is invoked. +- locationInformationInMSC: +This parameter indicates the location of the MSC of the served subscriber. This parameter shall be included only if the InitialDP operation is sent from the MSC. +- locationInformationInSGSN: +This parameter indicates the location of the SGSN of the served subscriber. This parameter shall be included only if the InitialDPSMS operation is sent from the SGSN. +- serviceKey: +This parameter indicates to the gsmSCF the requested IN service. It is used to address the required application/SLP within the gsmSCF; it is not for gsmSCF addressing. +- timeAndTimeZone: +This parameter contains the time that the smsSSF was triggered, and the time zone that the invoking smsSSF resides in. +- tPDataCodingScheme: +This parameter indicates the data coding scheme of the TP-User-Data element within the TPDU. It may indicate a message class. The message class may indicate e.g. the originator of the Short Message. +- tPShortMessageSpecificInfo: +This parameter contains the 1st octet of the TPDU. Refer to 3GPP TS 23.040 [6] for a description of the various TPDUs. +- tPProtocolIdentifier: +This parameter indicates the protocol used above the SM-Transfer Layer. +- tPValidityPeriod: +This parameter indicates the length of the validity period or the absolute time of the validity period termination. +- sMSCAddress: +This parameter defines the address of the SMSC to which the Short Message is intended to be submitted. +- smsReferenceNumber: +This parameter contains the SMS Reference Number assigned to the Short Message by the MSC or SGSN. +- mscAddress: +This parameter contains the E.164 address of the MSC. It shall be present if the SMS processing takes place in the MSC; otherwise shall be absent. + +- **sgsn-Number:** +This parameter contains the Global Title of the SGSN. It shall be present if the SMS processing takes place in the SGSN; otherwise it shall be absent. +- **ms-Classmark2:** +This parameter contains the MS Classmark 2 of the mobile subscriber for which the service is invoked. +- **gPRSMSCClass:** +This parameter contains the GPRS MS capabilities of the mobile subscriber for which the CAMEL service is invoked. +- **iMEI:** +This parameter contains the IMEI (with software version) of the mobile subscriber for which the service is invoked. +- **calledPartyNumber:** +This parameter indicates the served subscriber in an MT-SMS procedure. + +## 12.5.2 Invoking entity (smsSSF) + +### 12.5.2.1 Normal procedure + +smsSSF preconditions: + +- (1) A Short Message submission attempt or a Short Message delivery attempt has been initiated. +- (2) An event has been detected at a DP. +- (3) For MT-SMS, the event fulfilled the criteria for the DP being executed. + +smsSSF postconditions: + +- (1) A control relationship has been established and the smsSSF waits for instructions from the gsmSCF. + +The address of the gsmSCF the InitialDPSMS operation shall be sent to, shall be fetched from the MO-SMS-CSI or the MT-SMS-CSI. The smsSSF shall provide all available parameters to the gsmSCF. + +A control relationship is established with the gsmSCF. The smsSSF application timer Tssf is laded with the deafult value and is started. It is used to prevent excessive Short Message submission or delivery suspension time. + +### 12.5.2.2 Error handling + +If the gsmSCF is not accessible, then the smsSSF instructs the MSC or SGSN to proceed with the Short Message processing in accordance with the Default SMS Handling parameter of the MO-SMS-CSI or MT-SMS-CSI. + +If Tssf expires, then the smsSSF aborts the interaction with the gsmSCF by means of an abort to TC and shall instruct the MSC or SGSN to proceed with the Short Message processing in accordance with the Default SMS Handling parameter of the MO-SMS-CSI CSI or MT-SMS-CSI. + +In the case of an MO-SMS Service, if the sending mobile party abandons after the sending of InitialDPSMS and before the TC dialogue is established, then the smsSSF shall abort the interaction with the gsmSCF by means of an abort to TC. + +Generic error handling for the operation related errors is described in clause 10 and the TC services which are used for reporting operation errors are described in clause 14. + +## 12.6 ReleaseSMS procedure + +### 12.6.1 General description + +The gsmSCF uses this operation to tear down a Short Message submission attempt or Short Message delivery attempt. The operation may be sent within a control relationship only; it is not allowed in a monitor relationship. + +#### 12.6.1.1 Parameters + +- rPCause: +This parameter gives an indication to the smsSSF about the reason of releasing this specific Short Message. For a MO-SMS Service, the rPCause shall be sent to the served subscriber in the RP-ERROR RPDU. For a MT-SMS Service, the rPCause shall be sent to the SMS-GMSC in the RP-ERROR RPDU. + +### 12.6.2 Responding entity (smsSSF) + +#### 12.6.2.1 Normal procedure + +smsSSF preconditions: + +- (1) The smsSSF FSM is in the state "Waiting\_for\_Instructions". +- (2) The FSM is in DP SMS\_Collected\_Info or in DP SMS\_Delivery\_Requested. + +smsSSF postconditions: + +- (1) The smsSSF FSM transits to the state "Idle". All armed EDPs shall be disarmed. All resources in the MSC or SGSN related to the Short Message shall be released. + +#### 12.6.2.2 Error handling + +Operation related error handling is not applicable, due to class 4 operation. + +## 12.7 RequestReportSMSEvent procedure + +### 12.7.1 General description + +The gsmSCF uses this operation to request the smsSSF to monitor for a Short Message related event (FSM events such as failure, delivery or submission) and to send a notification to the gsmSCF when the event is detected. + +The monitoring of more than one event may be requested with a single RequestReportSMSEvent operation, but each of these requested events will be reported in a separate EventReportSMS operation. + +#### 12.7.1.1 Parameters + +- smsEvents: +This parameter indicates the event or events of which a report is requested. + - eventTypeSMS: +This parameter indicates the type of event of which a report is requested. Values SMSCollectedInfo and SMSDeliveryRequested are not valid for the RequestReportSMSEvent operation. + - monitorMode: +This parameter indicates how the event shall be reported. When the "monitorMode" is "interrupted", the event shall be reported as a request, if the "monitorMode" is "notifyAndContinue", the event shall be reported as a notification, if the "monitorMode" is "transparent", then the event shall not be reported. + +### 12.7.2 Responding entity (smsSSF) + +#### 12.7.2.1 Normal procedure + +smsSSF preconditions: + +- (1) A control relationship exists between the smsSSF and the gsmSCF. +- (2) The smsSSF FSM is in the state "Waiting\_for\_Instructions". + +smsSSF postconditions: + +- (1) The requested EDPs have been armed or disarmed as indicated. +- (2) Armed events are monitored until ended by a transparent monitor mode, until the occurrence of the event or until the implicit disarming of the event. +- (3) No smsSSF FSM state transition. + +### 12.7.2.2 Error handling + +Generic error handling for the operation related errors is described in clause 10 and the TC services which are used for reporting operation errors are described in clause 14. + +## 12.8 ResetTimerSMS procedure + +### 12.8.1 General description + +The gsmSCF uses this operation to refresh the Tssf application timer, in order to prevent Tssf expiry at the smsSSF. + +#### 12.8.1.1 Parameters + +- timerID: +This parameter indicates which timer shall be reset. The only permissible value of this parameter is "tssf". +- timerValue: +This parameter defines the value to which the timer shall be set. + +### 12.8.2 Responding entity (smsSSF) + +#### 12.8.2.1 Normal procedure + +smsSSF preconditions: + +- (1) Short Message processing has been suspended at a DP. +- (2) The smsSSF FSM is in the state "Waiting\_for\_Instructions". + +smsSSF postconditions: + +- (1) The Tssf timer is loaded with the value received from the gsmSCF and is restarted. +- (2) No smsSSF FSM state transition. + +#### 12.8.2.2 Error handling + +Generic error handling for the operation related errors are described in clause 10 and the TC services which are used for reporting operation errors are described in clause 14. + +--- + +## 13 Detailed operation procedures for GPRS control + +NOTE Where a parameter for a GPRS control Operation is marked OPTIONAL in ASN.1, the reader is referred to the conditions for presence for this parameter, specified in the respective Information Flow in 3GPP TS 23.078 [7]. + +## 13.1 ActivityTestGPRS procedure + +### 13.1.1 General description + +The gsmSCF uses this operation to check for the continued existence of a relationship between the gsmSCF and the gprsSSF. If the relationship is still in existence, then the identified instance of gprsSSF will respond. If the ActivityTestGPRS operation timer expires, then the gsmSCF will assume that the receiving entity has failed in some way and will take appropriate action. This operation opens a new SS7 dialogue between gsmSCF and gprsSSF. + +#### 13.1.1.1 Parameters + +None. + +### 13.1.2 Responding entity (gprsSSF) + +#### 13.1.2.1 Normal procedure + +gprsSSF preconditions: + +- (1) A relationship exists between the gsmSCF and the gprsSSF. +- (2) The gprsSSME FSM is in the state "Idle Management". +- (3) No active TC dialogue exists at the moment of receiving ActivityTestGPRS. + +gprsSSF postconditions: + +- (1) The gprsSSME FSM transits to the state "Non-call Associated Treatment". +- (2) If there is a gprsSSF using the GPRS-Reference Number, then the gprsSSME FSM sends a Return Result "ActivityTestGPRS" to the gsmSCF. The gprsSSME FSM then returns to the state "Idle Management". + +If there is no gprsSSF using the GPRS-ReferenceNumber, then the gprsSSME FSM will issue a U-Abort. The gprsSSME FSM then returns to the state "Idle Management". + +- (3) The temporary TC dialogue is closed. + +If at the time of receiving ActivityTestGPRS there is an active TC dialogue for this GPRS Dialogue, then the gprsSSME FSM issues a U-Abort with Abort reason "overlapping-dialogue". + +#### 13.1.2.2 Error handling + +Generic error handling for the operation related errors is described in clause 10 and the TC services used for reporting operation errors are described in clause 14. + +## 13.2 ApplyChargingGPRS procedure + +### 13.2.1 General description + +The gsmSCF uses this operation for interacting with the gprsSSF function "CSE control of GPRS session or PDP Context duration and volume". The ApplyChargingGPRSReport operation provides the feedback from the gprsSSF to the gsmSCF. The charging scenarios supported by this operation are those given in 3GPP TS 22.078 [3] for "CSE control of GPRS session and PDP Context duration and volume". + +If this procedure is used within a PDP Context dialogue, then the charging instruction shall pertain to the PDP Context only. Data volume threshold and duration threshold may be defined separately. + +If this procedure is used within a GPRS Session dialogue, then the charging instruction may pertain to the GPRS Session or to a single PDP Context. Charging for a PDP Context may be on duration and/or volume. Charging for a GPRS Session may be on duration only. + +NOTE: Charging for a PDP Context on duration and volume requires two ApplyChargingGPRS operations. + +### 13.2.1.1 Parameters + +- **chargingCharacteristics:** +This parameter is a choice between parameters required for "CSE control of a GPRS session or a PDP Context duration or volume": + - **maxTransferredVolume:** +This parameter specifies the maximum volume that may be transferred before a ApplyChargingReportGPRS shall be sent to the gsmSCF. + - **maxElapsedTime:** +This parameter specifies the maximum period of time before a ApplyChargingReportGPRS shall be sent to the gsmSCF. +- **tariffSwitchInterval:** +This parameter indicates the time duration until the next tariff switch. The measurement of the elapsed tariff switch period shall start immediately after successful execution of this operation. +- **pDPID:** +This parameter identifies the PDP Context, within the GPRS Session dialogue, to which the charging instruction applies. + +## 13.2.2 Responding entity (gprsSSF) + +### 13.2.2.1 Normal procedure + +gprsSSF preconditions: + +- (1) A control relationship exists between the gsmSCF and the GPRS Session or PDP Context to which the operation applies. +- (2) The gprsSSF FSM is in one of the following states: "Waiting\_for\_Instructions" or "Monitoring". + +gprsSSF postconditions: + +- (1) No gprsSSF FSM state transition. + +On receipt of this operation, the gprsSSF shall set the charging data using the information elements included in the operation. + +### 13.2.2.2 Error handling + +"TaskRefused": In addition to the generic error handling noted below, this error shall be indicated when: + +- a previously received GPRS Session or PDP Context period or volume duration is pending; +- a tariffSwitchInterval is indicated when a previously received tariffSwitchInterval is pending; +- the gprsSSF has received an ApplyChargingGPRS operation for a PDP Context that is already disconnected; +- the gprsSSF has received an ApplyChargingGPRS operation for the GPRS Session when the subscriber is already detached. + +Generic error handling for the operation related errors is described in clause 10 and the TC services used for reporting operation errors are described in clause 14. + +## 13.3 ApplyChargingReportGPRS procedure + +### 13.3.1 General description + +The gprsSSF uses this operation to report charging related information to the gsmSCF as requested by the gsmSCF using the ApplyChargingGPRS operation. + +Timing of duration and measuring of transferred data (if applicable) shall be started when either an Attach, PDP Context Establishment Acknowledgement or an Inter SGSN Routeing Area Update acceptance is detected by the gprsSSF. + +A report shall be made when a PDP Context Disconnect, a Detach or a Change in QoS is detected by the gprsSSF or when the gprsSSF detects that the transferred volume or elapsed time duration indicated in the parameter "transferredVolume" or "elapsedTime" (received in ApplyChargingGPRS operation) has been reached. ApplyChargingReportGPRS shall be sent only on chargeable QoS changes. + +### 13.3.1.1 Parameters + +- chargingResult: + +This parameter provides the gsmSCF with the charging related information previously requested using the ApplyChargingGPRS operation. The "ChargingResult" is a choice, and can contain either of the following parameters: + +- transferredVolume: + +This is a choice of the following parameters: + +- volumeIfNoTariffSwitch: + +This parameter shall be present if no tariff switch has occurred for the PDP Context, otherwise it shall be absent. If present, then the volume transferred since the detection of the event that triggered volume count shall be reported. + +- volumeIfTariffSwitch: + +This parameter shall be present if a tariff switch has occurred for the PDP Context, otherwise it shall be absent. This parameter may contain the following information: + +- volumeSinceLastTariffSwitch: + +The volume since the detection of the event that triggered volume count or the last tariffSwitch (whichever of these events was last detected) shall be reported. + +- VolumeTariffSwitchInterval: + +This parameter shall be present only if a tariff switch was detected after the event that triggered volume count for the PDP Context in the current volume count period. If present, the volume between either the detection the event that triggered volume count or the previous tariff switch (whichever of these events was last detected) and the last tariff switch shall be reported. + +- elapsedTime: + +This parameter is a choice of the following parameters: + +- timeGPRSIfNoTariffSwitch: + +This parameter shall be present if no tariff switch has occurred for the GPRS Session or the PDP Context, otherwise it shall be absent. If present, then the elapsed time since the detection of the event that triggered time count shall be reported. + +- timeGPRSIfTariffSwitch: + +This parameter shall be present if a tariff switch has occurred for the GPRS Session or the PDP Context, otherwise it shall be absent. This parameter may contain the following information: + +- timeGPRSSinceLastTariffSwitch: + +The time since the event that triggered time count or the last tariffSwitch shall be reported. + +- timeGPRSTariffSwitchInterval: + +This parameter shall be present only if a tariff switch was detected after the event that triggered time count for the GPRS Session or PDP Context in the current time count period. If present, then the time between either the detection the event that triggered time count or the previous tariff switch (whichever of these events was last detected) and the last tariff switch shall be reported. + +- qualityOfService: + +This parameter identifies the QoS which was negotiated between the user, the SGSN and the GGSN. + +This parameter shall be present only if the sending of the ApplyChargingReportGPRS operation was triggered by a change in Quality of Service. The "negotiated-QoS-Extension" may be present as a supplement to the "negotiated-QoS". + +- active: +This parameter indicates whether the GPRS Session or PDP Context is still active +- pDPID: +This parameter identifies the PDP Context, within the GPRS Session dialogue, for which the charging report is valid. +- chargingRollOver: +This parameter indicates possible rollovers of the "ChargingResult" parameter due to the limited value ranges of the associated charging parameters. The "chargingRollOver" parameter is a choice and may contain either of the following parameters: + - transferredVolumeRollOver: +This parameter is a choice of the following parameters: + - rO-VolumeIfNoTariffSwitch: +This parameter indicates how many times the volumeIfNoTariffSwitch parameter of the chargingResult has rolled over. If no rollover has happened, then rO-VolumeIfNoTariffSwitch may be absent. + - rO-VolumeIfTariffSwitch: +This parameter is present if at least one of the parameters below is present. It may contain the following information: + - rO-VolumeSinceLastTariffSwitch: +This parameter indicates how many times the volumeSinceLastTariffSwitch parameter of the chargingResult has rolled over. If no rollover has happened, then rO-VolumeSinceLastTariffSwitch may be absent. + - rO-VolumeTariffSwitchInterval: +This parameter indicates how many times the VolumeTariffSwitchInterval parameter of the chargingResult has rolled over. If no rollover has happened, then rO-VolumeTariffSwitchInterval may be absent. + - elapsedTimeRollOver: +This parameter is a choice of the following parameters: + - rO-TimeGPRSIfNoTariffSwitch: +This parameter indicates how many times the timeGPRSIfNoTariffSwitch parameter of the chargingResult has rolled over. If no rollover has happened, then rO-TimeGPRSIfNoTariffSwitch may be absent. + - rO-TimeGPRSIfTariffSwitch: +This parameter shall be present if at least one of the parameters below is present. If It may contain the following information: + - rO-TimeGPRSSinceLastTariffSwitch: +This parameter indicates how many times the timeGPRSSinceLastTariffSwitch parameter of the chargingResult has rolled over. If no rollover has happened, then rO-TimeGPRSSinceLastTariffSwitch may be absent. + - rO-TimeGPRSTariffSwitchInterval: +This parameter indicates how many times the timeGPRSTariffSwitchInterval parameter of the chargingResult has rolled over. If no rollover has happened, then rO-TimeGPRSTariffSwitchInterval may be absent. + +## 13.3.2 Invoking entity (gprsSSF) + +### 13.3.2.1 Normal procedure + +gprsSSF preconditions: + +- (1) A relationship exists between the gsmSCF and the GPRS Session or PDP Context. +- (2) A charging event has been detected that was requested by the gsmSCF via an ApplyChargingGPRS operation. + +gprsSSF postconditions: + +- (1) If termination of the GPRS Session or a PDP Context has occurred, then: + - If the sending of ApplyChargingReportGPRS is directly followed by the reporting of an EDP-R, then the gprsSSF FSM shall transit to the state "Waiting\_for\_Instructions"; else + - If there are any armed EDPs or pending reports, then the gprsSSF FSM shall remain in the same state; else + - If there are no armed EDPs or pending reports, then the gprsSSF FSM shall transit to the state "Idle". +- (2) If the sending of ApplyChargingReportGPRS is due to a timer or counter expiry, then: + - If there are any armed EDPs or pending reports, then the gprsSSF FSM shall remain in the same state; else + - If there are no armed EDPs or pending reports, then the gprsSSF FSM shall transit to the state "Idle". +- (3) If the sending of ApplyChargingReportGPRS is due to a change in QoS of a PDP Context, then: + - The gprsSSF FSM shall remain in the same state. + +### 13.3.2.2 Error handling + +If the operation timer expires, then the gprsSSF shall abort the TC dialogue, terminate the GPRS dialogue and instruct the SGSN to handle the GPRS session or PDP context in accordance with the default GPRS handling parameter of the valid CSI. + +Generic error handling for the operation related errors is described in clause 10 and the TC services used for reporting operation errors are described in clause 14. + +## 13.4 CancelGPRS procedure + +### 13.4.1 General description + +The gsmSCF uses this operation to request the gprsSSF to disarm all pending EDPs and to cancel all pending reports for a GPRS Session or for a specific PDP Context. This enables the gprsSSF FSM to transit to the state "Idle". This procedure can not be used to cancel a previous operation. + +#### 13.4.1.1 Parameters + +- pDPID: +This parameter identifies the PDP Context, within the GPRS Session dialogue, for which the armed EDPs shall be disarmed and the pending reports shall be cancelled. + +### 13.4.2 Responding entity (gprsSSF) + +#### 13.4.2.1 Normal procedure + +gprsSSF preconditions: + +- (1) The gprsSSF FSM is in the state "Waiting\_for\_Instructions" or in the state "Monitoring". + +gprsSSF postconditions: + +- (1) All pending ApplyChargingReportGPRS are cancelled and all pending EDPs are disarmed. If a PDPID is included in the operation, then the cancelling of the pending reports and the disarming of the armed events applies to the indicated PDP Context only. +- (2) If the gprsSSF FSM was in the state "Monitoring" and there are no more armed EDPs or pending ApplyChargingReportsGPRS, then the gprsSSF FSM shall transit to the state "Idle". + +If the gprsSSF FSM was in the state "Waiting\_for\_Instructions", it shall remain in that state. If there are no more armed EDPs or pendingApplyChargingReportsGPRS, then subsequent GPRS Session or PDP Context processing operation will result in the gprsSSF FSM to transit the state "Idle". + +The GPRS Session or PDP Context to which the CancelGPRS operation applies, if in active state, shall further be treated by the gprsSSF autonomously as a normal (non-CAMEL) GPRS Session or PDP Context. + +### 13.4.2.2 Error handling + +Generic error handling for the operation related errors is described in clause 10 and the TC services which are used for reporting operation errors are described in clause 14. + +## 13.5 ConnectGPRS procedure + +### 13.5.1 General description + +The gsmSCF uses this operation to provide an APN to the gprsSSF, to be used for establishing a PDP Context. + +#### 13.5.1.1 Parameters + +- accessPointName: +This parameter contains the Access Point Name towards which the PDP Context shall be established. Refer to 3GPP TS 29.060 [12] for details on the Access Point Name. +- pDPID: +This parameter identifies the PDP Context, within the GPRS Session dialogue, for which the Access Point Name shall be used. + +### 13.5.2 Responding entity (gprsSSF) + +#### 13.5.2.1 Normal procedure + +gprsSSF preconditions: + +- (1) A control relationship exists between the gsmSCF and the PDP Context. +- (2) The GPRS PDP Context FSM is suspended at DP PDP\_Context\_Establishment. +- (3) The gprsSSF FSM is in the state "Waiting\_for\_Instructions". + +gprsSSF postconditions: + +- (1) The gprsSSF performs the actions to establish the PDP Context using the given Access Point Name. +- (2) The gprsSSF stops Tssf. +- (3) If no EDPs are armed, then the gprsSSF FSM transits to the state "Idle". Otherwise the gprsSSF FSM transits to the state "Monitoring". + +The gsmSSF shall not perform any implicit arming or disarming of DPs. + +#### 13.5.2.2 Error handling + +Generic error handling for the operation related errors is described in clause 10 and the TC services which are used for reporting operation errors are described in clause 14. + +## 13.6 ContinueGPRS procedure + +### 13.6.1 General description + +The gsmSCF uses this operation to request the gprsSSF to proceed with GPRS Session or PDP Context processing at the DP at which it previously suspended processing to await gsmSCF instructions. The gprsSSF continues processing without substituting new data from the gsmSCF. + +### 13.6.1.1 Parameters + +- pDPID: +This parameter identifies the PDP Context within the control relationship for which the processing shall continue. + +## 13.6.2 Responding entity (gprsSSF) + +### 13.6.2.1 Normal procedure + +gprsSSF preconditions: + +- (1) A control relationship exists between the gsmSCF and the GPRS Session or PDP Context. +- (2) The GPRS Session or PDP Context processing has been suspended at any DP. +- (3) The gprsSSF FSM is in the state "Waiting\_for\_Instructions". + +gsmSSF postconditions: + +- (1) GPRS Session or PDP Context processing continues. +- (2) The gprsSSF FSM is in one of the following states: + - "Monitoring" because at least one EDP was armed or an ApplyChargingReportGPRS was requested; or + - "Idle" because no EDPs were armed and no ApplyChargingReportGPRS was requested. + +### 13.6.2.2 Error handling + +Operation related error handling is not applicable, due to class 4 operation. + +## 13.7 EntityReleasedGPRS procedure + +### 13.7.1 General description + +The gprsSSF uses this operation to inform the gsmSCF that the GPRS Session is detached or a PDP Context is disconnected. It shall be used only when the associated event detection point (ie. for GPRS Session Detach: DP "Detach" and for PDP Context Disconnect: DP "PDP Context Disconnection") is at that moment not armed for reporting. + +This operation shall be used irrespectively of the functional entity that initiated the Detach or PDP Context Disconnect and irrespectively of the cause for the Detach or PDP Context Disconnect. + +When a PDP Context is terminated, then the gprsSSF shall send all pending reports of that PDP Context to the gsmSCF. When a GPRS Session is terminated, then the gprsSSF shall send all outstanding reports of the GPRS Session to the gsmSCF. + +### 13.7.1.1 Parameters + +- gPRSCause: +This parameter gives an indication to the gsmSCF about the reason for discontinuing the PDP Context or GPRS Session. This may be used by gsmSCF if a FurnishChargingInformationGPRS operation needs to be sent to the gprsSSF. +- pDPID: +This parameter identifies the PDP Context within the GPRS Session dialogue, which has terminated. + +### 13.7.2 Invoking entity (gprsSSF) + +### 13.7.2.1 Normal procedure + +gprsSSF preconditions: + +- (1) The gprsSSF FSM is in the state "Waiting\_for\_Instructions" or in the state "Monitoring". + +gprsSSF postconditions: + +- (1) All armed EDPs for the indicated PDP Context or GPRS Session shall be disarmed. All connections and resources related to the indicated PDP Context or GPRS Session shall be released. +If there are no more armed EDPs or pending reports, then the gprsSSF FSM transits to the state "Idle"; otherwise the gprsSSF FSM remains in the same state. + +### 13.7.2.2 Error handling + +If the operation timer expires, then the gprsSSF shall abort the TC dialogue, terminate the GPRS dialogue and instruct the SGSN to handle the GPRS session or PDP context in accordance with the default GPRS handling parameter of the valid CSI. + +Generic error handling for the operation related errors is described in clause 10 and the TC services which are used for reporting operation errors are described in clause 14. + +## 13.8 EventReportGPRS procedure + +### 13.8.1 General description + +The gprsSSF uses this operation to notify the gsmSCF of a GPRS Session or PDP Context event previously requested by the gsmSCF in a RequestReportGPRSEvent operation. + +#### 13.8.1.1 Parameters + +- gPRSEventType: +This parameter specifies the type of event that is reported. +- gPRSEventSpecificInformation: +This parameter indicates the GPRS Session or PDP Context related information specific to the event. + +For Change of Position GPRS Session it shall contain the "locationInformationGPRS", if available. + +For Change of Position PDP Context it shall contain the "accessPointName", "chargingID", "locationInformationGPRS", "endUserAddress", Quality of Service, "timeAndTimeZone" and "gGSNAddress" and "secondaryPDP-context", if available. + +For Detach and PDP Context Disconnect it shall contain the "initiatingEntity" and, conditionally, "routeingAreaUpdate". The "initiatingEntity" indicates the entity that initiated the Detach or PDP Context Disconnect. The "routeingAreaUpdate" indicates that the Detach or PDP Context Disconnect is due to inter-SGSN routeing area update. + +In the case of inter-SGSN routeing area update, the gsmSCF may ignore the "initiatingEntity". + +For PDP Context Establishment it shall contain the "accessPointName", "endUserAddress", "pDPInitiationType", Quality of Service, "locationInformationGPRS", "timeAndTimeZone" and "secondaryPDP-context", if available. + +The Quality of Service shall contain the Requested QoS and the Subscribed QoS. The "requested-QoS-Extension" and the "subscribed-QoS-Extension" may be present as supplements to the "requested-QoS" and the "subscribed-QoS" respectively. + +For PDP Context Establishment Acknowledgement it shall contain the "accessPointName", "chargingID", "endUserAddress", Quality of Service, "locationInformationGPRS", "timeAndTimeZone" and "gGSNAddress", if available. + +The Quality of Service shall contain the Requested QoS, the Subscribed QoS and the Negotiated QoS. The "requested-QoS-Extension", the "subscribed-QoS-Extension" and the "negotiated-QoS-Extension" may be present as supplements to the "requested-QoS", the "subscribed-QoS" and the "negotiated-QoS" respectively. + +All optional gPRSEventSpecificInformation parameters shall be sent in accordance with 3GPP TS 23.078 [7] subclause 6.6.1.4 and 3GPP TS 22.078 [3] annex "GPRS Information provided to the CSE". + +- miscGPRSInfo: +This parameter contains DP related information. + +- messageType: +This parameter indicates whether the message is a request, i.e. resulting from a RequestReportGPRSEvent with "monitorMode" = "interrupted", or a notification, i.e. resulting from a RequestReportGPRSEvent with "monitorMode" = "notifyAndContinue". +- pDPID: +This parameter identifies the PDP Context, within the GPRS Session dialogue, for which the event is reported. + +## 13.8.2 Invoking entity (gprsSSF) + +### 13.8.2.1 Normal procedure + +gprsSSF preconditions: + +- (1) The gprsSSF FSM is in the state "Monitoring" or in the state "WaitingForInstructions". +- (2) The GPRS Session or PDP Context FSM proceeds to an EDP that is armed. + +gprsSSF postconditions: + +- (1) If the message type was notification and there are still armed EDPs that can be met or there are any pending reports, then the gprsSSF FSM shall remain in the state "Monitoring". +- (2) If the message type was notification and there are no more EDPs armed that can be met and there are no pending reports, then the gprsSSF FSM shall transit to the state "Idle". +- (3) If the message type was request, then the gprsSSF FSM shall transit to the state "Waiting\_for\_Instructions". +GPRS Session or PDP Context processing is interrupted. + +If an EDP-R is met that causes the release of a GPRS Session or PDP Context, then all EDPs related to the GPRS Session or PDP Context shall be disarmed. + +### 13.8.2.2 Error handling + +If the operation timer expires, then the gprsSSF shall abort the TC dialogue, terminate the GPRS dialogue and instruct the SGSN to handle the GPRS session or PDP context in accordance with the default GPRS handling parameter of the valid CSI. + +If the message type is "request" and the Tssf timer expires, then the gprsSSF shall abort the TC dialogue and shall instruct the SGSN to treat the GPRS Session or PDP Context in accordance with the default GPRS handling of the valid CSI. + +Generic error handling for the operation related errors is described in clause 10 and the TC services which are used for reporting operation errors are described in clause 14. + +## 13.9 FurnishChargingInformationGPRS procedure + +### 13.9.1 General description + +The gsmSCF uses this operation to send charging related information to a Logical GPRS record. This Logical GPRS record is CAMEL specific. The first FurnishChargingInformationGPRS operation results in the generation of a Logical GPRS record. Receipt of subsequent FurnishChargingInformationGPRS operations shall overwrite or append the contents of the Logical GPRS record. + +#### 13.9.1.1 Parameters + +- fCIGPRSBillingChargingCharacteristics: +This parameter contains the following parameters; +- fCIBCCCAMELsequence1: +This parameter contains the following parameters; +- freeFormatData: +This parameter contains free-format billing and/or charging characteristics. + +- appendFreeFormatData: +This parameter indicates whether previous FCI free format data is appended or overwritten. Refer to 3GPP TS 23.078 [7] for details of this mechanism. +- pDPID: +This parameter indicates the PDP Context's Logical GPRS record to which the free format data belongs. + +## 13.9.2 Responding entity (gprsSSF) + +### 13.9.2.1 Normal procedure + +gprsSSF preconditions: + +- (1) The gprsSSF FSM is in the state "Waiting\_for\_Instructions" or in the state "Monitoring". + +gprsSSF postconditions: + +- (1) No gprsSSF FSM state transition. + +On receipt of this operation the gprsSSF performs actions to create the Logical GPRS record, if necessary, and writes the free-format information carried in the operation into the GPRS record. A FurnishChargingInformationGPRS operation will create a Logical GPRS Data Record (CDR) if such a record does not already exist. Subsequent FurnishChargingInformationGPRS operations received, will either overwrite or append the data previously written in the free-format CDR field depending on the presence and value of the parameter "appendFreeFormatData". + +The Logical GPRS records will be associated for a given GPRS Session or PDP Context with one or more physical CDRs, as specified in 3GPP TS 32.250 [14] and 3GPP TS 22.115 [4]. + +### 13.9.2.2 Error handling + +Generic error handling for the operation related errors is described in clause 10 and the TC services which are used for reporting operation errors are described in clause 14. + +## 13.10 InitialDPGPRS procedure + +### 13.10.1 General description + +The gprsSSF uses this operation after detection of a TDP-R in the GPRS Session or PDP Context state machine, to request the gsmSCF for instructions to complete the GPRS Session or PDP Context. + +For a GPRS Session, the "Attach" and "Change of Position Session" TDPs may result in the InitialDPGPRS Procedure. + +For a PDP Context, the "PDP Context Establishment", the "PDP Context Establishment Acknowledgement" and the "Change of Position Context" TDPs may result in the InitialDPGPRS Procedure. + +If a PDP Context related TDP is met and there is at that moment a GPRS dialogue for the GPRS Session, then the gprsSSF shall not initiate the InitialDPGPRS Procedure for that PDP Context. + +If the "PDP Context Establishment Acknowledgement" event occurs and this event is armed as a TDP, and there is at that moment a GPRS dialogue for the PDP Context, then the gprsSSF shall not initiate a new InitialDPGPRS Procedure for that PDP Context. + +#### 13.10.1.1 Parameters + +- serviceKey: +This parameter indicates to the gsmSCF the requested IN service. It is used to address the required application/SLP within the gsmSCF; it is not used for SCP addressing. +- gPRSEventType: +This parameter indicates the armed GPRS Attach/Detach FSM or PDP Context FSM DP event, resulting in the InitialDPGPRS operation. +- mSISDN: +This parameter contains the MSISDN of the mobile subscriber for which the CAMEL service is invoked. + +- iMSI: +This parameter contains the IMSI of the mobile subscriber for which the CAMEL service is invoked. +- timeAndTimezone: +This parameter contains the time that the gprsSSF is triggered, and the time zone that the invoking gprsSSF resides in. +- gPRSMSCClass: +This parameter contains the MS capabilities of the mobile subscriber for which the CAMEL service is invoked. +- endUserAddress: +This parameter identifies the PDP type, PDP type organisation and the actual PDP address. +- qualityOfService: +This parameter contains the Quality of Service. +If the InitialDPGPRS operation is sent as a result of the "PDP Context Establishment" TDP, then the Quality of Service parameter shall contain the Requested QoS and the Subscribed QoS. The "requested-QoS-Extension" and the "subscribed-QoS-Extension" may be present as supplements to the "requested-QoS" and the "subscribed-QoS" respectively. +If the InitialDPGPRS operation is sent as a result of the "PDP Context Establishment Acknowledgement" TDP or the Change of Position Context TDP, then the Quality of Service parameter shall contain the Requested QoS, the Subscribed QoS and the Negotiated QoS. The "requested-QoS-Extension", the "subscribed-QoS-Extension" and the "negotiated-QoS-Extension" may be present as supplements to the "requested-QoS", the "subscribed-QoS" and the "negotiated-QoS" respectively. +- accessPointName: +This parameter contains the requested address that the MS for which the CAMEL service is invoked for wants to connect to. +- routeingAreaIdentity: +This parameter contains the location information of the MS for which the CAMEL service is invoked. +- chargingID: +This parameter contains the charging ID that, together with the gGSNAddress, uniquely identifies the PDP Context for the MS for which the CAMEL service is invoked. +- sGSNcapabilities: +This parameter specifies the capabilities which the SGSN node can provide for the CAMEL service control. +- locationInformationInSGSN: +This parameter indicates the location of the sending MS. +- pDPInitiationType: +This parameter indicates whether a PDP Context was established as a result of a network-initiated request or as a result of a subscriber request. +- gGSNAddress: +This parameter refers to the IP address of the GGSN where the PDP Context terminates. It is used together with the chargingID for uniquely identification of the PDP Context for which the CAMEL service is invoked from. +- secondaryPDP-context: +This parameter indicates that the PDP Context is requested as a secondary PDP Context. +- iMEI: +This parameter contains the IMEI (with software version) of the mobile subscriber for which the service is invoked. + +## 13.10.2 Invoking entity (gprsSSF) + +### 13.10.2.1 Normal procedure + +gprsSSF preconditions: + +- (1) An event has been met that is armed as TDP. +- (2) There is no GPRS dialogue active for that PDP Context or for the GPRS Session. + +gprsSSF postconditions: + +- (1) A control relationship is established between the gsmSCF and the GPRS Session or the PDP Context. +- (2) The gprsSSF FSM is in the state "Waiting\_for\_Instructions". + +The address of the gsmSCF that the InitialDPGPRS operation shall be sent to, shall be fetched from the valid CSI. The gprsSSF shall provide all available parameters to the gsmSCF. + +The gprsSSF application timer Tssf shall be loaded and started when the gprsSSF sends InitialDPGPRS for requesting instructions from the gsmSCF. It is used to prevent excessive GPRS Session or PDP Context duration or volume usage. + +### 13.10.2.2 Error handling + +If the gsmSCF is not accessible, then the gprsSSF instructs the SGSN to handle the GPRS Session or PDP Context in accordance with the Default GPRS Handling parameter of the valid CSI. + +If Tssf expires, then the gprsSSF shall abort the interaction with the gsmSCF by means of an abort to TC and shall instruct the SGSN to handle the GPRS Session or PDP Context in accordance with the Default GPRS Handling parameter of the valid CSI. + +If the MS abandons the establishment of a GPRS Session or PDP Context after the sending of InitialDPGPRS and before the TC dialogue is established, then the gprsSSF shall abort the interaction with the gsmSCF by means of an abort to TC. + +Generic error handling for the operation related errors is described in clause 10 and the TC services which are used for reporting operation errors are described in clause 14. + +## 13.11 ReleaseGPRS procedure + +### 13.11.1 General description + +The gsmSCF uses this operation to tear down by the gsmSCF an existing GPRS Session or PDP Context at any phase. + +#### 13.11.1.1 Parameters + +- gPRSCause: +This parameter gives an indication to the gprsSSF about the reason of releasing the GPRS Session or a specific PDP Context. This may be used by gprsSSF for generating specific indications to the MS or to fill in the "cause" in the release message. +- pDPID: +This parameter identifies the PDP Context, within the GPRS Session dialogue, which shall be released. + +### 13.11.2 Responding entity (gprsSSF) + +#### 13.11.2.1 Normal procedure + +gprsSSF preconditions: + +- (1) A control relationship exists between gsmSCF and the GPRS Session or PDP Context. More specifically, in order to tear down an individual PDP Context, an EDP-R must be armed for that PDP Context. In order to make a SCP controlled detach an EDP-R must be armed for the GPRS Session. +- (2) The gprsSSF FSM is in the state "Waiting\_for\_Instructions" or in the state "Monitoring". + +gprsSSF postconditions: + +- (1) All pending reports for the GPRS Session or the PDP Context shall be reported to the gsmSCF. +- (2) All connections and resources related to the GPRS Session or the PDP Context shall be released. +- (3) All armed EDPs for the GPRS Session or the PDP Context shall be disarmed. + +- (4) If there are no more pending reports or armed events, then the gprsSSF FSM transits to the state "Idle". + +If there are any pending reports or armed events, then the gprsSSF FSM remains in the same state. + +### 13.11.2.2 Error handling + +Generic error handling for the operation related errors is described in clause 10 and the TC services which are used for reporting operation errors are described in clause 14. + +## 13.12 RequestReportGPRSEvent procedure + +### 13.12.1 General description + +The gsmSCF uses this operation to request the gprsSSF to monitor for a GPRS Session or PDP Context related event (e.g., events such as PDP Context establishment or detach) and to send a notification to the gsmSCF when the event is detected. + +The monitoring of more than one event may be requested with a single RequestReportGPRSEvent operation, but each of these requested events will be reported in a separate EventReportGPRS operation. + +#### 13.12.1.1 Parameters + +- gPRSEvent: +This parameter specifies the event or events of which a report is requested. +- gPRSEventType: +This parameter specifies the type of event of which a report is requested. +- monitorMode: +This parameter indicates how the event shall be reported. If the "monitorMode" is "interrupted", then the event shall be reported as a request; if the "monitorMode" is "notifyAndContinue", then the event shall be reported as a notification; if the "monitorMode" is "transparent", then the event shall not be reported. +- pDPID: +This parameter identifies the PDP Context, within the GPRS Session dialogue, for which the event reporting is requested + +### 13.12.2 Responding entity (gprsSSF) + +#### 13.12.2.1 Normal procedure + +gprsSSF preconditions: + +- (1) A control relationship exists between the gsmSCF and the GPRS Session or PDP Context. +- (2) The gprsSSF FSM is in the state "Waiting\_for\_Instructions" or the state "Monitoring". + +In the state "monitoring" only requests to disarm detection points (with MonitorMode set to "Transparent") or send notifications of events (with MonitorMode set to "NotifyAndContinue") shall be accepted. + +gprsSSF postconditions: + +- (1) The requested EDPs have been armed or disarmed as indicated. +- (2) Previously requested events are monitored until ended by a transparent monitor mode, until the end of the GPRS Session or PDP Context or until the EDPs are detected. +- (3) If there are no armed events or pending reports, then the gsmSSF FSM shall transit to the state "Idle". Otherwise it shall remain in the same state. + +#### 13.12.2.2 Error handling + +Generic error handling for the operation related errors is described in clause 10 and the TC services which are used for reporting operation errors are described in clause 14. + +## 13.13 ResetTimerGPRS procedure + +### 13.13.1 General description + +The gsmSCF uses this operation to refresh the Tssf application timer, in order to avoid the Tssf time-out at the gprsSSF. + +#### 13.13.1.1 Parameters + +- timerID: +This parameter indicates which timer shall be reset. The only permissible value for this parameter is "Tssf". +- timerValue: +This parameter specifies the value to which the timer shall be set. + +### 13.13.2 Responding entity (gprsSSF) + +#### 13.13.2.1 Normal procedure + +gprsSSF preconditions: + +- (1) GPRS Session or PDP Context processing has been suspended at a DP. +- (2) The gprsSSF FSM is in the state "Waiting\_for\_Instructions". + +gprsSSF postconditions: + +- (1) The Tssf timer is loaded with the value received from the gsmSCF and is restarted. +- (2) No gprsSSF FSM state transition. + +#### 13.13.2.2 Error handling + +Generic error handling for the operation related errors is described in clause 10 and the TC services which are used for reporting operation errors are described in clause 14. + +## 13.14 SendChargingInformationGPRS Procedure + +### 13.14.1 General description + +The gsmSCF uses this operation to instruct the gprsSSF on the Advice of Charge information to be sent to the MS, provided that the SGSN supports Advice of Charge. The operation may be invoked on multiple occasions. + +#### 13.14.1.1 Parameters + +- sCIGPRSBillingChargingCharacteristics: +This parameter contains the Advice of Charge information: + - aOCGPRS: +This parameter specifies the Advice of Charge information that shall be sent to the MS. It may contain one or more of the following parameters: + - aOCInitial: +This is a set of Charge Advice Information elements, as defined in 3GPP TS 22.024 [2]. These CAI elements shall be sent by the gprsSSF to the MS when an Activate PDP Context Accept or Attach Accept is sent to MS and a tariff switch has not yet occurred. It may also be sent at any other time e.g. upon change of QoS or RAI. + - aOCSubsequent: +This parameter may contain the following information: + - cAIElements: +This is a set of Charge Advice Information (CAI) elements, as defined in 3GPP TS 22.024 [2]. These CAI elements shall be sent to the MS when an Activate PDP Context Accept or Attach Accept is + +detected and a tariff switch has occurred previously, or when Activate PDP Context Accept or Attach Accept has previously been detected and a tariff switch occurs. + +- tariffSwitchInterval: +This parameter indicates to the gprsSSF the time duration until the next tariff switch. The measurement of the elapsed tariff switch period shall start immediately after successful execution of this operation. +- pDPID: +This parameter identifies the PDP Context, within the GPRS Session dialogue, for which the Advice-of-Charge instruction applies. + +## 13.14.2 Responding Entity (gprsSSF) + +### 13.14.2.1 Normal Procedure + +gprsSSF preconditions: + +- (1) A relationship exists between the gsmSCF and the GPRS Session or PDP Context. +- (2) The gprsSSF FSM is in the state "Waiting\_for\_Instructions" or in the state "Monitoring". + +gprsSSF postconditions: + +- (1) No gprsSSF FSM state transition. + +On receipt of this operation, the gprsSSF performs actions to send the Advice of Charge information to the MS, provided that the SGSN supports Advice of Charge. + +If Advice of Charge is to be provided to an MS in conjunction with "CSE control of GPRS Session or PDP Context duration or volume", then the following sequence of operations shall be sent from the gsmSCF to the gprsSSF in the following order and in the same TC TC-CONTINUE or TC-BEGIN component: + +ApplyChargingGPRS; SendChargingInformationGPRS. + +These operations shall be processed sequentially by the gprsSSF, in the order that they are sent by the gsmSCF. In this, case parameter TariffSwitchInterval may be present either in the ApplyChargingGPRS operation or in the SendChargingInformationGPRS operation, but not in both operations. It is recommended that this parameter be transported in the ApplyGPRSCharging operation. + +The TariffSwitchInterval information received with either one of these operations shall set the same tariff switch timer in the gprsSSF. This duration timer shall run from the time of successful operation execution. + +### 13.14.2.2 Error handling + +"TaskRefused": In addition to the generic error handling noted below, this error shall be indicated when: + +- a tariffSwitchInterval is indicated when a previously received tariffSwitchInterval is pending. + +Generic error handling for the operation related errors is described in clause 10 and the TC services which are used for reporting operation errors are described in clause 14. + +--- + +## 14 Services assumed from lower layers + +### 14.1 Services assumed from TC + +The SS7 application layer protocol defined in this 3GPP TS, is a protocol to provide communication between a pair of application processes. In the SS7 environment this is represented as communication between a pair of application-entities (AEs) using the TC. The function of an AE is provided by a set of application-service-elements (ASEs). The interaction between AEs is described in terms of their use of the services provided by the ASEs. + +If AC are to be used for FE differentiation within a physical node, then the version of TC used must support the dialogue portion of TC (i.e. ETSI ETS 300 287-1 [22]). + +This requirement applies to all interfaces, not just those used for internetworking. + +Table 14-1 defines which versions of TC are the minimum versions required to support the defined CAP interfaces: + +**Table 14-1: Minimum TC requirements for CAP interfaces** + +| Interface | CAP | +|------------------------|------------| +| gsmSSF - gsmSCF | White Book | +| gsmSRF - gsmSCF | White Book | +| assist gsmSSF - gsmSCF | White Book | +| smsSSF - gsmSCF | White Book | +| gprsSSF - gsmSCF | White Book | + +## 14.1.1 Common procedures + +The present subclause defines the procedures and mapping which apply between CAP and TC to be used in the absence of specific procedures and mapping instructions for the specific CAP interfaces as defined in subsequent subclauses. + +### 14.1.1.1 Normal procedures + +The present subclause describes the procedures and TC primitives that shall be used for transmitting messages between AEs under normal operation. + +The CAP, as TC-user, uses only the structured dialogue facility provided by TC. The following situations can occur when a message is sent between two PE: + +- a dialogue shall be established: the TC-user issues a TC-BEGIN request primitive. +- a dialogue shall be maintained: the TC-user issues a TC-CONTINUE request primitive. +- a dialogue shall no longer be maintained: the TC-user issues a TC-END request primitive with either basic end or with pre-arranged end depending on the following conditions: + - Basic End + - In the case the dialogue is established, operations, leading to a termination of the relationship, can be transmitted by the FE with a TC-END request primitive (basic) in the case the FE is not interested in the reception of any ERROR or REJECT components for these sent operations. Once the FE dialogue resources have been released, any ERROR or REJECT components received for these operations will be discarded by TC as described in ETSI ETS 300 287-1 [22]. + - In the case that the dialogue is established and the FE has received an operation, leading to the termination of the relationship, does not wish to continue dialogue and there is no operation to be sent, a TC-END request primitive (basic) with zero components can be sent from the FE. + - Pre-arranged End + - Where an entity is interested in possible ERROR or REJECT messages on response to sent operations leading to a termination of the relationship, the dialogue is ended with a TC-END request primitive (pre-arranged end) after the last associated operation timer expires. The receiving entity can end the dialogue with a TC-END request primitive (pre-arranged end) after successful processing of these operations (i.e. the relationship is terminated). + - in general, the use of prearranged end shall be limited to the case for both communicating entities clearly recognizable that peer entity applies prearranged end. In all other cases, basic end shall be used. + +### 14.1.1.2 Abnormal procedures + +The present subclause describes the procedures and TC primitives that shall be used for reporting abnormal situations between AEs. The error cases are defined in clause 10. + +The following primitives shall be used to report abnormal situations: + +- operation errors, as defined in the CAP, are reported with TC-U-ERROR request primitive. + +- rejection of a TC component by the TC-user shall be reported with TC-U-REJECT request primitive. +- when the FE detecting error or rejecting operation decides the termination of TC dialogue, TC-END request primitive (basic) with error or reject can be used for the termination of TC dialogue. +- when the gsmSSF or the gsmSRF detecting error or rejecting operation recognizes the possibility to continue dialogue, TC-CONTINUE request primitive with error or reject can be used for the continuation of TC dialogue. +- a dialogue shall be aborted by the TC-user with a TC-U-ABORT request primitive. +- on expiration of application timer Tssf or Tsrf, dialogue shall be terminated by means of by TC-U-ABORT primitive with an Abort reason, regardless of TC dialogue is established or not. + +For abnormal situations detected by TC the same rules shall apply for reception of TC-R-REJECT indication as for transmission of TC-U-REJECT request and for transmission of TC-P-ABORT indication as for transmission of TC-U-ABORT request primitive. + +The following rules shall be applied to terminate the TC dialogue under abnormal situations: + +- in the case that abort condition is detected and TC dialogue is established, TC dialogue is terminated by TC-U-ABORT primitive with an Abort reason. +- in the case that abort condition is detected and TC dialogue is not established, TC dialogue is locally terminated by TC-U-ABORT primitive. (in the case such as application time out). + +In error situations prearranged end shall not be used to terminate the TC dialogue. In the case any AE encounters an error situation the peer entity shall be explicitly notified of the error, if possible. If from any entity's point of view the error encountered requires the relationship to be ended, then it shall close the dialogue via a TC-END request primitive with basic end or via a TC-U-ABORT request primitive, depending on whether any pending ERROR or REJECT component is to be sent or not. + +In the case an entity receives a TC-END indication primitive and after all components have been considered, the FSM is not in a state to terminate the relationship, an appropriate internal error should be provided. + +In cases when a dialogue needs to be closed by the initiating entity before its establishment has been completed (before the first TC indication primitive to the TC-BEGIN request primitive has been received from the responding entity), the TC-user shall issue a TC-END request primitive with prearranged end or a TC-U-ABORT request primitive. The result of these primitives will be only local, any subsequent TC indication received for this dialogue will be handled in accordance with the abnormal procedures as specified in ETSI ETS 300 287-1 [22]. + +When the gsmSSF, gprsSSF or smsSSF receives multiple Operation components in a single TC Message and there is an error in the processing of one of these Operations, then the gsmSSF FSM, gprsSSF FSM or smsSSF FSM shall process the error and shall discard all Operation components in that TC Message of which the processing has not yet started. + +### 14.1.1.3 Dialogue handling + +#### 14.1.1.3.1 Dialogue establishment + +The establishment of a CAP dialogue involves two application processes as described in clause 1, one that is the dialogue-initiator and one that is the dialogue-responder. + +This procedure is driven by the following signals: + +- A TC-BEGIN request primitive from the dialogue-initiator. +- A TC-BEGIN indication primitive occurring at the responding side +- The first TC-CONTINUE indication primitive occurring at the initiating side or under specific conditions: + - A TC-END indication primitive occurring at the initiating side + - A TC-U-ABORT indication primitive occurring at the initiating side + - A TC-P-ABORT indication primitive occurring at the initiating side + +*Sending of a TC-BEGIN request* + +Before issuing a TC-BEGIN request primitive, TC-USER shall store the AC-name and if present the user-information parameter. + +TC-USER shall request the invocation of the associated operations using the TC-INVOKE service. See subclause 14.1.1.4.1 for a description of the invocation procedure. + +After processing of the last invocation request, TC-USER shall issue a TC-BEGIN request primitive. + +The initiator TC-USER then waits for a TC indication primitive and will not issue any other requests, except a TC-U-ABORT request or a TC-END request with the release method parameter set to "pre-arranged release". + +*Receipt of a TC-BEGIN indication* + +On receipt of a TC-BEGIN indication primitive, responder TC-USER shall: + +- Analyse the application-context-name included in the primitive. If it is supported, then process any other indication primitives received from TC as described in subclause 14.1.1.4.1. +- If the application-context-name included in the primitive is not supported, then issue a TC-U-ABORT request primitive. + +*Receipt of the first TC-CONTINUE indication* + +On receipt of the first TC-CONTINUE indication primitive for a dialogue, TC-USER shall check the value of the application-context-name parameter. If this value matches the one used in the TC-BEGIN request primitive, then TC-USER shall process the following TC component handling indication primitives as described in subclause 14.1.1.4.1, otherwise it shall issue a TC-U-ABORT request primitive. + +*Receipt of a TC-END indication* + +On receipt of a TC-END indication primitive in the dialogue initiated state, TC-USER shall check the value of the application-context-name parameter. If this value match the one used in the TC-BEGIN request primitive, then the TC-USER shall process the following TC component handling indication primitives as described in subclause 14.1.1.4.1. + +*Receipt of a TC-U-ABORT indication* + +Receipt of a TC-U-ABORT indication primitive is described as part of user abort procedure (see 14.1.1.3.4.). + +*Receipt of a TC-P-ABORT indication* + +Receipt of a TC-P-ABORT indication primitive is described as part of provider abort procedure (see 14.1.1.3.5.). + +#### 14.1.1.3.2 Dialogue continuation + +Once established the dialogue is said to be in a continuation phase. + +Both application processes can request the transfer of CAP APDUs until one of them requests the termination of the dialogue. + +*Sending entity* + +TC-USER shall process any component handling request primitives as described in subclause 14.1.1.4.1. + +After processing the last component handling request primitive, TC-USER shall issue a TC-CONTINUE request primitive. + +*Receiving entity* + +On receipt of a TC-CONTINUE indication primitive TC-USER shall accept zero, one or several TC component handling indication primitives and process them as described in subclause 14.1.1.4.1. + +### 14.1.1.3.3 Dialogue termination + +Both the dialogue-initiator and the dialogue-responder have the ability to request the termination of a dialogue after it has been established when no dialogue is to be established or when a dialogue is no longer to be maintained according to the rules as stated in subclauses 14.1.2.1.1 and 14.1.2.1.2. + +The dialogue termination procedure is driven by the following events: + +- A TC-END request primitive +- A TC-END indication primitive + +#### *Sending of TC-END request* + +When the dialogue shall no longer be maintained, TC-USER shall process any component handling request primitives as described in subclause 14.1.1.4.1 + +After processing the last component handling request primitive (if any), TC-USER shall issue a TC-END request primitive with the release method parameter set to "basic end" or "prearranged release", in accordance with the rules as stated in subclauses 14.1.2.1.1 and 14.1.2.1.2. + +When no dialogue is to be established, refer to subclauses 14.1.1.3.1. + +#### *Receipt of a TC-END indication* + +On receipt of a TC-END indication primitive, the TC-USER shall accept any component handling indication primitives and process them as described in subclause 14.1.1.4.1. + +After processing the last component handling primitive all dialogue related resources are released. + +### 14.1.1.3.4 User abort + +Both the dialogue-initiator and the dialogue-responder have the ability to abort a dialogue at any time. + +The user abort procedure is driven by one of the following events: + +- A TC-U-ABORT request primitive +- A TC-U-ABORT indication primitive + +#### *Sending of TC-U-ABORT request* + +After issuing a TC-U-ABORT request primitive, all dialogue related resources are released. + +#### *Receipt of a TC-U-ABORT indication* + +On receipt of a TC-U-ABORT indication all dialogue related resources are released. + +### 14.1.1.3.5 Provider abort + +TC has the ability to abort a dialogue at both the dialogue-initiator side and the dialogue-responder side. + +The provider abort procedure is driven by the following event: + +- A TC-P-ABORT indication primitive + +#### *Receipt of a TC-P-ABORT indication* + +On receipt of a TC-P-ABORT indication, all dialogue related resources are released. + +#### 14.1.1.3.6 Mapping to TC dialogue primitives + +The TC-UNI service is not used by CAP. + +The mapping of parameters onto the TC Dialogue services is as follows: + +The use of parameters of the TC-BEGIN service is as defined in subclause 14.1.1.3.7 with the following qualifications: + +- The Destination Address parameter of the TC-BEGIN service shall be set to the CAP address of the AE which is to respond to the TC-BEGIN service. + +NOTE 1: The address used in this parameter may be mapped by SCCP address translation to one of a number of alternative AEs. + +- The AC Name parameter of the TC-BEGIN service shall be set according to the specific interface being used between the initiating AE and the responding AE. +- The Originating Address parameter of the TC-BEGIN service shall be set to the unambiguous CAP address of the AE initiating the TC-BEGIN service. + +The use of parameters of the TC-CONTINUE service is as defined in subclause 14.1.1.3.7 with the following qualifications: + +- The AC Name parameter of the TC-CONTINUE service shall be set to the value of the AC Name parameter of the TC-BEGIN service for the same TC Dialogue ID parameter value. +- If present, the Originating Address parameter of the TC-CONTINUE service shall be set to the unambiguous CAP address of the AE initiating the TC-CONTINUE service. This parameter is present only in the first TC-CONTINUE service after a TC-BEGIN service with the same TC Dialogue ID parameter value. + +The use of parameters of the TC-END service is as defined in subclause 14.1.1.3.7 with the following qualifications: + +- The AC Name parameter of the TC-END service shall be set to the value of the AC Name parameter of the TC-BEGIN service for the same TC Dialogue ID parameter value. This parameter is present only if the TC-END service is used immediately after the TC-BEGIN service. + +The use of parameters of the TC-U-ABORT service is as defined in subclause 14.1.1.3.7 with the following qualifications: + +- The Abort Reason parameter of the TC-U-ABORT service shall be used as specified in ETSI ETS 300 287-1 [22]. +- The AC Name parameter of the TC-U-ABORT service shall be set to the value used in the TC-BEGIN service. + +NOTE 2: This parameter is present only if the TC-U-ABORT is the immediate response to a TC-BEGIN indication. + +The use of parameters of the TC-P-ABORT service is as defined in subclause 14.1.1.3.7 with the following qualifications: + +- The P-Abort parameter of the TC-P-ABORT service is set by TC to indicate the reason why TC aborted the dialogue. It shall take the values as defined in ETSI ETS 300 287-1 [22]. + +#### 14.1.1.3.7 Default mapping to TC dialogue parameters + +##### *Dialogue Id* + +The value of this parameter is associated with the CAP invocation in an implementation dependent manner. This parameter uniquely identifies a specific TC dialogue to a remote CAP AE for a CAP AE. + +*Application-context-name* + +The application-context-name parameter is set in accordance with the set of Operations which need to be supported by the TC dialogue. The defined AC Names can be found in clauses 6 to 8. + +*User information* + +This parameter may be used by both initiating and responding application processes. This parameter shall be used for the CAP-GPRS-ReferenceNumber as defined in 14.1.7. For interfaces other than the gprsSSF-gsmSCF interface and for SMS related messages (as in subclauses 14.1.3, 14.1.4 and 14.1.5) the receiving side may ignore this parameter if received. The User Information parameter shall be encoded in accordance with the definition provided in ITU-T Recommendation Q.773 [46], subclause 3.2, and the definition of EXTERNAL type provided in ITU-T Recommendation X.690 [57], with the restriction that: + +- a size (1..10) constraint of SEQUENCE OF EXTERNAL; +- an Object Identifier shall always be present to identify the user information and the entity which sent it; +- a single-ASN-1-type is used for encoding. + +For the use of CAP defined TC-U-Abort reason, see the ASN.1 notation in the subclause 5.7. + +For the use of CAP defined CAP-GPRS-ReferenceNumber, see subclause 14.1.7. For the abstract syntax of CAP defined CAP-GPRS-ReferenceNumber, see the ASN.1 notation in the subclause 8.1. + +*Component present* + +This parameter is used by TC-USER as described in ETSI ETS 300 287-1 [22]. + +*Termination* + +The value of the release method parameter of the TC-END request primitive is set by TC-USER according to the rules as stated in subclauses 14.1.2.1.1 and 14.1.2.1.2. + +*Quality of service* + +The quality of service of TC request primitives is set by the TC-USER to the following value: + +- Sequencing requested; +- return option, this parameter is set by TC-USER in an implementation dependent manner. + +#### 14.1.1.4 Component handling + +##### 14.1.1.4.1 Procedures for CAP Operations + +The present subclause describes the procedures for CAP Operations. + +*Operation invocation* + +TC-USER shall build an operation argument from the parameters received and request the invocation of the associated operation using the TC-INVOKE procedure. If a linked ID parameter is inserted in the primitive, then this indicates a child operation and implies that the operation is linked to a parent operation. + +*Operation invocation receipt* + +On receipt of a TC-INVOKE indication primitive, TC-USER shall: + +- If the operation code does not correspond to an operation supported by the application-context, then request the transfer of a reject component using the TC-U-REJECT request primitive, with the appropriate problem code (unrecognized operation); +- If a linked ID is included, then perform the following checks: If the operation referred to by the linked ID does not allow linked operations or if the operation code does not correspond to a permitted linked operation, or if the parent operation invocation is not active, then request the transfer of a reject component using the TC-U-REJECT request primitive, with the appropriate problem code (linked response unexpected or unexpected linked operation); + +- If a linked ID is not included, but a Linked ID is needed to correlate the indication primitive with a parent operation invocation, then request the transfer of a reject component using the TC-U-REJECT request primitive, with the appropriate problem code (mistyped parameter); +- If the type of the argument is not the one defined for the operation, then request the transfer of a reject component using the TC-U-REJECT request primitive, with the appropriate problem code (mistyped parameter); +- If the operation cannot be invoked because the CAP related dialogue is about to be released, then request the transfer of a reject component using the TC-U-REJECT request primitive with the problem code (Initiating Release); +- If sufficient CAP related resources are not available to perform the requested operation, then request the transfer of a reject component using the TC-U-REJECT request primitive with the problem code (Resource Limitation); +- Otherwise, accept the TC-INVOKED indication primitive. If the operation is to be user confirmed, then TC-USER waits for the corresponding response. + +#### *Operation Response* + +For user confirmed operations, TC-USER shall: + +- If no error indication is included in the response to a class 1 or 3 operation, then construct a result information element from the parameters received and request its transfer using the TC-RESULT-L service. +- If an error indication is included in the response to a class 1 or 2 operation, then construct an error parameter from the parameters received and request its transfer using the TC-U-ERROR request primitive. + +#### *Receipt of a response* + +On receipt of a TC-RESULT-NL indication, TC-USER shall: + +- Request the transfer of a reject component using the TC-U-REJECT request primitive, with the appropriate problem code (mistyped parameter). + +On receipt of a TC-RESULT-L indication, TC-USER shall: + +- If the type of the result parameter is not the one defined for the result of this operation, request the transfer of a reject component using the TC-U-REJECT request primitive, with the appropriate problem code (mistyped parameter); +- Otherwise, accept the TC-RESULT-L indication primitive. + +On receipt of a TC-U-ERROR indication, TC-USER shall: + +- If the error code is not defined for the TC-USER or is not one associated with the operation referred to by the invoke ID, request the transfer of a reject component using the TC-U-REJECT request primitive, with the appropriate problem code (unrecognized error or unexpected error); +- If the type of the error parameter is not the one defined for this error, request the transfer of a reject component using the TC-U-REJECT request primitive, with the appropriate problem code (mistyped parameter); +- Otherwise, accept the TC-U-ERROR indication primitive. + +On receipt of a TC-U-REJECT indication primitive which affects a pending operation, TC-USER shall: + +- accept the TC-U-REJECT indication primitive. + +On receipt of a TC-L-REJECT indicating "return result problem, return error unexpected", TC-USER shall inform the application process. + +On receipt of a TC-L-REJECT indicating "return error problem, return error unexpected", TC-USER shall inform the application process. + +This event occurs when the local TC detects a protocol error in an incoming component which affects an operation. + +When the problem code indicates a general problem, it is considered that the event cannot be related to an active operation even if the invoke Id is provided by TC. This is because it is unclear whether the invoke Id refers to a local or remote invocation. The behaviour of TC-USER in such a case is described in the subclause headed "other events". + +On receipt of a TC-L-CANCEL indication, the TC-USER shall: + +- If the associated operation is a class 1 operation, inform the application process; +- If the associated operation is a class 2 operation and no linked operations are defined for this operation, ignore the primitive; +- If the associated operation is a class 2 operation and has linked operations but none of them has been invoked, inform the application process; +- If the associated operation is a class 2 operation and a linked operation invocation has already been received in response to this operation, ignore the primitive; +- If the associated operation is a class 3 operation, inform the application process; +- If the associated operation is a class 4 operation, ignore the primitive; + +#### *Other events* + +This subclause describes the behaviour of TC-USER on receipt of a component handling indication primitive which cannot be related to any operation or which does not affect a pending one. + +On receipt of a TC-U-REJECT indication primitive which does not affect an active operation (i.e. indicating a return result or return error problem), it is up to the application process to abort, continue or terminate the dialogue, if not already terminated by the sending application process according to the rules as stated in subclause 14.1.2.1.2. This is also applicable for invoke problems related to a class 4 linked operation. + +On receipt of a TC-R-REJECT indication (i.e. when a protocol error has been detected by the peer TC entity) which does not affect an active operation, it is up to the application process to abort, continue or terminate the dialogue, if not already terminated by the sending application process according to the rules as stated in subclause 14.1.2.1.2. + +On receipt of a TC-L-REJECT indication primitive (i.e. when a protocol error has been detected by the local TC entity) which cannot be related to an active operation, it is up to the application process to continue, or to terminate the dialogue and implicitly trigger the transmission of the reject component or to abort the dialogue. + +On receipt of a TC-NOTICE indication primitive, which informs the TC-USER that a message cannot be delivered by the Network Layer, it is for the application process to decide whether to terminate the dialogue or retry. + +This primitive can occur only if the Return Option has been set (see subclause 14.1.1.3.6). + +#### 14.1.1.4.2 Mapping to TC component primitives + +The mapping of parameters onto the TC Component services is as follows: + +The TC-U-CANCEL service is not used. + +The TC-RESULT-NL service is not used. + +The use of parameters of the TC-INVOKE service is as defined in subclause 14.1.1.4.3 with the following qualifications: + +- The Operation parameter of the TC-INVOKE service shall contain the *operation.&operationCode* value of the CAP Operation to be invoked. The operation must be one of the valid operations supported by the AC for the TC dialogue and must be invokable by the local AE. +- The Parameters parameter of the TC-INVOKE service shall contain a value of the *operation.&ArgumentType* value for the operation being invoked, as specified by the Operation parameter. + +The use of parameters of the TC-RESULT-L service is as defined in subclause 14.1.1.4.3 with the following qualifications: + +- The Invoke Id parameter of the TC-RESULT-L service shall be set to the value of the Invoke Id parameter of the TC-INVOKE service from the remote AE to which a result is being sent. +- The Operation parameter of the TC-RESULT-L service be set to the value of the Operation parameter of the TC-INVOKE service from the remote AE which contains the same Invoke Id Parameter value. +- The Parameters parameter of the TC-RESULT-L service shall contain the *operation.&ResultType* value for the operation result, as specified by the Operation parameter. + +The use of parameters of the TC-U-ERROR service is as defined in subclause 14.1.1.4.3 with the following qualifications: + +- The Invoke Id parameter of the TC-U-ERROR service shall be set to the value of the Invoke Id parameter of the TC-INVOKE service from the remote AE to which an error is being sent. +- The Error parameter of the TC-U-ERROR service shall be set to the value of the *error.&errorCode* of the error to be sent. It must be one of the errors which is expected for the invoked operation as defined in the *operation.&Errors* specification. +- The Parameters parameter of the TC-U-ERROR service shall be set to the value of the *error.&ParameterType* of the error to be sent, as identified by the Error parameter. + +The use of parameters of the TC-U-REJECT service is as defined in subclause 14.1.1.4.3 with the following qualifications: + +- The Invoke Id parameter of the TC-U-REJECT service shall be set to the Invoke Id Parameter of the TC component service from the remote AE which is being rejected. + +The use of parameters of the TC-L-CANCEL service is as defined in subclause 14.1.1.4.3. + +#### 14.1.1.4.3 Default mapping to TC component parameters + +##### *Invoke Id* + +This parameter is set by the sending application process. It represents the unique identity of an instance of an operation which is invoked by an AE within a specific TC dialogue. The TC dialogue is identified by the Dialogue Id parameter. + +##### *Linked Id* + +This parameter is set by the sending application process. It represents the Invoke Id of an operation which was received from the remote AE for a specific TC dialogue to which the operation being invoked by the local AE is to be linked. This parameter is present only if the original operation invoked by the remote AE is defined as having linked operations. The type of local operation invoked must be the same type as one of the operations defined as being linked. + +##### *Dialogue Id* + +The value of this parameter is associated with the CAP invocation in an implementation dependent manner. It represents the identity of the established TC dialogue which will carry the component services between the local AE and the remote AE. + +##### *Class* + +The value of this parameter is set according to the type of the operation to be invoked according to the operation definitions in clauses 6 through 8. + +##### *Time out* + +The value of this parameter is set according to the type of operation invoked. + +##### *Last component* + +This parameter is used as described in ETSI ETS 300 287-1 [22]. + +##### *Problem code* + +This parameter is used as described in subclause 14.1.1.4.1. + +*Abort reason* + +This parameter is used by TC-USER, and attributes and coding are specified by network operator. + +## 14.1.2 gsmSSF-gsmSCF interfaces + +### 14.1.2.1 Normal procedures + +#### 14.1.2.1.1 gsmSSF-to-gsmSCF messages + +The present subclause defines the normal procedures for TC messages from the gsmSSF to the gsmSCF. + +*gsmSSF FSM related messages* + +A dialogue shall be established when the gsmSSF FSM transits from the state "Idle" to the state "Waiting\_for\_Instructions". + +The CAP Operation InitialDP shall be sent with a TC-BEGIN request primitive. + +When the dialogue was opened with InitialDP or InitiateCallAttempt operation then the gsmSSF shall maintain the dialogue when sending the SpecializedResourceReport operation indicating the announcement complete for PlayAnnouncement regardless of the fact whether the disconnectFromIPForbidden parameter was set to true or false. + +For all other operations sent from the gsmSSF FSM, the dialogue shall be maintained except for the following cases. + +When the gsmSSF FSM executes a non-error case state transition to the state "Idle" and there is one or more pending operation and TC dialogue is established, TC dialogue can be terminated by TC-END primitive with component(s). When the gsmSSF sends the last EventReportBCSM, ApplyChargingReport or CallInformationReport the dialogue may be ended from the gsmSSF by a TC-END request primitive with basic end. + +In the case that there is no pending operation and TC dialogue is established, TC dialogue can be terminated by TC-END primitive with zero component or prearranged end. When the gsmSSF FSM makes a non-error case state transition to the state "Idle" and there is no operation to be sent, the dialogue is ended by means of a TC-END request primitive (basic) with zero components, or the dialogue is locally ended by means of a TC-END request primitive with prearranged end. + +In the case where a call release is initiated by any other entity than a gsmSCF, the gsmSSF can end a dialogue with a TC-END request primitive with zero component or prearranged end if a TC dialogue is established and the gsmSSF has no pending call information requests (or pending requests which should be treated in the same way, see subclause 14.1.1.1) nor any armed EDP. + +When the gsmSSF has sent the last EventReportBCSM, ApplyChargingReport or CallInformationReport the dialogue may be ended from the gsmSCF by a TC-END request primitive with basic end. + +*Assisting gsmSSF FSM related messages* + +A dialogue shall be established when the assisting gsmSSF FSM transits from the state "Idle" to the state "Waiting\_for\_Instructions". The AssistRequestInstructions operation shall be transmitted with a TC-BEGIN request primitive. + +For all other operations sent from the assisting gsmSSF FSM, the dialogue shall be maintained except for the following cases. + +When the assisting gsmSSF FSM makes a non-error case state transition to the state "Idle" and there is one or more pending operation and TC dialogue is established, TC dialogue can be terminated by TC-END primitive with component(s). + +In the assisting gsmSSF case the same rules apply as for the gsmSRF as specified for the SpecializedResourceReport operation in subclause 14.1.3.1.1. + +In the case that there is no pending operation and TC dialogue is established, TC dialogue can be terminated by TC-END primitive with zero component or prearranged end. When the assisting gsmSSF FSM makes a non-error case state transition to the state "Idle" and there is no operation to be sent, the dialogue is ended by means of a TC-END request primitive (basic) with zero components, or the dialogue is locally ended by means of a TC-END request primitive with prearranged end. + +*gsmSSME FSM related messages* + +The following procedures shall be followed: + +- The dialogue shall be maintained when the ActivityTest Return Result is sent. + +#### 14.1.2.1.2 gsmSCF-to-gsmSSF messages + +The present subclause defines the normal procedures for TC messages from the gsmSCF to the gsmSSF. + +*SCSM-FSM related messages* + +A dialogue shall be established when the SCSM-FSM receives an InitialDP operation for TDP-R or an AssistRequestInstructions operation, or sends an InitiateCallAttempt operation. + +For subsequent operations sent from the SCSM-FSM, the dialogue shall be maintained except for the following cases; + +The dialogue shall no longer be maintained when the prearranged end condition is met in the gsmSCF. When the gsmSCF does not expect any messages other than possibly REJECT or ERROR messages for the operations sent and when the last associated operation timer expires, the dialogue is locally ended by means of a TC-END request primitive with prearranged end. + +Alternatively, the sending of operations, leading to the termination of the relationship, by means of a TC-END request primitive (basic end) is possible. + +*SCME-FSM related messages* + +The operations sent from the SCME-FSM shall be issued according to the following procedures: + +- The dialogue shall be maintained when the ActivityTest operation is sent. +- For sending one or more CallGap operations, the SCME FSM shall use an existing SCSM FSM associated dialogue which was initiated by a gsmSSF FSM (i.e. established for the transmission of the InitialDP operation). The dialogue shall be maintained. + +#### 14.1.2.1.3 smsSSF -to-gsmSCF SMS related messages + +A dialogue shall be established when the smsSSF has finalised trigger processing and transits to the state "Waiting\_for\_Instructions". The relevant CAP Operation, which can be the InitialDPSMS operation only, shall be transmitted in the same message. + +For all other operations sent from the smsSSF, the dialogue shall be maintained. + +The dialogue shall no longer be maintained when the prearranged end condition is met in the smsSSF. When the smsSSF makes a state transition to the state "Idle", the dialogue is locally ended by means of a TC-END request primitive with prearranged end. + +When the smsSSF FSM transits to the state "Idle", but no event was reported to the gsmSCF, then the smsSSF shall send TC-END with zero components to the gsmSCF. + +When the smsSSF has sent the last EventReportSMS operation the dialogue may be ended from the gsmSCF by a TC-END request primitive with basic end. If the smsSSF decides to apply basic end, then it shall send TC-END with zero components. + +#### 14.1.2.1.4 gsmSCF-to-smsSSF SMS related messages + +All operations are sent after a dialogue was established from the smsSSF (the gsmSCF has previously received a TC-BEGIN indication primitive with an InitialSMSEvent operation). + +The dialogue shall no longer be maintained when the prearranged end condition is met in the gsmSCF. When the gsmSCF does not expect any messages other than possibly REJECT or ERROR messages for the operations sent and when the last associated operation timer expires, the dialogue is locally ended by means of a TC-END request primitive with prearranged end. + +Alternatively, the sending of operations, leading to the termination of the control relationship, by means of a TC-END request primitive (basic end) is possible. + +#### 14.1.2.1.5 Use of dialogue handling services + +Dialogue handling services are used to trigger the sending of the APDUs associated with the operations involved in the CAP packages. + +Component grouping is performed under the control of the application-process through an appropriate usage of the TC-BEGIN, TC-CONTINUE and TC-END service. + +#### 14.1.2.2 Abnormal procedures + +The following procedures also apply to the gsmSCF-gsmSRF interfaces. + +##### 14.1.2.2.1 gsmSCF-to-gsmSSF/gsmSRF messages + +Considering that gsmSSF and gsmSRF do not have the logic to recover from error cases detected on the gsmSCF-gsmSSF/gsmSRF interface, the following shall apply: + +- Operation errors and rejection of TC components shall be transmitted to the gsmSSF and, respectively, the gsmSRF with a TC-END request primitive, basic end. + +If, in violation of the above procedure, an ERROR or REJECT component is received with a TC-CONTINUE indication primitive, then the gsmSSF and, respectively, the gsmSRF shall abort the dialogue with a TC-U-ABORT request primitive. + +##### 14.1.2.2.2 gsmSSF/gsmSRF/ -to-gsmSCF messages + +Operation errors and rejection of TC components shall be transmitted to the gsmSCF according to the following rules: + +- The dialogue shall be maintained when the preceding message, which contained the erroneous component, indicated that the dialogue shall be maintained. I.e. the error or reject shall be transmitted with a TC-CONTINUE request primitive if the erroneous component was received with a TC-CONTINUE indication primitive. +On receipt of an ERROR or REJECT component the gsmSCF decides on further processing. It may either continue, explicitly end or abort the dialogue. +- When the gsmSSF has received and processed InitiateCallAttempt and has acknowledged InitiateCallAttempt with InitiateCallAttempt-RESULT, then a User Error resulting from an erroneous component that is contained in the same TC\_Begin message as InitiateCallAttempt, shall be transmitted with a TC-CONTINUE indication primitive. +- In all other situations the dialogue shall no longer be maintained. I.e. the error or reject shall be transmitted with a TC-END request primitive, basic end, if the erroneous component was received with a TC-BEGIN indication primitive. +- on expiration of application timer Tssf or Tsrf, dialogue shall be terminated by means of by TC-U-ABORT primitive with an Abort reason, regardless of TC dialogue is established or not. + +If the error processing in the gsmSSF or gsmSRF leads to the case where the gsmSSF or gsmSRF is not able to process further gsmSCF operations while the dialogue is to be maintained, then the gsmSSF or gsmSRF aborts the dialogue with a TC-END request primitive with basic end or a TC-U-ABORT request primitive, depending on whether any pending ERROR or REJECT component is to be sent or not. + +The gsmSSF can end a dialogue with a TC-U-ABORT request primitive in the case that call release is initiated by any other entity then the gsmSCF and the gsmSSF has no pending call information requests (or pending requests which should be treated in the same way, i.e., ApplyCharging nor any armed EDP to notify the gsmSCF of the call release (for alternative way, see subclause 14.1.2.1.1). + +##### 14.1.2.2.3 gsmSCF-to-smsSSF SMS related messages + +Considering that the smsSSF does not have the logic to recover from error cases detected on the gsmSCF-smsSSF interface, the following shall apply: + +- operation errors and rejection of TC components shall be transmitted to the smsSSF with a TC-END request primitive, basic end. + +If, in violation of the above procedure, an ERROR or REJECT component is received with a TC-CONTINUE indication primitive, then the smsSSF shall abort the dialogue with a TC-U-ABORT request primitive. + +#### 14.1.2.2.4 smsSSF-to-gsmSCF SMS related messages + +Operation errors and rejection of TC components shall be transmitted to the gsmSCF according to the following rules: + +- the dialogue shall be maintained when the preceding message, which contained the erroneous component, indicated that the dialogue shall be maintained. I.e. the error or reject shall be transmitted with a TC-CONTINUE request primitive if the erroneous component was received with a TC-CONTINUE indication primitive; +- on receipt of an ERROR or REJECT component the gsmSCF decides on further processing. It may either continue, explicitly end or abort the dialogue; + +If the error processing in the smsSSF leads to the case where the smsSSF is not able to process further gsmSCF operations while the dialogue is to be maintained, then the smsSSF aborts the dialogue with a TC-U-ABORT request primitive. + +The smsSSF aborts a dialogue with a TC-U-ABORT request primitive if release is initiated by any other entity than the gsmSCF and the smsSSF has no armed EDPs to notify the gsmSCF. + +#### 14.1.2.2.5 Use of dialogue handling services + +On receipt of a TC-U-REJECT.ind in the FE, this primitive should be ignored. It is up to the application process to abort, continue or terminate the dialogue, if not already terminated by the sending application process according to the rules as stated in subclause 14.1.1.2. This is also applicable for invoke problems related to a class 4 linked operation. + +A TC-U-REJECT.req should be sent followed by a TC-CONTINUE.req. + +On receipt of a TC-R-REJECT.ind in the FE, this primitive should be ignored. It is up to the application process to abort, continue or terminate the dialogue, if not already terminated by the sending application process according to the rules as stated in subclause 14.1.1.2. This is also applicable for invoke problems related to a class 4 linked operation. + +On receipt of a TC-L-REJECT indication primitive (i.e. when a protocol error has been detected by the local TC entity) which cannot be related to an active operation, it is up to the application process to continue or to terminate the dialogue and implicitly trigger the transmission of the reject component or to abort the dialogue. + +On receipt of a TC-NOTICE indication the TC-USER is informed that a message cannot be delivered by the Network Layer. It occurs if the Return Option has been set (see subclause 14.1.1.3.7). It is for the application process to decide whether to terminate the dialogue or retry. + +The application-process is the sole user of the TC-P-ABORT service and TC-NOTICE service. + +The receipt of a TC-U-ABORT-Ind or TC-P-ABORT-Ind on a dialogue terminates all request processing. + +#### 14.1.2.3 Dialogue handling + +##### 14.1.2.3.1 Dialogue establishment + +##### 14.1.2.3.2 Dialogue continuation + +##### 14.1.2.3.3 Dialogue termination + +##### 14.1.2.3.4 User abort + +##### 14.1.2.3.5 Provider abort + +##### 14.1.2.3.6 Mapping to TC dialogue primitives + +The gsmSSF-gsmSCF IN services can be mapped onto TC services. The present subclause defines the mapping of the gsmSSF-gsmSCF IN services onto the services of the TC dialogue handling services defined in ETSI ETS 300 287-1 [22]. + +- a) The TC-BEGIN service is used to invoke the operations of the gsmSCF-gsmSSF connection packages as defined in clause 6. +- b) The TC-CONTINUE service is used to report the success of the operations invoked in a TC-BEGIN service and to invoke or respond to any other operations. +- c) The TC-U-ABORT service is used to report the failure of operations of the connection packages as defined in clause 6. + +The mapping of the parameters onto the TC-BEGIN primitive is defined in subclause 14.1.1.3.6 with the following qualifications: + +- The AC Name parameter shall take the value of the application-context-name field of the cap3-sms-AC object if the initiating AE is a gsmSSF. + +The mapping of the parameters onto the TC-CONTINUE primitive is defined in subclause 14.1.1.3.6. + +The mapping of the parameters onto the TC-U-ABORT primitive is defined in subclause 14.1.1.3.6 with the following qualifications: + +- The Application-Context-Name parameter shall be used as specified in ETSI ETS 300 287-1 [22]. When the responding AE refuses a dialogue because the application-context-name it receives is not supported, this parameter shall have the value of the application-context-name field of the cap3-sms-AC object if the responding AE is a gsmSCF. + +The use of the parameters of the TC-END service is defined in subclause 14.1.1.3.6. + +## 14.1.2.4 Component Handling + +### 14.1.2.4.1 Procedures for CAP Operations + +The CAP ASEs are users of the TC component handling services except for the TC-L-REJECT and TC-L-CANCEL services which are used by the application-process. Receipt of a TC-L-REJECT-Ind leads the application-process to abandon the dialogue (i.e. it issues a TC-U-ABORT-Request primitive). + +The TC-U-CANCEL service is never used. + +### 14.1.2.4.2 Mapping to TC component parameters + +The gsmSSF-gsmSCF IN ASE services are mapped onto the TC component handling services. The mapping of operations and errors onto TC services is defined in subclause 14.1.1.4.2 with the following qualifications: + +The timeout parameter of the TC-INVVOKE-Req primitives is set according to clause 6. + +## 14.1.3 gsmSCF-gsmSRF interface + +### 14.1.3.1 Normal procedures + +#### 14.1.3.1.1 gsmSCF-to/from-gsmSRF messages + +A dialogue is established when the gsmSRF sends an AssistRequestInstructions operation to the gsmSCF. For all other operations sent to/from the gsmSRF, the dialogue shall be maintained. + +In the case that there is no pending operation and TC dialogue is established, TC dialogue can be terminated by TC-END primitive with zero component. When the SCSM makes a non-error case state transition to end-user interaction and there is no operation to be sent, the dialogue is ended by means of a TC-END request primitive (basic) with zero components. + +When the dialogue is opened with the AssistRequestInstructions operation then the gsmSRF shall no longer maintain the dialogue when sending the SpecializedResourceReport operation indicating announcement complete for PlayAnnouncement with disconnectFromIPForbidden parameter was set to false or Return Result of the PromptAndCollectUserInfo with disconnectFromIPForbidden parameter was set to false. The dialogue is ended by means of a TC-END request primitive with basic end, and the SpecializedResourceReport operation is transmitted with the same request. + +Regardless of whether pending operation exists or not, when the SRSM-FSM is informed of the disconnection of bearer connection (in the case of gsmSCF initiated disconnection or call abandon from call party) and dialogue is established, the dialogue is ended by means of a TC-END request primitive (basic) with zero components or TC-END request primitive (prearranged end). + +The dialogue shall no longer be maintained when the prearranged end condition is met in the gsmSRF. When the SRSM-FSM is informed the disconnection of bearer connection and TC dialogue is not established, TC dialogue is locally terminated by TC-END primitive with prearranged end. + +When the gsmSCF does not expect any messages other than possibly REJECT or ERROR messages for the operations sent and when the last associated operation timer expires, the dialogue is locally ended by means of a TC-END request primitive with prearranged end. Alternatively, the sending of operations, leading to the termination of the relationship, by means of a TC-END request primitive (basic end) is possible. + +In the relay case, the gsmSRF-gsmSCF relationship uses the gsmSSF-gsmSCF TC dialogue. This is possible, because begin and end of the gsmSRF-gsmSCF relationship are embedded in the gsmSSF-gsmSCF relationship. gsmSRF-gsmSCF information shall be exchanged with TC-CONTINUE request primitives. + +#### 14.1.3.1.2 Abnormal procedures + +##### 14.1.3.1.3 Dialogue handling + +###### 14.1.3.1.3.1 Dialogue establishment + +###### 14.1.3.1.3.2 Dialogue continuation + +###### 14.1.3.1.3.3 Dialogue termination + +###### 14.1.3.1.3.4 User abort + +###### 14.1.3.1.3.5 Provider abort + +###### 14.1.3.1.3.6 Mapping to TC dialogue primitives + +The gsmSCF-gsmSRF IN services can be mapped onto TC services. The present subclause defines the mapping of the gsmSCF-gsmSRF IN services onto the services of the TC dialogue handling services defined in ETSI ETS 300 287-1 [22]. + +- a) The TC-BEGIN service is used to invoke the operations of the gsmSRF-gsmSCF connection packages as defined in clause 6. +- b) The TC-CONTINUE service is used to report the success of the operations invoked in a TC-BEGIN service and to invoke or respond to any other operations. +- c) The TC-U-ABORT service is used to report the failure of operation of the gsmSCF-gsmSRF operations packages as defined in clause 6. + +The mapping of parameters onto the TC Dialogue services is as defined in subclause 14.1.1.3.6 with the following qualifications: + +The mapping of the parameters onto the TC-BEGIN primitive is defined in subclause 14.1.1.3.6 with the following qualifications: + +- The AC Name parameter shall take the value of the application-context-name field of the gsmSRF-gsmSCF-ac object. + +#### 14.1.3.2 Component handling + +##### 14.1.3.2.1 Procedures for CAP Operations + +##### 14.1.3.2.2 Mapping to TC component parameters + +The mapping of parameters for the TC component services is defined in subclause 14.1.1.4.2 with the following qualifications. + +The Timeout Parameter of the TC-INVOKE service is set according to clauses 6. + +## 14.1.4 gprsSSF-gsmSCF interface + +### 14.1.4.1 Normal procedures + +#### 14.1.4.1.1 TC-dialogues and relationships + +The GPRS dialogue can consist of multiple consecutive TC-dialogues. A GPRS dialogue is identified by a GPRS-ReferenceNumber consisting of the originationReference and the destinationReference. One GPRS-Reference is assigned by the SGSN and shall be unique within this SGSN. The other GPRS-Reference is assigned by the gsmSCF and shall be unique within this gsmSCF. + +The *TC*-dialogues are closed and (re)opened whenever necessary. + +#### 14.1.4.1.2 Use of the GPRS Reference + +For the use of CAP defined GPRS-ReferenceNumber, see also the ASN.1 notation in the subclause 8.1. + +When the gprsSSF sends the first operation for a new GPRS dialogue (InitialDPGPRS), the gprsSSF shall include a GPRS Reference Number in the TC message. This GPRS Reference Number shall consist of the *SGSN Process Id* as originationReference, which is internally allocated by the gprsSSF. This number is used by the gprsSSF to associate an incoming TC message with an internal GPRS Process. + +When the gsmSCF has received the InitialDPGPRS operation, it shall store the SGSN Process ID and allocate an *SCF Process Id* which is used by the gsmSCF to associate an incoming TC message with an internal gsmSCF Process. + +The gsmSCF shall include the GPRS Reference Number in the first TC-CONTINUE message, *SGSN Process Id* in destinationReference and *SCF Process Id* in originationReference, returned to the gprsSSF. + +When the gprsSSF receives the first TC message from the gsmSCF for this GPRS dialogue, the gprsSSF shall store the gsmSCF Process Id together with the SGSN Process Id. + +From here onwards all the TC messages that open a new TC dialogue shall include the GPRS Reference Number consisting of the originationReference and the destinationReference to associate the internal process in the origination entity and the destination entity, respectively, until the end of the relationship between these processes. + +For any TC-CONTINUE in the existing TC dialogue, transporting the GPRS Reference Number is not needed except for the first response after the InitialDPGPRS operation. + +#### 14.1.4.1.3 gprsSSF-to-gsmSCF messages + +The present subclause defines the normal procedures for TC messages from the gprsSSF to the gsmSCF. + +##### *gprsSSF FSM related messages* + +A GPRS dialogue and a TC dialogue shall be established when the gprsSSF FSM transits from the state "Idle" to the state "Waiting\_for\_Instructions". The InitialDPGPRS operation shall be transmitted in the same TC message, i.e. TC-BEGIN. It shall contain the GPRS-Reference as assigned by the SGSN in the originationReference. The gprsSSF may initiate the subsequent TC dialogues for this GPRS dialogue with the following operations: + +- ApplyChargingReportGPRS +- EntityReleasedGPRS +- EventReportGPRS + +For the establishment of a new TC dialogue within the context of the current GPRS dialogue, the gprsSSF may apply one of the following mechanisms: + +- (1) the gprsSSF shall memorise the gsmSCF address used in the first response message to the InitialDPGPRS and use it to open the new TC dialogue; +- (2) the gprsSSF shall use the gsmSCF address from GPRS-CSI to open the new TC dialogue. + +The gsmSCF shall memorise the gprsSSF address received along with the InitialDPGPRS and use it for the opening of new TC dialogues within the context of the current GPRS dialogue. + +The gsmSCF may open subsequent TC dialogues with the following CAP Operations: + +- ActivityTestGPRS; +- ApplyChargingGPRS; +- CancelGPRS; +- FurnishChargingInformationGPRS; +- ReleaseGPRS; +- RequestReportGPRSEvent; +- SendChargingInformationGPRS. + +The CAP Operation that opens a TC dialogue shall be sent with a TC-BEGIN request primitive. This message shall contain the GPRS-ReferenceNumber assigned by the sender of this message in the originationReference. If the operation opens a subsequent TC dialogue, then this message shall contain also the previously received destinationReference. If an operation opens a GPRS dialogue, then the TC message reply shall contain the originationReference as assigned by the sender, i.e. the gsmSCF. + +The TC dialogue shall be closed for the idle periods, i.e. when the gprsSSF FSM transits from the state "Waiting\_for\_Instructions" to the state "Idle", if the gprsSSF FSM is in the state "Monitoring" and has received all replies or time-outs for the operations sent, after standalone operations of the gsmSCF in Monitoring state if gprsSSF FSM does not transit to the state "Idle" (ActivityTestGPRS, ApplyChargingGPRS, CancelGPRS, FurnishChargingInformationGPRS, RequestReportGPRSEvent, SendChargingInformationGPRS), or at the end of a GPRS dialogue. + +Each TC dialogue shall be terminated by the gprsSSF using TC-END (basic end). The following operations can cause the end of the GPRS dialogue: + +- ContinueGPRS; +- ConnectGPRS; +- ApplyChargingReportGPRS result; +- EntityReleasedGPRS result; +- EventReportGPRS (EDP-N) result; +- CancelGPRS; +- ReleaseGPRS; +- RequestReportGPRSEvent (disarming of DPs). + +When the gprsSSF FSM makes a non-error case state transition to the state "Idle" and there is one or more pending operation and TC dialogue is established, TC dialogue may be terminated by TC-END primitive with zero component(s) after all pending operations have been sent. When the gprsSSF sends the last EventReportGPRS, EntityreleasedGPRS or ApplyChargingReportGPRS, then after reception of the result or error, the GPRS dialogue may be ended from the gprsSSF by a TC-END request primitive with basic end. + +In the case that there is no pending operation, result nor error, and TC dialogue is established, TC dialogue shall be terminated by a TC-END primitive with zero component. + +In the case where a PDP Context release or detach is initiated by any other entity than a gsmSCF, the gprsSSF shall end a GPRS dialogue with the EntityReleasedGPRS operation if the gprsSSF has no armed DP to report nor pending ApplyChargingReportGPRS which should reported. + +In the case of overlapping dialogues for the same GPRS dialogue the gsmSCF opened TC dialogue is aborted by the gprsSSF with the abort reason overlapping-dialogue as specified in subclause 5.7. This abort reason is used to indicate to the gsmSCF that a specific instance already has a TC dialogue open. It is typically obtained when both the gsmSCF and gprsSSF open a new dialogue at the same time. While the gprsSSF waits for a response to an operation sent in TC-BEGIN it may receive an operation from the gsmSCF in TC-BEGIN. In such cases the dialogue opened by the gprsSSF is maintained and the dialogue opened by the gsmSCF is aborted with this abort reason. + +#### *gprsSSME FSM related messages* + +The following procedures shall be followed: + +- The TC dialogue shall be terminated by a TC-END primitive with zero components after the ActivityTestGPRS Return Result is sent. + +#### 14.1.4.1.4 gsmSCF-to-gprsSSF messages + +The present subclause defines the normal procedures for TC messages from the gsmSCF to the gprsSSF. + +In the case of overlapping dialogues for the same relationship the gsmSCF opened dialogue is closed by the gprsSSF as specified in subclause 5.7. The gsmSCF shall first respond normally to the operations sent by the gprsSSF, and then decide on the further actions. + +#### *SCME-FSM related messages* + +The operations sent from the SCME-FSM shall be issued according to the following procedures: + +- A new subsequent TC dialogue is established when the ActivityTestGPRS operation is sent. + +### 14.1.4.2 Abnormal procedures + +#### 14.1.4.2.1 gsmSCF-to-gprsSSF messages + +The present subclause defines the abnormal procedures for TC messages from the gsmSCF to the gprsSSF. + +Considering that the gprsSSF does not have the logic to recover from error cases detected on the gsmSCF-gprsSSF interface, the following shall apply: + +- Operation errors and rejection of TC components shall be transmitted to the gprsSSF with a TC-END request primitive, basic end. +- The GPRS dialogue shall be closed. +- The gprsSSF shall apply Default GPRS Handling from the valid CSI to the PDP Context or GPRS Session. + +If, in violation of the above procedure, an ERROR or REJECT component is received with a TC-CONTINUE indication primitive, then the gprsSSF shall abort the dialogue with a TC-U-ABORT request primitive and shall apply Default GPRS Handling from the valid CSI to the PDP Context or GPRS Session. + +#### 14.1.4.2.2 gprsSSF-to-gsmSCF messages + +The present subclause defines the abnormal procedures for TC messages from the gprsSSF to the gsmSCF. + +Operation errors and rejection of TC components shall be transmitted to the gsmSCF according to the following rules: + +- The TC dialogue shall be maintained when the preceding message, which contained the erroneous component, indicated that the dialogue shall be maintained. I.e. the error or reject shall be transmitted with a TC-CONTINUE request primitive. +On receipt of an ERROR or REJECT component the gsmSCF decides on further processing. It may either continue, explicitly end or abort the TC dialogue. If the TC dialogue is closed due to such error, then the GPRS dialogue shall also be closed. +- on expiration of application timer Tssf, the TC dialogue shall be terminated by means of by TC-U-ABORT primitive with an Abort reason. The GPRS dialogue shall be closed. + +If the error processing in the gprsSSF leads to the case where the gprsSSF is not able to process further gsmSCF operations while the TC dialogue is to be maintained, then the gprsSSF aborts the TC dialogue with a TC-END request + +primitive with basic end or a TC-U-ABORT request primitive, depending on whether any pending ERROR or REJECT component is to be sent or not. + +The gprsSSF can end a TC dialogue with a TC-U-ABORT request primitive in the following case: + +- Any entity other than the gsmSCF initiates closure of the GPRS dialogue, and +- The gprsSSF has no pending reports, and +- The gprsSSF has no armed EDP to notify the gsmSCF that the GPRS dialogue has been closed. + +For an alternative method, see subclause 14.1.7.1.1. + +#### 14.1.4.2.3 Default GPRS Handling + +If a TC dialogue is closed due to unrecoverable TC/protocol error (does not apply to the overlapping TC dialogues), or aborted by the gsmSCF, or at the Tssf expiry, then the gprsSSF shall check the applicable Default GPRS Handling parameter of the GPRS-CSI. In this context the applicable Default GPRS Handling is the one that corresponds the TDP that opened the GPRS dialogue. The same default handling shall apply to all state models that are controlled by the particular GPRS dialogue. + +## 14.2 Services assumed from SCCP + +The present subclause describes the services required from the SCCP that may be used by the CAMEL applications for the CAMEL Application Part (CAP) used between the gsmSSF, assisting gsmSSF, gsmSRF, gprsSSF, and gsmSCF. + +The following SCCP revisions are supported by CAP: + +- Signalling Connection Control Part, Signalling System no. 7 CCITT ("Blue Book SCCP") +- Signalling Connection Control Part, Signalling System no. 7 ITU-T Recommendation Q.711 to Q.716 ("White Book SCCP") + +NOTE: Support of White Book SCCP at the receiving side shall be mandated from 00:01hrs, 1st July 2002(UTC). + +- ANSI T1.112-1996 [91]: "American National Standards for Telecommunications– Signalling System Number 7 (SS7) – Signalling Connection Control Part (SCCP)". + +When CAP uses White Book SCCP to send a message, and SCCP segments the message into one or more XUDT messages, then the transmission of this message may fail. + +Failure will occur when the destination SCCP, or any intermediate SCCP, does not support White Book SCCP. + +Support of ANSI T1.112-1996 [91] SCCP applies to PLMNs in North America only. Interworking between a PLMN in North America and a PLMN outside North America will involve a STP to translate between ANSI SCCP and ITU-T/CCITT SCCP. + +### 14.2.1 Normal procedures + +The SCCP forms the link between the TC and the MTP and provides (in conjunction with the MTP) the network services for the CAMEL applications. The network services provided allow the signalling messages sent by the application to the lower layers to be successfully delivered to the peer application. + +### 14.2.2 Service functions from SCCP + +#### 14.2.2.1 SCCP connectionless services + +The services described are those given in the SCCP ITU-T recommendations Q.711 to Q.716 should be consulted to identify possible interworking and compatibility issues between the different SCCP versions. + +The following Connection-less services are expected from the SCCP: + +- a) Network Addressing to enable signalling connections between SCCP users; + +- b) Sequence Control to enable the SCCP users to invoke "sequence guaranteed" or "sequence not guaranteed" options for a given stream of messages to the same destination; +- c) Segmentation/reassembly of large user messages (for "White Book SCCP" only); +- d) Return Option to enable the SCCP users to invoke "discard message on error" or "return message on error" for a given message not able to be delivered by the SCCP to the destination SCCP user, due to routeing or segmentation/re-assembly failure; +- e) Congestion control. + +The primitives used for the above services are given below. + +The N-UNITDATA request and N-UNITDATA indication primitives are used to send and receive data. The parameters of these primitives include the Called and Calling Addresses, Sequence Control, Return Option and User Data with the addressing parameters always mandatory. + +The N-NOTICE indication primitive is used to return undelivered data if return option is set and a routeing/segmentation error occurs. + +#### 14.2.2.1.1 Sub-System Number (SSN) + +The use of SSN is a network operator option and values for intra-PLMN usage are network specific. A CAP SSN has been reserved for inter-PLMN use, as defined in 3GPP TS 23.003 [5]. + +#### 14.2.2.1.2 Addressing + +The addressing elements consist of information contained within the Calling and the Called Party Addresses which are sent by the application to the lower layers. + +The application expects the SCCP to route messages by either (a) the use of the Destination Point Code (DPC) plus the Subsystem Number (SSN), or (b) the use of the GT plus optionally the SSN. The application also specifies to the lower layer whether to route the message on the DPC or the GT. + +Method (a) above may be used when the application is aware of the destination point code and the destination SSN located at that point code to which the message is to be delivered. Within a national network different SSNs, according to ITU-T Recommendation Q.713 [42], may be allocated for the different network specific applications, e.g. a SSN may be allocated for a gsmSCF functionality. + +Method (b) above may be used when a message is to be delivered to a SCCP-user which can be identified by the combination of the elements within the GT. An example of the use of this method is when messages have to be delivered between different networks. This method may be used since the originating network is unaware of the point code and SSN's allocations within the destination network. The network that determines the end-node to which the message is to be delivered has to perform a GT Translation to derive the destination Point Code and the SSN. If optionally the original address contained the SSN, then this may be used as the destination SSN, or the translation may, if required, provide an appropriate new SSN. + +When GT is used for addressing, the CAMEL application expects that the SCCP supports the following elements as defined in ITU-T Recommendation Q.713 [42]: + +##### *Address Indicator:* + +The application will set this indicator to indicate one or any combination of the elements "signalling point code, GT, subsystem number" in the address information octets. + +##### *GT Indicator:* + +This indicator specifies the method employed for the formatting of the address information. There are four values (1 to 4), for example, the value 4 indicates that the format includes the numbering plan, the nature of the address indicator and the translation type. The format with the indicator value 4 is always used for internetwork connections. + +##### *Translation Type:* + +The Translation Types are defined within ITU-T Recommendation Q.713 [42]. + +*Numbering Plan:* + +- 1) The *proposed* "generic numbering plan" is described within the ITU-T Recommendation Q.713 [42]. This numbering plan identifies the SCCP nodes or SCCP subsystems unambiguously such that messages may be efficiently routed within one or more networks, and is particularly useful when used in the Calling Address for the sending of a response message back to the originating node. This is achieved by having an international and a national part in the generic numbering plan. For response messages the responding node analyses the international part of the generic numbering plan to determine the gateway node to which the response is to be routed. Having routed to the gateway node, the national part (which was populated within the originating network) is analysed to determine the originating node within the originating network. +- 2) A numbering plan which would define particular nodes based specifically on services is outside the scope of CAMEL. +- 3) The SCCP caters for a number of other numbering plans (e.g. ISDN, Mobile etc. numbering plans). The whole range catered for is shown in [?]. These may be used by CAMEL applications if deemed suitable. + +*Encoding Scheme:* + +This identifies the encoding scheme employed by the application and is generally BCD encoded with odd or even number of digits. + +*GT Address Information:* + +These are the actual address digits supplied by the application and may be BCD digits or encoded as indicated by the encoding scheme. + +The network provider must ensure that any change of GT value during translation preserves any CAP specific information contained in the initial GT value. + +This requirement applies to all interfaces, not just those used for internetworking. + +If *route on SSN* is to be supported from the originating node, then an ITU-T non-zero internationally standardised SSN is required for international internetworking. + +In the absence of a ITU-T standardised non-zero SSN for CAP services, the use of *route on GT* is mandatory from the origin node to the network containing the destination node. + +When the SCCP of CCITT Signalling System No. 7 is used, the format and coding of address parameters carried by the SCCP for that purpose shall comply with ITU-T Recommendation Q.713 [42] with the following restrictions: + +- 1) Intra-PLMN addressing + +For communication between entities within the same PLMN, the use of SCCP addressing is network specific, and method (a) and (b) are both applicable. + +- 2) Inter-PLMN addressing + +method (b) with the mandatory SSN is applicable only with the following format: + +- i) Called Party Address + +- SSN indicator = a standardised SSN shall be used. The SSN used shall be that specified for CAP in 3GPP TS 23.003 [5]; +- Point Code indicator = 0; +- Global title indicator = 0100 (Global title includes translation type, numbering plan, encoding scheme and nature of address indicator); +- Translation type = 0 (Not used); +- Routing indicator = 0 (Routing on global title); + +The format is also described in the table 14-2 below (for NP=1, NAI=4): + +**Table 14-2: Called Party Address format** + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|----------------------------------------------------------|-------------------------------------------------|----------------|---|-----------------------------------|---|----------|---------|----------| +| 0 | RI = 0 | GTI = 4 (0100) | | | | SSNI = 1 | PCI = 0 | Octet 1 | +| SSN = a value for CAP as specified in 3GPP TS 23.003 [5] | | | | | | | | Octet 2 | +| Translation type = 0 | | | | | | | | Octet 3 | +| Numbering plan = 1 (E.164) | | | | Encoding scheme = 1 or 2 | | | | Octet 4 | +| 0 | Nature of address indicator = 4 (International) | | | | | | | Octet 5 | +| Country code digit 2 (if present) | | | | Country code digit 1 | | | | Octet 6 | +| National Destination Code (NDC) Digit 1 | | | | Country code digit 3 (if present) | | | | Octet 7 | +| NDC digit 3 (if present) | | | | NDC digit 2 (if present) | | | | Octet 8 | +| NDC digit 5 (if present) | | | | NDC digit 4 (if present) | | | | Octet 9 | +| Equipment identification digit 2 | | | | Equipment identification digit 1 | | | | Octet 10 | +| ... | | | | ... | | | | ... | +| filler = 0 (if needed) | | | | Equipment identification digit m | | | | Octet n | + +Note Country code, National Destination Code, and SN(equipment id) are provided as example, so each digit may differ for each Inter-PLMN addressing case. (e.g., there is a case where only CC digit 1 shall be used). See ITU-T Recommendation Q.713 [42] for translation rules. + +ii) Calling Party Address + +- SSN indicator = a standardised SSN shall be used. The SSN used shall be that specified for CAP in 3GPP TS 23.003 [5]; +- Point code indicator = 0; +- Global title indicator = 0100 (Global title includes translation type, numbering plan, encoding scheme and nature of address indicator); +- Translation type = 0 (Not used); +- Routing indicator = 0 (Routeing on Global Title). + +The format is also described in the table 14-3 below (for NP=1, NAI=4): + +**Table 14-3: Calling Party Address format** + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|----------------------------------------------------------|-------------------------------------------------|---------|---|-----------------------------------|---|----------|---------|----------| +| 0 | RI = 0 | GTI = 4 | | | | SSNI = 1 | PCI = 0 | Octet 1 | +| SSN = a value for CAP as specified in 3GPP TS 23.003 [5] | | | | | | | | Octet 2 | +| Translation type = 0 | | | | | | | | Octet 3 | +| Numbering plan = 1 (E.164) | | | | Encoding scheme = 1 or 2 | | | | Octet 4 | +| 0 | Nature of address indicator = 4 (International) | | | | | | | Octet 5 | +| Country code digit 2 (if present) | | | | Country code digit 1 | | | | Octet 6 | +| National Destination Code (NDC) Digit 1 | | | | Country code digit 3 (if present) | | | | Octet 7 | +| NDC digit 3 (if present) | | | | NDC digit 2 (if present) | | | | Octet 8 | +| NDC digit 5 (if present) | | | | NDC digit 4 (if present) | | | | Octet 9 | +| Equipment identification digit 2 | | | | Equipment identification digit 1 | | | | Octet 10 | +| ... | | | | ... | | | | ... | +| Filler = 0 (if needed) | | | | Equipment identification digit m | | | | Octet n | + +Note Country code, National Destination Code, and SN(equipment id) are provided as example, so each digit may differ for each Inter-PLMN addressing case. (e.g., there is a case where only CC digit 1 shall be used). See ITU-T Recommendation Q.713 [42] for translation rules. + +When the SCCP of ANSI Signalling System No. 7 is used, the format and coding of address parameters carried by the SCCP for the purpose of signalling transfer shall comply with ANSI Recommendation T1.112-1996 [91] with the following restrictions: + +1) Intra-PLMN addressing + +For communication between entities within the same PLMN, the use of SCCP addressing is network specific. + +## 2) Inter-PLMN addressing + +### a) Called Party Address + +- SSN indicator = a standardised SSN shall be used. The SSN used shall be that specified for CAP in 3GPP TS 23.003 [5]; +- Point Code indicator = 0; +- Global title indicator = 0010 (Global title includes translation type); +- the Translation Type (TT) field shall be coded according to the content of the address information as follows: + - TT = 9 (decimal), if IMSI is included; or + - TT = 14 (decimal), if MSISDN is included; or + - TT = 10 (decimal), if a Network Element address is included. (If TT=10, then Number Portability is not applicable, if TT=14, then Number Portability is applicable) +- Routing indicator = 0 (Routeing on global title); + +### b) Calling Party Address + +- SSN indicator = a standardised SSN shall be used. The SSN used shall be that specified for CAP in 3GPP TS 23.003 [5]; +- Point code indicator = 0; +- Global title indicator = 0010 (Global title includes translation type); +- the Translation Type (TT) field shall be coded according to the content of the address information as follows: + - TT = 9 (decimal), if IMSI is included; or + - TT = 14 (decimal), if MSISDN is included; or + - TT = 10 (decimal), if a Network Element address is included. (If TT=10, then Number Portability is not applicable, if TT=14, then Number Portability is applicable) +- Routing indicator = 0 (Routeing on Global Title). + +### 14.2.2.1.3 Sequence control + +The application will specify whether SCCP protocol class 0 or 1 is required. Class 0 provides a basic connection-less service where the sequence of message delivery is not guaranteed. Class 1 connection-less service provides a guaranteed sequence delivery of messages (with the same called address) for a given stream of messages. Class 1 shall be requested by any application that can send more than 1 TC message to its peer (consecutive TR-CONTINUE) before receiving a response from its peer (TR-CONTINUE or TR-END). + +On receipt of a TC-RESULT-NL indication, the TC-USER shall request the transfer of a reject component using TC-U-REJECT request primitive, with the appropriate problem code (mistyped parameter). + +The return option may be used if requested by the application (Network Operator to determine). + +### 14.2.2.1.4 Return on error + +Return on Error mechanism may be required by the CAMEL applications such that the application is aware of messages that have not been delivered to the destination by the SCCP. The return option allows the return of the message that was not delivered due to routeing or segmentation/re-assembly failure back to the issuing user. This return option may be required in all segments of a long message or only in the first segment by the CAMEL applications. + +If the return option is invoked by the application and the message is not delivered, then the SCCP specifies the "return reason" as specified in ITU-T Recommendation Q.713 [42]. The N-NOTICE primitive is used to return the undelivered message to the originating user. + +#### 14.2.2.1.5 Segmentation / reassembly + +The application expects that since the SCCP can send up to 260 octets of user data (including the address information and TC-message) in a UDT message (248 octets in a XUDT message performing segmentation and congestion control), segmentation is available for long user messages. + +Also the SCCP is expected to perform the reassembly function on received segmented messages and deliver the reassembled message to the user. + +However, it should be noted that even though the theoretical maximum size of SCCP-user data and addresses that can be segmented by the SCCP is 3 968 octets, the SCCP-user would limit the length to about 2 560 octets to allow for the largest known addresses. Note that the application must also allow for the octets used for the TC-message in the 2 560 octets. + +The CAMEL application does not expect the SCCP to segment the long message into more than 16 segments. + +#### 14.2.2.1.6 Congestion control + +To help control of possible congestion that might occur in the lower layers the application may assign a value to indicate the importance of the message. The use of this parameter requires the use of SCCP (1997) ITU-T Recommendations. + +Also there exist other congestion control mechanisms as indicated below in SCCP Management. + +These congestion control methods are network operator option in the case of intra-PLMN network signalling, and shall not be used in the case of inter-PLMN network signalling. + +#### 14.2.2.2 SCCP connection oriented services + +The use by CAMEL applications for the Connection-oriented services is outside the scope of CAMEL. + +#### 14.2.2.3 SCCP management + +The subsystems used within the CAMEL application expect the SCCP to provide management procedures to maintain network performance by re-routeing in the event of failure of a subsystem, and in the case of network congestion by use of the congestion handling procedure. These procedures have appropriate interactions with the SCCP user as described in ITU-T Recommendations Q.713 [42] and ITU-T Recommendation Q.714 [43]. + +To achieve the above the SCCP is expected to perform the following procedures: + +- Signalling point status management (which include the signalling point prohibited, signalling point allowed, signalling point congested, and local MTP availability sub procedures). +- Subsystem status management (which include the subsystem prohibited, subsystem allowed, and subsystem status test sub procedures). +- Co-ordinated state change (a procedure which allows a duplicated subsystem to be withdrawn from service without affecting the performance of the network). + +These SCCP management procedures are network operator option in the case of intra-PLMN network signalling, and shall not be used in the case of inter-PLMN network signalling. + +## Annex A (normative): Mapping between CAP and ISUP + +### A.1 InitialDP operation + +Table A.1 + +| ISUP message
IAM (Note 1) | CAP Operation
InitialDP | +|-----------------------------------------------------------------------------------------------|---------------------------------------------------------------------| +| Called party number (note 6) | CalledPartyNumber | +| Calling party number | CallingPartyNumber | +| Calling party's category | CallingPartysCategory | +| Location number | LocationNumber | +| Original called number | OriginalCalledPartyID | +| User teleservice information (1 st priority) | HighLayerCompatibility | +| High layer compatibility IE contained in access transport (2 nd priority) (Note 2) | | +| High layer compatibility IE contained in access transport (Note 2) | HighLayerCompatibility2 | +| Low Layer compatibility IE contained in access transport (note 4) | LowLayerCompatibility | +| Low Layer compatibility IE contained in access transport (note 4) | LowLayerCompatibility2 | +| Generic number "additional calling party number" | AdditionalCallingPartyNumber | +| User service information prime (1 st priority) | BearerCapability | +| User service information (2 nd priority) (Note 3) | | +| User service information (Note 3) | BearerCapability2 | +| Redirecting number | RedirectingPartyID | +| Redirection information | RedirectionInformation | +| Call diversion treatment indicators | ServiceInteractionIndicatorsTwo.Call diversion treatment indicators | +| Conference treatment indicators | ServiceInteractionIndicatorsTwo.Conference treatment indicators | +| User-to-user indicators (Note 5) | UU-Data.UUIndicator | +| User-to-user information (Note 5) | UU-Data.UUI | + +NOTE 1: Optional parameters may be absent, i.e. they are only mapped only if these parameters are available at the DP. + +NOTE 2: If two high layer compatibility information elements are contained in the access transport parameter, then the second information element, carrying the preferred HLC, is mapped to the CAP highLayerCompatibility parameter, and the first information element, carrying the less preferred HLC, is mapped to the CAP highLayerCompatibility2 parameter. + +NOTE 3: If User service information prime and User service information are present, then one of the following two mapping rules shall be applied. The principles for the choice of mapping rule are specified in 3GPP TS 23.078 [7]. + +- One of User service information prime or User service information is mapped to Bearer Capability. +- User service information prime is mapped to BearerCapability and User service information is mapped to Bearer Capability2. + +NOTE 4: If two low layer compatibility information elements are contained in the access transport parameter, then the first information element, carrying the preferred LLC, is mapped to the CAP lowLayerCompatibility parameter, and the second information element, carrying the less preferred LLC, is mapped to the CAP lowLayerCompatibility2 parameter. + +NOTE 5: If present in ISUP IAM, user-to-user indicators and user-to-user information may optionally be mapped into the InitialDP Operation. + +NOTE 6: For trunk originating calls using overlap signalling, the called party number may contain partial address digits. + +## A.1.1 EventReportBCSM Operation + +Table A.1.1 + +| ISUP message
SAMs (Note 1) | CAP Operation
EventReportBCSM | +|-------------------------------|----------------------------------| +| Subsequent number | CalledPartyNumber | + +NOTE 1: For trunk originating calls using overlap signalling, subsequent address digits may be reported to the gsmSCF in EventReportBCSM, if requested by the gsmSCF with the 'Collect Information' operation. + +## A.2 ContinueWithArgument operation + +Table A.2 illustrates the mapping of parameters received in the ContinueWithArgument operation to parameters sent in the ISUP IAM to the succeeding exchange. All parameters which were received in the ISUP IAM and which are not replaced by parameters mapped from the ContinueWithArgument operation, shall be treated (and propagated to the succeeding exchange) according to the normal procedures. Propagation of ISUP parameters and mapping of parameters according to Table A.2 applies also for CWA when used to set up a new party leg in an existing call, except when the existing call is a NC call, in which case only mapping of parameters according to Table A.2 applies. The rule of copying ISUP parameters received from incoming leg to NP leg is valid also when the incoming leg no longer exists. + +For trunk originating calls using overlap signalling, the called party number in ISUP IAM may contain partial address digits. Any address digits received in SAMs, before the ISUP IAM is sent out, may also be included in the called party number parameter. Any address digits received in SAMs, after the ISUP IAM is sent out and before an ISUP ACM is received, shall be passed on to the succeeding exchange as received. + +On sending of the ISUP IAM the awaiting address complete timer is started. If the timer expires, then the call is released in both directions and an appropriate indication is returned to the calling subscriber. + +Table A.2 + +| CAP Operation ContinueWithArgument (Note 1) | ISUP message IAM | +|---------------------------------------------|-------------------------------------------| +| callingPartysCategory | Calling party's category | +| genericNumbers | Generic number (Note 2) | +| serviceInteractionIndicatorTwo | See Table A.4 | +| cug-Interlock | Closed user group interlock code | +| cug-OutgoingAccess | Optional forward call indicators (Note 3) | + +NOTE 1: Optional parameters may be absent, i.e. they are mapped only if received. + +NOTE 2: The set of generic numbers received in the genericNumbers parameter is mapped to the appropriate number of Generic Number parameters in the ISUP IAM. This shall be performed irrespective of the value of the screening indicator in the ISUP calling party number. + +NOTE 3: The cug-OutgoingAccess is mapped to the Closed User Group indicator which is carried in bits A & B of the Optional forward call indicators. + +## A.3 Connect operation + +On receipt of a Connect operation from the gsmSCF the called party number used for routing is derived from the destinationRoutingAddress (see Table A.3). If the triggering of the CAMEL service was made for a mobile terminating call in the GMSC or VMSC or for a mobile forwarded call, then an ISUP ACM shall be sent to the preceding exchange. The encoding of the backward call indicators in the ISUP ACM is specified in 3GPP TS 09.12 [1]. + +On receipt of a Connect operation from the gsmSCF for a trunk originating call, the called party number used for routing is derived from the destinationRoutingAddress (see Table A.3) and an ISUP ACM is sent to the preceding exchange (in an overlap signalling scenario this will prevent any further SAMs being sent by the preceding exchange). + +Table A.3 illustrates the mapping of parameters received in the Connect operation to parameters sent in the ISUP IAM to the succeeding exchange. Parameters which were received in the ISUP IAM and are not replaced by parameters of the Connect operation are treated according to the normal procedures. + +On sending of the ISUP IAM the awaiting address complete timer is started. If the timer expires, then the call is released in both directions and an appropriate indication is returned to the calling subscriber. + +**Table A.3** + +| CAP Operation
Connect (Note 1) | ISUP message
IAM | +|-------------------------------------------|-------------------------------------------| +| DestinationRoutingAddress | Called party number | +| OriginalCalledPartyID | Original called number | +| callingPartysCategory | Calling party's category | +| redirectingPartyID | Redirecting number | +| redirectionInformation | Redirection information | +| GenericNumbers | Generic number (Note 2) | +| ServiceInteractionIndicatorTwo | See Table A.4 | +| Cug-Interlock | Closed user group interlock code | +| cug-OutgoingAccess | Optional forward call indicators (Note 3) | + +NOTE 1: Optional parameters may be absent, i.e. they are mapped only if received. + +NOTE 2: The set of generic numbers received in the genericNumbers parameter is mapped to the appropriate number of Generic Number parameters in the ISUP IAM. This shall be performed irrespective of the value of the screening indicator in the ISUP calling party number. + +NOTE 3: The cug-OutgoingAccess is mapped to the Closed User Group indicator which is carried in bits A & B of the Optional forward call indicators. + +Table A.4 – Mapping of the CAP Connect and ContinueWithArgument operation serviceInteractionIndicatorsTwo to ISUP. + +Table A.4 + +| CAP
ServiceInteractionIndicators | ISUP parameter in | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | ACM/CPG/CON/ANM/REL | IAM | +| Call to be diverted indicator
– call diversion allowed
– call diversion not allowed | --- | Call diversion treatment indicators parameter
Call to be diverted indicator
– no indication
– call diversion allowed
– call diversion not allowed | +| Conference at DLE accept. ind.
– accept conference request
– reject conference request | --- | Conference treatment indicators parameter
Conference acceptance ind.
– no indication
– accept conference request
– reject conference request | +| Calling party restriction indicator
– no IN impact
– presentation restricted | --- | Calling party number address presentation restricted indicator
– no impact
– presentation restricted | +| Conference at OLE accept. ind.
– accept conference request
– reject conference request | ACM/CPG/CON/ANM: Conference treatment indicators parameter
Conference acceptance ind.
– no indication
– accept conference request
– reject conference request | --- | +| Call completion treatment indicator
– accept CCBS service request
– reject CCBS service request | REL, busy cause
Diagnostig field
– CCBS possible
– CCBS not possible | --- | +| Connected number treatment indicator
– no IN impact
– presentation restricted
– present called IN number
– present called IN number restricted | Note 3 | | + +## NOTE 3: + +If "no IN impact" was received for Connected number treatment indicator in the serviceInteractionIndicatorsTwo, then a connected number parameter and a generic number parameter "additional connected number" are passed on unchanged. + +If "presentation restricted" was received for Connected number treatment indicator in the serviceInteractionIndicatorsTwo, then: + +- If a connected number parameter has been received in the ISUP ANM or ISUP CON, then the address presentation restricted indicator is set to "presentation restricted". +- If a generic number parameter "additional connected number" has been received in the ISUP ANM or ISUP CON, then the address presentation restricted indicator is set to "presentation restricted". +- If a redirection number parameter has been received, then a redirection number restriction parameter is sent in the ISUP ANM with bits AB set to "presentation restricted". + +If "present called IN number" was received for Connected number treatment indicator in the serviceInteractionIndicatorsTwo, then: + +- If a connected number parameter has been received in the ISUP ANM or ISUP CON, then the connected number parameter is modified as follows: + +nature of address indicator and numbering plan indicator are encoded as received in the called party number of the ISUP IAM, + +address presentation restricted indicator: 00 (presentation allowed), + +address signals:as received in the called party number and possible subsequent number parameters, until the ISUP ACM was sent. + +- b) A generic number parameter "additional connected number" is deleted from the message, if applicable, +- c) A redirection number parameter is deleted from the relevant messages, if applicable. + +If "present called IN number restricted" was received for Connected number treatment indicator in the serviceInteractionIndicatorsTwo, then: + +- a) If a connected number parameter has been received in the ISUP ANM or ISUP CON, then the connected number parameter is modified as follows: + +nature of address indicator and numbering plan indicator are encoded as received in the called party number of the ISUP IAM, + +address presentation restricted indicator: 01 (presentation restricted), + +address signals:as received in the called party number and possible subsequent number parameters, until the ISUP ACM was sent. + +- b) A generic number parameter "additional connected number" is deleted from the message, if applicable, +- c) A redirection number parameter is deleted from the relevant messages, if applicable. + +--- + +## A.4 AssistRequestInstructions operation + +If an ISUP IAM is received at an assisting SSP containing an assisting gsmSSF or at an IP containing a gsmSRF, then an AssistRequestInstructions operation is sent to the gsmSCF. The correlationID parameter in the AssistRequestInstructions operation can contain: + +- a) the CorrelationID digits extracted from the ISUP IAM Called Party Number, +- b) the whole Called Party Number received in the ISUP IAM (CorrelationID digits extracted at gsmSCF), +- c) the contents of the ISUP IAM CorrelationID parameter. + +In the case where the gsmSCF and the assisting gsmSSF are both in the HPLMN and ISUP 97 is supported then any of these mechanisms may be used. + +In the case where the gsmSCF and the assisting gsmSSF are both in the HPLMN and ISUP 97 is not supported then mechanisms a) and b) may be used. + +In the case where the gsmSCF is in the HPLMN and the assisting gsmSSF is in the VPLMN then only mechanism b) may be used when an all-ISUP 97 signalling path cannot be guaranteed. Mechanism a) may be used if bilateral agreements on the format of the information transferred in the ISUP IAM Called Party Number are defined between the HPLMN and the VPLMN. + +In the case where the gsmSCF is in the HPLMN and the assisting gsmSSF is in the VPLMN then mechanism c) may only be used if an all-ISUP 97 signalling path can be guaranteed between the HPLMN and the VPLMN. + +--- + +## A.5 ConnectToResource operation + +On receipt of a ConnectToResource operation from the gsmSCF, the gsmSRF is connected to the call, to facilitate User Interactive dialogue with the user. + +If the User Interactive dialogue is to be performed at a forwarding MSC or at a terminating MSC (GMSC or VMSC), then an ISUP ACM shall be sent to the preceding exchange. The encoding of the backward call indicators in the ISUP ACM is specified in 3GPP TS 09.12 [1], with the Optional Backward Call Indicators indicating "in-band information or an appropriate pattern is now available". + +If the User Interactive dialogue is to be performed at a forwarding MSC or at a terminating MSC (GMSC or VMSC), then when the gsmSRF indicates through-connection and the ConnectToResource operation indicates that a bothway + +throughconnection is required, an ISUP ANM shall be sent to the preceding exchange if answer has not previously been sent. As a network operator/equipment vendor option an ISUP CPG message may be sent if ISUP ANM has already been sent. + +## A.6 EstablishTemporaryConnection operation + +On receipt of an EstablishTemporaryConnection operation from the gsmSCF then if the triggering of the CAMEL service was made for a mobile terminating call in the GMSC or VMSC or for a forwarded call, then an ISUP ACM shall be sent to the preceding exchange. The encoding of the backward call indicators in the ISUP ACM is specified in 3GPP TS 09.12 [1]. In addition, an ISUP IAM shall be sent to the succeeding exchange. + +Table A.5 illustrates the mapping of parameters received in the EstablishTemporaryConnection operation to parameters sent in the ISUP IAM to the succeeding exchange. On sending of the ISUP IAM the awaiting address complete timer is started. If the timer expires, then the call is released in both directions and an appropriate indication is returned to the calling subscriber. + +**Table A.5** + +| CAP Operation
EstablishTemporaryConnection | ISUP message
IAM | +|-----------------------------------------------|---------------------------------| +| AssistingSSPIRoutingAddress (note 1) | Called party number | +| CorrelationID | Correlation id (note 2) | +| ScfId | GsmSCF id (note 2) | +| OriginalCalledPartyID | Original called number (note 3) | +| CallingPartyNumber | Calling party number (note 3) | + +NOTE 1: The AssistingSSPIRoutingAddress parameter may also include a Hex B digit, in order to delineate the boundary between digits used for routing and digits forming part of the SCFiD and/or CorrelationID. + +NOTE 2: These optional parameters may be absent, i.e. they are mapped only if received. If they are received and cannot be mapped, then an error is sent to the gsmSCF as detailed in clause 11. + +NOTE 3: These optional parameters may be absent, i.e. they are mapped only if received. + +Except for the Called Party Number the remaining mandatory ISUP IAM parameters are set as follows: + +a) Nature of connection indicators + +Satellite indicator: set as in an Originating MSC, + +Continuity check indicator: set as in Originating MSC, + +Echo control device indicator: set as in Originating MSC + +b) Forward Call Indicators + +National/international call indicator: set as in Originating MSC, + +End-to-end method indicator: 00 (no end-to-end method available), + +Interworking indicator: 0 (no interworking encountered), + +End-to-end information indicator: 0 (no end-to-end information available), + +ISDN User Part indicator: 1 (ISDN User Part used all the way), + +ISDN User Part preference indicator: 00 (ISDN User Part preferred all the way), + +ISDN access indicator: 0 (originating access non-ISDN), + +SCCP method indicator: 00 (no indication) + +c) Calling Party's Category + +00001010 (ordinary subscriber) + +d) Transmission Medium Requirement + +00000011 (3.1 kHz audio) + +The ISUP IAM optional parameter Propagation Delay Counter is set as in an Originating MSC. + +## A.7 ReleaseCall operation + +Upon receipt of the ReleaseCall operation, the GMSC/gsmSSF (VMSC/gsmSSF) sends REL messages in both directions. The cause indicators parameter contains the releaseCallArg parameter of the ReleaseCall operation. + +## A.8 InitiateCallAttempt operation + +On receipt of an InitiateCallAttempt operation, the GMSC/gsmSSF or VMSC/gsmSSF prepares to set up a new call leg in an existing call configuration, or to set up a new call, to the destination defined by the DestinationRoutingAddress parameter. The GMSC/gsmSSF or VMSC/gsmSSF does not send the ISUP IAM until it has received a ContinueWithArgument operation, which contains additional information needed to populate the parameters of the ISUP IAM. + +For a new call leg in an existing call, except a NC call, all parameters which were received in the ISUP IAM and which were not replaced by parameters mapped from the InitiateCallAttempt or ContinueWithArgument operation, shall be treated (and propagated to the succeeding exchange) according to the normal procedures. The rule of copying ISUP parameters received from incoming leg to NP leg is valid also when the incoming leg no longer exists. + +Table A.6 illustrates the mapping of parameters received in the InitiateCallAttempt operation to parameters sent in the ISUP IAM to the succeeding exchange. + +**Table A.6** + +| CAP Operation
InitiateCallAttempt (Note 1) | ISUP message
IAM | +|-----------------------------------------------|---------------------------------------------------| +| DestinationRoutingAddress | Called party number | +| CallingPartyNumber | Calling party number | +| | Transmission medium requirement (Note 2) (Note 4) | +| | Access transport (Note 3) (Note 4) | + +NOTE 1: Optional parameters may be absent, i.e. they are mapped only if received. + +NOTE 2: The transmission medium requirement parameter field shall be set to "speech". + +NOTE 3: The "Bearer capability" and "High layer compatibility information" elements shall be filled in accordance with ETSI EN 300 403-1 [25] for speech call. + +NOTE 4: Only the minimum set of parameters indicating the fact that the call is a speech call is described here. + +--- + +## Annex B (normative): Mapping between CAP and MAP and mapping between CAP and SM-CP + +The Short Message signalling between the SMS-GMSC and the MSC or SGSN, for the transport of SM RP-DUs, is specified in 3GPP TS 29.002 [11]. The Short Message signalling between the MSC or SGSN and the MS, for the transport of SM RP-DUs, is specified in 3GPP TS 24.011 [10]. + +--- + +### B.1 Mapping between CAP and MAP + +#### B.1.1 MO-SMS + +##### B.1.1.1 ConnectSMS operation + +The Short Message TPDU is carried by a Short Message RPDU. The RPDU between the MSC or SGSN and the SMS-IWMSC is conveyed in the MAP MO-ForwardSM OPERATION. The MSC or SGSN shall obtain information from CAP OPERATION ConnectSMS and place it in MAP OPERATION MO-ForwardSM. + +**Table B.1** + +| CAP ConnectSMS | MAP MO-ForwardSM ARGUMENT | +|-----------------------------|------------------------------------------------| +| CallingPartysNumber | sm-RP-OA; CHOICE set to msisdn | +| DestinationSubscriberNumber | sm-RP-UI; TP-Destination-Address | +| SMSCAddress | sm-RP-DA; CHOICE set to serviceCentreAddressDA | + +NOTE The encoding of "SignalInfo" in MO-ForwardSM is specified in 3GPP TS 23.040 [6]. + +##### B.1.1.2 EventReportSMS operation + +The MSC or SGSN may receive error information from the SMS-IWMSC, via the MAP OPERATION MO-ForwardSM ERROR. The MSC or SGSN shall obtain the error information from MAP OPERATION MO-ForwardSM and place it in the CAP OPERATION EventReportSMS. + +**Table B.2** + +| CAP EventReportSMS | MAP MO-ForwardSM ERROR | +|--------------------|--------------------------------------------------------------------------------| +| MO_SMS Cause | SM-DeliveryFailure; SM-DeliveryFailureCause; SM-EnumeratedDeliveryFailureCause | + +## B.1.2 MT-SMS + +### B.1.2.1 InitialDPSMS operation (MT-SMS) + +The Short Message TPDU is carried by a Short Message RPDU. The RPDU between the SMS-GMSC and the MSC or SGSN is conveyed in the MAP MT-ForwardSM OPERATION ARGUMENT. The MSC or SGSN shall obtain information from the MT-ForwardSM MAP Message and place it in CAP InitialDPSMS. + +**Table B.3** + +| CAP InitialDPSMS | MAP MT-ForwardSM ARGUMENT | +|----------------------------|------------------------------------------------------------------------------------------| +| CallingPartysNumber | TP-Originating-Address from SMS-Deliver-TPDU. SMS-Deliver-TPDU is contained in sm-RP-UI. | +| SMSCAddress | sm-RP-OA | +| TPShortMessageSpecificInfo | First OCTET of the TPDU. The TPDU is contained in sm-RP-UI. | +| TPProtocolIdentifier | TP-Protocol-Identifier of the TPDU. The TPDU is contained in sm-RP-UI. | +| TPDataCodingScheme | TP-Data-Coding-Scheme of the TPDU. The TPDU is contained in sm-RP-UI. | +| TPValidityPeriod | TP-Validity-Period of the TPDU. The TPDU is contained in sm-RP-UI. | + +NOTE The encoding of "SignalInfo" in MT-ForwardSM is specified in 3GPP TS 23.040 [6]. + +### B.1.2.2 ReleaseSMS operation (MT-SMS) + +When the MSC or SGSN receives the CAP ReleaseSMS operation, it shall return a RP-ERROR RPDU to the SMS-GMSC. The RP-ERROR RPDU between the MSC or SGSN and the SMS-GMSC is conveyed in the MAP MT-ForwardSM OPERATION ERROR. + +**Table B.4** + +| CAP ReleaseSMS | MAP MT-ForwardSM ERROR | +|----------------|--------------------------------------------------------------------------------| +| RPCause | SM-DeliveryFailure; sm-DeliveryFailureCause; sm-EnumeratedDeliveryFailureCause | + +## B.2 Mapping between CAP and SM-CP + +### B.2.1 MO-SMS + +#### B.2.1.1 InitialDPSMS operation + +The Short Message TPDU is carried by a Short Message RPDU. The RPDU between the MS and the MSC or SGSN is conveyed in the RP-DATA Relay Message. The MSC or SGSN shall obtain information from the RP-DATA Message and place it in CAP InitialDP OPERATION. + +**Table B.5** + +| CAP InitialDPSMS ARGUMENT | SM-CP RP-DATA Message | +|-----------------------------|-----------------------------------------------| +| DestinationSubscriberNumber | RP-User Data; TPDU; TP-Destination-Address | +| SMSCAddress | RP-User Data; RP-Destination Address | +| TPShortMessageSpecificInfo | RP-User Data; TPDU; 1 st octet | +| TPProtocolIdentifier | RP-User Data; TPDU; TP-Protocol-Identifier | +| TPDataCodingScheme | RP-User Data; TPDU; TP-Data-Coding-Scheme | +| TPValidityPeriod | RP-User Data; TPDU; TP-Validity-Period-Format | + +## B.2.1.2 ReleaseSMS operation + +When the MSC or SGSN receives the CAP ReleaseSMS operation, it shall return a RP-ERROR RPDUs to the MS. The RP-ERROR RPDUs between the MSC or SGSN and the MS is conveyed in the RP-ERROR Relay Message. The MSC or SGSN shall obtain the RPCause from the CAP ReleaseSMS OPERATION and place it in the RP-ERROR Message. + +**Table B.6** + +| CAP ReleaseSMS ARGUMENT | SM-CP RP-ERROR Message | +|-------------------------|------------------------| +| RPCause | RP-Cause | + +## B.2.2 MT-SMS + +### B.2.2.1 ConnectSMS operation + +When the MSC or SGSN receives the ConnectSMS operation, it shall use the received information to replace data in the Short Message SMS-DELIVER TPDU. The SMS-DELIVER TPDU is carried in a RP-MT-DATA RPDUs. The RP-MT-DATA RPDUs between the MSC or SGSN and the MS is conveyed by the SM-CP CP-Data Message. + +**Table B.7** + +| CAP ConnectSMS | SM-CP RP-DATA Message | +|---------------------|--------------------------------------------| +| CallingPartysNumber | RP-User Data; TPDU; TP-Originating-Address | + +### B.2.2.2 EntReportSMS operation + +When the MSC or SGSN receives the RP-ERROR RPDUs from the MS, it shall send the RP-Cause to the gsmSCF. The RP-ERROR RPDUs between the MS and the MSC or SGSN is conveyed in the RP-ERROR Relay Message. The MSC or SGSN shall obtain the RPCause from the RP-ERROR Message and place it in CAP EventReportSMS. + +**Table B.8** + +| CAP EventReportSMS | SM-CP RP-ERROR Message | +|--------------------------|------------------------| +| EventSpecificInformation | RP-Cause | + +--- + +## Annex C (informative): Change history + +### Comments on CAMEL Phase 4 Rel-6 + +- For Release Rel-6, the version of module CAP-U-ABORT-Data is aligned with the other CAP modules; the module version is increased to version8(7). The increase of module version number does not affect the data type definitions contained within the module. +- CAP Operation "SpecialisedResourceReport" is spelled with a "z" (American spelling) in ASN.1. Therefore, TS 29.078 shall write in the text SpecializedResourceReport with a "z" consistently. +- For consistency purposes, module CAP-GPRS-ReferenceNumber is placed in a separate section. All CAP Modules (starting with BEGIN and ending with END) are specified in a separate section. +- The Rel-5 history overview ("How CAMEL Phase 4 Rel-5 Version 5.0.0 was created") is removed from the Rel-6 version of the present specification. + +| Change history | | | | | | | | +|----------------|-------|-----------|------|------|--------------------------------------------------------------------------------------------------|--------|--------| +| Date | TSG # | TSG Doc. | CR | Re v | Subject/Comment | Old | New | +| 2003-12 | CN#22 | NP-030527 | 332 | 1 | Collective CR for Rel-6 Enhanced Dialled Services | 5.6.0 | 6.0.0 | +| 2003-12 | CN#22 | NP-030528 | 343 | 1 | Change of position armed with criteria | 5.6.0 | 6.0.0 | +| 2004-03 | CN#23 | NP-040138 | 350 | 2 | Enhancement of Event Specific Information for DP 'Change of Position' | 6.0.0 | 6.1.0 | +| 2004-03 | CN#23 | NP-040095 | 352 | 1 | CAMEL4 SCUDIF notification during active call for prepay | 6.0.0 | 6.1.0 | +| 2004-03 | CN#23 | NP-040096 | 356 | 1 | LLC passes on the gsmSSF - gsmSCF interface | 6.0.0 | 6.1.0 | +| 2004-03 | CN#23 | NP-040136 | 360 | | Correction to description of Service Interaction Indicators Two parameter | 6.0.0 | 6.1.0 | +| 2004-03 | CN#23 | NP-040136 | 361 | | Correction to temporary connection establishment | 6.0.0 | 6.1.0 | +| 2004-03 | CN#23 | NP-040137 | 362 | | Correction to SplitLeg and MoveLeg preconditions | 6.0.0 | 6.1.0 | +| 2004-03 | CN#23 | NP-040138 | 363 | | Correction to Disconnect Leg preconditions | 6.0.0 | 6.1.0 | +| 2004-03 | CN#23 | NP-040138 | 364 | | Correction to GPRS protocol definition | 6.0.0 | 6.1.0 | +| 2004-06 | CN#24 | NP-040249 | 366 | 1 | Enhancement to User Interaction | 6.1.0 | 6.2.0 | +| 2004-06 | CN#24 | NP-040249 | 367 | 1 | Adding missing ROS Object Identifier | 6.1.0 | 6.2.0 | +| 2004-06 | CN#24 | NP-040207 | 370 | 1 | Mapping between ICA and IAM | 6.1.0 | 6.2.0 | +| 2004-06 | CN#24 | NP-040207 | 371 | | Correction to Tssf timer | 6.1.0 | 6.2.0 | +| 2004-06 | CN#24 | NP-040207 | 372 | | Correction to ERB pre-condition for gsmSSF FSM state | 6.1.0 | 6.2.0 | +| 2004-06 | CN#24 | NP-040207 | 374 | 2 | Correction to Move Leg pre-condition | 6.1.0 | 6.2.0 | +| 2004-06 | CN#24 | NP-040249 | 375 | | Correction to First Digit Timer for Prompt&Collect | 6.1.0 | 6.2.0 | +| 2004-09 | CN#25 | NP-040405 | 380 | | Support of User-to-User Information (UUI) in CAMEL InitialDP operation | 6.2.0 | 6.3.0 | +| 2004-09 | CN#25 | NP-040397 | 382 | 2 | Clarification on the handling of operation invocation when LinkedID is missing although expected | 6.2.0 | 6.3.0 | +| 2004-09 | CN#25 | NP-040406 | 383 | | Correction to usage of ACM for CAP ETC and CAP CTR | 6.2.0 | 6.3.0 | +| 2004-09 | CN#25 | NP-040406 | 384 | | Correction to Cancel procedure description | 6.2.0 | 6.3.0 | +| 2004-09 | CN#25 | NP-040406 | 385 | | Correction to SplitLeg ASN.1 description | 6.2.0 | 6.3.0 | +| 2004-09 | CN#25 | NP-040406 | 386 | | Correction to Apply Charging Report procedure | 6.2.0 | 6.3.0 | +| 2004-09 | CN#25 | NP-040406 | 387 | | Correction to Assist Request Instructions procedure | 6.2.0 | 6.3.0 | +| 2004-09 | CN#25 | NP-040406 | 388 | | Correction to Call Information Request and Report | 6.2.0 | 6.3.0 | +| 2004-09 | CN#25 | NP-040406 | 389 | | Correction to Tssf timer setting for SMS control | 6.2.0 | 6.3.0 | +| 2004-12 | CN#26 | NP-040544 | 390 | | Correction of wrong TS numbers in references | 6.3.0 | 6.4.0 | +| 2005-06 | CT#28 | CP-050103 | 392 | 1 | Additions to CAP for trunk originated services | 6.4.0 | 7.0.0 | +| 2005-09 | CT#29 | CP-050312 | 393 | 1 | Additions and clarifications to CAP for trunk originated services | 7.0.0 | 7.1.0 | +| 2005-12 | CT#30 | CP-050626 | 0396 | 1 | Support of an Operation Arg and Errors for CollectInformation | 7.1.0 | 7.2.0 | +| 2006-06 | CT#32 | CP-060311 | 0397 | 1 | Addition of information related to service change | 7.2.0 | 7.3.0 | +| 2007-09 | CT#37 | CP-070540 | 0399 | 2 | AC/ACR Handling | 7.3.0 | 7.4.0 | +| 2007-09 | CT#37 | CP-070540 | 0400 | | QoS Extension | 7.3.0 | 7.4.0 | +| 2008-12 | CT#42 | | | | Upgraded unchanged from Rel-7 | 7.4.0 | 8.0.0 | +| 2009-09 | CT#45 | CP-090523 | 0407 | | Correction to InvokeID syntax definition | 8.0.0 | 8.1.0 | +| 2009-12 | CT#46 | | | | Upgraded unchanged from Rel-8 | 8.1.0 | 9.0.0 | +| 2010-03 | CT#47 | CP-100029 | 0409 | 1 | User CSG Information for CAMEL | 9.0.0 | 9.1.0 | +| 2010-04 | | | | | Figures 4-1/4, 4-1/6 and 4-1/8 were not visible. Release corrected on cover page. | 9.1.0 | 9.1.1 | +| 2010-06 | CT#48 | CP-100261 | 0413 | | ASN.1 Module Version Update | 9.1.1 | 9.2.0 | +| 2011-03 | CT#51 | | | | Update to Rel-10 version (MCC) | 9.2.0 | 10.0.0 | +| 2011-09 | CT#53 | CP-110733 | 0414 | 2 | Extension parameter for Release Call | 10.0.0 | 11.0.0 | +| 2011-12 | CT#53 | CP-110813 | 0415 | 2 | Extension of ScfID parameter length | 11.0.0 | 11.1.0 | +| 2012-12 | CT#58 | CP-120749 | 0416 | 1 | CWA Correction and CWA and ICA Clarification | 11.1.0 | 11.2.0 | \ No newline at end of file diff --git a/marked/Rel-11/29_series/29079/0931f3e098bd4539041de11c50cec2d2_img.jpg b/marked/Rel-11/29_series/29079/0931f3e098bd4539041de11c50cec2d2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e19141886ec95d3d8b3da4c4f5ac4d802061166f --- /dev/null +++ b/marked/Rel-11/29_series/29079/0931f3e098bd4539041de11c50cec2d2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f9b1ef7ccf1bea39583a72c2757ea9c1d599475392d2e0409efd568ae157d0d3 +size 161605 diff --git a/marked/Rel-11/29_series/29079/2a476a0b3dbc3429436246db4784ff9f_img.jpg b/marked/Rel-11/29_series/29079/2a476a0b3dbc3429436246db4784ff9f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..73195ac1456c2da037d2e1d6ea71a685cbd43ef8 --- /dev/null +++ b/marked/Rel-11/29_series/29079/2a476a0b3dbc3429436246db4784ff9f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9f0278376246c93024cbd9eafcbf1b45344d047f949588fda047e7ecdae7e4e9 +size 108656 diff --git a/marked/Rel-11/29_series/29079/4af57aad638888edf2062306f8a54a6c_img.jpg b/marked/Rel-11/29_series/29079/4af57aad638888edf2062306f8a54a6c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5241e95d59f00f1dda77b1664c8f2d5364448976 --- /dev/null +++ b/marked/Rel-11/29_series/29079/4af57aad638888edf2062306f8a54a6c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e7d0e3bffa66c8d3a31007ffd854fbe9f940d15851f256aabf9957b770d29872 +size 78821 diff --git a/marked/Rel-11/29_series/29079/56a5265d174ce056c1dbe5e7a60839fc_img.jpg b/marked/Rel-11/29_series/29079/56a5265d174ce056c1dbe5e7a60839fc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..82f4a97ff4d81e42aca56eab95e26809a7fb1703 --- /dev/null +++ b/marked/Rel-11/29_series/29079/56a5265d174ce056c1dbe5e7a60839fc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c644bb0ff9492116b971f77161d50f07b99877c6bf8dc0a94715176fc069e59e +size 226527 diff --git a/marked/Rel-11/29_series/29079/68a5a1a1a761c652b4b4c56da7cf9914_img.jpg b/marked/Rel-11/29_series/29079/68a5a1a1a761c652b4b4c56da7cf9914_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2a53f10aceebc1f7709ab8900b45d11be798c4f7 --- /dev/null +++ b/marked/Rel-11/29_series/29079/68a5a1a1a761c652b4b4c56da7cf9914_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8b0a017e492f05e998f55e94893c6f73c1479818aedf6aae4331504de32560cd +size 80898 diff --git a/marked/Rel-11/29_series/29079/dd5771673aececa53d42ece89218299d_img.jpg b/marked/Rel-11/29_series/29079/dd5771673aececa53d42ece89218299d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ceca180e76bbe61ea437ccde7e406139aa415b66 --- /dev/null +++ b/marked/Rel-11/29_series/29079/dd5771673aececa53d42ece89218299d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:870636269d5033ad37a5d5a5e0add42948ac82103c1d95834222df22c0241c53 +size 221956 diff --git a/marked/Rel-11/29_series/29079/e05122559f56af5699789b7118d8fe87_img.jpg b/marked/Rel-11/29_series/29079/e05122559f56af5699789b7118d8fe87_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c24afce63f311b187713faf72fb35e55e9a12348 --- /dev/null +++ b/marked/Rel-11/29_series/29079/e05122559f56af5699789b7118d8fe87_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d7d82eb46c21c94a197ca193c3bc2ceda2ad46d174cad5c736c900fe24fa1068 +size 243043 diff --git a/marked/Rel-11/29_series/29079/e94cbc0895c6914a2bb53f150ab7495e_img.jpg b/marked/Rel-11/29_series/29079/e94cbc0895c6914a2bb53f150ab7495e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e3fe83b58658bd1507f35897a0ca1ea5e0e390aa --- /dev/null +++ b/marked/Rel-11/29_series/29079/e94cbc0895c6914a2bb53f150ab7495e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0129d6d49a8bb0e379c4f3acfa82f3f8bd53731939d6d3b18a87d6b3c7613d39 +size 80317 diff --git a/marked/Rel-11/29_series/29079/raw.md b/marked/Rel-11/29_series/29079/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..b178535ee7176c8f834967c527ce8613ddae4590 --- /dev/null +++ b/marked/Rel-11/29_series/29079/raw.md @@ -0,0 +1,4137 @@ + + + + +Error! No +text of + +Error! No text of specified style in +document. + +# Contents + +| | | +|------------------------------------------------------------------------------------------------------------------------|----| +| Foreword ..... | 5 | +| 1 Scope..... | 6 | +| 2 References..... | 6 | +| 3 Definitions, symbols and abbreviations..... | 7 | +| 3.1 Definitions..... | 7 | +| 3.2 Symbols..... | 8 | +| 3.3 Abbreviations ..... | 8 | +| 4 General..... | 8 | +| 5 Common SDP Procedures..... | 9 | +| 5.1 General ..... | 9 | +| 5.2 Encapsulation of previous SDP information..... | 9 | +| 5.2.1 Media level information ..... | 9 | +| 5.2.2 Session level information ..... | 9 | +| 5.3 Determination of codec related SDP information associated to a previous realm instance..... | 10 | +| 5.4 Modifying codec related information..... | 11 | +| 5.4.1 Modifying the format list..... | 11 | +| 5.4.2 Modifying preferred configurations ..... | 11 | +| 5.5 Additional handling for SDP answer with actual configuration ..... | 12 | +| 5.6 Procedures specific to OMR attributes..... | 12 | +| 5.6.1 General ..... | 12 | +| 5.6.2 instance-number ..... | 12 | +| 5.6.3 Session and media checksum calculation..... | 13 | +| 5.7 Roaming architecture for voice over IMS with local breakout..... | 13 | +| 6 IMS-ALG procedures ..... | 13 | +| 6.1 IMS-ALG handling of initial SDP offer ..... | 13 | +| 6.1.1 General ..... | 13 | +| 6.1.2 Validating the received SDP offer..... | 13 | +| 6.1.3 Deciding whether to allocate a primary local MR and if any previous MR can be bypassed..... | 14 | +| 6.1.4 Bypassing previous MRs..... | 15 | +| 6.1.5 Bypassing no previous MRs..... | 16 | +| 6.1.6 Allocating a primary local MR..... | 16 | +| 6.1.7 Allocating no primary local MR..... | 17 | +| 6.1.8 Allocating secondary local MRs ..... | 17 | +| 6.1.9 Forwarding SDP offer ..... | 18 | +| 6.2 IMS-ALG handling of initial SDP answer..... | 18 | +| 6.2.1 General ..... | 18 | +| 6.2.2 IMS-ALG bypasses an allocated transcoding MR ..... | 18 | +| 6.2.3 IMS-ALG allocates a local transcoding MR when performing proactive transcoding without resource reservation..... | 19 | +| 6.2.4 IMS-ALG determines steps required to complete the handling of the SDP answer ..... | 19 | +| 6.2.5 Receiving an unspecified connection address and a visited-realm instance ..... | 20 | +| 6.2.6 Receiving an unspecified connection address and a secondary-realm instance..... | 20 | +| 6.2.7 Other handling when no primary local MR allocated ..... | 21 | +| 6.2.8 Retaining a primary or secondary local MR..... | 21 | +| 6.2.9 Forwarding the SDP answer..... | 22 | +| 6.3 IMS-ALG OMR media resource operations ..... | 22 | +| 6.3.1 General ..... | 22 | +| 6.3.2 IMS-ALG operations..... | 23 | +| 6.4 Handling of connected IP realms ..... | 23 | +| 7 UA Procedures ..... | 24 | +| 7.1 UA sending an initial SDP offer ..... | 24 | +| 7.2 UA receiving an initial SDP offer ..... | 24 | +| 7.2.1 General ..... | 24 | +| 7.2.2 Validating the incoming SDP offer ..... | 24 | +| 7.2.3 UA may choose an alternate realm instance to bypass an upstream MR..... | 24 | + +7.3 UA receiving an initial SDP answer ..... 25 + +7.3.1 General ..... 25 + +7.3.2 Receiving SDP answer with an unspecified connection address ..... 25 + +7.3.3 Receiving SDP answer with a valid connection address..... 25 + +7.4 UA OMR media resource operations..... 26 + +7.4.1 General ..... 26 + +7.4.2 UA operations..... 26 + +7.5 Handling of connected IP realms ..... 26 + +8 Subsequent SDP offer/answer transactions..... 26 + +8.1 General ..... 26 + +8.2 IMS-ALG and UA subsequent SDP offer procedures ..... 27 + +8.3 IMS-ALG and UA subsequent SDP answer procedures..... 27 + +8.4 Handling media resources during a subsequent SDP offer/answer transaction ..... 28 + +**Annex A (informative): Signalling flows..... 29** + +A.1 Scope of signalling flows..... 29 + +A.2 Introduction..... 29 + +A.3 Media bypassing all IMS-ALGs ..... 30 + +A.3.1 General ..... 30 + +A.3.2 Message flow..... 30 + +A.4 IMS-ALG allocates a local transcoding MR when performing proactive transcoding without +resource reservation ..... 42 + +A.4.1 General ..... 42 + +A.4.2 Message flow..... 42 + +A.5 IMS-ALG bypasses an allocated transcoding MR..... 61 + +A.5.1 General ..... 61 + +A.5.2 Message flow..... 62 + +A.6 Loopback routeing via an intermediate network..... 75 + +A.6.1 General ..... 75 + +A.6.2 Message flow..... 76 + +Annex B (informative): Change history..... 90 + +# --- Foreword + +This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +# --- 1 Scope + +The present document defines optional Optimal Media Routeing (OMR) procedures that can be applied by entities in the IP Multimedia Subsystem (IMS) that control media resources and are capable of manipulating the Session Description Protocol (SDP) as defined by IETF RFC 4566 [6]. + +The OMR procedures in the present specification relate to the handling of OMR-specific SDP attributes that are documented in TS 24.229 [4]. The OMR procedures use SDP offer/answer related procedures in IETF RFC 3264 [5] and in TS 24.229 [4] in a backward-compatible manner. + +The 3GPP network architecture, including the configuration and network entities of the IMS, is defined in TS 23.002 [2]. The Stage 2 of the IMS is defined TS 23.228 [3]. Annex Q of TS 23.228 [3] documents the architecture and call flows for OMR. + +The OMR procedures in this document are applicable to the following IMS entities that perform as an IMS-ALG or UA according to TS 24.229 [4] and that control media resources: + +- an IBCF acting as an IMS-ALG; +- a P-CSCF acting as IMS-ALG; +- an AS acting as B2BUA and adapting IMS-ALG procedures to control an MRF; +- an AS acting as B2BUA and adapting UA procedures to control an MRF; and +- an MGCF acting as UA. + +NOTE 1: An AS acting as B2BUA to perform application functions such as conferencing or announcements will normally perform separate originating and terminating UA procedures, treating the media resource as an endpoint. An AS acting as B2BUA offering transcoding options will typically follow IMS-ALG procedures. + +NOTE 2: The controlled media resource can be a TrGW, IMS-AGW, MRF, or a media function of the entity performing OMR. + +The OMR procedures are not applicable for an UE. + +# --- 2 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. +- For a specific reference, subsequent revisions do not apply. +- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. + +- [1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications". +- [2] 3GPP TS 23.002: "Network architecture". +- [3] 3GPP TS 23.228: "IP multimedia subsystem; Stage 2". +- [4] 3GPP TS 24.229: "IP multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3" +- [5] IETF RFC 3264: "An Offer/Answer Model with Session Description Protocol (SDP)". +- [6] IETF RFC 4566: "SDP: Session Description Protocol". + +- [7] IETF RFC 2617: "HTTP Authentication: Basic and Digest Access Authentication". +- [8] IETF RFC 3605: "Real Time Control Protocol (RTCP) attribute in Session Description Protocol (SDP)". +- [9] 3GPP TS 29.238: "Interconnection Border Control Functions (IBCF) – Transition Gateway (TrGW) interface, Ix Interface; Stage 3". +- [10] 3GPP TS 29.334: "IMS Application Level Gateway (IMS-ALG) – IMS Access Gateway (IMS-AGW); Iq Interface; Stage 3". +- [11] IETF RFC 4240: "Basic Network Media Services with SIP". +- [12] IETF RFC 3260: "Media Control Channel Framework". +- [13] IETF RFC 6505: "A Mixer Control Package for the media Control Channel Framework". +- [14] 3GPP TS 29.332: "Media Gateway Control Function (MGCF) – IM Media Gateway Mn Interface". +- [15] 3GPP TS 23.334: "IP Multimedia Subsystem (IMS) Application Level Gateway (IMS-ALG) – IMS Access Gateway (IMS-AGW) interface: Procedures descriptions". +- [16] 3GPP TS 29.162: "Interworking between the IM CN subsystem and IP networks". +- [17] 3GPP TS 29.163: "Interworking between the IP Multimedia (IM) Core Network (CN) subsystem and Circuit Switched (CS) networks". +- [18] IETF RFC 5552: "SIP Interface to VoiceXML Media Services". +- [19] IETF RFC 4117: "Transcoding Services Invocation in the Session Initiation Protocol (SIP) Using Third Party Call Control (3pcc)". +- [20] IETF RFC 5939: "Session Description Protocol (SDP) Capability Negotiation". +- [21] IETF RFC 2234: "Augmented BNF for Syntax Specification: ABNF". + +# --- 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]. + +**Codec:** A media configuration for a media line in SDP that is specified by one or more formats in the format list of the m-line, by one or more preferred configurations (pcfg) associated with the media line, or by a combination of both. + +**Codec Change:** Any modification to the media configurations for the media line in the format list or the list of preferred configurations. + +**Codec List:** Either the format list of the m-line, or a combination of all the preferred configurations and the format list for the media line. + +**Connected IP realm:** Compared to a reference IP realm, a connected IP realm is one identified with a different unique name where all IP endpoints in the two IP realms are mutually reachable (accessible) by means of IP routing without address translation. Interconnection between the IP realms may be via direct link, via IP tunnel through other networks, via IP routing through intermediate networks, or via any other method of internetworking as long as their IP endpoints are mutually reachable. The property of connectedness is symmetric but not necessarily transitive. In particular, two IP realms connected to a reference IP realm are not necessarily themselves connected. + +**Incoming termination:** The termination at an MR in the direction from where an incoming SDP offer is being received at the IMS-ALG that is controlling the MR. + +**IP realm:** A collection of IP endpoints identified by a unique name, where all IP endpoints are mutually reachable by means of IP routing without address translation. + +**Media resource:** An IMS Network entity that provides resources to process media streams and is controlled by an entity applying OMR procedures. A TrGW, BGW, MRF, or a function internal to the entity performing OMR can be a media resource. + +**Loopback routeing:** A method of routeing a SIP request back to the visited network for local breakout according to the Roaming Architecture for Voice over IMS with Local Breakout as specified in TS 24.229 [4]. + +**Outgoing termination:** The termination at an MR in the direction towards where an outgoing SDP offer is being sent at the IMS-ALG that is controlling the MR. + +**Second SDP offer/answer:** An SDP offer/answer transaction initiated by any of the involved IMS-ALGs during session establishment towards the initial SDP answerer upon reception of the initial SDP answer and MR resources are required (e.g. when an intermediate IMS-ALG performs proactive transcoding without resource reservation) or not required (e.g. when MR resources are reserved for the purpose of transcoding and transcoding is not required). The second SDP offer is not an end-to-end negotiation and is handled as the initial SDP offer. + +**Subsequent SDP offer/answer:** An end-to-end SDP offer/answer transaction initiated after a completed initial or second SDP offer/answer transaction. The subsequent SDP offer contains no OMR specific attributes. + +## 3.2 Symbols + +For the purposes of the present document, the following symbols apply: + +| | | +|----|---------------------------------------------------------------| +| Ix | Reference Point between IBCF and TrGW | +| Iq | Reference Point between the P-CSCF and the IMS Access Gateway | + +## 3.3 Abbreviations + +For the purposes of the present document, the abbreviations given in TR 21.905 [1], in TS 23.228 [3] 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] or in TS 23.228 [3]. + +| | | +|-------|----------------------------------------| +| ALG | Application Level Gateway | +| B2BUA | Back-to-Back User Agent | +| IC | Interconnection | +| ICE | Interactive Connectivity Establishment | +| MR | Media Resource | +| OMR | Optimal Media Routeing | +| TRF | Transit and Roaming Function | +| UA | User Agent | + +# --- 4 General + +The procedures in clause 5, clause 6, clause 7 and clause 8 shall apply separately to each media line with non-zero port value in each SDP message, and shall apply separately to each SDP offer/answer transaction. In the presence of forking of a SIP INVITE request that includes an SDP offer, the OMR procedures for handling of the SDP offer apply once for all forked dialogs, and the OMR procedures for handling of the corresponding SDP answer apply independently to each dialog. Entities supporting OMR use the OMR-specific SDP extension attributes defined in TS 24.229 [4]. + +OMR builds on the ALG NAT traversal model and is not consistent with ICE. + +OMR does not modify the SIP signalling route path and usually does not modify the flow of SIP messages except in some cases when transcoding options are offered. + +# --- 5 Common SDP Procedures + +## 5.1 General + +The IMS-ALG or UA using the OMR procedures in clause 6 or clause 7, respectively, shall additionally use the procedures in this subclause when manipulating SDP. + +## 5.2 Encapsulation of previous SDP information + +### 5.2.1 Media level information + +If an IMS-ALG forwards an SDP offer and for a given media line: + +- adds or removes offered format(s); +- modifies the transport protocol; +- adds or removes other corresponding media level SDP attribute(s) than "visited-realm", "secondary-realm", "omr-codecs", "omr-m-att", "omr-s-att", "omr-m-bw", "omr-s-bw", "omr-s-cksum" or "omr-m-cksum" attributes; +- modifies the value of other corresponding media level SDP attribute(s) than "visited-realm", "secondary-realm", "omr-codecs", "omr-m-att", "omr-s-att", "omr-m-bw", "omr-s-bw", "omr-s-cksum" or "omr-m-cksum" attributes; +- adds or removes corresponding media level SDP bandwidth line(s); or +- modifies the value of corresponding media level SDP bandwidth line(s), + +then the IMS-ALG shall apply the procedures below to encapsulate all media level information of the corresponding media line. + +The IMS ALG shall encapsulate the received transport protocol and format list of the corresponding media line within an "omr-codecs" attribute and add this attribute as a media level attribute for the corresponding media line. + +The IMS ALG shall encapsulate each received attribute of the corresponding media line within an "omr-m-att" attribute and add this attribute as a media level attribute for the corresponding media line. + +The IMS ALG shall encapsulate each received bandwidth line of the corresponding media line within an "omr-m-bw" attribute and add this attribute as media level attribute for the corresponding media line. + +If the IMS-ALG received any visited-realm instances in the SDP offer, the IMS-ALG shall supply the instance number one above the highest instance number in the received SDP offer as instance number within the "omr-codecs", the "omr-m-att" and "omr-m-bw" attribute(s). Otherwise the IMS-ALG shall supply the instance number 2. + +### 5.2.2 Session level information + +If an IMS-ALG forwards an SDP offer and: + +- encapsulated any media level information according to the conditions in subclause 5.2.1; +- adds or removes any session level SDP attribute(s); +- modifies the value of any session level SDP attribute(s); +- adds or removes session level SDP bandwidth line(s); or +- modifies the value of session level SDP bandwidth line(s), + +then the IMS-ALG shall apply the procedures below to encapsulate all session level information. + +The IMS ALG shall encapsulate each received session-level attribute within an "omr-s-att" attribute and add this attribute as a media level attribute for every media line. + +The IMS ALG shall encapsulate each received session-level bandwidth line within an "omr-s-bw" attribute and add this attribute as a media level attribute for every media line. + +If the IMS-ALG received any visited-realm instances in the SDP offer, the IMS-ALG shall supply the instance number one above the highest instance number in the received SDP offer as instance number within the "omr-s-att" and "omr-s-bw" attribute(s). Otherwise the IMS-ALG shall supply the instance number 2. + +NOTE 1: The instance number 1 is reserved for the incoming SDP offer when it contains no visited-realm instance. + +NOTE 2: The remaining SDP session level attributes (e.g., the "o" line) are not modified by the OMR procedures. + +## 5.3 Determination of codec related SDP information associated to a previous realm instance + +When deciding to bypass some previous MR, an IMS-ALG needs to determine the SDP information which is applicable together with the visited-realm instance or secondary-realm instance that the IMS selects for the bypass (see subclause 6.1). The IMS-ALG will include that SDP information in a forwarded SDP offer or perform additional modifications on top of it, e.g., to offer transcoding at its own MR. + +To determine the codec related SDP information associated to that previous realm instance for the media line, the IMS-ALG shall use the procedures below. + +- 1) If any "omr-codecs", "omr-m-att", or "omr-m-bw" attributes with a higher instance number than the previous visited-realm instance or secondary-realm instance exist for a media line, the IMS-ALG shall consider the information within the set of attributes with the lowest instance number among those as follows: + - the IMS-ALG shall replace the transport format and media formats in the media line with the transport format and media formats from the "omr-codecs" attribute with this instance number; + - the IMS-ALG shall retain all the "visited-realm", "secondary-realm", "omr-s-cksum", "omr-m-cksum", "omr-codecs", "omr-m-att", "omr-s-att", "omr-m-bw" and "omr-s-bw" attributes for the media line and replace all other SDP a-line(s) for the media line with the attributes extracted from the "omr-m-att" attribute(s) with this instance number; and + +NOTE 1: This procedure only describes update to codec related SDP information. Clauses 6 and 7 describe the corresponding modifications to the OMR related attributes. + +- the IMS-ALG shall replace the SDP b-line(s) for the media line with the b-line(s) extracted from the "omr-m-bw" attributes with this instance number. + +Otherwise, the IMS-ALG shall use the SDP a-lines, b-lines, transport format and list of media formats of the corresponding media line. + +- 2) If any "omr-s-att" or "omr-s-bw" attributes with a higher instance number than the previous visited-realm instance or secondary-realm instance exist, the IMS-ALG shall consider the information within the set of attributes with the lowest instance number among those as follows: + - If the same attributes are provided for each media line, the IMS ALG shall replace all session-level SDP a-lines and b-lines with the encapsulated attributes and bandwidth within the "omr-s-att" attributes and "omr-s-bw" attributes of one media line as session level attributes and bandwidth, and may apply attribute or bandwidth modifier specific logic to verify and possibly adjust the session-level information from "omr-s-att" and "omr-s-bw" attributes and media level information determined as described above; + +NOTE 2: Verification helps in the possible event of splitting media lines by intermediate entities. + +- otherwise the IMS-ALG shall apply attribute or bandwidth modifier specific logic to derive appropriate session-level information from "omr-s-att" and "omr-s-bw" attributes and media level information determined as described above, or delete all those encapsulated attributes and all session-level SDP a-lines and b-lines. + +NOTE 3: In the possible event of merging of media lines by intermediate entities, there may be inconsistencies in the encapsulated session level a-lines and/or b-lines. + +- 3) Otherwise, the IMS-ALG shall use the session-level SDP a-lines and b-lines. + +For an SDP offer with several media lines, an IMS-ALG applies the OMR algorithm separately for each media line and can select different optimised paths. In such a case, the session-level attributes and bandwidth information determined by the above algorithm can differ for different optimised paths, depending on the selected visited-realm instance or secondary-realm instance for each media line. The IMS-ALG may then apply attribute or bandwidth modifier specific logic to determine the appropriate session-level information or discard conflicting information. An IMS-ALG may also apply a policy not to choose different optimised paths for different media to avoid such conflicts. + +NOTE 4: Upon receiving an SDP offer and validating the OMR attributes in the SDP offer, but before making any codec changes to the SDP offer, the IMS-ALG supporting OMR can delete any unsupported attributes from the SDP offer, e.g., attributes associated with capability negotiation. The IMS-ALG supporting OMR can also delete any ignored attributes, e.g., due to lack of support of a required extension to capability negotiation, as determined by the creq attribute defined in IETF RFC 5939 [20]. + +## 5.4 Modifying codec related information + +### 5.4.1 Modifying the format list + +When forwarding an SDP offer, the IMS-ALG should not make changes to the attributes associated with a format remaining in the format list of the m-line that require the allocation of an MR to translate the media payload between the format described by the received SDP offer and the format described by the forwarded SDP offer. + +NOTE 1: Examples include changing between AMR octet-aligned and bandwidth-efficient modes, and incompatible AMR mode-sets. + +To add a codec to the format list of the m-line in the SDP offer to be forwarded, the IMS-ALG shall either: + +- add a media format to the format list on the media line that is different from any format in the "omr-codecs" attributes for the media line, along with any necessary media attributes, or +- re-insert a format from an "omr-codecs" attribute for the media line that is not in the current format list, along with the corresponding attributes for the format with the same instance number in "omr-m-att" attributes. + +NOTE 2: This procedure avoids the potential need to retain a media resource to perform format mapping when performing proactive transcoding, if the bypass decision is based on the SDP answer. + +### 5.4.2 Modifying preferred configurations + +When forwarding an SDP offer, the IMS-ALG supporting SDP capability negotiation shall only make a change to a preferred configuration in the incoming SDP offer without changing the configuration number if the change is backward compatible. A backward compatible change is one that, if it is selected as the actual configuration, does not require the allocation of an MR to translate the media payload between the format described by the received SDP offer and the format described by the forwarded SDP offer, and does not require modification of the actual configuration number when forwarding the SDP answer. This applies to the preferred configuration (pcfg) itself and any capabilities referenced in the pcfg. + +NOTE 1: It is recommended that an IMS-ALG not make any codec list changes to an SDP offer that includes any mandatory session capabilities unless it also deletes all attributes associated with capability negotiation as if capability negotiation were not supported. + +To make any of the following changes to a preferred configuration in the SDP offer: + +- to change the priority of the preferred configuration with respect to others; +- to allow insertion of a new preferred configurations with higher priority; +- to allow reassignment of another preferred configuration to a higher priority; or +- to make any other changes to a preferred configuration that are not backward compatible and cannot be realized by inserting a new preferred configuration, + +the IMS-ALG shall reassign the configuration number to one unused in the SDP offer or in any of the encapsulated information for the media line in the SDP offer and add any necessary capability attributes. + +NOTE 2: Changing the priority of a codec or preferred configuration increases the possibility of introducing a transcoding function that is not otherwise needed. Normally new or changed preferred configurations are assigned with higher configuration numbers (of lower priority) than existing preferred configurations. + +When forwarding an SDP offer, the IMS-ALG supporting SDP capability negotiation shall not change any existing SDP capneg capability attributes, but may insert additional capability attributes. + +The IMS-ALG may delete a preferred configuration from the SDP offer. However, the IMS-ALG shall not delete any unreferenced capability attributes. + +If the IMS-ALG desires to add a preferred configuration, it should search for an equivalent or backward compatible preferred configuration within the encapsulated codec related information. If it finds such a suitable preferred configuration, the IMS-ALG should reuse the configuration number from the encapsulated preferred configuration if the resulting priority with respect to other preferred configurations is acceptable. + +To add a new preferred configuration to the media line of the SDP offer that is different from and not backward compatible with any pcfg attribute in encapsulated codec information for the media line, the IMS-ALG shall allocate a new configuration number for the new preferred configuration with a configuration number unused by any other preferred configuration within the SDP offer or within the encapsulated codec related information. + +## 5.5 Additional handling for SDP answer with actual configuration + +In subclause 6.2.2 and subclause 6.2.8 step 4), if the media line in the initial or second SDP answer includes an actual configuration, the IMS-ALG should perform the following procedure to determine if the codecs in the initial or second SDP answer are supported by a previous version of the received initial or second SDP offer: + +The IMS-ALG should compare the actual configuration with SDP capneg preferred configurations in encapsulated codec related information to determine if previous realm instances are associated with matching codec related information. The actual configuration matches a preferred configuration: + +- if the preferred configuration has the same configuration number as the actual configuration; or +- if the capabilities listed in the actual configuration match the capabilities available in the preferred configuration in the initial or second SDP offer. + +**NOTE:** An IMS-ALG can choose not to compare the SDP capneg actual configuration with encapsulated preferred configurations, or only to compare configuration numbers, but this may lead to a failure to find opportunities to bypass previous realm instances. However, SDP capneg procedures recommend that the offerer performs a second offer/answer transaction where the actual configuration is offered in normal SDP. Missed opportunities to bypass previous realm instances could still be found during this second offer/answer transaction. + +If the IMS-ALG selected a preferred configuration with a different configuration number than the actual configuration for bypassing a previous realm, the IMS-ALG shall change the capability number of the actual configuration to equal the capability number of the matching preferred configuration before forwarding the initial or second SDP answer. + +## 5.6 Procedures specific to OMR attributes + +### 5.6.1 General + +This subclause describes additional procedures specific to SDP attributes associated with OMR specified in TS 24.229 [4], subclause 7.5.3. + +### 5.6.2 instance-number + +When creating a new visited-realm instance for a media line in an SDP offer, the IMS-ALG shall assign an instance-number value for the instance that is "1" higher than the highest existing instance-number value for any visited-realm attribute for any media line in the received SDP offer, starting with the value "1" if there are no such attributes in the SDP offer. If the IMS-ALG adds visited-realm instances for several media lines, the IMS-ALG shall use the same instance-number. If the IMS-ALG adds a "secondary-realm" SDP attribute for a media line in the SDP offer the IMS-ALG shall assign the same instance-number value as assigned to the "visited-realm" SDP attribute. + +A UA creating a visited-realm instance for a media line in an SDP offer shall assign an instance-number value "1" for the instance. If the UA adds a "secondary-realm" SDP attribute for a media line in the SDP offer the UA shall assign the instance-number value "1" for a secondary-realm instance. + +### 5.6.3 Session and media checksum calculation + +An IMS ALG or a UA supporting OMR shall determine a session level checksum and a media level checksum for each media line containing a "visited-realm" SDP attribute in an SDP offer. + +**NOTE:** A session level checksum and a media level checksum calculation is not performed for an SDP answer containing media line with a "visited-realm" SDP attribute or a "secondary-realm" SDP attribute. + +The session level checksum shall be calculated by summing all the hex values of the individual ASCII characters (excluding all white space) of the "b" and "a" session level lines. The media level checksum shall be calculated by summing all the hex values of the individual ASCII characters (excluding all white space) of the "m", "b", and "a" media level lines including attributes specific to OMR but excluding the session and media level checksum attribute lines themselves. + +When there are no "b" or "a" session level lines to calculate the session level checksum, the session level checksum is set to "0". + +## 5.7 Roaming architecture for voice over IMS with local breakout + +In a network supporting the roaming architecture for voice over IMS with local breakout OMR related policies may depend on the identification of a roaming architecture for voice over IMS with local breakout session. + +An IBCF acting as an IMS-ALG can identify a session to be a roaming architecture for voice over IMS with local breakout session as specified in TS 24.229 [4], subclause 5.10.9. + +# --- 6 IMS-ALG procedures + +## 6.1 IMS-ALG handling of initial SDP offer + +### 6.1.1 General + +Upon receiving an initial SDP offer, the IMS-ALG supporting OMR shall apply the procedures in the following subclauses for each media line with non-zero port value. + +Upon receiving a subsequent SDP offer that includes OMR attributes for some media lines, the IMS-ALG supporting OMR shall apply the procedures in the following clauses for each media line with non-zero port value and OMR attributes. + +NOTE: An example of a second SDP offer/answer transaction is when any of the IMS-ALGs performs proactive transcoding without resource reservation or removes media resources when transcoding is no longer required. See clauses 6.2.2 and 6.2.3. + +After the completion of an initial SDP offer/answer transaction and when receiving an SDP offer without OMR attributes for a media line, the IMS-ALG supporting OMR shall apply the procedures for subsequent SDP offer/answer transaction in clause 8 for that media line. + +### 6.1.2 Validating the received SDP offer + +If any of the following conditions are true: + +- 1) the received SDP offer includes any OMR attributes for the media line, but no visited-realm instance; +- 2) the connection-address and port information in the visited-realm instance with the highest value of instance-number for the media line does not match the connection address and port information for the media line; or +- 3) one of the following conditions are true: + - the "omr-m-cksum" attribute does not match the checksum value computed for the media line as described in subclause 5.6.3; or + - based on local policy, if the "omr-m-cksum" attribute matches the computed media line checksum, but the "omr-s-cksum" attribute does not match the checksum value computed for the session level lines as described in subclause 5.6.3, + +then the IMS-ALG shall remove all OMR attributes associated with the media line from the received SDP offer and use the modified SDP offer as the received SDP offer in the procedures in the following subclauses. + +### 6.1.3 Deciding whether to allocate a primary local MR and if any previous MR can be bypassed + +The IMS-ALG considers information in the received SDP offer and applies local policy to decide whether to allocate a primary local MR and if it is to bypass any previous MRs. + +NOTE: An IMS-ALG can revise these decisions when receiving the SDP answer, applying procedures in subclause 6.2. + +The IMS ALG shall perform the following steps: + +- 0) If the connection address for the media line in the received SDP offer is the unspecified address, then the IMS-ALG should: + - a) select to not allocate a primary local MR (regardless of local policy), and to not bypass any previous MRs; + - b) convert the unspecified address in the connection address for the media line in the received SDP offer to the addrtype of the outgoing IP realm, if necessary; + - c) if subsequently choosing to perform proactive transcoding in subclause 6.1.7, then select to perform proactive transcoding without resource reservation (regardless of local policy); + - d) select to not add secondary-realm instances to the modified SDP offer when performing the procedure in subclause 6.1.8 (regardless of local policy); and + - e) skip to step 6), +- 1) If all of the following conditions apply: + - a) local policy does not require the allocation of an MR for any non-OMR related reason (e.g. for hosted NAPT traversal on the incoming signalling path, or for legal interception; and + - b) the IP realm, nettype and addrtype for the outgoing signalling path is the same as the IP realm, nettype and addrtype associated with a visited-realm or secondary-realm instance for the media line + - such that the instance has an instance-number value $i$ that is less than the highest instance-number value $n$ associated with the media line in the received SDP offer; and + - such that the instance $i$ is associated with a codec list, determined using the procedures in clause 5.3, which includes all codecs required by local policy, unless the IMS-ALG has a policy to offer the missing codecs proactively without reserving an MR, + +then the IMS-ALG shall store an indication that the allocation of a primary local MR is not required and shall store the realm instances with instance-number greater than $i$ , which are associated with MRs that can be bypassed without allocating a primary local MR. + +- 2) If the following condition applies: + - a) the IMS-ALG controls an MR with access to an IP realm or connected IP realm, nettype and addrtype associated with a visited-realm or secondary-realm instance for the media line + - such that the instance has an instance-number value $j$ that is less than the highest instance-number value $n$ associated with the media line in the received SDP offer; and + - such that the instance $j$ is associated with a codec list, determined using the procedures in clause 5.3, which includes all codecs required by local policy, unless such codecs are provided at a local MR via transcoding, + +then the IMS-ALG shall store the realm instances with instance-number greater than $j$ , which are associated with MRs that can be bypassed when allocating a primary local MR. + +- 3) If all of the following conditions apply: + - a) the condition in step 1) does not apply; + +- b) the IP realm, nettype and addrtype for the outgoing signalling path is the same as the IP realm, nettype and addrtype for the incoming signalling path; +- c) the codec list in the received SDP offer, determined from the SDP m-line and associated non-OMR attribute lines, includes all codecs required by local policy, unless the IMS-ALG has a policy to offer the missing codecs proactively without reserving an MR; and +- d) local policy does not require the allocation of an MR for any non-OMR related reason (e.g. for hosted NAPT traversal on the incoming signalling path, or for legal interception), + +then the IMS-ALG shall store an indication that the allocation of a primary local MR is not required and that no MRs can be bypassed when no primary local MR is allocated. + +- 4) If an indication that the allocation of a primary local MR is not required has been stored in steps 1) or 3), + + - then the IMS-ALG shall compare the realm instances (and MRs) that can be bypassed with or without allocation of a primary local MR, as determined in steps 1), 2) and 3), and shall use local policy to select whether to allocate a primary local MR, + - else the IMS-ALG shall select to allocate a primary local MR, + +**NOTE:** Usually the decision is made based on which choice retains the smallest total number of MRs in the media path, but local policy may apply other criteria. + +- 5) If the IMS-ALG selected in step 4) to allocate a primary local MR, then the IMS-ALG shall: + + - if one or more realm instances can be bypassed when allocating a primary local MR, then store instance-number value $k=j$ and apply the procedures in subclause 6.1.4 to bypass previous MRs, else apply the procedures in subclause 6.1.5 to not bypass previous MRs; and + - apply the procedures in subclause 6.1.6 to allocate a primary local MR. + +- 6) If the IMS-ALG selected in step 4) to not allocate a primary local MR, then the IMS-ALG shall: + + - if one or more realm instances can be bypassed when not allocating a primary local MR, then store instance-number value $k=i$ and apply the procedures in subclause 6.1.4 to bypass previous MRs, else apply the procedures in subclause 6.1.5 to not bypass previous MRs; and + - apply the procedures in subclause 6.1.7 to not allocate a primary local MR. + +### 6.1.4 Bypassing previous MRs + +If the IMS-ALG decides (applying the criteria in subclauses 6.1.3, 6.2.2, 6.2.3 or 6.2.8) to bypass a previous MR, the IMS-ALG shall: + +- 1) use the connection address and port information from the selected instance $k$ for the media line in the received SDP offer as incoming connection address and incoming port information for the media line in the subsequent steps; +- 2) reconstruct the associated codec information for the media line in the received SDP offer from the selected instance $k$ as described in subclause 5.3, and use that codec information as incoming codec information in the subsequent steps; and +- 3) delete every OMR attribute for the media line with instance-number value higher than $k$ . + +### 6.1.5 Bypassing no previous MRs + +If the IMS-ALG decides (applying the criteria in subclauses 6.1.3, 6.2.2 or 6.2.3) not to bypass any previous MR, the IMS-ALG shall: + +- 1) use the connection-address from the SDP c-line in the received SDP offer as incoming connection-address in subsequent steps; +- 2) use the port information from the SDP m-line in the received SDP offer as incoming port information in subsequent steps; and + +- 3) use the codec information from the SDP m-line and associated non-OMR attribute lines in the received SDP offer as incoming codec information in the subsequent steps. + +### 6.1.6 Allocating a primary local MR + +If the IMS-ALG decides (applying the criteria in subclauses 6.1.3 or 6.2.3) to allocate a local MR, the IMS-ALG shall: + +- 1) if no MR context has been allocated due to a previous SDP offer-answer exchange, allocate an MR context with access to the IP realms, nettypes and addrtypes associated with the incoming connection address and port information determined in subclause 6.1.4 or 6.1.5, and the outgoing signalling path, respectively applying procedures as described in subclause 6.3; +- 2) if the IMS-ALG is not performing hosted NAPT traversal on the incoming side, then insert the incoming connection address and incoming port information for the media line, as determined in subclause 6.1.4 or 6.1.5, into the remote connection address and port information for the incoming termination on the MR; +- 3) if the IMS-ALG is performing hosted NAPT traversal on the incoming side, then discover the remote connection address and port information for the incoming termination on the MR using latching or other unspecified technique; +- 4) if codec information is to be provided to the allocated MR on the incoming termination, provide to the MR the incoming codec information as determined in subclause 6.1.4 or 6.1.5; + +NOTE: The IMS-ALG can defer the allocation of an MR termination at the incoming side and the related procedures in steps 1) to 4) until it processes the SDP answer. + +- 5) if the IMS-ALG requires according to local policy that its MR remain in the media path for reasons unrelated to OMR, remove all OMR specific attributes from the modified SDP offer; +- 6) if there is no visited-realm instance associated with the connection address and port information for the media line in the received (and possibly modified) SDP offer, and there is no local policy prohibiting removal of the allocated MR, then construct and add this visited-realm instance to the modified SDP offer; +- 7) replace the connection address and port information for the media line in the modified SDP offer with the connection address and port information from the MR termination on the outgoing side; +- 8) make any codec changes to incoming codec information, as determined in subclause 6.1.4 or 6.1.5, according to local policy, taking into account the procedures in clause 5.4, and insert the changed codec information into the SDP m-line and associated attribute lines of the modified SDP offer; +- 9) if codec information is to be provided to the allocated MR for the outgoing termination, provide to the MR the modified codec information derived in step 8); and +- 10) add to the modified SDP offer a visited-realm instance for the IP realm associated with the connection address and port information for the media line in the modified SDP offer, including the incoming codec information encoded according to clause 5.2 if any codec changes were inserted in step 8). + +### 6.1.7 Allocating no primary local MR + +If the IMS-ALG decides (applying the criteria in subclauses 6.1.3 or 6.2.2) not to allocate a primary local MR, the IMS-ALG shall: + +- 1) decide according to local policy if the IMS-ALG performs any codec changes to the incoming codec information, as determined in subclause 6.1.4 or 6.1.5, without allocating an MR (i.e., for proactive transcoding without resource reservation); + +NOTE: The IMS-ALG can only make codec changes if the available SIP signalling allows the IMS-ALG to initiate a 2nd SDP offer/answer transaction if necessary to allocate a transcoding MR after receipt of the SDP answer, as described in subclause 6.2.3. + +- 2) if the IMS-ALG decided in step 1) to perform any codec changes, then + - a) if there is no visited-realm instance associated with the connection address and port information for the media line in the received SDP offer, then construct and add this visited-realm instance; + +- b) make the codec changes to incoming codec information according to local policy, taking into account the procedures in clause 5.4, and insert the changed codec information into the SDP m-line and associated attribute lines of the modified SDP offer; and + - c) add to the modified SDP offer a visited-realm instance with the same IP realm, connection address and port information as the previous visited-realm instance (after a possible execution of step 3 in subclause 6.1.4 for the media line, including the incoming codec information encoded according to clause 5.2), +- 3) if the IMS-ALG decided in step 1) not to perform any codec changes, then + - a) insert the incoming codec information, determined in subclause 6.1.4 or 6.1.5 into the SDP m-line and associated attribute lines of the modified SDP offer. + - 4) use the incoming connection address, determined in subclause 6.1.4 or 6.1.5, as the connection address in the SDP c-line of the modified SDP offer; and + - 5) use the incoming port information as determined in previous steps as port information in the SDP m-line of the modified SDP offer. + +### 6.1.8 Allocating secondary local MRs + +According to local policy, the IMS-ALG may allocate a secondary MR for each combination of IP realm, nettype and addrtype on the outgoing side for which the IMS-ALG can allocate an MR context. However, if the IMS-ALG does not require a local MR for non-OMR reasons, the IMS ALG should only allocate a secondary MR for a combination of IP realm, nettype and addrtype if the IP realm, nettype and addrtype are not represented by a visited-realm or secondary-realm instance for the media line in the SDP offer. To allocate a secondary MR, the IMS-ALG shall: + +- 1) if no MR context has been allocated due to a previous SDP offer-answer exchange, allocate an MR context for the IP realm, nettype and addrtype on the outgoing side, using the incoming connection address and incoming port information for the media line, determined in subclause 6.1.4 or 6.1.5, as the remote connection address and port information for the incoming termination; +- 2) if codec information is to be provided to the allocated MR for the incoming termination, provide to the MR the incoming codec information, as determined in subclause 6.1.4 or 6.1.5; + +NOTE: The IMS-ALG can defer the allocation of an MR termination at the incoming side and the related procedures in steps 1) and 2) until it processes the SDP answer. + +- 3) if any codec information is to be provided to the allocated MR for the outgoing termination, provide to the MR the codec information from the SDP m-line and associated attribute lines of the modified SDP offer; +- 4) if the IMS-ALG did not yet add a visited-realm instance for the outgoing side (the IMS-ALG did not allocate a primary MR and did not perform any codec changes, see subclause 6.1.7); then + - a) if there is no visited-realm instance associated with the connection address and port information for the media line in the received SDP offer, then construct and add this visited-realm instance; and + - b) add to the SDP offer a visited-realm instance with the same IP realm, connection address and port information as the previous visited-realm instance (after a possible execution of step 3 in subclause 6.1.4 for the media line), +- 5) add to the modified SDP offer a secondary-realm instance for the context allocated in step 1). + +### 6.1.9 Forwarding SDP offer + +The IMS-ALG shall: + +- 1) if local policy forbids sending of OMR related attributes to the outgoing IP realm, the IMS-ALG shall delete all OMR related attributes from the modified SDP offer; and +- 2) if the IMS-ALG has made any modifications to the received SDP offer before forwarding and the modified SDP offer includes OMR related attributes, the IMS-ALG shall compute checksum values as described in subclause 5.6.3 and replace or add the "omr-s-cksum" and "omr-m-cksum" attributes for the media line. + +The IMS-ALG forwards the SDP offer according to TS 24.229 [4]. + +## 6.2 IMS-ALG handling of initial SDP answer + +### 6.2.1 General + +Upon receiving the initial or second SDP answer corresponding to the initial or second SDP offer sent in subclause 6.1, the IMS-ALG supporting OMR shall perform the procedures in the following subclauses for each media line in the initial or second SDP answer. + +### 6.2.2 IMS-ALG bypasses an allocated transcoding MR + +The IMS-ALG uses the following conditions to determine that a previously allocated primary local MR or upstream MR is to be bypassed and that a second SDP offer/answer transaction is needed to update the connection information on the outgoing side. Two examples of this procedure are given in Annex Q of TS 23.228 [3]: steps 5) and 6) of Figure Q.5, and steps 7) and 8) of Figure Q.7. + +If the following conditions are true: + +- 1) the received initial SDP answer includes connection address information for the media line that is a valid IP address other than the unspecified address (i.e., IPv4: "0.0.0.0", IPv6: "invalid.invalid"); and +- 2) it is possible to immediately initiate a second SDP offer/answer transaction towards the initial SDP answerer with the available SIP signalling, + +then the IMS-ALG should re-evaluate the conditions in subclause 6.1.3, steps 1) to 4), taking into account the information from the originally received initial SDP offer, as well as the codecs received in the initial SDP answer as additional information (using the procedure in subclause 5.5 if the initial SDP answer includes an actual configuration), to select again whether to allocate a primary local MR and to recompute how many realm instances can be bypassed. The IMS-ALG should select to modify the previous decision if a higher number of realm instances can be bypassed. + +If the IMS-ALG selected in the previous step to modify the previous decision and + +- to not allocate a primary local MR that has previously been allocated; or +- to not allocate a primary local MR and to bypass other previous realm instances than decided when previously evaluating subclause 6.1.3, + +then the IMS-ALG shall: + +- 1) apply the procedures in subclause 6.1.4 to bypass previous MRs or the procedures in subclause 6.1.5 to not bypass previous MRs (using information from the originally received initial SDP offer), depending on its corresponding decision; +- 2) apply the procedures in subclause 6.1.7 to not allocate a primary local MR without making any codec changes; +- 3) after subclauses 6.2.2 and 6.2.3 are completed as applicable for all media lines, apply the procedures in subclause 6.1.9 for each media line to send a second SDP offer within available SIP signalling, initiating a new second SDP offer/answer transaction towards the SDP answerer; and +- 4) upon receipt of the second SDP answer, continue handling of the second SDP answer as if it were the initial SDP answer, and reference the most recent data associated with the forwarding of the (modified) second SDP offer (i.e., incoming SDP information, allocated MRs and modified second SDP offer) as if it occurred the first time. + +### 6.2.3 IMS-ALG allocates a local transcoding MR when performing proactive transcoding without resource reservation + +The IMS-ALG uses the procedures in this subclause if it receives an initial SDP answer without a realm instance, performed proactive transcoding without resource reservation when forwarding the initial SDP offer, as in step 2) of subclause 6.1.7, and then determines that it needs to allocate an MR for proactive transcoding. + +If all the following conditions are true: + +- 1) the received initial SDP answer includes connection address information for the media line that is a valid IP address other than the unspecified address (i.e., IPv4: "0.0.0.0", IPv6: "invalid.invalid"); + +- 2) the IMS-ALG performed proactive transcoding without resource reservation when previously forwarding the initial SDP offer, as in step 2) of subclause 6.1.7; +- 3) the selected codec in the received initial SDP answer is not supported by the incoming media path and incoming codec information, as previously determined in subclause 6.1.4 or 6.1.5 (using information from the originally received initial SDP offer), indicating that an MR must be allocated to provide transcoding; and +- 4) it is possible to immediately initiate another second SDP offer/answer transaction towards the SDP answerer with the available SIP signalling, + +NOTE: If a second SDP offer/answer transaction cannot be initiated with available SIP signalling, the OMR algorithm will fail to allocate a functioning end-to-end media path. + +then the IMS-ALG shall: + +- 1) if when previously handling the initial SDP offer it was determined in step 2) of subclause 6.1.3 that one or more realm instances can be bypassed when allocating a primary local MR (using information from the originally received initial SDP offer), then store instance-number value $k=j$ and apply the procedures in subclause 6.1.4 to bypass previous MRs, else apply the procedures in subclause 6.1.5 to not bypass previous MRs (using information from the originally received initial SDP offer); +- 2) apply the procedures in subclause 6.1.6 to allocate a primary local MR; +- 3) apply the procedures in subclause 6.1.8 to update allocation of any secondary MRs, if necessary; +- 4) after subclauses 6.2.2 and 6.2.3 are completed as applicable for all media lines, apply the procedures in subclause 6.1.9 for each media line, to send a second SDP offer within available SIP signalling, and to initiate a new SDP offer/answer transaction towards the initial SDP answerer; and +- 5) upon receipt of the second SDP answer, continue handling of the second SDP answer as if it were the initial SDP answer, and reference the most recent data associated with the forwarding of the (modified) second SDP offer (i.e., incoming information, allocated MRs and modified second SDP offer) as if it occurred the first time. + +### 6.2.4 IMS-ALG determines steps required to complete the handling of the SDP answer + +The IMS-ALG performs the following steps to determine the disposition of any allocated MRs and to complete the handling of the SDP answer: + +- 1) if the received SDP answer for the media line includes a connection address with unspecified address and a visited-realm instance, then the IMS-ALG shall apply the procedures in subclause 6.2.5; +- 2) if the received SDP answer for the media line includes a connection address with unspecified address and a secondary-realm instance, then the IMS-ALG shall apply the procedures in subclause 6.2.6; +- 2a) If the received SDP answer for the media line includes a connection address with unspecified address and no visited-realm or secondary-realm instance, then the IMS-ALG shall: + - a) if necessary, update the unspecified connection address information in the SDP answer with the unspecified address of the appropriate type for the network into which the SDP answer will be sent (i.e., IPv4: "0.0.0.0", IPv6: "invalid.invalid"); +- 3) if all the following conditions are true: + - a) the connection address for the media line in the received SDP answer is a valid (not unspecified) address; and + - b) the IMS-ALG did not allocate a primary local MR (i.e., executed subclause 6.1.7) when forwarding the SDP offer, + then the IMS-ALG shall apply the procedures in subclause 6.2.7, and +- 4) if all the following conditions are true: + - a) the connection address for the media line in the received SDP answer is a valid (not unspecified) address; and + - b) the IMS-ALG allocated a primary local MR (i.e., executed subclause 6.1.6) when forwarding the SDP offer, + +then the IMS-ALG shall apply the procedures in subclause 6.2.8 to retain a primary local MR. + +### 6.2.5 Receiving an unspecified connection address and a visited-realm instance + +If the IMS-ALG receives a connection address with unspecified address and a visited-realm instance, then the IMS-ALG shall: + +- 1) If the visited-realm instance for the media line in the SDP answer has an instance-number that matches the visited-realm instance associated with the incoming SDP offer information, + +NOTE 1: The visited-realm instance associated with the incoming SDP offer information is either the one in the received SDP offer with highest instance-number (before any bypass decision is made), if one is present, or the one added in subclause 6.1.6 step 6) or in subclause 6.1.7 step 2a). + +NOTE 2: The IP realms in the two visited-realm instances either have the same name or are connected. + +then the IMS-ALG shall: + +- replace the connection address and port information for the media line in the SDP answer with the connection address and port information from the visited-realm instance in the received SDP answer, and + - retain the visited-realm instance in the SDP answer, +- 2) else the IMS-ALG shall: + - if necessary, update the unspecified connection address information in the SDP answer with the unspecified address of the appropriate type for the network into which the SDP answer will be sent (i.e., IPv4: "0.0.0.0", IPv6: "invalid.invalid"). + +### 6.2.6 Receiving an unspecified connection address and a secondary-realm instance + +If the IMS-ALG receives a connection address with unspecified address and a secondary-realm instance, then the IMS-ALG shall: + +- 1) if the secondary-realm instance for the media line in the SDP answer has an instance-number that matches a secondary-realm instance added by the IMS-ALG when applying procedures in subclause 6.1.8 then the IMS-ALG shall apply the procedures in subclause 6.2.8 to retain a secondary local MR, + +NOTE: The IP realms in the two secondary-realm instances either have the same name or are connected. + +- 2) else the IMS-ALG shall: + +- if necessary, update the unspecified connection address information in the SDP answer with the unspecified address of the appropriate type for the network into which the SDP answer will be sent (i.e., IPv4: "0.0.0.0", IPv6: "invalid.invalid"). + +### 6.2.7 Other handling when no primary local MR allocated + +If the IMS-ALG receives (as determined in subclause 6.2.4) an SDP answer with a valid connection address after forwarding an SDP offer without allocating a primary local MR, then the IMS-ALG shall: + +- 1) If the IMS-ALG applied subclause 6.1.4 to bypass previous MRs when handling the forwarding of the SDP offer, then the IMS-ALG shall: + - a) copy into the media line of the SDP answer the visited-realm or secondary-realm instance from the media line of the received SDP offer that was used to populate the connection address and port information in the forwarded SDP offer, replacing the connection-address and port information in the instance with the connection address and port information from the received SDP answer, and if the IP realm in the instance is a connected IP realm, replacing the IP realm name with the corresponding local IP realm name; and + - b) replace the connection address information in the SDP answer with the unspecified address of the appropriate type for the network into which the SDP answer will be sent (i.e., IPv4: "0.0.0.0", IPv6: "invalid.invalid"), + +- 2) else the IMS-ALG did not bypass previous MRs when forwarding the SDP offer and the IMS-ALG shall not modify the SDP answer. + +NOTE: In step 1) the received SDP answer never includes a realm instance. In step 2) the SDP answer can but does not necessarily include a realm instance. + +### 6.2.8 Retaining a primary or secondary local MR + +If the IMS-ALG decides (applying the criteria in subclause 6.2.4 and subclause 6.2.6) to retain a primary or secondary local MR, the IMS-ALG shall: + +- 1) if the IMS-ALG received an SDP answer with no secondary-realm instance for the media line, then the IMS-ALG shall: + +NOTE: The IMS-ALG retains a primary local MR in this case. The IMS-ALG can but does not necessarily receive a visited-realm instance in an SDP answer when retaining a primary local MR. If present, the visited-realm instance can be used to identify the connected IP realm for the outgoing termination, if different from the IP realm of the outgoing termination. + +- a) update the remote connection address and port information for the outgoing termination on the selected primary local MR context with the connection address and port information for the media line in the received SDP answer, + - b) delete the visited-realm instance from the SDP answer, if present, +- 2) if the IMS-ALG received an SDP answer with a secondary-realm instance for the media line, then the IMS-ALG shall: + - a) update the remote connection address and port information for the outgoing termination on the selected secondary local MR context with the connection-address and port information from the secondary-realm instance in the received SDP answer; and + - b) delete the secondary-realm instance from the SDP answer, +- 3) if the selected codecs in the SDP answer are not in the set of codecs associated with the incoming SDP offer information, as determined in subclause 6.1.4 or 6.1.5 when handling the SDP offer, then modify the SDP answer to include the codecs selected for the incoming termination of the selected local MR; +- 4) if the selected MR has access to an IP realm or connected IP realm, nettype and addrtype associated with a visited-realm or secondary-realm instance for the media line + - such that the instance has an instance-number value $k$ that is less than the highest instance-number value $n$ associated with the media line in the incoming SDP offer information, previously determined in subclause 6.1.4 or 6.1.5; and + - such that the instance $k$ is associated with a codec list, determined using the procedures in clause 5.3, which includes the codecs selected for the incoming termination of the selected local MR in step 3) (using the procedure in subclause 5.5 if the SDP answer includes an actual configuration), + +then the IMS-ALG shall: + +- a) store the realm instances with instance-number greater than $k$ , which are associated with additional MRs that can be bypassed after selecting a codec for the incoming media path when allocating a primary local MR; +- b) apply the procedures in subclause 6.1.4 to bypass additional previous MRs (using information from the originally received SDP offer); +- c) insert the incoming connection address and incoming port information for the media line, as determined in step b), as the remote connection address and port information for the selected IP realm on the incoming termination of the selected MR; +- d) if necessary, modify the selected codec information in the SDP answer to be a valid response to the incoming SDP offer codec information determined in step b); + +- e) if codec information is to be provided to the allocated MR on the incoming termination, provide to the MR the incoming codec information as determined in step d), +- 5) If the IMS-ALG applied subclause 6.1.4 to bypass previous MRs when forwarding the SDP offer or in step 4b), then the IMS-ALG shall: +- a) copy into the media line of the SDP answer the visited-realm or secondary-realm instance from the media line of the received SDP offer that was used for the remote connection address and port information for the incoming termination on the MR, replacing the connection-address and port information in the instance with the local connection address and port information for the incoming termination on the selected MR, and if the IP realm in the instance is a connected IP realm, replacing the IP realm name with the corresponding local IP realm name; and + - b) replace the connection address information in the SDP answer with the unspecified address of the appropriate type for the network into which the SDP answer will be sent (i.e., IPv4: "0.0.0.0", IPv6: "invalid.invalid"), +- 6) If the IMS-ALG applied subclause 6.1.5 to not bypass previous MRs when forwarding the SDP offer, and did not bypass previous MRs in step 4b), then the IMS-ALG shall: +- a) replace the connection address and port information for the media line in the SDP answer with the local connection address and port information for the incoming termination on the selected MR. + +### 6.2.9 Forwarding the SDP answer + +The IMS-ALG forwards the SDP answer according to TS 24.229 [4]. + +The IMS-ALG shall release each MR for the media line, when it is no longer potentially needed for this and any other forked dialog. + +## 6.3 IMS-ALG OMR media resource operations + +### 6.3.1 General + +The IMS-ALG OMR procedures as specified by subclauses 6.1 and 6.2 refer to generic MR allocation operation. When no MR was previously allocated, e.g. during the initial SDP offer/answer exchange, this allocation will result in the allocation of one or more local media termination point pairs (ingress and egress) – one for the primary IP realm and possible additional terminations points for secondary IP realms. + +Subsequent SDP offer/answer exchanges may result in the decision that a local MR is needed. If a local MR was not previously allocated, then one will now be allocated. If a local MR was previously allocated that matches the resource information needed, then the previously allocated resource will be used. If the previously allocated local MR does not match the resource information needed, then the local MR will be modified to meet the current need. + +If it is determined that local MR may be by-passed or no longer needed, then any previously allocated local MRs will be deallocated. + +### 6.3.2 IMS-ALG operations + +The OMR MR procedures in this document are applicable to the following IMS entities that perform as IMS-ALG using the media resource interface operations as indicated. + +- An IBCF acting as an IMS-ALG controlling a TrGW using the Ix interface as defined by TS 29.162 [16] and TS 29.238 [9]: + - Reserve TrGW Connection Point; + - Configure TrGW Connection Point, + - Reserve and Configure TrGW Connection Point; and + - Release TrGW Connection Point. +- A P-CSCF acting as IMS-ALG controlling an IMS-AGW using the Iq interface as defined by TS 23.334 [15] and TS 29.334 [10]: + +- Reserve AGW Connection Point; +- Configure AGW Connection Point; +- Reserve and Configure AGW Connection Point; and +- Release AGW Connection Point. +- An AS acting as B2BUA and adapting IMS-ALG procedures to control an MRF shall use one or more of the following: + - IETF RFC 4240 [11] conference service; + - IETF RFC 4117 [19]; and + - IETF RFC 3260 [12] and IETF RFC 6505 [13]. + +## 6.4 Handling of connected IP realms + +For each IP realm to which a controlled MR has direct access, the IMS-ALG supporting OMR may be provisioned with a list of the names of connected IP realms, if any. The IMS-ALG shall determine if an IP realm is connected to a local IP realm based only on provisioning. + +NOTE 1: The OMR algorithm assumes that a first IMS-ALG or UA sending an SDP offer that offers connectivity via a local IP realm will accept from a second IMS-ALG or UA an SDP answer with an address in a connected IP realm, even if the first IMS-ALG or UA does not have provisioned information about the connected IP realm. + +NOTE 2: Connected IP realm lists only need to be provisioned at certain OMR-capable nodes. For example, it is preferred that an IBCF whose TrGW has connectivity to multiple peer networks via bilateral interconnect be provisioned with connected IP realm information. + +# --- 7 UA Procedures + +## 7.1 UA sending an initial SDP offer + +Upon preparing an initial SDP offer for sending to begin an initial SDP offer/answer transaction, a UA supporting OMR shall additionally: + +- 1) add to the initial SDP offer a visited-realm instance for the IP realm associated with the connection address and port information for the media line in the initial SDP offer; +- 2) for each combination of IP realm, nettype and addrtype on the outgoing side for which the UA can allocate an MR termination according to local policy, if the IP realm, nettype and addrtype are not associated with the media line in the initial SDP offer, allocate an MR termination for the IP realm, nettype and addrtype on the outgoing side, using the same codecs associated with the media line; +- 3) add to the initial SDP offer a secondary-realm instance for each termination allocated in step 2); and +- 4) compute a checksum values as described in subclause 5.6.3 and add the "omr-s-cksum" and "omr-m-cksum" attributes for the media line. + +The UA then sends the initial SDP offer according to TS 24.229 [4]. + +NOTE: A subsequent SDP offer is sent according to procedures in clause 8. + +## 7.2 UA receiving an initial SDP offer + +### 7.2.1 General + +Upon receiving an SDP offer that includes OMR attributes and selecting a codec for the media line, a UA supporting OMR shall perform the procedures specified in subclauses 7.2.2 and 7.2.3, and then send the initial or second SDP answer according to TS 24.229 [4]. + +### 7.2.2 Validating the incoming SDP offer + +If any of the following conditions are true: + +- 1) the SDP offer includes any OMR attributes for the media line, but no visited-realm instance; +- 2) the connection-address and port information in the visited-realm instance with the highest value of instance-number for the media line does not match the connection address and port information for the media line; or +- 3) one of the following checksum comparison failures are true: + - the "omr-m-cksum" attribute does not match the checksum value computed for the media line as described in subclause 5.6.3; or + - based on local policy, if the "omr-m-cksum" attribute matches the computed media line checksum, but the "omr-s-cksum" attribute does not match the checksum value computed for the session level lines as described in subclause 5.6.3, + +then the UA shall remove all OMR related attributes associated with the media line. + +### 7.2.3 UA may choose an alternate realm instance to bypass an upstream MR + +If all the following conditions are true: + +- 1) the UA can make available a media termination in an IP realm, nettype and addrtype such that this IP realm or a connected IP realm, nettype and addrtype match the IP realm, nettype and addrtype of a visited-realm or secondary-realm instance for the media line in the SDP offer; +- 2) the instance does not match the connection address and port information in the SDP offer; and +- 3) the instance supports the codec selected by the UA, + +then the UA shall: + +- 1) select the visited-realm or secondary-realm instance with the lowest value of instance-number such that the UA can make available a media termination in the IP realm or connected IP realm, nettype and addrtype that matches the IP realm, nettype and addrtype of the instance and the instance supports the codec selected by the UA; +- 2) allocate a media termination in the selected IP realm, nettype and addrtype; +- 3) copy into the media line of the SDP answer the selected visited-realm or secondary-realm instance from the media line of the received SDP offer, replacing the connection-address and port information in the instance with the local connection address and port information for the allocated termination, and if the IP realm in the instance is a connected IP realm, replacing the IP realm name with the corresponding local IP realm name; and +- 4) replace the connection address information in the SDP answer with the unspecified address of the appropriate type for the network into which the SDP answer will be sent (i.e., IPv4: "0.0.0.0", IPv6: "invalid.invalid"). + +## 7.3 UA receiving an initial SDP answer + +### 7.3.1 General + +Upon receiving the initial SDP answer corresponding to the initial SDP offer sent in subclause 7.1, the UA supporting OMR shall perform the procedures specified in either subclause 7.3.2 if the SDP answer included a realm instance or subclause 7.3.3 if the initial SDP answer did not include a realm instance. + +### 7.3.2 Receiving SDP answer with an unspecified connection address + +If the received SDP answer for the media line includes an unspecified connection address (i.e., IPv4: "0.0.0.0", IPv6: "invalid.invalid") and a visited-realm or a secondary-realm instance with an instance-number that matches a visited-realm or secondary-realm instance for the media line from the SDP offer, then the UA shall: + +NOTE: The IP realms in the two realm instances either have the same name or are connected. + +- 1) update the remote connection address and port information for the selected outgoing termination with the connection-address and port information from the visited-realm or secondary-realm instance in the received SDP answer; and +- 2) release any other MR apart from the selected MR allocated for the media line, when it is no longer potentially needed for any other forked dialog. + +### 7.3.3 Receiving SDP answer with a valid connection address + +If the received SDP answer includes a valid (not unspecified) connection address for the media line, then the UA shall: + +- 1) update the remote connection address and port information for the primary outgoing termination with the connection address and port information from the received SDP answer; and +- 2) release any secondary MR allocated for the media line, when it is no longer potentially needed for any other forked dialog. + +## 7.4 UA OMR media resource operations + +### 7.4.1 General + +The UA OMR procedures as specified by subclauses 7.1, 7.2, and 7.3 refer to generic MR allocation operation. This allocation will result in the allocation of a local media termination associated with the selected IP realm. + +Subsequent SDP offer/answer exchanges may result in either the exact same local MR being allocated or possibly a different local MR. If the UA is able to determine that the same resource information is being requested, the existing allocated local MR will be used. If the previously allocated local MR does not match the resource information needed, then the local MR will be modified to meet the current need. + +### 7.4.2 UA operations + +The OMR MR procedures in this document are applicable to the following IMS entities that perform as UA using the media resource interface operations as indicated. + +- An AS acting as B2BUA and adapting UA procedures to control an MRF shall use one or more of the following: + - IETF RFC 4240 [11] conference service and tone/announcement service; + - IETF RFC 5552 [18]; and + - IETF RFC 3260 [12] and IETF RFC 6505 [13]. +- An MGCF acting as an UA controlling an IM-MGW using the Mn interface as defined by TS 29.163 [17] and TS 29.332 [14]: + - Reserve IMS Connection Point; + - Configure IMS Connection Point; + - Reserve and Configure IMS Connection Point; and + - Release IMS Connection Point. + +## 7.5 Handling of connected IP realms + +For each IP realm to which a controlled MR has direct access, the UA supporting OMR may be provisioned with a list of the names of connected IP realms, if any. The UA shall determine if an IP realm is connected to a local IP realm based only on provisioning. + +NOTE 1: The OMR algorithm assumes that a first IMS-ALG or UA sending an SDP offer that offers connectivity via a local IP realm will accept from a second IMS-ALG or UA an SDP answer with an address in a connected IP realm, even if the first IMS-ALG or UA does not have provisioned information about the connected IP realm. + +NOTE 2: Connected IP realm lists only need to be provisioned at certain OMR-capable nodes. For example, it is preferred that an IBCF whose TrGW has connectivity to multiple peer networks via bilateral interconnect be provisioned with connected IP realm information. + +# 8 Subsequent SDP offer/answer transactions + +## 8.1 General + +Any UA or IMS-ALG controlling a media stream may initiate a subsequent SDP offer/answer transaction at any time after first establishing the media flow, in order to modify characteristics of the media flow. + +NOTE: For example, a media endpoint (IP address) can change, the preferred codec can change, or a server can select to insert a media function such as a tone generator or conference focus. + +An IMS-ALG or UA shall handle a received SDP offer as a subsequent SDP offer as specified in clause 8.2 if an initial or second SDP offer/answer transaction has been completed and a received SDP offer contains no OMR specific SDP attribute. + +## 8.2 IMS-ALG and UA subsequent SDP offer procedures + +When a IMS-ALG determines according to clause 8.1 that a received SDP offer shall be handled as a subsequent SDP offer, the IMS-ALG with or without a local primary or secondary MR allocated shall perform the following steps: + +When a IMS-ALG determines according to clause 8.1 that a received SDP offer shall be handled as a subsequent SDP offer, the IMS-ALG with or without a local primary or secondary MR allocated shall perform the following steps: + +- 1) determine if the local primary or secondary MR can be inserted or removed from the media path as specified in clause 8.4; +- 2) if the IMS-ALG keeps an allocated MR or allocates a new MR and continues with an MR inserted in the media path, the IMS-ALG shall: + - if necessary (e.g. due to a codec change or allocation of a new MR) interact with the MR; + - update the connection address for the media line in the outgoing subsequent SDP offer; and + - forward the modified SDP offer as specified in TS 24.229 [4]. +- 3) if the IMS-ALG does not allocate a new MR or deallocated an MR allocated in the initial or second SDP offer / answer transaction in clause 6 and continues without a MR inserted in the media path, forward the incoming subsequent SDP offer as received. + +When a UA (e.g. a conference application treating the media resource as an endpoint or an MGCF) determines according to clause 8.1 that a SDP offer shall be sent as a subsequent SDP offer , the UA shall not apply OMR procedures in clause 7 when sending the subsequent SDP offer. If the conditions in clause 8.4 for reallocating a MR are fulfilled, the UA may reallocate a MR. + +## 8.3 IMS-ALG and UA subsequent SDP answer procedures + +When an IMS-ALG receives a subsequent SDP answer as the result of a subsequent SDP offer generated according to clauses 8.2, the IMS-ALG with or without a local primary or secondary MR allocated shall perform the following steps: + +- 1) if the IMS-ALG has a local MR allocated: + +NOTE: The local MR can have been allocated during the initial or second SDP offer / answer transaction as described in clause 6 or as the result of the subsequent SDP offer generated in clause 8.2. + +- a) if necessary interact with the MR as described in clauses 6.3; and +- b) update connection address in the outgoing subsequent SDP answer for the media line with the MR connection information; +- c) forward the modified SDP answer as specified in TS 24.229 [4]; and + +- 2) if the IMS-ALG has no local MR allocated: + - a) if the local MR was allocated when the subsequent SDP offer was received, release MR resources; and + - b) forward the subsequent SDP answer as received. + +When a UA not acting as a B2BUA (e.g. a conference application treating the media resource as an endpoint or the MGCF) receives a subsequent SDP answer, the UA shall not apply OMR procedures specified in clause 7. + +## 8.4 Handling media resources during a subsequent SDP offer/answer transaction + +An IMS-ALG, an AS acting as B2BUA and adapting IMS-ALG procedures to control an MRF or a UA not acting as a B2BUA (e.g. a conference application treating the media resource as an endpoint or the MGCF) shall not allocate, deallocate or reallocate a MR during the subsequent SDP offer/answer transaction unless any of the following exceptions apply: + +- an IMS-ALG may allocate an MR resource if the downstream and upstream media anchoring points are within the same realm and in the same operator network as the IMS-ALG; +- an IMS-ALG may deallocate an MR resource if the downstream and upstream media anchoring points are within the same realm and in the same operator network as the IMS-ALG; or +- an UA may reallocate an MR resource if the downstream and upstream media anchoring point is within the same realm and in the same operator network as the UA. + +If an IMS-ALG or UA decides to allocate or reallocate a MR, the IMS-ALG or UA shall interact with the MR as described in clause 6.3 or 7.4. + +If a IMS-ALG decides to deallocate a MR, the IMS-ALG shall release the MR resource when receiving the subsequent SDP answer. + +# Annex A (informative): Signalling flows + +## A.1 Scope of signalling flows + +This annex gives examples of signalling flows for Optimized Media Routeing (OMR) based on the Session Initiation Protocol (SIP) and the Session Description Protocol (SDP). The OMR specific SDP syntax is described in TS 24.229 [4]. + +## A.2 Introduction + +The signalling flows in this annex are based on IP realm and IP structure in Figure A.2-1. + +![Diagram of IP realm and IP structure showing Home IMS network H, IPX network X, and Visited network V with various network elements like S-CSCF, IBCF, TrGW, IC, MGW, P-CSCF, PCRF, PDN, TRF, and UE-A.](4af57aad638888edf2062306f8a54a6c_img.jpg) + +The diagram illustrates the IP realm and IP structure across three network domains: + +- Home IMS network H:** Realm Ha.operatorH.net. It contains an S-CSCF/BGCF connected to two parallel paths. Each path consists of an IBCF (IBCF-2 and IBCF-3) and a TrGW. The IBCFs have IP address 190.1.15.2 (Ha). The TrGWs have internal IP addresses Xa4 179.14.1.2 and Xa4 179.14.1.3. +- IPX network X:** Realm Xa.operatorX.net. It receives connections from the Home IMS network H's TrGWs and connects to the Visited network V. It contains two parallel paths. Each path consists of an IC (IC-1 and IC-2) and an MGW. The ICs have IP addresses 179.14.1.1 (Xa2) and 179.14.1.4 (Xa2). The MGWs have internal IP addresses Xa2 178.15.1.2 and Xa2 178.15.1.3. +- Visited network V:** Realm Va.operatorV.net. It contains a P-CSCF-A connected to UE-A (IP Va 192.0.2.1). The P-CSCF-A is also connected to a PCRF and a PDN. The PDN is connected to a PDN GW. The PDN GW is connected to a TRF. The TRF is connected to an IBCF-5 and a TrGW. The IBCF-5 has an internal IP address Va 192.0.2.4. The PDN GW is also connected to two parallel paths. Each path consists of an IBCF (IBCF-1 and IBCF-4) and a TrGW. The IBCFs have IP addresses 178.15.1.1 (Xa1) and 178.15.1.4 (Xa1). The TrGWs have internal IP addresses 192.0.2.2 and 192.0.2.3. + +**Legend:** + +- Control signalling path:** Represented by a solid line with double-headed arrows. +- Media path after OMR:** Represented by a dashed line with single-headed arrows. + +Diagram of IP realm and IP structure showing Home IMS network H, IPX network X, and Visited network V with various network elements like S-CSCF, IBCF, TrGW, IC, MGW, P-CSCF, PCRF, PDN, TRF, and UE-A. + +Figure A.2-1: IP realm and IP structure + +Operator X and operator Y have an agreement to allow roaming users and to use OMR as much as possible. + +UE-A and UE-B are mobile users roaming into the visited network X. IP addresses etc. are obtained as described in TS 24.229 [4]. + +The operator X implements the IBCF policy to allow OMR optimization of anchoring if originating UE is a visiting/roaming user respectively if terminating UE is a visiting/roaming user. + +The operator Y implements the IBCF policy to allow OMR optimization of anchoring if home UE is visiting/roaming in another network. + +## --- A.3 Media bypassing all IMS-ALGs + +### A.3.1 General + +This subclause provides an example of a call where the media is bypassing all IMS-ALG and sent directly between the UEs. + +### A.3.2 Message flow + +This subclause describes the scenario when two mobile user A and B roams into a visited network X and both users belongs to the same operator Y. + +Preconditions: + +- Both user A and B are registered to the Home IMS network Y via the visited operator X network; +- the visited operator X and the operator of user A and B IMS home network Y have an agreement to allow media to be bypassed using OMR; +- both user A and B are connected to IP realm Xa of the visited operator network X; +- the AMR codec is allowed and accepted by all involved entities; and +- no B2BUA manipulating SDP is connected in the intermediate IM CN subsystem. + +Figure A.3.2-1 shows the message flow for the scenario. + +![Sequence diagram showing the signalling flow for media bypassing all IMS ALGs. The diagram illustrates the interaction between UE-A, P-CSCF A, IBCF-1, IBCF-2, Intermediate IM CN subsystem entities X, IBCF-3, IBCF-4, P-CSCF B, and UE-B across three network domains: Visited network X, Home IMS network Y, and Visited network X. The flow includes INVITE, 183, PRACK, 200 OK (PRACK), UPDATE, 200 OK (UPDATE), 180, 200 OK (INVITE), and ACK messages, with a continuous audio media stream indicated at the bottom.](dd5771673aececa53d42ece89218299d_img.jpg) + +The diagram illustrates the signalling flow for media bypassing all IMS ALGs. It is divided into three network domains: Visited network X (left), Home IMS network Y (of user A and B) (middle), and Visited network X (right). The entities involved are UE-A, P-CSCF A, IBCF-1, IBCF-2, Intermediate IM CN subsystem entities X, IBCF-3, IBCF-4, P-CSCF B, and UE-B. The flow consists of the following steps: + +1. INVITE [AMR, c=192.0.2.1] from UE-A to P-CSCF A. +2. INVITE [AMR, c=192.0.2.1] from P-CSCF A to IBCF-1. +3. INVITE [AMR, c=13.24.1.1, visited-realm:1 Xa 192.0.2.1, visited-realm:2 X-Y 13.24.1.1] from IBCF-1 to IBCF-2. +4. INVITE [AMR, c=190.1.15.2, visited-realm:1 Xa 192.0.2.1, visited-realm:2 X-Y 13.24.1.1, visited-realm:3 Yb 190.1.15.2] from IBCF-2 to Intermediate IM CN subsystem entities X. +5. INVITE [AMR, c=190.1.15.2, visited-realm:1 Xa 192.0.2.1, visited-realm:2 X-Y 34.24.1.1, visited-realm:3 Yb 190.1.15.2] from Intermediate IM CN subsystem entities X to IBCF-3. +6. INVITE [AMR, c=13.24.1.1, visited-realm:1 Xa 192.0.2.1, visited-realm:2 X-Y 13.24.1.1] from IBCF-3 to IBCF-4. +7. INVITE [AMR, c=192.0.2.1, visited-realm:1 Xa 192.0.2.1] from IBCF-4 to P-CSCF B. +8. INVITE [c=192.0.2.1] from P-CSCF B to UE-B. +9. 183 [c=192.0.2.4] from UE-B to P-CSCF B. +10. 183 [AMR, c=192.0.2.4] from P-CSCF B to IBCF-4. +11. 183 [AMR, c=0.0.0.0, visited-realm:1 Xa 192.0.2.4] from IBCF-4 to IBCF-3. +12. 183 [AMR, c=0.0.0.0, visited-realm:1 Xa 192.0.2.4] from IBCF-3 to Intermediate IM CN subsystem entities X. +13. 183 [AMR, c=0.0.0.0, visited-realm:1 Xa 192.0.2.4] from Intermediate IM CN subsystem entities X to IBCF-2. +14. 183 [AMR, c=0.0.0.0, visited-realm:1 Xa 192.0.2.4] from IBCF-2 to IBCF-1. +15. 183 [AMR, c=192.0.2.4] from IBCF-1 to P-CSCF A. +16. 183 [AMR, c=192.0.2.4] from P-CSCF A to UE-A. +17. PRACK from UE-A to P-CSCF A. +18. PRACK from P-CSCF A to IBCF-1. +19. PRACK from IBCF-1 to IBCF-2. +20. PRACK from IBCF-2 to Intermediate IM CN subsystem entities X. +21. PRACK from Intermediate IM CN subsystem entities X to IBCF-3. +22. PRACK from IBCF-3 to IBCF-4. +23. PRACK from IBCF-4 to P-CSCF B. +24. PRACK from P-CSCF B to UE-B. +25. 200 OK (PRACK) from UE-B to P-CSCF B. +26. 200 OK (PRACK) from P-CSCF B to IBCF-4. +27. 200 OK (PRACK) from IBCF-4 to IBCF-3. +28. 200 OK (PRACK) from IBCF-3 to Intermediate IM CN subsystem entities X. +29. 200 OK (PRACK) from Intermediate IM CN subsystem entities X to IBCF-2. +30. 200 OK (PRACK) from IBCF-2 to IBCF-1. +31. 200 OK (PRACK) from IBCF-1 to P-CSCF A. +32. 200 OK (PRACK) from P-CSCF A to UE-A. +33. UPDATE [AMR, c=192.0.2.1] from UE-A to P-CSCF A. +34. UPDATE [AMR, c=192.0.2.1] from P-CSCF A to IBCF-1. +35. UPDATE [AMR, c=192.0.2.1] from IBCF-1 to IBCF-2. +36. UPDATE [AMR, c=192.0.2.1] from IBCF-2 to Intermediate IM CN subsystem entities X. +37. UPDATE [AMR, c=192.0.2.1] from Intermediate IM CN subsystem entities X to IBCF-3. +38. UPDATE [AMR, c=192.0.2.1] from IBCF-3 to IBCF-4. +39. UPDATE [AMR, c=192.0.2.1] from IBCF-4 to P-CSCF B. +40. UPDATE [AMR, c=192.0.2.1] from P-CSCF B to UE-B. +41. 200 OK (UPDATE) [c=192.0.2.4] from UE-B to P-CSCF B. +42. 200 OK (UPDATE) [AMR, c=192.0.2.4] from P-CSCF B to IBCF-4. +43. 200 OK (UPDATE) [AMR, c=192.0.2.4] from IBCF-4 to IBCF-3. +44. 200 OK (UPDATE) [AMR, c=192.0.2.4] from IBCF-3 to Intermediate IM CN subsystem entities X. +45. 200 OK (UPDATE) [AMR, c=192.0.2.4] from Intermediate IM CN subsystem entities X to IBCF-2. +46. 200 OK (UPDATE) [AMR, c=192.0.2.4] from IBCF-2 to IBCF-1. +47. 200 OK (UPDATE) [AMR, c=192.0.2.4] from IBCF-1 to P-CSCF A. +48. 200 OK (UPDATE) [AMR, c=192.0.2.4] from P-CSCF A to UE-A. +49. 180 from UE-B to P-CSCF B. +50. 180 from P-CSCF B to IBCF-4. +51. 180 from IBCF-4 to IBCF-3. +52. 180 from IBCF-3 to Intermediate IM CN subsystem entities X. +53. 180 from Intermediate IM CN subsystem entities X to IBCF-2. +54. 180 from IBCF-2 to IBCF-1. +55. 180 from IBCF-1 to P-CSCF A. +56. 180 from P-CSCF A to UE-A. +57. 200 OK (INVITE) [c=192.0.2.4] from UE-B to P-CSCF B. +58. 200 OK (INVITE) [AMR, c=192.0.2.4] from P-CSCF B to IBCF-4. +59. 200 OK (INVITE) [AMR, c=192.0.2.4] from IBCF-4 to IBCF-3. +60. 200 OK (INVITE) [AMR, c=192.0.2.4] from IBCF-3 to Intermediate IM CN subsystem entities X. +61. 200 OK (INVITE) [AMR, c=192.0.2.4] from Intermediate IM CN subsystem entities X to IBCF-2. +62. 200 OK (INVITE) [AMR, c=192.0.2.4] from IBCF-2 to IBCF-1. +63. 200 OK (INVITE) [AMR, c=192.0.2.4] from IBCF-1 to P-CSCF A. +64. 200 OK (INVITE) [AMR, c=192.0.2.4] from P-CSCF A to UE-A. +65. ACK from UE-A to P-CSCF A. +66. ACK from P-CSCF A to IBCF-1. +67. ACK from IBCF-1 to IBCF-2. +68. ACK from IBCF-2 to Intermediate IM CN subsystem entities X. +69. ACK from Intermediate IM CN subsystem entities X to IBCF-3. +70. ACK from IBCF-3 to IBCF-4. +71. ACK from IBCF-4 to P-CSCF B. +72. ACK from P-CSCF B to UE-B. + +audio media + +Sequence diagram showing the signalling flow for media bypassing all IMS ALGs. The diagram illustrates the interaction between UE-A, P-CSCF A, IBCF-1, IBCF-2, Intermediate IM CN subsystem entities X, IBCF-3, IBCF-4, P-CSCF B, and UE-B across three network domains: Visited network X, Home IMS network Y, and Visited network X. The flow includes INVITE, 183, PRACK, 200 OK (PRACK), UPDATE, 200 OK (UPDATE), 180, 200 OK (INVITE), and ACK messages, with a continuous audio media stream indicated at the bottom. + +Figure A.3.2-1: Signalling flow for media bypassing all IMS ALGs + +NOTE: For clarity, the SIP 100 (Trying) messages are not shown in the signalling flow. + +The steps of the flow are as follows: + +#### **1. INVITE request (UE-A to P-CSCF-A) - see example in table A.3.2-1.** + +The UE-A sends a SIP INVITE request including an initial SDP offer according to TS 24.229 [4]. + +**Table A.3.2-1: SIP INVITE request (UE-A to P-CSCF-A)** + +``` + +INVITE SIP: user_B@operator_Y.net; SIP/2.0 + +SIP headers according to 3GPP TS 24.229 [4] + +Content-Type: application/sdp +Content-Length: (...) + +v=0 +o= 2987933615 2987933615 IN IP4 192.0.2.1 +s= +t=0 0 +c=IN IP4 192.0.2.1 +m=audio 49170 RTP/AVP 96 97 +a=curr:qos local none +a=curr:qos remote none +a=des:qos mandatory local sendrecv +a=des:qos none remote sendrecv +a=rtpmap:97 AMR +a=fmtp:97 mode-set=0,2,5,7; mode-change-period=2 +a=rtpmap:96 telephone-event +a=maxptime:20 + +``` + +#### **2. INVITE request (P-CSCF-A to IBCF-1) - see example in table A.3.2-1.** + +The P-CSCF-A uses the procedures in subclauses 6.1.5, 6.1.7 and 6.1.9 since no MR could be bypassed and no MR is allocated. + +The P-CSCF-A: + +- uses the connection-address from the SDP c-line as incoming connection-address in subsequent steps; +- uses the port information from the SDP m-line as incoming port information in subsequent steps; +- uses the codec information from the SDP m-line in subsequent steps; +- inserts the incoming codec information into the SDP m-line and associated attribute lines of the modified initial SDP offer; +- uses the incoming connection address as the connection address in the SDP c-line of the forwarded initial SDP offer, and +- use the incoming port information as port information in the SDP m-line of the modified initial SDP offer. + +The P-CSCF-A then selects an IBCF, IBCF-1, in the IP realm "Xa.operatorX.net" and forwards the INVITE request with the initial SDP offer to the IBCF-1 according to TS 24.229 [4]. + +#### **3. INVITE request (IBCF-1 to IBCF-2) - see example in table A.3.2-3** + +The IBCF-1 uses the procedures in subclauses 6.1.5, 6.1.6 and 6.1.9 since no previous realm instance offers an opportunity to bypass a previous MR and a local MR is required for IP realm matching. + +The IBCF-1: + +- uses the connection-address from the SDP c-line as incoming connection-address in subsequent steps; +- uses the port information from the SDP m-line as incoming port information in subsequent steps; +- uses the codec information from the SDP m-line in subsequent steps; +- allocates an MR context with access to the IP realms and addrtypes associated with the incoming and outgoing signalling paths; +- inserts the incoming connection address and incoming port information for the media line into the remote connection address and port information for the incoming termination on the MR; +- provides to the MR the incoming codec information; + +- replaces the connection address and port information for the media line in the initial SDP offer with the connection address and port information from the MR termination on the outgoing side; +- constructs and adds a visited-realm instance for the media line in the received initial SDP offer to the modified initial SDP offer; +- adds to the modified initial SDP offer a visited-realm instance for the IP realm associated with the connection address and port information for the media line in the modified initial SDP offer, including the incoming codec; and +- computes a checksum value for the media line as described in subclause 5.6.3 and adds the "omr-m-cksum" and "omr-s-cksum" attributes for the media line. The "omr-s-cksum" is set to "0" since there are no session attributes to compute the checksum on. + +The IBCF-1 then selects an IBCF, IBCF-2, in the IP realm "X-Y.operatorX.net" and forwards the INVITE request with the initial SDP offer to the IBCF-2 according to TS 24.229 [4]. + +**Table A.3.2-3: SIP INVITE request (IBCF-1 to IBCF-2)** + +``` +INVITE SIP: user_B@operator_Y.net; SIP/2.0 + +SIP headers according to 3GPP TS 24.229 [4] + +Content-Type: application/sdp +Content-Length: (...) + +v=0 +o=- 2987933615 2987933615 IN IP4 192.0.2.1 +s= +t=0 0 +c=IN IP4 13.24.1.1 +m=audio 62111 RTP/AVP 96 97 +a=curr:qos local none +a=curr:qos remote none +a=des:qos mandatory local sendrecv +a=des:qos none remote sendrecv +a=rtpmap:97 AMR +a=fmtp:97 mode-set=0,2,5,7; mode-change-period=2 +a=rtpmap:96 telephone-event +a=maxptime:20 +a=visited-realm:1 Xa.operatorX.net IN IP4 192.0.2.1 49170 +a=visited-realm:2 X-Y.operator.netX IN IP4 13.24.1.1 62111 +a=omr-m-cksum:(..) +a=omr-s-cksum:0 +``` + +#### 4-5. INVITE request (IBCF-2 to IBCF-3 via intermediate IMS CN subsystem entities) - see example in table A.3.2-4. + +The IBCF-2 uses the procedure in subclauses 6.1.5, 6.1.6 and 6.1.9 since no realm instance offers an opportunity to bypass a previous MR and a local MR is required for IP realm matching. + +The IBCF-2: + +- uses the connection-address from the SDP c-line as incoming connection-address in subsequent steps; +- uses the port information from the SDP m-line as incoming port information in subsequent steps; +- uses the codec information from the SDP m-line and associated non-OMR attribute lines as incoming codec information in subsequent steps; +- allocates an MR context with access to the IP realms, nettypes and addrtypes associated with the incoming and outgoing signalling paths, respectively, applying procedures as described in subclause 6.3, +- insert the incoming connection address and incoming port information for the media line into the remote connection address and port information for the incoming termination on the MR; +- provides to the MR the incoming codec information; +- replaces the connection address and port information for the media line in the initial SDP offer with the connection address and port information from the MR termination on the outgoing side; + +- adds to the modified initial SDP offer a visited-realm instance for the IP realm associated with the connection address and port information for the media line in the modified SDP offer, including the incoming codec; and +- computes a checksum value for the media line as described in subclause 5.3.4 and adds the "omr-m-cksum" and "omr-s-cksum" attributes for the media line The "omr-s-cksum" attribute is set to "0" since there are no session attributes to compute the checksum on.. + +The IBCF-2 forwards the INVITE request to the intermediate IMS CN subsystem entities in IP realm "Yb.operatorY.net" according to TS 24.229 [4]. + +None of the intermediate IMS CN subsystem entities manipulated with the initial SDP offer but the identity of [user\\_B@operator\\_Y.net](#) in the Request-URI is change to the contact address, i.e. UE-B@operatorX.net. + +The intermediate IMS CN subsystem entities select an IBCF, IBCF-3, and forward the INVITE request with the initial SDP offer to the IBCF-3 according to TS 24.229 [4]. + +**Table A.3.2-4: SIP INVITE request (IBCF-2 to IBCF-3 via intermediate IMS CN subsystem entities)** + +``` +INVITE SIP: sip:UE-B@operatorX.net; SIP/2.0 + +SIP headers according to 3GPP TS 24.229 [4] + +Content-Type: application/sdp +Content-Length: (...) + +v=0 +o=- 2987933615 2987933615 IN IP4 192.0.2.1 +s= +t=0 0 +c=IN IP4 190.1.15.2 +m=audio 11324 RTP/AVP 96 07 +a=curr:qos local none +a=curr:qos remote none +a=des:qos mandatory local sendrecv +a=des:qos none remote sendrecv +a=rtpmap:97 AMR +a=fmtp:97 mode-set=0,2,5,7; mode-change-period=2 +a=rtpmap:96 telephone-event +a=maxptime:20 +a=visited-realm:1 Xa.operatorX.net IN IP4 192.0.2.1 49170 +a=visited-realm:2 X-Y.operator.netX IN IP4 13.24.1.1 62111 +a=visited-realm:3 Yb.operatorY.net IN IP4 190.1.15.2 11324 +a=omr-m-cksum:(..) +a=omr-s-cksum:0 +``` + +#### 6. INVITE request (IBCF-3 to IBCF-4) - see example in table A.3.2-6. + +The IBCF-3 uses the procedures in subclauses 6.1.4, 6.1.7 and 6.1.9 since a previous realm instance exists that can be used to bypass a previous MR, IBCF-2, and bypass is allowed according to operator X and operator Y agreements, and the previous realm instance match the outgoing IP realm so that no local MR is required. + +The IBCF-3: + +- uses the connection address and port information for the media line in the initial SDP offer with the connection-address and port information from the selected instance 2 as incoming connection address and incoming port information for the media line; +- deletes the visited-realm instance 3; +- inserts the incoming codec information into the SDP m-line and associated attribute lines of the modified initial SDP offer; +- uses the incoming connection address as the connection address in the SDP c-line of the forwarded initial SDP offer; +- uses the incoming port information as port information in the SDP m-line of the modified initial SDP offer; and + +- computes a checksum value for the media line as described in subclause 5.3.4 and adds the "omr-m-cksum" and "omr-s-cksum" attributes for the media line. The "omr-s-cksum" attribute is set to "0" since there are no session attributes to compute the checksum on. + +The IBCF-3 then selects an IBCF, IBCF-4, in the IP realm "X.operatorX.net, Y.operatorY.net" and forwards the initial SDP offer according to TS 24.229 [4] to IBCF-4. + +**Table A.3.2-6: SIP INVITE request (IBCF-3 to IBCF-4)** + +``` +INVITE SIP: sip:UE-B@operatorX.net; SIP/2.0 + +SIP headers according to 3GPP TS 24.229 [4] + +Content-Type: application/sdp +Content-Length: (...) + +v=0 +o=- 2987933615 2987933615 IN IP4 192.0.2.1 +s= +t=0 0 +c=IN IP4 13.24.1.1 +m=audio 62111 RTP/AVP 96 07 +a=curr:qos local none +a=curr:qos remote none +a=des:qos mandatory local sendrecv +a=des:qos none remote sendrecv +a=rtpmap:97 AMR +a=fmtp:97 mode-set=0,2,5,7; mode-change-period=2 +a=rtpmap:96 telephone-event +a=maxptime:20 +a=visited-realm:1 Xa.operatorX.net IN IP4 192.0.2.1 49170 +a=visited-realm:2 X-Y.operator.net IN IP4 13.24.1.1 62111 +a=omr-m-cksum: (...) +a=omr-s-cksum: 0 +``` + +#### 7. INVITE request (IBCF-4 to P-CSCF B) - see example in table A.3.2-7. + +The IBCF-4 uses the procedures in subclauses 6.1.4, 6.1.7 and 6.1.9 since a previous realm instance exists that can be used to bypass a previous MR, IBCF-1, and the previous realm instance match the outgoing IP realm so that no local MR is required. + +The IBCF-4: + +- uses the connection address and port information for the media line in the initial SDP offer with the connection-address and port information from the selected instance 1 as incoming connection address and incoming port information for the media line; +- deletes the visited-realm instance 2; +- inserts the incoming codec information into the SDP m-line and associated attribute lines of the modified initial SDP offer; +- uses the incoming connection address as the connection address in the SDP c-line of the forwarded initial SDP offer; +- uses the incoming port information as port information in the SDP m-line of the modified initial SDP offer; and +- computes a checksum value for the media line as described in subclause 5.3.4 and adds the "omr-m-cksum" and "omr-s-cksum" attributes for the media line. The "omr-s-cksum" attribute is set to "0" since there are no session attributes to compute the checksum on. + +The IBCF-4 forwards the INVITE request with the initial SDP offer to the P-CSCF-B, in the IP realm "X.operatorX.net" according to TS 24.229 [4]. + +**Table A.3.2-7: SIP INVITE request (IBCF-4 to P-CSCF B)** + +``` + +INVITE SIP: sip:UE-B@operatorX.net; SIP/2.0 + +SIP headers according to 3GPP TS 24.229 [4] + +Content-Type: application/sdp +Content-Length: (...) + +v=0 +o=- 2987933615 2987933615 IN IP4 192.0.2.1 +s= +t=0 0 +c=IN IP4 192.0.2.1 +m=audio 49170 RTP/AVP 96 97 +a=curr:qos local none +a=curr:qos remote none +a=des:qos mandatory local sendrecv +a=des:qos none remote sendrecv +a=rtpmap:97 AMR +a=fmtp:97 mode-set=0,2,5,7; mode-change-period=2 +a=rtpmap:96 telephone-event +a=maxptime:20 +a=visited-realm:1 Xa.operatorX.net IN IP4 192.0.2.1 49170 +a=omr-m-cksum:(..) +a=omr-s-cksum:0 + +``` + +#### **8. INVITE request (P-CSCF to UE-B) - see example in table A.3.2-8.** + +The P-CSCF-B uses the procedures in subclauses 6.1.5, 6.1.7 and 6.1.9 since no previous realm instance offers an opportunity to bypass an MR and no local MR is required to match the incoming realm to the outgoing realm. + +- uses the connection-address from the SDP c-line as incoming connection-address; +- uses the port information from the SDP m-line as incoming port information; +- uses the codec information from the SDP m-line and associated non-OMR attribute lines as incoming codec information; and +- according to the local policy, deletes the visited-realm "visited-realm:1 Xa.operatorX.net IN IP4 192.0.2.1 49170", the "omr-m-cksum:(...)" and the "omr-s-cksum=:0" attributes from the SDP offer. + +The P-CSCF-B forwards the INVITE request with the initial SDP offer to the UE-B according to TS 24.229 [4]. + +**Table A.3.2-8: SIP INVITE request (P-CSCF to UE-B)** + +``` + +INVITE SIP: sip:UE-B@operatorX.net; SIP/2.0 + +SIP headers according to 3GPP TS 24.229 [4] + +Content-Type: application/sdp +Content-Length: (...) + +v=0 +o=- 2987933615 2987933615 IN IP4 192.0.2.1 +s= +t=0 0 +c=IN IP4 192.0.2.1 +m=audio 49170 RTP/AVP 96 97 +a=curr:qos local none +a=curr:qos remote none +a=des:qos mandatory local sendrecv +a=des:qos none remote sendrecv +a=rtpmap:97 AMR +a=fmtp:97 mode-set=0,2,5,7; mode-change-period=2 +a=rtpmap:96 telephone-event +a=maxptime:20 + +``` + +#### **9. 183 (Session Progress) response (UE-B to P-CSCF-B) - see example in table A.3.2-9.** + +The UE accepts the codec and sends a 183 (Session Progress) response with an initial SDP answer indicating that resources are not yet available to P-CSCF-B according to TS 24.229 [4]. + +**Table A.3.2-9: 183 (Session Progress) response (UE-B to P-CSCF-B)** + +``` + +SIP/2.0 183 Session Progress + +SIP headers according to 3GPP TS 24.229 [4] + +Content-Type: application/sdp +Content-Length: (...) + +v=0 +o=- 2987933615 2987933615 IN IP4 192.0.2.1 +s=- +c=IN IP4 192.0.2.4 +t=0 0 +m=audio 16511 RTP/AVP 97 98 +a=curr:qos local none +a=curr:qos remote none +a=des:qos mandatory local sendrecv +a=des:qos none remote sendrecv +a=rtpmap:98 AMR +a=fmtp:98 mode-set=0,2,5,7; mode-change-period=2 +a=rtpmap:97 telephone-event +a=maxptime:20 + +``` + +#### **10. 183 (Session Progress) response (P-CSCF-B to IBCF-4) - see example in table A.3.2-9** + +The P-CSCF-B uses the procedures in subclauses 6.2.7 and 6.2.9 since the connection address is valid and no primary local MR was allocated. + +The P-CSCF-B:- does not modify the initial SDP answer and forwards the 183 (Session Progress) response with the initial SDP answer to IBCF-4 according to TS 24.229 [4]. + +#### **11. 183 (Session Progress) response (IBCF-4 to IBCF-3) - see example in table A.3.2-11** + +The IBCF-4 uses the procedures in subclause 6.2.7 and 6.2.9 since the connection address is valid and no primary local MR was allocated. + +The IBCF-4: + +- copies into the media line of the initial SDP answer the visited-realm instance 1 from the media line of the received initial SDP offer that was used to populate the connection address and port information in the forwarded initial SDP offer, replacing the connection-address and port information in the instance with the connection address and port information from the received initial SDP answer; and +- replaces the connection address information in the initial SDP answer with the unspecified IPv4 address. + +The IBCF-4 forwards the 183 (Session Progress) response with the initial SDP answer to IBCF-3 according to TS 24.229 [4]. + +**Table A.3.2-11 183 (Session Progress) response (IBCF-4 to IBCF-3)** + +``` + +SIP/2.0 183 Session Progress +SIP headers according to 3GPP TS 24.229 [4] + +Content-Type: application/sdp +Content-Length: (...) + +v=0 +o=- 2987933615 2987933615 IN IP4 192.0.2.1 +s=- +c=IN IP4 0.0.0.0 +t=0 0 +m=audio 16511 RTP/AVP 97 98 +a=curr:qos local none +a=curr:qos remote sendrecv +a=des:qos mandatory local sendrecv +a=des:qos none remote sendrecv +a=rtpmap:98 AMR +a=fmtp:98 mode-set=0,2,5,7; mode-change-period=2 +a=rtpmap:97 telephone-event +a=maxptime:20 +a=visited-realm:1 Xa.operatorX.net IN IP4 192.0.2.4 16511 + +``` + +#### 12-13. 183 (Session Progress) response (IBCF-3 to IBCF-2 via intermediate IMS CN subsystem entities) - see example in table A.3.2-11 + +The IBCF-3 uses the procedures in subclauses 6.2.5 and 6.2.9 since the initial SDP answer contained an unspecified connection address and a realm instance matching one in the received initial SDP offer and since no primary local MR was allocated. + +The IBCF-3 does not modify the initial SDP answer since the visited-realm instance does not match the information in the initial SDP offer. + +The IBCF-3 then forwards the 183 (Session Progress) response with the initial SDP answer to intermediate IMS CN subsystem entities according to TS 24.229 [4]. + +The intermediate IMS CN subsystem entities do not modify the initial SDP answer and forwards the 183 (Session Progress) response with the initial SDP answer to IBCF-2 according to TS 24.229 [4]. + +#### 14. 183 (Session Progress) response (IBCF-2 to IBCF-1) - see example in table A.3.2-11 + +The IBCF-2 uses the procedures in subclauses 6.2.5 and 6.2.9 since the initial SDP answer contained an unspecified connection address and a realm instance matching one in the received initial SDP offer and the local MR allocated in step 4 can be bypassed. + +The IBCF does not modify the initial SDP answer since the visited-realm instance does not match the information in the initial SDP offer. + +The IBCF-2 forwards the 183 (Session Progress) response with the initial SDP answer to IBCF-1 according to TS 24.229 [4]. + +The IBCF-2 retains the primary local MR allocated in step 4, until it is no longer potentially needed for this and any other forked dialog. + +#### 15. 183 (Session Progress) response (IBCF-1 to P-CSCF-A) - see example in table A.3.2-15 + +The IBCF-1 uses the procedures in subclauses 6.2.5 and 6.2.8 since the initial SDP answer contained an unspecified connection address and a realm instance matching one in the received initial SDP offer and the local MR allocated in step 3 can be bypassed. + +The IMS-ALG: + +- replaces the connection address and port information for the media line in the initial SDP answer with the connection address and port information from the visited-realm instance in the received initial SDP answer. + +The IBCF-1 forwards the 183 (Session Progress) response with the initial SDP answer to P-CSCF-A according to TS 24.229 [4]. + +The IBCF-1 retains the primary local MR allocated in step 3, until it is no longer potentially needed for this and any other forked dialog. + +**Table A.3.2-15: 183 (Session Progress) response (IBCF-1 - P-CSCF-A)** + +``` +SIP/2.0 183 Session Progress + +SIP headers according to 3GPP TS 24.229 [4] + +Content-Type: application/sdp +Content-Length: (...) + +v=0 +o=- 2987933615 2987933615 IN IP4 192.0.2.1 +s=- +c=IN IP4 192.0.2.4 +t=0 0 +m=audio 16511 RTP/AVP 97 98 +a=curr:qos local none +a=curr:qos remote sendrecv +a=des:qos mandatory local sendrecv +a=des:qos none remote sendrecv +a=rtpmap:98 AMR +a=fmtp:98 mode-set=0,2,5,7; mode-change-period=2 +a=rtpmap:97 telephone-event +a=maxptime:20 +``` + +#### **16. 183 (Session Progress) response (P-CSCF-A to UE-A) - see example in table A.3.2-15** + +The P-CSCF-A: + +- forwards the 183 (Session Progress) with the initial SDP answer to the UE-A according to TS 24.229 [4] ; and +- deletes the visited-realm instance according to local policy. + +#### **17-24. PRACK request (UE-A to UE-B via P-CSCF-A, IBCF-1, IBCF-2, intermediate IMS CN subsystem entities, IBCF-3, IBCF-4 and P-CSCF-B).** + +The UE-A acknowledge the reception of the initial SDP answer and the 183 (Session Progress) response by means of a PRACK request. + +#### **25-32. 200 (OK) response to the PRACK request (UE-B to UE-A via P-CSCF-B, IBCF-4, IBCF-3, intermediate IMS CN subsystem entities, IBCF-2, IBCF-1 and P-CSCF-A).** + +The UE-B acknowledges the reception of the PRACK request by means of a 200 (OK) response. + +#### **33. UPDATE request (UE-A to P-CSCF-A) - see example in table A.3.2-33.** + +When the UE-A has got resources reserved the UE-A sends an UPDATE request. + +The subsequent SDP offer in the UPDATE the request is the same as the initial SDP offer in the INVITE request in the step 1 with the only exception that "a=curr:qos local none" is now changed to "a=curr:qos local sendrecv". + +**Table A.3.2-33: UPDATE request (UE-A to P-CSCF-A)** + +``` + +UPDATE SIP: sip:UE-A@operatorX.net; SIP/2.0 + +SIP headers according to 3GPP TS 24.229 [4] +Content-Type: application/sdp +Content-Length: (...) + +v=0 +o=- 2987933615 2987933616 IN IP4 192.0.2.4 +s=- +c=IN IP4 192.0.2.1 +t=0 0 +m=audio 16511 RTP/AVP 97 98 +a=curr:qos local sendrecv +a=curr:qos remote none +a=des:qos mandatory local sendrecv +a=des:qos none remote sendrecv +a=rtpmap:98 AMR +a=fmtp:98 mode-set=0,2,5,7; mode-change-period=2 +a=rtpmap:97 telephone-event +a=maxptime:20 + +``` + +#### **34-40. UPDATE request (P-CSCF-A to UE-B via IBCF-1, IBCF-2, intermediate IMS CN subsystem entities, IBCF-3, IBCF-4 and P-CSCF-B).** + +- 34) When the P-CSCF-A receives the UPDATE request, the P-CSCF-A forwards the UPDATE request without modifying the subsequent SDP offer. +- 35) When the IBCF-1 receives the UPDATE request, the IBCF-1 forwards the UPDATE request without modifying the subsequent SDP offer. +- 36) When the IBCF-2 receives the UPDATE request, the IBCF-2 forwards the UPDATE request without modifying the subsequent SDP offer. +- 37) Intermediate IMS CN subsystem entities do not manipulate the SDP offer. +- 38) When the IBCF-3 receives the UPDATE request, the IBCF-3 forwards the UPDATE request without modifying the subsequent SDP offer. +- 39) When the IBCF-4 receives the UPDATE request, the IBCF-4 forwards the UPDATE request without modifying the subsequent SDP offer. +- 40) When the P-CSCF-B receives the UPDATE request, the P-CSCF-B forwards the UPDATE request without modifying the subsequent SDP offer. + +#### **41. 200 (OK) response to the UPDATE request (UE-B to P-CSCF-B) - see example in table A.3.2-41.** + +The UE-B acknowledges the reception of the UPDATE request by means of a 200 (OK) response containing a subsequent SDP answer. + +**Table A.3.2-41: 200 (OK) response to the UPDATE request (UE-B to P-CSCF-B).** + +``` + +SIP/2.0 200 OK +Via: +To: ; tag=171828 +From: ; tag=543210 +Call-ID: cb03a0s09a2sdfglkj490237 +CSeq: +P-Preferred-Identity: +Contact: sip:UE-B@operatorX.net;gr=urn:uuid:354faf-7dad-22a1-b123-8a0d21f676f +Allow: +Content-Type: application/sdp +Content-Length: (...) + +v=0 +o=- 2987933615 2987933615 IN IP4 192.0.2.4 +s= +t=0 0 +c=IN IP4 192.0.2.4 +m=audio 49170 RTP/AVP 97 98 +a=curr:qos local sendrecv +a=curr:qos remote sendrecv +a=des:qos mandatory local sendrecv +a=des:qos none remote sendrecv +a=rtpmap:97 AMR +a=fmtp:97 mode-set=0,2,5,7; mode-change-period=2 +a=rtpmap:96 telephone-event +a=maxptime:20 + +``` + +#### **42-48. 200 (OK) response to the UPDATE request (P-CSCF-B to UE-A via IBCF-4, IBCF-3, intermediate IMS CN subsystem entities, IBCF-2 and IBCF-1).** + +- 42) When P-CSCF-B receives the 200 (OK) response to the UPDATE request, the P-CSCF-B forwards the response without modifying the subsequent SDP answer. +- 43) When IBCF-4 receives the 200 (OK) response to the UPDATE request, the IBCF-4 forwards the response without modifying the subsequent SDP answer. +- 44) When IBCF-3 receives the 200 (OK) response to the UPDATE request, the IBCF-3 forwards the response without modifying the subsequent SDP answer. +- 45) The intermediate IMS CN subsystem entities do not manipulate the SDP answer. +- 46) When IBCF-2 receives the 200 (OK) response to the UPDATE request, the IBCF-2 forwards the response without modifying the subsequent SDP answer. +- 47) When IBCF-1 receives the 200 (OK) response to the UPDATE request, the IBCF-1 forwards the response without modifying the subsequent SDP answer. +- 48) When P-CSCF-A receives the 200 (OK) response to the UPDATE request, the P-CSCF-A forwards the response without modifying the subsequent SDP answer. + +#### **49-56. 180 (Ringing) response (UE-B to UE-A via P-CSCF-B, IBCF-4, IBCF-3, intermediate IMS CN subsystem entities, IBCF-2, IBCF-1 and P-CSCF-A).** + +No OMR specific action is required. + +#### **57-64. 200 (OK) response to the INVITE request (UE-B to UE-A via P-CSCF-B, IBCF-4, IBCF-3, intermediated IMS CN subsystem, IBCF-2, IBCF-1 and P-CSCF-A).** + +The User B accepts the call and the UE-B sends a 200 (OK) response to the INVITE request. No OMR specific action is required. + +#### **65-72. ACK request (UE-A to UE-B via P-CSCF-A, IBCF-1, IBCF-2, intermediated IMS CN subsystem, IBCF-3, IBCF-4 and P-CSCF-B).** + +The UE-B acknowledges the reception of the 200 (OK) response by means of a 200 (OK) response. + +## A.4 IMS-ALG allocates a local transcoding MR when performing proactive transcoding without resource reservation + +### A.4.1 General + +This subclause provides an example of a call where a transcoding MR adds the AMR codec to the initial SDP offer without MR allocation. + +The UE selects the added codec and the IMS-ALG needs to reserve MR and send an UPDATE request with the IP address and port number of the allocated MR. + +The IMS-ALG is transcoding between the AMR-WB codec and the AMR codec when the call is established. + +Figure A.4.1-1 shows the realm and IP structure used in this example. + +![Diagram of IP realm and IP structure showing Home IMS network H, IPX network X, and Visited network V with various network elements like S-CSCF, IBCF, TrGW, IC, MGW, P-CSCF, PCRF, PDN GW, TRF, and UE-A.](e94cbc0895c6914a2bb53f150ab7495e_img.jpg) + +The diagram illustrates the IP realm and IP structure across three networks: + + +- Home IMS network H:** Realm Ha.operatorH.net. Contains S-CSCF/BGCF, IBCF-2 (Ha: 190.1.15.2), TrGW (Xa4: 179.14.1.2), IBCF-3 (Ha: 190.1.15.2), and TrGW (Xa4: 179.14.1.3). +- IPX network X:** Realm Xa.operatorX.net. Contains IC-1 (Xa2: 179.14.1.1), MGW (Xa2: 178.15.1.2), IC-2 (Xa2: 179.14.1.4), and MGW (Xa2: 178.15.1.3). +- Visited network V:** Realm Va.operatorV.net. Contains UE-A (Va: 192.0.2.1), P-CSCF-A, PCRF, PDN GW, IBCF-1 (Xa1: 178.15.1.1), TrGW (192.0.2.2), IBCF-4 (Xa1: 178.15.1.4), TrGW (192.0.2.3), TRF, IBCF-5 (Va: 192.0.2.4), and TrGW. + + Signaling paths (solid lines) connect UE-A to P-CSCF-A, then through IBCF-1, IBCF-2, IBCF-3, IBCF-4, TRF, and IBCF-5. Media paths (dashed lines) connect UE-A to PDN GW, then through IBCF-1, IBCF-2, IBCF-3, IBCF-4, TRF, and IBCF-5. + +Diagram of IP realm and IP structure showing Home IMS network H, IPX network X, and Visited network V with various network elements like S-CSCF, IBCF, TrGW, IC, MGW, P-CSCF, PCRF, PDN GW, TRF, and UE-A. + +Figure A.4.1-1: IP realm and IP structure + +### A.4.2 Message flow + +The user A at UE-A and the user B at UE-B are roaming into a visited network X and both users belong to the same operator Y. + +Preconditions: + +- Both user A and B are registered to the Home IMS network Y via the visited operator X network; +- the visited operator X and the operator Y have an agreement to allow media to be bypassed using OMR; +- both user A and B are connected to the realm "Xa.operatorX.net" of the visited operator network X; + +- the AMR-WB codec is allowed and accepted by all involved entities. However, the local policy of operator X is that the AMR codec shall always be included in the initial SDP offer from a UE in the operator X network; and +- no B2BUA manipulating SDP is connected in the intermediate IM CN subsystem. + +Figure A.4.2-1 shows the message flow for the scenario. + +![Sequence diagram showing message flow for proactive transcoding without resource reservation. The diagram spans three network domains: Visited network X (left), Home IMS network Y (center), and Visited network X (right). Entities involved are UE-A, P-CSCF A, IBCF-1, IBCF-2, Intermediate IM CN subsystem entities X, IBCF-3, IBCF-4, P-CSCF B, and UE-B. The flow shows SIP messages (INVITE, 183, PRACK, 200 OK, UPDATE, 180, 200 OK (INVITE), ACK) being passed through various network elements. SDP details include codec preferences (AMR-WB, AMR) and visited realm information. A final summary at the bottom shows the active codecs: AMR-WB between UE-A and IBCF-1, and AMR between IBCF-1 and UE-B.](e05122559f56af5699789b7118d8fe87_img.jpg) + +The diagram illustrates the message flow for proactive transcoding without resource reservation across three network domains: Visited network X (left), Home IMS network Y (center), and Visited network X (right). The entities involved are UE-A, P-CSCF A, IBCF-1, IBCF-2, Intermediate IM CN subsystem entities X, IBCF-3, IBCF-4, P-CSCF B, and UE-B. The flow consists of the following steps: + +1. INVITE [AMR-WB, c=192.0.2.1] from UE-A to P-CSCF A. +2. INVITE [AMR-WB, c=192.0.2.1] from P-CSCF A to IBCF-1. +3. INVITE [AMR-WB and AMR, c=192.0.2.5, visited-realm:1 Xa 192.0.2.1, visited-realm:2 Xa 192.0.2.5 AMR-WB] from IBCF-1 to IBCF-2. +4. INVITE [AMR-WB and AMR, c=190.1.15.2, visited-realm:1 Xa 192.0.2.1, visited-realm:2 Xa 192.0.2.5 AMR-WB, visited-realm:3 Yb 190.1.15.2] from IBCF-2 to Intermediate IM CN subsystem entities X. +5. INVITE [AMR-WB and AMR, c=190.1.15.2, visited-realm:1 Xa 192.0.2.1, visited-realm:2 Xa 192.0.2.5 AMR-WB, visited-realm:3 Yb 190.1.15.2] from Intermediate IM CN subsystem entities X to IBCF-3. +6. INVITE [AMR-WB and AMR, c=192.0.2.5, visited-realm:1 Xa 192.0.2.1, visited-realm:2 Xa 192.0.2.5 AMR-WB] from IBCF-3 to IBCF-4. +7. INVITE [AMR-WB and AMR, c=192.0.2.5, visited-realm:1 Xa 192.0.2.1, visited-realm:2 Xa 192.0.2.5 AMR-WB] from IBCF-4 to P-CSCF B. +8. INVITE [AMR-WB and AMR, c=192.0.2.5] from P-CSCF B to UE-B. +9. 183 [AMR, c=192.0.2.4] from UE-B to P-CSCF B. +10. 183 [AMR, c=192.0.2.4] from P-CSCF B to IBCF-4. +11. 183 [AMR, c=0.0.0.0, visited-realm:2 Xa 192.0.2.4] from IBCF-4 to IBCF-3. +12. 183 [AMR, c=0.0.0.0, visited-realm:2 Xa 192.0.2.4] from IBCF-3 to Intermediate IM CN subsystem entities X. +13. 183 [AMR, c=0.0.0.0, visited-realm:2 Xa 192.0.2.4] from Intermediate IM CN subsystem entities X to IBCF-2. +14. 183 [AMR, c=192.0.2.4, visited-realm:2 Xa 192.0.2.4] from IBCF-2 to IBCF-1. +15. PRACK [AMR and AMR-WB, c=192.0.2.5, visited-realm:2 Xa 192.0.2.5] from IBCF-1 to P-CSCF A. +16. PRACK [AMR and AMR-WB, c=190.1.15.2, visited-realm:2 Xa 192.0.2.5, visited-realm:3 Yb 190.1.15.2] from IBCF-2 to Intermediate IM CN subsystem entities X. +17. PRACK [AMR and AMR-WB, c=190.1.15.2, visited-realm:2 Xa 192.0.2.5, visited-realm:3 Yb 190.1.15.2] from Intermediate IM CN subsystem entities X to IBCF-3. +18. PRACK [AMR and AMR-WB, c=192.0.2.5, visited-realm:2 Xa 192.0.2.5] from IBCF-3 to IBCF-4. +19. PRACK [AMR and AMR-WB, c=192.0.2.5, visited-realm:2 Xa 192.0.2.5] from IBCF-4 to P-CSCF B. +20. PRACK [AMR and AMR-WB, c=192.0.2.5] from P-CSCF B to UE-B. +21. 200 OK (PRACK) [AMR, c=192.0.2.4] from UE-B to P-CSCF B. +22. 200 OK (PRACK) [AMR, c=192.0.2.4] from P-CSCF B to IBCF-4. +23. 200 OK (PRACK) [AMR, c=192.0.2.4] from IBCF-4 to IBCF-3. +24. 200 OK (PRACK) [AMR, c=0.0.0.0, visited-realm:2 Xa 192.0.2.4] from IBCF-3 to Intermediate IM CN subsystem entities X. +25. 200 OK (PRACK) [AMR, c=0.0.0.0, visited-realm:2 Xa 192.0.2.4] from Intermediate IM CN subsystem entities X to IBCF-2. +26. 200 OK (PRACK) [AMR, c=192.0.2.4, visited-realm:2 Xa 192.0.2.4] from IBCF-2 to IBCF-1. +27. 183 [AMR-WB, c=192.0.2.2] from IBCF-1 to P-CSCF A. +28. 183 [AMR-WB, c=192.0.2.2] from P-CSCF A to UE-A. +29. PRACK from UE-A to P-CSCF A. +30. PRACK from P-CSCF A to IBCF-1. +31. 200 OK (PRACK) from IBCF-1 to P-CSCF A. +32. 200 OK (PRACK) from P-CSCF A to UE-A. +33. UPDATE [AMR-WB, c=192.0.2.1] from UE-A to P-CSCF A. +34. UPDATE [AMR-WB, c=192.0.2.1] from P-CSCF A to IBCF-1. +35. UPDATE [AMR, c=192.0.2.5] from IBCF-1 to IBCF-2. +36. UPDATE [AMR, c=192.0.2.5] from IBCF-2 to Intermediate IM CN subsystem entities X. +37. UPDATE [AMR, c=192.0.2.5] from Intermediate IM CN subsystem entities X to IBCF-3. +38. UPDATE [AMR, c=192.0.2.5] from IBCF-3 to IBCF-4. +39. UPDATE [AMR, c=192.0.2.5] from IBCF-4 to P-CSCF B. +40. UPDATE [AMR, c=192.0.2.5] from P-CSCF B to UE-B. +41. 200 OK (UPDATE) [AMR, c=192.0.2.4] from UE-B to P-CSCF B. +42. 200 OK (UPDATE) [AMR, c=192.0.2.4] from P-CSCF B to IBCF-4. +43. 200 OK (UPDATE) [AMR, c=192.0.2.4] from IBCF-4 to IBCF-3. +44. 200 OK (UPDATE) [AMR, c=192.0.2.4] from IBCF-3 to Intermediate IM CN subsystem entities X. +45. 200 OK (UPDATE) [AMR, c=192.0.2.4] from Intermediate IM CN subsystem entities X to IBCF-2. +46. 200 OK (UPDATE) [AMR, c=192.0.2.4] from IBCF-2 to IBCF-1. +47. 200 OK (UPDATE) [AMR-WB, c=192.0.2.5] from IBCF-1 to P-CSCF A. +48. 200 OK (UPDATE) [AMR-WB, c=192.0.2.5] from P-CSCF A to UE-A. +49. 180 from UE-B to P-CSCF B. +50. 180 from P-CSCF B to IBCF-4. +51. 180 from IBCF-4 to IBCF-3. +52. 180 from IBCF-3 to Intermediate IM CN subsystem entities X. +53. 180 from Intermediate IM CN subsystem entities X to IBCF-2. +54. 180 from IBCF-2 to IBCF-1. +55. 180 from IBCF-1 to P-CSCF A. +56. 180 from P-CSCF A to UE-A. +57. 200 OK (INVITE) from UE-B to P-CSCF B. +58. 200 OK (INVITE) from P-CSCF B to IBCF-4. +59. 200 OK (INVITE) from IBCF-4 to IBCF-3. +60. 200 OK (INVITE) from IBCF-3 to Intermediate IM CN subsystem entities X. +61. 200 OK (INVITE) from Intermediate IM CN subsystem entities X to IBCF-2. +62. 200 OK (INVITE) from IBCF-2 to IBCF-1. +63. 200 OK (INVITE) from IBCF-1 to P-CSCF A. +64. 200 OK (INVITE) from P-CSCF A to UE-A. +65. ACK from UE-A to P-CSCF A. +66. ACK from P-CSCF A to IBCF-1. +67. ACK from IBCF-1 to IBCF-2. +68. ACK from IBCF-2 to Intermediate IM CN subsystem entities X. +69. ACK from Intermediate IM CN subsystem entities X to IBCF-3. +70. ACK from IBCF-3 to IBCF-4. +71. ACK from IBCF-4 to P-CSCF B. +72. ACK from P-CSCF B to UE-B. + +At the bottom of the diagram, a summary indicates the active codecs: AMR-WB between UE-A and IBCF-1, and AMR between IBCF-1 and UE-B. + +Sequence diagram showing message flow for proactive transcoding without resource reservation. The diagram spans three network domains: Visited network X (left), Home IMS network Y (center), and Visited network X (right). Entities involved are UE-A, P-CSCF A, IBCF-1, IBCF-2, Intermediate IM CN subsystem entities X, IBCF-3, IBCF-4, P-CSCF B, and UE-B. The flow shows SIP messages (INVITE, 183, PRACK, 200 OK, UPDATE, 180, 200 OK (INVITE), ACK) being passed through various network elements. SDP details include codec preferences (AMR-WB, AMR) and visited realm information. A final summary at the bottom shows the active codecs: AMR-WB between UE-A and IBCF-1, and AMR between IBCF-1 and UE-B. + +**Figure A.4.2-1: Message flow for proactive transcoder without resource reservation** + +NOTE: For clarity, the SIP 100 (Trying) messages are not shown in the signalling flow. + +The steps of the flow are as follows: + +#### **1. INVITE request (UE-A to P-CSCF-A) - see example in table A.4.2-1.** + +The UE-A sends a SIP INVITE request according to TS 24.229 [4]. The INVITE request includes an initial SDP offer proposing the use of the AMR-WB codec and inband DTMF. + +**Table A.4.2-1: SIP INVITE request (UE-A to P-CSCF-A)** + +``` + +INVITE SIP: user_B@operator_Y.net; SIP/2.0 + +SIP headers according to 3GPP TS 24.229 [4] + +Content-Type: application/sdp +Content-Length: (...) + +v=0 +o= 2987933615 2987933615 IN IP4 192.0.2.1 +s= +b=AS:30 +b=RS:0 +b=RR:2000 +c=IN IP4 192.0.2.1 +m=audio 49170 RTP/AVP 96 97 +a=curr:qos local none +a=curr:qos remote none +a=des:qos mandatory local sendrecv +a=des:qos none remote sendrecv +a=rtpmap:96 telephone-event +a=rtpmap:97 AMR-WB/16000/1 +a=fmtp:97 mode-change-capability=2; max-red=220 +a=ptime:20 +a=maxptime:240 + +``` + +#### 2. INVITE request (P-CSCF-A to IBCF-1) - see example in table A.4.2-1. + +The P-CSCF-A uses the procedures in subclauses 6.1.5, 6.1.7 and 6.1.9 since no MR could be bypassed and no MR is allocated. + +The P-CSCF-A: + +- uses the connection-address from the SDP c-line as incoming connection-address; +- uses the port information from the SDP m-line as incoming port information; +- uses the codec information from the SDP m-line; +- inserts the incoming codec information into the SDP m-line and associated attribute lines of the modified initial SDP offer; +- uses the incoming connection address as the connection address in the SDP c-line of the forwarded initial SDP offer, and +- uses the incoming port information as port information in the SDP m-line of the modified initial SDP offer. + +The P-CSCF-A then selects an IBCF, IBCF-1, in the realm "Xa.operatorX.net" and forwards the INVITE request with the initial SDP offer to the IBCF-1 according to TS 24.229 [4]. + +#### 3. INVITE request (IBCF-1 to IBCF-2) - see example in table A.4.2-3 + +The IBCF-1 uses the procedures in subclauses 6.1.5, 6.1.7 and 6.1.9 since no previous realm instance offers an opportunity to bypass a previous MR and a local MR is not required for realm matching. The IBCF-1 has access to a transcoding MR. + +The IBCF-1: + +- uses the connection-address from the SDP c-line as incoming connection-address; +- uses the port information from the SDP m-line as incoming port information; +- uses the codec information from the SDP m-line; +- constructs and adds to the modified initial SDP offer a visited-realm instance 1 for the media line associated with the connection address and port information for the media line in the received initial SDP offer; + +- makes the codec changes to incoming codec information according to local policy, taking into account the procedures in clause 5.4, and inserts the AMR codec information into the SDP m-line and associated attribute lines of the modified initial SDP offer; +- adds to the modified initial SDP offer a visited-realm instance 2 with the same IP realm, connection address and port information as in the previous visited-realm instance 1 for the media line including the incoming codec information; and +- computes a checksum value for the media line as described in subclause 5.6.3 and adds omr-m-cksum and omr-s-cksum attributes for the media line. The omr-s-cksum is set to "0" since there are no session line attributes left to calculate the checksum on. + +The IBCF-1 then selects an IBCF, IBCF-2, in the realm "Xa.operatorX.net" and forwards the INVITE request with the initial SDP offer to the IBCF-2 according to TS 24.229 [4]. + +**Table A.4.2.2-3: SIP INVITE request (IBCF-1 to IBCF-2)** + +``` +INVITE SIP: user_B@operator_Y.net; SIP/2.0 + +SIP headers according to 3GPP TS 24.229 [4] + +Content-Type: application/sdp +Content-Length: (...) + +v=0 +o= 2987933615 2987933615 IN IP4 192.0.2.1 +s= +c=IN IP4 192.0.2.5 +m=audio 49170 RTP/AVP 96 97 98 +a=curr:qos local none +a=curr:qos remote none +a=des:qos mandatory local sendrecv +a=des:qos none remote sendrecv +a=rtpmap:96 telephone-event +a=rtpmap:97 AMR-WB/16000/1 +a=fmtp:97 mode-change-capability=2; max-red=220 +a=rtpmap:98 AMR/8000/1 +a=fmtp:98 mode-change-capability=2; max-red=220; octet-align=1 +a=ptime:20 +a=maxptime:240 +b=AS:30 +b=RS:0 +b=RR:2000 +a=visited-realm:1 Xa.operatorX.net IN IP4 192.0.2.1 49170 +a=visited-realm:2 Xa.operatorX.net IN IP4 192.0.2.5 49170 +a=omr-codecs:2 audio RTP/AVP 96 97 +a=omr-m-att:2 rtpmap:96 telephone-event +a=omr-m-att:2 rtpmap:97 AMR-WB/16000/1 +a=omr-m-att:2 fmtp:97 mode-change-capability=2; max-red=220 +a=omr-m-att:2 curr:qos local none +a=omr-m-att:2 curr:qos remote none +a=omr-m-att:2 des:qos mandatory local sendrecv +a=omr-m-att:2 des:qos none remote sendrecv +a=omr-m-att:2 ptime:20 +a=omr-m-att:2 maxptime:240 +a=omr-s-bw:2 AS:30 +a=omr-s-bw:2 RS:0 +a=omr-s-bw:2 RR:2000 +a=omr-m-cksum:(..) +a=omr-s-cksum:0 +``` + +#### 4-5. INVITE request (IBCF-2 to IBCF-3 via intermediate IMS CN subsystem entities) - see example in table A.4.2-4. + +The IBCF-2 uses the procedure in subclauses 6.1.5, 6.1.6 and 6.1.9 since no realm instance offers an opportunity to bypass a previous MR and a local MR is required for realm matching. + +The IBCF-2: + +- uses the connection-address from the SDP c-line as incoming connection-address; +- uses the port information from the SDP m-line as incoming port information; + +- uses the codec information from the SDP m-line and associated non-OMR attribute lines as incoming codec information; +- allocates an MR context with access to the IP realms, nettypes and addrtypes associated with the incoming connection address and port information and outgoing signalling paths, respectively, applying procedures as described in subclause 6.3; +- insert the incoming connection address and incoming port information for the media line into the remote connection address and port information for the incoming termination on the MR; +- provides to the MR the incoming codec information; +- replaces the connection address and port information for the media line in the initial SDP offer with the connection address and port information from the MR termination on the outgoing side; +- adds to the modified initial SDP offer a visited-realm instance 3 for the IP realm associated with the connection address and port information for the media line in the modified initial SDP offer; +- computes a checksum value for the media line as described in subclause 5.6.3 and adds the omr-m-cksum and omr-s-cksum attributes for the media line. The omr-s-cksum attribute is set to "0" since there are no session line attributes to compute the checksum on; and +- forwards the INVITE request to the intermediate IMS CN subsystem entities in realm "Yb.operatorY.net" according to TS 24.229 [4]. + +None of the intermediate IMS CN subsystem entities manipulated with the initial SDP offer but the identity of [user\\_B@operator\\_Y.net](#) in the Request-URI is change to the contact address, i.e. UE-B@operatorX.net. + +The intermediate IMS CN subsystem entities select an IBCF, IBCF-3, and forward the INVITE request with the initial SDP offer to the IBCF-3 according to TS 24.229 [4]. + +**Table A.4.2-4: SIP INVITE request (IBCF-2 to IBCF-3 via intermediate IMS CN subsystem entities)** + +``` + +INVITE SIP: sip:user_B@operatorX.net; SIP/2.0 + +SIP headers according to 3GPP TS 24.229 [4] + +Content-Type: application/sdp +Content-Length: (...) + +v=0 +o=- 2987933615 2987933615 IN IP4 192.0.2.1 +s= +c=IN IP4 190.1.15.2 +m=audio 11324 RTP/AVP 96 97 98 +a=curr:qos local none +a=curr:qos remote none +a=des:qos mandatory local sendrecv +a=des:qos none remote sendrecv +a=rtpmap:96 telephone-event +a=rtpmap:97 AMR-WB/16000/1 +a=fmtp:97 mode-change-capability=2; max-red=220 +a=rtpmap:98 AMR/8000/1 +a=fmtp:98 mode-change-capability=2; max-red=220; octet-align=1 +a=ptime:20 +a=maxptime:240 +b=AS:30 +b=RS:0 +b=RR:2000 +a=visited-realm:1 Xa.operatorX.net IN IP4 192.0.2.1 49170 +a=visited-realm:2 Xa.operatorX.net IN IP4 192.0.2.5 49170 +a=omr-codecs:2 audio RTP/AVP 96 97 +a=omr-m-att:2 rtpmap:96 telephone-event +a=omr-m-att:2 rtpmap:97 AMR-WB/16000/1 +a=omr-m-att:2 fmtp:97 mode-change-capability=2; max-red=220 +a=omr-m-att:2 curr:qos local none +a=omr-m-att:2 curr:qos remote none +a=omr-m-att:2 des:qos mandatory local sendrecv +a=omr-m-att:2 des:qos none remote sendrecv +a=omr-m-att:2 ptime:20 +a=omr-m-att:2 maxptime:240 +a=omr-s-bw:2 AS:30 +a=omr-s-bw:2 RS:0 +a=omr-s-bw:2 RR:2000 +a=visited-realm:3 Yb.operatorY.net IN IP4 190.1.15.2 11324 +a=omr-m-cksum:(...) +a=omr-s-cksum:0 + +``` + +#### 6. INVITE request (IBCF-3 to IBCF-4) - see example in table A.4.2-6. + +The IBCF-3 uses the procedures in subclauses 6.1.4, 6.1.7 and 6.1.9 since a previous realm instance exists that can be used to bypass a previous MR, IBCF-2, and bypass is allowed according to operator X and operator Y agreements, and the previous realm instance match the outgoing realm so that no local MR is required. + +The IBCF-3: + +- uses the connection address and port information for the media line in the initial SDP offer with the connection-address and port information from the selected instance 2 as incoming connection address and incoming port information for the media line; +- reconstruct the associated codec information for the media line in the received initial SDP offer from the selected instance 2 as described in subclause 5.3, i.e. using the SDP a-lines, b-lines, transport format and list of media formats of the media line in the received initial SDP offer; +- deletes the visited-realm instance 3; +- inserts the incoming codec information into the SDP m-line and associated attribute lines of the modified initial SDP offer; +- uses the incoming connection address as the connection address in the SDP c-line of the forwarded initial SDP offer; +- uses the incoming port information as port information in the SDP m-line of the modified initial SDP offer; + +- computes a checksum value for the media line as described in subclause 5.6.3 and adds the omr-m-cksum and omr-s-cksum attributes for the media line. The omr-s-cksum attribute is set to "0" since there are no session line attributes to compute the checksum on; and +- selects an IBCF, IBCF-4, in the realm "Xa.operatorX.net" and forwards the initial SDP offer according to TS 24.229 [4] to IBCF-4. + +**Table A.4.2-6: SIP INVITE request (IBCF-3 to IBCF-4)** + +``` + +INVITE SIP: sip:UE-B@operatorX.net; SIP/2.0 + +SIP headers according to 3GPP TS 24.229 [4] + +Content-Type: application/sdp +Content-Length: (...) + +v=0 +o=- 2987933615 2987933615 IN IP4 192.0.2.1 +s= +c=IN IP4 192.0.2.5 +m=audio 49170 RTP/AVP 96 97 98 +a=curr:qos local none +a=curr:qos remote none +a=des:qos mandatory local sendrecv +a=des:qos none remote sendrecv +a=rtpmap:96 telephone-event +a=rtpmap:97 AMR-WB/16000/1 +a=fmtp:97 mode-change-capability=2; max-red=220 +a=rtpmap:98 AMR/8000/1 +a=fmtp:98 mode-change-capability=2; max-red=220; octet-align=1 +a=ptime:20 +a=maxptime:240 +b=AS:30 +b=RS:0 +b=RR:2000 +a=visited-realm:1 Xa.operatorX.net IN IP4 192.0.2.1 49170 +a=visited-realm:2 Xa.operatorX.net IN IP4 192.0.2.5 49170 +a=omr-codecs:2 audio RTP/AVP 96 97 +a=omr-m-att:2 rtpmap:96 telephone-event +a=omr-m-att:2 rtpmap:97 AMR-WB/16000/1 +a=omr-m-att:2 fmtp:97 mode-change-capability=2; max-red=220 +a=omr-m-att:2 curr:qos local none +a=omr-m-att:2 curr:qos remote none +a=omr-m-att:2 des:qos mandatory local sendrecv +a=omr-m-att:2 des:qos none remote sendrecv +a=omr-m-att:2 ptime:20 +a=omr-m-att:2 maxptime:240 +a=omr-s-bw:2 AS:30 +a=omr-s-bw:2 RS:0 +a=omr-s-bw:2 RR:2000 +a=omr-m-cksum:(..) +a=omr-m-cksum:0 + +``` + +#### 7. INVITE request (IBCF-4 to P-CSCF B) - see example in table A.4.2-7. + +The IBCF-4 uses the procedures in subclauses 6.1.5, 6.1.7 and 6.1.9 since a previous realm instance exists that can be used to bypass a previous MR, IBCF-1, and the previous realm instance match the outgoing realm so that no local MR is required. + +The IBCF-4: + +- uses the connection address and port information from the SDP c-line in the received initial SDP offer in the initial SDP offer as incoming connection address and incoming port information in subsequent steps; +- use the port information from the SDP m-line in the received initial SDP offer as incoming port in subsequent steps; +- uses the codec information from the SDP m-line and associated non-OMR attribute lines in the received initial SDP offer as incoming codec information in the subsequent steps; +- inserts the incoming codec information into the SDP m-line and associated attribute lines of the modified initial SDP offer; + +- uses the incoming connection address as the connection address in the SDP c-line of the forwarded initial SDP offer; and +- uses the incoming port information as port information in the SDP m-line of the modified initial SDP offer; and +- forwards the INVITE request with the unmodified initial SDP offer to the P-CSCF-B, in the realm "X.operatorX.net" according to TS 24.229 [4]. + +**Table A.4.2-7: SIP INVITE request (IBCF-4 to P-CSCF B)** + +| | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 
 INVITE SIP: sip:UE-B@operatorX.net; SIP/2.0  SIP headers according to 3GPP TS 24.229 [4]  Content-Type: application/sdp Content-Length: (...)  v=0 o=- 2987933615 2987933615 IN IP4 192.0.2.1 s= c=IN IP4 192.0.2.5 m=audio 49170 RTP/AVP 96 97 98 a=curr:qos local none a=curr:qos remote none a=des:qos mandatory local sendrecv a=des:qos none remote sendrecv a=rtpmap:96 telephone-event a=rtpmap:97 AMR-WB/16000/1 a=fmtp:97 mode-change-capability=2; max-red=220 a=rtpmap:98 AMR/8000/1 a=fmtp:98 mode-change-capability=2; max-red=220; octet-align=1 a=ptime:20 a=maxptime:240 b=AS:30 b=RS:0 b=RR:2000 a=visited-realm:1 Xa.operatorX.net IN IP4 192.0.2.1 49170 a=visited-realm:2 Xa.operatorX.net IN IP4 192.0.2.5 49170 a=omr-codecs:2 audio RTP/AVP 96 97 a=omr-m-att:2 rtpmap:96 telephone-event a=omr-m-att:2 rtpmap:97 AMR-WB/16000/1 a=omr-m-att:2 fmtp:97 mode-change-capability=2; max-red=220 a=omr-m-att:2 curr:qos local none a=omr-m-att:2 curr:qos remote none a=omr-m-att:2 des:qos mandatory local sendrecv a=omr-m-att:2 des:qos none remote sendrecv a=omr-m-att:2 ptime:20 a=omr-m-att:2 maxptime:240 a=omr-s-bw:2 AS:30 a=omr-s-bw:2 RS:0 a=omr-s-bw:2 RR:2000 a=omr-m-cksum:(..) a=omr-m-cksum:0
| +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +#### **8. INVITE request (P-CSCF to UE-B) - see example in table A.4.2-8.** + +The P-CSCF-B uses the procedures in subclauses 6.1.5, 6.1.7 and 6.1.9 since no previous realm instance offers an opportunity to bypass an MR and no local MR is required to match the incoming realm to the outgoing realm. + +- uses the connection-address from the SDP c-line as incoming connection-address; +- uses the port information from the SDP m-line as incoming port information; +- uses the codec information from the SDP m-line and associated non-OMR attribute lines as incoming codec information; +- according to the local policy, deletes all OMR attributes from the initial SDP offer; and +- forwards the INVITE request with the unmodified initial SDP offer to the UE-B according to TS 24.229 [4]. + +**Table A.4.2-8: SIP INVITE request (P-CSCF-B to UE-B)** + +``` + +INVITE SIP: sip:UE-B@operatorX.net; SIP/2.0 + +SIP headers according to 3GPP TS 24.229 [4] + +Content-Type: application/sdp +Content-Length: (...) + +v=0 +o=- 2987933615 2987933615 IN IP4 192.0.2.1 +s= +c=IN IP4 192.0.2.5 +m=audio 49170 RTP/AVP 96 97 98 +a=curr:qos local none +a=curr:qos remote none +a=des:qos mandatory local sendrecv +a=des:qos none remote sendrecv +a=rtpmap:96 telephone-event +a=rtpmap:97 AMR-WB/16000/1 +a=fmtp:97 mode-change-capability=2; max-red=220 +a=rtpmap:98 AMR/8000/1 +a=fmtp:98 mode-change-capability=2; max-red=220; octet-align=1 +a=ptime:20 +a=maxptime:240 +b=AS:30 +b=RS:0 +b=RR:2000 + +``` + +#### **9. 183 (Session Progress) response (UE-B to P-CSCF-B) - see example in table A.4.2-9.** + +The UE accepts the AMR codec and sends a 183 (Session Progress) response with an initial SDP answer indicating that resources are not yet available to P-CSCF-B according to TS 24.229 [4]. + +**Table A.4.2-9: 183 (Session Progress) response (UE-B to P-CSCF-B)** + +``` + +SIP/2.0 183 Session Progress + +SIP headers according to 3GPP TS 24.229 [4] + +Content-Type: application/sdp +Content-Length: (...) + +v=0 +o=- 2987933615 2312345678 IN IP4 192.0.2.1 +s= +c=IN IP4 192.0.2.4 +m=audio 16511 RTP/AVP 96 98 +a=curr:qos local none +a=curr:qos remote none +a=des:qos mandatory local sendrecv +a=des:qos none remote sendrecv +a=rtpmap:96 telephone-event +a=rtpmap:98 AMR/8000/1 +a=fmtp:98 mode-change-capability=2; max-red=220; octet-align=1 +a=ptime:20 +a=maxptime:240 +b=AS:30 +b=RS:0 +b=RR:2000 + +``` + +#### **10. 183 (Session Progress) response (P-CSCF-B to IBCF-4) - see example in table A.4.2-9** + +The P-CSCF-B uses the procedures in subclauses 6.2.7 and 6.2.9 since the connection address is valid and no primary local MR was allocated. + +The P-CSCF-B: + +- does not modify the initial SDP answer and forwards the 183 (Session Progress) response with the initial SDP answer to IBCF-4 according to TS 24.229 [4]. + +#### **11. 183 (Session Progress) response (IBCF-4 to IBCF-3) - see example in table A.4.2-11** + +The IBCF-4 uses procedures in subclauses 6.2.7 and 6.2.9 since a valid connection address was received in the initial SDP answer and no MR was allocated when sending the initial SDP answer. + +The IBCF-4: + +- copies into the media line of the SDP answer the visited-realm instance 2 from the media line of the received initial SDP offer that was used to populate the connection address and port information in the forwarded initial SDP offer, replacing the connection-address and port information in the instance with the connection address and port information from the received initial SDP answer; +- replaces the connection address information in the initial SDP answer with the unspecified address of IPv4, i.e. "0.0.0.0"; and +- forwards the 183 (Session Progress) response with the modified initial SDP answer according to TS 24.229 [4]. + +**Table A.4.2-11: 183 (Session Progress) response (IBCF-4 to IBCF-3)** + +``` +SIP/2.0 183 Session Progress + +SIP headers according to 3GPP TS 24.229 [4] + +Content-Type: application/sdp +Content-Length: (...) +v=0 +o=- 2987933615 2312345678 IN IP4 192.0.2.1 +s=- +c=IN IP4 0.0.0.0 +m=audio 16511 RTP/AVP 96 98 +a=curr:qos local none +a=curr:qos remote none +a=des:qos mandatory local sendrecv +a=des:qos none remote sendrecv +a=rtpmap:96 telephone-event +a=rtpmap:98 AMR/8000/1 +a=fmtp:98 mode-change-capability=2; max-red=220; octet-align=1 +a=ptime:20 +a=maxptime:240 +b=AS:30 +b=RS:0 +b=RR:2000 +a=visited-realm:1 Xa.operatorX.net IN IP4 192.0.2.4 16511 +``` + +#### 12-13. 183 (Session Progress) response (IBCF-3 to IBCF-2 via intermediate IMS CN subsystem entities) - see example in table A.4.2-11 + +The IBCF-3 uses procedures in subclauses 6.2.5 and 6.2.9 since an unspecified connection address and a visited-realm was received. + +The IBCF-3 forwards the 183 (Session Progress) response with the unmodified initial SDP answer to the intermediate IM CN subsystem entities according to TS 24.229 [4]. + +The intermediate IM CN subsystem entities forward without modification the 183 (Session Progress) response to the IBCF-2 according to TS 24.229 [4]. + +#### 14. 183 (Session Progress) response (IBCF-2 to IBCF-1) - see example in table A.4.2-14 + +The IBCF-2 uses the procedures in subclauses 6.2.5 and 6.2.9 since the initial SDP answer contained an unspecified connection address and a realm instance matching one in the received initial SDP offer and the local MR allocated in step 4 can be bypassed. + +The IBCF-2: + +- replaces the connection address and port information for the media line in the initial SDP answer with the connection address and port information from the visited-realm instance 2 in the received initial SDP answer. + +The IBCF-2 retains the primary local MR allocated for realm matching in step 4, until it is no longer potentially needed for this and any other forked dialog. + +The IBCF-2 forwards the 183 (Session Progress) response with initial SDP answer to IBCF-1 according to TS 24.229 [4]. + +**Table A.4.2-14: 183 (Session Progress) response (IBCF-2 to IBCF-1)** + +``` + +SIP/2.0 183 Session Progress + +SIP headers according to 3GPP TS 24.229 [4] + +Content-Type: application/sdp +Content-Length: (...) + +v=0 +o=- 2987933615 2312345678 IN IP4 192.0.2.1 +s=- +c=IN IP4 192.0.2.4 +m=audio 16511 RTP/AVP 96 98 +a=curr:qos local none +a=curr:qos remote none +a=des:qos mandatory local sendrecv +a=des:qos none remote sendrecv +a=rtpmap:96 telephone-event +a=rtpmap:98 AMR/8000/1 +a=fmtp:98 mode-change-capability=2; max-red=220; octet-align=1 +a=ptime:20 +a=maxptime:240 +b=AS:30 +b=RS:0 +b=RR:2000 + +``` + +#### 15. PRACK request (IBCF-1 to IBCF-2) - see example in table A.4.2-15 + +The IBCF-1 determines by subclause 6.2.3 that a transcoder MR is needed since the UE-B selected the codec added by IBCF-1 in step 7. The IBCF-4 uses subclause 6.1.5, 6.1.6 and 6.1.9 since no IMS-ALG can be bypassed and a primary MR is allocated. + +The IBCF-1: + +- uses the connection-address from the SDP c-line in the initial SDP offer as incoming connection-address in subsequent steps; +- uses the port information from the SDP m-line in the initial SDP offer as incoming port information in subsequent steps; +- use the codec information from the SDP m-line and associated non-OMR attribute lines in the initial SDP offer as incoming codec information in the subsequent steps; +- allocates an MR context with access to the IP realms, nettypes and addrtypes associated with the incoming connection address and port information and the outgoing signalling path; +- inserts the incoming connection address and incoming port information for the media line into the remote connection address and port information for the incoming termination on the MR; +- provides to the MR the incoming codec information; +- remove all OMR specific attributes from the modified second SDP offer; +- replaces the connection address and port information for the media line in the second SDP offer with the connection address and port information from the MR termination on the outgoing side; +- inserts the modified codec information (keeps the telephone-event codec, removes the AMR-WB codec and adds the AMR codec) into the SDP m-line and associated attribute lines of the modified second SDP offer; +- adds to the modified second SDP offer a visited-realm instance 2 for the IP realm associated with the connection address and port information for the media line in the modified second SDP offer; +- provides to the MR the modified codec information; +- computes checksum values as described in subclause 5.6.3 adds the "omr-s-cksum" and "omr-m-cksum" attributes for the media line; and + +- forwards the PRACK request with the second SDP offer to IBCF-2 according to TS 24.229 [4]. + +**Table A.4.2-15: PRACK request (IBCF-1 to IBCF-2)** + +| | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 
 PRACK SIP: sip:UE-B@operatorX.net; SIP/2.0  SIP headers according to 3GPP TS 24.229 [4]  Content-Type: application/sdp Content-Length: (...)  v=0 o=- 2987933615 2087654321 IN IP4 192.0.2.1 s= b=AS:30 b=RS:0 b=RR:2000 c=IN IP4 192.0.2.5 m=audio 18435 RTP/AVP 96 97 98 a=curr:qos local none a=curr:qos remote none a=des:qos mandatory local sendrecv a=des:qos none remote sendrecv a=rtpmap:96 telephone-event a=rtpmap:97 AMR-WB/16000/1 a=fmtp:97 mode-change-capability=2; max-red=220 a=rtpmap:98 AMR/8000/1 a=fmtp:98 mode-change-capability=2; max-red=220; octet-align=1 a=ptime:20 a=maxptime:240 a=visited-realm:2 Xa.operatorX.net IN IP4 192.0.2.5 18435 a=omr-m-cksum:(..) a=omr-s-cksum:(..)
| +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +#### **16-17. PRACK request (IBCF-2 to IBCF-3 via intermediate IMS CN subsystem entities) - see example in table A.4.2-16** + +The IBCF-2 uses the procedures in subclauses 6.1.5, 6.1.6 and 6.1.9 since no previous MRs can be bypassed and a local MR is needed for realm matching. + +The IBCF-2: + +- uses the connection-address from the SDP c-line in the received second SDP offer as incoming connection-address in subsequent steps; +- uses the port information from the SDP m-line in the received second SDP offer as incoming port information in subsequent steps; and +- uses the codec information from the SDP m-line and associated non-OMR attribute lines in the received second SDP offer as incoming codec information in the subsequent steps. +- inserts the incoming connection address and incoming port information for the media line into the remote connection address and port information for the incoming termination on the MR; +- provides to the MR the incoming codec information;- +- replaces the connection address and port information for the media line in the second SDP offer with the connection address and port information from the MR termination on the outgoing side; +- add to the modified second SDP offer a visited-realm instance 3 for the IP realm associated with the connection address and port information for the media line in the modified second SDP offer; +- computes checksum values as described in subclause 5.6.3 and replace or add the "omr-s-cksum" and "omr-m-cksum" attributes for the media line; and +- forwards the PRACK request with the modified second SDP offer to the intermediate IM CN subsystem entities according to TS 24.229 [4]. + +The intermediate IM CN subsystem entities forward the PRACK request without modifying the second SDP offer to the IBCF-3 according to TS 24.229 [4]. + +**Table A.4.2-16: PRACK request (IBCF-2 to IBCF-3 via intermediate IMS CN subsystem entities)** + +``` + +PRACK SIP: sip:UE-B@operatorX.net; SIP/2.0 + +SIP headers according to 3GPP TS 24.229 [4] + +Content-Type: application/sdp +Content-Length: (...) + +v=0 +o=- 2987933615 2087654321 IN IP4 192.0.2.1 +s= +b=AS:30 +b=RS:0 +b=RR:2000 +c=IN IP4 190.1.15.2 +m=audio 11324 RTP/AVP 96 97 98 +a=curr:qos local none +a=curr:qos remote none +a=des:qos mandatory local sendrecv +a=des:qos none remote sendrecv +a=rtpmap:96 telephone-event +a=rtpmap:97 AMR-WB/16000/1 +a=fmtp:97 mode-change-capability=2; max-red=220 +a=rtpmap:98 AMR/8000/1 +a=fmtp:98 mode-change-capability=2; max-red=220; octet-align=1 +a=ptime:20 +a=maxptime:240 +a=visited-realm:2 Xa.operatorX.net IN IP4 192.0.2.5 18435 +a=visited-realm:3 Yb.operatorY.net IN IP4 190.1.15.2 11324 +a=omr-m-cksum:(..) +a=omr-s-cksum:(..) + +``` + +#### **18. PRACK request (IBCF-3 to IBCF-4) - see example in table A.4.2-18** + +The IBCF-3 uses procedures in subclauses 6.1.4, 6.1.7 and 6.1.9 since previous MR can be bypassed and no local MR is needed. + +The IBCF: + +- uses the connection address and port information from the selected instance 2 for the media line in the received second SDP offer as incoming connection address and incoming port information for the media line in the subsequent steps; +- reconstructs the associated codec information for the media line in the received second SDP offer from the selected instance 2 as described in subclause 5.3, and use that codec information as incoming codec information in the subsequent steps; +- inserts the incoming codec information into the SDP m-line and associated attribute lines of the modified second SDP offer, +- uses the incoming connection address as the connection address in the SDP c-line of the forwarded second SDP offer; and +- uses the incoming port information as determined in previous steps as port information in the SDP m-line of the modified second SDP offer; +- computes checksum values as described in subclause 5.6.3 and replaces the "omr-s-cksum" and "omr-m-cksum" attributes for the media line; and +- forwards the PRACK request with the modified second SDP offer to IBCF-2 according to TS 24.229 [4]. + +**Table A.4.2-18: PRACK request (IBCF-3 to IBCF-4)** + +``` + +PRACK SIP: sip:UE-B@operatorX.net; SIP/2.0 + +SIP headers according to 3GPP TS 24.229 [4] + +Content-Type: application/sdp +Content-Length: (...) + +v=0 +o=- 2987933615 2087654321 IN IP4 192.0.2.1 +s= +b=AS:30 +b=RS:0 +b=RR:2000 +c=IN IP4 192.0.2.5 +m=audio 18435 RTP/AVP 96 97 98 +a=curr:qos local none +a=curr:qos remote none +a=des:qos mandatory local sendrecv +a=des:qos none remote sendrecv +a=rtpmap:96 telephone-event +a=rtpmap:97 AMR-WB/16000/1 +a=fmtp:97 mode-change-capability=2; max-red=220 +a=rtpmap:98 AMR/8000/1 +a=fmtp:98 mode-change-capability=2; max-red=220; octet-align=1 +a=ptime:20 +a=maxptime:240 +a=visited-realm:2 Xa.operatorX.net IN IP4 192.0.2.5 18435 +a=omr-m-cksum:(..) +a=omr-s-cksum:(..) + +``` + +#### 19. PRACK request (IBCF-4 to P-CSCF-B) - see example in table A.4.2-18 + +The IBCF-4 uses the procedures in subclauses 6.1.5, 6.1.7 and 6.1.9 since allocation of a local MR is not needed and no previous MR can be by passed. + +The IBCF-4: + +- uses the connection-address from the SDP c-line in the received second SDP offer as incoming connection-address in subsequent steps; +- uses the port information from the SDP m-line in the received second SDP offer as incoming port information in subsequent steps; +- uses the codec information from the SDP m-line and associated non-OMR attribute lines in the received second SDP offer as incoming codec information in the subsequent steps; +- inserts the incoming codec information into the SDP m-line and associated attribute lines of the modified second SDP offer; +- uses the incoming connection address as the connection address in the SDP c-line of the forwarded second SDP offer; +- uses the incoming port information as determined in previous steps as port information in the SDP m-line of the modified second SDP offer; and +- forwards the PRACK request with the unmodified second SDP offer to P-CSCF-B according to TS 24.229 [4]. + +#### 20. PRACK request (P-CSCF-B to UE- B) - see example in table A.4.2-20. + +The P-CSCF-B uses the procedures in subclauses 6.1.5, 6.1.7 and 6.1.9 since no previous realm instance offers an opportunity to bypass an MR and no local MR is required to match the incoming realm to the outgoing realm. + +- uses the connection-address from the SDP c-line as incoming connection-address; +- uses the port information from the SDP m-line as incoming port information; +- uses the codec information from the SDP m-line and associated non-OMR attribute lines as incoming codec information; + +- inserts the incoming codec information into the SDP m-line and associated attribute lines of the modified second SDP offer; +- uses the incoming connection address as the connection address in the SDP c-line of the forwarded second SDP offer; +- uses the incoming port information as port information in the SDP m-line of the modified second SDP offer; +- according to the local policy, deletes the visited-realm "visited-realm:1 Xa.operatorX.net IN IP4 192.0.2.5 18435", the omr-s-cksum=(..) and the "omr-m-cksum=(..)" from the second SDP offer ; and +- forwards the PRACK request with the modified second SDP offer to the UE-B according to TS 24.229 [4]. + +**Table A.4.2-20: SIP PRACK request (P-CSCF-B to UE-B)** + +``` +UPDATE SIP: sip:UE-B@operatorX.net; SIP/2.0 + +SIP headers according to 3GPP TS 24.229 [4] + +Content-Type: application/sdp +Content-Length: (...) + +v=0 +o= 2987933615 2087654321 IN IP4 192.0.2.1 +s= +c=IN IP4 192.0.2.5 +m=audio 18435 RTP/AVP 96 98 +a=curr:qos local none +a=curr:qos remote none +a=des:qos mandatory local sendrecv +a=des:qos none remote sendrecv +a=rtpmap:96 telephone-event +a=rtpmap:98 AMR/8000/1 +a=fmtp:98 mode-change-capability=2; max-red=220; octet-align=1 +a=ptime:20 +a=maxptime:240 +``` + +#### **21. 200 (OK) response (UE-B to P-CSCF-B) - see example in table A.4.2-21.** + +The UE accepts the AMR codec (again) and sends a 200 (OK) response to the PRACK request with a second SDP answer still indicating that resources are not yet available to P-CSCF-B according to TS 24.229 [4]. + +**Table A.4.2-21: 200 (OK) response to PRACK request (UE-B to P-CSCF-B)** + +``` +SIP/2.0 200 OK + +SIP headers according to 3GPP TS 24.229 [4] + +Content-Type: application/sdp +Content-Length: (...) + +v=0 +o= 2987933615 2312345678 IN IP4 192.0.2.1 +s= +b=AS:30 +b=RS:0 +b=RR:2000 +c=IN IP4 192.0.2.4 +m=audio 16511 RTP/AVP 96 98 +a=curr:qos local none +a=curr:qos remote none +a=des:qos mandatory local sendrecv +a=des:qos none remote sendrecv +a=rtpmap:96 telephone-event +a=rtpmap:98 AMR/8000/1 +a=fmtp:98 mode-change-capability=2; max-red=220; octet-align=1 +a=ptime:20 +a=maxptime:240 +``` + +#### **22. 200 (OK) response (P-CSCF-B to IBCF-4) - see example in table A.4.2-21.** + +The P-CSCF-B uses the procedures in subclauses 6.2.7 and 6.2.9 since no local MR was allocated the connection address is valid and no visited-realm instance was received in the second SDP answer. + +The P-CSCF-B: + +- does not modify the second SDP answer and forwards the 200 (OK) response with the second SDP answer to IBCF-4 according to TS 24.229 [4]. + +#### **23. 200 (OK) response (IBCF-4 to IBCF-3) - see example in table A.4.2-21.** + +The IBCF-4 uses the procedures in subclauses 6.2.7 and 6.2.9 since no local MR was allocated and a valid connection address was received in the second SDP answer. + +The IBCF-4 forwards the 200 (OK) response to the PRACK request with the unmodified second SDP answer according to TS 24.229 [4]. + +#### **24-25. 200 (OK) response (IBCF-3 to IBCF-2 via intermediate IM CN subsystem entities) - see example in table A.4.2-24.** + +The IBCF-3 uses procedures in subclauses 6.2.7 and 6.2.9 since no local MR was allocated and an unspecified connection address and no visited-realm instance was received in the second SDP answer. + +The IBCF-3: + +- copies into the media line of the second SDP answer the visited-realm instance 2 from the media line of the received second SDP offer that was used to populate the connection address and port information in the forwarded second SDP offer, replacing the connection-address and port information in the instance with the connection address and port information from the received second SDP answer; +- replaces the connection address information in the second SDP answer with the unspecified address of the IPv4, i.e. "0.0.0.0"; and +- forwards the 200 (OK) response to the PRACK request with the modified second SDP answer to the intermediate IM CN subsystem entities according to TS 24.229 [4]. + +The intermediate IM CN subsystem entities forward the 200 (OK) response to the PRACK request to the IBCF-2 according to TS 24.229 [4] without modifying the second SDP answer. + +###### **Table A.4.2-24: 200 (OK) response to PRACK request (IBCF-3 to IBCF-2 via intermediate IM CN subsystem entities)** + +``` +SIP/2.0 200 OK + +SIP headers according to 3GPP TS 24.229 [4] + +Content-Type: application/sdp +Content-Length: (...) + +v=0 +o=- 2987933615 2312345678 IN IP4 192.0.2.1 +s=- +b=AS:30 +b=RS:0 +b=RR:2000 +c=IN IP4 0.0.0.0 +m=audio 16511 RTP/AVP 96 98 +a=curr:qos local none +a=curr:qos remote none +a=des:qos mandatory local sendrecv +a=des:qos none remote sendrecv +a=rtpmap:96 telephone-event +a=rtpmap:98 AMR/8000/1 +a=fmtp:98 mode-change-capability=2; max-red=220; octet-align=1 +a=ptime:20 +a=maxptime:240 +a=visited-realm:2 Xa.operatorX.net 192.0.2.4 16511 +``` + +#### **26. 200 (OK) response (IBCF-2 to IBCF-1) - see example in table A.4.2-26.** + +The IBCF-2 uses the procedures in subclauses 6.2.5 and 6.2.9 since an unspecified connection address and a visited-realm instance was received. + +The IBCF-2: + +- replaces the connection address and port information for the media line in the second SDP answer with the connection address and port information from the visited-realm instance 2 in the received second SDP answer; +- forwards the 200 (OK) response to the PRACK request with the modified second SDP answer to IBCF-1 according to TS 24.229 [4]; and +- keeps the allocated MR until it is no longer potentially needed for this and any other forked dialog. + +**Table A.4.2-26: 200 (OK) response to PRACK request (IBCF-2 to IBCF-1)** + +``` + +SIP/2.0 200 OK + +SIP headers according to 3GPP TS 24.229 [4] + +Content-Type: application/sdp +Content-Length: (...) + +v=0 +o=- 2987933615 2312345678 IN IP4 192.0.2.1 +s=- +b=AS:30 +b=RS:0 +b=RR:2000 +c=IN IP4 192.0.2.4 +m=audio 16511 RTP/AVP 96 98 +a=curr:qos local none +a=curr:qos remote none +a=des:qos mandatory local sendrecv +a=des:qos none remote sendrecv +a=rtpmap:96 telephone-event +a=rtpmap:98 AMR/8000/1 +a=fmtp:98 mode-change-capability=2; max-red=220; octet-align=1 +a=ptime:20 +a=maxptime:240 + +``` + +#### **27.183 (Session Progress) response (IBCF-1 to P-CSCF-A) - see example in table A.4.2-27.** + +The IBCF-1 continues from the point when the 183 (Session Progress) response to the INVITE request was received in step 14 and uses the procedures in subclauses 6.2.8 and 6.2.9 since the IBCF-4 retains the MR allocated in step 14. + +The IBCF-1: + +- updates the remote connection address and port information for the outgoing termination on the selected MR context with the connection address and port information for the media line in the received second SDP answer; +- modifies the second SDP answer to include the codecs selected for the incoming termination of the selected local MR; +- replaces the connection address and port information for the media line in the initial SDP answer with the local connection address and port information for the incoming termination on the selected MR; +- removes the visited-realm instance; and +- forwards 183 (Session Progress) response with the modified initial SDP answer to P-CSCF-A according to TS 24.229 [4]. + +**Table A.4.2-27 183 (Session Progress) response (IBCF-1 to P-CSCF-A)** + +``` +SIP/2.0 183 Session Progress + +SIP headers according to 3GPP TS 24.229 [4] + +Content-Type: application/sdp +Content-Length: (...) + +v=0 +o=- 2987933615 2087654321 IN IP4 192.0.2.3 +s=- +b=AS:30 +b=RS:0 +b=RR:2000 +c=IN IP4 192.0.2.2 +m=audio 23563 RTP/AVP 96 97 +a=curr:qos local none +a=curr:qos remote sendrecv +a=des:qos mandatory local sendrecv +a=des:qos none remote sendrecv +a=rtpmap:97 AMR-WB/16000/1 +a=fmtp:97 mode-change-capability=2; max-red=220 +a=rtpmap:96 telephone-event +a=maxptime:20 +a=maxptime:240 +``` + +#### **28. 183 (Session Progress) response (P-CSCF-A to UE-A) - see example in table A.4.2-27** + +The P-CSCF-A forwards the 183 (Session Progress) with the initial SDP answer to the UE-A according to TS 24.229 [4]. + +#### **29-30. PRACK request (UE-A to IBCF-1 via P-CSCF-A).** + +The UE-A acknowledge the reception of the initial SDP answer and the 183 (Session Progress) response by means of a PRACK request. + +#### **31-32. 200 (OK) response to the PRACK request (IBCF-1 to UE-A via P-CSCF-A).** + +The IBCF-1 acknowledges the reception of the PRACK request by means of a 200 (OK) response. + +#### **33. UPDATE request (UE-A to P-CSCF-A) - see example in table A.4.2-33.** + +When the UE-A has got resources reserved the UE-A sends an UPDATE request. + +The subsequent SDP offer in the UPDATE the request is the same as the initial SDP offer in the INVITE request in the step 1 with the only exception that "a=curr:qos local none" is now changed to "a=curr:qos local sendrecv". + +**Table A.4.2-33: UPDATE request (UE-A to P-CSCF-A)** + +``` +UPDATE SIP: sip:UE-A@operatorX.net; SIP/2.0 + +SIP headers according to 3GPP TS 24.229 [4] + +Content-Type: application/sdp +Content-Length: (...) + +v=0 +o=- 2987933615 2987933616 IN IP4 192.0.2.1 +s= +b=AS:30 +b=RS:0 +b=RR:2000 +c=IN IP4 192.0.2.1 +m=audio 49170 RTP/AVP 96 97 +a=curr:qos local sendrecv +a=curr:qos remote none +a=des:qos mandatory local sendrecv +a=des:qos none remote sendrecv +a=rtpmap:96 telephone-event +a=rtpmap:97 AMR-WB/16000/1 +a=fmtp:97 mode-change-capability=2; max-red=220 +a=ptime:20 +a=maxptime:240 +``` + +#### **34-40. UPDATE request (P-CSCF-A to UE-B via IBCF-1, IBCF-2, intermediate IMS CN subsystem entities IBCF-3, IBCF-4 and P-CSCF-B).** + +- 34) The P-CSCF-A forwards the subsequent SDP offer as received. +- 35) The IBCF-1 replaces the connection information received in the subsequent SDP offer with the IBCF-1 own MR connection information. +- 36) The IBCF-2 forwards the subsequent SDP offer as received. +- 37) Intermediate IMS CN subsystem entities do not manipulate the SDP offer. +- 38) The IBCF-3 forwards the subsequent SDP offer as received. +- 39) The IBCF-4 forwards the subsequent SDP offer as received. +- 40) The P-CSCF-B forwards the subsequent SDP offer as received. + +#### **41. 200 (OK) response to the UPDATE request (UE-B to P-CSCF-B) - see example in table A.4.2-41.** + +The UE-B acknowledges the reception of the UPDATE request by means of a 200 (OK) response containing a subsequent SDP answer. + +**Table A.4.2-41: 200 (OK) response to the UPDATE request (UE-B to P-CSCF-B).** + +``` + +SIP/2.0 200 OK + +SIP headers according to 3GPP TS 24.229 [4] + +Content-Type: application/sdp +Content-Length: (...) + +v=0 +o=- 2987933615 2987933615 IN IP4 192.0.2.4 +s= +t=0 0 +c=IN IP4 192.0.2.4 +m=audio 16511 RTP/AVP 96 98 +a=curr:qos local sendrecv +a=curr:qos remote sendrecv +a=des:qos mandatory local sendrecv +a=des:qos none remote sendrecv +a=rtpmap:98 AMR/8000/1 +a=fmtp:98 mode-change-capability=2; max-red=220; octet-align=1 +a=rtpmap:96 telephone-event +a=maxptime:20 + +``` + +#### **42-48. 200 (OK) response to the UPDATE request (P-CSCF-B to UE-A via IBCF-4, IBCF-3, intermediate IMS CN subsystem entities, IBCF-2 and IBCF-1).** + +- 42) The P-CSCF-B forwards the subsequent SDP answer as received. +- 43) The IBCF-4 forwards the subsequent SDP answer as received. +- 44) The IBCF-3 forwards the subsequent SDP answer as received. +- 45) Intermediate IMS CN subsystem entities do not manipulate the SDP answer. +- 46) The IBCF-2 forwards the subsequent SDP answer as received. +- 47) The IBCF-1 replaces the connection information received in the subsequent SDP answer with the IBCF-1 own MR connection information. +- 48) The P-CSCF-A forwards the subsequent SDP answer as received. + +#### **49-56. 180 (Ringing) response (UE-B to UE-A via P-CSCF-B, IBCF-4, IBCF-3, intermediate IMS CN subsystem entities, IBCF-2, IBCF-1 and P-CSCF-A).** + +No OMR specific action is required. + +#### **57-64. 200 (OK) response to the INVITE request (UE-B to UE-A via P-CSCF-B, IBCF-4, IBCF-3, intermediated IMS CN subsystem, IBCF-2, IBCF-1 and P-CSCF-A).** + +The User B accepts the call and the UE-B sends a 200 (OK) response to the INVITE request. The response contains no SDP. + +The IBCF-2 releases the MR not used in the call. + +#### **65-72. ACK request (UE-A to UE-B via P-CSCF-A, IBCF-1, IBCF-2, intermediated IMS CN subsystem, IBCF-3, IBCF-4 and P-CSCF-B).** + +The UE-B acknowledges the reception of the 200 (OK) response by means of a 200 (OK) response. + +## --- A.5 IMS-ALG bypasses an allocated transcoding MR + +### A.5.1 General + +This subclause provides an example of a call where the UE initiating a call offers the AMR codec. An IMS-ALG, IBCF-1 in figure A.2.1, adds the AMR-WB codec to the initial SDP offer and reserves an MR resource. + +The terminating UE selects the AMR codec and the IMS-ALG needs to deallocate the MR and update the terminating UE with the IP addresses of the UE-A in a realm instance to allow bypassing of the IMS-ALG itself. + +Figure A.5.1-1 shows the realm and IP structure used in this example. + +![Figure A.5.1-1: IP realm and IP structure diagram showing three network realms: Home IMS network H (Realm Ha.operatorH.net), IPX network X (Realm Xa.operatorX.net), and Visited network V (Realm Va.operatorV.net). UE-A is connected to Visited network V via P-CSCF-A and IBCF-1. Control signalling paths are shown with solid arrows, and media paths after OMR are shown with dashed arrows. IP addresses are assigned to various network elements across the realms.](68a5a1a1a761c652b4b4c56da7cf9914_img.jpg) + +The diagram illustrates the IP realm and IP structure across three network domains: + +- Home IMS network H: Realm Ha.operatorH.net** contains S-CSCF/BGCF, IBCF-2 (Ha: 190.1.15.2, Xa4: 179.14.1.2), and TrGW. +- IPX network X: Realm Xa.operatorX.net** contains IBCF-3 (Ha: 190.1.15.2, Xa4: 179.14.1.3), TrGW, IC-1 (Xa2: 179.14.1.1, Xa2: 178.15.1.2), MGW, IC-2 (Xa2: 179.14.1.4, Xa2: 178.15.1.3), and MGW. +- Visited network V: Realm Va.operatorV.net** contains UE-A (Va: 192.0.2.1), P-CSCF-A, PCRF, PDN-GW, IBCF-1 (Xa1: 178.15.1.1, 192.0.2.2), TrGW, IBCF-4 (Xa1: 178.15.1.4, 192.0.2.3), TrGW, TRF, IBCF-5 (Va: 192.0.2.4), and TrGW. + +Control signalling paths are indicated by solid double-headed arrows, and media paths after OMR are indicated by dashed double-headed arrows. + +Figure A.5.1-1: IP realm and IP structure diagram showing three network realms: Home IMS network H (Realm Ha.operatorH.net), IPX network X (Realm Xa.operatorX.net), and Visited network V (Realm Va.operatorV.net). UE-A is connected to Visited network V via P-CSCF-A and IBCF-1. Control signalling paths are shown with solid arrows, and media paths after OMR are shown with dashed arrows. IP addresses are assigned to various network elements across the realms. + +Figure A.5.1-1: IP realm and IP structure + +### A.5.2 Message flow + +The user A at UE-A and the user B at UE-B roams into a visited network X and both users belongs to the same operator Y. + +Preconditions: + +- Both users A and B are registered to the Home IMS network Y via the visited operator X network; +- the visited operator X and the operator of user A and B IMS home network Y have an agreement to allow media to be bypassed using OMR; +- both users A and B are connected to realm Xa of the visited operator network X; +- the AMR codec is allowed and accepted by all involved entities. However, the local policy of operator X is that the AMR-WB codec shall always be included in the initial SDP offers from the operator X network; and +- no B2BUA manipulating SDP is connected in the intermediate IM CN subsystem. + +Figure A.5.2-1 shows the message flow for the scenario. + +![Sequence diagram showing message flow for a transcoder with resource reservation. The diagram spans across three network domains: Visited network X (left), Home IMS network Y (center, containing user A and B), and Visited network X (right). Lifelines include UE-A, P-CSCF A, IBCF-1, IBCF-2, Intermediate IM CN subsystem entities X, IBCF-3, IBCF-4, P-CSCF B, and UE-B. The sequence of messages is: 1. INVITE (UE-A to P-CSCF A), 2. INVITE (P-CSCF A to IBCF-1), 3. INVITE (IBCF-1 to IBCF-2), 4. INVITE (IBCF-2 to Intermediate IM CN), 5. INVITE (Intermediate IM CN to IBCF-3), 6. INVITE (IBCF-3 to IBCF-4), 7. INVITE (IBCF-4 to P-CSCF B), 8. INVITE (P-CSCF B to UE-B). Subsequent messages include 10. 183, 11. PRACK, 12. PRACK, 13. 200 OK (PRACK), 14. 200 OK (PRACK), 15. 183, 16. 183, 17. 183, 18. 183, 19. 183, 20. 183, 21. PRACK, 22. PRACK, 23. PRACK, 24. PRACK, 25. PRACK, 26. PRACK, 27. 200 OK (PRACK), 28. 200 OK (PRACK), 29. 200 OK (PRACK), 30. 200 OK (PRACK), 31. 200 OK (PRACK), 32. 200 OK (PRACK), 33. UPDATE, 34. UPDATE, 35. UPDATE, 36. UPDATE, 37. UPDATE, 38. UPDATE, 39. UPDATE, 40. UPDATE, 41. 200 OK (UPDATE), 42. 200 OK (UPDATE), 43. 200 OK (UPDATE), 44. 200 OK (UPDATE), 45. 200 OK (UPDATE), 46. 200 OK (UPDATE), 47. 200 OK (UPDATE), 48. 200 OK (UPDATE), 49. 180, 50. 180, 51. 180, 52. 180, 53. 180, 54. 180, 55. 180, 56. 180, 57. 200 OK (INVITE), 58. 200 OK (INVITE), 59. 200 OK (INVITE), 60. 200 OK (INVITE), 61. 200 OK (INVITE), 62. 200 OK (INVITE), 63. 200 OK (INVITE), 64. 200 OK (INVITE), 65. ACK, 66. ACK, 67. ACK, 68. ACK, 69. ACK, 70. ACK, 71. ACK, 72. ACK. A thick horizontal line at the bottom is labeled AMR.](56a5265d174ce056c1dbe5e7a60839fc_img.jpg) + +Sequence diagram showing message flow for a transcoder with resource reservation. The diagram spans across three network domains: Visited network X (left), Home IMS network Y (center, containing user A and B), and Visited network X (right). Lifelines include UE-A, P-CSCF A, IBCF-1, IBCF-2, Intermediate IM CN subsystem entities X, IBCF-3, IBCF-4, P-CSCF B, and UE-B. The sequence of messages is: 1. INVITE (UE-A to P-CSCF A), 2. INVITE (P-CSCF A to IBCF-1), 3. INVITE (IBCF-1 to IBCF-2), 4. INVITE (IBCF-2 to Intermediate IM CN), 5. INVITE (Intermediate IM CN to IBCF-3), 6. INVITE (IBCF-3 to IBCF-4), 7. INVITE (IBCF-4 to P-CSCF B), 8. INVITE (P-CSCF B to UE-B). Subsequent messages include 10. 183, 11. PRACK, 12. PRACK, 13. 200 OK (PRACK), 14. 200 OK (PRACK), 15. 183, 16. 183, 17. 183, 18. 183, 19. 183, 20. 183, 21. PRACK, 22. PRACK, 23. PRACK, 24. PRACK, 25. PRACK, 26. PRACK, 27. 200 OK (PRACK), 28. 200 OK (PRACK), 29. 200 OK (PRACK), 30. 200 OK (PRACK), 31. 200 OK (PRACK), 32. 200 OK (PRACK), 33. UPDATE, 34. UPDATE, 35. UPDATE, 36. UPDATE, 37. UPDATE, 38. UPDATE, 39. UPDATE, 40. UPDATE, 41. 200 OK (UPDATE), 42. 200 OK (UPDATE), 43. 200 OK (UPDATE), 44. 200 OK (UPDATE), 45. 200 OK (UPDATE), 46. 200 OK (UPDATE), 47. 200 OK (UPDATE), 48. 200 OK (UPDATE), 49. 180, 50. 180, 51. 180, 52. 180, 53. 180, 54. 180, 55. 180, 56. 180, 57. 200 OK (INVITE), 58. 200 OK (INVITE), 59. 200 OK (INVITE), 60. 200 OK (INVITE), 61. 200 OK (INVITE), 62. 200 OK (INVITE), 63. 200 OK (INVITE), 64. 200 OK (INVITE), 65. ACK, 66. ACK, 67. ACK, 68. ACK, 69. ACK, 70. ACK, 71. ACK, 72. ACK. A thick horizontal line at the bottom is labeled AMR. + +**Figure A.5.2-1: Message flow for transcoder with resource reservation, codec not selected** + +NOTE: For clarity, the SIP 100 (Trying) messages are not shown in the signalling flow. + +The steps of the flow are as follows: + +#### **1. INVITE request (UE-A to P-CSCF-A) - see example in table A.5.2-1.** + +The UE-A sends a SIP INVITE request according to TS 24.229 [4]. The INVITE request includes an initial SDP offer proposing the use of the AMR codec and inband DTMF. + +**Table A.5.2-1: SIP INVITE request (UE-A to P-CSCF-A)** + +``` + +INVITE SIP: user_B@operator_Y.net; SIP/2.0 + +SIP headers according to 3GPP TS 24.229 [4] + +Content-Type: application/sdp +Content-Length: (...) + +v=0 +o=- 2987933615 2987933615 IN IP4 192.0.2.1 +s= +b=AS:30 +b=RS:0 +b=RR:2000 +c=IN IP4 192.0.2.1 +m=audio 49170 RTP/AVP 96 97 +a=curr:qos local none +a=curr:qos remote none +a=des:qos mandatory local sendrecv +a=des:qos none remote sendrecv +a=rtpmap:96 telephone-event +a=rtpmap:97 AMR/8000/1 +a=fmtp:97 mode-change-capability=2; max-red=220; octet-align=1 +a=ptime:20 +a=maxptime:240 + +``` + +#### 2. INVITE request (P-CSCF-A to IBCF-1) - see example in table A.5.2-1. + +The P-CSCF-A uses the procedures in subclauses 6.1.5, 6.1.7 and 6.1.9 since no MR could be bypassed and no MR is allocated. + +The P-CSCF-A: + +- uses the connection-address from the SDP c-line as incoming connection-address; +- uses the port information from the SDP m-line as incoming port information; +- uses the codec information from the SDP m-line; +- inserts the incoming codec information into the SDP m-line and associated attribute lines of the modified initial SDP offer; +- uses the incoming connection address as the connection address in the SDP c-line of the forwarded initial SDP offer, and +- use the incoming port information as port information in the SDP m-line of the modified initial SDP offer. + +The P-CSCF-A then selects an IBCF, IBCF-1, in the realm "Xa.operatorX.net" and forwards the INVITE request with the initial SDP offer to the IBCF-1 according to TS 24.229 [4]. + +#### 3. INVITE request (IBCF-1 to IBCF-2) - see example in table A.5.2-3 + +The IBCF-1 uses the procedures in 6.1.5, 6.1.6 and 6.1.9 since IBCF-1 determines according to local policy that a transcoding MR is needed and that there is no previous MR to bypass. + +The IBCF-1: + +- uses the connection-address from the SDP c-line in the received SDP offer as incoming connection-address in subsequent steps; +- uses the port information from the SDP m-line in the received SDP offer as incoming port information in subsequent steps; +- uses the codec information from the SDP m-line and associated non-OMR attribute lines in the received SDP offer as incoming codec information in the subsequent steps; +- allocates an MR context with access to the IP realms, nettypes and addrtypes associated with the incoming connection address and port information and the outgoing signalling path; + +- inserts the incoming connection address and incoming port information for the media line into the remote connection address and port information for the incoming termination on the MR; +- provides to the MR the incoming codec information; +- constructs a visited-realm instance 1; +- replaces the connection address and port information for the media line in the initial SDP offer with the connection address and port information from the MR termination on the outgoing side; +- adds a AMR-WB codec changes to incoming codec information, according to local policy, taking into account the procedures in clause 5.4, and insert the changed codec information into the SDP m-line and associated attribute lines of the modified initial SDP offer; +- provides to the MR the modified codec information; +- adds to the modified initial SDP offer a visited-realm instance 2 for the IP realm associated with the connection address and port information for the media line in the modified initial SDP offer, including the incoming codec information encoded according to clause 5.2; +- computes checksum values as described in subclause 5.6.3 and adds the "omr-s-cksum" and "omr-m-cksum" attributes for the media line. The "omr-s-cksum" is set to "0" since there is no session line attributes to compute the checksum on; and +- selects an IBCF, IBCF-2, in the realm "Xa.operatorX.net" and forwards the INVITE request with the modified initial SDP offer to the IBCF-2 according to TS 24.229 [4]. + +**Table A.5.2-3: SIP INVITE request (IBCF-1 to IBCF-2)** + +``` + +INVITE SIP: user_B@operator_Y.net; SIP/2.0 + +SIP headers according to 3GPP TS 24.229 [4] + +Content-Type: application/sdp +Content-Length: (...) + +v=0 +o= 2987933615 2987933615 IN IP4 192.0.2.1 +s= +c=IN IP4 192.0.2.5 +m=audio 62111 RTP/AVP 96 97 98 +a=curr:qos local none +a=curr:qos remote none +a=des:qos mandatory local sendrecv +a=des:qos none remote sendrecv +a=rtpmap:96 telephone-event +a=rtpmap:97 AMR/8000/1 +a=fmtp:97 mode-change-capability=2; max-red=220; octet-align=1 +a=rtpmap:98 AMR-WB/16000/1 +a=fmtp:98 mode-change-capability=2; max-red=220 +a=ptime:20 +a=maxptime:240 +b=AS:30 +b=RS:0 +b=RR:2000 +a=visited-realm:1 Xa.operatorX.net IN IP4 192.0.2.1 49170 +a=visited-realm:2 Xa.operatorX.net IN IP4 192.0.2.5 62111 +a=omr-codecs:2 audio RTP/AVP 96 97 +a=omr-m-att:2 rtpmap:96 +a=omr-m-att:2 telephone-event +a=omr-m-att:2 rtpmap:97 AMR/8000/1 +a=omr-m-att:2 fmtp:97 +a=omr-m-att:2 mode-change-capability=2; max-red=220; octet-align=1 +a=omr-m-att:2 curr:qos local none +a=omr-m-att:2 curr:qos remote none +a=omr-m-att:2 des:qos mandatory local sendrecv +a=omr-m-att:2 des:qos none remote sendrecv +a=omr-m-att:2 ptime:20 +a=omr-m-att:2 maxptime:240 +a=omr-s-bw:2 AS:30 +a=omr-s-bw:2 RS:0 +a=omr-s-bw:2 RR:2000 +a=omr-m-cksum:(..) +a=omr-s-cksum:0 + +``` + +#### 4.5. INVITE request (IBCF-2 to IBCF-3 via intermediate IMS CN subsystem entities) - see example in table A.5.2-4 + +The IMS-ALG uses the procedures in subclauses 6.1.5, 6.1.6 and 6.1.9 since no MR can be bypassed and a local MR is needed for realm matching. + +The IBCF-2: + +- uses the connection-address from the SDP c-line as incoming connection-address in subsequent steps; +- uses the port information from the SDP m-line as incoming port information in subsequent steps; +- uses the codec information from the SDP m-line and associated non-OMR attribute lines as incoming codec information in the subsequent steps. +- allocates an MR context with access to the IP realms, nettypes and addrtypes associated with the incoming connection address and port information and the outgoing signalling path; +- inserts the incoming connection address and incoming port information for the media line into the remote connection address and port information for the incoming termination on the MR; +- provides to the MR the incoming codec information; +- replaces the connection address and port information for the media line in the initial SDP offer with the connection address and port information from the MR termination on the outgoing side; + +- adds to the modified initial SDP offer a visited-realm instance 3 for the IP realm associated with the connection address and port information for the media line in the modified initial SDP offer; and +- computes checksum values as described in subclause 5.6.3 and adds the "omr-s-cksum" and "omr-m-cksum" attributes for the media line. The "omr-s-cksum" is set to "0" since there is no session line attributes to compute the checksum on. + +None of the intermediate IMS CN subsystem entities manipulated with the initial SDP offer but the identity of [user\\_B@operator\\_Y.net](#) in the Request-URI is change to the contact address, i.e. UE-B@operatorX.net. + +The intermediate IMS CN subsystem entities select an IBCF, IBCF-3, in the realm "Ya.operatorY.net" and forward the INVITE request with the initial SDP offer to the IBCF-3 according to TS 24.229 [4]. + +**Table A.5.2-4: SIP INVITE request (IBCF-2 to IBCF-3 via intermediate IMS CN subsystem entities)** + +``` +INVITE SIP: user_B@operator_Y.net; SIP/2.0 + +SIP headers according to 3GPP TS 24.229 [4] + +Content-Type: application/sdp +Content-Length: (...) + +v=0 +o=- 2987933615 2987933615 IN IP4 192.0.2.1 +s= +c=IN IP4 190.1.15.2 +m=audio 11324 RTP/AVP 96 97 98 +a=curr:qos local none +a=curr:qos remote none +a=des:qos mandatory local sendrecv +a=des:qos none remote sendrecv +a=rtpmap:96 telephone-event +a=rtpmap:97 AMR/8000/1 +a=fmtp:97 mode-change-capability=2; max-red=220; octet-align=1 +a=rtpmap:98 AMR-WB/16000/1 +a=fmtp:98 mode-change-capability=2; max-red=220 +a=ptime:20 +a=maxptime:240 +b=AS:30 +b=RS:0 +b=RR:2000 +a=visited-realm:1 Xa.operatorX.net IN IP4 192.0.2.1 49170 +a=visited-realm:2 Xa.operatorX.net IN IP4 192.0.2.5 62111 +a=omr-codes:2 audio RTP/AVP 96 97 +a=omr-m-att:2 rtpmap:96 +a=omr-m-att:2 telephone-event +a=omr-m-att:2 rtpmap:97 AMR/8000/1 +a=omr-m-att:2 fmtp:97 +a=omr-m-att:2 mode-change-capability=2; max-red=220; octet-align=1 +a=omr-m-att:2 curr:qos local none +a=omr-m-att:2 curr:qos remote none +a=omr-m-att:2 des:qos mandatory local sendrecv +a=omr-m-att:2 des:qos none remote sendrecv +a=omr-m-att:2 ptime:20 +a=omr-m-att:2 maxptime:240 +a=omr-s-bw:2 AS:30 +a=omr-s-bw:2 RS:0 +a=omr-s-bw:2 RR:2000 +a=visited-realm:3 Ya.operatorY.net IN IP4 190.1.15.2 11324 +a=omr-m-cksum:(..) +a=omr-s-cksum:0 +``` + +#### 6. INVITE request (IBCF-3 to IBCF-4) - see example in table A.5.2-6 + +The IBCF-3 uses procedures in subclauses 6.1.4, 6.1.7 and 6.1.9 since previous MRs can be bypassed and no local MR is needed for realm matching. + +The IBCF-3: + +- uses the connection address and port information from the selected instance 2 for the media line in the initial SDP offer as incoming connection address and incoming port information for the media line in the subsequent steps. The instance 2 is selected since it contains more codecs than the visited-realm instance 1; + +- reconstructs the associated codec information for the media line in the initial SDP offer from the selected instance 2 according to subclause 5.3 and uses that codec information as incoming codec information in the subsequent steps; +- deletes visited-realm instance 3; +- insert the incoming codec information into the SDP m-line and associated attribute lines of the modified initial SDP offer; +- uses the incoming connection address as the connection address in the SDP c-line of the forwarded initial SDP offer; +- uses the incoming port information as determined in previous steps as port information in the SDP m-line of the initial modified SDP offer; +- computes checksum values as described in subclause 5.6.3 and adds the "omr-s-cksum" and "omr-m-cksum" attributes for the media line. The "omr-s-cksum" is set to "0" since there is no session line attributes to compute the checksum on; and +- selects an IBCF, IBCF-4, in the realm "Xa.operatorX.net" and forwards the INVITE request with the initial SDP offer according to TS 24.229 [4] to IBCF-4. + +**Table A.5.2-6: SIP INVITE request (IBCF-3 to IBCF-4)** + +``` + +INVITE SIP: UE-B@operator_Y.net; SIP/2.0 + +SIP headers according to 3GPP TS 24.229 [4] + +Content-Type: application/sdp +Content-Length: (...) + +v=0 +o=- 2987933615 2987933615 IN IP4 192.0.2.1 +s= +c=IN IP4 192.0.2.5 +m=audio 62111 RTP/AVP 96 97 98 +a=curr:qos local none +a=curr:qos remote none +a=des:qos mandatory local sendrecv +a=des:qos none remote sendrecv +a=rtpmap:96 telephone-event +a=rtpmap:97 AMR/8000/1 +a=fmtp:97 mode-change-capability=2; max-red=220; octet-align=1 +a=rtpmap:98 AMR-WB/16000/1 +a=fmtp:98 mode-change-capability=2; max-red=220 +a=ptime:20 +a=maxptime:240 +b=AS:30 +b=RS:0 +b=RR:2000 +a=visited-realm:1 Xa.operatorX.net IN IP4 192.0.2.1 49170 +a=visited-realm:2 Xa.operatorX.net IN IP4 192.0.2.5 62111 +a=omr-codecs:audio RTP/AVP 96 97 +a=omr-m-att:2 rtpmap:96 +a=omr-m-att:2 telephone-event +a=omr-m-att:2 rtpmap:97 AMR/8000/1 +a=omr-m-att:2 fmtp:97 +a=omr-m-att:2 mode-change-capability=2; max-red=220; octet-align=1 +a=omr-m-att:2 curr:qos local none +a=omr-m-att:2 curr:qos remote none +a=omr-m-att:2 des:qos mandatory local sendrecv +a=omr-m-att:2 des:qos none remote sendrecv +a=omr-m-att:2 ptime:20 +a=omr-m-att:2 maxptime:240 +a=omr-s-bw:2 AS:30 +a=omr-s-bw:2 RS:0 +a=omr-s-bw:2 RR:2000 +a=omr-m-cksum:(...) +a=omr-s-cksum:0 + +``` + +#### **7. INVITE request (IBCF-4 to P-CSCF B) - see example in table A.5.2-7.** + +The IBCF-4 uses procedures in subclauses 6.1.5, 6.1.7 and 6.1.9 since the visited-realm with the highest instance number is connected to the same realm as the IBCF-4 and contains codecs according to the local policy. Using the visited-realm instance 1 would reduce the number of available codecs. No MR for realm matching is needed. + +The IBCF-4: + +- uses the connection-address from the SDP c-line in the received SDP offer as incoming connection-address in subsequent steps; +- uses the port information from the SDP m-line in the received SDP offer as incoming port information in subsequent steps; +- uses the codec information from the SDP m-line and associated non-OMR attribute lines in the received initial SDP offer as incoming codec information in the subsequent steps; +- inserts the incoming codec information into the SDP m-line and associated attribute lines of the modified initial SDP offer; +- uses the incoming connection address as the connection address in the SDP c-line of the forwarded initial SDP offer; and +- use the incoming port information as determined in previous steps as port information in the SDP m-line of the modified initial SDP offer; and +- forwards the INVITE request with the unmodified initial SDP offer to the P-CSCF-B according to TS 24.229 [4]. + +**Table A.5.2-7: SIP INVITE request (IBCF-4 to P-CSCF B)** + +``` + +INVITE SIP: UE-B@operator_Y.net; SIP/2.0 + +SIP headers according to 3GPP TS 24.229 [4] + +Content-Type: application/sdp +Content-Length: (...) + +v=0 +o= 2987933615 2987933615 IN IP4 192.0.2.1 +s= +c=IN IP4 192.0.2.5 +m=audio 62111 RTP/AVP 96 97 98 +a=curr:qos local none +a=curr:qos remote none +a=des:qos mandatory local sendrecv +a=des:qos none remote sendrecv +a=rtpmap:96 telephone-event +a=rtpmap:97 AMR/8000/1 +a=fmtp:97 mode-change-capability=2; max-red=220; octet-align=1 +a=rtpmap:98 AMR-WB/16000/1 +a=fmtp:98 mode-change-capability=2; max-red=220 +a=ptime:20 +a=maxptime:240 +b=AS:30 +b=RS:0 +b=RR:2000 +a=visited-realm:1 Xa.operatorX.net IN IP4 192.0.2.1 49170 +a=visited-realm:2 Xa.operatorX.net IN IP4 192.0.2.5 62111 +a=omr-codecs:2 audio RTP/AVP 96 97 +a=omr-m-att:2 rtpmap:96 +a=omr-m-att:2 telephone-event +a=omr-m-att:2 rtpmap:97 AMR/8000/1 +a=omr-m-att:2 fmtp:97 +a=omr-m-att:2 mode-change-capability=2; max-red=220; octet-align=1 +a=omr-m-att:2 curr:qos local none +a=omr-m-att:2 curr:qos remote none +a=omr-m-att:2 des:qos mandatory local sendrecv +a=omr-m-att:2 des:qos none remote sendrecv +a=omr-m-att:2 ptime:20 +a=omr-m-att:2 maxptime:240 +a=omr-s-bw:2 AS:30 +a=omr-s-bw:2 RS:0 +a=omr-s-bw:2 RR:2000 +a=omr-m-cksum: (...) +a=omr-s-cksum:0 + +``` + +#### 8. INVITE request (P-CSCF to UE- B) - see example in table A.5.2-8. + +The P-CSCF-B uses the procedures in subclauses 6.1.5, 6.1.7 and 6.1.9 since no previous realm instance offers an opportunity to bypass an MR and no local MR for realm matching is needed. + +The P-CSCF-B: + +- uses the connection-address from the SDP c-line in the received initial SDP offer as incoming connection-address in subsequent steps; +- uses the port information from the SDP m-line in the received initial SDP offer as incoming port information in subsequent steps; +- uses the codec information from the SDP m-line and associated non-OMR attribute lines in the received initial SDP offer as incoming codec information in the subsequent steps; +- inserts the incoming codec information into the SDP m-line and associated attribute lines of the modified initial SDP offer; +- uses the incoming connection address as the connection address in the SDP c-line of the forwarded initial SDP offer; +- use the incoming port information as determined in previous steps as port information in the SDP m-line of the modified initial SDP offer; + +- deletes all OMR attributes from the initial SDP offer according to the local policy; and +- forwards the INVITE request with the modified initial SDP offer to the UE-B according to TS 24.229 [4]. + +**Table A.5.2-8: SIP INVITE request (P-CSCF to UE-B)** + +``` +INVITE SIP: UE-B@operator_Y.net; SIP/2.0 + +SIP headers according to 3GPP TS 24.229 [4] + +Content-Type: application/sdp +Content-Length: (...) + +v=0 +o= 2987933615 2987933615 IN IP4 192.0.2.1 +s= +c=IN IP4 192.0.2.5 +m=audio 62111 RTP/AVP 96 97 98 +b=AS:30 +b=RS:0 +b=RR:2000 +a=curr:qos local none +a=curr:qos remote none +a=des:qos mandatory local sendrecv +a=des:qos none remote sendrecv +a=rtpmap:96 telephone-event +a=rtpmap:97 AMR/8000/1 +a=fmtp:97 mode-change-capability=2; max-red=220; octet-align=1 +a=rtpmap:98 AMR-WB/16000/1 +a=fmtp:98 mode-change-capability=2; max-red=220 +a=ptime:20 +a=maxptime:240 +``` + +#### **9. 183 (Session Progress) response (UE-B to P-CSCF-B) - see example in table A.5.2-9.** + +The UE accepts the AMR codec and sends a 183 (Session Progress) response to P-CSCF-B with an initial SDP answer selecting the AMR codec and indicating that resources are not yet available according to TS 24.229 [4]. + +**Table A.5.2-9: 183 (Session Progress) response (UE-B to P-CSCF-B)** + +``` +SIP/2.0 183 Session Progress + +SIP headers according to 3GPP TS 24.229 [4] + +Content-Type: application/sdp +Content-Length: (...) + +v=0 +o= 2987933615 2312345678 IN IP4 192.0.2.1 +s= +c=IN IP4 192.0.2.4 +m=audio 16511 RTP/AVP 96 97 +b=AS:30 +b=RS:0 +b=RR:2000 +a=curr:qos local none +a=curr:qos remote none +a=des:qos mandatory local sendrecv +a=des:qos none remote sendrecv +a=rtpmap:96 telephone-event +a=rtpmap:97 AMR/8000/1 +a=fmtp:97 mode-change-capability=2; max-red=220; octet-align=1 +a=ptime:20 +a=maxptime:240 +``` + +#### **10. 183 (Session Progress) response (P-CSCF-B to IBCF-4) - see example in table A.5.2-9** + +The P-CSCF-B uses the procedures in subclauses 6.2.7 and 6.2.9 since the connection address is valid and no primary local MR was allocated when the initial SDP offer was sent. + +The P-CSCF-B forwards the 183 (Session Progress) response with the unmodified initial SDP answer to IBCF-4 according to TS 24.229 [4]. + +#### **11. PRACK request (IBCF-4 to P-CSCF-B) - see example in table A.5.2-11.** + +The IBCF-4 uses the procedure in subclause 6.2.2 to determine that the transcoder allocated by IBCF-1 is not needed any longer and that a PRACK request can be sent to update the IP address according to visited-realm instance 1. + +The IBCF-4 uses the procedures in 6.1.4, 6.1.7 and 6.1.9 since the previous MR at IBCF-1 can be bypassed and no local MR is needed for realm matching. + +The IBCF-4: + +- uses the connection address and port information from the selected visited-realm instance 1 for the media line in the received initial SDP offer (received in the initial INVITE request in step 6) as incoming connection address and incoming port information for the media line in the subsequent steps; +- reconstructs the associated codec information for the media line in the received initial SDP offer from the selected instance 1 as described in subclause 5.3, and use the AMR codec and associated attribute lines as incoming codec information in the subsequent steps; +- deletes every OMR attribute for the media line with instance-number value 2 and 3; +- inserts the incoming codec information into the SDP m-line and associated attribute lines of the modified second SDP offer; +- uses the incoming connection address as the connection address in the SDP c-line of the forwarded second SDP offer; +- uses the incoming port information as port information in the SDP m-line of the modified second SDP offer; +- computes checksum values as described in subclause 5.6.3 and replaces or add the "omr-s-cksum" and "omr-m-cksum" attributes for the media line; and +- sends the PRACK request with the modified second SDP offer to P-CSCF-B according to TS 24.229 [4]. + +**Table A.5.2-11: SIP PRACK request (IBCF-4 to P-CSCF-B)** + +``` +UPDATE SIP: UE_B@operator_Y.net; SIP/2.0 + +SIP headers according to 3GPP TS 24.229 [4] + +Content-Type: application/sdp +Content-Length: (...) + +v=0 +o=- 2987933615 2987933615 IN IP4 192.0.2.1 +s= +b=AS:30 +b=RS:0 +b=RR:2000 +c= IN IP4 192.0.2.1 +m=audio 49170 RTP/AVP 96 97 +a=rtpmap:96 telephone-event +a=rtpmap:97 AMR/8000/1 +a=fmtp:97 mode-change-capability=2; max-red=220; octet-align=1 +a=qos local none +a=curr: qos remote none +a=des:qos mandatory local sendrecv +a=des:qos none remote sendrecv +a=ptime:20 +a=maxptime:240 +a=visited-realm:1 Xa.operatorX.net IN IP4 192.0.2.1 49170 +a=omr-m-cksum:(..) +a=omr-s-cksum:(..) +``` + +#### 12. PRACK request (P-CSCF-B to UE-B) - see example in table A.5.2-12. + +The P-CSCF-B uses the procedure in 6.1.5, 6.1.7 and 6.1.9 since there are no MR to bypass and since no local MR is allocated for realm matching. + +The P-CSCF-B: + +- uses the connection-address from the SDP c-line in the received second SDP offer as incoming connection-address in subsequent steps; +- uses the port information from the SDP m-line in the received second SDP offer as incoming port information in subsequent steps; +- uses the codec information from the SDP m-line and associated non-OMR attribute lines in the received second SDP offer as incoming codec information in the subsequent steps; +- inserts the incoming codec information into the SDP m-line and associated attribute lines of the modified second SDP offer; +- uses the incoming connection address as the connection address in the SDP c-line of the forwarded second SDP offer; +- uses the incoming port information as port information in the SDP m-line of the modified second SDP offer; +- deletes all OMR related attributes from the second SDP offer according to local policy; and +- forwards the PRACK request and the modified second SDP offer to the UE-B according to TS 24.229 [4]. + +**Table A.5.2-12: SIP PRACK request (P-CSCF-B to UE-B)** + +``` + +PRACK SIP: UE_B@operator_Y.net; SIP/2.0 + +SIP headers according to 3GPP TS 24.229 [4] + +Content-Type: application/sdp +Content-Length: (...) + +v=0 +o=- 2987933615 2987933615 IN IP4 192.0.2.1 +s= +b=AS:30 +b=RS:0 +b=RR:2000 +c= IN IP4 192.0.2.1 +m=audio 49170 RTP/AVP 96 97 +a=rtpmap:96 telephone-event +a=rtpmap:97 AMR/8000/1 +a=fmtp:97 mode-change-capability=2; max-red=220; octet-align=1 +a=qos local none +a=curr: qos remote none +a=des:qos mandatory local sendrecv +a=des:qos none remote sendrecv +a=ptime:20 +a=maxptime:240 + +``` + +#### **13. 200 (OK) response (UE-B to P-CSCF-B) - see the SDP example in table A.5.2-9.** + +The UE accepts the AMR codec and sends a 200 (OK) response to the PRACK request to P-CSCF-B with a second SDP answer indicating that resources are not yet available according to TS 24.229 [4]. + +#### **14. 200 (OK) response (P-CSCF-B to IBCF-4) - see the SDP example in table A.5.2-9.** + +The P-CSCF-B uses the procedures in subclauses 6.2.7 and 6.2.9 since the connection address is valid and no primary local MR was allocated when the second SDP offer was sent. + +The P-CSCF-B forwards the 200 (OK) response to the PRACK request with the unmodified second SDP answer to IBCF-4 according to TS 24.229 [4]. + +#### **15. 183 (Session Progress) response (IBCF-4 - to IBCF-3) - see example in table A.5.2-15.** + +The IBCF-4 continues from the point in step 10 where the 183 (Session Progress) response was received with an initial SDP answer corresponding to the visited-realm 1 and no transcoding by IBCF-1 was required. + +The IBCF-4 uses the procedures in subclause 6.2.7 and 6.2.9 since a valid connection address was received in the 200 (OK) response to the UPDATE request and no MR was allocated when the second SDP offer was sent. + +The IBCF-4: + +- copies into the media line of the initial SDP answer the visited-realm instance 1 from the media line of the received initial SDP offer that was used to populate the connection address and port information in the forwarded second SDP offer, replacing the connection-address and port information in the instance with the connection address and port information from the received second SDP answer; +- replaces the connection address information in the initial SDP answer with the unspecified address of IPv4, "0.0.0.0"; and +- sends the 183 (Session Progress) response with the modified second SDP answer as the initial SDP answer to the IBCF-3 according to TS 24.229 [4]. + +**Table A.5.2-15: 183 (Session Progress) response (IBCF-4 - to IBCF-3)** + +``` + +SIP/2.0 183 Session Progress + +SIP headers according to 3GPP TS 24.229 [4] + +Content-Type: application/sdp +Content-Length: (...) + +v=0 +o=- 2987933615 2312345678 IN IP4 192.0.2.1 +s=- +b=AS:30 +b=RS:0 +b=RR:2000 +c=IN IP4 0.0.0.0 +m=audio 16511 RTP/AVP 96 97 +a=curr:qos local none +a=curr:qos remote none +a=des:qos mandatory local sendrecv +a=des:qos none remote sendrecv +a=rtpmap:96 telephone-event +a=rtpmap:97 AMR/8000/1 +a=fmtp:97 mode-change-capability=2; max-red=220; octet-align=1 +a=ptime:20 +a=maxptime:240 +a=visited-realm:1 Xa.operatorX.net IN IP4 192.0.2.4 16511 + +``` + +#### **16-17. 183 (Session Progress) response (IBCF-3 to IBCF-2 via intermediate IM CN subsystem entities) - see example in table A.5.2-16.** + +The IBCF-3 uses the procedures in subclauses 6.2.5 and 6.2.9 since the initial SDP answer contains an unspecified connection address and a visited-realm instance and the allocated MR is not needed. + +The IBCF-3 forwards the 183 (Session Progress) response with the unmodified initial SDP answer to the intermediate IM CN subsystem entities according to TS 24.229 [4]. + +The intermediate IM CN subsystem entities forwards the 183 (Session Progress) response with the unmodified initial SDP answer to the IBCF-2 according to TS 24.229 [4]. + +#### **18. 183 (Session Progress) response (IBCF-2 to IBCF-1) - see example in table A.5.2-16.** + +The IBCF-2 uses procedures in subclauses 6.2.5 and 6.2.9 since an unspecified connection address and a visited-realm instance was received and the allocated MR is not needed. + +IBCF-2: + +- forwards the 183 (Session Progress) response with the unmodified initial SDP answer to IBCF-1 according to TS 24.229 [4]; and +- keeps the allocated MR until it is no longer potentially needed for this and any other forked dialog. + +#### **19. 183 (Session Progress) response (IBCF-1 to P-CSCF-A) - see example in table A.5.2-19.** + +The IBCF-1 uses the procedures in subclauses 6.2.5 and 6.2.9 since an unspecified connection address and a visited-realm instance was received and the MR allocated for transcoding is not needed. + +- replaces the connection address and port information for the media line in the initial SDP answer with the connection address and port information from the visited-realm instance 1 in the received initial SDP answer; + +- forwards the 183 (Session Progress) response with the modified initial SDP answer to P-CSCF-A according to TS 24.229 [4]; and +- keeps the MR allocated for transcoding until it is no longer potentially needed for this and any other forked dialog. + +**Table A.5.2-19: 183 (Session Progress) response (IBCF-1 to P-CSCF-A)** + +``` + +SIP/2.0 183 Session Progress + +SIP headers according to 3GPP TS 24.229 [4] + +Content-Type: application/sdp +Content-Length: (...) + +v=0 +o=- 2987933615 2312345678 IN IP4 192.0.2.1 +s=- +b=AS:30 +b=RS:0 +b=RR:2000 +c=IN IP4 192.0.2.4 +m=audio 16511 RTP/AVP 96 97 +a=curr:qos local none +a=curr:qos remote none +a=des:qos mandatory local sendrecv +a=des:qos none remote sendrecv +a=rtpmap:96 telephone-event +a=rtpmap:97 AMR/8000/1 +a=fmtp:97 mode-change-capability=2; max-red=220; octet-align=1 +a=ptime:20 +a=maxptime:240 + +``` + +#### **20. 183 (Session Progress) response (P-CSCF-A to UE-A) - see example in table A.5.2-23.** + +The P-CSCF-A uses procedures in subclause 6.2.7 and 6.2.9 since a valid connection address is received and no MR was allocated when the SDP offer was sent. + +P-CSCF-A forwards the 183 (Session Progress) response with the unmodified initial SDP answer to the UE-B according to TS 24.229 [4]. + +#### **21-74. Remaining SIP message for establishing the call** + +The rest of the steps follow the same principles as described in subclause A.3.2 steps 17 – 65. + +## **A.6 Loopback routeing via an intermediate network** + +### **A.6.1 General** + +This subclause provides an example on how OMR is used to find an optimal media path when loopback routeing is used and how to preserve signalling paths and media paths compatible with the existing CS charging model. + +The example does not focus on the OMR algorithm as such instead the focus is on the selection and configuration of IP realm names. The example only describes the message flow on the originating side. + +Figure A.6.1-1 shows the IP realm and IP configuration used in this example. + +![Diagram showing IP realm and IP address configurations across Home IMS network H, IPX network X, and Visited network V. It details the hierarchy of network elements like S-CSCF, IBCF, TrGW, IC, MGW, P-CSCF, PCRF, PDN, and TRF, along with their associated IP addresses and realms.](2a476a0b3dbc3429436246db4784ff9f_img.jpg) + +The diagram illustrates the network architecture and IP address configurations for a roaming scenario. It is divided into three main network domains: + +- Home IMS network H: Realm Ha.operatorH.net** + - Contains an **S-CSCF/BGCF** at the top. + - Below it are two parallel paths, each consisting of an **IBCF** (IBCF-2 and IBCF-3), a **TrGW**, and an **Xa4** interface. + - IP addresses: IBCF-2/3 have **190.1.15.2 Ha**; TrGWs have **Xa4 179.14.1.2** and **179.14.1.3**. +- IPX network X: Realm Xa.operatorX.net** + - Connects to the Home network via the Xa4 interfaces. + - Contains two parallel paths with **IC** (IC-1 and IC-2), **MGW**, and **Xa2** interfaces. + - IP addresses: IC-1/2 have **179.14.1.1 Xa2** and **179.14.1.4 Xa2**; MGWs have **Xa2 178.15.1.2** and **178.15.1.3**. +- Visited network V: Realm Va.operatorV.net** + - Connects to the IPX network via the Xa2 interfaces. + - Contains two parallel paths with **IBCF** (IBCF-1 and IBCF-4), **TrGW**, and **Xa1** interfaces. + - IP addresses: IBCF-1/4 have **178.15.1.1 Xa1** and **178.15.1.4 Xa1**; TrGWs have **192.0.2.2** and **192.0.2.3**. + - A **TRF** (Traffic Router) is connected to IBCF-4. + - On the far right, another path includes **IBCF-5**, **TrGW**, and **Va 192.0.2.4**. + - At the bottom left, a **UE-A** (User Equipment) with IP **Va 192.0.2.1** is connected to a **P-CSCF-A**. + - P-CSCF-A** is connected to **IBCF-1** and has dashed connections to a **PCRF** and a **PDN** (PDN Gateway). + - Dashed lines represent the media path after OMR (Optimized Media Routing), connecting UE-A to IBCF-5 via the PDN. + +**Legend:** + +- Control signalling path:** Represented by solid double-headed arrows. +- Media path after OMR:** Represented by dashed double-headed arrows. + +Diagram showing IP realm and IP address configurations across Home IMS network H, IPX network X, and Visited network V. It details the hierarchy of network elements like S-CSCF, IBCF, TrGW, IC, MGW, P-CSCF, PCRF, PDN, and TRF, along with their associated IP addresses and realms. + +Figure A.6.1-1: IP realm and IP address configurations + +### A.6.2 Message flow + +The user A at UE-A is roaming into a visited network V. The user A is a subscriber of operator H. + +Preconditions in this example: + +- The user A is registered to the Home IMS network H via the visited operator V network and the IC network X; The IC network does not store any registration information. +- P-CSCF-A and S-CSCF support loopback routing; +- IBCF-1, IBCF-2, IBCF-3, IBCF-4, IBCF-5, IC-1 and IC-2 support OMR and all networks supports loopback routing; +- IBCF-1, IBCF-4 and IBCF-5 are instances in the same physical IBCF in the visited network V; +- IC-1 and IC-2 are instances in the same physical IC hub; +- IBCF-2 and IBCF-3 are instances in the same physical IBCF in the home network H; and +- no B2BUA manipulating SDP is connected in the home operator H network. + +Figure A.6.2-1 shows the message flow for the scenario. + +![Sequence diagram showing message flow for loopback routing via an IC network. The diagram spans across Visited network V, IC network X, and Home IMS network H (of user A). It details the flow of INVITE, 183, PRACK, UPDATE, and 200 OK messages between UE-A, P-CSCF-A, IBCF-1, IC1, IBCF-2, S-CSCF/BGCF, IBCF-3, IC2, IBCF-4, TRF, and IBCF-5. Each message includes specific SIP headers and SDP information like realm and IP addresses.](0931f3e098bd4539041de11c50cec2d2_img.jpg) + +The diagram illustrates the message flow for loopback routing via an IC network across five network domains: Visited network V, IC network X, Home IMS network H (of user A), IC network X, and Visited network V. The entities involved are UE-A, P-CSCF-A, IBCF-1, IC1, IBCF-2, S-CSCF/BGCF, IBCF-3, IC2, IBCF-4, TRF, and IBCF-5. The flow consists of several steps: + + +- 1. INVITE:** UE-A sends an INVITE request with SDP: AMR c=192.0.2.1 to P-CSCF-A. +- 2. INVITE:** P-CSCF-A forwards the INVITE with FC=TRF URI, PANI, and SDP: AMR c=192.0.2.1 to IBCF-1. +- 3. INVITE:** IBCF-1 adds visited-realm information (Va, Xa1, Xa2) and forwards it to IC1. +- 4. INVITE:** IC1 adds its own visited-realm information and forwards it to IBCF-2. +- 5. INVITE:** IBCF-2 forwards the request to S-CSCF/BGCF. +- 6. INVITE:** S-CSCF/BGCF adds more visited-realm information and forwards it to IBCF-3. +- 7. INVITE:** IBCF-3 forwards the request to IC2. +- 8. INVITE:** IC2 adds visited-realm information and forwards it to IBCF-4. +- 9. INVITE:** IBCF-4 forwards the request to TRF. +- 10. INVITE:** TRF forwards the request to IBCF-5. +- 11. 183:** IBCF-5 sends a 183 response back to TRF. +- 12. 183:** TRF forwards the 183 response to IBCF-4. +- 13. 183:** IBCF-4 forwards the 183 response to IC2. +- 14. 183:** IC2 forwards the 183 response to IBCF-3. +- 15. 183:** IBCF-3 forwards the 183 response to S-CSCF/BGCF. +- 16. 183:** S-CSCF/BGCF forwards the 183 response to IBCF-2. +- 17. 183:** IBCF-2 forwards the 183 response to IC1. +- 18. 183:** IC1 forwards the 183 response to IBCF-1. +- 19. 183:** IBCF-1 forwards the 183 response to P-CSCF-A. +- 20. 183:** P-CSCF-A forwards the 183 response to UE-A. +- 21. PRACK:** A PRACK message is sent from UE-A to P-CSCF-A without an SDP offer. +- 22. UPDATE:** An UPDATE message is sent from UE-A to P-CSCF-A following the same principles as in subclause A.3.2 steps 33 - 48. +- 23. 180 Ringing:** A 180 Ringing message is sent from UE-A to P-CSCF-A (Resources are reserved and no update needed since a=conf was not included by the UE-A). +- 24. 200 OK:** A 200 OK message is sent from UE-A to P-CSCF-A (without SDP) and ACK. + + Resource authorization and Resource reservation steps are also indicated in the diagram. + +Sequence diagram showing message flow for loopback routing via an IC network. The diagram spans across Visited network V, IC network X, and Home IMS network H (of user A). It details the flow of INVITE, 183, PRACK, UPDATE, and 200 OK messages between UE-A, P-CSCF-A, IBCF-1, IC1, IBCF-2, S-CSCF/BGCF, IBCF-3, IC2, IBCF-4, TRF, and IBCF-5. Each message includes specific SIP headers and SDP information like realm and IP addresses. + +Figure A.6.2-1: Message flow for loopback routing via an IC network + +NOTE: For clarity, the SIP 100 (Trying) messages are not shown in the signalling flow. + +The steps of the flow are as follows: + +#### **1. INVITE request (UE-A to P-CSCF-A) - see example in table A.6.2-1.** + +The user A at UE-A initiates a call. The UE-A sends an initial INVITE request containing an initial SDP offer to the P-CSCF-A according to TS 24.229 [4]. + +**Table A.6.2-1: INVITE request (UE-A to P-CSCF-A)** + +``` + +INVITE SIP: tel:+4687197378; SIP/2.0 + +Route: + +Other SIP headers according to 3GPP TS 24.229 [4] + +Content-Type: application/sdp +Content-Length: (...) + +v=0 +o=- 2987933615 2987933615 IN IP4 192.0.2.1 +s= +t=0 0 +c=IN IP4 192.0.2.1 +m=audio 49170 RTP/AVP 96 97 +a=curr:qos local none +a=curr:qos remote none +a=des:qos mandatory local sendrecv +a=des:qos optional remote sendrecv +a=rtpmap:97 AMR +a=fmtp:97 mode-set=0,2,5,7; mode-change-period=2 +a=rtpmap:96 telephone-event +a=maxptime:20 + +``` + +#### 2. INVITE request (P-CSCF-A to IBCF-1) - see example in table A.6.2-2. + +When the P-CSCF-A receives the initial INVITE request and, since the user A is a roaming user, the P-CSCF-A adds the Feature-Caps header field with the g.3gpp.trf with the address to the TRF; and + +The P-CSCF-A selects an IBCF (IBCF-1) to be the exit IBCF towards the home IMS network H of the user A and sends the INVITE request without modifying the initial SDP offer according to TS 24.229 [4] to IBCF-1. + +**Table A.6.2-1: INVITE request (P-CSCF-A to IBCF-1)** + +``` + +INVITE SIP: tel:+4687197378; SIP/2.0 + +Route: +Feature-Caps:+g.3gpp.trf="" +P-Access-Network-Info:3GPP-UTRAN-TDD;utran-cell-id-3gpp=234151D0FCE11 +P-Charging-Vector: icid-value="AyretyU0dm+6O2IrT5tAFrbHLso=023551024" + +Other SIP headers according to 3GPP TS 24.229 [4] + +Content-Type: application/sdp +Content-Length: (...) + +v=0 +o=- 2987933615 2987933615 IN IP4 192.0.2.1 +s= +t=0 0 +c=IN IP4 192.0.2.1 +m=audio 49170 RTP/AVP 96 97 +a=curr:qos local none +a=curr:qos remote none +a=des:qos mandatory local sendrecv +a=des:qos none remote sendrecv +a=rtpmap:97 AMR +a=fmtp:97 mode-set=0,2,5,7; mode-change-period=2 +a=rtpmap:96 telephone-event +a=maxptime:20 + +``` + +#### 3. INVITE request (IBCF-1 to IC-1) - see example in table A.6.2-3. + +When the IBCF-1 receives the initial INVITE request containing the "+g.3gpp.trf" header field parameter in a Feature-Caps header field, the IBCF-1 updates the SDP as follows: + +- the media parameters received from the TrGW are included in the initial SDP offer; +- the IP address, port number and the IP realm Va.operatorV.net of the UE-A is included as the visited-realm 1 instance; + +- the IP address, port number of the TrGW and the local IP realm Xa1.operatorX.net are included as the visited-realm 2 instance. To avoid unwanted optimal media paths being created the local IP realm Xa1.operatorX.net is selected as this is a local IP realm only known by the IBCF-1, IBCF-4 and IBCF-5. + +The IBCF-1 selects to route the INVITE request via an IC network and sends the INVITE request with the modified SDP offer according to TS 24.229 [4] to the IC-1. + +**Table A.6.2-3: INVITE request (IBCF-1 to IC-1)** + +``` +INVITE SIP: tel:+4687197378; SIP/2.0 + +Route: +Feature-Caps:+g.3gpp.trf="" +P-Access-Network-Info:3GPP-UTRAN-TDD;utran-cell-id-3gpp=234151D0FCE11 +P-Charging-Vector: icid-value="AyretyU0dm+6O2IrT5tAFrbHLso=023551024" + +Other SIP headers according to 3GPP TS 24.229 [4] + +Content-Type: application/sdp +Content-Length: (...) + +v=0 +o= 2987933615 2987933615 IN IP4 192.0.2.1 +s= +t=0 0 +c=IN IP4 178.15.1.1 +m=audio 62111 RTP/AVP 96 97 +a=curr:qos local none +a=curr:qos remote none +a=des:qos mandatory local sendrecv +a=des:qos none remote sendrecv +a=rtpmap:97 AMR +a=fmtp:97 mode-set=0,2,5,7; mode-change-period=2 +a=rtpmap:96 telephone-event +a=maxptime:20 +a=visited-realm:1 Va.operatorV.net IN IP4 192.0.2.1 49170 +a=visited-realm:2 Xa1.operatorX.net IN IP4 178.15.1.1 62111 +a=omr-m-cksum:(..) +a=omr-s-cksum:0 +``` + +#### 4. INVITE request (IC-1 to IBCF-2) - see example in table A.6.2-4. + +When the IC-1 receives the initial INVITE request and since the IC-1 according to local policy allows itself to be bypassed by media then the IC-1 updates the initial SDP offer as follows: + +- the media parameters of the IC-1 are included in the initial SDP offer; and +- the IP address, port number of the IC-1 and the local IP realm Xa2.operatorX.net are included as the visited-realm 3 instance. To avoid unwanted optimal media paths being created the local IP realm Xa2.operatorX.net is selected as this is a local IP realm only known by the IC-1 and IC-2. + +The IC-1 selects an entry IBCF of the home IMS network H and sends the INVITE request with the modified initial SDP offer according to TS 24.229 [4] to the IBCF-2. + +**Table A.6.2-4: INVITE request (IC-1 to IBCF-2)** + +``` + +INVITE SIP: tel:+4687197378; SIP/2.0 + +Route: +Feature-Caps:+g.3gpp.trf="" +P-Access-Network-Info:3GPP-UTRAN-TDD;utran-cell-id-3gpp=234151D0FCE11 +P-Charging-Vector: icid-value="AyretyU0dm+6O2IrT5tAFrbHLso=023551024";orig-ioi="Va.operatorV.net" + +Other SIP headers according to 3GPP TS 24.229 [4] + +Content-Type: application/sdp +Content-Length: (...) + +v=0 +o= 2987933615 2987933615 IN IP4 192.0.2.1 +s= +t=0 0 +c=IN IP4 179.14.1.1 +m=audio 52211 RTP/AVP 96 97 +a=curr:qos local none +a=curr:qos remote none +a=des:qos mandatory local sendrecv +a=des:qos none remote sendrecv +a=rtpmap:97 AMR +a=fmtp:97 mode-set=0,2,5,7; mode-change-period=2 +a=rtpmap:96 telephone-event +a=maxptime:20 +a=visited-realm:1 Va.operatorV.net IN IP4 192.0.2.1 49170 +a=visited-realm:2 Xal.operatorX.net IN IP4 178.15.1.1 62111 +a=visited-realm:3 Xa2.operatorX.net IN IP4 179.14.1.1 52211 +a=omr-m-cksum:(..) +a=omr-s-cksum:0 + +``` + +#### 5. INVITE request (IBCF-2 to S-CSCF) - see example in table A.6.2-5. + +When the IBCF-2 receives the initial INVITE request containing the "+g.3gpp.trf" header field parameter in a Feature-Caps header field, the IBCF-2 updates the initial SDP offer as follows: + +- the media parameters of the TrGW are included in the initial SDP offer; and +- the IP address, port number of the TrGW and the IP realm Ha.operatorH.net are included as the visited-realm 4 instance. + +The IBCF-2 sends the INVITE request with the modified initial SDP offer according to TS 24.229 [4] to the S-CSCF. + +**Table A.6.2-5: INVITE request (IBCF-2 to S-CSCF)** + +``` + +INVITE SIP: tel:+4687197378; SIP/2.0 + +Route: +Feature-Caps:+g.3gpp.trf ="" +P-Access-Network-Info:3GPP-UTRAN-TDD;utran-cell-id-3gpp=234151D0FCE11 +P-Charging-Vector: icid-value="AyretyU0dm+6O2IrT5tAFrbHLso=023551024";orig-ioi="Va.operatorV.net" + +Other SIP headers according to 3GPP TS 24.229 [4] + +Content-Type: application/sdp +Content-Length: (...) + +v=0 +o= 2987933615 2987933615 IN IP4 192.0.2.1 +s= +t=0 0 +c=IN IP4 190.1.15.1 +m=audio 16789 RTP/AVP 96 97 +a=curr:qos local none +a=curr:qos remote none +a=des:qos mandatory local sendrecv +a=des:qos none remote sendrecv +a=rtpmap:97 AMR +a=fmtp:97 mode-set=0,2,5,7; mode-change-period=2 +a=rtpmap:96 telephone-event +a=maxptime:20 +a=visited-realm:1 Va.operatorV.net IN IP4 192.0.2.1 49170 +a=visited-realm:2 Xal.operatorX.net IN IP4 178.15.1.1 62111 +a=visited-realm:3 Xa2.operatorX.net IN IP4 179.14.1.1 52211 +a=visited-realm:4 Ha.operatorH.net IN IP4 190.1.15.1 16789 +a=omr-m-cksum:(..) +a=omr-s-cksum:0 + +``` + +#### **6. INVITE request (S-CSCF to IBCF-3) - see example in table A.6.2-6.** + +When the S-CSCF receives the initial INVITE request the S-CSCF decides according to local policy that loopback routeing shall be used. + +The S-CSCF: + +- includes the TRF URI included in the g.3gpp.trf in the Route header field; and +- includes in a Feature-Caps header field the feature tag +g.3gpp.loopback to indicate that loopback routeing is ongoing. + +NOTE: Number normalization and ENUM translation is deferred to the visited network. + +The S-CSCF/BGCF selects an entry IBCF and sends the INVITE request with the modified initial SDP offer according to TS 24.229 [4] to the IBCF-3. + +**Table A.6.2-6: INVITE request (S-CSCF to IBCF-3)** + +``` + +INVITE SIP: tel:+4687197378; SIP/2.0 + +Route: +Feature-Caps:+g.3gpp.loopback +P-Access-Network-Info:3GPP-UTRAN-TDD;utran-cell-id-3gpp=234151D0FCE11 +P-Charging-Vector: icid-value="AyretyU0dm+6O2IrT5tAFrbHLso=023551024" + +Other SIP headers according to 3GPP TS 24.229 [4] + +Content-Type: application/sdp +Content-Length: (...) + +v=0 +o=- 2987933615 2987933615 IN IP4 192.0.2.1 +s= +t=0 0 +c=IN IP4 190.1.15.1 +m=audio 16789 RTP/AVP 96 97 +a=curr:qos local none +a=curr:qos remote none +a=des:qos mandatory local sendrecv +a=des:qos none remote sendrecv +a=rtpmap:97 AMR +a=fmtp:97 mode-set=0,2,5,7; mode-change-period=2 +a=rtpmap:96 telephone-event +a=maxptime:20 +a=visited-realm:1 Va.operatorV.net IN IP4 192.0.2.1 49170 +a=visited-realm:2 Xal.operatorX.net IN IP4 178.15.1.1 62111 +a=visited-realm:3 Xa2.operatorX.net IN IP4 179.14.1.1 52211 +a=visited-realm:4 Ha.operatorH.net IN IP4 190.1.15.1 16789 +a=omr-m-cksum:(...) +a=omr-s-cksum:0 + +``` + +#### 7. INVITE request (IBCF-3 to IC-2) - see example in table A.6.2-7. + +When the IBCF-3 receives the initial INVITE request containing the "+g.3gpp.loopback" header field parameter in a Feature-Caps header field, the IBCF-3 updates the initial SDP offer as follows: + +- the media parameters of the TrGW are included in the initial SDP offer; and +- the IP address, port number of the TrGW and the local IP realm Xa4.operatorX.net are included as the visited-realm 5 instance. To avoid unwanted optimal media paths being created the local IP realm Xa4.operatorX.net is selected as this is a local IP realm only known by the IBCF-2 and IBCF-3. + +The IBCF-3 selects to route the INVITE request via an IC network and sends the INVITE request with the modified initial SDP offer according to TS 24.229 [4] to the IC-2. + +**Table A.6.2-7: INVITE request (IBCF-3 to IC-2)** + +``` + +INVITE SIP: tel:+4687197378; SIP/2.0 + +Route: +Feature-Caps:+g.3gpp.loopback +P-Access-Network-Info:3GPP-UTRAN-TDD;utran-cell-id-3gpp=234151D0FCE11 +P-Charging-Vector:icid-value="AyretyU0dm+6O2IrT5tAFrbHLso=023551024" + +Other SIP headers according to 3GPP TS 24.229 [4] + +Content-Type: application/sdp +Content-Length: (...) + +v=0 +o= 2987933615 2987933615 IN IP4 192.0.2.1 +s= +t=0 0 +c=IN IP4 179.14.1.3 +m=audio 34500 RTP/AVP 96 97 +a=curr:qos local none +a=curr:qos remote none +a=des:qos mandatory local sendrecv +a=des:qos none remote sendrecv +a=rtpmap:97 AMR +a=fmtp:97 mode-set=0,2,5,7; mode-change-period=2 +a=rtpmap:96 telephone-event +a=maxptime:20 +a=visited-realm:1 Va.operatorV.net IN IP4 192.0.2.1 49170 +a=visited-realm:2 Xal.operatorX.net IN IP4 178.15.1.1 62111 +a=visited-realm:3 Xa2.operatorX.net IN IP4 179.14.1.1 52211 +a=visited-realm:4 Ha.operatorH.net IN IP4 190.1.15.1 16789 +a=visited-realm:5 Xa4.operatorX.net IN IP4 179.14.1.3 34500 +a=omr-m-cksum:(..) +a=omr-s-cksum:0 + +``` + +#### **8. INVITE request (IC-2 to IBCF-4) - see example in table A.6.2-8.** + +When the IC-2 receives the initial INVITE request the IC-2 detects that an optimal media path avoiding media to be sent through the home IMS network H is possible. The IC-2 updates initial the SDP offer as follows: + +- the IP address and port number included by IC-1 in visited-realm instance 3 are included in the initial SDP offer; and +- the visited-realm instances 4 and 5 are removed so that the media path is no longer passing the home IMS network H. + +The IC-2 selects an entry IBCF in the visited network and sends the INVITE request with the modified initial SDP offer according to TS 24.229 [4] to the IBCF-4. + +**Table A.6.2-8: INVITE request (IC-2 to IBCF-4)** + +``` + +INVITE SIP: tel:+4687197378; SIP/2.0 + +Route: +Feature-Caps:+g.3gpp.loopback +P-Access-Network-Info:3GPP-UTRAN-TDD;utran-cell-id-3gpp=234151D0FCE11 +P-Charging-Vector: icid-value="AyretyU0dm+6O2IrT5tAFrbHLso=023551024" + +Other SIP headers according to 3GPP TS 24.229 [4] + +Content-Type: application/sdp +Content-Length: (...) + +v=0 +o= 2987933615 2987933615 IN IP4 192.0.2.1 +s= +t=0 0 +c=IN IP4 179.14.1.1 +m=audio 52211 RTP/AVP 96 97 +a=curr:qos local none +a=curr:qos remote none +a=des:qos mandatory local sendrecv +a=des:qos none remote sendrecv +a=rtpmap:97 AMR +a=fmtp:97 mode-set=0,2,5,7; mode-change-period=2 +a=rtpmap:96 telephone-event +a=maxptime:20 +a=visited-realm:1 Va.operatorV.net IN IP4 192.0.2.1 49170 +a=visited-realm:2 Xal.operatorX.net IN IP4 178.15.1.1 62111 +a=visited-realm:3 Xa2.operatorX.net IN IP4 179.14.1.1 52211 +a=omr-m-cksum:(..) +a=omr-s-cksum:0 + +``` + +#### **9. INVITE request (IBCF-4 to TRF) - see example in table A.6.2-9.** + +When the IBCF-4 receives the initial INVITE request containing the "+g.3gpp.loopback" header field parameter in a Feature-Caps header field, the IBCF-4 searches for a possible optimal media path and detects that an optimal media path within the visited network is possible. The IBCF-4 updates the initial SDP offer as follows: + +- the IP address and port numbers in the visited-realm instance 1 is included in the initial SDP offer; and +- the visited-realm instances 2 and 3 are removed so that the media path is no longer passing the IC network. + +The IBCF-4 sends the INVITE request with the modified initial SDP offer according to TS 24.229 [4] to the TRF. + +**Table A.6.2-9: INVITE request (IBCF-4 to TRF)** + +``` + +INVITE SIP: tel:+4687197378; SIP/2.0 + +Route: +Feature-Caps:+g.3gpp.loopback +P-Access-Network-Info:3GPP-UTRAN-TDD;utran-cell-id-3gpp=234151D0FCE11 +P-Charging-Vector: icid-value="AyretyU0dm+6O2IrT5tAFrbHLso=023551024" + +Other SIP headers according to 3GPP TS 24.229 [4] + +Content-Type: application/sdp +Content-Length: (...) + +v=0 +o=- 2987933615 2987933615 IN IP4 192.0.2.1 +s= +t=0 0 +c=IN IP4 192.0.2.1 +m=audio 49170 RTP/AVP 96 97 +a=curr:qos local none +a=curr:qos remote none +a=des:qos mandatory local sendrecv +a=des:qos none remote sendrecv +a=rtpmap:97 AMR +a=fmtp:97 mode-set=0,2,5,7; mode-change-period=2 +a=rtpmap:96 telephone-event +a=maxptime:20 +a=visited-realm:1 Va.operatorV.net IN IP4 192.0.2.1 49170 +a=omr-m-cksum:(..) +a=omr-s-cksum:0 + +``` + +#### **10. INVITE request (TRF to IBCF-5) - see example in table A.6.2-10.** + +When the TRF receives the initial INVITE request the TRF: + +- performs number normalization and ENUM translation and updates the Request-URI if necessary; and +- appends "iotl" SIP URI parameter with the value "visitedA-homeB" to the Request-URI. + +The TRF selects an exit IBCF and sends the INVITE request with the unmodified initial SDP offer according to TS 24.229 [4] to the IBCF-5. + +**Table A.6.2-10: INVITE request (TRF to IBCF-5)** + +``` + +INVITE SIP: SIP/2.0 + +Feature-Caps:+g.3gpp.omr="disable-omr" +P-Access-Network-Info:3GPP-UTRAN-TDD;utran-cell-id-3gpp=234151D0FCE11 +P-Charging-Vector: icid-value="AyretyU0dm+6O2IrT5tAFrbHLso=023551024";orig-ioi="Va.operatorV.net" + +Other SIP headers according to 3GPP TS 24.229 [4] + +Content-Type: application/sdp +Content-Length: (...) + +v=0 +o=- 2987933615 2987933615 IN IP4 192.0.2.1 +s= +t=0 0 +c=IN IP4 192.0.2.1 +m=audio 49170 RTP/AVP 96 97 +a=curr:qos local none +a=curr:qos remote none +a=des:qos mandatory local sendrecv +a=des:qos none remote sendrecv +a=rtpmap:97 AMR +a=fmtp:97 mode-set=0,2,5,7; mode-change-period=2 +a=rtpmap:96 telephone-event +a=maxptime:20 +a=visited-realm:1 Va.operatorV.net IN IP4 192.0.2.1 49170 +a=omr-m-cksum:(..) +a=omr-s-cksum:0 + +``` + +#### **11. 183 (Session Progress) response (IBCF-5 to TRF) - see example in table A.6.2-11.** + +When the IBCF-5 receives the initial INVITE request the IBCF-5 sends the INVITE request towards the terminating network. The INVITE request may or may not include OMR specific parameters based on the IBCF-5 local policy. + +When the IBCF-5 receives an initial SDP answer in a 183 (Session Progress) response from the terminating network the IBCF-5: + +- includes its own IP address and port number received from the TrGW in the initial SDP answer. + +The IBCF sends the 183 (Session Progress) response with the modified initial SDP answer according to TS 24.229 [4] to the TRF. + +**Table A.6.2-11: 183 (Session Progress) response (IBCF-5 to TRF)** + +``` +SIP/2.0 183 Session Progress + +P-Charging-Vector: icid-value="AyretyU0dm+6O2IrT5tAFrbHLso=023551024";term-ioi="y.operatorY.net" + +Other SIP headers according to 3GPP TS 24.229 [4] + +Content-Type: application/sdp +Content-Length: (...) + +v=0 +o=- 2987933615 2987933615 IN IP4 192.0.2.1 +s=- +c=IN IP4 192.0.2.4 +t=0 0 +m=audio 16511 RTP/AVP 97 98 +a=curr:qos local none +a=curr:qos remote none +a=des:qos mandatory local sendrecv +a=des:qos none remote sendrecv +a=rtpmap:98 AMR +a=fmtp:98 mode-set=0,2,5,7; mode-change-period=2 +a=rtpmap:97 telephone-event +a=maxptime:20 +a=visited-realm:1 Va.operatorV.net IN IP4 192.0.2.4 16511 +``` + +#### **12. 183 (Session Progress) response (TRF to IBCF-4) - see example in table A.6.2-12.** + +When the TRF receives the 183 (Session Progress) response the TRF stores the received term-ioi; and + +The TRF sends the 183 (Session Progress) response with the unmodified initial SDP answer according to TS 24.229 [4] to the IBCF-4. + +**Table A.6.2-12: 183 (Session Progress) response (TRF to IBCF-4)** + +``` +SIP/2.0 183 Session Progress + +SIP headers according to 3GPP TS 24.229 [4] + +Content-Type: application/sdp +Content-Length: (...) + +v=0 +o=- 2987933615 2987933615 IN IP4 192.0.2.1 +s=- +c=IN IP4 192.0.2.4 +t=0 0 +m=audio 16511 RTP/AVP 97 98 +a=curr:qos local none +a=curr:qos remote none +a=des:qos mandatory local sendrecv +a=des:qos none remote sendrecv +a=rtpmap:98 AMR +a=fmtp:98 mode-set=0,2,5,7; mode-change-period=2 +a=rtpmap:97 telephone-event +a=maxptime:20 +a=visited-realm:1 Va.operatorV.net IN IP4 192.0.2.4 16511 +``` + +#### **13-15. 183 (Session Progress) response (IBCF-4 to S-CSCF via IC-2 and IBCF-3) - see example in table A.6.2-13.** + +When the IBCF-4 receives the 183 (Session Progress) response the IBCF-4 updates the initial SDP answer as follows: + +- The c=IN IP4 192.0.2.4 is replaced with an invalid IPv4 address, i.e. c=IN IP4 0.0.0.0, since the IP realm on visited network side and the IC network side are not the same hence the received IP address is not valid on the IC side. + +The IBCF-4 sends the 183 (Session Progress) response with the modified initial SDP answer according to TS 24.229 [4] towards the S-CSCF via the IC-2 and IBCF-3. Neither the IC-2 nor the IBCF-3 updates the SDP. + +**Table A.6.2-13: 183 (Session Progress) response (IBCF-4 to S-CSCF via IC-2 and IBCF-3)** + +``` +SIP/2.0 183 Session Progress + +SIP headers according to 3GPP TS 24.229 [4] + +Content-Type: application/sdp +Content-Length: (...) + +v=0 +o=- 2987933615 2987933615 IN IP4 192.0.2.1 +s=- +c=IN IP4 0.0.0.0 +t=0 0 +m=audio 16511 RTP/AVP 97 98 +a=curr:qos local none +a=curr:qos remote none +a=des:qos mandatory local sendrecv +a=des:qos none remote sendrecv +a=rtpmap:98 AMR +a=fmtp:98 mode-set=0,2,5,7; mode-change-period=2 +a=rtpmap:97 telephone-event +a=maxptime:20 +a=visited-realm:1 Va.operatorV.net IN IP4 192.0.2.4 16511 +``` + +**16-18. 183 (Session Progress) response (S-CSCF to IBCF-1 via IBCF-2 and IC-1) - see example in table A.6.2-16.** + +The S-CSCF sends the 183 (Session Progress) response according to TS 24.229 [4] to the IBCF-1. Neither the IBCF-2 nor IC-1 updates the initial SDP answer. + +**Table A.6.2-16: 183 (Session Progress) response (S-CSCF to IBCF-1 via IBCF-2 and IC-1)** + +``` +SIP/2.0 183 Session Progress + +SIP headers according to 3GPP TS 24.229 [4] + +Content-Type: application/sdp +Content-Length: (...) + +v=0 +o=- 2987933615 2987933615 IN IP4 192.0.2.1 +s=- +c=IN IP4 0.0.0.0 +t=0 0 +m=audio 16511 RTP/AVP 97 98 +a=curr:qos local none +a=curr:qos remote none +a=des:qos mandatory local sendrecv +a=des:qos none remote sendrecv +a=rtpmap:98 AMR +a=fmtp:98 mode-set=0,2,5,7; mode-change-period=2 +a=rtpmap:97 telephone-event +a=maxptime:20 +a=visited-realm:1 Va.operatorV.net IN IP4 192.0.2.4 16511 +``` + +**19. 183 (Session Progress) response (IBCF-1 to P-CSCF-A) - see example in table A.6.2-19.** + +When the IBCF-1 receives the 183 (Session Progress) response the IBCF-1 updates the initial SDP answer. + +The IBCF-1: + +- replaces the received invalid IPv4 address with the IP address received in the visited-realm instance 1; and + +- removes all OMR specific attributes since the initial SDP offer from P-CSCF-A did not contain any OMR specific attributes. + +The IBCF-1 sends the 183 (Session Progress) response with the modified initial SDP answer according to TS 24.229 [4] to the P-CSCF-A. + +**Table A.6.2-19: 183 (Session Progress) response (IBCF-1 to P-CSCF-A)** + +``` +SIP/2.0 183 Session Progress + +SIP headers according to 3GPP TS 24.229 [4] + +Content-Type: application/sdp +Content-Length: (...) + +v=0 +o=- 2987933615 2987933615 IN IP4 192.0.2.1 +s=- +c=IN IP4 192.0.2.4 +t=0 0 +m=audio 16511 RTP/AVP 97 98 +a=curr:qos local none +a=curr:qos remote none +a=des:qos mandatory local sendrecv +a=des:qos none remote sendrecv +a=rtpmap:98 AMR +a=fmtp:98 mode-set=0,2,5,7; mode-change-period=2 +a=rtpmap:97 telephone-event +a=maxptime:20 +``` + +#### 20. 183 (Session Progress) response (P-CSCF-A to UE-A) - see example in table A.6.2-20. + +When the P-CSCF-A receives the 183 (Session Progress) response the P-CSCF authorizes the resources; + +The P-CSCF-A sends the 183 (Session Progress) response with the unmodified initial SDP answer according to TS 24.229 [4] to the UE-A. + +**Table A.6.2-20: 183 (Session Progress) response (P-CSCF-A to the UE-A)** + +``` +SIP/2.0 183 Session Progress + +SIP headers according to 3GPP TS 24.229 [4] + +Content-Type: application/sdp +Content-Length: (...) + +v=0 +o=- 2987933615 2987933615 IN IP4 192.0.2.1 +s=- +c=IN IP4 192.0.2.4 +t=0 0 +m=audio 16511 RTP/AVP 97 98 +a=curr:qos local none +a=curr:qos remote none +a=des:qos mandatory local sendrecv +a=des:qos none remote sendrecv +a=rtpmap:98 AMR +a=fmtp:98 mode-set=0,2,5,7; mode-change-period=2 +a=rtpmap:97 telephone-event +a=maxptime:20 +``` + +#### 21. PRACK requests and SIP 200 (OK) response to the SIP PRACK request + +The PRACK is sent without any SDP offer/SDP answer between the UE-A and IBCF-5 according to TS 24.229 [4]. + +#### 22. UPDATE request and SIP 200 (OK) response to the SIP UPDATE request + +The UPDATE request and the 200 (OK) response to the UPDATE request is sent with a subsequent SDP offer and subsequent SDP answer following the same principle as in clause A.3.2 steps 33 - 48 but now indicating that resources are reserved at UE-A. + +#### **23. 180 (Ringing) response to INVITE request** + +The remote UE sends a 180 (Ringing) response when resources are reserved. The remote UE does not have to send an UPDATE request to indicate that resources are reserved since the subsequent SDP offer did not include the "a=conf" attribute. + +When the IBCF-5 receives the response the IBCF-5 forwards the response to the UE-A via all intermediate nodes. There are no OMR specific actions since the 180 (Ringing) response does not contain any SDP. + +#### **24. 200 (OK) response to INVITE request and the SIP ACK request** + +The 200 (OK) response to the initial INVITE request is sent according to TS 24.229 [4] between the IBCF-5 and UE-A via all intermediate nodes as specified in TS 24.229 [4]. + +The ACK request is sent according to TS 24.229 [4] between the UE-A and IBCF-5 via all intermediate nodes as specified in TS 24.229 [4]. + +# Annex B (informative): Change history + +| Change history | | | | | | | | +|----------------|--------|-----------|------|-----|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------|--------| +| Date | TSG # | TSG Doc. | CR | Rev | Subject/Comment | Old | New | +| 11.30.10 | | | | | Version 1.0.0 was created by MCC | 0.3.0 | 1.0.0 | +| 01.31.11 | | | | | Version 1.1.0 created by rapporteur based on PCRs C3-110028, C3-110030, C3-110031, C3-110032, C3-110033, C3-110034, C3-110233, C3-110234, C3-110235, C3-110238, C3-110374, C3-110375, C3-110376 | 1.0.0 | 1.1.0 | +| 02.28.11 | | | | | Version 1.2.0 created by rapporteur based on PCRs C3-110472, C3-110579, C3-110580, C3-110582, C3-110601, C3-110603, C3-110604, C3-110605, C3-110650, C3-110651, C3-110696, C3-110699, C3-110723, C3-110755 | 1.1.0 | 1.2.0 | +| 03/2011 | TSG#51 | | | | 3GPP TS 29.079 2.0.0 have been approved in TSG#51 | 2.0.0 | 10.0.0 | +| 06/2011 | TSG#52 | CP-110408 | 1 | 2 | Adding session checksum in the simple example flow | 10.0.0 | 10.1.0 | +| 06/2011 | TSG#52 | CP-110408 | 2 | 2 | Update of proactive transcoder without resource reservation FLOW | 10.0.0 | 10.1.0 | +| 06/2011 | TSG#52 | CP-110408 | 3 | 3 | Clarifying checksum calculation | 10.0.0 | 10.1.0 | +| 06/2011 | TSG#52 | CP-110408 | 4 | 3 | Receiving and modified SDP offer clarification | 10.0.0 | 10.1.0 | +| 06/2011 | TSG#52 | CP-110408 | 5 | 2 | IMS-ALG bypasses an allocated transcoding MR - FLOW | 10.0.0 | 10.1.0 | +| 06/2011 | TSG#52 | CP-110408 | 6 | 2 | Enhanced IP realm definition | 10.0.0 | 10.1.0 | +| 06/2011 | TSG#52 | CP-110408 | 7 | 2 | Making connected IP realm information available | 10.0.0 | 10.1.0 | +| 09/2011 | TSG#53 | | | | Editorial Improvement by MCC | 10.1.0 | 10.1.1 | +| 12/2011 | TSG#54 | CP-110834 | 8 | | Updated references - Media Control Channel Framework | 10.1.1 | 10.2.0 | +| 06/2012 | TSG#56 | CP-120355 | 9 | 3 | RAVEL Loop-back routing example updates | 10.2.0 | 11.0.0 | +| 06/2012 | TSG#56 | CP-120357 | 10 | | Incorrect IP address in example | 10.2.0 | 11.0.0 | +| 09/2012 | TSG#57 | CP-120535 | 13 | | OMR modification | 11.0.0 | 11.1.0 | +| 09/2012 | TSG#57 | CP-120535 | 14 | 1 | Naming of transit network | 11.0.0 | 11.1.0 | +| 12/2012 | TSG#58 | CP-120840 | 15 | 1 | Updating loopback example | 11.1.0 | 11.2.0 | +| 12/2012 | TSG#58 | CP-120827 | 18 | | Reference update of draft-ietf-mediactrl-mixer-control-package | 11.1.0 | 11.2.0 | +| 12/2012 | TSG#58 | CP-120827 | 20 | 2 | OMR Signalling Flows | 11.1.0 | 11.2.0 | +| 03/2013 | TSG#59 | CP-130079 | 16 | 4 | Identifying an RAVEL session | 11.2.0 | 11.3.0 | +| 03/2013 | TSG#59 | CP-130079 | 21 | | Removing all editors notes in the loopback flow | 11.2.0 | 11.3.0 | +| 06-2014 | TSG#64 | CP-140362 | 024 | 2 | Correcting IP addresses on OMR call flow examples | 11.3.0 | 11.4.0 | +| 09-2014 | CT-65 | CP-140528 | 0031 | 1 | Message flow correction for media bypassing all IMS-ALGs | 11.4.0 | 11.5.0 | +| 09-2014 | CT-65 | CP-140528 | 0027 | 2 | Correcting references | 11.4.0 | 11.5.0 | +| 03-2015 | CT-67 | CP-150100 | 0035 | | Instance-number value for secondary-realm | 11.5.0 | 11.6.0 | +| 03-2015 | CT-67 | CP-150100 | 0038 | | Checksum calculation | 11.5.0 | 11.6.0 | +| 03-2015 | CT-67 | CP-150100 | 0041 | | Correcting UA procedure | 11.5.0 | 11.6.0 | +| 06-2015 | CT-68 | CP-150340 | 0048 | 2 | Procedures for avoiding changes in the OMR algorithm outcome on subsequent SDP offer/answer transactions | 11.6.0 | 11.7.0 | \ No newline at end of file diff --git a/marked/Rel-11/29_series/29108/raw.md b/marked/Rel-11/29_series/29108/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..0c289b2ca5cda683ee5842c6478a2ca6221cf265 --- /dev/null +++ b/marked/Rel-11/29_series/29108/raw.md @@ -0,0 +1,404 @@ + + + + + + +# --- Contents + +| | | +|------------------------------------------------------------------------------------------------------------------|----| +| Foreword ..... | 4 | +| 1 Scope..... | 5 | +| 2 References..... | 5 | +| 3 Abbreviations ..... | 5 | +| 4 Principles for the use of RANAP on the E-interface ..... | 6 | +| 4.1 General ..... | 6 | +| 4.2 Transfer of RANAP layer 3 messages on the E-interface..... | 6 | +| 4.3 Roles of 3G_MSC-A, 3G_MSC-I and 3G_MSC-T ..... | 6 | +| 5 Use of the RANAP on the E-interface ..... | 7 | +| 5.1 RAB Assignment..... | 7 | +| 5.2 RAB Release Request ..... | 8 | +| 5.3 Iu Release Request ..... | 8 | +| 5.4 Relocation Resource Allocation..... | 8 | +| 5.5 Relocation Cancel ..... | 8 | +| 5.6 Relocation Detect and Relocation Complete ..... | 9 | +| 5.7 CN Trace invocation ..... | 9 | +| 5.8 Security mode control ..... | 9 | +| 5.9 Location Reporting Control ..... | 9 | +| 5.10 Location Report..... | 9 | +| 5.11 Direct Transfer ..... | 10 | +| 5.12 Error Indication ..... | 10 | +| 5.13 CN Deactivate Trace..... | 10 | +| 5.14 Common ID..... | 10 | +| 5.15 Location Related Data..... | 10 | +| 5.16 UE Specific Information ..... | 10 | +| 5.17 RAB Modification Request..... | 11 | +| 6 RANAP messages transferred on the E-interface ..... | 11 | +| 7 Exceptions for RANAP message contents and information element coding when transferred on the E-interface ..... | 12 | +| 7.1 Message Contents..... | 12 | +| 8 RANAP message error handling when transferred on the E-interface ..... | 13 | +| Annex A (informative): Change history..... | 14 | + +# --- Foreword + +This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +# --- 1 Scope + +The present document describes the subset of Radio Access Network Application Part (RANAP) messages and procedures, defined in 3GPP TS 25.413 [4], which is used on the E-interface. A general description can be found in 3GPP TS 23.002 [7] and 3GPP TS 23.009 [2]. + +For the initiation and execution of relocation of SRNS (relocation for short, throughout the whole document) between MSCs a subset of RANAP procedures are used. For the subsequent control of resources allocated to the User Equipment (UE) RANAP procedures are used. The Direct Transfer Elementary Procedure (EP) of RANAP, is used for the transfer of connection management and mobility management messages between the UE and the controlling 3G\_MSC. + +# --- 2 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. + - For a specific reference, subsequent revisions do not apply. + - For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. +- [1] 3GPP TR 21.905: "Vocabulary". +- [2] 3GPP TS 23.009: "Handover procedures". +- [3] Void +- [4] 3GPP TS 25.413: "UTRAN Iu Interface Radio Access Network Application Part (RANAP) signalling". +- [5] 3GPP TS 29.002: "Mobile Application Part (MAP) specification". +- [6] 3GPP TS 29.010: "Information element mapping between Mobile Station - Base Station System (MS - BSS) and Base Station System - Mobile-services Switching Centre (BSS - MSC); Signalling procedures and the Mobile Application Part (MAP)". +- [7] 3GPP TS 23.002: "Network architecture". +- [8] Void + +# --- 3 Abbreviations + +For the purposes of the present document, the abbreviations defined in TR 21.905 [1] and the following apply: + +| | | +|-----------|------------------------------------------------------------------------------------------------------------------------| +| 3G_MSC | A third generation Mobile services Switching Centre that supports the Iu interface (and possibly also the A-interface) | +| 3G_MSC-A | The controlling 3G_MSC on which the call was originally established | +| 3G_MSC-B | The 3G_MSC to which the UE is handed over in a Basic Handover | +| 3G_MSC-B' | The 3G_MSC to which the UE is handed over in a Subsequent Handover | +| 3G_MSC-I | Interworking 3G_MSC | +| 3G_MSC-T | Target 3G_MSC | +| EP | Elementary Procedure | +| NNSF | NAS Node Selection Function | +| RNC | Radio Network Controller | + +# 4 Principles for the use of RANAP on the E-interface + +## 4.1 General + +The mechanism for the transfer of the RANAP messages on the E-interface is defined in TS 29.002 [5]. The operation of the relocation procedures between 3G\_MSCs and the use of the RANAP messages for those procedures is described in TS 23.009 [2] and TS 29.010 [6]. + +RANAP is defined to connect the RNS to both, the cs and ps domain of an UMTS CN. Procedures, messages and IEs, only defined for communication between the RNS and the ps domain of an UMTS CN will, of course, never appear on the E-interface. + +In the same way as a the connection oriented service of SCCP is used for the messages relating to one UE on the 3G\_MSC-RNS interface a TCAP dialogue is used on the E-interface for messages relating to one UE. As no correspondence to the connectionless service on the 3G\_MSC-RNS interface is used on the E-interface none of the global procedures are applicable. + +The management of the terrestrial circuits between the 3G\_MSCs is outside the scope of the E-interface (see TS 23.009 [2]), therefore all procedures, messages and information elements relating to terrestrial circuits are also excluded from the RANAP procedures and messages used on the E-interface. + +## 4.2 Transfer of RANAP layer 3 messages on the E-interface + +The RANAP data which on the 3G\_MSC-RNS interface is contained in the user data field of the exchanged SCCP frames is on the E-interface transferred as the contents of the access network signalling info in the AN-APDU parameter as described in TS 29.002 [5], indicating the access network protocol identification "ts3G-25413". + +## 4.3 Roles of 3G\_MSC-A, 3G\_MSC-I and 3G\_MSC-T + +For the description in the present document, the 3G\_MSC's functionality related to the relocation between 3G\_MSCs has been split into three logical parts, 3G\_MSC-A, 3G\_MSC-T and 3G\_MSC-I. The different roles need not necessarily be performed by different 3G\_MSCs. + +3G\_MSC-A is the call/connection controlling part of the 3G\_MSC where the call/connection was originally established and the switching point for relocation between 3G\_MSCs. (This corresponds to 3G\_MSC-A as defined in TS 23.009 [2] and TS 29.002 [5]). The 3G\_MSC that is the 3G\_MSC-A will not be changed during the duration of a call/connection. + +3G\_MSC-T is the part relating to the transitory state during the relocation for the 3G\_MSC controlling the RNS the serving RNS functionality is relocated to, when basic relocation or subsequent relocation (see TS 23.009) take place. (This corresponds, depending on the type of relocation to 3G\_MSC-A, 3G\_MSC-B or 3G\_MSC-B' in TS 23.009 [2] and TS 29.002 [5]). + +3G\_MSC-I is the part of a 3G\_MSC through which the 3G\_MSC-A, via an E-interface (or an internal interface) is in contact with the UE. (This corresponds, depending on the type of relocation to 3G\_MSC-A, 3G\_MSC-B or 3G\_MSC-B' in TS 23.009 [2] and TS 29.002 [5]). + +The 3G\_MSC that is the 3G\_MSC-A can also have the role of either the 3G\_MSC-I or the 3G\_MSC-T during a period of the call/connection. + +The following is applicable for the involved 3G\_MSCs concerning the exchange of RANAP data on an E-interface before and after a successful inter 3G\_MSC relocation: + +- 1) At basic relocation, two 3G\_MSCs are involved, one 3G\_MSC being 3G\_MSC-A and one being 3G\_MSC-T. When this relocation has been performed, the two 3G\_MSCs interworking on the E-interface have the roles of 3G\_MSC-A and 3G\_MSC-I respectively, i.e. the 3G\_MSC that is the 3G\_MSC-T during the relocation is now the 3G\_MSC-I. +- 2) At subsequent relocation back to 3G\_MSC-A, two 3G\_MSCs are involved. The 3G\_MSC having the role of 3G\_MSC-A has also the role of 3G\_MSC-T. The other 3G\_MSC involved has the role of 3G\_MSC-I. When this relocation has been completed, there is no exchange of RANAP data on the E-interface, i.e. the 3G\_MSC being the 3G\_MSC-I before and during the relocation is now no longer taking part. + +- 3) At subsequent relocation of SRNS to an 3G\_MSC not being 3G\_MSC-A, three 3G\_MSCs are involved. The roles of these 3G\_MSCs are 3G\_MSC-A, 3G\_MSC-I, and 3G\_MSC-T respectively. When this relocation has been performed, the two 3G\_MSCs interworking on an E-interface have the roles of 3G\_MSC-A and 3G\_MSC-I respectively, i.e. the 3G\_MSC that is the 3G\_MSC-T during the relocation is now the 3G\_MSC-I and the 3G\_MSC being 3G\_MSC-I during the relocation is now no longer taking part. + +# --- 5 Use of the RANAP on the E-interface + +The dedicated RANAP procedures used on the E-interface to some extent are: + +- RAB assignment; +- RAB Release Request; +- Iu Release Request; +- Relocation resource allocation; +- Relocation Detect; +- Relocation Complete; +- Relocation Cancel; +- CN Invoke Trace; +- Security mode control; +- Location Reporting Control; +- Location Report; +- Direct Transfer; +- Error Indication; +- Common ID; +- Location Related Data; +- UE Specific Information; +- RAB Modification Request. + +## 5.1 RAB Assignment + +The RAB Assignment procedure (TS 25.413 [4] subclause 8.2) is applied on the E-interface with following conditions: + +- the 3G\_MSC-A acts as the 3G\_MSC; +- the 3G\_MSC-I acts as the RNS. + +The handling of terrestrial resources is not applicable, i.e. the RANAP IEs *Transport Layer Address* and *Iu Transport Association* will be assigned by the 3G\_MSC-I. + +## 5.2 RAB Release Request + +For the RAB Release Request procedure (TS 25.413 [4] subclauses 8.3) the involved 3G\_MSCs shall act according to the following: + +- the 3G\_MSC-I acts as the RNS; +- the 3G\_MSC-A acts as the 3G\_MSC. + +## 5.3 Iu Release Request + +For the Iu Release Request procedure (TS 25.413 [4] subclause 8.4) the involved 3G\_MSCs shall act according to the following: + +- the 3G\_MSC-I acts as the RNS; +- the 3G\_MSC-A acts as the 3G\_MSC. + +Additionally, at basic Inter-3G\_MSC relocation and at subsequent Inter-3G\_MSC relocation (TS 23.009 [2]), if the 3G\_MSC that is the 3G\_MSC-A is not also the 3G\_MSC-T, the Iu Release Request procedure (TS 25.413 [4] subclause 8.4) is applied on the E-interface with the following conditions: + +- the 3G\_MSC-T acts as the RNS; +- the 3G\_MSC-A acts as the 3G\_MSC. + +## 5.4 Relocation Resource Allocation + +At basic Inter-3G\_MSC relocation (TS 23.009 [2]) the Relocation Resource Allocation procedure (TS 25.413 [4] subclause 8.7) is applied on the E-interface with the following conditions: + +- the 3G\_MSC-A acts as the 3G\_MSC; +- the 3G\_MSC-T acts as the target RNS. + +At subsequent Inter-3G\_MSC relocation the Relocation Resource Allocation procedure is applied on the E-interface with the following conditions: + +- the 3G\_MSC-I acts as the 3G\_MSC; +- the 3G\_MSC-T acts as the target RNS; +- if the 3G\_MSC that is the 3G\_MSC-A is not also the 3G\_MSC-T, then this 3G\_MSC shall act as the target RNS towards the 3G\_MSC-I and as the 3G\_MSC towards the 3G\_MSC-T. + +The handling of terrestrial resources is not applicable, i.e. the RANAP IEs *Transport Layer Address* and *Iu Transport Association* will be assigned by the 3G\_MSC-T. + +In case NNSF is active, the *Iu Signalling Connection Identifier* IE and the *Global CN ID* IE shall be set by the 3G\_MSC-T towards Target RNC. + +## 5.5 Relocation Cancel + +For subsequent Inter-3G\_MSC relocation the Relocation Cancel procedure (TS 25.413 [4] subclause 8.10) is applied on the E-interface with the following conditions. + +- the 3G\_MSC-A, acts as the 3G\_MSC; +- the 3G\_MSC-I, acts as the serving RNS. + +## 5.6 Relocation Detect and Relocation Complete + +For the Relocation Detect and Relocation Complete procedure (TS 25.413 [4] subclauses 8.8 and 8.9) the applicable parts on the E-interface are the transfer of RELOCATION DETECT, RELOCATION COMPLETE messages at inter 3G\_MSC relocation. For those parts, the involved 3G\_MSCs shall act according to the following: + +- the 3G\_MSC-A acts as the 3G\_MSC; +- the 3G\_MSC-T acts as the target RNS. + +## 5.7 CN Trace invocation + +For the CN Trace invocation procedure (TS 25.413 [4], subclause 8.17), the involved 3G\_MSCs shall act according to the following: + +- the 3G\_MSC-A acts as the 3G\_MSC; +- the 3G\_MSC-I acts as the RNS. + +Additionally, at basic Inter-3G\_MSC relocation and at subsequent Inter-3G\_MSC relocation (TS 23.009 [2]), if the 3G\_MSC that is the 3G\_MSC-A is not also the 3G\_MSC-T, the CN Trace invocation procedure (TS 25.413 [4], subclause 8.17) is applied on the E-interface with the following conditions: + +- the 3G\_MSC-A acts as the 3G\_MSC; +- the 3G\_MSC-T acts as the RNS. + +## 5.8 Security mode control + +For the Security mode control procedure (TS 25.413 [4], subclause 8.18), the involved 3G\_MSCs shall act according to the following: + +- the 3G\_MSC-A acts as the 3G\_MSC; +- the 3G\_MSC-I acts as the RNS. + +## 5.9 Location Reporting Control + +For the Location Reporting Control procedure (TS 25.413 [4], subclause 8.19), the involved 3G\_MSCs shall act according to the following: + +- the 3G\_MSC-A acts as the 3G\_MSC; +- the 3G\_MSC-I acts as the RNS. + +Additionally, at basic Inter-3G\_MSC relocation and at subsequent Inter-3G\_MSC relocation (3GPP TS 23.009 [2]), if the 3G\_MSC that is the 3G\_MSC-A is not also the 3G\_MSC-T, the Location Reporting Control procedure (TS 25.413 [4] subclause 8.19) is applied on the E-interface with the following conditions: + +- the 3G\_MSC-A acts as the 3G\_MSC; +- the 3G\_MSC-T acts as the RNS. + +## 5.10 Location Report + +For the Location Report procedure (TS 25.413 [4], subclause 8.20), the involved 3G\_MSCs shall act according to the following: + +- the 3G\_MSC-A acts as the 3G\_MSC; +- the 3G\_MSC-I acts as the RNS. + +## 5.11 Direct Transfer + +For the Direct Transfer procedure (TS 25.413 [4], subclause 8.23), the involved 3G\_MSCs shall act according to the following: + +- the 3G\_MSC-A acts as the 3G\_MSC; +- the 3G\_MSC-I acts as the RNS. + +## 5.12 Error Indication + +For the Error Indication procedure (TS 25.413 [4], subclause 8.27), the involved 3G\_MSCs shall act according to the following: + +- the 3G\_MSC-A acts as the 3G\_MSC; +- the 3G\_MSC-I acts as the RNS. + +## 5.13 CN Deactivate Trace + +For the CN Deactivate Trace procedure procedure (TS 25.413 [4], subclause 8.28), the involved 3G\_MSCs shall act according to the following: + +- the 3G\_MSC-A acts as the 3G\_MSC; +- the 3G\_MSC-I acts as the RNS. + +## 5.14 Common ID + +For the Common ID procedure (TS 25.413 [4], subclause 8.16), the involved 3G MSCs shall act according to the following: + +- the 3G\_MSC-A acts as the 3G\_MSC; +- the 3G\_MSC-I acts as the RNS. + +## 5.15 Location Related Data + +For the Location Related Data procedure (TS 25.413 [4], subclause 8.31), the involved 3G\_MSCs shall act according to the following: + +- the 3G\_MSC-A acts as the 3G\_MSC; +- the 3G\_MSC-I acts as the RNS. + +## 5.16 UE Specific Information + +For the UE Specific Information procedure (TS 25.413 [4], subclause 8.33), the involved 3G MSCs shall act according to the following: + +- the 3G\_MSC-A acts as the 3G\_MSC; +- the 3G\_MSC-I acts as the RNS. + +## 5.17 RAB Modification Request + +For the RAB Modification Request procedure (TS 25.413 [4], subclause 8.30), the involved 3G MSCs shall act according to the following: + +- the 3G\_MSC-A acts as the 3G\_MSC; +- the 3G\_MSC-I acts as the RNS. + +# --- 6 RANAP messages transferred on the E-interface + +The list given below shows the RANAP messages, defined in TS 25.413 [4] subclause 9.1(tabular format) and 9.3 (ASN.1 notation) that are transferred on the E-interface. + +| | | +|-------------------------|------------------------| +| RAB ASSIGNMENT REQUEST | (3G_MSC-A -> 3G_MSC-I) | +| RAB ASSIGNMENT RESPONSE | (3G_MSC-I -> 3G_MSC-A) | + +| | | +|------------------------------------|-------------------------------------------------| +| RAB RELEASE REQUEST | (3G_MSC-I -> 3G_MSC-A) | +| IU RELEASE REQUEST | (3G_MSC-I -> 3G_MSC-A and 3G_MSC-T -> 3G_MSC-A) | +| * RELOCATION REQUEST | (3G_MSC-A -> 3G_MSC-T and 3G_MSC-I -> 3G_MSC-A) | +| * RELOCATION REQUEST ACKNOWLEDGE | (3G_MSC-T -> 3G_MSC-A and 3G_MSC-A -> 3G_MSC-I) | +| * RELOCATION DETECT | (3G_MSC-T -> 3G_MSC-A) | +| * RELOCATION COMPLETE | (3G_MSC-T -> 3G_MSC-A) | +| * RELOCATION FAILURE | (3G_MSC-T -> 3G_MSC-A and 3G_MSC-A -> 3G_MSC-I) | +| * RELOCATION CANCEL | (3G_MSC-I -> 3G_MSC-A) | +| * RELOCATION CANCEL ACKNOWLEDGE | (3G_MSC-A -> 3G_MSC-I) | +| # CN INVOKE TRACE | (3G_MSC-A -> 3G_MSC-I and 3G_MSC-A -> 3G_MSC-T) | +| SECURITY MODE COMMAND | (3G_MSC-A -> 3G_MSC-I) | +| SECURITY MODE COMPLETE | (3G_MSC-I -> 3G_MSC-A) | +| SECURITY MODE REJECT | (3G_MSC-I -> 3G_MSC-A) | +| LOCATION REPORTING CONTROL | (3G_MSC-A -> 3G_MSC-I and 3G_MSC-A -> 3G_MSC-T) | +| LOCATION REPORT | (3G_MSC-I -> 3G_MSC-A) | +| DIRECT TRANSFER | (3G_MSC-A -> 3G_MSC-I and 3G_MSC-I -> 3G_MSC-A) | +| ERROR INDICATION | (3G_MSC-A -> 3G_MSC-I and 3G_MSC-I -> 3G_MSC-A) | +| # CN DEACTIVATE TRACE | (3G_MSC-A -> 3G_MSC-I) | +| COMMON ID | (3G_MSC-A -> 3G_MSC-I) | +| LOCATION RELATED DATA REQUEST | (3G_MSC-A -> 3G_MSC-I) | +| LOCATION RELATED DATA RESPONSE | (3G_MSC-I -> 3G_MSC-A) | +| LOCATION RELATED DATA FAILURE | (3G_MSC-I -> 3G_MSC-A) | +| UE SPECIFIC INFORMATION INDICATION | (3G_MSC-A -> 3G_MSC-I) | +| RAB MODIFY REQUEST | (3G_MSC-I -> 3G_MSC-A) | + +All other RANAP messages shall be considered as non-existent on the E-interface. + +Some of the messages above are qualified by \* or #. This indicates whether the message, when sent on the E interface, is considered as: + +- relocation related message (\*); or +- trace related message (#). + +# --- 7 Exceptions for RANAP message contents and information element coding when transferred on the E-interface + +## 7.1 Message Contents + +For the applicable RANAP messages transferred on the E-interface the following exceptions to the descriptions in TS 25.413 [4] are valid: + +RAB ASSIGNMENT REQUEST message + +- *Transport Layer Address* IE: + - if received, this IE shall be ignored; +- *Iu Transport Association* IE: + - if received, this IE shall be ignored; +- *UP Mode Versions* IE: + - the information given within this IE is only useful in case of TrFO. + +RELOCATION REQUEST message + +- *Transport Layer Address* IE: + - if received, this IE shall be ignored; +- *Iu Transport Association* IE: + - if received, this IE shall be ignored; +- *UP Mode Versions* IE: + - the information given within this IE is only useful in case of TrFO; +- *Iu Signalling Connection Identifier* IE: + - if received, this IE shall be ignored; +- *Global CN ID* IE: + - if received, this IE shall be ignored. + +# --- 8 RANAP message error handling when transferred on the E-interface + +The RANAP error handling (TS 25.413 [4], clause 10) is applicable. The handling of faults concerning the use of SCCP is not applicable. + +The RANAP error messages sent on the E-interface shall only be sent as response to RANAP messages received on the same interface. + +# Annex A (informative): Change history + +| Change history | | | | | | +|----------------|---------|------------|-----------|-------------|--------------------------------------------------------| +| TSG RAN# | Version | CR | Tdoc RAN | New Version | Subject/Comment | +| RAN_08 | 2.0.0 | - | RP-000258 | 3.0.0 | Approved at TSG RAN #8 and placed under Change Control | +| RAN_10 | 3.0.0 | 001
002 | RP-000634 | 3.1.0 | Approved at TSG RAN #10 | + +| Change history | | | | | | | | +|----------------|-------|-----------|-----|-----|--------------------------------------------------------------------------|--------|--------| +| Date | TSG # | TSG Doc. | CR | Rev | Subject/Comment | Old | New | +| 03/2001 | 11 | - | - | - | Approved at TSG RAN #11 and placed under Change Control | - | 4.0.0 | +| 09.2001 | 13 | RP-010590 | 004 | - | Iu Signalling Connection identifier on E-i/f | 4.0.0 | 4.1.0 | +| 03/2002 | 15 | - | - | - | Approved at TSG RAN #15 and placed under Change Control | 4.1.0 | 5.0.0 | +| 06/2002 | 16 | RP-020416 | 007 | - | Location Related Data procedure missing | 5.0.0 | 5.1.0 | +| 12/2002 | 18 | RP-020755 | 010 | 1 | Explicit indication of relocation related messages | 5.1.0 | 5.2.0 | +| 03/2003 | 19 | RP-030079 | 013 | 1 | Corrections to the list of RANAP messages transferred on the E-interface | 5.2.0 | 5.3.0 | +| 12/2003 | 22 | - | - | - | Introduction of Release 6 specification | 5.3.0 | 6.0.0 | +| 06/2004 | 24 | RP-040177 | 015 | - | PUESBINE support over E-interface | 6.0.0 | 6.1.0 | +| 03/2005 | 27 | RP-050120 | 017 | - | Full RANAP support of network initiated SCUDIF | 6.1.0 | 6.2.0 | +| 03/2006 | 31 | - | - | - | Introduction of Release 7 specification | 6.2.0 | 7.0.0 | +| 06/2003 | 32 | RP-060278 | 019 | - | Iu-Flex for Inter-3G MSC Relocation | 7.0.0 | 7.1.0 | +| 12/2008 | 42 | | | | Upgrade to Release 8 without technical change | 7.1.0 | 8.0.0 | +| 12/2009 | - | - | - | - | Upgrade to Release 9 without technical change | 8.0.0 | 9.0.0 | +| 03/2011 | | | | | Upgrade to Release 10 without technical change | 9.0.0 | 10.0.0 | +| 06/2011 | 52 | RP-110684 | 020 | | Corrections of References | 10.0.0 | 10.1.0 | +| 09/2012 | | | | | Update to Rel-11 version (MCC) | 10.1.0 | 11.0.0 | \ No newline at end of file diff --git a/marked/Rel-11/29_series/29109/1b5a812c8aa20fd5cba28e97001d32de_img.jpg b/marked/Rel-11/29_series/29109/1b5a812c8aa20fd5cba28e97001d32de_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..de30cd5eeab3df6b98cf352665bd4b1dc93accf3 --- /dev/null +++ b/marked/Rel-11/29_series/29109/1b5a812c8aa20fd5cba28e97001d32de_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4d8bdaed02e0b9551e4809149d4d1b441d3a88b8ca5a4abaf25fc135413d0bc8 +size 95947 diff --git a/marked/Rel-11/29_series/29109/28d75f39a24203712ee907b32cf0bbe5_img.jpg b/marked/Rel-11/29_series/29109/28d75f39a24203712ee907b32cf0bbe5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..df0035d46af9c4a5ac94c8ec657c97e0f6d42048 --- /dev/null +++ b/marked/Rel-11/29_series/29109/28d75f39a24203712ee907b32cf0bbe5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7e4ae4493d6d7039aa31f27e3bba49085d15fd266f1679041f54c31f54a9015b +size 75041 diff --git a/marked/Rel-11/29_series/29109/4cc7cdce3d498d8b0ba033a9be24ade5_img.jpg b/marked/Rel-11/29_series/29109/4cc7cdce3d498d8b0ba033a9be24ade5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..39266067bb1c70f64c646ebd61e4633ce680b410 --- /dev/null +++ b/marked/Rel-11/29_series/29109/4cc7cdce3d498d8b0ba033a9be24ade5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:dc0058da931c418e043ec176678177a9b93ddea13bbedfb3fb118d42eaac3580 +size 11134 diff --git a/marked/Rel-11/29_series/29109/5793a44ffdadd039928e2f9fe6daae06_img.jpg b/marked/Rel-11/29_series/29109/5793a44ffdadd039928e2f9fe6daae06_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d711ce4b9d5892df169f991f921d00150c08c27a --- /dev/null +++ b/marked/Rel-11/29_series/29109/5793a44ffdadd039928e2f9fe6daae06_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:27ae9285b1caaada6fd809760f63ef1f8d323b900110d64faac1ea62b6221bc1 +size 36023 diff --git a/marked/Rel-11/29_series/29109/5dfc130b129ace4df375839020a5700d_img.jpg b/marked/Rel-11/29_series/29109/5dfc130b129ace4df375839020a5700d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2437b078223efabceb211d393e5a3de38d802487 --- /dev/null +++ b/marked/Rel-11/29_series/29109/5dfc130b129ace4df375839020a5700d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6a5b788f778c61b79998ab9bc4844e71fab1b84bf8a3a33e48ea8257ada7f55b +size 40162 diff --git a/marked/Rel-11/29_series/29109/608f1b5ef8f3dc0723f2b4ea1fb72be2_img.jpg b/marked/Rel-11/29_series/29109/608f1b5ef8f3dc0723f2b4ea1fb72be2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b06f04a27c07547b37c3393306a35294db48fc8e --- /dev/null +++ b/marked/Rel-11/29_series/29109/608f1b5ef8f3dc0723f2b4ea1fb72be2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:24b6aaecd9ac3945efb46e8c2cb9f3770b51dd2f964a7f40dca77e9edff81b73 +size 9062 diff --git a/marked/Rel-11/29_series/29109/6f31cdb576d2f15c35c3f266e5f59211_img.jpg b/marked/Rel-11/29_series/29109/6f31cdb576d2f15c35c3f266e5f59211_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3e1d2d3314f3272c0bf7a8ab086ab73627c9e302 --- /dev/null +++ b/marked/Rel-11/29_series/29109/6f31cdb576d2f15c35c3f266e5f59211_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ab0d1f64f9a46c9db58c305d19ba98e09cac40d3a40745383dacc8639bcda86b +size 120277 diff --git a/marked/Rel-11/29_series/29109/75f0cb39f1cd165dfe4a6aa6c4d9388d_img.jpg b/marked/Rel-11/29_series/29109/75f0cb39f1cd165dfe4a6aa6c4d9388d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c5f283dc947262c394c197249dadb03a92cf62b6 --- /dev/null +++ b/marked/Rel-11/29_series/29109/75f0cb39f1cd165dfe4a6aa6c4d9388d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2b2e07f466d42f6affb45773d0f5e338bf3b57e24bacc1a6467d0c74ec8af9e4 +size 86628 diff --git a/marked/Rel-11/29_series/29109/90ddb84c323b956e2d50a54d3f870566_img.jpg b/marked/Rel-11/29_series/29109/90ddb84c323b956e2d50a54d3f870566_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3d67b58404280a0282e98d9c8b01ab2957f1518f --- /dev/null +++ b/marked/Rel-11/29_series/29109/90ddb84c323b956e2d50a54d3f870566_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3322f4d4dd28c1c05ac5fb0006889f561a4777c65b661e681621346e811156e5 +size 106352 diff --git a/marked/Rel-11/29_series/29109/997233d405f0d4b89ddeb7683e047f66_img.jpg b/marked/Rel-11/29_series/29109/997233d405f0d4b89ddeb7683e047f66_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..07bd57b69731f791c63c99f1864ecf4c7717d2e0 --- /dev/null +++ b/marked/Rel-11/29_series/29109/997233d405f0d4b89ddeb7683e047f66_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1f185e4c6976da69a1d72e5774a3eb89cf8f969edd45366129e20f6ba0f9d11b +size 95883 diff --git a/marked/Rel-11/29_series/29109/9f9386d5b3d6cbeb1ed104a799320ebf_img.jpg b/marked/Rel-11/29_series/29109/9f9386d5b3d6cbeb1ed104a799320ebf_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..06f5002072dd2fcc6953fe279a5503b0a2f7236f --- /dev/null +++ b/marked/Rel-11/29_series/29109/9f9386d5b3d6cbeb1ed104a799320ebf_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:531b22a0d44af52c013c3d3cc8c2c91f6f0d06ae38d835a9d2d7f57f5b42847a +size 76741 diff --git a/marked/Rel-11/29_series/29109/d0abac95583b52a3b35f74a215567334_img.jpg b/marked/Rel-11/29_series/29109/d0abac95583b52a3b35f74a215567334_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..05060b672c98558dd4c0c6c2c5ba3f7bc5160876 --- /dev/null +++ b/marked/Rel-11/29_series/29109/d0abac95583b52a3b35f74a215567334_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ad3b11a788b52090d6cf81e59a9cfe3a98ddfc59aa4adc615c4e7dbf6436223a +size 90937 diff --git a/marked/Rel-11/29_series/29109/ddc7460821484f1ae2835c67955c554c_img.jpg b/marked/Rel-11/29_series/29109/ddc7460821484f1ae2835c67955c554c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c0d5106778f40597d1910e17c4e9d10250958f85 --- /dev/null +++ b/marked/Rel-11/29_series/29109/ddc7460821484f1ae2835c67955c554c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e36a15b119128675ff57c0831f2bc49959b21fd5ae0aa458e425f9bcc905baa2 +size 9707 diff --git a/marked/Rel-11/29_series/29109/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg b/marked/Rel-11/29_series/29109/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..91e1a19998565cca11a906683cb66a07b8e4dc2f --- /dev/null +++ b/marked/Rel-11/29_series/29109/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9f4fb00fb5d8c5125ba8120d6a7e641aceccb6d9b9cf7e8d8542b82f6df1a20f +size 41521 diff --git a/marked/Rel-11/29_series/29109/e9d825d87c5f85c8dba0664eace96ef4_img.jpg b/marked/Rel-11/29_series/29109/e9d825d87c5f85c8dba0664eace96ef4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ff2a9c263e56ad8a1f2ae5b49128aef4b37023d4 --- /dev/null +++ b/marked/Rel-11/29_series/29109/e9d825d87c5f85c8dba0664eace96ef4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4323cd0b5b81350d85f59c9029f5517d48933f26deaa0922452e306e740f6842 +size 14139 diff --git a/marked/Rel-11/29_series/29109/f6d72d7c790e7f585532140f3971639a_img.jpg b/marked/Rel-11/29_series/29109/f6d72d7c790e7f585532140f3971639a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..801ef061164b5b66fef37b9fd2ecf33075712929 --- /dev/null +++ b/marked/Rel-11/29_series/29109/f6d72d7c790e7f585532140f3971639a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a55e7ff7d11d1cad5f9caec530cbb31ecf7efa5d49947fb6d6823cc6aa848178 +size 61681 diff --git a/marked/Rel-11/29_series/29109/raw.md b/marked/Rel-11/29_series/29109/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..8fda7a3d8bf80defedf2b6bbfc0b5b8386708d26 --- /dev/null +++ b/marked/Rel-11/29_series/29109/raw.md @@ -0,0 +1,3587 @@ + + + + + + +# Contents + +| | | | +|----------|-------------------------------------------------------------------------|----| +| 1 | Scope..... | 5 | +| 2 | References..... | 9 | +| 3 | Definitions, symbols and abbreviations ..... | 11 | +| 3.1 | Definitions ..... | 11 | +| 3.2 | Symbols..... | 11 | +| 3.3 | Abbreviations ..... | 12 | +| 4 | GBA Bootstrapping Zh interface and Zh' interface ..... | 13 | +| 4.1 | Generic bootstrapping network architecture ..... | 13 | +| 4.2 | Protocol Zh between BSF and HSS ..... | 13 | +| 4.3 | Protocol Zh' between BSF and HLR..... | 18 | +| 4.3.1 | Public to Private Identity Resolution over Zh between BSF and HLR ..... | 19 | +| 5 | GAA Application Zn and Zpn interfaces..... | 21 | +| 5.1 | Applications' network architecture ..... | 21 | +| 5.2 | Protocol Zn between NAF and BSF based on Diameter..... | 22 | +| 5.3 | Protocol Zn between NAF and BSF based on Web Services ..... | 25 | +| 5.4 | Protocol Zpn between NAF and BSF based on Diameter..... | 28 | +| 5.5 | Protocol Zpn between NAF and BSF based on Web Services ..... | 32 | +| 6 | Diameter application for Zh, Zn and Zpn interfaces..... | 35 | +| 6.0 | Introduction ..... | 35 | +| 6.1 | Command-Code values ..... | 35 | +| 6.2 | Result-Code AVP values..... | 35 | +| 6.2.1 | Success ..... | 35 | +| 6.2.2 | Permanent failures ..... | 35 | +| 6.2.2.1 | DIAMETER_ERROR_IDENTITY_UNKNOWN (5401) ..... | 35 | +| 6.2.2.2 | DIAMETER_ERROR_NOT_AUTHORIZED (5402)..... | 35 | +| 6.2.2.3 | DIAMETER_ERROR_TRANSACTION_IDENTIFIER_INVALID (5403) ..... | 36 | +| 6.2.2.4 | Void ..... | 36 | +| 6.2.2.5 | Void ..... | 36 | +| 6.2.2.6 | Void ..... | 36 | +| 6.2.2.7 | Void ..... | 36 | +| 6.3 | AVPs ..... | 37 | +| 6.3.1 | Common AVPs..... | 38 | +| 6.3.1.1 | GBA-UserSecSettings AVP ..... | 38 | +| 6.3.1.2 | Transaction-Identifier AVP ..... | 38 | +| 6.3.1.3 | NAF-Id..... | 38 | +| 6.3.1.4 | GAA-Service-Identifier AVP ..... | 38 | +| 6.3.1.5 | Key-ExpiryTime AVP..... | 38 | +| 6.3.1.6 | ME-Key-Material AVP..... | 38 | +| 6.3.1.7 | UICC-Key-Material AVP ..... | 38 | +| 6.3.1.8 | GBA_U-Awareness-Indicator ..... | 38 | +| 6.3.1.9 | BootstrapInfoCreationTime AVP ..... | 39 | +| 6.3.1.10 | GUSS-Timestamp AVP..... | 39 | +| 6.3.1.11 | GBA-Type ..... | 39 | +| 6.3.1.12 | UE-Id ..... | 39 | +| 6.3.1.13 | UE-Id-Type ..... | 39 | +| 6.3.1.14 | UICC-App-Label ..... | 39 | +| 6.3.1.15 | UICC-ME..... | 39 | +| 6.3.1.16 | Requested-Key-Lifetime..... | 40 | +| 6.3.1.17 | Private-Identity-Request ..... | 40 | +| 6.3.1.18 | GBA-Push-Info ..... | 40 | +| 6.3.1.19 | NAF-SA-Identifier ..... | 40 | +| 6.3.1.20 | Security-Feature-Request..... | 40 | +| 6.3.1.21 | Security-Feature-Response ..... | 40 | +| 6.4 | User identity to HSS resolution..... | 40 | + +| | | | +|-------------------------------|-----------------------------------------------------------------|-----------| +| 7 | Use of namespaces..... | 42 | +| 7.1 | AVP codes..... | 42 | +| 7.2 | Experimental-Result-Code AVP values..... | 42 | +| 7.3 | Command Code values..... | 42 | +| Annex A (normative): | GBA-UserSecSettings XML definition..... | 43 | +| Annex B (normative): | GAA Service Type Codes ..... | 48 | +| Annex C (normative): | GAA Authorization flag codes ..... | 48 | +| Annex D (normative): | Web Services Definition for Zn interface..... | 49 | +| Annex E (informative): | Liberty authentication context definitions for GBA ..... | 50 | +| E.1 | Introduction..... | 50 | +| E.2 | GBA Authentication context statement data model..... | 50 | +| E.3 | GBA authentication context statement schema ..... | 51 | +| E.4 | GBA authentication context classes..... | 52 | +| E.4.1 | GBAOneFactorUnregistered..... | 52 | +| E.4.1.1 | Associated 3GPP URI ..... | 52 | +| E.4.1.2 | Class schema ..... | 53 | +| E.4.2 | GBATwoFactorUnregistered ..... | 53 | +| E.4.2.1 | Associated 3GPP URI ..... | 53 | +| E.4.2.2 | Class schema ..... | 53 | +| E.4.3 | GBAOneFactorContract..... | 54 | +| E.4.3.1 | Associated 3GPP URI ..... | 54 | +| E.4.3.2 | Class schema ..... | 54 | +| E.4.4 | GBATwoFactorContract..... | 55 | +| E.4.4.1 | Associated 3GPP URI ..... | 55 | +| E.4.4.2 | Class schema ..... | 55 | +| Annex F (informative): | SAML authentication context definitions for GBA ..... | 56 | +| F.1 | Introduction..... | 56 | +| F.2 | GBA authentication context declaration data model ..... | 56 | +| F.3 | GBA authentication context declaration types..... | 57 | +| F.4 | GBA authentication context declaration classes..... | 58 | +| F.4.1 | GBAOneFactorUnregistered..... | 58 | +| F.4.1.1 | Associated 3GPP URI ..... | 58 | +| F.4.1.2 | Class schema ..... | 58 | +| F.4.2 | GBATwoFactorUnregistered ..... | 61 | +| F.4.2.1 | Associated 3GPP URI ..... | 61 | +| F.4.2.2 | Class schema ..... | 61 | +| F.4.3 | GBAOneFactorContract..... | 63 | +| F.4.3.1 | Associated 3GPP URI ..... | 63 | +| F.4.3.2 | Class schema ..... | 63 | +| F.4.4 | GBATwoFactorContract..... | 65 | +| F.4.4.1 | Associated 3GPP URI ..... | 65 | +| F.4.4.2 | Class schema ..... | 65 | +| Annex G (normative): | Web Services Definition for Zpn interface ..... | 68 | +| Annex H (informative): | Change history..... | 69 | + +# --- Foreword + +This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +# --- 1 Scope + +The present stage 3 specification defines the Diameter based implementation for bootstrapping Zh interface (BSF-HSS) and Dz interface (BSF-SLF) for HSS resolution for the BSF, the MAP based implementation for bootstrapping Zh' interface (BSF-HLR) and GAA Application Zn interface (BSF-NAF) in Generic Authentication Architecture (GAA). This specification also defines the Web Services based implementation for GAA Application Zn reference point (BSF-NAF). The definition contains procedures, message contents and coding. The procedures for bootstrapping and usage of bootstrapped security association are defined in 3GPP TS 33.220 [5]. + +The present document also specifies the Diameter and Web Services based implementation for the GAA Application Push Function Zpn reference point (BSF-NAF). The procedures for bootstrapping are defined in 3GPP TS 33.223 [23]. + +This specification is a part of the Generic Authentication Architecture (GAA) specification series. + +The diameter based implementation for the Zh interface is based on re-usage of Cx interface Multimedia-Auth-Request/Answer messages originally between CSCF and HSS. These messages are defined in 3GPP TS 29.229 [3]. The 3GPP IMS mobility management uses the same definitions between CSCF and HSS. The present document defines how the defined messages are used with the bootstrapping and GAA application procedures (e.g. subscriber certificates) and the application logic that is needed in GAA network elements (BSF, HSS, and NAF). + +Figure 1.1 depicts the relationships of these specifications to the other specifications for the Diameter based implementations. + +![Diagram showing the relationships between various specifications for Diameter-based implementations, categorized by 3GPP and IETF standards.](f6d72d7c790e7f585532140f3971639a_img.jpg) + +| | | | | +|----------------|--------------------------------------------------|---------|------------------| +| 3GPP | GAA System Description TR 33.919 | Stage 2 | IMS TS 23.228 | +| | GAA GBA TS 33.220
GBA Push Function TS 33.223 | | IMS MM TS 29.228 | +| | GAA Zh, Zn and Zpn TS 29.109 | Stage 3 | | +| IETF with 3GPP | IMS Cx Diameter message definitions TS 29.229 | | | +| IETF | Diameter Base Protocol RFC 3588 | | | +| | SCTP | | | +| | IP | | | + +Diagram showing the relationships between various specifications for Diameter-based implementations, categorized by 3GPP and IETF standards. + +**Figure 1.1: Relationships to other specifications** + +Figure 1.2 provides an informal overall quick introduction to the whole signalling procedures in GAA system. The important identifiers are marked **bold** and optional data items are *italicised*. The Ub and Ua interfaces, not defined in this TS, are simplified. + +NOTE: The Zh' interface (BSF-HLR) is not represented in this figure. + +![Figure 1.2: The whole signalling procedure in GAA system. The diagram shows the interaction between a UE, BSF, SLF, HSS, and NAF across GAA Security and Application domains.](997233d405f0d4b89ddeb7683e047f66_img.jpg) + +The diagram illustrates the signalling procedure in the GAA system, divided into two domains: GAA Security Domain (top, green background) and GAA Application Domain (bottom, blue background). + +**Entities:** + +- UE (User Equipment):** Located in the GAA Application Domain. +- BSF (Bootstrap Function):** Located in the GAA Security Domain. +- SLF (Subscription Locator Function):** Located in the GAA Security Domain, connected to BSF via Dz and IMPI interfaces. +- HSS (Home Subscriber Server):** Located in the GAA Security Domain. +- NAF (Network Application Function):** Located in the GAA Application Domain, containing sub-components: Auth.Proxy and Appl.Spec. Servers. + +**Signalling Procedure:** + +- (1) UE sends **IMPI** to BSF via the **Ub** interface. +- (2) BSF sends **IMPI** to HSS via the **Zh** interface. +- (3) HSS responds with *AV, IMPI* and **GUSS(USS\*(UID\*))** to BSF. +- (4) BSF sends **B-TID** and *Key-Lifetime* to UE via the **Ub** interface. +- (5) UE sends **B-TID, UID** to NAF via the **Ua** interface. +- (6) NAF sends **B-TID, GSID\*, NAF-Id** to BSF via the **Zn** interface. +- (7) BSF sends a large message to HSS containing **USS\*(UID\*)**, **Ks\_(ext)\_NAF**, **Key-Expirytime**, **BootstrapInfoCreationTime**, **Ks\_int\_NAF**, and **IMPI**. +- (8) NAF sends a response to UE via the **Ua** interface. +- (9) if needed: Sh, GUP, etc. (indicated by a dashed arrow from NAF to HSS). + +**Interfaces:** + +- Ub:** Interface between UE and BSF (simplified). +- Ua:** Interface between UE and NAF (simplified). +- Zn:** Interface between BSF and NAF. +- Zh:** Interface between BSF and HSS. +- Dz:** Interface between BSF and SLF. + +**Identifiers and Data Items:** + +- Bold:** Important Identity (**IMPI**, **B-TID**, **GUSS(USS\*(UID\*))**, **USS\*(UID\*)**, **Ks\_(ext)\_NAF**, **Key-Expirytime**, **BootstrapInfoCreationTime**, **Ks\_int\_NAF**, **UID**, **GSID\***, **NAF-Id**). +- Italic:* optional items (*Key-Lifetime*, *AV*, *IMPI*, *Key-Expirytime*, *BootstrapInfoCreationTime*, *IMPI*). + +Figure 1.2: The whole signalling procedure in GAA system. The diagram shows the interaction between a UE, BSF, SLF, HSS, and NAF across GAA Security and Application domains. + +**Bold**=Important Identity. *Italic*=optional items. Ub and Ua interfaces are simplified. + +**Figure 1.2: The whole signalling procedure in GAA system** + +Figure 1.3 provides an informal overall quick introduction to the whole signalling procedures in GAA Push Function. The important identifiers are marked bold and optional data items are italicised. The Ua and Upa interfaces, not defined in this TS, are simplified. + +![Signalling procedure in GAA Bootstrapping Push Function diagram showing interactions between UE, SLF, BSF, HSS, and NAF across GAA Security and Application domains.](d0abac95583b52a3b35f74a215567334_img.jpg) + +The diagram illustrates the signalling procedure for GAA Bootstrapping Push Function across two domains: GAA Security Domain (top, green background) and GAA Application Domain (bottom, light blue background). + +**Entities:** + +- UE (User Equipment):** Located in the GAA Application Domain. +- SLF (SLF Function):** Located in the GAA Security Domain. +- BSF (BSF Function):** Located in the GAA Security Domain. +- HSS (Home Subscriber Server):** Located in the GAA Security Domain. +- NAF (Network Application Function):** Located in the GAA Application Domain, with a sub-component 'Appl.Spec. Servers'. + +**Signalling Steps:** + +- (1)** UE sends a message to NAF containing: **UE-Id (Type)**, **P-TID**, **GSID\***, **NAF-Id**, and **Zpn**. +- (2)** BSF sends **IMPI/IMPU** to the HSS. +- (3)** HSS responds with **Zh**, **AV, IMPI**, and **GUSS(USS\*(UID\*))**. +- (4)** BSF sends a message to NAF containing: **GPI**, **USS\*(UID\*)**, **Ks\_(ext)\_NAF**, **Key-Expirytime**, **BootstrapInfoCreationTime**, **Ks\_int\_NAF**, and **IMPI**. +- (5)** NAF sends **GPI** and **Upa** to the UE. + +**Other Interactions:** + +- UE and BSF have a vertical connection line. +- SLF and BSF have a vertical connection line with labels **Dz** and **IMPI/IMPU**. + +Signalling procedure in GAA Bootstrapping Push Function diagram showing interactions between UE, SLF, BSF, HSS, and NAF across GAA Security and Application domains. + +**Bold**=Important Identity. *Italic*=optional items. Ub and Ua interfaces are simplified. + +**Figure 1.3: Signalling procedure in GAA Bootstrapping Push Function** + +# --- 2 References + +The following documents contain provisions that, 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] IETF RFC 3588, "Diameter Base Protocol". +- [2] 3GPP TS 29.228: "IP Multimedia (IM) Subsystem Cx and Dx Interfaces; Signalling flows and message contents". +- [3] 3GPP TS 29.229: "Cx and Dx interfaces based on the Diameter protocol". +- [4] 3GPP TR 33.919 "Generic Authentication Architecture (GAA); System Description". +- [5] 3GPP TS 33.220 "Generic Authentication Architecture (GAA); Generic Bootstrapping Architecture". +- [6] 3GPP TS 33.221 "Generic Authentication Architecture (GAA); Support for Subscriber Certificates". +- [7] 3GPP TS 24.109: "Bootstrapping interface (Ub) and Network application function interface (Ua);Protocol details". +- [8] 3GPP TS 29.230: "Diameter applications; 3GPP specific codes and identifiers" +- [9] IETF RFC 3589: "Diameter Command Codes for Third Generation Partnership Project (3GPP)". +- [10] 3GPP TS 23.008: "Organisation of subscriber data" +- [11] 3GPP TS 33.222: "Generic Authentication Architecture (GAA); Access to network application functions using secure hypertext transfer protocol (HTTPS)". +- [12] 3GPP TS 23.228: "IP Multimedia Subsystem (IMS); Stage 2" +- [13] W3C: "Web Services Activity", . +- [14] W3C: "Web Services Description Language (WSDL) Version 2.0 Part 0: Primer", . +- [15] 3GPP TR 33.980: "Liberty Alliance and 3GPP Security Interworking; Interworking of Liberty Alliance ID-FF, ID-WSF and Generic Authentication Architecture". +- [16] Liberty Alliance Project: "Liberty ID-FF Authentication Context Specification". +- [17] 3GPP TS 33.110: "Key establishment between a Universal Integrated Circuit Card (UICC) and a terminal" +- [18] 3GPP TS 33.259: "Key establishment between a UICC Hosting Device and a Remote Device" +- [19] 3GPP TS 29.002: "Mobile Application Part (MAP) Specification" +- [20] 3GPP TS 33.102: "3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; 3G Security; Security architecture". +- [21] 3GPP TS 23.003: "Numbering, addressing and identification". +- [22] OASIS Standard: "Authentication Context for the OASIS Security Assertion Markup Language (SAML) V2.0 OASIS Standard, 15 March 2005, saml-authn-context-2.0-os". + +- [23] 3GPP TS 33.223 "Generic Authentication Architecture (GAA); Generic Bootstrapping Architecture (GBA) Push Function". +- [24] 3GPP TS 33.402: "3GPP System Architecture Evolution (SAE); Security aspects of non-3GPP accesses". +- [25] Void +- [26] 3GPP TS 26.237: "IP Multimedia Subsystem (IMS) based Packet Switched Streaming (PSS) Multimedia Broadcast/Multicast Services (MBMS); User Service; Protocols". +- [27] Void +- [28] Void +- [29] 3GPP TR 33.924: "Identity Management and 3GPP Security Interworking; Identity Management and Generic Authentication Architecture (GAA) Interworking". +- [30] 3GPP TS 33.224: "Generic Authentication Architecture (GAA); Generic Push Layer". +- [31] 3GPP TS 33.203: "Access security for IP-based services". +- [32] 3GPP TS 29.329: " Sh Interface based on the Diameter protocol; Protocol details". + +# --- 3 Definitions, symbols and abbreviations + +## 3.1 Definitions + +For the purposes of the present document, the terms and definitions given in 3GPP TS 23.008 [10], 3GPP TR 33.919 [4], 3GPP TS 33.220 [5] apply with following additions. + +**Bootstrapping information** (Bootstrapped data) in a BSF consists of a bootstrapping transaction identifier (B-TID), a key material (Ks), the key lifetime (expiry time), the bootstrapinfo creation time, the IMPI and the GUSS (if received from HSS) with BSF control information. Each bootstrapping procedure creates a bootstrapped data entity with B-TID as retrieval key.. + +**GAA application** is an application that uses the security association created by GBA Bootstrapping procedure. + +**GAA service** is an operator specific end user service that uses the security association created by GAA Bootstrapping procedure. GAA services are identified by **GAA Service Identifiers**. A GAA service is implemented using some standardised or proprietary GAA application defined by GAA application type. + +**NAF specific Bootstrapping information** transferred from a BSF to a NAF contains NAF and its service specific parts from bootstrapped data and needed key information derived from the bootstrapped data. + +**Service/Application.** The term service is used here in its common meaning. A service is something that a MNO offers to subscribers. GAA Services are identified by GAA Service Identifier (GSID). In stage 2 documents ([4], [5], [6] and [11]) the term application is used in the same meaning i.e. MNOs offer applications to subscribers. There is a reason to avoid the usage of the term application here. The application is an already reserved term in Diameter. In Diameter applications are identified by Application Identifiers. + +## 3.2 Symbols + +For the purposes of the present document, the terms and definitions given in 3GPP TS 23.008 [10]. + +## 3.3 Abbreviations + +For the purposes of the present document, the following abbreviations apply: + +| | | +|------------|------------------------------------------------------------------------------------------------------------------------------------| +| AK | Anonymity Key | +| AKA | Authentication and Key Agreement | +| AUTN | Authentication token | +| AV | Authentication Vector. 3GPP AV=[RAND,AUTN,XRES,CK,IK]. | +| AVP | Attribute-Value-Pair in Diameter messages. | +| BIA | BootstrappingInfo-Answer message | +| BIR | BootstrappingInfo-Request message | +| BS | BootStrapping Procedure | +| BSF | Bootstrapping server functionality
BSF is hosted in a network element under the control of an MNO. | +| B-TID | Bootstrapping Transaction Identifier | +| CA | Certificate Authority | +| CK | Confidential Key | +| FQDN | Full Qualified Domain Name in URI (e.g. http://FQDN:80 ) | +| GAA | Generic Authentication Architecture | +| GBA | Generic Bootstrapping Architecture | +| GPI | GBA Push Information | +| GSID | GAA Service Identifier | +| GUSS | GBA User Security Settings | +| HSS | Home Subscriber System | +| IK | Integrity Key | +| IMPI | IP Multimedia Private Identity | +| IMPU | IP Multimedia Public Identity | +| Ks | Key Material | +| Ks_ext_NAF | MEbased key for a specific NAF | +| Ks_int_NAF | UICC based key for a specific NAF | +| ME | Mobile Equipment | +| MNO | Mobile network operator | +| NAF | Operator-controlled network application function functionality.
NAF is hosted in a network element under the control of an MNO. | +| P-TID | Push Temporary Identifier | +| RAND | Random challenge in authentication | +| REQ | In Diameter header indicates that the message is a Request. | +| SCTP | Stream Control Transmission Protocol | +| SLF | Subscription Location Function | +| SSC | Subscriber Certificate Procedure | +| Ua | UE-NAF interface for GAA applications | +| Ub | UE-BSF interface for bootstrapping | +| UE | User Equipment | +| USS | User Security Settings (a part of GUSS) | +| XRES | Expected response in authentication | +| Zh | BSF-HSS interface for bootstrapping procedure | +| Zh' | BSF-HLR interface for bootstrapping procedure | +| Zn | BSF-NAF interface for GAA applications | +| Zpn | BSF-NAF interface for GBA push. | + +# 4 GBA Bootstrapping Zh interface and Zh' interface + +## 4.1 Generic bootstrapping network architecture + +The network architecture of the Diameter based implementation for Bootstrapping procedure is presented in Figure 4.1-1. The interface Ub (bootstrapping) is defined in 3GPP TS 24.109 [7] and the interface Zh in this specification. + +![Figure 4.1-1: Network architecture of bootstrapping procedure. A diagram showing three entities: UE, BSF, and HSS. UE is connected to BSF via the Ub interface. BSF is connected to HSS via the Zh interface.](ddc7460821484f1ae2835c67955c554c_img.jpg) + +``` + +graph LR + UE[UE] -- Ub --> BSF[BSF] + BSF -- Zh --> HSS[HSS] + +``` + +Figure 4.1-1: Network architecture of bootstrapping procedure. A diagram showing three entities: UE, BSF, and HSS. UE is connected to BSF via the Ub interface. BSF is connected to HSS via the Zh interface. + +**Figure 4.1-1: Network architecture of bootstrapping procedure** + +The generic bootstrapping network architecture for Bootstrapping Push procedures is presented in Figure 4.1-2. The interface Zpn is also defined in this specification. + +![Figure 4.1-2: Network architecture of bootstrapping push procedure. A diagram showing four entities: UE, NAF, BSF, and HSS. UE is connected to NAF via the Upa interface. NAF is connected to BSF via the Zpn interface. BSF is connected to HSS via the Zh interface.](e9d825d87c5f85c8dba0664eace96ef4_img.jpg) + +``` + +graph LR + UE[UE] -- Upa --> NAF[NAF] + NAF -- Zpn --> BSF[BSF] + BSF -- Zh --> HSS[HSS] + +``` + +Figure 4.1-2: Network architecture of bootstrapping push procedure. A diagram showing four entities: UE, NAF, BSF, and HSS. UE is connected to NAF via the Upa interface. NAF is connected to BSF via the Zpn interface. BSF is connected to HSS via the Zh interface. + +**Figure 4.1-2: Network architecture of bootstrapping push procedure** + +The protocol stack of the Zh interface in Bootstrapping procedure is presented in Figure 4.2. The Diameter Base protocol is defined in [1] and the Diameter application in 3GPP TS 29.229 [3]. The requirements for Zh interface are defined in 3GPP TS 33.220 [5] and 3GPP TS 33.223 [23]. + +![Figure 4.2: Protocol stack of Zh interface. A diagram showing the protocol stacks for BSF and HSS. Both stacks consist of five layers: Zh application logic (in BSF or HSS), Diameter application, Diameter Base Protocol, SCTP, and IP. The IP layers of both stacks are connected by the Zh interface.](5dfc130b129ace4df375839020a5700d_img.jpg) + +| BSF | HSS | +|-----------------------------|-----------------------------| +| Zh application logic in BSF | Zh application logic in HSS | +| Diameter application | Diameter application | +| Diameter Base Protocol | Diameter Base Protocol | +| SCTP | SCTP | +| IP | IP | + +The IP layers of both stacks are connected by the Zh interface. + +Figure 4.2: Protocol stack of Zh interface. A diagram showing the protocol stacks for BSF and HSS. Both stacks consist of five layers: Zh application logic (in BSF or HSS), Diameter application, Diameter Base Protocol, SCTP, and IP. The IP layers of both stacks are connected by the Zh interface. + +**Figure 4.2: Protocol stack of Zh interface** + +The MAP based Bootstrapping Zh' interface is defined in the section 4.3. + +## 4.2 Protocol Zh between BSF and HSS + +The requirements for Zh interface are defined in 3GPP TS 33.220 [5] and 3GPP TS 33.223 [23]. + +The Bootstrapping Zh interface performs the retrieval of an authentication vector and possibly GBA User Security Settings from the HSS. + +The overall Bootstrapping procedure is depicted in Figure 4.3. The basic procedure is: + +- A UE starts the bootstrapping procedure by protocol Ub with a BSF giving the IMPI of the user (see 3GPP TS 24.109 [7]). +- The BSF starts protocol Zh with user's HSS + +- The BSF requests user's authentication vector and GBA User Security Settings (GUSS) corresponding to the IMPI. If the authentication scheme is to use SIP Digest credentials, the BSF shall indicate this in the request. +- The HSS supplies to the BSF the requested authentication vector and GUSS (if applicable, cf. 3GPP TS 33.220 [5]). The HSS supplies the requested authentication vector relating to SIP Digest only if explicitly indicated in the request. + +NOTE 1: If there is more than one HSS deployed within the network, the BSF may have to contact the SLF using the Dz interface prior to sending the request for information to the HSS (see section 6.4). + +C) The BSF continues the protocol Ub with the UE (see 3GPP TS 24.109 [7]). + +![Sequence diagram of the GBA bootstrapping procedure between UE, BSF, and HSS.](1b5a812c8aa20fd5cba28e97001d32de_img.jpg) + +``` + +sequenceDiagram + participant UE + participant BSF + participant HSS + Note left of UE: If non-IMS subscriber, generates IMPI from IMSI + UE->>BSF: Bootstrapping-Request (IMPI) + BSF->>HSS: 1. Multimedia-Auth-Request ( IMPI ) + Note right of HSS: 2. HSS derives Authentication data and fetches GUSS for IMPI. + HSS->>BSF: 3. Multimedia-Auth-Answer (Authentication data, GAA-UserSecSettings) + Note right of BSF: 4. BSF stores bootstrapping information tuple for IMPI. + BSF->>UE: Bootstrapping-Answer (realm,nonce,algorithm) + Note right of UE: The rest of the Bootstrapping procedure + +``` + +The diagram illustrates the GBA bootstrapping procedure involving three main entities: UE (User Equipment), BSF (Bootstrap Server), and HSS (Home Subscriber Server). The sequence of messages is as follows: + + +- The UE sends a **Bootstrapping-Request (IMPI)** to the BSF over the **Ub** interface. A note indicates that if the UE is a non-IMS subscriber, it generates an IMPI from its IMSI. +- The BSF sends a **1. Multimedia-Auth-Request ( IMPI )** to the HSS over the **Zh** interface. +- The HSS performs an internal step: **2. HSS derives Authentication data and fetches GUSS for IMPI.** +- The HSS sends a **3. Multimedia-Auth-Answer (Authentication data, GAA-UserSecSettings)** back to the BSF over the **Zh** interface. +- The BSF performs an internal step: **4. BSF stores bootstrapping information tuple for IMPI.** +- The BSF sends a **Bootstrapping-Answer (realm,nonce,algorithm)** back to the UE over the **Ub** interface. +- A final note indicates **The rest of the Bootstrapping procedure** follows between the UE and BSF. + +Sequence diagram of the GBA bootstrapping procedure between UE, BSF, and HSS. + +Figure 4.3: The GBA bootstrapping procedure + +The overall Bootstrapping Push procedure is depicted in Figure 4.4. The Push procedure shall not apply with an authentication scheme using SIP Digest credentials. The Push procedure is: + +A) A NAF sends a bootstrapping push request to the BSF via Zpn interface including the IMPI or IMPU of the user (see section 5). + +B) The BSF starts protocol Zh with user's HSS + +- The BSF requests user's authentication vector and GBA User Security Settings (GUSS) corresponding to the IMPI or IMPU. +- The HSS supplies to the BSF the requested authentication vector and GUSS (if any). + +NOTE 2: If there is more than one HSS deployed within the network, the BSF may have to contact the SLF using the Dz interface prior to sending the request for information to the HSS (see section 6.4). + +C) The BSF continues the protocol Zpn with the NAF (see section 5). + +D) The NAF starts protocol Upa with the UE, as specified in 3GPP TS 24.109 [7]. + +![Sequence diagram of the GBA bootstrapping Push procedure. The diagram shows five entities: UE, NAF, BSF, HSS, and NAF. The sequence of messages is: 1. NAF sends a 'Generate GPI Request' to BSF. 2. BSF sends a 'GPI-Request (IMPI or IMPU, NAF-Id)' to NAF. 3. BSF sends a 'Multimedia-Auth-Request (IMPI or IMPU)' to HSS. 4. HSS generates AV and fetches GUSS for IMPI. 5. HSS sends a 'Multimedia-Auth-Answer (RAND, AUTN, XRES, CK, IK, GAA-UserSecSettings)' to BSF. 6. BSF generates GPI. 7. BSF sends a 'GPI-Response (GPI)' to NAF. 8. NAF sends a 'GPI Push' to UE.](75f0cb39f1cd165dfe4a6aa6c4d9388d_img.jpg) + +``` + +sequenceDiagram + participant UE + participant NAF + participant BSF + participant HSS + Note right of NAF: Generate GPI Request + NAF->>BSF: GPI-Request (IMPI or IMPU, NAF-Id) + BSF->>HSS: 1. Multimedia-Auth-Request (IMPI or IMPU) + Note right of HSS: 2. HSS generates AV and fetches GUSS for IMPI. + HSS->>BSF: 3. Multimedia-Auth-Answer (RAND, AUTN, XRES, CK, IK, GAA-UserSecSettings) + Note right of BSF: 4. BSF generates GPI + BSF->>NAF: GPI-Response (GPI) + Note right of NAF: GPI Push + NAF->>UE: GPI Push + +``` + +Sequence diagram of the GBA bootstrapping Push procedure. The diagram shows five entities: UE, NAF, BSF, HSS, and NAF. The sequence of messages is: 1. NAF sends a 'Generate GPI Request' to BSF. 2. BSF sends a 'GPI-Request (IMPI or IMPU, NAF-Id)' to NAF. 3. BSF sends a 'Multimedia-Auth-Request (IMPI or IMPU)' to HSS. 4. HSS generates AV and fetches GUSS for IMPI. 5. HSS sends a 'Multimedia-Auth-Answer (RAND, AUTN, XRES, CK, IK, GAA-UserSecSettings)' to BSF. 6. BSF generates GPI. 7. BSF sends a 'GPI-Response (GPI)' to NAF. 8. NAF sends a 'GPI Push' to UE. + +Figure 4.4: The GBA bootstrapping Push procedure + +The steps of the bootstrapping procedure over Zh reference point in Figure 4.3 and Figure 4.4 are: + +### Step 1 + +The BSF shall send the following Bootstrapping-Request to the HSS in the format of Multimedia-Auth-Request (MAR) message. The content of the message is given below in the same format as in 3GPP TS 29.229 [3]. The curly brackets indicate mandatory AVPs. The square brackets indicate optional AVPs. The "address of" refers to the Fully Qualified Host Name (FQDN). + +``` + + ::= + < Session-Id > + { Vendor-Specific-Application-Id } + { Auth-Session-State } ; NO_STATE_MAINTAINED + { Origin-Host } ; Address of BSF + { Origin-Realm } ; Realm of BSF + { Destination-Realm } ; Realm of HSS + [ Destination-Host ] ; Address of the HSS + [ User-Name ] ; IMPI from UE + [ Public-Identity ] ; IMPU from UE + [ SIP-Auth-Data-Item ] ; Authentication Scheme, + Synchronization Failure + [ GUSS-Timestamp ] ; Timestamp of GUSS in BSF + *[ AVP ] + *[ Proxy-Info ] + *[ Route-Record ] + +``` + +The content of mandatory Vendor-Specific-Application-ID according [1] is: + +``` + ::= + 1* [Vendor-Id] ; 3GPP is 10415 + 0*1 {Auth-Application-Id} ; 16777221 + 0*1 {Acct-Application-Id} ; Omitted +``` + +When determining the value of Destination-Host AVP the BSF can use redirector function (SLF) to resolve the address of the HSS if needed (see 3GPP TS 29.229 [3]). The BSF shall set the Auth-Session-State AVP to NO\_STATE\_MAINTAINED to inform that the HSS does not need to maintain any status information for this session according 3GPP TS 29.229 [3]. + +The User-name is the IMS Private User Identity (IMPI) as required in 3GPP TS 29.228 [2]. In bootstrapping push procedures the IMPI may not be available to the NAF and BSF. In such cases, only the Public-Identity AVP shall be present instead, and shall contain the IMS Public User Identity, otherwise only the User-Name AVP shall be present. If the identity received from the NAF is an MSISDN, the BSF shall include this MSISDN in the form of a tel URI in the Public-Identity AVP (see 3GPP TS 29.229 [2]). + +If the BSF supports the GUSS timestamp mechanism and has local copy of the GUSS, which has a timestamp, the BSF may include the GUSS-Timestamp AVP. In this case the GUSS-Timestamp AVP shall contain the timestamp from subscriber's GUSS. Otherwise the GUSS-Timestamp AVP shall not be present. + +The SIP-Auth-Data-Item AVP, when present, shall indicate the authentication scheme chosen, i.e SIP Digest when applicable. By default, when the SIP-Auth-Data-Item AVP is not present, the authentication scheme is Digest-AKA v1-MD5. The SIP-Auth-Data-Item AVP should not be present to indicate the authentication scheme is Digest-AKA v1-MD5. + +NOTE 3: A pre-Rel-11 HSS only received SIP-Auth-Data-Item AVP in Zh MAR in case of synchronization failure for IMS-AKA. Apart from that, when SIP-Auth-Data-Item AVP was not present, it implied that the authentication scheme was Digest-AKA v1-MD5. Therefore, if SIP-Auth-Data-Item AVP is not present, it means that the authentication scheme is Digest-AKA v1-MD5, like before Rel-11. Moreover, in order to avoid interoperability problems between a pre-Rel-11 HSS and a Rel-11 (or later) BSF, the BSF should not include the SIP-Auth-Data-Item AVP to indicate the authentication scheme is Digest-AKA v1-MD5. + +If the Authentication Request is triggered by a synchronization failure (see 3GPP TS 24.109 [7]), the BSF shall include the SIP-Auth-Data-Item AVP within the MAR message according to 3GPP TS 29.228 [2] + +### Step 2 + +When the HSS receives the MAR message, the HSS shall derive the user Authentication Vector (AV) information according the IMPI and, if present, the authentication scheme and populates it into SIP-Auth-Data-Item AVP as defined for IMS-AKA or SIP Digest authentication schemes in 3GPP TS 29.229 [3]. Only one AV shall be provided. + +If the Public User Identity is received, the HSS shall resolve to the corresponding IMPI/IMSI associated to such IMPU/MSISDN before deriving the AV information. If Public to Private identity resolution is not possible i.e. due to the IMPU is shared with multiple IMPIs, the HSS shall set the Experimental-Result-Code to DIAMETER\_ERROR\_OPERATION\_NOT\_ALLOWED (see 3GPP TS 29.329 [32]). + +If the request indicates that there is a synchronization failure, the HSS shall process AUTS as described in 3GPP TS 33.203 [31] and return the requested authentication information. The Result-Code shall be set to DIAMETER\_SUCCESS. + +If GUSS exists for the IMPI, the HSS shall do one of the following: + +1. If the HSS supports the GUSS timestamp mechanism and received the GUSS-Timestamp AVP in MAR message then it shall compare the timestamp of the GUSS in the HSS with the received timestamp. + - If timestamps are equal, then it shall populate the GBA-UserSecSettings AVP with static string "GUSS TIMESTAMP EQUAL". + - If the GUSS-Timestamp AVP was not received, or timestamps are not equal, then it shall populate the GBA-UserSecSettings AVP with the GUSS. +2. If the HSS does not support GUSS timestamp mechanism, it shall populate the GBA-UserSecSettings AVP with the GUSS. + +The MAR/MAA sequence in the Zh interface must not change possible status information of the possible simultaneously ongoing IMS MM application sessions in the HSS. + +If the User-Name (IMPI) or Public-Identity (IMPU) from the BSF is totally unknown to the HSS, the error situation 5401 is raised. + +Exceptions to the cases specified here shall be treated by HSS as error situations. The Result-Code shall be set to DIAMETER\_UNABLE\_TO\_COMPLY and no authentication or GUSS information shall be returned. + +### Step 3 + +The HSS shall send the following Bootstrapping-Answer message in the format of Multimedia-Auth-Answer (MAA) message back to the BSF. + +``` +< Multimedia-Auth-Answer> ::= < Diameter Header: 303, PXY, 16777221 > + < Session-Id > + { Vendor-Specific-Application-Id } + [ Result-Code ] + [ Experimental-Result ] + { Auth-Session-State } ; NO_STATE_MAINTAINED + { Origin-Host } ; Address of HSS + { Origin-Realm } ; Realm of HSS + [ User-Name ] ; IMPI + [ Public-Identity ] ; IMPU + [ SIP-Auth-Data-Item ] + [ GBA-UserSecSettings ] ; GUSS + *[ AVP ] + *[ Proxy-Info ] + *[ Route-Record ] +``` + +The HSS shall set the mandatory Auth-Session-State AVP to NO\_STATE\_MAINTAINED because the HSS does not maintain any state information about this session and the BSF does not need to send any session termination request 3GPP TS 29.229 [3]. + +If the Public-Identity was present in the request, both Public-Identity and User-Name AVPs shall be present in the response. Otherwise, the User-name AVP (IMPI) may be sent back for checking. + +The required authentication vector data is sent in the SIP-Auth-Data-Items AVP as defined for IMS-AKA or SIP Digest authentication schemes according to 3GPP TS 29.228 [2]. The security settings of user's all GAA applications are sent in GBA-UserSecSettings AVP. + +If the 2G GBA option (see 3GPP TS 33.220, Annex I [5]) is applied for the user the SIP-Auth-Data-Item AVP shall be filled as follows: The SIP-Authentication-Scheme AVP is set to "Digest-AKA-v1-MD5-2G-GBA" to indicate a 2G GBA vector for GBA. The SIP-Authenticate AVP contains only RAND. The SIP-Authorization AVP contains RES. The Confidentiality-Key AVP contains Kc. The Integrity-Key AVP shall not be present. If a 2G Authentication Vector is requested for the user but the 2G GBA option is not supported by the HSS, the HSS shall set the Experimental-Result-Code to DIAMETER\_AUTHENTICATION\_SCHEME\_NOT\_SUPPORTED (see 3GPP TS 29.228 [2]). + +### Step 4 + +When the BSF receives the MAA message, the BSF shall check the value of the SIP-Authentication-Scheme AVP. If the BSF does not support the authentication-scheme the BSF shall stop processing the message and should indicate an error via the O&M subsystem. + +The BSF generates the needed key material (Ks) as described in 3GPP TS 33.220 [5] and stores temporarily the tuple for further use in GAA applications. The rest of the bootstrapping procedure in Ub interface will later add also the Bootstrapping Transaction Identifier (B-TID) to that tuple as key and the key lifetime (expiry time). + +If the BSF sent the GUSS-Timestamp AVP in step 1, and if the GBA-UserSecSettings AVP contains a static string "GUSS TIMESTAMP EQUAL", then the local copy of the GUSS in the BSF shall be preserved. If the GBA-UserSecSettings AVP was not present in the MAA message, the local copy of the GUSS shall be deleted. If the GBA-UserSecSettings AVP contains a new GUSS, the local copy of the GUSS shall be deleted, and the new GUSS shall be stored in the BSF. + +In GBA Bootstrapping Push procedures, the BSF generates the requested NAF-key(s) according to provided NAF\_Id + +and the GBA Push Information (GPI). The BSF completes the rest of the bootstrapping push procedure sending its response to the NAF over Zpn interface, and deleting the Ks used as defined in section 5. + +## 4.3 Protocol Zh' between BSF and HLR + +The requirements for Zh' reference point are the same with the one for the Zh reference point defined in 3GPP TS 33.220 [5], except that the GBA User Security Settings (GUSS) are not supported. + +The Bootstrapping Zh' interface performs the retrieval of an authentication vector. The basic procedure is: + +- A) A UE starts the bootstrapping procedure by protocol Ub with a BSF giving the IMPI of the user (see 3GPP TS 24.109 [7]). In bootstrapping push procedures a NAF initiates a GBA Push Information Request by protocol Zpn with the BSF giving the user identity (see section 5). The BSF derives the IMSI from the IMPI. In bootstrapping push procedures when only the Public Identity of the user is made available to the BSF, the BSF shall perform public to private identity resolution as defined in section 4.3.1. +- B) The BSF starts protocol Zh' with user's HLR + - The BSF requests user's authentication vector corresponding to the IMSI. + - The HLR supplies to the BSF the requested authentication vector. +- C) The BSF continues the protocol Ub with the UE (see 3GPP TS 24.109 [7]). + +The BSF shall use the following Bootstrapping-Request to the HLR in the format of a MAP\_SEND\_AUTHENTICATION\_INFO. The content of the request, result and error messages is given below in the same format as in 3GPP TS 29.002 [19]. The parameter usage is as follows: + +### IMSI + +See 3GPP TS 29.002 [19] section 7.6.2 for the use of this parameter. + +#### Number of requested vectors + +The BSF shall only request one authentication vector at a time. + +### Requesting node type + +BSF + +### Re-synchronisation Info + +For definition and use of this parameter see 3GPP TS 33.102 [20]. + +### Segmentation prohibited indicator + +This parameter is not applicable and should not be sent by the BSF. + +### Immediate response preferred indicator + +This parameter indicates that one of the requested authentication vectors is requested for immediate use in the BSF. + +### Requesting PLMN ID + +The PLMN-ID of the requesting node. See 3GPP TS 23.003 [21]. + +### AuthenticationSetList + +One authentication vector is transferred from the HLR to the BSF, if the outcome of the service was successful. + +### User error + +One of the following error causes defined in 3GPP TS 29.002 [19] shall be sent by the user in case of unsuccessful outcome of the service, depending on the respective failure reason: + +- unknown subscriber; + +- unexpected data value; +- system failure; +- data missing. + +### Provider error + +See 3GPP TS 29.002 [19] for the use of this parameter. + +When the BSF receives the response of the MAP\_SEND\_AUTHENTICATION\_INFO service, then it shall generate the needed key material (Ks) from confidential key (CK) and integrity key (IK) as described in 3GPP TS 33.220 [5], respectively from Kc as described in 3GPP TS 33.220 [5] and stores temporarily the tuple for further use in GAA/GBA applications. The rest of the bootstrapping procedure in Ub interface will later add also the Bootstrapping Transaction Identifier (B-TID) to that tuple as key and the key lifetime (expiry time). + +### 4.3.1 Public to Private Identity Resolution over Zh between BSF and HLR + +When the UE identity used by the NAF in a GPI Request towards the BSF is an MSISDN, the BSF shall resolve the corresponding private user identity (IMSI) for the user. + +When Zh interface between BSF and HLR is used, the BSF shall resolve the private user identity with the HLR in the format of a MAP\_SEND\_IMSI or a MAP\_SEND\_ROUTING\_INFO\_FOR\_SM. + +The content of the request, result and error messages is given below in the same format as in 3GPP TS 29.002 [19]. The parameter usage when the MAP\_SEND\_IMSI operation is used is as follows: + +#### MSISDN + +See 3GPP TS 29.002 [19] section 7.6.2 for the use of this parameter. + +#### IMSI + +See 3GPP TS 29.002 [19] section 7.6.2 for the use of this parameter. The presence of this parameter is mandatory in a successful case. + +#### User error + +Only one of the following values is applicable: + +- Unknown subscriber; +- Unexpected data value; +- Data missing. + +The parameter usage when the MAP\_SEND\_ROUTING\_INFO\_FOR\_SM operation is used is as follows: + +#### MSISDN + +See 3GPP TS 29.002 [19] section 7.6.2 for the use of this parameter. + +#### SM-RP-PRI + +BSF shall set this parameter to indicate that delivery of the short message shall NOT be attempted when a service centre address is already contained in the Message Waiting Data file. + +#### Service Centre Address + +BSF shall include the BSF address within this parameter. + +#### SM-RP-MTI + +#### SM-RP-SMEA + +#### GPRS Support Indicator + +BSF shall not use these parameters in the public to private identity resolution request. + +#### SM-Delivery Not Intended + +BSF shall set this parameter to indicate that delivery of a short message is not intended and that only IMSI is requested. + +#### IMSI + +See 3GPP TS 29.002 [19] section 7.6.2 for the use of this parameter. The presence of this parameter is mandatory in a successful case. + +#### Network Node Number + +#### LMSI + +#### GPRS Node Indicator + +#### Additional Number + +BSF ignores these parameters if present in the public to private identity resolution response. + +#### User error + +One of the following error causes defined in 3GPP TS 29.002 [19] shall be sent by the user in case of unsuccessful outcome of the service, depending on the respective failure reason: + +- Unknown subscriber; +- Call Barred; +- Teleservice Not Provisioned; +- Absent Subscriber\_SM; +- Facility Not Supported; +- System failure; +- Unexpected Data Value; +- Data missing. + +#### Provider error + +See 3GPP TS 29.002 [19] for the use of this parameter. + +When the HLR is able to resolve the private identity of the user, the BSF continues with the bootstrapping procedures over Zh and requests a user's authentication vector corresponding to the IMSI as defined above. Otherwise the BSF provides the corresponding error to the NAF over Zpn as defined in section 5. + +# 5 GAA Application Zn and Zpn interfaces + +## 5.1 Applications' network architecture + +The network architecture of the GAA applications procedure using Zn is presented in Figure 5.1-1. The 3GPP GAA applications are listed in annex B. Different GAA applications may implement the Ua interface in different way. The Zn interface is defined in this specification. + +![Figure 5.1-1: Network architecture of GAA application using Zn](4cc7cdce3d498d8b0ba033a9be24ade5_img.jpg) + +``` +graph LR; UE[UE] -- Ua --> NAF[NAF]; NAF -- Zn --> BSF[BSF]; +``` + +The diagram shows a linear network architecture for GAA applications. It consists of three main components connected in a sequence: a User Equipment (UE) block, a Network Application Function (NAF) block, and a Bootstrap Server (BSF) block. The UE is connected to the NAF via the Ua interface. The NAF is connected to the BSF via the Zn interface. + +Figure 5.1-1: Network architecture of GAA application using Zn + +**Figure 5.1-1: Network architecture of GAA application using Zn** + +The network architecture of GBA push procedure using Zpn is presented in Figure 5.1-2. The Zpn interface is also defined in this specification. + +![Figure 5.1-2: Network architecture of GBA push procedure using Zpn](608f1b5ef8f3dc0723f2b4ea1fb72be2_img.jpg) + +``` +graph LR; UE[UE] -- Upa --> NAF[NAF]; NAF -- Zpn --> BSF[BSF]; +``` + +The diagram shows a linear network architecture for GBA push procedures. It consists of three main components connected in a sequence: a User Equipment (UE) block, a Network Application Function (NAF) block, and a Bootstrap Server (BSF) block. The UE is connected to the NAF via the Upa interface. The NAF is connected to the BSF via the Zpn interface. + +Figure 5.1-2: Network architecture of GBA push procedure using Zpn + +**Figure 5.1-2: Network architecture of GBA push procedure using Zpn** + +Two options are specified for the protocol stack to be used on the Zn and Zpn interface: + +The protocol stack of the DIAMETER based Zn interface, + +the protocol stack of the Web Services based Zn interface. + +The BSF shall support both options whereas the NAF shall support one or both of these options. + +The protocol stack of the Diameter based implementation of the Zn interface for GAA applications and Zpn interface for GBA push procedure is presented in Figure 5.2-1. The Zn interface is specified in clause 5.2. The Zpn interface is specified in clause 5.4. The diameter Base protocol is defined in [1] and the Diameter application in 3GPP TS 29.229 [3]. The requirements for Zn interface are defined in 3GPP TS 33.220 [5]. The requirements for Zpn interface are defined in 3GPP TS 33.223 [23]. + +![Figure 5.2-1: Protocol stack of Diameter based Zn and Zpn interfaces. The diagram shows two protocol stacks for NAF and BSF. Both stacks have five layers: Zn/Zpn application logic (yellow), Diameter application (light blue), Diameter Base (light blue), SCT (white), and IP (white). The IP layers of both stacks are connected by a line labeled Zn/Zpn.](e180f2b5fcbe8001554a7c0677cd3f82_img.jpg) + +| NAF | | BSF | +|---------------------------------|--------|---------------------------------| +| Zn/Zpn application logic in NAF | | Zn/Zpn application logic in BSF | +| Diameter application | | Diameter application | +| Diameter Base | | Diameter Base | +| SCT | | SCT | +| IP | Zn/Zpn | IP | + +Figure 5.2-1: Protocol stack of Diameter based Zn and Zpn interfaces. The diagram shows two protocol stacks for NAF and BSF. Both stacks have five layers: Zn/Zpn application logic (yellow), Diameter application (light blue), Diameter Base (light blue), SCT (white), and IP (white). The IP layers of both stacks are connected by a line labeled Zn/Zpn. + +**Figure 5.2-1: Protocol stack of Diameter based Zn and Zpn interfaces** + +The protocol stack of the Web Services based Zn interface for GAA applications and Zpn interface for GBA push procedure is presented in Figure 5.2-2. The Zn interface is specified in clause 5.3. The Zpn interface is specified in clause 5.5. + +![Figure 5.2-2: Protocol stack of Web Services based Zn interface. The diagram shows two protocol stacks for NAF and BSF. Both stacks have five layers: Zn/Zpn application logic (yellow), SOAP (light blue), HTTP (light blue), TCP (white), and IP (white). The IP layers of both stacks are connected by a line labeled Zn/Zpn.](5793a44ffdadd039928e2f9fe6daae06_img.jpg) + +| NAF | | BSF | +|---------------------------------|--------|---------------------------------| +| Zn/Zpn application logic in NAF | | Zn/Zpn application logic in BSF | +| SOAP | | SOAP | +| HTTP | | HTTP | +| TCP | | TCP | +| IP | Zn/Zpn | IP | + +Figure 5.2-2: Protocol stack of Web Services based Zn interface. The diagram shows two protocol stacks for NAF and BSF. Both stacks have five layers: Zn/Zpn application logic (yellow), SOAP (light blue), HTTP (light blue), TCP (white), and IP (white). The IP layers of both stacks are connected by a line labeled Zn/Zpn. + +**Figure 5.2-2: Protocol stack of Web Services based Zn interface** + +## 5.2 Protocol Zn between NAF and BSF based on Diameter + +The requirements for Zn interface are defined in 3GPP TS 33.220 [5]. + +The protocol Zn retrieves the key material and possibly user security settings data by NAF from BSF. After UE is authenticated with the BSF, every time the UE wants to interact with an NAF the following steps are executed as depicted in Figure 5.3. The basic procedure is: + +A) The UE starts protocol Ua (see 3GPP TS 33.220 [5]) + +- In general, the UE and the NAF will not yet share the key(s) required to protect protocol Ua. If they already do, there is no need for the NAF to invoke protocol Zn. +- It is assumed that UE supplies sufficient information to NAF, i.e. the Bootstrapping Transaction Identifier (B-TID), to allow the NAF to retrieve specific key material (e.g. Ks\_NAF in the case of GBA\_ME, and Ks\_ext\_NAF or Ks\_int\_NAF or both in the case of GBA\_U) from BSF. +- The UE derives the keys required to protect protocol Ua from the key material. + +B) The NAF starts protocol Zn with BSF + +- The NAF requests NAF specific key material corresponding to the information supplied by the UE to the NAF (i.e. the bootstrapping transaction identifier) in the start of protocol Ua. +- The BSF generates and supplies to the NAF the requested NAF specific key material, the expiry time, the bootstrapinfo creation time, and the appropriate User Security Settings defined for received application identifiers. + +C) The NAF continues protocol Ua with the UE (see 3GPP TS 33.221 [6]) + +Once the run of protocol Ua is completed the purpose of bootstrapping is fulfilled as it enabled UE and NAF to run protocol Ua in a secure way. + +The common GAA application procedure is presented in Figure 5.3. + +![Sequence diagram of the Diameter based GAA application procedure between UE, NAF, and BSF.](6f31cdb576d2f15c35c3f266e5f59211_img.jpg) + +``` + +sequenceDiagram + participant UE + participant NAF + participant BSF + + Note over UE: UE knows: + Note over UE,NAF: { a security association created by bootstrapping } + Note over BSF: BSF has tuple: + + UE->>NAF: UE start the GAA application procedure by sending a B-TID. + Note right of NAF: GUSS is GBA User Security Settings. +GSID is GAA Service Indentifier. + NAF->>BSF: 1. Bootstrapping-Info-Request ( B-TID, GSID*, NAF-Id) + Note over BSF: 2. BSF checks the B-TID and derives ME-Key and UICC-Key + BSF-->>NAF: 3. Bootstrapping-Info-Answer ( IMPI, Key-ExpiryTime, Ks_(ext)_NAF, Ks_int_NAF, BootstrapInfoCreationTime, UserSecSetting* ) + Note over UE,NAF: UE and NAF mutually authenticate each others using ME-Ks + +``` + +**GUSS** is GBA User Security Settings. +**GSID** is GAA Service Indentifier. + +Sequence diagram of the Diameter based GAA application procedure between UE, NAF, and BSF. + +**Figure 5.3: The Diameter based GAA application procedure** + +The steps of the GAA application procedure in Figure 5.3 are: + +Step 1 + +The NAF shall send a Bootstrapping-Info-Request message (BIR) to the BSF. The content of the message is given here in the same format as in 3GPP TS 29.229 [3]. The curly brackets indicate mandatory AVPs. The square brackets indicate optional AVP. The address refers to the Fully Qualified Host Name (FQDN). + +``` + +< Bootstrapping-Info-Request> ::= + < Session-Id > + { Vendor-Specific-Application-Id } + [ Auth-Session-State ] ; NO_STATE_MAINTAINED + { Origin-Host } ; Address of NAF + { Origin-Realm } ; Realm of NAF + { Destination-Realm } ; Realm of BSF + [ Destination-Host ] ; Address of the BSF + * [ GAA-Service-Identifier ] ; Service identifiers + { Transaction-Identifier } ; B-TID + { NAF-Id } ; NAF_ID + [ GBA_U-Awareness-Indicator ] ; GBA_U awareness of the NAF + * [ AVP ] + * [ Proxy-Info ] + * [ Route-Record ] + +``` + +The content of Vendor-Specific-Application-ID according [1] is: + +``` + +::= + 1* [Vendor-Id] ; 3GPP is 10415 + 0*1 {Auth-Application-Id} ; 16777220 + 0*1 {Acct-Application-Id} ; Omitted + +``` + +The NAF should set the Auth-Session-State AVP to NO\_STATE\_MAINTAINED to inform that the BSF does not need to maintain any session state information for this session according 3GPP TS 29.229 [3]. + +The Destination-Realm AVP is set to subscriber's BSF. The address of the BSF is extracted from the B-TID. + +NOTE: In the case where the subscriber has contacted a NAF that is in a visited network, the NAF contacts the subscriber's home BSF through a Diameter based Proxy (Zn-Proxy) that is located in the same network as the NAF. The local BSF and the Zn-Proxy may be co-located. See 3GPP TS 33.220 [6]. + +The NAF indicates the GAA services for which the information is retrieved by GAA-Service-Identifier AVPs. The Bootstrapping Transaction Identifier defines the earlier bootstrapping procedure execution. + +### Step 2 + +In the successful case the BSF has a tuple identified by Bootstrapping Transaction Identifier (B-TID). When the BSF receives the request it checks the existence and validity of the tuple for given B-TID. If checking fails the BSF sends an Answer message with Experimental-Result set to indicate the error type 5403. If the tuple for B-TID exists, but is expired, error type 5403 is also sent to indicate needs for renewal of the bootstrapping procedure. In successful case the Result-Code is set to 2xxx as defined in [1]. + +The BSF derives the key material for the ME (i.e., Ks\_NAF in the case of GBA\_ME, and Ks\_ext\_NAF in the case of GBA\_U) and possibly the key material for the UICC (i.e., Ks\_int\_NAF in the case of GBA\_U) according to the B-TID and packs them into ME-Key-Material AVP and possible UICC-Key-Material AVP. The ME-Key-Material contains Ks\_(ext)\_NAF and the UICC-key-Material contains the Ks\_int\_NAF key. The BSF select correct user's Security Settings according the request's GAA-Service-Identifier AVP to GBA-UserSecSettings AVP. If NAF grouping is used by the operator and there are one or more USSs corresponding to the requested GSID, then also the nafGroup attribute of USS is checked. If the NAF has sent a GAA-Service-Identifier that does not have corresponding user's security settings, and the BSF is locally configured to reject those requests from the NAF, then the error 5402 is raised. If the NAF has sent a GAA-Service-Identifier that have corresponding user's security settings, but the BSF is locally configured to reject those from that NAF, then the error 5402 is raised too. + +The NAF may be addressed from the UE with different FQDNs. The BSF shall check if this NAF-Id is allowed to be used for the NAF. If the NAF identified by its Origin-Host AVP is configured in the BSF not to be authorized to use the given NAF-Id, the BSF may raise the error situation 5402. The BSF may also be configured so that a certain NAF is not authorized to use a certain GAA-Service-Identifier. This situation may be also indicated by error code 5402. + +Exceptions to the cases specified here shall be treated by BSF as error situations. The Result-Code shall be set to DIAMETER\_UNABLE\_TO\_COMPLY. + +### Step 3 + +After that the BSF shall send a Bootstrapping-Info-Answer message (BIA) back to the NAF. + +``` +< Boostrapping-Info-Answer> ::= < Diameter Header: 310, PXY, 16777220 > + < Session-Id > + { Vendor-Specific-Application-Id } + [ Auth-Session-State ] ; NO_STATE_MAINTAINED + [ Result-Code ] + [ Experimental-Result] + { Origin-Host } ; Address of BSF + { Origin-Realm } ; Realm of BSF + [ User-Name ] ; IMPI + [ ME-Key-Material ] ; Required + [ UICC-Key-Material ] ; Conditional + [ Key-ExpiryTime ] ; Time of expiry + [ BootstrapInfoCreationTime ] ; Bootstrapinfo creation time + [ GBA-UserSecSettings ] ; Selected USSS + [ GBA-Type ] ; GBA type used in bootstrapping + *[ AVP ] + *[ Proxy-Info ] + *[ Route-Record ] +``` + +The BSF shall set the Auth-Session-State AVP to NO\_STATE\_MAINTAINED because the BSF does not maintain any session state information about this session and the NAF does not need to send any session termination request 3GPP TS 29.229 [3]. + +The BSF may or may not send the User-name AVP (IMPI) according its configuration. + +The mandatory common key material with the ME (Ks\_NAF or Ks\_ext\_NAF) is sent in the ME-Key-Material AVP. The common key material with the UICC (Ks\_int\_NAF) is optionally sent in the UICC-Key-Material AVP only if the "uiccType" tag in bsfInfo from the HSS is set to "GBA\_U". + +The Key-ExpiryTime AVP contains the expiry time of the Bootstrapping information in the BSF according its configuration. The expiry time is represented according the Diameter Time data format in seconds that have passed since 0h on January 1, 1900 UTC . If a special key lifetime value is given in the "lifeTime" tag inside the bsfInfo from the HSS in bootstrapping procedure, it is used instead of the BSF default configuration value when the expiry time is calculated. + +The BootstrapInfoCreationTime AVP contains the bootstrapinfo creation time, i.e., creation time of the Bootstrapping information in the BSF. The bootstrapinfo creation time is represented in seconds that have passed since January 1, 1900 00:00:00.000 UTC. + +The BSF selects the appropriate User Security Settings (if any) to the GBA-UserSecSettings AVP from stored GAA-UserSecSettings in Bootstrapping information according the GBA-Service-Identifier AVPs in the request message. + +The BSF shall indicate the type of used authentication in the bootstrapping procedure to the NAF in GBA-Type, if other than 3G GBA type has been performed. + +When the NAF receives the BIA message, the NAF shall check the value of the GBA-Type AVP if it is included in the message. If the NAF does not support the GBA-Type the NAF shall stop processing the message and should indicate an error via the O&M subsystem. The further procedure in the NAF when the BIA is received is described in 3GPP TS 33.220 [5], 3GPP TS 33.222 [11] and optionally in GAA service type specific TSs. + +## 5.3 Protocol Zn between NAF and BSF based on Web Services + +The procedures in the NAF and in the BSF related Web Services [13] based Zn interface are the same as specified in clause 5.2, but instead of Diameter messages a Web Services procedures shall be used to communicate over Zn interface. Annex D specifies the GBA Service for Web Services, i.e., it contains the Web Services Definition Language (WSDL) [14] specification for GBA Service. Below are the attributes that are defined for GBA Service request, response, and fault cases. + +![Sequence diagram of the Web Services based GAA application procedure. Lifelines: UE, NAF, BSF. UE knows . NAF has a security association. BSF has a tuple . UE starts GAA application by sending B-TID. NAF sends requestBootstrappingInfoRequest to BSF. BSF checks B-TID and derives ME-Key and UICC-Key. BSF sends requestBootstrappingInfoResponse to NAF. UE and NAF mutually authenticate using ME-Ks.](90ddb84c323b956e2d50a54d3f870566_img.jpg) + +``` + +sequenceDiagram + participant UE + participant NAF + participant BSF + + Note over UE, NAF: Ua + Note over NAF, BSF: Zn + + Note left of UE: UE knows: + + Note right of NAF: { a security association +created by bootstrapping } + Note right of BSF: BSF has tuple: + + + UE->>NAF: UE start the GAA application procedure +by sending a B-TID. + NAF->>BSF: 1. requestBootstrappingInfoRequest +( b-tid, nafid, gsid*, +gbaUAware, extension ) + Note right of BSF: 2. BSF checks the B-TID +and derives +ME-Key and UICC-Key + BSF->>NAF: 3. requestBootstrappingInfoResponse +( impi, meKeyMaterial, +uiccKeyMaterial, keyExpiryTime, +bootstrappingInfoCreationTime, +gbaType, ussList, extension ) + Note over UE, NAF: UE and NAF mutually authenticate +each others using ME-Ks + +``` + +Sequence diagram of the Web Services based GAA application procedure. Lifelines: UE, NAF, BSF. UE knows . NAF has a security association. BSF has a tuple . UE starts GAA application by sending B-TID. NAF sends requestBootstrappingInfoRequest to BSF. BSF checks B-TID and derives ME-Key and UICC-Key. BSF sends requestBootstrappingInfoResponse to NAF. UE and NAF mutually authenticate using ME-Ks. + +**Figure 5.4: The Web Services based GAA application procedure** + +The possible attribute value definitions and restrictions for the request, response, and fault messages are the same as in clause 6 unless explicitly specified in this clause. The steps of the GAA application procedure in Figure 5.4 are: + +### Step 1 + +The NAF shall send a "requestBootstrappingInfoRequest" message to the BSF. The WSDL schema of this message is included in Annex D. + +Following elements are included into this message: + +- "btid" + +This is B-TID and defines the earlier bootstrapping procedure execution. Description in subclause 6.3.1.2 applies. + +- "nafid" + +This is the NAF-Id. Description in subclause 6.3.1.3 applies. + +- "gsid" + +This element contains the GAA Services Identifiers. Description in subclause 6.3.1.4 applies while the GAA Service Type Codes for 3GPP standardized services are defined in Annex B. + +- "gbaUAware" + +This element is optionally included. It indicates whether NAF is GBA\_U aware, and is capable of using and handling the "uiccKeyMaterial". The default value for "gbaUAware" is false. Description and values defined for the corresponding Diameter AVP in subclause 6.3.1.8 apply. + +The NAF may use one or more "extension" elements to include additional data to the request, but the BSF may ignore the additional data. + +This SOAP message shall be sent to BSF, then the URI of the message shall contain the BSF address extracted from "btid". In the case where the subscriber has contacted a NAF that is in a visited network, the + +NAF contacts the subscriber's home BSF through a GBA-Proxy that is located in the same network as the NAF. The local BSF and the GBA-Proxy may be co-located. See 3GPP TS 33.220 [6]. + +### Step 2 + +The procedures for step 2 are the same as in step 2 in clause 5.2. + +If any of the error situations described in step 2 in clause 5.2 arises, the BSF shall respond with a "requestBootstrappingInfoFault" message, as defined in Annex D. The "errorCode" element shall contain the corresponding Diameter error code (see clause 6.2.2). If the "errorText" is included, it shall contain a human-readable description of the error. + +### Step 3 + +After that, "requestBootstrappingInfoResponse" message is sent back to the NAF. The WSDL schema of this message is included in Annex D. + +Following elements are included into this message: + +- "impi" + +This element is optionally included according to BSF configuration. Description for User-Name AVP from 3GPP TS 29.229 [3] applies. + +- "meKeyMaterial" + +It includes the mandatory common key material with the ME (Ks\_NAF or Ks\_ext\_NAF). Description in subclause 6.3.1.6 applies. + +- "uiccKeyMaterial" + +This element is the common key material with the UICC (Ks\_int\_NAF). It is optionally sent only if the "uiccType" tag in "bsfInfo" (received by BSF from the HSS over Zh) is set to "GBA\_U". Description in subclause 6.3.1.7 applies. + +- "keyExpiryTime" + +It contains the expiry time of the Bootstrapping information in the BSF according its configuration. If a special key lifetime value is given in the "lifeTime" tag inside the "bsfInfo" (received by BSF from the HSS over Zh) in bootstrapping procedure, it shall be used instead of the BSF default configuration value when the expiry time is calculated. Description in subclause 6.3.1.5 applies. + +- "bootstrappingInfoCreationTime" + +This element contains the bootstrapinfo creation time, i.e., creation time of the Bootstrapping information in the BSF. Description in subclause 6.3.1.9 applies. + +- "gbaType" + +This element indicates the type of used authentication in the bootstrapping procedure to the NAF in "gbaType" element. It shall be included if other than 3G GBA type has been performed. Description and values defined for the corresponding Diameter AVP in subclause 6.3.1.11 apply. + +- "ussList" + +This element is optionally included. The BSF shall select the appropriate User Security Settings (if any) into the "ussList" element from stored GAA-UserSecSettings in Bootstrapping information according "gsid" elements in the request message. The "ussList" element contains a standalone XML document whose root element shall be "ussList" element as specified in Annex A and which contains the User Security Settings selected by the BSF. Description in subclause 6.3.1.1 applies. + +The BSF may use one or more "extension" elements to include additional data to the request, but the NAF may ignore the additional data. + +When the NAF receives the "requestBootstrappingInfoResponse" message, the NAF shall check the value of the "gbaType" element if it is included in the message. If the NAF does not support the GBA type the NAF + +shall stop processing the message and should indicate an error via the O&M subsystem. The further procedure in the NAF when the requestBootstrappingInfoResponse message is received is described in 3GPP TS 33.220 [5], 3GPP TS 33.222 [11] and optionally in GAA service type specific TSs. + +## 5.4 Protocol Zpn between NAF and BSF based on Diameter + +The requirements for Zpn interface are defined in 3GPP TS 33.223 [23]. + +The protocol Zpn retrieves the GPI, key material and possibly user security settings data by NAF from BSF. When the NAF wants to send data to the UE, but the NAF has no valid NAF-key available, the following steps are executed as depicted in Figure 5.4. The basic procedure is: + +In general, the UE and the NAF will not yet share the key(s) required to protect protocol Ua. If they already do, there is no need for the NAF to invoke protocol Zpn. + +It is assumed that the NAF has sufficient information available, i.e. user identity and the address of BSF. + +A) The NAF starts protocol Zpn with BSF + +- The NAF requests GBA-Push-Info (GPI), NAF specific key material corresponding to the user identity. +- The BSF fetches AVs from the HSS, generates and supplies to the NAF the requested GPI, NAF specific key material, the expiry time, the bootstrapinfo creation time, and the appropriate User Security Settings defined for received application identifiers. + +B) The NAF sends GPI over protocol Upa to the UE (see 3GPP TS 33.223 [23]) + +Once the run of protocol Upa is completed the purpose of bootstrapping is fulfilled and it will enable the UE and NAF to run protocol Ua in a secure way. + +The GBA push procedure over Zpn is presented in Figure 5.4. + +![Sequence diagram of the Diameter based GBA push procedure over Zpn. Lifelines: UE, NAF, BSF, HSS. The procedure involves: 1. GBA-Push-Info-Request from NAF to BSF; 2. BSF processing and AV request/response with HSS; 3. GBA-Push-Info-Answer from BSF to NAF; and finally a GPI push from NAF to UE.](28d75f39a24203712ee907b32cf0bbe5_img.jpg) + +``` + +sequenceDiagram + participant UE + participant NAF + participant BSF + participant HSS + + Note over UE, HSS: Interfaces: Upa (UE-NAF), Zpn (NAF-BSF), Zh (BSF-HSS) + + NAF->>BSF: 1. GBA-Push-Info-Request (user identity, NAF-Id, GSID*, ...) + + Note right of BSF: 2. BSF processing, generation of NAF keys and GPI + + BSF->>HSS: AV request (user identity, ...) + HSS-->>BSF: AV response (AV, USS, ...) + + BSF->>NAF: 3. GBA-Push-Info-Answer (IMPI, GPI, Ks_(ext)_NAF, Ks_int_NAF, USS, ...) + + NAF->>UE: GPI push (cf. TS 33.223) + +``` + +Sequence diagram of the Diameter based GBA push procedure over Zpn. Lifelines: UE, NAF, BSF, HSS. The procedure involves: 1. GBA-Push-Info-Request from NAF to BSF; 2. BSF processing and AV request/response with HSS; 3. GBA-Push-Info-Answer from BSF to NAF; and finally a GPI push from NAF to UE. + +**Figure 5.4-1: The Diameter based GBA push procedure over Zpn** + +The steps of the GBA push procedure in Figure 5.4-1 are: + +- Step 1 + +The NAF shall send a GBA-Push-Info-Request message to the BSF. The content of the message is given here in the same format as in 3GPP TS 29.229 [3]. The curly brackets indicate mandatory AVPs. The square brackets indicate optional AVP. The address refers to the Fully Qualified Domain Name (FQDN). + +``` + +< GBA-Push-Info-Request > ::= < Diameter Header: xxx, REQ, PXY, xxxxxxxx > + < Session-Id > + { Vendor-Specific-Application-Id } + { Origin-Host } ; Address of NAF + { Origin-Realm } ; Realm of NAF + { Destination-Realm } ; Realm of BSF + [ Destination-Host ] ; Address of the BSF + { UE-Id } ; User identity + { UE-Id-Type } ; Public or private identity + { UICC-App-Label } ; UICC application label +* [ GAA-Service-Identifier ] ; Service identifiers + { NAF-SA-Identifier } ; P-TID + { NAF-Id } ; NAF_ID + { UICC-ME } ; Use of GBA_ME or GBA_U + { Requested-Key-Lifetime } ; Requested NAF-Key lifetime + { Private-Identity-Request } ; Request private identity + [ GBA_U-Awareness-Indicator ] ; GBA_U awareness of the NAF + [ Security-Feature-Request ] ; Sec. feature request +* [ AVP ] +* [ Proxy-Info ] +* [ Route-Record ] + +``` + +The content of Vendor-Specific-Application-ID according [1] is: + +``` + +::= + 1* [Vendor-Id] ; 3GPP is 10415 + 0*1 {Auth-Application-Id} ; xxxxxxxx + 0*1 {Acct-Application-Id} ; Omitted + +``` + +The Destination-Realm AVP and Destination-Host AVP are set to subscriber's BSF. + +NOTE: In the case the NAF is in a visited network, the NAF contacts the subscriber's home BSF through a Diameter based Proxy (Zn-Proxy) that is located in the same network as the NAF. In this case the Destination-Host shall not be included. The local BSF and the Zn-Proxy may be co-located. See 3GPP TS 33.220 [6]. + +The NAF indicates the GAA services for which the information is retrieved by GAA-Service-Identifier AVPs. + +With UE-Id and UE-Id-Type AVPs the NAF indicates the user identity and its type, i.e. private or public. The NAF uses UICC-ME and UICC-App-Label AVPs to identify which UICC application is to be used and if GBA-ME or GBA\_U should be used. Private-Identity-Request indicates if the NAF requests the BSF to send the private user identity. Requested-Key-Lifetime AVP indicates the requested key lifetime for the NAF keys. NAF-SA-Identifier (P-TID) is sent to the BSF so that BSF can include it to the encrypted GPI. See 3GPP TS 33.223 [23]. + +The NAF may request information on the availability of security features using the Security-Features-Request AVP. The AVP may contain a semicolon-separated list of security features that are available ordered by preference. + +### - Step 2 + +When the BSF receives the GPI request it checks that the requested key lifetime in the GPI request is less than the allowed max value in the system. If checking fails the BSF sends an Answer message with Experimental-Result set to indicate the error type 5402. In successful case the Result-Code is set to 2xxx as defined in [1]. + +The BSF includes the received user identity (public or private) to the Zh protocol request. + +If GBA\_U was requested by the NAF, the BSF queries its database to find out if the private user identity is registered and if a valid Ks already exists. If a valid Ks exists, the BSF shall invalidate this Ks + +The BSF derives the key material for the ME (i.e., Ks\_NAF in the case of GBA\_ME, and Ks\_ext\_NAF in the case of GBA\_U) and possibly the key material for the UICC (i.e., Ks\_int\_NAF in the case of GBA\_U) according to the NAF-ID and packs them into ME-Key-Material AVP and possible UICC-Key-Material AVP. The ME-Key-Material contains Ks\_(ext)\_NAF and the UICC-key-Material contains the Ks\_int\_NAF key. The BSF select correct user's Security Settings according the request's GAA-Service-Identifier AVP to GBA-UserSecSettings AVP. If NAF grouping is used by the operator and there are one or more USSs corresponding to the requested GSID, then also the nafGroup attribute of USS is checked. If the NAF has sent a GAA-Service-Identifier that does not have corresponding user's security settings, and the BSF is locally configured to reject those requests from the NAF, then the error 5402 is raised. If the NAF has sent a GAA-Service-Identifier that have corresponding user's security settings, but the BSF is locally configured to reject those from that NAF, then the error 5402 is raised too. + +The BSF generates the GPI according to TS 33.223 [23]. + +The BSF shall check if this NAF-Id is allowed to be used for the NAF. If the NAF identified by its Origin-Host AVP is configured in the BSF not to be authorized to use the given NAF-Id, the BSF may raise the error situation 5402. The BSF may also be configured so that a certain NAF is not authorized to use a certain GAA-Service-Identifier. This situation may be also indicated by error code 5402. + +### - Step 3 + +After that the BSF shall send a GBA-Push-Info-Answer message back to the NAF. The BSF deletes the used Ks according to 3GPP TS 33.223 [23]. + +``` + +< GBA-Push-Info-Answer> ::= < Diameter Header: xxx, PXY, xxxxxxxx > + < Session-Id > + { Vendor-Specific-Application-Id } + [ Result-Code ] + [ Experimental-Result ] + { Origin-Host } ; Address of BSF + { Origin-Realm } ; Realm of BSF + [ User-Name ] ; IMPI + [ ME-Key-Material ] ; Required + [ UICC-Key-Material ] ; Conditional + [ Key-ExpiryTime ] ; Time of expiry + [ BootstrapInfoCreationTime ] ; Bootstrapinfo creation time + [ GBA-UserSecSettings ] ; Selected USSs + [ GBA-Type ] ; GBA type used in bootstrapping + [ GBA-Push-Info ] ; GBA Push Info + [ Security-Feature-Response ] ; Sec. feature response + *[ AVP ] + *[ Proxy-Info ] + *[ Route-Record ] + +``` + +The BSF may or may not send the User-name AVP (IMPI) It is only returned if requested and public user identity was used in the GBA-Push-Info-Request message according its configuration. + +The mandatory common key material with the ME (Ks\_NAF or Ks\_ext\_NAF) is sent in the ME-Key-Material AVP. The common key material with the UICC (Ks\_int\_NAF) is optionally sent in the UICC-Key-Material AVP only if the "uiccType" tag in bsfInfo from the HSS is set to "GBA\_U". + +The Key-ExpiryTime AVP contains the expiry time of the Bootstrapping information in the BSF according its configuration. The expiry time is represented according the Diameter Time data format in seconds that have passed since 0h on January 1, 1900 UTC . If a special key lifetime value is given in the "lifeTime" tag inside the bsfInfo from the HSS in bootstrapping procedure, it is used instead of the BSF default configuration value when the expiry time is calculated. + +The BootstrapInfoCreationTime AVP contains the bootstrapinfo creation time, i.e., creation time of the Bootstrapping information in the BSF. The bootstrapinfo creation time is represented in seconds that have passed since January 1, 1900 00:00:00.000 UTC. + +The BSF selects the appropriate User Security Settings (if any) to the GBA-UserSecSettings AVP from stored GAA-UserSecSettings in Bootstrapping information according the GBA-Service-Identifier AVPs in the request message. + +The BSF shall indicate the type of used authentication in the bootstrapping procedure to the NAF in GBA-Type, if other than 3G GBA type has been performed. + +The GBA-Push-Info AVP includes the GPI. The contents of GPI are defined in 3GPP TS 33.223 [23]. + +If the BSF supports the usage of securityFeature and the NAF has requested the securityFeatures from the BSF in the request, the BSF shall extract securityFeatures element from the bsfInfo element in subscriber's GUSS and add those security features to the Security-Features-Response AVP in the response which are common in the received securityFeatures request from the NAF and in the extracted information from the bsfInfo element. The common security features are added to the Security-Features-Response AVP in the order as they appear in the bsfInfo element. If securityFeatures element is not defined in the GUSS, or there is no common securityFeature, the BSF shall include an empty string to the Security-Features-Response AVP in the response. + +When the NAF receives the GBA-Push-Info-Answer message, the NAF shall check the value of the GBA-Type AVP if it is included in the message. If the NAF does not support the GBA-Type the NAF shall stop processing the message and should indicate an error via the O&M subsystem. The further procedure in the NAF when the GBA-Push-Info-Answer message is received is described in 3GPP TS 33.223 [23], 3GPP TS 24.109 [7]. + +## 5.5 Protocol Zpn between NAF and BSF based on Web Services + +The procedures in the NAF and in the BSF related Web Services [13] based Zpn interface are the same as specified in clause 5.4, but instead of Diameter messages a Web Services procedures shall be used to communicate over Zpn interface. AnnexG specifies the GBA Service for Web Services, i.e., it contains the Web Services Definition Language + +(WSDL) [14] specification for GBA Service. Below are the attributes that are defined for GBA Service request, response, and fault cases. + +![Sequence diagram of the Web Services based GAA application procedure. Lifelines: UE, NAF, BSF, HSS. The sequence starts with NAF sending a requestGbaPushInfoRequest to BSF. BSF sends an AV request to HSS and receives an AV response. BSF then sends a requestGbaPushInfoResponse to NAF. Finally, NAF sends a GPI push to UE.](9f9386d5b3d6cbeb1ed104a799320ebf_img.jpg) + +``` + +sequenceDiagram + participant UE + participant NAF + participant BSF + participant HSS + Note right of BSF: 2. BSF processing, generation of NAF keys and GPI + NAF->>BSF: 1. requestGbaPushInfoRequest (user identity, NAF-Id, GSID*, ...) + BSF->>HSS: AV request (user identity, ...) + HSS-->>BSF: AV response (AV, USS, ...) + BSF->>NAF: 3. requestGbaPushInfoResponse (IMPI, GPI, Ks_(ext)_NAF, Ks_int_NAF, USS, ...) + NAF->>UE: GPI push (cf. TS 33.223) + +``` + +Sequence diagram of the Web Services based GAA application procedure. Lifelines: UE, NAF, BSF, HSS. The sequence starts with NAF sending a requestGbaPushInfoRequest to BSF. BSF sends an AV request to HSS and receives an AV response. BSF then sends a requestGbaPushInfoResponse to NAF. Finally, NAF sends a GPI push to UE. + +**Figure 5.5: The Web Services based GAA application procedure** + +The possible attribute value definitions and restrictions for the request, response, and fault messages are the same as in clause 6 unless explicitly specified in this clause. The steps of the GAA application procedure in Figure 5.4 are: + +### Step 1 + +The NAF shall send a "requestGbaPushInfoRequest message" to the BSF. The WSDL schema of this message is included in Annex G. + +Following elements are included into this message: + +- "ptid" + +This is P-TID and it is given to the BSF so that it can be included in the encrypted "gbaPushInfo" element in the response. Description in subclause 6.3.1.19 applies. + +- "nafid" + +This is the NAF-Id. Description in subclause 6.3.1.3 applies. + +- "gsid" + +This element contains the GAA Services Identifiers. Description in subclause 6.3.1.4 applies while the GAA Service Type Codes for 3GPP standardized services are defined in Annex B. + +- "gbaUAware" + +This element is optionally included. It indicates whether NAF is GBA\_U aware, and is capable of using and handling the "uiccKeyMaterial". The default value for "gbaUAAware" is false. Description and values defined for the corresponding Diameter AVP in subclause 6.3.1.8 apply. + +#### - "userId" + +This element indicates the user identity. Description in subclause 6.3.1.12 applies. + +#### - "userIdType" + +This element indicates the user identity type, i.e. private or public. Description and values defined for the corresponding Diameter AVP in subclause 6.3.1.13 apply. + +#### - "uiccAppLabel" + +This element includes the UICC application identity to be used. Description in subclause 6.3.1.14 applies. + +#### - "uiccOrMe" + +This element indicates the BSF whether GBA\_ME or GBA\_U is to be used for GBA push. Description and values defined for the corresponding Diameter AVP in subclause 6.3.1.15 apply. + +#### - "requestedLifeTime" + +This element indicates the requested key lifetime for the NAF keys. Description in subclause 6.3.1.16 applies. + +#### - "privateIdRequest" + +- If this element is present it indicates that the NAF requests the BSF to send the private user identity of the user. Description and values defined for the corresponding Diameter AVP in subclause 6.3.1.17 apply. + +"securityFeaturesRequest" + +If this element is present it indicates that the NAF requests information on the availability of security features. The element may contain a semicolon-separated list of security features that are available ordered by preference. Description in subclause 6.3.1.20 applies while the values are defined in Annex A. + +The NAF may use one or more "extension" elements to include additional data to the request, but the BSF may ignore the additional data. + +This SOAP message shall be sent to BSF, then the URI of the message shall contain the BSF address. + +In the case the NAF is in a visited network, the NAF contacts the subscriber's home BSF through a GBA-Proxy that is located in the same network as the NAF. The local BSF and the GBA-Proxy may be co-located. See 3GPP TS 33.220 [6]. + +### Step 2 + +The procedures for step 2 are the same as in step 2 in clause 5.4. + +If any of the error situations described in step 2 in clause 5.4 arises, the BSF shall respond with a requestGbaPushInfoFault message, as defined in Annex G. The "errorCode" element shall contain the corresponding Diameter error code (see clause 6.2.2). If the "errorText" is included, it shall contain a human-readable description of the error. + +### Step 3 + +After that, the "requestGbaPushInfoResponse" message is sent back to the NAF. The WSDL schema of this message is included in Annex G. + +Following elements are included into this message: + +- "impi" + +This element is optionally included according to BSF configuration. It is only returned if requested and public user identity was used in "requestGbaPushInfoRequest" message. Description for User-Name AVP from 3GPP TS 29.229 [3] applies. + +#### - "meKeyMaterial" + +It includes the mandatory common key material with the ME (Ks\_NAF or Ks\_ext\_NAF). Description in subclause 6.3.1.6 applies. + +#### - "uiccKeyMaterial" + +This element is the common key material with the UICC (Ks\_int\_NAF). It is optionally sent only if the "uiccType" tag in "bsfInfo" (received by BSF from the HSS over Zh) is set to "GBA\_U". Description in subclause 6.3.1.7 applies. + +#### - "keyExpiryTime" + +It contains the expiry time of the Bootstrapping information in the BSF according its configuration. If a special key lifetime value is given in the "lifeTime" tag inside the "bsfInfo" (received by BSF from the HSS over Zh) in bootstrapping procedure, it shall be used instead of the BSF default configuration value when the expiry time is calculated. Description in subclause 6.3.1.5 applies. + +#### - "bootstrappingInfoCreationTime" + +This element contains the bootstrapinfo creation time, i.e., creation time of the Bootstrapping information in the BSF. Description in subclause 6.3.1.9 applies. + +#### - "gbaType" + +This element indicates the type of used authentication in the bootstrapping procedure to the NAF in "gbaType" element. It shall be included if other than 3G GBA type has been performed. Description and values defined for the corresponding Diameter AVP in subclause 6.3.1.11 apply. + +#### - "ussList" + +This element is optionally included. The BSF shall select the appropriate User Security Settings (if any) into the "ussList" element from stored GAA-UserSecSettings in Bootstrapping information according "gsid" elements in the request message. The "ussList" element contains a standalone XML document whose root element shall be "ussList" element as specified in Annex A and which contains the User Security Settings selected by the BSF. Description in subclause 6.3.1.1 applies. + +#### - "gbaPushInfo" + +This element includes the GPI. Description in subclause 6.3.1.18 applies. + +#### - "securityFeaturesResponse" + +If the BSF supports the usage of securityFeature and the NAF has requested the securityFeatures from the BSF in the request, the BSF shall extract securityFeatures element from the "bsfInfo" element in subscriber's GUSS and add those security features to the securityFeaturesResponse element in the response which are common in the received "securityFeaturesRequest" from the NAF and the extracted information from the "bsfInfo" element. The common security features are added to the "SecurityFeaturesResponse" element in the order as they appear in the "bsfInfo" element. If "securityFeatures" element is not defined in the GUSS or there is no common "securityFeature", the BSF shall add empty string to the "securityFeaturesResponse" element in the response. Description in subclause 6.3.1.21 applies while the values are defined in Annex A. + +The BSF may use one or more "extension" elements to include additional data to the request, but the NAF may ignore the additional data. + +When the NAF receives the "requestGbaPushInfoResponse" message, the NAF shall check the value of the "gbaType" element if it is included in the message. If the NAF does not support the GBA type the NAF shall stop processing the message and should indicate an error via the O&M subsystem. The further procedure in the NAF when the "requestGbaPushInfoResponse" message is received is described in 3GPP TS 33.220 [5], 3GPP TS 33.222 [11] and optionally in GAA service type specific TSs. + +# 6 Diameter application for Zh, Zn and Zpn interfaces + +## 6.0 Introduction + +The Zh, Zn and Zpn interface protocols are defined as IETF vendor specific Diameter applications, where the vendor is 3GPP. The vendor identifier assigned by IANA to 3GPP () is 10415. + +The Diameter application identifier assigned to the Zh interface application is 16777221 (allocated by IANA). + +The Diameter application identifiers assigned to the Zn and Zpn interface application are 16777220 and 16777268 respectively (allocated by IANA). + +## 6.1 Command-Code values + +The Zn and Zpn interfaces assign new Command-Codes 310 and 312. + +The messages in Zh interface use the same Command-Code value 303 as Multimedia-Auth-Request/Answer messages defined in 3GPP TS 29.229 [3] for Cx interface. + +## 6.2 Result-Code AVP values + +This section defines new result code values that must be supported by all Diameter implementations that conform to this specification. When one of the result codes defined here is included in a response, it shall be inside an Experimental-Result AVP and Result-Code AVP shall be absent. + +### 6.2.1 Success + +Errors that fall within the Success category are used to inform a peer that a request has been successfully completed. + +The success category result codes defined in 3GPP TS 29.229 [3] for Cx interface are useless and therefore not required in Zh, Zn and Zpn interfaces. + +### 6.2.2 Permanent failures + +Errors that fall within the Permanent Failures category are used to inform the peer that the request failed, and should not be attempted again. + +The Permanent failure category result codes defined in 3GPP TS 29.229 [3] for Cx interface are useless and therefore not required in Zh, Zn and Zpn interfaces. + +#### 6.2.2.1 DIAMETER\_ERROR\_IDENTITY\_UNKNOWN (5401) + +A message was received by the HSS for an IMPI or IMPU that is unknown. + +#### 6.2.2.2 DIAMETER\_ERROR\_NOT\_AUTHORIZED (5402) + +A message was received by the BSF which the BSF can not authorize. In this case the NAF should indicate to the UE that the service is not allowed. In case of GBA push, the NAF should not contact the UE. + +#### 6.2.2.3 DIAMETER\_ERROR\_TRANSACTION\_IDENTIFIER\_INVALID (5403) + +A message was received by the BSF for an invalid (e.g. unknown or expired) Bootstrapping Transaction Identifier (B-TID). In this case the NAF should request the UE to bootstrap again. + +#### 6.2.2.4 Void + +#### 6.2.2.5 Void + +#### 6.2.2.6 Void + +#### 6.2.2.7 Void + +## 6.3 AVPs + +The AVPs defined in 3GPP TS 29.229 [3] for 3GPP IMS Cx interface Multimedia-Auth-Request/Answer messages are used as they are. + +The following table describes the additional new Diameter AVPs defined for the Zh, Zn and Zpn interface protocol, their AVP Code values, types, possible flag values and whether or not the AVP may be encrypted. The Vendor-Id header of all AVPs defined in this specification shall be set to 3GPP (10415). + +**Table 6.1: New Diameter Multimedia Application AVPs** + +| Attribute Name | AVP Code | Section defined | Value Type | AVP Flag rules | | | | May Encr. | +|---------------------------|----------|-----------------|-------------|----------------|-----|------------|----------|-----------| +| | | | | Must | May | Should not | Must not | | +| GBA-UserSecSettings | 400 | 6.3.1.1 | OctedString | M, V | | | | No | +| Transaction-Identifier | 401 | 6.3.1.2 | OctetString | M, V | | | | No | +| NAF-Id | 402 | 6.3.1.3 | OctetString | M, V | | | | No | +| GAA-Service-Identifier | 403 | 6.3.1.4 | OctedString | M, V | | | | No | +| Key-ExpiryTime | 404 | 6.3.1.5 | Time | M, V | | | | No | +| ME-Key-Material | 405 | 6.3.1.6 | OctedString | M, V | | | | No | +| UICC-Key-Material | 406 | 6.3.1.7 | OctedString | M, V | | | | No | +| GBA_U-Awareness-Indicator | 407 | 6.3.1.8 | Enumerated | M, V | | | | No | +| BootstrapInfoCreationTime | 408 | 6.3.1.9 | Time | M, V | | | | No | +| GUSS-Timestamp | 409 | 6.3.1.10 | Time | V | | | M | No | +| GBA-Type | 410 | 6.3.1.11 | Enumerated | M, V | | | | No | +| UE-Id | 411 | 6.3.1.12 | OctetString | M, V | | | | No | +| UE-Id-Type | 412 | 6.3.1.13 | Enumerated | M, V | | | | No | +| UICC-App-Label | 413 | 6.3.1.14 | OctetString | M, V | | | | No | +| UICC-ME | 414 | 6.3.1.15 | Enumerated | M, V | | | | No | +| Requested-Key-Lifetime | 415 | 6.3.1.16 | Time | M, V | | | | No | +| Private-Identity-Request | 416 | 6.3.1.17 | Enumerated | M, V | | | | No | +| GBA-Push-Info | 417 | 6.3.1.18 | OctedString | M, V | | | | No | +| NAF-SA-Identifier | 418 | 6.3.1.19 | OctedString | M, V | | | | No | +| Security-Feature-Request | 419 | 6.3.1.20 | OctetString | M, V | | | | No | +| Security-Feature-Response | 420 | 6.3.1.21 | OctetString | M, V | | | | No | + +NOTE 1: The AVP header bit denoted as 'M', indicates whether support of the AVP is required. The AVP header bit denoted as 'V', indicates whether the optional Vendor-ID field is present in the AVP header. + +### 6.3.1 Common AVPs + +#### 6.3.1.1 GBA-UserSecSettings AVP + +The GBA-UserSecSettings AVP (AVP code 400) is of type OctetString. If transmitted on the Zh interface it contains GBA user security settings (GUSS). If transmitted on the Zn interface it contains the relevant USSs only. The content of GBA-UserSecSettings AVP is a XML document whose root element shall be the "guss" element for Zh interface and the "ussList" element for the Zn interface. The XML schema is defined in annex A. + +#### 6.3.1.2 Transaction-Identifier AVP + +The Transaction-Identifier AVP (AVP code 401) is of type OctetString. This AVP contains the Bootstrapping Transaction Identifier (B-TID). + +#### 6.3.1.3 NAF-Id + +The NAF-Id AVP (AVP code 402) is of type OctetString. This AVP contains the full qualified domain name (FQDN) of the NAF that the UE uses concatenated with the Ua security protocol identifier as specified in 3GPP TS 33.220 [5]. The FQDN of the NAF that is part of the NAF\_Id may be a different domain name that with which the BSF knows the NAF. + +#### 6.3.1.4 GAA-Service-Identifier AVP + +The GAA-Service-identifier AVP (AVP code 403) is of type OctetString. This AVP informs a BSF about the support of a GAA-service by the NAF. According this AVP the BSF can select the right service's user security settings. + +For 3GPP standardized services (e.g., PKI portal), the GAA-Service-Identifier (GSID) shall be in the range 0 to 999999, and the currently standardized values for GSID shall be the GAA Service Type Code of the particular service. The GAA Service Type Codes for 3GPP standardized services are defined in Annex B. + +NOTE: In the future, standardized GSID values that are different than the GAA Service Type Code may be standardised (e.g. to differentiate between the services "MBMS streaming" and "MBMS download") and then several different GSID can exist within one GAA Service Type Code. + +Examples: The GSID is "1" for all PKI-portals, and "4" for all MBMS services. + +#### 6.3.1.5 Key-ExpiryTime AVP + +The Key-ExpiryTime AVP (AVP code 404) is of type Time. This AVP informs the NAF about the expiry time of the key. + +#### 6.3.1.6 ME-Key-Material AVP + +The required ME-Key-Material AVP (AVP code 405) is of type OctetString. The NAF is sharing this key material (Ks\_NAF in the case of GBA\_ME or Ks\_ext\_NAF in the case of GBA\_U) with the Mobile Equipment (ME). + +#### 6.3.1.7 UICC-Key-Material AVP + +The conditional UICC-Key-Material AVP (AVP code 406) is of type OctetString. The NAF may share this key material (Ks\_int\_NAF in the case of GBA\_U) with a security element (e.g. USIM, ISIM, etc..) in the UICC. Only some GAA applications use this conditional AVP. + +#### 6.3.1.8 GBA\_U-Awareness-Indicator + +The conditional GBA\_U-Awareness-Indicator AVP (AVP code 407) is of type Enumerated. The following values are defined. + +NO (0) The sending node is not GBA\_U aware + +YES(1) The sending node is GBA\_U aware + +The default value is 0 i.e. absence of this AVP indicates that the sending node is not GBA\_U aware. + +#### 6.3.1.9 BootstrapInfoCreationTime AVP + +The BootstrapInfoCreationTime AVP (AVP code 408) is of type Time. This AVP informs the NAF about the bootstrap information creation time of the key. + +#### 6.3.1.10 GUSS-Timestamp AVP + +The GUSS-Timestamp AVP (AVP code 409) is of type Time. If transmitted this AVP informs the HSS about the timestamp of the GUSS stored in the BSF. + +#### 6.3.1.11 GBA-Type + +The GBA-Type AVP (AVP code 410) is of type Enumerated. The AVP informs the NAF about the authentication type that was used during bootstrapping procedure. + +The following values are defined: + +- 3G GBA (0) The 3G GBA has been performed as defined in TS 33.220 [5]. +- 2G GBA (1) The 2G GBA has been performed as defined in TS 33.220 [5], Annex I. +- GBA Digest (2) The GBA Digest has been performed as defined in TS 33.220 [5], Annex M. + +The default value is 0 i.e. the absence of this AVP indicates 3G GBA. The value 2 is not applicable for Zpn. + +#### 6.3.1.12 UE-Id + +The UE-Id AVP (AVP code 411) is of type OctetString. The AVP informs the BSF the identity of the user. + +#### 6.3.1.13 UE-Id-Type + +The UE-Id-Type AVP (AVP code 412) is of type Enumerated. The AVP informs the BSF the type of the identity of the user. + +The following values are defined: + +- (0) Private user identity. +- (1) Public user identity. + +#### 6.3.1.14 UICC-App-Label + +The UICC-App-Label AVP (AVP code 413) is of type OctetString. The AVP informs the BSF the UICC application to be used for GBA push. + +#### 6.3.1.15 UICC-ME + +The UICC-ME AVP (AVP code 414) is of type Enumerated. The AVP informs the BSF whether GBA\_ME or GBA\_U is to be used for GBA push. + +The following values are defined: + +- GBA\_ME (0) GBA\_ME shall be run. +- GBA\_U (1) GBA\_U shall be run. + +#### 6.3.1.16 Requested-Key-Lifetime + +The Requested-Key-Lifetime AVP (AVP code 415) is of type Time. The AVP informs the BSF about the requested lifetime for the NAF keys. + +#### 6.3.1.17 Private-Identity-Request + +The Private-Identity-Request AVP (AVP code 416) is of type Enumerated. The AVP informs the BSF if the NAF requests the private identity of the user. + +The following values are defined: + +- Private identity requested (0). +- Private identity not requested (1) + +#### 6.3.1.18 GBA-Push-Info + +The GBA-Push-Info AVP (AVP code 417) is of type OctetString. The AVP includes the GBA-Push-Info as defined in 3GPP TS 33.223 [23]. + +#### 6.3.1.19 NAF-SA-Identifier + +The NAF-SA-Identifier AVP (AVP code 418) is of type OctetString. The AVP contains the NAF-SA-Identifier (P-TID). See 3GPP TS 33.223 [23]. + +#### 6.3.1.20 Security-Feature-Request + +The Security-Feature-Request AVP (AVP code 419) is of type OctetString. The AVP contains one or several of the security features requested by the NAF. The values are defined in Annex A. + +#### 6.3.1.21 Security-Feature-Response + +The Security-Feature-Request AVP (AVP code 420) is of type OctetString. The AVP contains one or several of the security features identified by the HSS. This information is conveyed to the BSF using the "securityFeatures" element in the "bsfElement" of GUSS (cf. Annex A), and the securityFeatures received in the request. The values are defined in Annex A. + +## 6.4 User identity to HSS resolution + +The User identity to HSS resolution mechanism enables the BSF to find the identity of the HSS that holds the subscriber data for a given subscriber when multiple and separately addressable HSSs have been deployed by the network operator. The resolution mechanism is not required in networks that utilise a single HSS or when a BSF is configured to use pre-defined HSS. + +The resolution mechanism is equivalent to the mechanism defined for the Cx/Dx interface described in 3GPP TS 23.228 [12] and shall use a Subscription Locator Function (SLF) or a Diameter Proxy Agent. + +The BSF accesses the SLF via the Dz interface. The Dz interface shall be always used in conjunction with the Zh interface. The Dz interface is based on Diameter. The SLF functionality shall use the routing mechanism provided by an enhanced Diameter redirect agent, which is able to extract the Subscriber identity from the received requests. + +The SLF or the Diameter Proxy Agent shall be able to determine the HSS identity. + +To get the HSS identity the BSF shall send the Zh request normally destined to the HSS to a pre-configured Diameter identity. + +- If this Zh request is received by an SLF (acting as a Diameter redirect agent), the SLF shall determine the HSS identity and shall send to the BSF a notification of redirection towards the HSS identity, in response to the Zh request. Multiple HSS identities may be included in the response, as specified in IETF RFC 3588 [1]. In such a case, the BSF shall send the Zh Request to the first HSS identity in the ordered list received in the Zh Response from the SLF. If the BSF does not receive a successful response to the Zh Request, the BSF shall send a Zh Request to the next HSS identity in the ordered list. This procedure shall be repeated until a successful response from an HSS is received. +- If this Zh request is received by the Diameter Proxy Agent, the Diameter Proxy Agent shall determine the HSS identity and shall forward the Zh request directly to the HSS. The BSF shall determine the HSS identity from the response to the Zh request received from the HSS. + +After the user identity to HSS resolution, the BSF may store the HSS identity and, if stored, shall use it in further Zh requests associated to the same Subscriber. + +In networks where the use of the user identity to HSS resolution mechanism is required and the BSF is not configured to use predefined HSS, each BSF shall be configured with the address/name of the SLF or the Diameter Proxy Agent implementing this resolution mechanism. + +# --- 7 Use of namespaces + +This clause contains the namespaces that have either been created in this 3GPP specification, or in 3GPP specification 3GPP TS 29.229 [3] or the values assigned to existing namespaces managed by IANA. + +## 7.1 AVP codes + +This specification reserves the 3GPP vendor specific values 10415:400-499 and assigns values 10415:400-418 for the GAA from the 3GPP AVP Code namespace for 3GPP Diameter applications ([8]). The 3GPP vendor specific AVP code space is managed by 3GPP CT4. See section 6 for the assignment of the namespace in this specification. + +Besides the Diameter Base Protocol AVPs [1] this specification reuses the following AVPs from 3GPP TS 29.229 [3]: `Authentication-Session-State`, `User-Name`, `Public-User-Identity` and `SIP-Auth-Data-Item`. + +## 7.2 Experimental-Result-Code AVP values + +This specification reserves Experimental-Result-Code AVP values 10415:2401-2409 and 10415:5401-5409. See section 6.2. + +## 7.3 Command Code values + +Only Command-Codes 310 and 303 from 3GPP TS 29.229 [3] is used in this specification. + +This specification reuses only the Command-Code value, not the content of the original specification. The AVPs, that are defined required in TS 29.229 [3], but are not needed in Zh, Zn or Zpn interfaces, are removed and are therefore not required in Zh, Zn or Zpn interface messages. All new AVPs for GAA are defined optional although they may be mandatory in GAA viewpoint. + +This specification does not assign new command codes to the 3GPP TS 29.229 [3]. + +# Annex A (normative): GBA-UserSecSettings XML definition + +This annex contains the XML schema definition for an XML document carrying the GBA User Security Settings inside GBA-UserSecSettings AVP in Zh,Zn and Zpn interface. + +``` + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +``` + +``` + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +``` + +NOTE 1: The elements within the complex types ExtensionType allow for compatible standard extensions in future releases. The elements within the other complex types allow for compatible private extensions. + +The values are: + +- The value of the attribute "id" in the element "guss" is the same as user's IM Private Identity (IMPI) used in User-Name AVP. + +- The value of the element "timestamp" in the element "guss" is the same type as GUSS-Timestamp used in GUSS-Timestamp AVP and indicates the timestamp of the GUSS. Timestamp value shall be expressed in UTC form, indicated by a time zone designator "Z" immediately following the time portion of the value. +- The value of the attribute "id" in the element "uss" is the same as service identifier (GSID) used in GAA-Service-Identifier AVP. + +NOTE 2: In the case with currently standardized 3GPP applications (c. f. Annex B), the service identifier (GSID) is the same as the GAA Service Type Code i.e. the "id" and the "type" attribute would have the same value. For example, in the interoperator GAA where the requesting BM-SC (i.e. NAF) is different operator network than the answering BSF, the BM-SC (NAF) can request particular user's MBMS USS by using "4" for the GSID in the "id" attribute in the USS. If the BSF operator wishes to have different MBMS USSs for different BM-SCs (NAFs), it can use the nafGroup attribute to separate NAFs to specific groups, and each group would get a particular USSs: would be given to NAFs in group A, and would be given to NAFs in group B when they request it. NAF groups are operator specific, i.e., operator decides which USS is given to which NAF." + +- The value of the element "uiccType" in the element "bsfInfo" is: +GBA to indicate the basic case, or +GBA\_U to indicate that generation of Ks\_int\_NAF is also required in the BSF. +The default value is GBA. +- The value of the element "lifeTime" in the element "bsfInfo" indicates a user specific key lifetime (duration in seconds). If the lifeTime element is missing the default value in the BSF is used. +- The value of the optional element "securityFeatures" in the element "bsfInfo" indicates a user specific security feature list that the UE supports. If the securityFeature element is missing then the security features are not defined. If there is a list of several values, they are separated by ";". Defined values are: + - "GPL\_U": The UICC supports Generic Push Layer on the UICC as specified in 3GPP TS 33.224 [30]. +- The value of attribute "type" in the element "uss" is GAA service type code defined in annex B. +- The value of attribute "nafGroup" in the element "uss" is an operator internal group designator for a NAF group the USS is valid for. If this attribute is missing then only the attribute "id" is used for selection of this element. +- Values of the element "uid" are user's public authentication identities from the HSS. +- Values of element "flag" are user's authorization flag codes from the HSS for GAA service type indicated in the type attribute in the parent uss element. If an authorization flag exist the NAF have permission to give the corresponding service, otherwise not +- The value of the element "keyChoice" in the "Extension" element inside the "uss" element is "ME-based-key", i.e., Ks\_NAF or Ks\_ext\_NAF shall be used, or "UICC-based-key", i.e., Ks\_int\_NAF shall be used or "ME-UICC-based-keys", i.e., Ks\_ext\_NAF or Ks\_int\_NAF can be used. The value of this element indicates to the NAF, which key shall be used. If the keyChoice element is missing, then as a default the "ME-based-key" shall be used by the NAF unless a prior agreement exists that mandates to use "UICC-based-key" or "ME-UICC-based-keys". + +In the following illustrative examples the values are *italised and underlined*. The content of one User Security Setting tag is boxed. + +``` + + + 86400 + + + + + tel:358504836551 + lauri.laitinen@example.com + ... + + + + +``` + +``` + + + + 1 + ... + + + ME-based-key + + + +``` + +``` + + ... + + + +``` + +The above GAA User Security Settings example for user "358500004836551@ ims.mnc050.mcc358.3gppnetwork.org" defines that for PKI-Portal (GAA service type code is 1) services are allowed for user identities "tel:358504836551" and "lauri.laitinen@example.com" and authentication is allowed (flag 1 exists) but non-repudiation is not allowed (flag 2 is missing) to NAFs that provide the GAA service identified by "1" GAA Service Identifier. This particular USS for PKI-Portal is intended to be used only with a NAF group that is labeled as "A" (NAF groupings and NAFs that belong to these groups are specified by the MNO). Additionally, the key choice for the PKI-Portal should use only ME based key (as key keyChoice is set to "ME-based-key"). The BSF shall not generate UICC-Ks, because uiccType is missing. A special key lifetime defines that the duration after which the key expires is 86400 seconds. + +``` + + + + + + tel:358504836551 + lauri.laitinen@example.com + + + 1 + + + ME-based-key + + + +]]> + +``` + +The above is an example how the value of "GAA-UserSecSettings" in Diameter based Zn reference point and "ussList" in Web Services based Zn reference point is populated. + +NOTE 3: The BSF has removed the "nafGroup" attribute from "uss" element. Also, the XML document has been surrounded by "" tags, so that the XML parser handling the outer message (i.e., in Web Services case) will not parse the ussList. The ussList will be parsed by the application itself handling the incoming message. + +Below is an example illustrating the usage of the flag for service authorization. The content of one User Security Setting tag is boxed. + +``` + + + + 86400 + + + +``` + +``` + + + + tel:358501234567 + pekka.mustermann@example.com + ... + + +``` + +``` + + + + + +``` + +``` + + 1 + ... + + + ME-based-key + ... + + +... + + +``` + +The above GAA User Security Settings example for user "358501234567@ims.mnc050.mcc358.3gppnetwork.org" defines that for ANDSF (GAA service type code is 8) services are allowed for user identities "tel:358501234567" and "pekka.mustermann@example.com" and authentication is allowed (flag 1 exists) i.e. the user is authorized to use the ANDSF service according to the policy stored in the ANDSF server. If the flag contains a 0 or is missing, the stated user identities would not be authorized to use the GAA service identified by "8" GAA Service Identifier. Additionally, the key choice for the ANDSF should use only ME based key (as key keyChoice is set to "ME-based-key"). + +Analogously, the authorization flag is used for OpenID GBA Interworking (GAA Service Type Code 11) the authentication is allowed (flag 1 exists) i.e. the user is authorized to use the OpenID-GBA Interworking service. If the flag contains a 0 or is missing, the stated user identities would not be authorized to use the GAA service identified by "11" GAA Service Identifier. Additionally, the key choice for the OpenID/GBA Interworking should use only ME based key if the keyChoice extension is set to "ME-based-key". + +# --- Annex B (normative): GAA Service Type Codes + +The GAA Service Type Code values are used in GAA to indicate interpretation, coding and usage of GAA service type specific data. + +For examples each GAA service type may have their own set of authorization flags. Meaning and coding of these flags are defined in Annex C. There may also be proprietary GAA service types with their own definitions in the future. + +Code values 0 – 999999 are reserved for standardized GAA service types. + +The following values are defined for standardized GAA service types with 3GPP specification: + +- 0 Unspecific service +- 1 PKI-Portal +- 2 Authentication Proxy +- 3 Presence +- 4 MBMS +- 5 Liberty Alliance Project (see [15]) +- 6 UICC - Terminal Key Establishment (see [17]) +- 7 Terminal – Remote Device Key Establishment (see [18]) +- 8 ANDSF (see [24]) +- 9. GBA Push (see [25]) +- 10 IMS based PSS MBMS (see [26]) +- 11 OpenID GBA Interworking (see [29]) +- 12 Generic Push Layer (see [30]) + +Default value is 0. An unspecific service may or may not have user security settings containing or not a list of public identities. An unspecific service cannot have specified authorization flags or other service type specific data. + +# --- Annex C (normative): GAA Authorization flag codes + +For GAA services which have a defined set of special authorization flag codes the following rule holds: The service specified by the GAA authorization flag codes is allowed for a user only if user's user security setting contains that flag. + +The following standardised GAA service types that are listed in previous annex B have the following special authorization flag codes: + +## **PKI-Portal (1)** + +- 1 Authentication allowed +- 2 Non-repudiation allowed + +## **ANDSF (8)** + +- 0 Not authorized +- 1 Authorized according to policy stored in ANDSF server + +## **OpenID Interworking (13)** + +- 0 Not authorized +- 1 Authorized + +# --- Annex D (normative): Web Services Defintion for Zn interface + +This annex contains the Web Services Defination Language (WSDL) [14] for Zn interface: + +``` + +``` + +``` + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +``` + +``` + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +``` + +# Annex E (informative): Liberty authentication context definitions for GBA + +## E.1 Introduction + +This clause describes the GBA Authentication Context definition that the Liberty Identity Provider uses to describe GBA parameters to Liberty Service Provider. The Liberty 3GPP Security Interworking is further discussed in 3GPP TR 33.980 [15]. + +## E.2 GBA Authentication context statement data model + +A particular Liberty authentication context statement will capture the characteristics of the process, procedures, and mechanisms by which the authentication authority verified the subject before issuing an identity, protects the secrets on which subsequent authentications are based, and the mechanisms used for this authentication. These characteristics are categorized in the Liberty ID-FF Authentication Context Specification [16] as follows: + +- Identification - Characteristics that describe the processes and mechanism the authentication authority uses to initially create an association between a subject and the identity (or name) by which the subject will be known. +- Technical Protection - Characteristics that describe how the "secret" (the knowledge or possession of which allows the subject to authenticate to the authentication authority) is kept secure. +- Operational Protection - Characteristics that describe procedural security controls employed by the authentication authority (for example, security audits, records archival). +- Authentication Method - Characteristics that define the mechanisms by which the subject of the issued assertion authenticates to the authentication authority (for example, a password versus a smartcard). +- Governing Agreements - Characteristics that describe the legal framework (e.g. liability constraints and contractual obligations) underlying the authentication event and/or its associated technical authentication infrastructure. + +Compared to Liberty Authentication Context [16], the GBA Authentication Context statement data model adds a description to to which GBA mechanism was used during bootstrapping with the BSF, and how the corresponding shared secret was used with the Identity Provider (IdP) that functions as a NAF. + +The authentication contexts classes specific to mobile terminals specified by Liberty Alliance are called + +- MobileOneFactorUnregistered, +- MobileTwoFactorUnregistered, +- MobileOneFactorContract, and +- MobileTwoFactorContract classes. + +The GBA authentication context uses some of the elements in these classes and introduces a new element called "GBAMechanism", which can be used to describe GBA specific parameters of the authentication. The elements used in the GBA Authentication Context schemas are: + +- GBAMechanismType: describes the GBA bootstrapping mechanism (identifies the method used over Ub reference point); +- AuthenticatorTransportProtocolType: describes the authentication mechanism that was used authenticate the UE towards the Liberty Identity Provider (identifies the method used over Ua reference point); +- KeyActivationType: describes the mechanism to achieve two factor authentication (valid in \*TwoFactor\* authentication schemas). + +## E.3 GBA authentication context statement schema + +This section lists the complete GBA Authentication Context XML schema. It is based on Liberty Authentication Context XML Schema to which the addition is the additional description of how GBA procedures have been conducted, i.e., GBAMechanism element. + +``` + + + + + + + + + + This authentication context has been defined for the + 3GPP and 3GPP2 Generic Bootstrapping Architecture. It + defines new GBAMechanismType and its values, but reuses + the Liberty authentication context schema for other + values. The GBA authentication context is based on the + MobileOneFactor* and MobileTwoFactor* authentication + contexts with the exception that only shared secret + based authentication methods (i.e., symmetric) are used, + and private key (i.e., asymmetric) methods are not + used when authenticating the UE due to the nature of GBA. + + + + + + + + Legacy GBA where existing old authentication + frameworks are used for bootstrapping such + 2G GBA in 3GPP, and CDMA 1x and CDMA 1xEVDO + in 3GPP2. + + + + + + + + GBA using AKA as specified in 3GPP and 3GPP2. + The shared secret is derived in the mobile and + used in the mobile. + + + + +``` + +``` + + + + + + + + GBA_U using AKA as specified in 3GPP and 3GPP2. + The shared secret is derived in the UICC and used + in the mobile. + + + + + + + + GBA_U using AKA as specified in 3GPP and 3GPP2. + The shared secret is derived in the UICC and used + in the UICC. + + + + + + + + GBA mechanism used in the bootstrapping procedure. + + + + + + + + + + + + + + + +``` + +## E.4 GBA authentication context classes + +### E.4.1 GBAOneFactorUnregistered + +This class reflects that there were no mobile customer registration procedures and an authentication of the UE is done without requiring explicit end-user interaction. + +#### E.4.1.1 Associated 3GPP URI + + + +#### E.4.1.2 Class schema + +``` + + + + + + + + + + + +``` + +``` + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +``` + +### E.4.2 GBATwoFactorUnregistered + +This class reflects that there were no mobile customer registration procedures and a two-factor based authentication of the UE is done requiring an explicit end-user interaction during authentication procedure (e.g., a PIN needs to be typed). + +#### E.4.2.1 Associated 3GPP URI + + + +#### E.4.2.2 Class schema + +``` + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +``` + +``` + + + + + + + + + + + + + + + + + + + + + + + + +``` + +### E.4.3 GBAOneFactorContract + +This class reflects that mobile customer registration procedures have taken place and an authentication of the UE is done without requiring explicit end-user interaction. + +#### E.4.3.1 Associated 3GPP URI + + + +#### E.4.3.2 Class schema + +``` + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +``` + +``` + + + + + + + + + + + + + + + + + + + +``` + +### E.4.4 GBATwoFactorContract + +This class reflects that mobile customer registration procedures have taken place and a two-factor based authentication of the UE is done requiring an explicit end-user interaction during authentication procedure (e.g., a PIN needs to be typed). + +#### E.4.4.1 Associated 3GPP URI + + + +#### E.4.4.2 Class schema + +``` + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +``` + +``` + + + + + + + + + + + + + + + + + + + + + + + + + + +``` + +# Annex F (informative): SAML authentication context definitions for GBA + +## F.1 Introduction + +This clause describes the GBA Authentication Context definition that an Identity Provider (IdP) uses to describe GBA parameters to a Service Provider (SP). SAML authentication contexts are further discussed in the SAML Authentication Context specification [19]. + +## F.2 GBA authentication context declaration data model + +Similarly to Liberty (cf. Annex E), a SAML authentication context declaration captures characteristics of the processes, procedures, and mechanisms by which the authentication authority verified the subject before issuing an identity, protects the secrets on which subsequent authentications are based, and the mechanisms used for this authentication (identification, technical protection, operational protection, authentication method and governing agreements) OASIS Standard [22]. + +Compared to the SAML authentication context declaration data model OASIS Standard [22], the GBA authentication context declaration data model extends the SAML model by adding a description of which GBA mechanism was used during bootstrapping with the BSF, and at the same time restricts the SAML model in a number of respects specific to GBA (only shared secret as authenticator type, only HTTP or SSL as authenticator transport protocol, secret key activation by PIN, only mobile device or smartcard as key storage medium). + +The authentication contexts classes specific to mobile terminals specified by SAML are: + +- MobileOneFactorUnregistered, +- MobileTwoFactorUnregistered, +- MobileOneFactorContract, and +- MobileTwoFactorContract. + +The GBA authentication context classes introduced herein correspond to the above ones and are: + +- GBAOneFactorUnregistered, +- GBATwoFactorUnregistered, + +- GBAOneFactorContract, and +- GBATwoFactorContract. + +The GBA authentication context classes are derived from the corresponding SAML authentication context classes by means of the following patterns: + +- The GBA mechanism (corresponding to ME-based GBA, UICC-based GBA, 2G GBA, etc.) is added to the authentication method type for all the four classes. +- A set of GBA-specific restrictions (only shared secret as authenticator type, only HTTP or SSL as authenticator transport protocol, only mobile device or smartcard as key storage medium) is applied to all the four classes. +- For the “OneFactor” classes (GBAOneFactorUnregistered and GBAOneFactorContract), there is no more difference (compared to the corresponding SAML class) in addition to the two changes described above. +- For the “TwoFactor” classes (GBATwoFactorUnregistered and GBATwoFactorContract), the key activation by means of PIN is mandatory in secret key protection. + +Given the above patterns, the rest of this annex is expected to be understood without further detailed explanations. + +## F.3 GBA authentication context declaration types + +This section lists the type definitions common to all the four GBA authentication context declaration classes. It adds the GBA mechanism elements (and the necessary type definitions) to the SAML types. + +``` + + + + + These types are intended to be used in the definition of + the authentication context classes in 3GPP and 3GPP2 Generic + Bootstrapping Architecture (GBA). The new authentication + context classes are defined separately. + + + + + + + + + GBA mechanism used in the bootstrapping procedure. + + + + + + + Legacy GBA where existing old authentication + frameworks are used for bootstrapping such + 2G GBA in 3GPP, and CDMA 1x and CDMA 1xEvDo + in 3GPP2. + + + + + + + GBA using AKA as specified in 3GPP and 3GPP2. + The shared secret is derived in the mobile and + used in the mobile. + + + + + + + GBA_U using AKA as specified in 3GPP and 3GPP2. + The shared secret is derived in the UICC and used + in the mobile. + + + + +``` + +``` + + + + + + + + GBA_U using AKA as specified in 3GPP and 3GPP2. + The shared secret is derived in the UICC and used + in the UICC. + + + + + + + + + + + + + + + +``` + +## F.4 GBA authentication context declaration classes + +### F.4.1 GBAOneFactorUnregistered + +This class reflects that there were no mobile customer registration procedures and an authentication of the UE is done without requiring explicit end-user interaction. + +#### F.4.1.1 Associated 3GPP URI + +urn:3gpp:gba:ac:saml:2007-08:classes:GBAOneFactorUnregistered + +#### F.4.1.2 Class schema + +``` + + + + + + + The GBA authentication context class comparable to + the SAML MobileOneFactorUnregistered class. + Id: 3gpp-gba-saml-authn-context-gbaonefactor-unreg-1.0.xsd + + + + + + + + + + + + + + + + + + + + + + +``` + +``` + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +``` + +``` + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +``` + +### F.4.2 GBATwoFactorUnregistered + +This class reflects that there were no mobile customer registration procedures and a two-factor based authentication of the UE is done requiring an explicit end-user interaction during authentication procedure (e.g., a PIN needs to be typed). + +#### F.4.2.1 Associated 3GPP URI + +urn:3gpp:gba:ac:saml:2007-08:classes:GBATwoFactorUnregistered + +#### F.4.2.2 Class schema + +``` + + + + + + + The GBA authentication context class comparable to + the SAML MobileTwoFactorUnregistered class. + Id: 3gpp-gba-saml-authn-context-gbatwofactor-unreg-1.0.xsd + + + + + + + +``` + +``` + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +``` + +``` + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +``` + +### F.4.3 GBAOneFactorContract + +This class reflects that mobile customer registration procedures have taken place and an authentication of the UE is done without requiring explicit end-user interaction. + +#### F.4.3.1 Associated 3GPP URI + +urn:3gpp:gba:ac:saml:2007-08:classes:GBAOneFactorContract + +#### F.4.3.2 Class schema + +``` + + + + + + The GBA authentication context class comparable to + the SAML MobileOneFactorContract class. + Id: 3gpp-gba-saml-authn-context-gbaonefactor-reg-1.0.xsd + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +``` + +``` + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +``` + +``` + + + + + + + + + +``` + +### F.4.4 GBATwoFactorContract + +This class reflects that mobile customer registration procedures have taken place and a two-factor based authentication of the UE is done requiring an explicit end-user interaction during authentication procedure (e.g., a PIN needs to be typed). + +#### F.4.4.1 Associated 3GPP URI + +urn:3gpp:gba:ac:saml:2007-08:classes:GBATwoFactorContract + +#### F.4.4.2 Class schema + +``` + + + + + + + The GBA authentication context class comparable to + the SAML MobileTwoFactorContract class. + Id: 3gpp-gba-saml-authn-context-mobiletwofactor-reg-1.0.xsd + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +``` + +``` + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +``` + +``` + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +``` + +# Annex G (normative): Web Services Definition for Zpn interface + +This annex contains the Web Services Definition Language (WSDL) [14] for Zpn interface: + +``` + + + + + + + + + + + + + + + + + + + + + + + + + + + +``` + +``` + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +``` + +``` + + + + + + + + +``` + +# Annex H (informative): Change history + +| Change history | | | | | | | | +|----------------|-------|-----------|------|-------------|-------------------------------------------------------------------------------|--------|--------| +| Date | TSG # | TSG Doc. | CR | R
e
v | Subject/Comment | Old | New | +| 2004-09 | CN#25 | NP-040410 | | | Version 2.0.0 approved in CN#25 | 2.0.0 | 6.0.0 | +| 2004-12 | CN#26 | NP-040580 | 001 | | Authorization Flag Code Annex | 6.0.0 | 6.1.0 | +| 2004-12 | | | 002 | | Finalization of GAA Service Identifier | | | +| 2004-12 | | | 003 | 1 | BSF control information (bsfInfo) tag to GUSS | | | +| 2004-12 | | | 005 | | Structure to GAA Service Identifier | | | +| 2004-12 | | | 006 | 1 | Finalisation of terminology | | | +| 2004-12 | | | 008 | 1 | Command code 310 Zn messages | | | +| 2004-12 | | | 009 | | Introduction of NAF groups | | | +| 2005-01 | | | | | Fix Word problem | 6.1.0 | 6.1.1 | +| 2005-03 | CN#27 | NP-050041 | 010 | | GAA Error Codes | 6.1.1 | 6.2.0 | +| | | | 011 | | Only one AV from HSS to BSF | | | +| | | | 012 | | Clarification of LifeTime/ExpiryTime terminology | | | +| | | | 013 | 1 | Application identifiers to Z-interfaces | | | +| | | | 014 | 1 | Modification of key lifetime material | | | +| 2005-06 | CT#28 | CP-050090 | 0015 | | XML extensibility | 6.2.0 | 6.3.0 | +| | | | 0016 | 1 | Remove BSF from visited network | | | +| 2005-09 | CT#29 | CP-050300 | 0017 | 1 | Correction for GBA with multiple HSS's | 6.3.0 | 6.4.0 | +| | | | 0021 | | Key naming alignment with TS 33.220 | | | +| 2005-09 | CT#29 | CP-050317 | 0019 | 1 | Key indication in USS | 6.4.0 | 7.0.0 | +| | | | 0020 | 2 | Addition of GUSS timestamp to Zh reference point | | | +| 2005-12 | CT#30 | CP-050613 | 0019 | 1 | XML syntax correction | 7.0.0 | 7.1.0 | +| | | CP-050624 | 0022 | 1 | 2G GBA implementation to Zh and Zn | | | +| 2006-03 | CT#31 | CP-060071 | 0025 | 1 | Correction of NAF ID | 7.1.0 | 7.2.0 | +| | | | 0026 | 1 | HTTP based Zn interface | | | +| | | | 0027 | 1 | Liberty authentication context for GAA | | | +| 2006-06 | CT#32 | CP-060318 | 0028 | 1 | Optionality of the HTTP based Zn interface for NAF | 7.2.0 | 7.3.0 | +| | | | 0029 | 1 | Replacement of "GAA-Application-Type-Code" with "GAA Service Type Code" | | | +| 2006-09 | CT#33 | CP-060415 | 0030 | 1 | Inconsistent description about the proxy between BSF and visited NAF | 7.3.0 | 7.4.0 | +| | | | 0031 | | Only one instance of SIP-Auth-Data-Item sent in MAA | | | +| 2006-12 | CT#34 | CP-060567 | 0032 | 1 | Zh MAR/MAA Diameter Application identifier | 7.4.0 | 7.5.0 | +| | | | 0033 | | Definition of GAA Service Type Code for Liberty Alliance Interworking | | | +| | | | 0034 | | Corrections to GAA authentication context schema | | | +| | | | 0035 | | WSDL definition enhancements for Zn interface | | | +| 2007-06 | CT#36 | CP-070320 | 0037 | 1 | Addition of Service Type For Rel-7 | 7.5.0 | 7.6.0 | +| | | CP-070320 | 0038 | 1 | Bug fixes on Zn WSDL definition | | | +| | | CP-070317 | 0040 | | GUSS schema fix | | | +| 2007-09 | CT#37 | CP-070528 | 0036 | 4 | HLR support for BSF | 7.6.0 | 7.7.0 | +| | | | 0041 | 1 | Addition of SAML authentication context declaration classes | | | +| 2007-12 | CT#38 | CP-070741 | 0042 | 1 | GUSS and USS handling corrections | 7.7.0 | 7.8.0 | +| 2008-03 | CT#39 | CP-080013 | 0045 | | GBA-UserSecSettings XML fix | 7.8.0 | 7.9.0 | +| 2008-06 | CT#40 | CP-080275 | 0047 | 2 | Key choice correction | 7.9.0 | 7.10.0 | +| 2008-12 | CT#42 | | | | Upgraded unchanged from Rel-7 | 7.10.0 | 8.0.0 | +| 2008-03 | CT#43 | CP-090033 | 0048 | | Introduction of GBA Push within TS 29.109 – Scope, References and Definitions | 8.0.0 | 8.1.0 | +| | | | 0049 | 2 | Introduction of GBA Push within TS 29.109 – Zpn Interface | | | +| | | | 0050 | 1 | Introduction of GBA Push within TS 29.109 – Impacts on Zh Interface | | | +| | | | 0051 | 3 | User identity to HSS Resolution mechanism using a Diameter Proxy | | | + +| | | | | | | | | +|---------|-------|-----------|------|---|---------------------------------------------------------------------------------------|--------|--------| +| | | | 0055 | 1 | Renaming of the reference point between BSF and HLR | | | +| 2009-06 | CT#44 | CP-090486 | 0056 | 2 | ANDSF Service Authorization | 8.1.0 | 8.2.0 | +| 2009-09 | CT#45 | CP-090554 | 0057 | 1 | Additional GBA Service Codes | 8.2.0 | 8.3.0 | +| | | | 0059 | 2 | MSISDN support in GBA | | | +| 2009-09 | CT#45 | CP-090555 | 0058 | 1 | GBA Service Type Codes and Authorziation Flag | 8.3.0 | 9.0.0 | +| 2009-12 | CT#46 | CP-091031 | 0068 | 2 | 2G GBA Option not supported in HSS | 9.0.0 | 9.1.0 | +| | | CP-091031 | 0069 | 2 | Synchronization Failure Recovery over Zh | | | +| | | CP-091031 | 0070 | 2 | Zh and Zn Unable to Comply | | | +| | | CP-090782 | 0071 | 1 | Zh identity unknown | | | +| | | CP-090782 | 0072 | 2 | Only User-Name or Public-Identity AVP shall be present in a MAR request | | | +| 2010-03 | CT#47 | CP-100036 | 0073 | 2 | GPL_U support in TS 29.109 | 9.1.0 | 9.2.0 | +| | | | 0074 | | Correction to WSDL schema of Zn/Zpn reference point | | | +| 2011-03 | - | - | - | - | Update to Rel-10 version (MCC) | 9.2.0 | 10.0.0 | +| 2012-03 | CT#55 | CP-120043 | 0077 | 2 | SIP Digest over Zh | 10.0.0 | 11.0.0 | +| 2012-06 | CT#56 | CP-120225 | 0078 | 1 | GBA Digest over Zn | 11.0.0 | 11.1.0 | +| 2012-12 | CT#58 | CP-120712 | 0083 | - | Introduction of GBA Push within TS 29.109 – Zpn Interface | 11.1.0 | 11.2.0 | +| | | CP-120752 | 0079 | 1 | USS example | | | +| 2013-01 | | | | | Annex numbering corrected | 11.2.0 | 11.2.1 | +| 2013-03 | CT#59 | CP-130011 | 0084 | 1 | Error codes in Zn and Zpn | 11.2.1 | 11.3.0 | +| 2013-12 | CT#62 | CP-130601 | 0092 | 1 | Lack of element definitions and wrong references for Zn and Zpn based on Web Services | 11.3.0 | 11.4.0 | +| 2014-03 | CT#63 | CP-140015 | 0096 | 1 | userIdType and uiccOrMe in requestGbaPushInfoRequest message | 11.4.0 | 11.5.0 | +| 2015-03 | CT#67 | CP-150017 | 0097 | 1 | Authentication scheme Digest-AKAv1-MD5 in MAR | 11.5.0 | 11.6.0 | +| 2015-06 | CT#68 | CP-150244 | 0103 | 1 | Auth-Session-State in BIR/BIA | 11.6.0 | 11.7.0 | \ No newline at end of file diff --git a/marked/Rel-11/29_series/29119/47e8c2042061e08a14e012472e9fdbaa_img.jpg b/marked/Rel-11/29_series/29119/47e8c2042061e08a14e012472e9fdbaa_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bc783b25113d3ab38b0c7cdbe94bcdd08cf862d4 --- /dev/null +++ b/marked/Rel-11/29_series/29119/47e8c2042061e08a14e012472e9fdbaa_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:492b70eeb32c679e1e255391a3e7339c2c8c37c7c448f547ce44e251aea19a16 +size 49790 diff --git a/marked/Rel-11/29_series/29119/e1a0d046fbe7f28f5e93a47091851747_img.jpg b/marked/Rel-11/29_series/29119/e1a0d046fbe7f28f5e93a47091851747_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2a676c3be84c279e591dfc0f5dd11f9b5eefc2d3 --- /dev/null +++ b/marked/Rel-11/29_series/29119/e1a0d046fbe7f28f5e93a47091851747_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bd52192e2533189edc1569ccf9de7db5ddc11207f3a82d9a783e382d32b0142b +size 42293 diff --git a/marked/Rel-11/29_series/29119/raw.md b/marked/Rel-11/29_series/29119/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..933606f8c5c62e461ac0cfc12abf2ea0c86ba9fe --- /dev/null +++ b/marked/Rel-11/29_series/29119/raw.md @@ -0,0 +1,307 @@ + + + + + + +# Contents + +Foreword .....4 + +1 Scope.....5 + +1.1 References .....5 + +2 Definitions and abbreviations .....5 + +2.1 Definitions.....5 + +2.2 Abbreviations .....6 + +3 General.....6 + +4 Transmission order and bit definitions.....7 + +5 GTP header .....7 + +6 GTP Message and Message Formats .....7 + +6.1 Signalling Message Formats .....7 + +6.2 Path Management messages.....8 + +6.3 Tunnel Management messages.....8 + +6.4 Location Management message .....9 + +6.5 Mobility Management messages.....9 + +6.6 Reliable delivery of signalling messages .....9 + +6.7 Information element .....10 + +7 Signalling Plane (GTP-C) .....10 + +8 GTP-U .....10 + +9 Path Protocol .....10 + +10 Error handling .....10 + +11 Inter-PLMN GTP communication over the Gp Interface .....10 + +12 IP, the networking technology used by GTP .....10 + +13 GTP parameters.....10 + +Annex A (informative): Change history.....11 + +# --- Foreword + +The present document 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 signalling requirements and procedures used at network elements related to the GLR for GTP within the 3GPP system at the application level. + +The present document gives the description of the systems needed only in the network utilising GLR as the delta document against 3GPP TS 29.060. + +## 1.1 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. + - For a specific reference, subsequent revisions do not apply. + - For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. +- [1] 3GPP TS 23.060: "General Packet Radio Service (GPRS); Service description Stage2". +- [2] 3GPP TS 23.119: "Gateway Location Register (GLR) – stage2". +- [3] 3GPP TS 24.008: "Mobile radio interface layer 3 specification, Core Network Protocols – Stage 3". +- [4] 3GPP TS 29.002: "Mobile Application Part (MAP) specification". +- [5] 3GPP TS 29.060: "General Packet Radio Service (GPRS); GPRS Tunnelling Protocol (GTP) across the Gn and Gp Interface". + +# 2 Definitions and abbreviations + +## 2.1 Definitions + +For the purposes of the present document, the following terms and definitions apply. + +**Gateway Location Register:** this entity handles location management of roaming subscriber in visited network without involving HLR + +**Intermediate GSN:** this entity is used as serving GSN towards home network and relay some PDU notification messages between serving GSN and Gateway GSN + +**MM context:** information sets held in MS and GSNs for a GPRS subscriber related to mobility management (MM) + +**MM Context ID:** IMSI or equivalent for use in conjunction with Anonymous Access (please refer to section GTP Header) + +**Path:** UDP/IP path and TCP/IP path are examples of paths that may be used to multiplex GTP tunnels + +**Path Protocol:** path Protocol is the protocol(s) used as a bearer of GTP between GSNs + +**PDP:** packet Data Protocol (PDP) is a network protocol used by an external packet data network interfacing to GPRS + +**PDP Context:** information sets held in MS and GSNs for a PDP address + +- Signalling message:** GTP signalling messages are exchanged between GSN pairs in a path. The signalling messages are used to transfer GSN capability information between GSN pairs and to create, update and delete GTP tunnels +- T-PDU:** original packet, for example an IP datagram, from an MS or a network node in an external packet data network. A T-PDU is the payload that is tunnelled in the GTP tunnel +- Tunnel Endpoint Identifier (TEID):** this field unambiguously identifies a tunnel endpoint in the receiving GTP-U or GTP-C protocol entity. The receiving end side of a GTP tunnel locally assigns the TEID value the transmitting side has to use. The TEID values are exchanged between tunnel endpoints using GTP-C messages + +## 2.2 Abbreviations + +For the purposes of the present document, the following abbreviations apply: + +| | | +|--------|------------------------------| +| GGSN | Gateway GPRS support node | +| GLR | Gateway Location Register | +| GPRS | General Packet Radio Service | +| GTP | GPRS Tunnelling Protocol | +| IM_GSN | Intermediate GSN | +| IP | Internet Protocol | +| GLR | Gateway Location Register | +| SGSN | Serving GPRS support node | +| TEID | Tunnel Endpoint Identifier | +| UDP | User Datagram Protocol | + +# 3 General + +The present document defines the GPRS Tunnelling Protocol (GTP) specific to the network with the GLR, i.e. the protocol between IM\_GSN and other nodes (i.e. GGSN, SGSN and GTP-MAP protocol converting GSN). It includes only the GTP signalling but not data transfer procedures. + +The interface between IM\_GSN and GGSN is either intra-PLMN interface or inter-PLMN interface. + +![Figure 1: Logical Architecture for PS domain in the network with GLR. The diagram shows a network architecture with GLR, HLR, GTP-MAP Protocol Converting GSN, IM_GSN, SGSN, and GGSN. Solid lines represent Signalling and Data Transfer Interfaces, while dotted lines represent Signalling Interfaces.](47e8c2042061e08a14e012472e9fdbaa_img.jpg) + +``` + +graph TD + GLR[GLR] -.-> HLR[HLR] + GLR -.-> GTPMAP1[GTP-MAP Protocol Converting GSN] + GLR -.-> IM_GSN[IM_GSN] + HLR -.-> GTPMAP2[GTP-MAP Protocol Converting GSN] + HLR -.-> GGSN[GGSN] + GTPMAP1 -.-> IM_GSN + GTPMAP2 -.-> GGSN + SGSN[SGSN] --- IM_GSN + SGSN --- GGSN + IM_GSN --- GGSN + +``` + +Legend: + +- ..... Signalling Interface +- \_\_\_\_\_ Signalling and Data Transfer Interface + +Figure 1: Logical Architecture for PS domain in the network with GLR. The diagram shows a network architecture with GLR, HLR, GTP-MAP Protocol Converting GSN, IM\_GSN, SGSN, and GGSN. Solid lines represent Signalling and Data Transfer Interfaces, while dotted lines represent Signalling Interfaces. + +Figure 1: Logical Architecture for PS domain in the network with GLR + +The GTP protocol is implemented only by IM\_GSNs, SGSNs and GGSNs. No other systems need to be aware of GTP. GPRS MSs are connected to a SGSN without being aware of GTP. + +It is assumed that there will be a many-to-many relationship between IM\_GSNs, SGSNs and GGSNs. An IM\_GSN may provide service to many GGSNs. A SGSN may provide service to many IM\_GSNs and GGSNs. + +# 4 Transmission order and bit definitions + +Transmission order and bit definitions on the interface between the IM\_GSN and other nodes in the network with GLR are the same as that used in the network without the GLR, see 3GPP TS 29.060. + +# 5 GTP header + +The GTP header used on interface between the IM\_GSN and other nodes in the network with GLR is the same as that used in the network without the GLR, see 3GPP TS 29.060. + +# 6 GTP Message and Message Formats + +The only signalling plane exists between the IM\_GSN and other nodes (i.e. GGSN, SGSN and GTP-MAP protocol converting GSN). + +## 6.1 Signalling Message Formats + +GTP defines a set of signalling messages between two associated GSNs. The signalling messages to be used between the IM\_GSN and other nodes are defined in the table below. For the GTP signalling messages to be used on other interfaces see 3GPP TS 29.060. + +**Table 1: Signalling messages** + +| Message Type value (Decimal) | Signalling message | Reference | +|------------------------------|---------------------------------------------|--------------------------| +| 3 | Version Not Supported | 7.4.3 in 3GPP TS 29.060 | +| 27 | PDU Notification Request | 7.5.12 in 3GPP TS 29.060 | +| 28 | PDU Notification Response | 7.5.13 in 3GPP TS 29.060 | +| 29 | PDU Notification Reject Request | 7.5.14 in 3GPP TS 29.060 | +| 30 | PDU Notification Reject Response | 7.5.15 in 3GPP TS 29.060 | +| 32 | Send Routeing Information for GPRS Request | 7.6.1 in 3GPP TS 29.060 | +| 33 | Send Routeing Information for GPRS Response | 7.6.2 in 3GPP TS 29.060 | +| 34 | Failure Report Request | 7.6.3 in 3GPP TS 29.060 | +| 35 | Failure Report Response | 7.6.4 in 3GPP TS 29.060 | + +## 6.2 Path Management messages + +The messages, which are listed in following table, are used on the interface between the IM\_GSN and other nodes. For the definitions of these messages and other messages used on the other interfaces refer to the corresponding sections in 3GPP TS 29.060. + +| Messages | Sending node | Receiving node | +|-----------------------|--------------|----------------| +| Version Not Supported | IM_GSN | GGSN, SGSN | +| | GGSN, SGSN | IM_GSN | + +## 6.3 Tunnel Management messages + +In following table, only the messages used between the IM\_GSN and GGSN and between the IM\_GSN and SGSN are listed. For the definitions of these messages and other messages used on the other interfaces refer to the corresponding sections in 3GPP TS 29.060. + +| Messages | Sending node | Receiving node | +|----------------------------------|--------------|----------------| +| PDU Notification Request | GGSN | IM_GSN | +| | IM_GSN | SGSN | +| PDU Notification Response | SGSN | IM_GSN | +| | IM_GSN | GGSN | +| PDU Notification Reject Request | SGSN | IM_GSN | +| | IM_GSN | GGSN | +| PDU Notification Reject Response | GGSN | IM_GSN | +| | IM_GSN | SGSN | + +## 6.4 Location Management message + +In the network with the GLR, The optional Location Management messages are defined to support the case when Network-Requested PDP Context Activation procedures are used and an IM\_GSN does not have a SS7 MAP interface. GTP is then used to transfer signalling messages between the IM\_GSN and a GTP-MAP protocol-converting GSN in the GPRS backbone network. The GTP-MAP protocol-converting GSN converts the signalling messages described in this section between GTP and MAP. The MAP messages are sent to and received from the GLR. The GTP-MAP protocol-converting function is described in 3GPP TS 23.060. The MAP protocol describing the corresponding procedures and messages is described in 3GPP TS 29.002. This alternative method is illustrated in Figure 2. + +![Diagram illustrating IM_GSN - GLR Signalling via a GTP-MAP protocol-converter in a GSN. The diagram shows three main entities: IM_GSN, GSN (with GTP-MAP Interworking), and GLR. The IM_GSN has a protocol stack of GTP, UDP, IP, L2, and L1. The GSN has two stacks: one for GTP (GTP, UDP, IP, L2, L1) and one for MAP (MAP, TCAP, SCCP, MTP3, MTP2, L1). The GLR has a protocol stack of MAP, TCAP, SCCP, MTP3, MTP2, and L1. Arrows show the flow of messages from IM_GSN through the GSN's GTP stack to its MAP stack, and then through the GLR's MAP stack.](e1a0d046fbe7f28f5e93a47091851747_img.jpg) + +The diagram illustrates the protocol stacks for IM\_GSN, GSN, and GLR. The IM\_GSN stack consists of GTP, UDP, IP, L2, and L1. The GSN is shown with two stacks: a GTP stack (GTP, UDP, IP, L2, L1) and a MAP stack (MAP, TCAP, SCCP, MTP3, MTP2, L1). The GLR stack consists of MAP, TCAP, SCCP, MTP3, MTP2, and L1. Arrows indicate the flow of signalling messages from the IM\_GSN, through the GSN's GTP stack, then through the GSN's MAP stack, and finally through the GLR's MAP stack. + +Diagram illustrating IM\_GSN - GLR Signalling via a GTP-MAP protocol-converter in a GSN. The diagram shows three main entities: IM\_GSN, GSN (with GTP-MAP Interworking), and GLR. The IM\_GSN has a protocol stack of GTP, UDP, IP, L2, and L1. The GSN has two stacks: one for GTP (GTP, UDP, IP, L2, L1) and one for MAP (MAP, TCAP, SCCP, MTP3, MTP2, L1). The GLR has a protocol stack of MAP, TCAP, SCCP, MTP3, MTP2, and L1. Arrows show the flow of messages from IM\_GSN through the GSN's GTP stack to its MAP stack, and then through the GLR's MAP stack. + +Figure 2: IM\_GSN - GLR Signalling via a GTP-MAP protocol-converter in a GSN + +In following table, only the messages used between the IM\_GSN and The GTP-MAP protocol-converting GSN are listed. For the definitions of these messages and other messages used on the other interfaces refer to the corresponding sections in 3GPP TS 29.060. + +| Messages | Sending node | Receiving node | +|---------------------------------------------|-----------------------------|-----------------------------| +| Send Routeing Information for GPRS Request | IM_GSN | GTP-MAP protocol-converting | +| Send Routeing Information for GPRS Response | GTP-MAP protocol-converting | IM_GSN | +| Failure Report Request | IM_GSN | GTP-MAP protocol-converting | +| Failure Report Response | GTP-MAP protocol-converting | IM_GSN | + +## 6.5 Mobility Management messages + +The messages belonging to the mobility management messages are not used on the interface between the IM\_GSN and other nodes in the network with the GLR. + +## 6.6 Reliable delivery of signalling messages + +For the Reliability mechanism in the IM\_GSN, see section 7.8 in 3GPP TS 29.060. + +## 6.7 Information element + +The format of information elements in the message used on the interface between the IM\_GSN and other nodes in the network with GLR is the same as that in the network without the GLR. See 3GPP TS 29.060. + +# --- 7 Signalling Plane (GTP-C) + +The definition of signalling plane used in the network with the GLR is the same as that used in the network without the GLR, see in 3GPP TS 29.060. + +# --- 8 GTP-U + +GTP-U is not used on the interface between the IM\_GSN and other nodes. For the definition of GTP-U on the other interfaces, see in 3GPP TS 29.060. + +# --- 9 Path Protocol + +The Path Protocol on the interface between the IM\_GSN and other nodes in the network with the GLR is the same as that used in the network without the GLR. See 3GPP TS 29.060. + +# --- 10 Error handling + +The error handling on the interface between the IM\_GSN and other nodes is the same as that in the network without the GLR. See 3GPP TS 29.060. One exception is that the IM\_GSN doesn't have a Restart Counter because the IM\_GSM stores no PDP and MM context and therefore the synchronisation of the status of these with other GSNs is not needed. + +# --- 11 Inter-PLMN GTP communication over the Gp Interface + +Refer to the corresponding section in 3GPP TS 29.060. + +# --- 12 IP, the networking technology used by GTP + +Refer to the corresponding section in 3GPP TS 29.060. + +# --- 13 GTP parameters + +The definitions and directions for use of the parameters in GTP (inc. timer values or counter values and so on) on the interface between the IM\_GSN and other nodes is the same as that used in the network without the GLR. See 3GPP TS 29.060. + +# Annex A (informative): Change history + +| Document history | | | +|-------------------------|-----------|---------------------------------------------------------------------------------------------------------------------| +| V0.0.1 | Oct 1999 | The GTP protocol part is separated from MAP protocol part, and new specification related to GTP issue is generated. | +| V0.1.0 | Nov 1999 | For approval by N2#8 | +| V1.0.0 | Dec 1999 | For information and approval by TSG CN#6. | +| V1.0.1 | Jan 2000 | Only editorial modifications including some alignment with 29.060 | +| V2.0.0 | Mar 2000 | Submitted for approval to TSG CN#07 | +| V3.0.0 | Mar 2000 | Approved by TSG CN#07 | +| V4.0.0 | Mar 2001 | Approved by TSG CN#11 | +| V5.0.0 | Jun 2002 | Rel-5 created after CN#16 | +| V6.0.0 | Dec 2004 | Rel-6 created after CN#26 | +| V7.0.0 | June 2007 | Upgraded unchanged from Rel-6 after CT#36 | +| V8.0.0 | Dec 2008 | Upgraded unchanged from Rel-7 after CT#42 | +| V9.0.0 | Dec 2009 | Update to Rel-9 version (MCC) | +| V10.0.0 | Mar 2011 | Update to Rel-10 version (MCC) | +| V11.0.0 | Sep 2012 | Update to Rel-11 version (MCC) | \ No newline at end of file diff --git a/marked/Rel-11/29_series/29120/00504fc688ebcf131ccbeff94dfc9939_img.jpg b/marked/Rel-11/29_series/29120/00504fc688ebcf131ccbeff94dfc9939_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..afc2fc127d40203fd923bbe4ac6b8cdab11a1fcf --- /dev/null +++ b/marked/Rel-11/29_series/29120/00504fc688ebcf131ccbeff94dfc9939_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:84e4aa3a3de690b23a23d7c79befa64e627aa3b9a5d677bc20e09fda39f24bc1 +size 130135 diff --git a/marked/Rel-11/29_series/29120/036c200da9b64c3eb5aae2d67bb53e1f_img.jpg b/marked/Rel-11/29_series/29120/036c200da9b64c3eb5aae2d67bb53e1f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4986e3b571a61d26e0dad2ce0b36cbd2f7419c7f --- /dev/null +++ b/marked/Rel-11/29_series/29120/036c200da9b64c3eb5aae2d67bb53e1f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cee50e7261be6f6d266e4400da91412508715a4449e59554afdc1c55608fdab7 +size 111845 diff --git a/marked/Rel-11/29_series/29120/05eb72d372e4bf78e3d6a64949d77bcc_img.jpg b/marked/Rel-11/29_series/29120/05eb72d372e4bf78e3d6a64949d77bcc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3027e6d88153b83ffe7847d325f6f1f921d7c57d --- /dev/null +++ b/marked/Rel-11/29_series/29120/05eb72d372e4bf78e3d6a64949d77bcc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:34baa9d10f52b97fa104d519801378bfea7fab8459f55d39da51a052eb561b91 +size 146654 diff --git a/marked/Rel-11/29_series/29120/0931f3e098bd4539041de11c50cec2d2_img.jpg b/marked/Rel-11/29_series/29120/0931f3e098bd4539041de11c50cec2d2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c4f79431ee2472bcafedd6bd7a62b2af0c1bfa6b --- /dev/null +++ b/marked/Rel-11/29_series/29120/0931f3e098bd4539041de11c50cec2d2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8d8fc6ce78e0838018b38987b873e31782061bc433a7be27f189bc38bbc95b70 +size 164897 diff --git a/marked/Rel-11/29_series/29120/0a73b03fba21af142d619a9a662e6490_img.jpg b/marked/Rel-11/29_series/29120/0a73b03fba21af142d619a9a662e6490_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..027329e2d20f5300844f66a5a0562e2f8016cf25 --- /dev/null +++ b/marked/Rel-11/29_series/29120/0a73b03fba21af142d619a9a662e6490_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:58f078ed0bb7771b2e9ecdff84e5eb1eeaa48e53e23fa0e005eb78ee41f8f3b4 +size 93354 diff --git a/marked/Rel-11/29_series/29120/0b998e3ad8f9d104768642612605cb35_img.jpg b/marked/Rel-11/29_series/29120/0b998e3ad8f9d104768642612605cb35_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..de93b665d923e780a1beb04b132bb775c9a01b46 --- /dev/null +++ b/marked/Rel-11/29_series/29120/0b998e3ad8f9d104768642612605cb35_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fb96e6e35a2cf08aff9d77a7281362ef7b5271d80636b2dad6f0ee5504e4a226 +size 130661 diff --git a/marked/Rel-11/29_series/29120/0f6e3cdce0f01d6ccceabcced508bb5b_img.jpg b/marked/Rel-11/29_series/29120/0f6e3cdce0f01d6ccceabcced508bb5b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..396081e892b5b6c4ec3b42b0a1575795f83b30d3 --- /dev/null +++ b/marked/Rel-11/29_series/29120/0f6e3cdce0f01d6ccceabcced508bb5b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a688b65fb3a2524d822dd98e78fa49627d19d7a144c955acab41f9737309f2c9 +size 117931 diff --git a/marked/Rel-11/29_series/29120/11f18bf0233d812ad2604f88f3385d60_img.jpg b/marked/Rel-11/29_series/29120/11f18bf0233d812ad2604f88f3385d60_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..414e913dec8cb19cc1a0e5725ad7b2e761a37bf2 --- /dev/null +++ b/marked/Rel-11/29_series/29120/11f18bf0233d812ad2604f88f3385d60_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a95df66e18800adfd4fbb74f37519bf3aefa407933bada69dadfb50918a68723 +size 125487 diff --git a/marked/Rel-11/29_series/29120/17431d8b59408f09df7552d8bdbaa015_img.jpg b/marked/Rel-11/29_series/29120/17431d8b59408f09df7552d8bdbaa015_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6bca86c7cd003a23c6b1e5722a33034dafc27e14 --- /dev/null +++ b/marked/Rel-11/29_series/29120/17431d8b59408f09df7552d8bdbaa015_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:18fdfab0bb2d715b1eef9a479e4f442b976a1738f87b6b5ce167cd45348ab239 +size 126089 diff --git a/marked/Rel-11/29_series/29120/18003425d0e8638dde4acc9c5c468c5c_img.jpg b/marked/Rel-11/29_series/29120/18003425d0e8638dde4acc9c5c468c5c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..64be219d4d75090b63a05098a8589768b2d2e86b --- /dev/null +++ b/marked/Rel-11/29_series/29120/18003425d0e8638dde4acc9c5c468c5c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f4dcea52cedf73dea7cef82e266b9de93e74e3a3682e2739007d8f673997caf4 +size 130088 diff --git a/marked/Rel-11/29_series/29120/18dbea0ac6b7ad13e47afda3ddd53b64_img.jpg b/marked/Rel-11/29_series/29120/18dbea0ac6b7ad13e47afda3ddd53b64_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fbe19ac1e62044d52eedb6e25f475197213c045b --- /dev/null +++ b/marked/Rel-11/29_series/29120/18dbea0ac6b7ad13e47afda3ddd53b64_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2020cfd5279fe3a7efd4cd3ed14ccd724368a4838123a6ccce1e371c0af47b8c +size 51377 diff --git a/marked/Rel-11/29_series/29120/1cac1845cf99a3f64ae00cd2bb4f9ed7_img.jpg b/marked/Rel-11/29_series/29120/1cac1845cf99a3f64ae00cd2bb4f9ed7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7b59e692a10d711a028d9c88808be1de5e06d0b4 --- /dev/null +++ b/marked/Rel-11/29_series/29120/1cac1845cf99a3f64ae00cd2bb4f9ed7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:dec77e3a5ec69f3161b83a803e66aed4babdc705715b67b7a73e1ae9516d1a52 +size 127979 diff --git a/marked/Rel-11/29_series/29120/1e5a58dcaf0936bf18dc3dd0d9cd43ff_img.jpg b/marked/Rel-11/29_series/29120/1e5a58dcaf0936bf18dc3dd0d9cd43ff_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4c9476050db5fe5476637dc9f2604fcd074d82cd --- /dev/null +++ b/marked/Rel-11/29_series/29120/1e5a58dcaf0936bf18dc3dd0d9cd43ff_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e68f6819ad731d9c7b7d994ed00871cc289776a2d3b9c8e6a5a8b3a55b9698bc +size 41673 diff --git a/marked/Rel-11/29_series/29120/223792b3652794024244c277cc46394b_img.jpg b/marked/Rel-11/29_series/29120/223792b3652794024244c277cc46394b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..59e12d25b3390de23475acc9e8e5fe4a2c13946c --- /dev/null +++ b/marked/Rel-11/29_series/29120/223792b3652794024244c277cc46394b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f41aba9f6a3cdd1749878a055a34a6825fdf028e5a51ac84e327b7e895704e32 +size 124688 diff --git a/marked/Rel-11/29_series/29120/245166735676c675f98f535bc4c6f0a1_img.jpg b/marked/Rel-11/29_series/29120/245166735676c675f98f535bc4c6f0a1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ff45a68d5ce3abe5a3ccab9f856946b1f5901d19 --- /dev/null +++ b/marked/Rel-11/29_series/29120/245166735676c675f98f535bc4c6f0a1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:32cbe9f0bc8ac54f40c724eb0b3cf1d21cb3dfc7cb0bea479d128191a38b5545 +size 157226 diff --git a/marked/Rel-11/29_series/29120/28d75f39a24203712ee907b32cf0bbe5_img.jpg b/marked/Rel-11/29_series/29120/28d75f39a24203712ee907b32cf0bbe5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d845c106c45fe5d5a7385fc088832be92aba681e --- /dev/null +++ b/marked/Rel-11/29_series/29120/28d75f39a24203712ee907b32cf0bbe5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6c6f1a599d6f959448442f7001008ea534ff4afb28ad5badb9639d7cfbcbab33 +size 109279 diff --git a/marked/Rel-11/29_series/29120/2a476a0b3dbc3429436246db4784ff9f_img.jpg b/marked/Rel-11/29_series/29120/2a476a0b3dbc3429436246db4784ff9f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a3db30080fcf2f0ce57feb6349159775363b5897 --- /dev/null +++ b/marked/Rel-11/29_series/29120/2a476a0b3dbc3429436246db4784ff9f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b2c351d9ff28f3e3e3090bf470d45586c8a162a41eef20de5205fab90adbe890 +size 162985 diff --git a/marked/Rel-11/29_series/29120/329c96049bb432e9c2cbda4e224a0c9c_img.jpg b/marked/Rel-11/29_series/29120/329c96049bb432e9c2cbda4e224a0c9c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c2410ae71da94f497a86572d9528d777ecb58b99 --- /dev/null +++ b/marked/Rel-11/29_series/29120/329c96049bb432e9c2cbda4e224a0c9c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9b05b5d132f2551fb84fded4c1f79be29b857159b4bcfdc175f7f1c8062eb91d +size 140011 diff --git a/marked/Rel-11/29_series/29120/32ff77da4286b58c4778033acaa10836_img.jpg b/marked/Rel-11/29_series/29120/32ff77da4286b58c4778033acaa10836_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..120026092f176e3fc2204d580f2d1bdd66285ac3 --- /dev/null +++ b/marked/Rel-11/29_series/29120/32ff77da4286b58c4778033acaa10836_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3ad916933a8bbee95caf2ff1db7d7281cae51f897055a4c851c7015082527ab2 +size 136737 diff --git a/marked/Rel-11/29_series/29120/3334fcca5dac808f4fd3840aba35bc2e_img.jpg b/marked/Rel-11/29_series/29120/3334fcca5dac808f4fd3840aba35bc2e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ba4f92b9d9230f42cafbb3248028eb0f52a47536 --- /dev/null +++ b/marked/Rel-11/29_series/29120/3334fcca5dac808f4fd3840aba35bc2e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5a2c2d5e2a3e190cbf9d4e8e8dd48a8f3a660db237759f924d8da12139e061a5 +size 94824 diff --git a/marked/Rel-11/29_series/29120/3337af75dfee8af7687b4f49914d6c93_img.jpg b/marked/Rel-11/29_series/29120/3337af75dfee8af7687b4f49914d6c93_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..83c2598e460730bd438235e6dfe15407befc5f4e --- /dev/null +++ b/marked/Rel-11/29_series/29120/3337af75dfee8af7687b4f49914d6c93_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ccb5dd6f59b4335395cd273c70b0228582c6464ee86c6327acb820a35e971d4f +size 106156 diff --git a/marked/Rel-11/29_series/29120/347010b7ac06d3ae97927fde0f784d7c_img.jpg b/marked/Rel-11/29_series/29120/347010b7ac06d3ae97927fde0f784d7c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a9dca1253e1486a62177f0e1395aab58926ac4c9 --- /dev/null +++ b/marked/Rel-11/29_series/29120/347010b7ac06d3ae97927fde0f784d7c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5c8eb24056e31ec43cc6beff9c764ea73abc1a0e4902761476908959de1db717 +size 116491 diff --git a/marked/Rel-11/29_series/29120/36fd537a1e39baa2471ecfaaf869751a_img.jpg b/marked/Rel-11/29_series/29120/36fd537a1e39baa2471ecfaaf869751a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b02d844aa1d13a0bc858f98efffb418dfbb7fdda --- /dev/null +++ b/marked/Rel-11/29_series/29120/36fd537a1e39baa2471ecfaaf869751a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1b9fcbd60b8b002f6f2e92d132f2e7e37c2b14ea2e95fa0ed9df8a6c7abcb0ae +size 28145 diff --git a/marked/Rel-11/29_series/29120/3750b0149a6380885998ab3ca6a8787c_img.jpg b/marked/Rel-11/29_series/29120/3750b0149a6380885998ab3ca6a8787c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2f31e599155610cebee644b5faf65010a228a7cc --- /dev/null +++ b/marked/Rel-11/29_series/29120/3750b0149a6380885998ab3ca6a8787c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6c1f9949c66ffd95c5be63bc37444a7104270a487f9835bea0f7cdb21339d968 +size 39262 diff --git a/marked/Rel-11/29_series/29120/38d82ffe820e339811b396206f40a201_img.jpg b/marked/Rel-11/29_series/29120/38d82ffe820e339811b396206f40a201_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d3da6452e866a8c82b9fd22189950288cb2529f4 --- /dev/null +++ b/marked/Rel-11/29_series/29120/38d82ffe820e339811b396206f40a201_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ba4beabfff4f06db64a80d8e17d0a8833a0ea312ab7e6da0a291d6a0776bf10e +size 136750 diff --git a/marked/Rel-11/29_series/29120/3ec35c497a0765a1a885c85f214b1bef_img.jpg b/marked/Rel-11/29_series/29120/3ec35c497a0765a1a885c85f214b1bef_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1c8378d70ae24bf1abd8c0ff2b567d568b71f5b1 --- /dev/null +++ b/marked/Rel-11/29_series/29120/3ec35c497a0765a1a885c85f214b1bef_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e3467aec236fed04dc5a21e4cf84da8ea3d603f77230c3fd0ff6a3c2a866410f +size 157412 diff --git a/marked/Rel-11/29_series/29120/40b80ef077f6151a9fbb593b8ad4864d_img.jpg b/marked/Rel-11/29_series/29120/40b80ef077f6151a9fbb593b8ad4864d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..37728a68c1544e42d3988eaf12509c7495f5c6ea --- /dev/null +++ b/marked/Rel-11/29_series/29120/40b80ef077f6151a9fbb593b8ad4864d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:85cf493c01103c659b3e63f487523a22304f509b5fe7934ef0b29a194e03448c +size 136640 diff --git a/marked/Rel-11/29_series/29120/4806f9f95fff13a30d6523bd6ffeac63_img.jpg b/marked/Rel-11/29_series/29120/4806f9f95fff13a30d6523bd6ffeac63_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..38bb5a789b34cc5eea364bea868d65865c16df9b --- /dev/null +++ b/marked/Rel-11/29_series/29120/4806f9f95fff13a30d6523bd6ffeac63_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9e6e49a06a2a26808ed80f34681c0b07cd57d8ecaba2bd789b51f917d47860e3 +size 132567 diff --git a/marked/Rel-11/29_series/29120/4847c98185bc52e8786b78738bc52b45_img.jpg b/marked/Rel-11/29_series/29120/4847c98185bc52e8786b78738bc52b45_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5f3b1f8252b2095baf214a12c87f8741e764880d --- /dev/null +++ b/marked/Rel-11/29_series/29120/4847c98185bc52e8786b78738bc52b45_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e5af902f2ed65c0cc34af16853a338646e56bb158eac333540a4ef7386c83836 +size 97005 diff --git a/marked/Rel-11/29_series/29120/49fe8fe978c0f7e73112d231feb377eb_img.jpg b/marked/Rel-11/29_series/29120/49fe8fe978c0f7e73112d231feb377eb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f600ee786864c5fff27501f544d1893315da5441 --- /dev/null +++ b/marked/Rel-11/29_series/29120/49fe8fe978c0f7e73112d231feb377eb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:83079285c26f0bb531b6701153fe91cad02de3b82599974d79e1a35d96d51cad +size 130491 diff --git a/marked/Rel-11/29_series/29120/4b398c5e8c4fd656d5b7a61806400650_img.jpg b/marked/Rel-11/29_series/29120/4b398c5e8c4fd656d5b7a61806400650_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7c71460dfab62454eee64b96c598cad4b096b95d --- /dev/null +++ b/marked/Rel-11/29_series/29120/4b398c5e8c4fd656d5b7a61806400650_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:af6969a629b209cd3e22b3446bbc8adbc6d25d8c15bf37872eb27fdada0448a2 +size 151597 diff --git a/marked/Rel-11/29_series/29120/4c9ba399ca7df11cbe9b6322cd9aee0a_img.jpg b/marked/Rel-11/29_series/29120/4c9ba399ca7df11cbe9b6322cd9aee0a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7f130459246196a70d258cc16e13d85683f5d9c6 --- /dev/null +++ b/marked/Rel-11/29_series/29120/4c9ba399ca7df11cbe9b6322cd9aee0a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:69a4bc4d0713161e2f63dc9a778b652ffc5dcb2d25bd187f575d713bcacd3ca0 +size 42633 diff --git a/marked/Rel-11/29_series/29120/4ff00a489baaa34a0c01070de1d613db_img.jpg b/marked/Rel-11/29_series/29120/4ff00a489baaa34a0c01070de1d613db_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..be019540d4e0b99f356d2e9e545bcc2e5019a8c2 --- /dev/null +++ b/marked/Rel-11/29_series/29120/4ff00a489baaa34a0c01070de1d613db_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6907b5806658552b5e200d7e07306a379cef2cb3fbe5d99184c9a5c8b08c6335 +size 106712 diff --git a/marked/Rel-11/29_series/29120/50214d232017279410e9c9db8eb75119_img.jpg b/marked/Rel-11/29_series/29120/50214d232017279410e9c9db8eb75119_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e7d1c3ca9f6a583d41dd8b8429b30bbe1907da9a --- /dev/null +++ b/marked/Rel-11/29_series/29120/50214d232017279410e9c9db8eb75119_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:08c3b3af98a22a06d5ca9b96ce3de0dd39b577b767faa8b6efcd8e148bb8965f +size 44139 diff --git a/marked/Rel-11/29_series/29120/5478f70a6cef3e5672b2b22d28830cfb_img.jpg b/marked/Rel-11/29_series/29120/5478f70a6cef3e5672b2b22d28830cfb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e0f8c2dfcc5f8777c49115643a3ee9a312570e7e --- /dev/null +++ b/marked/Rel-11/29_series/29120/5478f70a6cef3e5672b2b22d28830cfb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5613698a1dd1483622ca563e245628d2ffb68fa0b2c762161058e526230fe2d2 +size 104002 diff --git a/marked/Rel-11/29_series/29120/56a5265d174ce056c1dbe5e7a60839fc_img.jpg b/marked/Rel-11/29_series/29120/56a5265d174ce056c1dbe5e7a60839fc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d9a6395eea354298477d63d5c174b71a82bfad7f --- /dev/null +++ b/marked/Rel-11/29_series/29120/56a5265d174ce056c1dbe5e7a60839fc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:96a6292734ae30a7684621fff394a30000669e644060c59348db73449bdbce23 +size 134031 diff --git a/marked/Rel-11/29_series/29120/5801c19431e76330430e92a598cc7a16_img.jpg b/marked/Rel-11/29_series/29120/5801c19431e76330430e92a598cc7a16_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1265ec396bfc717c23dda8be2603ef33398df6d1 --- /dev/null +++ b/marked/Rel-11/29_series/29120/5801c19431e76330430e92a598cc7a16_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ea677e84e38b915de0bab9d6bf624d0f591b36b9e49dc3eda86bf2ced05998eb +size 115712 diff --git a/marked/Rel-11/29_series/29120/5cf80bac69830ea773ac17c87e0ae24d_img.jpg b/marked/Rel-11/29_series/29120/5cf80bac69830ea773ac17c87e0ae24d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b989561d95d8bac5112e806e86852f03fa1ed4b1 --- /dev/null +++ b/marked/Rel-11/29_series/29120/5cf80bac69830ea773ac17c87e0ae24d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3e9ea1783c156742c064c7130392ef8a6ae5f18c780067b88bba7864e401f172 +size 42160 diff --git a/marked/Rel-11/29_series/29120/5e9af8986a5845504f251d3079da8078_img.jpg b/marked/Rel-11/29_series/29120/5e9af8986a5845504f251d3079da8078_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..64de509d1b21b2d559d5a7a9bfb302d7548103f8 --- /dev/null +++ b/marked/Rel-11/29_series/29120/5e9af8986a5845504f251d3079da8078_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:34666a80d3fac88f00a7442a64d897f9774cc6239d68a469a3b8f103d8ab4351 +size 133509 diff --git a/marked/Rel-11/29_series/29120/61a7f401eb46fe99a71f27bc37493f04_img.jpg b/marked/Rel-11/29_series/29120/61a7f401eb46fe99a71f27bc37493f04_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..91045f1b0f816adf5a2eddd1869beffcd21eabc2 --- /dev/null +++ b/marked/Rel-11/29_series/29120/61a7f401eb46fe99a71f27bc37493f04_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:24927104c6672610ade0e44627f07471bccf9564aaecec22407f11d66fe5ab1d +size 20019 diff --git a/marked/Rel-11/29_series/29120/61b2e15aedbb8a8dffc5426c0a284eb1_img.jpg b/marked/Rel-11/29_series/29120/61b2e15aedbb8a8dffc5426c0a284eb1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..31becdfead20fe26b4e21545139b8b43735f1061 --- /dev/null +++ b/marked/Rel-11/29_series/29120/61b2e15aedbb8a8dffc5426c0a284eb1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:db6979391611e709ed30819f709ec9954cbb7b0fc183d473362abbad9f8242db +size 114909 diff --git a/marked/Rel-11/29_series/29120/6629e8a87e7552e2454b7c3e9f6d73a0_img.jpg b/marked/Rel-11/29_series/29120/6629e8a87e7552e2454b7c3e9f6d73a0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6d04575888db6c8bb7bea093820c5732b0b9b1e1 --- /dev/null +++ b/marked/Rel-11/29_series/29120/6629e8a87e7552e2454b7c3e9f6d73a0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:03bb68d922f9ac71ae7de302ffb6b2f7a4d40f66195f9c034584549e667fb8d3 +size 96479 diff --git a/marked/Rel-11/29_series/29120/67d03c9e89620d73e3786c869e559752_img.jpg b/marked/Rel-11/29_series/29120/67d03c9e89620d73e3786c869e559752_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6b4f2aa78711f94eef39737ad4daed709e806bf6 --- /dev/null +++ b/marked/Rel-11/29_series/29120/67d03c9e89620d73e3786c869e559752_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:deb614029f9e8cf45260631cfbfeb0b7c220a89c03ca59af8653da3be885ae90 +size 127169 diff --git a/marked/Rel-11/29_series/29120/684f7a2cd4ba3346bcaec1f7336f6aa3_img.jpg b/marked/Rel-11/29_series/29120/684f7a2cd4ba3346bcaec1f7336f6aa3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1d723613ca506f6dc06bcc4bea5afd8904f7652a --- /dev/null +++ b/marked/Rel-11/29_series/29120/684f7a2cd4ba3346bcaec1f7336f6aa3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b9863547f7bd693c0d65e41520cd170a664cb6fd704e2184bac2eb42dc31ca9b +size 147709 diff --git a/marked/Rel-11/29_series/29120/68a5a1a1a761c652b4b4c56da7cf9914_img.jpg b/marked/Rel-11/29_series/29120/68a5a1a1a761c652b4b4c56da7cf9914_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8a2fbe0aa9243464c72ba692184a741718b6077d --- /dev/null +++ b/marked/Rel-11/29_series/29120/68a5a1a1a761c652b4b4c56da7cf9914_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c6648608f6848787a3826bd0776f267e1371e67c7708be523d06efa435224bb7 +size 102651 diff --git a/marked/Rel-11/29_series/29120/694df81535f89c7bfb9ef0df6f130dc0_img.jpg b/marked/Rel-11/29_series/29120/694df81535f89c7bfb9ef0df6f130dc0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a9d20eeaabf908fa5301e5a209297291c748dfd1 --- /dev/null +++ b/marked/Rel-11/29_series/29120/694df81535f89c7bfb9ef0df6f130dc0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9ff79f4d85a95324f07d6b6d14f2ba37894a5f465ff8e505710224c3e57502a6 +size 118115 diff --git a/marked/Rel-11/29_series/29120/69e5f1993021af230d08c08aac97d9df_img.jpg b/marked/Rel-11/29_series/29120/69e5f1993021af230d08c08aac97d9df_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3857de3a61ee31bab963a15122575f2f9405af7c --- /dev/null +++ b/marked/Rel-11/29_series/29120/69e5f1993021af230d08c08aac97d9df_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4927e8ef4aedb36367e073f4e6cbcf2d5f7fb0c07276829ce7c06f48bf9d0b94 +size 127352 diff --git a/marked/Rel-11/29_series/29120/6a993bfdf2e00cfad01c4d2188a75d86_img.jpg b/marked/Rel-11/29_series/29120/6a993bfdf2e00cfad01c4d2188a75d86_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3280fe36d38dbb38382d18e309ecf2d8f56c40f4 --- /dev/null +++ b/marked/Rel-11/29_series/29120/6a993bfdf2e00cfad01c4d2188a75d86_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:02a02a25a28594d9ce40546b7f0e17ac6d46972d73bb0eadc0ca737321c5b877 +size 117674 diff --git a/marked/Rel-11/29_series/29120/6bc05e56e8453678a84fa6bdba3fd903_img.jpg b/marked/Rel-11/29_series/29120/6bc05e56e8453678a84fa6bdba3fd903_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2ddd4c93ca6d246c9631d4db107f3c5e1d5f04fe --- /dev/null +++ b/marked/Rel-11/29_series/29120/6bc05e56e8453678a84fa6bdba3fd903_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ccc027e223dffa16be3f998a399bc2f602b727334fad5f168ecbd9a2d52bc624 +size 105052 diff --git a/marked/Rel-11/29_series/29120/6e15fc9ea763541c5913d26f85072ae1_img.jpg b/marked/Rel-11/29_series/29120/6e15fc9ea763541c5913d26f85072ae1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..eaeb7474b9a2bf1b118ea18f4f692d0ab7c980db --- /dev/null +++ b/marked/Rel-11/29_series/29120/6e15fc9ea763541c5913d26f85072ae1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:81de0d3ba948975e6cb15d7ac96bee3c01aa8421d64814a122e99c72c3824cb9 +size 167568 diff --git a/marked/Rel-11/29_series/29120/6e9d059430baba0c363e33749f68b107_img.jpg b/marked/Rel-11/29_series/29120/6e9d059430baba0c363e33749f68b107_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..93f0fff7b38e241b0c23ef6dcd95c3374abf970a --- /dev/null +++ b/marked/Rel-11/29_series/29120/6e9d059430baba0c363e33749f68b107_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d8d410495874d7cb61af68e010fa58f827ed94ea228b397b90245b173be79a64 +size 136730 diff --git a/marked/Rel-11/29_series/29120/710ff83dc4a77abbe489fbf1a462845a_img.jpg b/marked/Rel-11/29_series/29120/710ff83dc4a77abbe489fbf1a462845a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a8635ba95e19f55098fd03376a1cb840317410b8 --- /dev/null +++ b/marked/Rel-11/29_series/29120/710ff83dc4a77abbe489fbf1a462845a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:531d0a6c6f6ccbd8f4dcb4df1c22cdb9b80c9c9bf3ce037caa8e8fc08c5f1252 +size 119298 diff --git a/marked/Rel-11/29_series/29120/719ef0f734259484038b2434e5dc3f24_img.jpg b/marked/Rel-11/29_series/29120/719ef0f734259484038b2434e5dc3f24_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f5d2d838cc669f71a30cdf1768aa6290674f09a3 --- /dev/null +++ b/marked/Rel-11/29_series/29120/719ef0f734259484038b2434e5dc3f24_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ba64236d64f50ed1d1cec0f083139c3725619f75630431a232a8d01ea67a7be7 +size 121411 diff --git a/marked/Rel-11/29_series/29120/750b1652a4f4791b84c02aa755a1dedd_img.jpg b/marked/Rel-11/29_series/29120/750b1652a4f4791b84c02aa755a1dedd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f5d2a0defb047ab0dc95ecf9e82be6842159fc06 --- /dev/null +++ b/marked/Rel-11/29_series/29120/750b1652a4f4791b84c02aa755a1dedd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:18946e2b548385018c90c73982c4ead76ae4dd44d26fc06f5d5aeb853b37bc5d +size 137437 diff --git a/marked/Rel-11/29_series/29120/78ff716475b2f65bf01c3a4d02d89fc4_img.jpg b/marked/Rel-11/29_series/29120/78ff716475b2f65bf01c3a4d02d89fc4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c208c5d8e9a378f54c0b3ffaeefe8251e1559e94 --- /dev/null +++ b/marked/Rel-11/29_series/29120/78ff716475b2f65bf01c3a4d02d89fc4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:917f998ea3ed44df72db2b3581f182ef720cc8360cbeedc21ec9b697530cb2de +size 133379 diff --git a/marked/Rel-11/29_series/29120/7e61b2e2506cc7e5d6e16ce9c9df25bb_img.jpg b/marked/Rel-11/29_series/29120/7e61b2e2506cc7e5d6e16ce9c9df25bb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ae84afbea505ab34d8192706be14cbe70e55a866 --- /dev/null +++ b/marked/Rel-11/29_series/29120/7e61b2e2506cc7e5d6e16ce9c9df25bb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e93c86d8358746c68c9ef3543f814c8e688d26b29278a523de8d43b2bf2238d6 +size 134233 diff --git a/marked/Rel-11/29_series/29120/7f16ae750ce9a533b0bd301dd986355e_img.jpg b/marked/Rel-11/29_series/29120/7f16ae750ce9a533b0bd301dd986355e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b80e0ba1bf2d66cfd0045ebebde62cbb12cfde6c --- /dev/null +++ b/marked/Rel-11/29_series/29120/7f16ae750ce9a533b0bd301dd986355e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:af25ca1409cd4cb5d4e847c4fde4bb53883fad768beac5fe0f9ba8425848790a +size 132458 diff --git a/marked/Rel-11/29_series/29120/8269648391c59363ea61243864a2adf7_img.jpg b/marked/Rel-11/29_series/29120/8269648391c59363ea61243864a2adf7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f336bdb3df03a1bb76e7ceba30c0a93661479994 --- /dev/null +++ b/marked/Rel-11/29_series/29120/8269648391c59363ea61243864a2adf7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e967a398187667c6f2ac2e5fe39271784ee01e03edfdee2db8c37e469fa54372 +size 35783 diff --git a/marked/Rel-11/29_series/29120/85680f3dcbe15424dd54fa3fd9e1c90d_img.jpg b/marked/Rel-11/29_series/29120/85680f3dcbe15424dd54fa3fd9e1c90d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2f3a32e26f6c22cdedc66af46a412c58379838a2 --- /dev/null +++ b/marked/Rel-11/29_series/29120/85680f3dcbe15424dd54fa3fd9e1c90d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:14a735c929804329a6d13261daeb62fca6ad0532be64499023729bfd6909b433 +size 79140 diff --git a/marked/Rel-11/29_series/29120/884c44b6cb9fbe15347e0562a6085df2_img.jpg b/marked/Rel-11/29_series/29120/884c44b6cb9fbe15347e0562a6085df2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..75e7ab60182b80c1feb97c40ddf4307eac228f91 --- /dev/null +++ b/marked/Rel-11/29_series/29120/884c44b6cb9fbe15347e0562a6085df2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2a14db2c1e05090551fb8cb180b71491a60c747afba65a72048482e4d8ecb673 +size 124155 diff --git a/marked/Rel-11/29_series/29120/8aafdc3df2af4882f3c1b5e1e7e8dc8a_img.jpg b/marked/Rel-11/29_series/29120/8aafdc3df2af4882f3c1b5e1e7e8dc8a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..34e7f8d913b33e507af43d7d25c77b94a505364e --- /dev/null +++ b/marked/Rel-11/29_series/29120/8aafdc3df2af4882f3c1b5e1e7e8dc8a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:da40a3b3fde397acbf22dde967c44801a3cc83634cb459fcad1d0463ec2f6498 +size 70196 diff --git a/marked/Rel-11/29_series/29120/8d66c9c295023a1380f9986d3663bb1e_img.jpg b/marked/Rel-11/29_series/29120/8d66c9c295023a1380f9986d3663bb1e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6a99fc7908951244a420e3eab553839be94790eb --- /dev/null +++ b/marked/Rel-11/29_series/29120/8d66c9c295023a1380f9986d3663bb1e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ec20866be894ebd7af75cb4f41962c87e1b5346bbf9ca838843d883a82d3d3a3 +size 112325 diff --git a/marked/Rel-11/29_series/29120/8faeb7db381e28ab1ba06e9f48c19c6e_img.jpg b/marked/Rel-11/29_series/29120/8faeb7db381e28ab1ba06e9f48c19c6e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d27475b5af3cd5ddb5194eda0cb230c598a78ac8 --- /dev/null +++ b/marked/Rel-11/29_series/29120/8faeb7db381e28ab1ba06e9f48c19c6e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ecb75a2f08b8f2042286e3ca45a0e893ee0d68b96ff13f4abd7f58a23c8dab07 +size 137022 diff --git a/marked/Rel-11/29_series/29120/921f8fa0f7ce2c9956f20d33162c13a2_img.jpg b/marked/Rel-11/29_series/29120/921f8fa0f7ce2c9956f20d33162c13a2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..32ba3f48bc234313a5af484dd45883b682f4fe84 --- /dev/null +++ b/marked/Rel-11/29_series/29120/921f8fa0f7ce2c9956f20d33162c13a2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ebc365fae6d1ececbd9d34100fe4b8de66a461e461f867000f635cf1ac655fef +size 81944 diff --git a/marked/Rel-11/29_series/29120/92724c769da9d46b730fde1a6dccb023_img.jpg b/marked/Rel-11/29_series/29120/92724c769da9d46b730fde1a6dccb023_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b9d0a390bee718851820cadc9402aba29a34197d --- /dev/null +++ b/marked/Rel-11/29_series/29120/92724c769da9d46b730fde1a6dccb023_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a670d6840853767637298eb57fd247fe99bdeca87c1a3bf522e6d1e7f2dea575 +size 136382 diff --git a/marked/Rel-11/29_series/29120/93699fb71e95b4df5a3871fdcf818982_img.jpg b/marked/Rel-11/29_series/29120/93699fb71e95b4df5a3871fdcf818982_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a187732248257c363d436b83008c729b4268c3b1 --- /dev/null +++ b/marked/Rel-11/29_series/29120/93699fb71e95b4df5a3871fdcf818982_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c2545684c7adad04e8d75acbf2f7c8af3d00fbc253b12ba089c92c36a4a0a3d8 +size 79540 diff --git a/marked/Rel-11/29_series/29120/93bd00a00fa28558486f0664550699b1_img.jpg b/marked/Rel-11/29_series/29120/93bd00a00fa28558486f0664550699b1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cf6b7794bdbc55a7afa24b7595b9a9d75696374d --- /dev/null +++ b/marked/Rel-11/29_series/29120/93bd00a00fa28558486f0664550699b1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c595914cc86f91c4003caf46f6f069efaa91d61b840cceb7b2723c7869863b3c +size 126281 diff --git a/marked/Rel-11/29_series/29120/9b1ec0090070bdf52ea28763b8d52477_img.jpg b/marked/Rel-11/29_series/29120/9b1ec0090070bdf52ea28763b8d52477_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..053c13dc59d0c49f0dc99135e7dcd4bf411c727c --- /dev/null +++ b/marked/Rel-11/29_series/29120/9b1ec0090070bdf52ea28763b8d52477_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8ad88bc2909398c56e88154125c156f78e0f36d324dfb24ee029354e7665b535 +size 129152 diff --git a/marked/Rel-11/29_series/29120/9c45844d796e85ae05505870a54e4eb4_img.jpg b/marked/Rel-11/29_series/29120/9c45844d796e85ae05505870a54e4eb4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2ef2b30bde3e127d8fb3590f274b38f80eded163 --- /dev/null +++ b/marked/Rel-11/29_series/29120/9c45844d796e85ae05505870a54e4eb4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:09018821cd3104bab826a260428e544b4d8790ee4c352d309e03345226d6af45 +size 138969 diff --git a/marked/Rel-11/29_series/29120/9cd6ff4a43174e4afe1cc5e4ea2fcae4_img.jpg b/marked/Rel-11/29_series/29120/9cd6ff4a43174e4afe1cc5e4ea2fcae4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2f6cfa28eb3baf63333012cac323b4808d16b471 --- /dev/null +++ b/marked/Rel-11/29_series/29120/9cd6ff4a43174e4afe1cc5e4ea2fcae4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:694b3cd81d6db739ccd52b13ab915c80994de4fe63c1b5828160976aa8c3892c +size 116761 diff --git a/marked/Rel-11/29_series/29120/a161a2bbb4d830e847ccb4f44b7e41a9_img.jpg b/marked/Rel-11/29_series/29120/a161a2bbb4d830e847ccb4f44b7e41a9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b251a5a383530d81767c33418df9e27eb4c99c18 --- /dev/null +++ b/marked/Rel-11/29_series/29120/a161a2bbb4d830e847ccb4f44b7e41a9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bedbed9322c2bf06fc5f78a434b66ecd91fe3515758ce12528cc110692cf5c47 +size 134597 diff --git a/marked/Rel-11/29_series/29120/a1b35c85c93d7a2e30d1feea2faac2e6_img.jpg b/marked/Rel-11/29_series/29120/a1b35c85c93d7a2e30d1feea2faac2e6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c925ec61c773c98da7e1400358bbef67325302b1 --- /dev/null +++ b/marked/Rel-11/29_series/29120/a1b35c85c93d7a2e30d1feea2faac2e6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7f2a57f73f5ac86eb58ae6ee46b5c9c095661a7fe6fff347049064017c967c2a +size 138186 diff --git a/marked/Rel-11/29_series/29120/a5404b7275b06497eecf9b5883604753_img.jpg b/marked/Rel-11/29_series/29120/a5404b7275b06497eecf9b5883604753_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a5bc510b1ecb6a78d28dc4a635142a11c49e6e1c --- /dev/null +++ b/marked/Rel-11/29_series/29120/a5404b7275b06497eecf9b5883604753_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:55f34495022602aefdaf6bec98e5717a11d990bf7d406bdd844ac10fec63f3c5 +size 158860 diff --git a/marked/Rel-11/29_series/29120/a7450c80e88ad3f6ca1427ad84020998_img.jpg b/marked/Rel-11/29_series/29120/a7450c80e88ad3f6ca1427ad84020998_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..261102a3e6c95dcbf593306ead18411cdf5f0ef9 --- /dev/null +++ b/marked/Rel-11/29_series/29120/a7450c80e88ad3f6ca1427ad84020998_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b7664f20442b63c9a5c304de7da90210421c614fc04061aa21f28f4d97da8ca8 +size 111582 diff --git a/marked/Rel-11/29_series/29120/a963ca41bde1669b18a4b783616f228b_img.jpg b/marked/Rel-11/29_series/29120/a963ca41bde1669b18a4b783616f228b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2786f9771928029f9e7cdabbf554a9039076feb9 --- /dev/null +++ b/marked/Rel-11/29_series/29120/a963ca41bde1669b18a4b783616f228b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7aea0733f087cde309e909ca95d7396705a70e64f0e0d7046f88e65a1bbb329d +size 113602 diff --git a/marked/Rel-11/29_series/29120/ac42de838505beb048fb1267c46de428_img.jpg b/marked/Rel-11/29_series/29120/ac42de838505beb048fb1267c46de428_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..79c96766ba84b22f115be1343bd8cfbbe688082d --- /dev/null +++ b/marked/Rel-11/29_series/29120/ac42de838505beb048fb1267c46de428_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:59e1e2bd82fef86eb604fea6d731f9a97a7b2468cb15f3cc146f515d5de86fb2 +size 33093 diff --git a/marked/Rel-11/29_series/29120/aeb2a26a07219661191294dba528067a_img.jpg b/marked/Rel-11/29_series/29120/aeb2a26a07219661191294dba528067a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8939810bb06aa61f588638833d9ea15a0304bf33 --- /dev/null +++ b/marked/Rel-11/29_series/29120/aeb2a26a07219661191294dba528067a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6ebe4483a6bf82b6695fb0f769f756feaec62a0ff98ef66edd12ba83c9663a6c +size 133092 diff --git a/marked/Rel-11/29_series/29120/b0384c8e0ff826a8116ab2ff67dadc43_img.jpg b/marked/Rel-11/29_series/29120/b0384c8e0ff826a8116ab2ff67dadc43_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..68b363c37de03b67486e0cd912265118935eac87 --- /dev/null +++ b/marked/Rel-11/29_series/29120/b0384c8e0ff826a8116ab2ff67dadc43_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:313cf1b615f48e43e38026f9d050cf4e60d08b9c324ffd65db68f8a557de94b0 +size 138783 diff --git a/marked/Rel-11/29_series/29120/b34c69e1ec326b01c3a485b27b1df5f6_img.jpg b/marked/Rel-11/29_series/29120/b34c69e1ec326b01c3a485b27b1df5f6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0040a9c01112d80bacc93e18eacf3e9f67915f27 --- /dev/null +++ b/marked/Rel-11/29_series/29120/b34c69e1ec326b01c3a485b27b1df5f6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7b58d81a963734329039e082db1e537808575864d751456cfdd07cd0e94d8e5b +size 96712 diff --git a/marked/Rel-11/29_series/29120/b55cd9b5721bd8aabc979c85316924e4_img.jpg b/marked/Rel-11/29_series/29120/b55cd9b5721bd8aabc979c85316924e4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..dc3ffecdaa648057faf1a6772f8583bb6d124af2 --- /dev/null +++ b/marked/Rel-11/29_series/29120/b55cd9b5721bd8aabc979c85316924e4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4046d38301ef66c730c404b08ac03d86a0c06d86acb89cacd0089acd9a3fbbb0 +size 129653 diff --git a/marked/Rel-11/29_series/29120/ba676d18b6a00f27c5bfaec9eeec20be_img.jpg b/marked/Rel-11/29_series/29120/ba676d18b6a00f27c5bfaec9eeec20be_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a238b7823da163d6166e1bf572e5480de9a85705 --- /dev/null +++ b/marked/Rel-11/29_series/29120/ba676d18b6a00f27c5bfaec9eeec20be_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d97aad669c5a61311d9d11fcf667e83d54e3495c46fb84d91218a039148e945d +size 136172 diff --git a/marked/Rel-11/29_series/29120/bdd96f20e71f079cad85240efb3d3f24_img.jpg b/marked/Rel-11/29_series/29120/bdd96f20e71f079cad85240efb3d3f24_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c06d500ccdb09e1028ca1dd8ba8fa844cd664de0 --- /dev/null +++ b/marked/Rel-11/29_series/29120/bdd96f20e71f079cad85240efb3d3f24_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8baeb0cf4921bcf0fd50d8525b25960cd4f334871d54278cab139efb8e0be51f +size 20391 diff --git a/marked/Rel-11/29_series/29120/c21bad844b5cb6026c067a1f43ce67c3_img.jpg b/marked/Rel-11/29_series/29120/c21bad844b5cb6026c067a1f43ce67c3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..036eaecacdb0c84b19b57b6afd6a19fab0b5f891 --- /dev/null +++ b/marked/Rel-11/29_series/29120/c21bad844b5cb6026c067a1f43ce67c3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:93eb37a7d42e97744d2d77c597508b617abe4c7c8cc020b77804bdb9eb2568b3 +size 117332 diff --git a/marked/Rel-11/29_series/29120/c3fcdb9e14cb1f7e5e0232c5fe0c5198_img.jpg b/marked/Rel-11/29_series/29120/c3fcdb9e14cb1f7e5e0232c5fe0c5198_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c7947360d94f59b44c7fb0296ad1851fd79a6efc --- /dev/null +++ b/marked/Rel-11/29_series/29120/c3fcdb9e14cb1f7e5e0232c5fe0c5198_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a35add4b3e983a6ea48cd16f8b2224313ca86bdd7f86777e252b4fa23be9d85b +size 88424 diff --git a/marked/Rel-11/29_series/29120/c99bf3a0530a3e58f5f2d2790ba7441b_img.jpg b/marked/Rel-11/29_series/29120/c99bf3a0530a3e58f5f2d2790ba7441b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..38a56bd9553acc6309b5e40285d25d7f6af541e3 --- /dev/null +++ b/marked/Rel-11/29_series/29120/c99bf3a0530a3e58f5f2d2790ba7441b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3dff331a782b03625d7d83df86a6829c2e0b519e93f0897116386c83930b8105 +size 164622 diff --git a/marked/Rel-11/29_series/29120/ca9fd3bd2fe73a46244dd1d017ffa3b5_img.jpg b/marked/Rel-11/29_series/29120/ca9fd3bd2fe73a46244dd1d017ffa3b5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f7c4fbf0af28c854ea42eeb293bd05b3cce35176 --- /dev/null +++ b/marked/Rel-11/29_series/29120/ca9fd3bd2fe73a46244dd1d017ffa3b5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:90eb4587fb2030388b344d122b3150cc8bd95f3f07ff99b7a357fc8bbb80f160 +size 36984 diff --git a/marked/Rel-11/29_series/29120/d2417b04116c354deccb25d98a84a0fb_img.jpg b/marked/Rel-11/29_series/29120/d2417b04116c354deccb25d98a84a0fb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..037a389320494a2429e3aeff4e653aef7274ec51 --- /dev/null +++ b/marked/Rel-11/29_series/29120/d2417b04116c354deccb25d98a84a0fb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a03e5614f82bfdfae2fa4806081d24a90c1848bb864212a3180a440a33bdf548 +size 139870 diff --git a/marked/Rel-11/29_series/29120/da85343976fdbb19f866d9ddbdad0eae_img.jpg b/marked/Rel-11/29_series/29120/da85343976fdbb19f866d9ddbdad0eae_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..26117177e9ab72fe3f28e2d029d9b01e40b76a48 --- /dev/null +++ b/marked/Rel-11/29_series/29120/da85343976fdbb19f866d9ddbdad0eae_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4e6bd214df6b6846d329ec1fdcbcab5c5e6cb9482eafd3700916c38106af2e60 +size 116747 diff --git a/marked/Rel-11/29_series/29120/db39acbd11df5eb7e79ab84562fb8f74_img.jpg b/marked/Rel-11/29_series/29120/db39acbd11df5eb7e79ab84562fb8f74_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ea1687e08d73982419e647df050903a59bb63946 --- /dev/null +++ b/marked/Rel-11/29_series/29120/db39acbd11df5eb7e79ab84562fb8f74_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bc4f969e650caecd2d65efc012a545e8501cb77061904797287f5dd09eb91b97 +size 130573 diff --git a/marked/Rel-11/29_series/29120/dbd4bab54b57e8d1abf80e3de6471130_img.jpg b/marked/Rel-11/29_series/29120/dbd4bab54b57e8d1abf80e3de6471130_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a3fc555372699e1d29ffd5563b097bea37ca849e --- /dev/null +++ b/marked/Rel-11/29_series/29120/dbd4bab54b57e8d1abf80e3de6471130_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9fb56f9a07b90e7c909e57a127e6b596041a0746ee09b94722fd420f7145a03f +size 140183 diff --git a/marked/Rel-11/29_series/29120/dd5771673aececa53d42ece89218299d_img.jpg b/marked/Rel-11/29_series/29120/dd5771673aececa53d42ece89218299d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3e0a3110039c1ab0e5e7046246349fa14c9c4fe0 --- /dev/null +++ b/marked/Rel-11/29_series/29120/dd5771673aececa53d42ece89218299d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8c002ddbeaf84eef1240b7366b7d3bb8fa4395028c92b743cf4f7ac22a821e3a +size 128447 diff --git a/marked/Rel-11/29_series/29120/dd6c544ab685b25dd17f59456efcfbfc_img.jpg b/marked/Rel-11/29_series/29120/dd6c544ab685b25dd17f59456efcfbfc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8c99461da0b19456c8986ab0d9f6edda09ec1376 --- /dev/null +++ b/marked/Rel-11/29_series/29120/dd6c544ab685b25dd17f59456efcfbfc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c773865033cb3266a4d99c4f24955f83b21431cb14ca258499c7da2e3ce51210 +size 19799 diff --git a/marked/Rel-11/29_series/29120/e05b36c0d46549e681ce6581422c66b2_img.jpg b/marked/Rel-11/29_series/29120/e05b36c0d46549e681ce6581422c66b2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3eb4f874f32a8880c1e04b3fe15fbbf1f8ffee27 --- /dev/null +++ b/marked/Rel-11/29_series/29120/e05b36c0d46549e681ce6581422c66b2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:88e5ceef0f7b1acf7386bfadbeb82ac03291e03bad7134017eb58dbf782669fe +size 94638 diff --git a/marked/Rel-11/29_series/29120/e16bfa31d748f4d99ec4ae3d16656926_img.jpg b/marked/Rel-11/29_series/29120/e16bfa31d748f4d99ec4ae3d16656926_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5add40279febe4374c6fb5d72e458520be675c1d --- /dev/null +++ b/marked/Rel-11/29_series/29120/e16bfa31d748f4d99ec4ae3d16656926_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5c4afadf38dc4f20a5d3963e1840de611ce3bbcfbed8b17adf70e4d89adedb61 +size 158723 diff --git a/marked/Rel-11/29_series/29120/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg b/marked/Rel-11/29_series/29120/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7053734bde3829535ea620ad9332024f6e39ddd2 --- /dev/null +++ b/marked/Rel-11/29_series/29120/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b4afee64f3ab93691030890b236908b51bd2d05ef1c1f0aa528cfe5dd9af953d +size 167778 diff --git a/marked/Rel-11/29_series/29120/e18841eb4a995df8354a793459e12fd0_img.jpg b/marked/Rel-11/29_series/29120/e18841eb4a995df8354a793459e12fd0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a270bada9c753cb7775882595c75cc4d75d8a3a2 --- /dev/null +++ b/marked/Rel-11/29_series/29120/e18841eb4a995df8354a793459e12fd0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:645eb7e2c046f5d2983753ec3fd1586a6b506a75bf70ba2d277e315acd2aca05 +size 119254 diff --git a/marked/Rel-11/29_series/29120/e2c120be98ede6deb60dd341f5a9803b_img.jpg b/marked/Rel-11/29_series/29120/e2c120be98ede6deb60dd341f5a9803b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..98ca62f0182207a5caec48a6860406da56e511db --- /dev/null +++ b/marked/Rel-11/29_series/29120/e2c120be98ede6deb60dd341f5a9803b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f9f3e88c0ed914d9fa1e61e0fb60e64e1b864e44daa747b5d610a74d3f4d8a4a +size 152970 diff --git a/marked/Rel-11/29_series/29120/e7010c66da16316c2935dfbbef5056b3_img.jpg b/marked/Rel-11/29_series/29120/e7010c66da16316c2935dfbbef5056b3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c47d83bd4532e8861f7b6eed1c180dbae67cfd2d --- /dev/null +++ b/marked/Rel-11/29_series/29120/e7010c66da16316c2935dfbbef5056b3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d6dad54992aa4049a2a1af3c2d295861da356d8d903dadfe57fa9f5b2baf2ad1 +size 88433 diff --git a/marked/Rel-11/29_series/29120/e90987faabad6a6665cd8ed1151dc474_img.jpg b/marked/Rel-11/29_series/29120/e90987faabad6a6665cd8ed1151dc474_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..946c694c3719b3bcb2fdedc64e0bcafdf2c1be77 --- /dev/null +++ b/marked/Rel-11/29_series/29120/e90987faabad6a6665cd8ed1151dc474_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:798977f7c4f3a43a08e78e28a466c19c2bc30001b5378d7b820b588f5f4eb389 +size 141151 diff --git a/marked/Rel-11/29_series/29120/eabcb2f8b9acedb194571d5bc734b463_img.jpg b/marked/Rel-11/29_series/29120/eabcb2f8b9acedb194571d5bc734b463_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..70d058f263c46c818c73fa3109a9b2b944e498f5 --- /dev/null +++ b/marked/Rel-11/29_series/29120/eabcb2f8b9acedb194571d5bc734b463_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f95afa129bb68a16f404428afea58a108ba84877ae701818a9777296ebc63e9e +size 112251 diff --git a/marked/Rel-11/29_series/29120/eefcb3f73fb33cce57cd04109c81506f_img.jpg b/marked/Rel-11/29_series/29120/eefcb3f73fb33cce57cd04109c81506f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d3dafcb425d0585ca73bf8f155f317aedcd081b2 --- /dev/null +++ b/marked/Rel-11/29_series/29120/eefcb3f73fb33cce57cd04109c81506f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3db5a0fabce44c9377da241a95c35452461dec04187a7c08e3b3c19add60ce85 +size 68979 diff --git a/marked/Rel-11/29_series/29120/ef45b00396c293be0b18d32b97118bf4_img.jpg b/marked/Rel-11/29_series/29120/ef45b00396c293be0b18d32b97118bf4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a62e31f34b3857f9cc761a144b92ed348b22c62b --- /dev/null +++ b/marked/Rel-11/29_series/29120/ef45b00396c293be0b18d32b97118bf4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4402414502118811b8e66088069e8f0b289a2a7634ef2d6a2136da335abd12b5 +size 118675 diff --git a/marked/Rel-11/29_series/29120/f4e5a86da5c799372a7c1ea2397dedb7_img.jpg b/marked/Rel-11/29_series/29120/f4e5a86da5c799372a7c1ea2397dedb7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..eea0b17957ed12d00bd2bc9a2969643974dfb73b --- /dev/null +++ b/marked/Rel-11/29_series/29120/f4e5a86da5c799372a7c1ea2397dedb7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:faee39badf0e6fe1cce861445107dff3c61658f1b8fce8dbc12b2cb359532b88 +size 130994 diff --git a/marked/Rel-11/29_series/29120/f61d0925551545b5938b3a4d1bbf63c3_img.jpg b/marked/Rel-11/29_series/29120/f61d0925551545b5938b3a4d1bbf63c3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2bb20bb2917ed50ade4021e7de0b45dc28a77a5c --- /dev/null +++ b/marked/Rel-11/29_series/29120/f61d0925551545b5938b3a4d1bbf63c3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:27852569af244cd842745d3487d91e525819d377d8aa3bf87a6fcf07534b1117 +size 126634 diff --git a/marked/Rel-11/29_series/29120/fc3e2b49a9f850951570e502393b697f_img.jpg b/marked/Rel-11/29_series/29120/fc3e2b49a9f850951570e502393b697f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..958fe143e9044a7f7ef9893d75cebd9c0cf28296 --- /dev/null +++ b/marked/Rel-11/29_series/29120/fc3e2b49a9f850951570e502393b697f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5143b5bf7dd79585b93d2133cdfc0f744b02c0236b02e7f213f261a7155d1af8 +size 118723 diff --git a/marked/Rel-11/29_series/29120/fd3cbb53e991f8209ba17b398f426e13_img.jpg b/marked/Rel-11/29_series/29120/fd3cbb53e991f8209ba17b398f426e13_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0da0572492afec68a18a3e0e7ed322383e84139a --- /dev/null +++ b/marked/Rel-11/29_series/29120/fd3cbb53e991f8209ba17b398f426e13_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:898392f3b20104046c7891f35b7dd8f1812ae9f3d0413db14e4cae1ea37dc219 +size 158320 diff --git a/marked/Rel-11/29_series/29120/fe7304192caf64cda93b580c5e7e5c06_img.jpg b/marked/Rel-11/29_series/29120/fe7304192caf64cda93b580c5e7e5c06_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4f814b8ddbec50a4ce5ddad7ec49d5c071bb6a9a --- /dev/null +++ b/marked/Rel-11/29_series/29120/fe7304192caf64cda93b580c5e7e5c06_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:745a461cae1d3f935a39c775787a6d433bdd0feac262758d468290cf0534db48 +size 85136 diff --git a/marked/Rel-11/29_series/29120/ffb6acd27b8e3a54392840948a75869f_img.jpg b/marked/Rel-11/29_series/29120/ffb6acd27b8e3a54392840948a75869f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2346c506f8885e5437741855ad33f3b03d650e3d --- /dev/null +++ b/marked/Rel-11/29_series/29120/ffb6acd27b8e3a54392840948a75869f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5cd9be571746fba6174e7c02960df18656db130c0db03d031f0d1566e6242d9a +size 21010 diff --git a/marked/Rel-11/29_series/29120/raw.md b/marked/Rel-11/29_series/29120/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..816db416f8178bc79f7d4b1d7883984d21a0f620 --- /dev/null +++ b/marked/Rel-11/29_series/29120/raw.md @@ -0,0 +1,5675 @@ + + + + + + +# Contents + +| | | +|---------------------------------------------------------------------------------|----| +| Foreword ..... | 7 | +| 1 Scope..... | 8 | +| 2 References..... | 8 | +| 3 Abbreviations ..... | 8 | +| 4 The entities and interfaces within the mobile network utilising the GLR ..... | 9 | +| 4.1 The entities of the mobile system..... | 9 | +| 4.2 The Interfaces within the mobile services..... | 9 | +| 5 Overload and compatibility overview..... | 9 | +| 5.1 Overload control for MAP entities..... | 9 | +| 5.2 Compatibility..... | 9 | +| 6 Requirements concerning the use of SCCP and TC ..... | 10 | +| 6.1 Use of SCCP..... | 10 | +| 6.1.1 SCCP Class..... | 10 | +| 6.1.2 Sub-System Number (SSN)..... | 10 | +| 6.1.3 SCCP addressing ..... | 10 | +| 6.1.3.1 Introduction..... | 10 | +| 6.1.3.2 The Gateway Location Register (GLR) ..... | 10 | +| 6.1.3.2.1 Addressed by the VLR..... | 10 | +| 6.1.3.2.2 Addressed by the HLR..... | 10 | +| 6.1.3.2.3 Addressed by the GMSC..... | 11 | +| 6.1.3.2.4 Addressed by the IM-GSN..... | 11 | +| 6.1.3.3 The Intermediate MSC (IM_MSC)..... | 11 | +| 6.1.3.3.1 Addressed by the GMSC..... | 11 | +| 6.1.3.3.2 Addressed by the GMLC..... | 11 | +| 6.1.3.4 The Intermediate GSN (IM_GSN) ..... | 11 | +| 6.1.3.5 Summary table ..... | 11 | +| 6.2 Use of TC ..... | 12 | +| 7 General on MAP services ..... | 13 | +| 7.1 Common MAP services ..... | 13 | +| 7.1.1 MAP-U-ABORT service..... | 13 | +| 8 Mobility services..... | 14 | +| 8.1 General ..... | 14 | +| 8.2 Location Management services..... | 15 | +| 8.3 Authentication Management services ..... | 15 | +| 8.4 Subscriber management services ..... | 15 | +| 8.5 Fault recovery services..... | 16 | +| 8.6 Subscriber Information services..... | 16 | +| 9 Operation and maintenance services..... | 16 | +| 9.1 General ..... | 16 | +| 9.2 MAP_SEND_IMSI service ..... | 16 | +| 10 Call handling services ..... | 17 | +| 10.1 General ..... | 17 | +| 10.2 MAP_PROVIDE_ROAMING_NUMBER service ..... | 17 | +| 10.3 MAP_SET_REPORTING_STATE service..... | 17 | +| 10.4 MAP_STATUS_REPORT service ..... | 17 | +| 10.5 MAP_REMOTE_USER_FREE service ..... | 17 | +| 11 Supplementary services related services..... | 18 | +| 11.1 General ..... | 18 | +| 11.2 MAP_REGISTER_SS service ..... | 18 | +| 11.3 MAP_ERASE_SS service..... | 18 | +| 11.4 MAP_ACTIVATE_SS service ..... | 18 | +| 11.5 MAP_DEACTIVATE_SS service..... | 18 | + +| | | | +|----------|--------------------------------------------------------------|----| +| 11.6 | MAP_INTERROGATE_SS service ..... | 19 | +| 11.7 | MAP_REGISTER_PASSWORD service ..... | 19 | +| 11.8 | MAP_GET_PASSWORD service ..... | 19 | +| 11.9 | MAP_PROCESS_UNSTRUCTURED_SS_REQUEST service ..... | 19 | +| 11.10 | MAP_UNSTRUCTURED_SS_REQUEST service ..... | 20 | +| 11.11 | MAP_UNSTRUCTURED_SS_NOTIFY service ..... | 20 | +| 11.12 | MAP_REGISTER_CC_ENTRY service ..... | 20 | +| 11.13 | MAP_ERASE_CC_ENTRY service ..... | 20 | +| 12 | Short message service management services ..... | 20 | +| 12.1 | General ..... | 20 | +| 12.2 | MAP-READY-FOR-SM service ..... | 21 | +| 12.3 | MAP-MT-FORWARD-SHORT-MESSAGE service ..... | 21 | +| 13 | Network-Requested PDP Context Activation services ..... | 21 | +| 13.1 | General ..... | 21 | +| 13.2 | MAP_SEND_ROUTING_INFO_FOR_GPRS service ..... | 21 | +| 13.3 | MAP_FAILURE_REPORT service ..... | 22 | +| 14 | Void ..... | 22 | +| 15 | Element of procedure ..... | 22 | +| 15.1 | SDL descriptions ..... | 22 | +| 16 | Mapping onto TC services ..... | 23 | +| 17 | Abstract syntax of the MAP protocol ..... | 24 | +| 17.1 | General ..... | 24 | +| 17.2 | Packages specifications ..... | 24 | +| 17.3 | Application contexts ..... | 25 | +| 18 | General on MAP user procedure ..... | 26 | +| 19 | Mobility procedures ..... | 27 | +| 19.1 | Location management Procedures ..... | 27 | +| 19.1.1 | Location updating ..... | 29 | +| 19.1.1.1 | General ..... | 29 | +| 19.1.1.2 | Detailed procedure in the GLR ..... | 30 | +| 19.1.2 | Location Cancellation ..... | 43 | +| 19.1.2.1 | General ..... | 43 | +| 19.1.2.2 | Detailed procedure in the GLR ..... | 44 | +| 19.1.3 | Purge MS ..... | 49 | +| 19.1.3.1 | General ..... | 49 | +| 19.1.3.2 | Detailed procedure in GLR ..... | 49 | +| 19.2 | Fault recovery procedures ..... | 54 | +| 19.2.1 | RESET procedure ..... | 54 | +| 19.2.1.1 | HLR failure case ..... | 54 | +| 19.2.1.2 | GLR failure case ..... | 54 | +| 19.2.1.3 | Detailed procedure in GLR ..... | 54 | +| 19.2.2 | VLR restoration: the restore data procedure in the GLR ..... | 58 | +| 19.2.2.1 | General ..... | 58 | +| 19.2.2.2 | Detailed procedure in GLR ..... | 58 | +| 20 | Operations and maintenance procedures ..... | 65 | +| 20.1 | General ..... | 65 | +| 20.2 | Subscriber data management procedures ..... | 65 | +| 20.2.1 | General ..... | 65 | +| 20.2.2 | Procedures in the GLR ..... | 67 | +| 20.2.2.1 | Subscriber deletion procedure ..... | 67 | +| 20.2.2.2 | Subscriber data modification procedure ..... | 67 | +| 20.3 | Subscriber Identity procedure ..... | 77 | +| 20.3.1 | Subscriber identity procedure in the GLR ..... | 78 | +| 21 | Call handling procedures ..... | 81 | +| 21.1 | General ..... | 81 | + +| | | | +|---------|--------------------------------------------------------------------------|-----| +| 21.2 | Retrieval of routing information ..... | 82 | +| 21.2.1 | General ..... | 82 | +| 21.2.2 | Process in the GLR to provide a roaming number ..... | 83 | +| 21.2.3 | Process in the GLR to provide subscriber information ..... | 86 | +| 21.3 | Setting of Reporting State ..... | 89 | +| 21.3.1 | General ..... | 89 | +| 21.3.2 | Process in the GLR to set the reporting state ..... | 89 | +| 21.4 | Status Reporting ..... | 92 | +| 21.4.1 | General ..... | 92 | +| 21.4.2 | Process in the GLR for Status Reporting ..... | 92 | +| 21.5 | Remote User Free..... | 94 | +| 21.5.1 | General ..... | 94 | +| 21.5.2 | Process in the GLR for Remote User Free ..... | 95 | +| 22 | Supplementary services procedures..... | 98 | +| 22.1 | Functional supplementary service processes..... | 98 | +| 22.1.1 | Functional supplementary service process co-ordinator for GLR..... | 98 | +| 22.1.2 | Call completion supplementary service process co-ordinator for GLR ..... | 100 | +| 22.2 | Registration procedure ..... | 102 | +| 22.2.1 | General ..... | 102 | +| 22.2.2 | Procedures in the GLR ..... | 103 | +| 22.3 | Erasure procedure..... | 105 | +| 22.3.1 | General ..... | 105 | +| 22.3.2 | Procedures in the GLR ..... | 106 | +| 22.4 | Activation procedure..... | 106 | +| 22.4.1 | General ..... | 106 | +| 22.4.2 | Procedures in the GLR ..... | 106 | +| 22.5 | Deactivation procedure ..... | 108 | +| 22.5.1 | General ..... | 108 | +| 22.5.2 | Procedures in the GLR ..... | 109 | +| 22.6 | Interrogation procedure..... | 109 | +| 22.6.1 | General ..... | 109 | +| 22.6.2 | Procedures in the GLR ..... | 109 | +| 22.7 | Password registration procedure ..... | 109 | +| 22.7.1 | General ..... | 109 | +| 22.7.2 | Procedures in the GLR ..... | 109 | +| 22.8 | Mobile Initiated USSD procedure..... | 109 | +| 22.8.1 | Procedures in the GLR ..... | 109 | +| 22.9 | Network initiated USSD procedure..... | 112 | +| 22.9.1 | Procedure in the GLR..... | 112 | +| 22.10 | Common macros for clause 22..... | 116 | +| 22.10.1 | SS Password handling macros..... | 116 | +| 22.11 | Activation of a CCBS request..... | 118 | +| 22.11.1 | General ..... | 118 | +| 22.11.2 | Procedure in the GLR ..... | 118 | +| 22.12 | Deactivation of a CCBS request..... | 120 | +| 22.12.1 | General ..... | 120 | +| 22.12.2 | Procedure in the GLR..... | 121 | +| 23 | Short message service procedures..... | 124 | +| 23.1 | General ..... | 124 | +| 23.2 | The mobile terminated short message transfer procedure..... | 124 | +| 23.2.1 | Procedure in the Intermediate MSC ..... | 124 | +| 23.2.2 | Procedure in the GLR..... | 130 | +| 23.3 | The Short Message Alert procedure..... | 136 | +| 23.3.1 | Procedures in the GLR ..... | 137 | +| 24 | GPRS process description..... | 139 | +| 24.1 | General ..... | 139 | +| 24.2 | Send Routing Information procedure..... | 139 | +| 24.2.1 | Process in the GLR for Send Routing Information for GPRS..... | 139 | +| 24.2.2 | Process in the IM-GSN for Send Routing Information for GPRS ..... | 140 | +| 24.3 | Failure Report procedure..... | 143 | + +| | | | +|------------------------|----------------------------------------------------------------------------|-----| +| 24.3.1 | Process in the GLR for Failure Report ..... | 143 | +| 24.3.2 | Process in the IM-GSN for Failure Report..... | 144 | +| 25 | General macro description ..... | 147 | +| 25.1 | MAP open macros..... | 147 | +| 25.2 | Macros to check the content of indication and confirmation primitives..... | 147 | +| 25.3 | Authentication processes..... | 147 | +| 25.3.1 | Process Obtain_Authentication_Sets_GLR..... | 147 | +| 25.3.2 | Process Authentication_Failure_Report_GLR ..... | 149 | +| 25.4 | Short Message Alert procedures ..... | 151 | +| 25.4.1 | Subscriber_Present_GLR_AS_VLR process ..... | 151 | +| 25.4.2 | The Mobile Subscriber is present..... | 154 | +| Annex A (informative): | Change history..... | 156 | + +# --- Foreword + +This Technical Specification (TS) has been produced by the 3rd Generation Partnership Project (3GPP). + +The present document specifies the signalling requirements and procedures used at network elements related to the Gateway Location Register (GLR) for Mobile Application Part (MAP) within the 3GPP system. (i.e. the present document specifies the delta against 3GPP TS 29.002.) + +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 signalling requirements and procedures used at network elements related to the GLR for MAP within the 3GPP system at the application level. + +The present document gives the description of the systems needed only in the network utilising GLR as the delta document against 3GPP TS 29.002. + +# --- 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 23.003: "Numbering, addressing and identification". +- [2] 3GPP TS 23.007: "Restoration procedures". +- [3] 3GPP TS 23.012: "Location registration procedures". +- [4] 3GPP TS 23.040: "Technical realization of the Short Message Service (SMS) Point to Point (PP)". +- [5] 3GPP TS 29.002: "Mobile Application Part (MAP) specification". +- [6] 3GPP TS 23.119: "Gateway Location Register (GLR) - stage2". + +# --- 3 Abbreviations + +For the purposes of the present document, the following abbreviations apply: + +| | | +|--------|---------------------------------------| +| CCBS | Completion of Call to Busy Subscriber | +| GLR | Gateway Location Register | +| GPRS | General Packet Radio Service | +| IM_GSN | Intermediate GSN | +| IM_MSC | Intermediate MSC | +| SGSN | Serving GPRS support node | +| GGSN | Gateway GPRS support node | + +# --- 4 The entities and interfaces within the mobile network utilising the GLR + +## 4.1 The entities of the mobile system + +The functional entities related to the GLR are described below. The description of each entity is detailed in 3GPP TS 23.119 (GLR stage2 specification). The other functional entities described in the present document (e.g. MSC, VLR, and HLR) are specified in 3GPP TS 29.002. + +- The Gateway location Register (GLR). +- The Intermediate MSC (IM-MSC). +- The Intermediate GSN (IM-GSN). + +## 4.2 The Interfaces within the mobile services + +The Interfaces related to the GLR are described below. The description of each interface is detailed in 3GPP TS 23.119 (GLR stage2 specification). + +- Interface between the HLR and the GLR. +- Interface between the VLR and the GLR. +- Interface between the MSC and the IM\_MSC. +- Interface between the SGSN and the GLR. +- Interface between the MSC and the GLR. +- Interface between the GLR and the IM\_GSN. + +# --- 5 Overload and compatibility overview + +## 5.1 Overload control for MAP entities + +The VLR and SGSN see the GLR as an HLR, and the HLR sees the GLR as a VLR or a SGSN. Therefore the GLR shall behave like mobile entity as which the GLR is regarded. If overload of the GLR is detected, the responder may ignore requests for certain MAP operations (see tables 5.1/1, 5.1/2 and 5.1/3 in 3GPP TS 29.002). The decision as to which MAP Operations may be ignored is made by the MAP service provider and is based upon the priority of the application context. + +## 5.2 Compatibility + +A version negotiation mechanism based on the use of an application-context-name is used to negotiate the protocol version used between two entities for supporting a MAP-user signalling procedure. The description of the version negotiation mechanism is detailed in 3GPP TS 29.002. + +# --- 6 Requirements concerning the use of SCCP and TC + +## 6.1 Use of SCCP + +The Mobile Application Part makes use of the services offered by the Signalling Connection Control Part of signalling System No. 7. CCITT Blue Book or ITU-T (03/93) Recommendations Q.711 to Q.716 should be consulted for the full specification of SCCP. In North America (World Zone 1) the national version of SCCP is used as specified in ANSI T1.112. + +### 6.1.1 SCCP Class + +MAP will only make use of the connectionless classes (0 or 1) of the SCCP. + +### 6.1.2 Sub-System Number (SSN) + +The Application Entities (AEs) defined for MAP consist of several Application Service Elements (ASEs) and are addressed by sub-system numbers (SSNs). The SSN for MAP are specified in 3GPP TS 23.003 [1]. The specific SSN is not needed for the GLR, IM\_MSC, and IM\_GSN. + +### 6.1.3 SCCP addressing + +#### 6.1.3.1 Introduction + +The format and coding of address parameters carried by SCCP are detailed in 3GPP TS 29.002. + +The following subclauses describe the method of SCCP addressing appropriate for each entity both for the simple intra-PLMN case and where an inter-PLMN communication is required. The following entities are considered for the GLR additionally: + +- the Gateway location Register (GLR); +- the Intermediate Mobile-services Switching Centre (IM\_MSC); +- the Intermediate GPRS Support Node (IM\_GSN). + +#### 6.1.3.2 The Gateway Location Register (GLR) + +##### 6.1.3.2.1 Addressed by the VLR + +In the network utilising the GLR, when an MS that belongs to other PLMN registers in a VLR/SGSN, the VLR/SGSN sees the GLR as the MS's HLR. When initiating the update location dialogues, the VLR is able to address the GLR based on the SPC of the GLR because of intra-PLMN signalling. And the VLR can address the GLR based on an E.214 Mobile Global Title originally derived by the VLR from the IMSI (when CCITT or ITU-T SCCP is used), or an E.212 number originally derived from IMSI (when ANSI SCCP is used, an IMSI). When answering with Global Title to the VLR, the GLR shall insert its E.164 address in the Calling Party Address of the SCCP message containing the first responding CONTINUE message. After that, the VLR can address the GLR based on an E.164 GLR address. + +##### 6.1.3.2.2 Addressed by the HLR + +When a location updating dialogue initiated by a GLR has been successfully completed, the HLR sees the GLR as the VLR. When initiating dialogues towards the VLR, the routeing information used by the HLR is derived from the E.164 VLR number received as a parameter of the MAP message initiating the update location dialogue, but in reality the HLR addresses the GLR using the VLR number. + +##### 6.1.3.2.3 Addressed by the GMSC + +In the case that the MS is served by the SGSN in the network utilising the GLR, the GMSC sees the GLR as the SGSN. When the GMSC initiates dialogues towards the SGSN the SGSN (MAP) SSN (See 3GPP TS 23.003) shall be included in the called party address. The routeing information used by the GMSC is derived from the E.164 SGSN number received as a parameter of the MAP message initiating the forward short message procedure. But in reality the GMSC addresses the GLR using the SGSN number. + +##### 6.1.3.2.4 Addressed by the IM-GSN + +In the network utilising the GLR, the IM-GSN initiates the GPRS location information retrieval to the GLR. The IM-GSN must have the value of the GLR address beforehand. + +#### 6.1.3.3 The Intermediate MSC (IM\_MSC) + +##### 6.1.3.3.1 Addressed by the GMSC + +When a short message for CS has to be routed to an MS, the GMSC addresses the MSC by an MSC identity received from the HLR that complies with E.164 rules. But in reality the GMSC addresses the IM-MSC in the network utilising the GLR. + +##### 6.1.3.3.2 Addressed by the GMLC + +When a location request for a particular MS needs to be sent to the MS's VMSC, the GMLC addresses the MSC using an E.164 address received from the MS's HLR. But in reality the GMLC addresses the IM-MSC in the network utilising the GLR. + +#### 6.1.3.4 The Intermediate GSN (IM\_GSN) + +The IM-GSN provides routing of the Network-Requested PDP Context activation. If a Network-Requested PDP Context activation fails, the GLR will alert the IM-GSN when the subscriber becomes reachable. The GLR will use the E.164 IM-GSN number received as parameter of the MAP message reporting the failure. + +#### 6.1.3.5 Summary table + +The following table summarises the SCCP address used for invoke operations. As a principle, within a PLMN either an SPC or a GT may be used (network operation option), whereas when addressing an entity outside the PLMN the GT must be used. The address type mentioned in the table (e.g. MSISDN) is used as GT or to derive the SPC. + +For a response, the originating address passed in the invoke message is used as SCCP Called Party Address. For extra-PLMN addressing the own E.164 entity address is used as SCCP Calling Party Address; for intra-PLMN addressing an SPC derived from the entity number may be used instead. When using an SPC, the SPC may be taken directly from MTP. + +Table 6.1.3/1 + +| to
from | fixed
net
work | HLR | VLR | MSC | SGSN | GGSN | GLR | IM-MSC | IM-
GSN | +|--------------------------------------------|----------------------|-----------------------------------------------------------------------------------------------|-------------------------------------|-----------------------------|--------------------------------------|-------|---------------------------------------------------------------------------------------------------------|-------------------------------------|------------| +| fixed
network | | | | | | | | | | +| home
location
register | | | | | | | I:SPC/GT
E:GT
T:VLR NUMBER | | | +| visitor
location
register | | | | | | | I:SPC/GT
E:GT
T:MGT
(outside World Zone
1)/MSISDN
(World Zone 1)/HLR
NUMBER
(note) | | | +| mobile-
services
switching
centre | | | | | | | E:GT
T:SGSN NUMBER | I:SPC/GT
E:GT
T:MSC
NUMBER | | +| Serving
GPRS
Support
Node | | | | | | | I:SPC/GT
T:MGT/MSISDN/HL
R NUMBER | | | +| Gateway
GPRS
Support
Node | | | | | | Note1 | | | | +| Gateway
Location
register | --- | E:GT
T:MGT
(outside
World
Zone1)/MSISDN(
World Zone1/)
HLR NUMBER
(note) | I:SPC/G
T
T:VLR
NUMBE
R | --- | I:SPC/G
T
T:SGSN
NUMBE
R | | | | | +| Intermedia
te-
MSC | --- | | | I:SPC/GT
T:MSC
NUMBER | | | | | | +| Intermedia
te-
GSN | --- | | | | | | I:SPC/GT
T:HLR
NUMBER | | | + +I: Intra-PLMN E: Extra (Inter)-PLMN T: Address Type + GT: Global Title MGT: E.214 Mobile Global Title SPC: Signalling Point Code + +NOTE 0: For initiating the location updating procedure and an authentication information retrieval from the HLR preceding it, the VLR has to derive the HLR address from the IMSI of the MS. The result can be an SPC or an E.214 Mobile Global Title if CCITT or ITU-T SCCP is used, or IMSI itself if ANSI SCCP is used (ANSI SCCP is used in World Zone 1). When continuing the established update location dialogue (as with any other dialogue) the VLR must derive the routing information towards the HLR from the Calling Party Address received with the first responding CONTINUE message until the dialogue terminating message is received. + +For transactions invoked by the VLR after update location completion, the VLR may derive the information for addressing the HLR from addresses received in the course of the update location procedure (MSISDN or HLR number) or from the IMSI. + +When invoking the Restore Data procedure and an authentication information retrieval from the HLR preceding it, the VLR must derive the information for addressing the HLR from the address information received in association with the roaming number request. This may be either the IMSI received as a parameter of the MAP message requesting the Roaming Number or the Calling Party Address associated with the MAP message requesting the Roaming Number. + +From VLR in, GLR as for T (address type) only HLR Number is used. VLR and HLR are because only the thing that is belonging to same PLMN is thought. + +NOTE1: The hatching part is the same part of 3GPP TS29.002. + +## 6.2 Use of TC + +Refer to the corresponding section in 3GPP TS 29.002. + +# 7 General on MAP services + +Refer to the corresponding section in 3GPP TS 29.002 with the exceptions described below. + +## 7.1 Common MAP services + +The following common services are used: + +- MAP-OPEN service; +- MAP-CLOSE service; +- MAP-DELIMITER service; +- MAP-U-ABORT service; +- MAP-P-ABORT service; +- MAP-NOTICE service; +- MAP-SECURE-TRANSPORT-CLASS-1 service; +- MAP-SECURE-TRANSPORT-CLASS-2 service; +- MAP-SECURE-TRANSPORT-CLASS-3 service; +- MAP-SECURE-TRANSPORT-CLASS-4 service. + +Replace the MAP-U-ABORT service as follows. + +### 7.1.1 MAP-U-ABORT service + +This service enables the service-user to request the MAP dialogue to be aborted. The service is an unconfirmed service with service-primitives as shown in table 7.1/1. MAP service-user in the GLR may set “application context not supported” as user reason. + +**Table 7.1/1: Service-primitives for the MAP-U-ABORT service** + +| Parameters | Request | Indication | +|------------------------|---------|------------| +| User reason | M | M(=) | +| Diagnostic information | U | C(=) | +| Specific information | U | C(=) | + +#### User reason: + +This parameter can take the following values: + +- resource limitation (congestion); +the requested user resource is unavailable due to congestion; +- resource unavailable; +the requested user resource is unavailable for reasons other than congestion; +- application procedure cancellation; +the procedure is cancelled for reason detailed in the diagnostic information parameter; +- application context not supported; +the requested application context is not supported; + +- procedure error; + +processing of the procedure is terminated for procedural reasons. + +#### Diagnostic information: + +This parameter may be used to give additional information for some of the values of the user-reason parameter: + +**Table 7.1/2: User reason and diagnostic information** + +| User reason | Diagnostic information | +|------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Resource limitation (congestion) | - | +| Resource unavailable | Short term/long term problem | +| Application procedure cancellation | Handover cancellation/
Radio Channel release/
Network path release/
Call release/
Associated procedure failure/
Tandem dialogue released/
Remote operations failure | +| Application context not supported | - | +| Procedure error | - | + +#### Specific information: + +This parameter may be used for passing any user specific information. Establishment and processing of the Specific information is not specified by GSM and shall be performed according to operator specific requirements. + +# 8 Mobility services + +## 8.1 General + +Regarding definition of each service, only the interval for adoption shall be considered for the GLR introduction. The interval for adoption for the GLR specification is described below. Service primitives and parameter definitions are as in 3GPP TS 29.002. + +## 8.2 Location Management services + +| Services | Interval for adoption | +|--------------------------|-----------------------| +| MAP_UPDATE_LOCATION | VLR – GLR | +| | GLR – HLR | +| MAP_CANCEL_LOCATION | HLR – GLR | +| | GLR – VLR | +| | GLR – SGSN | +| MAP_PURGE_MS | VLR – GLR | +| | SGSN – GLR | +| | GLR – HLR | +| MAP_UPDATE_GPRS_LOCATION | SGSN – GLR | +| | GLR – HLR | + +**Figure 8.2 /1** + +## 8.3 Authentication Management services + +| Services | Interval for adoption | +|---------------------------------------|-----------------------| +| MAP_SEND_AUTHENTICATION_IN
FO | VLR – GLR | +| | SGSN – GLR | +| | GLR – HLR | +| MAP_AUTHENTICATION_FAILURE
_REPORT | VLR – GLR | +| | SGSN – GLR | +| | GLR – HLR | + +Figure 8.3/1 + +## 8.4 Subscriber management services + +| Services | Interval for adoption | +|----------------------------|-----------------------| +| MAP_INSERT-SUBSCRIBER-DATA | HLR – GLR | +| | GLR – VLR | +| | GLR – SGSN | +| MAP-DELETE-SUBSCRIBER-DATA | HLR – GLR | +| | GLR – VLR | +| | GLR – SGSN | + +Figure 8.4/1 + +## 8.5 Fault recovery services + +| Services | Interval for adoption | +|-------------------------------------|-----------------------| +| MAP_RESET | HLR – GLR | +| | GLR – VLR | +| | GLR – SGSN | +| MAP_FORWARD_CHECK_SS_INDICA
TION | HLR – GLR | +| | GLR – VLR | +| MAP_RESTORE_DATA | VLR – GLR | + +Figure 8.5/1 + +## 8.6 Subscriber Information services + +| Services | Interval for adoption | +|-----------------------------|-----------------------| +| MAP-PROVIDE-SUBSCRIBER-Info | VLR – GLR | +| | GLR – HLR | + +Figure 8.6/1 + +# --- 9 Operation and maintenance services + +## 9.1 General + +Regarding definition of each service, only the interval for adoption shall be considered for the GLR introduction. The intervals for adoption for the GLR specification are described below. Service primitives and parameter definitions are as in 3GPP TS 29.002. + +## 9.2 MAP\_SEND\_IMSI service + +| Services | Interval for adoption | +|---------------|-----------------------| +| MAP_SEND_IMSI | HLR – GLR | +| | GLR – VLR | + +Figure 9.2/1 + +# --- 10 Call handling services + +## 10.1 General + +Regarding definition of each service, only the interval for adoption shall be considered for the GLR introduction. The intervals for adoption for the GLR specification are described below. Service primitives and parameter definitions are as in 3GPP TS 29.002. + +## 10.2 MAP\_PROVIDE\_ROAMING\_NUMBER service + +| Services | Interval for adoption | +|----------------------------|-----------------------| +| MAP_PROVIDE_ROAMING_NUMBER | HLR – GLR | +| | GLR – VLR | + +Figure 10.2/1 + +## 10.3 MAP\_SET\_REPORTING\_STATE service + +| Services | Interval for adoption | +|-------------------------|-----------------------| +| MAP_SET_REPORTING_STATE | HLR – GLR | +| | GLR – VLR | + +Figure 10.3/1 + +## 10.4 MAP\_STATUS\_REPORT service + +| Services | Interval for adoption | +|-------------------|-----------------------| +| MAP_STATUS_REPORT | VLR – GLR | +| | GLR – HLR | + +Figure 10.4/1 + +## 10.5 MAP\_REMOTE\_USER\_FREE service + +| Services | Interval for adoption | +|----------------------|-----------------------| +| MAP_REMOTE_USER_FREE | VLR – GLR | +| | GLR – HLR | + +Figure 10.5/1 + +# --- 11 Supplementary services related services + +## 11.1 General + +Regarding definition of each service, only the interval for adoption shall be considered for the GLR introduction. The intervals for adoption for the GLR specification are described below. Service primitives and parameter definitions are as in 3GPP TS 29.002. + +## 11.2 MAP\_REGISTER\_SS service + +| Services | Interval for adoption | +|-----------------|-----------------------| +| MAP_REGISTER_SS | VLR – GLR | +| | GLR – HLR | + +Figure 11.2/1 + +## 11.3 MAP\_ERASE\_SS service + +| Services | Interval for adoption | +|--------------|-----------------------| +| MAP_ERASE_SS | VLR – GLR | +| | GLR – HLR | + +Figure 11.3/1 + +## 11.4 MAP\_ACTIVATE\_SS service + +| Services | interval for adoption | +|-----------------|-----------------------| +| MAP_ACTIVATE_SS | VLR – GLR | +| | GLR – HLR | + +Figure 11.4/1 + +## 11.5 MAP\_DEACTIVATE\_SS service + +| Services | Interval for adoption | +|-------------------|-----------------------| +| MAP_DEACTIVATE_SS | VLR – GLR | +| | GLR – HLR | + +Figure 11.5/1 + +## 11.6 MAP\_INTERROGATE\_SS service + +| Services | Interval for adoption | +|--------------------|-----------------------| +| MAP_INTERROGATE_SS | VLR – GLR | +| | GLR – HLR | + +Figure 11.6/1 + +## 11.7 MAP\_REGISTER\_PASSWORD service + +| Services | Interval for adoption | +|-----------------------|-----------------------| +| MAP_REGISTER_PASSWORD | VLR – GLR | +| | GLR – HLR | + +Figure 11.7/1 + +## 11.8 MAP\_GET\_PASSWORD service + +| Services | Interval for adoption | +|------------------|-----------------------| +| MAP_GET_PASSWORD | HLR – GLR | +| | GLR – VLR | + +Figure 11.8/1 + +## 11.9 MAP\_PROCESS\_UNSTRUCTURED\_SS\_REQUEST service + +| Services | Interval for adoption | +|-------------------------------------|-----------------------| +| MAP_PROCESS_UNSTRUCTURED_SS_REQUEST | VLR – GLR | +| | GLR – HLR | + +Figure 11.9/1 + +## 11.10 MAP\_UNSTRUCTURED\_SS\_REQUEST service + +| Services | Interval for adoption | +|-----------------------------|-----------------------| +| MAP_UNSTRUCTURED_SS_REQUEST | HLR – GLR | +| | GLR – VLR | + +Figure 11.10/1 + +## 11.11 MAP\_UNSTRUCTURED\_SS\_NOTIFY service + +| Services | Interval for adoption | +|----------------------------|-----------------------| +| MAP_UNSTRUCTURED_SS_NOTIFY | HLR – GLR | +| | GLR – VLR | + +Figure 11.11/1 + +## 11.12 MAP\_REGISTER\_CC\_ENTRY service + +| Services | Interval for adoption | +|----------------------------|-----------------------| +| MAP_UNSTRUCTURED_SS_NOTIFY | VLR – GLR | +| | GLR – HLR | + +Figure 11.12/1 + +## 11.13 MAP\_ERASE\_CC\_ENTRY service + +| Services | Interval for adoption | +|---------------------|-----------------------| +| MAP_ERASE_CC_NOTIFY | VLR – GLR | +| | GLR – HLR | + +Figure 11.13/1 + +# 12 Short message service management services + +## 12.1 General + +Regarding definition of each service, only the interval for adoption shall be considered for the GLR introduction. The intervals for adoption for the GLR specification are described below. Service primitives and parameter definitions are as in 3GPP TS 29.002. + +## 12.2 MAP-READY-FOR-SM service + +| Services | interval for adoption | +|------------------|-----------------------| +| MAP-READY-FOR-SM | VLR – GLR | +| | SGSN – GLR | +| | GLR – HLR | + +Figure 12.2/1 + +## 12.3 MAP-MT-FORWARD-SHORT-MESSAGE service + +| Services | interval for adoption | +|------------------------------|-----------------------| +| MAP_MT_FORWARD_SHORT_MESSAGE | SMS-GMSC – IM-MSC | +| | IM-MSC – MSC | +| | SMS-GMSC – GLR | +| | GLR – SGSN | + +Figure 12.3/1 + +# 13 Network-Requested PDP Context Activation services + +## 13.1 General + +Regarding definition of each service, only the interval for adoption shall be considered for the GLR introduction. The intervals for adoption for the GLR specification are described below. Service primitives and parameter definitions are as in 3GPP TS 29.002. + +## 13.2 MAP\_SEND\_ROUTING\_INFO\_FOR\_GPRS service + +| Services | Interval for adoption | +|--------------------------------|-----------------------| +| MAP_SEND_ROUTING_INFO_FOR_GPRS | IM-GSN – GLR | + +Figure 13.2/1 + +## 13.3 MAP\_FAILURE\_REPORT service + +| Services | Interval for adoption | +|--------------------|-----------------------| +| MAP_FAILURE_REPORT | IM-GSN – GLR | + +Figure 13.3/1 + +# --- 14 Void + +# 15 Element of procedure + +The elements of procedures for the MAP protocol are referred to the corresponding section in 3GPP TS 29.002002 with the exceptions described below. + +## 15.1 SDL descriptions + +Replace the corresponding part of Process Secure\_MAP\_DSM as figure 15.1/1. + +![State transition diagram for Process Secure_MAP_DSM_GLR. The diagram shows transitions between states DIALOGUE_ACCEPTED, DIALOGUE_ESTABLISHED, and IDLE based on various MAP and TC primitives and conditions.](e180f2b5fcbe8001554a7c0677cd3f82_img.jpg) + +Process Secure\_MAP\_DSM\_GLR 15.1.1(1) + +Process to manage a MAP dialogue + +``` + +stateDiagram-v2 + [*] --> DIALOGUE_ACCEPTED + DIALOGUE_ACCEPTED --> MAP_REQ + DIALOGUE_ACCEPTED --> MAP_rsp + DIALOGUE_ACCEPTED --> MAP_DELIMITER_req + MAP_REQ --> Secure_Transport_required + Secure_Transport_required --> Requesting_MAP_SSM : (TRUE) + Secure_Transport_required --> Service_Invoked_VIA_Intern2 : (FALSE) + Requesting_MAP_SSM --> Service_Invoked_VIA_Intern2 + Service_Invoked_VIA_Intern2 --> DIALOGUE_ESTABLISHED + MAP_rsp --> Secure_Transport_required + Secure_Transport_required --> Response_Issued_VIA_Intern1 : (TRUE) + Secure_Transport_required --> Response_Issued_VIA_Intern3 : (FALSE) + Response_Issued_VIA_Intern1 --> DIALOGUE_ACCEPTED + Response_Issued_VIA_Intern3 --> DIALOGUE_ACCEPTED + MAP_DELIMITER_req --> TC_CONTINUE_req_VIA_TC1 + TC_CONTINUE_req_VIA_TC1 --> DIALOGUE_ESTABLISHED + DIALOGUE_ESTABLISHED --> MAP_CLOSE_req + DIALOGUE_ESTABLISHED --> MAP_U_ABORT_req + MAP_CLOSE_req --> TC_END_req_VIA_TC1 + TC_END_req_VIA_TC1 --> Secure_Transport_required + Secure_Transport_required --> Terminated_VIA_Intern1 : (FALSE) + Secure_Transport_required --> Terminated_VIA_Intern3 : (TRUE) + Terminated_VIA_Intern1 --> To_all_active_PSSMs + Terminated_VIA_Intern3 --> To_all_active_SPSSMs + Terminated_VIA_Intern1 --> Terminated_VIA_Intern2 + Terminated_VIA_Intern3 --> Terminated_VIA_Intern4 + Terminated_VIA_Intern2 --> To_all_active_RSSMs + Terminated_VIA_Intern4 --> To_all_active_SRSSMs + To_all_active_PSSMs --> IDLE + To_all_active_RSSMs --> IDLE + To_all_active_SPSSMs --> IDLE + To_all_active_SRSSMs --> IDLE + MAP_U_ABORT_req --> User_reason_AC_not_supported + User_reason_AC_not_supported --> Abort_reason_User_specific : yes + User_reason_AC_not_supported --> Abort_reason_AC_not_supported : no + Abort_reason_User_specific --> User_info_MAP_UserAbortInfo + User_info_MAP_UserAbortInfo --> TC_U_ABORT_req_VIA_TC1 + Abort_reason_AC_not_supported --> TC_U_ABORT_req_VIA_TC1 + TC_U_ABORT_req_VIA_TC1 --> Secure_Transport_required + +``` + +State transition diagram for Process Secure\_MAP\_DSM\_GLR. The diagram shows transitions between states DIALOGUE\_ACCEPTED, DIALOGUE\_ESTABLISHED, and IDLE based on various MAP and TC primitives and conditions. + +Figure 15.1/1: Process Secure\_MAP\_DSM\_GLR + +# 16 Mapping onto TC services + +Dialogue control, Service specific procedures and SDL descriptions are referred to the corresponding section in 3GPP TS 29.002. + +# 17 Abstract syntax of the MAP protocol + +## 17.1 General + +Refer to the corresponding section in 3GPP TS 29.002 except Packages specifications and Application contexts. + +Regarding the operations which are initiated by the VLR or SGSN toward HLR via GLR, the timer value used in the operations should be configured enough long to guarantee the GLR specific fallback mechanism. + +## 17.2 Packages specifications + +Regarding Packages specifications, only the supplier and consumer definition shall be considered for the GLR introduction. The supplier and consumer definition for the GLR specification are derived Table 17.2/1. For the other definitions of the package specifications are as in 3GPP TS 29.002. + +**Table 17.2/1: supplier and consumer definition** + +| Operation Package | supplier | consumer | +|----------------------------------------|-----------------|-----------------| +| LocationUpdatingPackage-v3 | HLR | GLR | +| | GLR | VLR | +| LocationCancellationPackage-v3 | VLR or SGSN | GLR | +| | GLR | HLR | +| RoamingNumberEnquiryPackage-v3 | VLR | GLR | +| | GLR | HLR | +| InfoRetrievalPackage-v2 | HLR | GLR | +| | GLR | VLR | +| | GLR | SGSN | +| InfoRetrievalPackage-v1 | HLR | GLR | +| | GLR | VLR | +| | GLR | SGSN | +| IMSIRetrievalPackage-v2 | HLR | GLR | +| | GLR | VLR | +| SubscriberDataMngtStandAlonePackage-v3 | VLR or SGSN | GLR | +| | GLR | HLR | +| SubscriberDataMngtPackage-v3 | VLR or SGSN | GLR | +| | GLR | HLR | +| ResetPackage-v2 | VLR or SGSN | GLR | +| | GLR | HLR | +| FunctionalSsPackage-v2 | HLR | GLR | +| | GLR | HLR | +| BindingPackage-v1 | HLR | GLR | +| | GLR | VLR | +| UnstructuredSsPackage-v2 | HLR | GLR | +| | GLR | VLR | +| UnstructuredSsPackage-v1 | HLR | GLR | +| | GLR | VLR | +| MTShortMsgRelayPackage-v3 | IM-MSC or | GMSC | +| | GLR | | +| | MSC | IM-MSC | +| | SGSN | GLR | +| MwdMngtPackage-v3 | HLR | GLR | +| | GLR | SGSN | +| | GLR | VLR | +| MwdMngtPackage-v1 | HLR | GLR | +| | GLR | VLR | +| DataRestorationPackage-v3 | GLR | VLR | +| PurgingPackage-v3 | HLR | GLR | +| | GLR | VLR | +| | GLR | SGSN | +| SubscriberInformationEnquiryPackage-v3 | VLR | GLR | +| | GLR | HLR | + +| Operation Package | supplier | consumer | +|---------------------------------------|----------------------------------------------------------------------------------------------------------------------------|-----------------| +| GprsLocationUpdatingPackage-v3 | HLR | GLR | +| | GLR | SGSN | +| FailureReportingPackage-v3 | GLR | IM-GSN | +| SetReportingStatePackage-v3 | VLR | GLR | +| | GLR | HLR | +| StatusReportPackage-v3 | HLR | GLR | +| | GLR | VLR | +| RemoteUserFreePackage-v3 | VLR | GLR | +| | GLR | HLR | +| CallCompletionPackage-v3 | HLR | GLR | +| | GLR | VLR | +| AuthenticationFailureReportPackage-v3 | HLR | GLR | +| | GLR | VLR | +| | GLR | SGSN | +| SecureTransportHandlingPackage-v3 | This operation package includes the operations required for the secure transport of MAP messages between any MAP entities. | | + +## 17.3 Application contexts + +Regarding Application contexts specifications, only the responder and initiator definition shall be considered for the GLR introduction. The responder and initiator definition for the GLR specification are derived Table 17.3/1. For the other definitions of the package specifications are as in 3GPP TS 29.002. + +**Table 17.3/1: supplier and consumer definition** + +| Application Context | Version | Initiator | Responder | +|------------------------------------|---------|-----------------------------------------------------------------------------------------------------|----------------| +| locationCancellationContext | v3 | HLR | GLR | +| | | GLR | VLR or SGSN | +| imsiRetrievalContext | v2 | VLR | GLR | +| | | GLR | HLR | +| infoRetrievalContext | v2 | VLR or SGSN | GLR | +| | | GLR | HLR | +| mwdMngtContext | v3 | VLR or SGSN | GLR | +| | | GLR | HLR | +| msPurgingContext | v3 | VLR or SGSN | GLR | +| | | GLR | HLR | +| resetContext | v2 | HLR | GLR | +| | | GLR | VLR or SGSN | +| networkUnstructuredSsContext | v2 | VLR | GLR | +| | | GLR | HLR | +| | | HLR | GLR | +| | | GLR | VLR | +| networkFunctionalSsContext | v2 | VLR | GLR | +| | | GLR | HLR | +| shortMsgMT-RelayContext | v3 | MSC | IM- MSC or GLR | +| | | IM- MSC | MSC | +| | | GLR | SGSN | +| networkLocUpContext | v3 | VLR | GLR | +| | | GLR | HLR | +| gprsLocationUpdateContext | v3 | SGSN | GLR | +| | | GLR | HLR | +| subscriberDataMngtContext | v3 | HLR | GLR | +| | | GLR | VLR or SGSN | +| roamingNumberEnquiryContext | v3 | HLR | GLR | +| | | GLR | VLR | +| gprsLocationInfoRetrievalContext | v3 | IM-GSN | GLR | +| failureReportContext | v3 | IM-GSN | GLR | +| subscriberInfoEnquiryContext | v3 | HLR | GLR | +| | | GLR | VLR | +| reportingContext | v3 | VLR | GLR | +| | | GLR | HLR | +| | | HLR | GLR | +| | | GLR | VLR | +| callCompletionContext | v3 | VLR | GLR | +| | | GLR | HLR | +| authenticationFailureReportContext | v3 | VLR or SGSN | GLR | +| | | GLR | HLR | +| SecureTransportHandlingContext | v3 | This application context is used for the secure transport of MAP messages between any MAP entities. | | + +# 18 General on MAP user procedure + +Refer to 3GPP TS 29.002 for general matters for procedure description such as notation convention, version handling at dialogue establishment and interaction between MAP provider and MAP users. + +# 19 Mobility procedures + +## 19.1 Location management Procedures + +For non-GPRS subscribers, this subclause comprises a number of processes to handle the mobile nature of the subscriber. The processes will be addressed by SCCP SSN (VLR or HLR) and the Application Context. The processes in the GLR interact with the processes in the VLR or HLR defined in 29.002. The followings show the relations between the protocol processes in the GLR and the processes in the other node. + +Process Update Location (VLR-GLR): + +- Initiator: Update\_Location\_Area\_VLR or Update\_Location\_HLR; +- Responder: Update\_Location\_GLR. + +Process Update Location (GLR-HLR): + +- Initiator: GLR\_Update\_Location\_HLR; +- Responder: Update\_Location\_HLR. + +Process Cancel Location (VLR-GLR): + +- Initiator: GLR\_Cancel\_Location\_VLR; +- Responder: Cancel\_Location\_VLR. + +Process Cancel Location (GLR-HLR): + +- Initiator: Cancel\_Location\_HLR; +- Responder: Cancel\_Location\_GLR. + +Process Purge MS (VLR-GLR): + +- Initiator: Purge\_MS\_VLR; +- Responder: Purge\_MS\_GLR. + +Process Purge MS (GLR-HLR): + +- Initiator: GLR\_Purge\_MS\_HLR; +- Responder: Purge\_MS\_HLR. + +A Location Management Co-ordinator in the GLR co-ordinates the two protocol processes “Update\_Location\_GLR” (subclause 19.1.2) and “RESTORE\_DATA\_GLR” (subclause 19.2) that are addressed by the same application context. + +On receipt of a dialogue request for the Location Management Application Context, the location Management\_Coordinator\_GLR will: + +- Terminate the process in case of parameter problems; or +- Revert to MAP version Vr protocol if the VLR requests version Vr protocol; or +- Continue as described in the following, if the dialogue is accepted. + +The protocol process is created depending on the first primitive received from the MAP service provider within this dialogue: + +- Update\_Location\_GLR if the primitive is a MAP\_UPDATE\_LOCATION indication. +- RESTORE\_DATA\_GLR if the primitive is a MAP\_RESTORE\_DATA indication. + +If a MAP\_NOTICE indication is received instead, the dialogue towards the VLR is terminated and the process returns to idle state. + +After creation of the protocol process the service primitive received from the MAP service-provider is passed to the protocol process. Henceforth, the co-ordinator will relay all service primitives from MAP service-provider to the MAP service-user and vice versa, until a request or indication for dialogue termination is received. This last primitive will be relayed, too, before the Co-ordinator process returns to idle state. + +![Flowchart of Process Location_Management_Coordinator_GLR. The process starts with an oval, leading to a 'NULL' oval. It then enters a 'Receive_Open_Ind' box, which points to 'Section 25.1'. From 'Receive_Open_Ind', three paths emerge: 'OK' leads to 'WAIT_FOR_SERVICE_PRIMITIVE'; 'Vr' leads to 'Perform_MAP_Vr_Dialogue' which ends at 'NULL'; 'Error' leads directly to 'NULL'. 'WAIT_FOR_SERVICE_PRIMITIVE' branches into three parallel paths: 1) 'MAP_UPDATE_LOCATION_Ind' -> 'Update_Location_GLR' -> 'MAP_UPDATE_LOCATION_Ind' (diamond) -> 'RELAY_INFO'; 2) 'MAP_RESTORE_DATA_Ind' -> 'RESTORE_DATA_GLR' -> 'MAP_RESTORE_DATA_Ind' (diamond) -> 'RELAY_INFO'; 3) 'MAP_NOTICE_Ind' -> 'MAP_CLOSE_Req' (diamond) -> 'NULL'. All three 'RELAY_INFO' ovals converge to a central junction. From this junction, four paths emerge: 1) 'from Provider' (diamond) -> 'to OFFSPRING' (diamond) -> 'RELAY_INFO' oval; 2) 'from OFFSPRING' (diamond) -> 'to Provider' (diamond) -> 'RELAY_INFO' oval; 3) 'MAP-U-ABORT_Req, MAP-CLOSE_Req from OFFSPRING' (diamond) -> 'to Provider' (diamond) -> 'NULL' oval; 4) 'MAP-P-ABORT_Ind, MAP-U-ABORT_Ind, MAP-CLOSE_Ind' (diamond) -> 'to OFFSPRING' (diamond) -> 'NULL' oval.](e90987faabad6a6665cd8ed1151dc474_img.jpg) + +**Process Location\_Management\_Coordinator\_GLR** 19.1.1.1(1) + +Location management coordination process in the GLR + +``` + +graph TD + Start([ ]) --> NULL1([NULL]) + NULL1 --> Receive_Open_Ind[Receive_Open_Ind] + Receive_Open_Ind --> Section_25_1[Section 25.1] + Receive_Open_Ind --> OK[OK] + Receive_Open_Ind --> Vr[Vr] + Receive_Open_Ind --> Error[Error] + OK --> WAIT_FOR_SERVICE_PRIMITIVE([WAIT_FOR_SERVICE_PRIMITIVE]) + WAIT_FOR_SERVICE_PRIMITIVE --> MAP_UPDATE_LOCATION_Ind[MAP_UPDATE_LOCATION_Ind] + WAIT_FOR_SERVICE_PRIMITIVE --> MAP_RESTORE_DATA_Ind[MAP_RESTORE_DATA_Ind] + WAIT_FOR_SERVICE_PRIMITIVE --> MAP_NOTICE_Ind[MAP_NOTICE_Ind] + MAP_UPDATE_LOCATION_Ind --> Update_Location_GLR[Update_Location_GLR] + Update_Location_GLR --> MAP_UPDATE_LOCATION_Ind_Diamond{MAP_UPDATE_LOCATION_Ind} + MAP_RESTORE_DATA_Ind --> RESTORE_DATA_GLR[RESTORE_DATA_GLR] + RESTORE_DATA_GLR --> MAP_RESTORE_DATA_Ind_Diamond{MAP_RESTORE_DATA_Ind} + MAP_NOTICE_Ind --> MAP_CLOSE_Req_Diamond{MAP_CLOSE_Req} + MAP_CLOSE_Req_Diamond --> NULL2([NULL]) + MAP_UPDATE_LOCATION_Ind_Diamond --> RELAY_INFO1([RELAY_INFO]) + MAP_RESTORE_DATA_Ind_Diamond --> RELAY_INFO2([RELAY_INFO]) + RELAY_INFO1 --> Junction(( )) + RELAY_INFO2 --> Junction + Junction --> from_Provider{from Provider} + Junction --> from_OFFSPRING{from OFFSPRING} + Junction --> MAP_U_ABORT_Req{MAP-U-ABORT_Req, MAP-CLOSE_Req from OFFSPRING} + Junction --> MAP_P_ABORT_Ind{MAP-P-ABORT_Ind, MAP-U-ABORT_Ind, MAP-CLOSE_Ind} + from_Provider --> to_OFFSPRING1{to OFFSPRING} + to_OFFSPRING1 --> RELAY_INFO3([RELAY_INFO]) + from_OFFSPRING --> to_Provider1{to Provider} + to_Provider1 --> RELAY_INFO4([RELAY_INFO]) + MAP_U_ABORT_Req --> to_Provider2{to Provider} + to_Provider2 --> NULL3([NULL]) + MAP_P_ABORT_Ind --> to_OFFSPRING2{to OFFSPRING} + to_OFFSPRING2 --> NULL4([NULL]) + +``` + +Flowchart of Process Location\_Management\_Coordinator\_GLR. The process starts with an oval, leading to a 'NULL' oval. It then enters a 'Receive\_Open\_Ind' box, which points to 'Section 25.1'. From 'Receive\_Open\_Ind', three paths emerge: 'OK' leads to 'WAIT\_FOR\_SERVICE\_PRIMITIVE'; 'Vr' leads to 'Perform\_MAP\_Vr\_Dialogue' which ends at 'NULL'; 'Error' leads directly to 'NULL'. 'WAIT\_FOR\_SERVICE\_PRIMITIVE' branches into three parallel paths: 1) 'MAP\_UPDATE\_LOCATION\_Ind' -> 'Update\_Location\_GLR' -> 'MAP\_UPDATE\_LOCATION\_Ind' (diamond) -> 'RELAY\_INFO'; 2) 'MAP\_RESTORE\_DATA\_Ind' -> 'RESTORE\_DATA\_GLR' -> 'MAP\_RESTORE\_DATA\_Ind' (diamond) -> 'RELAY\_INFO'; 3) 'MAP\_NOTICE\_Ind' -> 'MAP\_CLOSE\_Req' (diamond) -> 'NULL'. All three 'RELAY\_INFO' ovals converge to a central junction. From this junction, four paths emerge: 1) 'from Provider' (diamond) -> 'to OFFSPRING' (diamond) -> 'RELAY\_INFO' oval; 2) 'from OFFSPRING' (diamond) -> 'to Provider' (diamond) -> 'RELAY\_INFO' oval; 3) 'MAP-U-ABORT\_Req, MAP-CLOSE\_Req from OFFSPRING' (diamond) -> 'to Provider' (diamond) -> 'NULL' oval; 4) 'MAP-P-ABORT\_Ind, MAP-U-ABORT\_Ind, MAP-CLOSE\_Ind' (diamond) -> 'to OFFSPRING' (diamond) -> 'NULL' oval. + +**Figure 19.1.1/1: Process Location\_Management\_Coordinator\_GLR** + +For GPRS subscribers, this subclause comprises a number of other processes to handle the mobile nature of the subscriber. The processes will be addressed by SCCP Sub-System Number (SGSN or HLR) and the Application + +Context. The processes in the GLR interact with the processes in the VLR, SGSN or HLR defined in 29.002. The followings show the relations between the processes in the GLR and the processes in the other node: + +Process GPRS Update Location (VLR or SGSN-GLR): + +Initiator: GPRS\_Update\_Location\_Area\_VLR, or SGSN\_Update\_HLR. + +Responder: Update\_GPRS\_Location\_GLR. + +Process GPRS Update Location (GLR-HLR): + +Initiator: GLR\_Update\_GPRS\_Location\_HLR. + +Responder: Update\_GPRS\_Location\_HLR. + +Process Cancel Location (SGSN-GLR): + +Initiator: GLR\_Cancel\_Location\_SGSN. + +Responder: Cancel\_Location\_SGSN. + +Process Cancel Location (GLR-HLR): + +Initiator: Cancel\_GPRS\_Location\_HLR. + +Responder: Cancel\_GPRS\_Location\_GLR. + +Process Purge MS (SGSN-GLR): + +Initiator: Purge\_MS\_SGSN. + +Responder: Purge\_MS\_GLR\_for\_GPRS. + +Process Purge MS (GLR-HLR): + +Initiator: GLR\_Purge\_MS\_HLR\_for\_GPRS. + +Responder: Purge\_MS\_HLR. + +### 19.1.1 Location updating + +#### 19.1.1.1 General + +This location updating procedure is used to update the location information held in the network. + +If the GLR is located between the VLR and the HLR, the MAP\_UPDATE\_LOCATION service is invoked towards the GLR whose identity is contained in the VLR table. When the GLR receives a MAP\_UPDATE\_LOCATION indication, it determines whether it invokes the MAP\_UPDATE\_LOCATION service towards the HLR, and invokes it if necessary. + +If the GLR is located between the SGSN and the HLR, the MAP\_UPDATE\_GPRS\_LOCATION service is invoked towards the GLR whose identity is contained in the SGSN table. When the GLR receives a MAP\_UPDATE\_GPRS\_LOCATION indication, it determines whether it invokes the MAP\_UPDATE\_GPRS\_LOCATION service towards the HLR, and invokes it if necessary. + +![Sequence diagram showing network interfaces and services for location updating between VLR/SGSN, GLR, HLR, and PGLR/PVLR/PSGSN.](28d75f39a24203712ee907b32cf0bbe5_img.jpg) + +``` + +sequenceDiagram + participant VLR_SGSN as VLR/SGSN + participant GLR + participant HLR + participant PGLR_PVLR_PSGSN as PGLR/PVLR/PSGSN + + VLR_SGSN->>GLR: MAP UPDATE_LOCATION +or MAP UPDATE GPRS LOCATION + GLR->>HLR: MAP UPDATE_LOCATION +or MAP UPDATE GPRS LOCATION + HLR->>PGLR_PVLR_PSGSN: MAP_CANCEL_LOCATION + PGLR_PVLR_PSGSN-->>HLR: MAP_CANCEL_LOCATION ack + + HLR-->>GLR: MAP INSERT SUBSCRIBER DATA + GLR-->>VLR_SGSN: MAP INSERT SUBSCRIBER DATA + + VLR_SGSN->>GLR: MAP INSERT SUBSCRIBER DATA ack + GLR->>HLR: MAP INSERT SUBSCRIBER DATA ack + + HLR-->>GLR: MAP CHECK SS INDICATION + GLR-->>VLR_SGSN: MAP CHECK SS INDICATION + + HLR-->>GLR: MAP UPDATE_LOCATION ack +or MAP UPDATE GPRS LOCATION ack + GLR-->>VLR_SGSN: MAP UPDATE_LOCATION ack +or MAP UPDATE GPRS LOCATION ack + +``` + +Sequence diagram showing network interfaces and services for location updating between VLR/SGSN, GLR, HLR, and PGLR/PVLR/PSGSN. + +**Figure 19.1.2/1: Interface and services for Location updating** + +#### 19.1.1.2 Detailed procedure in the GLR + +Figure 19.1.2/2 shows the Process Update\_Location\_GLR. This process is a GLR MAP protocol machine handling location updating and is a responder to the VLR. + +![State transition diagram for Process Update_Location_GLR. The diagram shows a sequence of states and transitions starting from an initial state, through waiting for a service primitive, handling an update location indication, and then branching based on the application response (Ack, Negative Response, Insert Subscriber Data, Forward check SS indication, or Abort).](dd5771673aececa53d42ece89218299d_img.jpg) + +### Process Update\_Location\_GLR + +19.1.2.2\_1(3) + +GLR MAP protocol machine handling location updating and interfacing with VLR MAP protocol machine + +Left to VLR +Right to GLR application + +``` +stateDiagram-v2 + [*] --> WAIT_FOR_SERVICE_PRIMITIVE + WAIT_FOR_SERVICE_PRIMITIVE --> MAP_Update_Location_ind + MAP_Update_Location_ind --> Update_Location + Update_Location --> 2 + 2 --> WAIT_FOR_APPLICATION_RESPONSE + WAIT_FOR_APPLICATION_RESPONSE --> Update_Location_Ack + WAIT_FOR_APPLICATION_RESPONSE --> Update_Location_Negative_Response + WAIT_FOR_APPLICATION_RESPONSE --> Insert_Subscriber_Data + WAIT_FOR_APPLICATION_RESPONSE --> Forward_check_SS_indication + WAIT_FOR_APPLICATION_RESPONSE --> Abort + Update_Location_Ack --> Set_result + Set_result --> MAP_UPDATE_LOCATION_Rsp_MAP_CLOSE_Req_1 + Update_Location_Negative_Response --> Set_Error + Set_Error --> MAP_UPDATE_LOCATION_Rsp_MAP_CLOSE_Req_2 + Insert_Subscriber_Data --> 1 + Forward_check_SS_indication --> WAIT_FOR_APPLICATION_RESPONSE_2 + WAIT_FOR_APPLICATION_RESPONSE_2 --> MAP_FORWARD_CHECK_SS_INDICATION_req_MAP_DELIMITER_req + Abort --> MAP_U_ABORT_req + MAP_UPDATE_LOCATION_Rsp_MAP_CLOSE_Req_1 --> [*] + MAP_UPDATE_LOCATION_Rsp_MAP_CLOSE_Req_2 --> [*] + MAP_FORWARD_CHECK_SS_INDICATION_req_MAP_DELIMITER_req --> [*] + MAP_U_ABORT_req --> [*] +``` + +**States:** + +- Initial State (oval) +- WAIT\_FOR\_SERVICE\_PRIMITIVE (oval) +- MAP\_Update\_Location\_ind (diamond) +- Update\_Location (parallelogram) +- 2 (circle connector) +- WAIT\_FOR\_APPLICATION\_RESPONSE (oval) +- Update\_Location\_Ack (diamond) +- Update\_Location\_Negative\_Response (diamond) +- Insert\_Subscriber\_Data (diamond) +- Forward\_check\_SS\_indication (diamond) +- Abort (diamond) +- Set\_result (rectangle) +- Set\_Error (rectangle) +- WAIT\_FOR\_APPLICATION\_RESPONSE\_2 (oval) + +**Transitions and Messages:** + +- From **Update\_Location\_Ack**: Set result -> MAP\_UPDATE\_LOCATION\_Rsp. MAP\_CLOSE\_Req. +- From **Update\_Location\_Negative\_Response**: Set Error -> MAP\_UPDATE\_LOCATION\_Rsp. MAP\_CLOSE\_Req. +- From **Insert\_Subscriber\_Data**: 1 (circle connector). +- From **Forward\_check\_SS\_indication**: WAIT\_FOR\_APPLICATION\_RESPONSE\_2 -> MAP\_FORWARD\_CHECK\_SS\_INDICATION\_req MAP\_DELIMITER\_req. +- From **Abort**: MAP\_U\_ABORT\_req. + +State transition diagram for Process Update\_Location\_GLR. The diagram shows a sequence of states and transitions starting from an initial state, through waiting for a service primitive, handling an update location indication, and then branching based on the application response (Ack, Negative Response, Insert Subscriber Data, Forward check SS indication, or Abort). + +Figure 19.1.2/2 (sheet 1 of 3): Process Update\_Location\_GLR + +![State transition diagram for Process Update_Location_GLR. The process starts at state 1, transitions to a waiting state, then branches based on MAP indications (Cnf, Abort, NOTICE). The Cnf path leads to a confirmation check and then to state 2. The Abort path ends. The NOTICE path leads to a negative response and then to state 2.](00504fc688ebcf131ccbeff94dfc9939_img.jpg) + +### Process Update\_Location\_GLR + +19.1.2.2\_2(3) + +``` +stateDiagram-v2 + [*] --> 1 + 1 --> WAIT + state "WAIT_FOR_ISD_Cnf
WAIT_FOR_SUBSEQUENT_APPLICATION_RESPONSE" as WAIT + WAIT --> MAP_Insert_Subscriber_Data_Cnf + WAIT --> MAP_U_ABORT_Ind + WAIT --> MAP_NOTICE_Ind + MAP_INSERT_SUBSCRIBER_DATA_REQ[MAP_Insert_Subscriber_Data_Req
MAP_Delimiter_Req] --> WAIT + MAP_INSERT_SUBSCRIBER_DATA_CNF[MAP_Insert_Subscriber_Data_Cnf] --> CHECK[Check Confirmation] + CHECK --> OK + CHECK --> PE[Provider error
Data error] + CHECK --> UE[User error] + OK --> INSERT[Insert_Subscriber_Data_Cnf] + INSERT --> 2 + PE --> SNR[Set Negative Response
System Failure] + UE --> MUE[MAP User Error
to Negative Response] + SNR --> ISDNR[ISD Negative Response] + MUE --> ISDNR + ISDNR --> 2 + MAP_U_ABORT_Ind --> ABORT[Abort] + ABORT --> X[ ] + style X fill:none,stroke:none + MAP_NOTICE_Ind --> SNF[Set Negative Result
System Failure] + SNF --> ISDNR2[ISD Negative Response] + ISDNR2 --> 2 +``` + +GLR MAP protocol machine handling location updating and interfacing with VLR MAP protocol machine + +Left to VLR +Right to GLR application + +MAP\_Insert\_Subscriber\_Data\_Req +MAP\_Delimiter\_Req + +WAIT\_FOR\_ISD\_Cnf +WAIT\_FOR\_SUBSEQUENT\_APPLICATION\_RESPONSE + +MAP\_Insert\_Subscriber\_Data\_Cnf + +MAP\_U\_ABORT\_Ind +MAP\_P\_ABORT\_Ind +MAP\_CLOSE\_Ind + +Abort + +MAP\_NOTICE\_Ind + +Set Negative Result +System Failure + +ISD Negative Response + +Check Confirmation + +Section 25.2 + +OK + +Provider error +Data error + +User error + +Insert\_Subscriber\_Data\_Cnf + +Set Negative Response +System Failure + +MAP User Error +to Negative Response + +ISD Negative Response + +1 + +2 + +State transition diagram for Process Update\_Location\_GLR. The process starts at state 1, transitions to a waiting state, then branches based on MAP indications (Cnf, Abort, NOTICE). The Cnf path leads to a confirmation check and then to state 2. The Abort path ends. The NOTICE path leads to a negative response and then to state 2. + +Figure 19.1.2/2 (sheet 2 of 3): Process Update\_Location\_GLR + +![State transition diagram for Process Update_Location_GLR. The diagram shows four main paths from a common 'WAIT' state. Path 1: 'Update Location Ack' leads to 'Set result', which then leads to a merge point for 'MAP_UPDATE_LOCATION_Rsp.' and 'MAP_CLOSE_Req.'. Path 2: 'Update Location Negative Response' leads to 'Set Error', which also leads to the same merge point. Path 3: 'Insert Subscriber Data' leads to a circle labeled '1'. Path 4: 'Abort' leads to 'MAP_U_ABORT_Req.', which ends in an 'X' (error state). The initial 'WAIT' state is labeled with 'WAIT_FOR_ISD_Cnf' and 'WAIT_FOR_SUBSEQUENT_APPLICATION_RESPONSE'.](e05b36c0d46549e681ce6581422c66b2_img.jpg) + +### Process Update\_Location\_GLR + +19.1.2.2\_3(3) + +GLR MAP protocol machine handling location updating and interfacing with VLR MAP protocol machine + +Left to VLR +Right to GLR application + +``` +stateDiagram-v2 + [*] --> WAIT + state "WAIT_FOR_ISD_Cnf
WAIT_FOR_SUBSEQUENT_APPLICATION_RESPONSE" as WAIT + WAIT --> UpdateLocationAck[Update Location Ack] + UpdateLocationAck --> SetResult[Set result] + SetResult --> Merge(( )) + WAIT --> UpdateLocationNeg[Update Location Negative Response] + UpdateLocationNeg --> SetError[Set Error] + SetError --> Merge + WAIT --> InsertSubscriberData[Insert Subscriber Data] + InsertSubscriberData --> One((1)) + WAIT --> Abort[Abort] + Abort --> MAPUAbortReq[MAP_U_ABORT_Req.] + MAPUAbortReq --> X((X)) + Merge --> MAPUpdateLocationRsp[MAP_UPDATE_LOCATION_Rsp.] + Merge --> MAPCloseReq[MAP_CLOSE_Req.] + MAPUpdateLocationRsp --> X + MAPCloseReq --> X +``` + +State transition diagram for Process Update\_Location\_GLR. The diagram shows four main paths from a common 'WAIT' state. Path 1: 'Update Location Ack' leads to 'Set result', which then leads to a merge point for 'MAP\_UPDATE\_LOCATION\_Rsp.' and 'MAP\_CLOSE\_Req.'. Path 2: 'Update Location Negative Response' leads to 'Set Error', which also leads to the same merge point. Path 3: 'Insert Subscriber Data' leads to a circle labeled '1'. Path 4: 'Abort' leads to 'MAP\_U\_ABORT\_Req.', which ends in an 'X' (error state). The initial 'WAIT' state is labeled with 'WAIT\_FOR\_ISD\_Cnf' and 'WAIT\_FOR\_SUBSEQUENT\_APPLICATION\_RESPONSE'. + +Figure 19.1.2/2 (sheet 3 of 3): Process Update\_Location\_GLR + +Figure 19.1.2/3 shows the Process GLR\_Update\_Location\_HLR. This process is a GLR MAP protocol machine handling location updating and is an initiator to the HLR. + +Sheet 1: If the Macro Open\_Receive\_Cnf results Vr, the process requests to perform MAP Vr. It causes a request for sending an abort message to Process Update\_Location\_GLR. + +![Flowchart for Process GLR_Update_Location_HLR. The process starts at an oval, goes to an IDLE state (oval), then an Update Location transition (chevron). It then reaches a decision diamond where it sends MAP_OPEN_Req, MAP_UPDATE_LOCATION_Req, and MAP_DELIMITER_Req to the right. It then enters a Receive Open Cnf state (double rectangle), which is linked to Section 25.1. From this state, three paths emerge: OK leads to Wait_For_HLR_Response (oval); Vr leads to Perform MAP Vr (diamond); Error leads to Set error (rectangle) and then Update Location Negative Response (chevron). Both Perform MAP Vr and Update Location Negative Response lead to end symbols (crossed lines).](5478f70a6cef3e5672b2b22d28830cfb_img.jpg) + +### Process GLR\_Update\_Location\_HLR + +19.1.2.3\_1(3) + +GLR MAP protocol machine handling Location Management and interfacing to HLR MAP protocol machine, handling Location Management. + +Signals to/from the left are to/from the GLR application. +Signals to/from the right are to/from the HLR MAP protocol machine. + +``` +graph TD; Start([ ]) --> IDLE([IDLE]); IDLE --> UpdateLocation{Update Location}; UpdateLocation --> Decision{ }; Decision --> MAP_Req["MAP_OPEN_Req
MAP_UPDATE_LOCATION_Req
MAP_DELIMITER_Req"]; Decision --> ReceiveOpenCnf[Receive Open Cnf]; ReceiveOpenCnf --> Section251[Section 25.1]; ReceiveOpenCnf -- OK --> WaitForHLRResponse([Wait_For_HLR_Response]); ReceiveOpenCnf -- Vr --> PerformMAPVr{Perform MAP Vr}; PerformMAPVr --> End1[ ]; ReceiveOpenCnf -- Error --> SetError[Set error]; SetError --> UpdateLocationNegativeResponse{Update Location Negative Response}; UpdateLocationNegativeResponse --> End2[ ]; +``` + +Flowchart for Process GLR\_Update\_Location\_HLR. The process starts at an oval, goes to an IDLE state (oval), then an Update Location transition (chevron). It then reaches a decision diamond where it sends MAP\_OPEN\_Req, MAP\_UPDATE\_LOCATION\_Req, and MAP\_DELIMITER\_Req to the right. It then enters a Receive Open Cnf state (double rectangle), which is linked to Section 25.1. From this state, three paths emerge: OK leads to Wait\_For\_HLR\_Response (oval); Vr leads to Perform MAP Vr (diamond); Error leads to Set error (rectangle) and then Update Location Negative Response (chevron). Both Perform MAP Vr and Update Location Negative Response lead to end symbols (crossed lines). + +Figure 19.1.2/3 (Sheet 1 of 3): Process GLR\_Update\_Location\_HLR + +![State transition diagram for Process GLR_Update_Location_HLR. The diagram shows various states and transitions for the GLR MAP protocol machine. It starts with 'Wait_For_HLR_Response' at the top. Transitions include 'MAP_FORWARD_Check_SS_ind' leading to 'Forward Check SS Indication', 'MAP_INSERT_SUBSCRIBER_DATA_ind' leading to 'Insert Subscriber data', 'MAP_Notice_Indication' leading to 'MAP_Close_request', and 'MAP_U_Abort_ind' leading to 'Abort'. 'Forward Check SS Indication' and 'Insert Subscriber data' both lead to 'Wait_For_HLR_or_Application_Response'. 'MAP_Close_request' leads to 'Set negative response', which leads to 'Update Location negative response', which leads to 'Idle'. 'Abort' leads to 'Idle'. 'MAP_Update_Location_cnf' leads to 'Check Confirmation'. 'Check Confirmation' has an 'OK' transition to 'Update Location ack' and an error transition ('Provider Error, User Error, Data Error') to 'Set negative response'. Both 'Update Location ack' and 'Update Location negative response' lead to 'Idle'. A note 'Section 25.2' is associated with the 'Check Confirmation' state.](05eb72d372e4bf78e3d6a64949d77bcc_img.jpg) + +### Process GLR\_Update\_Location\_HLR + +19.1.2.3\_2(3) + +GLR MAP protocol machine handling Location Management and interfacing to HLR MAP protocol machine, handling Location Management. + +Signals to/from the left are to/from the GLR application. +Signals to/from the right are to/from the HLR MAP protocol machine. + +``` +stateDiagram-v2 + [*] --> Wait_For_HLR_Response + Wait_For_HLR_Response --> MAP_FORWARD_Check_SS_ind + Wait_For_HLR_Response --> MAP_INSERT_SUBSCRIBER_DATA_ind + Wait_For_HLR_Response --> MAP_Notice_Indication + Wait_For_HLR_Response --> MAP_U_Abort_ind + MAP_FORWARD_Check_SS_ind --> Forward_Check_SS_Indication + Forward_Check_SS_Indication --> Wait_For_HLR_or_Application_Response + MAP_INSERT_SUBSCRIBER_DATA_ind --> Insert_Subscriber_data + Insert_Subscriber_data --> Wait_For_HLR_or_Application_Response + MAP_Notice_Indication --> MAP_Close_request + MAP_Close_request --> Set_negative_response_1[Set negative response] + Set_negative_response_1 --> Update_Location_negative_response_1[Update Location negative response] + Update_Location_negative_response_1 --> Idle_1[Idle] + MAP_U_Abort_ind --> Abort + Abort --> Idle_2[Idle] + Wait_For_HLR_Response --> MAP_Update_Location_cnf + MAP_Update_Location_cnf --> Check_Confirmation + Check_Confirmation --> Update_Location_ack[Update Location ack] + Check_Confirmation --> Set_negative_response_2[Set negative response] + Update_Location_ack --> Idle_3[Idle] + Set_negative_response_2 --> Update_Location_negative_response_2[Update Location negative response] + Update_Location_negative_response_2 --> Idle_3 +``` + +Section 25.2 + +State transition diagram for Process GLR\_Update\_Location\_HLR. The diagram shows various states and transitions for the GLR MAP protocol machine. It starts with 'Wait\_For\_HLR\_Response' at the top. Transitions include 'MAP\_FORWARD\_Check\_SS\_ind' leading to 'Forward Check SS Indication', 'MAP\_INSERT\_SUBSCRIBER\_DATA\_ind' leading to 'Insert Subscriber data', 'MAP\_Notice\_Indication' leading to 'MAP\_Close\_request', and 'MAP\_U\_Abort\_ind' leading to 'Abort'. 'Forward Check SS Indication' and 'Insert Subscriber data' both lead to 'Wait\_For\_HLR\_or\_Application\_Response'. 'MAP\_Close\_request' leads to 'Set negative response', which leads to 'Update Location negative response', which leads to 'Idle'. 'Abort' leads to 'Idle'. 'MAP\_Update\_Location\_cnf' leads to 'Check Confirmation'. 'Check Confirmation' has an 'OK' transition to 'Update Location ack' and an error transition ('Provider Error, User Error, Data Error') to 'Set negative response'. Both 'Update Location ack' and 'Update Location negative response' lead to 'Idle'. A note 'Section 25.2' is associated with the 'Check Confirmation' state. + +Figure 19.1.2/3 (Sheet 2 of 3): Process GLR\_Update\_Location\_HLR + +![State transition diagram for Process GLR_Update_Location_HLR. The diagram shows various states and transitions between them, including Wait_For_HLR_or_Application_Response, Forward Check SS Indication, Insert Subscriber data, Insert Subscriber Data ack, Insert Subscriber Data negative response, Set user error, MAP_Insert Subscriber Data response, MAP_Update_Location_cnf, Check Confirmation, Update Location ack, Set negative response, Update Location negative response, Abort, Map_U_Abort request, MAP_Notify_Indication, MAP_Close_request, MAP_U_Abort_ind, MAP_P_Abort_ind, MAP_Close_ind, and Idle. Transitions are labeled with MAP messages and application responses.](6e15fc9ea763541c5913d26f85072ae1_img.jpg) + +### Process GLR\_Update\_Location\_HLR + +19.1.2.3\_3(3) + +GLR MAP protocol machine handling Location Management and interfacing to HLR MAP protocol machine, handling Location Management. + +Signals to/from the left are to/from the GLR application. +Signals to/from the right are to/from the HLR MAP protocol machine. + +``` +stateDiagram-v2 + [*] --> Wait_For_HLR_or_Application_Response + state "Wait_For_HLR_or_Application_Response" as Wait_For_HLR_or_Application_Response + state "Forward Check SS Indication" as Forward_Check_SS_Indication + state "Insert Subscriber data" as Insert_Subscriber_data + state "Insert Subscriber Data ack" as Insert_Subscriber_Data_ack + state "Insert Subscriber Data negative response" as Insert_Subscriber_Data_negative_response + state "Set user error" as Set_user_error + state "MAP_Insert Subscriber Data response" as MAP_Insert_Subscriber_Data_response + state "MAP_Update_Location_cnf" as MAP_Update_Location_cnf + state "Check Confirmation" as Check_Confirmation + state "Update Location ack" as Update_Location_ack + state "Set negative response" as Set_negative_response + state "Update Location negative response" as Update_Location_negative_response + state "Abort" as Abort + state "Map_U_Abort request" as Map_U_Abort_request + state "MAP_Notify_Indication" as MAP_Notify_Indication + state "MAP_Close_request" as MAP_Close_request + state "MAP_U_Abort_ind, MAP_P_Abort_ind, MAP_Close_ind" as MAP_U_Abort_ind_MAP_P_Abort_ind_MAP_Close_ind + state "Idle" as Idle + + Wait_For_HLR_or_Application_Response --> Forward_Check_SS_Indication + Wait_For_HLR_or_Application_Response --> Insert_Subscriber_data + Wait_For_HLR_or_Application_Response --> Insert_Subscriber_Data_ack + Wait_For_HLR_or_Application_Response --> Insert_Subscriber_Data_negative_response + + Forward_Check_SS_Indication --> Wait_For_HLR_or_Application_Response + Insert_Subscriber_data --> Wait_For_HLR_or_Application_Response + Insert_Subscriber_Data_ack --> MAP_Insert_Subscriber_Data_response + Insert_Subscriber_Data_ack --> Wait_For_HLR_or_Application_Response + Insert_Subscriber_Data_negative_response --> Set_user_error + Set_user_error --> MAP_Insert_Subscriber_Data_response + MAP_Insert_Subscriber_Data_response --> Wait_For_HLR_or_Application_Response + + Wait_For_HLR_or_Application_Response --> MAP_Update_Location_cnf + Wait_For_HLR_or_Application_Response --> Abort + Wait_For_HLR_or_Application_Response --> MAP_Notify_Indication + Wait_For_HLR_or_Application_Response --> MAP_U_Abort_ind_MAP_P_Abort_ind_MAP_Close_ind + + MAP_Update_Location_cnf --> Check_Confirmation + Check_Confirmation --> Update_Location_ack : OK + Check_Confirmation --> Set_negative_response : Provider Error, User Error, Data Error + Update_Location_ack --> Idle + Set_negative_response --> Update_Location_negative_response + Update_Location_negative_response --> Idle + + Abort --> Map_U_Abort_request + Map_U_Abort_request --> Idle + + MAP_Notify_Indication --> MAP_Close_request + MAP_Close_request --> Set_negative_response + Set_negative_response --> Update_Location_negative_response + Update_Location_negative_response --> Idle + + MAP_U_Abort_ind_MAP_P_Abort_ind_MAP_Close_ind --> Abort + Abort --> Map_U_Abort_request + Map_U_Abort_request --> Idle +``` + +State transition diagram for Process GLR\_Update\_Location\_HLR. The diagram shows various states and transitions between them, including Wait\_For\_HLR\_or\_Application\_Response, Forward Check SS Indication, Insert Subscriber data, Insert Subscriber Data ack, Insert Subscriber Data negative response, Set user error, MAP\_Insert Subscriber Data response, MAP\_Update\_Location\_cnf, Check Confirmation, Update Location ack, Set negative response, Update Location negative response, Abort, Map\_U\_Abort request, MAP\_Notify\_Indication, MAP\_Close\_request, MAP\_U\_Abort\_ind, MAP\_P\_Abort\_ind, MAP\_Close\_ind, and Idle. Transitions are labeled with MAP messages and application responses. + +Figure 19.1.2/3 (Sheet 3 of 3): Process GLR\_Update\_Location\_HLR + +Figure 19.1.2/4 shows the Process Update\_GPRS\_Location\_GLR. This process is a GLR MAP protocol machine handling location updating and is a responder to the SGSN. + +![State transition diagram for Process Update_GPRS_Location_GLR. The process starts at an initial state, goes to NULL, then receives an Open Indication. From there, it branches based on version: V2 leads to Perform_MAP_Vr_Dialogue and then NULL; V1 Error leads to NULL; OK leads to WAIT_FOR_SERVICE_PRIMITIVE. From WAIT_FOR_SERVICE_PRIMITIVE, it sends a MAP_Update_GPRS_Location_ind to the application. The application responds with Update GPRS Location, which leads to connector 2. From connector 2, it goes to WAIT_FOR_APPLICATION_RESPONSE. From this wait state, it handles four possible responses: Update GPRS Location Ack (Set result -> MAP_UPDATE_GPRS_LOCATION_Rsp. MAP_CLOSE_Req.), Update GPRS Location Negative Response (Set error -> MAP_UPDATE_GPRS_LOCATION_Rsp. MAP_CLOSE_Req.), Insert Subscriber Data (connector 1), and Abort (MAP_U_ABORT_req.). All response paths end with an 'X' symbol.](1cac1845cf99a3f64ae00cd2bb4f9ed7_img.jpg) + +### Process Update\_GPRS\_Location\_GLR + +19.1.2.4\_1(3) + +``` +stateDiagram-v2 + [*] --> NULL1[NULL] + NULL1 --> Receive_Open_Ind[Receive Open Ind.] + Receive_Open_Ind --> WAIT_FOR_SERVICE_PRIMITIVE[WAIT_FOR_SERVICE_PRIMITIVE] + WAIT_FOR_SERVICE_PRIMITIVE --> MAP_Update_GPRS_Location_ind{MAP_Update_GPRS_Location_ind} + MAP_Update_GPRS_Location_ind --> Update_GPRS_Location[Update GPRS Location] + Update_GPRS_Location --> 2((2)) + 2 --> WAIT_FOR_APPLICATION_RESPONSE[WAIT_FOR_APPLICATION_RESPONSE] + WAIT_FOR_APPLICATION_RESPONSE --> Update_GPRS_Location_Ack[Update GPRS Location Ack] + Update_GPRS_Location_Ack --> Set_result[Set result] + Set_result --> MAP_UPDATE_GPRS_LOCATION_Rsp_1{MAP_UPDATE_GPRS_LOCATION_Rsp. MAP_CLOSE_Req.} + MAP_UPDATE_GPRS_LOCATION_Rsp_1 --> X1[X] + WAIT_FOR_APPLICATION_RESPONSE --> Update_GPRS_Location_Negative_Response[Update GPRS Location Negative Response] + Update_GPRS_Location_Negative_Response --> Set_error[Set error] + Set_error --> MAP_UPDATE_GPRS_LOCATION_Rsp_2{MAP_UPDATE_GPRS_LOCATION_Rsp. MAP_CLOSE_Req.} + MAP_UPDATE_GPRS_LOCATION_Rsp_2 --> X2[X] + WAIT_FOR_APPLICATION_RESPONSE --> Insert_Subscriber_Data[Insert Subscriber Data] + Insert_Subscriber_Data --> 1((1)) + WAIT_FOR_APPLICATION_RESPONSE --> Abort[Abort] + Abort --> MAP_U_ABORT_req{MAP_U_ABORT_req.} + MAP_U_ABORT_req --> X3[X] +``` + +GLR MAP protocol machine handling location updating and interfacing with SGSN MAP protocol machine + +Left to SGSN +Right to GLR application + +OK + +V2 + +V1 Error + +NULL + +NULL + +WAIT\_FOR\_SERVICE\_PRIMITIVE + +MAP\_Update\_GPRS\_Location\_ind + +Update GPRS Location + +2 + +WAIT\_FOR\_APPLICATION\_RESPONSE + +Update GPRS Location Ack + +Set result + +MAP\_UPDATE\_GPRS\_LOCATION\_Rsp. MAP\_CLOSE\_Req. + +X + +Update GPRS Location Negative Response + +Set error + +MAP\_UPDATE\_GPRS\_LOCATION\_Rsp. MAP\_CLOSE\_Req. + +X + +Insert Subscriber Data + +1 + +Abort + +MAP\_U\_ABORT\_req. + +X + +State transition diagram for Process Update\_GPRS\_Location\_GLR. The process starts at an initial state, goes to NULL, then receives an Open Indication. From there, it branches based on version: V2 leads to Perform\_MAP\_Vr\_Dialogue and then NULL; V1 Error leads to NULL; OK leads to WAIT\_FOR\_SERVICE\_PRIMITIVE. From WAIT\_FOR\_SERVICE\_PRIMITIVE, it sends a MAP\_Update\_GPRS\_Location\_ind to the application. The application responds with Update GPRS Location, which leads to connector 2. From connector 2, it goes to WAIT\_FOR\_APPLICATION\_RESPONSE. From this wait state, it handles four possible responses: Update GPRS Location Ack (Set result -> MAP\_UPDATE\_GPRS\_LOCATION\_Rsp. MAP\_CLOSE\_Req.), Update GPRS Location Negative Response (Set error -> MAP\_UPDATE\_GPRS\_LOCATION\_Rsp. MAP\_CLOSE\_Req.), Insert Subscriber Data (connector 1), and Abort (MAP\_U\_ABORT\_req.). All response paths end with an 'X' symbol. + +Figure 19.1.2/4 (sheet 1 of 3): Process Update\_GPRS\_Location\_GLR + +![SDL Diagram for Process Update_GPRS_Location_GLR sheet 2 of 3](78ff716475b2f65bf01c3a4d02d89fc4_img.jpg) + +### Process Update\_GPRS\_Location\_GLR + +19.1.2.4\_2(3) + +GLR MAP protocol machine handling location updating and interfacing with SGSN MAP protocol machine + +Left to SGSN +Right to GLR application + +``` + + stateDiagram-v2 + state "WAIT_FOR_ISD_Cnf +WAIT_FOR_SUBSEQUENT_ +APPLICATION_RESPONSE" as WAIT + + [*] --> 1 + 1 --> 3 + 3 --> Request + state "MAP_Insert_Subscriber_Data_Req +MAP_Delimiter_Req" as Request + Request --> WAIT + + WAIT --> MAP_Insert_Subscriber_Data_Cnf + MAP_Insert_Subscriber_Data_Cnf --> CheckConfirmation + state "Check Confirmation +Section 25.2" as CheckConfirmation + + CheckConfirmation --> OK + OK --> Insert_Subscriber_Data_Cnf + Insert_Subscriber_Data_Cnf --> 2 + + CheckConfirmation --> ProviderError : Provider error +Data error + state "Set Negative Response +System Failure" as ProviderError + ProviderError --> ISD_Negative_Response_1 + + CheckConfirmation --> UserError : User error + state "MAP User Error +to Negative +Response" as UserError + UserError --> ISD_Negative_Response_1 + + state "ISD +Negative Response" as ISD_Negative_Response_1 + ISD_Negative_Response_1 --> 2 + + WAIT --> AbortSignals + state "MAP_U_ABORT_Ind +MAP_P_ABORT_Ind +MAP_CLOSE_Ind" as AbortSignals + AbortSignals --> Abort + Abort --> X + + WAIT --> MAP_NOTICE_Ind + MAP_NOTICE_Ind --> SetNegativeResult + state "Set Negative Result +System Failure" as SetNegativeResult + SetNegativeResult --> ISD_Negative_Response_2 + state "ISD +Negative Response" as ISD_Negative_Response_2 + ISD_Negative_Response_2 --> 3 + +``` + +SDL Diagram for Process Update\_GPRS\_Location\_GLR sheet 2 of 3 + +**Figure 19.1.2/4 (sheet 2 of 3): Process Update\_GPRS\_Location\_GLR** + +![SDL diagram for Process Update_GPRS_Location_GLR showing transitions from WAIT_FOR_ISD_Cnf and WAIT_FOR_SUBSEQUENT_APPLICATION_RESPONSE states based on various input signals like Update Location Ack and Abort.](6629e8a87e7552e2454b7c3e9f6d73a0_img.jpg) + +### Process Update\_GPRS\_Location\_GLR + +19.1.2.4\_3(3) + +GLR MAP protocol machine +handling location updating and +interfacing with SGSN MAP +protocol machine + +Left to SGSN +Right to GLR +application + +``` + +stateDiagram-v2 + state "WAIT_FOR_ISD_Cnf\nWAIT_FOR_SUBSEQUENT_\nAPPLICATION_RESPONSE" as State1 + + State1 --> Update_Location_Ack + State1 --> Update_GPRS_Location_Negative_Response + State1 --> Insert_Subscriber_Data + State1 --> Abort + + Update_Location_Ack --> Set_result + Update_GPRS_Location_Negative_Response --> Set_Error + Insert_Subscriber_Data --> Connector1 : 1 + Abort --> MAP_U_ABORT_req + + Set_result --> MAP_UPDATE_LOCATION_Rsp + Set_Error --> MAP_UPDATE_LOCATION_Rsp + + MAP_UPDATE_LOCATION_Rsp --> End1 : X + MAP_U_ABORT_req --> End2 : X + + state "Update Location Ack" as Update_Location_Ack + state "Update GPRS Location\nNegative Response" as Update_GPRS_Location_Negative_Response + state "Insert\nSubscriber\nData" as Insert_Subscriber_Data + state "Abort" as Abort + state "Set result" as Set_result + state "Set Error" as Set_Error + state "MAP_UPDATE_LOCATION_Rsp.\nMAP_CLOSE_Req." as MAP_UPDATE_LOCATION_Rsp + state "MAP_U_ABORT_req" as MAP_U_ABORT_req + +``` + +SDL diagram for Process Update\_GPRS\_Location\_GLR showing transitions from WAIT\_FOR\_ISD\_Cnf and WAIT\_FOR\_SUBSEQUENT\_APPLICATION\_RESPONSE states based on various input signals like Update Location Ack and Abort. + +**Figure 19.1.2/4 (sheet 3 of 3): Process Update\_GPRS\_Location\_GLR** + +Figure 19.1.2/5 shows the Process GLR\_Update\_GPRS\_Location\_HLR. This process is a GLR MAP protocol machine handling location updating and is an initiator to the HLR. + +Sheet 1: If the Macro Open\_Receive\_Cnf results Vr, the process requests to perform MAP Vr. It causes a request for sending an abort message to Process Update\_GPRS\_Location\_GLR. + +![Flowchart for Process GLR_Update_GPRS_Location_HLR. It starts with an oval connector, followed by an IDLE state. A transition 'Update GPRS Location' leads to a decision diamond. The right side of the diamond lists 'MAP_OPEN_Req', 'MAP_UPDATE_GPRS_LOCATION_Req', and 'MAP_DELIMITER_Req'. The bottom side is 'Receive Open Cnf.', with a note 'Section 25.1'. From 'Receive Open Cnf.', three paths emerge: 'OK' leads to 'Wait_For_HLR_Response'; 'Vr' leads to 'Perform MAP Vr' (terminated with an X); 'Error' leads to 'Set error' then 'Update GPRS Location Negative Response' (terminated with an X).](4ff00a489baaa34a0c01070de1d613db_img.jpg) + +**Process GLR\_Update\_GPRS\_Location\_HLR** 19.1.2.5\_1(3) + +GLR MAP protocol machine handling Location Management and interfacing to HLR MAP protocol machine, handling Location Management. + +Signals to/from the left are to/from the GLR application. +Signals to/from the right are to/from the HLR MAP protocol machine. + +``` +graph TD; Start([ ]) --> IDLE([IDLE]); IDLE --> UpdateGPRS[Update GPRS Location]; UpdateGPRS --> Decision{ }; Decision -- "MAP_OPEN_Req +MAP_UPDATE_GPRS_LOCATION_Req +MAP_DELIMITER_Req" --> Right1[ ]; Decision -- "Receive Open Cnf. +Section 25.1" --> Bottom1[ ]; Decision -- OK --> Wait[Wait_For_HLR_Response]; Decision -- Vr --> Perform[Perform MAP Vr]; Perform --> X1[X]; Decision -- Error --> SetError[Set error]; SetError --> Negative[Update GPRS Location Negative Response]; Negative --> X2[X]; +``` + +Flowchart for Process GLR\_Update\_GPRS\_Location\_HLR. It starts with an oval connector, followed by an IDLE state. A transition 'Update GPRS Location' leads to a decision diamond. The right side of the diamond lists 'MAP\_OPEN\_Req', 'MAP\_UPDATE\_GPRS\_LOCATION\_Req', and 'MAP\_DELIMITER\_Req'. The bottom side is 'Receive Open Cnf.', with a note 'Section 25.1'. From 'Receive Open Cnf.', three paths emerge: 'OK' leads to 'Wait\_For\_HLR\_Response'; 'Vr' leads to 'Perform MAP Vr' (terminated with an X); 'Error' leads to 'Set error' then 'Update GPRS Location Negative Response' (terminated with an X). + +Figure 19.1.2/5 (Sheet 1 of 3): Process GLR\_Update\_GPRS\_Location\_HLR + +![State transition diagram for Process GLR_Update_GPRS_Location_HLR. The diagram shows four main entry points from the top: MAP_Update_GPRS_Location_cnf, MAP_INSERT_SUBSCRIBER_DATA_ind, MAP_Notice_Indication, and MAP_U_Abort_ind / MAP_P_Abort_ind / MAP_Close_ind. The first path leads to a 'Check Confirmation' block (referencing Section 25.2), which then branches into 'Update GPRS Location ack' (leading to Idle) or 'Set negative response' (leading to 'Update GPRS Location negative response' and then Idle). The second path leads to 'Insert Subscriber Data', which then leads to 'Wait_For_HLR_or_Application_Response'. The third path leads to 'MAP_Close_request', then 'Set negative response', then 'Update GPRS Location negative response', and finally Idle. The fourth path leads directly to 'Abort' and then Idle.](329c96049bb432e9c2cbda4e224a0c9c_img.jpg) + +### Process GLR\_Update\_GPRS\_Location\_HLR + +19.1.2.5\_2(3) + +GLR MAP protocol machine handling Location Management and interfacing to HLR MAP protocol machine, handling Location Management. + +Signals to/from the left are to/from the GLR application. +Signals to/from the right are to/from the HLR MAP protocol machine. + +``` +stateDiagram-v2 + [*] --> Wait_For_HLR_Response + state "Wait_For_HLR_Response" as Wait_For_HLR_Response + state "MAP_Update_GPRS_Location_cnf" as MAP_Update_GPRS_Location_cnf + state "MAP_INSERT_SUBSCRIBER_DATA_ind" as MAP_INSERT_SUBSCRIBER_DATA_ind + state "MAP_Notice_Indication" as MAP_Notice_Indication + state "MAP_U_Abort_ind / MAP_P_Abort_ind / MAP_Close_ind" as MAP_U_Abort_ind_MAP_P_Abort_ind_MAP_Close_ind + state "Check Confirmation" as CheckConfirmation["Check Confirmation (Section 25.2)"] + state "Insert Subscriber Data" as InsertSubscriberData + state "MAP_Close_request" as MAP_Close_request + state "Abort" as Abort + state "Set negative response" as SetNegativeResponse + state "Update GPRS Location ack" as UpdateGPRSLocationAck + state "Update GPRS Location negative response" as UpdateGPRSLocationNegativeResponse + state "Wait_For_HLR_or_Application_Response" as Wait_For_HLR_or_Application_Response + state "Idle" as Idle + + Wait_For_HLR_Response --> MAP_Update_GPRS_Location_cnf + Wait_For_HLR_Response --> MAP_INSERT_SUBSCRIBER_DATA_ind + Wait_For_HLR_Response --> MAP_Notice_Indication + Wait_For_HLR_Response --> MAP_U_Abort_ind_MAP_P_Abort_ind_MAP_Close_ind + + MAP_Update_GPRS_Location_cnf --> CheckConfirmation + CheckConfirmation --> UpdateGPRSLocationAck : OK + CheckConfirmation --> SetNegativeResponse : Provider Error, User Error, Data Error + UpdateGPRSLocationAck --> Idle + SetNegativeResponse --> UpdateGPRSLocationNegativeResponse + UpdateGPRSLocationNegativeResponse --> Idle + + MAP_INSERT_SUBSCRIBER_DATA_ind --> InsertSubscriberData + InsertSubscriberData --> Wait_For_HLR_or_Application_Response + + MAP_Notice_Indication --> MAP_Close_request + MAP_Close_request --> SetNegativeResponse + SetNegativeResponse --> UpdateGPRSLocationNegativeResponse + UpdateGPRSLocationNegativeResponse --> Idle + + MAP_U_Abort_ind_MAP_P_Abort_ind_MAP_Close_ind --> Abort + Abort --> Idle +``` + +State transition diagram for Process GLR\_Update\_GPRS\_Location\_HLR. The diagram shows four main entry points from the top: MAP\_Update\_GPRS\_Location\_cnf, MAP\_INSERT\_SUBSCRIBER\_DATA\_ind, MAP\_Notice\_Indication, and MAP\_U\_Abort\_ind / MAP\_P\_Abort\_ind / MAP\_Close\_ind. The first path leads to a 'Check Confirmation' block (referencing Section 25.2), which then branches into 'Update GPRS Location ack' (leading to Idle) or 'Set negative response' (leading to 'Update GPRS Location negative response' and then Idle). The second path leads to 'Insert Subscriber Data', which then leads to 'Wait\_For\_HLR\_or\_Application\_Response'. The third path leads to 'MAP\_Close\_request', then 'Set negative response', then 'Update GPRS Location negative response', and finally Idle. The fourth path leads directly to 'Abort' and then Idle. + +Figure 19.1.2/5 (Sheet 2 of 3): Process GLR\_Update\_GPRS\_Location\_HLR + +![State transition diagram for Process GLR_Update_GPRS_Location_HLR. The diagram shows two main vertical paths. The left path starts with 'Wait_For_HLR_or_Application_Response', followed by 'MAP_INSERT_SUBSCRIBER_DATA_ind', 'Insert Subscriber Data', 'MAP_Insert Subscriber_Data_response', and back to 'Wait_For_HLR_or_Application_Response'. The right path from 'Insert Subscriber Data' goes to 'Insert Subscriber Data ack' and 'Insert Subscriber Data negative response', which leads to 'Set user error' and then to the 'MAP_Insert Subscriber_Data_response' transition. Below this, the diagram branches into four horizontal paths: 1) 'MAP_Update_GPRS_Location_cnf' leads to 'Check Confirmation', which has 'OK' (leading to 'Update GPRS Location ack' and 'Idle') and 'Provider Error, User Error, Data Error' (leading to 'Set negative response' and 'Update GPRS Location negative response'). A note 'Section 25.2' is near this path. 2) 'Abort' leads to 'Map_U_Abort request' and then to 'Idle'. 3) 'MAP_Notice_Indication' leads to 'MAP_Close_request', 'Set negative response', 'Update GPRS Location negative response', and then to 'Idle'. 4) 'MAP_U_Abort_ind MAP_P_Abort_ind MAP_Close_ind' leads to 'Abort' and then to 'Idle'.](c99bf3a0530a3e58f5f2d2790ba7441b_img.jpg) + +**Process GLR\_Update\_GPRS\_Location\_HLR** 19.1.2.5\_3(3) + +GLR MAP protocol machine handling Location Management and interfacing to HLR MAP protocol machine, handling Location Management. + +Signals to/from the left are to/from the GLR application. + Signals to/from the right are to/from the HLR MAP protocol machine. + +``` + +stateDiagram-v2 + [*] --> Wait_For_HLR_or_Application_Response + state "Wait_For_HLR_or_Application_Response" as Wait_For_HLR_or_Application_Response + state "MAP_INSERT_SUBSCRIBER_DATA_ind" as MAP_INSERT_SUBSCRIBER_DATA_ind + state "Insert Subscriber Data" as Insert Subscriber Data + state "Insert Subscriber Data ack" as Insert Subscriber Data ack + state "Insert Subscriber Data negative response" as Insert Subscriber Data negative response + state "Set user error" as Set user error + state "MAP_Insert Subscriber_Data_response" as MAP_Insert Subscriber_Data_response + state "MAP_Update_GPRS_Location_cnf" as MAP_Update_GPRS_Location_cnf + state "Check Confirmation" as Check Confirmation + state "OK" as OK + state "Provider Error, User Error, Data Error" as Provider Error, User Error, Data Error + state "Update GPRS Location ack" as Update GPRS Location ack + state "Set negative response" as Set negative response + state "Update GPRS Location negative response" as Update GPRS Location negative response + state "Idle" as Idle + state "Abort" as Abort + state "Map_U_Abort request" as Map_U_Abort request + state "MAP_Notice_Indication" as MAP_Notice_Indication + state "MAP_Close_request" as MAP_Close_request + state "MAP_U_Abort_ind MAP_P_Abort_ind MAP_Close_ind" as MAP_U_Abort_ind MAP_P_Abort_ind MAP_Close_ind + + Wait_For_HLR_or_Application_Response --> MAP_INSERT_SUBSCRIBER_DATA_ind + MAP_INSERT_SUBSCRIBER_DATA_ind --> Insert Subscriber Data + Insert Subscriber Data --> Insert Subscriber Data ack + Insert Subscriber Data --> Insert Subscriber Data negative response + Insert Subscriber Data negative response --> Set user error + Set user error --> MAP_Insert Subscriber_Data_response + MAP_Insert Subscriber_Data_response --> Wait_For_HLR_or_Application_Response + + MAP_Update_GPRS_Location_cnf --> Check Confirmation + Check Confirmation --> OK + Check Confirmation --> Provider Error, User Error, Data Error + OK --> Update GPRS Location ack + Update GPRS Location ack --> Idle + Provider Error, User Error, Data Error --> Set negative response + Set negative response --> Update GPRS Location negative response + Update GPRS Location negative response --> Idle + + Abort --> Map_U_Abort request + Map_U_Abort request --> Idle + + MAP_Notice_Indication --> MAP_Close_request + MAP_Close_request --> Set negative response + Set negative response --> Update GPRS Location negative response + Update GPRS Location negative response --> Idle + + MAP_U_Abort_ind MAP_P_Abort_ind MAP_Close_ind --> Abort + Abort --> Idle + +``` + +State transition diagram for Process GLR\_Update\_GPRS\_Location\_HLR. The diagram shows two main vertical paths. The left path starts with 'Wait\_For\_HLR\_or\_Application\_Response', followed by 'MAP\_INSERT\_SUBSCRIBER\_DATA\_ind', 'Insert Subscriber Data', 'MAP\_Insert Subscriber\_Data\_response', and back to 'Wait\_For\_HLR\_or\_Application\_Response'. The right path from 'Insert Subscriber Data' goes to 'Insert Subscriber Data ack' and 'Insert Subscriber Data negative response', which leads to 'Set user error' and then to the 'MAP\_Insert Subscriber\_Data\_response' transition. Below this, the diagram branches into four horizontal paths: 1) 'MAP\_Update\_GPRS\_Location\_cnf' leads to 'Check Confirmation', which has 'OK' (leading to 'Update GPRS Location ack' and 'Idle') and 'Provider Error, User Error, Data Error' (leading to 'Set negative response' and 'Update GPRS Location negative response'). A note 'Section 25.2' is near this path. 2) 'Abort' leads to 'Map\_U\_Abort request' and then to 'Idle'. 3) 'MAP\_Notice\_Indication' leads to 'MAP\_Close\_request', 'Set negative response', 'Update GPRS Location negative response', and then to 'Idle'. 4) 'MAP\_U\_Abort\_ind MAP\_P\_Abort\_ind MAP\_Close\_ind' leads to 'Abort' and then to 'Idle'. + +Figure 19.1.2/5 (Sheet 3 of 3): Process GLR\_Update\_GPRS\_Location\_HLR + +### 19.1.2 Location Cancellation + +#### 19.1.2.1 General + +The purpose of this process is to delete a subscriber's record from a previous GLR/VLR/SGSN after she has registered with a new GLR/VLR/SGSN. The procedure may also be used if the subscriber's record is to be deleted for other operator determined purposes. Location cancellation can be used to enforce location updating including updating of subscriber data in the VLR or in the SGSN at the next subscriber access. + +In all cases, the process is performed independently of the invoking process (e.g. Location Updating). + +If GLR is located between the VLR or the SGSN and the HLR, the MAP\_CANCEL\_LOCATION service is invoked towards the GLR whose identity is contained in the HLR table. + +![Sequence diagram for Figure 19.1.3/1: Interface and services for Location Cancellation. The diagram shows four entities: VLR/GLR, HLR, PGLR, and PVLR. The HLR is connected to each of the other three entities by dashed lines labeled 'D'. The sequence of messages is: 1. VLR/GLR sends a solid line 'MAP_UPDATE_LOCATION' to HLR. 2. HLR sends a dotted line 'MAP_CANCEL_LOCATION' to PGLR. 3. PGLR sends a dotted line 'MAP_CANCEL_LOCATION' to PVLR. 4. PGLR sends a solid line 'MAP_CANCEL_LOCATION' back to HLR. 5. HLR sends a solid line 'ack' back to PGLR. 6. PGLR sends a solid line 'MAP_CANCEL_LOCATION' back to PVLR. 7. PVLR sends a solid line 'ack' back to PGLR.](50214d232017279410e9c9db8eb75119_img.jpg) + +Sequence diagram for Figure 19.1.3/1: Interface and services for Location Cancellation. The diagram shows four entities: VLR/GLR, HLR, PGLR, and PVLR. The HLR is connected to each of the other three entities by dashed lines labeled 'D'. The sequence of messages is: 1. VLR/GLR sends a solid line 'MAP\_UPDATE\_LOCATION' to HLR. 2. HLR sends a dotted line 'MAP\_CANCEL\_LOCATION' to PGLR. 3. PGLR sends a dotted line 'MAP\_CANCEL\_LOCATION' to PVLR. 4. PGLR sends a solid line 'MAP\_CANCEL\_LOCATION' back to HLR. 5. HLR sends a solid line 'ack' back to PGLR. 6. PGLR sends a solid line 'MAP\_CANCEL\_LOCATION' back to PVLR. 7. PVLR sends a solid line 'ack' back to PGLR. + +NOTE: The service shown in dotted lines indicates the trigger provided by other MAP signalling. + +**Figure 19.1.3/1: Interface and services for Location Cancellation** + +![Sequence diagram for Figure 19.1.3/2: Interface and services for Location Cancellation in GPRS. The diagram shows four entities: SGSN/GLR, HLR, PGLR, and PSGSN. The HLR is connected to each of the other three entities by dashed lines labeled 'D'. The sequence of messages is: 1. SGSN/GLR sends a solid line 'MAP_UPDATE_GPRS_LOCATION' to HLR. 2. HLR sends a dotted line 'MAP_CANCEL_LOCATION' to PGLR. 3. PGLR sends a dotted line 'MAP_CANCEL_LOCATION' to PSGSN. 4. PGLR sends a solid line 'MAP_CANCEL_LOCATION' back to HLR. 5. HLR sends a solid line 'ack' back to PGLR. 6. PGLR sends a solid line 'MAP_CANCEL_LOCATION' back to PSGSN. 7. PSGSN sends a solid line 'ack' back to PGLR.](4c9ba399ca7df11cbe9b6322cd9aee0a_img.jpg) + +Sequence diagram for Figure 19.1.3/2: Interface and services for Location Cancellation in GPRS. The diagram shows four entities: SGSN/GLR, HLR, PGLR, and PSGSN. The HLR is connected to each of the other three entities by dashed lines labeled 'D'. The sequence of messages is: 1. SGSN/GLR sends a solid line 'MAP\_UPDATE\_GPRS\_LOCATION' to HLR. 2. HLR sends a dotted line 'MAP\_CANCEL\_LOCATION' to PGLR. 3. PGLR sends a dotted line 'MAP\_CANCEL\_LOCATION' to PSGSN. 4. PGLR sends a solid line 'MAP\_CANCEL\_LOCATION' back to HLR. 5. HLR sends a solid line 'ack' back to PGLR. 6. PGLR sends a solid line 'MAP\_CANCEL\_LOCATION' back to PSGSN. 7. PSGSN sends a solid line 'ack' back to PGLR. + +NOTE: The service shown in dotted lines indicates the trigger provided by other MAP signalling. + +**Figure 19.1.3/2: Interface and services for Location Cancellation in GPRS** + +Additionally, The MAP\_CANCEL\_LOCATION service is invoked when the GLR that stores the subscriber's record receives a MAP\_UPDATE\_LOCATION indication from a VLR other than that stored in its table for this subscriber. Also the MAP\_CANCEL\_LOCATION service is invoked when the GLR that stores the subscriber's record a MAP\_UPDATE\_GPRS\_LOCATION indication from a SGSN other than stored in its table for this subscriber. The MAP\_CANCEL\_LOCATION service is in any case invoked towards the VLR or the SGSN whose identity is contained in the HLR table. + +![Sequence diagram showing network interfaces and services for location cancellation. Lifelines: VLR/SGSN, GLR, and PVLR/PSGSN. The diagram shows three messages: 1. MAP_UPDATE_LOCATION or MAP_UPDATE_GPRS_LOCATION from VLR/SGSN to GLR. 2. MAP_CANCEL_LOCATION from GLR to PVLR/PSGSN. 3. MAP_CANCEL_LOCATION ack from PVLR/PSGSN back to GLR. Horizontal dashed lines labeled 'D' connect the lifelines.](8269648391c59363ea61243864a2adf7_img.jpg) + +``` +sequenceDiagram + participant VLR_SGSN as VLR/SGSN + participant GLR + participant PVLR_PSGSN as PVLR/PSGSN + Note over VLR_SGSN, GLR: D + Note over GLR, PVLR_PSGSN: D + VLR_SGSN->>GLR: MAP_UPDATE_LOCATION or MAP_UPDATE_GPRS_LOCATION + GLR->>PVLR_PSGSN: MAP_CANCEL_LOCATION + PVLR_PSGSN-->>GLR: MAP_CANCEL_LOCATION ack +``` + +Sequence diagram showing network interfaces and services for location cancellation. Lifelines: VLR/SGSN, GLR, and PVLR/PSGSN. The diagram shows three messages: 1. MAP\_UPDATE\_LOCATION or MAP\_UPDATE\_GPRS\_LOCATION from VLR/SGSN to GLR. 2. MAP\_CANCEL\_LOCATION from GLR to PVLR/PSGSN. 3. MAP\_CANCEL\_LOCATION ack from PVLR/PSGSN back to GLR. Horizontal dashed lines labeled 'D' connect the lifelines. + +**Figure 19.1.3/4: Interface and services for Location Cancellation in case that the GLR stores the subscriber's record** + +#### 19.1.2.2 Detailed procedure in the GLR + +Figure 19.1.3/5 shows the Process Cancel\_Location\_GLR. This process is a GLR MAP protocol machine handling location cancellation and is a responder to the HLR. + +![State transition diagram for Process Cancel_Location_GLR. The process starts at a NULL state, receives an Open Indication, and then branches based on OK, V2, or V1 Error signals. The OK path leads to WAIT_FOR_SERVICE_PRIMITIVE, then to MAP_CANCEL_LOCATION_ind and MAP_NOTICE_ind. MAP_CANCEL_LOCATION_ind leads to a Cancel Location state, which then leads to WAIT_FOR_APPLICATION_RESPONSE. From there, it branches to Cancel Location Ack, Cancel Location Negative response, or Abort. Cancel Location Ack and Negative response lead to MAP_CANCEL_LOCATION_Rsp. and MAP_CLOSE_Req., which then lead to NULL. Abort leads to MAP_U_ABORT_req., which then leads to NULL. The V2 path leads to Perform_MAP_Vr_Dialogue, which leads to NULL. The V1 Error path leads to NULL.](32ff77da4286b58c4778033acaa10836_img.jpg) + +**Process Cancel\_Location\_GLR** 19.1.3.5(1) + +GLR MAP protocol machine handling Location cancelation and interfacing to HLR MAP protocol machine, handling Location Cancelation. + +Signals to/from the left are to/from the GLR Location cancellation application. +Signals to/from the right are to/from the HLR MAP protocol machine, handling Location Cancellation. + +``` +stateDiagram-v2 + [*] --> NULL1[NULL] + NULL1 --> Receive_Open_Ind[Receive Open Ind.] + Receive_Open_Ind --> WAIT_FOR_SERVICE_PRIMITIVE[WAIT_FOR_SERVICE_PRIMITIVE] + WAIT_FOR_SERVICE_PRIMITIVE --> MAP_CANCEL_LOCATION_ind[MAP_CANCEL_LOCATION_ind] + WAIT_FOR_SERVICE_PRIMITIVE --> MAP_NOTICE_ind[MAP_NOTICE_ind] + WAIT_FOR_SERVICE_PRIMITIVE --> Perform_MAP_Vr_Dialogue[Perform_MAP_Vr_Dialogue] + WAIT_FOR_SERVICE_PRIMITIVE --> NULL2[NULL] + MAP_CANCEL_LOCATION_ind --> Cancel_Location{Cancel Location} + MAP_NOTICE_ind --> MAP_CLOSE_req[MAP_CLOSE_req] + MAP_CLOSE_req --> NULL3[NULL] + Perform_MAP_Vr_Dialogue --> NULL4[NULL] + Cancel_Location --> WAIT_FOR_APPLICATION_RESPONSE[WAIT_FOR_APPLICATION_RESPONSE] + WAIT_FOR_APPLICATION_RESPONSE --> Cancel_Location_Ack[Cancel Location Ack] + WAIT_FOR_APPLICATION_RESPONSE --> Cancel_Location_Negative_response[Cancel Location Negative response] + WAIT_FOR_APPLICATION_RESPONSE --> Abort[Abort] + Cancel_Location_Ack --> MAP_CANCEL_LOCATION_Rsp_and_MAP_CLOSE_Req[MAP_CANCEL_LOCATION_Rsp. MAP_CLOSE_Req.] + Cancel_Location_Negative_response --> MAP_CANCEL_LOCATION_Rsp_and_MAP_CLOSE_Req + MAP_CANCEL_LOCATION_Rsp_and_MAP_CLOSE_Req --> NULL5[NULL] + Abort --> MAP_U_ABORT_req[MAP_U_ABORT_req] + MAP_U_ABORT_req --> NULL6[NULL] +``` + +State transition diagram for Process Cancel\_Location\_GLR. The process starts at a NULL state, receives an Open Indication, and then branches based on OK, V2, or V1 Error signals. The OK path leads to WAIT\_FOR\_SERVICE\_PRIMITIVE, then to MAP\_CANCEL\_LOCATION\_ind and MAP\_NOTICE\_ind. MAP\_CANCEL\_LOCATION\_ind leads to a Cancel Location state, which then leads to WAIT\_FOR\_APPLICATION\_RESPONSE. From there, it branches to Cancel Location Ack, Cancel Location Negative response, or Abort. Cancel Location Ack and Negative response lead to MAP\_CANCEL\_LOCATION\_Rsp. and MAP\_CLOSE\_Req., which then lead to NULL. Abort leads to MAP\_U\_ABORT\_req., which then leads to NULL. The V2 path leads to Perform\_MAP\_Vr\_Dialogue, which leads to NULL. The V1 Error path leads to NULL. + +**Figure 19.1.3/5: Process Cancel\_Location\_GLR** + +Figure 19.1.3/6 shows the Process GLR\_Cancel\_Location\_VLR. This process is a GLR MAP protocol machine handling location cancellation and is an initiator to the VLR. + +Sheet 1: If the Macro Open\_Receive\_Cnf results Vr, the process requests to perform MAP Vr. It causes a request for sending an abort message to Process Cancel\_Location\_GLR. + +![SDL diagram for Process GLR_Cancel_Location_VLR showing states IDLE and WAIT_FOR_ACK, and various MAP signals.](67d03c9e89620d73e3786c869e559752_img.jpg) + +### Process GLR\_Cancel\_Location\_VLR 19.1.3.6(1) + +GLR MAP protocol machine handling cancel location and interfacing with VLR MAP protocol machine + +VLR to the Left +GLR Application to the Right + +``` + +stateDiagram-v2 + [*] --> IDLE + IDLE --> Cancel_Location : Input + Cancel_Location --> MAP_Signals : Output + note right of MAP_Signals + MAP_OPEN_Req + MAP_CANCEL_LOCATION_Req + MAP_DELIMITER_Req + end note + MAP_Signals --> Receive_Open_Cnf : Task + Receive_Open_Cnf --> Decision1 + state Decision1 <> + Decision1 --> WAIT_FOR_ACK : OK + Decision1 --> Perform_MAP_Vr : Vr + Decision1 --> Cancel_Location_Negative_Response_1 : Error + + WAIT_FOR_ACK --> MAP_CANCEL_LOCATION_Cnf : Input + MAP_CANCEL_LOCATION_Cnf --> Check_Confirmation : Task + Check_Confirmation --> Decision2 + state Decision2 <> + Decision2 --> Cancel_Location_Ack : OK + Decision2 --> Cancel_Location_Negative_Response_2 : Error + + Perform_MAP_Vr --> End1 + Cancel_Location_Negative_Response_1 --> End2 + Cancel_Location_Ack --> End3 + Cancel_Location_Negative_Response_2 --> End4 + + WAIT_FOR_ACK --> MAP_P_ABORT_Ind : Input + MAP_P_ABORT_Ind --> Cancel_Location_Negative_Response_3 : Output + Cancel_Location_Negative_Response_3 --> End5 + + WAIT_FOR_ACK --> MAP_NOTICE_Ind : Input + MAP_NOTICE_Ind --> MAP_CLOSE_Req : Output + MAP_CLOSE_Req --> Cancel_Location_Negative_Response_4 : Output + Cancel_Location_Negative_Response_4 --> End6 + + state End1 <> + state End2 <> + state End3 <> + state End4 <> + state End5 <> + state End6 <> + +``` + +SDL diagram for Process GLR\_Cancel\_Location\_VLR showing states IDLE and WAIT\_FOR\_ACK, and various MAP signals. + +Figure 19.1.3/6: Process GLR\_Cancel\_Location\_VLR + +Figure 19.1.3/7 shows the Process Cancel\_GPRS\_Location\_GLR. This process is a GLR MAP protocol machine handling location cancellation and is a responder to the HLR. + +![State transition diagram for Process Cancel_GPRS_Location_GLR. The process starts at a NULL state, receives an Open Indication, and then branches based on the response: OK, V2, or V1 Error. The OK path leads to a service primitive wait, then a MAP_CANCEL_LOCATION_ind, followed by a Cancel Location action, then a response wait, and finally either a MAP_CANCEL_LOCATION_Rsp/MAP_CLOSE_Req or a MAP_U_ABORT_req, both returning to NULL. The V2 path leads to a MAP dialogue perform, returning to NULL. The V1 Error path returns to NULL.](a161a2bbb4d830e847ccb4f44b7e41a9_img.jpg) + +### Process Cancel\_GPRS\_Location\_GLR 19.1.3.7(1) + +GLR MAP protocol machine handling Location cancellation and interfacing to HLR MAP protocol machine, handling Location Cancellation. + +Signals to/from the right are to/from the GLR Location cancellation application. +Signals to/from the left are to/from the HLR MAP protocol machine, handling Location Cancellation. + +``` +stateDiagram-v2 + [*] --> NULL1[NULL] + NULL1 --> Receive_Open_Ind[Receive Open Ind.] + Receive_Open_Ind --> OK + Receive_Open_Ind --> V2 + Receive_Open_Ind --> V1_Error + OK --> WAIT_FOR_SERVICE_PRIMITIVE[WAIT_FOR_SERVICE_PRIMITIVE] + WAIT_FOR_SERVICE_PRIMITIVE --> MAP_CANCEL_LOCATION_ind{MAP_CANCEL_LOCATION_ind} + MAP_CANCEL_LOCATION_ind --> Cancel_Location[Cancel Location] + Cancel_Location --> WAIT_FOR_APPLICATION_RESPONSE[WAIT_FOR_APPLICATION_RESPONSE] + WAIT_FOR_APPLICATION_RESPONSE --> Cancel_Location_Ack{Cancel Location Ack} + WAIT_FOR_APPLICATION_RESPONSE --> Cancel_Location_Negative_Response{Cancel Location Negative Response} + WAIT_FOR_APPLICATION_RESPONSE --> Abort{Abort} + Cancel_Location_Ack --> MAP_CANCEL_LOCATION_Rsp_MAP_CLOSE_Req{MAP_CANCEL_LOCATION_Rsp. MAP_CLOSE_Req.} + Cancel_Location_Negative_Response --> MAP_CANCEL_LOCATION_Rsp_MAP_CLOSE_Req + Abort --> MAP_U_ABORT_req{MAP_U_ABORT_req} + MAP_CANCEL_LOCATION_Rsp_MAP_CLOSE_Req --> NULL2[NULL] + MAP_U_ABORT_req --> NULL3[NULL] + V2 --> Perform_MAP_Vr_Dialogue[Perform MAP Vr_Dialogue] + Perform_MAP_Vr_Dialogue --> NULL4[NULL] + V1_Error --> NULL5[NULL] +``` + +State transition diagram for Process Cancel\_GPRS\_Location\_GLR. The process starts at a NULL state, receives an Open Indication, and then branches based on the response: OK, V2, or V1 Error. The OK path leads to a service primitive wait, then a MAP\_CANCEL\_LOCATION\_ind, followed by a Cancel Location action, then a response wait, and finally either a MAP\_CANCEL\_LOCATION\_Rsp/MAP\_CLOSE\_Req or a MAP\_U\_ABORT\_req, both returning to NULL. The V2 path leads to a MAP dialogue perform, returning to NULL. The V1 Error path returns to NULL. + +Figure 19.1.3/7: Process Cancel\_GPRS\_Location\_GLR + +Figure 19.1.3/8 shows the Process GLR\_Cancel\_Location\_SGSN. This process is a GLR MAP protocol machine handling location cancellation and is an initiator to the SGSN. + +Sheet 1: If the Macro Open\_Receive\_Cnf results Vr, the process requests to perform MAP Vr. It causes a request for sending an abort message to Process Cancel\_GPRS\_Location\_GLR. + +![State transition diagram for Process GLR_Cancel_Location_SGSN. The process starts at IDLE, receives a Cancel Location request, sends MAP requests (OPEN, CANCEL_LOCATION, DELIMITER), receives an Open Confirmation (Vr), and then branches based on the result (OK, Vr, Error). The OK path leads to WAIT_FOR_ACK and then to MAP_CANCEL_LOCATION_Cnf. The Vr path leads to Perform MAP Vr. The Error path leads to Cancel Location Negative Response. From WAIT_FOR_ACK, three outcomes are possible: MAP_CANCEL_LOCATION_Cnf (OK), MAP_P_ABORT_Ind (Error), and MAP_NOTICE_Ind (Error). MAP_CANCEL_LOCATION_Cnf leads to Check Confirmation, which results in either Cancel Location Ack (OK) or Cancel Location Negative Response (Error). MAP_P_ABORT_Ind and MAP_NOTICE_Ind both lead to Cancel Location Negative Response. All terminal states are marked with an 'X'.](69e5f1993021af230d08c08aac97d9df_img.jpg) + +**Process GLR\_Cancel\_Location\_SGSN** 19.1.3.8(1) + +``` +stateDiagram-v2 + [*] --> IDLE + IDLE --> Cancel_Location_In: Cancel Location + Cancel_Location_In --> MAP_Requests: MAP_OPEN_Req, MAP_CANCEL_LOCATION_Req, MAP_DELIMITER_Req + MAP_Requests --> Receive_Open_Cnf: Receive Open Cnf. + Receive_Open_Cnf --> OK: OK + Receive_Open_Cnf --> Vr: Vr + Receive_Open_Cnf --> Error: Error + Error --> Cancel_Location_Neg_Resp1: Cancel Location Negative Response + OK --> WAIT_FOR_ACK: WAIT_FOR_ACK + Vr --> Perform_MAP_Vr: Perform MAP Vr + WAIT_FOR_ACK --> MAP_CANCEL_LOCATION_Cnf: MAP_CANCEL_LOCATION_Cnf + WAIT_FOR_ACK --> MAP_P_ABORT_Ind: MAP_P_ABORT_Ind + WAIT_FOR_ACK --> MAP_NOTICE_Ind: MAP_NOTICE_Ind + MAP_CANCEL_LOCATION_Cnf --> Check_Confirmation: Check Confirmation + Check_Confirmation --> OK2: OK + Check_Confirmation --> Error2: Error + OK2 --> Cancel_Location_Ack: Cancel Location Ack + Error2 --> Cancel_Location_Neg_Resp2: Cancel Location Negative Response + MAP_P_ABORT_Ind --> Cancel_Location_Neg_Resp3: Cancel Location Negative Response + MAP_NOTICE_Ind --> MAP_CLOSE_Req: MAP_CLOSE_Req + MAP_CLOSE_Req --> Cancel_Location_Neg_Resp4: Cancel Location Negative Response +``` + +Notes: + +- GLR MAP protocol machine handling cancel location and interfacing with SGSN MAP protocol machine +- SGSN to the Left, GLR Application to the Right + +State transition diagram for Process GLR\_Cancel\_Location\_SGSN. The process starts at IDLE, receives a Cancel Location request, sends MAP requests (OPEN, CANCEL\_LOCATION, DELIMITER), receives an Open Confirmation (Vr), and then branches based on the result (OK, Vr, Error). The OK path leads to WAIT\_FOR\_ACK and then to MAP\_CANCEL\_LOCATION\_Cnf. The Vr path leads to Perform MAP Vr. The Error path leads to Cancel Location Negative Response. From WAIT\_FOR\_ACK, three outcomes are possible: MAP\_CANCEL\_LOCATION\_Cnf (OK), MAP\_P\_ABORT\_Ind (Error), and MAP\_NOTICE\_Ind (Error). MAP\_CANCEL\_LOCATION\_Cnf leads to Check Confirmation, which results in either Cancel Location Ack (OK) or Cancel Location Negative Response (Error). MAP\_P\_ABORT\_Ind and MAP\_NOTICE\_Ind both lead to Cancel Location Negative Response. All terminal states are marked with an 'X'. + +Figure 19.1.3/8: Process GLR\_Cancel\_Location\_SGSN + +### 19.1.3 Purge MS + +#### 19.1.3.1 General + +This Purge MS procedure is used to treat any request for routing information for a mobile terminated call or a mobile terminated short message as if the MS is not reachable. + +If GLR is located between the VLR or the SGSN and the HLR, the MAP\_PURGE\_MS service is invoked towards the GLR whose identity is contained in the VLR table or the SGSN table. + +When the GLR receives a MAP\_PURGE\_MS indication, the GLR determines whether it invokes the MAP\_PURGE\_MS service towards the HLR. + +![Sequence diagram showing the interface and services for Purge MS between VLR/SGSN, GLR, and HLR.](36fd537a1e39baa2471ecfaaf869751a_img.jpg) + +The diagram illustrates the interaction between three network elements: VLR/SGSN, GLR, and HLR. The sequence of messages is as follows: + +- The VLR/SGSN sends a **MAP\_PURGE\_MS** message to the GLR. +- The GLR then sends a **MAP\_PURGE\_MS** message to the HLR. +- The HLR responds with a **MAP\_PURGE\_MS ack** message to the GLR. +- Finally, the GLR sends a **MAP\_PURGE\_MS ack** message back to the VLR/SGSN. + +Sequence diagram showing the interface and services for Purge MS between VLR/SGSN, GLR, and HLR. + +**Figure 19.1.4/1: Interface and services for Purge MS** + +#### 19.1.3.2 Detailed procedure in GLR + +Figure 19.1.4/2 shows the Process Purge\_MS\_GLR. This process is a GLR MAP protocol machine handling purge MS and is a responder to the VLR. + +![State transition diagram for Process Purge_MS_GLR. It starts with an initial state leading to NULL, then Receive Open Ind. From there, three paths emerge: OK leads to WAIT_FOR_SERVICE_PRIMITIVE, V2 leads to Perform_MAP_Vr_Dialogue, and V1 Error leads to NULL. WAIT_FOR_SERVICE_PRIMITIVE leads to MAP_NOTICE_Ind, which leads to MAP_CLOSE_Req, which ends with a crossed-out circle. Perform_MAP_Vr_Dialogue leads to NULL, then MAP_PURGE_MS_Ind, then Purge MS, then WAIT_FOR_APPLICATION_RESPONSE. From WAIT_FOR_APPLICATION_RESPONSE, three paths emerge: Purge MS Ack leads to MAP_PURGE_MS_Rsp / MAP_CLOSE_Req, then NULL; Purge MS Negative Response leads to MAP_PURGE_MS_Rsp / MAP_CLOSE_Req; Abort leads to MAP_U_ABORT_req, then NULL.](8d66c9c295023a1380f9986d3663bb1e_img.jpg) + +### Process Purge\_MS\_GLR + +19.1.4.2(1) + +GLR MAP protocol machine handling purge MS + +VLR to the Left +GLR Application to the Right + +``` +stateDiagram-v2 + [*] --> NULL1[NULL] + NULL1 --> ReceiveOpenInd[Receive Open Ind.] + ReceiveOpenInd --> OK: OK + ReceiveOpenInd --> V2: V2 + ReceiveOpenInd --> NULL2[NULL]: V1 Error + OK --> WAIT_FOR_SERVICE_PRIMITIVE[WAIT_FOR_SERVICE_PRIMITIVE] + V2 --> Perform_MAP_Vr_Dialogue[Perform_MAP_Vr_Dialogue] + WAIT_FOR_SERVICE_PRIMITIVE --> MAP_NOTICE_Ind[MAP_NOTICE_Ind] + Perform_MAP_Vr_Dialogue --> NULL3[NULL] + MAP_NOTICE_Ind --> MAP_CLOSE_Req[MAP_CLOSE_Req] + MAP_CLOSE_Req --> X((X)) + NULL3 --> MAP_PURGE_MS_Ind[MAP_PURGE_MS_Ind] + MAP_PURGE_MS_Ind --> PurgeMS[Purge MS] + PurgeMS --> WAIT_FOR_APPLICATION_RESPONSE[WAIT_FOR_APPLICATION_RESPONSE] + WAIT_FOR_APPLICATION_RESPONSE --> PurgeMSAck[Purge MS Ack] + WAIT_FOR_APPLICATION_RESPONSE --> PurgeMSNegResp[Purge MS Negative Response] + WAIT_FOR_APPLICATION_RESPONSE --> Abort[Abort] + PurgeMSAck --> MAP_PURGE_MS_Rsp_MAP_CLOSE_Req[MAP_PURGE_MS_Rsp / MAP_CLOSE_Req] + PurgeMSNegResp --> MAP_PURGE_MS_Rsp_MAP_CLOSE_Req + MAP_PURGE_MS_Rsp_MAP_CLOSE_Req --> NULL4[NULL] + Abort --> MAP_U_ABORT_req[MAP_U_ABORT_req] + MAP_U_ABORT_req --> NULL5[NULL] +``` + +State transition diagram for Process Purge\_MS\_GLR. It starts with an initial state leading to NULL, then Receive Open Ind. From there, three paths emerge: OK leads to WAIT\_FOR\_SERVICE\_PRIMITIVE, V2 leads to Perform\_MAP\_Vr\_Dialogue, and V1 Error leads to NULL. WAIT\_FOR\_SERVICE\_PRIMITIVE leads to MAP\_NOTICE\_Ind, which leads to MAP\_CLOSE\_Req, which ends with a crossed-out circle. Perform\_MAP\_Vr\_Dialogue leads to NULL, then MAP\_PURGE\_MS\_Ind, then Purge MS, then WAIT\_FOR\_APPLICATION\_RESPONSE. From WAIT\_FOR\_APPLICATION\_RESPONSE, three paths emerge: Purge MS Ack leads to MAP\_PURGE\_MS\_Rsp / MAP\_CLOSE\_Req, then NULL; Purge MS Negative Response leads to MAP\_PURGE\_MS\_Rsp / MAP\_CLOSE\_Req; Abort leads to MAP\_U\_ABORT\_req, then NULL. + +Figure 19.1.4/2: Process Purge\_MS\_GLR + +Figure 19.1.4/3 shows the Process GLR\_Purge\_MS\_HLR. This process is a GLR MAP protocol machine handling purge MS and is an initiator to the HLR. + +![State transition diagram for Process GLR_Purge_MS_HLR. The process starts at a 'Null' state, transitions to 'Purge MS', then to a state where it sends 'MAP_OPEN_Req', 'MAP_PURGE_MS_Req', and 'MAP_DELIMITER_Req'. It then receives an 'Open Cnf' (Section 25.1). From there, it can either 'Perform MAP Vr' (leading to another 'Null' state), 'Set error' (leading to 'Purge MS Negative Response'), or 'Wait_For_HLR_Response' (leading to a 'Check Confirmation' state). In 'Check Confirmation', it can receive 'MAP_PURGE_MS_cnf' (OK, leading to 'Purge MS lack'), 'MAP_Notice_Indication' (leading to 'MAP_Close_request'), or 'MAP_U_Abort_ind', 'MAP_P_Abort_ind', or 'MAP_Close_ind' (all leading to 'Set negative response'). 'Purge MS lack' leads to 'Purge MS negative response', which leads to 'Null'. 'MAP_Close_request' leads to 'Set negative response' if there is a 'Provider Error, User Error, Data Error', otherwise it leads to 'Null'. 'Set negative response' leads to 'Purge MS negative response', which leads to 'Null'.](7e61b2e2506cc7e5d6e16ce9c9df25bb_img.jpg) + +**Process GLR\_Purge\_MS\_HLR** 19.1.4.3(1) + +GLR MAP protocol machine handling purge MS and interfacing to HLR MAP protocol machine, handling Purge MS. + +Signals to/from the left are to/from the GLR application. + Signals to/from the right are to/from the HLR MAP protocol machine. + +``` + +stateDiagram-v2 + [*] --> Null + Null --> Purge_MS : Purge MS + Purge_MS --> State1 : MAP_OPEN_Req, MAP_PURGE_MS_Req, MAP_DELIMITER_Req + State1 --> Receive_Open_Cnf : Section 25.1 + Receive_Open_Cnf --> Perform_MAP_Vr : Vr + Perform_MAP_Vr --> Null + Receive_Open_Cnf --> Set_error : Error + Set_error --> Purge_MS_Negative_Response : Purge MS Negative Response + Purge_MS_Negative_Response --> [*] + Receive_Open_Cnf --> Wait_For_HLR_Response : OK + Wait_For_HLR_Response --> Check_Confirmation : MAP_PURGE_MS_cnf, MAP_Notice_Indication, MAP_U_Abort_ind, MAP_P_Abort_ind, MAP_Close_ind + Check_Confirmation --> Purge_MS_lack : OK + Purge_MS_lack --> Purge_MS_negative_response : Purge MS negative response + Purge_MS_negative_response --> Null + Check_Confirmation --> MAP_Close_request : MAP_Notice_Indication + MAP_Close_request --> [*] + Check_Confirmation --> Set_negative_response : Provider Error, User Error, Data Error + Set_negative_response --> Purge_MS_negative_response : Purge MS negative response + Purge_MS_negative_response --> Null + +``` + +State transition diagram for Process GLR\_Purge\_MS\_HLR. The process starts at a 'Null' state, transitions to 'Purge MS', then to a state where it sends 'MAP\_OPEN\_Req', 'MAP\_PURGE\_MS\_Req', and 'MAP\_DELIMITER\_Req'. It then receives an 'Open Cnf' (Section 25.1). From there, it can either 'Perform MAP Vr' (leading to another 'Null' state), 'Set error' (leading to 'Purge MS Negative Response'), or 'Wait\_For\_HLR\_Response' (leading to a 'Check Confirmation' state). In 'Check Confirmation', it can receive 'MAP\_PURGE\_MS\_cnf' (OK, leading to 'Purge MS lack'), 'MAP\_Notice\_Indication' (leading to 'MAP\_Close\_request'), or 'MAP\_U\_Abort\_ind', 'MAP\_P\_Abort\_ind', or 'MAP\_Close\_ind' (all leading to 'Set negative response'). 'Purge MS lack' leads to 'Purge MS negative response', which leads to 'Null'. 'MAP\_Close\_request' leads to 'Set negative response' if there is a 'Provider Error, User Error, Data Error', otherwise it leads to 'Null'. 'Set negative response' leads to 'Purge MS negative response', which leads to 'Null'. + +Figure 19.1.4/3: Process GLR\_PURGE\_MS\_HLR + +Figure 19.1.4/4 shows the Process Purge\_MS\_GLR\_for\_GPRS. This process is a GLR MAP protocol machine handling purge MS and is a responder to the SGSN. + +Sheet 1: If the Macro Open\_Receive\_Cnf results Vr, the process requests to perform MAP Vr. It causes a request for sending an abort message to Process PURGE\_MS\_GLR. + +![SDL diagram for Process Purge_MS_GLR_for_GPRS. The flow starts with a NULL state, followed by a 'Receive Open Ind.' input. It branches into three paths: 'OK' leading to 'WAIT_FOR_SERVICE_PRIMITIVE', 'V2' leading to 'Perform_MAP_Vr_Dialogue' then 'NULL', and 'V1 Error' leading to 'NULL'. From 'WAIT_FOR_SERVICE_PRIMITIVE', it branches to 'MAP_NOTICE_Ind' (followed by 'MAP_CLOSE_Req' and termination) or 'MAP_PURGE_MS_Ind'. The latter leads to 'Purge MS' output and 'WAIT_FOR_APPLICATION_RESPONSE' state. From there, three inputs are possible: 'Purge MS Ack', 'Purge MS Negative Response' (both leading to 'MAP_PURGE_MS_Rsp' and 'MAP_CLOSE_Req' then 'NULL'), or 'Abort' (leading to 'MAP_U_ABORT_req' then 'NULL').](036c200da9b64c3eb5aae2d67bb53e1f_img.jpg) + +**Process Purge\_MS\_GLR\_for\_GPRS** 19.1.4.4(1) + +GLR MAP protocol machine +handling purge MS + +SGSN to the Left +GLR Application to the Right + +``` + +graph TD + Start([ ]) --> NULL1(NULL) + NULL1 --> RecOpenInd[Receive Open Ind.] + RecOpenInd --> OK{OK} + RecOpenInd --> V2{V2} + RecOpenInd --> V1Err{V1 Error} + + OK --> WAIT_SERV((WAIT_FOR_SERVICE_PRIMITIVE)) + V2 --> PerfMAP[Perform_MAP_Vr_Dialogue] + PerfMAP --> NULL2(NULL) + V1Err --> NULL3(NULL) + + WAIT_SERV --> MAP_NOT_IND[/MAP_NOTICE_Ind/] + WAIT_SERV --> MAP_PURGE_IND[/MAP_PURGE_MS_Ind/] + + MAP_NOT_IND --> MAP_CLOSE_REQ[/MAP_CLOSE_Req/] + MAP_CLOSE_REQ --> Term((X)) + + MAP_PURGE_IND --> PurgeMS[Purge MS] + PurgeMS --> WAIT_APP((WAIT_FOR_APPLICATION_RESPONSE)) + + WAIT_APP --> PurgeAck[/Purge MS Ack/] + WAIT_APP --> PurgeNeg[/Purge MS Negative Response/] + WAIT_APP --> Abort[/Abort/] + + PurgeAck --> MAP_RSP_CLOSE[/MAP_PURGE_MS_Rsp +MAP_CLOSE_Req/] + PurgeNeg --> MAP_RSP_CLOSE + MAP_RSP_CLOSE --> NULL4(NULL) + + Abort --> MAP_ABORT[/MAP_U_ABORT_req/] + MAP_ABORT --> NULL5(NULL) + +``` + +SDL diagram for Process Purge\_MS\_GLR\_for\_GPRS. The flow starts with a NULL state, followed by a 'Receive Open Ind.' input. It branches into three paths: 'OK' leading to 'WAIT\_FOR\_SERVICE\_PRIMITIVE', 'V2' leading to 'Perform\_MAP\_Vr\_Dialogue' then 'NULL', and 'V1 Error' leading to 'NULL'. From 'WAIT\_FOR\_SERVICE\_PRIMITIVE', it branches to 'MAP\_NOTICE\_Ind' (followed by 'MAP\_CLOSE\_Req' and termination) or 'MAP\_PURGE\_MS\_Ind'. The latter leads to 'Purge MS' output and 'WAIT\_FOR\_APPLICATION\_RESPONSE' state. From there, three inputs are possible: 'Purge MS Ack', 'Purge MS Negative Response' (both leading to 'MAP\_PURGE\_MS\_Rsp' and 'MAP\_CLOSE\_Req' then 'NULL'), or 'Abort' (leading to 'MAP\_U\_ABORT\_req' then 'NULL'). + +Figure 19.1.4/4: Process Purge\_MS\_GLR\_for\_GPRS + +Figure 19.1.4/5 shows the Process GLR\_Purge\_MS\_HLR\_for\_GPRS. This process is a GLR MAP protocol machine handling purge MS and is an initiator to the HLR. + +Sheet 1: If the Macro Open\_Receive\_Cnf results Vr, the process requests to perform MAP Vr. It causes a request for sending an abort message to Process PURGE\_MS\_HLR\_for\_GPRS. + +![Flowchart for Process GLR_Purge_MS_HLR_for_GPRS. The process starts at 'Null', goes to 'Purge MS', then to a decision point for MAP requests (MAP_OPEN_Req, MAP_PURGE_MS_Req, MAP_DELIMITER_Req). It then receives an 'Open Cnf' response. If 'OK', it goes to 'Wait_For_HLR_Response'. If 'Vr', it goes to 'Perform MAP Vr' (which leads to a dead end). If 'Error', it goes to 'Set error' and then 'Purge MS Negative Response' (which also leads to a dead end). From 'Wait_For_HLR_Response', it can receive 'MAP_PURGE_MS_cnf' (leading to 'Check Confirmation'), 'MAP_Notice_Indication' (leading to 'MAP_Close_request'), or 'MAP_U_Abort_ind / MAP_P_Abort_ind / MAP_Close_ind'. 'Check Confirmation' leads to 'Purge MS lack' (OK) or 'Set negative response' (Provider Error, User Error, Data Error). Both lead to 'Purge MS negative response' and finally 'Null'.](aeb2a26a07219661191294dba528067a_img.jpg) + +**Process GLR\_Purge\_MS\_HLR\_for\_GPRS** 19.1.4.5(1) + +GLR MAP protocol machine handling purge MS and interfacing to HLR MAP protocol machine, handling Purge MS. + +Signals to/from the left are to/from the GLR application. +Signals to/from the right are to/from the HLR MAP protocol machine. + +``` +graph TD; Start([Null]) --> PurgeMS[Purge MS]; PurgeMS --> MAP_Requests{MAP_OPEN_Req +MAP_PURGE_MS_Req +MAP_DELIMITER_Req}; MAP_Requests --> OpenCnf[Receive Open Cnf]; OpenCnf -- OK --> WaitForHLR[Wait_For_HLR_Response]; OpenCnf -- Vr --> PerformMAPVr[Perform MAP Vr]; PerformMAPVr --> DeadEnd1((X)); OpenCnf -- Error --> SetError[Set error]; SetError --> NegativeResponse1[Purge MS Negative Response]; NegativeResponse1 --> DeadEnd2((X)); WaitForHLR --> MAP_PURGE_MS_cnf[MAP_PURGE_MS_cnf]; WaitForHLR --> MAP_Notice_Indication[MAP_Notice_Indication]; WaitForHLR --> MAP_U_Abort_ind[MAP_U_Abort_ind / MAP_P_Abort_ind / MAP_Close_ind]; MAP_PURGE_MS_cnf --> CheckConfirmation[Check Confirmation]; CheckConfirmation -- OK --> PurgeMSlack[Purge MS lack]; CheckConfirmation -- "Provider Error, User Error, Data Error" --> SetNegativeResponse[Set negative response]; MAP_Notice_Indication --> MAP_Close_request[MAP_Close_request]; MAP_Close_request --> DeadEnd3((X)); MAP_U_Abort_ind --> DeadEnd3; PurgeMSlack --> PurgeMSnegativeResponse[Purge MS negative response]; SetNegativeResponse --> PurgeMSnegativeResponse; PurgeMSnegativeResponse --> Null([Null]); +``` + +Flowchart for Process GLR\_Purge\_MS\_HLR\_for\_GPRS. The process starts at 'Null', goes to 'Purge MS', then to a decision point for MAP requests (MAP\_OPEN\_Req, MAP\_PURGE\_MS\_Req, MAP\_DELIMITER\_Req). It then receives an 'Open Cnf' response. If 'OK', it goes to 'Wait\_For\_HLR\_Response'. If 'Vr', it goes to 'Perform MAP Vr' (which leads to a dead end). If 'Error', it goes to 'Set error' and then 'Purge MS Negative Response' (which also leads to a dead end). From 'Wait\_For\_HLR\_Response', it can receive 'MAP\_PURGE\_MS\_cnf' (leading to 'Check Confirmation'), 'MAP\_Notice\_Indication' (leading to 'MAP\_Close\_request'), or 'MAP\_U\_Abort\_ind / MAP\_P\_Abort\_ind / MAP\_Close\_ind'. 'Check Confirmation' leads to 'Purge MS lack' (OK) or 'Set negative response' (Provider Error, User Error, Data Error). Both lead to 'Purge MS negative response' and finally 'Null'. + +Figure 19.1.4/5: Process GLR\_Purge\_MS\_HLR\_for\_GPRS + +## 19.2 Fault recovery procedures + +### 19.2.1 RESET procedure + +This procedure is used to notify VLR, SGSN and GLR of the failure of the node for restoration of the subscriber data. + +#### 19.2.1.1 HLR failure case + +In the case of HLR failure, the HLR invokes MAP\_RESET service towards the affected GLR, if GLR is located between the VLR and the HLR or between the SGSN and the HLR. When a GLR receives MAP\_RESET indication, it sends a MAP\_RESET message to the affected VLR and/or SGSN. + +#### 19.2.1.2 GLR failure case + +In the case of GLR failure, the GLR invokes MAP\_RESET service towards the affected VLR and/or SGSN. + +#### 19.2.1.3 Detailed procedure in GLR + +Figure 19.2.1/1 shows the Process RECEIVE\_RESET\_IN\_GLR. This process is a GLR MAP protocol machine handling reset message from HLR. + +![Flowchart for Process RECEIVE_RESET_IN_GLR. It starts with an oval, leading to a NULL state. Then 'Receive Open Ind.' is processed. From there, three paths emerge: 'OK' leads to 'WAIT_FOR_SERVICE_PRIMITIVE' -> 'MAP_RESET_ind' -> 'MAP_CLOSE_req' (with a note 'Release method: Prearenged end') -> 'Check_Indication' -> 'Reset' -> NULL; 'Vr' leads to 'Perform_MAP_Vr_Dialogue' -> NULL; 'Error' leads to NULL.](0a73b03fba21af142d619a9a662e6490_img.jpg) + +### Process RECEIVE\_RESET\_IN\_GLR 19.2.1.1(1) + +GLR MAP protocol machine handling reset message from HLR. + +Left to GLR application +Right to HLR + +``` +graph TD; Start([ ]) --> NULL1(NULL); NULL1 --> ReceiveOpen[Receive Open Ind.]; ReceiveOpen -- OK --> WAIT_FOR_SERVICE_PRIMITIVE(WAIT_FOR_SERVICE_PRIMITIVE); ReceiveOpen -- Vr --> Perform_MAP_Vr_Dialogue(Perform_MAP_Vr_Dialogue); ReceiveOpen -- Error --> NULL2(NULL); WAIT_FOR_SERVICE_PRIMITIVE --> MAP_RESET_ind[/MAP_RESET_ind/]; MAP_RESET_ind --> MAP_CLOSE_req[/MAP_CLOSE_req/]; Note1[Release method: Prearenged end] -.-> MAP_CLOSE_req; MAP_CLOSE_req --> Check_Indication[Check_Indication]; Check_Indication -- OK --> Reset{Reset}; Check_Indication -- Error --> NULL3(NULL); Reset --> NULL4(NULL); Perform_MAP_Vr_Dialogue --> NULL5(NULL); +``` + +Flowchart for Process RECEIVE\_RESET\_IN\_GLR. It starts with an oval, leading to a NULL state. Then 'Receive Open Ind.' is processed. From there, three paths emerge: 'OK' leads to 'WAIT\_FOR\_SERVICE\_PRIMITIVE' -> 'MAP\_RESET\_ind' -> 'MAP\_CLOSE\_req' (with a note 'Release method: Prearenged end') -> 'Check\_Indication' -> 'Reset' -> NULL; 'Vr' leads to 'Perform\_MAP\_Vr\_Dialogue' -> NULL; 'Error' leads to NULL. + +Figure 19.2.1/1: Process RECEIVE\_RESET\_IN\_GLR + +Figure 19.2.1/2 shows the Process SEND\_RESET\_TO\_VLR. This process is a GLR MAP protocol machine handling reset message to VLR. + +![Flowchart for Process SEND_RESET_TO_VLR. The process starts at an oval, goes to a 'Null' state, then a 'Reset' state. It then enters a loop waiting for 'MAP_OPEN_req', 'MAP_RESET_req', or 'MAP_DELIMITER_req'. Upon receiving one, it goes to 'Receive_Open_Cnf'. From there, an 'OK' response leads to 'MAP_CLOSE_req' (with 'Release method: Prearenged end'), an 'error' response leads to 'Aborted', and a 'Vr' response leads to 'Perform Vr dialogue'. All three paths lead to a final 'Null' state.](fe7304192caf64cda93b580c5e7e5c06_img.jpg) + +**Process SEND\_RESET\_TO\_VLR** 19.2.1.2(1) + +GLR MAP protocol machine handling reset message to VLR. + +Left to VLR +Right to GLR application + +``` +graph TD; Start([ ]) --> Null1[Null]; Null1 --> Reset[Reset]; Reset --> Wait{MAP_OPEN_req +MAP_RESET_req +MAP_DELIMITER_req}; Wait --> Receive[Receive_Open_Cnf]; Receive -- OK --> Close{MAP_CLOSE_req}; Close -- "Release method: +Prearenged end" --> Null2[Null]; Receive -- error --> Aborted{Aborted}; Aborted --> Null2; Receive -- Vr --> Perform[Perform Vr dialogue]; Perform --> Null2; +``` + +Flowchart for Process SEND\_RESET\_TO\_VLR. The process starts at an oval, goes to a 'Null' state, then a 'Reset' state. It then enters a loop waiting for 'MAP\_OPEN\_req', 'MAP\_RESET\_req', or 'MAP\_DELIMITER\_req'. Upon receiving one, it goes to 'Receive\_Open\_Cnf'. From there, an 'OK' response leads to 'MAP\_CLOSE\_req' (with 'Release method: Prearenged end'), an 'error' response leads to 'Aborted', and a 'Vr' response leads to 'Perform Vr dialogue'. All three paths lead to a final 'Null' state. + +Figure 19.2.1/2: Process SEND\_RESET\_TO\_VLR + +Figure 19.2.1/3 shows the Process SEND\_RESET\_TO\_SGSN. This process is a GLR MAP protocol machine handling reset message to SGSN. + +![Flowchart for Process SEND_RESET_TO_SGSN. The process starts at an oval, goes to a 'Null' state, then a 'Reset' message. It then checks for MAP_OPEN_req, MAP_RESET_req, or MAP_DELIMITER_req. Upon receiving an Open_Cnf, it checks for 'OK', 'error', or 'Vr'. 'OK' leads to a 'MAP_CLOSE_req' (with 'Release method: Prearenged end'), 'error' leads to 'Aborted', and 'Vr' leads to 'Perform Vr dialogue'. All three paths lead to a final 'Null' state.](c3fcdb9e14cb1f7e5e0232c5fe0c5198_img.jpg) + +**Process SEND\_RESET\_TO\_SGSN** 19.2.1.3(1) + +GLR MAP protocol machine handling reset message to SGSN. + +``` +graph TD; Start([ ]) --> Null1([Null]); Null1 --> Reset[Reset]; Reset --> Decision{MAP_OPEN_req +MAP_RESET_req +MAP_DELIMITER_req}; Decision --> Receive[Receive Open_Cnf]; Receive -- OK --> MAP_CLOSE_req{MAP_CLOSE_req}; MAP_CLOSE_req -- "Release method: Prearenged end" --> Null2([Null]); Receive -- error --> Aborted{Aborted}; Aborted --> Null2; Receive -- Vr --> Perform[Perform Vr dialogue]; Perform --> Null2; +``` + +Left to SGSN +Right to GLR application + +Flowchart for Process SEND\_RESET\_TO\_SGSN. The process starts at an oval, goes to a 'Null' state, then a 'Reset' message. It then checks for MAP\_OPEN\_req, MAP\_RESET\_req, or MAP\_DELIMITER\_req. Upon receiving an Open\_Cnf, it checks for 'OK', 'error', or 'Vr'. 'OK' leads to a 'MAP\_CLOSE\_req' (with 'Release method: Prearenged end'), 'error' leads to 'Aborted', and 'Vr' leads to 'Perform Vr dialogue'. All three paths lead to a final 'Null' state. + +Figure 19.2.1/3: Process SEND\_RESET\_TO\_SGSN + +### 19.2.2 VLR restoration: the restore data procedure in the GLR + +#### 19.2.2.1 General + +This procedure is used to restore the subscriber data for an unidentified MS (i.e. IMSI unknown in VLR), or for a known MS whose IMSI record is marked as "Not Confirmed" by the indicator "Confirmed by HLR" in VLR. + +If GLR is located between the VLR and the HLR, the MAP\_RESTORE\_DATA service is invoked towards the GLR whose identity is contained in the VLR table. When the GLR receives a MAP\_RESTORE\_DATA indication, it determines whether it invokes the MAP\_RESTORE\_DATA service towards the HLR, and invokes it if necessary. + +#### 19.2.2.2 Detailed procedure in GLR + +Figure 19.2.2/1 shows the Process RESTORE\_DATA\_GLR. This process is a GLR MAP protocol machine handling VLR restoration and is a responder to the VLR. + +![State transition diagram for Process RESTORE_DATA_GLR. It starts with an initial state leading to WAIT_FOR_SERVICE_PRIMITIVE. From there, it receives a MAP_RESTORE_DATA_ind primitive. A 'Restore data' action is performed, leading to connector 2. From connector 2, it enters WAIT_FOR_APPLICATION_RESPONSE. From this state, four actions are possible: 'Restore data Ack' (leading to 'Set result' and then MAP_RESTORE_DATA_Rsp. / MAP_CLOSE_Req.), 'Restore data Negative Response' (leading to 'Set error' and then MAP_RESTORE_DATA_Rsp. / MAP_CLOSE_Req.), 'Insert Subscriber Data' (leading to connector 1), and 'Abort' (leading to MAP_U_ABORT_req.). All three output primitives end with an 'X' symbol, indicating a transition to another state or process.](3337af75dfee8af7687b4f49914d6c93_img.jpg) + +### Process RESTORE\_DATA\_GLR + +19.2.2.1\_1(3) + +GLR MAP protocol machine handling VLR restoration and interfacing with VLR MAP protocol machine + +Left to VLR +Right to GLR application + +``` +graph TD; Start([ ]) --> S1(WAIT_FOR_SERVICE_PRIMITIVE); S1 --> I1{MAP_RESTORE_DATA_ind}; I1 --> A1[Restore data]; A1 --> C2((2)); C2 --> S2(WAIT_FOR_APPLICATION_RESPONSE); S2 --> A2[Restore data Ack]; S2 --> A3[Restore data Negative Response]; S2 --> A4[Insert Subscriber Data]; S2 --> A5[Abort]; A2 --> R1[Set result]; R1 --> O1{MAP_RESTORE_DATA_Rsp. / MAP_CLOSE_Req.}; O1 --> X1[X]; A3 --> R2[Set error]; R2 --> O2{MAP_RESTORE_DATA_Rsp. / MAP_CLOSE_Req.}; O2 --> X2[X]; A4 --> C1((1)); A5 --> O3{MAP_U_ABORT_req.}; O3 --> X3[X]; +``` + +State transition diagram for Process RESTORE\_DATA\_GLR. It starts with an initial state leading to WAIT\_FOR\_SERVICE\_PRIMITIVE. From there, it receives a MAP\_RESTORE\_DATA\_ind primitive. A 'Restore data' action is performed, leading to connector 2. From connector 2, it enters WAIT\_FOR\_APPLICATION\_RESPONSE. From this state, four actions are possible: 'Restore data Ack' (leading to 'Set result' and then MAP\_RESTORE\_DATA\_Rsp. / MAP\_CLOSE\_Req.), 'Restore data Negative Response' (leading to 'Set error' and then MAP\_RESTORE\_DATA\_Rsp. / MAP\_CLOSE\_Req.), 'Insert Subscriber Data' (leading to connector 1), and 'Abort' (leading to MAP\_U\_ABORT\_req.). All three output primitives end with an 'X' symbol, indicating a transition to another state or process. + +Figure 19.2.2/1 (Sheet 1 of 3): Process RESTORE\_DATA\_GLR + +![Flowchart for Process RESTORE_DATA_GLR. It starts at connector 1, leading to a decision diamond. The diamond has two input labels: 'MAP_Insert_Subscriber_Data_Req' and 'MAP_Delimiter_Req'. The main path goes down to a 'WAIT_FOR_ISD_Cnf' and 'WAIT_FOR_SUBSEQUENT_APPLICATION_RESPONSE' block. From there, it branches into three paths: 1) 'MAP_Insert_Subscriber_Data_Cnf' -> 'Check Confirmation' -> 'Insert_Subscriber_Data_Cnf' (connector 2). The 'Check Confirmation' block has three output labels: 'OK', 'Provider error Data error', and 'User error'. 'OK' leads to 'Insert_Subscriber_Data_Cnf'. 'Provider error Data error' and 'User error' both lead to 'Set Negative Response System Failure' -> 'ISD Negative Response' (connector 2). 2) A middle path leads to an 'Abort' block, which ends with a crossed-out circle. 3) 'MAP_NOTICE_Ind' -> 'Set Negative Result System Failure' -> 'ISD Negative Response' (connector 2). A side block contains 'MAP_U_ABORT_Ind', 'MAP_P_ABORT_Ind', and 'MAP_CLOSE_Ind' connected to the middle path.](9b1ec0090070bdf52ea28763b8d52477_img.jpg) + +### Process RESTORE\_DATA\_GLR + +19.2.2.1\_2(3) + +GLR MAP protocol machine handling VLR restoration and interfacing with VLR MAP protocol machine + +Left to VLR +Right to GLR application + +``` +graph TD; Start((1)) --> Decision{ }; Decision -- "MAP_Insert_Subscriber_Data_Req +MAP_Delimiter_Req" --> Decision; Decision --> Wait["WAIT_FOR_ISD_Cnf +WAIT_FOR_SUBSEQUENT_APPLICATION_RESPONSE"]; Wait --> InsertCnf["MAP_Insert_Subscriber_Data_Cnf"]; InsertCnf --> Check["Check Confirmation"]; Check -- "OK" --> InsertSub["Insert_Subscriber_Data_Cnf"]; InsertSub --> End2a((2)); Check -- "Provider error Data error" --> SetNeg["Set Negative Response System Failure"]; SetNeg --> ISDNeg["ISD Negative Response"]; ISDNeg --> End2b((2)); Check -- "User error" --> MAPUserErr["MAP User Error to Negative Response"]; MAPUserErr --> ISDNeg; Wait --> Abort["Abort"]; Abort --> X((X)); Wait --> Notice["MAP_NOTICE_Ind"]; Notice --> SetNegRes["Set Negative Result System Failure"]; SetNegRes --> ISDNegRes["ISD Negative Response"]; ISDNegRes --> End2c((2)); Side["MAP_U_ABORT_Ind +MAP_P_ABORT_Ind +MAP_CLOSE_Ind"] -.-> Abort; +``` + +Flowchart for Process RESTORE\_DATA\_GLR. It starts at connector 1, leading to a decision diamond. The diamond has two input labels: 'MAP\_Insert\_Subscriber\_Data\_Req' and 'MAP\_Delimiter\_Req'. The main path goes down to a 'WAIT\_FOR\_ISD\_Cnf' and 'WAIT\_FOR\_SUBSEQUENT\_APPLICATION\_RESPONSE' block. From there, it branches into three paths: 1) 'MAP\_Insert\_Subscriber\_Data\_Cnf' -> 'Check Confirmation' -> 'Insert\_Subscriber\_Data\_Cnf' (connector 2). The 'Check Confirmation' block has three output labels: 'OK', 'Provider error Data error', and 'User error'. 'OK' leads to 'Insert\_Subscriber\_Data\_Cnf'. 'Provider error Data error' and 'User error' both lead to 'Set Negative Response System Failure' -> 'ISD Negative Response' (connector 2). 2) A middle path leads to an 'Abort' block, which ends with a crossed-out circle. 3) 'MAP\_NOTICE\_Ind' -> 'Set Negative Result System Failure' -> 'ISD Negative Response' (connector 2). A side block contains 'MAP\_U\_ABORT\_Ind', 'MAP\_P\_ABORT\_Ind', and 'MAP\_CLOSE\_Ind' connected to the middle path. + +Figure 19.2.2/1 (Sheet 2 of 3): Process RESTORE\_DATA\_GLR + +![State transition diagram for Process RESTORE_DATA_GLR. The diagram shows four main paths originating from a central state labeled 'WAIT_FOR_ISD_Cnf' and 'WAIT_FOR_SUBSEQUENT_APPLICATION_RESPONSE'. Path 1: 'Restore_Data_Ack' (glide) leads to 'Set result' (action), which then leads to a merge point for 'MAP_RESTORE_DATA_Rsp.' and 'MAP_CLOSE_Req.' (glide), ending at a terminal state (X). Path 2: 'Restore_Data_Negative_Response' (glide) leads to 'Set Error' (action), which also leads to the same merge point. Path 3: 'Insert_Subscriber_Data' (glide) leads to a connector circle labeled '1'. Path 4: 'Abort' (glide) leads to 'MAP_U_ABORT_req' (action), which ends at a terminal state (X).](b34c69e1ec326b01c3a485b27b1df5f6_img.jpg) + +### Process RESTORE\_DATA\_GLR + +19.2.2.1\_3(3) + +GLR MAP protocol machine handling VLR restoration and interfacing with VLR MAP protocol machine + +Left to VLR +Right to GLR application + +``` +stateDiagram-v2 + [*] --> WAIT_FOR_ISD_Cnf + state "WAIT_FOR_ISD_Cnf
WAIT_FOR_SUBSEQUENT_APPLICATION_RESPONSE" as WAIT_FOR_ISD_Cnf + WAIT_FOR_ISD_Cnf --> Restore_Data_Ack + WAIT_FOR_ISD_Cnf --> Restore_Data_Negative_Response + WAIT_FOR_ISD_Cnf --> Insert_Subscriber_Data + WAIT_FOR_ISD_Cnf --> Abort + Restore_Data_Ack --> Set_result + Restore_Data_Negative_Response --> Set_Error + Insert_Subscriber_Data --> 1 + Abort --> MAP_U_ABORT_req + Set_result --> Merge + Set_Error --> Merge + Merge --> MAP_RESTORE_DATA_Rsp + MAP_RESTORE_DATA_Rsp --> [*] + MAP_U_ABORT_req --> [*] +``` + +State transition diagram for Process RESTORE\_DATA\_GLR. The diagram shows four main paths originating from a central state labeled 'WAIT\_FOR\_ISD\_Cnf' and 'WAIT\_FOR\_SUBSEQUENT\_APPLICATION\_RESPONSE'. Path 1: 'Restore\_Data\_Ack' (glide) leads to 'Set result' (action), which then leads to a merge point for 'MAP\_RESTORE\_DATA\_Rsp.' and 'MAP\_CLOSE\_Req.' (glide), ending at a terminal state (X). Path 2: 'Restore\_Data\_Negative\_Response' (glide) leads to 'Set Error' (action), which also leads to the same merge point. Path 3: 'Insert\_Subscriber\_Data' (glide) leads to a connector circle labeled '1'. Path 4: 'Abort' (glide) leads to 'MAP\_U\_ABORT\_req' (action), which ends at a terminal state (X). + +Figure 19.2.2/1 (Sheet 3 of 3): Process RESTORE\_DATA\_GLR + +Figure 19.2.2/2 shows the Process GLR\_RESTORE\_DATA\_HLR. This process is a GLR MAP protocol machine handling VLR restoration and is an initiator to the HLR. + +Sheet 1: If the Macro Open\_Receive\_Cnf results Vr, the process requests to perform MAP Vr. It causes a request for sending an abort message to Process RESTORE\_DATA\_GLR. + +![SDL diagram for Process GLR_RESTORE_DATA_HLR Sheet 1. The flow starts at IDLE, receives 'restore data', sends three MAP requests, then receives 'Open Cnf'. Branching occurs based on OK, Vr, or Error results.](68a5a1a1a761c652b4b4c56da7cf9914_img.jpg) + +**Process GLR\_RESTORE\_DATA\_HLR** 19.2.2.2\_1(3) + +GLR MAP protocol machine handling restore data and interfacing to HLR MAP protocol machine, handling restore data. + +Signals to/from the left are to/from the GLR application. +Signals to/from the right are to/from the HLR MAP protocol machine. + +``` + +stateDiagram-v2 + [*] --> IDLE + IDLE --> restore_data : restore data + state restore_data <> + restore_data --> Send_Requests + state Send_Requests { + direction TB + MAP_OPEN_Req + MAP_RESTORE_DATA_Req + MAP_DELIMITER_Req + } + Send_Requests --> Receive_Open_Cnf + state Receive_Open_Cnf { + direction TB + Section_25_1 : Section 25.1 + } + Receive_Open_Cnf --> OK + Receive_Open_Cnf --> Vr + Receive_Open_Cnf --> Error + + OK --> Wait_For_HLR_Response + Wait_For_HLR_Response --> [*] + + Vr --> Perform_MAP_Vr + Perform_MAP_Vr --> [*] + + Error --> Set_error + Set_error --> Restore_data_Negative_Response + Restore_data_Negative_Response --> [*] + +``` + +SDL diagram for Process GLR\_RESTORE\_DATA\_HLR Sheet 1. The flow starts at IDLE, receives 'restore data', sends three MAP requests, then receives 'Open Cnf'. Branching occurs based on OK, Vr, or Error results. + +Figure 19.2.2/2 (Sheet 1 of 3): Process GLR\_RESTORE\_DATA\_HLR + +![State transition diagram for Process GLR_RESTORE_DATA_HLR. The diagram shows four main paths starting from a 'Wait_For_HLR_Response' state. Path 1: MAP_RESTORE_DATA_cnf -> Check Confirmation (Section 25.2) -> OK (Restore data ack -> Idle) or Provider Error, User Error, Data Error (Set negative response -> Restore data negative response -> Idle). Path 2: MAP_INSERT_SUBSCRIBER_DATA_ind -> Insert Subscriber data -> Wait_For_HLR or Application_Response. Path 3: MAP_Notice_Indication -> MAP_Close_request -> Set negative response -> Restore data negative response -> Idle. Path 4: MAP_U_Abort_ind, MAP_P_Abort_ind, MAP_Close_ind -> Abort -> Idle.](56a5265d174ce056c1dbe5e7a60839fc_img.jpg) + +**Process GLR\_RESTORE\_DATA\_HLR** 19.2.2.2\_2(3) + +GLR MAP protocol machine handling restore data and interfacing to HLR MAP protocol machine, handling restore data. + +Signals to/from the left are to/from the GLR application. +Signals to/from the right are to/from the HLR MAP protocol machine. + +``` +stateDiagram-v2 + [*] --> Wait_For_HLR_Response + state "Wait_For_HLR_Response" as Wait_For_HLR_Response + state "MAP_RESTORE_DATA_cnf" as MAP_RESTORE_DATA_cnf + state "MAP_INSERT_SUBSCRIBER_DATA_ind" as MAP_INSERT_SUBSCRIBER_DATA_ind + state "MAP_Notice_Indication" as MAP_Notice_Indication + state "MAP_U_Abort_ind, MAP_P_Abort_ind, MAP_Close_ind" as MAP_U_Abort_ind, MAP_P_Abort_ind, MAP_Close_ind + state "Check Confirmation" as Check Confirmation + state "Section 25.2" as Section 25.2 + state "OK" as OK + state "Provider Error, User Error, Data Error" as Provider Error, User Error, Data Error + state "Restore data ack" as Restore data ack + state "Set negative response" as Set negative response + state "Restore data negative response" as Restore data negative response + state "Idle" as Idle + state "Insert Subscriber data" as Insert Subscriber data + state "Wait_For_HLR or Application_Response" as Wait_For_HLR or Application_Response + state "MAP_Close_request" as MAP_Close_request + state "Set negative response" as Set negative response + state "Restore data negative response" as Restore data negative response + state "Abort" as Abort + + Wait_For_HLR_Response --> MAP_RESTORE_DATA_cnf + Wait_For_HLR_Response --> MAP_INSERT_SUBSCRIBER_DATA_ind + Wait_For_HLR_Response --> MAP_Notice_Indication + Wait_For_HLR_Response --> MAP_U_Abort_ind, MAP_P_Abort_ind, MAP_Close_ind + + MAP_RESTORE_DATA_cnf --> Check Confirmation + Check Confirmation --> Section 25.2 + Section 25.2 --> OK + Section 25.2 --> Provider Error, User Error, Data Error + OK --> Restore data ack + Provider Error, User Error, Data Error --> Set negative response + Restore data ack --> Idle + Set negative response --> Restore data negative response + Restore data negative response --> Idle + + MAP_INSERT_SUBSCRIBER_DATA_ind --> Insert Subscriber data + Insert Subscriber data --> Wait_For_HLR or Application_Response + + MAP_Notice_Indication --> MAP_Close_request + MAP_Close_request --> Set negative response + Set negative response --> Restore data negative response + Restore data negative response --> Idle + + MAP_U_Abort_ind, MAP_P_Abort_ind, MAP_Close_ind --> Abort + Abort --> Idle +``` + +State transition diagram for Process GLR\_RESTORE\_DATA\_HLR. The diagram shows four main paths starting from a 'Wait\_For\_HLR\_Response' state. Path 1: MAP\_RESTORE\_DATA\_cnf -> Check Confirmation (Section 25.2) -> OK (Restore data ack -> Idle) or Provider Error, User Error, Data Error (Set negative response -> Restore data negative response -> Idle). Path 2: MAP\_INSERT\_SUBSCRIBER\_DATA\_ind -> Insert Subscriber data -> Wait\_For\_HLR or Application\_Response. Path 3: MAP\_Notice\_Indication -> MAP\_Close\_request -> Set negative response -> Restore data negative response -> Idle. Path 4: MAP\_U\_Abort\_ind, MAP\_P\_Abort\_ind, MAP\_Close\_ind -> Abort -> Idle. + +Figure 19.2.2/2 (Sheet 2 of 3): Process GLR\_RESTORE\_DATA\_HLR + +![State transition diagram for Process GLR_RESTORE_DATA_HLR. The diagram shows two main paths starting from 'Wait_For_HLR_or_Application_Response'. The left path handles 'MAP_RESTORE_DATA_cnf' with a 'Check Confirmation' (Section 25.2), leading to 'Restore data ack' (OK) or 'Set negative response' (Provider Error, User Error, Data Error), both ending at 'Idle'. The right path handles 'MAP_INSERT_SUBSCRIBER_DATA_ind' with 'Insert Subscriber data', leading to 'Insert Subscriber Data ack', 'Insert Subscriber Data negative response' (Set user error), or 'MAP_Insert Subscriber Data_response', all leading to another 'Wait_For_HLR_or_Application_Response' state. From this second wait state, 'Abort' leads to 'Map_U_Abort_request' then 'Idle'; 'MAP_Notice_Indication' leads to 'MAP_Close_request', 'Set negative response', 'Update Location negative response', then 'Idle'; and 'MAP_U_Abort_ind MAP_P_Abort_ind MAP_Close_ind' leads to 'Abort' then 'Idle'.](fd3cbb53e991f8209ba17b398f426e13_img.jpg) + +**Process GLR\_RESTORE\_DATA\_HLR** 19.2.2.2\_3(3) + +GLR MAP protocol machine handling restore data and interfacing to HLR MAP protocol machine, handling restore data. + +Signals to/from the left are to/from the GLR application. + Signals to/from the right are to/from the HLR MAP protocol machine. + +``` + +stateDiagram-v2 + [*] --> Wait_For_HLR_or_Application_Response + state "Wait_For_HLR_or_Application_Response" as Wait_For_HLR_or_Application_Response + state "MAP_RESTORE_DATA_cnf" as MAP_RESTORE_DATA_cnf + state "Check Confirmation" as Check Confirmation + state "OK" as OK + state "Provider Error, User Error, Data Error" as Provider_Error_User_Error_Data_Error + state "Restore data ack" as Restore_data_ack + state "Set negative response" as Set_negative_response + state "Restore data negative response" as Restore_data_negative_response + state "Idle" as Idle + state "MAP_INSERT_SUBSCRIBER_DATA_ind" as MAP_INSERT_SUBSCRIBER_DATA_ind + state "Insert Subscriber data" as Insert_Subscriber_data + state "Insert Subscriber Data ack" as Insert_Subscriber_Data_ack + state "Insert Subscriber Data negative response" as Insert_Subscriber_Data_negative_response + state "Set user error" as Set_user_error + state "MAP_Insert Subscriber Data_response" as MAP_Insert_Subscriber_Data_response + state "Wait_For_HLR_or_Application_Response_2" as Wait_For_HLR_or_Application_Response + state "Abort" as Abort + state "MAP_Notice_Indication" as MAP_Notice_Indication + state "MAP_Close_request" as MAP_Close_request + state "Set negative response_2" as Set_negative_response + state "Update Location negative response" as Update_Location_negative_response + state "MAP_U_Abort_request" as Map_U_Abort_request + state "MAP_U_Abort_ind MAP_P_Abort_ind MAP_Close_ind" as MAP_U_Abort_ind_MAP_P_Abort_ind_MAP_Close_ind + + Wait_For_HLR_or_Application_Response --> MAP_RESTORE_DATA_cnf + MAP_RESTORE_DATA_cnf --> Check Confirmation + Check Confirmation --> OK + Check Confirmation --> Provider_Error_User_Error_Data_Error + OK --> Restore_data_ack + Provider_Error_User_Error_Data_Error --> Set_negative_response + Restore_data_ack --> Idle + Set_negative_response --> Restore_data_negative_response + Restore_data_negative_response --> Idle + + Wait_For_HLR_or_Application_Response --> MAP_INSERT_SUBSCRIBER_DATA_ind + MAP_INSERT_SUBSCRIBER_DATA_ind --> Insert_Subscriber_data + Insert_Subscriber_data --> Insert_Subscriber_Data_ack + Insert_Subscriber_data --> Insert_Subscriber_Data_negative_response + Insert_Subscriber_Data_negative_response --> Set_user_error + Set_user_error --> MAP_Insert_Subscriber_Data_response + MAP_Insert_Subscriber_Data_response --> Wait_For_HLR_or_Application_Response_2 + + Wait_For_HLR_or_Application_Response_2 --> Abort + Wait_For_HLR_or_Application_Response_2 --> MAP_Notice_Indication + Wait_For_HLR_or_Application_Response_2 --> MAP_U_Abort_ind_MAP_P_Abort_ind_MAP_Close_ind + + Abort --> Map_U_Abort_request + Map_U_Abort_request --> Idle + + MAP_Notice_Indication --> MAP_Close_request + MAP_Close_request --> Set_negative_response_2 + Set_negative_response_2 --> Update_Location_negative_response + Update_Location_negative_response --> Idle + + MAP_U_Abort_ind_MAP_P_Abort_ind_MAP_Close_ind --> Abort + Abort --> Idle + +``` + +State transition diagram for Process GLR\_RESTORE\_DATA\_HLR. The diagram shows two main paths starting from 'Wait\_For\_HLR\_or\_Application\_Response'. The left path handles 'MAP\_RESTORE\_DATA\_cnf' with a 'Check Confirmation' (Section 25.2), leading to 'Restore data ack' (OK) or 'Set negative response' (Provider Error, User Error, Data Error), both ending at 'Idle'. The right path handles 'MAP\_INSERT\_SUBSCRIBER\_DATA\_ind' with 'Insert Subscriber data', leading to 'Insert Subscriber Data ack', 'Insert Subscriber Data negative response' (Set user error), or 'MAP\_Insert Subscriber Data\_response', all leading to another 'Wait\_For\_HLR\_or\_Application\_Response' state. From this second wait state, 'Abort' leads to 'Map\_U\_Abort\_request' then 'Idle'; 'MAP\_Notice\_Indication' leads to 'MAP\_Close\_request', 'Set negative response', 'Update Location negative response', then 'Idle'; and 'MAP\_U\_Abort\_ind MAP\_P\_Abort\_ind MAP\_Close\_ind' leads to 'Abort' then 'Idle'. + +Figure 19.2.2/2 (Sheet 3 of 3): Process GLR\_RESTORE\_DATA\_HLR + +# 20 Operations and maintenance procedures + +## 20.1 General + +The Operations and Maintenance procedures are needed for operating and maintaining the UMTS PLMN network. + +The following procedures exist for operation and maintenance purposes: + +- i) Tracing procedures; +- ii) Subscriber Data Management procedures; +- iii) Subscriber Identity procedures. + +The following application contexts refer to complex MAP Users consisting of several processes: + +- subscriberDataManagementContext; +- tracingContext. + +These two application contexts need a co-ordinating process in the VLR or in the SGSN. Refer to the 3GPP TS 29.002 for detail procedures. + +The Subscriber Data Management procedures are only procedures that impact to the GLR. The following subclause describes the Subscriber Identity procedures in the GLR. + +## 20.2 Subscriber data management procedures + +### 20.2.1 General + +Two types of subscriber data management procedures exist in the Mobile Application Part + +- i) Subscriber Deletion; +- ii) Subscriber Data Modification. + +No requirements have been identified for the Subscriber creation and subscriber data interrogation procedures. + +The subscriber deletion and subscriber data modification procedures are initiated by the OMC (see figures 20.2.1/1, 20.2.1/2, 20.2.1/3 and 20.2.1/4). + +![Sequence diagram of the subscriber deletion procedure. The diagram shows four lifelines: VLR, GLR, HLR, and OMC. The sequence of messages is: 1) OMC sends a message to HLR; 2) HLR sends a message to GLR; 3) GLR sends a message to VLR; 4) HLR sends a message to OMC. The legend below the diagram lists: 1) Delete Subscriber, 2) MAP_CANCEL_LOCATION, 3) MAP_CANCEL_LOCATION_ACK, 4) Subscriber Deleted.](ac42de838505beb048fb1267c46de428_img.jpg) + +``` +sequenceDiagram + participant OMC + participant HLR + participant GLR + participant VLR + Note right of OMC: 1) Delete Subscriber. + OMC->>HLR: 2) MAP_CANCEL_LOCATION + Note right of HLR: 3) MAP_CANCEL_LOCATION_ACK + HLR->>GLR: 3) MAP_CANCEL_LOCATION_ACK + Note right of GLR: 4) Subscriber Deleted. + GLR->>VLR: 4) Subscriber Deleted + Note right of HLR: 4) Subscriber Deleted. + HLR->>OMC: 4) Subscriber Deleted +``` + +- 1) Delete Subscriber. +- 2) MAP\_CANCEL\_LOCATION. +- 3) MAP\_CANCEL\_LOCATION\_ACK. +- 4) Subscriber Deleted. + +Sequence diagram of the subscriber deletion procedure. The diagram shows four lifelines: VLR, GLR, HLR, and OMC. The sequence of messages is: 1) OMC sends a message to HLR; 2) HLR sends a message to GLR; 3) GLR sends a message to VLR; 4) HLR sends a message to OMC. The legend below the diagram lists: 1) Delete Subscriber, 2) MAP\_CANCEL\_LOCATION, 3) MAP\_CANCEL\_LOCATION\_ACK, 4) Subscriber Deleted. + +**Figure 20.2.1/1: Subscriber deletion procedure** + +In the subscriber deletion procedure the subscriber data should be removed from the VLR and from the HLR. The HLR uses the MAP\_CANCEL\_LOCATION service. + +![Sequence diagram for Figure 20.2.1/2: Subscriber deletion procedure for GPRS. Lifelines: SGSN, GLR, HLR, OMC. The sequence is: 1. HLR sends a message to OMC; 2. SGSN sends a message to GLR; 3. GLR sends a message to HLR; 4. OMC sends a message to HLR.](61a7f401eb46fe99a71f27bc37493f04_img.jpg) + +``` + +sequenceDiagram + participant SGSN + participant GLR + participant HLR + participant OMC + Note right of HLR: 1. + HLR-->>OMC: + Note left of GLR: 2. + SGSN-->>GLR: + Note right of GLR: 3. + GLR-->>HLR: + Note right of OMC: 4. + OMC-->>HLR: + +``` + +Sequence diagram for Figure 20.2.1/2: Subscriber deletion procedure for GPRS. Lifelines: SGSN, GLR, HLR, OMC. The sequence is: 1. HLR sends a message to OMC; 2. SGSN sends a message to GLR; 3. GLR sends a message to HLR; 4. OMC sends a message to HLR. + +- 1) Delete GPRS Subscriber. +- 2) MAP\_CANCEL\_LOCATION. +- 3) MAP\_CANCEL\_LOCATION\_ACK. +- 4) GPRS Subscriber Deleted. + +**Figure 20.2.1/2: Subscriber deletion procedure for GPRS** + +In the subscriber deletion procedure the subscriber data should be removed from the SGSN and from the HLR. The HLR uses the MAP\_CANCEL\_LOCATION service. + +![Sequence diagram for Figure 20.2.1/3: Subscriber data modification procedure. Lifelines: VLR, GLR, HLR, OMC. The sequence is: 1. HLR sends a message to OMC; 2. VLR sends a message to GLR; 3. GLR sends a message to HLR; 4. OMC sends a message to HLR.](dd6c544ab685b25dd17f59456efcfbfc_img.jpg) + +``` + +sequenceDiagram + participant VLR + participant GLR + participant HLR + participant OMC + Note right of HLR: 1. + HLR-->>OMC: + Note left of GLR: 2. + VLR-->>GLR: + Note right of GLR: 3. + GLR-->>HLR: + Note right of OMC: 4. + OMC-->>HLR: + +``` + +Sequence diagram for Figure 20.2.1/3: Subscriber data modification procedure. Lifelines: VLR, GLR, HLR, OMC. The sequence is: 1. HLR sends a message to OMC; 2. VLR sends a message to GLR; 3. GLR sends a message to HLR; 4. OMC sends a message to HLR. + +- 1) Modify Subscriber Data. +- 2) MAP\_CANCEL\_LOCATION, MAP\_INSERT\_SUBSCRIBER\_DATA or MAP\_DELETE\_SUBSCRIBER\_DATA. +- 3) MAP\_CANCEL\_LOCATION\_ACK, MAP\_INSERT\_SUBSCRIBER\_DATA\_ACK or MAP\_DELETE\_SUBSCRIBER\_DATA\_ACK. +- 4) Subscriber Data Modified. + +**Figure 20.2.1/3: Subscriber data modification procedure** + +![Sequence diagram for Figure 20.2.1/4: Subscriber data modification procedure for GPRS. Lifelines: SGSN, GLR, HLR, OMC. The sequence is: 1. HLR sends a message to OMC; 2. SGSN sends a message to GLR; 3. GLR sends a message to HLR; 4. OMC sends a message to HLR.](bdd96f20e71f079cad85240efb3d3f24_img.jpg) + +``` + +sequenceDiagram + participant SGSN + participant GLR + participant HLR + participant OMC + Note right of HLR: 1. + HLR-->>OMC: + Note left of GLR: 2. + SGSN-->>GLR: + Note right of GLR: 3. + GLR-->>HLR: + Note right of OMC: 4. + OMC-->>HLR: + +``` + +Sequence diagram for Figure 20.2.1/4: Subscriber data modification procedure for GPRS. Lifelines: SGSN, GLR, HLR, OMC. The sequence is: 1. HLR sends a message to OMC; 2. SGSN sends a message to GLR; 3. GLR sends a message to HLR; 4. OMC sends a message to HLR. + +- 1) Modify Subscriber Data. +- 2) MAP\_CANCEL\_LOCATION, MAP\_INSERT\_SUBSCRIBER\_DATA or MAP\_DELETE\_SUBSCRIBER\_DATA. +- 3) MAP\_CANCEL\_LOCATION\_ACK, MAP\_INSERT\_SUBSCRIBER\_DATA\_ACK or MAP\_DELETE\_SUBSCRIBER\_DATA\_ACK. +- 4) Subscriber Data Modified. + +**Figure 20.2.1/4: Subscriber data modification procedure for GPRS** + +In the subscriber data modification procedure the subscriber data is modified in the HLR and when necessary also in the VLR or in the SGSN. The HLR initiates either the MAP\_INSERT\_SUBSCRIBER\_DATA, MAP\_DELETE\_SUBSCRIBER\_DATA or MAP\_CANCEL\_LOCATION service depending on the modified data. + +### 20.2.2 Procedures in the GLR + +#### 20.2.2.1 Subscriber deletion procedure + +The subscriber deletion procedure in the GLR is described in the subclause 19. + +#### 20.2.2.2 Subscriber data modification procedure + +When receiving either the MAP\_INSERT\_SUBSCRIBER\_DATA indication or the MAP\_DELETE\_SUBSCRIBER\_DATA indication, the GLR checks the parameters and data in the primitive. Data errors are reported as an unexpected data value error or a data missing error depending on the nature of the error. + +After receiving the first MAP\_INSERT\_SUBSCRIBER\_DATA indication, the GLR will check the IMSI that is included in the primitive. If the IMSI is unknown, the error "Unidentified subscriber" is returned. + +If the GLR does not support received basic or supplementary services or the network feature Operator Determined Barring, or there is a problem with Regional Subscription Data then this is reported to the HLR. + +If the entire MSC area that covered the VLR wherein the subscriber is registered is restricted due to regional subscription, this is reported to the HLR. + +If the updating of the subscriber data is not possible, the GLR will initiate the MAP\_U\_ABORT request primitive. + +If the updating is successful in the GLR, the GLR will initiate the MAP\_INSERT\_SUBSCRIBER\_DATA request or the MAP\_DELETE\_SUBSCRIBER\_DATA request to the VLR or to the SGSN wherein the subscriber is registered. + +The subscriber data modification procedure in the GLR is shown in the figures 20.2.2.2/1, 20.2.2.2/2, 20.2.2.2/3, 20.2.2.2/4, 20.2.2.2/5 and 20.2.2.2/6. + +![Flowchart for Process INS_SUBS_DATA_GLR. The process starts with NULL, receives an Open Indication, and then enters a Wait_For_indication state. It then checks for MAP_INSERT_SUBSCRIBER_DATA_ind, MAP_NOTICE_ind, MAP_U_ABORT_ind, MAP_P_ABORT_ind, and MAP_CLOSE_ind. If none are present, it proceeds to Check_Indication. If MAP_NOTICE_ind is present, it sends a MAP_CLOSE_req. If MAP_INSERT_SUBSCRIBER_DATA_ind is present, it proceeds to Parameter OK. If Parameter OK is Yes, it checks if IMSI is Known. If IMSI is Known, it proceeds to connector 1. If IMSI is not Known, it sets UE to Unidentified Subscriber. If Parameter OK is No, it sets UE to Unexpected Data value. Both UE setting actions lead to MAP_INSERT_SUBSCRIBER_DATA_rsp and MAP_CLOSE_Req, which then lead to connector 1. If any error occurs at the Wait_For_indication stage, it leads to a NULL state with a 'Vr' 'Error' message.](5801c19431e76330430e92a598cc7a16_img.jpg) + +### Process INS\_SUBS\_DATA\_GLR + +20.2.2.2.1\_1(3) + +Figure 20.2.2.2/1: The insert subscriber data process in the GLR + +Arrows to left are to VLR +Arrows to right are to HLR + +``` +graph TD + NULL1([NULL]) --> Receive[Receive Open Ind] + Receive -- OK --> Wait[Wait_For_indication] + Wait --> NULL2([NULL]) + Wait --> MAP_INSERT[MAP_INSERT_SUBSCRIBER_DATA_ind] + Wait --> MAP_NOTICE[MAP_NOTICE_ind] + Wait --> MAP_ABORT[MAP_U_ABORT_ind, MAP_P_ABORT_ind, MAP_CLOSE_ind] + MAP_NOTICE --> MAP_CLOSE_req[MAP_CLOSE_req] + MAP_CLOSE_req --> X1((X)) + MAP_INSERT --> Check[Check_Indication] + Check -- Ok --> ParamOK{Parameter OK} + ParamOK -- Yes --> IMSI{IMSI Known} + ParamOK -- No --> SetUE[Set UE= Unexpected Data value] + IMSI -- Yes --> 1((1)) + IMSI -- No --> SetUE2[Set UE= Unidentified Subscriber] + SetUE2 --> MAP_RSP[MAP_INSERT_SUBSCRIBER_DATA_rsp, MAP_CLOSE_Req] + SetUE --> MAP_RSP + MAP_RSP --> X2((X)) + X2 --> 1 +``` + +Flowchart for Process INS\_SUBS\_DATA\_GLR. The process starts with NULL, receives an Open Indication, and then enters a Wait\_For\_indication state. It then checks for MAP\_INSERT\_SUBSCRIBER\_DATA\_ind, MAP\_NOTICE\_ind, MAP\_U\_ABORT\_ind, MAP\_P\_ABORT\_ind, and MAP\_CLOSE\_ind. If none are present, it proceeds to Check\_Indication. If MAP\_NOTICE\_ind is present, it sends a MAP\_CLOSE\_req. If MAP\_INSERT\_SUBSCRIBER\_DATA\_ind is present, it proceeds to Parameter OK. If Parameter OK is Yes, it checks if IMSI is Known. If IMSI is Known, it proceeds to connector 1. If IMSI is not Known, it sets UE to Unidentified Subscriber. If Parameter OK is No, it sets UE to Unexpected Data value. Both UE setting actions lead to MAP\_INSERT\_SUBSCRIBER\_DATA\_rsp and MAP\_CLOSE\_Req, which then lead to connector 1. If any error occurs at the Wait\_For\_indication stage, it leads to a NULL state with a 'Vr' 'Error' message. + +Figure 20.2.2.2/1 (Sheet 1 of 3): Process INS\_SUBS\_DATA\_GLR + +![Flowchart of Process INS_SUBS_DATA_GLR. It starts with a connector '1', followed by a decision diamond with MAP_OPEN_Req, MAP_INSERT_SUBSCRIBER_DATA_Req, and MAP_DELIMITER. A 'Receive Open Cnf' block follows. From there, an 'OK' path leads to a 'WF PRIMITIVE_OR_CLOSE' block, while a 'Vr, Error' path leads to a 'MAP U ABORT_req' block which ends in a cross. The 'WF PRIMITIVE_OR_CLOSE' block branches into three paths: 1) MAP_CLOSE_ind. -> MAP_CLOSE_req (ends in a cross); 2) MAP_NOTICE_ind -> MAP_CLOSE_req -> MAP_U_ABORT_ind -> 'Set Not Confirmed by HLR' (ends in a cross); 3) MAP_U_ABORT_ind. / MAP_P_ABORT_ind -> MAP_U_ABORT_ind -> 'Set Not Confirmed by HLR' -> MAP U ABORT req (ends in a cross). There is also a second set of three paths starting from a horizontal line: 1) MAP_CLOSE_ind. -> MAP_CLOSE_req (ends in a cross); 2) MAP_NOTICE_ind -> MAP_CLOSE_req; 3) MAP_U_ABORT_ind. / MAP_P_ABORT_ind -> 'Set Not Confirmed by HLR' -> MAP U ABORT req (ends in a cross). The 'MAP_CLOSE_req' from the second set of paths 2) connects to the 'Set Not Confirmed by HLR' block in the first set of paths 3).](db39acbd11df5eb7e79ab84562fb8f74_img.jpg) + +### Process INS\_SUBS\_DATA\_GLR + +20.2.2.2.1\_2(3) + +Figure 20.2.2.2/1: The insert subscriber data process in the GLR + +Arrows to left are to VLR +Arrows to right are to HLR + +Flowchart of Process INS\_SUBS\_DATA\_GLR. It starts with a connector '1', followed by a decision diamond with MAP\_OPEN\_Req, MAP\_INSERT\_SUBSCRIBER\_DATA\_Req, and MAP\_DELIMITER. A 'Receive Open Cnf' block follows. From there, an 'OK' path leads to a 'WF PRIMITIVE\_OR\_CLOSE' block, while a 'Vr, Error' path leads to a 'MAP U ABORT\_req' block which ends in a cross. The 'WF PRIMITIVE\_OR\_CLOSE' block branches into three paths: 1) MAP\_CLOSE\_ind. -> MAP\_CLOSE\_req (ends in a cross); 2) MAP\_NOTICE\_ind -> MAP\_CLOSE\_req -> MAP\_U\_ABORT\_ind -> 'Set Not Confirmed by HLR' (ends in a cross); 3) MAP\_U\_ABORT\_ind. / MAP\_P\_ABORT\_ind -> MAP\_U\_ABORT\_ind -> 'Set Not Confirmed by HLR' -> MAP U ABORT req (ends in a cross). There is also a second set of three paths starting from a horizontal line: 1) MAP\_CLOSE\_ind. -> MAP\_CLOSE\_req (ends in a cross); 2) MAP\_NOTICE\_ind -> MAP\_CLOSE\_req; 3) MAP\_U\_ABORT\_ind. / MAP\_P\_ABORT\_ind -> 'Set Not Confirmed by HLR' -> MAP U ABORT req (ends in a cross). The 'MAP\_CLOSE\_req' from the second set of paths 2) connects to the 'Set Not Confirmed by HLR' block in the first set of paths 3). + +Figure 20.2.2.2/1 (Sheet 2 of 3): Process INS\_SUBS\_DATA\_GLR + +![Flowchart for Process INS_SUBS_DATA_GLR. It starts with a 'WF PRIMITIVE_OR_CLOSE' primitive, followed by 'MAP_INSERT_SUBSCRIBER_DATA_ind'. A decision 'Parameters OK' follows. If 'No', it goes to 'Set UE= Unexpected Data Value' and then to an unlabeled connector. If 'Yes', it sends 'MAP_INSERT_SUBSCRIBER_DATA_req' and 'MAP_DELIMITER_req' to the VLR, then receives 'MAP_INSERT_SUBSCRIBER_DATA_rsp' and 'MAP_DELIMITER_req' from the VLR. Next, a decision 'Roaming_restriction_due_to_unsupported_feature_or_MSC_are_restricted_received' is made. If 'Yes', it performs a 'GLR internal action'. If 'No', it sends a response to the HLR. The HLR sends 'MAP_INSERT_SUBSCRIBER_DATA_cnf' to the GLR. A 'Check Confirmation' block follows. If 'OK', it checks 'Service unsupported in VLR?'. If 'Yes', it performs a 'GLR internal action'. If 'No', it sends a response to the HLR. If 'User error, Data error' or 'Provider error', it sends 'MAP_U_ABORT_req' to the HLR. Finally, it calls 'Save subscriber data' and ends with another 'WF PRIMITIVE_OR_CLOSE' primitive.](e2c120be98ede6deb60dd341f5a9803b_img.jpg) + +### Process INS\_SUBS\_DATA\_GLR + +20.2.2.2.1\_3(3) + +Figure 20.2.2.2/1: The insert subscriber data process in the GLR + +Arrows to left are to VLR +Arrows to right are to HLR + +``` +graph TD + Start((WF PRIMITIVE_OR_CLOSE)) --> Ind{MAP_INSERT_SUBSCRIBER_DATA_ind} + Ind --> ParamsOK{Parameters OK} + ParamsOK -- No --> SetUE[Set UE= Unexpected Data Value] + SetUE --> UnlabeledConnector[ ] + ParamsOK -- Yes --> Req1[MAP_INSERT_SUBSCRIBER_DATA_req +MAP_DELIMITER_req] + Req1 --> Connector1[ ] + Connector1 --> Rsp1[MAP_INSERT_SUBSCRIBER_DATA_rsp +MAP_DELIMITER_req] + Rsp1 --> RoamingRestriction{Roaming_restriction_due_to_unsupported_feature_or_MSC_are_restricted_received} + RoamingRestriction -- Yes --> GLRAction1[GLR internal action] + RoamingRestriction -- No --> Connector2[ ] + Connector2 --> Rsp2[MAP_INSERT_SUBSCRIBER_DATA_rsp +MAP_DELIMITER_req] + Rsp2 --> SaveData[Save subscriber data] + SaveData --> End((WF PRIMITIVE_OR_CLOSE)) + Ind --> Cnf{MAP_INSERT_SUBSCRIBER_DATA_cnf} + Cnf --> CheckConf[Check Confirmation] + CheckConf -- OK --> ServiceUnsupported{Service unsupported in VLR?} + ServiceUnsupported -- Yes --> GLRAction2[GLR internal action] + ServiceUnsupported -- No --> Connector3[ ] + CheckConf -- "User error, Data error" --> AbortReq1{MAP_U_ABORT_req} + CheckConf -- "Provider error" --> AbortReq2{MAP_U_ABORT_req} + AbortReq1 --> HLR[ ] + AbortReq2 --> HLR + HLR --> Connector3 +``` + +Flowchart for Process INS\_SUBS\_DATA\_GLR. It starts with a 'WF PRIMITIVE\_OR\_CLOSE' primitive, followed by 'MAP\_INSERT\_SUBSCRIBER\_DATA\_ind'. A decision 'Parameters OK' follows. If 'No', it goes to 'Set UE= Unexpected Data Value' and then to an unlabeled connector. If 'Yes', it sends 'MAP\_INSERT\_SUBSCRIBER\_DATA\_req' and 'MAP\_DELIMITER\_req' to the VLR, then receives 'MAP\_INSERT\_SUBSCRIBER\_DATA\_rsp' and 'MAP\_DELIMITER\_req' from the VLR. Next, a decision 'Roaming\_restriction\_due\_to\_unsupported\_feature\_or\_MSC\_are\_restricted\_received' is made. If 'Yes', it performs a 'GLR internal action'. If 'No', it sends a response to the HLR. The HLR sends 'MAP\_INSERT\_SUBSCRIBER\_DATA\_cnf' to the GLR. A 'Check Confirmation' block follows. If 'OK', it checks 'Service unsupported in VLR?'. If 'Yes', it performs a 'GLR internal action'. If 'No', it sends a response to the HLR. If 'User error, Data error' or 'Provider error', it sends 'MAP\_U\_ABORT\_req' to the HLR. Finally, it calls 'Save subscriber data' and ends with another 'WF PRIMITIVE\_OR\_CLOSE' primitive. + +Figure 20.2.2.2/1 (Sheet 3 of 3): Process INS\_SUBS\_DATA\_GLR + +![Flowchart for Process INS_GPRS_SUBS_DATA_GLR. It starts with 'NULL' leading to 'Receive Open Ind'. From 'Receive Open Ind', an 'OK' path leads to 'Wait_For_indication' and a 'MAP_INSET_SUBSCRIBER_DATA_ind' message to the SGSN. A 'Vr Error' path leads to another 'NULL' state. From 'Wait_For_indication', three messages are sent to the HLR: 'MAP_INSET_SUBSCRIBER_DATA_ind', 'MAP_NOTICE_ind', and a group containing 'MAP_U_ABORT_ind', 'MAP_P_ABORT_ind', and 'MAP_CLOSE_ind'. 'MAP_NOTICE_ind' leads to 'MAP_CLOSE_req' to the SGSN. 'MAP_INSET_SUBSCRIBER_DATA_ind' leads to 'Check_Indication'. From 'Check_Indication', an 'OK' path leads to 'Parameter OK'. From 'Parameter OK', 'Yes' leads to 'IMSI Known' and 'Error'/'No' leads to 'Set UE= Unexpected Data value'. From 'IMSI Known', 'Yes' leads to connector '1' and 'No' leads to 'Set UE= Unidentified Subscriber'. Both 'Set UE' blocks lead to 'MAP_INSERT_SUBSCRIBER_DATA_rsp' and 'MAP_CLOSE_req' to the HLR, which then ends in a crossed-out state.](0f6e3cdce0f01d6ccceabcced508bb5b_img.jpg) + +### Process INS\_GPRS\_SUBS\_DATA\_GLR + +20.2.2.2.2\_1(3) + +Figure 20.2.2.2/2: The insert subscriber data process in the GLR + +Arrows to left are to SGSN +Arrows to right are to HLR + +``` +graph TD + NULL1(NULL) --> RecOpenInd[Receive Open Ind] + RecOpenInd -- OK --> WaitForInd[Wait_For_indication] + RecOpenInd -- "'Vr' 'Error'" --> NULL2(NULL) + WaitForInd --> MAP_INSET_IND[MAP_INSET_SUBSCRIBER_DATA_ind] + WaitForInd --> MAP_NOTICE_IND[MAP_NOTICE_ind] + WaitForInd --> MAP_U_ABORT_IND[MAP_U_ABORT_ind] + WaitForInd --> MAP_P_ABORT_IND[MAP_P_ABORT_ind] + WaitForInd --> MAP_CLOSE_IND[MAP_CLOSE_ind] + MAP_NOTICE_IND --> MAP_CLOSE_REQ1[MAP_CLOSE_req] + MAP_CLOSE_REQ1 --> X1((X)) + MAP_INSET_IND --> CheckInd[Check_Indication] + CheckInd -- OK --> ParamOK{Parameter OK} + ParamOK -- Yes --> IMSIKnown{IMSI Known} + ParamOK -- Error --> SetUEUnexpected[Set UE= Unexpected Data value] + ParamOK -- No --> SetUEUnexpected + IMSIKnown -- Yes --> Connector1((1)) + IMSIKnown -- No --> SetUEUnidentified[Set UE= Unidentified Subscriber] + SetUEUnidentified --> MAP_INSERT_RSP[MAP_INSERT_SUBSCRIBER_DATA_rsp] + SetUEUnexpected --> MAP_INSERT_RSP + MAP_INSERT_RSP --> MAP_CLOSE_REQ2[MAP_CLOSE_req] + MAP_CLOSE_REQ2 --> X2((X)) +``` + +Flowchart for Process INS\_GPRS\_SUBS\_DATA\_GLR. It starts with 'NULL' leading to 'Receive Open Ind'. From 'Receive Open Ind', an 'OK' path leads to 'Wait\_For\_indication' and a 'MAP\_INSET\_SUBSCRIBER\_DATA\_ind' message to the SGSN. A 'Vr Error' path leads to another 'NULL' state. From 'Wait\_For\_indication', three messages are sent to the HLR: 'MAP\_INSET\_SUBSCRIBER\_DATA\_ind', 'MAP\_NOTICE\_ind', and a group containing 'MAP\_U\_ABORT\_ind', 'MAP\_P\_ABORT\_ind', and 'MAP\_CLOSE\_ind'. 'MAP\_NOTICE\_ind' leads to 'MAP\_CLOSE\_req' to the SGSN. 'MAP\_INSET\_SUBSCRIBER\_DATA\_ind' leads to 'Check\_Indication'. From 'Check\_Indication', an 'OK' path leads to 'Parameter OK'. From 'Parameter OK', 'Yes' leads to 'IMSI Known' and 'Error'/'No' leads to 'Set UE= Unexpected Data value'. From 'IMSI Known', 'Yes' leads to connector '1' and 'No' leads to 'Set UE= Unidentified Subscriber'. Both 'Set UE' blocks lead to 'MAP\_INSERT\_SUBSCRIBER\_DATA\_rsp' and 'MAP\_CLOSE\_req' to the HLR, which then ends in a crossed-out state. + +Figure 20.2.2.2/2 (Sheet 1 of 3): Process INS\_GPRS\_SUBS\_DATA\_GLR + +![Sequence diagram for Process INS_GPRS_SUBS_DATA_GLR. The diagram shows the interaction between a GLR and an HLR. It starts with a circle labeled '1'. The GLR sends MAP_OPEN_Req, MAP_INSERT_SUBSCRIBER_DATA_Req, and MAP_DELIMITER to the HLR. The HLR responds with 'Recieve Open conf'. From this point, two paths emerge: 'OK' leads to 'WF PRIMITIVE_OR_CLOSE', and 'Vr, Error' leads to 'MAP U_ABORT_req' (terminated). 'WF PRIMITIVE_OR_CLOSE' branches into three parallel paths: 1) MAP_CLOSE_ind. -> MAP_CLOSE_req (terminated); 2) MAP NOTICE -> MAP_CLOSE_req -> MAP_U_ABORT_ind -> 'Set Not Confirmed by HLR' (terminated); 3) MAP_U_ABORT_ind. / MAP_P_ABORT_ind -> MAP_U_ABORT_ind -> 'Set Not Confirmed by HLR' -> MAP U_ABORT req (terminated). A second parallel sequence follows: MAP_CLOSE_ind. -> MAP_CLOSE_req (terminated); MAP NOTICE ind -> MAP_CLOSE_req -> 'Set Not Confirmed by HLR' -> MAP U_ABORT req (terminated); MAP_U_ABORT_ind. / MAP_P_ABORT_ind -> 'Set Not Confirmed by HLR' -> MAP U_ABORT req (terminated).](5e9af8986a5845504f251d3079da8078_img.jpg) + +### Process INS\_GPRS\_SUBS\_DATA\_GLR + +20.2.2.2.2\_2(3) + +Figure 20.2.2.2/2: The insert subscriber data process in the GLR + +Arrows to left are to SGSN +Arrows to right are to HLR + +``` +sequenceDiagram + participant GLR + participant HLR + Note left of GLR: 1 + GLR->>HLR: MAP_OPEN_Req, MAP_INSERT_SUBSCRIBER_DATA_Req, MAP_DELIMITER + HLR-->>GLR: Recieve Open conf + Note right of GLR: OK + Note right of GLR: Vr, Error + GLR->>HLR: MAP U_ABORT_req + Note right of GLR: X + GLR->>HLR: WF PRIMITIVE_OR_CLOSE + Note right of GLR: MAP_CLOSE_ind. + Note right of GLR: MAP NOTICE + Note right of GLR: MAP_U_ABORT_ind. / MAP_P_ABORT_ind + Note right of GLR: MAP_CLOSE_ind. + Note right of GLR: MAP NOTICE ind + Note right of GLR: MAP_U_ABORT_ind. / MAP_P_ABORT_ind + Note right of GLR: MAP_CLOSE_req + Note right of GLR: MAP_CLOSE_req + Note right of GLR: MAP_U_ABORT_ind + Note right of GLR: MAP_CLOSE_req + Note right of GLR: Set Not Confirmed by HLR + Note right of GLR: MAP U_ABORT req + Note right of GLR: X +``` + +Sequence diagram for Process INS\_GPRS\_SUBS\_DATA\_GLR. The diagram shows the interaction between a GLR and an HLR. It starts with a circle labeled '1'. The GLR sends MAP\_OPEN\_Req, MAP\_INSERT\_SUBSCRIBER\_DATA\_Req, and MAP\_DELIMITER to the HLR. The HLR responds with 'Recieve Open conf'. From this point, two paths emerge: 'OK' leads to 'WF PRIMITIVE\_OR\_CLOSE', and 'Vr, Error' leads to 'MAP U\_ABORT\_req' (terminated). 'WF PRIMITIVE\_OR\_CLOSE' branches into three parallel paths: 1) MAP\_CLOSE\_ind. -> MAP\_CLOSE\_req (terminated); 2) MAP NOTICE -> MAP\_CLOSE\_req -> MAP\_U\_ABORT\_ind -> 'Set Not Confirmed by HLR' (terminated); 3) MAP\_U\_ABORT\_ind. / MAP\_P\_ABORT\_ind -> MAP\_U\_ABORT\_ind -> 'Set Not Confirmed by HLR' -> MAP U\_ABORT req (terminated). A second parallel sequence follows: MAP\_CLOSE\_ind. -> MAP\_CLOSE\_req (terminated); MAP NOTICE ind -> MAP\_CLOSE\_req -> 'Set Not Confirmed by HLR' -> MAP U\_ABORT req (terminated); MAP\_U\_ABORT\_ind. / MAP\_P\_ABORT\_ind -> 'Set Not Confirmed by HLR' -> MAP U\_ABORT req (terminated). + +Figure 20.2.2.2/2 (Sheet 2 of 3): Process INS\_GPRS\_SUBS\_DATA\_GLR + +![Flowchart for Process INS_GPRS_SUBS_DATA_GLR. The process starts with a 'WF PRIMITIVE_OR_CLOSE' connector, followed by 'MAP_INSERT_SUBSCRIBER_DATA_ind'. A decision 'Parameters OK' follows. If 'No', it goes to 'Set UE= Unexpected Data Value' and then to an unlabeled connector. If 'Yes', it goes to 'MAP_INSERT_SUBSCRIBER_DATA_req' (with 'MAP_DELIMITER_req'), then to another unlabeled connector, then to 'MAP_INSERT_SUBSCRIBER_DATA_rsp' (with 'MAP_DELIMITER_req'). Both unlabeled connectors lead to a 'Roaming restriction due to unsupported feature or MSC are restricted received' decision. If 'Yes', it goes to 'GLR internal action'. If 'No', it goes to an unlabeled connector, then to 'MAP_INSERTt_SUBSCRIBER_DATA_rsp' (with 'MAP_DELIMITER_req'), then to 'Save subscriber data'. From 'Save subscriber data', the flow goes to 'MAP_INSERT_SUBSCRIBER_DATA_cnf', then to 'Check Confirmation'. From 'Check Confirmation', 'OK' leads to a 'Service unsupported in VLR?' decision. If 'Yes', it goes to 'GLR internal action'. If 'No', it leads to the unlabeled connector before 'MAP_INSERTt_SUBSCRIBER_DATA_rsp'. From 'Check Confirmation', 'User error, Data error' leads to 'MAP_U_ABORT_req' (to SGSN) and 'Provider error' leads to 'MAP_U_ABORT_req' (to HLR). The process ends at another 'WF PRIMITIVE_OR_CLOSE' connector.](4b398c5e8c4fd656d5b7a61806400650_img.jpg) + +**Process INS\_GPRS\_SUBS\_DATA\_GLR** 20.2.2.2.2\_3(3) + +Figure 20.2.2.2/2: The insert subscriber data process in the GLR + +Arrows to left are to SGSN + Arrows to right are to HLR + +``` + +graph TD + Start((WF PRIMITIVE_OR_CLOSE)) --> Ind{MAP_INSERT_SUBSCRIBER_DATA_ind} + Ind --> Params{Parameters OK} + Params -- No --> SetUE[Set UE= Unexpected Data Value] + SetUE --> C1{ } + Params -- Yes --> Req1[MAP_INSERT_SUBSCRIBER_DATA_req +MAP_DELIMITER_req] + Req1 --> C2{ } + C1 --> Roaming{Roaming restriction due to unsupported feature or MSC are restricted received} + C2 --> Roaming + Roaming -- Yes --> GLR1[GLR internal action] + Roaming -- No --> C3{ } + C3 --> Req2[MAP_INSERTt_SUBSCRIBER_DATA_rsp +MAP_DELIMITER_req] + Req2 --> Save[Save subscriber data] + Save --> Cnf{MAP_INSERT_SUBSCRIBER_DATA_cnf} + Cnf --> Check[Check Confirmation] + Check -- OK --> Service{Service unsupported in VLR?} + Service -- Yes --> GLR2[GLR internal action] + Service -- No --> C3 + Check -- "User error, Data error" --> Abort1{MAP_U_ABORT_req} + Abort1 --> SGSN[SGSN] + Check -- "Provider error" --> Abort2{MAP_U_ABORT_req} + Abort2 --> HLR[HLR] + End((WF PRIMITIVE_OR_CLOSE)) + +``` + +Flowchart for Process INS\_GPRS\_SUBS\_DATA\_GLR. The process starts with a 'WF PRIMITIVE\_OR\_CLOSE' connector, followed by 'MAP\_INSERT\_SUBSCRIBER\_DATA\_ind'. A decision 'Parameters OK' follows. If 'No', it goes to 'Set UE= Unexpected Data Value' and then to an unlabeled connector. If 'Yes', it goes to 'MAP\_INSERT\_SUBSCRIBER\_DATA\_req' (with 'MAP\_DELIMITER\_req'), then to another unlabeled connector, then to 'MAP\_INSERT\_SUBSCRIBER\_DATA\_rsp' (with 'MAP\_DELIMITER\_req'). Both unlabeled connectors lead to a 'Roaming restriction due to unsupported feature or MSC are restricted received' decision. If 'Yes', it goes to 'GLR internal action'. If 'No', it goes to an unlabeled connector, then to 'MAP\_INSERTt\_SUBSCRIBER\_DATA\_rsp' (with 'MAP\_DELIMITER\_req'), then to 'Save subscriber data'. From 'Save subscriber data', the flow goes to 'MAP\_INSERT\_SUBSCRIBER\_DATA\_cnf', then to 'Check Confirmation'. From 'Check Confirmation', 'OK' leads to a 'Service unsupported in VLR?' decision. If 'Yes', it goes to 'GLR internal action'. If 'No', it leads to the unlabeled connector before 'MAP\_INSERTt\_SUBSCRIBER\_DATA\_rsp'. From 'Check Confirmation', 'User error, Data error' leads to 'MAP\_U\_ABORT\_req' (to SGSN) and 'Provider error' leads to 'MAP\_U\_ABORT\_req' (to HLR). The process ends at another 'WF PRIMITIVE\_OR\_CLOSE' connector. + +Figure 20.2.2.2/2 (Sheet 3 of 3): Process INS\_GPRS\_SUBS\_DATA\_GLR + +![Flowchart for Process Delete_Subscriber_Data_GLR. The process starts with NULL, receives an Open Indication, and checks if the subscriber is known. If not known, it sets the UE as an unidentified subscriber. If known, it checks if services are registered in a GLR. If not registered, it sets the subscriber as not confirmed by the HLR. If registered, it proceeds to delete subscriber data in the GLR, which then leads to Figure 20.2.2.2/5. Both successful and error paths from the deletion step lead to sending a response and close request to the HLR.](347010b7ac06d3ae97927fde0f784d7c_img.jpg) + +### Process Delete\_Subscriber\_Data\_GLR + +20.2.2.2.3(1) + +Figure 20.2.2.2/3: The delete subscriber data process in the GLR + +Arrows to left are to VLR +Arrows to right are to HLR + +``` +graph TD; NULL1(NULL) --> RecOpenInd[Receive Open Ind]; RecOpenInd -- OK --> WaitForInd[Wait_For indication]; RecOpenInd -- "'Vr' 'Error'" --> NULL2(NULL); WaitForInd --> MAP_DEL_SUB[MAP_DELETE_SUBSCRIBER_DATA ind]; MAP_DEL_SUB --> CheckInd[Check Indication]; CheckInd --> SubKnow{Subscriber Know}; SubKnow -- Yes --> ServicesReg{Services registered in a GLR}; SubKnow -- No --> SetUE[Set UE= Unidentified Subscriber]; SubKnow -- Error --> SetNotConf[Set Not Confirmed by HLR]; ServicesReg -- Yes --> DeleteSubs[Delete Subs Data GLR]; ServicesReg -- No --> JoinX1((X)); SetUE --> JoinX1; SetNotConf --> JoinX1; DeleteSubs -- "Figure 20.2.2.2/5" --> JoinX1; DeleteSubs -- OK --> DeleteData[Delete Subscriber Data in the GLR]; DeleteData -- Error --> JoinX2((X)); DeleteData --> MAP_DEL_RSP[MAP_DELETE_SUBSCRIBER_DATA_rsp MAP_CLOSE_req]; JoinX1 --> MAP_DEL_RSP; MAP_DEL_RSP --> JoinX3((X)); +``` + +Flowchart for Process Delete\_Subscriber\_Data\_GLR. The process starts with NULL, receives an Open Indication, and checks if the subscriber is known. If not known, it sets the UE as an unidentified subscriber. If known, it checks if services are registered in a GLR. If not registered, it sets the subscriber as not confirmed by the HLR. If registered, it proceeds to delete subscriber data in the GLR, which then leads to Figure 20.2.2.2/5. Both successful and error paths from the deletion step lead to sending a response and close request to the HLR. + +Figure 20.2.2.2/3: Process Delete\_Subscriber\_Data\_GLR + +![Flowchart for Process Delete_GPRS_Subscriber_Data_GLR. The process starts with NULL, receives an Open Indication, and checks if the subscriber is known. If not known, it sets the UE as an unidentified subscriber. If known, it checks if services are registered in a GLR. If not registered, it sets the subscriber as not confirmed by the HLR. If registered, it deletes GPRS subscriber data and then deletes subscriber data in the GLR. Both deletion steps have OK and Error paths. The process ends with a response message (MAP_DELETE_SUBSCRIBER_DATA_rsp / MAP_CLOSE_req) or NULL.](694df81535f89c7bfb9ef0df6f130dc0_img.jpg) + +### Process Delete\_GPRS\_Subscriber\_Data\_GLR + +20.2.2.2.4(1) + +Figure 20.2.2.2/4: The delete subscriber data process in the GLR + +Arrows to left are to SGSN +Arrows to right are to HLR + +``` +graph TD; NULL1(NULL) --> RecOpenInd[Receive Open Ind]; RecOpenInd -- OK --> WaitForInd[Wait_For indication]; RecOpenInd -- "'Vr' 'Error'" --> NULL2(NULL); WaitForInd --> MAPDeleteInd[MAP_DELETE_SUBSCRIBER_DATA ind]; MAPDeleteInd --> CheckInd[Check Indication]; CheckInd --> SubKnow{Subscriber Know}; SubKnow -- No --> SetUE[Set UE= Unidentified Subscriber]; SubKnow -- Yes --> ServicesReg{Services registered in a GLR}; SubKnow -- Error --> SetNotConfirmed[Set Not Confirmed by HLR]; SetUE --> Join1(( )); SetNotConfirmed --> Join1; ServicesReg -- No --> Join1; ServicesReg -- Yes --> DeleteGPRS[Delete GPRS Subs Data_GLR]; DeleteGPRS -- "Figure 20.2.2.2/6" --> Join1; DeleteGPRS -- OK --> DeleteGLR[Delete Subscriber Data in the GLR]; DeleteGPRS -- Error --> Join1; DeleteGLR --> Join1; Join1 --> MAPDeleteRsp[MAP_DELETE_SUBSCRIBER_DATA_rsp / MAP_CLOSE_req]; MAPDeleteRsp --> End1(( )); End1 --> NULL3(NULL); +``` + +Flowchart for Process Delete\_GPRS\_Subscriber\_Data\_GLR. The process starts with NULL, receives an Open Indication, and checks if the subscriber is known. If not known, it sets the UE as an unidentified subscriber. If known, it checks if services are registered in a GLR. If not registered, it sets the subscriber as not confirmed by the HLR. If registered, it deletes GPRS subscriber data and then deletes subscriber data in the GLR. Both deletion steps have OK and Error paths. The process ends with a response message (MAP\_DELETE\_SUBSCRIBER\_DATA\_rsp / MAP\_CLOSE\_req) or NULL. + +**Figure 20.2.2.2/4: Process Delete\_GPRS\_Subscriber\_Data\_GLR** + +![SDL Diagram for Macro Delete_Subs_Data_GLR. The flow starts with an entry point, sends MAP_OPEN_req, MAP_DELETE_SUBSCRIBER_DATA_req, and MAP_DELIMITER to the HLR. It then waits for a confirmation. Depending on the received signal (MAP_CLOSE_ind, MAP_NOTICE_ind, MAP_U_ABORT_ind, or MAP_DELETE_SUBSCRIBER_DATA_cnf), it follows different paths. A major decision branch checks for errors and MSC Area Restricted flags, leading to either an 'Error' state or an 'OK' state.](2a476a0b3dbc3429436246db4784ff9f_img.jpg) + +**Macrodefinition Delete\_Subs\_Data\_GLR** 20.2.2.2.5(1) + +Figure 20.2.2.2/5: The delete subscriber data macro in the GLR + +Arrows to left are to VLR + Arrows to right are to HLR + + + +``` + + graph TD + Start([ ]) --> Out1[/MAP_OPEN_req +MAP_DELETE_SUBSCRIBER_DATA_req +MAP_DELIMITER/] + Out1 --> In1[Receive +Open cnf] + In1 -- Ok --> Wait[Wait_For_ +Confirm] + Wait --> VrError{Vr,Error} + Wait --> MAP_CLOSE_ind[MAP_CLOSE_ind.] + Wait --> MAP_NOTICE_ind1[MAP_NOTICE_ind] + Wait --> MAP_U_ABORT_ind1[MAP_U_ABORT_ind +MAP_P_ABORT_ind] + Wait --> MAP_DELETE_SUBSCRIBER_DATA_cnf[MAP_DELETE_SUBSCRIBER_DATA_cnf] + Wait --> MAP_NOTICE_ind2[MAP_NOTICE_ind] + Wait --> MAP_U_ABORT_ind2[MAP_U_ABORT_ind +MAP_P_ABORT_ind +MAP_CLOSE_ind] + + MAP_CLOSE_ind --> MAP_CLOSE_Req[MAP_CLOSE_ +Req] + MAP_NOTICE_ind1 --> MAP_CLOSE_req_box[MAP_CLOSE_req] + MAP_CLOSE_req_box --> MAP_CLOSE_Req + MAP_U_ABORT_ind1 --> MAP_U_ABORT_ind_box[MAP_U_ABORT_ind.] + MAP_U_ABORT_ind_box --> MAP_CLOSE_Req + MAP_CLOSE_Req --> Error1((Error)) + + MAP_NOTICE_ind2 --> MAP_CLOSE_req_box2[MAP_CLOSE_ +req] + MAP_U_ABORT_ind2 --> MAP_U_ABORT_req_out[/MAP U ABORT req/] + MAP_U_ABORT_req_out --> Error2((Error)) + + MAP_DELETE_SUBSCRIBER_DATA_cnf --> Error_Dec{Error} + Error_Dec -- No --> MSC_Dec{ } + MSC_Dec -- Yes --> MSC_Text[MSC_Area_Restricted_received or +"Roaming_Restricted_Due_ +To_Unsupported_Feature"] + MSC_Dec -- No --> MSC_Flag_Dec{ } + MSC_Flag_Dec -- No --> MSC_Not_Restricted[MSC_Area_ +Restricted_Flag +=not Restricted] + MSC_Flag_Dec -- Yes --> MSC_Restricted[MSC_Area_ +Restricted_Flag +=Restricted] + + MSC_Not_Restricted --> MAP_DEL_CNF1[MAP_DELETE_ +SUBSCRIBER_ +DATA_Cnf] + MSC_Restricted --> MAP_DEL_CNF2[MAP_DELETE_ +SUBSCRIBER_ +DATA_Cnf] + + MAP_DEL_CNF1 --> Error3((Error)) + MAP_DEL_CNF2 --> OK((OK)) + +``` + +SDL Diagram for Macro Delete\_Subs\_Data\_GLR. The flow starts with an entry point, sends MAP\_OPEN\_req, MAP\_DELETE\_SUBSCRIBER\_DATA\_req, and MAP\_DELIMITER to the HLR. It then waits for a confirmation. Depending on the received signal (MAP\_CLOSE\_ind, MAP\_NOTICE\_ind, MAP\_U\_ABORT\_ind, or MAP\_DELETE\_SUBSCRIBER\_DATA\_cnf), it follows different paths. A major decision branch checks for errors and MSC Area Restricted flags, leading to either an 'Error' state or an 'OK' state. + +**Figure 20.2.2.2/5: Macro Delete\_Subs\_Data\_GLR** + +![Flowchart for Macrodefinition Delete_GPRS_Subs_Data_GLR. The process starts with an entry point, followed by sending MAP_OPEN_req, MAP_DELETE_SUBSCRIBER_DATA_req, and MAP_DELIMITER to the HLR. It receives an 'Open Cnf' and checks for 'Ok'. If 'Ok', it enters a 'Wait_For_Confirm' state. From there, it handles various indications: MAP_CLOSE_ind., MAP_NOTICE_ind, MAP_U_ABORT_ind, MAP_P_ABORT_ind, MAP_DELETE_SUBSCRIBER_DATA_Cnf, and MAP_U_ABORT_ind. The flowchart includes decision diamonds for 'Error' and 'SGSN_Area_Restricted_received or Roaming_Restricted_Due_To_Unsupported_Feature'. Depending on these decisions, it sends MAP_CLOSE_req, MAP_U_ABORT_req, or MAP_DELETE_SUBSCRIBER_DATA_Cnf to the HLR, leading to 'Error', 'OK', or 'Vr,Error' outcomes.](0931f3e098bd4539041de11c50cec2d2_img.jpg) + +**Macrodefinition Delete\_GPRS\_Subs\_Data\_GLR** 20.2.2.2.6(1) + +Figure 20.2.2.2/6: The delete subscriber data macro in the GLR + +Arrows to left are to SGSN +Arrows to right are to HLR + +``` + +graph TD + Start([ ]) --> OpenReq["MAP_OPEN_req +MAP_DELETE_SUBSCRIBER_DATA_req +MAP_DELIMITER"] + OpenReq --> OpenCnf["Receive Open Cnf"] + OpenCnf -- Ok --> WaitConfirm([Wait_For_Confirm]) + WaitConfirm --> Indications["MAP_CLOSE_ind. | MAP_NOTICE_ind | MAP_U_ABORT_ind +MAP_P_ABORT_ind | MAP_DELETE_SUBSCRIBER_DATA_Cnf | MAP_NOTICE_ind | MAP_U_ABORT_ind +MAP_P_ABORT_ind | MAP_CLOSE_ind"] + Indications --> Error1{Error} + Error1 -- No --> Restricted{SGSN_Area_Restricted_received or +"Roaming_Restricted_Due_To_Unsupported_Feature"} + Restricted -- Yes --> DeleteCnf1["MAP_DELETE_SUBSCRIBER_DATA_Cnf"] + Restricted -- No --> NotRestricted{SGSN_Area_Restricted_Flag +=not Restricted} + NotRestricted -- Yes --> DeleteCnf2["MAP_DELETE_SUBSCRIBER_DATA_Cnf"] + NotRestricted -- No --> DeleteCnf2 + DeleteCnf1 --> Error2((Error)) + DeleteCnf2 --> OK((OK)) + Error1 -- Yes --> CloseReq["MAP_CLOSE_req"] + CloseReq --> CloseReq2["MAP_CLOSE Req"] + CloseReq2 --> Error3((Error)) + MAP_NOTICE_ind --> CloseReq3["MAP_CLOSE_req"] + CloseReq3 --> HLR[HLR] + MAP_U_ABORT_ind --> UAbortReq["MAP U ABORT req"] + UAbortReq --> Error4((Error)) + MAP_P_ABORT_ind --> Error5((Error)) + MAP_CLOSE_ind. --> Error6((Error)) + MAP_DELETE_SUBSCRIBER_DATA_Cnf --> VrError["Vr,Error"] + +``` + +Flowchart for Macrodefinition Delete\_GPRS\_Subs\_Data\_GLR. The process starts with an entry point, followed by sending MAP\_OPEN\_req, MAP\_DELETE\_SUBSCRIBER\_DATA\_req, and MAP\_DELIMITER to the HLR. It receives an 'Open Cnf' and checks for 'Ok'. If 'Ok', it enters a 'Wait\_For\_Confirm' state. From there, it handles various indications: MAP\_CLOSE\_ind., MAP\_NOTICE\_ind, MAP\_U\_ABORT\_ind, MAP\_P\_ABORT\_ind, MAP\_DELETE\_SUBSCRIBER\_DATA\_Cnf, and MAP\_U\_ABORT\_ind. The flowchart includes decision diamonds for 'Error' and 'SGSN\_Area\_Restricted\_received or Roaming\_Restricted\_Due\_To\_Unsupported\_Feature'. Depending on these decisions, it sends MAP\_CLOSE\_req, MAP\_U\_ABORT\_req, or MAP\_DELETE\_SUBSCRIBER\_DATA\_Cnf to the HLR, leading to 'Error', 'OK', or 'Vr,Error' outcomes. + +Figure 20.2.2.2/6: Macro Delete\_GPRS\_Subs\_Data\_GLR + +## 20.3 Subscriber Identity procedure + +In the subscriber identity procedure the IMSI of the subscriber is retrieved from the HLR. The procedure is shown in figure 20.3/1. + +![Sequence diagram showing the subscriber identity procedure between OMC, VLR, GLR, and HLR. The sequence is: 1) Identity request from OMC to VLR; 2) MAP_SEND_IMSI from VLR to HLR; 3) MAP_SEND_IMSI_ACK from HLR to GLR; 4) Identity confirm from GLR to OMC.](ffb6acd27b8e3a54392840948a75869f_img.jpg) + +``` +sequenceDiagram + participant OMC + participant VLR + participant GLR + participant HLR + Note left of OMC: 1) Identity request. + OMC->>VLR: 1. + Note right of VLR: 2) MAP_SEND_IMSI. + VLR->>HLR: 2. + Note right of HLR: 3) MAP_SEND_IMSI_ACK. + HLR->>GLR: 3. + Note left of GLR: 4) Identity confirm. + GLR->>OMC: 4. +``` + +Sequence diagram showing the subscriber identity procedure between OMC, VLR, GLR, and HLR. The sequence is: 1) Identity request from OMC to VLR; 2) MAP\_SEND\_IMSI from VLR to HLR; 3) MAP\_SEND\_IMSI\_ACK from HLR to GLR; 4) Identity confirm from GLR to OMC. + +- 1) Identity request. +- 2) MAP\_SEND\_IMSI. +- 3) MAP\_SEND\_IMSI\_ACK. +- 4) Identity confirm. + +**Figure 20.3/1: The subscriber identity procedure** + +### 20.3.1 Subscriber identity procedure in the GLR + +The subscriber identity procedure in the GLR is shown in figure 20.3/2. + +![Flowchart of the Send_IMSI_GLR process. It starts at 'Idle', receives an 'Open_ind', waits for a response, checks indications (MAP_NOTICE_ind, MAP_SEND_IMSI_ind), evaluates if the subscriber is known, and then either sends requests to the HLR or handles an unknown subscriber. It ends at 'Idle' through various paths.](719ef0f734259484038b2434e5dc3f24_img.jpg) + +### Process Send\_IMSI\_GLR + +20.3.2\_1(2) + +Figure 20.3/2: The send IMSI process in the GLR + +Arrows to left are to VLR +Arrows to right are to HLR + +``` +graph TD; Idle1([Idle]) --> RecOpen[Receive Open_ind]; RecOpen --> WaitFor[Wait For Response]; WaitFor --> MAP_NOTICE{MAP_NOTICE_ind}; WaitFor --> MAP_SEND{MAP_SEND_IMSI_ind}; MAP_NOTICE --> MAP_CLOSE_req{MAP_CLOSE_req}; MAP_CLOSE_req --> Idle2([Idle]); MAP_SEND --> CheckInd[Check Indication]; CheckInd --> SubKnown{OK Subscriber Known}; SubKnown -- Yes --> HLR_Req[MAP_OPEN_req, MAP_SEND_IMSI_req, MAP_SWLIMITER_req]; SubKnown -- No --> SetUnknown[Set UE= Unknown Subscriber]; SetUnknown --> HLR_Rsp[MAP_SEND_IMSI_rsp, MAP_CLOSE_req]; HLR_Req --> RecOpenCnf[Receive Open_Cnf]; RecOpenCnf -- Ok --> WF_ID[WF_IDENTITY_RESULT]; RecOpenCnf -- "Vr, Error" --> MAP_U_ABORT{MAP_U_ABORT_req}; MAP_U_ABORT --> Idle3([Idle]); HLR_Rsp --> Idle4([Idle]); WaitFor -- Vr --> PerformVr[Perform Vr Dialogue]; PerformVr --> Idle5([Idle]); WaitFor -- Error --> Idle6([Idle]); SubKnown -- Error --> Idle7([Idle]); +``` + +Flowchart of the Send\_IMSI\_GLR process. It starts at 'Idle', receives an 'Open\_ind', waits for a response, checks indications (MAP\_NOTICE\_ind, MAP\_SEND\_IMSI\_ind), evaluates if the subscriber is known, and then either sends requests to the HLR or handles an unknown subscriber. It ends at 'Idle' through various paths. + +Figure 20.3/2 (Sheet 1 of 2): Process Send\_IMSI\_GLR + +#### Process Send\_IMSI\_GLR + +20.3.2\_2(2) + +Figure 20.3/2: The send IMSI process in the GLR + +Arrows to left are to VLR +Arrows to right are to HLR + +![Flowchart of Process Send_IMSI_GLR showing interactions between VLR and HLR.](18dbea0ac6b7ad13e47afda3ddd53b64_img.jpg) + +The flowchart illustrates the 'Process Send\_IMSI\_GLR' within the GLR. It begins with an entry point labeled 'WF\_IDENTITY\_RESULT'. The process then enters a loop: it sends a 'MAP\_SEND\_IMSI\_cnf' message to the HLR (indicated by an arrow pointing right). The HLR responds with 'MAP\_NOTICE\_ind' (arrow pointing left). The GLR then sends a 'MAP\_CLOSE\_req' to the HLR (arrow pointing right). The HLR responds with 'MAP\_CLOSE\_ind', 'MAP\_U\_ABORT\_ind', and 'MAP\_P\_ABORT\_ind' (arrow pointing left). The GLR receives 'MAP\_U\_ABORT\_req' from the HLR (arrow pointing left) and transitions to an 'Idle' state (oval). Alternatively, the 'MAP\_SEND\_IMSI\_cnf' message is processed through a 'Check Confirmation' block. This block has two outcomes: 'OK', which leads to a merge point, and 'Error', which leads to a 'Set error' block and then to the same merge point. From this merge point, the GLR sends 'MAP\_SEND\_IMSI\_rsp' and 'MAP\_CLOSE\_req' to the HLR (arrow pointing right) and then transitions to an 'Idle' state (oval). A legend indicates that arrows pointing left are to the VLR and arrows pointing right are to the HLR. + +Flowchart of Process Send\_IMSI\_GLR showing interactions between VLR and HLR. + +Figure 20.3/2 (Sheet 2 of 2): Process Send\_IMSI\_GLR + +# --- 21 Call handling procedures + +## 21.1 General + +The MAP call handling procedures are used: + +1. to retrieve routing information to handle a mobile terminating call; +2. to transfer control of a call back to the GMSC if the call is to be forwarded; +3. to retrieve and transfer information between anchor MSC and relay MSC for inter MSC group calls / broadcast calls; +4. to allocate resources in an SIWFS; +5. to handle the reporting of MS status for call completion services; +6. to handle the notification of remote user free for CCBS. + +Items 1, 5 and 6 are only procedures that have impact to the GLR. The following subclause describes the function of the GLR related to these procedures. + +## 21.2 Retrieval of routing information + +### 21.2.1 General + +The message flows for successful retrieval of routing information for a mobile terminating call are shown in figure 21.2.1/1 (mobile terminating call which has not been optimally routed) and 21.2.1/2 (mobile-to-mobile call which has been optimally routed). + +![Sequence diagram showing message flow for retrieval of routing information (non-optimally routed call).](4847c98185bc52e8786b78738bc52b45_img.jpg) + +``` + +sequenceDiagram + participant Network + participant Gateway as Gateway + participant HLR + participant GLR + participant VLR + + Note left of Network: I_IAM (note2) + Network->>Gateway: I_IAM (note2) + Gateway->>HLR: MAP_SEND_ROUTING_INFO + Note right of HLR: (note 1) + HLR->>GLR: MAP_PROVIDE_SUBSCRIBER_INFO + GLR->>VLR: MAP_PROVIDE_SUBSCRIBER_INFO + VLR->>GLR: MAP_PROVIDE_SUBSCRIBER_INFO ack + GLR->>HLR: MAP_PROVIDE_SUBSCRIBER_INFO ack + HLR->>Gateway: MAP_SEND_ROUTING_INFO ack + Gateway->>HLR: MAP_SEND_ROUTING_INFO + HLR->>GLR: MAP_PROVIDE_ROAMING_NUMBER + GLR->>VLR: MAP_PROVIDE_ROAMING_NUMBER + VLR->>GLR: MAP_PROVIDE_ROAMING_NUMBER ack + GLR->>HLR: MAP_PROVIDE_ROAMING_NUMBER ack + HLR->>Gateway: MAP_SEND_ROUTING_INFO ack + Gateway->>Network: I_IAM + +``` + +The diagram illustrates the message flow for a non-optimally routed mobile terminating call. It involves five lifelines: Network, Gateway (MSC), HLR, GLR, and VLR. The process starts with the Network sending an I\_IAM message to the Gateway. The Gateway then sends a MAP\_SEND\_ROUTING\_INFO message to the HLR. The HLR sends a MAP\_PROVIDE\_SUBSCRIBER\_INFO message to the GLR, which in turn sends it to the VLR. The VLR returns a MAP\_PROVIDE\_SUBSCRIBER\_INFO ack to the GLR, which returns it to the HLR. The HLR then sends a MAP\_SEND\_ROUTING\_INFO ack to the Gateway. The Gateway sends another MAP\_SEND\_ROUTING\_INFO message to the HLR. The HLR sends a MAP\_PROVIDE\_ROAMING\_NUMBER message to the GLR, which sends it to the VLR. The VLR returns a MAP\_PROVIDE\_ROAMING\_NUMBER ack to the GLR, which returns it to the HLR. The HLR then sends a MAP\_SEND\_ROUTING\_INFO ack to the Gateway. Finally, the Gateway sends an I\_IAM message to the Network. There are two notes: Note 1 indicates that the MAP\_PROVIDE\_SUBSCRIBER\_INFO message is optional, and Note 2 indicates that the I\_IAM message may be replaced by TUP or ISUP depending on the network type. + +Sequence diagram showing message flow for retrieval of routing information (non-optimally routed call). + +Notes: + +xxx = *Optional Procedure* + +NOTE 1: This service may also be used by an ISDN exchange for obtaining routing information from the HLR. + +NOTE 2: TUP or ISUP may be used in signalling between MSCs, depending on the network type between the MSCs. For further details on the TUP and ISUP procedures refer to the following ITU-T Recommendations and ETSI specification: + Q.721-725 - Telephone User Part (TUP); + ETS 300 356-1 - Integrated Services Digital Network (ISDN); Signalling System No.7; ISDN User Part (ISUP) version 2 for the international interface; Part 1: Basic services. + +NOTE 3: As a network operator option, the HLR sends MAP\_PROVIDE\_SUBSCRIBER\_INFORMATION to the VLR. For further details on the CAMEL procedures refer to GSM 3GPP TS 03.78. + +**Figure 21.2.1/1: Message flow for retrieval of routing information (non-optimally routed call)** + +![Sequence diagram showing message flow for retrieval of routing information (optimally routed call). Lifelines: Network, Gateway (MSC), HLR, GLR, VLR. The process involves MAP_SEND_ROUTING_INFO from Gateway to HLR, followed by MAP_PROVIDE_SUBSCRIBER_INFO from HLR to GLR and VLR. The GLR and VLR return acknowledgments. An 'OR' condition exists between the subscriber info and roaming number flows. Finally, the Gateway sends I_IAM to the Network.](e7010c66da16316c2935dfbbef5056b3_img.jpg) + +``` + +sequenceDiagram + participant Network + participant Gateway as Gateway (MSC) + participant HLR + participant GLR + participant VLR + + Note left of Network: I_IAM (note) + Gateway->>HLR: MAP_SEND_ROUTING_INFO + HLR->>GLR: MAP_PROVIDE_SUBSCRIBER_INFO + HLR->>VLR: MAP_PROVIDE_SUBSCRIBER_INFO + GLR->>HLR: MAP_PROVIDE_SUBSCRIBER_INFO ack + VLR->>HLR: MAP_PROVIDE_SUBSCRIBER_INFO ack + Note right of GLR: OR + HLR->>GLR: MAP_PROVIDE_ROAMING_NUMBER + HLR->>VLR: MAP_PROVIDE_ROAMING_NUMBER + GLR->>HLR: MAP_PROVIDE_ROAMING_NUMBER ack + VLR->>HLR: MAP_PROVIDE_ROAMING_NUMBER ack + HLR->>Gateway: MAP_SEND_ROUTING_INFO ack + Gateway->>Network: I_IAM + +``` + +Sequence diagram showing message flow for retrieval of routing information (optimally routed call). Lifelines: Network, Gateway (MSC), HLR, GLR, VLR. The process involves MAP\_SEND\_ROUTING\_INFO from Gateway to HLR, followed by MAP\_PROVIDE\_SUBSCRIBER\_INFO from HLR to GLR and VLR. The GLR and VLR return acknowledgments. An 'OR' condition exists between the subscriber info and roaming number flows. Finally, the Gateway sends I\_IAM to the Network. + +**Figure 21.2.1/2: Message flow for retrieval of routing information (optimally routed call)** + +#### **Notes:** + +xxx = *Optional Procedure.* + +For Optimal Routing phase 1, only one of the information flows for Provide Subscriber Info and Provide Roaming Number is used. For later phases of Optimal Routing, the HLR may return a MAP\_SEND\_ROUTING\_INFORMATION ack after the Provide Subscriber Info information flow, and the GMSC may send a second MAP\_SEND\_ROUTING\_INFORMATION, which will trigger the Provide Roaming Number information flow. + +TUP or ISUP may be used in signalling between MSCs, depending on the network type between the MSCs. For further details on the TUP and ISUP procedures refer to the following CCITT. + +Recommendations & ETSI specification: + +Q.721-725 - Telephone User Part (TUP); + +ETS 300 356-1 - Integrated Services Digital Network (ISDN); Signalling System No.7; ISDN User Part (ISUP) version 2 for the international interface; Part 1: Basic services. + +### 21.2.2 Process in the GLR to provide a roaming number + +The MAP process in the GLR to provide a roaming number for a mobile terminating call is shown in figure 21.2.2/1 (Process PRN\_Receive\_GLR) and figure 21.2.2/2 (Process PRN\_Send\_GLR). The MAP process invokes a macro not defined in this subclause; the definition of this macro can be found as follows: + +- Receive\_Open\_Ind            see subclause 25.1. +- Receive\_Open\_Cnf          see subclause 25.1. +- Check\_Confirmation       see subclause 25.2. + +![Flowchart for Process PRN_Receive_GLR. It starts at 'Idle', receives an 'Open Ind', then branches based on 'OK', 'Error', or 'Vr'. The 'OK' path leads to 'Wait For Service Indication', then 'MAP_PROVIDE_ROAMING_NUMBER_ind.', 'Provide Roaming Number To GLR Call process', 'Wait For Response', and finally 'MAP_PROVIDE_ROAMING_NUMBER_rsp.' back to 'Idle'. The 'Error' path leads to 'Idle'. The 'Vr' path leads to 'Perform MAP Vr Dialogue' then 'Idle'. Other branches include 'MAP_P_ABORT_ind.', 'MAP_NOTICE_ind.', 'MAP_CLOSE_req.', 'Provide Roaming Number ack', 'Provide Roaming Number negative response', 'Abort', 'Set result', 'Set error', and 'MAP_U_ABORT_req.'.](dbd4bab54b57e8d1abf80e3de6471130_img.jpg) + +### Process PRN\_Receive\_GLR + +21.2.2.1(1) + +Figure 21.2.2/1: Process in the GLR to respond to a request routing information + +Signals to/from the left are to/from the HLR; signals to/from the right are to/from the GLR Call process + +``` +graph TD; Idle1([Idle]) --> OpenInd[Receive Open Ind]; OpenInd -- Vr --> PerformMAP[Perform MAP Vr Dialogue]; OpenInd -- OK --> WaitService[Wait For Service Indication]; OpenInd -- Error --> Idle2([Idle]); PerformMAP --> Idle3([Idle]); WaitService --> MAP_P_ABORT_ind{MAP_P_ABORT_ind}; WaitService --> MAP_PROVIDE_ROAMING_NUMBER_ind[MAP_PROVIDE_ROAMING_NUMBER_ind.]; WaitService --> MAP_NOTICE_ind{MAP_NOTICE_ind}; MAP_P_ABORT_ind --> Idle4([Idle]); MAP_PROVIDE_ROAMING_NUMBER_ind --> ProvideRoamingNumber[Provide Roaming Number To GLR Call process]; ProvideRoamingNumber --> WaitResponse[Wait For Response]; MAP_NOTICE_ind --> MAP_CLOSE_req{MAP_CLOSE_req}; MAP_CLOSE_req --> Idle5([Idle]); WaitResponse --> ProvideRoamingNumberAck[Provide Roaming Number ack]; WaitResponse --> ProvideRoamingNumberNegativeResponse[Provide Roaming Number negative response]; WaitResponse --> Abort[Abort]; ProvideRoamingNumberAck --> SetResult[Set result]; ProvideRoamingNumberNegativeResponse --> SetError[Set error]; Abort --> MAP_U_ABORT_req[MAP_U_ABORT_req]; SetResult --> MAP_PROVIDE_ROAMING_NUMBER_rsp[MAP_PROVIDE_ROAMING_NUMBER_rsp.]; SetError --> MAP_PROVIDE_ROAMING_NUMBER_rsp; MAP_PROVIDE_ROAMING_NUMBER_rsp --> Idle6([Idle]); +``` + +Flowchart for Process PRN\_Receive\_GLR. It starts at 'Idle', receives an 'Open Ind', then branches based on 'OK', 'Error', or 'Vr'. The 'OK' path leads to 'Wait For Service Indication', then 'MAP\_PROVIDE\_ROAMING\_NUMBER\_ind.', 'Provide Roaming Number To GLR Call process', 'Wait For Response', and finally 'MAP\_PROVIDE\_ROAMING\_NUMBER\_rsp.' back to 'Idle'. The 'Error' path leads to 'Idle'. The 'Vr' path leads to 'Perform MAP Vr Dialogue' then 'Idle'. Other branches include 'MAP\_P\_ABORT\_ind.', 'MAP\_NOTICE\_ind.', 'MAP\_CLOSE\_req.', 'Provide Roaming Number ack', 'Provide Roaming Number negative response', 'Abort', 'Set result', 'Set error', and 'MAP\_U\_ABORT\_req.'. + +Figure 21.2.2/1: Process PRN\_Receive\_GLR + +![State transition diagram for Process PRN_Send_GLR. The process starts at 'Idle', transitions to 'Provide Roaming Number', then to a state where it sends MAP_Open_req, MAP_PROVIDE_ROAMING_NUMBER_req, and MAP_DELIMITER_req. It then receives an 'Open cnf' and enters 'Wait For Response'. From there, it can receive 'MAP_PROVIDE_ROAMING_NUMBER_cnf' (OK), 'MAP_U_ABORT_ind'/'MAP_P_ABORT_ind' (Vr), or 'MAP_NOTICE_ind' (Error). The first leads to 'Check Confirmation' and then either 'Provide Roaming Number ack' (OK) or 'Provide Roaming Number negative response' (Error). The second and third lead to 'Abort'.](4806f9f95fff13a30d6523bd6ffeac63_img.jpg) + +### Process PRN\_Send\_GLR 21.2.2.2(1) + +Figure 21.2.2/2: Process in the GLR to respond to a request routing information + +Signals to/from the left are to/from the GLR Call; process signals to/from the right are to/from the VLR + +``` +stateDiagram-v2 + [*] --> Idle + Idle --> ProvideRoamingNumber: Provide Roaming Number + state " " as Outgoing + ProvideRoamingNumber --> Outgoing + Outgoing --> ReceiveOpenCnf: MAP_Open_req, MAP_PROVIDE_ROAMING_NUMBER_req, MAP_DELIMITER_req + ReceiveOpenCnf --> WaitForResponse: Open cnf + state "Wait For Response" as WaitForResponse + WaitForResponse --> OK + WaitForResponse --> Vr + WaitForResponse --> Error + OK --> CheckConfirmation: MAP_PROVIDE_ROAMING_NUMBER_cnf + CheckConfirmation --> ProvideRoamingNumberAck: OK + CheckConfirmation --> ProvideRoamingNumberNegResponse: Error + Vr --> PerformMAPVr: MAP_U_ABORT_ind, MAP_P_ABORT_ind + PerformMAPVr --> [*] + Error --> ProvideRoamingNumberNegResponse2: MAP_NOTICE_ind + ProvideRoamingNumberNegResponse2 --> MAP_CLOSE_req: MAP_CLOSE_req + MAP_CLOSE_req --> Abort2: Abort + Abort2 --> [*] +``` + +State transition diagram for Process PRN\_Send\_GLR. The process starts at 'Idle', transitions to 'Provide Roaming Number', then to a state where it sends MAP\_Open\_req, MAP\_PROVIDE\_ROAMING\_NUMBER\_req, and MAP\_DELIMITER\_req. It then receives an 'Open cnf' and enters 'Wait For Response'. From there, it can receive 'MAP\_PROVIDE\_ROAMING\_NUMBER\_cnf' (OK), 'MAP\_U\_ABORT\_ind'/'MAP\_P\_ABORT\_ind' (Vr), or 'MAP\_NOTICE\_ind' (Error). The first leads to 'Check Confirmation' and then either 'Provide Roaming Number ack' (OK) or 'Provide Roaming Number negative response' (Error). The second and third lead to 'Abort'. + +Figure 21.2.2/2: Process PRN\_Send\_GLR + +### 21.2.3 Process in the GLR to provide subscriber information + +The MAP process in the GLR to provide subscriber information for a mobile terminating call is shown in figure 21.2.3/1 (Process PSI Receive\_GLR) and figure 21.2.3/2 (Process PSI Send\_GLR). The MAP process invokes a macro not defined in this subclause; the definition of this macro can be found as follows: + +| | | +|--------------------|---------------------| +| Receive_Open_Ind | see subclause 25.1. | +| Receive_Open_Cnf | see subclause 25.1. | +| Check_Confirmation | see subclause 25.2. | + +![Flowchart for Process PSI_Receive_GLR. The process starts at an Idle state, receives an Open Indication, and then branches based on the response: OK, Error, or Vr. The OK path leads to waiting for a service indication, then handling MAP_P_ABORT_ind, MAP_PROVIDE_SUBSCRIBER_INFO_ind, or MAP_NOTICE_ind. The MAP_PROVIDE_SUBSCRIBER_INFO_ind path leads to providing subscriber info and waiting for a response, which results in either a successful response (MAP_PROVIDE_SUBSCRIBER_INFO_rsp) or an abort (MAP_U_ABORT_req). The Error path leads to an Idle state. The Vr path leads to performing a MAP Vr Dialogue and returning to Idle.](9c45844d796e85ae05505870a54e4eb4_img.jpg) + +### Process PSI\_Receive\_GLR + +21.2.3.1(1) + +Figure 21.2.3/1: Process in the GLR to respond to a request routing information + +Signals to/from the left are to/from the HLR; signals to/from the right are to/from the GLR Call process + +``` +graph TD; Start([Idle]) --> OpenInd[Receive Open Ind]; OpenInd -- Vr --> MAPVr[Perform MAP Vr Dialogue]; OpenInd -- OK --> WaitService[Wait For Service Indication]; OpenInd -- Error --> Idle1([Idle]); MAPVr --> Idle2([Idle]); WaitService --> P_ABORT_ind{MAP_P_ABORT_ind}; WaitService --> PROVIDE_INFO_ind{MAP_PROVIDE_SUBSCRIBER_INFO_ind}; WaitService --> NOTICE_ind{MAP_NOTICE_ind}; P_ABORT_ind --> Idle3([Idle]); PROVIDE_INFO_ind --> ProvideInfo[Provide Subscriber Info To GLR Call process]; ProvideInfo --> WaitResponse[Wait For Response]; WaitResponse --> Ack{Provide Subscriber Info ack}; WaitResponse --> NegativeResponse{Provide Subscriber Info negative response}; WaitResponse --> Abort{Abort}; Ack --> SetResult[Set result]; NegativeResponse --> SetError[Set error]; Abort --> U_ABORT_req{MAP_U_ABORT_req}; SetResult --> PROVIDE_INFO_rsp{MAP_PROVIDE_SUBSCRIBER_INFO_rsp}; SetError --> PROVIDE_INFO_rsp; PROVIDE_INFO_rsp --> Idle4([Idle]); U_ABORT_req --> Idle5([Idle]); +``` + +Flowchart for Process PSI\_Receive\_GLR. The process starts at an Idle state, receives an Open Indication, and then branches based on the response: OK, Error, or Vr. The OK path leads to waiting for a service indication, then handling MAP\_P\_ABORT\_ind, MAP\_PROVIDE\_SUBSCRIBER\_INFO\_ind, or MAP\_NOTICE\_ind. The MAP\_PROVIDE\_SUBSCRIBER\_INFO\_ind path leads to providing subscriber info and waiting for a response, which results in either a successful response (MAP\_PROVIDE\_SUBSCRIBER\_INFO\_rsp) or an abort (MAP\_U\_ABORT\_req). The Error path leads to an Idle state. The Vr path leads to performing a MAP Vr Dialogue and returning to Idle. + +Figure 21.2.3/1 : Process PSI\_Receive\_GLR + +![State transition diagram for Process PSI_Send_GLR. The process starts at an initial state, goes to Idle, then Provide Subscriber Info. It sends MAP_Open_req, MAP_PROVIDE_SUBSCRIBER_INFO_req, and MAP_DELIMITER_req. It then receives an Open cnf. From there, it branches based on the response: OK leads to Wait For Response; Vr leads to Perform MAP Vr (which leads to an error state); Error leads to Provide Subscriber Info negative response (which also leads to an error state). From Wait For Response, it branches into three possible indications: MAP_PROVIDE_SUBSCRIBER_INFO_cnf, MAP_U_ABORT_ind/MAP_P_ABORT_ind, or MAP_NOTICE_ind. The first leads to Check Confirmation, which then branches into Provide Subscriber Info ack (OK) or Provide Subscriber Info negative response (Error), both leading to error states. The second and third lead directly to Abort, which also leads to an error state.](49fe8fe978c0f7e73112d231feb377eb_img.jpg) + +**Process PSI\_Send\_GLR** 21.2.3.2(1) + +Figure 21.2.3/2: Process in the GLR to respond to a request routing information + +Signals to/from the left are to/from the GLR Call; process signals to/from the right are to/from the VLR + +``` + +stateDiagram-v2 + [*] --> Idle + Idle --> ProvideSubscriberInfo: Provide Subscriber Info + ProvideSubscriberInfo --> Out: MAP_Open_req, MAP_PROVIDE_SUBSCRIBER_INFO_req, MAP_DELIMITER_req + Out --> ReceiveOpenCnf: Receive Open cnf + ReceiveOpenCnf --> WaitForResponse: OK + ReceiveOpenCnf --> PerformMAPVr: Vr + ReceiveOpenCnf --> ProvideSubscriberInfoNegativeResponse: Error + PerformMAPVr --> [*]: + ProvideSubscriberInfoNegativeResponse --> [*]: + WaitForResponse --> In: MAP_PROVIDE_SUBSCRIBER_INFO_cnf + WaitForResponse --> Abort1: MAP_U_ABORT_ind, MAP_P_ABORT_ind + WaitForResponse --> In2: MAP_NOTICE_ind + In --> CheckConfirmation: Check Confirmation + CheckConfirmation --> ProvideSubscriberInfoAck: OK + CheckConfirmation --> ProvideSubscriberInfoNegativeResponse2: Error + ProvideSubscriberInfoAck --> [*]: + ProvideSubscriberInfoNegativeResponse2 --> [*]: + Abort1 --> [*]: + In2 --> MAP_CLOSE_req: MAP_CLOSE_req + MAP_CLOSE_req --> Abort2: Abort + Abort2 --> [*]: + +``` + +State transition diagram for Process PSI\_Send\_GLR. The process starts at an initial state, goes to Idle, then Provide Subscriber Info. It sends MAP\_Open\_req, MAP\_PROVIDE\_SUBSCRIBER\_INFO\_req, and MAP\_DELIMITER\_req. It then receives an Open cnf. From there, it branches based on the response: OK leads to Wait For Response; Vr leads to Perform MAP Vr (which leads to an error state); Error leads to Provide Subscriber Info negative response (which also leads to an error state). From Wait For Response, it branches into three possible indications: MAP\_PROVIDE\_SUBSCRIBER\_INFO\_cnf, MAP\_U\_ABORT\_ind/MAP\_P\_ABORT\_ind, or MAP\_NOTICE\_ind. The first leads to Check Confirmation, which then branches into Provide Subscriber Info ack (OK) or Provide Subscriber Info negative response (Error), both leading to error states. The second and third lead directly to Abort, which also leads to an error state. + +Figure 21.2.3/2 : Process PSI\_Send\_GLR + +## 21.3 Setting of Reporting State + +### 21.3.1 General + +In case the HLR received the CCBS request message from the other HLR for CCSB monitoring, the message flow for setting the reporting state is shown in figure 21.3.1/1. The message flow shown in figure 21.3.1/1 shall also be applied in case for stop monitoring. The stage2 specification for the interaction with CCBS in a GLR is in 3GPP TS 23.119. + +![Sequence diagram showing the message flow for setting the reporting state between VLR, GLR, and HLR.](5cf80bac69830ea773ac17c87e0ae24d_img.jpg) + +``` +sequenceDiagram + participant VLR + participant GLR + participant HLR + Note right of VLR: MAP_SET_REPORTING_STATE + VLR->>GLR: MAP_SET_REPORTING_STATE + Note right of GLR: MAP_SET_REPORTING_STATE + GLR->>HLR: MAP_SET_REPORTING_STATE + Note right of HLR: MAP_SET_REPORTING_STATE ack + HLR-->>GLR: MAP_SET_REPORTING_STATE ack + Note right of GLR: MAP_SET_REPORTING_STATE ack + GLR-->>VLR: MAP_SET_REPORTING_STATE ack +``` + +Sequence diagram showing the message flow for setting the reporting state between VLR, GLR, and HLR. + +Figure 21.3.1/1: Message Flow for Setting the Reporting State + +### 21.3.2 Process in the GLR to set the reporting state + +The MAP process in the GLR to set the reporting state is shown in figures 21.3.2/1 and 21.3.2/2. The MAP process invokes a macro not defined in this subclause; the definition of this macro can be found as follows: + +| | | +|--------------------|---------------------| +| Receive_Open_Ind | see subclause 25.1. | +| Receive_Open_Cnf | see subclause 25.1. | +| Check_Confirmation | see subclause 25.2. | + +#### Set the reporting state + +When receiving the MAP\_SET\_REPORTING\_STATE indication, the MAP user in the GLR transfers the information to the VLR in the MAP\_SET\_REPORTING\_STATE request. + +The GLR then awaits the receipt of the MAP\_SET\_REPORTING\_STATE confirm from the VLR. The MAP user in the GLR shall transfer the information contained in this primitive to the HLR in the MAP\_SET\_REPORTING\_STATE response without checking its contents. + +![State transition diagram for Process Reporting_State_Receive_GLR. The process starts at Idle, receives an Open Indication, and then branches based on the response: OK leads to Wait For Service Indication, which then leads to MAP_SET_REPORTING_ind and Set Reporting To GLR Call process, followed by Wait For Response. From Wait For Response, it branches to Set Reporting ack (leading to Set result and MAP_SET_REPORTING_rsp), Set Reporting negative response (leading to Set error), or Abort (leading to MAP_U_ABORT_req). A Vr dialogue leads to Perform MAP Vr Dialogue and then Idle. An Error response leads to Idle. MAP_P_ABORT_ind and MAP_NOTICE_ind also lead to Idle. MAP_CLOSE_req leads to Idle.](750b1652a4f4791b84c02aa755a1dedd_img.jpg) + +**Process Reporting\_State\_Receive\_GLR** 21.3.2.1(1) + +Figure 21.3.2/1: Process in the GLR to respond to a request reporting state + +Signals to/from the left are to/from the HLR; signals to/from the right are to/from the GLR Call process + +``` + +stateDiagram-v2 + [*] --> Idle + Idle --> ReceiveOpenInd + ReceiveOpenInd --> Vr + Vr --> PerformMAPVrDialogue + PerformMAPVrDialogue --> Idle + ReceiveOpenInd --> OK + OK --> WaitForServiceIndication + WaitForServiceIndication --> MAP_P_ABORT_ind + WaitForServiceIndication --> MAP_SET_REPORTING_ind + WaitForServiceIndication --> MAP_NOTICE_ind + MAP_P_ABORT_ind --> Idle + MAP_SET_REPORTING_ind --> SetReportingToGLRCallProcess + SetReportingToGLRCallProcess --> WaitForResponse + MAP_NOTICE_ind --> MAP_CLOSE_req + MAP_CLOSE_req --> Idle + WaitForResponse --> SetReportingAck + WaitForResponse --> SetReportingNegativeResponse + WaitForResponse --> Abort + SetReportingAck --> SetResult + SetReportingNegativeResponse --> SetError + SetResult --> MAP_SET_REPORTING_rsp + SetError --> MAP_SET_REPORTING_rsp + MAP_SET_REPORTING_rsp --> Idle + Abort --> MAP_U_ABORT_req + MAP_U_ABORT_req --> Idle + ReceiveOpenInd --> Error + Error --> Idle + +``` + +State transition diagram for Process Reporting\_State\_Receive\_GLR. The process starts at Idle, receives an Open Indication, and then branches based on the response: OK leads to Wait For Service Indication, which then leads to MAP\_SET\_REPORTING\_ind and Set Reporting To GLR Call process, followed by Wait For Response. From Wait For Response, it branches to Set Reporting ack (leading to Set result and MAP\_SET\_REPORTING\_rsp), Set Reporting negative response (leading to Set error), or Abort (leading to MAP\_U\_ABORT\_req). A Vr dialogue leads to Perform MAP Vr Dialogue and then Idle. An Error response leads to Idle. MAP\_P\_ABORT\_ind and MAP\_NOTICE\_ind also lead to Idle. MAP\_CLOSE\_req leads to Idle. + +Figure 21.3.2/1: Process Reporting\_State\_Receive\_GLR + +![State transition diagram for Process Reporting_State_Send_GLR. The process starts at Idle, transitions to Set Reporting, then sends MAP_Open_req, MAP_SET_REPORTING_req, and MAP_DELIMITER_req. It receives an Open cnf and checks for OK, Vr, or Error. On OK, it goes to Wait For Response. On Vr, it performs MAP Vr. On Error, it sends a negative response. From Wait For Response, it handles MAP_SET_REPORTING_cnf (OK leads to Set Reporting ack, Error leads to negative response), MAP_U_ABORT_ind/MAP_P_ABORT_ind (leads to Abort), or MAP_NOTICE_ind (leads to MAP_CLOSE_req and then Abort).](f61d0925551545b5938b3a4d1bbf63c3_img.jpg) + +**Process Reporting\_State\_Send\_GLR** 21.3.2.2(1) + +Figure 21.3.2/2: Process in the GLR to respond to a request reporting state + +Signals to/from the left are to/from the GLR Call; process signals to/from the right are to/from the VLR + +``` + +stateDiagram-v2 + [*] --> Idle + Idle --> Set_Reporting: Set Reporting + Set_Reporting --> Send_Requests: MAP_Open_req, MAP_SET_REPORTING_req, MAP_DELIMITER_req + Send_Requests --> Receive_Open_cnf: Receive Open cnf + Receive_Open_cnf --> Wait_For_Response: OK + Receive_Open_cnf --> Perform_MAP_Vr: Vr + Receive_Open_cnf --> Set_Negative_Response_1: Error + Perform_MAP_Vr --> [*] + Set_Negative_Response_1 --> [*] + Wait_For_Response --> Check_Cnf: MAP_SET_REPORTING_cnf + Wait_For_Response --> Abort_1: MAP_U_ABORT_ind, MAP_P_ABORT_ind + Wait_For_Response --> MAP_CLOSE_req: MAP_NOTICE_ind + Check_Cnf --> Set_Reporting_Ack: OK + Check_Cnf --> Set_Negative_Response_2: Error + Set_Reporting_Ack --> [*] + Set_Negative_Response_2 --> [*] + Abort_1 --> [*] + MAP_CLOSE_req --> Abort_2: MAP_CLOSE_req + Abort_2 --> [*] + +``` + +State transition diagram for Process Reporting\_State\_Send\_GLR. The process starts at Idle, transitions to Set Reporting, then sends MAP\_Open\_req, MAP\_SET\_REPORTING\_req, and MAP\_DELIMITER\_req. It receives an Open cnf and checks for OK, Vr, or Error. On OK, it goes to Wait For Response. On Vr, it performs MAP Vr. On Error, it sends a negative response. From Wait For Response, it handles MAP\_SET\_REPORTING\_cnf (OK leads to Set Reporting ack, Error leads to negative response), MAP\_U\_ABORT\_ind/MAP\_P\_ABORT\_ind (leads to Abort), or MAP\_NOTICE\_ind (leads to MAP\_CLOSE\_req and then Abort). + +Figure 21.3.2/2: Process Reporting\_State\_Send\_GLR + +## 21.4 Status Reporting + +### 21.4.1 General + +In case that the monitored subscriber becomes to the idle state, the message flow for reporting subscriber's state to the HLR is shown in figure 21.4.1/1. The stage2 specification for the interaction with CCBS in a GLR is in 3GPP TS 23.119. + +![Sequence diagram showing message flow between VLR, GLR, and HLR for status reporting. The VLR sends a MAP_STATUS_REPORT to the GLR, which receives an acknowledgment. The GLR then sends a MAP_STATUS_REPORT to the HLR, which also receives an acknowledgment.](3750b0149a6380885998ab3ca6a8787c_img.jpg) + +``` +sequenceDiagram + participant VLR + participant GLR + participant HLR + Note right of VLR: MAP_STATUS_REPORT + VLR->>GLR: MAP_STATUS_REPORT + Note right of GLR: MAP_STATUS_REPORT ack + GLR-->>VLR: MAP_STATUS_REPORT ack + Note right of GLR: MAP_STATUS_REPORT + GLR->>HLR: MAP_STATUS_REPORT + Note right of HLR: MAP_STATUS_REPORT ack + HLR-->>GLR: MAP_STATUS_REPORT ack +``` + +Sequence diagram showing message flow between VLR, GLR, and HLR for status reporting. The VLR sends a MAP\_STATUS\_REPORT to the GLR, which receives an acknowledgment. The GLR then sends a MAP\_STATUS\_REPORT to the HLR, which also receives an acknowledgment. + +Figure 21.4.1/1: Message Flow for Status Reporting + +### 21.4.2 Process in the GLR for Status Reporting + +The MAP process in the GLR to send the status report to the HLR is shown in figures 21.4.1/1 and 21.4.2/2. + +#### Send Status report + +When receiving the MAP\_STATUS\_REPORT indication, the MAP user in the GLR transfers the information to the HLR in the MAP\_STATUS\_REPORT request. + +The GLR then awaits the receipt of the MAP\_STATUS\_REPORT confirm from the HLR. The MAP user in the GLR shall transfer the information contained in this primitive to the VLR in the MAP\_STATUS\_REPORT response without checking its contents. + +![Flowchart for Process Status_Report_Receive_GLR](38d82ffe820e339811b396206f40a201_img.jpg) + +**Process Status\_Report\_Receive\_GLR** 21.4.2.1(1) + +Figure 21.4.2/1: Process in the GLR to respond to a request status report + +Signals to/from the left are to/from the HLR; signals to/from the right are to/from the GLR Call process + +``` +graph TD; Start([ ]) --> Idle1([Idle]); Idle1 --> RecOpen[Receive Open Ind]; RecOpen --> VrLine(( )); VrLine -- OK --> WaitForService([Wait For Service Indication]); VrLine -- Error --> Idle2([Idle]); WaitForService --> MAP_P_ABORT_ind{MAP_P_ABORT_ind}; WaitForService --> MAP_STATUS_REPORT_ind{MAP_STATUS_REPORT_ind}; WaitForService --> MAP_NOTICE_ind{MAP_NOTICE_ind}; MAP_P_ABORT_ind --> Idle3([Idle]); MAP_STATUS_REPORT_ind --> StatusReportToGLR[Status Report To GLR Call process]; StatusReportToGLR --> WaitForResponse([Wait For Response]); MAP_NOTICE_ind --> MAP_CLOSE_req{MAP_CLOSE_req}; MAP_CLOSE_req --> Idle4([Idle]); WaitForResponse --> StatusReportAck{Status Report ack}; WaitForResponse --> StatusReportNegResponse{Status Report negative response}; WaitForResponse --> Abort{Abort}; StatusReportAck --> SetResult[Set result]; StatusReportNegResponse --> SetError[Set error]; Abort --> MAP_U_ABORT_req{MAP_U_ABORT_req}; SetResult --> MAP_STATUS_REPORT_rsp{MAP_STATUS_REPORT_rsp}; SetError --> MAP_STATUS_REPORT_rsp; MAP_STATUS_REPORT_rsp --> Idle5([Idle]); MAP_U_ABORT_req --> Idle6([Idle]); +``` + +The flowchart illustrates the process for receiving and responding to a status report in the GLR. It begins with an 'Idle' state, followed by 'Receive Open Ind'. A decision point labeled 'Vr' leads to 'OK' (proceeding to 'Wait For Service Indication'), 'Error' (returning to 'Idle'), or 'Vr' (proceeding to 'Perform MAP Vr Dialogue' then 'Idle'). From 'Wait For Service Indication', three paths emerge: 'MAP\_P\_ABORT\_ind' (leading to 'Idle'), 'MAP\_STATUS\_REPORT\_ind' (leading to 'Status Report To GLR Call process' then 'Wait For Response'), and 'MAP\_NOTICE\_ind' (leading to 'MAP\_CLOSE\_req' then 'Idle'). From 'Wait For Response', three paths emerge: 'Status Report ack' (leading to 'Set result'), 'Status Report negative response' (leading to 'Set error'), and 'Abort' (leading to 'MAP\_U\_ABORT\_req' then 'Idle'). Both 'Set result' and 'Set error' lead to 'MAP\_STATUS\_REPORT\_rsp', which then leads to 'Idle'. + +Flowchart for Process Status\_Report\_Receive\_GLR + +**Figure 21.4.2/1: Process Status\_Report\_Receive\_GLR** + +![State transition diagram for Process Status_Report_Send_GLR. The process starts at 'Idle', receives a 'Status Report', sends 'MAP_Open_req', 'MAP_STATUS_REPORT_req', and 'MAP_DELIMITER_req', receives 'Open cnf', and then enters 'Wait For Response'. From 'Wait For Response', it can receive 'MAP_STATUS_REPORT_cnf' (leading to 'Check Confirmation' and then 'Status Report ack' or 'Status Report negative response'), 'MAP_U_ABORT_ind'/'MAP_P_ABORT_ind' (leading to 'Abort'), or 'MAP_NOTICE_ind' (leading to 'MAP_CLOSE_req' and then 'Abort'). Transitions to 'Abort' and 'Status Report negative response' from 'Wait For Response' are labeled 'Vr' and 'Error' respectively and lead to terminal states (X).](11f18bf0233d812ad2604f88f3385d60_img.jpg) + +### Process Status\_Report\_Send\_GLR 21.4.2.2(1) + +Figure 21.4.2/2: Process in the GLR to respond to a request status report + +Signals to/from the left are to/from the GLR Call; process signals to/from the right are to/from the HLR + +``` +stateDiagram-v2 + [*] --> Idle + Idle --> Status_Report + Status_Report --> Open_Req + Open_Req --> Open_Cnf + Open_Cnf --> Wait_For_Response + state "Wait For Response" as Wait_For_Response + state "Status Report" as Status_Report + state "Open cnf" as Open_Cnf + state "Check Confirmation" as Check_Confirmation + state "Status Report ack" as Status_Report_ack + state "Status Report negative response" as Status_Report_negative_response + state "Abort" as Abort + state "MAP_NOTICE_ind" as MAP_NOTICE_ind + state "MAP_CLOSE_req" as MAP_CLOSE_req + + Note right of Open_Req: MAP_Open_req +MAP_STATUS_REPORT_req +MAP_DELIMITER_req + Note left of Open_Cnf: Open cnf + Note right of MAP_NOTICE_ind: MAP_CLOSE_req + Note right of Check_Confirmation: OK / Error + + Wait_For_Response --> Status_Report_ack + Wait_For_Response --> Abort + Wait_For_Response --> MAP_NOTICE_ind + Status_Report_ack --> Check_Confirmation + Check_Confirmation --> Status_Report_ack + Check_Confirmation --> Status_Report_negative_response + Status_Report_ack --> [*] + Status_Report_negative_response --> [*] + Abort --> [*] + MAP_NOTICE_ind --> MAP_CLOSE_req + MAP_CLOSE_req --> Abort + Abort --> [*] +``` + +State transition diagram for Process Status\_Report\_Send\_GLR. The process starts at 'Idle', receives a 'Status Report', sends 'MAP\_Open\_req', 'MAP\_STATUS\_REPORT\_req', and 'MAP\_DELIMITER\_req', receives 'Open cnf', and then enters 'Wait For Response'. From 'Wait For Response', it can receive 'MAP\_STATUS\_REPORT\_cnf' (leading to 'Check Confirmation' and then 'Status Report ack' or 'Status Report negative response'), 'MAP\_U\_ABORT\_ind'/'MAP\_P\_ABORT\_ind' (leading to 'Abort'), or 'MAP\_NOTICE\_ind' (leading to 'MAP\_CLOSE\_req' and then 'Abort'). Transitions to 'Abort' and 'Status Report negative response' from 'Wait For Response' are labeled 'Vr' and 'Error' respectively and lead to terminal states (X). + +Figure 21.4.2/2: Process Status\_Report\_Send\_GLR + +## 21.5 Remote User Free + +### 21.5.1 General + +The message flow for handling remote user free is shown in figure 21.5.1/1. + +![Sequence diagram showing message flow between VLR, GLR, and HLR for Remote User Free. The diagram shows three vertical lifelines: VLR, GLR, and HLR. The sequence of messages is: 1. GLR sends MAP_REMOTE_USER_FREE to VLR. 2. VLR sends MAP_REMOTE_USER_FREE ack to GLR. 3. GLR sends MAP_REMOTE_USER_FREE to HLR. 4. HLR sends MAP_REMOTE_USER_FREE ack to GLR. There is a placeholder '--' between the third and fourth messages.](1e5a58dcaf0936bf18dc3dd0d9cd43ff_img.jpg) + +``` +sequenceDiagram + participant VLR + participant GLR + participant HLR + Note right of GLR: -- + GLR->>VLR: MAP_REMOTE_USER_FREE + VLR-->>GLR: MAP_REMOTE_USER_FREE ack + GLR->>HLR: MAP_REMOTE_USER_FREE + HLR-->>GLR: MAP_REMOTE_USER_FREE ack +``` + +Sequence diagram showing message flow between VLR, GLR, and HLR for Remote User Free. The diagram shows three vertical lifelines: VLR, GLR, and HLR. The sequence of messages is: 1. GLR sends MAP\_REMOTE\_USER\_FREE to VLR. 2. VLR sends MAP\_REMOTE\_USER\_FREE ack to GLR. 3. GLR sends MAP\_REMOTE\_USER\_FREE to HLR. 4. HLR sends MAP\_REMOTE\_USER\_FREE ack to GLR. There is a placeholder '--' between the third and fourth messages. + +Figure 21.5.1/1: Message Flow for Remote User Free + +### 21.5.2 Process in the GLR for Remote User Free + +The MAP process in the GLR to handling Remote User Free is shown in figures 21.5.2/1 and 21.5.2/2. + +#### Remote User Free + +When receiving the MAP\_REMOTE\_USER\_FREE indication, the MAP user in the GLR transfers the information to the VLR in the MAP\_REMOTE\_USER\_FREE request. + +The GLR then awaits the receipt of the MAP\_REMOTE\_USER\_FREE confirm from the VLR. The MAP user in the GLR shall transfer the information contained in this primitive to the HLR in the MAP\_REMOTE\_USER\_FREE response without checking its contents. + +![State transition diagram for Process Remote_User_Free_Receive_GLR. The process starts at Idle, receives an Open Indication, and then branches based on the response: OK leads to Wait For Service Indication, which then leads to MAP_REMOTE_USER_FREE_ind and Remote User Free To GLR Call process, followed by Wait For Response. From Wait For Response, three outcomes are possible: Remote User Free ack leads to Set result and then MAP_REMOTE_USER_FREE_rsp; Remote User Free negative response leads to Set error; Abort leads to MAP_U_ABORT_req. A Vr dialogue path leads to Perform MAP Vr Dialogue. An Error path leads to Idle. MAP_P_ABORT_ind and MAP_NOTICE_ind also lead to Idle. MAP_CLOSE_req leads to Idle.](d2417b04116c354deccb25d98a84a0fb_img.jpg) + +**Process Remote\_User\_Free\_Receive\_GLR** 21.5.2.1(1) + +Figure 21.5.2/1: Process in the GLR to respond to a request remote user free + +Signals to/from the left are to/from the HLR; signals to/from the right are to/from the GLR Call process + +``` +stateDiagram-v2 + [*] --> Idle + Idle --> ReceiveOpenInd + ReceiveOpenInd --> OK + OK --> WaitForServiceIndication + WaitForServiceIndication --> MAP_REMOTE_USER_FREE_ind + MAP_REMOTE_USER_FREE_ind --> RemoteUserFreeToGLRCallProcess[Remote User Free To GLR Call process] + RemoteUserFreeToGLRCallProcess --> WaitForResponse + WaitForResponse --> RemoteUserFreeAck[Remote User Free ack] + WaitForResponse --> RemoteUserFreeNegativeResponse[Remote User Free negative response] + WaitForResponse --> Abort + RemoteUserFreeAck --> SetResult[Set result] + RemoteUserFreeNegativeResponse --> SetError[Set error] + SetResult --> MAP_REMOTE_USER_FREE_rsp + SetError --> MAP_REMOTE_USER_FREE_rsp + MAP_REMOTE_USER_FREE_rsp --> Idle + Abort --> MAP_U_ABORT_req + MAP_U_ABORT_req --> Idle + ReceiveOpenInd --> Vr + Vr --> PerformMAPVrDialogue[Perform MAP Vr Dialogue] + PerformMAPVrDialogue --> Idle + ReceiveOpenInd --> Error + Error --> Idle + WaitForServiceIndication --> MAP_P_ABORT_ind + MAP_P_ABORT_ind --> Idle + WaitForServiceIndication --> MAP_NOTICE_ind + MAP_NOTICE_ind --> MAP_CLOSE_req + MAP_CLOSE_req --> Idle +``` + +State transition diagram for Process Remote\_User\_Free\_Receive\_GLR. The process starts at Idle, receives an Open Indication, and then branches based on the response: OK leads to Wait For Service Indication, which then leads to MAP\_REMOTE\_USER\_FREE\_ind and Remote User Free To GLR Call process, followed by Wait For Response. From Wait For Response, three outcomes are possible: Remote User Free ack leads to Set result and then MAP\_REMOTE\_USER\_FREE\_rsp; Remote User Free negative response leads to Set error; Abort leads to MAP\_U\_ABORT\_req. A Vr dialogue path leads to Perform MAP Vr Dialogue. An Error path leads to Idle. MAP\_P\_ABORT\_ind and MAP\_NOTICE\_ind also lead to Idle. MAP\_CLOSE\_req leads to Idle. + +**Figure 21.5.2/1: Process Remote\_User\_Free\_Receive\_GLR** + +![State transition diagram for Process Remote_User_Free_Send_GLR. The process starts at 'Idle', receives 'Remote User Free', sends 'MAP_Open_req', 'MAP_REMOTE_USER_FREE_req', and 'MAP_DELIMITER_req', then receives 'Open cnf'. From 'Receive Open cnf', an 'OK' path leads to 'Wait For Response', while 'Vr' and 'Error' paths lead to 'Perform MAP Vr' and 'Remote User Free negative response' respectively, both of which are terminated. From 'Wait For Response', three paths emerge: 'MAP_REMOTE_USER_FREE_cnf' leads to 'Check Confirmation', 'MAP_U_ABORT_ind'/'MAP_P_ABORT_ind' leads to 'Abort', and 'MAP_NOTICE_ind' leads to 'MAP_CLOSE_req' and then 'Abort'. 'Check Confirmation' has 'OK' and 'Error' paths leading to 'Remote User Free ack' and 'Remote User Free negative response' respectively, both terminated. All terminal states are marked with an 'X'.](18003425d0e8638dde4acc9c5c468c5c_img.jpg) + +### Process Remote\_User\_Free\_Send\_GLR 21.5.2.2(1) + +Figure 21.5.2/2: Process in the GLR to respond to a request remote user free + +Signals to/from the left are to/from the GLR Call; process signals to/from the right are to/from the VLR + +``` +stateDiagram-v2 + [*] --> Idle + Idle --> Remote_User_Free + Remote_User_Free --> Send_Requests + state "Send_Requests" as Send_Requests + Send_Requests --> Receive_Open_cnf + state "Receive Open cnf" as Receive_Open_cnf + Receive_Open_cnf --> Wait_For_Response : OK + Receive_Open_cnf --> Perform_MAP_Vr : Vr + Receive_Open_cnf --> Remote_User_Free_negative_response_1 : Error + state "Perform MAP Vr" as Perform_MAP_Vr + state "Remote User Free negative response" as Remote_User_Free_negative_response_1 + Perform_MAP_Vr --> [*] + Remote_User_Free_negative_response_1 --> [*] + state "Wait For Response" as Wait_For_Response + Wait_For_Response --> Check_Confirmation : MAP_REMOTE_USER_FREE_cnf + Wait_For_Response --> Abort_1 : MAP_U_ABORT_ind, MAP_P_ABORT_ind + Wait_For_Response --> MAP_NOTICE_ind + state "Check Confirmation" as Check_Confirmation + Check_Confirmation --> Remote_User_Free_ack : OK + Check_Confirmation --> Remote_User_Free_negative_response_2 : Error + state "Remote User Free ack" as Remote_User_Free_ack + state "Remote User Free negative response" as Remote_User_Free_negative_response_2 + Remote_User_Free_ack --> [*] + Remote_User_Free_negative_response_2 --> [*] + state "Abort" as Abort_1 + Abort_1 --> [*] + MAP_NOTICE_ind --> MAP_CLOSE_req + state "MAP CLOSE req" as MAP_CLOSE_req + MAP_CLOSE_req --> Abort_2 : Abort + state "Abort" as Abort_2 + Abort_2 --> [*] +``` + +State transition diagram for Process Remote\_User\_Free\_Send\_GLR. The process starts at 'Idle', receives 'Remote User Free', sends 'MAP\_Open\_req', 'MAP\_REMOTE\_USER\_FREE\_req', and 'MAP\_DELIMITER\_req', then receives 'Open cnf'. From 'Receive Open cnf', an 'OK' path leads to 'Wait For Response', while 'Vr' and 'Error' paths lead to 'Perform MAP Vr' and 'Remote User Free negative response' respectively, both of which are terminated. From 'Wait For Response', three paths emerge: 'MAP\_REMOTE\_USER\_FREE\_cnf' leads to 'Check Confirmation', 'MAP\_U\_ABORT\_ind'/'MAP\_P\_ABORT\_ind' leads to 'Abort', and 'MAP\_NOTICE\_ind' leads to 'MAP\_CLOSE\_req' and then 'Abort'. 'Check Confirmation' has 'OK' and 'Error' paths leading to 'Remote User Free ack' and 'Remote User Free negative response' respectively, both terminated. All terminal states are marked with an 'X'. + +Figure 21.5.2/2: Process Remote\_User\_Free\_Send\_GLR + +# 22 Supplementary services procedures + +## 22.1 Functional supplementary service processes + +### 22.1.1 Functional supplementary service process co-ordinator for GLR + +Any functional SS process in the GLR starts by the GLR receiving a MAP-OPEN service indication. If that service is successful, the GLR can handle supplementary service indications from the VLR. Table 21.1/1 shows the co-ordinating process' reaction on receipt of specific SS service indications from the VLR. After the relevant process is invoked, the received service indication is sent to that process, and the co-ordinating process terminates. + +**Table 21.1/1: Relationship between received service indication and invoked process in the GLR** + +| Service indication received | Process invoked | +|------------------------------------|------------------------| +| MAP_REGISTER_SS_ind | REGISTER_SS_GLR | +| MAP_ERASE_SS_ind | ERASE_SS_GLR | +| MAP_ACTIVATE_SS_ind | ACTIVATE_SS_GLR | +| MAP_DEACTIVATE_SS_ind | DEACTIVATE_SS_GLR | +| MAP_INTERROGATE_SS_ind | INTERROGATE_SS_GLR | +| MAP_REGISTER_PASSWORD | REGISTER_PASSWORD_GLR | + +Figure 22.1/1 shows the co-ordinating process in the GLR. + +#### Process SS\_Coordinator\_GLR + +22.1.1\_1(2) + +Figure 22.1/1: Supplementary Service Coordination process in the GLR, to identify which functional supplementary service process be invoked. + +![Flowchart for Process SS_Coordinator_GLR. It starts with an oval, followed by a NULL connector, then 'Receive_Open_ind' (labeled Section25.1). A 'Wait_for_service_ind' block follows, with an 'Error' path leading to 'Perform_MAP_V1_Dialogue' (labeled v1) and then a NULL connector. A large block contains six parallel paths: MAP_REGISTER_ SS_ind -> Register_SS_GLR -> MAP_REGISTER_ SS_ind; MAP_ERASE_ SS_ind -> Erase_SS_GLR -> MAP_ERASE_ SS_ind; MAP_ACTIVATE_ SS_ind -> Activate_SS_GLR -> MAP_ACTIVATE_ SS_ind; MAP_DEACTIVATE_ SS_ind -> Deactivate_SS_GLR -> MAP_DEACTIVATE_ SS_ind; MAP_INTERROGATE_ SS_ind -> Interrogate_SS_GLR -> MAP_INTERROGATE_ SS_ind; and MAP_REGISTER_PASSWORD_ SS_ind -> Register_Password_SS_GLR -> MAP_REGISTER_PASSWORD_ SS_ind. All six paths converge to a 'Relay_Info' oval. Below this, a 'MAP_NOTICE_ind' block leads to a diamond-shaped 'MAP_CLOSE_ind' block, which then leads to a final NULL connector. A callout box on the right explains signal directions: 'Signals to/from the left are to/from the VLR via the MAP provider; signals to/from the right are to/from the child process'.](7f16ae750ce9a533b0bd301dd986355e_img.jpg) + +``` + +graph TD + Start([ ]) --> NULL1(NULL) + NULL1 --> Receive_Open_ind[Receive_Open_ind] + Receive_Open_ind --- Section25.1[Section25.1] + Receive_Open_ind --> Wait_for_service_ind[Wait_for_service_ind] + Wait_for_service_ind -- Error --> Perform_MAP_V1_Dialogue[Perform_MAP_V1_Dialogue] + Perform_MAP_V1_Dialogue --- v1[v1] + Perform_MAP_V1_Dialogue --> NULL2(NULL) + Wait_for_service_ind --> MR[MAP_REGISTER_ SS_ind] + Wait_for_service_ind --> ME[MAP_ERASE_ SS_ind] + Wait_for_service_ind --> MA[MAP_ACTIVATE_ SS_ind] + Wait_for_service_ind --> MD[MAP_DEACTIVATE_ SS_ind] + Wait_for_service_ind --> MI[MAP_INTERROGATE_ SS_ind] + Wait_for_service_ind --> MP[MAP_REGISTER_PASSWORD_ SS_ind] + MR --> R[Register_SS_GLR] + ME --> E[Erase_SS_GLR] + MA --> A[Activate_SS_GLR] + MD --> D[Deactivate_SS_GLR] + MI --> I[Interrogate_SS_GLR] + MP --> P[Register_Password_SS_GLR] + R --> MR_out[MAP_REGISTER_ SS_ind] + E --> ME_out[MAP_ERASE_ SS_ind] + A --> MA_out[MAP_ACTIVATE_ SS_ind] + D --> MD_out[MAP_DEACTIVATE_ SS_ind] + I --> MI_out[MAP_INTERROGATE_ SS_ind] + P --> MP_out[MAP_REGISTER_PASSWORD_ SS_ind] + MR_out --> Relay_Info([Relay_Info]) + ME_out --> Relay_Info + MA_out --> Relay_Info + MD_out --> Relay_Info + MI_out --> Relay_Info + MP_out --> Relay_Info + Relay_Info --> MN[MAP_NOTICE_ind] + MN --> MC{MAP_CLOSE_ind} + MC --> NULL3(NULL) + MN --- Abort[MAP_U_ABORT_ind +MAP_P_ABORT_ind +MAP_CLOSE_ind] + +``` + +Flowchart for Process SS\_Coordinator\_GLR. It starts with an oval, followed by a NULL connector, then 'Receive\_Open\_ind' (labeled Section25.1). A 'Wait\_for\_service\_ind' block follows, with an 'Error' path leading to 'Perform\_MAP\_V1\_Dialogue' (labeled v1) and then a NULL connector. A large block contains six parallel paths: MAP\_REGISTER\_ SS\_ind -> Register\_SS\_GLR -> MAP\_REGISTER\_ SS\_ind; MAP\_ERASE\_ SS\_ind -> Erase\_SS\_GLR -> MAP\_ERASE\_ SS\_ind; MAP\_ACTIVATE\_ SS\_ind -> Activate\_SS\_GLR -> MAP\_ACTIVATE\_ SS\_ind; MAP\_DEACTIVATE\_ SS\_ind -> Deactivate\_SS\_GLR -> MAP\_DEACTIVATE\_ SS\_ind; MAP\_INTERROGATE\_ SS\_ind -> Interrogate\_SS\_GLR -> MAP\_INTERROGATE\_ SS\_ind; and MAP\_REGISTER\_PASSWORD\_ SS\_ind -> Register\_Password\_SS\_GLR -> MAP\_REGISTER\_PASSWORD\_ SS\_ind. All six paths converge to a 'Relay\_Info' oval. Below this, a 'MAP\_NOTICE\_ind' block leads to a diamond-shaped 'MAP\_CLOSE\_ind' block, which then leads to a final NULL connector. A callout box on the right explains signal directions: 'Signals to/from the left are to/from the VLR via the MAP provider; signals to/from the right are to/from the child process'. + +Figure 22.1/1 (sheet 1 of 2): Process SS\_Coordinator\_GLR + +![Sequence diagram for Process SS_Coordinator_GLR. The diagram shows two parallel processing paths. The left path starts with a 'Relay_Info' object, followed by a '*FROM PROVIDER' message block containing 'MAP_U_ABORT_ind', 'MAP_P_ABORT_ind', and 'MAP_CLOSE_ind'. This is followed by two '*TO OFFSPRING' message blocks, leading to 'Relay_Info' and 'NULL' objects respectively. The right path starts with a '*FROM OFFSPRING' message block containing 'MAP_U_ABORT_ind' and 'MAP_CLOSE_ind'. This is followed by two '*TO PROVIDER' message blocks, leading to 'Relay_Info' and 'NULL' objects respectively.](a963ca41bde1669b18a4b783616f228b_img.jpg) + +**Process SS\_Coordinator\_GLR** 22.1.1\_2(2) + +Figure 22.1/1: Supplementary Service Coordination process in the GLR, to identify which functional supplementary service process be invoked. + +Signals to/from the left are to/from the VLR via the MAP provider; signals to/from the right are to/from the child process + +``` + +sequenceDiagram + participant RI1 as Relay_Info + Note left of RI1: MAP_U_ABORT_ind, MAP_P_ABORT_ind, MAP_CLOSE_ind + RI1->>FP: *FROM PROVIDER + FP->>TOO1: *TO OFFSPRING + TOO1->>RI2 as Relay_Info + FP->>TOO2: *TO OFFSPRING + TOO2->>NULL1 as NULL + + Note right of RI1: MAP_U_ABORT_ind, MAP_CLOSE_ind + FO->>TP1: *FROM OFFSPRING + TP1->>RI3 as Relay_Info + TP1->>TP2: *TO PROVIDER + TP2->>NULL2 as NULL + +``` + +Sequence diagram for Process SS\_Coordinator\_GLR. The diagram shows two parallel processing paths. The left path starts with a 'Relay\_Info' object, followed by a '\*FROM PROVIDER' message block containing 'MAP\_U\_ABORT\_ind', 'MAP\_P\_ABORT\_ind', and 'MAP\_CLOSE\_ind'. This is followed by two '\*TO OFFSPRING' message blocks, leading to 'Relay\_Info' and 'NULL' objects respectively. The right path starts with a '\*FROM OFFSPRING' message block containing 'MAP\_U\_ABORT\_ind' and 'MAP\_CLOSE\_ind'. This is followed by two '\*TO PROVIDER' message blocks, leading to 'Relay\_Info' and 'NULL' objects respectively. + +**Figure 22.1/1 (sheet 2 of 2): Process SS\_Coordinator\_GLR** + +### 22.1.2 Call completion supplementary service process co-ordinator for GLR + +The MAP co-ordinating process in the GLR to handle a dialogue opened with the call Completion application context is shown in figure 22.1/2. The MAP process invokes a macro not defined in this subclause; the definition of this macro can be found as follows: + +Receive\_Open\_Ind            see subclause 25.1. + +Any call completion SS process in the GLR starts by the GLR receiving a MAP-OPEN service indication. If that service is successful, the GLR can handle call completion supplementary service indications from the VLR. Table 22.1/2 shows the co-ordinating process' reaction on receipt of specific call completion SS service indications from the VLR. After the relevant process is invoked, the received service indication is sent to that process. + +**Table 22.1/2: Relationship between received service indication and invoked process in the GLR** + +| Service indication received | Process invoked | +|------------------------------------|------------------------| +| MAP_REGISTER_CC_ENTRY_ind | REGISTER_CC_ENTRY_GLR | +| MAP_ERASE_CC_ENTRY_ind | ERASE_CC_ENTRY_GLR | + +After creation of the user process the Co-ordinator relays the messages between the MAP\_PM and the invoked process until a request or an indication for dialogue termination is received. + +The Call\_Completion Co-ordinator is shown in figure 22.1/2. + +![Flowchart for Process CC_Coord_GLR. The process starts at an oval, goes to an 'Idle' state (oval). It receives an 'Open_ind' (rectangle) from the left, labeled 'Section 25.1'. From 'Open_ind', an 'OK' path leads to 'Wait_for_service_ind' (oval) and a 'Vr, Error' path leads to another 'Idle' state (oval). From 'Wait_for_service_ind', three paths lead to 'MAP_REGISTER_CC_ENTRY_ind' (parallelogram), 'MAP_ERASE_CC_ENTRY_ind' (parallelogram), and 'MAP_NOTICE_ind' (parallelogram). 'MAP_REGISTER_CC_ENTRY_ind' leads to 'Register_CC_RNTRY_GLR' (rectangle), which leads to 'MAP_REGISTER_CC_ENTRY_ind' (parallelogram). 'MAP_ERASE_CC_ENTRY_ind' leads to 'Erase_CC_ENTRY_GLR' (rectangle), which leads to 'MAP_ERASE_CC_ENTRY_ind' (parallelogram). 'MAP_NOTICE_ind' leads to 'MAP_CLOSE_ind' (diamond), which leads to an 'Idle' state (oval). Both 'MAP_REGISTER_CC_ENTRY_ind' and 'MAP_ERASE_CC_ENTRY_ind' lead to 'Relay_Info' (oval). From 'Relay_Info', the flow splits into two main branches. The left branch has a 'FROM PROVIDER' parallelogram leading to a 'TO OFFSPRING' parallelogram, which leads to 'Relay_Info' (oval). The right branch has a 'FROM OFFSPRING' parallelogram leading to a 'TO PROVIDER' parallelogram, which leads to 'Relay_Info' (oval). There are also 'TO OFFSPRING' and 'TO PROVIDER' parallelograms leading to 'NULL' (oval) states. Various 'MAP_U_ABORT_ind', 'MAP_P_ABORT_ind', and 'MAP_CLOSE_ind' signals are shown in boxes on the right side of the diagram.](e16bfa31d748f4d99ec4ae3d16656926_img.jpg) + +**Process CC\_Coord\_GLR** 22.1.2(1) + +Figure 22.1/2: Coordinating process in the GLR to handle dialogue opened with the AC Call Completion Context + +Signals to/from the left are to/from the VLR via the MAP provider; signals to/from the right are to/from the child process + +``` + +graph TD + Start([ ]) --> Idle1([Idle]) + Idle1 --> Open_ind[Receive_Open_ind] + Open_ind -- "Section 25.1" --> Open_ind + Open_ind -- OK --> Wait_for_service_ind([Wait_for_service_ind]) + Open_ind -- "Vr, Error" --> Idle2([Idle]) + Wait_for_service_ind --> MAP_REGISTER_CC_ENTRY_ind1[MAP_REGISTER_CC_ENTRY_ind] + Wait_for_service_ind --> MAP_ERASE_CC_ENTRY_ind1[MAP_ERASE_CC_ENTRY_ind] + Wait_for_service_ind --> MAP_NOTICE_ind[MAP_NOTICE_ind] + MAP_REGISTER_CC_ENTRY_ind1 --> Register_CC_RNTRY_GLR[Register_CC_RNTRY_GLR] + Register_CC_RNTRY_GLR --> MAP_REGISTER_CC_ENTRY_ind2[MAP_REGISTER_CC_ENTRY_ind] + MAP_ERASE_CC_ENTRY_ind1 --> Erase_CC_ENTRY_GLR[Erase_CC_ENTRY_GLR] + Erase_CC_ENTRY_GLR --> MAP_ERASE_CC_ENTRY_ind2[MAP_ERASE_CC_ENTRY_ind] + MAP_NOTICE_ind --> MAP_CLOSE_ind{MAP_CLOSE_ind} + MAP_CLOSE_ind --> Idle3([Idle]) + MAP_REGISTER_CC_ENTRY_ind2 --> Relay_Info1([Relay_Info]) + MAP_ERASE_CC_ENTRY_ind2 --> Relay_Info1 + Relay_Info1 --> FROM_PROVIDER[FROM PROVIDER] + FROM_PROVIDER --> TO_OFFSPRING1[TO OFFSPRING] + TO_OFFSPRING1 --> Relay_Info2([Relay_Info]) + FROM_PROVIDER --> TO_OFFSPRING2[TO OFFSPRING] + TO_OFFSPRING2 --> NULL1([NULL]) + FROM_OFFSPRING[FROM OFFSPRING] --> TO_PROVIDER1[TO PROVIDER] + TO_PROVIDER1 --> Relay_Info3([Relay_Info]) + FROM_OFFSPRING --> TO_PROVIDER2[TO PROVIDER] + TO_PROVIDER2 --> NULL2([NULL]) + +``` + +Flowchart for Process CC\_Coord\_GLR. The process starts at an oval, goes to an 'Idle' state (oval). It receives an 'Open\_ind' (rectangle) from the left, labeled 'Section 25.1'. From 'Open\_ind', an 'OK' path leads to 'Wait\_for\_service\_ind' (oval) and a 'Vr, Error' path leads to another 'Idle' state (oval). From 'Wait\_for\_service\_ind', three paths lead to 'MAP\_REGISTER\_CC\_ENTRY\_ind' (parallelogram), 'MAP\_ERASE\_CC\_ENTRY\_ind' (parallelogram), and 'MAP\_NOTICE\_ind' (parallelogram). 'MAP\_REGISTER\_CC\_ENTRY\_ind' leads to 'Register\_CC\_RNTRY\_GLR' (rectangle), which leads to 'MAP\_REGISTER\_CC\_ENTRY\_ind' (parallelogram). 'MAP\_ERASE\_CC\_ENTRY\_ind' leads to 'Erase\_CC\_ENTRY\_GLR' (rectangle), which leads to 'MAP\_ERASE\_CC\_ENTRY\_ind' (parallelogram). 'MAP\_NOTICE\_ind' leads to 'MAP\_CLOSE\_ind' (diamond), which leads to an 'Idle' state (oval). Both 'MAP\_REGISTER\_CC\_ENTRY\_ind' and 'MAP\_ERASE\_CC\_ENTRY\_ind' lead to 'Relay\_Info' (oval). From 'Relay\_Info', the flow splits into two main branches. The left branch has a 'FROM PROVIDER' parallelogram leading to a 'TO OFFSPRING' parallelogram, which leads to 'Relay\_Info' (oval). The right branch has a 'FROM OFFSPRING' parallelogram leading to a 'TO PROVIDER' parallelogram, which leads to 'Relay\_Info' (oval). There are also 'TO OFFSPRING' and 'TO PROVIDER' parallelograms leading to 'NULL' (oval) states. Various 'MAP\_U\_ABORT\_ind', 'MAP\_P\_ABORT\_ind', and 'MAP\_CLOSE\_ind' signals are shown in boxes on the right side of the diagram. + +Figure 22.1/2: Process\_CC\_Coord\_GLR + +## 22.2 Registration procedure + +### 22.2.1 General + +The registration procedure is used to register data related to a supplementary service in the HLR. The registration procedure is a fully transparent communication between the MS and the HLR. + +### 22.2.2 Procedures in the GLR + +#### Supplementary service registration + +When receiving the MAP\_REGISTER\_SS indication from VLR, the MAP user in the GLR transfers the information to the HLR in the MAP\_REGISTER\_SS request without checking the contents of the service indication. + +The GLR then awaits the receipt of the MAP\_REGISTER\_SS confirm from the HLR. The MAP user in the GLR shall transfer the information contained in this primitive to the VLR in the MAP\_REGISTER\_SS response without checking its contents. + +#### Error handling + +If at any time during this procedure a MAP\_P\_ABORT, MAP\_U\_ABORT, MAP\_NOTICE or unexpected MAP\_CLOSE indication is received from the VLR concerning the process, a MAP\_U\_ABORT request indicating application procedure cancellation is sent to the HLR (if a connection exists). If a MAP\_NOTICE indication was received from the VLR, that dialogue must be closed by sending a MAP\_CLOSE request towards the VLR. The process is terminated. + +If a MAP\_P\_ABORT, MAP\_U\_ABORT or MAP\_CLOSE indication is received from the HLR, a MAP\_U\_ABORT request shall be sent to the VLR terminating the process. If a MAP\_NOTICE indication was received from the HLR, that dialogue must be closed by sending a MAP\_CLOSE request towards the HLR. The process terminates. + +The registration procedure in the GLR is shown in figure 22.2/1. + +![Sequence diagram for Process SS_REGISTER_GLR showing the interaction between a mobile station and the network (VLR/HLR). The process starts with NULL, followed by MAP_REGISTER_SS_ind, MAP_OPEN_req (with Destination reference = subscriber's IMSI and Originating reference = GLR number), MAP_REGISTER_req, MAP_DELIMITER_req, and Receive_Open_Confirm (Section 25.1). From Receive_Open_Confirm, an 'OK' path leads to Wait_for_ss_cnf and a 'Vr, Error' path leads to MAP_U_ABORT_req. There is also a MAP_NOTICE_ind and MAP_CLOSE_req sequence. A box on the right lists MAP_U_ABORT_ind, MAP_P_ABORT_ind, and MAP_CLOSE_ind. The diagram includes callouts for signal directions and a connector '1'.](fc3e2b49a9f850951570e502393b697f_img.jpg) + +### Process SS\_REGISTER\_GLR + +22.2.1\_1(2) + +Figure 22.2/1: Mobile Initiated registration of supplementary service in the GLR + +Signals to/from the left are to/from the VLR +signals to/from the right are to/from the HLR +unless otherwise stated + +``` +sequenceDiagram + participant MS as Mobile Station + participant VLR as VLR + participant HLR as HLR + + Note left of MS: NULL + MS->>VLR: MAP_REGISTER_SS_ind + VLR->>HLR: MAP_OPEN_req + Note right of MAP_OPEN_req: Including +- Destination reference = subscriber's IMSI +- Originating reference = GLR number + VLR->>MS: MAP_REGISTER_req + VLR->>MS: MAP_DELIMITER_req + VLR->>MS: Receive_Open_Confirm + Note right of Receive_Open_Confirm: Section 25.1 + Note right of Receive_Open_Confirm: 1 + MS-->>VLR: OK + MS-->>VLR: Vr, Error + VLR->>MS: Wait_for_ss_cnf + VLR->>MS: MAP_U_ABORT_req + Note right of VLR: MAP_NOTICE_ind + VLR->>HLR: MAP_CLOSE_req + Note right of HLR: MAP_U_ABORT_ind +MAP_P_ABORT_ind +MAP_CLOSE_ind +``` + +Sequence diagram for Process SS\_REGISTER\_GLR showing the interaction between a mobile station and the network (VLR/HLR). The process starts with NULL, followed by MAP\_REGISTER\_SS\_ind, MAP\_OPEN\_req (with Destination reference = subscriber's IMSI and Originating reference = GLR number), MAP\_REGISTER\_req, MAP\_DELIMITER\_req, and Receive\_Open\_Confirm (Section 25.1). From Receive\_Open\_Confirm, an 'OK' path leads to Wait\_for\_ss\_cnf and a 'Vr, Error' path leads to MAP\_U\_ABORT\_req. There is also a MAP\_NOTICE\_ind and MAP\_CLOSE\_req sequence. A box on the right lists MAP\_U\_ABORT\_ind, MAP\_P\_ABORT\_ind, and MAP\_CLOSE\_ind. The diagram includes callouts for signal directions and a connector '1'. + +Figure 22.2/1 (sheet 1 of 2): Procedure SS\_Register\_GLR + +![Sequence diagram for Process SS_REGISTER_GLR showing Mobile Initiated registration of supplementary service in the GLR. The diagram starts with 'Wait_for_ss_cnf' and branches based on 'MAP P_ERROR'.](6a993bfdf2e00cfad01c4d2188a75d86_img.jpg) + +**Process SS\_REGISTER\_GLR** 22.2.1\_2(2) + +Figure 22.2/1: Mobile Initiated registration of supplementary service in the GLR + +Signals to/from the left are to/from the VLR +signals to/from the right are to/from the HLR +unless otherwise stated + +``` + +sequenceDiagram + participant MS + participant VLR + participant HLR + Note left of MS: Wait_for_ss_cnf + MS->>VLR: MAP_REGISTER_SS_req + VLR->>HLR: MAP_REGISTER_SS_req + HLR-->>VLR: MAP_REGISTER_SS_rsp + VLR-->>MS: MAP_REGISTER_SS_rsp + Note right of MS: Signals to/from the left are to/from the VLR +signals to/from the right are to/from the HLR +unless otherwise stated + VLR->>MS: MAP P_ERROR (yes) + Note right of MS: 1 + VLR-->>MS: MAP_REGISTER_SS_rsp + VLR->>HLR: MAP_CLOSE_req + Note right of MS: X + Note right of MS: MAP_U_ABORT_ind +MAP_P_ABORT_ind + Note right of MS: MAP_NOTICE_ind + Note right of MS: MAP_CLOSE_req + Note right of MS: X + Note right of MS: MAP_U_ABORT_req + Note right of MS: X + +``` + +Sequence diagram for Process SS\_REGISTER\_GLR showing Mobile Initiated registration of supplementary service in the GLR. The diagram starts with 'Wait\_for\_ss\_cnf' and branches based on 'MAP P\_ERROR'. + +Figure 22.2/1 (sheet 2 of 2): Procedure SS\_Register\_GLR + +## 22.3 Erasure procedure + +### 22.3.1 General + +The erasure procedure is used to erase data related to a supplementary service in the HLR. The erasure procedure is a fully transparent communication between the MS and the HLR. + +### 22.3.2 Procedures in the GLR + +The GLR procedures for erasure are identical to those specified for registration in subclause 22.2. The text and diagrams in subclause 22.2 apply with all references to registration changed to erasure. + +## 22.4 Activation procedure + +### 22.4.1 General + +The activation procedure is used to activate a supplementary service in the HLR. The activation procedure is a fully transparent communication between the MS and the HLR. + +### 22.4.2 Procedures in the GLR + +#### Supplementary service activation + +When receiving the MAP\_ACTIVATE\_SS indication, the MAP user in the GLR transfers the information to the HLR in the MAP\_ACTIVATE\_SS request without checking the contents of the service indication. + +The GLR may then receive the MAP\_GET\_PASSWORD indication. This information is transferred to the VLR in the MAP\_GET\_PASSWORD request. If a MAP\_GET\_PASSWORD confirm primitive is received from the VLR, the VLR initiates the MAP\_GET\_PASSWORD response towards the HLR. + +The GLR will receive the MAP\_ACTIVATE\_SS confirm from the HLR. The MAP user in the GLR shall transfer the information contained in this primitive to the VLR in the MAP\_ACTIVATE\_SS response without checking its contents. + +#### Error handling + +The handling of MAP\_P\_ABORT, MAP\_U\_ABORT, MAP\_NOTICE and unexpected MAP\_CLOSE in this procedure is identical to the handling in the Registration procedure in the GLR, see subclause 22.2 of the present document. + +The activation procedure in the GLR is shown in figure 22.4/1. + +![Flowchart for Process SS_ACTIVATE_GLR. The process starts with an oval, followed by a 'NULL' block. It then enters a loop: 'MAP ACTIVATE_SS_ind' -> 'MAP_OPEN_req' (with a note: 'To HLR, Including - Destination reference = subscriber's IMSI - Originating reference = GLR number') -> 'MAP_ACTIVATE_req' -> 'MAP_DELIMITER_req' -> 'Receive_Open_Confirm' (linked to 'Section 25.1'). From 'Receive_Open_Confirm', an 'OK' path leads to 'Wait_for_ss_cnf' and a 'Vr,Error' path leads to 'MAP_U_ABORT_req' (which ends in a cross). A circle with the number '1' is on the 'Vr,Error' path. To the right, 'MAP_NOTICE_ind' -> 'MAP_CLOSE_req' (which ends in a cross) is shown. A box on the far right lists 'MAP_U_ABORT_ind', 'MAP_P_ABORT_ind', and 'MAP_CLOSE_ind'.](e18841eb4a995df8354a793459e12fd0_img.jpg) + +### Process SS\_ACTIVATE\_GLR + +22.4.1\_1(2) + +Figure 22.4/1: Activation of supplementary service procedure in the GLR + +Signals to/from the left are to/from the VLR via the MAP provider; signals to/from the right are to/from the child process + +``` +graph TD; Start([ ]) --> NULL[NULL]; NULL --> MAP_ACTIVATE_SS_ind{MAP ACTIVATE_SS_ind}; MAP_ACTIVATE_SS_ind --> MAP_OPEN_req{MAP_OPEN_req}; MAP_OPEN_req --> To_HLR["To HLR, Including
- Destination reference = subscriber's IMSI
- Originating reference = GLR number"]; To_HLR --> MAP_ACTIVATE_req{MAP_ACTIVATE_req}; MAP_ACTIVATE_req --> MAP_DELIMITER_req{MAP_DELIMITER_req}; MAP_DELIMITER_req --> Receive_Open_Confirm[Receive_Open_Confirm]; Receive_Open_Confirm --> Section_25_1[Section 25.1]; Receive_Open_Confirm -- OK --> Wait_for_ss_cnf[Wait_for_ss_cnf]; Receive_Open_Confirm -- Vr,Error --> Circle_1((1)); Circle_1 --> MAP_U_ABORT_req{MAP_U_ABORT_req}; MAP_U_ABORT_req --> Cross1[×]; MAP_NOTICE_ind{MAP NOTICE_ind} --> MAP_CLOSE_req{MAP_CLOSE_req}; MAP_CLOSE_req --> Cross2[×]; MAP_U_ABORT_ind[MAP_U_ABORT_ind]; MAP_P_ABORT_ind[MAP_P_ABORT_ind]; MAP_CLOSE_ind[MAP_CLOSE_ind]; +``` + +Flowchart for Process SS\_ACTIVATE\_GLR. The process starts with an oval, followed by a 'NULL' block. It then enters a loop: 'MAP ACTIVATE\_SS\_ind' -> 'MAP\_OPEN\_req' (with a note: 'To HLR, Including - Destination reference = subscriber's IMSI - Originating reference = GLR number') -> 'MAP\_ACTIVATE\_req' -> 'MAP\_DELIMITER\_req' -> 'Receive\_Open\_Confirm' (linked to 'Section 25.1'). From 'Receive\_Open\_Confirm', an 'OK' path leads to 'Wait\_for\_ss\_cnf' and a 'Vr,Error' path leads to 'MAP\_U\_ABORT\_req' (which ends in a cross). A circle with the number '1' is on the 'Vr,Error' path. To the right, 'MAP\_NOTICE\_ind' -> 'MAP\_CLOSE\_req' (which ends in a cross) is shown. A box on the far right lists 'MAP\_U\_ABORT\_ind', 'MAP\_P\_ABORT\_ind', and 'MAP\_CLOSE\_ind'. + +Figure 22.4/1 (sheet 1 of 2): Procedure Activate\_SS\_GLR + +![Flowchart for Process SS_ACTIVATE_GLR. The process starts with 'Wait_for_ss_cnf'. It branches into two main paths. The left path involves 'MAP_REGISTER_SS_cnf', a decision 'MAP_P_ERROR' (yes leads to connector 1, no leads to 'MAP_REGISTER_SS_rsp'), 'MAP_CLOSE_req', and an error symbol. The right path involves 'MAP_NOTICE_ind', 'MAP_CLOSE_req', 'MAP_U_ABORT_req', and an error symbol. A central box contains 'MAP_U_ABORT_ind', 'MAP_P_ABORT_ind', and 'MAP_CLOSE_ind'. A bottom section includes 'MAP_NOTICE_ind', 'MAP_CLOSE_req', 'MAP_U_ABORT_req', 'GET_PASSWORD_GLR' (linked to Section 22.10), 'OK' leading to 'Wait_for_ss_cnf', and 'NULL' leading to an error symbol.](0b998e3ad8f9d104768642612605cb35_img.jpg) + +**Process SS\_ACTIVATE\_GLR** 22.4.1\_2(2) + +Figure 22.4/1: Activation of supplementary service procedure in the GLR + +Signals to/from the left are to/from the VLR via the MAP provider; signals to/from the right are to/from the child process + +``` + +graph TD + Start([Wait_for_ss_cnf]) --> LeftPath[ ] + subgraph LeftPath + direction TB + L1[MAP_REGISTER_SS_cnf] --> L2{MAP_P_ERROR} + L2 -- yes --> L3((1)) + L2 -- no --> L4[MAP_REGISTER_SS_rsp] + L4 --> L5[MAP_CLOSE_req] + L5 --> L6[✗] + end + subgraph RightPath + direction TB + R1[MAP_NOTICE_ind] --> R2[MAP_CLOSE_req] + R2 --> R3[MAP_U_ABORT_req] + R3 --> R4[✗] + end + subgraph BottomPath + direction TB + B1[MAP_NOTICE_ind] --> B2[MAP_CLOSE_req] + B2 --> B3[MAP_U_ABORT_req] + B3 --> B4[✗] + B5[GET_PASSWORD_GLR] -- OK --> B6([Wait_for_ss_cnf]) + B5 -- NULL --> B7[✗] + end + L1 --> Center[ ] + R1 --> Center + B1 --> Center + Center --> CenterData[MAP_U_ABORT_ind +MAP_P_ABORT_ind +MAP_CLOSE_ind] + CenterData --> Center + Center --> B5 + B5 --> B5Ref[Section 22.10] + +``` + +Flowchart for Process SS\_ACTIVATE\_GLR. The process starts with 'Wait\_for\_ss\_cnf'. It branches into two main paths. The left path involves 'MAP\_REGISTER\_SS\_cnf', a decision 'MAP\_P\_ERROR' (yes leads to connector 1, no leads to 'MAP\_REGISTER\_SS\_rsp'), 'MAP\_CLOSE\_req', and an error symbol. The right path involves 'MAP\_NOTICE\_ind', 'MAP\_CLOSE\_req', 'MAP\_U\_ABORT\_req', and an error symbol. A central box contains 'MAP\_U\_ABORT\_ind', 'MAP\_P\_ABORT\_ind', and 'MAP\_CLOSE\_ind'. A bottom section includes 'MAP\_NOTICE\_ind', 'MAP\_CLOSE\_req', 'MAP\_U\_ABORT\_req', 'GET\_PASSWORD\_GLR' (linked to Section 22.10), 'OK' leading to 'Wait\_for\_ss\_cnf', and 'NULL' leading to an error symbol. + +Figure 22.4/1 (sheet 2 of 2): Procedure SS\_Activate\_GLR + +## 22.5 Deactivation procedure + +### 22.5.1 General + +The deactivation procedure is used to deactivate a supplementary service in the HLR. The deactivation procedure is a fully transparent communication between the MS and the HLR. + +### 22.5.2 Procedures in the GLR + +The GLR procedures for deactivation are identical to those specified for activation in subclause 22.4. The text and diagrams in subclause 22.4 apply with all references to activation changed to deactivation. + +## 22.6 Interrogation procedure + +### 22.6.1 General + +The interrogation procedure is used to retrieve information related to a supplementary service from the VLR or the HLR. The interrogation procedure in the GLR is a fully transparent communication between the VLR and the HLR. + +### 22.6.2 Procedures in the GLR + +The GLR procedures for interrogation are identical to those specified for registration in subclause 22.2. The text and diagrams in subclause 22.2 apply with all references to registration changed to interrogation. + +## 22.7 Password registration procedure + +### 22.7.1 General + +The password registration procedure is used to register a password in the HLR. The password registration procedure is a fully transparent communication between the MS and the HLR. + +### 22.7.2 Procedures in the GLR + +The password registration procedure in the GLR is identical to that for activation specified in subclause 22.4. All the text and diagrams in subclause 22.4 apply with all references to activation changed to password registration. + +## 22.8 Mobile Initiated USSD procedure + +### 22.8.1 Procedures in the GLR + +The initiation of the process is shown in subclause 22.1. + +In the case that a GLR is located between the VLR and the HLR, the Mobile Initiated USSD procedure in the GLR is a fully transparent communication between the VLR and the HLR. + +When receiving the MAP\_PROCESS\_UNSTRUCTURED\_SS\_REQUEST indication from VLR, the MAP user in the GLR transfers the information to the HLR in the MAP\_PROCESS\_UNSTRUCTURED\_SS\_REQUEST request without checking the contents of the service indication. + +The GLR may subsequently receive one or more MAP\_UNSTRUCTURED\_SS\_REQUEST or MAP\_UNSTRUCTURED\_SS\_NOTIFY indications from the HLR. These shall be sent transparently to the VLR. When a confirmation is received from the VLR this shall be returned to the HLR. + +When the GLR receives a MAP\_PROCESS\_UNSTRUCTURED\_SS\_REQUEST confirmation from the HLR then it shall pass this to the VLR and closes the MAP provider service. + +#### Error Handling + +Both the VLR and the HLR may initiate release of the MAP service at any time. This is handled as shown in the diagrams. + +The procedure in the HLR is shown in figure 22.8/1. + +![Flowchart for Process MS_INIT_USSD_GLR. The process starts with NULL, followed by Receive_Open_ind (Section25.1). It branches based on OK (Wait_for_service_ind) or Vr, Error (NULL). The main path involves MAP_PROCESS_UNSTD_SS_REQUEST_ind, MAP_OPEN_req (with Destination reference = subscriber's IMSI and Originating reference = GLR number), MAP_PROCESS_UNSTD_SS_REQUEST_req, MAP_DELIMITER_req, and Receive_Open_cnf (Section25.1). From Receive_Open_cnf, it branches based on OK (Wait_for_pussd_cnf), Vr (MAP_U_ABORT_req), or Error (Set UE= System Failure). MAP_U_ABORT_req leads to MAP_PROCESS_UNSTD_SS_REQUEST_rsp and then NULL. MAP_NOTICE_ind and MAP_CLOSE_ind are shown as side paths with a cross-out on the latter.](ba676d18b6a00f27c5bfaec9eeec20be_img.jpg) + +### Process MS\_INIT\_USSD\_GLR + +22.8.1\_1(2) + +Figure 22.8/1: Handling of mobile initiated USSD at GLR. + +Signals to/from the left are to/from the VLR +signals to/from the right are to/from the HLR +unless otherwise stated + +``` +graph TD + NULL1(NULL) --> RO1[Receive_Open_ind] + RO1 --- S25_1_1[Section25.1] + RO1 -- OK --> WS[Wait_for_service_ind] + RO1 -- "Vr, Error" --> NULL2(NULL) + WS --> MPRI[MAP_PROCESS_UNSTD_SS_REQUEST_ind] + MPRI --> MR[MAP_NOTICE_ind] + MR --> J1(( )) + J1 --> MAI["MAP_U_ABORT_ind +MAP_P_ABORT_ind +MAP_CLOSE_ind"] + MPRI --> MOR[MAP_OPEN_req] + MOR --- MOR_DETAILS["-Destination reference = subscriber's IMSI +-Originating reference = GLR number"] + MOR --> MPRR[MAP_PROCESS_UNSTD_SS_REQUEST_req] + MRR --> MD[MAP_DELIMITER_req] + MD --> RO2[Receive_Open_cnf] + RO2 --- S25_1_2[Section25.1] + RO2 -- OK --> WPC[Wait_for_pussd_cnf] + RO2 -- Vr --> MUAR[MAP_U_ABORT_req] + RO2 -- Error --> SU["Set UE= System Failure"] + MUAR --> MPRESP[MAP_PROCESS_UNSTD_SS_REQUEST_rsp] + MPRESP --> NULL3(NULL) + MOR --> MC[MAP_CLOSE_ind] + MC -- X --> NULL3 +``` + +Flowchart for Process MS\_INIT\_USSD\_GLR. The process starts with NULL, followed by Receive\_Open\_ind (Section25.1). It branches based on OK (Wait\_for\_service\_ind) or Vr, Error (NULL). The main path involves MAP\_PROCESS\_UNSTD\_SS\_REQUEST\_ind, MAP\_OPEN\_req (with Destination reference = subscriber's IMSI and Originating reference = GLR number), MAP\_PROCESS\_UNSTD\_SS\_REQUEST\_req, MAP\_DELIMITER\_req, and Receive\_Open\_cnf (Section25.1). From Receive\_Open\_cnf, it branches based on OK (Wait\_for\_pussd\_cnf), Vr (MAP\_U\_ABORT\_req), or Error (Set UE= System Failure). MAP\_U\_ABORT\_req leads to MAP\_PROCESS\_UNSTD\_SS\_REQUEST\_rsp and then NULL. MAP\_NOTICE\_ind and MAP\_CLOSE\_ind are shown as side paths with a cross-out on the latter. + +Figure 22.8/1 (sheet 1 of 2): Procedure MI\_USSD\_GLR + +![Flowchart for Process MS_INIT_USSD_GLR showing four main signal paths: MAP_PROCESS_UNSTD_SS_REQUEST_cnf, MAP_UNSTD_SS_NOTIFY_ind, MAP_UNSTD_SS_REQUEST_ind, and MS_Receive_Error_at_GLR. Each path leads to various processing steps including error handling, delimiter processing, and waiting for confirmations.](a5404b7275b06497eecf9b5883604753_img.jpg) + +**Process MS\_INIT\_USSD\_GLR** 22.8.1\_2(2) + +Figure 22.8/1: Handling of mobile initiated USSD at GLR. + +Signals to/from the left are to/from the VLR +signals to/from the right are to/from the HLR +unless otherwise stated + +``` + +graph TD + Start([Wait_for_pussd_cnf]) --> P1[MAP_PROCESS_UNSTD_SS_REQUEST_cnf] + Start --> P2[MAP_UNSTD_SS_NOTIFY_ind] + Start --> P3[MAP_UNSTD_SS_REQUEST_ind] + Start --> P4[MS_Receive_Error_at_GLR] + + P1 --> D1{MAP_P_ERROR} + D1 -- no --> R1[MAP_PROCESS_UNSTD_SS_REQUEST_rsp] + D1 -- yes --> R2[MAP_U_ABORT_req] + R1 --> R3[MAP_DELIMITER_req] + R3 --> W1([Wait_for_ussdn_cnf]) + W1 --> R4[MAP_UNSTD_SS_NOTIFY_cnf] + R4 --> R5[MAP_UNSTD_SS_NOTIFY_rsp] + R5 --> R6[MAP_DELIMITER_req] + R6 --> W2([Wait_for_pussd_cnf]) + + P2 --> D2{MAP_UNSTD_SS_NOTIFY_req} + D2 --> R7[MAP_DELIMITER_req] + R7 --> W3([Wait_for_ussdn_cnf]) + W3 --> R8[MAP_UNSTD_SS_REQUEST_cnf] + R8 --> R9[MS_Receive_Error_at_GLR] + R9 --> NULL1([NULL]) + R8 --> R10[MAP_UNSTD_SS_REQUEST_rsp] + R10 --> R11[MAP_DELIMITER_req] + R11 --> W4([Wait_for_pussd_cnf]) + + P3 --> D3{MAP_UNSTD_SS_REQUEST_req} + D3 --> R12[MAP_DELIMITER_req] + R12 --> W5([Wait_for_ussdn_cnf]) + W5 --> R13[MAP_UNSTD_SS_REQUEST_cnf] + R13 --> R14[MS_Receive_Error_at_GLR] + R14 --> NULL2([NULL]) + R13 --> R15[MAP_UNSTD_SS_REQUEST_rsp] + R15 --> R16[MAP_DELIMITER_req] + R16 --> W6([Wait_for_pussd_cnf]) + + P4 --> NULL3([NULL]) + +``` + +Flowchart for Process MS\_INIT\_USSD\_GLR showing four main signal paths: MAP\_PROCESS\_UNSTD\_SS\_REQUEST\_cnf, MAP\_UNSTD\_SS\_NOTIFY\_ind, MAP\_UNSTD\_SS\_REQUEST\_ind, and MS\_Receive\_Error\_at\_GLR. Each path leads to various processing steps including error handling, delimiter processing, and waiting for confirmations. + +Figure 22.8/1 (sheet 2 of 2): Procedure MI\_USSD\_GLR + +![State transition diagram for MS_Receive_Error_at_GLR macro. It shows two main paths. The left path starts with 'Wait_for_cnf', followed by 'MAP_CLOSE_ind', 'MAP_CLOSE_req', and an end state. The right path starts with 'MAP_U_ABORT_ind' and 'MAP_P_ABORT_ind', leading to 'MAP_NOTICE_ind', 'MAP_CLOSE_req', 'MAP_U_ABORT_req', and an end state. A second part of the diagram shows 'MAP_NOTICE_ind', 'MAP_CLOSE_req', 'MAP_U_ABORT_req', and an end state, with a return path to the first part labeled with 'MAP_U_ABORT_ind', 'MAP_P_ABORT_ind', 'MAP_CLOSE_ind' from VLR.](a7450c80e88ad3f6ca1427ad84020998_img.jpg) + +**Macrodefinition MS\_Receive\_Error\_at\_GLR** 22.8.2(1) + +Figure 22.8/2: Handling of error at GLR for MS initiated USSD + +Signals to/from the left are to/from the VLR + signals to/from the right are to/from the HLR + unless otherwise stated + +``` + +stateDiagram-v2 + [*] --> Wait_for_cnf + state "MAP_CLOSE_ind" as MAP_CLOSE_ind + state "MAP_U_ABORT_ind, MAP_P_ABORT_ind" as MAP_U_ABORT_ind_MAP_P_ABORT_ind + state "MAP_NOTICE_ind" as MAP_NOTICE_ind + state "MAP_CLOSE_req" as MAP_CLOSE_req + state "MAP_U_ABORT_req" as MAP_U_ABORT_req + state [*] as End + + Wait_for_cnf --> MAP_CLOSE_ind + MAP_CLOSE_ind --> MAP_CLOSE_req + MAP_CLOSE_req --> End + + MAP_U_ABORT_ind_MAP_P_ABORT_ind --> MAP_NOTICE_ind + MAP_NOTICE_ind --> MAP_CLOSE_req + MAP_CLOSE_req --> MAP_U_ABORT_req + MAP_U_ABORT_req --> End + + MAP_U_ABORT_req --> MAP_NOTICE_ind + MAP_NOTICE_ind --> MAP_CLOSE_req + MAP_CLOSE_req --> MAP_U_ABORT_req + +``` + +State transition diagram for MS\_Receive\_Error\_at\_GLR macro. It shows two main paths. The left path starts with 'Wait\_for\_cnf', followed by 'MAP\_CLOSE\_ind', 'MAP\_CLOSE\_req', and an end state. The right path starts with 'MAP\_U\_ABORT\_ind' and 'MAP\_P\_ABORT\_ind', leading to 'MAP\_NOTICE\_ind', 'MAP\_CLOSE\_req', 'MAP\_U\_ABORT\_req', and an end state. A second part of the diagram shows 'MAP\_NOTICE\_ind', 'MAP\_CLOSE\_req', 'MAP\_U\_ABORT\_req', and an end state, with a return path to the first part labeled with 'MAP\_U\_ABORT\_ind', 'MAP\_P\_ABORT\_ind', 'MAP\_CLOSE\_ind' from VLR. + +Figure 22.8/2: Macro MS\_Receive\_ERROR\_at\_GLR + +## 22.9 Network initiated USSD procedure + +### 22.9.1 Procedure in the GLR + +In the case that a GLR is located between the VLR and the HLR, the Network initiated USSD procedure in the GLR is a fully transparent communication between the VLR and the HLR. + +The procedure may be invoked by the HLR. It may start by using either the MAP\_UNSTRUCTURED\_SS\_REQUEST or MAP\_UNSTRUCTURED\_SS\_NOTIFY service. + +The GLR may subsequently receive one or more MAP\_UNSTRUCTURED\_SS\_REQUEST\_ind or MAP\_UNSTRUCTURED\_SS\_NOTIFY\_ind indications from the VLR. These shall be sent transparently to the HLR. When a confirmation is received from the HLR this shall be returned to the VLR. + +When the GLR receives a MAP\_CLOSE\_ind from the HLR then it shall pass this to the VLR and close the MAP dialogue. + +#### **Error Handling** + +Both the VLR and the HLR may initiate release of the MAP service at any time. This is handled as shown in the diagrams. + +The Network initiated USSD procedure in the GLR is shown in figure 22.9/1. + +![Flowchart for Process NW_INIT_USSD_GLR. The process starts with NULL, followed by Receive_Open_ind (Section 25.1). It then branches based on OK or Vr, Error. The OK path leads to Wait_for_service_ind, which then branches into three parallel paths: MAP_UNSTD_SS_NOTIFY_ind (leading to MAP_OPEN_req, then MAP_UNSTD_SS_NOTIFY_req, then MAP_DELIMITER_req), MAP_UNSTD_SS_REQUEST_ind (leading to MAP_OPEN_req, then MAP_UNSTD_SS_REQUEST_req), and MAP_NOTICE_ind (leading to MAP_CLOSE_req). All three paths converge to Receive_Open_cnf (Section 25.1). From Receive_Open_cnf, it branches based on OK or Vr, Error. The OK path leads to Wait_for_ussdn_cnf, which then leads to NULL. The Vr, Error path leads to MAP_U_ABORT_req, which then leads to NULL. A box on the right contains MAP_U_ABORT_ind, MAP_P_ABORT_ind, and MAP_CLOSE_ind, with an arrow pointing to the MAP_CLOSE_req path.](17431d8b59408f09df7552d8bdbaa015_img.jpg) + +### Process NW\_INIT\_USSD\_GLR + +22.9.1\_1(2) + +Figure 22.9/1: Handling of network initiated USSD at GLR. + +Signals to/from the left are to/from the VLR +signals to/from the right are to/from the HLR +unless otherwise stated + +``` +graph TD + NULL1(NULL) --> RO1[Receive_Open_ind] + RO1 --- S251_1[Section 25.1] + RO1 -- OK --> WSI(Wait_for_service_ind) + RO1 -- Vr, Error --> NULL2(NULL) + WSI --> MU_NI[MAP_UNSTD_SS_NOTIFY_ind] + WSI --> MU_R[MAP_UNSTD_SS_REQUEST_ind] + WSI --> MN[MAP_NOTICE_ind] + MU_NI --> MO_N[MAP_OPEN_req] + MU_R --> MO_R[MAP_OPEN_req] + MN --> MC[MAP_CLOSE_req] + MO_N --> MUN_N[MAP_UNSTD_SS_NOTIFY_req] + MO_R --> MUN_R[MAP_UNSTD_SS_REQUEST_req] + MC --> MCX((X)) + MUN_N --> MD[MAP_DELIMITER_req] + MUN_R --> MD + MD --> RO2[Receive_Open_cnf] + RO2 --- S251_2[Section 25.1] + RO2 -- OK --> WUC(Wait_for_ussdn_cnf) + RO2 -- Vr, Error --> MU_A[MAP_U_ABORT_req] + WUC --> NULL3(NULL) + MU_A --> NULL4(NULL) + subgraph RightBox [ ] + direction TB + UA[MAP_U_ABORT_ind] + PA[MAP_P_ABORT_ind] + C[MAP_CLOSE_ind] + end + RightBox --> MC +``` + +Flowchart for Process NW\_INIT\_USSD\_GLR. The process starts with NULL, followed by Receive\_Open\_ind (Section 25.1). It then branches based on OK or Vr, Error. The OK path leads to Wait\_for\_service\_ind, which then branches into three parallel paths: MAP\_UNSTD\_SS\_NOTIFY\_ind (leading to MAP\_OPEN\_req, then MAP\_UNSTD\_SS\_NOTIFY\_req, then MAP\_DELIMITER\_req), MAP\_UNSTD\_SS\_REQUEST\_ind (leading to MAP\_OPEN\_req, then MAP\_UNSTD\_SS\_REQUEST\_req), and MAP\_NOTICE\_ind (leading to MAP\_CLOSE\_req). All three paths converge to Receive\_Open\_cnf (Section 25.1). From Receive\_Open\_cnf, it branches based on OK or Vr, Error. The OK path leads to Wait\_for\_ussdn\_cnf, which then leads to NULL. The Vr, Error path leads to MAP\_U\_ABORT\_req, which then leads to NULL. A box on the right contains MAP\_U\_ABORT\_ind, MAP\_P\_ABORT\_ind, and MAP\_CLOSE\_ind, with an arrow pointing to the MAP\_CLOSE\_req path. + +Figure 22.9/1 (sheet 1 of 2): Procedure NI\_USSD\_GLR + +![SDL diagram for Process NW_INIT_USSD_GLR showing state transitions for USSD handling at GLR.](6e9d059430baba0c363e33749f68b107_img.jpg) + +Process NW\_INIT\_USSD\_GLR + +22.9.1\_2(2) + +Figure 22.9/1: Handling of network initiated USSD at GLR. + +Signals to/from the left are to/from the VLR +signals to/from the right are to/from the HLR +unless otherwise stated + +``` + +graph TD + Start([Wait_for_pussd_cnf]) + + %% Path 1: Notify + Start --> NotifyInd[/MAP_UNSTD_SS_NOTIFY_ind/] + NotifyInd --> NotifyReq[MAP_UNSTD_SS_NOTIFY_req] + NotifyReq --> Delim1[MAP_DELIMITER_req] + Delim1 --> WaitUssdn1([Wait_for_ussdn_cnf]) + + WaitUssdn1 --> NotifyCnf[/MAP_UNSTD_SS_NOTIFY_cnf/] + NotifyCnf --> NotifyRsp[MAP_UNSTD_SS_NOTIFY_rsp] + NotifyRsp --> Delim2[MAP_DELIMITER_req] + Delim2 --> Start + + WaitUssdn1 --> RecError1[NW_Receive_Error_at_GLR] + RecError1 --> Null1([NULL]) + + %% Path 2: Request + Start --> RequestInd[/MAP_UNSTD_SS_REQUEST_ind/] + RequestInd --> RequestReq[MAP_UNSTD_SS_REQUEST_req] + RequestReq --> Delim3[MAP_DELIMITER_req] + Delim3 --> WaitUssdn2([Wait_for_ussdn_cnf]) + + WaitUssdn2 --> RequestCnf[/MAP_UNSTD_SS_REQUEST_cnf/] + RequestCnf --> RequestRsp[MAP_UNSTD_SS_REQUEST_rsp] + RequestRsp --> Delim4[MAP_DELIMITER_req] + Delim4 --> Start + + WaitUssdn2 --> RecError2[NW_Receive_Error_at_GLR] + RecError2 --> Null2([NULL]) + + %% Path 3: Direct Error + Start --> RecError3[NW_Receive_Error_at_GLR] + RecError3 --> Null3([NULL]) + +``` + +SDL diagram for Process NW\_INIT\_USSD\_GLR showing state transitions for USSD handling at GLR. + +**Figure 22.9/1 (sheet 2 of 2): Procedure NI\_USSD\_GLR** + +![State transition diagram for NW_Receive_Error_at_GLR macro. It shows two main paths. The left path starts with a start symbol, followed by 'Wait_for_cnf', then 'MAP_CLOSE_ind', 'MAP_CLOSE_req', and an end symbol. The right path starts from the 'Wait_for_cnf' state, goes through a merge point, then 'MAP_U_ABORT_ind' / 'MAP_P_ABORT_ind', then another merge point, then 'MAP_NOTICE_ind', 'MAP_CLOSE_req', 'MAP_U_ABORT_req', and an end symbol. Below this, there is another path starting from a merge point, going through 'MAP_NOTICE_ind', 'MAP_CLOSE_req', 'MAP_U_ABORT_req', and an end symbol. To the right of this path is a box containing 'MAP_U_ABORT_ind', 'MAP_P_ABORT_ind', 'MAP_CLOSE_ind', and 'From VLR'.](eabcb2f8b9acedb194571d5bc734b463_img.jpg) + +### Macrodefinition NW\_Receive\_Error\_at\_GLR + +22.9.2(1) + +Figure 22.9/2: Handling of error at GLR for NW initiated USSD + +Signals to/from the left are to/from the VLR +signals to/from the right are to/from the HLR +unless otherwise stated + +``` +stateDiagram-v2 + [*] --> Wait_for_cnf + state "Wait_for_cnf" as Wait_for_cnf + state "MAP_CLOSE_ind" as MAP_CLOSE_ind + state "MAP_CLOSE_req" as MAP_CLOSE_req + state "MAP_U_ABORT_ind / MAP_P_ABORT_ind" as MAP_U_ABORT_ind_MAP_P_ABORT_ind + state "MAP_NOTICE_ind" as MAP_NOTICE_ind + state "MAP_CLOSE_req" as MAP_CLOSE_req + state "MAP_U_ABORT_req" as MAP_U_ABORT_req + state "MAP_U_ABORT_req" as MAP_U_ABORT_req + state "MAP_NOTICE_ind" as MAP_NOTICE_ind + state "MAP_CLOSE_req" as MAP_CLOSE_req + state "MAP_U_ABORT_req" as MAP_U_ABORT_req + state [*] as [*] + + Wait_for_cnf --> MAP_CLOSE_ind + MAP_CLOSE_ind --> MAP_CLOSE_req + MAP_CLOSE_req --> [*] + + Wait_for_cnf --> Merge1 + state "Merge1" as Merge1 + Merge1 --> MAP_U_ABORT_ind_MAP_P_ABORT_ind + MAP_U_ABORT_ind_MAP_P_ABORT_ind --> Merge2 + state "Merge2" as Merge2 + Merge2 --> MAP_NOTICE_ind + MAP_NOTICE_ind --> MAP_CLOSE_req + MAP_CLOSE_req --> MAP_U_ABORT_req + MAP_U_ABORT_req --> [*] + + Merge3 --> MAP_NOTICE_ind + state "Merge3" as Merge3 + MAP_NOTICE_ind --> MAP_CLOSE_req + MAP_CLOSE_req --> MAP_U_ABORT_req + MAP_U_ABORT_req --> [*] + + Note right of Merge3: MAP_U_ABORT_ind +MAP_P_ABORT_ind +MAP_CLOSE_ind +From VLR +``` + +State transition diagram for NW\_Receive\_Error\_at\_GLR macro. It shows two main paths. The left path starts with a start symbol, followed by 'Wait\_for\_cnf', then 'MAP\_CLOSE\_ind', 'MAP\_CLOSE\_req', and an end symbol. The right path starts from the 'Wait\_for\_cnf' state, goes through a merge point, then 'MAP\_U\_ABORT\_ind' / 'MAP\_P\_ABORT\_ind', then another merge point, then 'MAP\_NOTICE\_ind', 'MAP\_CLOSE\_req', 'MAP\_U\_ABORT\_req', and an end symbol. Below this, there is another path starting from a merge point, going through 'MAP\_NOTICE\_ind', 'MAP\_CLOSE\_req', 'MAP\_U\_ABORT\_req', and an end symbol. To the right of this path is a box containing 'MAP\_U\_ABORT\_ind', 'MAP\_P\_ABORT\_ind', 'MAP\_CLOSE\_ind', and 'From VLR'. + +Figure 22.9/2: Macro NW\_Receive\_Rrror\_at\_GLR + +## 22.10 Common macros for clause 22 + +### 22.10.1 SS Password handling macros + +Macro Get\_Password\_GLR + +This macro is used by the GLR to relay a request for password from the HLR to the VLR, and to relay a response from the VLR back to the HLR. The macro is described in figure 22.10/1. + +![Flowchart for Macrodefinition GET_PASSWORD_GLR. The process starts with an oval connector, followed by MAP_GET_PASSWORD_ind (VLR to GLR), MAP_GET_PASSWORD_req (GLR to VLR), and MAP_DELIMITER_req (GLR to VLR). A 'Wait_for_password' state follows. A horizontal line separates the VLR interaction from the HLR interaction. On the VLR side, MAP_GET_PASSWORD_cnf (VLR to GLR) leads to MAP_GET_PASSWORD_rsp (GLR to VLR), then MAP_DELIMITER_req (GLR to VLR), and an 'OK' connector. On the HLR side, a merge point leads to a box with MAP_U_ABORT_ind and MAP_P_ABORT_ind, then to MAP_NOTICE_ind (GLR to HLR), MAP_CLOSE_req (GLR to HLR), MAP_U_ABORT_req (GLR to HLR), and a 'NULL' connector. A return path from the 'NULL' connector goes back to the HLR side, where it splits into a box with MAP_U_ABORT_ind, MAP_P_ABORT_ind, and MAP_CLOSE_ind, then to another MAP_NOTICE_ind (GLR to HLR), MAP_CLOSE_req (GLR to HLR), MAP_U_ABORT_req (GLR to HLR), and a 'NULL' connector.](40b80ef077f6151a9fbb593b8ad4864d_img.jpg) + +**Macrodefinition GET\_PASSWORD\_GLR** 22.10.1(1) + +Figure 22.10/1: Macro which relay a GET Password request from the HLR to the VLR and relay a GET Password response from the VLR to the HLR + +Signals to/from the left are to/from the VLR +signals to/from the right are to/from the HLR +unless otherwise stated + +``` + +graph TD + Start([ ]) --> MAP_GET_PASSWORD_ind[/MAP_GET_PASSWORD_ind/] + MAP_GET_PASSWORD_ind --> MAP_GET_PASSWORD_req{MAP_GET_PASSWORD_req} + MAP_GET_PASSWORD_req --> MAP_DELIMITER_req{MAP_DELIMITER_req} + MAP_DELIMITER_req --> Wait[Wait_for_password] + Wait --> Split1(( )) + subgraph VLR_Side [VLR Interaction] + Split1 --> MAP_GET_PASSWORD_cnf[/MAP_GET_PASSWORD_cnf/] + MAP_GET_PASSWORD_cnf --> MAP_GET_PASSWORD_rsp{MAP_GET_PASSWORD_rsp} + MAP_GET_PASSWORD_rsp --> MAP_DELIMITER_req2{MAP_DELIMITER_req} + MAP_DELIMITER_req2 --> OK([OK]) + end + Split1 --> Merge1(( )) + subgraph HLR_Side_1 [HLR Interaction 1] + Merge1 --> Abort1[MAP_U_ABORT_ind +MAP_P_ABORT_ind] + Abort1 --> Notice1[/MAP_NOTICE_ind/] + Notice1 --> Close1{MAP_CLOSE_req} + Close1 --> AbortReq1{MAP_U_ABORT_req} + AbortReq1 --> NULL1([NULL]) + end + NULL1 --> Merge2(( )) + subgraph HLR_Side_2 [HLR Interaction 2] + Merge2 --> Abort2[MAP_U_ABORT_ind +MAP_P_ABORT_ind +MAP_CLOSE_ind] + Abort2 --> Notice2[/MAP_NOTICE_ind/] + Notice2 --> Close2{MAP_CLOSE_req} + Close2 --> AbortReq2{MAP_U_ABORT_req} + AbortReq2 --> NULL2([NULL]) + end + Merge1 --> Notice3[/MAP_NOTICE_ind/] + Notice3 --> Close3{MAP_CLOSE_req} + Close3 --> AbortReq3{MAP_U_ABORT_req} + AbortReq3 --> NULL3([NULL]) + +``` + +Flowchart for Macrodefinition GET\_PASSWORD\_GLR. The process starts with an oval connector, followed by MAP\_GET\_PASSWORD\_ind (VLR to GLR), MAP\_GET\_PASSWORD\_req (GLR to VLR), and MAP\_DELIMITER\_req (GLR to VLR). A 'Wait\_for\_password' state follows. A horizontal line separates the VLR interaction from the HLR interaction. On the VLR side, MAP\_GET\_PASSWORD\_cnf (VLR to GLR) leads to MAP\_GET\_PASSWORD\_rsp (GLR to VLR), then MAP\_DELIMITER\_req (GLR to VLR), and an 'OK' connector. On the HLR side, a merge point leads to a box with MAP\_U\_ABORT\_ind and MAP\_P\_ABORT\_ind, then to MAP\_NOTICE\_ind (GLR to HLR), MAP\_CLOSE\_req (GLR to HLR), MAP\_U\_ABORT\_req (GLR to HLR), and a 'NULL' connector. A return path from the 'NULL' connector goes back to the HLR side, where it splits into a box with MAP\_U\_ABORT\_ind, MAP\_P\_ABORT\_ind, and MAP\_CLOSE\_ind, then to another MAP\_NOTICE\_ind (GLR to HLR), MAP\_CLOSE\_req (GLR to HLR), MAP\_U\_ABORT\_req (GLR to HLR), and a 'NULL' connector. + +Figure 22.10/1: Macro Get\_PW\_GLR + +## 22.11 Activation of a CCBS request + +### 22.11.1 General + +The Activation of a CCBS request procedure in the GLR is a fully transparent communication between the VLR and the HLR. + +### 22.11.2 Procedure in the GLR + +When receiving the MAP\_REGISTER\_CC\_ENTRY indication from VLR, the MAP user in the GLR transfers the information to the HLR in the MAP\_REGISTER\_CC\_ENTRY request without checking the contents of the service indication. + +When the GLR receives a MAP\_REGISTER\_CC\_ENTRY confirmation from the HLR then it shall pass this to the VLR and closes the MAP provider service. + +The activation of a CCBS request procedure in the GLR is shown in figure 22.11/1. + +![Sequence diagram for Process Register_CC_Entry_GLR. The process starts with NULL, followed by MAP_REGISTER_CC_ENTRY_ind. It then branches: one path goes to HLR with MAP_OPEN_req (including Destination reference = subscriber's IMSI and Originating reference = GLR number), followed by MAP_REGISTER_CC_ENTRY_req, MAP_DELIMITER_req, and Receive_Open_Confirm (Section 25.1). The other path goes to VLR with MAP_NOTICE_ind, then MAP_CLOSE_req (which is rejected with an X). From Receive_Open_Confirm, an 'OK' leads to Wait_for_cnf, and a 'Vr, Error' leads to a connector '1' and then to MAP_U_ABORT_req (which is also rejected with an X). A box on the right lists MAP_U_ABORT_ind, MAP_P_ABORT_ind, and MAP_CLOSE_ind.](ef45b00396c293be0b18d32b97118bf4_img.jpg) + +### Process Register\_CC\_Entry\_GLR + +22.11.1\_1(2) + +Figure 22.11/1: Handling of Register\_CC\_Entry at GLR + +Signals to/from the left are to/from the VLR +signals to/from the right are to/from the HLR +unless otherwise stated + +``` +sequenceDiagram + participant NULL + participant VLR + participant HLR + Note right of HLR: To HLR, Including + Note right of HLR: - Destination reference = subscriber's IMSI + Note right of HLR: - Originating reference = GLR number + Note right of HLR: Section 25.1 + + NULL->>VLR: + VLR->>HLR: MAP_REGISTER_CC_ENTRY_ind + VLR->>VLR: MAP_NOTICE_ind + VLR->>HLR: MAP_OPEN_req + Note right of HLR: To HLR, Including + Note right of HLR: - Destination reference = subscriber's IMSI + Note right of HLR: - Originating reference = GLR number + HLR-->>VLR: + VLR->>VLR: MAP_CLOSE_req + Note right of VLR: X + VLR->>HLR: MAP_REGISTER_CC_ENTRY_req + VLR->>HLR: MAP_DELIMITER_req + HLR-->>VLR: Receive_Open_Confirm + Note right of HLR: Section 25.1 + VLR->>VLR: Wait_for_cnf + VLR->>HLR: Vr, Error + Note right of HLR: 1 + VLR->>VLR: MAP_U_ABORT_req + Note right of VLR: X +``` + +MAP\_U\_ABORT\_ind +MAP\_P\_ABORT\_ind +MAP\_CLOSE\_ind + +Sequence diagram for Process Register\_CC\_Entry\_GLR. The process starts with NULL, followed by MAP\_REGISTER\_CC\_ENTRY\_ind. It then branches: one path goes to HLR with MAP\_OPEN\_req (including Destination reference = subscriber's IMSI and Originating reference = GLR number), followed by MAP\_REGISTER\_CC\_ENTRY\_req, MAP\_DELIMITER\_req, and Receive\_Open\_Confirm (Section 25.1). The other path goes to VLR with MAP\_NOTICE\_ind, then MAP\_CLOSE\_req (which is rejected with an X). From Receive\_Open\_Confirm, an 'OK' leads to Wait\_for\_cnf, and a 'Vr, Error' leads to a connector '1' and then to MAP\_U\_ABORT\_req (which is also rejected with an X). A box on the right lists MAP\_U\_ABORT\_ind, MAP\_P\_ABORT\_ind, and MAP\_CLOSE\_ind. + +Figure 22.11/1 (sheet 1 of 2): Process Register\_CC\_Entry\_GLR + +![Sequence diagram for Process Register_CC_Entry_GLR. The process starts with 'Wait_for_cnf'. It sends 'MAP_REGISTER_CC_ENTRY_cnf' to the left. A decision 'MAP_P_ERROR' follows. If 'yes', it goes to connector '1'. If 'no', it receives 'MAP_REGISTER_CC_ENTRY_rsp' from the left, then sends 'MAP_CLOSE_req' to the left, and ends. A loop exists from the 'yes' path: it sends 'MAP_U_ABORT_ind' and 'MAP_P_ABORT_ind' to the right, then 'MAP_NOTICE_ind' to the right, then 'MAP_CLOSE_req' to the right, then 'MAP_U_ABORT_req' to the right (ending with an X). A return path from the right sends 'MAP_NOTICE_ind', then a group of 'MAP_U_ABORT_ind', 'MAP_P_ABORT_ind', and 'MAP_CLOSE_ind', then 'MAP_CLOSE_req' to the left, then 'MAP_U_ABORT_req' to the left (ending with an X).](9cd6ff4a43174e4afe1cc5e4ea2fcae4_img.jpg) + +**Process Register\_CC\_Entry\_GLR** 22.11.1\_2(2) + +Figure 22.11/1: Handling of Register\_CC\_Entry at GLR + +Signals to/from the left are to/from the VLR +signals to/from the right are to/from the HLR +unless otherwise stated + +``` + +sequenceDiagram + participant GLR + participant VLR + participant HLR + + Note right of HLR: Signals to/from the left are to/from the VLR +signals to/from the right are to/from the HLR +unless otherwise stated + + Note left of VLR: Figure 22.11/1: Handling of Register_CC_Entry at GLR + + Note over GLR: Process Register_CC_Entry_GLR + + GLR->>VLR: Wait_for_cnf + VLR->>GLR: MAP_REGISTER_CC_ENTRY_cnf + Note right of GLR: MAP_P_ERROR + alt yes: Connector 1 + alt no: + GLR->>VLR: MAP_REGISTER_CC_ENTRY_rsp + VLR->>GLR: MAP_CLOSE_req + Note right of GLR: X + Note left of HLR: MAP_U_ABORT_ind +MAP_P_ABORT_ind + GLR->>HLR: MAP_NOTICE_ind + HLR->>GLR: MAP_CLOSE_req + Note right of GLR: MAP_U_ABORT_req + Note right of GLR: X + + Note left of HLR: MAP_NOTICE_ind + Note left of HLR: MAP_U_ABORT_ind +MAP_P_ABORT_ind +MAP_CLOSE_ind + HLR->>GLR: MAP_CLOSE_req + GLR->>HLR: MAP_U_ABORT_req + Note right of HLR: X + +``` + +Sequence diagram for Process Register\_CC\_Entry\_GLR. The process starts with 'Wait\_for\_cnf'. It sends 'MAP\_REGISTER\_CC\_ENTRY\_cnf' to the left. A decision 'MAP\_P\_ERROR' follows. If 'yes', it goes to connector '1'. If 'no', it receives 'MAP\_REGISTER\_CC\_ENTRY\_rsp' from the left, then sends 'MAP\_CLOSE\_req' to the left, and ends. A loop exists from the 'yes' path: it sends 'MAP\_U\_ABORT\_ind' and 'MAP\_P\_ABORT\_ind' to the right, then 'MAP\_NOTICE\_ind' to the right, then 'MAP\_CLOSE\_req' to the right, then 'MAP\_U\_ABORT\_req' to the right (ending with an X). A return path from the right sends 'MAP\_NOTICE\_ind', then a group of 'MAP\_U\_ABORT\_ind', 'MAP\_P\_ABORT\_ind', and 'MAP\_CLOSE\_ind', then 'MAP\_CLOSE\_req' to the left, then 'MAP\_U\_ABORT\_req' to the left (ending with an X). + +Figure 22.11/1 (sheet 2 of 2): Process Register\_CC\_Entry\_GLR + +## 22.12 Deactivation of a CCBS request + +### 22.12.1 General + +The Deactivation of a CCBS request procedure in the GLR is a fully transparent communication between the VLR and the HLR. + +### 22.12.2 Procedure in the GLR + +When receiving the MAP\_ERASE\_CC\_ENTRY indication from VLR, the MAP user in the GLR transfers the information to the HLR in the MAP\_ERASE\_CC\_ENTRY request without checking the contents of the service indication. + +When the GLR receives a MAP\_ERASE\_CC\_ENTRY confirmation from the HLR then it shall pass this to the VLR and closes the MAP provider service. + +The deactivation of a CCBS request procedure in the GLR is shown in figure 22.12/1. + +![Sequence diagram for Process Erase_CC_Entry_GLR](da85343976fdbb19f866d9ddbdad0eae_img.jpg) + +### Process Erase\_CC\_Entry\_GLR + +22.12.1\_1(2) + +Figure 22.12/1: Handling of Erase\_CC\_Entry at GLR + +Signals to/from the left are to/from the VLR +signals to/from the right are to/from the HLR +unless otherwise stated + +``` +sequenceDiagram + participant Start(( )) + participant NULL[NULL] + participant GLR + participant VLR + participant HLR + Note right of GLR: Including
- Destination reference = subscriber's IMSI
- Originating reference = GLR number + Note right of GLR: Section 25.1 + Note right of HLR: MAP_U_ABORT_ind
MAP_P_ABORT_ind
MAP_CLOSE_ind + + Start->>NULL + NULL-->>GLR + GLR->>VLR: MAP_ERASE_CC_ENTRY_ind + VLR->>GLR: MAP_OPEN_req + Note right of GLR + GLR->>VLR: MAP_ERASE_CC_ENTRY_req + VLR->>GLR: MAP_DELIMITER_req + GLR->>VLR: Receive_Open_Confirm + Note right of GLR + VLR-->>GLR: OK + VLR-->>GLR: Vr, Error + Note right of VLR: 1 + GLR->>Start: Wait_for_cnf + GLR->>VLR: MAP_U_ABORT_req + Note right of VLR: X +``` + +The sequence diagram illustrates the interaction for processing an Erase\_CC\_Entry at the GLR. It begins with an initial node leading to a 'NULL' state. From 'NULL', the process moves to the GLR entity. The GLR sends a 'MAP\_ERASE\_CC\_ENTRY\_ind' to the VLR. The VLR responds with a 'MAP\_OPEN\_req' to the GLR, which includes the destination reference (subscriber's IMSI) and the originating reference (GLR number). The GLR then sends a 'MAP\_ERASE\_CC\_ENTRY\_req' to the VLR, followed by a 'MAP\_DELIMITER\_req'. The VLR returns a 'Receive\_Open\_Confirm' to the GLR, with a note pointing to Section 25.1. The GLR then enters a 'Wait\_for\_cnf' state. The VLR can respond with either an 'OK' or a 'Vr, Error' (indicated by a circle with the number 1). In the event of an error, the GLR sends a 'MAP\_U\_ABORT\_req' to the VLR, which is marked with an 'X' (indicating it is not used or rejected). A note on the right indicates that signals to the left are from the VLR, signals to the right are from the HLR, and the HLR entity includes 'MAP\_U\_ABORT\_ind', 'MAP\_P\_ABORT\_ind', and 'MAP\_CLOSE\_ind'. + +Sequence diagram for Process Erase\_CC\_Entry\_GLR + +Figure 22.12/1 (sheet 1 of 2): Process Erase\_CC\_Entry\_GLR + +![Sequence diagram for Process Erase_CC_Entry_GLR](c21bad844b5cb6026c067a1f43ce67c3_img.jpg) + +**Process Erase\_CC\_Entry\_GLR** 22.12.1\_2(2) + +Figure 22.12/1: Handling of Erase\_CC\_Entry at GLR + +Signals to/from the left are to/from the VLR +signals to/from the right are to/from the HLR +unless otherwise stated + +``` +sequenceDiagram + participant GLR + participant VLR + participant HLR + + Note left of GLR: Wait_for_cnf + GLR->>VLR: MAP_REGISTER_CC_ENTRY_cnf + Note right of VLR: MAP_U_ABORT_ind, MAP_P_ABORT_ind + Note right of HLR: MAP_NOTICE_ind + GLR->>HLR: MAP_CLOSE_req + Note right of HLR: MAP_U_ABORT_req + Note right of HLR: X + GLR->>VLR: MAP_REGISTER_CC_ENTRY_rsp + Note right of VLR: MAP_NOTICE_ind + Note right of VLR: MAP_CLOSE_req + Note right of VLR: MAP_U_ABORT_req + Note right of VLR: X + GLR->>VLR: MAP_P_ERROR + Note right of VLR: 1 +``` + +The diagram illustrates the message exchange for processing an Erase\_CC\_Entry at the GLR. It begins with a 'Wait\_for\_cnf' state. The GLR sends a 'MAP\_REGISTER\_CC\_ENTRY\_cnf' message to the VLR. The VLR responds with 'MAP\_U\_ABORT\_ind' and 'MAP\_P\_ABORT\_ind' to the GLR. Simultaneously, the GLR sends a 'MAP\_CLOSE\_req' to the HLR, which receives a 'MAP\_U\_ABORT\_req' in response (marked with an 'X'). The GLR then sends a 'MAP\_REGISTER\_CC\_ENTRY\_rsp' to the VLR. The VLR responds with 'MAP\_NOTICE\_ind', 'MAP\_CLOSE\_req', and 'MAP\_U\_ABORT\_req' (marked with an 'X'). Finally, the GLR sends a 'MAP\_P\_ERROR' message to the VLR, which receives a '1' in response. + +Sequence diagram for Process Erase\_CC\_Entry\_GLR + +Figure 22.12/1 (sheet 2 of 2): Process Erase\_CC\_Entry\_GLR + +# 23 Short message service procedures + +## 23.1 General + +The short message service procedures are used to control both mobile originated and mobile terminated short message transfer. + +Four procedures exist for short message services (see 29.002) but only the following two procedures are involved in the GLR and the IM-MSC: + +- mobile terminated short message service transfer; +- short message alert procedure. + +## 23.2 The mobile terminated short message transfer procedure + +The mobile terminated short message transfer procedure is used for forwarding a short message or several short messages from a Service Centre to a mobile subscriber. This subclause includes the description of the procedures in the IM-MSC and the GLR. The procedures in the other existing entities are entirely the same as in the network without the GLR and are described in 29.002. + +### 23.2.1 Procedure in the Intermediate MSC + +When initiating the dialogue with the IM-MSC, the SMS Gateway MSC must provide the IMSI of the subscriber to whom the short message is directed. + +The IMSI can be included either in the Destination Reference of the MAP\_OPEN indication received from the SMS Gateway MSC or in the sm-RP-DA information field of the MAP\_MT\_FORWARD\_SHORT\_MESSAGE indication. + +When receiving a MAP\_OPEN indication primitive that is not associated with any MAP service indication primitive and if the dialogue is accepted, the MAP service-user in the IM-MSC issues a MAP\_DELIMITER request primitive in order to trigger the local MAP service-provider to confirm the dialogue. + +When receiving the first MAP\_MT\_FORWARD\_SHORT\_MESSAGE indication from the gateway MSC, the IM-MSC retrieves the E.164 Number of the servicing MSC from the GLR if the MAP service primitive is accepted. + +The MAP\_MT\_FORWARD\_SHORT\_MESSAGE indication primitive is checked by the macro "Check\_Indication". If the received MAP service primitive contains errors, the service is aborted and an unexpected data value error or data missing error is returned to the GMSC. + +The subscriber identity information that may be included in the MAP\_OPEN indication primitive and in the MAP service indication primitive is checked by the macro "Check\_Subscr\_Identity\_For\_MT\_SMS" as follows. + +If a Destination Reference has been received in the MAP\_OPEN indication, an LMSI must be present in the sm-RP-DA information field of the MAP\_MT\_FORWARD\_SHORT\_MESSAGE indication. The LMSI shall be key information for retrieving the MSC Number in the GLR. + +Otherwise, if the IMSI is included in the sm-RP-DA information field of the MAP\_MT\_FORWARD\_SHORT\_MESSAGE indication, it is used to retrieve the MSC Number in the GLR. + +If: + +a Destination Reference has been received in the IM-MSC and the sm-RP-DA information field of the MAP\_MT\_FORWARD\_SHORT\_MESSAGE indication does not include an LMSI, or + +no Destination Reference has been received and the sm-RP-DA information field does not cover an IMSI; + +the service is aborted in the IM-MSC and the error "Unexpected Data Value" is returned to the SMS GMSC. + +The interaction between the IM- MSC and the GLR for the MSC Number retrieval is described in 3GPP TS 23.119 GLR-stage2. + +If the IM- MSC is successfully retrieves the MSC Number it initiates the forward short message procedure to the servicing MSC. The presence of the Destination Reference in the MAP\_OPEN request and the LMSI or IMSI in the first MAP\_MT\_FORWARD\_SHORT\_MESSAGE request follows the message received from the GMSC. The More Messages To Send flag is set to TRUE or FALSE depending on the information received from the GMSC. + +If the grouping of MAP\_OPEN request and MAP\_MT\_FORWARD\_SHORT\_MESSAGE request together would need segmenting, these primitives must not be grouped together. The MAP\_OPEN request primitive is sent first without any associated MAP service request primitive and the dialogue confirmation must be received before the MAP\_MT\_FORWARD\_SHORT\_MESSAGE request is sent. + +As a response to the procedure, the IM- MSC will receive the MAP\_MT\_FORWARD\_SHORT\_MESSAGE confirmation indicating: + +- a successful forwarding of the short message. This indication is passed to the GMSC; +- unsuccessful forwarding of the short message. This indication is passed to the GMSC. + +The IM- MSC informs the delivery failure to the GLR, if an absent subscriber\_SM, an unidentified subscriber or SM delivery failure with error cause MS memory capacity exceeded indication is received from the servicing MSC. That enables the GLR set the MNRF. The interaction between the IM- MSC and the GLR regarding the procedure is described in 3GPP TS 23.119 GLR-stage2. + +Unexpected data value, system failure errors and other errors are simply passed to the GMSC. + +If the More Messages To Send flag was TRUE in the MAP\_MT\_FORWARD\_SHORT\_MESSAGE request and the previous short message transfer succeeded, then the IM- MSC awaits the next short message. + +When receiving the next short message from the GMSC, the IM- MSC sets the More Messages To Send flag according to the information received and starts the service MAP\_MT\_FORWARD\_SHORT\_MESSAGE again. + +If the More Messages To Send flag was FALSE or the service MAP\_MT\_FORWARD\_SHORT\_MESSAGE ends unsuccessfully, the transaction to the gateway MSC is terminated. + +The mobile terminated short message transfer procedure in the IM- MSC is shown in figure 23.2/1 and 23.2/2. + +![Flowchart for Process MT_SM_Transfer_IMMSC. It starts with an oval, followed by a NULL state, then 'Receive_Open_ind' (linked to Section 25.1). A decision 'Dest_Ref_received' follows: 'OK' leads to 'Store_Destination_Reference' then 'WAIT_FOR_SERVICE_PRIMITIVE'; 'no' leads to NULL; 'Error' leads to NULL. From 'WAIT_FOR_SERVICE_PRIMITIVE', four paths emerge: 1) 'MAP_DELIMITER_ind' -> 'MAP_DELIMITER_req' -> 'WAIT_FOR_SERVICE_PRIMITIVE'; 2) 'MAP_MT_FORWARD_SHORT_MESSAGE_ind' -> 'Check Indication' (linked to Section 25.2) -> 'MT_SM_IM-MSC' (linked to Figure 23.2/2) -> 'More_msg_to_sent' decision; 3) A group of 'MAP_U_ABORT_ind', 'MAP_P_ABORT_ind', and 'MAP_CLOSE_ind' -> NULL; 4) 'MAP_NOTICE_ind' -> 'MAP_CLOSE_ind' -> NULL. From 'More_msg_to_sent': 'yes' leads to a box with 'MAP_MT_FORWARD_SHORT_MESSAGE_rsp' and 'MAP_DELIMITER_req' -> 'WAIT_FOR_MORE_MESSAGES'; 'no' leads to a box with 'MAP_MT_FORWARD_SHORT_MESSAGE_rsp' and 'MAP_CLOSE_req' -> NULL; 'error' leads to NULL.](3ec35c497a0765a1a885c85f214b1bef_img.jpg) + +### Process MT\_SM\_Transfer\_IMMSC + +23.2.1\_1(3) + +Figure 23.2/1: The mobile terminated short message service in the IM-MSC + +Signals to/from the left are to/from the SMS-GMSC; signals to/from the right are to/from the MSC + +``` +graph TD; Start([ ]) --> NULL1(NULL); NULL1 --> Receive_Open_ind[Receive_Open_ind]; Receive_Open_ind --- Section_25_1[Section 25.1]; Receive_Open_ind -- OK --> Dest_Ref_received{Dest_Ref_received}; Dest_Ref_received -- no --> NULL2(NULL); Dest_Ref_received -- OK --> Store_Destination_Reference[Store_Destination_Reference]; Store_Destination_Reference --> WAIT_FOR_SERVICE_PRIMITIVE1(WAIT_FOR_SERVICE_PRIMITIVE); Dest_Ref_received -- Error --> NULL2; WAIT_FOR_SERVICE_PRIMITIVE1 --> MAP_DELIMITER_ind1[MAP_DELIMITER_ind]; WAIT_FOR_SERVICE_PRIMITIVE1 --> MAP_MT_FORWARD_SHORT_MESSAGE_ind[MAP_MT_FORWARD_SHORT_MESSAGE_ind]; WAIT_FOR_SERVICE_PRIMITIVE1 --> MAP_U_ABORT_ind[MAP_U_ABORT_ind]; WAIT_FOR_SERVICE_PRIMITIVE1 --> MAP_P_ABORT_ind[MAP_P_ABORT_ind]; WAIT_FOR_SERVICE_PRIMITIVE1 --> MAP_CLOSE_ind1[MAP_CLOSE_ind]; WAIT_FOR_SERVICE_PRIMITIVE1 --> MAP_NOTICE_ind[MAP_NOTICE_ind]; MAP_DELIMITER_ind1 --> MAP_DELIMITER_req[MAP_DELIMITER_req]; MAP_DELIMITER_req --> WAIT_FOR_SERVICE_PRIMITIVE2(WAIT_FOR_SERVICE_PRIMITIVE); MAP_MT_FORWARD_SHORT_MESSAGE_ind --> Check_Indication[Check Indication]; Check_Indication --- Section_25_2[Section 25.2]; Check_Indication -- ok --> MT_SM_IM-MSC[MT_SM_IM-MSC]; MT_SM_IM-MSC --- Figure_23_2_2[Figure 23.2/2]; MT_SM_IM-MSC -- error --> NULL3(NULL); MT_SM_IM-MSC -- ok --> More_msg_to_sent{More_msg_to_sent}; More_msg_to_sent -- yes --> MT_FORWARD_SHORT_MESSAGE_rsp1[MAP_MT_FORWARD_SHORT_MESSAGE_rsp]; More_msg_to_sent -- yes --> MAP_DELIMITER_req2[MAP_DELIMITER_req]; MT_FORWARD_SHORT_MESSAGE_rsp1 --> WAIT_FOR_MORE_MESSAGES(WAIT_FOR_MORE_MESSAGES); More_msg_to_sent -- no --> MT_FORWARD_SHORT_MESSAGE_rsp2[MAP_MT_FORWARD_SHORT_MESSAGE_rsp]; More_msg_to_sent -- no --> MAP_CLOSE_req[MAP_CLOSE_req]; MT_FORWARD_SHORT_MESSAGE_rsp2 --> NULL4(NULL); MAP_U_ABORT_ind --> NULL3; MAP_P_ABORT_ind --> NULL3; MAP_CLOSE_ind1 --> NULL3; MAP_NOTICE_ind --> MAP_CLOSE_ind2[MAP_CLOSE_ind]; MAP_CLOSE_ind2 --> NULL5(NULL); +``` + +Flowchart for Process MT\_SM\_Transfer\_IMMSC. It starts with an oval, followed by a NULL state, then 'Receive\_Open\_ind' (linked to Section 25.1). A decision 'Dest\_Ref\_received' follows: 'OK' leads to 'Store\_Destination\_Reference' then 'WAIT\_FOR\_SERVICE\_PRIMITIVE'; 'no' leads to NULL; 'Error' leads to NULL. From 'WAIT\_FOR\_SERVICE\_PRIMITIVE', four paths emerge: 1) 'MAP\_DELIMITER\_ind' -> 'MAP\_DELIMITER\_req' -> 'WAIT\_FOR\_SERVICE\_PRIMITIVE'; 2) 'MAP\_MT\_FORWARD\_SHORT\_MESSAGE\_ind' -> 'Check Indication' (linked to Section 25.2) -> 'MT\_SM\_IM-MSC' (linked to Figure 23.2/2) -> 'More\_msg\_to\_sent' decision; 3) A group of 'MAP\_U\_ABORT\_ind', 'MAP\_P\_ABORT\_ind', and 'MAP\_CLOSE\_ind' -> NULL; 4) 'MAP\_NOTICE\_ind' -> 'MAP\_CLOSE\_ind' -> NULL. From 'More\_msg\_to\_sent': 'yes' leads to a box with 'MAP\_MT\_FORWARD\_SHORT\_MESSAGE\_rsp' and 'MAP\_DELIMITER\_req' -> 'WAIT\_FOR\_MORE\_MESSAGES'; 'no' leads to a box with 'MAP\_MT\_FORWARD\_SHORT\_MESSAGE\_rsp' and 'MAP\_CLOSE\_req' -> NULL; 'error' leads to NULL. + +Figure 23.2/1 (sheet1 of 3): Procedure\_MT\_SM\_Transfer\_IM-MSC + +#### Process MT\_SM\_Transfer\_IMMSC + +23.2.1\_2(3) + +Figure 23.2/1: The mobile terminated short message service in the IM-MSC + +![Flowchart for Process MT_SM_Transfer_IMMSC. The process starts with 'WAIT_FOR_MORE_MESSAGES', followed by 'MAP_MT_FORWARD_SHORT_MESSAGE_ind'. It then goes to 'Check Indication' (Section 25.2). If 'ok', it sends 'MAP_MT_FORWARD_SHORT_MESSAGE_req' and 'MAP_DELIMITER_req', then 'WAIT_FOR_MT_SMS_CONFIRM', receives 'MAP_MT_FORWARD_SHORT_MESSAGE_cnf', and goes to 'Check Confirmation' (Section 25.2). If 'ok' from 'Check Confirmation', it checks 'More msg to_sent'. If 'yes', it loops back to 'WAIT_FOR_MORE_MESSAGES'. If 'no', it sends 'MAP_MT_FORWARD_SHORT_MESSAGE_rsp' and 'MAP_DELIMITER_req' to 'WAIT_FOR_MORE_MESSAGES'. If 'error' from 'Check Indication', it checks 'Absent Subscriber?'. If 'yes', it sends 'Inform SM Delivery Failure' to 'GLR Application Process in TS23.119'. If 'no', it sends 'MAP_MT_FORWARD_SHORT_MESSAGE_rsp' and 'MAP_CLOSE_req' to 'NULL'. Other error paths (Provider error, Data error, User error) lead to the 'MAP_MT_FORWARD_SHORT_MESSAGE_rsp' and 'MAP_DELIMITER_req' path.](6bc05e56e8453678a84fa6bdba3fd903_img.jpg) + +``` +graph TD; Start([WAIT_FOR_MORE_MESSAGES]) --> Ind{MAP_MT_FORWARD_SHORT_MESSAGE_ind}; Ind --> CheckInd[Check Indication]; CheckInd --- Section25_2_1[Section 25.2]; CheckInd -- ok --> Req[MAP_MT_FORWARD_SHORT_MESSAGE_req
MAP_DELIMITER_req]; Req --> WaitConfirm([WAIT_FOR_MT_SMS_CONFIRM]); WaitConfirm --> Cnf{MAP_MT_FORWARD_SHORT_MESSAGE_cnf}; Cnf --> CheckConf[Check Confirmation]; CheckConf --- Section25_2_2[Section 25.2]; CheckConf -- ok --> MoreMsg{More msg to_sent}; MoreMsg -- yes --> Start; MoreMsg -- no --> Rsp1[MAP_MT_FORWARD_SHORT_MESSAGE_rsp
MAP_DELIMITER_req]; Rsp1 --> WaitMore([WAIT_FOR_MORE_MESSAGES]); CheckInd -- error --> Absent{Absent Subscriber?}; Absent -- yes --> Failure[Inform SM Delivery Failure]; Failure --- GLR[GLR Application Process in TS23.119]; Absent -- no --> Rsp2[MAP_MT_FORWARD_SHORT_MESSAGE_rsp
MAP_CLOSE_req]; Rsp2 --> NULL([NULL]); CheckConf -- "Provider error
Data error
User error" --> Rsp1 +``` + +Flowchart for Process MT\_SM\_Transfer\_IMMSC. The process starts with 'WAIT\_FOR\_MORE\_MESSAGES', followed by 'MAP\_MT\_FORWARD\_SHORT\_MESSAGE\_ind'. It then goes to 'Check Indication' (Section 25.2). If 'ok', it sends 'MAP\_MT\_FORWARD\_SHORT\_MESSAGE\_req' and 'MAP\_DELIMITER\_req', then 'WAIT\_FOR\_MT\_SMS\_CONFIRM', receives 'MAP\_MT\_FORWARD\_SHORT\_MESSAGE\_cnf', and goes to 'Check Confirmation' (Section 25.2). If 'ok' from 'Check Confirmation', it checks 'More msg to\_sent'. If 'yes', it loops back to 'WAIT\_FOR\_MORE\_MESSAGES'. If 'no', it sends 'MAP\_MT\_FORWARD\_SHORT\_MESSAGE\_rsp' and 'MAP\_DELIMITER\_req' to 'WAIT\_FOR\_MORE\_MESSAGES'. If 'error' from 'Check Indication', it checks 'Absent Subscriber?'. If 'yes', it sends 'Inform SM Delivery Failure' to 'GLR Application Process in TS23.119'. If 'no', it sends 'MAP\_MT\_FORWARD\_SHORT\_MESSAGE\_rsp' and 'MAP\_CLOSE\_req' to 'NULL'. Other error paths (Provider error, Data error, User error) lead to the 'MAP\_MT\_FORWARD\_SHORT\_MESSAGE\_rsp' and 'MAP\_DELIMITER\_req' path. + +Figure 23.2/1 (sheet 2 of 3): Procedure MT\_SM\_Transfer\_IM-MSC + +#### Process MT\_SM\_Transfer\_IMMSC + +23.2.1\_3(3) + +Figure 23.2/1: The mobile terminated short message service in the IM-MSC + +![Sequence diagram for Process MT_SM_Transfer_IMMSC showing interactions between IM-MSC, SMS-GMSC, and VMSC.](85680f3dcbe15424dd54fa3fd9e1c90d_img.jpg) + +The sequence diagram illustrates the process of mobile terminated short message service in the IM-MSC. It begins with an initial state labeled 'WAIT\_FOR\_MORE\_MESSAGES' and 'WAIT\_FOR\_MT\_SMS\_CONFIRM'. The process then enters a loop. First, it checks for incoming messages from the SMS-GMSC. If 'MAP\_U\_ABORT\_ind' or 'MAP\_P\_ABORT\_ind' is received, it sends a 'MAP\_U\_ABORT\_req' to the VMSC and ends. If 'MAP\_NOTICE\_ind' is received from the SMS-GMSC, it sends a 'MAP\_CLOSE\_req' to the SMS-GMSC. After this, it checks for messages from the VMSC. If 'MAP\_NOTICE\_ind' is received from the VMSC, it sends a 'MAP\_CLOSE\_req' to the VMSC. If 'MAP\_U\_ABORT\_ind', 'MAP\_P\_ABORT\_ind', or 'MAP\_CLOSE\_ind' is received from the VMSC, it sends a 'MAP\_U\_ABORT\_req' to the SMS-GMSC and ends. The diagram uses standard notation: rectangles for states, diamonds for decision points, and arrows for messages. A circle with an 'X' indicates the end of a process path. + +Sequence diagram for Process MT\_SM\_Transfer\_IMMSC showing interactions between IM-MSC, SMS-GMSC, and VMSC. + +Figure 23.2/1 (sheet 3 of 3): Procedure MT\_SM\_Transfer\_IM-MSC + +![Flowchart for Macro MT_SM_IMMSC. The process starts with a connector, followed by 'Obtain MSC Number' (to GLR Application Process in TS23.119), 'WAIT_FOR_RESPONSE', and 'RESPONSE' (from GLR Application Process in TS23.119). A decision 'MSC Number Obtained?' follows. If 'no', it goes to 'User Error = Unidentified User' and then 'ERR OR'. If 'yes', it goes to 'Message segmenting needed?'. If 'no', it sends 'MAP_OPEN_req', 'MAP_MT_FORWARD_SHORT_MESSAGE_req', and 'MAP_DELIMITER_req', then 'Receive_Open_Cnf', then 'WAIT_FOR_MT_SMS_CONFIRM'. If 'yes', it sends 'MAP_OPEN_req', 'MAP_DELIMITER_req', then 'Receive_Open_Cnf', then another decision. From this second decision, if 'ok', it sends 'MAP_MT_FORWARD_SHORT_MESSAGE_req' and 'MAP_DELIMITER_req', then 'WAIT_FOR_MT_SMS_CONFIRM'. If 'error', it goes to 'Error = System Failure' and then 'ERR OR'. Both 'WAIT_FOR_MT_SMS_CONFIRM' paths lead to a merge point, then 'MAP_MT_FORWARD_SHORT_MESSAGE_Cnf', and finally connector '1 page2'.](684f7a2cd4ba3346bcaec1f7336f6aa3_img.jpg) + +**Macrodefinition MT\_SM\_IMMSC** **23.2.2\_1(2)** + +Figure 23.2/2: Macro which transfer short message PDUs to VMSC in the IM-MSC + +Signals to/from the right are to/from the MSC + +``` + +graph TD + Start([ ]) --> Obtain[Obtain MSC Number] + Obtain --> GLR[to GLR Application Process in TS23.119] + Obtain --> Wait1(WAIT_FOR_RESPONSE) + Wait1 --> Response[RESPONSE] + Response --> FromGLR[from GLR Application Process in TS23.119] + Response --> Obtained{MSC Number Obtained?} + Obtained -- no --> UserError[User Error = Unidentified User] + UserError --> ERR1((ERR OR)) + Obtained -- yes --> Segmenting{Message segmenting needed?} + Segmenting -- no --> OpenReq1[MAP_OPEN_req +MAP_MT_FORWARD_SHORT_MESSAGE_req +MAP_DELIMITER_req] + OpenReq1 --> ReceiveOpenCnf1[Receive_Open_Cnf] + Segmenting -- yes --> OpenReq2[MAP_OPEN_req +MAP_DELIMITER_req] + OpenReq2 --> ReceiveOpenCnf2[Receive_Open_Cnf] + ReceiveOpenCnf1 -- ok --> Wait2(WAIT_FOR_MT_SMS_CONFIRM) + ReceiveOpenCnf1 -- error --> SystemFailure[Error = System Failure] + SystemFailure --> ERR2((ERR OR)) + ReceiveOpenCnf2 -- ok --> OpenReq3[MAP_MT_FORWARD_SHORT_MESSAGE_req +MAP_DELIMITER_req] + OpenReq3 --> Wait3(WAIT_FOR_MT_SMS_CONFIRM) + Wait2 --> Merge(( )) + Wait3 --> Merge + Merge --> Cnf[MAP_MT_FORWARD_SHORT_MESSAGE_Cnf] + Cnf --> Page2((1 page2)) + +``` + +Flowchart for Macro MT\_SM\_IMMSC. The process starts with a connector, followed by 'Obtain MSC Number' (to GLR Application Process in TS23.119), 'WAIT\_FOR\_RESPONSE', and 'RESPONSE' (from GLR Application Process in TS23.119). A decision 'MSC Number Obtained?' follows. If 'no', it goes to 'User Error = Unidentified User' and then 'ERR OR'. If 'yes', it goes to 'Message segmenting needed?'. If 'no', it sends 'MAP\_OPEN\_req', 'MAP\_MT\_FORWARD\_SHORT\_MESSAGE\_req', and 'MAP\_DELIMITER\_req', then 'Receive\_Open\_Cnf', then 'WAIT\_FOR\_MT\_SMS\_CONFIRM'. If 'yes', it sends 'MAP\_OPEN\_req', 'MAP\_DELIMITER\_req', then 'Receive\_Open\_Cnf', then another decision. From this second decision, if 'ok', it sends 'MAP\_MT\_FORWARD\_SHORT\_MESSAGE\_req' and 'MAP\_DELIMITER\_req', then 'WAIT\_FOR\_MT\_SMS\_CONFIRM'. If 'error', it goes to 'Error = System Failure' and then 'ERR OR'. Both 'WAIT\_FOR\_MT\_SMS\_CONFIRM' paths lead to a merge point, then 'MAP\_MT\_FORWARD\_SHORT\_MESSAGE\_Cnf', and finally connector '1 page2'. + +Figure 23.2/2 (sheet1 of 2): Macro MT\_SM\_IM-MSC + +![Flowchart for Macro MT_SM_IMMSC. It starts at connector '1 page1', goes to 'Check Confirmation' (linked to Section 25.2). From there, three paths emerge: 'ok' leads to 'OK' connector; 'User Error' leads to 'Absent Subscriber?' decision; 'Provider Error Data Error' leads to 'ERR OR' connector. From 'Absent Subscriber?', 'yes' leads to 'Inform SM Delivery Failure' (linked to 'to GLR Application Process in TS 23.119') which then leads to 'ERR OR'; 'no' leads directly to 'ERR OR'.](921f8fa0f7ce2c9956f20d33162c13a2_img.jpg) + +**Macrodefinition MT\_SM\_IMMSC** **23.2.2\_2(2)** + +Figure 23.2/2: Macro which transfer short message PDUs to VMSC in the IM-MSC + +``` +graph TD; Start((1 page1)) --> Check[Check Confirmation]; Check --- Section[Section 25.2]; Check -- ok --> OK((OK)); Check -- User Error --> Absent{Absent Subscriber?}; Check -- "Provider Error Data Error" --> ERR[ERR OR]; Absent -- yes --> Inform[Inform SM Delivery Failure]; Inform --- GLR[to GLR Application Process in TS 23.119]; Inform --> ERR; Absent -- no --> ERR; +``` + +Flowchart for Macro MT\_SM\_IMMSC. It starts at connector '1 page1', goes to 'Check Confirmation' (linked to Section 25.2). From there, three paths emerge: 'ok' leads to 'OK' connector; 'User Error' leads to 'Absent Subscriber?' decision; 'Provider Error Data Error' leads to 'ERR OR' connector. From 'Absent Subscriber?', 'yes' leads to 'Inform SM Delivery Failure' (linked to 'to GLR Application Process in TS 23.119') which then leads to 'ERR OR'; 'no' leads directly to 'ERR OR'. + +**Figure 23.2/2 (sheet2 of 2): Macro MT\_SM\_IM- MSC** + +### 23.2.2 Procedure in the GLR + +When initiating the dialogue with the GLR, the SMS Gateway MSC must provide the IMSI of the subscriber to whom the short message is directed. + +The IMSI is included in the sm-RP-DA information field of the MAP\_MT\_FORWARD\_SHORT\_MESSAGE indication. + +When receiving a MAP\_OPEN indication primitive that is not associated with any MAP service indication primitive and if the dialogue is accepted, the MAP service-user in the GLR issues a MAP\_DELIMITER request primitive in order to trigger the local MAP service-provider to confirm the dialogue. + +When receiving the first MAP\_MT\_FORWARD\_SHORT\_MESSAGE indication from the gateway MSC, the GLR performs some subscriber data checks, if the MAP service primitive is accepted. + +The MAP\_MT\_FORWARD\_SHORT\_MESSAGE indication primitive is checked by the macro "Check\_Indication". If the received MAP service primitive contains errors, the service is aborted and an unexpected data value error or data missing error is returned to the GMSC. + +The subscriber identity information that is included in the MAP service indication primitive is checked by the macro "Check\_Subscr\_Identity\_For\_MT\_SMS" as follows: + +If the IMSI is included in the sm-RP-DA information field of the MAP\_MT\_FORWARD\_SHORT\_MESSAGE indication, the MAP\_OPEN indication received from the gateway MSC shall not include a Destination Reference. + +If no Destination Reference has been received and the sm-RP-DA information field does not cover an IMSI the service is aborted in the GLR and the error "Unexpected Data Value" is returned to the GMSC. + +The following outcomes from the subscriber data checks can occur in GLR: + +- if the mobile subscriber is unknown, the unidentified subscriber error is forwarded to the GMSC; +- if the "Confirmed by HLR" indicator is set to "Not Confirmed", the unidentified subscriber error is forwarded to the GMSC. + +If the mobile subscriber is known and "Confirmed by HLR" indicator is set to "Confirmed", the GLR shall successfully retrieves the SGSN Number. + +If the GLR is successfully retrieves the SGSN Number it initiates the forward short message procedure to the SGSN. The IMSI is included in the sm-RP-DA information field of the MAP\_MT\_FORWARD\_SHORT\_MESSAGE request. More Messages To Send flag is set to TRUE or FALSE depending on the information received from the GMSC. + +If the grouping of MAP\_OPEN request and MAP\_MT\_FORWARD\_SHORT\_MESSAGE request together would need segmenting, these primitives must not be grouped together. The MAP\_OPEN request primitive is sent first without any associated MAP service request primitive and the dialogue confirmation must be received before the MAP\_MT\_FORWARD\_SHORT\_MESSAGE request is sent. + +As a response to the procedure, the GLR will receive the MAP\_MT\_FORWARD\_SHORT\_MESSAGE confirmation indicating: + +- a successful forwarding of the short message. This indication is passed to the GMSC; +- unsuccessful forwarding of the short message. This indication is passed to the GMSC. + +The GLR sets MNRG, if an absent subscriber\_SM (except for the case that absent subscriber reason is PurgedMS), an unidentified subscriber or SM delivery failure with error cause MS memory capacity exceeded indication is received from the SGSN. + +If the GLR receives an absent subscriber\_SM and absent subscriber reason is PurgedMS, the GLR deletes the subscriber data for the user. + +Unexpected data value, system failure errors and other errors are simply passed to the GMSC. + +If the More Messages To Send flag was TRUE in the MAP\_MT\_FORWARD\_SHORT\_MESSAGE request and the previous short message transfer succeeded, then the GLR awaits the next short message. + +When receiving the next short message from the GMSC, the GLR sets the More Messages To Send flag according to the information received and starts the service MAP\_MT\_FORWARD\_SHORT\_MESSAGE again. + +If the More Messages To Send flag was FALSE or the service MAP\_MT\_FORWARD\_SHORT\_MESSAGE ends unsuccessfully, the transaction to the gateway MSC is terminated. + +The mobile terminated short message transfer procedure in the GLR is shown in figure 23.2/3 and 23.2/4. + +![Flowchart for Process MT_SM_Transfer_GLR. The process starts with an oval connector, leading to a 'NULL' state. It then enters a 'Receive_Open_ind' block (referencing Section 25.1). From here, an 'Error' path leads to another 'NULL' state. An 'OK' path leads to a 'Dest_Ref_received' decision. If 'no', it goes to 'NULL'. If 'yes', it proceeds to 'Store_Destination_Reference' and then to a 'WAIT_FOR_SERVICE_PRIMITIVE' block. From this block, four paths emerge: 1) 'MAP_DELIMITER_ind' leads to 'MAP_DELIMITER_req' and then to 'WAIT_FOR_SERVICE_PRIMITIVE'. 2) 'MAP_MT_FORWARD_SHORT_MESSAGE_ind' leads to 'Check_Indication' (referencing Section 25.2). From 'Check_Indication', an 'ok' path leads to 'MT_SM_GLR' (referencing Figure 23.2/4), and an 'error' path leads to 'NULL'. From 'MT_SM_GLR', an 'ok' path leads to 'More_msg_to_sent' decision. If 'yes', it goes to a connector leading to 'MAP_MT_FORWARD_SHORT_MESSAGE_rsp' and 'MAP_DELIMITER_req', which then leads to 'WAIT_FOR_MORE_MESSAGES'. If 'no', it leads to 'NULL'. 3) A third path from the initial split leads to a connector for 'MAP_U_ABORT_ind', 'MAP_P_ABORT_ind', and 'MAP_CLOSE_ind', which then leads to 'NULL'. 4) 'MAP_NOTICE_ind' leads to 'MAP_CLOSE_ind', which then leads to 'NULL'.](245166735676c675f98f535bc4c6f0a1_img.jpg) + +### Process MT\_SM\_Transfer\_GLR + +23.2.3\_1(3) + +Figure 23.2/3: The mobile terminated short message service in the GLR + +Signals to/from the left are to/from the SMS-GMSC; +signals to/from the right are to/from the SGSN + +``` +graph TD; Start([ ]) --> NULL1(NULL); NULL1 --> Receive_Open_ind[Receive_Open_ind]; Receive_Open_ind --- Section_25_1[Section 25.1]; Receive_Open_ind -- Error --> NULL2(NULL); Receive_Open_ind -- OK --> Dest_Ref_received{Dest_Ref_received}; Dest_Ref_received -- no --> NULL3(NULL); Dest_Ref_received -- yes --> Store_Destination_Reference[Store_Destination_Reference]; Store_Destination_Reference --> WAIT_FOR_SERVICE_PRIMITIVE1(WAIT_FOR_SERVICE_PRIMITIVE); WAIT_FOR_SERVICE_PRIMITIVE1 --> MAP_DELIMITER_ind1[MAP_DELIMITER_ind]; WAIT_FOR_SERVICE_PRIMITIVE1 --> MAP_MT_FORWARD_SHORT_MESSAGE_ind[MAP_MT_FORWARD_SHORT_MESSAGE_ind]; WAIT_FOR_SERVICE_PRIMITIVE1 --> MAP_U_ABORT_ind[MAP_U_ABORT_ind]; WAIT_FOR_SERVICE_PRIMITIVE1 --> MAP_NOTICE_ind[MAP_NOTICE_ind]; MAP_DELIMITER_ind1 --> MAP_DELIMITER_req1[MAP_DELIMITER_req]; MAP_DELIMITER_req1 --> WAIT_FOR_SERVICE_PRIMITIVE2(WAIT_FOR_SERVICE_PRIMITIVE); MAP_MT_FORWARD_SHORT_MESSAGE_ind --> Check_Indication[Check_Indication]; Check_Indication --- Section_25_2[Section 25.2]; Check_Indication -- ok --> MT_SM_GLR[MT_SM_GLR]; Check_Indication -- error --> NULL4(NULL); MT_SM_GLR --- Figure_23_2_4[Figure 23.2/4]; MT_SM_GLR -- ok --> More_msg_to_sent{More_msg_to_sent}; More_msg_to_sent -- yes --> Connector1{{ }}; More_msg_to_sent -- no --> NULL5(NULL); Connector1 --> MAP_MT_FORWARD_SHORT_MESSAGE_rsp1[MAP_MT_FORWARD_SHORT_MESSAGE_rsp]; Connector1 --> MAP_DELIMITER_req2[MAP_DELIMITER_req]; MAP_MT_FORWARD_SHORT_MESSAGE_rsp1 --> WAIT_FOR_MORE_MESSAGES(WAIT_FOR_MORE_MESSAGES); MAP_DELIMITER_req2 --> WAIT_FOR_MORE_MESSAGES; MAP_U_ABORT_ind --> MAP_U_ABORT_ind_group[MAP_U_ABORT_ind]; MAP_P_ABORT_ind_group[MAP_P_ABORT_ind]; MAP_CLOSE_ind_group[MAP_CLOSE_ind]; MAP_U_ABORT_ind_group --> NULL6(NULL); MAP_P_ABORT_ind_group --> NULL6; MAP_CLOSE_ind_group --> NULL6; MAP_NOTICE_ind --> MAP_CLOSE_ind2[MAP_CLOSE_ind]; MAP_CLOSE_ind2 --> NULL7(NULL); +``` + +Flowchart for Process MT\_SM\_Transfer\_GLR. The process starts with an oval connector, leading to a 'NULL' state. It then enters a 'Receive\_Open\_ind' block (referencing Section 25.1). From here, an 'Error' path leads to another 'NULL' state. An 'OK' path leads to a 'Dest\_Ref\_received' decision. If 'no', it goes to 'NULL'. If 'yes', it proceeds to 'Store\_Destination\_Reference' and then to a 'WAIT\_FOR\_SERVICE\_PRIMITIVE' block. From this block, four paths emerge: 1) 'MAP\_DELIMITER\_ind' leads to 'MAP\_DELIMITER\_req' and then to 'WAIT\_FOR\_SERVICE\_PRIMITIVE'. 2) 'MAP\_MT\_FORWARD\_SHORT\_MESSAGE\_ind' leads to 'Check\_Indication' (referencing Section 25.2). From 'Check\_Indication', an 'ok' path leads to 'MT\_SM\_GLR' (referencing Figure 23.2/4), and an 'error' path leads to 'NULL'. From 'MT\_SM\_GLR', an 'ok' path leads to 'More\_msg\_to\_sent' decision. If 'yes', it goes to a connector leading to 'MAP\_MT\_FORWARD\_SHORT\_MESSAGE\_rsp' and 'MAP\_DELIMITER\_req', which then leads to 'WAIT\_FOR\_MORE\_MESSAGES'. If 'no', it leads to 'NULL'. 3) A third path from the initial split leads to a connector for 'MAP\_U\_ABORT\_ind', 'MAP\_P\_ABORT\_ind', and 'MAP\_CLOSE\_ind', which then leads to 'NULL'. 4) 'MAP\_NOTICE\_ind' leads to 'MAP\_CLOSE\_ind', which then leads to 'NULL'. + +Figure 23.2/3 (sheet 1 of 3): Procedure MT\_SM\_Transfer\_GLR + +![Flowchart for Process MT_SM_Transfer_GLR. The process starts with 'WAIT_FOR_MORE_MESSAGES', followed by 'MAP_MT_FORWARD_SHORT_MESSAGE_ind'. It then checks the indication (Section 25.2). If 'ok', it sends 'MAP_MT_FORWARD_SHORT_MESSAGE_req' and 'MAP_DELIMITER_req', then waits for 'MT_SMS_CONFIRM'. Upon receiving 'MAP_MT_FORWARD_SHORT_MESSAGE_cnf', it checks the confirmation (Section 25.2). If 'ok', it checks if the subscriber is absent. If 'yes', it sets MNRG and checks 'Absent SubscriberSM_In_GLR' (See TS 23.119). If 'no' (either from 'Absent Subscriber?' or 'Check Confirmation'), it sends 'MAP_MT_FORWARD_SHORT_MESSAGE_rsp' and 'MAP_CLOSE_req', leading to 'NULL'. If 'ok' from 'Check Confirmation', it checks 'More_msg_to_sent'. If 'yes', it loops back to 'WAIT_FOR_MORE_MESSAGES'. If 'no', it sends 'MAP_MT_FORWARD_SHORT_MESSAGE_rsp' and 'MAP_DELIMITER_req', leading to 'WAIT_FOR_MORE_MESSAGES'. Error paths for 'Provider error', 'Data error', and 'User error' lead to 'NULL'.](92724c769da9d46b730fde1a6dccb023_img.jpg) + +### Process MT\_SM\_Transfer\_GLR + +23.2.3\_2(3) + +Figure 23.2/3: The mobile terminated short message service in the GLR + +``` +graph TD; Start([WAIT_FOR_MORE_MESSAGES]) --> Ind{MAP_MT_FORWARD_SHORT_MESSAGE_ind}; Ind --> CheckInd[Check Indication]; CheckInd -- Section 25.2; CheckInd -- ok --> SendReq[MAP_MT_FORWARD_SHORT_MESSAGE_req
MAP_DELIMITER_req]; SendReq --> WaitConfirm([WAIT_FOR_MT_SMS_CONFIRM]); WaitConfirm --> RecvCnf{MAP_MT_FORWARD_SHORT_MESSAGE_cnf}; RecvCnf --> CheckCnf[Check Confirmation]; CheckCnf -- Section 25.2; CheckCnf -- ok --> AbsentSub{Absent Subscriber?}; AbsentSub -- yes --> SetMNRG[set MNRG]; SetMNRG --> CheckAbsentSM[Check Absent SubscriberSM_In_GLR]; CheckAbsentSM -- See TS 23.119; AbsentSub -- no --> SendRsp1[MAP_MT_FORWARD_SHORT_MESSAGE_rsp
MAP_CLOSE_req]; SendRsp1 --> NULL1([NULL]); CheckCnf -- "Provider error
Data error
User error" --> NULL2([NULL]); CheckCnf -- ok --> MoreMsg{More_msg_to_sent}; MoreMsg -- yes --> Start; MoreMsg -- no --> SendRsp2[MAP_MT_FORWARD_SHORT_MESSAGE_rsp
MAP_DELIMITER_req]; SendRsp2 --> Start2([WAIT_FOR_MORE_MESSAGES]); +``` + +Flowchart for Process MT\_SM\_Transfer\_GLR. The process starts with 'WAIT\_FOR\_MORE\_MESSAGES', followed by 'MAP\_MT\_FORWARD\_SHORT\_MESSAGE\_ind'. It then checks the indication (Section 25.2). If 'ok', it sends 'MAP\_MT\_FORWARD\_SHORT\_MESSAGE\_req' and 'MAP\_DELIMITER\_req', then waits for 'MT\_SMS\_CONFIRM'. Upon receiving 'MAP\_MT\_FORWARD\_SHORT\_MESSAGE\_cnf', it checks the confirmation (Section 25.2). If 'ok', it checks if the subscriber is absent. If 'yes', it sets MNRG and checks 'Absent SubscriberSM\_In\_GLR' (See TS 23.119). If 'no' (either from 'Absent Subscriber?' or 'Check Confirmation'), it sends 'MAP\_MT\_FORWARD\_SHORT\_MESSAGE\_rsp' and 'MAP\_CLOSE\_req', leading to 'NULL'. If 'ok' from 'Check Confirmation', it checks 'More\_msg\_to\_sent'. If 'yes', it loops back to 'WAIT\_FOR\_MORE\_MESSAGES'. If 'no', it sends 'MAP\_MT\_FORWARD\_SHORT\_MESSAGE\_rsp' and 'MAP\_DELIMITER\_req', leading to 'WAIT\_FOR\_MORE\_MESSAGES'. Error paths for 'Provider error', 'Data error', and 'User error' lead to 'NULL'. + +Figure 23.2/3 (sheet 2 of 3): Procedure MT\_SM\_Transfer\_GLR + +#### Process MT\_SM\_Transfer\_GLR + +23.2.3\_3(3) + +Figure 23.2/3: The mobile terminated short message service in the GLR + +![Sequence diagram for Process MT_SM_Transfer_GLR showing interactions between GLR, SMS-GMSC, and SGSN.](93699fb71e95b4df5a3871fdcf818982_img.jpg) + +The sequence diagram illustrates the 'Process MT\_SM\_Transfer\_GLR' procedure. It begins with an initial state labeled 'WAIT\_FOR\_MORE\_MESSAGES' and 'WAIT\_FOR\_MT\_SMS\_CONFIRM'. The first interaction is a 'MAP\_NOTICE\_ind' from the SMS-GMSC. This is followed by a 'MAP\_CLOSE\_req' to the SMS-GMSC. A subsequent 'MAP\_U\_ABORT\_req' is sent to the SGSN, marked with an 'X' indicating an error or termination. The sequence then continues with a 'MAP\_NOTICE\_ind' from the SGSN, followed by a 'MAP\_CLOSE\_req' to the SGSN. Finally, a 'MAP\_U\_ABORT\_req' is sent to the SMS-GMSC, also marked with an 'X'. + +``` +sequenceDiagram + participant GLR + Note right of GLR: WAIT_FOR_MORE_MESSAGES +WAIT_FOR_MT_SMS_CONFIRM + Note left of GLR: MAP_U_ABORT_ind +MAP_P_ABORT_ind +from SMS-GMSC + GLR->>SMS-GMSC: MAP_NOTICE_ind + Note right of SMS-GMSC: from SMS-GMSC + GLR->>SMS-GMSC: MAP_CLOSE_req + Note right of SMS-GMSC: to SMS-GMSC + GLR->>SGSN: MAP_U_ABORT_req + Note right of SGSN: to SGSN + Note right of GLR: X + Note left of GLR: MAP_NOTICE_ind +from SGSN + GLR->>SGSN: MAP_CLOSE_req + Note right of SGSN: to SGSN + Note left of GLR: MAP_U_ABORT_ind +MAP_P_ABORT_ind +fMAP_CLOSE_ind +from SGSN + GLR->>SMS-GMSC: MAP_U_ABORT_req + Note right of SMS-GMSC: to SMS-GMSC + Note right of GLR: X +``` + +Sequence diagram for Process MT\_SM\_Transfer\_GLR showing interactions between GLR, SMS-GMSC, and SGSN. + +Figure 23.2/3 (sheet 3 of 3): Procedure MT\_SM\_Transfer\_GLR + +![Flowchart for Macro MT_SM_GLR. It starts with an oval connector, followed by 'Subscriber known?' (yes/no). 'no' leads to 'User Error = Unidentified User' and 'ERR OR'. 'yes' leads to 'Confirmed by HLR?' (yes/no). 'no' leads to 'ERR OR'. 'yes' leads to 'Retrieve and set SGSN Number'. Then 'Message segmenting needed?' (yes/no). 'no' leads to a process block with MAP_OPEN_req, MAP_MT_FORWARD_SHORT_MESSAGE_req, and MAP_DELIMITER_req, then 'Receive_Open_Cnf'. 'yes' leads to a process block with MAP_OPEN_req, MAP_DELIMITER_req, then 'Receive_Open_Cnf'. Both 'Receive_Open_Cnf' blocks lead to 'WAIT_FOR_MT_SMS_CONFIRM' (ok) or 'Error = System Failure' (error). 'Error = System Failure' leads to 'ERR OR'. Both 'WAIT_FOR_MT_SMS_CONFIRM' blocks lead to a process block with MAP_MT_FORWARD_SHORT_MESSAGE_Cnf, which then leads to connector '1 page2'.](8faeb7db381e28ab1ba06e9f48c19c6e_img.jpg) + +### Macrodefinition MT\_SM\_GLR + +23.2.4\_1(2) + +Figure 23.2/4: Macro which transfer short message PDUs to SGSN in the GLR + +Signals to/from the right are to/from the SGSN + +``` +graph TD; Start([ ]) --> Sub{Subscriber known?}; Sub -- no --> UE[User Error = Unidentified User]; UE --> ERR1((ERR OR)); Sub -- yes --> Conf{Confirmed by HLR?}; Conf -- no --> ERR2((ERR OR)); Conf -- yes --> Ret[Retrieve and set SGSN Number]; Ret --> Seg{Message segmenting needed?}; Seg -- no --> Proc1[MAP_OPEN_req +MAP_MT_FORWARD_SHORT_MESSAGE_req +MAP_DELIMITER_req]; Proc1 --> Recv1[Receive_Open_Cnf]; Seg -- yes --> Proc2[MAP_OPEN_req +MAP_DELIMITER_req]; Proc2 --> Recv2[Receive_Open_Cnf]; Recv1 -- ok --> Wait1((WAIT_FOR_MT_SMS_CONFIRM)); Recv1 -- error --> Err[Error = System Failure]; Err --> ERR3((ERR OR)); Recv2 -- ok --> Proc3[MAP_MT_FORWARD_SHORT_MESSAGE_req +MAP_DELIMITER_req]; Proc3 --> Wait2((WAIT_FOR_MT_SMS_CONFIRM)); Wait1 --> Join1(( )); Wait2 --> Join1; Join1 --> Proc4[MAP_MT_FORWARD_SHORT_MESSAGE_Cnf]; Proc4 --> End((1 page2)); +``` + +Flowchart for Macro MT\_SM\_GLR. It starts with an oval connector, followed by 'Subscriber known?' (yes/no). 'no' leads to 'User Error = Unidentified User' and 'ERR OR'. 'yes' leads to 'Confirmed by HLR?' (yes/no). 'no' leads to 'ERR OR'. 'yes' leads to 'Retrieve and set SGSN Number'. Then 'Message segmenting needed?' (yes/no). 'no' leads to a process block with MAP\_OPEN\_req, MAP\_MT\_FORWARD\_SHORT\_MESSAGE\_req, and MAP\_DELIMITER\_req, then 'Receive\_Open\_Cnf'. 'yes' leads to a process block with MAP\_OPEN\_req, MAP\_DELIMITER\_req, then 'Receive\_Open\_Cnf'. Both 'Receive\_Open\_Cnf' blocks lead to 'WAIT\_FOR\_MT\_SMS\_CONFIRM' (ok) or 'Error = System Failure' (error). 'Error = System Failure' leads to 'ERR OR'. Both 'WAIT\_FOR\_MT\_SMS\_CONFIRM' blocks lead to a process block with MAP\_MT\_FORWARD\_SHORT\_MESSAGE\_Cnf, which then leads to connector '1 page2'. + +Figure 23.2/4 (sheet1 of 2): Macro MT\_SM\_GLR + +##### Macrodefinition MT\_SM\_GLR + +23.2.4\_2(2) + +Figure 23.2/4: Macro which transfer short message PDUs to SGSN in the GLR + +![Flowchart for Macro MT_SM_GLR. It starts with '1 page1', followed by 'Check Confirmation' (linked to Section 25.2). A decision diamond 'Absent Subscriber?' follows. 'yes' leads to 'set MNRG' then 'Check_Absent SubscriberSM_in_GLR' (linked to See TS 23.119). 'no' leads to 'ERR OR'. 'ok' leads to 'OK'. 'Provider Error Data Error' and 'User Error' both lead to 'ERR OR'.](ca9fd3bd2fe73a46244dd1d017ffa3b5_img.jpg) + +``` +graph TD; Start((1 page1)) --> Check[Check Confirmation]; Check --- Section[Section 25.2]; Check --> Decision{Absent Subscriber?}; Decision -- yes --> setMNRG[set MNRG]; setMNRG --> CheckAbsent[Check_Absent SubscriberSM_in_GLR]; CheckAbsent --- TS[See TS 23.119]; Decision -- no --> ERR((ERR OR)); Decision -- ok --> OK((OK)); ProviderError[Provider Error Data Error] --> ERR; UserError[User Error] --> ERR; +``` + +Flowchart for Macro MT\_SM\_GLR. It starts with '1 page1', followed by 'Check Confirmation' (linked to Section 25.2). A decision diamond 'Absent Subscriber?' follows. 'yes' leads to 'set MNRG' then 'Check\_Absent SubscriberSM\_in\_GLR' (linked to See TS 23.119). 'no' leads to 'ERR OR'. 'ok' leads to 'OK'. 'Provider Error Data Error' and 'User Error' both lead to 'ERR OR'. + +Figure 23.2/4 (sheet2 of 2): Macro MT\_SM\_GLR + +## 23.3 The Short Message Alert procedure + +The Short Message Alert procedure is used for alerting the Service Centre when the mobile subscriber is active after a short message transfer has failed because the mobile subscriber is not reachable or when the MS has indicated that it has memory capacity to accept a short message. + +### 23.3.1 Procedures in the GLR + +When the GLR receives MAP\_READY\_FOR\_SM indication from the VLR or the SGSN and it has MNRF or MNRG, it sends MAP\_READY\_FOR\_SM request to the HLR. + +If the outcome is successful, the MNRF or MNRG is cleared. + +The short message alert procedure in the GLR is shown in figure 23.3/1. + +![Flowchart of Process SM_Alert_GLR. The process starts with NULL, then receives an indication (Section 25.1). If ok, it enters WAIT_FOR_SERVICE_PRIMITIVE. From there, it checks for MAP_READY_FOR_SM_ind (Section 25.2). If ok, it checks if the subscriber is known. If yes, it sends MAP_OPEN_req, MAP_READY_FOR_SM_req, and MAP_DELIMITER_req to the HLR, receives a confirmation (Section 25.1), and if ok, sets UE to system failure and ends. If no, it sets UE to UNKNOWN SUBSCRIBWR and ends. If error, it ends with NULL. If MAP_NOTICE_ind is received, it sends MAP_CLOSE_req to the HLR and ends with NULL. If MAP_U_ABORT_ind, MAP_P_ABORT_ind, or MAP_CLOSE_ind are received, it ends with NULL.](a1b35c85c93d7a2e30d1feea2faac2e6_img.jpg) + +**Process SM\_Alert\_GLR** 23.3.1\_1(2) + +Figure 23.3/1: The short message alert process in the GLR + +Signals to/from the left are to/from the VLR/SGSN; signals to/from the right are to/from the HLR + +``` + +graph TD + Start([NULL]) --> RecInd[Receive_Ind] + RecInd -- Section 25.1 --> RecInd + RecInd -- ok --> Wait[WAIT_FOR_SERVICE_PRIMITIVE] + RecInd -- Error --> NULL1([NULL]) + Wait --> ReadyInd{MAP_READY_FOR_SM_ind} + ReadyInd -- Section 25.2 --> CheckInd[Check_Indication] + CheckInd -- ok --> SubKnown{Subscriber_known?} + SubKnown -- yes --> SendReq[MAP_OPEN_req, MAP_READY_FOR_SM_req, MAP_DELIMITER_req] + SubKnown -- no --> SetUnknown[SET UE = UNKNOWN SUBSCRIBWR] + SubKnown -- error --> NULL2([NULL]) + SendReq --> RecCnf[Receive_Cnf] + RecCnf -- Section 25.1 --> RecCnf + RecCnf -- ok --> SetFailure[SET UE = system failure] + RecCnf -- error --> NULL3([NULL]) + SetFailure --> End1((1 page2)) + SetUnknown --> NULL4([NULL]) + NoticeInd{MAP_NOTICE_ind} --> CloseReq[MAP_CLOSE_req] + CloseReq --> NULL5([NULL]) + AbortInd{MAP_U_ABORT_ind, MAP_P_ABORT_ind, MAP_CLOSE_ind} --> NULL6([NULL]) + +``` + +Flowchart of Process SM\_Alert\_GLR. The process starts with NULL, then receives an indication (Section 25.1). If ok, it enters WAIT\_FOR\_SERVICE\_PRIMITIVE. From there, it checks for MAP\_READY\_FOR\_SM\_ind (Section 25.2). If ok, it checks if the subscriber is known. If yes, it sends MAP\_OPEN\_req, MAP\_READY\_FOR\_SM\_req, and MAP\_DELIMITER\_req to the HLR, receives a confirmation (Section 25.1), and if ok, sets UE to system failure and ends. If no, it sets UE to UNKNOWN SUBSCRIBWR and ends. If error, it ends with NULL. If MAP\_NOTICE\_ind is received, it sends MAP\_CLOSE\_req to the HLR and ends with NULL. If MAP\_U\_ABORT\_ind, MAP\_P\_ABORT\_ind, or MAP\_CLOSE\_ind are received, it ends with NULL. + +Figure 23.3/1 (sheet 1 of 2): Process SM\_Alert\_GLR + +![Flowchart for Process SM_Alert_GLR. It starts with a connector '1 page1', followed by 'WF_RESULT', 'MAP_READY_FOR_SM_Cnf', and 'Check Confirmation' (linked to Section 25.2). A decision 'MNRF or MNRG set?' follows. If 'ok' and 'yes', it goes to 'REASON'. If 'error', it goes to 'SET USER ERROR'. From 'REASON', 'non-GPRS' leads to 'Clear MNRF' and 'GPRS' leads to 'Clear MNRG'. Both lead to a merge point. From the merge point, it goes to a process block with 'MAP_READY_FOR_SM_rsp' and 'MAP_CLOSE_req', and finally to 'NULL'.](3334fcca5dac808f4fd3840aba35bc2e_img.jpg) + +**Process SM\_Alert\_GLR** 23.3.1\_2(2) + +Figure 23.3/1: The short message alert process in the GLR + +``` +graph TD; Start((1 page1)) --> WF_RESULT([WF_RESULT]); WF_RESULT --> MAP_READY_FOR_SM_Cnf[MAP_READY_FOR_SM_Cnf]; MAP_READY_FOR_SM_Cnf --> CheckConfirmation[Check Confirmation]; CheckConfirmation --- Section252[Section 25.2]; CheckConfirmation -- ok --> MNRF_MNRG{MNRF or MNRG set?}; CheckConfirmation -- error --> SET_USER_ERROR[SET USER ERROR]; MNRF_MNRG -- yes --> REASON{REASON}; MNRF_MNRG -- no --> MergePoint(( )); REASON -- non-GPRS --> ClearMNRF[Clear MNRF]; REASON -- GPRS --> ClearMNRG[Clear MNRG]; ClearMNRF --> MergePoint; ClearMNRG --> MergePoint; MergePoint --> ProcessBlock[MAP_READY_FOR_SM_rsp
MAP_CLOSE_req]; ProcessBlock --> NULL([NULL]); +``` + +Flowchart for Process SM\_Alert\_GLR. It starts with a connector '1 page1', followed by 'WF\_RESULT', 'MAP\_READY\_FOR\_SM\_Cnf', and 'Check Confirmation' (linked to Section 25.2). A decision 'MNRF or MNRG set?' follows. If 'ok' and 'yes', it goes to 'REASON'. If 'error', it goes to 'SET USER ERROR'. From 'REASON', 'non-GPRS' leads to 'Clear MNRF' and 'GPRS' leads to 'Clear MNRG'. Both lead to a merge point. From the merge point, it goes to a process block with 'MAP\_READY\_FOR\_SM\_rsp' and 'MAP\_CLOSE\_req', and finally to 'NULL'. + +Figure 23.3/1 (sheet 2 of 2): Process SM\_Alert\_GLR + +# 24 GPRS process description + +## 24.1 General + +The MAP GPRS procedures are used for the Network Requested PDP-Context Activation procedures. + +The stage 2 specification for Packet Switched Service involving GLR is in 3GPP TS 23.119. + +## 24.2 Send Routing Information procedure + +### 24.2.1 Process in the GLR for Send Routing Information for GPRS + +The MAP process in the GLR to provide routing information for a network-requested PDP context activation is shown in figure 24.2/1. The MAP process invokes a macro not defined in this subclause; the definition of this macro can be found as follows: + +- Receive\_Open\_Ind see subclause 25.1; +- Check\_Indication see subclause 25.2. + +#### Successful outcome + +When the MAP process receives a MAP\_OPEN indication with the application context gprsLocationInfoRetrieval, it checks it by invoking the macro Receive\_Open\_Ind. + +If the macro takes the OK exit, the MAP process waits for a service indication. + +If a MAP\_SEND\_ROUTING\_INFO\_FOR\_GPRS service indication is received, the GLR sends a Send Routing Info For Gprs request to the GPRS application process in the GLR, and wait for a response. The Send Routing Info For Gprs request contains the parameter received in the MAP\_SEND\_ROUTING\_INFO\_FOR\_GPRS service indication. + +If the GPRS application process in the GLR returns a positive response containing the routing information, the MAP process constructs a MAP\_SEND\_ROUTING\_INFO\_FOR\_GPRS service response containing the routing info, constructs a MAP\_CLOSE service request, sends them to the IM-GSN and returns to the idle state. + +#### Negative response from GLR GPRS application process + +If the GPRS application process in the GLR returns a negative response, the MAP process constructs a MAP\_SEND\_ROUTING\_INFO\_FOR\_GPRS service response containing the appropriate error, constructs a MAP\_CLOSE service request, sends them to the IM-GSN and returns to the idle state. + +#### Failure of dialogue opening with the IM-GSN + +If the macro Receive\_Open\_Ind takes the Vr exit or the Error exit, the MAP process returns to the idle state. + +If the MAP provider sends a MAP\_P\_ABORT while the MAP process is waiting for a service indication, the MAP process returns to the idle state. + +If the MAP provider sends a MAP\_NOTICE while the MAP process is waiting for a service indication, the MAP process sends a MAP\_CLOSE request to terminate the dialogue and returns to the idle state. + +![Flowchart for Process Send_Routing_Info_For_Gprs_GLR. The process starts at an oval, goes to an 'Idle' state, then receives an 'Open_Ind' signal (linked to Section 25.1). From 'Receive Open_Ind', an 'OK' path leads to 'Wait_For_Service_Indication' and a 'Vr, Error' path leads to another 'Idle' state. From 'Wait_For_Service_Indication', three paths emerge: 'MAP_P_ABORT_ind' leading to 'Idle', 'MAP_SEND_ROUTING_INFO_FOR_GPRS_ind' leading to 'Send Routing Info For Gprs', and 'MAP_NOTICE_ind' leading to 'MAP_CLOSE_req' and then 'Idle'. From 'Send Routing Info For Gprs', the flow goes to 'Wait For Routing Info', which then branches into 'Send Routing Info For Gprs negative response' (leading to 'Set UE') and 'Send Routing Info For Gprs ack' (leading to 'Set Routing Info'). Both 'Set UE' and 'Set Routing Info' lead to a merge point. From this merge point, the flow goes to a box containing 'MAP_SEND_ROUTING_INFO_FOR_GPRS_rsp' and 'MAP_CLOSE_req', which then leads to a final 'Idle' state.](93bd00a00fa28558486f0664550699b1_img.jpg) + +### Process Send\_Routing\_Info\_For\_Gprs\_GLR + +24.2.1(1) + +Figure 24.2/1: The Send Routing Info For Gprs process in the GLR + +Signals to/from the right are to/from the GPRS application process + +``` +graph TD; Start([ ]) --> Idle1([Idle]); Idle1 --> ReceiveOpenInd[Receive Open_Ind]; ReceiveOpenInd --- Section251[Section 25.1]; ReceiveOpenInd -- OK --> WaitForServiceIndication[Wait_For_Service_Indication]; ReceiveOpenInd -- "Vr, Error" --> Idle2([Idle]); WaitForServiceIndication --> MAP_P_ABORT_ind[/MAP_P_ABORT_ind/]; WaitForServiceIndication --> MAP_SEND_ROUTING_INFO_FOR_GPRS_ind[/MAP_SEND_ROUTING_INFO_FOR_GPRS_ind/]; WaitForServiceIndication --> MAP_NOTICE_ind[/MAP_NOTICE_ind/]; MAP_P_ABORT_ind --> Idle3([Idle]); MAP_SEND_ROUTING_INFO_FOR_GPRS_ind --> SendRoutingInfoForGprs[/Send Routing Info For Gprs/]; MAP_NOTICE_ind --> MAP_CLOSE_req[/MAP_CLOSE_req/]; MAP_CLOSE_req --> Idle4([Idle]); SendRoutingInfoForGprs --> WaitForRoutingInfo[Wait For Routing Info]; WaitForRoutingInfo --> SendRoutingInfoForGprsNegativeResponse[/Send Routing Info For Gprs negative response/]; WaitForRoutingInfo --> SendRoutingInfoForGprsAck[/Send Routing Info For Gprs ack/]; SendRoutingInfoForGprsNegativeResponse --> SetUE[Set UE]; SendRoutingInfoForGprsAck --> SetRoutingInfo[Set Routing Info]; SetUE --> Merge(( )); SetRoutingInfo --> Merge; Merge --> MAP_SEND_ROUTING_INFO_FOR_GPRS_rsp[MAP_SEND_ROUTING_INFO_FOR_GPRS_rsp]; Merge --> MAP_CLOSE_req2[MAP_CLOSE_req]; MAP_SEND_ROUTING_INFO_FOR_GPRS_rsp --> Idle5([Idle]); MAP_CLOSE_req2 --> Idle5; +``` + +Flowchart for Process Send\_Routing\_Info\_For\_Gprs\_GLR. The process starts at an oval, goes to an 'Idle' state, then receives an 'Open\_Ind' signal (linked to Section 25.1). From 'Receive Open\_Ind', an 'OK' path leads to 'Wait\_For\_Service\_Indication' and a 'Vr, Error' path leads to another 'Idle' state. From 'Wait\_For\_Service\_Indication', three paths emerge: 'MAP\_P\_ABORT\_ind' leading to 'Idle', 'MAP\_SEND\_ROUTING\_INFO\_FOR\_GPRS\_ind' leading to 'Send Routing Info For Gprs', and 'MAP\_NOTICE\_ind' leading to 'MAP\_CLOSE\_req' and then 'Idle'. From 'Send Routing Info For Gprs', the flow goes to 'Wait For Routing Info', which then branches into 'Send Routing Info For Gprs negative response' (leading to 'Set UE') and 'Send Routing Info For Gprs ack' (leading to 'Set Routing Info'). Both 'Set UE' and 'Set Routing Info' lead to a merge point. From this merge point, the flow goes to a box containing 'MAP\_SEND\_ROUTING\_INFO\_FOR\_GPRS\_rsp' and 'MAP\_CLOSE\_req', which then leads to a final 'Idle' state. + +Figure 24.2/1: Process Send Routing Info For Gprs\_GLR + +### 24.2.2 Process in the IM-GSN for Send Routing Information for GPRS + +Successful Outcome + +When the MAP process receives a Send Routing Info For Gprs request from the GPRS application process in the IM-GSN, it: + +- requests a dialogue with the GLR whose identity is contained in the Send Routing Info For Gprs request by sending a MAP\_OPEN service request; +- requests routing information using a MAP\_SEND\_ROUTING\_INFO\_FOR\_GPRS service request, and +- invokes the macro Receive\_Open\_Cnf to wait for the response to the dialogue opening request. + +If the dialogue opening is successful, the MAP process waits for a response from the GLR. + +If the MAP process receives a MAP\_SEND\_ROUTING\_INFO\_FOR\_GPRS service confirm from the GLR, the MAP process invokes the macro Check\_Confirmation to check the content of the confirmation. + +If the macro Check\_Confirmation takes the OK exit, the MAP process sends a Send Routing Info For Gprs ack containing the routing information received from the GLR to the GPRS application process in the IM-GSN and returns to the idle state. + +#### **Failure of dialogue opening with the GLR** + +If the macro Receive\_Open\_Cnf takes the Vr exit or the Error exit, the MAP process sends a negative response to the GPRS application process in the IM-GSN and returns to the idle state. + +#### **Error in MAP\_SEND\_ROUTING\_INFO\_FOR\_GPRS confirm** + +If the MAP\_SEND\_ROUTING\_INFO\_FOR\_GPRS service confirm contains a user error or a provider error, or the macro Check\_Confirmation indicates that there is a data error, the MAP process sends a Send Routing Info For Gprs negative response to the GPRS application process in the IM-GSN and returns to the idle state. + +#### **Abort of GLR dialogue** + +After the dialogue with the GLR has been established, the MAP service provider may abort the dialogue by issuing a MAP\_P\_ABORT or a MAP\_U\_ABORT indication. In this case, the MAP process sends a Send Routing Info For Gprs negative response to the GPRS application process in the IM-GSN and returns to the idle state. + +If the MAP provider indicates a protocol problem by sending a MAP\_NOTICE indication, the MAP process closes the dialogue with the GLR, sends a Send Routing Info For Gprs negative response indicating system failure to the GPRS application process in the IM-GSN and returns to the idle state. + +![State transition diagram for Process Send_Routing_Info_For_Gprs_IMGSN. The process starts at Idle, transitions to Send Routing Info For Gprs, then to a state where it sends MAP_OPEN_req, MAP_SEND_ROUTING_INFO_FOR_GPRS_req, and MAP_DELIMITER_req. It then receives an Open_cnf (Section 25.1). From Open_cnf, an OK leads to Wait_For_Ack, while Vr, Error leads to Send Routing Info For Gprs negative response and back to Idle. From Wait_For_Ack, three paths emerge: MAP_SEND_ROUTING_INFO_FOR_GPRS_cnf (leading to Check_Confirmation, Section 25.2, and then OK), MAP_P_ABORT_ind / MAP_U_ABORT_ind, and MAP_NOTICE_ind. MAP_NOTICE_ind leads to MAP_CLOSE_req. Both OK and MAP_CLOSE_req lead to a state with Send Routing Info For Gprs ack and Send Routing Info For Gprs negative response, which then returns to Idle. The MAP_P_ABORT_ind / MAP_U_ABORT_ind path leads to a state with Provider User Error, Data Error, which also returns to Idle.](f4e5a86da5c799372a7c1ea2397dedb7_img.jpg) + +### Process Send\_Routing\_Info\_For\_Gprs\_IMGSN 24.2.2(1) + +Figure 24.2/2: The Send Routing Info For Gprs process in the IMGSN + +Signals to/from the right are to/from the GPRS application process + +``` +stateDiagram-v2 + [*] --> Idle + Idle --> Send_Routing_Info_For_Gprs + Send_Routing_Info_For_Gprs --> Out + state "MAP_OPEN_req
MAP_SEND_ROUTING_INFO_FOR_GPRS_req
MAP_DELIMITER_req" as Out + Out --> Receive_Open_cnf + state "Section 25.1" as Receive_Open_cnf + Receive_Open_cnf --> Wait_For_Ack + Receive_Open_cnf --> Vr_Error: Vr, Error + Vr_Error --> Send_Routing_Info_For_Gprs_Neg_Response: Send Routing Info For Gprs negative response + Send_Routing_Info_For_Gprs_Neg_Response --> Idle + Wait_For_Ack --> MAP_SEND_ROUTING_INFO_FOR_GPRS_cnf + Wait_For_Ack --> MAP_P_ABORT_ind + Wait_For_Ack --> MAP_NOTICE_ind + MAP_SEND_ROUTING_INFO_FOR_GPRS_cnf --> Check_Confirmation + state "Section 25.2" as Check_Confirmation + Check_Confirmation --> OK + OK --> Send_Routing_Info_For_Gprs_Ack + OK --> MAP_CLOSE_req + MAP_P_ABORT_ind --> MAP_U_ABORT_ind + MAP_U_ABORT_ind --> Provider_User_Error: Provider User Error, Data Error + Provider_User_Error --> Idle + MAP_NOTICE_ind --> MAP_CLOSE_req + Send_Routing_Info_For_Gprs_Ack --> Idle + Send_Routing_Info_For_Gprs_Neg_Response --> Idle +``` + +State transition diagram for Process Send\_Routing\_Info\_For\_Gprs\_IMGSN. The process starts at Idle, transitions to Send Routing Info For Gprs, then to a state where it sends MAP\_OPEN\_req, MAP\_SEND\_ROUTING\_INFO\_FOR\_GPRS\_req, and MAP\_DELIMITER\_req. It then receives an Open\_cnf (Section 25.1). From Open\_cnf, an OK leads to Wait\_For\_Ack, while Vr, Error leads to Send Routing Info For Gprs negative response and back to Idle. From Wait\_For\_Ack, three paths emerge: MAP\_SEND\_ROUTING\_INFO\_FOR\_GPRS\_cnf (leading to Check\_Confirmation, Section 25.2, and then OK), MAP\_P\_ABORT\_ind / MAP\_U\_ABORT\_ind, and MAP\_NOTICE\_ind. MAP\_NOTICE\_ind leads to MAP\_CLOSE\_req. Both OK and MAP\_CLOSE\_req lead to a state with Send Routing Info For Gprs ack and Send Routing Info For Gprs negative response, which then returns to Idle. The MAP\_P\_ABORT\_ind / MAP\_U\_ABORT\_ind path leads to a state with Provider User Error, Data Error, which also returns to Idle. + +Figure 24.2/2: Process Send\_Routing\_Info\_For\_Gprs\_IM-GSN + +## 24.3 Failure Report procedure + +### 24.3.1 Process in the GLR for Failure Report + +The MAP process in the GLR to set the MNRG (Mobile station Not Reachable for GPRS) flag for the subscriber is shown in figure 24.3/1. The MAP process invokes a macro not defined in this subclause; the definition of this macro can be found as follows: + +- Receive\_Open\_Ind see subclause 25.1; +- Check Indication see subclause 25.2. + +#### Successful outcome + +When the MAP process receives a MAP\_OPEN indication with the application context failureReport, it checks it by invoking the macro Receive\_Open\_Ind. + +If the macro takes the OK exit, the MAP process waits for a service indication. + +If a MAP\_FAILURE\_REPORT service indication is received, the GLR sends a Failure Report request to the GPRS application process in the GLR, and wait for a response. The Failure Report request contains the parameter received in the MAP\_FAILURE\_REPORT service indication. + +If a positive response is received, the MAP process constructs a MAP\_FAILURE\_REPORT service response, constructs a MAP\_CLOSE service request, sends them to the IM-GSN and returns to the idle state. + +#### Negative response from GLR GPRS application process + +If the GPRS application process in the GLR returns a negative response, the MAP process constructs a MAP\_FAILURE\_REPORT service response containing the appropriate error, constructs a MAP\_CLOSE service request, sends them to the IM-GSN and returns to the idle state. + +#### Failure of dialogue opening with the IM-GSN + +If the macro Receive\_Open\_Ind takes the Vr exit or the Error exit, the MAP process returns to the idle state. + +If the MAP provider sends a MAP\_P\_ABORT while the MAP process is waiting for a service indication, the MAP process returns to the idle state. + +If the MAP provider sends a MAP\_NOTICE while the MAP process is waiting for a service indication, the MAP process sends a MAP\_CLOSE request to terminate the dialogue and returns to the idle state. + +![Flowchart of Process Failure_Report_GLR](61b2e15aedbb8a8dffc5426c0a284eb1_img.jpg) + +### Process Failure\_Report\_GLR + +24.3.1(1) + +Figure 24.3/1: The Failure Report process in the GLR + +Signals to/from the right are to/from the application process + +``` +graph TD; Start([ ]) --> Idle1([Idle]); Idle1 --> RecOpen[Receive Open_Ind]; RecOpen --> WaitFor[Wait_For_Service_Indication]; RecOpen --> VrError[Idle]; VrError --> VrError; WaitFor --> MAP_P_ABORT[MAP_P_ABORT_ind]; WaitFor --> MAP_FAILURE_REPORT[MAP_FAILURE_REPORT_ind]; WaitFor --> MAP_NOTICE[MAP_NOTICE_ind]; MAP_P_ABORT --> Idle2([Idle]); MAP_FAILURE_REPORT --> FailureReport[Failure Report]; FailureReport --> WaitForResponse[Wait For Response]; MAP_NOTICE --> MAP_CLOSE_req1[MAP_CLOSE_req]; MAP_CLOSE_req1 --> Idle3([Idle]); WaitForResponse --> NegResponse[Failure Report negative response]; WaitForResponse --> Ack[Failure Report ack]; NegResponse --> SetUE[Set UE]; SetUE --> MAP_FAILURE_REPORT_rsp[MAP_FAILURE_REPORT_rsp]; Ack --> MAP_FAILURE_REPORT_rsp; MAP_FAILURE_REPORT_rsp --> MAP_CLOSE_req2[MAP_CLOSE_req]; MAP_FAILURE_REPORT_rsp --> Idle4([Idle]); +``` + +The flowchart illustrates the 'Process Failure\_Report\_GLR'. It begins with an initial state leading to an 'Idle' state. Upon receiving an 'Open\_Ind' signal (referenced to Section 25.1), the process enters a 'Wait\_For\_Service\_Indication' state. From here, three outcomes are possible: an 'OK' result leads to a subsequent 'Idle' state; a 'Vr, Error' result also leads to an 'Idle' state; or a specific indication is received. The indications include 'MAP\_P\_ABORT\_ind' (leading to 'Idle'), 'MAP\_FAILURE\_REPORT\_ind' (leading to 'Failure Report'), and 'MAP\_NOTICE\_ind' (leading to 'MAP\_CLOSE\_req' and then 'Idle'). The 'Failure Report' path continues to 'Wait For Response', which then branches into 'Failure Report negative response' (leading to 'Set UE') or 'Failure Report ack'. Both 'Set UE' and 'Failure Report ack' lead to a common state where 'MAP\_FAILURE\_REPORT\_rsp' and 'MAP\_CLOSE\_req' signals are generated, finally returning the process to an 'Idle' state. A note indicates that signals to/from the right are to/from the application process. + +Flowchart of Process Failure\_Report\_GLR + +Figure 24.3/1: Process Failure\_Report\_GLR + +### 24.3.2 Process in the IM-GSN for Failure Report + +Successful Outcome + +When the MAP process receives a Failure Report request from the GPRS application process in the IM-GSN, it requests a dialogue with the GLR whose identity is contained in the Failure Report request by sending a MAP\_OPEN service request, sending failure information using a MAP\_FAILURE\_REPORT service request and invokes the macro Receive\_Open\_Cnf to wait for the response to the dialogue opening request. If the dialogue opening is successful, the MAP process waits for a response from the GLR. + +If the MAP process receives a MAP\_FAILURE\_REPORT service confirm from the GLR, the MAP process invokes the macro Check\_Confirmation to check the content of the confirmation. + +If the macro Check\_Confirmation takes the OK exit, the MAP process sends a Failure Report ack containing the information received from the GLR to the GPRS application process in the IM-GSN and returns to the idle state. + +#### **Failure of dialogue opening with the GLR** + +If the macro Receive\_Open\_Cnf takes the Vr exit or the Error exit, the MAP process sends a negative response to the GPRS application process in the IM-GSN and returns to the idle state. + +#### **Error in MAP\_FAILURE\_REPORT confirm** + +If the MAP\_FAILURE\_REPORT service confirm contains a user error or a provider error, or the macro Check\_Confirmation indicates that there is a data error, the MAP process sends a Failure Report negative response to the GPRS application process in the IM-GSN and returns to the idle state. + +#### **Abort of GLR dialogue** + +After the dialogue with the GLR has been established, the MAP service provider may abort the dialogue by issuing a MAP\_P\_ABORT or a MAP\_U\_ABORT indication. In this case, the MAP process sends a Failure Report negative response to the GPRS application process in the IM-GSN and returns to the idle state. + +If the MAP provider indicates a protocol problem by sending a MAP\_NOTICE indication, the MAP process closes the dialogue with the GLR, sends a Failure Report negative response indicating system failure to the GPRS application process in the IM-GSN and returns to the idle state. + +![Flowchart of the Failure Report process in the IMGSN. The process starts at an 'Idle' state, receives a 'Failure Report', sends 'MAP_OPEN_req', 'MAP_FAILURE_REPORT_req', and 'MAP_DELIMITER_req', receives 'Open_cnf' (Section 25.1), enters 'Wait_For_Ack', receives 'MAP_FAILURE_REPORT_cnf' (Section 25.2), sends 'Failure Report ack', and returns to 'Idle'. It also handles 'MAP_P_ABORT_ind', 'MAP_U_ABORT_ind', 'MAP_NOTICE_ind', and 'MAP_CLOSE_req' signals, leading to 'Failure Report negative response' or 'Provider User Error, Data Error' states.](710ff83dc4a77abbe489fbf1a462845a_img.jpg) + +### Process Failure\_Report\_IMGSN + +24.3.2(1) + +Figure 24.3/2: The Failure Report process in the IMGSN + +Signals to/from the right are to/from the GPRS application process + +``` +graph TD; Start([ ]) --> Idle1([Idle]); Idle1 --> FailureReport[/Failure Report/]; FailureReport --> OpenReq{ }; OpenReq --> OpenReqText["MAP_OPEN_req +MAP_FAILURE_REPORT_req +MAP_DELIMITER_req"]; OpenReq --> OpenCnf[Receive Open_cnf]; OpenCnf --> OpenCnfText["Section 25.1"]; OpenCnf --> WaitForAck([Wait_For_Ack]); WaitForAck --> WaitForAckText["OK"]; WaitForAck --> VrError["Vr, Error"]; VrError --> FailureReportNeg["Failure Report negative response"]; FailureReportNeg --> Idle2([Idle]); WaitForAck --> Junction1(( )); Junction1 --> Junction2(( )); Junction2 --> FailureReportCnf[/MAP_FAILURE_REPORT_cnf/]; FailureReportCnf --> FailureReportCnfText["Section 25.2"]; FailureReportCnf --> CheckConfirmation[Check Confirmation]; CheckConfirmation --> CheckConfirmationText["OK"]; CheckConfirmation --> FailureReportAck[/Failure Report ack/]; FailureReportAck --> Idle3([Idle]); Junction2 --> MAP_P_ABORT_ind[/MAP_P_ABORT_ind +MAP_U_ABORT_ind/]; MAP_P_ABORT_ind --> MAP_P_ABORT_indText["ABORT_ind"]; MAP_P_ABORT_ind --> ErrorState["Provider User Error, Data Error"]; Junction2 --> MAP_NOTICE_ind[/MAP_NOTICE_ind/]; MAP_NOTICE_ind --> MAP_CLOSE_req[/MAP_CLOSE_req/]; MAP_CLOSE_req --> FailureReportNeg2[/Failure Report negative response/]; FailureReportNeg2 --> Idle3; +``` + +Flowchart of the Failure Report process in the IMGSN. The process starts at an 'Idle' state, receives a 'Failure Report', sends 'MAP\_OPEN\_req', 'MAP\_FAILURE\_REPORT\_req', and 'MAP\_DELIMITER\_req', receives 'Open\_cnf' (Section 25.1), enters 'Wait\_For\_Ack', receives 'MAP\_FAILURE\_REPORT\_cnf' (Section 25.2), sends 'Failure Report ack', and returns to 'Idle'. It also handles 'MAP\_P\_ABORT\_ind', 'MAP\_U\_ABORT\_ind', 'MAP\_NOTICE\_ind', and 'MAP\_CLOSE\_req' signals, leading to 'Failure Report negative response' or 'Provider User Error, Data Error' states. + +Figure 24.3/2: Process Failure\_Report\_IM-GSN + +# --- 25 General macro description + +## 25.1 MAP open macros + +This subclause refers 3GPP TS 29.002. + +## 25.2 Macros to check the content of indication and confirmation primitives + +This subclause refers 3GPP TS 29.002. + +## 25.3 Authentication processes + +### 25.3.1 Process Obtain\_Authentication\_Sets\_GLR + +This process is initiated by the GLR to fetch authentication vectors from a subscriber's HLR to the VLR. The process is described in figure 25.3/1. + +![Flowchart for Process Obtain_Authent_Sets_GLR. The process starts with an oval connector, leading to a 'NULL' state. It then enters a 'Receive_Open_ind' block (Section 25.1). From here, an 'OK' path leads to 'Wait_For_Service_Primitive', which then branches into three parallel paths: one leading to 'NULL' via 'MAP_P_ABORT_ind', 'MAP_U_ABORT_ind', and 'MAP_CLOSE_ind'; another leading to 'NULL' via 'MAP_SEND_AUTHENTICATION_INFO_ind'; and a third leading to 'NULL' via 'MAP_NOTICE_ind' and 'MAP_CLOSE_req'. A 'Vr, Error' path from 'Wait_For_Service_Primitive' also leads to 'NULL'. The middle path from 'Wait_For_Service_Primitive' leads to a block with 'MAP_OPEN_req', 'MAP_SEND_AUTHENTICATION_INFO_req', and 'MAP_DELIMITER_req', which then leads to 'Receive_Open_cnf' (Section 25.1). From 'Receive_Open_cnf', an 'OK' path leads to 'WAIT_FOR_AUTHENTICATION_INFO', and a 'Vr, Error' path leads to 'MAP_U_ABORT_req' and then 'NULL'.](884c44b6cb9fbe15347e0562a6085df2_img.jpg) + +### Process Obtain\_Authent\_Sets\_GLR + +25.3.1\_1(2) + +Figure 25.3/1: The Process to obtain authentication sets from the HLR to the VLR via the GLR + +Left from/to VLR +Right from/to HLR + +``` +graph TD; Start([ ]) --> NULL1(NULL); NULL1 --> Receive_Open_ind[Receive_Open_ind]; subgraph Section_25_1_1 [Section 25.1]; Receive_Open_ind; end; Receive_Open_ind -- OK --> Wait_For_Service_Primitive((Wait_For_Service_Primitive)); Receive_Open_ind -- "Vr, Error" --> NULL2(NULL); Wait_For_Service_Primitive --> MAP_P_ABORT_ind[MAP_P_ABORT_ind +MAP_U_ABORT_ind +MAP_CLOSE_ind]; Wait_For_Service_Primitive --> MAP_SEND_AUTHENTICATION_INFO_ind[MAP_SEND_AUTHENTICATION_INFO_ind]; Wait_For_Service_Primitive --> MAP_NOTICE_ind[MAP_NOTICE_ind]; MAP_P_ABORT_ind --> NULL3(NULL); MAP_SEND_AUTHENTICATION_INFO_ind --> NULL4(NULL); MAP_NOTICE_ind --> MAP_CLOSE_req{MAP_CLOSE_req}; MAP_CLOSE_req --> NULL5(NULL); Wait_For_Service_Primitive --> MAP_OPEN_req[MAP_OPEN_req +MAP_SEND_AUTHENTICATION_INFO_req +MAP_DELIMITER_req]; MAP_OPEN_req --> Receive_Open_cnf[Receive_Open_cnf]; subgraph Section_25_1_2 [Section 25.1]; Receive_Open_cnf; end; Receive_Open_cnf -- OK --> WAIT_FOR_AUTHENTICATION_INFO((WAIT_FOR_AUTHENTICATION_INFO)); Receive_Open_cnf -- "Vr, Error" --> MAP_U_ABORT_req{MAP_U_ABORT_req}; MAP_U_ABORT_req --> NULL6(NULL); +``` + +Flowchart for Process Obtain\_Authent\_Sets\_GLR. The process starts with an oval connector, leading to a 'NULL' state. It then enters a 'Receive\_Open\_ind' block (Section 25.1). From here, an 'OK' path leads to 'Wait\_For\_Service\_Primitive', which then branches into three parallel paths: one leading to 'NULL' via 'MAP\_P\_ABORT\_ind', 'MAP\_U\_ABORT\_ind', and 'MAP\_CLOSE\_ind'; another leading to 'NULL' via 'MAP\_SEND\_AUTHENTICATION\_INFO\_ind'; and a third leading to 'NULL' via 'MAP\_NOTICE\_ind' and 'MAP\_CLOSE\_req'. A 'Vr, Error' path from 'Wait\_For\_Service\_Primitive' also leads to 'NULL'. The middle path from 'Wait\_For\_Service\_Primitive' leads to a block with 'MAP\_OPEN\_req', 'MAP\_SEND\_AUTHENTICATION\_INFO\_req', and 'MAP\_DELIMITER\_req', which then leads to 'Receive\_Open\_cnf' (Section 25.1). From 'Receive\_Open\_cnf', an 'OK' path leads to 'WAIT\_FOR\_AUTHENTICATION\_INFO', and a 'Vr, Error' path leads to 'MAP\_U\_ABORT\_req' and then 'NULL'. + +Figure 25.3.1/1 (sheet 1 of 2): Process Obtain\_Authentication\_Sets\_GLR + +![State transition diagram for Process Obtain_Authent_Sets_GLR. The diagram shows two main sections of state transitions. The top section starts with 'WAIT FOR AUTHENTICATION_INFO' and branches into four paths: 1) MAP SEND AUTHENTICATION_INFO_req leads to MAP SEND AUTHENTICATION_INFO_ind, which leads to MAP SEND AUTHENTICATION_INFO_req, which leads to 'WAIT FOR AUTHENTICATION_INFO'. 2) MAP SEND AUTHENTICATION_INFO_ind leads to MAP SEND AUTHENTICATION_INFO_req, which leads to 'NULL'. 3) MAP CLOSE_ind leads to MAP CLOSE_req, which leads to 'NULL'. 4) MAP CLOSE_ind leads to MAP CLOSE_req, which leads to the bottom section. The bottom section starts with four paths: 1) MAP NOTICE_ind leads to MAP CLOSE_req, which leads to MAP U_ABORT_req, which leads to 'NULL'. 2) MAP NOTICE_ind leads to MAP CLOSE_req, which leads to MAP U_ABORT_req, which leads to 'NULL'. 3) MAP_P_ABORT_ind / MAP_U_ABORT_ind leads to MAP U_ABORT_req, which leads to 'NULL'. 4) MAP_P_ABORT_ind / MAP_U_ABORT_ind leads to MAP U_ABORT_req, which leads to 'NULL'.](b0384c8e0ff826a8116ab2ff67dadc43_img.jpg) + +**Process Obtain\_Authent\_Sets\_GLR** 25.3.1\_2(2) + +Figure 25.3/1: The Process to obtain authentication sets from the HLR to the VLR via the GLR + +Left from/to VLR +Right from/to HLR + +``` + +stateDiagram-v2 + [*] --> WAIT_FOR_AUTHENTICATION_INFO + WAIT_FOR_AUTHENTICATION_INFO --> MAP_SEND_AUTHENTICATION_INFO_req + WAIT_FOR_AUTHENTICATION_INFO --> MAP_SEND_AUTHENTICATION_INFO_ind + WAIT_FOR_AUTHENTICATION_INFO --> MAP_CLOSE_ind + WAIT_FOR_AUTHENTICATION_INFO --> MAP_CLOSE_ind + + state "MAP_SEND_AUTHENTICATION_INFO_req" as MAP_SEND_AUTHENTICATION_INFO_req + state "MAP_SEND_AUTHENTICATION_INFO_ind" as MAP_SEND_AUTHENTICATION_INFO_ind + state "MAP_CLOSE_ind" as MAP_CLOSE_ind + state "MAP_CLOSE_ind" as MAP_CLOSE_ind + + MAP_SEND_AUTHENTICATION_INFO_req --> MAP_SEND_AUTHENTICATION_INFO_ind + MAP_SEND_AUTHENTICATION_INFO_ind --> MAP_SEND_AUTHENTICATION_INFO_req + MAP_SEND_AUTHENTICATION_INFO_ind --> MAP_SEND_AUTHENTICATION_INFO_req + MAP_SEND_AUTHENTICATION_INFO_req --> WAIT_FOR_AUTHENTICATION_INFO + MAP_SEND_AUTHENTICATION_INFO_req --> NULL + + MAP_CLOSE_ind --> MAP_CLOSE_req + MAP_CLOSE_ind --> MAP_CLOSE_req + + MAP_CLOSE_req --> NULL + MAP_CLOSE_req --> MAP_NOTICE_ind + MAP_CLOSE_req --> MAP_NOTICE_ind + MAP_CLOSE_req --> MAP_P_ABORT_ind_MAP_U_ABORT_ind + MAP_CLOSE_req --> MAP_P_ABORT_ind_MAP_U_ABORT_ind + + state "MAP_NOTICE_ind" as MAP_NOTICE_ind + state "MAP_NOTICE_ind" as MAP_NOTICE_ind + state "MAP_P_ABORT_ind / MAP_U_ABORT_ind" as MAP_P_ABORT_ind_MAP_U_ABORT_ind + state "MAP_P_ABORT_ind / MAP_U_ABORT_ind" as MAP_P_ABORT_ind_MAP_U_ABORT_ind + + MAP_NOTICE_ind --> MAP_CLOSE_req + MAP_NOTICE_ind --> MAP_CLOSE_req + MAP_P_ABORT_ind_MAP_U_ABORT_ind --> MAP_U_ABORT_req + MAP_P_ABORT_ind_MAP_U_ABORT_ind --> MAP_U_ABORT_req + + MAP_CLOSE_req --> MAP_U_ABORT_req + MAP_CLOSE_req --> MAP_U_ABORT_req + + MAP_U_ABORT_req --> NULL + MAP_U_ABORT_req --> NULL + MAP_U_ABORT_req --> NULL + MAP_U_ABORT_req --> NULL + +``` + +State transition diagram for Process Obtain\_Authent\_Sets\_GLR. The diagram shows two main sections of state transitions. The top section starts with 'WAIT FOR AUTHENTICATION\_INFO' and branches into four paths: 1) MAP SEND AUTHENTICATION\_INFO\_req leads to MAP SEND AUTHENTICATION\_INFO\_ind, which leads to MAP SEND AUTHENTICATION\_INFO\_req, which leads to 'WAIT FOR AUTHENTICATION\_INFO'. 2) MAP SEND AUTHENTICATION\_INFO\_ind leads to MAP SEND AUTHENTICATION\_INFO\_req, which leads to 'NULL'. 3) MAP CLOSE\_ind leads to MAP CLOSE\_req, which leads to 'NULL'. 4) MAP CLOSE\_ind leads to MAP CLOSE\_req, which leads to the bottom section. The bottom section starts with four paths: 1) MAP NOTICE\_ind leads to MAP CLOSE\_req, which leads to MAP U\_ABORT\_req, which leads to 'NULL'. 2) MAP NOTICE\_ind leads to MAP CLOSE\_req, which leads to MAP U\_ABORT\_req, which leads to 'NULL'. 3) MAP\_P\_ABORT\_ind / MAP\_U\_ABORT\_ind leads to MAP U\_ABORT\_req, which leads to 'NULL'. 4) MAP\_P\_ABORT\_ind / MAP\_U\_ABORT\_ind leads to MAP U\_ABORT\_req, which leads to 'NULL'. + +Figure 25.3.1/2 (sheet 2 of 2): Process Obtain\_Authentication\_Sets\_GLR + +### 25.3.2 Process Authentication\_Failure\_Report\_GLR + +This process is initiated by the GLR to notify a subscriber's HLR about the occurrence of an authentication failure in the VLR or SGSN. The process is described in figure 25.3/2. + +![Flowchart for Process Authentication_Failure_Report_GLR. The process starts with an initial state leading to a NULL state. It then enters a 'Receive_Open_ind' block (Section 25.1). From here, an 'OK' path leads to 'Wait_For_Service_Primitive', which then leads to a decision point. A 'Vr, Error' path from 'Receive_Open_ind' leads to a NULL state. From the decision point, a 'MAP_P_ABORT_ind, MAP_U_ABORT_ind, MAP_CLOSE_ind' path leads to a NULL state. A 'MAP_AUTHENTICATION_FAILURE_REPORT_ind' path leads to 'MAP_NOTICE_ind', which then leads to 'MAP_CLOSE_req' and a NULL state. A central path from the decision point leads to a block with 'MAP_OPEN_req, MAP_AUTHENTICATION_FAILURE_REPORT_req, MAP_DELIMITER_req', which then leads to 'Receive_Open_cnf' (Section 25.1). From 'Receive_Open_cnf', an 'OK' path leads to 'WAIT_FOR_RESPONSE' and a 'Vr, Error' path leads to 'MAP_U_ABORT_req' and a NULL state.](223792b3652794024244c277cc46394b_img.jpg) + +### Process Authentication\_Failure\_Report\_GLR + +25.3.2\_1(2) + +Figure 25.3.2/1: The Process to notify authentication failure report from the VLR/SGSN to the HLR via the GLR + +Left from/to VLR or SGSN +Right from/to HLR + +``` +graph TD; Start([ ]) --> NULL1([NULL]); NULL1 --> Receive_Open_ind[Receive_Open_ind]; Receive_Open_ind --- Section25_1_1[Section 25.1]; Receive_Open_ind -- OK --> Wait_For_Service_Primitive[Wait_For_Service_Primitive]; Receive_Open_ind -- "Vr, Error" --> NULL2([NULL]); Wait_For_Service_Primitive --> Decision1{ }; Decision1 -- "MAP_P_ABORT_ind, MAP_U_ABORT_ind, MAP_CLOSE_ind" --> NULL3([NULL]); Decision1 -- "MAP_AUTHENTICATION_FAILURE_REPORT_ind" --> MAP_NOTICE_ind[MAP_NOTICE_ind]; MAP_NOTICE_ind --> MAP_CLOSE_req{MAP_CLOSE_req}; MAP_CLOSE_req --> NULL4([NULL]); Decision1 --> Decision2{ }; Decision2 -- "MAP_OPEN_req, MAP_AUTHENTICATION_FAILURE_REPORT_req, MAP_DELIMITER_req" --> Receive_Open_cnf[Receive_Open_cnf]; Receive_Open_cnf --- Section25_1_2[Section 25.1]; Receive_Open_cnf -- OK --> WAIT_FOR_RESPONSE[WAIT_FOR_RESPONSE]; Receive_Open_cnf -- "Vr, Error" --> MAP_U_ABORT_req{MAP_U_ABORT_req}; MAP_U_ABORT_req --> NULL5([NULL]); +``` + +Flowchart for Process Authentication\_Failure\_Report\_GLR. The process starts with an initial state leading to a NULL state. It then enters a 'Receive\_Open\_ind' block (Section 25.1). From here, an 'OK' path leads to 'Wait\_For\_Service\_Primitive', which then leads to a decision point. A 'Vr, Error' path from 'Receive\_Open\_ind' leads to a NULL state. From the decision point, a 'MAP\_P\_ABORT\_ind, MAP\_U\_ABORT\_ind, MAP\_CLOSE\_ind' path leads to a NULL state. A 'MAP\_AUTHENTICATION\_FAILURE\_REPORT\_ind' path leads to 'MAP\_NOTICE\_ind', which then leads to 'MAP\_CLOSE\_req' and a NULL state. A central path from the decision point leads to a block with 'MAP\_OPEN\_req, MAP\_AUTHENTICATION\_FAILURE\_REPORT\_req, MAP\_DELIMITER\_req', which then leads to 'Receive\_Open\_cnf' (Section 25.1). From 'Receive\_Open\_cnf', an 'OK' path leads to 'WAIT\_FOR\_RESPONSE' and a 'Vr, Error' path leads to 'MAP\_U\_ABORT\_req' and a NULL state. + +Figure 25.3.2/1 (sheet 1 of 2): Process Authentication\_Failure\_Report\_GLR + +![State transition diagram for Process Authentication_Failure_Report_GLR. The diagram shows two main sections. The top section starts with a 'WAIT_FOR_RESPONSE' state, leading to a horizontal transition line. Below this line are three parallel paths: 1) 'MAP_AUTHENTICATION_FAILURE_REPORT_cnf' (indicated by a right-pointing chevron) leads to a 'MAP_AUTHENTICATION_FAILURE_REPORT_cnf' request (diamond), which then leads to a 'NULL' state (oval). 2) 'MAP_CLOSE_ind' (indicated by a right-pointing chevron) leads to a 'MAP_CLOSE_req' request (diamond), which then leads to a 'NULL' state. 3) 'MAP_CLOSE_ind' (indicated by a left-pointing chevron) leads to a 'MAP_CLOSE_req' request (diamond), which then leads to a 'NULL' state. The bottom section starts with a horizontal transition line. Below this line are four parallel paths: 1) 'MAP_NOTICE_ind' (indicated by a right-pointing chevron) leads to a 'MAP_CLOSE_req' request (diamond), which leads to a 'MAP_U_ABORT_req' request (diamond), which then leads to a 'NULL' state. 2) 'MAP_NOTICE_ind' (indicated by a left-pointing chevron) leads to a 'MAP_CLOSE_req' request (diamond), which leads to a 'MAP_U_ABORT_req' request (diamond), which then leads to a 'NULL' state. 3) 'MAP_P_ABORT_ind' and 'MAP_U_ABORT_ind' (indicated by a right-pointing chevron) lead to a 'MAP_U_ABORT_req' request (diamond), which then leads to a 'NULL' state. 4) 'MAP_P_ABORT_ind' and 'MAP_U_ABORT_ind' (indicated by a left-pointing chevron) lead to a 'MAP_U_ABORT_req' request (diamond), which then leads to a 'NULL' state.](b55cd9b5721bd8aabc979c85316924e4_img.jpg) + +**Process Authentication\_Failure\_Report\_GLR** 25.3.2\_2(2) + +Figure 25.3.2/1: The Process to notify authentication failure report from the VLR/SGSN to the HLR via the GLR + +Left from/to VLR or SGSN +Right from/to HLR + +State transition diagram for Process Authentication\_Failure\_Report\_GLR. The diagram shows two main sections. The top section starts with a 'WAIT\_FOR\_RESPONSE' state, leading to a horizontal transition line. Below this line are three parallel paths: 1) 'MAP\_AUTHENTICATION\_FAILURE\_REPORT\_cnf' (indicated by a right-pointing chevron) leads to a 'MAP\_AUTHENTICATION\_FAILURE\_REPORT\_cnf' request (diamond), which then leads to a 'NULL' state (oval). 2) 'MAP\_CLOSE\_ind' (indicated by a right-pointing chevron) leads to a 'MAP\_CLOSE\_req' request (diamond), which then leads to a 'NULL' state. 3) 'MAP\_CLOSE\_ind' (indicated by a left-pointing chevron) leads to a 'MAP\_CLOSE\_req' request (diamond), which then leads to a 'NULL' state. The bottom section starts with a horizontal transition line. Below this line are four parallel paths: 1) 'MAP\_NOTICE\_ind' (indicated by a right-pointing chevron) leads to a 'MAP\_CLOSE\_req' request (diamond), which leads to a 'MAP\_U\_ABORT\_req' request (diamond), which then leads to a 'NULL' state. 2) 'MAP\_NOTICE\_ind' (indicated by a left-pointing chevron) leads to a 'MAP\_CLOSE\_req' request (diamond), which leads to a 'MAP\_U\_ABORT\_req' request (diamond), which then leads to a 'NULL' state. 3) 'MAP\_P\_ABORT\_ind' and 'MAP\_U\_ABORT\_ind' (indicated by a right-pointing chevron) lead to a 'MAP\_U\_ABORT\_req' request (diamond), which then leads to a 'NULL' state. 4) 'MAP\_P\_ABORT\_ind' and 'MAP\_U\_ABORT\_ind' (indicated by a left-pointing chevron) lead to a 'MAP\_U\_ABORT\_req' request (diamond), which then leads to a 'NULL' state. + +**Figure 25.3.2/2 (sheet 2 of 2): Process Authentication\_Failure\_Report\_GLR** + +## 25.4 Short Message Alert procedures + +### 25.4.1 Subscriber\_Present\_GLR\_AS\_VLR process + +The Subscriber\_Present\_GLR\_AS\_VLR process is invoked by the GLR, when GLR receives Update Location from VLR and the MNRF flag is set. The general description of the short message alert procedures is in the subclause 23.3. + +The GLR sends the MAP\_READY\_FOR\_SM request to the HLR and waits for the HLR to answer. When receiving the answer, the GLR will act as follows: + +- the MNRF flag is cleared if the procedure is successful; +- the MNRF flag is not cleared if the procedure is not successful. + +The Subscriber\_Present\_GLR\_AS\_VLR process is shown in the figure 25.4/1. + +#### Process Subscriber\_Present\_GLR\_AS\_VLR + +25.4.1(1) + +Figure 25.4/1: The short message alert process in the GLR for mobile present situation + +![Flowchart for Process Subscriber_Present_GLR_AS_VLR. It starts with a decision 'MNRF set'. If 'No', it goes to an 'Error' state. If 'Yes', it sends 'MAP_OPEN_req', 'MAP_READY_FOR_SM_req', and 'MAP_DELIMITER_req', then receives 'Open_cnf' (referencing Section 25.1). It then reaches a 'WF_RESPONSE' node. From there, it branches into 'Perform_MAP_V1_Dialogue' (leading to 'V1' state), 'MAP_READY_FOR_SM_rsp' (leading to an 'Error' decision), and 'MAP_P_ABORT_ind', 'MAP_U_ABORT_ind', 'MAP_CLOSE_ind' (leading to an 'X' state). If the 'Error' decision is 'Yes', it goes to an 'X' state. If 'No', it performs 'Clear MNRF' and then goes to an 'X' state.](eefcb3f73fb33cce57cd04109c81506f_img.jpg) + +``` +graph TD; Start([ ]) --> MNRF{MNRF set}; MNRF -- No --> Error[Error]; MNRF -- Yes --> Req["MAP_OPEN_req
MAP_READY_FOR_SM_req
MAP_DELIMITER_req"]; Req --> OpenCnf["Receive_Open_cnf
Section 25.1"]; OpenCnf --> WF_RESPONSE((WF_RESPONSE)); WF_RESPONSE --> Perform["Perform_MAP_V1_Dialogue"]; WF_RESPONSE --> ReadyRsp["MAP_READY_FOR_SM_rsp"]; WF_RESPONSE --> AbortInd["MAP_P_ABORT_ind
MAP_U_ABORT_ind
MAP_CLOSE_ind"]; Perform --> V1[V1]; ReadyRsp --> ErrorDecision{Error}; ErrorDecision -- Yes --> X1[X]; ErrorDecision -- No --> ClearMNRF[Clear MNRF]; ClearMNRF --> X2[X]; AbortInd --> X3[X]; +``` + +Flowchart for Process Subscriber\_Present\_GLR\_AS\_VLR. It starts with a decision 'MNRF set'. If 'No', it goes to an 'Error' state. If 'Yes', it sends 'MAP\_OPEN\_req', 'MAP\_READY\_FOR\_SM\_req', and 'MAP\_DELIMITER\_req', then receives 'Open\_cnf' (referencing Section 25.1). It then reaches a 'WF\_RESPONSE' node. From there, it branches into 'Perform\_MAP\_V1\_Dialogue' (leading to 'V1' state), 'MAP\_READY\_FOR\_SM\_rsp' (leading to an 'Error' decision), and 'MAP\_P\_ABORT\_ind', 'MAP\_U\_ABORT\_ind', 'MAP\_CLOSE\_ind' (leading to an 'X' state). If the 'Error' decision is 'Yes', it goes to an 'X' state. If 'No', it performs 'Clear MNRF' and then goes to an 'X' state. + +Figure 25.4/1: Process Subscriber\_Present\_GLR\_AS\_VLR + +### 25.4.2 The Mobile Subscriber is present + +When GLR receives Update GPRS Location from SGSN, while the MS not reachable for GPRS (MNRG) flag is set, the GLR will send the MAP\_READY\_FOR\_SM request towards the HLR. The Alert Reason is set to indicate that the mobile subscriber is present for GPRS. + +When receiving the answer, the GLR will act as follows: + +- MNRG is cleared if the procedure is successful. +- MNRG is not cleared if the procedure is not successful. + +The Subscriber\_Present\_GLR\_AS\_SGSN process is shown in the figure 25.4/2. + +#### Process Subscriber\_Present\_GLR\_AS\_SGSN + +25.4.2(1) + +Figure 25.4/2: The short message alert process in the GLR for mobile present situation + +![Flowchart for Process Subscriber_Present_GLR_AS_SGSN. It starts with a decision 'MNRG set'. If 'No', it ends. If 'Yes', it sends 'MAP_OPEN_req', 'MAP_READY_FOR_SM_req', and 'MAP_DELIMITER_req', then receives 'Open_cnf' (Section 25.1). It then checks 'WF_RESPONSE'. If 'Error', it ends. If 'V1', it performs 'MAP_V1_Dialogue' and ends. If 'OK', it receives 'MAP_READY_FOR_SM_rsp' and checks for 'Error'. If 'Error' is 'Yes', it ends. If 'Error' is 'No', it performs 'Clear MNRG' and ends. If no error is received, it sends 'MAP_P_ABORT_ind', 'MAP_U_ABORT_ind', and 'MAP_CLOSE_ind' and ends.](8aafdc3df2af4882f3c1b5e1e7e8dc8a_img.jpg) + +``` +graph TD; Start([ ]) --> MNRG_set{MNRG set}; MNRG_set -- No --> End1(( )); MNRG_set -- Yes --> SendReq[MAP_OPEN_req
MAP_READY_FOR_SM_req
MAP_DELIMITER_req]; SendReq --> ReceiveOpenCnf[Receive_Open_cnf]; ReceiveOpenCnf -- Section 25.1 --> WF_RESPONSE{WF_RESPONSE}; WF_RESPONSE -- Error --> End2(( )); WF_RESPONSE -- V1 --> PerformV1[Perform_MAP_V1_Dialogue]; PerformV1 --> End3(( )); WF_RESPONSE -- OK --> ReceiveRsp[MAP_READY_FOR_SM_rsp]; ReceiveRsp --> ErrorCheck{Error}; ErrorCheck -- Yes --> End4(( )); ErrorCheck -- No --> ClearMNRG[Clear MNRG]; ClearMNRG --> End5(( )); ClearMNRG --> SendInd[MAP_P_ABORT_ind
MAP_U_ABORT_ind
MAP_CLOSE_ind]; SendInd --> End6(( )); +``` + +Flowchart for Process Subscriber\_Present\_GLR\_AS\_SGSN. It starts with a decision 'MNRG set'. If 'No', it ends. If 'Yes', it sends 'MAP\_OPEN\_req', 'MAP\_READY\_FOR\_SM\_req', and 'MAP\_DELIMITER\_req', then receives 'Open\_cnf' (Section 25.1). It then checks 'WF\_RESPONSE'. If 'Error', it ends. If 'V1', it performs 'MAP\_V1\_Dialogue' and ends. If 'OK', it receives 'MAP\_READY\_FOR\_SM\_rsp' and checks for 'Error'. If 'Error' is 'Yes', it ends. If 'Error' is 'No', it performs 'Clear MNRG' and ends. If no error is received, it sends 'MAP\_P\_ABORT\_ind', 'MAP\_U\_ABORT\_ind', and 'MAP\_CLOSE\_ind' and ends. + +Figure 25.4/2: Process Subscriber\_Present\_GLR\_AS\_SGSN + +# Annex A (informative): Change history + +| Change history | | | | | | | +|----------------|--------|---------|-------|---------|-------------|----------------------------------------------------------| +| TSG CN# | Spec | Version | CR | | New Version | Subject/Comment | +| CN#07 | 29.120 | 2.0.0 | | R99 | 3.0.0 | Approved at TSGN#07 | +| CN#09 | 29.120 | 3.0.0 | 001r1 | R99 | 3.1.0 | Changes to support Authentication Failure Report for GLR | +| CN#09 | 29.120 | 3.1.0 | 002 | Rel-4 | 4.0.0 | Changes to support secure transport MAP for GLR | +| CN#16 | 29.120 | 4.0.0 | | Rel-5 | 5.0.0 | Rel-5 created after CN#16 | +| CN#26 | 29.120 | 5.0.0 | | Rel-6 | 6.0.0 | Rel-6 created after CN#26 | +| CT#36 | 29.120 | 6.0.0 | | Rel-7 | 7.0.0 | Upgraded unchanged from Rel-6 | +| CT#42 | 29.120 | 7.0.0 | | Rel-8 | 8.0.0 | Upgraded unchanged from Rel-7 | +| 2009-12 | 29.120 | 8.0.0 | - | Rel-9 | 9.0.0 | Update to Rel-9 version (MCC) | +| 2011-03 | 29.120 | 9.0.0 | - | Rel-10 | 10.0.0 | Update to Rel-10 version (MCC) | +| 2012-09 | 29.120 | 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/29_series/29139/1d27fed9c01eb99f6535283f35fe3bbf_img.jpg b/marked/Rel-11/29_series/29139/1d27fed9c01eb99f6535283f35fe3bbf_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b95ab17704d6b63d76d4198f02665d1badbed996 --- /dev/null +++ b/marked/Rel-11/29_series/29139/1d27fed9c01eb99f6535283f35fe3bbf_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d9dbde56316da893929275126866dff2efe95d96158fd0382421bb3b860eca94 +size 38726 diff --git a/marked/Rel-11/29_series/29139/43fec6623ab9cb223a9ff74e2d2a4402_img.jpg b/marked/Rel-11/29_series/29139/43fec6623ab9cb223a9ff74e2d2a4402_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..49a0adf277c9177d21f57fbcf4120d1f776b4418 --- /dev/null +++ b/marked/Rel-11/29_series/29139/43fec6623ab9cb223a9ff74e2d2a4402_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:68dc959bf2ee8e603c84ce4f6c2a59cabbf7f76172776f4ff483f6f8bbd02254 +size 28973 diff --git a/marked/Rel-11/29_series/29139/49ee89a1d5852ab005dbbab6de09a8a6_img.jpg b/marked/Rel-11/29_series/29139/49ee89a1d5852ab005dbbab6de09a8a6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3767ea40983cb164b8dc0e6801e4156ac983f302 --- /dev/null +++ b/marked/Rel-11/29_series/29139/49ee89a1d5852ab005dbbab6de09a8a6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:372126e7ca5e9fec6ab5d6bd7fce06ba8415e3959fc1d01feff16fd8f673eb41 +size 46582 diff --git a/marked/Rel-11/29_series/29139/9791722d75115ddcc599b07d7bc35d73_img.jpg b/marked/Rel-11/29_series/29139/9791722d75115ddcc599b07d7bc35d73_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..24d9db8a321427f4b0aeedefab3c1f0328a6d85d --- /dev/null +++ b/marked/Rel-11/29_series/29139/9791722d75115ddcc599b07d7bc35d73_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c78700beb8966b61cd51a9d76c07a3a278a76a5b0878935cd6d332f6a6e8640b +size 28339 diff --git a/marked/Rel-11/29_series/29139/raw.md b/marked/Rel-11/29_series/29139/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..4b8801b138bf28ed59281f9ba8b5f26a6bffe5f7 --- /dev/null +++ b/marked/Rel-11/29_series/29139/raw.md @@ -0,0 +1,331 @@ + + + + + + +# Contents + +| | | +|----------------------------------------------------------------------|----| +| Foreword ..... | 4 | +| 1 Scope..... | 5 | +| 2 References..... | 5 | +| 3 Definitions and abbreviations ..... | 5 | +| 3.1 Definitions..... | 5 | +| 3.2 Abbreviations ..... | 6 | +| 4 General..... | 6 | +| 4.1 Protocol Stack ..... | 6 | +| 4.1.1 Control Plane for H(e)NB – SeGW ..... | 6 | +| 4.1.2 User Plane for H(e)NB – SeGW ..... | 7 | +| 5 Supporting QoS..... | 8 | +| 5.1 General ..... | 8 | +| 5.2 H(e)NB procedures ..... | 8 | +| 5.2.1 General ..... | 8 | +| 5.2.2 QCI mapping ..... | 8 | +| 5.2.3 Reflective QoS..... | 8 | +| 5.3 SeGW procedures..... | 8 | +| 6 Tunnel Management ..... | 8 | +| 6.1 General ..... | 8 | +| 6.2 H(e)NB procedures ..... | 9 | +| 6.2.1 Tunnel establishment..... | 9 | +| 6.2.1.1 IP address allocation ..... | 9 | +| 6.2.1.2 NAT Traversal..... | 9 | +| 6.2.1.3 H(e)NB NATed Tunnel-IP address discovery..... | 9 | +| 6.2.2 Tunnel modification ..... | 9 | +| 6.2.3 Tunnel disconnection..... | 9 | +| 6.3 SeGW procedures..... | 9 | +| 6.3.1 Tunnel establishment..... | 9 | +| 6.3.1.1 IP address allocation ..... | 9 | +| 6.3.1.2 NAT Traversal..... | 10 | +| 6.3.1.3 H(e)NB NATed Tunnel-IP address discovery..... | 10 | +| 6.3.2 Tunnel modification ..... | 10 | +| 6.3.3 Tunnel disconnection..... | 10 | +| 7 PDUs and parameters specific to the present document ..... | 10 | +| 7.1 IETF RFC coding information defined within present document..... | 10 | +| 7.1.1 IKEv2 Configuration Payloads attributes..... | 10 | +| 7.1.1.1 EXTERNAL_SOURCE_IP4_NAT_INFO attribute ..... | 10 | +| Annex A (informative): Change history..... | 12 | + +# --- Foreword + +This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +# --- 1 Scope + +The present document specifies the H(e)NB – SeGW interface. The interface is used for the interworking between a 3GPP system and a Fixed Broadband Access network defined by Broadband Forum. The interworking procedure provides the IP connectivity to a 3GPP UE using a H(e)NB connected to a Fixed Broadband Access network as specified in 3GPP TS 23.139 [2]. + +The specification covers the QoS aspects and Tunnel management procedures. + +# --- 2 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. + - For a specific reference, subsequent revisions do not apply. + - For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. +- [1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications". +- [2] 3GPP TS 23.139: "3GPP System-Fixed Broadband Access Network Interworking; Stage 2". +- [3] 3GPP TS 24.139: "3GPP System-Fixed Broadband Access Network Interworking; Stage 3". +- [4] IETF RFC 2474 (December 1998): "Definition of the Differentiated Services Field (DS Field) in the IPv4 and IPv6 Headers". +- [5] IETF RFC 5996: "Internet Key Exchange Protocol Version 2 (IKEv2)". +- [6] IETF RFC 3948: "UDP Encapsulation of IPsec ESP Packets". +- [7] 3GPP TS 33.320: "Security of Home Node B (HNB) / Home evolved Node B (HeNB)". + +# --- 3 Definitions and abbreviations + +## 3.1 Definitions + +For the purposes of the present document, the terms and definitions given in TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905 [1]. + +**H(e)NB Reflective QoS function:** H(e)NB Reflective QoS function is a H(e)NB function in order to support QoS for uplink traffic over a Fixed Broadband Access network as specified in 3GPP TS 23.139 [2]. + +**H(e)NB local IP address Info:** H(e)NB local IP address Info is defined as either the public IPv4 address or IPv6 address assigned to the H(e)NB by the Fixed Broadband Access Network domain, or the public IPv4 address and the UDP port number used by the NATed RG that is used for this H(e)NB. The public IPv4 address used by the NATed RG is assigned by the Fixed Broadband Access Network domain. + +## 3.2 Abbreviations + +For the purposes of the present document, the abbreviations given in TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905 [1]. + +| | | +|--------|------------------------------------| +| DSCP | Differentiated Services Code Point | +| H(e)NB | Home (e)NodeB | + +| | | +|-------|-----------------------------| +| NAT | Network Address Translation | +| NAT-T | NAT Traversal | +| SeGW | Security Gateway | + +# 4 General + +## 4.1 Protocol Stack + +### 4.1.1 Control Plane for H(e)NB – SeGW + +![Diagram of control plane protocol stack for IPv4 transport network between H(e)NB and SeGW via NAT.](1d27fed9c01eb99f6535283f35fe3bbf_img.jpg) + +The diagram illustrates the control plane protocol stack for an IPv4 transport network. It shows three main components: H(e)NB on the left, NAT in the center, and SeGW on the right. The H(e)NB and SeGW both have a vertical stack of five protocols: IKEv2, UDP, IPv4, L2, and L1. The NAT component is represented by a dashed box containing two parallel vertical stacks of four protocols: UDP, IPv4, L2, and L1. Horizontal lines connect the IKEv2, UDP, IPv4, L2, and L1 layers of the H(e)NB to the corresponding layers in the NAT box, and from the NAT box to the corresponding layers in the SeGW. The IKEv2 layers at the H(e)NB and SeGW are connected by a single horizontal line that bypasses the NAT box. + +Diagram of control plane protocol stack for IPv4 transport network between H(e)NB and SeGW via NAT. + +#### **Legend:** + +- **IKEv2 Protocol:** This protocol is used to between H(e)NB and SeGW. The IKEv2 protocol is defined in IETF RFC 5996 [5]. + +**Figure 4.1.1-1: Control Plane for H(e)NB - SeGW Interface over IPv4 transport network** + +![Diagram of control plane protocol stack for IPv6 transport network between H(e)NB and SeGW.](43fec6623ab9cb223a9ff74e2d2a4402_img.jpg) + +The diagram illustrates the control plane protocol stack for an IPv6 transport network. It shows two main components: H(e)NB on the left and SeGW on the right. Both have a vertical stack of five protocols: IKEv2, UDP, IPv6, L2, and L1. Horizontal lines connect the IKEv2, UDP, IPv6, L2, and L1 layers of the H(e)NB directly to the corresponding layers in the SeGW. The IKEv2 layers are connected by a single horizontal line at the top of the stack. + +Diagram of control plane protocol stack for IPv6 transport network between H(e)NB and SeGW. + +#### **Legend:** + +- **IKEv2 Protocol:** This protocol is used to between H(e)NB and SeGW. The IKEv2 protocol is defined in RFC 5996 [5]. + +**Figure 4.1.1-2: Control Plane for H(e)NB - SeGW Interface over IPv6 transport network** + +### 4.1.2 User Plane for H(e)NB – SeGW + +![Diagram of User Plane for H(e)NB - SeGW Interface over IPv4 transport network with NAT](49ee89a1d5852ab005dbbab6de09a8a6_img.jpg) + +The diagram illustrates the user plane protocol stack for H(e)NB and SeGW over an IPv4 transport network with NAT. The stack layers are shown in a table format: + +| | | | | +|---------|------|------|---------| +| Payload | | | Payload | +| IPsec | | | IPsec | +| UDP | UDP | UDP | UDP | +| IPv4 | IPv4 | IPv4 | IPv4 | +| L2 | L2 | L2 | L2 | +| L1 | L1 | L1 | L1 | + +The H(e)NB and SeGW stacks are connected via a NAT box (dashed line) that contains two parallel paths for UDP and IPv4. The NAT box is labeled 'NAT'. + +Diagram of User Plane for H(e)NB - SeGW Interface over IPv4 transport network with NAT + +#### **Legend:** + +- **UDP:** UDP encapsulation is used if NAT is detected between the H(e)NB and the SeGW. + +**Figure 4.1.2-1: User Plane for H(e)NB - SeGW Interface over IPv4 transport network** + +![Diagram of User Plane for H(e)NB - SeGW Interface over IPv6 transport network](9791722d75115ddcc599b07d7bc35d73_img.jpg) + +The diagram illustrates the user plane protocol stack for H(e)NB and SeGW over an IPv6 transport network. The stack layers are shown in a table format: + +| | | +|---------|---------| +| Payload | Payload | +| IPsec | IPsec | +| IPv6 | IPv6 | +| L2 | L2 | +| L1 | L1 | + +The H(e)NB and SeGW stacks are directly connected. The H(e)NB is on the left and the SeGW is on the right. + +Diagram of User Plane for H(e)NB - SeGW Interface over IPv6 transport network + +**Figure 4.1.2-2: User Plane for H(e)NB - SeGW Interface over IPv6 transport network** + +# 5 Supporting QoS + +## 5.1 General + +At interworking with a Fixed Broadband Access network, QoS is provided by DSCP marking as specified in IETF RFC 2474 [4]. + +## 5.2 H(e)NB procedures + +### 5.2.1 General + +The H(e)NB shall support DSCP marking on the IPsec header when forwarding the UE uplink traffic. + +Based on H(e)NB configuration either the QCI mapping or the Reflective QoS may be used. + +### 5.2.2 QCI mapping + +The QCI mapping table contains a one-to-one mapping from QCI value to DSCP marking value. The QCI mapping table is configured in the H(e)NB by the operator. + +When forwarding an uplink IP packet, the H(e)NB shall perform a lookup in the QCI mapping table based on the QCI value of the EPS bearer/PDP context before the IPsec tunnel encapsulation. The H(e)NB shall set the DSCP marking value of the IPsec header according to the matched QCI mapping table entry. + +### 5.2.3 Reflective QoS + +To support the H(e)NB Reflective QoS function for uplink traffic, the H(e)NB shall create and maintain the uplink DSCP marking rules for each active PDN connection as specified for UE Reflective QoS function in 3GPP TS 24.139 [3]. + +When forwarding an uplink IP packet, the H(e)NB shall perform a lookup in the DSCP marking table based on the n-tuple of the IP header before the IPsec tunnel encapsulation. If a matching entry is found, the H(e)NB shall set the DSCP marking value of the IPsec header according to the matched DSCP marking rule. If no matching entry is found, the H(e)NB shall copy the DSCP field of the outer IP header into the IPsec header before forwarding to the SeGW. + +## 5.3 SeGW procedures + +When receiving a downlink data packet, the SeGW shall copy the DSCP marking value from the outer IP header into the IPsec header before forwarding to the H(e)NB using the IPsec tunnel, as specified in 3GPP TR 23.139 [2]. + +# --- 6 Tunnel Management + +## 6.1 General + +The tunnel is an IPsec tunnel established via an IKEv2 protocol exchange IETF RFC 5996 [5] between the H(e)NB and the SeGW which is through the Fixed Broadband Access Network. + +In an IPv4 Fixed Broadband Access Network, NAT can be deployed between the H(e)NB and the SeGW, e.g. in a Residence Gateway. A H(e)NB behind the NAT shall invoke the NAT traversal procedure for IKEv2. The IPsec tunnel is encapsulated over UDP in the Tunnel-Mode as specified in IETF RFC 5996 [5]. + +## 6.2 H(e)NB procedures + +### 6.2.1 Tunnel establishment + +#### 6.2.1.1 IP address allocation + +The SeGW shall provide the IP address to the H(e)NB for the communication with the EPC network. + +For dynamic IP address allocation, the H(e)NB shall include the requested IP address type (IPv4 address or IPv6 address) that needs to be configured in an IKEv2 CFG\_REQUEST Configuration Payload in the IKE\_AUTH request message as defined in IETF RFC 5996 [5] after reception of the IKE\_SA\_INIT response from the SeGW. + +#### 6.2.1.2 NAT Traversal + +NAT can be deployed in an IPv4 Fixed Broadband Access Network. IKEv2 NAT Traversal specified in section 2.23 of IETF RFC 5996 [5] shall be supported by H(e)NB. + +If NAT is detected between the H(e)NB and SeGW, the following procedures shall be performed: + +- UDP-Encapsulated ESP as defined in IETF RFC 5996 [5]; +- sending the NAT-keepalive packet to keep NAT mapping alive if no other packet to the SeGW has been sent in M seconds as defined in the IETF RFC 3948 [6]; + +NOTE: M is a locally configurable parameter with a default value of 20 seconds as defined in the IETF RFC 3948 [6]. + +#### 6.2.1.3 H(e)NB NATed Tunnel-IP address discovery + +If NAT is detected between the H(e)NB and SeGW, the H(e)NB shall request the SeGW to return the H(e)NB local IP address information by including the EXTERNAL\_SOURCE\_IP4\_NAT\_INFO attribute as defined in subclause 7.1.1.1 + +in the CFG\_REQUEST Configuration Payload within the IKE\_AUTH request message. The length field of the attribute shall be set to zero. The NATed IPv4 Address field and UDP Port number field shall be absent. + +If the H(e)NB subsequently receives the EXTERNAL\_SOURCE\_IP4\_NAT\_INFO attribute in the CFG\_REPLY configuration payload from the SeGW, the H(e)NB shall report the IP address received in EXTERNAL\_SOURCE\_IP4\_NAT\_INFO attribute as the H(e)NB local IP address to the MME/SGSN. + +### 6.2.2 Tunnel modification + +NAT mappings can change when the UDP port number is reassigned by the NAT, and/or H(e)NB local IP address is reallocated due to NAT restart. + +Upon NAT remapping, the SeGW initiates the tunnel disconnection procedure as specified in subclause 6.3.3. Then the H(e)NB shall re-initiate the tunnel establishment procedure as specified in sub-clause 6.2.1. + +### 6.2.3 Tunnel disconnection + +The H(e)NB shall use the procedures defined in IETF RFC 5996 [5] to disconnect an IPsec tunnel to the SeGW. + +## 6.3 SeGW procedures + +### 6.3.1 Tunnel establishment + +#### 6.3.1.1 IP address allocation + +For dynamic IP address allocation, upon receipt of an IKE\_AUTH request message from the H(e)NB requesting the IP address, the SeGW shall include the remote IP address information in the IKEv2 Configuration Payload (CFG\_REPLY) of the final IKE\_AUTH response message to the H(e)NB. The SeGW shall assign either an IPv4 or an IPv6 address to the H(e)NB via a single CFG\_REPLY Configuration Payload. + +#### 6.3.1.2 NAT Traversal + +NAT can be deployed in an IPv4 Fixed Broadband Access Network. IKEv2 NAT Traversal specified in section 2.23 of IETF RFC 5996 [5] shall be supported by SeGW. + +If NAT is detected between the H(e)NB and SeGW, the SeGW shall use UDP-Encapsulated ESP as defined in IETF RFC 5996 [5]. + +#### 6.3.1.3 H(e)NB NATed Tunnel-IP address discovery + +If the SeGW receives the EXTERNAL\_SOURCE\_IP4\_NAT\_INFO attribute as defined in subclause 7.1.1.1 in the CFG\_REQUEST configuration payload within IKE\_AUTH request message, the SeGW shall provide the H(e)NB local IP address information (i.e. NATed IPv4 address and UDP port number) to the H(e)NB by including the EXTERNAL\_SOURCE\_IP4\_NAT\_INFO attribute in the CFG\_REPLY configuration payload within the IKE\_AUTH response message. + +### 6.3.2 Tunnel modification + +NAT mappings can change when the UDP port number is reassigned by the NAT, and/or H(e)NB local IP address is reallocated due to NAT restart. + +If NAT remapping is detected by the SeGW, the SeGW shall initiate the tunnel disconnection procedure (see subclause 6.3.3). + +NOTE: No procedures are defined in current release of specification to enable the SeGW to send the modified H(e)NB local IP address information to the H(e)NB during the lifetime of IKEv2 security association. + +### 6.3.3 Tunnel disconnection + +The SeGW shall use the procedures defined in IETF RFC 5996 [5] to disconnect an IPsec tunnel to the H(e)NB. + +# 7 PDUs and parameters specific to the present document + +## 7.1 IETF RFC coding information defined within present document + +### 7.1.1 IKEv2 Configuration Payloads attributes + +#### 7.1.1.1 EXTERNAL\_SOURCE\_IP4\_NAT\_INFO attribute + +The format of the EXTERNAL\_SOURCE\_IP4\_NAT\_INFO attribute follows the definition of Configuration Attributes as specified in IETF RFC 5996 [5], section 3.15.1. The format is shown in figure 7.1.1.1-1 as below. The length of the EXTERNAL\_SOURCE\_IP4\_NAT\_INFO attribute is 0 or 6 bytes. + +| 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 | Octets | | | | | | | | +|--------------------|----------------|---|---|---|---|---|---|--------|--|--|--|--|--|--|--| +| R | Attribute Type | | | | | | | 1 | | | | | | | | +| Attribute Type | | | | | | | | 2 | | | | | | | | +| Length | | | | | | | | 3, 4 | | | | | | | | +| NATed IPv4 Address | | | | | | | | 5 - 8 | | | | | | | | +| UDP Port number | | | | | | | | 9 - 10 | | | | | | | | + +Figure 7.1.1.1-1: EXTERNAL\_SOURCE\_IP4\_NAT\_INFO attribute + +The R bit in the first octet is as defined in IETF RFC 5996 [5]. + +The Attribute Type indicating EXTERNAL\_SOURCE\_IP4\_NAT\_INFO is of the value 23. + +# Annex A (informative): Change history + +| Change history | | | | | | | | +|----------------|-------|-----------|------|-----|------------------------------------------------------------------------------------------------|--------|--------| +| Date | TSG # | TSG Doc. | CR | Rev | Subject/Comment | Old | New | +| 2012-12 | CT#58 | CP-120895 | | | V2.0.0 presented for approval | 2.0.0 | 11.0.0 | +| 2012-12 | CT#58 | CP-120697 | 0001 | - | Removal of invalid reference and editor's note | 11.0.0 | 11.1.0 | +| 2016-03 | CT#71 | CP-160019 | 0002 | 1 | Complete the EXTERNAL_SOURCE_IP4_NAT_INFO attribute information according to IANA registration | 11.1.0 | 11.2.0 | +| | | | | | | | | +| | | | | | | | | +| | | | | | | | | +| | | | | | | | | +| | | | | | | | | +| | | | | | | | | +| | | | | | | | | \ No newline at end of file diff --git a/marked/Rel-11/29_series/29161/27b06ec9f42b5d727a2630f61a5f1861_img.jpg b/marked/Rel-11/29_series/29161/27b06ec9f42b5d727a2630f61a5f1861_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..93f78d9113b364811726c946ecc4dc547f0f4ffb --- /dev/null +++ b/marked/Rel-11/29_series/29161/27b06ec9f42b5d727a2630f61a5f1861_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9608391e60fa1d0ff1fc7c24291e3634d46cff5d0724638574c51fa53043eaf5 +size 57276 diff --git a/marked/Rel-11/29_series/29161/40f30e4d577a17052f8b1e6dc802a0d8_img.jpg b/marked/Rel-11/29_series/29161/40f30e4d577a17052f8b1e6dc802a0d8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..214d5da98120aead68ae972c821ff93a2be35b6e --- /dev/null +++ b/marked/Rel-11/29_series/29161/40f30e4d577a17052f8b1e6dc802a0d8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:013dd7a28db1f2eec1238b57da1fab938248f2b7497f202b8bae71e8f26bfe71 +size 87885 diff --git a/marked/Rel-11/29_series/29161/5a4e62bead259c258d069fd3663ea670_img.jpg b/marked/Rel-11/29_series/29161/5a4e62bead259c258d069fd3663ea670_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f3fca9af8ebe4d479d37595f80a1ee6e4651958f --- /dev/null +++ b/marked/Rel-11/29_series/29161/5a4e62bead259c258d069fd3663ea670_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1848b2a24e76958534d1851a8beba50c985100e9a08acbdcb9e29fd20b5f63b9 +size 71592 diff --git a/marked/Rel-11/29_series/29161/7efae06af3af43ffe5d4b956a679cf54_img.jpg b/marked/Rel-11/29_series/29161/7efae06af3af43ffe5d4b956a679cf54_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9f95c3665fa1861bf300df8de463dd3d65b523c4 --- /dev/null +++ b/marked/Rel-11/29_series/29161/7efae06af3af43ffe5d4b956a679cf54_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ae421e871716d079fd8812a8aa685fe1219aafb824f07feb38bda7805b055a4d +size 59845 diff --git a/marked/Rel-11/29_series/29161/8307f6b04df072c9332f9987e034272c_img.jpg b/marked/Rel-11/29_series/29161/8307f6b04df072c9332f9987e034272c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..15553b616a09fce32095fd35c204bf394027df51 --- /dev/null +++ b/marked/Rel-11/29_series/29161/8307f6b04df072c9332f9987e034272c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7e2460b6d8c5b4805fc1ffbea75f147759a7941b51024e6d9c4a08275681bd73 +size 90260 diff --git a/marked/Rel-11/29_series/29161/b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg b/marked/Rel-11/29_series/29161/b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0ec485ab7c39f92eb7c6ada80c05d95470cc43e3 --- /dev/null +++ b/marked/Rel-11/29_series/29161/b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b658535f61ddd45441021b44783e254e1e2253a7ee1a9243360b5f4bce225184 +size 81370 diff --git a/marked/Rel-11/29_series/29161/ff0952ef692c9d960ce5f6708bcc9711_img.jpg b/marked/Rel-11/29_series/29161/ff0952ef692c9d960ce5f6708bcc9711_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..102c5a9f229d4bd16b825fa8085c2b53d4c4eca1 --- /dev/null +++ b/marked/Rel-11/29_series/29161/ff0952ef692c9d960ce5f6708bcc9711_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:602dafb11e55fa01bd0da33794448104939748bb52397febd6e4b1e8efb77a1a +size 52010 diff --git a/marked/Rel-11/29_series/29161/raw.md b/marked/Rel-11/29_series/29161/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..cd2720fe9f7e9f77e0c6df1e345822d588506124 --- /dev/null +++ b/marked/Rel-11/29_series/29161/raw.md @@ -0,0 +1,741 @@ + + + + + + +# Contents + +| | | +|----------------------------------------------------------------------------|----| +| Foreword ..... | 5 | +| 1 Scope..... | 6 | +| 2 References..... | 6 | +| 3 Definitions, abbreviations and symbols ..... | 7 | +| 3.1 Definitions..... | 7 | +| 3.2 Abbreviations ..... | 7 | +| 3.3 Symbols..... | 8 | +| 4 Network characteristics..... | 8 | +| 4.1 Key characteristics of PLMN..... | 8 | +| 4.2 Key characteristics of IP Networks..... | 8 | +| 5 Interworking classifications ..... | 8 | +| 6 Access reference configuration..... | 8 | +| 7 Subscription checking..... | 8 | +| 8 Interworking with PDN (IP) ..... | 8 | +| 8.1 General ..... | 8 | +| 8.2 PDN Interworking Model..... | 8 | +| 8.2.1 Access to Internet, Intranet or ISP through Packet Domain..... | 9 | +| 8.2.1.1 Transparent access to the Internet..... | 9 | +| 8.2.1.2 IPv4 Non Transparent access to an Intranet or ISP ..... | 9 | +| 8.2.1.3 IPv6 Non Transparent access to an Intranet or ISP ..... | 10 | +| 8.2.1.3.1 Tunnel establishment and Intranet/ISP access authorization ..... | 11 | +| 8.2.1.3.2 IPv6 Stateless Address Autoconfiguration..... | 12 | +| 8.2.1.3.3 IPv6 Stateful Address Autoconfiguration ..... | 13 | +| 8.2.1.3.4 IPv6 Router Configuration Variables in the PDG..... | 14 | +| 8.3 Numbering and addressing..... | 14 | +| 8.4 Charging..... | 14 | +| 8.5 Domain Name System server (DNS Server)..... | 14 | +| 8.6 IP Multicast access ..... | 14 | +| 9 Interworking with PDN (DHCP) ..... | 15 | +| 9.1 General ..... | 15 | +| 9.2 Address allocation by the Intranet or ISP..... | 15 | +| 9.3 Other configuration by the Intranet or ISP (IPv6 only) ..... | 15 | +| 10 Interworking between Packet Domains ..... | 16 | +| 11 Usage of RADIUS on Wi interface..... | 16 | +| 11.1 RADIUS Authentication and Authorization ..... | 16 | +| 11.2 RADIUS Accounting ..... | 17 | +| 11.3 Authentication, Authorization and Accounting message flows..... | 17 | +| 11.4 List of RADIUS attributes..... | 19 | +| 11a Usage of Diameter on Wi interface..... | 19 | +| 11a.1 Diameter Authentication ..... | 19 | +| 11a.2 Diameter Accounting ..... | 20 | +| 11a.3 Authentication and accounting message flows ..... | 20 | +| 11a.4 Wi Diameter messages and AVPs..... | 21 | +| 12 Usage of RADIUS on Pp interface ..... | 21 | +| 12.1 General ..... | 21 | +| 12.2 Radius Profile for Pp interface ..... | 21 | +| 12.3 Interconnecting the Presence Network Agent and the PDG ..... | 22 | +| Annex A (informative): Change history..... | 23 | + +# --- Foreword + +This Technical Specification (TS) has been produced by the 3rd Generation Partnership Project (3GPP). + +The present document describes the network interworking for the Packet Domain. Interworking to various external networks is defined together with the interworking for data forwarding while subscribers roam within the 3GPP system. + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +# --- 1 Scope + +The present document defines the requirements for Packet Domain interworking between a: + +- a) PLMN with WLAN access and PDN; +- b) PLMN with WLAN access and PLMN. + +The present document also defines, in clause 12, the usage of Radius at the Pp Reference Point between the Packet Data Gateway and the Presence Network Agent, see 3GPP TS 23.141 [18]. + +# --- 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.234: "3GPP system to Wireless Local Area Network (WLAN) interworking; System description". +- [2] 3GPP TS 29.234: "3GPP system to Wireless Local Area Network (WLAN) interworking; Stage 3". +- [3] 3GPP TS 24.234: "3GPP system to Wireless Local Area Network (WLAN) interworking; User Equipment (UE) to network protocols; Stage 3". +- [4] 3GPP TS 29.061: "Interworking between the Public Land Mobile Network (PLMN) supporting packet based services and Packet Data Networks (PDN)". +- [5] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications". +- [6] IETF RFC 1034 (1987): "Domain names - concepts and facilities". +- [7] IETF RFC 1035 (1987): "Domain names - implementation and specification". +- [8] IETF RFC 2131 (1997): "Dynamic Host Configuration Protocol". +- [9] IETF RFC 3315 (2003) "Dynamic Host Configuration Protocol for IPv6 (DHCPv6)". +- [10] IETF RFC 2865 (2000): "Remote Authentication Dial In User Service (RADIUS)". +- [11] IETF RFC 3162 (2001): "RADIUS and IPv6". +- [12] IETF RFC 2866 (2000): "RADIUS Accounting". +- [13] IETF RFC 2373 (1998): "IP Version 6 Addressing Architecture". +- [14] IETF RFC 2461 (1998): "Neighbor Discovery for IP Version 6 (IPv6)". +- [15] IETF RFC 2462 (1998): "IPv6 Stateless Address Autoconfiguration". +- [16] 3GPP TS 33.234: "3G security; Wireless Local Area Network (WLAN) interworking security". +- [17] 3GPP TS 24.229: "Internet Protocol (IP) multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3". +- [18] 3GPP TS 23.141: "Presence Service; Architecture and functional description". + +- [19] IETF RFC 4739, (2006): "Multiple Authentication Exchanges in the Internet Key Exchange (IKEv2) Protocol". +- [20] IETF RFC 3579, September 2003: "RADIUS (Remote Authentication Dial In User Service) Support for Extensible Authentication Protocol (EAP)". +- [21] IETF RFC 4005 (2005): "Diameter Network Access Server Application". +- [22] IETF RFC 3588 "Diameter Base Protocol". + +# --- 3 Definitions, abbreviations and symbols + +## 3.1 Definitions + +For the purposes of the present document, the terms and definitions given in 3GPP TS 23.234 [1] and the following apply: + +**3GPP - WLAN Interworking:** used generically to refer to interworking between the 3GPP system and the WLAN family of standards + +**interworking WLAN:** WLAN that interworks with a 3GPP system + +**Serving WLAN:** interworking WLAN that the user is connected to, i.e. either a visited or a home WLAN + +**Visited WLAN:** interworking WLAN that Interworks only with a visited PLMN + +**WLAN UE:** UE (equipped with UICC card including (U)SIM) utilized by a 3GPP subscriber to access the WLAN interworking + +**External AAA Server:** The External AAA Server is located in an external packet data network. The PDG interworks with the External AAA Server via the Wi reference point. + +## 3.2 Abbreviations + +For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [5] and the following apply: + +| | | +|--------|-----------------------------------------------| +| APN | Access Point Name | +| DHCP | Dynamic Host Configuration Protocol | +| DHCPv6 | Dynamic Host Configuration Protocol version 6 | +| DNS | Domain Name System | +| IETF | Internet Engineering Task Force | +| IP | Internet Protocol | +| IPv4 | Internet Protocol version 4 | +| IPv6 | Internet Protocol version 6 | +| ISP | Internet Service Provider | +| I-WLAN | Interworked / interworking WLAN | +| LAN | Local Area Network | +| MTU | Maximum Transfer Unit | +| PDG | Packet Data Gateway | +| PDN | Packet Data Network | +| PPP | Point-to-Point Protocol | +| PS | Packet Switched | +| RADIUS | Remote Authentication Dial In User Service | +| TCP | Transmission Control Protocol | +| W-APN | WLAN APN | +| WLAN | Wireless Local Area Network | + +## 3.3 Symbols + +For the purposes of the present document, the following symbols apply: + +| | | +|----|--------------------------------------------------------------------------| +| Wi | Reference point between a Packet Data Gateway and an external IP Network | +|----|--------------------------------------------------------------------------| + +Pp + +Reference point between a Packet Data Gateway and a Presence Network Agent + +# --- 4 Network characteristics + +## 4.1 Key characteristics of PLMN + +The PLMN is fully defined in the 3GPP technical specifications. The key characteristics of 3GPP - WLAN Interworking are found in 3GPP TS 23.234 [1]. + +## 4.2 Key characteristics of IP Networks + +Refer to 3GPP TS 29.061 [4]. + +# --- 5 Interworking classifications + +Refer to 3GPP TS 29.061 [4]. + +# --- 6 Access reference configuration + +Refer to scenario 3 in the clause Interworking Architecture in 3GPP TS 23.234 [1]. + +# --- 7 Subscription checking + +Subscription is checked during the WLAN attach procedure and at the tunnel establishment as described in 3GPP TS 23.234 [1]. + +# --- 8 Interworking with PDN (IP) + +**NOTE:** The application of procedures in this subclause is not recommended if user authentication and authorisation with AAA server is required because of the following reason: In order to perform RADIUS Authentication, the user ID and password information have to be passed from WLAN UE to PDG. However, this function is missing in the IKEv2 protocol that 3GPP TS 33.234 [16] refers in this release. In addition, user authentication and authorisation with AAA server will be standardised in release 7. + +## 8.1 General + +Packet Domain with the 3GPP - WLAN Interworking access shall support interworking with networks based on the Internet Protocol (IP). These interworked networks may be either intranets or the Internet. + +## 8.2 PDN Interworking Model + +When interworking with the IP networks, the Packet Domain with the 3GPP - WLAN Interworking access can operate IPv4 or IPv6. The interworking point with IP networks is at the Wi reference point, refer to scenario 3 in the clause Interworking Architecture in 3GPP TS 23.234 [1]. + +The PDG for interworking with the IP network is the access point of the Packet Domain. In this case the Packet Domain network will look like any other IP network or subnetwork. + +Typically in the IP networks, the interworking with subnetworks is done via IP routers. The Wi reference point is between the PDG and the external IP network. From the external IP network's point of view, the PDG is seen as a normal IP router. The L2 and L1 layers are operator specific. + +It is out of the scope of the present document to standardize the router functions and the used protocols in the Wi reference point. + +Interworking with user defined ISPs and private/public IP networks is subject to interconnect agreements between the network operators. + +No user data or header compression is done in the PDG. + +### 8.2.1 Access to Internet, Intranet or ISP through Packet Domain + +The access to Internet, Intranet or ISP may involve specific functions such as user authentication, user's authorization, end to end encryption between the UE and Intranet/ISP, allocation of a dynamic address belonging to the PLMN/Intranet/ISP addressing space, IPv6 address autoconfiguration, etc. + +For this purpose the Packet Domain may offer: + +- either direct transparent access to the Internet; or +- a non-transparent access to the Intranet/ISP. In this case the Packet Domain, i.e. the PDG, takes part in the functions listed above. + +#### 8.2.1.1 Transparent access to the Internet + +The WLAN UE is given an IPv4 address or IPv6 Prefix belonging to the operator addressing space. The address or IPv6 Prefix is given either at subscription in which case it is a static address or at the WLAN session authorization in which case it is a dynamic address. This address or IPv6 Prefix is used for packet forwarding between the Internet and the PDG and within the packet domain. With IPv6, either Stateless or Stateful Address Autoconfiguration shall be used to assign an IPv6 address to the terminal. These procedures are as described in the IPv6 non-transparent access case except that the addresses belong to the operator addressing space. The use of stateful or stateless is configured per W-APN. + +The transparent case provides at least a basic ISP service. As a consequence of this it may therefore provide a bearer service for a tunnel to a private Intranet. For details of this specific case, refer to 3GPP TS 29.061 [4], subclause "Transparent access to the Internet". + +#### 8.2.1.2 IPv4 Non Transparent access to an Intranet or ISP + +The WLAN UE is given an address belonging to the Intranet/ISP addressing space. The address is given either at subscription in which case it is a static address or at the WLAN session authorization in which case it is a dynamic address. This address is used for packet forwarding within the PDG and for packet forwarding on the Intranet/ISP. This requires a link between the PDG and an address allocation server, like AAA or DHCP belonging to the Intranet/ISP. + +Access to the ISP/Intranet may require the authentication and authorization with the External AAA Server. The PDG may negotiate with the WLAN UE whether "Multiple authentication Exchanges in IKEv2" is supported or not. If both WLAN UE and PDG support this function and WLAN UE requests multiple authentications with the External AAA Server, then next authentication and authorization with the External AAA Server is performed after the successful authentication and autorisation with the 3GPP AAA Server. Details on the multiple authentications are specified in IETF RFC 4739 [19]. Whether or not multiple authentications and authorizations are required is configured on a W-APN basis in the PDG. + +If the UE requests an IP address from a DHCP server, refer to RFC 2131 [8], the tunnel establishment acknowledgement brings the IP address from the PDG to the WLAN UE, refer to 3GPP TS 24.234 [3]. + +Figure 1 describes the access signalling between the PDG and the ISP/Intranet in the IPv4 Non-Transparent case. + +![Sequence diagram for IPv4 Non-Transparent access to an Intranet or ISP. The diagram shows four lifelines: WLAN UE, PDG, 3GPP AAA server, and ISP/Intranet RADIUS/DHCP. The process starts with the WLAN UE sending an ike-auth-req to the PDG. The PDG then initiates authentication and authorization with the 3GPP AAA server. The 3GPP AAA server responds with an ike-auth-req to the PDG, indicating that another authentication follows. The PDG then performs W-APN to ISP address translation via DNS and RADIUS/DHCP client allocation. The PDG sends a RADIUS Access Request to the ISP/Intranet RADIUS/DHCP server, which responds with a RADIUS Access Accept. The PDG then sends a DHCP-DISCOVER to the server, which responds with a DHCP-OFFER. The PDG sends a DHCP-REQUEST to the server, which responds with a DHCP-ACK. Finally, the PDG sends an ike-auth-resp with an IP address to the WLAN UE.](b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg) + +``` + +sequenceDiagram + participant WLAN UE + participant PDG + participant 3GPP AAA server + participant ISP/Intranet RADIUS/DHCP + + Note right of 3GPP AAA server: Authentication and Authorization with the 3GPP AAA Server + + Note right of PDG: W-APN to ISP address translation via DNS. +RADIUS/DHCP client allocation. + + WLAN UE->>PDG: ike-auth-req [User ID, W-APN, ...] + PDG->>3GPP AAA server: Authentication and Authorization with the 3GPP AAA Server + 3GPP AAA server->>PDG: ike-auth-req [User ID, ANOTHER AUTH FOLLOWS, ...] + PDG->>ISP/Intranet RADIUS/DHCP: RADIUS Access Request + ISP/Intranet RADIUS/DHCP-->>PDG: RADIUS Access Accept + PDG-->>ISP/Intranet RADIUS/DHCP: DHCP-DISCOVER + ISP/Intranet RADIUS/DHCP-->>PDG: DHCP-OFFER + PDG-->>ISP/Intranet RADIUS/DHCP: DHCP-REQUEST + ISP/Intranet RADIUS/DHCP-->>PDG: DHCP-ACK + PDG->>WLAN UE: ike-auth-resp [IP address] + +``` + +Sequence diagram for IPv4 Non-Transparent access to an Intranet or ISP. The diagram shows four lifelines: WLAN UE, PDG, 3GPP AAA server, and ISP/Intranet RADIUS/DHCP. The process starts with the WLAN UE sending an ike-auth-req to the PDG. The PDG then initiates authentication and authorization with the 3GPP AAA server. The 3GPP AAA server responds with an ike-auth-req to the PDG, indicating that another authentication follows. The PDG then performs W-APN to ISP address translation via DNS and RADIUS/DHCP client allocation. The PDG sends a RADIUS Access Request to the ISP/Intranet RADIUS/DHCP server, which responds with a RADIUS Access Accept. The PDG then sends a DHCP-DISCOVER to the server, which responds with a DHCP-OFFER. The PDG sends a DHCP-REQUEST to the server, which responds with a DHCP-ACK. Finally, the PDG sends an ike-auth-resp with an IP address to the WLAN UE. + +**Figure 1: IPv4 Non-Transparent access to an Intranet or ISP** + +#### 8.2.1.3 IPv6 Non Transparent access to an Intranet or ISP + +When using IPv6 Address Autoconfiguration (either Stateless or Stateful), the process of setting up the access to an Intranet or ISP involves two signalling phases. The first signalling phase is done in the control plane and consists of the WLAN access authentication and authorization and tunnel establishment. The second signalling phase is done in the user plane. + +The user plane signalling phase shall be either stateless or stateful. The stateless procedure, which involves only the WLAN UE and the PDG, is described in subclause "IPv6 Stateless Address Autoconfiguration". The stateful procedure, which involves the WLAN UE, PDG (as DHCP relay agent) and one or several DHCP servers on the Intranet or ISP, is described in subclause "IPv6 Stateful Address Autoconfiguration". + +Whether to use stateless or stateful address autoconfiguration procedure is configured per W-APN in the PDG. For W-APNs configured as stateless, the PDG shall only use the Prefix part of the IPv6 address for forwarding of UE terminated IP packets. The size of the prefix shall be according to the maximum prefix length for a global IPv6 address as specified in the IPv6 Addressing Architecture, see RFC 2373 [13]. + +The selection between Stateful and Stateless Autoconfiguration is dictated by the Router Advertisements sent by the PDG as described in the corresponding subclauses below and according to the principles defined in RFC 2461 [14] and RFC 2462 [15]. + +##### 8.2.1.3.1 Tunnel establishment and Intranet/ISP access authorization + +The PDG provides the WLAN UE with an IPv6 Prefix belonging to the Intranet/ISP addressing space. A dynamic IPv6 address shall be given using either stateless or stateful address autoconfiguration. This IPv6 address is used for packet forwarding within the packet domain and for packet forwarding on the Intranet/ISP. The WLAN UE may send an authentication request at the tunnel establishment and the PDG may request user authentication from a server, e.g. AAA, belonging to the Intranet/ISP. + +Access to the ISP/Intranet may require the authentication and authorization with the External AAA Server. The PDG may negotiate with the WLAN UE whether "Multiple authentication Exchanges in IKEv2" is supported or not. If both WLAN UE and PDG support this function and WLAN UE requests multiple authentications with the External AAA Server, then next authentication and authorization with the External AAA Server is performed after the successful authentication and autorisation with the 3GPP AAA Server. Details on the multiple authentications are specified in IETF RFC 4739 [19]. Whether or not multiple authentications and authorizations are required is configured on a W-APN basis in the PDG. + +In order to avoid any conflict between the link-local address of the WLAN UE and that of the PDG, the Interface-Identifier used by the UE to build its link-local address shall be assigned by the PDG. The PDG ensures the uniqueness of this interface-identifier. + +Figure 2 describes the tunnel establishment between the WLAN UE and the PDG in the IPv6 Non-Transparent case. + +The PDG deduces from local configuration data associated with the W-APN: + +- IPv6 address allocation type (stateless or stateful); +- the source of IPv6 Prefixes in the stateless case (PDG internal prefix pool, or external address allocation server); +- any server(s) to be used for address allocation, authentication and/or protocol configuration options retrieval (e.g. IMS related configuration, see 3GPP TS 24.229 [17]); +- the protocol e.g. RADIUS, to be used with the server(s); +- the communication and security feature needed to communicate with the server(s). + +As an example the PDG may use one of the following options: + +- PDG internal Prefix pool for IPv6 prefix allocation and no authentication; +- PDG internal Prefix pool for IPv6 prefix allocation and RADIUS for authentication. The External AAA Server responds with either an Access-Accept or an Access-Reject to the RADIUS client in the PDG; +- RADIUS for authentication and IPv6 prefix allocation. The External AAA Server responds with either an Access-Accept or an Access-Reject to the RADIUS client in the PDG. + +DHCPv6 may be used for IPv6 prefix allocation. + +IPv6 Prefixes in a PDG internal Prefix pool shall be configurable and structured per W-APN. + +The PDG shall return an IPv6 address composed of a Prefix and an Interface-Identifier in the tunnel establishment acknowledgement message (ike-auth-resp). The Interface-Identifier may have any value and it does not need to be unique within or across W-APNs. It shall however not conflict with the Interface-Identifier the PDG has selected for its own side of the UE-PDG link. The Prefix assigned by the PDG or the External AAA Server shall be globally or site-local unique, if stateless address autoconfiguration is configured on this W-APN. If, on the other hand, stateful address autoconfiguration is configured on the W-APN, the Prefix part of the IPv6 address returned to the UE shall be set to the link-local prefix (FE80::/64). + +![Sequence diagram showing tunnel establishment and Intranet/ISP access authorization. Lifelines: WLAN UE, PDG, 3GPP AAA server, ISP/Intranet RADIUS/DHCP. The process involves IKE authentication, AAA server authorization, DNS translation, RADIUS/DHCP allocation, and a final IKE response with an IP address.](5a4e62bead259c258d069fd3663ea670_img.jpg) + +``` + +sequenceDiagram + participant WLAN UE + participant PDG + participant 3GPP AAA server + participant ISP/Intranet RADIUS/DHCP + + Note right of 3GPP AAA server: Authentication and Authorization with the 3GPP AAA Server + + Note right of PDG: W-APN to ISP address translation via DNS. RADIUS/DHCP client allocation. + + WLAN UE->>PDG: ike-auth-req [User ID W-APN, ...] + PDG->>3GPP AAA server: + Note right of 3GPP AAA server: + 3GPP AAA server->>PDG: + PDG->>WLAN UE: ike-auth-req [User ID, ANOTHER AUTH FOLLOWS, ...] + Note right of PDG: + PDG->>ISP/Intranet RADIUS/DHCP: RADIUS Access Request + ISP/Intranet RADIUS/DHCP->>PDG: RADIUS Access Accept + ISP/Intranet RADIUS/DHCP->>PDG: DHCPv6 (see note) + PDG->>WLAN UE: ike-auth-resp [IP address] + +``` + +Sequence diagram showing tunnel establishment and Intranet/ISP access authorization. Lifelines: WLAN UE, PDG, 3GPP AAA server, ISP/Intranet RADIUS/DHCP. The process involves IKE authentication, AAA server authorization, DNS translation, RADIUS/DHCP allocation, and a final IKE response with an IP address. + +NOTE: DHCPv6 may be used or IPv6 prefix allocation. + +**Figure 2: Tunnel establishment and Intranet/ISP access authorization** + +##### 8.2.1.3.2 IPv6 Stateless Address Autoconfiguration + +The tunnel establishment and Intranet/ISP access authorization is followed by a stateless address autoconfiguration procedure, which provides the WLAN UE with an IPv6 Global or Site-Local Unicast Address for the Intranet/ISP. (A terminal, e.g. a PC or a PDA with the WLAN UE may not have been able to receive the IP address during the 3GPP specific tunnel establishment signalling). + +The procedure describing W-APNs configured to use Stateless Address Autoconfiguration may be as follows, (for details refer to RFC 2462 [15] and RFC 2461 [14]): + +- After the tunnel establishment, the PDG starts sending Router Advertisements periodically in the tunnel towards the WLAN UE, with the M-flag cleared to indicate stateless address autoconfiguration. +- The UE may issue a Router Solicitation directly after the user plane establishment. This shall trigger the PDG to send a Router Advertisement immediately. +- The Prefix sent in the Router Advertisements shall be identical to the Prefix returned earlier in the tunnel establishment acknowledgement. + +![Sequence diagram for IPv6 Stateless Address Autoconfiguration](27b06ec9f42b5d727a2630f61a5f1861_img.jpg) + +``` +sequenceDiagram + participant WLAN_UE as WLAN UE + participant PDG as PDG + participant ISP as ISP/Intranet RADIUS/DHCP + + Note left of WLAN_UE: Tunnel Establishment + WLAN_UE->>PDG: Tunnel Establishment + PDG->>ISP: RADIUS / DHCPv6 + Note left of WLAN_UE: Router solicitation + WLAN_UE-->>PDG: Router solicitation + PDG->>WLAN_UE: Router Advertisement + Note right of WLAN_UE: [M-flag=0, O-flag, Prefix, Litetime, A-flag=1, L-flag=0] + PDG->>WLAN_UE: Router Advertisement + Note right of WLAN_UE: [M-flag=0, O-flag, Prefix, Litetime, A-flag=1, L-flag=0] +``` + +The diagram illustrates the IPv6 Stateless Address Autoconfiguration process. It involves three entities: WLAN UE, PDG, and ISP/Intranet RADIUS/DHCP. The process begins with 'Tunnel Establishment' from the WLAN UE to the PDG, followed by 'RADIUS / DHCPv6' from the PDG to the ISP. The WLAN UE then sends a 'Router solicitation' (dashed line) to the PDG. The PDG responds with two 'Router Advertisement' messages. Each advertisement contains the following flags and parameters: [M-flag=0, O-flag, Prefix, Litetime, A-flag=1, L-flag=0]. + +Sequence diagram for IPv6 Stateless Address Autoconfiguration + +**Figure 3: IPv6 Stateless Address Autoconfiguration** + +##### 8.2.1.3.3 IPv6 Stateful Address Autoconfiguration + +The tunnel establishment and Intranet/ISP access authorization is followed by a stateful address autoconfiguration procedure, which provides the WLAN UE with an IPv6 Global or Site-Local Unicast Address from the Intranet/ISP. The address has not yet been available during the tunnel establishment phase, but the UE requests the address from the Intranet/ISP by the stateful address autoconfiguration procedure. The PDG acts as a DHCP relay agent. + +The procedure describing W-APNs configured to use Stateful Address Autoconfiguration may be as follows, (for details refer to RFC 2461 [14] and RFC 3315 [9]): + +- The UE issues a Router Solicitation after the user plane establishment. +- This triggers the PDG to start sending Router Advertisements periodically in the tunnel towards the WLAN UE, with the M-flag set to indicate stateful address autoconfiguration and with no IPv6 prefix. +- When the UE receives the Router Advertisement with the M-flag set, it starts a DHCPv6 configuration including a request for an IPv6 address. + +![Sequence diagram for IPv6 Stateful Address Autoconfiguration showing interactions between WLAN UE, PDG, and ISP/Intranet RADIUS/DHCP.](ff0952ef692c9d960ce5f6708bcc9711_img.jpg) + +``` + +sequenceDiagram + participant WLAN UE + participant PDG + participant ISP/Intranet RADIUS/DHCP + WLAN UE->>PDG: Tunnel Establishment + PDG->>ISP/Intranet RADIUS/DHCP: RADUIS + WLAN UE-->>PDG: Router solicitation + PDG->>WLAN UE: Router Advertisement + Note over WLAN UE: [M-flag=1, no prefix info option included] + WLAN UE->>PDG: DHCP PROCEDURE + PDG->>ISP/Intranet RADIUS/DHCP: DHCP PROCEDURE + +``` + +The diagram illustrates the IPv6 Stateful Address Autoconfiguration process. It involves three main entities: WLAN UE, PDG, and ISP/Intranet RADIUS/DHCP. The sequence of messages is as follows: + +- A 'Tunnel Establishment' occurs between the WLAN UE and the PDG. +- The PDG communicates with the ISP/Intranet RADIUS/DHCP using 'RADUIS' (sic). +- The WLAN UE sends a 'Router solicitation' (dashed line) to the PDG. +- The PDG responds with a 'Router Advertisement' to the WLAN UE, with a note indicating '[M-flag=1, no prefix info option included]'. +- Finally, a 'DHCP PROCEDURE' is conducted across all three entities. + +Sequence diagram for IPv6 Stateful Address Autoconfiguration showing interactions between WLAN UE, PDG, and ISP/Intranet RADIUS/DHCP. + +**Figure 4: IPv6 Stateful Address Autoconfiguration** + +##### 8.2.1.3.4 IPv6 Router Configuration Variables in the PDG + +Refer to 3GPP TS 29.061 [4], subclause "IPv6 Router Configuration Variables in the GGSN". + +## 8.3 Numbering and addressing + +Refer to 3GPP TS 23.234 [1] and 3GPP TS 29.061 [4]. + +## 8.4 Charging + +Refer to 3GPP TS 23.234 [1] and 3GPP TS 29.234 [2]. + +## 8.5 Domain Name System server (DNS Server) + +Provision of Domain Name services shall be provided by the PLMN operators in the transparent case and the ISP in the non-transparent case. (DNS documentation is provided in RFC 1034 [6] and RFC 1035 [7]). + +## 8.6 IP Multicast access + +The Packet Domain with 3GPP – WLAN interworking access may allow an access to IP Multicast traffic coming from an external network. The support of IP Multicast in the Packet Domain is optional. + +In order for the Packet Core Network with WLAN interworking access to support Multicast traffic that allows the WLAN UE to subscribe to multicast groups from outside the PLMN, the PDG shall support IGMP (IPv4) and/or MLD (IPv6) and one or more Inter-Router Multicast protocols, such as DVMRP, MOSPF, or PIM-SM. + +For details, refer to 3GPP TS 29.061 [4], subclause "IP Multicast access". + +# 9 Interworking with PDN (DHCP) + +## 9.1 General + +In current LAN environments the most commonly used configuration protocol is DHCP (Dynamic Host Configuration Protocol, RFC 2131 [8]) and DHCPv6 (Dynamic Host Configuration Protocol for IPv6, RFC 3315 [9]). It provides a + +mechanism for passing a large set of configuration parameters to hosts connected to a TCP/IP network (IP address, sub-net mask, domain name, MTU, etc.) in an automatic manner. Moreover DHCP may assign IP addresses to clients for a finite lease time, allowing for sequential reassignment of addresses to different users. + +The lease time is chosen by the administrator of the DHCP server (in the external network), and is therefore out of the scope of the present document. + +The Packet Domain offers the end user the possibility to run DHCP end-to-end the same way as he does when connected directly to a LAN (e.g. an enterprise Intranet). No modifications should be required in common implementations of DHCP clients and servers. However a Packet Domain-specific DHCP relay agent, refer to RFC 2131 [8] and RFC 3315 [9], is needed in the PDG so as to allow correct routing of DHCP requests and replies between the WLAN UE and the DHCP servers. + +## 9.2 Address allocation by the Intranet or ISP + +Address allocation schemes using DHCP are described in subclause "Access to Internet, Intranet or ISP through Packet Domain", with details for IPv4 in RFC 2131 [8] and for IPv6 in RFC 3315 [9]. + +## 9.3 Other configuration by the Intranet or ISP (IPv6 only) + +When using IPv6, in some situations the WLAN UE may need additional configuration information from the Intranet or ISP besides the IP address. It may for example be IMS related configuration options (see 3GPP TS 24.229 [17]). If the UE is DHCP capable and the IPv6 address has been allocated using Stateless Address Autoconfiguration, the UE may use a procedure as in the example in figure 5 to configure additional external network protocol parameters, or other parameters that apply to the Intranet or ISP. The PDG shall in this case indicate to the UE that there is additional configuration information to retrieve by setting the O-flag in the Router Advertisements. This shall be configured per W-APN in the PDG. + +The following bullets describe an example of a signal flow, where the UE directs an Information-Request to the All\_DHCP\_Relay\_Agents\_and\_Servers multicast address. The UE may also direct the message to a specific server instead of all servers. For a detailed description of the DHCPv6 messages refer to the DHCPv6 RFC 3315 [9]. The sequence is depicted in figure 5. + +- 1) A Router Advertisement with the O-flag set is sent from the PDG to the UE to indicate to it to retrieve other configuration information. +- 2) The UE sends an INFORMATION-REQUEST message with the IP destination address set to the All\_DHCP\_Relay\_Agents\_and\_Servers multicast address defined in the DHCPv6 RFC 3315 [9]. The source address shall be the link-local address of the UE. The DHCP relay agent in the PDG shall forward the message. +- 3) DHCP servers receiving the forwarded INFORMATION-REQUEST message reply by sending a RELAY-REPLY message, with the "Relay Message" option including a REPLY message with the requested configuration parameters. + +The UE chooses one of the possibly several REPLY messages and extracts the configuration information. + +![Sequence diagram showing DHCPv6 other configuration signal flow between WLAN UE, PDG DHCP relay agent, and ISP/Intranet DHCP server(s).](7efae06af3af43ffe5d4b956a679cf54_img.jpg) + +``` + +sequenceDiagram + participant WLAN_UE as WLAN UE + participant PDG_DHCP_relay_agent as PDG DHCP relay agent + participant ISP_Intranet_DHCP_server as ISP/Intranet DHCP server(s) + + Note left of PDG_DHCP_relay_agent: 1. Router advertisement [O-flag=1] + PDG_DHCP_relay_agent-->>WLAN_UE: 1. Router advertisement [O-flag=1] + + Note right of WLAN_UE: 2. INFORMATION-REQUEST + WLAN_UE->>PDG_DHCP_relay_agent: 2. INFORMATION-REQUEST + PDG_DHCP_relay_agent->>ISP_Intranet_DHCP_server: RELAY-FORWARD (INFORMATION REQUEST) + + Note right of ISP_Intranet_DHCP_server: 3. REPLY + ISP_Intranet_DHCP_server-->>PDG_DHCP_relay_agent: 3. REPLY + PDG_DHCP_relay_agent-->>WLAN_UE: 3. REPLY + + Note right of ISP_Intranet_DHCP_server: n. REPLY + ISP_Intranet_DHCP_server-->>PDG_DHCP_relay_agent: n. REPLY + PDG_DHCP_relay_agent-->>WLAN_UE: n. REPLY + +``` + +Sequence diagram showing DHCPv6 other configuration signal flow between WLAN UE, PDG DHCP relay agent, and ISP/Intranet DHCP server(s). + +Figure 5: DHCPv6 other configuration signal flow + +# 10 Interworking between Packet Domains + +Refer to 3GPP TS 23.234 [1]. + +# 11 Usage of RADIUS on Wi interface + +NOTE: The application of procedures in subclause 11.1 is not recommended. The application of procedures in subclause 11.3 is only recommended if user authentication and authorisation is not required. The procedures of those flows are incomplete for the following reason: In order to perform RADIUS Authentication, user ID and password information have to be passed from WLAN UE to PDG. However, this function is missing in the IKEv2 protocol that 3GPP TS 33.234 [16] refers in this release. In addition, user authentication and authorisation with AAA server will be standardised in release 7. + +A PDG may, on a per W-APN basis, use RADIUS authentication to authenticate a user and RADIUS accounting to provide information to an External AAA (Authentication, Authorization and Accounting) server. + +## 11.1 RADIUS Authentication and Authorization + +RADIUS authentication and authorization shall be used according to RFC 2865 [10] and RFC 3162 [11]. + +The RADIUS client function may reside in a PDG. When the PDG receives a tunnel establishment request, the RADIUS client function may initiate the authentication and authorization procedure with the External AAA Server after the successful authentication and authorisation with the 3GPP AAA Server. + +The following procedure may take place depending on an ability of the External AAA Server. Details on the following procedures are specified in 3GPP TS 33.234 [16]. + +- The EAP procedure +This procedure is the most preferable configuration for the ISP/Intranet access. In this procedure, the External AAA Server shall support EAP extensions specified in the RADIUS (Remote Authentication Dial In User Service) Support for Extensible Authentication Protocol (EAP) [20]. +- The PAP procedure +This procedure is applied if the External AAA server performs PAP procedure. + +- The CHAP procedure +This procedure is applied if the External AAA server performs CHAP procedure. + +The External AAA Server checks that the user can be accepted. The response (when positive) may contain network information, such as an IPv4 address or IPv6 prefix for the user. + +The information delivered during the RADIUS authentication and authorization can be used to automatically correlate the users identity to the IPv4 address or IPv6 prefix, assigned/confirmed by the PDG or the External AAA Server respectively. The same procedure applies, in case of sending the authentication and authorization to a 'proxy' authentication server. + +## 11.2 RADIUS Accounting + +RADIUS Accounting shall be used according to RFC 2866 [12] and RFC 3162 [11]. + +The RADIUS accounting client function may reside in a PDG. The RADIUS accounting client may send information to an accounting server, which is identified during the W-APN provisioning. The accounting server may store this information and use it to automatically identify the user. This information can be trusted because the 3GPP network has authenticated the subscriber. + +The Accounting-Request STOP and the Accounting ON and Accounting OFF messages may be used to ensure that information stored in the accounting server is synchronized with the PDG information. + +## 11.3 Authentication, Authorization and Accounting message flows + +Figure 6 presents the RADIUS message flows between a PDG and an Authentication, Authorization and Accounting (AAA) server. For details of the tunnel establishment and deletion signalling, refer to 3GPP TS 24.234 [3]. + +![Sequence diagram illustrating the RADIUS message flow between a WLAN UE, PDG, 3GPP AAA Server, External AAA Server, and PDN. The flow starts with an ike-auth-req from the UE to the PDG. The PDG then initiates authentication with the 3GPP AAA Server. The 3GPP AAA Server sends an Access-Request to the External AAA Server, which responds with an Access-Accept. The 3GPP AAA Server then sends an Accounting-Request (start) to the External AAA Server, which responds with an Accounting-Response (start). The PDG then sends the ike-auth-resp to the UE. User data is then transferred from the PDN to the UE. Finally, the UE sends an informational (delete) message to the PDG, which responds with an informational-resp. The PDG also sends an Accounting-Request (stop) to the External AAA Server, which responds with an Accounting-Response (stop).](8307f6b04df072c9332f9987e034272c_img.jpg) + +``` + +sequenceDiagram + participant WLAN UE + participant PDG + participant 3GPP AAA Server + participant External AAA Server + participant PDN + + Note right of External AAA Server: (Note 2) + + WLAN UE->>PDG: ike-auth-req [User ID, W-APN, ...] + PDG->>3GPP AAA Server: Authentication and Authorization with the 3GPP AAA Server + 3GPP AAA Server->>PDG: ike-auth-req [User ID, ANOTHER AUTH FOLLOWS, ...] + PDG->>External AAA Server: Access-Request + External AAA Server-->>PDG: Access-Accept + PDG->>External AAA Server: Accounting-Request (start) + External AAA Server-->>PDG: Accounting-Response (start) + PDG->>WLAN UE: ike-auth-resp (Note 1) + PDN->>WLAN UE: User data + WLAN UE->>PDG: informational (delete) + PDG->>External AAA Server: Accounting-Request (stop) + External AAA Server-->>PDG: Accounting-Response (stop) + PDG->>WLAN UE: informational-resp + +``` + +Sequence diagram illustrating the RADIUS message flow between a WLAN UE, PDG, 3GPP AAA Server, External AAA Server, and PDN. The flow starts with an ike-auth-req from the UE to the PDG. The PDG then initiates authentication with the 3GPP AAA Server. The 3GPP AAA Server sends an Access-Request to the External AAA Server, which responds with an Access-Accept. The 3GPP AAA Server then sends an Accounting-Request (start) to the External AAA Server, which responds with an Accounting-Response (start). The PDG then sends the ike-auth-resp to the UE. User data is then transferred from the PDN to the UE. Finally, the UE sends an informational (delete) message to the PDG, which responds with an informational-resp. The PDG also sends an Accounting-Request (stop) to the External AAA Server, which responds with an Accounting-Response (stop). + +NOTE 1: If some external applications require RADIUS Accounting request (Start) information before they can process user packets, then the selected W-APN (PDG) may be configured in such a way that the PDG drops user data until the Accounting Response (START) is received from the External AAA server. The PDG may wait for the Accounting Response (START) before sending the ike-auth response. The PDG may reject the tunnel establishment, if the Accounting Response (START) is not received. + +NOTE 2: Separate accounting and authentication servers may be used. + +NOTE 3: The Accounting-Request (Start) message may be sent at a later stage, e.g. after IPv6 address has been assigned and PDP Context updated, in case of a stateful address autoconfiguration. + +**Figure 6: RADIUS message flow** + +When a PDG receives a tunnel establishment request (IKE-AUTH request) for a given W-APN, the PDG may (depending on the configuration for this W-APN) send a RADIUS Access-Request to an External AAA Server after the successful authentication and autorisation with the 3GPP AAA Server. The External AAA server authenticates and authorizes the user. If RADIUS is also responsible for IPv4 address or IPv6 prefix allocation, the External AAA Server shall return the allocated IPv4 address or IPv6 prefix in the Access-Accept message. + +Even if the PDG was not involved in user authentication (e.g. transparent network access mode), it may send a RADIUS Accounting-Request START message to an External AAA Server. This message contains parameters, e.g. the tuple, which includes the user-id and IPv4 address or IPv6 prefix, to be used by application servers (e.g. WAP gateway) in order to identify the user. This message also indicates to the External AAA Server that the user session has started. The session is uniquely identified by the Acct-Session-Id that is composed of the Charging-Id and the PDG-Address. + +If some external applications require RADIUS Accounting request (Start) information before they can process user packets, then the selected W-APN (PDG) may be configured in such a way that the PDG drops user data until the Accounting Response (START) is received from the AAA server. The PDG may wait for the Accounting Response (START) before sending the tunnels establishment response (IKE-AUTH response). The PDG may reject the tunnel establishment request, if the Accounting Response (START) is not received. The authentication and accounting servers may be separately configured for each W-APN. + +At a stateful address autoconfiguration, no IPv4 address or IPv6 prefix is available at tunnel establishment. In that case the PDG may wait to send the Accounting-Request START message until the WLAN UE receives its IP address in a DHCP-REPLY. + +When the PDG receives a delete tunnel request (*informational (delete)*) and providing a RADIUS Accounting-Request START message was sent previously, the PDG shall send a RADIUS Accounting-Request STOP message to the External AAA Server, which indicates the termination of this particular user session. The PDG shall immediately send a delete tunnel response (*informational-resp*), without waiting for an Accounting-Response STOP message from the AAA server. + +The External AAA Server shall deallocate the IPv4 address or IPv6 prefix (if any) initially allocated to the subscriber, if there is no session for the subscriber. + +Accounting-Request ON and Accounting-Request OFF messages may be sent from the PDG to the External AAA Server to ensure the correct synchronization of the session information in the PDG and the External AAA Server. + +The PDG may send an Accounting-Request ON message to the External AAA Server to indicate that a restart has occurred. The External AAA Server may then release the associated resources. + +Prior to a scheduled restart, the PDG may send Accounting-Request OFF message to the External AAA Server. The External AAA Server may then release the associated resources. + +If an Access-Challenge is sent to the PDG when an Access-Request message is pending, the PDG shall silently discard the Access-Challenge message and it shall treat an Access-Challenge as though it had received an Access-Reject instead RFC 2865 [10]. + +## 11.4 List of RADIUS attributes + +Refer to the 3GPP TS 29.061 [4], subclause "List of Radius attributes". + +# --- 11a Usage of Diameter on Wi interface + +As an operator option, it is also possible to use the Diameter protocol in order to provide Authentication, Authorization and Accounting services. + +A PDG may, on a per W-APN basis, use Diameter authentication to authenticate a user and Diameter accounting to provide information to a Diameter server. + +## 11a.1 Diameter Authentication + +Diameter Authentication shall be used according to RFC 4005 [21]. + +The PDG and the Diameter server shall advertise the support of the Diameter NASREQ Application by including the value of the appropriate application identifier in the Capability-Exchange-Request and Capability-Exchange-Answer commands as specified in RFC 3588 [22]. + +The Diameter client function may reside in a PDG. When the PDG receives a tunnel establishment request, the Diameter client function may send the authentication information to an authentication server, which is identified during the W-APN provisioning. + +The authentication server checks that the user can be accepted. The response (when positive) may contain network information, such as an IPv4 address or IPv6 prefix for the user. + +The information delivered during the Diameter authentication can be used to automatically correlate the users identity to the IPv4 address or IPv6 prefix, assigned/confirmed by the PDG or the authentication server respectively. The same procedure applies, in case of sending the authentication to a 'proxy' authentication server. + +## 11a.2 Diameter Accounting + +Diameter Accounting shall be used according to RFC 4005 [21]. + +The Diameter accounting client function may reside in a PDG. The Diameter accounting client may send information to an accounting server, which is identified during the W-APN provisioning. The accounting server may store this information and use it to automatically identify the user. This information can be trusted because the 3GPP network has authenticated the subscriber. + +## 11a.3 Authentication and accounting message flows + +Figure 6a presents the Diameter message flows between a PDG and a Diameter server. For details of the tunnel establishment and deletion signalling, refer to 3GPP TS 24.234 [3]. + +![Sequence diagram showing Diameter message flows between WLAN UE, PDG, 3GPP AAA Server, Diameter Server, and PDN. The process involves IKE authentication, Diameter AA-Request/Answer, and Accounting START/STOP messages.](40f30e4d577a17052f8b1e6dc802a0d8_img.jpg) + +``` + +sequenceDiagram + participant WLAN_UE as WLAN UE + participant PDG + participant 3GPP_AAA_Server as 3GPP AAA Server + participant Diameter_Server as Diameter Server + participant PDN + + Note right of Diameter_Server: (Note 2) + + WLAN_UE->>PDG: ike-auth-req [User ID, W-APN, ...] + Note over WLAN_UE, 3GPP_AAA_Server: Authentication and Authorization with the 3GPP AAA Server + WLAN_UE->>PDG: ike-auth-req [User ID, ANOTHER AUTH FOLLOWS, ...] + PDG-->>Diameter_Server: AA-Request + Diameter_Server-->>PDG: AA-Answer + PDG->>Diameter_Server: Accounting-Request (START) + PDG->>WLAN_UE: ike-auth-resp (Note 1) + Diameter_Server-->>PDG: Accounting-Answer (START) + PDG->>PDN: User data + WLAN_UE->>PDG: informational (delete) + PDG->>Diameter_Server: Accounting-Request (STOP) + WLAN_UE->>PDG: informational-resp + PDG-->>Diameter_Server: Accounting-Answer (STOP) + +``` + +Sequence diagram showing Diameter message flows between WLAN UE, PDG, 3GPP AAA Server, Diameter Server, and PDN. The process involves IKE authentication, Diameter AA-Request/Answer, and Accounting START/STOP messages. + +NOTE 1: If some external applications require Diameter Accounting request (START) information before they can process user packets, then the selected W-APN (PDG) may be configured in such a way that the PDG drops user data until the Accounting Answer (START) is received from the External AAA server. The PDG may wait for the Accounting Answer (START) before sending the ike-auth response. The PDG may reject the tunnel establishment, if the Accounting Answer (START) is not received. + +NOTE 2: Separate accounting and authentication servers may be used. + +NOTE 3: The Accounting-Request (START) message may be sent at a later stage, e.g. after IPv6 address has been assigned and PDP Context updated, in case of a stateful address autoconfiguration. + +Figure 6a: Diameter message flow + +When a PDG receives a tunnel establishment request (IKE-AUTH request) for a given W-APN, the PDG may (depending on the configuration for this W-APN) send a Diameter AA-Request to a Diameter Server after the successful authentication and autorisation with the 3GPP AAA Server. The Diameter server authenticates and authorizes the user. If Diameter is also responsible for IPv4 address or IPv6 prefix allocation, the Diameter Server shall return the allocated IPv4 address or IPv6 prefix in the AA-Answer message. + +Even if the PDG was not involved in user authentication (e.g. transparent network access mode), it may send a Diameter Accounting-Request (START) message to a Diameter Server. This message contains parameters, e.g. the tuple, which includes the user-id and IPv4 address or IPv6 prefix, to be used by application servers (e.g. WAP gateway) in order to identify the user. This message also indicates to the Diameter Server that the user session has started. + +If some external applications require Diameter Accounting request (START) information before they can process user packets, then the selected W-APN (PDG) may be configured in such a way that the PDG drops user data until the Accounting Answer (START) is received from the Diameter server. The PDG may wait for the Accounting Answer (START) before sending the tunnels establishment response (IKE-AUTH response). The PDG may reject the tunnel establishment request, if the Accounting Answer (START) is not received. The authentication and accounting servers may be separately configured for each W-APN. + +At a stateful address autoconfiguration, no IPv4 address or IPv6 prefix is available at tunnel establishment. In that case the PDG may wait to send the Accounting-Request (START) message until the WLAN UE receives its IP address in a DHCP-REPLY. + +When the PDG receives a delete tunnel request (*informational (delete)*) and providing a Diameter Accounting-Request (START) message was sent previously, the PDG shall send a Diameter Accounting-Request (STOP) message to the Diameter Server, which indicates the termination of this particular user session. The PDG shall immediately send a delete tunnel response (*informational-resp*), without waiting for an Accounting-Answer (STOP) message from the Diameter server. + +The Diameter Server shall deallocate the IPv4 address or IPv6 prefix (if any) initially allocated to the subscriber, if there is no session for the subscriber. + +## 11a.4 Wi Diameter messages and AVPs + +Refer to the 3GPP TS 29.061 [4], subclauses "Gi Diameter messages" and "Gi specific AVPs". + +# --- 12 Usage of RADIUS on Pp interface + +## 12.1 General + +The Pp interface is defined in 3GPP TS 23.141 [18] and allows 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). The Pp interface is implemented by reusing mechanisms of RADIUS authentication and accounting via Wi interface as defined in clause 11. + +## 12.2 Radius Profile for Pp interface + +The RADIUS interface on Wi reference point as defined in Clause 11 is used for the Pp Reference Point as clarified in the Profile in this Clause. + +Only the following messages are required for the Radius Profile for the Pp reference Point: + +- Accounting-Request START +- Accounting-Response START +- Accounting-Request STOP +- Accounting-Response STOP + +For the Radius Profile for the Pp Reference Point, only the mandatory Parameters within the Accounting-Request START and Accounting-Request STOP messages according to 3GPP TS 29.061 [4] Clauses 16.4.3 and 16.4.4, + +respectively, and the Parameter "Calling-Station-Id" need to be supported. The usage of other parameters is optional. They may be ignored by the Presence Network Agent. + +## 12.3 Interconnecting the Presence Network Agent and the PDG + +The Presence Network Agent may be directly attached to the PDG or via a Radius Proxy. + +If the PDG needs to connect both to some AAA server via the Wi interface and a Presence Network Agent via the Pp interface for the same APN, but supports only a single RADIUS interface, the PDG can be directly attached to that AAA server. The Presence Network Agent can in turn be attached to that AAA server, which acts as a RADIUS proxy. If the AAA server is configured as a RADIUS Proxy between the Presence Network Agent and the PDG, the Radius Profile for the Pp Reference Point shall be applicable on the interface between the Presence Network Agent and the AAA server. + +# Annex A (informative): Change history + +| Change history | | | | | | | | +|----------------|-------|-----------|-----|-----|---------------------------------------------------------------------------------------|--------|--------| +| Date | TSG # | TSG Doc. | CR | Rev | Subject/Comment | Old | New | +| 2004-09 | 25 | NP-040344 | | | Approved by CN Plenary and placed under change control | 2.0.1 | 6.0.0 | +| 2005-06 | 28 | CP-050041 | 002 | 2 | Pp Interface | 6.0.0 | 6.1.0 | +| 2006-06 | 32 | CP-060348 | 005 | 4 | Depreciating authentication and authorization functions | 6.1.0 | 6.2.0 | +| 2006-06 | 32 | CP-060226 | 003 | 1 | Introduction of I-WLAN Private Network Access | 6.2.0 | 7.0.0 | +| 2006-06 | 32 | CP-060225 | 004 | 1 | Usage of Diameter over the Wi interface | 6.2.0 | 7.0.0 | +| 2006-12 | 34 | CP-060628 | 006 | 2 | Authentication, Authorization, and Accounting message flows for Diameter Wi interface | 7.0.0 | 7.1.0 | +| 2006-12 | 34 | CP-060622 | 008 | 1 | Correcting a reference to TS 29.061 in TS 29.161 | 7.0.0 | 7.1.0 | +| 2007-03 | 35 | CP-070093 | 009 | 1 | Update reference | 7.1.0 | 7.2.0 | +| 2008-12 | 42 | | | | Upgraded to v8.0.0 due to simple upgrade without no technical change | 7.2.0 | 8.0.0 | +| 2009-12 | 46 | | | | Automatic upgrade from previous Release | 8.0.0 | 9.0.0 | +| 2011-03 | 51 | | | | Automatic upgrade from previous Release version 9.0.0 | 9.0.0 | 10.0.0 | +| 2011-03 | 51 | | | | Correction of heading and numbering made by MCC | 10.0.0 | 10.0.1 | +| 2012-09 | 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/29_series/29162/04f51626e2e10a16e3eb2c4b33cb2742_img.jpg b/marked/Rel-11/29_series/29162/04f51626e2e10a16e3eb2c4b33cb2742_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cd56554bc984ff149aa4879d94317d19a4a05919 --- /dev/null +++ b/marked/Rel-11/29_series/29162/04f51626e2e10a16e3eb2c4b33cb2742_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:258e02b42b7d42a2a6a7a42e12fffd583cbc2fcd6a7fc4ec866106690c24539d +size 17386 diff --git a/marked/Rel-11/29_series/29162/0b3d9fe35da3ee0c88f1420bb9ed7a03_img.jpg b/marked/Rel-11/29_series/29162/0b3d9fe35da3ee0c88f1420bb9ed7a03_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1cb6e1b32f2d8e9f76bf44cfed1560d3284602cc --- /dev/null +++ b/marked/Rel-11/29_series/29162/0b3d9fe35da3ee0c88f1420bb9ed7a03_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:22ac90972ec652b3fdd96efd12b0ff7421f90fb2632c652aecba59b961d94c73 +size 42462 diff --git a/marked/Rel-11/29_series/29162/24b1ac9eb58a2f22801620b9e2ea8bd3_img.jpg b/marked/Rel-11/29_series/29162/24b1ac9eb58a2f22801620b9e2ea8bd3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f8ef62064da1e2ed17fdd8f0fcb06a402b17b8cd --- /dev/null +++ b/marked/Rel-11/29_series/29162/24b1ac9eb58a2f22801620b9e2ea8bd3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:07e291d726aa737fbf74f8457846cffc9a06b6e8d911d36ceab518d4c6d0b298 +size 41361 diff --git a/marked/Rel-11/29_series/29162/5a4e62bead259c258d069fd3663ea670_img.jpg b/marked/Rel-11/29_series/29162/5a4e62bead259c258d069fd3663ea670_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..330b8b152d8917ffbfd86a2c8bdf3ef66d5ddd9a --- /dev/null +++ b/marked/Rel-11/29_series/29162/5a4e62bead259c258d069fd3663ea670_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9045f92c31cac8078f43257926d4e2471443217425790902ab65beb686cb1d1c +size 92733 diff --git a/marked/Rel-11/29_series/29162/7d3d5fb5d09c0cd35a9d637be241651e_img.jpg b/marked/Rel-11/29_series/29162/7d3d5fb5d09c0cd35a9d637be241651e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..29db28452f620d0ea5f7be1134040c2529a563ac --- /dev/null +++ b/marked/Rel-11/29_series/29162/7d3d5fb5d09c0cd35a9d637be241651e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9f904cd102b1ba9b96de7274878c8a215771fff99ff9a8e3cecf311a8ba72514 +size 41048 diff --git a/marked/Rel-11/29_series/29162/81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg b/marked/Rel-11/29_series/29162/81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..494b4e1a562164f61205557f545bf947317dde9d --- /dev/null +++ b/marked/Rel-11/29_series/29162/81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:798c97d86d54c9c9498dfc7c3a3eb8e46444c11537c4073f0cdb44286204122b +size 139534 diff --git a/marked/Rel-11/29_series/29162/90ddb84c323b956e2d50a54d3f870566_img.jpg b/marked/Rel-11/29_series/29162/90ddb84c323b956e2d50a54d3f870566_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..29889c86ad2456c395c96f217ad9d820a2a38a1e --- /dev/null +++ b/marked/Rel-11/29_series/29162/90ddb84c323b956e2d50a54d3f870566_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1bc6184a064350ef680c6d13789e7544a65a8d58199eeb91ebdd4aea4e900757 +size 151744 diff --git a/marked/Rel-11/29_series/29162/99bae07626f60f9ede10e2e387ef7051_img.jpg b/marked/Rel-11/29_series/29162/99bae07626f60f9ede10e2e387ef7051_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a9926d205c5287c181209a2a3f437f0357e5eff2 --- /dev/null +++ b/marked/Rel-11/29_series/29162/99bae07626f60f9ede10e2e387ef7051_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e94395a8028a381645dcb6c3e4611607ce42a397da350f2e0ddfdd4600c53432 +size 51799 diff --git a/marked/Rel-11/29_series/29162/9c1d3678db4a12d5864cb2a4def1135d_img.jpg b/marked/Rel-11/29_series/29162/9c1d3678db4a12d5864cb2a4def1135d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ecee0e493b444556f36d0500b02dcc5a1f31bfb8 --- /dev/null +++ b/marked/Rel-11/29_series/29162/9c1d3678db4a12d5864cb2a4def1135d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:365f44ae7f0bb9b19cdb14cbfcc636f64ab0e8d5dca49c5d8894178db01c0dfe +size 148874 diff --git a/marked/Rel-11/29_series/29162/9f6dec4d4e9fde40bce018861ef1278e_img.jpg b/marked/Rel-11/29_series/29162/9f6dec4d4e9fde40bce018861ef1278e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1aae9a28720585507a3348c99569f59d9016d8fb --- /dev/null +++ b/marked/Rel-11/29_series/29162/9f6dec4d4e9fde40bce018861ef1278e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e7139f2b31cfd0d5098c4a7bff4cdca395a05b7ee039ac6cfaa0c2c0bc82e13a +size 65881 diff --git a/marked/Rel-11/29_series/29162/ac31fdfebb9751f7f10416dfe33bc872_img.jpg b/marked/Rel-11/29_series/29162/ac31fdfebb9751f7f10416dfe33bc872_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6ff6c574052e5c8c52332cacee8327f3d0b1ae59 --- /dev/null +++ b/marked/Rel-11/29_series/29162/ac31fdfebb9751f7f10416dfe33bc872_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c14f865c73f9b25fc63d47d27210b40dab5e57262093ad01906f4be78b2b7402 +size 34615 diff --git a/marked/Rel-11/29_series/29162/b2f5606b9c7184c1c6070a290080a3e3_img.jpg b/marked/Rel-11/29_series/29162/b2f5606b9c7184c1c6070a290080a3e3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c954586b93e52a0e51b651d70e110d45ce497282 --- /dev/null +++ b/marked/Rel-11/29_series/29162/b2f5606b9c7184c1c6070a290080a3e3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5a76a78f68cae1c6e39420334c879a6228ea94c3b1379f8027ca1128b2949803 +size 31043 diff --git a/marked/Rel-11/29_series/29162/cd48273072c5c3a23e11fde892d1b6b6_img.jpg b/marked/Rel-11/29_series/29162/cd48273072c5c3a23e11fde892d1b6b6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2e9a3f4011977563f6ae8072859ef3e604b1557b --- /dev/null +++ b/marked/Rel-11/29_series/29162/cd48273072c5c3a23e11fde892d1b6b6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8d4cb7fc64f400618f06bb00c1ef0c7f21e5bd94caafe5392d09fb947ba506fa +size 17100 diff --git a/marked/Rel-11/29_series/29162/dd5771673aececa53d42ece89218299d_img.jpg b/marked/Rel-11/29_series/29162/dd5771673aececa53d42ece89218299d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e59c3cce4633ae6a7f5647cb073856a64b2d2e94 --- /dev/null +++ b/marked/Rel-11/29_series/29162/dd5771673aececa53d42ece89218299d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d49f8553cb49678a67ba54ba53a803b3bd5b1f0f8285118887a08704c8d14fab +size 145367 diff --git a/marked/Rel-11/29_series/29162/dec689324b075952626a86da862b9549_img.jpg b/marked/Rel-11/29_series/29162/dec689324b075952626a86da862b9549_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..39ac4dcc7b8c6e4158833289cc3e8683ea8128e7 --- /dev/null +++ b/marked/Rel-11/29_series/29162/dec689324b075952626a86da862b9549_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:606b4a9e873bc9647f790e5ba328d7a1f49dfecf8b5c1871eb944811681ca7a8 +size 37336 diff --git a/marked/Rel-11/29_series/29162/raw.md b/marked/Rel-11/29_series/29162/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..27a61da2f44e25f12a5e1f003a33e4982d5de893 --- /dev/null +++ b/marked/Rel-11/29_series/29162/raw.md @@ -0,0 +1,1722 @@ + + + + + + +# Contents + +| | | +|-------------------------------------------------------------------------------------------------|----| +| Foreword ..... | 5 | +| 1 Scope..... | 6 | +| 2 References..... | 6 | +| 3 Definitions, symbols and abbreviations ..... | 8 | +| 3.1 Definitions..... | 8 | +| 3.2 Symbols..... | 8 | +| 3.3 Abbreviations ..... | 8 | +| 4 General..... | 9 | +| 4.1 General interworking overview..... | 9 | +| 4.2 Interworking scenarios ..... | 9 | +| 4.2.1 UE with 3GPP SIP profile capability connecting to an external SIP device..... | 10 | +| 5 Network characteristics..... | 10 | +| 5.1 Key characteristics of IP Multimedia Networks ..... | 10 | +| 5.2 Key characteristics of UMTS IM CN Subsystem..... | 10 | +| 6 Interworking Reference Model for control plane interworking and user plane interworking ..... | 10 | +| 6.0 Reference Model ..... | 10 | +| 6.1 Interworking Functional Entities..... | 12 | +| 6.1.1 IBCF ..... | 12 | +| 6.1.2 IMS-ALG ..... | 12 | +| 6.1.3 TrGW..... | 12 | +| 6.1.4 Acces Transfer Control Function ..... | 12 | +| 6.1.5 Acces Transfer GateWay..... | 12 | +| 7 Control plane interworking..... | 12 | +| 7.1 SIP with 3GPP Profile to Standard SIP Interworking..... | 12 | +| 7.2 Additional interworking of protocols associated with services ..... | 13 | +| 8 User Plane Interworking ..... | 13 | +| 8.1 Overview ..... | 13 | +| 8.2 Void..... | 13 | +| 8.3 Void..... | 13 | +| 9 IMS-ALG and TrGW functionality for NAPT and IP Version Interworking ..... | 13 | +| 9.1 Control plane interworking ..... | 13 | +| 9.1.1 Session Set-up ..... | 13 | +| 9.1.1.0 General..... | 13 | +| 9.1.1.1 Receipt of the first SDP offer ..... | 13 | +| 9.1.1.2 Receipt of the first SDP answer..... | 14 | +| 9.1.2 Void..... | 14 | +| 9.1.3 Change of connection information ..... | 14 | +| 9.1.4 Interworking of SIP messages..... | 14 | +| 9.2 User plane transport ..... | 15 | +| 9.2.1 Payload transport..... | 15 | +| 9.2.2 IP header interworking ..... | 15 | +| 9.2.2.1 IPv4 to IPv6 ..... | 15 | +| 9.2.2.2 Abnormal cases..... | 16 | +| 9.2.2.3 IPv6 to IPv4 ..... | 17 | +| 9.2.2.4 Abnormal cases..... | 18 | +| 9.2.3 Fragmentation..... | 18 | +| 9.2.4 Abnormal cases ..... | 19 | +| 10 IBCF – TrGW Interactions ..... | 19 | +| 10.1 Overview ..... | 19 | +| 10.1.1 General ..... | 19 | +| 10.1.2 Network model ..... | 19 | +| 10.1.3 Example Call Flow ..... | 19 | + +| | | | +|-------------------------------|---------------------------------------------------------------------|-----------| +| 10.1.3.1 | Basic Procedures..... | 19 | +| 10.1.3.1.1 | Call Establishment..... | 19 | +| 10.1.3.1.2 | Call Release..... | 22 | +| 10.2 | Main Functions supported at the Ix Interface..... | 22 | +| 10.2.0 | Introduction ..... | 22 | +| 10.2.1 | NAPT and IP version interworking..... | 23 | +| 10.2.2 | Gate Management..... | 23 | +| 10.2.3 | RTCP Handling ..... | 23 | +| 10.2.4 | IP Realm Indication..... | 23 | +| 10.2.5 | Media Control..... | 24 | +| 10.2.6 | Media Inactivity Detection ..... | 31 | +| 10.2.7 | QoS Packet Marking (differentiated services)..... | 31 | +| 10.2.8 | Hanging Termination Detection ..... | 31 | +| 10.2.9 | Bandwidth Policing ..... | 31 | +| 10.2.10 | IMS end-to-end media plane security..... | 31 | +| 10.2.11 | Through-Connection..... | 32 | +| 10.2.12 | Emergency Call ..... | 32 | +| 10.2.13 | Explicit Congestion Notification support..... | 32 | +| 10.2.13.1 | General..... | 32 | +| 10.2.13.2 | Incoming SDP offer with ECN..... | 32 | +| 10.2.13.3 | Incoming SDP offer without ECN..... | 33 | +| 10.2.13.3a | Detection of ECN failures by TrGW ..... | 34 | +| 10.2.13.4 | Interworking with non-3GPP ECN IP terminal..... | 34 | +| 10.2.13.4.1 | Support for additional ECN parameters ..... | 34 | +| 10.2.13.4.2 | Incoming SDP offer from external IP network with ECN..... | 34 | +| 10.2.13.4.3 | Incoming SDP offer from the IMS with ECN..... | 34 | +| 10.2.13.5 | Message sequence chart..... | 36 | +| 10.2.13.5.1 | ECN support requested (ECN endpoint)..... | 36 | +| 10.2.13.5.2 | ECN Active Indicated (ECN transparent)..... | 36 | +| 10.2.13.5.3 | ECN Failure Indication (ECN endpoint)..... | 37 | +| 10.2.14 | Optimal Media Routeing..... | 37 | +| 10.2.15 | IP Realm Availability ..... | 37 | +| 10.2.16 | Access Transfer procedures with media anchored in ATGW ..... | 37 | +| 10.2.17 | Multimedia Priority Service (MPS) Support ..... | 38 | +| 10.2.17.1 | General..... | 38 | +| 10.2.17.2 | TrGW Resource Congestion in ADD response, request is queued ..... | 38 | +| 10.2.17.3 | TrGW Resource Congestion in ADD response, IBCF seizes new TrGW..... | 39 | +| 10.2.17.4 | TrGW Priority Resource Allocation..... | 39 | +| 10.2.17.5 | TrGW Priority User Data marking ..... | 40 | +| 10.2.17.6 | TrGW Priority Modification..... | 40 | +| 10.3 | Void..... | 40 | +| 10.4 | Procedures ..... | 40 | +| 10.4.1 | Call related Procedures..... | 40 | +| 10.4.1.1 | Reserve TrGW Connection Point ..... | 40 | +| 10.4.1.2 | Configure TrGW Connection Point..... | 43 | +| 10.4.1.3 | Reserve and Configure TrGW Connection Point ..... | 46 | +| 10.4.1.4 | Release TrGW Termination..... | 49 | +| 10.4.1.5 | IP Bearer Released..... | 50 | +| 10.4.1.6 | Media Inactivity Detection ..... | 50 | +| 10.4.1.7 | Termination heartbeat indication..... | 51 | +| 10.4.1.8 | Change Through-Connection..... | 51 | +| 10.4.1.9 | ECN Failure Indication..... | 52 | +| 10.4.1.10 | Change Flow Direction..... | 52 | +| 10.4.2 | Non Call related Procedures ..... | 52 | +| Annex A (informative): | Void..... | 53 | +| Annex B (informative): | Change history..... | 54 | + +# --- Foreword + +This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +# --- 1 Scope + +The IM CN subsystem interworks with the external IP networks through the Mb reference point. + +This document details the interworking between the IM CN subsystem and external IP networks for IM service support. It addresses the issues of control plane interworking and, user plane interworking for specific interworking use cases. Clause 10 describes the IMS-Ix interface requirements in the form of Use Cases which require H.248 protocol procedures. Subclause 10.4 then details the additional Information Elements required to perform the specific procedures. + +The IP version Interworking, between IP version 4 (IETF RFC 791 [9] ) and IP version 6 (IETF RFC 2460 [10] ) detailed in terms of the processes and protocol mappings required in order to support both mobile originated and terminated calls. + +# --- 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 24.229: "Internet Protocol (IP) multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3". +- [2] IETF RFC 3261: "SIP: Session Initiation Protocol". +- [3] 3GPP TS 23.221: "Architectural requirements". +- [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.002: "Network architecture". +- [6] 3GPP TS 26.235: "Packet switched conversational multimedia applications; Default codecs". +- [7] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications". +- [8] 3GPP TS 23.228: "IP Multimedia Subsystem (IMS); Stage 2". +- [9] IETF RFC 791: "Internet Protocol". +- [10] IETF RFC 2460: "Internet Protocol, Version 6 (IPv6) Specification". +- [11] IETF RFC 2766: "Network Address Translation - Protocol Translation (NAT-PT)". +- [12] IETF RFC 2663: "IP Network Address Translator (NAT) Terminology and Considerations". +- [13] 3GPP TR 29.962 version 6.1.0: "Signalling interworking between the 3GPP profile of the Session Initiation Protocol (SIP) and non-3GPP SIP usage". +- [14] Void. +- [15] Void. +- [16] Void. +- [17] Void. + +- [18] IETF RFC 792: "Internet Control Message Protocol". +- [19] IETF RFC 2463: "Internet Control Message Protocol (ICMPv6) for the Internet Protocol Version 6". +- [20] Void. +- [21] Void. +- [22] Void. +- [23] Void. +- [24] Void. +- [25] 3GPP TS 29.238: "Interconnection Border Control Functions – Transition Gateway; H.248 Profile; Stage 3". +- [26] ITU-T Recommendation H.248.1 (05): "Gateway Control Protocol: Version 3". +- [27] Void. +- [28] 3GPP TS 23.205: "Bearer-independent circuit-switched core network; Stage 2". +- [29] 3GPP TS 29.235: "Interworking between SIP-I based circuit-switched core network and other networks". +- [30] Void. +- [31] IETF RFC 2474: "Definition of the Differentiated Services Field (DS Field) in the IPv4 and IPv6 Headers". +- [32] 3GPP TS 33.328: "IMS Media Plane Security". +- [33] IETF RFC 4568: "Session Description Protocol (SDP) Security Descriptions for Media Streams". +- [34] IETF RFC 3711: "The Secure Real-time Transport Protocol (SRTP)". +- [35] IETF RFC 5124: "Extended Secure RTP Profile for Real-time Transport Control Protocol (RTCP)-Based Feedback (RTP/SAVPF)". +- [36] 3GPP TS 26.114: "IP Multimedia Subsystem (IMS); Multimedia Telephony; Media handling and interaction". +- [37] IETF RFC 3168: "The Addition of Explicit Congestion Notification (ECN) to IP". +- [38] IETF RFC 6679: "Explicit Congestion Notification (ECN) for RTP over UDP". +- [39] 3GPP TS 29.079: "Optimal Media Routeing within the IP Multimedia Subsystem; Stage 3". +- [40] 3GPP TS 29.165: "Inter-IMS Network to Network Interface (NNI)". +- [41] 3GPP TS 23.237: "IP Multimedia subsystem (IMS) Service Continuity; Stage 2". +- [42] 3GPP TS 24.237: "IP Multimedia subsystem (IMS) Service Continuity; Stage 3". +- [43] 3GPP TS 23.334: "IP Multimedia Subsystem (IMS) Application Level Gateway (IMS-ALG) – IMS Access Gateway (IMS-AGW) interface: Procedures descriptions". +- [44] 3GPP TS 22.153: "Multimedia Priority Service". + +# 3 Definitions, symbols and abbreviations + +## 3.1 Definitions + +For the purposes of the present document, the terms and definitions given in 3GPP TR 21.905 [7] and the following apply: + +**IM CN subsystem:** (IP Multimedia CN subsystem) comprises of all CN elements for the provision of IP multimedia applications over IP multimedia sessions + +**IP multimedia session:** set of multimedia senders and receivers and the data streams flowing from senders to receivers IP multimedia sessions are supported by the IP multimedia CN Subsystem and are enabled by IP connectivity bearers (e.g. GPRS as a bearer). A user may invoke concurrent IP multimedia sessions. + +**MSC Server enhanced for ICS:** An MSC Server that supports the network based ICS functionality. + +**MSC Server enhanced for SRVCC:** An MSC Server that supports the network based SRVCC functionality. + +## 3.2 Symbols + +For the purposes of the present document, the following symbols apply: + +| | | +|----|---------------------------------------------------------------------------------------------------------| +| Mm | Reference Point between a CSCF/BGCF/IMS-ALG and an IP multimedia network. | +| Mx | Reference Point between a CSCF/BGCF/MSC Server enhanced for ICS/MSC Server enhanced for SRVCC and IBCF. | +| Mb | Reference Point defined in 3GPP TS 23.002 [5] and is IP based. | +| Ix | Reference Point between IBCF and TrGW or CS-IBCF and CS-TrGW. | + +## 3.3 Abbreviations + +For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [7] 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 [7]. + +| | | +|-------------|----------------------------------------------------------------------------------| +| ATCF | Access Transfer Control Function | +| ATGW | Access Transfer Gateway | +| B2BUA | Back-to-Back User Agent | +| BGCF | Breakout Gateway Control Function | +| CS-TrGW | CS (domain) TrGW | +| ECN | Explicit Congestion Notification | +| ECN-CE | ECN Congestion Experienced | +| IBCF | Interconnect Border Control Function | +| ICS | IMS Centralized Services | +| I-CSCF | Interrogating CSCF | +| IMS-ALG | IMS - Application Level Gateway | +| ITU-T | International Telecommunication Union – Telecommunication Standardization Sector | +| MboIP | Mb over IP | +| MPS | Multimedia Priority Service | +| MRFP | Multimedia Resource Function Processor | +| NAT/NAPT | Network Address Translation / Network Address and Port Translation | +| NA (P) T-PT | Network Address (and Port) Translation - Protocol Translation | +| OMR | Optimal Media Routeing | +| P-CSCF | Proxy CSCF | +| RTCP | Real Time Control Protocol | +| SCTP | Stream Control Transmission Protocol | +| SIP UA | SIP User Agent | +| UAC | User Agent Client | +| UAS | User Agent Server | +| THIG | Topology Hiding Internetwork Gateway | +| TRF | Transit and Roaming Function | +| TrGW | Translation GateWay | + +WAN + +Wide Area Network + +# 4 General + +## 4.1 General interworking overview + +The IM CN Subsystem interworks with SIP (IETF RFC 3261 [2]) based IP Multimedia networks. These IP Multimedia networks include: + +- SIP User Agents (SIP UAs); and +- SIP Servers. + +As such, the IM CN Subsystem has to be able to interwork to all of these above functional entities in the IP multimedia network, as there is a possibility that they all may be involved in an IM session. The general interworking model is shown in figure 1. The SIP based Multimedia networks may use IP version 4 (IETF RFC 791 [9]) or IP version 6 (IETF RFC 2460 [10]). + +![Figure 1: Interworking Model for IM CN Subsystem to IP Multimedia Network. The diagram shows the IM CN subsystem network on the left and the IP multimedia network on the right, separated by a dashed vertical line. The IM CN subsystem includes a P/I/S/E-CSCF, BGCF, Transit function, TRF, IBCF, MSC Server enhanced for ICS, for SRVCC or for DRVCC, and TrGW. The IP multimedia network includes a SIP Proxy and a SIP UA. Signalling (dashed lines) flows from the P/I/S/E-CSCF through the BGCF, Transit function, and TRF to the IBCF. The IBCF connects to the TrGW. The TrGW connects to the IP multimedia network via a solid line (Bearer). The IBCF also connects to the IP multimedia network via a dashed line (Signalling) labeled 'Mx'. The IP multimedia network contains a SIP Proxy and a SIP UA connected by a dashed line (Signalling) labeled 'IPv4 or IPv6'.](99bae07626f60f9ede10e2e387ef7051_img.jpg) + +Figure 1: Interworking Model for IM CN Subsystem to IP Multimedia Network. The diagram shows the IM CN subsystem network on the left and the IP multimedia network on the right, separated by a dashed vertical line. The IM CN subsystem includes a P/I/S/E-CSCF, BGCF, Transit function, TRF, IBCF, MSC Server enhanced for ICS, for SRVCC or for DRVCC, and TrGW. The IP multimedia network includes a SIP Proxy and a SIP UA. Signalling (dashed lines) flows from the P/I/S/E-CSCF through the BGCF, Transit function, and TRF to the IBCF. The IBCF connects to the TrGW. The TrGW connects to the IP multimedia network via a solid line (Bearer). The IBCF also connects to the IP multimedia network via a dashed line (Signalling) labeled 'Mx'. The IP multimedia network contains a SIP Proxy and a SIP UA connected by a dashed line (Signalling) labeled 'IPv4 or IPv6'. + +**Figure 1: Interworking Model for IM CN Subsystem to IP Multimedia Network** + +The UE uses the CSCF in order to communicate with the external IP multimedia network entities. + +If no IP version interworking or no NAT/NAPT between different realms is required, the CSCF can communicate with SIP UAs in an external IP multimedia network directly. + +If no IP version interworking or no NAT/NAPT between different realms is required, the CSCF can also communicate with SIP proxies in an external IP multimedia network directly, which in turn can then communicate with SIP UAs. + +To provide the IP version interworking or NAT/NAPT between different realms the functions of an IMS-ALG and a TrGW may be inserted between the CSCF and external IP Multimedia Network by configuration. The IMS-ALG and the TrGW may be implemented as a part of other physical entities in the IMS. + +NOTE: Other methods to provide IP version interworking are outside the scope of this release. + +## 4.2 Interworking scenarios + +3GPP specifications design the IM CN subsystem elements and interfaces to exclusively support IPv6. + +3GPP TS 23.221 [3] details the interoperability scenarios that an UE may experience when interworking with an external PDN. All of these IP transport layer interworking scenarios can apply to the application layer interworking scenarios detailed in subclause 4.2.1. + +### 4.2.1 UE with 3GPP SIP profile capability connecting to an external SIP device + +The procedures used by an UE with 3GPP SIP profile to connect to an external SIP device, which may lack 3GPP SIP profile capabilities, have been analysed in Release 6 within 3GPP TR 29.962 [13] and are specified in 3GPP TS 24.229 [1]. + +# 5 Network characteristics + +## 5.1 Key characteristics of IP Multimedia Networks + +The Internet is a conglomeration of networks utilising a common set of protocols. IP protocols are defined in the relevant IETF RFCs. The networks topologies may be based on LANs (e.g. Ethernet), Point-to-Point leased lines, PSTN, ISDN, X.25 or WANs using switched technology (e.g. SMDS, ATM). + +IP multimedia networks provide the ability for users to invoke IP multimedia applications in order to send and receive (where applicable) voice and data communications. One protocol used to manage IP multimedia sessions is the Session Initiation Protocol (SIP) (IETF RFC 3261 [2]). + +## 5.2 Key characteristics of UMTS IM CN Subsystem + +The UMTS IM CN subsystem uses the SIP protocol to manage IP multimedia sessions, and uses IP as the transport mechanism for both SIP session signalling and media transport. + +The UMTS IM CN subsystem shall support interworking with existing fixed and mobile voice and IP data networks, including PSTN, ISDN, Mobile and Internet. + +# 6 Interworking Reference Model for control plane interworking and user plane interworking + +## 6.0 Reference Model + +Figure 2 details the reference architecture required to support interworking between the IM CN subsystem and IP networks for IM services. Figure 3 details the reference architecture required to support interworking between the IMS and IP SIP networks supporting IP version 4. + +![Diagram of IM CN Subsystem to IP network interworking reference Architecture without IP version interworking. It shows a CSCF box on the left connected to a Multimedia IP network (represented by an oval) on the right via two interfaces: Mm (control plane) and Mb (user plane).](cd48273072c5c3a23e11fde892d1b6b6_img.jpg) + +The diagram illustrates the reference architecture for interworking between the IM CN Subsystem and IP networks. On the left, a rectangular box labeled 'CSCF' is shown. To its right, a dashed horizontal line represents the 'Mm' interface, which connects to a large oval on the right labeled 'Multimedia IP network'. Below the Mm interface, a solid horizontal line represents the 'Mb' interface, which also connects to the 'Multimedia IP network' oval. Both interfaces are marked with a small cross symbol where they meet the network boundary. + +Diagram of IM CN Subsystem to IP network interworking reference Architecture without IP version interworking. It shows a CSCF box on the left connected to a Multimedia IP network (represented by an oval) on the right via two interfaces: Mm (control plane) and Mb (user plane). + +NOTE: Multimedia IP networks may be connected via the Mb interface to various network entities, such as an UE (via an GTP Tunnel reaching to the GGSN), an MRFP, or an application server. + +**Figure 2: IM CN Subsystem to IP network interworking reference Architecture without IP version interworking** + +![Figure 3: Border Control Functions. A network diagram showing the IMS network architecture. On the left, a UE connects to an IP-CAN, which connects to a P-CSCF. The P-CSCF connects to an E-CSCF, which in turn connects to an S-CSCF. The S-CSCF connects to an I-CSCF, which connects to a BGCF. The I-CSCF connects to an IBCF (containing IMS-ALG and THIG). The IBCF connects to a TrGW (containing Border Control Functions). The TrGW connects to an 'Other IMS/SIP network'. A dashed line representing 'Signalling' connects the UE to the IP-CAN, P-CSCF, E-CSCF, S-CSCF, I-CSCF, BGCF, and IBCF. A solid line representing 'Bearer' connects the UE to the IP-CAN, P-CSCF, E-CSCF, S-CSCF, I-CSCF, BGCF, and IBCF. The IBCF also connects to a DNS and an HSS. The IBCF connects to the TrGW via an 'Ix' interface. The TrGW connects to the 'Other IMS/SIP network' via an 'Mb' interface. The IBCF connects to the 'Other IMS/SIP network' via an 'Mm' interface. The IBCF also connects to the S-CSCF via an 'Mx' interface. The IBCF also connects to the I-CSCF via an 'Mx' interface. The IBCF also connects to the BGCF via an 'Mx' interface. The IBCF also connects to the P-CSCF via an 'Mx' interface. The IBCF also connects to the E-CSCF via an 'Mx' interface. The IBCF also connects to the S-CSCF via an 'Mx' interface. The IBCF also connects to the I-CSCF via an 'Mx' interface. The IBCF also connects to the BGCF via an 'Mx' interface. The IBCF also connects to the P-CSCF via an 'Mx' interface. The IBCF also connects to the E-CSCF via an 'Mx' interface.](5a4e62bead259c258d069fd3663ea670_img.jpg) + +Figure 3: Border Control Functions. A network diagram showing the IMS network architecture. On the left, a UE connects to an IP-CAN, which connects to a P-CSCF. The P-CSCF connects to an E-CSCF, which in turn connects to an S-CSCF. The S-CSCF connects to an I-CSCF, which connects to a BGCF. The I-CSCF connects to an IBCF (containing IMS-ALG and THIG). The IBCF connects to a TrGW (containing Border Control Functions). The TrGW connects to an 'Other IMS/SIP network'. A dashed line representing 'Signalling' connects the UE to the IP-CAN, P-CSCF, E-CSCF, S-CSCF, I-CSCF, BGCF, and IBCF. A solid line representing 'Bearer' connects the UE to the IP-CAN, P-CSCF, E-CSCF, S-CSCF, I-CSCF, BGCF, and IBCF. The IBCF also connects to a DNS and an HSS. The IBCF connects to the TrGW via an 'Ix' interface. The TrGW connects to the 'Other IMS/SIP network' via an 'Mb' interface. The IBCF connects to the 'Other IMS/SIP network' via an 'Mm' interface. The IBCF also connects to the S-CSCF via an 'Mx' interface. The IBCF also connects to the I-CSCF via an 'Mx' interface. The IBCF also connects to the BGCF via an 'Mx' interface. The IBCF also connects to the P-CSCF via an 'Mx' interface. The IBCF also connects to the E-CSCF via an 'Mx' interface. The IBCF also connects to the S-CSCF via an 'Mx' interface. The IBCF also connects to the I-CSCF via an 'Mx' interface. The IBCF also connects to the BGCF via an 'Mx' interface. The IBCF also connects to the P-CSCF via an 'Mx' interface. The IBCF also connects to the E-CSCF via an 'Mx' interface. + +**Figure 3: Border Control Functions** + +**Mm reference point:** The call control protocol applied to the Mm interface between CSCF and external IP networks is SIP, IETF RFC 3261 [2], as detailed in 3GPP TS 24.229 [1]. SIP extension packages mandated by 3GPP are possibly not supported. + +**Mb reference point:** This interface is defined in 3GPP TS 23.002 [5] and is IP based. Further information is provided in 3GPP TS 29.061 [4] and 3GPP TS 26.235 [6]. + +**Mx reference point:** The protocol applied at the Mx reference point is specified in 3GPP TS 24.229 [1]. + +**Ix reference point:** The protocol applied at the Ix reference point is specified in 3GPP TS 29.238 [25]. + +## 6.1 Interworking Functional Entities + +### 6.1.1 IBCF + +This entity provides control plane functionality to connect entities following the 3GPP profile of SIP, 3GPP TS 24.229 [1], and external SIP entities following IETF RFC 3261 [2]. + +### 6.1.2 IMS-ALG + +IMS-ALG functionality resides in IBCF. An IMS-ALG provides the application level translation function for SIP and SDP in order to communicate between IPv6 and IPv4 SIP applications or, based on operator policies between different realms using the same IP version. The IBCF acts as a SIP B2BUA when IBCF performs IMS-ALG functionality. + +### 6.1.3 TrGW + +The TrGW is a NAT-PT/NAPT-PT, which uses a pool of globally unique IPv4 addresses for assignment to IPv6 nodes on a dynamic basis as sessions are initiated across the IP version boundaries. NAT-PT binds addresses in IPv6 network with addresses in IPv4 network and vice versa to provide transparent routing between the two IP domain without requiring any changes to end points. NAPT-PT provides additional translation of transport identifier (TCP, SCTP and UDP port numbers). More detailed information on the NAT-PT/NAPT-PT is given in IETF RFC 2766 [11] and IETF RFC 2663 [12]. + +The TrGW may provide the NAT/NAPT functionality between two disparate address realms. + +### 6.1.4 Acces Transfer Control Function + +The ATCF may reside within the IBCF to support "SRVCC enhanced with ATCF" procedures as described in 3GPP TS 23.237 [41] and 3GPP TS 24.237 [42]. In this case, the Ix reference point is used for IMS sessions that the ATCF decides to anchor at the ATGW to provide the following functions: + +- reservation and configuration of ATGW resources for media anchoring during PS session origination or termination; +- reconfiguration of ATGW resources during access transfer to the CS domain; +- release of ATGW resources upon completion of the access transfer or release of the session; +- media transcoding if the media that was used prior to the access transfer is not supported by the MSC server; +- IP version interworking if different IP versions are used between the access and the remote legs; and +- indication of IP realm during allocation of transport addresses/resources (the PS and CS accesses may be reachable via different IP realms). + +### 6.1.5 Acces Transfer GateWay + +The ATGW may reside within the TrGW to support "SRVCC enhanced with ATCF" procedures as described in 3GPP TS 23.237 [41] and 3GPP TS 24.237 [42]. If the IBCF supports the ATCF functionality (see subclause 6.1.4), the IBCF shall select a TRGW which supports the ATGW functionality. + +# --- 7 Control plane interworking + +## 7.1 SIP with 3GPP Profile to Standard SIP Interworking + +3GPP TS 24.229 [1] defines the procedures, which allow a 3GPP-IMS UE to connect to a standard SIP terminal. + +## 7.2 Additional interworking of protocols associated with services + +There is no impact beyond that specified in subclause 7.1 provided the necessary SIP extensions are supported on both sides of the interworking point. + +Based on operator policy and/or service level agreements the interworking of services may be restricted. + +Additional information related to interworking with services is provided in 3GPP TS 29.165 [40]. + +# --- 8 User Plane Interworking + +## 8.1 Overview + +The present specification addresses user plane interworking between codec types used for either speech or video. Codecs used for conversational services in the PS domain are as defined in 3GPP TS 26.235 [6] and 3GPP TS 26.114 [36]. + +## 8.2 Void + +## 8.3 Void + +# --- 9 IMS-ALG and TrGW functionality for NAPT and IP Version Interworking + +## 9.1 Control plane interworking + +### 9.1.1 Session Set-up + +#### 9.1.1.0 General + +The procedure described in clause 9.1.1 applies both for an SDP offer received from the external network and received from the IMS. + +If different IP versions are used in the external network and the IMS, the TrGW shall provide IP version interworking of the user plane. Otherwise, the TrGW provides NAPT functionality. + +#### 9.1.1.1 Receipt of the first SDP offer + +At the receipt of the first SDP offer from an offering network A the IMS-ALG shall: + +- Request the TrGW to allocate a termination towards an answering network B and provide IP address(es) and port number(s) from its pool for this termination. + +When the IMS-ALG has received the requested information from the TrGW, the IMS-ALG shall include the address(es) and port number(s) in a new offer, and sent this offer toward the network B. The IMS-ALG shall create a SIP message in accordance with the rules for the IMS-ALG described in subclause 9.1.4 with the following clarification: + +- The IP address(es) and port number(s) received from the TrGW for the termination towards network B shall replace the IP address(es) and port number(s) in the SDP. + +#### 9.1.1.2 Receipt of the first SDP answer + +At the receipt of the first SDP answer from network B the IMS-ALG shall: + +- Provide to the TrGW the address(es) and port number(s) as received in the c-line(s) and m-line(s) in the SDP answer as destinations for the termination towards answering network B; +- Request the TrGW to allocate a termination towards the offering network A and provide IP address(es) and port number(s) from its pool for this termination, and provide the IP address and port number received in the first SDP offer from network A as destination for this termination, unless this step has already been executed earlier, e.g. at the receipt of the SDP offer; and +- Requests the TrGW to bind the termination towards network A and the the termination towards network B to enable the routing of user plane traffic towards the IPv4 SIP network through the TrGW. + +NOTE: The binding request will be combined with the request to create terminations in the H.248 protocol + +When the IMS-ALG has received the requested information, the IMS-ALG shall send an SDP answer to the network A. The IMS-ALG shall create the SIP message in accordance with the rules for the IMS-ALG described in subclause 9.1.4 with the following clarification: + +- The IP address(es) and port number(s) received from the TrGW for the termination towards network A shall replace the received IP address(es) and port number(s) in the SDP. + +### 9.1.2 Void + +### 9.1.3 Change of connection information + +After the dialog is established it is possible for both ends of the session to change the connection data for the session. When the IMS-ALG/TrGW receives a SDP offer/answer where port number(s) or IP address(es) is included., there are four different possibilities: + +- 1) IP address(es) or/and port number(s) have been added. In this case additional binding(s) shall be provided by the IMS-ALG/TrGW as detailed for the first SDP offer in the subclauses above; +- 2) IP address(es) or/and port number(s) have been deleted. In this case binding(s) shall be made free by the IMS-ALG/TrGW; +- 3) IP address(es) and port number(s) have been reassigned of the users. In this case the binding(s) shall reflect the reassignment; and +- 4) No change has been made to the IP address(es) and port number(s). In this case no change shall be made to the existing binding(s). + +### 9.1.4 Interworking of SIP messages + +The IMS-ALG behaves as a SIP B2BUA when interworking SIP messages. The IMS-ALG shall forward all SIP messages transparently with respect to all methods, result codes, headers and attachments except as follows: + +- The IMS-ALG modifies SDP according to subclauses 9.1.1, 9.1.2 and 9.1.3; +- When forwarding an incoming SIP request, the IMS-ALG should perform UAC procedures towards the intended target according to IETF RFC 3261 [2], by modifying those headers necessary to ensure that all transactions within the dialog pass through the IMS-ALG; +- When forwarding an incoming SIP response, the IMS-ALG should perform UAS procedures towards the originator of the corresponding request according to IETF RFC 3261 [2], by modifying those headers necessary to ensure that all transactions within the dialog pass through the IMS-ALG; +- The IMS-ALG may perform any appropriate error recovery procedures in the event that an incoming message contains errors inconsistent with the forwarding procedures above; and +- The IBCF can perform screening of SIP request and SIP responses based on local policy as described in subclause 5.10.6 of 3GPP TS 24.229 [1]. + +At the receipt of a SIP BYE request, SIP CANCEL request or non-200 SIP final response, the IMS-ALG shall release the session and request the TrGW to release the bindings established for the session. + +## 9.2 User plane transport + +### 9.2.1 Payload transport + +The TrGW shall use the established bindings described in subclause 9.1 to transport the messages between the network A and the network B in the following way. + +At the receipt of a payload message the TrGW shall: + +- replace the received destination IP address(es) and port number(s) in the payload message with the corresponding IP address(es) and port number(s) that have been signalled by the IBCF; and +- replace the received source IP address(es) and port number(s) in the payload message with the corresponding IP address(es) and port number(s) the TrGW allocated at its own terminations. + +### 9.2.2 IP header interworking + +#### 9.2.2.1 IPv4 to IPv6 + +When the TrGW receives an IPv4 message the following codings shall be set in the IPv6 headers of the message sent to the IPv6 network. + +- If the DF bit is set and the packet is not a fragment (i.e., the MF flag is not set and the Fragment Offset is zero) The IPv6 headers shall be set as described in table 1; +- If the DF bit is not set or the packet is a fragment the IPv6 headers shall be set as described in table 2. + +**Table 1: Derivation of IPv6 Header from IPv4 header (no fragmentation)** + +| IPv6 field | Value | +|---------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Version | 6 | +| Traffic Class: | The default behaviour is that the value of the IPv6 field Traffic Class field is the value of the IPv4 Type Of Service field (all 8 bits are copied). An implementation of a TrGW should also provide the ability to ignore the value of the IPv4 Type of Service and always set the IPv6 traffic class field to zero. | +| Flow label | The IPv6 Flow Label Field is set to 0 (all zero bits). | +| Payload Length | The IPv6 Payload Length field value is the IPv4 Total length field value minus the size of the IPv4 header and IPv4 options field length, if present. | +| Next Header | The IPv6 Next Header value is copied from IPv4 Protocol field | +| HopLimit: | The IPv6 Hop Limit value is The value of IPv4 field Time To Live minus 1. | +| Source Address | Shall be handled as the addresses of the payload message as described in subclause 9.2.1. | +| Destination Address | Shall be handled as the addresses of the payload message as described in subclause 9.2.1. | + +**Table 2: Derivation of IPv6 Header from IPv4 Header (fragmentation)** + +| IPv6 field | Value | +|----------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Version | 6 | +| Traffic Class: | The default behaviour is that the value of the IPv6 field Traffic Class field is the value of the IPv4 Type Of Service field (all 8 bits are copied). An implementation of a TrGW should also provide the ability to ignore the value of the IPv4 Type of Service and always set the IPv6 traffic class field to zero. | +| Flow label | The IPv6 Flow Label Field is set to 0 (all zero bits). | +| Payload Length | The IPv6 Payload Length field value is the IPv4 Total length field value plus 8 for the fragment header minus the size of the IPv4 header and IPv4 options field length, if present. | + +| IPv6 field | Value | +|--------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Version | 6 | +| Next Header | The IPv6 Next header field is set to Fragment header (44). | +| Hop Limit: | The IPv6 Hop Limit value is The value of IPv4 field Time To Live minus 1. | +| Source Address | Shall be handled as the addresses of the payload message as described in subclause 9.2.1. | +| Destination Address | Shall be handled as the addresses of the payload message as described in subclause 9.2.1. | +| Fragments headers
a) next header
b) fragment Offset
c) More fragment bit
d) Identification | Copied from IPv4 Protocol field.
Copied from the IPv4 Fragment offset field.
Copied from the value of the more fragment bit in the IPv4 flags field.
The value of this field should be mapped from the triple of the source address, destination address and IPv4 identification field of the incoming packet/fragments to a unique value for the source and destination address of the outgoing IPv6 packet/fragments. | + +#### 9.2.2.2 Abnormal cases + +If IPv4 options are present in the IPv4 packet, they should be ignored i.e., there is no attempt to translate them. However, if an unexpired source route option is present then the packet shall instead be discarded, and an ICMPv4 "destination unreachable/source route failed" Type 3/Code 5 error message shall be returned to the sender as defined in IETF RFC 792 [16]. + +When a translator receives the first fragment of a fragmented UDP IPv4 packet and the checksum field is zero the translator should drop the packet and generate a system management event specifying at least the IP addresses and port numbers in the packet. When the translator receives fragments other than the first it should silently drop the packet since there is no port information to log. + +When a translator receives an unfragmented UDP IPv4 packet and the checksum field is zero the translator shall compute the missing UDP checksum as part of translating the packet. Also, the translator should maintain a counter of how many UDP checksums are generated in this manner. + +#### 9.2.2.3 IPv6 to IPv4 + +When the TrGW receives an IPv6 message the following codings shall be set in the IPv4 headers of the message sent to the IPv4 network. + +- If there is no IPv6 fragment header, the IPv4 header fields shall be set as described in Table 3; +- if there is an IPv6 fragment header, the IPv4 header fields shall be set as described in Table 4. + +**Table 3: Derivation of IPv4 Header from IPv6 Header (no fragmentation)** + +| IPv4 field | Value | +|------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Version | 4 | +| Internet header length | 5 (No IPv4 options) | +| Type of Service | The default behaviour is that the value of the IPv4 field Type of service field is the value of the IPv6 Traffic class field (all 8 bits are copied). An implementation of a TrGW should also provide the ability to ignore the value of the IPv6 Traffic Class and always set the IPv4 Type of Service field to zero. | +| Total length | The IPv4 Total Length field value is the IPv6 Payload length value plus the size of the IPv4 headers. | +| Identification | All bits are set to zero. | +| Flags | The more fragment flag is set to zero. The Don't fragment flag is set to one. | +| Fragment offset | Set to zero. | +| Time to live (TTL) | The value of the field shall be set to the received IPv6 Hop Limit field value minus 1. | +| Protocol | The IPv4 field Protocol shall be set to the value of IPv6 field The next header value. | +| Header checksum | Computed once the IPv4 header has been created. | +| Source Address | Shall be handled as the addresses of the payload message as described in subclause 9.2.1. | +| Destination Address | Shall be handled as the addresses of the payload message as described in subclause 9.2.1. | + +**Table 4: Derivation of IPv4 Header from IPv6 Header (fragmentation)** + +| IPv4 field | Value | +|---------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Version | 4 | +| Internet header length | 5 (No IPv4 options) | +| Type of Service and Precedence: | The default behaviour is that the value of the IPv4 field Type of service field is the value of the IPv6 Traffic class field (all 8 bits are copied). An implementation of a TrGW should also provide the ability to ignore the value of the IPv6 Traffic Class and always set the IPv4 Type of Service field to zero. | +| Total length | The IPv4 Total Length field value is the IPv6 Payload length value plus the size of the IPv4 headers minus 8 for the Fragment header. | + +| | | +|---------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Identification | The value of this field should be mapped from the triple of the source address, destination address and IPv6 fragmentation header field "identification" of the incoming packet/fragments to a unique value for the source and destination address of the outgoing IPv4 packet/fragments. | +| Flags | The IPv4 More Fragments flag is copied from the IPv6 M flag in the IPv6 Fragment header the IPv4. The Don't Fragments flag is set to zero allowing this packet to be fragmented by IPv4 routers. | +| Time to live (TTL) | The value of the field shall be set to the received IPv6 Hop Limit field value minus 1. | +| Protocol | The IPv4 field Protocol shall be set to the value of IPv6 field The next header value. | +| Header checksum | Computed once the IPv4 header has been created. | +| Source Address | Shall be handled as the addresses of the payload message as described in subclause 9.2.1. | +| Destination Address | Shall be handled as the addresses of the payload message as described in subclause 9.2.1. | + +#### 9.2.2.4 Abnormal cases + +If any of an IPv6 hop-by-hop options header, destination options header, or routing header with the Segments Left field equal to zero are present in the IPv6 packet, they are ignored i.e., there is no attempt to translate them. However, the Total Length field and the Protocol field shall be adjusted to "skip" these extension headers. + +If a routing header with a non-zero Segments Left field is present then the packet shall be translated, and an ICMPv6 "parameter problem/ erroneous header field encountered" Type 4/Code 0 error message as defined in IETF RFC 2463 [17], with the Pointer field indicating the first byte of the Segments Left field should be returned to the sender. + +### 9.2.3 Fragmentation + +If the DF flag is not set and the IPv4 packet will result in an IPv6 packet larger than 1280 bytes the TrGW shall prior to transferring it in the IPv6 network: + +- Add the fragment header to the message; and +- fragment the IPv4 packets so that their length, excluding the IPv4 header, is at most 1232 bytes (1280 minus 40 for the IPv6 header and 8 for the Fragment header). + +### 9.2.4 Abnormal cases + +As a part of decrementing the Time To Live /Hop Limit value and the TrGW discovers that the zero value is reached the TrGW shall send an ICMPv4/ICMPv6 message with the error "time to live exceeded in transit" type 11 code 0 as defined in IETF RFC 792 [16] and "hop limit exceeded in transit" type 3 code 0 as defined in IETF RFC 2463 [19]. + +# 10 IBCF – TrGW Interactions + +## 10.1 Overview + +### 10.1.1 General + +The present specification describes Ix signalling procedures and their interaction with SIP signalling in the control plane, and with user plane procedures. Each scenario or "use case" is described in a separate subclause within subclause 10.2. 3GPP TS 29.238 [25] maps these signalling procedures to H.248 messages and defines the required H.248 profile (which provides details of used packages and parameters). + +### 10.1.2 Network model + +Figure 10.1.2.1 shows the network model. The broken line represents the call control signalling. The dotted line represents the user plane. The IBCF uses one context with two terminations in the TrGW. + +![Figure 10.1.2.1: Network model diagram showing IBCF and TrGW components and their connections.](04f51626e2e10a16e3eb2c4b33cb2742_img.jpg) + +The diagram illustrates the network model. At the top is a box labeled 'IBCF'. A horizontal green dashed line passes through the center of the IBCF box. Below the IBCF box is a vertical blue line connecting it to a second box labeled 'TrGW'. Inside the TrGW box, there is a symbol representing two terminations, labeled 'T1' and 'T2', connected by a switch-like symbol. A horizontal red dotted line passes through the center of the TrGW box, aligned with the terminations T1 and T2. + +Figure 10.1.2.1: Network model diagram showing IBCF and TrGW components and their connections. + +Figure 10.1.2.1: Network model + +### 10.1.3 Example Call Flow + +#### 10.1.3.1 Basic Procedures + +##### 10.1.3.1.1 Call Establishment + +Figure 10.1.3.1.1.1 depicts the signalling flow for a call setup either from or toward an external network. + +![Sequence diagram showing the interaction between TrGW and IBCF for TrGW functionality. The diagram includes 16 steps: 1. IBCF receives SDP offer; 2. IBCF detects need for TrGW; 3. IBCF sends H.248 ADD req to TrGW; 4. TrGW creates outgoing termination T1; 5. TrGW sends H.248 ADD resp; 6. IBCF modifies SDP offer; 7. IBCF sends SDP offer to network; 8. IBCF receives SDP answer; 9. IBCF sends H.248 MOD req to TrGW; 10. TrGW configures outgoing termination T1; 11. TrGW sends H.248 MOD Resp; 12. IBCF sends H.248 ADD req for incoming termination; 13. TrGW creates incoming termination T2; 14. TrGW sends H.248 ADD Resp; 15. IBCF modifies SDP answer; 16. IBCF sends SDP answer to network. Brackets on the right indicate phases: Reserve TrGW Connection Point, Configure TrGW Connection Point, and Reserve And Configure TrGW Connection Point.](81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg) + +``` + +sequenceDiagram + participant IBCF + participant TrGW + Note right of IBCF: 1. SDP offer (IP2o, P2o) + Note right of IBCF: 2. Use case X detected that needs TrGW functionality + Note right of IBCF: Reserve TrGW Connection Point (, Change Through-Connection) + IBCF->>TrGW: 3. H.248 ADD req (C= ?, T= ?, LAddr=?, LPort=?) + Note left of TrGW: 4. Create outgoing termination T1 + TrGW->>IBCF: 5. H.248 ADD resp. (C=C1, T=T1, LAddr=IP1o, LPort=P1o) + Note right of IBCF: 6. Modify SDP offer + IBCF-->>Network: 7. SDP offer (IP1o, P1o) + Network-->>IBCF: 8. SDP answer (IP1a, P1a) + Note right of IBCF: Configure TrGW Connection Point (, Change Through-Connection) + IBCF->>TrGW: 9. H.248 MOD req (C= C1, T= T1, RAddr=IP1a, RPort=P1a) + Note left of TrGW: 10. Configure Outgoing Termination T1 + TrGW->>IBCF: 11. H.248 MOD Resp (C= C1, T= T1) + Note right of IBCF: Reserve And Configure TrGW Connection Point (, Change Through-Connection) + IBCF->>TrGW: 12. H.248 ADD req (C= C1, T= ?, LAddr=?, LPort=?, RAddr=IP2o, RPort=P2o) + Note left of TrGW: 13. Create incoming Termination T2 + TrGW->>IBCF: 14. H.248 ADD Resp (C= C1, T= T2, LAddr=IP2a, LPort=P2a, RAddr=IP1a, RPort=P1a) + Note right of IBCF: 15. Modify SDP answer + IBCF-->>Network: 16. SDP answer(IP2a, P2a) + +``` + +Sequence diagram showing the interaction between TrGW and IBCF for TrGW functionality. The diagram includes 16 steps: 1. IBCF receives SDP offer; 2. IBCF detects need for TrGW; 3. IBCF sends H.248 ADD req to TrGW; 4. TrGW creates outgoing termination T1; 5. TrGW sends H.248 ADD resp; 6. IBCF modifies SDP offer; 7. IBCF sends SDP offer to network; 8. IBCF receives SDP answer; 9. IBCF sends H.248 MOD req to TrGW; 10. TrGW configures outgoing termination T1; 11. TrGW sends H.248 MOD Resp; 12. IBCF sends H.248 ADD req for incoming termination; 13. TrGW creates incoming termination T2; 14. TrGW sends H.248 ADD Resp; 15. IBCF modifies SDP answer; 16. IBCF sends SDP answer to network. Brackets on the right indicate phases: Reserve TrGW Connection Point, Configure TrGW Connection Point, and Reserve And Configure TrGW Connection Point. + +1. The IBCF receives an SDP offer in SIP signalling. +2. The IBCF detects that one of the CS-TrGW functions is required, e.g. NAPT/NAT. +3. The IBCF sends a H.248 ADD command to create the outgoing termination and to request resources to execute TrGW function. +4. The TrGW creates the outgoing termination. +5. The TrGW replies to IBCF with a H.248 Add reply command and provides the local address and port of the outgoing termination. +6. The IBCF replaces the IP address inside the SDP using the information coming from TrGW. +7. SDP offer is sent to the network at the outgoing side. +8. SDP answer is received by IBCF. + +9. The IBCF sends a H.248 MOD command to configure the outgoing termination with address and port information received in the SDP answer. + 10. The TrGW configures the outgoing termination. + 11. The TrGW replies to IBCF with a H.248 MOD reply command. + 12. The IBCF sends a H.248 ADD command to create the incoming termination and to request resources to execute TrGW function. + 13. The TrGW creates the incoming termination. + 14. The TrGW replies to the IBCF with a H.248 Add reply command and provides the local address and port of the incoming termination. +- NOTE 1: Steps 12 to 14 may also be executed after step 2. +15. The IBCF replaces the IP address inside the SDP using the information coming from TrGW. + 16. SDP answer is sent to the network at the incoming side. + +**Figure 10.1.3.1.1.1: IBCF and TrGW interaction at Call establishment.** + +When creating the termination towards the IMS network or towards external networks, the IBCF may also indicate that the IP Interface Type is "MboIP". + +NOTE : Other values may be indicated by a CS-IBCF, as detailed in 3GPP TS 29.235 [29]. + +The IP Interface Type allows the TrGW to collect statistics per interface type associated with the RTP bearer termination. The provision of these statistics is outside of the scope of this specification. + +##### 10.1.3.1.2 Call Release + +Figure 10.1.3.1.2.1 depicts the signalling flow for a call release. + +![Sequence diagram showing the interaction between TrGW and IBCF for call release. The process starts with an event causing release at the IBCF, followed by H.248 SUB requests and responses for outgoing and incoming terminations, with corresponding destroy operations at the TrGW.](7d3d5fb5d09c0cd35a9d637be241651e_img.jpg) + +``` + +sequenceDiagram + participant IBCF + participant TrGW + Note right of IBCF: 1. Event causing release + IBCF->>TrGW: 2. H.248 SUB req (C=C1, T=T1) + Note left of TrGW: 3. Destroy outgoing termination T1 + TrGW-->>IBCF: 4. H.248 SUB resp. (C=C1, T=T1) + Note right of IBCF: Release TrGW Termination + IBCF->>TrGW: 5. H.248 SUB req (C=C1, T=T2) + Note left of TrGW: 6. Destroy incoming termination T2 + TrGW-->>IBCF: 7. H.248 SUB resp. (C=C1, T=T2) + Note right of IBCF: Release TrGW Termination + +``` + +Sequence diagram showing the interaction between TrGW and IBCF for call release. The process starts with an event causing release at the IBCF, followed by H.248 SUB requests and responses for outgoing and incoming terminations, with corresponding destroy operations at the TrGW. + +1. The IBCF identifies that the call is to be release. Typically this will be by the receipt of a SIP BYE request. +2. The IBCF sends a H.248 SUB command to release the outgoing termination. +3. The TrGW destroys the outgoing termination. +4. The TrGW replies to IBCF with a H.248 SUB reply command. +5. The IBCF sends a H.248 SUB command to release the incoming termination. +6. The TrGW destroys the incoming termination. +7. The TrGW replies to IBCF with a H.248 SUB reply command. + +NOTE 1: Steps 5 to 7 may also be executed before steps 2 to 4 or in parallel with steps 2 to 4. + +NOTE 2: Rather than releasing the two terminations separately, the IBCF may request the TrGW to release both terminations in a single request. + +**Figure 10.1.3.1.2.1: IBCF and TrGW interaction at Call release** + +## 10.2 Main Functions supported at the Ix Interface + +### 10.2.0 Introduction + +The following functions shall be supported by the TrGW: + +- Gate Management including: + - o Opening/closing of gates; + +- o Remote source address filtering; and + - o Remote source port filtering; +- QoS packet marking (differentiated services); +- NAPT and IP Version Interworking; +- Bandwidth policing; +- Hanging termination detection; +- IP Realm Indication; +- Media Control; and +- Through-Connection. + +Additionally, the following functions may be supported by the TrGW: + +- Resource allocation per flow; +- Media Inactivity Detection; +- IP Realm Availability; +- Optimal Media Routeing; +- Explicit Congestion Notification support; +- Emergency Call; +- IMS end-to-end media plane security; +- Access Transfer procedures with media anchored in ATGW; and +- Multimedia Priority Service. + +### 10.2.1 NAPT and IP version interworking + +NAPT and IP version interworking is documented in clause 9. + +The IP Address and port conversion is configured by the standard Ix interactions at call setup depicted in figure 10.1.3.1.1.1. + +IP address and port conversion is mandatory every time a TrGW is inserted into the path for any reason to guarantee that all IP packets are routed through this entity. + +### 10.2.2 Gate Management + +The procedures in subclause A.7.1.2.2.3 of 3GPP TS 29.235 [29] are applicable. + +### 10.2.3 RTCP Handling + +The procedures in subclause A.7.1.2.2.7 of 3GPP TS 29.235 [29] are applicable. + +### 10.2.4 IP Realm Indication + +Whenever requesting a new IP media-path (i.e. creation of IP bearer terminations), the TrGW may indicate the correspondent IP realm/domain to the TrGW. The TrGW shall assign the IP termination in the IP realm indicated. The same IP realm shall be applied to all media streams associated with the termination. The IP realm identifier shall not be changed after the initial assignment. + +A default IP realm may be configured such that if the TrGW has not received the IP realm identifier and the TrGW supports multiple IP realms then the default IP realm shall be used. + +### 10.2.5 Media Control + +The transcoding functionality, where the TrGW processes and possibly converts application / media data (like e.g. RTP payload) is optional for the TrGW and IBCF to support. + +The IBCF shall determine the TrGW transcoding capability through provisioning and MGW selection, outside the scope of this specification. + +IBCF procedures to offer transcoding in SIP/SDP signalling are described in 3GPP TS 23.228 [8] and in 3GPP TS 24.229 [1]. The IBCF shall only apply those transcoding procedures if an attached TrGW supports transcoding. For media with "RTP/SAVP" (see IETF RFC 3711 [34]) or "RTP/SAVPF" (see IETF RFC 5124 [35]) as transport protocol, the IBCF shall not offer or apply transcoding. + +If the IBCF and available TrGW support transcoding, the IBCF may add codecs to a SDP offer within a SIP request. + +If the IBCF and available TrGW do not support transcoding, or if the IBCF chooses not to offer transcoding, the IBCF shall pass SDP offers without adding codecs to the SDP offer and the IBCF shall pass SDP answers without modification to the contained codecs. + +If the IBCF does not offer or apply transcoding procedures (as described above) but inserts the TrGW for any other reason, the IBCF shall either not signal media related information to the TrGW, or it shall signal the same media related information for all interconnected terminations (i.e. identical media configurations for the two connected H.248 stream endpoints). + +If the IBCF does not offer or apply transcoding but signals media attributes to a TrGW that does not support transcoding without having seized the peer termination (see figure 10.2.5.3, Step 3) the TrGW shall accept this request even though it cannot reserve any transcoding resources related to this media. When the peer termination is seized and configured it shall be configured with the same media related sub-fields in the media descriptor as for the first termination. If the selected codec is not the same as the codec configured at the first termination then this termination shall be modified before the peer termination is seized. + +NOTE 1: The signalling of such codec related information by an IBCF to a TrGW not supporting transcoding is an implementation decision. + +NOTE 2: A TrGW not supporting transcoding can use such codec related information to learn that RTCP ports need to be reserved, and to derive information about packet size and frequency useful for internal resource reservation. + +If the IBCF and available TrGW support transcoding and the IBCF includes in a SDP offer additional codecs, the following procedures apply: + +- The IBCF may seize a termination towards the terminating user, using the "Reserve TrGW Connection Point" procedure before sending an SDP offer with added codecs to the terminating user. The IBCF may signal media related information to the TrGW or omit media when adding the IP termination at this stage. + +NOTE 3: The signalling of media related information to a MGW requires that it reserve the indicated resources before returning a positive response to the H.248 command, by omitting media related information the TrGW does not need to reserve any associated resources at this stage. + +- When the IBCF receives the SDP answer from the terminating user, the IBCF shall check if any of the codecs offered by the originating side are contained in the answer. +- If only the codecs inserted by the IBCF are contained in the answer, the IBCF shall configure the TrGW to transcode. If it previously performed a "Reserve TrGW Connection Point" procedure it shall configure the TrGW using the "Configure TrGW Connection Point" procedure towards the termination on the terminating user side by supplying the media returned in the answer from the terminating user, otherwise it shall perform a "Reserve and Configure TrGW Connection Point" procedure. Within those procedures, the IBCF shall supply the media returned in the answer from the terminating user. If the IBCF seized the termination only at this point in time, it shall send the IP address and port information received from the TrGW in the acknowledgment to the "Reserve and Configure TrGW Connection Point" procedure towards the terminating user in a new SDP offer. The IBCF shall perform the "Reserve and Configure TrGW Connection Point" procedure towards the termination on the originating user side, supplying the preferred media offered by the originating side. + +- If the returned SDP contains media offered by the originating user no transcoding at the TrGW is required. If the IBCF previously performed the "Reserve TrGW Connection Point" procedure the IBCF shall configure the TrGW accordingly by either either supplying the same media related information for all interconnected terminations or by omitting the media related information. + +Some basic use cases are depicted in figures 10.2.5.1, 10.2.5.2, and 10.2.5.3. + +![Sequence diagram showing the interaction between TrGW and IBCF for media resource reservation and codec negotiation.](90ddb84c323b956e2d50a54d3f870566_img.jpg) + +``` + +sequenceDiagram + participant IBCF + participant TrGW + + Note right of IBCF: 1. SDP offer (IP2o, P2o, codec1, codec2) + Note right of IBCF: 2. IBCF supports transcoding and supports additional codecs, the IBCF inserts additional codecs in the SDP offer + IBCF->>TrGW: 3. H.248 ADD req (C= ?, T= ?, LAddr=?, LPort=?, Local Resources="-" or codec1 or codec 2 or codec3) + Note right of TrGW: Reserve TrGW Connection Point + TrGW->>IBCF: 4. Create outgoing termination T1 + TrGW->>IBCF: 5. H.248 ADD resp. (C=C1, T=T1, LAddr=IP1o, LPort=P1o) + Note right of IBCF: 6. Modify SDP offer + IBCF-->>TrGW: SDP offer (IP1o, P1o, codec 1, codec2, codec3) + TrGW-->>IBCF: 8. SDP answer (IP1a, P1a, codec 1) + Note right of IBCF: Configure TrGW Connection Point + IBCF->>TrGW: 9. H.248 MOD req (C= C1, T= T1, RAddr=IP1a, RPort=P1a, Local Resources="-" or codec1, Remote Resources="-" or codec1) + TrGW->>IBCF: 10. Configure Outgoing Termination T1 + TrGW->>IBCF: 11. H.248 MOD Resp (C= C1, T= T1) + Note right of IBCF: Reserve And Configure TrGW Connection Point + IBCF->>TrGW: 12. H.248 ADD req (C= C1, T= ?, LAddr=?, LPort=?, RAddr=IP2o, RPort=P2o, Local Resources="-" or codec1, Remote Resources="-" or codec1) + TrGW->>IBCF: 13. Create incoming Termination T2 + TrGW->>IBCF: 14. H.248 ADD Resp (C= C1, T= T2, LAddr=IP2a, LPort=P2a, RAddr=IP2o, RPort=P2o) + Note right of IBCF: 15. Modify SDP answer + IBCF-->>TrGW: 16. SDP answer(IP2a, P2a, codec 1) + +``` + +The sequence diagram illustrates the interaction between an IBCF (Interworking Border Controller) and a TrGW (Trunk Gateway). The process begins with the IBCF receiving an SDP offer (step 1) and adding additional codecs (step 2). It then sends an H.248 ADD request to the TrGW (step 3) to reserve resources and create an outgoing termination (step 4). The TrGW responds (step 5). The IBCF modifies the SDP offer (step 6) and sends it to the TrGW. The TrGW responds with an SDP answer (step 8). The IBCF then sends an H.248 MOD request (step 9) to configure the TrGW connection point. The TrGW configures the outgoing termination (step 10) and responds (step 11). The IBCF sends another H.248 ADD request (step 12) to reserve and configure the TrGW connection point for an incoming termination. The TrGW creates the incoming termination (step 13) and responds (step 14). Finally, the IBCF modifies the SDP answer (step 15) and sends it to the TrGW (step 16). + +Sequence diagram showing the interaction between TrGW and IBCF for media resource reservation and codec negotiation. + +1. The IBCF receives an SDP offer in SIP signalling. +2. The IBCF adds additional codecs to the subsequent SDP offer, giving priority to those offered by the preceding node/network. +3. In this example the IBCF seizes a TrGW prior to sending the new SDP offer; as this scenario is preparing for a possible transcoding in the TrGW then a TrGW supporting media shall be seized. The IBCF sends a H.248 ADD request command to create the outgoing termination and to request IP resources to execute TrGW function. As no media transcoding is yet known to be needed this may be indicated by omitting media related sub-fields in the media descriptor (i.e. signalling "-"). Alternatively the preferred codec (e.g. codec 1) may be signalled in order to reserve this resource in the event that transcoding was required. +4. The TrGW creates the outgoing termination. + +5. The TrGW replies to IBCF with a H.248 ADD reply command and provides the local address and port of the outgoing termination. +6. The IBCF replaces the IP address inside the SDP offer using the information coming from TrGW +7. The IBCF forwards the new SDP offer to the succeeding node. +8. The SDP answer is received by IBCF. In this example the codec1 received in the original SDP offer in step1 has been selected by the succeeding network/terminating UE and the IBCF determines that transcoding is not required. +9. The IBCF sends a H.248 MOD request command to configure the outgoing termination with address and port information received in the SDP answer. As no media transcoding is needed this may be indicated by omitting media related sub-fields in the media descriptor (i.e. signalling "-"). Alternatively the selected codec (codec 1) may be signalled. +10. The TrGW configures the outgoing termination. +11. The TrGW replies to IBCF with a H.248 MOD reply command. +12. The IBCF sends a H.248 ADD request command to create the incoming termination to configure this termination with remote address and port information and to request resources to execute TrGW function. As no media transcoding is needed this may be indicated by omitting media related sub-fields in the media descriptor (i.e. signalling "-"). Alternatively the selected codec received in step 8 (Codec 1) may be signalled. +13. The TrGW creates the incoming termination. +14. The TrGW replies to the IBCF with a H.248 ADD reply command and provides the local address and port of the incoming termination. +15. The IBCF replaces the IP address inside the SDP using the information coming from TrGW. +16. The SDP answer is sent to the network at the incoming side. + +**Figure 10.2.5.1: IBCF and TrGW interaction when the IBCF offers additional codecs but no transcoding is required, and the TrGW is seized in advance.** + +![Sequence diagram showing the interaction between TrGW and IBCF for media resource reservation and configuration. The diagram consists of 16 numbered steps with various SIP and H.248 messages. Annotations on the right side group steps into phases: 'Reserve TrGW Connection Point', 'Configure TrGW Connection Point', and 'Reserve And Configure TrGW Connection Point'.](9c1d3678db4a12d5864cb2a4def1135d_img.jpg) + +``` + +sequenceDiagram + participant IBCF + participant TrGW + Note right of IBCF: 1. SDP offer (IP2o, P2o, codec1, codec2) + IBCF->>TrGW: 2. IBCF supports transcoding and supports additional codecs + Note right of IBCF: Reserve TrGW Connection Point + IBCF->>TrGW: 3. H.248 ADD req (C= ?, T= ?, LAddr=?, LPort=?, Local Resources="-" or codec1 or codec 2 or codec 3) + TrGW->>IBCF: 4. Create outgoing termination T1 + IBCF->>TrGW: 5. H.248 ADD resp. (C=C1, T=T1, LAddr=IP1o, LPort=P1o) + Note right of IBCF: Configure TrGW Connection Point + IBCF->>TrGW: 6. Modify SDP offer + Note left of IBCF: SDP offer (IP1o, P1o, codec 1, codec 2, codec 3) + IBCF->>TrGW: 8. SDP answer (IP1a, P1a, codec 3) + IBCF->>TrGW: 9. H.248 MOD req (C= C1, T= T1, RAddr=IP1a, RPort=P1a, Local Resources= codec3 Remote Resources= codec3) + TrGW->>IBCF: 10. Configure Outgoing Termination T1 + IBCF->>TrGW: 11. H.248 MOD Resp (C= C1, T= T1) + Note right of IBCF: Reserve And Configure TrGW Connection Point + IBCF->>TrGW: 12. H.248 ADD req (C= C1, T= ?, LAddr=?, LPort=?, RAddr=IP2o, RPort=P2o, Local Resources=codec1 or codec2, Remote Resources=codec1 or codec2) + TrGW->>IBCF: 13. Create incoming Termination T2 + IBCF->>TrGW: 14. H.248 ADD Resp (C= C1, T= T2, LAddr=IP2a, LPort=P2a, RAddr=IP2o, RPort=P2o) + Note right of IBCF: 15. Modify SDP answer + Note right of IBCF: 16. SDP answer(IP2a, P2a, codec1 or codec2) + +``` + +Sequence diagram showing the interaction between TrGW and IBCF for media resource reservation and configuration. The diagram consists of 16 numbered steps with various SIP and H.248 messages. Annotations on the right side group steps into phases: 'Reserve TrGW Connection Point', 'Configure TrGW Connection Point', and 'Reserve And Configure TrGW Connection Point'. + +1. The IBCF receives an SDP offer in SIP signalling. +2. The IBCF adds additional codecs to the subsequent SDP offer, giving priority to those offered by the preceding node/network. +3. In this example the IBCF seizes a TrGW prior to sending the new SDP offer; as this scenario is preparing for a possible transcoding in the TrGW then a TrGW supporting media shall be seized. The IBCF sends a H.248 ADD request command to create the outgoing termination and to request IP resources to execute TrGW function. As no media transcoding is yet known to be needed this may be indicated by omitting media related sub-fields in the media descriptor (i.e. signalling "-"). Alternatively the preferred codec (e.g. Codec 1) may be signalled in order to reserve this resource in the event that transcoding was required. +4. The TrGW creates the outgoing termination. + +5. The TrGW replies to IBCF with a H.248 ADD reply command and provides the local address and port of the outgoing termination. +6. The IBCF replaces the IP address inside the SDP offer using the information coming from TrGW. +7. The IBCF forwards the new SDP offer to the succeeding node. +8. The SDP answer is received by IBCF. In this example the codec 3 added by the IBCF to the SDP offer has been selected. Transcoding is therefore required. +9. The IBCF sends a H.248 MOD request command to configure the outgoing termination with address and port information received in the SDP answer and the selected media attributes (codec 3). +10. The TrGW configures the outgoing termination. +11. The TrGW replies to IBCF with a H.248 MOD reply command. +12. The IBCF sends a H.248 ADD request command to create the incoming termination to configure this termination with remote address and port information and to request resources to execute TrGW function. As media transcoding is required it indicates this explicitly with a codec selected by the IBCF for the incoming termination from the offered codec(s) received in step1. +13. The TrGW creates the incoming termination. +14. The TrGW replies to the IBCF with a H.248 ADD reply command and provides the local address and port of the incoming termination. +15. The IBCF replaces the IP address inside the SDP using the information coming from TrGW and replaces the codec with the codec it selected for the incoming termination. +16. The SDP answer is sent to the network at the incoming side. + +**Figure 10.2.5.2: IBCF and TrGW interaction when IBCF offers additional codecs and transcoding is required, and the TrGW is seized in advance.** + +![Sequence diagram showing the interaction between TrGW and IBCF for resource reservation and configuration. The diagram consists of 16 numbered steps. Steps 1, 7, 8, and 16 are dashed arrows representing SIP/SDP messages. Steps 2, 4, 6, 10, and 13 are rounded rectangles representing internal actions. Steps 3, 5, 9, 11, 12, and 14 are solid arrows representing H.248 messages. Brackets on the right side group steps: 'Reserve TrGW Connection Point' (steps 3-5), 'Configure TrGW Connection Point' (steps 9-11), and 'Reserve And Configure TrGW Connection Point' (steps 12-14).](dd5771673aececa53d42ece89218299d_img.jpg) + +``` + +sequenceDiagram + participant IBCF + participant TrGW + Note right of IBCF: 1. SDP offer (IP2o, P2o, codec1, codec2) + Note right of IBCF: 2. Use case X detected that needs TrGW functionality + IBCF->>TrGW: 3. H.248 ADD req (C= ?, T= ?, LAddr=?, LPort=?, Local Resources="-" or codec1 or codec2) + Note right of TrGW: 4. Create outgoing termination T1 + TrGW->>IBCF: 5. H.248 ADD resp. (C=C1, T=T1, LAddr=IP1o, LPort=P1o) + Note right of IBCF: 6. Modify SDP offer + IBCF-->>TrGW: 7. SDP offer (IP1o, P1o, codec1, codec2) + TrGW-->>IBCF: 8. SDP answer (IP1a, P1a, codec1) + IBCF->>TrGW: 9. H.248 MOD req (C= C1, T= T1, RAddr=IP1a, RPort=P1a, Local Resources="-" or codec1, Remote Resources="-" or codec1) + Note right of TrGW: 10. Configure Outgoing Termination T1 + TrGW->>IBCF: 11. H.248 MOD Resp (C= C1, T= T1) + IBCF->>TrGW: 12. H.248 ADD req (C= C1, T= ?, LAddr=?, LPort=?, RAddr=IP2o, RPort=P2o, Local Resources="-" or codec1, Remote Resources="-" or codec1) + Note right of TrGW: 13. Create incoming Termination T2 + TrGW->>IBCF: 14. H.248 ADD Resp (C= C1, T= T2, LAddr=IP2a, LPort=P2a, RAddr=IP2o, RPort=P2o) + Note right of IBCF: 15. Modify SDP answer + IBCF-->>TrGW: 16. SDP answer (IP2a, P2a, codec1) + +``` + +Sequence diagram showing the interaction between TrGW and IBCF for resource reservation and configuration. The diagram consists of 16 numbered steps. Steps 1, 7, 8, and 16 are dashed arrows representing SIP/SDP messages. Steps 2, 4, 6, 10, and 13 are rounded rectangles representing internal actions. Steps 3, 5, 9, 11, 12, and 14 are solid arrows representing H.248 messages. Brackets on the right side group steps: 'Reserve TrGW Connection Point' (steps 3-5), 'Configure TrGW Connection Point' (steps 9-11), and 'Reserve And Configure TrGW Connection Point' (steps 12-14). + +1. The IBCF receives an SDP offer in SIP signalling. +2. The IBCF requires a TrGW for another use case but does not offer transcoding. +3. The IBCF sends a H.248 ADD request command to create the outgoing termination and to request IP resources to execute TrGW function. As no media transcoding is required this may be indicated by signalling "-". Alternatively any codec (e.g. codec 1) can be signalled. If the IBCF selects a TrGW that does not support transcoding, the IBCF may signal media related sub-fields in the media descriptor to the TrGW if the TrGW supports media encoding. The TrGW shall accept the ADD request even though it cannot reserve any transcoding resources for the indicated media. +4. The TrGW creates the outgoing termination. + +5. The TrGW replies to IBCF with a H.248 ADD reply command and provides the local address and port of the outgoing termination. +6. The IBCF replaces the IP address inside the SDP using the information coming from TrGW. +7. The IBCF forwards the new offer to the succeeding node. +8. The SDP answer is received by IBCF. In this example the codec 1 received in the original SDP offer in step 1 has been selected. +9. The IBCF sends a H.248 MOD request command to configure the outgoing termination with address and port information. As no media transcoding is needed this may be indicated by signalling "-" .Alternatively the selected codec (codec 1) can be signalled. +10. The TrGW configures the outgoing termination. +11. The TrGW replies to IBCF with a H.248 MOD reply command. +12. The IBCF sends a H.248 ADD command to create the incoming termination to configure this termination with remote address and port information and to request resources to execute TrGW function. As no media transcoding is needed this may be indicated by signalling "-" .Alternatively media related sub-fields in the media descriptor for the codec indicated to the incoming termination may be signalled (e.g. the selected codec received in step 8 (codec 1)). +13. The TrGW creates the incoming termination. +14. The TrGW replies to the IBCF with a H.248 ADD reply command and provides the local address and port of the incoming termination. +15. The IBCF replaces the IP address inside the SDP answer using the information coming from TrGW. +16. The SDP answer is sent to the network at the incoming side. + +**Figure 10.2.5.3: IBCF and TrGW interaction when IBCF does not offer transcoding** + +### 10.2.6 Media Inactivity Detection + +The procedures in subclause A.7.1.2.2.6 of 3GPP TS 29.235 [29] are applicable. + +### 10.2.7 QoS Packet Marking (differentiated services) + +The procedures in subclause A.7.1.2.2.4 of 3GPP TS 29.235 [29] are applicable. + +Those procedures relate to Diffserv code point marking as described in IETF RFC 2474 [31] + +### 10.2.8 Hanging Termination Detection + +The procedures in subclause A.7.1.2.2.2 of 3GPP TS 29.235 [29] are applicable. + +### 10.2.9 Bandwidth Policing + +The procedures in subclause A.7.1.2.2.8 of 3GPP TS 29.235 [29] are applicable. + +### 10.2.10 IMS end-to-end media plane security + +An IBCF and a TrGW may support the end-to-end IMS media plane security as specified in 3GPP TS 33.328 [32]. If supported, the IBCF shall use the following procedures. + +If the IBCF receives SDP containing media lines with "RTP/SAVP" (see IETF RFC 3711 [34]) or "RTP/SAVPF" (see IETF RFC 5124 [35]) as transport protocol, the IBCF shall: + +- forward the SDP with unmodified transport protocol for those media lines; +- apply the procedures to not offer or apply transcoding defined in subclause 10.2.5; and +- provide "RTP/SAVP" or "RTP/SAVPF", as received in the SDP, to the TrGW as transport protocol for all related terminations, and not provide media related information to these terminations, to configure the TrGW to pass media and possibly associated RTCP control flows and not to reserve any resources. + +**NOTE:** RTP/SAVP or SAVPF are provided to the TrGW even though it does not reserve any resources for this as such, but this is needed in order to allocate dual ports to support RTCP flows. These are also controlled as described in subclause 10.2.3. For "RTP/SAVP" or "RTP/SAVPF", RTCP will be encrypted and can not be interpreted by the TrGW. Media information is also meaningless as encryption will modify the properties of the media streams. + +If the IBCF receives SDP containing SDES SDP attribute(s) according to IETF RFC 4568 [33], IBCF shall forward the SDP with unmodified SDES SDP attribute(s), but shall not provide the SDES SDP attribute(s) to the TrGW. + +### 10.2.11 Through-Connection + +The procedures in subclause A.7.1.2.2.9 of 3GPP TS 29.235 [29] are applicable. + +### 10.2.12 Emergency Call + +The procedures in subclause A.7.1.2.2.10 of 3GPP TS 29.235 [29] are applicable. + +### 10.2.13 Explicit Congestion Notification support + +#### 10.2.13.1 General + +An IBCF and TrGW may support Multimedia Telephony using Explicit Congestion Notification (ECN) according to IETF RFC 3168 [37], and may act as an ECN endpoint to enable ECN with a local ECN-capable terminal within a local network that properly handles ECN-marked packets. + +#### 10.2.13.2 Incoming SDP offer with ECN + +If the IBCF receives an SDP offer containing the "a=ecn-capable-rtp" attribute (see IETF RFC 6679 [38]), then if all of the following statements are true: + +- a) the IBCF supports ECN according to 3GPP TS 26.114 [36]; +- b) the TrGW supports ECN according to 3GPP TS 26.114 [36]; +- c) the IBCF knows (via configuration) that the succeeding network supports ECN according to 3GPP TS 26.114 [36]; and +- d) the IBCF does not insert any transcoding; + +then the IBCF shall: + +- if the "ecn-capable-rtp" attribute includes both the "ice" initiation method and other initiation methods, remove the "ice" initiation method from the "ecn-capable-rtp" attribute and forward the attribute with this modification in the outgoing SDP offer; +- if the "ecn-capable-rtp" attribute only includes the "ice" initiation method, remove the "ecn-capable-rtp" attribute, any "rtcp-fb" attribute with the "nack" feedback parameter and the "ecn" feedback parameter value, and any "ecn-sum" parameter within a "rtcp-xr" attribute from the outgoing SDP offer; +- if the "ecn-capable-rtp" attribute did not include the "ice" initialisation method, forward the unmodified "ecn-capable-rtp" attribute within the outgoing SDP offer; and +- if the IBCF includes the "ecn-capable-rtp" attribute within the outgoing SDP offer, forward the SDP offer containing ECN parameters to the succeeding network. + +Otherwise the IBCF shall remove the "ecn-capable-rtp" attribute, any "rtcp-fb" attribute with the "nack" feedback parameter and the "ecn" feedback parameter value, and any "ecn-sum" parameter within an "rtcp-xr" attribute from the outgoing SDP offer. + +If the IBCF forwarded the SDP offer containing the "a=ecn-capable-rtp" attribute and receives an SDP answer also containing the "a=ecn-capable-rtp" attribute (the reception of the attribute indicates a successful ECN negotiation) then the IBCF shall forward the SDP answer to its preceding node and shall indicate to the TrGW that it shall transfer ECN bits in IP header transparently. + +If the IBCF forwarded the SDP offer containing the "a=ecn-capable-rtp" attribute and receives an SDP answer without the "a=ecn-capable-rtp" attribute and the TrGW supports at least some of the initialisation methods within the "a=ecn-capable-rtp" attribute in the previously received SDP offer, + +NOTE 1: Only the "leap" initialisation method is supported over the Ix interface in this release. + +the IBCF shall: + +- act as an end point for ECN; +- select an initialisation method supported by the TrGW; +- determine if application specific feedback or ECN feedback messages shall be used, taking into account whether the TrGW supports ECN feedback messages, and the negotiation procedures in 3GPP TS 26.114 [36]; +- determine if ECN XR summary reports can be used, taking into account whether they are supported at the TrGW, and the negotiation procedures in 3GPP TS 26.114 [36]; +- send the SDP answer according to 3GPP TS 26.114 [36] and the capabilities of the TrGW, containing the ECN attribute "a=ecn-capable-rtp"; and +- indicate to the TrGW that it shall apply the ECN procedures (according to 3GPP TS 26.114 [36]) and act as an ECT endpoint. + +If the IBCF receives an SDP offer containing the "a=ecn-capable-rtp" attribute and bullets a) and b) above are satisfied but if bullet c) or d) or both are not met then the IBCF shall remove ECN related attributes before forwarding the SDP offer. If the TrGW supports at least some of the initialisation methods offered within the "a=ecn-capable-rtp" attribute, + +NOTE 2: Only the "leap" initialisation method is supported over the Ix interface in this release. + +the IBCF shall: + +- act as an end point for ECN; +- select an initialisation method supported by the TrGW; +- determine if application specific feedback or ECN feedback messages shall be used, taking into account whether the TrGW supports ECN feedback messages, and the negotiation procedures in 3GPP TS 26.114 [36]; +- determine if ECN XR summary reports can be used, taking into account whether they are supported at the TrGW and the negotiation procedures in 3GPP TS 26.114 [36]; +- send an SDP answer according to 3GPP TS 26.114 [36] and the capabilities of the TrGW, containing the "a=ecn-capable-rtp" attribute; and +- indicate to the TrGW that it shall apply the ECN procedures (according to 3GPP TS 26.114 [36]) and act as an ECT endpoint. + +The TrGW should not send RTCP XR ECN summary reports. + +#### 10.2.13.3 Incoming SDP offer without ECN + +If the IBCF receives an SDP offer without the "a=ecn-capable-rtp" attribute then if all of the following statements are true: + +- a) the IBCF supports ECN according to 3GPP TS 26.114 [36]; +- b) the TrGW supports ECN according to 3GPP TS 26.114 [36]; and +- c) the IBCF knows (via configuration) that the succeeding network supports ECN according to 3GPP TS 26.114 [36]; + +the IBCF may include the "a=ecn-capable-rtp" attribute in the SDP offer it forwards towards the succeeding node, indicating the related capabilities of the TrGW. + +NOTE: ECN XR summary reports and RTCP AVPF ECN feedback message are not supported in this release towards IMS terminations. + +If the IBCF inserted ECN attributes in the SDP offer and receives an SDP answer containing the "a=ecn-capable-rtp" attribute the IBCF shall act as an endpoint and shall return the SDP answer to the preceding node removing the "a=ecn-capable-rtp" attribute, any "rtcp-fb" attribute with the "nack" feedback parameter and the "ecn" feedback parameter value, and any "ecn-sum" parameter within a "rtcp-xr" attribute, and shall indicate to the TrGW that it shall apply the ECN procedures according to 3GPP TS 26.114 [36] and act as an ECT endpoint. The TrGW should not send RTCP XR ECN summary reports. + +If the IBCF inserted the "a=ecn-capable-rtp" attribute in the SDP offer and receives an SDP answer without the "a=ecn-capable-rtp" attribute the IBCF shall continue the call without any ECN active. + +#### 10.2.13.3a Detection of ECN failures by TrGW + +If the TrGW acts as ECN endpoint and detects an ECN-related error case, for example non-ECT in the received packets when ECT(0) was expected or detecting a very high packet loss rate when ECN is used, the TrGW shall notify the IBCF. The IBCF should then initiate a session re-negotiation to disable ECN. + +#### 10.2.13.4 Interworking with non-3GPP ECN IP terminal + +##### 10.2.13.4.1 Support for additional ECN parameters + +An IBCF and TrGW may support additional ECN parameter settings than defined in 10.2.13.2. The following sub-clauses describe the optional behaviour if the IBCF and TrGW support these additional values. + +##### 10.2.13.4.2 Incoming SDP offer from external IP network with ECN + +If the IBCF receives an incoming SDP offer from the external IP network containing values in the incoming SDP offer not supported by MTSI then it shall configure the SDP offer as defined in subclause 10.2.13.2 when forwarding the SDP offer to the IMS. + +When receiving the SDP answer from the IMS the IBCF may configure the SDP answer to the external IP network with alternative settings depending on what is received from the IMS and what was offered by the external IP network. The permitted alternatives are listed in table 10.2.13.4.1; the supported alternatives are implementation options which need to be derived through configuration or package auditing. + +##### 10.2.13.4.3 Incoming SDP offer from the IMS with ECN + +If the IBCF receives an incoming SDP offer from the IMS and it supports additional ECN parameter settings than those defined in subclause 10.2.13.2 the IBCF may add these to the SDP offer forwarded to the external IP network. + +When receiving an SDP answer from the external IP network the IBCF shall respond to the IMS in accordance with 10.2.13.2. If the IBCF modifies any ECN-related parameters in the forwarded SDP answer compared to the received SDP answer, the IBCF shall configure its TrGW as an ECN endpoint. The permitted alternatives are listed in table 10.2.13.4.1; the supported alternatives are implementation options which need to be derived through configuration or package auditing. + +**Table 10.2.13.4.1: Possible configurations when interworking with non-3GPP ECN IP terminal** + +| ECN SDP Attribute and required TrGW Action | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| IMS side | External IP Network | TrGW Action | +| Initiation | | | +| "leap" | "rtp"
NOTE 3 | Act as an Endpoint and trigger explicit initiation using RTP and RTCP as described in IETF RFC 6679 [38] toward the external IP network. When initial ECT marked packets are received from the external IP network these are forwarded to the IMS (all packets shall be marked) and early feedback and XR Summary reports are sent back to the external IP network. If ECT marked packets are received from the IMS before any initiation is completed with the external IP network then ECT marking should be removed and only a fraction of the packets should be marked until feedback is received from the external IP network. | +| | "ice" | This initiation method is not supported in the present release. | +| Mode | | | +| "setread" | "readonly" | Act as ECN transparent unless required to act as an Endpoint for other reasons but mark packets toward the IMS with ECT(0). If ECN-CE is received from the IMS then this shall be handled by the IMS termination as currently specified for the non-interworking case and not forwarded to the external IP network. | +| | "setonly" | Act as ECN transparent (unless required to act as ECN Endpoint for other reasons) - ECN-CE marked packets will not be received from external IP network, ECN-CE marked packets from the IMS will be passed to the external IP network. | +| ECT | | | +| "ect(0)" | "ect(1)" | Act as ECN transparent unless required to act as an Endpoint for other reasons but mark packets toward the IMS with ECT(0) and mark packets toward external network with ECT(1). | +| | "random" | Act as ECN transparent unless required to act as an Endpoint for other reasons but mark packets toward IMS with ECT(0). Packets received from the IMS are left as ECT(0). | +| RTCP feedback | | | +| no "rtcp-fb:* nack ecn"
(received driven congestion control) | "rtcp-fb:* nack ecn" (sender driven congestion control) | For AMR, the handling of an AVPF feedback message received from the external IP the handling is not defined.

For video related AVFP feedback messages received from the external IP network the TrGW shall generate the appropriate TMBR request towards the IMS. If a TMBR request is received from the IMS the TrGW shall generate an appropriate AVPF feedback message to the external IP network. | +| "rtcp-fb:* nack ecn"
(sender driven congestion control) | "rtcp-fb:* nack ecn" (sender driven congestion control) | An AVPF feedback message received from the external IP network shall be forwarded via the IMS termination. | +| RTCP XR ECN summary report | | | +| - | "rtcp-xr:ecn-sum" | RTCP XR is not bi-directions and each end-point indicates whatever XR feedback it supports. Hence, if the SDP offer does not contain rtcp-xr with "ecn-sum" then it can still be added in the SDP answer.

The TrGW shall include XR ECN Summary reports towards the external IP network and receive reports from the external IP network. (NOTE 4) | +| NOTE1: The settings for IMS side may be supported on the External IP Network side in which case no interworking is specified. | | | +| NOTE 2: Each parameter is described separately as each parameter may or may not need to be interworked. Unless stated otherwise the assumption is that each parameter can be treated independently. | | | +| NOTE 3: RTCP feedback messages need to be supported and negotiated for the "rtp" initialisation method | | | +| NOTE 4: The contents of the XR reports will be limited to data received from the external IP network. | | | + +#### 10.2.13.5 Message sequence chart + +##### 10.2.13.5.1 ECN support requested (ECN endpoint) + +Figure 10.2.13.5.1.1 shows the message sequence chart example for requesting ECN. + +![Sequence diagram for Figure 10.2.13.5.1.1: Procedure to Request ECN. The diagram shows two lifelines: IBCF and TrGW. The IBCF sends a Context(Cx) message to the TrGW containing an H.248:ADD.req with Termination X, Transport = RTP/AVPF, ECN_enable=True, and {Notify_ECN_Error}. The TrGW responds with a Context(Cx) message containing an H.248:ADD.resp[Termination X]. The TrGW also performs internal actions: Reserve IMS Connection Point and Configure Remote Resources.](ac31fdfebb9751f7f10416dfe33bc872_img.jpg) + +``` + +sequenceDiagram + participant IBCF + participant TrGW + Note right of TrGW: Reserve IMS Connection Point and Configure Remote Resources + IBCF->>TrGW: Context(Cx) [H.248:ADD.req[ Termination X, Transport = RTP/AVPF, ECN_enable=True, {Notify_ECN_Error}]] + TrGW-->>IBCF: Context(Cx) [H.248:ADD.resp[Termination X]] + +``` + +Sequence diagram for Figure 10.2.13.5.1.1: Procedure to Request ECN. The diagram shows two lifelines: IBCF and TrGW. The IBCF sends a Context(Cx) message to the TrGW containing an H.248:ADD.req with Termination X, Transport = RTP/AVPF, ECN\_enable=True, and {Notify\_ECN\_Error}. The TrGW responds with a Context(Cx) message containing an H.248:ADD.resp[Termination X]. The TrGW also performs internal actions: Reserve IMS Connection Point and Configure Remote Resources. + +**Figure 10.2.13.5.1.1: Procedure to Request ECN** + +Upon receipt of a request to apply ECN the TrGW shall set the ECN field of the IP header in accordance with 3GPP TS 26.114 [36] when sending any data packets. + +Upon receipt of any IP headers indicating ECN Congestion Experienced (ECN-CE) the TrGW shall trigger rate adaptation in accordance with 3GPP TS 26.114 [36]. + +NOTE: ECN requires the IBCF to configure the TrGW with all media attributes to allow rate adaptation even if no transcoding is required/supported in the TrGW. + +##### 10.2.13.5.2 ECN Active Indicated (ECN transparent) + +Figure 10.2.13.5.2.1 shows the message sequence chart example for indicating ECN transparent. + +![Sequence diagram for Figure 10.2.13.5.2.1: Procedure to indicate ECN transparent negotiated. The diagram shows two lifelines: IBCF and TrGW. The IBCF sends a Context(Cx) message to the TrGW containing an H.248:ADD.req with Termination X, Transport = RTP/AVPF, ECN_enable = True, and Initialisation_Method = Inactive. The TrGW responds with a Context(Cx) message containing an H.248:ADD.resp[Termination X]. The TrGW also performs internal actions: Reserve IMS Connection Point and Configure Remote Resources.](dec689324b075952626a86da862b9549_img.jpg) + +``` + +sequenceDiagram + participant IBCF + participant TrGW + Note right of TrGW: Reserve IMS Connection Point and Configure Remote Resources + IBCF->>TrGW: Context(Cx) [H.248:ADD.req[ Termination X, Transport = RTP/AVPF, ECN_enable = True, Initialisation_Method = Inactive]] + TrGW-->>IBCF: Context(Cx) [H.248:ADD.resp[Termination X]] + +``` + +Sequence diagram for Figure 10.2.13.5.2.1: Procedure to indicate ECN transparent negotiated. The diagram shows two lifelines: IBCF and TrGW. The IBCF sends a Context(Cx) message to the TrGW containing an H.248:ADD.req with Termination X, Transport = RTP/AVPF, ECN\_enable = True, and Initialisation\_Method = Inactive. The TrGW responds with a Context(Cx) message containing an H.248:ADD.resp[Termination X]. The TrGW also performs internal actions: Reserve IMS Connection Point and Configure Remote Resources. + +**Figure 10.2.13.5.2.1: Procedure to indicate ECN transparent negotiated** + +Upon receipt of the indication that ECN transparent has been negotiated the TrGW shall forward IP packets with ECN bits set unmodified. + +##### 10.2.13.5.3 ECN Failure Indication (ECN endpoint) + +Figure 10.2.13.5.3.1 shows the message sequence chart example for an ECN Failure Event. + +![Sequence diagram showing the procedure to report ECN failure between IBCF and TrGW. The IBCF sends an H.248:NOTIFY.req(ECN Failure) message to the TrGW. The TrGW responds with an H.248:NOTIFY.resp(ECN Failure) message. The IBCF then reports the ECN failure to the Context(Cx).](b2f5606b9c7184c1c6070a290080a3e3_img.jpg) + +``` + +sequenceDiagram + participant IBCF + participant TrGW + Note left of IBCF: Context(Cx) + IBCF->>TrGW: H.248:NOTIFY.req(ECN Failure) +[Termination =x, cause=ecn_cause] + TrGW-->>IBCF: H.248:NOTIFY.resp(ECN Failure) +[Termination x] + Note right of TrGW: Report ECN Failure + Note left of IBCF: Context(Cx) + IBCF->>TrGW: + +``` + +Sequence diagram showing the procedure to report ECN failure between IBCF and TrGW. The IBCF sends an H.248:NOTIFY.req(ECN Failure) message to the TrGW. The TrGW responds with an H.248:NOTIFY.resp(ECN Failure) message. The IBCF then reports the ECN failure to the Context(Cx). + +**Figure 10.2.13.5.3.1: Procedure to Report ECN Failure** + +When the IBCF receives a Notification indicating that a failure has occurred, the MGCF may trigger a new SDP offer to disable ECN. + +### 10.2.14 Optimal Media Routeing + +An IBCF may support optimal media routeing (OMR) procedures, as defined in 3GPP TS 29.079 [39]. + +3GPP TS 29.079 [39] specifies that "secondary media resources" may be allocated in addition to "primary media resources". If controlled by an IBCF, such primary or secondary media resources are TrGWs controlled over the Ix interface with procedures specified in the present specification. + +If the IBCF applies OMR procedures, the following modifications to the procedures within the present specification are applicable: + +- Under conditions specified in 3GPP TS 29.079 [39], the IBCF uses information from OMR related SDP attributes as remote connection and port information that is provided towards the TrGW within the call establishment procedures in subclause 10.1.3.1.1. +- Under conditions specified in 3GPP TS 29.079 [39], the IBCF encapsulates local address and port information, as received from the TrGW within the call establishment procedures in subclause 10.1.3.1.1, in OMR related SDP attributes. +- Under conditions specified in 3GPP TS 29.079 [39], the IBCF uses information from OMR related SDP attributes as codec information that is provided towards the TrGW within the media control procedures in clause 10.2.5. +- 3GPP TS 29.079 [39] specifies OMR-specific events that trigger the call release procedures in subclause 10.1.3.1.2. + +### 10.2.15 IP Realm Availability + +The procedures in subclause A.7.1.2.2.5 of 3GPP TS 29.235 [29] are applicable. + +### 10.2.16 Access Transfer procedures with media anchored in ATGW + +The procedures in the present clause are optional to be supported for both IBCF and TrGW when supporting the ATCF and ATGW functionality (see subclause 6.1.4). + +The procedures in subclause 6.2.14 of 3GPP TS 23.334 [43] are applicable, except that where the Iq interface is mentioned in those procedures, the Ix interface is applicable. + +### 10.2.17 Multimedia Priority Service (MPS) Support + +#### 10.2.17.1 General + +The Multimedia Priority Service (MPS) is specified in 3GPP TS 22.153 [44]. The IBCF/TrGW may support the priority treatment of a call/session identified as an MPS call/session. If MPS is supported then upon receipt of the MPS priority information in the call control signalling: + +- The IBCF shall recognise the call/session as having priority. +- The IBCF shall send the Priority information for a context to the TrGW to enable the priority treatment described below related to the TrGW. +- The IBCF shall apply priority handling to H.248 transactions related to priority calls/sessions when network resources are congested, e.g., preferential treatment in any queues or buffers. +- The IBCF may send the updated priority information and, if DiffServ is used, provision a suitable DSCP marking for the updated MPS priority level to the TrGW if it needs to change the priority information previously communicated to the TrGW for an MPS call/session. +- If the H.248 control association utilises a transport with the possibility for prioritisation, the IBCF may apply priority using the appropriate prioritisation procedures. +- If the MPS Priority service requires a specific MPS DSCP setting, the IBCF shall configure the TrGW to apply a specific MPS DSCP marking to the user data transport packets to indicate that the packets are of a higher priority than those for normal calls. +- If the TrGW receives an indication to apply a specific MPS DSCP marking to the user data transport packets, it shall apply this DSCP marking to the IP headers. + +NOTE 1: Support of Diffserv procedures by the TrGW assumes an operator uses Diffserv for prioritising user plane traffic related to an MPS call/session. + +- When the IBCF marks a Context with Priority information, the TrGW may use the Priority information for selecting resources for the media and signaling transport with priority. The following actions may be taken by the TrGW if it has reached a congested state: + - i) seize priority reserved resources; or + - ii) if resources are completely congested, indicate that in a Command Response error code. + +NOTE 2: The Priority information can be used to derive Layer 2 QoS marking and trigger priority identification and priority treatment for other QoS technologies than Diffserv. + +This clause describes the Ix signalling procedures and their interactions with SIP signalling in the control plane and with user plane procedures to support the requirements for MPS. These Ix signalling procedures may or may not apply depending on the network configuration (e.g. whether the TrGW is shared by multiple IBCFs or whether the IBCF controls multiple TrGWs for a given route – Media Gateway Group). + +The IBCF can receive a SIP INVITE with MPS priority information (see 3GPP TS 23.228 [8], subclause 5.21). + +#### 10.2.17.2 TrGW Resource Congestion in ADD response, request is queued + +If the IBCF requests a resource via the Reserve and Configure TrGW Connection Point procedure or Reserve TrGW Connection Point procedure and receives an error indicating that the requested resource could not be seized (e.g. H.248 error code #510 "insufficient resources") and the IBCF does not have an alternative TrGW through which it can route the call/session, the IBCF queues the priority call/session and gives it priority over any further Reserve and Configure TrGW Connection Point or Reserve TrGW Connection Point procedures for lower priority calls/sessions towards this TrGW until the requested resource for this queued call/session is successfully seized. The example sequence is shown in Figure 10.2.17.2.1. + +![Sequence diagram showing the request to reserve MPS priority call resources when TrGW is congested. The diagram involves two main entities: IBCF and TrGW. The sequence starts with an INVITE message from an external source to the IBCF. The IBCF then sends an H.248 ADD Req to the TrGW. The TrGW responds with an H.248 ADD Reject due to congestion. The IBCF queues the request and later retransmits the H.248 ADD Req. The TrGW then successfully reserves the resources and responds with an H.248 ADD Resp.](9f6dec4d4e9fde40bce018861ef1278e_img.jpg) + +``` + +sequenceDiagram + participant External + participant IBCF + participant TrGW + Note right of TrGW: TrGW is congested + External->>IBCF: 1. INVITE [MPS priority indication] + IBCF->>TrGW: 2. H.248 ADD Req [C=?, T=?, Laddr=?, Lport=?, Local Resources, Priority] + TrGW-->>IBCF: 3. H.248 ADD Reject [Error = #510] + Note left of IBCF: Reserve TrGW Connection Point + IBCF-->>IBCF: 4. IBCF queues MPS request + Note left of IBCF: Reserve TrGW Connection Point + IBCF->>TrGW: 5. H.248 ADD Req [C=?, T=?, Laddr=?, Lport=?, Local Resources, Priority] + Note right of TrGW: TrGW successfully seizes required resources + TrGW-->>IBCF: 6. H.248 ADD Resp [C=C1, T=T2, Laddr=IP2o, LPort=P2o] + +``` + +Sequence diagram showing the request to reserve MPS priority call resources when TrGW is congested. The diagram involves two main entities: IBCF and TrGW. The sequence starts with an INVITE message from an external source to the IBCF. The IBCF then sends an H.248 ADD Req to the TrGW. The TrGW responds with an H.248 ADD Reject due to congestion. The IBCF queues the request and later retransmits the H.248 ADD Req. The TrGW then successfully reserves the resources and responds with an H.248 ADD Resp. + +**Figure 10.2.17.2.1: Request to Reserve MPS priority call resources when TrGW is congested** + +#### 10.2.17.3 TrGW Resource Congestion in ADD response, IBCF seizes new TrGW + +If the IBCF requests a resource via the Reserve and Configure TrGW Connection Point procedure or Reserve TrGW Connection Point procedure and receives an error indicating that the requested resources could not be seized due to congestion (e.g. H.248 error code #510 "insufficient resources") and Media Gateway Groups are implemented the IBCF seizes a new TrGW from the same Media Gateway Group before resorting to any queuing of the priority call/session (as described in subclause 10.2.17.2) to enable the MPS call/session to proceed as early as possible. + +#### 10.2.17.4 TrGW Priority Resource Allocation + +If the TrGW supports the Priority information (e.g. determined through provisioning or package profile), the IBCF requests a resource via the Reserve and Configure TrGW Connection Point procedure or Reserve TrGW Connection Point procedure and includes the Priority information. The TrGW may then provide priority allocation of resources once a congestion threshold is reached. The example sequence is shown in Figure 10.2.17.4.1. If the TrGW is completely congested it shall indicate this to the IBCF as described in subclause 10.2.17.2. + +![Sequence diagram showing the request to reserve MPS priority call resources when TrGW is congested, but priority resources are allocated. The diagram involves two main entities: IBCF and TrGW. The sequence starts with an INVITE message from an external source to the IBCF. The IBCF then sends an H.248 ADD Req to the TrGW. The TrGW responds with an H.248 ADD Resp, indicating that priority resources have been allocated despite congestion.](24b1ac9eb58a2f22801620b9e2ea8bd3_img.jpg) + +``` + +sequenceDiagram + participant External + participant IBCF + participant TrGW + Note right of TrGW: TrGW is in a congested state but allocates priority resources to this call. + External->>IBCF: 1. INVITE [MPS priority indication] + IBCF->>TrGW: 2. H.248 ADD Req [C=?, T=?, Laddr=?, Lport=?, Local Resources, Priority] + TrGW-->>IBCF: 3. H.248 ADD Resp [C=C1, T=T2, Laddr=IP2o, LPort=P2o] + Note left of IBCF: Reserve TrGW Connection Point + +``` + +Sequence diagram showing the request to reserve MPS priority call resources when TrGW is congested, but priority resources are allocated. The diagram involves two main entities: IBCF and TrGW. The sequence starts with an INVITE message from an external source to the IBCF. The IBCF then sends an H.248 ADD Req to the TrGW. The TrGW responds with an H.248 ADD Resp, indicating that priority resources have been allocated despite congestion. + +**Figure 10.2.17.4.1: Request to reserve MPS priority call resources when TrGW is congested, priority resources are allocated** + +The TrGW may also provide priority allocation for resources requested via a subsequent Configure TrGW Connection Point procedure not including Priority information if the related context has been marked with priority information during the Reserve TrGW Connection Point or Reserve and Configure TrGW Connection Point procedure. + +#### 10.2.17.5 TrGW Priority User Data marking + +The IBCF may request the streams associated to an MPS call/session to be marked with certain priority code point as described in subclause 10.2.7. The TrGW shall then mark each IP packet header accordingly. The example sequence is shown in Figure 10.2.17.5.1. + +![Sequence diagram showing the request to reserve IMS resources and apply DSCP marking for MPS between IBCF and TrGW.](0b3d9fe35da3ee0c88f1420bb9ed7a03_img.jpg) + +``` + +sequenceDiagram + participant IBCF + participant TrGW + Note left of IBCF: Reserve TrGW Connection Point + IBCF->>TrGW: 1. INVITE [MPS priority indication] + IBCF->>TrGW: 2. H.248 ADD Req [C=?, T= ?, Laddr = ?, Lport = ?, Local Resources, Diffserv Mark = DSCP1, Priority] + TrGW-->>IBCF: 3. H.248 ADD Resp [C=C1, T=T2, Laddr=IP2o, LPort=P2o] + Note right of TrGW: TrGW is requested to apply DSCP value in IP header of user data packets. + +``` + +The diagram illustrates a sequence of three messages between the IBCF and the TrGW. + 1. The IBCF sends an INVITE message with an MPS priority indication to the TrGW. + 2. The IBCF sends an H.248 ADD Req message to the TrGW, specifying parameters like C, T, Laddr, Lport, Local Resources, and Diffserv Mark (DSCP1, Priority). + 3. The TrGW responds with an H.248 ADD Resp message containing parameters like C=C1, T=T2, Laddr=IP2o, and LPort=P2o. + A bracket on the left side of the IBCF lifeline, spanning the first two messages, is labeled 'Reserve TrGW Connection Point'. + A note on the right side of the TrGW lifeline states: 'TrGW is requested to apply DSCP value in IP header of user data packets.'. + +Sequence diagram showing the request to reserve IMS resources and apply DSCP marking for MPS between IBCF and TrGW. + +**Figure 10.2.17.5.1: Request to reserve IMS resources and apply DSCP marking for MPS** + +#### 10.2.17.6 TrGW Priority Modification + +If the IBCF seized an IP termination for a priority call/session with a default priority and subsequently needs to modify the priority information previously communicated to the TrGW (e.g. subject to subsequent authorisation by an authorisation point, see 3GPP TS 24.229 [1] subclause 4.11), the IBCF may modify the existing IP termination for the MPS call/session with the actual priority and, if DiffServ is used, provision a suitable DSCP marking for the updated MPS priority level to the TrGW via the Configure TrGW Connection Point Procedure. + +NOTE: The specific Ix related call sequence which details the handling to support the requirements defined in 3GPP TS 24.229 [1] subclause 4.11 and 3GPP TS 23.228 [8], subclause 5.21 is not specified and therefore implementations might exist which fulfil these requirements but do not require modification of the priority information across the Ix interface. + +## 10.3 Void + +## 10.4 Procedures + +### 10.4.1 Call related Procedures + +#### 10.4.1.1 Reserve TrGW Connection Point + +This procedure is used to reserve an termination at the TrGW. + +##### **Table 10.4.1.1.1: Reserve TrGW Connection Point** + +| Procedure | Initiated | Information element name | Information element required | Information element description | +|-------------------------------|-----------|----------------------------------|------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Reserve TrGW Connection Point | IBCF | Context/Context Request | M | This information element indicates the existing context or requests a new context for the bearer termination. | +| | | Emergency Call Indicator | O | This information element identifies the call as emergency call that requires a preferential handling. | +| | | Priority information | O | This information element requests the TrGW to apply priority treatment for the terminations and bearer connections in the specified context. | +| | | Termination Request | M | This information element requests a new termination for the bearer to be established. | +| | | IP Interface | O | This information element specifies the type of external interface to be used for the IP termination (e.g. MboIP). | +| | | Local IP Resources | O | This information element indicates the resource(s) (e.g. codec, auxiliary payload types) for which the TrGW shall be prepared to receive user data. May be excluded (i.e. "-" is used in SDP m-line) if no transcoding or other media related functions are required. | +| | | ReserveValue | C | This information element indicates if multiple local resources are to be reserved.
This information element shall be included if a speech codec and auxiliary payload types are configured. | +| | | Local Connection Address Request | M | This information element requests an IP address and port number on the TrGW that the remote end can send user plane data to. | +| | | Remote Source Address Filtering | O | This information element indicates that remote source address filtering is required. | +| | | Remote Source Address Mask | C | This information element provides information on the valid remote source addresses. This may be included if remote source address filtering is included. It shall not be included if remote source address filtering is not included. | +| | | Remote Source Port Filtering | O | This information element indicates that remote source port filtering is required. | +| | | Remote Source Port | C | This information element identifies the valid remote source port. This may be included if remote source port filtering is included. It shall not be included if remote source port filtering is not included. (NOTE 1) | +| | | Remote Source Port Range | C | This information element identifies a range of valid remote source ports. This may be included if remote source port filtering is included. It shall not be included if remote source port filtering is not included. (NOTE 1) | +| | | RTCP handling | O | Indicates whether or not the TrGW shall reserve a port for an RTCP flow. | +| | | Notify termination heartbeat | M | This information element requests termination heartbeat indications. | +| | | Notify Released Bearer | O | This information element requests a notification of a released bearer. | + +| | | | +|-------------------------------------|---|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| DiffServ Code Point | O | This information element indicates a specific DiffServ code point to be used in the IP header in packets sent on the IP termination. | +| DiffServ Tagging Behaviour | O | This information element indicates whether the Diffserv code point in the IP header in packets sent on the IP termination should be copied from the received value or set to a specific value. | +| IP Realm Identifier | O | This information element indicates the IP realm of the IP termination. | +| Traffic Policing Required | O | This information element indicates that policing of the media flow is required. | +| Peak Data Rate | O | This information element may be present if Policing is required and specifies the permissible peak data rate for a media stream. (NOTE 2) | +| Sustainable Data Rate | O | This information element may be present if Policing is required and specifies the permissible sustainable data rate for a media stream. (NOTE 2) | +| Delay Variation Tolerance | O | This information element may be present if Policing on Peak Data Rate is required and specifies the maximum expected delay variation tolerance for the corresponding media stream. | +| Maximum Burst Size | C | This information element shall be present if Policing on Sustainable Data Rate is required and specifies the maximum expected burst size for the corresponding media stream. | +| Media Inactivity Detection Required | O | This information element indicates that detection of inactive media flows is required. | +| Inactivity Detection Time | C | This information element may be present if Inactive Media Detection is required and specifies the Inactivity Detection time. | +| Inactivity Detection Direction | C | This information element may be present if Inactive Media Detection is required and specifies the Inactivity Detection direction. | +| ECN Enable | O | This information element requests the TrGW to apply ECN procedures | +| ECN Initiation Method | C | This information element specifies the ECN Initiation method and requests the TrGW to perform IP header settings as an ECN endpoint, or indicates that ECN bits shall be passed transparently. It may be included only if ECN is enabled. | +| Congestion Response Method | C | This information element specifies the ECN Congestion Response Method; receiver driven or sender driven. The default is "received driven congestion control". It may be included only if ECN is enabled and the TrGW acts as ECN endpoint. (NOTE 3) | +| ECN ECT Marking | C | This information element specifies the ECN ECT Marking. It may be included only if ECN is enabled and the TrGW acts as ECN endpoint. (NOTE 3) | +| ECN Mode | C | This information element specifies the ECN Mode. It may be included only if ECN is enabled and the TrGW acts as ECN endpoint. (NOTE 3) | +| RTCP Feedback | C | This information element specifies the RTCP Feedback support. (NOTE 3) | + +| | | | | | | +|-----------------------------------------------------------------------------------------------|------|--------------------------|---|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--| +| | | XR Summary Report | C | This information element specifies the support of XR Summary Reporting. | | +| | | Notify ECN Failure Event | C | This information element requests a notification if a ECN failure occurs. It may only be supplied if ECN is enabled and the TrGW acts as ECN endpoint. | | +| Reserve TrGW Connection Point Ack | TrGW | Context | M | This information element indicates the context where the command was executed. | | +| | | Termination | M | This information element indicates the termination where the command was executed. | | +| | | Local IP Resources | C | This information element indicates the resources that the TrGW has reserved to receive the user plane data from the remote peer. This information element shall be present if it was contained in the request. If the information element was not contained in the request, it may be present in the reply. | | +| | | Local Connection Address | M | This information element indicates the IP address and port on the TrGW that shall receive user plane data from the remote peer. | | +| NOTE 1: Remote Source Port and Remote Source Port Range are mutually exclusive. | | | | | | +| NOTE 2: At least one of these information elementshall be present when policing is required. | | | | | | +| NOTE 3: This parameter does not need to be signalled if support is for 3GPP defined ECN only. | | | | | | + +#### 10.4.1.2 Configure TrGW Connection Point + +This procedure is used to configure or reconfigure an termination at the TrGW. + +##### **Table 10.4.1.2.1: Configure TrGW Connection Point Procedure** + +| Procedure | Initiated | Information element name | Information element required | Information element description | +|---------------------------------|-----------|---------------------------------|------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Configure TrGW Connection Point | IBCF | Context | M | This information element indicates the existing context. | +| | | Priority information | O | This information element shall be present if the priority information needs to be modified, it may be present otherwise. | +| | | Termination | M | This information element indicates the existing bearer termination. | +| | | IP Interface | O | This information element specifies the type of external interface to be used for the IP termination (e.g. MboIP). | +| | | Local IP Resources | O | This information element indicates the resources (e.g. codec, auxiliary payload types) that the TrGW may use on the reception of user plane data.
If Local Connection Address is supplied may be excluded (i.e. "-" is used in SDP m-line) if no transcoding or other media related functions are required. | +| | | Remote IP Resources | O | This information element indicates the resources (e.g. codec, auxiliary payload types) that the TrGW may send user plane data to.
If Remote Connection Address is supplied may be excluded (i.e. "-" is used in SDP m-line) if no transcoding or other media related functions are required. | +| | | Local Connection Address | O | This information element indicates the IP address and port on the TrGW that the remote peer can send user plane data to. | +| | | Remote Connection Address | O | This information element indicates the IP address and port that the TrGW can send user plane data to. | +| | | Reserve Value | C | This information element indicates if multiple resources are to be reserved. This information element shall be included if a speech codec and auxiliary payload types are configured. | +| | | Remote Source Address Filtering | O | This information element indicates that remote source address filtering is required. | +| | | Remote Source Address Mask | C | This information element provides information on the valid remote source addresses. This may be included if remote source address filtering is included. It shall not be included if remote source address filtering is not included. | +| | | Remote Source Port Filtering | O | This information element indicates that remote source port filtering is required. | +| | | Remote Source Port | C | This information element identifies the valid remote source port. This may be included if remote source port filtering is included. It shall not be included if remote source port filtering is not included. (NOTE 1) | +| | | Remote Source Port Range | C | This information element identifies a range of valid remote source ports. This may be included if remote source port filtering is included. It shall not be included if remote source port filtering is not included. (NOTE 1) | +| | | RTCP handling | O | Indicates whether or not the TrGW shall reserve a port for an RTCP flow | + +| | | | +|-------------------------------------|---|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Traffic Policing Required | O | This information element indicates that policing of the media flow is required. | +| Peak Data Rate | O | This information element may be present if Policing is required and specifies the permissible peak data rate for a media stream. (NOTE 2) | +| Sustainable Data Rate | O | This information element may be present if Policing is required and specifies the permissible sustainable data rate for a media stream. (NOTE 2) | +| Delay Variation Tolerance | O | This information element may be present if Policing on Peak Data Rate is required and specifies the maximum expected delay variation tolerance for the corresponding media stream. | +| Maximum Burst Size | C | This information element shall be present if Policing on Sustainable Data Rate is required and specifies the maximum expected burst size for the corresponding media stream. | +| DiffServ Code Point | O | This information element indicates a specific DiffServ code point to be used in the IP header in packets sent on the IP termination. | +| DiffServ Tagging Behaviour | O | This information element indicates whether the Diffserv code point in the IP header in packets sent on the IP termination should be copied from the received value or set to a specific value. | +| Media Inactivity Detection Required | O | This information element indicates that detection of inactive media flows is required. | +| Inactivity Detection Time | C | This information element may be present if Inactive Media Detection is required and specifies the Inactivity Detection time. | +| Inactivity Detection Direction | C | This information element may be present if Inactive Media Detection is required and specifies the Inactivity Detection direction. | +| ECN Enable | O | This information element requests the TrGW to apply ECN procedures. | +| ECN Initiation Method | C | This information element specifies the ECN Initiation method and requests the TrGW to perform IP header settings as an ECN endpoint, or indicates that ECN bits shall be passed transparently. It may be included only if ECN is enabled. | +| Congestion Response Method | C | This information element specifies the ECN Congestion Response Method; receiver driven or sender driven. The default is "received driven congestion control". It may be included only if ECN is enabled and the TrGW acts as ECN endpoint. (NOTE 3) | +| ECN ECT Marking | C | This information element specifies the ECN ECT Marking. It may be included only if ECN is enabled and the TrGW acts as ECN endpoint. (NOTE 3) | +| ECN Mode | C | This information element specifies the ECN Mode. It may be included only if ECN is enabled and the TrGW acts as ECN endpoint. (NOTE 3) | +| RTCP Feedback | C | This information element specifies the RTCP Feedback support. (NOTE 3) | +| XR Summary Report | C | This information element specifies the support of XR Summary Reporting. | + +| | | | | | | +|------------------------------------------------------------------------------------------------|------|---------------------------|---|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--| +| | | Notify ECN Failure Event | C | This information element requests a notification if a ECN failure occurs. It may only be supplied if ECN is enabled and the TrGW acts as ECN endpoint. | | +| Configure TrGW Connection Point Ack | TrGW | Context | M | This information element indicates the context where the command was executed. | | +| | | Termination | M | This information element indicates the termination where the command was executed. | | +| | | Local IP Resources | O | This information element indicates the resources that the TrGW has reserved to receive the user plane data from the far end. | | +| | | Remote IP Resources | O | This information element indicates the resource (i.e. codec) that the TrGW shall use to send user data to. May be present only if corresponding information element is present in the request. | | +| | | Local Connection Address | O | This information element indicates the IP address and port on the TrGW that the remote end can send user plane data to. | | +| | | Remote Connection Address | O | This information element indicates the IP address and port that the TrGW can send user plane data to. May be present only if corresponding information element is present in the request. | | +| NOTE 1: Remote Source Port and Remote Source Port Range are mutually exclusive. | | | | | | +| NOTE 2: At least one of these information elements shall be present when policing is required. | | | | | | +| NOTE 3: This parameter does not need to be signalled if support is for 3GPP defined ECN only. | | | | | | + +#### 10.4.1.3 Reserve and Configure TrGW Connection Point + +This procedure is used to reserve and configure multimedia-processing resources for a termination at the TrGW. + +##### **Table 10.4.1.3.1: Reserve and Configure TrGW Connection Point** + +| Procedure | Initiated | Information element name | Information element required | Information element description | +|---------------------------------------------|-----------|----------------------------------|------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Reserve and Configure TrGW Connection Point | IBCF | Context/Context Request | M | This information element indicates the existing context or requests a new context for the bearer termination. | +| | | Emergency Call Indicator | O | This information element identifies the call as emergency call that requires a preferential handling. | +| | | Priority information | O | This information element requests the TrGW to apply priority treatment for the terminations and bearer connections in the specified context. | +| | | Termination/ Termination Request | M | This information element indicates the existing bearer termination or requests a new termination for the bearer to be established. | +| | | IP Interface | O | This information element specifies the used interface type for the IP termination (e.g. MboIP). | +| | | Local IP Resources | C | This information element indicates the resource(s) (e.g. codec, auxiliary payload types) for which the TrGW shall be prepared to receive user data. May be excluded (i.e. "-" is used in SDP m-line) if no transcoding or other media related functions are required. | +| | | Remote IP Resources | C | This information element indicates the resources (e.g. codec, auxiliary payload types) that the TrGW shall use to send user data. May be excluded (i.e. "-" is used in SDP m-line) if no transcoding or other media related functions are required. | +| | | Reserve Value | C | This information element indicates if multiple IP resources are to be reserved. This information element shall be included if a speech codec and auxiliary payload types are configured. | +| | | Local Connection Address request | M | This information element requests an IP address and a port number on the TrGW that the remote end can send user plane data to. | +| | | Remote Connection Address | M | This information element indicates the IP address and ports of the remote party that the TrGW can send user plane data to. | +| | | Remote Source Address Filtering | O | This information element indicates that remote source address filtering is required. | +| | | Remote Source Address Mask | C | This information element provides information on the valid remote source addresses. This may be included if remote source address filtering is included. It shall not be included if remote source address filtering is not included. | +| | | Remote Source Port Filtering | O | This information element indicates that remote source port filtering is required. | +| | | Remote Source Port | C | This information element identifies the valid remote source port. This may be included if remote source port filtering is included. It shall not be included if remote source port filtering is not included. (NOTE 1) | +| | | Remote Source Port Range | C | This information element identifies a range of valid remote source ports. This may be included if remote source port filtering is included. It shall not be included if remote source port filtering is not included. (NOTE 1) | + +| | | | | | +|--|--|-------------------------------------|---|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | | RTCP handling | O | This information element indicates whether or not the TrGW shall reserve a port for an RTCP flow. | +| | | Notify termination heartbeat | M | This information element requests termination heartbeat indications. | +| | | Notify Released Bearer | O | This information element requests a notification of a released bearer. | +| | | IP Realm Identifier | O | This information element indicates the IP realm of the IP termination. | +| | | Traffic Policing Required | O | This information element indicates that policing of the media flow is required. | +| | | Peak Data Rate | O | This information element may be present if Policing is required and specifies the permissible peak data rate for a media stream. (NOTE 2) | +| | | Sustainable Data Rate | O | This information element may be present if Policing is required and specifies the permissible sustainable data rate for a media stream. (NOTE 2) | +| | | Delay Variation Tolerance | O | This information element may be present if Policing on Peak Data Rate is required and specifies the maximum expected delay variation tolerance for the corresponding media stream. | +| | | Maximum Burst Size | C | This information element shall be present if Policing on Sustainable Data Rate is required and specifies the maximum expected burst size for the corresponding media stream. | +| | | DiffServ Code Point | O | This information element indicates a specific DiffServ code point to be used in the IP header in packets sent on the IP termination. | +| | | DiffServ Tagging Behaviour | O | This information element indicates whether the Diffserv code point in the IP header in packets sent on the IP termination should be copied from the received value or set to a specific value. | +| | | Media Inactivity Detection Required | O | This information element indicates that detection of inactive media flows is required. | +| | | Inactivity Detection Time | C | This information element may be present if Inactive Media Detection is required and specifies the Inactivity Detection time. | +| | | Inactivity Detection Direction | C | This information element may be present if Inactive Media Detection is required and specifies the Inactivity Detection direction. | +| | | ECN Enable | O | This information element requests the TrGW to apply ECN procedures. | +| | | ECN Initiation Method | C | This information element specifies the ECN Initiation method and requests the TrGW to perform IP header settings as an ECN endpoint, or indicates that ECN bits shall be passed transparently. It may be included only if ECN is enabled. | +| | | Congestion Response Method | C | This information element specifies the ECN Congestion Response Method; receiver driven or sender driven. The default is "received driven congestion control". It may be included only if ECN is enabled and the TrGW acts as ECN endpoint. (NOTE 3) | +| | | ECN ECT Marking | C | This information element specifies the ECN ECT Marking. It may be included only if ECN is enabled and the TrGW acts as ECN endpoint. (NOTE 3) | + +| | | | | | +|-------------------------------------------------|------|----------------------------|---|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | | ECN Mode | C | This information element specifies the ECN Mode. It may be included only if ECN is enabled and the TrGW acts as ECN endpoint. (NOTE 3) | +| | | RTCP Feedback | C | This information element specifies the RTCP Feedback support. (NOTE 3) | +| | | XR Summary Report | C | This information element specifies the support of XR Summary Reporting. | +| | | Notify ECN FailureEvent | C | This information element requests a notification if a ECN failure occurs due to ECN. It may only be supplied if ECN is enabled and the TrGW acts as ECN endpoint. | +| Reserve and Configure TrGW Connection Point Ack | TrGW | Context | M | This information element indicates the context where the command was executed. | +| | | Termination | M | This information element indicates the termination where the command was executed. | +| | | Local IP Resources | C | This information element indicates the resources that the TrGW has reserved to receive the user plane data from the remote side. This information element shall be present if it was contained in the request. If the information element was not contained in the request, it may be present in the reply. | +| | | Remote IP Resources | O | This information element indicates the resource (i.e. codec) that the TrGW shall use to send user data. | +| | | Local Connection Addresses | M | This information element indicates the IP address and port on the TrGW that shall receive user plane data. | +| | | Remote Connection Address | O | This information element indicates the IP address and port that the TrGW can send user plane data to. | + +NOTE 1: Remote Source Port and Remote Source Port Range are mutually exclusive. +NOTE 2: At least one of these information elements shall be present when policing is required. +NOTE 3: This parameter does not need to be signalled if support is for 3GPP defined ECN only. + +#### 10.4.1.4 Release TrGW Termination + +This procedure is used to release multimedia-processing resources for a termination at the TrGW. + +**Table 10.4.1.4.1: Release TrGW Termination** + +| Procedure | Initiated | Information element name | Information element required | Information element description | +|------------------------------|-----------|--------------------------|------------------------------|------------------------------------------------------------------------------------| +| Release TrGW Termination | IBCF | Context | M | This information element indicates the existing context. | +| | | Termination | M | This information element indicates the existing bearer termination to be released. | +| Release TrGW Termination Ack | TrGW | Context | M | This information element indicates the context where the command was executed. | +| | | Termination | M | This information element indicates the termination where the command was executed. | + +NOTE: No requirement for statistics in the Release TrGW Termination Ack has been justified by a use case. + +#### 10.4.1.5 IP Bearer Released + +**Table 10.4.1.5.1: IP Bearer Released** + +| Procedure | Initiated | Information element name | Information element required | Information element description | +|------------------------|-----------|--------------------------|------------------------------|-----------------------------------------------------------------------------------------------| +| IP Bearer Released | TrGW | Context | M | This information element indicates the context for the bearer termination. | +| | | Termination | M | This information element indicates the bearer termination where the bearer was released. | +| | | Bearer Released | M | This information element notifies a bearer release. | +| | | Release Cause | M | This information element indicates the cause of a bearer release. | +| IP Bearer Released Ack | IBCF | Context | M | This information element indicates all context are where the command was executed. | +| | | Termination | M | This information element indicates that Bearer termination is where the command was executed. | + +#### 10.4.1.6 Media Inactivity Detection + +This command is used to notify the IBCF of media inactivity on the TrGW. + +**Table 10.4.1.6.1: Media Inactivity Notification** + +| Procedure | Initiated | Information element name | Information element required | Information element description | +|-----------------------------------|-----------|--------------------------|------------------------------|-------------------------------------------------------------------------------------------------------------------| +| Media Inactivity Notification | TrGW | Context | M | This information element indicates the existing context for the bearer termination. | +| | | Termination | M | This information element indicates that bearer termination is where the media inactivity detection was activated. | +| | | Media Inactivity | M | This information element notifies the IBCF of Media inactivity detection on the bearer termination. | +| Media Inactivity Notification Ack | IBCF | Context | M | This information element indicates the context where the command was executed. | +| | | Termination | M | This information element indicates the bearer termination where the command was executed. | + +#### 10.4.1.7 Termination heartbeat indication + +This command is used by the TrGW to periodically notify the IBCF of a termination heartbeat. + +**Table 10.4.1.7.1: Termination heartbeat indication** + +| Procedure | Initiated | Information element name | Information element required | Information element description | +|--------------------------------------|-----------|--------------------------|------------------------------|------------------------------------------------------------------------------------------------------------| +| Termination heartbeat indication | TrGW | Context | M | This information element indicates the context for the bearer termination. | +| | | Bearer Termination | M | This information element indicates the bearer termination for which the termination heartbeat is reported. | +| | | Termination heartbeat | M | Hanging Termination event. | +| Termination heartbeat indication Ack | IBCF | Context | M | This information element indicates the context where the command was executed. | +| | | Bearer Termination | M | This information element indicates the bearer termination where the command was executed. | + +#### 10.4.1.8 Change Through-Connection + +This procedure is used to change the Through-connection in the bearer termination. + +**Table 10.4.1.8.1: Change Through-Connection** + +| Procedure | Initiated | Information element name | Information element required | Information element description | +|-------------------------------|-----------|-----------------------------------------------|------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------| +| Change Through-Connection | IBCF | Context/Context Request | M | This information element indicates the existing context or requests a new context for the bearer termination. | +| | | Bearer Termination/Bearer Termination Request | M | This information element indicates the existing bearer termination or requests a new Bearer termination where the through connection is changed. | +| | | Through-Connection | M | This information element indicates the through-connection of the bearer termination. | +| Change Through-Connection Ack | TrGW | Context | M | This information element indicates the context where the command was executed. | +| | | Bearer Termination | M | This information element indicates the bearer termination where the command was executed. | + +NOTE: This procedure may be combined with Reserve and Configure TrGW Connection Point, Reserve TrGW Connection Point or Configure TrGW Connection Point procedure. This list of procedures is not exhaustive. + +#### 10.4.1.9 ECN Failure Indication + +This procedure is used to report ECN related failures (see clause 10.2.13.3a). + +**Table 10.4.1.9.1: Procedures toward the IM Subsystem: ECN Failure Indication** + +| Procedure | Initiated | Information element name | Information element required | Information element description | +|--------------------------|-----------|--------------------------|------------------------------|--------------------------------------------------------------------------------------------------| +| ECN Error Indication | TrGW | Context | M | This information element indicates the context for the bearer termination. | +| | | Bearer Termination | M | This information element indicates the bearer termination for which the ECN failure is reported. | +| | | ECN Error Indication | M | This information element indicates an ECN failure event. | +| ECN Error Indication Ack | IBCF | Context | M | This information element indicates the context where the command was executed. | +| | | Bearer Termination | M | This information element indicates the bearer termination where the command was executed. | + +#### 10.4.1.10 Change Flow Direction + +This procedure may be used to change the flow direction between bearer terminations within a context for access transfer procedures (see Clause 10.2.15). + +**Table 10.4.1.10.1: Procedures toward the IM Subsystem: Change Flow Direction** + +| Procedure | Initiated | Information element name | Information element required | Information element description | +|---------------------------|------------|----------------------------------------------------|------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------| +| Change Flow Direction | IBCF(ATCF) | Context/Context Request | M | This information element indicates the existing context or a new context where the flow direction is changed. | +| | | Bearer Termination 1/ Bearer Termination 1 Request | M | This information element indicates the existing bearer termination or a new bearer termination from where the new flow direction is applied. | +| | | Bearer Termination 2/ Bearer Termination 2 Request | M | This information element indicates the existing bearer termination or a new bearer termination where the new flow direction is applied. | +| | | Flow Direction | M | This information element indicates the flow direction from the bearer termination 1 to bearer termination 2 within the context. | +| Change Flow Direction Ack | TrGW(ATGW) | Context | M | This information element indicates the context where the command was executed. | + +### 10.4.2 Non Call related Procedures + +The procedures in table 10.4.2.1 shall be applied between the IBCF and TrGW. + +**Table 10.4.2.1: Non-call related procedures** + +| Stage 3 Procedure (for information) defined in 3GPP TS 29.238 [25] | Corresponding Stage 2 Procedure defined in 3GPP TS 23.205 [28] | Remarks | +|--------------------------------------------------------------------|----------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------| +| TrGW Out of service | MGW Out of Service | | +| TrGW Communication Up | MGW Communication Up | | +| TrGW Restoration | MGW Restoration | | +| TrGW Register | MGW Register | | +| TrGW Re-register | MGW Re-register | | +| CS-IBCF Ordered Re-register | (G)MSC Server Ordered Re-register | | +| CS-IBCF Restoration | (G)MSC Server Restoration | | +| CS-IBCF Out of Service | (G)MSC Server Out of Service | | +| Termination Out-of-Service | Termination Out-of-Service | The "Termination Out-of-Service procedure" is also used as a call-related H.248 command | +| Audit Value | Audit Value | | +| Command Rejected | Command Rejected | The "Command Rejected" procedure may be used in response both to call-related and non-call-related H.248 commands. | +| TrGW Capability Change | Capability Update | | +| TrGW Resource Congestion Handling – Activate | MGW Resource Congestion Handling – Activate | | +| TrGW Resource Congestion Handling – Indication | MGW Resource Congestion Handling – Indication | | +| Inactivity timeout activation | Inactivity timeout activation | | +| Inactivity timeout indication | Inactivity timeout indication | | +| Realm Availability Change Activation | | See 3GPP TS 29.235 [29] subclause A.7.2 | +| Realm Availability Change Indication | | See 3GPP TS 29.235 [29] subclause A.7.2 | + +# --- Annex A (informative): Void. + +# Annex B (informative): Change history + +| Change history | | | | | | | | +|-----------------------|--------------|-----------------|-----------|------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|------------| +| Date | TSG # | TSG Doc. | CR | Rev | Subject/Comment | Old | New | +| 2001-02 | | | | | Version 0.0.0 Presented to CN3 #16 – Sophia Antipolis - Initial Proposal - TS 29.162 number allocated by MCC | | 0.0.0 | +| 2001-05 | | | | | Tdocs N3-010226 and N3-010200 agreed at CN3#17 - Rio Grande, Puerto Rico | | 0.1.0 | +| 2001-10 | | | | | Tdoc N3-010331 agreed at CN3#18 - Dresden, Germany | 0.1.0 | 0.2.0 | +| 2001-10 | | | | | Revised TS based on decision within CN3#19 to reduce the scope of Work Item - as proposed in Tdoc N3-010425. Clean version based on changes agreed in N3-010479 at Cn3#19 - Brighton, UK. | 0.2.0 | 0.3.0 | +| 2001-11 | | | | | Added informative Annex A about interworking between IPv4 and IPv6, as agreed in Cn3#20 Cancun. | 0.3.0 | 0.4.0 | +| 2002-01 | | | | | Included N3-020094, N3-020104, and tidied editors notes. | 0.4.0 | 0.5.0 | +| 2002-02 | | | | | Editorial changes agreed in CN3#21, Sophia Antipolis. | 0.5.0 | 0.6.0 | +| 2002-02 | | | | | DAB, MCC some minor editorials | 0.6.0 | 0.6.1 | +| 2002-03 | | | | | Presented as v1.0.0 to TSG#15 for information | 0.6.1 | 1.0.0 | +| 2004-08 | | | | | Changes e.g. on IPv4-IPv6 interworking agreed in CN3#33, Sophia | 1.0.0 | 1.1.0 | +| 2004-09 | | | | | Editorial corrections made to ensure alignment with 3GPP drafting rules | 1.1.0 | 1.1.1 | +| 2004-10 | | | | | Changes e.g. on IPv4-IPv6 interworking agreed in CN3#33bis, Sophia | 1.1.1 | 1.2.0 | +| 2004-11 | | | | | Included changes agreed at CN3#34 | 1.2.0 | 1.3.0 | +| 2004-11 | | | | | Editorial update | 1.3.0 | 2.0.0 | +| 2004-12 | CN#26 | | | | Approved at Release 6 | 2.0.0 | 6.0.0 | +| 2005-06 | CP#28 | CP-050037 | 002 | 2 | ALG transparency | 6.0.0 | 6.1.0 | +| 2005-09 | CP#29 | CP-050377 | 003 | | Correction to obsolete reference | 6.1.0 | 6.2.0 | +| 2005-12 | CP#30 | | | | Created by MCC for reference by TISPAN | 6.2.0 | 7.0.0 | +| 2006-03 | CP#31 | CP-060051 | 005 | 2 | IBCF | 7.0.0 | 7.1.0 | +| 2008-05 | CP#40 | CP-080297 | 006 | 1 | Additions of subclause for TISPAN TIP/TIR and Common Basic Communication supplementary service interworking | 7.1.0 | 8.0.0 | +| 2008-12 | CP#42 | CP-080753 | 008 | 2 | Clarification of NAT/NAPT in 29.162 | 8.0.0 | 8.1.0 | +| 2008-12 | CP#42 | CP-080767 | 011 | 1 | [IBCF] 29.162 Ix - Clarification of protocol reference for Ix | 8.0.0 | 8.1.0 | +| 2008-12 | CP#42 | CP-080767 | 012 | 6 | [IBCF] 29.162 Ix Voice/audio transcoding | 8.0.0 | 8.1.0 | +| 2009-03 | CP#43 | CP-090079 | 021 | | Correction to 9.2.2.3 | 8.1.0 | 8.2.0 | +| 2009-03 | CP#43 | CP-090093 | 023 | 1 | Removal of Ix Interface from Release 8 | 8.1.0 | 8.2.0 | +| 2009-03 | CP#43 | CP-090098 | 022 | 4 | Ix procedures | 8.2.0 | 9.0.0 | +| 2009-05 | CP#44 | CP-090352 | 024 | 1 | Specification re-structuring | 9.0.0 | 9.1.0 | +| 2009-05 | CP#44 | CP-090471 | 025 | 3 | Use Case for Media Handling | 9.0.0 | 9.1.0 | +| 2009-05 | CP#44 | CP-090352 | 026 | 1 | Corrections to IM-IBCF / CS-TrGW non-call related procedures | 9.0.0 | 9.1.0 | +| 2009-05 | CP#44 | CP-090352 | 027 | | Ix protocol specified in Rel-9 | 9.0.0 | 9.1.0 | +| 2009-05 | CP#44 | CP-090352 | 028 | 3 | IP Address and Port Conversion | 9.0.0 | 9.1.0 | +| 2009-05 | CP#44 | CP-090352 | 029 | 1 | Source IP Address and Port Filtering | 9.0.0 | 9.1.0 | +| 2009-09 | CP#45 | CP-090582 | 032 | 1 | Addition of Release TrGW Termination to IMS-IBCF procedures | 9.1.0 | 9.2.0 | +| 2009-09 | CP#45 | CP-090582 | 033 | 2 | Handling of RTCP Streams | 9.1.0 | 9.2.0 | +| 2009-09 | CP#45 | CP-090582 | 034 | 3 | Use of Media Information at TrGW not supporting transcoding | 9.1.0 | 9.2.0 | +| 2009-09 | CP#45 | CP-090582 | 036 | 1 | Notification of released bearer | 9.1.0 | 9.2.0 | +| 2009-09 | CP#45 | CP-090582 | 037 | | Remote IP resources in responses optional | 9.1.0 | 9.2.0 | +| 2009-12 | CP#46 | CP-090851 | 039 | 4 | Media Inactivity Detection | 9.2.0 | 9.3.0 | +| 2009-12 | CP#46 | CP-090851 | 041 | 6 | Handling of RTCP | 9.2.0 | 9.3.0 | +| 2009-12 | CP#46 | CP-090851 | 042 | 2 | QoS Packet Marking | 9.2.0 | 9.3.0 | +| 2009-12 | CP#46 | CP-090851 | 043 | 2 | Termination Heartbeat Procedure | 9.2.0 | 9.3.0 | +| 2009-12 | CP#46 | CP-090851 | 045 | 2 | Mandatory features in TrGW | 9.2.0 | 9.3.0 | +| 2009-12 | CP#46 | CP-090851 | 046 | 2 | Specification clean-up | 9.2.0 | 9.3.0 | +| 2009-12 | CP#46 | CP-090851 | 047 | 1 | Abbreviations Tidy-Up | 9.2.0 | 9.3.0 | +| 2009-12 | CP#46 | CP-090851 | 048 | | Non-Call Related Procedure Alignment | 9.2.0 | 9.3.0 | +| 2009-12 | CP#46 | CP-090851 | 049 | 1 | Use of IP Interface Type | 9.2.0 | 9.3.0 | +| 2009-12 | CP#46 | CP-090851 | 050 | 3 | Traffic Policing | 9.2.0 | 9.3.0 | +| 2010-03 | CP#47 | CP-100089 | 052 | 4 | Support of end-to-end IMS media plane security | 9.3.0 | 9.4.0 | +| 2010-06 | CP#48 | CP-100320 | 056 | 2 | Transport protocol to be indicated to gateway for end-to-end media security | 9.4.0 | 9.5.0 | +| 2010-06 | CP#48 | CP-100317 | 057 | 1 | Handling of Stream mode | 9.4.0 | 9.5.0 | +| 2010-06 | CP#48 | CP-100315 | 059 | 2 | MSC Server enhanced for ICS missing in figure | 9.4.0 | 9.5.0 | +| 2010-06 | CP#48 | CP-100317 | 063 | 1 | Resolution of editors notes | 9.4.0 | 9.5.0 | +| 2010-09 | CP#49 | CP-100605 | 065 | 1 | Processing of fragmentation | 9.5.0 | 9.6.0 | +| 2010-09 | CP#49 | CP-100551 | 068 | 1 | Local IP Resources IE: resolution of Editors Notes | 9.5.0 | 9.6.0 | +| 2010-09 | CP#49 | CP-100551 | 069 | 1 | Procedures for Emergency indicator | 9.5.0 | 9.6.0 | +| 2010-12 | CP#50 | CP-100787 | 070 | 1 | Support of ECN | 9.6.0 | 10.0.0 | +| 2011-03 | CP#51 | CP-110117 | 75 | 2 | OMR | 10.0.0 | 10.1.0 | +| 2011-03 | CP#51 | CP-110119 | 76 | 2 | ECN Updates | 10.0.0 | 10.1.0 | + +| | | | | | | | | +|---------|-------|-----------|-----|---|--------------------------------------------------------------------------|--------|--------| +| 2011-03 | CP#51 | CP-110123 | 71 | 3 | Add missing E-CSCF to interworking network diagram | 10.0.0 | 10.1.0 | +| 2011-06 | CP#52 | CP-110397 | 79 | 3 | Overlapping 3GPP TS 29.162 and 3GPP TS 29.165 specifications | 10.1.0 | 10.2.0 | +| 2011-06 | CP#52 | CP-110402 | 81 | | Main functions supported at the Ix Interface corrections | 10.1.0 | 10.2.0 | +| 2011-06 | CP#52 | CP-110416 | 82 | | Editor's note removed | 10.1.0 | 10.2.0 | +| 2011-06 | CP#52 | CP-110410 | 83 | 3 | Correcting reference and errors in ECN | 10.1.0 | 10.2.0 | +| 2011-06 | CP#52 | CP-110408 | 84 | | Correcting minor errors in OMR procedures | 10.1.0 | 10.2.0 | +| 2011-06 | CP#52 | CP-110417 | 89 | 1 | Adding release version to external references | 10.1.0 | 10.2.0 | +| 2011-06 | CP#52 | CP-110417 | 90 | 1 | Missing subclause added and errors corrected | 10.1.0 | 10.2.0 | +| 2011-06 | CP#52 | CP-110410 | 91 | 3 | Interworking with Non-3GPP ECN networks | 10.1.0 | 10.2.0 | +| 2011-06 | CP#52 | CP-110410 | 92 | 3 | Adapting ECN IEs to agreed ECN H.248 package | 10.1.0 | 10.2.0 | +| 2011-09 | CP#53 | CP-110622 | 93 | | MSC server missing in figure 3 | 10.2.0 | 10.3.0 | +| 2011-09 | CP#53 | CP-110622 | 95 | 1 | Replacing annex A with a reference | 10.2.0 | 10.3.0 | +| 2011-09 | CP#53 | CP-110622 | 96 | 2 | Interworking of SIP messages clarification | 10.2.0 | 10.3.0 | +| 2011-09 | CP#53 | CP-110617 | 97 | 1 | ECN Interworking of AMR mode control | 10.2.0 | 10.3.0 | +| 2011-09 | CP#53 | CP-110618 | 98 | 1 | eSRVCC support at Ix interface | 10.2.0 | 10.3.0 | +| 2011-09 | CP#53 | CP-110617 | 99 | 2 | ECN reference update and other small corrections | 10.2.0 | 10.3.0 | +| 2011-12 | CP#54 | CP-110836 | 100 | | MSC server enhanced for SRVCC | 10.3.0 | 10.4.0 | +| 2012-03 | CP#55 | CP-120065 | 101 | 2 | ECN Initiation Method indication | 10.4.0 | 10.5.0 | +| 2012-06 | CP#56 | CP-120344 | 112 | 1 | Reference update: draft-ietf-avtcore-ecn-for-rtp | 10.5.0 | 10.6.0 | +| 2012-06 | CP#56 | CP-120377 | 104 | 3 | Multimedia Priority Control of Media Gateway resources | 10.6.0 | 11.0.0 | +| 2012-12 | CP#58 | CP-120828 | 114 | 1 | Reference update: RFC 6679 | 11.0.0 | 11.1.0 | +| 2012-12 | CP#58 | CP-120839 | 115 | 4 | Support of Multimedia Priority Service (MPS) in Modify over Ix Interface | 11.0.0 | 11.1.0 | +| 2013-12 | CP#62 | CP-130670 | 121 | 2 | Architecture update | 11.1.0 | 11.2.0 | \ No newline at end of file diff --git a/marked/Rel-11/29_series/29164/5a4e62bead259c258d069fd3663ea670_img.jpg b/marked/Rel-11/29_series/29164/5a4e62bead259c258d069fd3663ea670_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7805e681ca5ce9ff8c5cd55c11e52f6fca0917fd --- /dev/null +++ b/marked/Rel-11/29_series/29164/5a4e62bead259c258d069fd3663ea670_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c129cefa42a79e0dea2cc12c701024711ac98e46bf19c6e9361f3ecefa2e5b05 +size 51788 diff --git a/marked/Rel-11/29_series/29164/69f52512bb7387a5dc9f952279513019_img.jpg b/marked/Rel-11/29_series/29164/69f52512bb7387a5dc9f952279513019_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..dada0122a4379870e4c01c939a5a1abcdf8fb5e6 --- /dev/null +++ b/marked/Rel-11/29_series/29164/69f52512bb7387a5dc9f952279513019_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5cdaba29a83114c6b0cbe0c6ec414040320d69a58bfeff540b56fdf02ebf49b0 +size 37090 diff --git a/marked/Rel-11/29_series/29164/704082cc3e11776bda29595c76411362_img.jpg b/marked/Rel-11/29_series/29164/704082cc3e11776bda29595c76411362_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..089f76fea10c069c96201a9f2fb60e4d04f7ebde --- /dev/null +++ b/marked/Rel-11/29_series/29164/704082cc3e11776bda29595c76411362_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8ccc6ae094916d36da65b00865df95ca403ccccbec5fc20ccd4043e7df449411 +size 55437 diff --git a/marked/Rel-11/29_series/29164/7efae06af3af43ffe5d4b956a679cf54_img.jpg b/marked/Rel-11/29_series/29164/7efae06af3af43ffe5d4b956a679cf54_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fcb637447f1629e00aeccf8d8997e0ee81ca863e --- /dev/null +++ b/marked/Rel-11/29_series/29164/7efae06af3af43ffe5d4b956a679cf54_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7969ddab81376b381a662853b047dff5c634e646cbcf9799ad8606ade355bfd9 +size 61097 diff --git a/marked/Rel-11/29_series/29164/8307f6b04df072c9332f9987e034272c_img.jpg b/marked/Rel-11/29_series/29164/8307f6b04df072c9332f9987e034272c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5ea01368ceaeffaf167141e4c4a17791b69342e6 --- /dev/null +++ b/marked/Rel-11/29_series/29164/8307f6b04df072c9332f9987e034272c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:dbc1db80d138aa9b1ccc65ff6e330c13a383ee6526a3c9efeb40ff8089522494 +size 40746 diff --git a/marked/Rel-11/29_series/29164/dbe553cf16dd14073b89a8263a428664_img.jpg b/marked/Rel-11/29_series/29164/dbe553cf16dd14073b89a8263a428664_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0ced9566a6ab705516ce63799be8cd55b171f417 --- /dev/null +++ b/marked/Rel-11/29_series/29164/dbe553cf16dd14073b89a8263a428664_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5010624251206b00ee4b7481eaeecc0c84d22a1b83f4b2e7c41771c13a54f815 +size 67985 diff --git a/marked/Rel-11/29_series/29164/raw.md b/marked/Rel-11/29_series/29164/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..dfbf3a998ed91f03e69e9fb5aecbcef7678199f5 --- /dev/null +++ b/marked/Rel-11/29_series/29164/raw.md @@ -0,0 +1,546 @@ + + + + +CS Domain, LTE, Interworking, SIP-I, BICC, ISUP + +# Contents + +| | | +|-----------------------------------------------------------------------------------------------------------------|----| +| Foreword ..... | 5 | +| 1 Scope..... | 6 | +| 2 References..... | 6 | +| 3 Definitions and abbreviations ..... | 8 | +| 3.1 Definitions..... | 8 | +| 3.2 Abbreviations ..... | 8 | +| 4 Network characteristics..... | 8 | +| 4.1 Key characteristics of ISUP/BICC based CS Domain..... | 8 | +| 4.2 Key characteristics of external SIP-I network..... | 8 | +| 5 Interworking reference model..... | 9 | +| 6 Control plane interworking..... | 9 | +| 6.1 General ..... | 9 | +| 6.2 Interworking between CS Domain using ISUP signalling and external network using SIP-I signalling ..... | 10 | +| 6.2.1 Control Plane Interworking ..... | 10 | +| 6.2.2 Services performed by network entities in the control plane ..... | 11 | +| 6.2.2.1 Services of the IWU..... | 11 | +| 6.2.2.2 Services of the external SIP-I signalling function ..... | 11 | +| 6.2.3 Signalling interactions between network entities in the control plane ..... | 11 | +| 6.2.3.1 Signalling between the IWU and SIP-I signalling function ..... | 11 | +| 6.2.4 SIP-ISUP protocol interworking ..... | 11 | +| 6.2.4.1 Incoming call interworking from SIP-I to ISUP at I-IWU ..... | 11 | +| 6.2.4.1.0 General ..... | 11 | +| 6.2.4.1.1 Interworking of received ISUP messages to SIP messages ..... | 11 | +| 6.2.4.1.2 Receipt of encapsulated ISUP information within SIP ..... | 12 | +| 6.2.4.1.3 Special Procedures for the Reception of SIP INVITE request..... | 12 | +| 6.2.4.1.3.1 Propagation of overlap signalling toward the 3GPP CS domain ..... | 12 | +| 6.2.4.1.3.2 Derivation of TMR, USI and HLC parameters within send IAM message ..... | 12 | +| 6.2.4.1.3.3 Receipt of SIP INVITE without SDP offer ..... | 12 | +| 6.2.4.2 Outgoing Call Interworking from ISUP to SIP-I at O-IWU..... | 13 | +| 6.2.4.2.1 General ..... | 13 | +| 6.2.4.2.2 Sending of ISUP information to adjacent SIP nodes ..... | 13 | +| 6.2.4.2.3 Receipt of encapsulated ISUP information within SIP-I ..... | 13 | +| 6.2.4.2.4 Special procedures related to outgoing INVITE..... | 14 | +| 6.2.4.2.4.1 Overlap Signalling..... | 14 | +| 6.2.4.2.4.2 Coding of encapsulated ISUP IAM parameters in outgoing INVITE..... | 14 | +| 6.2.4.2.4.3 Media offered in SDP of outgoing INVITE ..... | 14 | +| 6.3 Interworking between CS Domain using BICC signalling and external network using SIP-I signalling ..... | 14 | +| 6.3.1 Control Plane Interworking ..... | 14 | +| 6.3.2 SIP-BICC protocol interworking..... | 15 | +| 6.3.2.1 General..... | 15 | +| 6.3.2.2 Incoming call interworking from SIP to BICC at I-IWU ..... | 15 | +| 6.3.2.3 Outgoing Call Interworking from BICC to SIP at O-IWU..... | 15 | +| 6.4 Supplementary services..... | 15 | +| 6.4.1 Special procedures for supplementary service interworking..... | 15 | +| 6.4.2 Interworking of CLIP/CLIR supplementary service ..... | 16 | +| 6.4.3 Interworking of Call Hold (HOLD) supplementary service..... | 16 | +| 6.4.4 Interworking of Completion of Calls to Busy Subscriber (CCBS) supplementary service to SIP networks ..... | 16 | +| 7 User plane Interworking..... | 16 | +| 7.1 ISUP based CS Domain ..... | 16 | +| 7.2 BICC based CS Domain..... | 16 | +| 8 Interactions between control node and MGW ..... | 17 | +| 8.1 Overview ..... | 17 | +| 8.2 Signalling interactions..... | 17 | + +8.2.1 Backward through-connection for outgoing call interworking from BICC to SIP at O-IWU. .... 17 +8.2.2 Handling of RTP telephone events..... 17 +8.3 Signalling procedures..... 18 +**Annex A (normative): Codec Negotiation between a BICC based CS Domain and an external SIP-I network..... 19** +Annex B (informative): Change history..... 20 + +# --- Foreword + +This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +# --- 1 Scope + +The present document defines interworking procedures between a 3GPP CS domain (see 3GPP TS 23.205 [2]) which applies either BICC or ISUP as signalling protocol, and external networks that use SIP-I (see ITU-T Q.1912.5 [20], Profile C) as signalling protocol. The document also describes the related interworking architecture. The control plane interworking is performed by an interworking unit at the interconnection between the 3GPP CS domain and an external SIP-I network. The user plane interworking is performed by an MGW. The present document defines stage 2 procedures for the control of the MGW. + +The present specification reuses existing interworking procedures of 3GPP TS 29.163 [4] and ITU-T Q.1912.5 [20], Profile C, as far as possible. + +# --- 2 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. + - For a specific reference, subsequent revisions do not apply. + - For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. +- [1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications". +- [2] 3GPP TS 23.205: "Bearer-independent circuit-switched core network; Stage 2". +- [3] 3GPP TS 26.102: "Adaptive Multi-Rate (AMR) speech codec; Interface to Iu and Uu". +- [4] 3GPP TS 29.163: "Interworking between the IP Multimedia (IM) Core Network (CN) subsystem and Circuit Switched (CS) networks". +- [5] 3GPP TS 29.205: "Application of Q.1900 series to Bearer Independent CS Network architecture; Stage 3". +- [6] 3GPP TS 29.332: "Media Gateway Control Function (MGCF) – IM-Media Gateway (IM-MGW) interface, Stage 3". +- [7] 3GPP TS 29.414: "Core network Nb data transport and transport signalling". +- [8] 3GPP TS 29.415: "Core network Nb interface user plane protocols". +- [9] ITU-T Recommendation E.164 (05/1997): "The international public telecommunication numbering plan". +- [10] ITU-T Recommendation G.711 (11/98): "Pulse Code Modulation (PCM) of voice frequencies". +- [11] ITU-T Recommendation H.248.1 (05/02): "Gateway control protocol: Version 2". +- [12] ITU-T Recommendation I.363.5 (1996): "B-ISDN ATM Adaptation Layer specification: Type 5 AAL". +- [13] ITU-T Recommendation Q.701 (03/93), Q.702 (11/88), Q.703 (07/96), Q.704 (07/96), Q.705 (03/93), Q.706 (03/93), Q.707 (11/88), Q.708 (03/99), Q.709 (03/93): "Functional description of the message transfer part (MTP) of Signalling System No. 7". + +- [14] ITU-T Recommendation Q.730 (12/99), Q.731.1 (07/96), Q.731.3 (03/93), Q.731.4 (03/93), Q.731.5 (03/93), Q.731.6 (03/93), Q.731.7 (06/97), Q.731.8 (02/92), Q.732.5-2 (12/99), Q.732.7 (07/96), Q.733.1 (02/92), Q.733.2 (03/93), Q.733.3 (06/97), Q.733.4 (03/93), Q.733.5 (12/99), Q.734.1 (03/93), Q.734.2 (07/96), Q.735.1 (03/93), Q.735.3 (03/93), Q.735.6 (07/93), Q.736.1 (10/95), Q.736.3 (10/95), Q.737.1 (06/97): "ISDN user part supplementary services". +- [15] ITU-T Recommendations Q.761 to Q.764 (12/99): "Signalling System No.7 ISDN User Part". +- [16] ITU-T Recommendation Q.765 (2000): "Signalling System No. 7 – Application transport mechanism". +- [17] ITU-T Recommendation Q.765.5 (2000): "Signalling system No. 7 – Application transport mechanism: Bearer Independent Call Control (BICC)". +- [18] ITU-T Recommendation Q.850 (1998): "Usage of cause and location in the Digital Subscriber Signalling System No. 1 and the Signalling System No. 7 ISDN User Part". +- [19] ITU-T Recommendations Q.1902.1 to Q.1902.6 (07/2001): "Bearer Independent Call Control". +- [20] ITU-T Recommendation Q.1912.5 (03/04): "Interworking between Session Initiation Protocol (SIP) and Bearer Independent Call Control Protocol or ISDN User Part". +- [21] ITU-T Recommendation Q.2110 (1994): "B-ISDN ATM adaptation layer - Service Specific Connection Oriented Protocol (SSCOP)". +- [22] ITU-T Recommendation Q.2140 (1995): "B-ISDN ATM adaptation layer - Service specific coordination function for signalling at the network node interface (SSCF AT NNI)". +- [23] ITU-T Recommendation Q.2210 (1996): "Message transfer part level 3 functions and messages using the services of ITU-T Recommendation Q.2140". +- [24] IETF RFC 791: "Internet Protocol". +- [25] IETF RFC 768: "User Datagram Protocol". +- [26] IETF RFC 793: "Transmission Control Protocol". +- [27] IETF RFC 2460: "Internet Protocol, Version 6 (IPv6) Specification" +- [28] IETF RFC 4733: "RTP Payload for DTMF Digits, Telephony Tones and Telephony Signals". +- [29] IETF RFC 2960: "Stream Control Transmission Protocol". +- [30] IETF RFC 2976: "The SIP INFO Method". +- [31] IETF RFC 3204: "MIME media types for ISUP and QSIG Objects". +- [32] IETF RFC 3261: "SIP: Session Initiation Protocol". +- [33] IETF RFC 3262: "Reliability of provisional responses". +- [34] IETF RFC 3264: "An Offer/Answer Model with the Session Description Protocol (SDP)". +- [40] IETF RFC 3311: "SIP UPDATE method". +- [35] IETF RFC 3312: "Integration of Resource Management and Session Initiation Protocol (SIP)". +- [36] IETF RFC 3550: "RTP: A Transport Protocol for Real-Time Applications". +- [37] 3GPP TS 29.202: "Core Signalling System No. 7 (SS7) signalling transport in core network; Stage 3". +- [38] 3GPP TS 29.231: "Application of SIP-I Protocols to Circuit Switched (CS) core network architecture; Stage 3". +- [39] 3GPP TS 29.235: "Interworking between the 3GPP CS domain with SIP-I as signalling protocol and other networks". + +# --- 3 Definitions and abbreviations + +## 3.1 Definitions + +For the purposes of the present document, the terms and definitions given in 3GPP TR 21.905 [1], in 3GPP TS 29.163 [4], in ITU-T E.164 [9], in ITU-T Q.1912.5 [20] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in any other of the specifications listed above. + +**Interworking Unit (IWU):** Logical entity that interworks SIP-I signalling with BICC or ISUP signalling in the 3GPP CS Domain. + +**Incoming Interworking Unit (I-IWU):** Logical entity that terminates incoming calls from the external SIP-I network side and originates outgoing calls towards the CS Domain side using the BICC or ISUP protocols. + +**Outgoing Interworking Unit (O-IWU):** Logical entity that terminates incoming BICC or ISUP calls from the CS Domain side and originates outgoing calls towards external SIP-I network. + +**External SIP-I signalling function:** function in the external network, which has the capabilities to process SIP with encapsulated ISUP messages. + +For references to 3GPP TS 29.163 [4] procedures within the present specification, the MGCF in 3GPP TS 29.163 [4] is to be understood as IWU. The IM-MGW is to be understood as MGW. The Mn interface is to be understood as interface between IWU and MGW. The IM CN subsystem is to be understood as external SIP-I network. The CS network is to be understood as 3GPP CS domain. + +## 3.2 Abbreviations + +For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [1], in 3GPP TS 29.163 [4], in ITU-T E.164 [9], in ITU-T Q.1912.5 [20], and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in any other of the specification listed above. + +| | | +|--------|-------------------------------------| +| IW-MGW | Interworking Media Gateway Function | +|--------|-------------------------------------| + +# --- 4 Network characteristics + +## 4.1 Key characteristics of ISUP/BICC based CS Domain + +The 3GPP CS domain uses either BICC Capability Set 2 (see ITU-T Q.1902.1 to Q.1902.6 [19] and Q.765.5 [17]) with 3GPP specific extensions, as specified for the 3GPP Nc interface in 3GPP TS 29.205 [5], or ISUP (see ITU-T Q.761 to Q.764 [15]), as signalling protocol. + +If BICC is used as signalling protocol, the 3GPP Nb interface, as specified in 3GPP TS 29.414 [7] and 3GPP TS 29.415 [8], is used for the user plane transport. If ISUP is applied as signalling protocol, TDM transport of the user plane is applied. + +## 4.2 Key characteristics of external SIP-I network + +The external SIP-I network applies SIP, IETF RFC 3261 [32], with ISUP encapsulated according to IETF RFC 3204 [31], as specified in ITU-T Q.1912.5 [20] Profile C. The SIP Signalling Profile defined for Profile C in Annex C of Q.1912.5 is applied. + +The network uses either IPv4 (IETF RFC 791 [24]) or IPv6 (IETF RFC 2460 [27]). + +For the transport of most media, RTP (IETF RFC 3550 [36]) over UDP (IETF RFC 768 [25]) is applied. + +For the transport of control signalling, UDP (IETF RFC 768 [25]), TCP (IETF RFC 793 [26]) or SCTP (IETF RFC 2960 [29]) can be used. + +# 5 Interworking reference model + +Figure 5.1 details the interworking reference model for the present specification + +![Figure 5.1: Interworking reference model diagram. The diagram shows the interconnection between an External SIP-I Network and the 3GPP CS Domain. On the left, the External SIP-I Network connects to an IWU via SIP-I (Control Plane) and a media path (User Plane, e.g., RTP/UDP/IP). The IWU is part of an IW-MGW. The IWU connects to an SGW via BICC/ISUP over M3UA/SCTP/IP (Control Plane). The SGW connects to a (G)MSC Server via Nc/ISUP over TDM (Control Plane). The IW-MGW connects to a (G)MSC Server via BICC/ISUP over SCTP/IP (Control Plane) and to an MGW via Nb/TDM (User Plane). The (G)MSC Server connects to the MGW via Mc (Control Plane). A legend indicates that solid lines represent the User Plane and dashed lines represent the Control Plane. A light blue shaded area indicates the Scope Of this TS, encompassing the IWU, IW-MGW, SGW, (G)MSC Server, and MGW.](dbe553cf16dd14073b89a8263a428664_img.jpg) + +Figure 5.1: Interworking reference model diagram. The diagram shows the interconnection between an External SIP-I Network and the 3GPP CS Domain. On the left, the External SIP-I Network connects to an IWU via SIP-I (Control Plane) and a media path (User Plane, e.g., RTP/UDP/IP). The IWU is part of an IW-MGW. The IWU connects to an SGW via BICC/ISUP over M3UA/SCTP/IP (Control Plane). The SGW connects to a (G)MSC Server via Nc/ISUP over TDM (Control Plane). The IW-MGW connects to a (G)MSC Server via BICC/ISUP over SCTP/IP (Control Plane) and to an MGW via Nb/TDM (User Plane). The (G)MSC Server connects to the MGW via Mc (Control Plane). A legend indicates that solid lines represent the User Plane and dashed lines represent the Control Plane. A light blue shaded area indicates the Scope Of this TS, encompassing the IWU, IW-MGW, SGW, (G)MSC Server, and MGW. + +NOTE 1: If needed a SGW is applied for conversion (both ways) of the transport level between the IWU and the (G)MSC. The SGW may be implemented as a stand-alone entity or it may be located in another entity of the CS Domain. A SGW function is not required for certain signalling transports, where M3UA+SCTP+IP is used in CS network and IWU. The implementation options are not further discussed in the present document. + +NOTE 2: The IWU is a logical function that may reside with other 3GPP logical functions in the same physical nodes, e.g. in an (G)MSC Server. The figure shows only the logical separation. + +Figure 5.1: interworking reference model + +# 6 Control plane interworking + +## 6.1 General + +The following sub-clauses define the signalling interworking between the Bearer Independent Call Control (BICC) or ISDN User Part (ISUP) protocols and Session Initiation Protocol (SIP) with its associated Session Description Protocol (SDP) and encapsulated ISUP at an IWU. + +The IWU shall act as a Type A or Type B exchange (ITU-T Q.764 [15]) for the purposes of ISUP and BICC compatibility procedures. + +The BICC/ISUP capabilities or signalling information defined for national use are outside the scope of the present document. + +The interworking procedures are based on ITU-T Recommendation Q.1912.5 [20] profile C. Clarifications are made within this specification on the application of Q.1912.5 profile C. + +NOTE: An IWU may apply additional procedures to support interworking for national-specific capabilities. + +The services that can be supported through the use of the signalling interworking are limited to the services that are supported both within the BICC or ISUP based 3GPP CS domain and the external SIP-I network. The IWU will originate and/or terminate services or capabilities that do not interwork seamlessly across domains according to the relevant protocol recommendation or specification. + +Table 6.1.1 lists the services seamlessly interworked within the scope of the present document. + +**Table 6.1.1: Service Interworking Capabilities** + +| Service | +|------------------------------------------------------------------| +| Speech/3.1 kHz audio | +| Data Calls (optional) | +| En bloc address signalling | +| Out of band transport of DTMF tones and information. (BICC only) | +| Inband transport of DTMF tones and information. (BICC and ISUP) | +| Multiple Subscriber Number (MSN) | +| Calling Line Identification Presentation (CLIP) | +| Calling Line Identification Restriction (CLIR) | +| Connected line presentation (COLP) | +| Connected line restriction (COLR) | +| Call Hold | +| Call Forwarding | +| Explicit Call Transfer (ECT) | +| User-to-User Signalling (UUS) | +| Call Deflection (CD) | +| Closed User Group (CUG) | +| Completion of Calls to Busy Subscriber (CCBS) | +| Multi-Level Precedence and Pre-emption (MLPP) | +| Call Waiting | + +The Clause 5.3.2 of ITU-T Q.1912.5 [20] describes additional general principles specific to SIP-I. + +## 6.2 Interworking between CS Domain using ISUP signalling and external network using SIP-I signalling + +### 6.2.1 Control Plane Interworking + +The control plane between CS networks supporting ISUP and the external network using SIP-I, where the underlying network is TDM or ATM and IP respectively, is as shown in figure 6.2.1. + +![Diagram illustrating control plane interworking between CS networks supporting ISUP and an external network using SIP-I signalling. The diagram shows three main entities: (G)MSC, Interworking Unit (IWU), and External SIP-I signalling function. The (G)MSC contains ISUP, MTP3, MTP2, and L1 layers. The IWU contains ISUP, MTP3, MTP2, L1, SIP-I, TCP/UDP/SCTP, and IP layers. The External SIP-I signalling function contains SIP-I, TCP/UDP/SCTP, and IP layers. Arrows indicate the flow of ISUP and TDM signals between the (G)MSC and the IWU. A dashed line labeled NNI separates the IWU from the External SIP-I signalling function. SIP-I and IP signals are shown between the IWU and the External SIP-I signalling function.](5a4e62bead259c258d069fd3663ea670_img.jpg) + +The diagram illustrates the control plane interworking between a (G)MSC and an external network. The (G)MSC is shown with layers ISUP, MTP3, MTP2, and L1. The Interworking Unit (IWU) is shown with layers ISUP, MTP3, MTP2, L1, SIP-I, TCP/UDP/SCTP, and IP. The External SIP-I signalling function is shown with layers SIP-I, TCP/UDP/SCTP, and IP. Arrows indicate the flow of ISUP and TDM signals between the (G)MSC and the IWU. A dashed line labeled NNI separates the IWU from the External SIP-I signalling function. SIP-I and IP signals are shown between the IWU and the External SIP-I signalling function. The 3GPP PLMN is indicated below the (G)MSC. + +Diagram illustrating control plane interworking between CS networks supporting ISUP and an external network using SIP-I signalling. The diagram shows three main entities: (G)MSC, Interworking Unit (IWU), and External SIP-I signalling function. The (G)MSC contains ISUP, MTP3, MTP2, and L1 layers. The IWU contains ISUP, MTP3, MTP2, L1, SIP-I, TCP/UDP/SCTP, and IP layers. The External SIP-I signalling function contains SIP-I, TCP/UDP/SCTP, and IP layers. Arrows indicate the flow of ISUP and TDM signals between the (G)MSC and the IWU. A dashed line labeled NNI separates the IWU from the External SIP-I signalling function. SIP-I and IP signals are shown between the IWU and the External SIP-I signalling function. + +**Figure 6.2.1: Control plane interworking between CS networks supporting ISUP and an external network using SIP-I signalling** + +### 6.2.2 Services performed by network entities in the control plane + +#### 6.2.2.1 Services of the IWU + +The IWU shall provide the interaction, through the use of its interworking function, between the SS7 MTP3-User part information (as detailed in ITU-T Q.701 to 709 [13]) and SIP-I. The IWU shall also provide the encapsulation from the SS7 MTP3-User part information to the SIP-I ISUP MIME and de-encapsulation from this ISUP MIME to the SS7 MTP3-User part information. + +#### 6.2.2.2 Services of the external SIP-I signalling function + +The external SIP-I signalling function is a remote SIP User Agent capable of processing ISUP. + +### 6.2.3 Signalling interactions between network entities in the control plane + +#### 6.2.3.1 Signalling between the IWU and SIP-I signalling function + +Signalling between the SIP-I signalling function and the IWU uses the services of IPv4 (IETF RFC 791 [24]) or IPv6 (IETF RFC 2460 [27]), transport protocol such as TCP (IETF RFC 793 [26]) or UDP (IETF RFC 768 [25]) or SCTP (IETF RFC 2960 [29]), and SIP-I. + +### 6.2.4 SIP-ISUP protocol interworking + +#### 6.2.4.1 Incoming call interworking from SIP-I to ISUP at I-IWU + +##### 6.2.4.1.0 General + +The procedures for Profile C in Clause 6 of ITU-T Q.1912.5 [20] shall be applied with the modifications provided in this Clause. + +##### 6.2.4.1.1 Interworking of received ISUP messages to SIP messages + +The I-IWU receiving backwards ISUP information shall apply any interworking procedures detailed in Clause 6 of ITU-T Q.1912.5 [20] affecting parameters within the ISUP, and then proceed to encapsulate any ISUP information received (with the exception of the excluded messages detailed in 5.4.3 of ITU-T Q.1912.5 [20]) in a SIP message in a MIME body according to IETF RFC 3204 [31]. The selected SIP Header fields relating to the handling of the ISUP body shall be set as specified in Clause 5.4.1.2 of ITU-T Q.1912.5 [20]. + +##### 6.2.4.1.2 Receipt of encapsulated ISUP information within SIP + +On receipt of a SIP message containing encapsulated ISUP, the IWU shall de-encapsulate the ISUP message from the SIP message body. The received SIP message shall be mapped to an ISUP message and merged with the de-encapsulated ISUP message according to the rules for Profile C in Clause 6 of ITU-T Q.1912.5 [20]. + +NOTE 1: These precedence rules have been derived from the following principles, which can also be applied for any ISUP information not covered by the present specification: + +- 1 Where a SIP header mapping to ISUP field(s) is possible (for example the mapping of Request-URI to Called Party Number), the SIP header is given precedence over the encapsulated ISUP value in the alignment process. (Conflicts can be caused by a possible service invocation within the external SIP-I network.) +- 2 De-encapsulated ISUP information overrides ISUP information derived from default values (rather than SIP information). +- 3 Local ISUP procedures may modify information derived from SIP or default values. + +This note has been derived from text in ITU-T Q.1912.5 [20], Clause 5.4.2. + +NOTE 2: There is a certain change against ITU-T Q.1912.5 [20], where the above note is formulated as normative procedures. However, this is very high level and not required if you look at the real interworking procedures later on. Therefore formulating this as a note makes much more sense. + +##### 6.2.4.1.3 Special Procedures for the Reception of SIP INVITE request + +###### 6.2.4.1.3.1 Propagation of overlap signalling toward the 3GPP CS domain + +The procedures in Clause 6 of ITU-T Q.1912.5 [20] related to the propagation of overlap signalling across the I-IWU shall not be applied. + +NOTE: A G-MSC acting as IWU will collect all digits required to identify the callee and not propagate the overlap signalling further. Therefore, it will not apply procedures from ITU-T Q.1912.5 [20] Clause 6 related to the propagation of overlap signalling. + +###### 6.2.4.1.3.2 Derivation of TMR, USI and HLC parameters within send IAM message + +The I-IWU may choose to transcode media and shall then set the parameters according to the coding applied within the CS Domain. Otherwise, the I-IWU shall select a codec for the SIP side termination using SDP offer-answer procedures, IETF RFC 3264 [34], and shall map the SDP information of this codec to the TMR/USI/HLC parameters according to table 2a of 3GPP TS 29.163 [4]. If the information derived from this mapping matches the information in the TMR/USI/HLC parameters in the encapsulated ISUP, the TMR/USI/HLC parameters from the encapsulated ISUP should be used as they may contain additional information. If the information derived from this mapping contradicts the information in the TMR/USI/HLC parameters in the encapsulated ISUP, the TMR/USI/HLC parameters derived by the mapping shall be used. + +NOTE: The procedures in this note are an amendment compared to ITU-T Q.1912.5 [20], which simply states the TMR parameters in encapsulated ISUP shall take precedence, However this is inappropriate if an incompatible codec is selected. + +###### 6.2.4.1.3.3 Receipt of SIP INVITE without SDP offer + +An IWU may reject receipt of SIP INVITE without SDP offer, otherwise the procedures in this paragraph shall be followed. + +Upon receipt of the first INVITE with sufficient digits for an IAM to be sent, but without an SDP offer (see IETF RFC3264 [34]), the I-IWU shall construct the SDP offer with contents according to local policy, e.g. SDP for a G.711 speech call. The IWU may use the TMR and USI parameters of the encapsulated IAM to determine the desired service and construct the SDP offer accordingly. + +- 1) If reliable provisional responses (see IETF RFC 3262 [33]) are supported in the external SIP-I network, the I-IWU should immediately send the SDP offer within a 183 Session Progress message. The I-IWU should send the IAM upon receipt of the SDP answer and may take into account the media selected in the answer when constructing the IAM. +- 2) If reliable provisional responses are not supported, the I-IWU should immediately send out the IAM. The I-IWU will also include the SDP offer in the 200 OK(INVITE) SIP message according to SIP procedures. + +NOTE: The text in the preceding paragraph has been derived from ITU-T Q.1912.5 [20], Clause 6.1.1. Compared to ITU-T Q.1912.5 [20], the recommendation has been added that for an incoming INVITE without media the TMR/USI is considered to select media. Furthermore, bullet 1 recommends to wait for the SDP answer to construct TMR, USI and BICC codec list accordingly. + +#### 6.2.4.2 Outgoing Call Interworking from ISUP to SIP-I at O-IWU + +##### 6.2.4.2.1 General + +The procedures for Profile C in Clause 7 of ITU-T Q.1912.5 [20] shall be applied with the modifications provided in this Clause. + +##### 6.2.4.2.2 Sending of ISUP information to adjacent SIP nodes + +The I-IWU receiving ISUP information shall apply any interworking procedures detailed in Clause 7 of ITU-T Q.1912.5 [20] affecting parameters within the ISUP, and then proceed to encapsulate any ISUP information received (with the exception of the excluded messages detailed in 5.4.3 of ITU-T Q.1912.5 [20]) in a SIP message in a MIME body according to IETF RFC 3204 [31]. SIP Header fields relating to the handling of the ISUP body shall be set as specified in 5.4.1.2 of ITU-T Q.1912.5 [20]. + +NOTE: The text in the preceding paragraph has been derived from ITU-T Q.1912.5 [20], Clause 5.4.1. + +For a basic call setup, the SIP message used to encapsulate the ISUP message shall be the SIP message that was first triggered to be sent from the IWU as a result of the interworking specified in Clause 7 of ITU-T Q.1912.5 [20]. As an example, this means that an ISUP IAM will be encapsulated within the INVITE message that is sent out from the O-IWU. For the ISUP messages listed in Table 1 of ITU-T Q.1912.5 [20], the special procedures in Clause 5.4.3 of ITU-T Q.1912.5 are applicable. + +NOTE: The text in the preceding paragraph has been derived from ITU-T Q.1912.5 [20], Clause 5.4.1.3. + +##### 6.2.4.2.3 Receipt of encapsulated ISUP information within SIP-I + +On receipt of a SIP message containing encapsulated ISUP, the IWU shall de-encapsulate the ISUP message from the SIP message body. The received SIP message shall be mapped to an ISUP message and merged with the de-encapsulated ISUP information according to the rules in in Clause 7 of ITU-T Q.1912.5 [20]. + +NOTE: The text in the preceding paragraph has been derived from ITU-T Q.1912.5 [20], Clause 5.4.2. + +NOTE: These precedence rules have been derived from the following principles, which can also be applied for any ISUP information not covered by the present specification: + +- 1 Where a SIP header mapping to ISUP field(s) is possible (for example the mapping of Request-URI to Called Party Number), the SIP header is given precedence over the encapsulated ISUP value in the alignment process. (Conflicts can be caused by a possible service invocation within the SIP network.) +- 2 De-encapsulated ISUP information overrides ISUP information derived from default values (rather than SIP information). +- 3 Local ISUP procedures may modify information derived from SIP or default values. + +This Note has been derived from text in ITU-T Q.1912.5 [20], Clause 5.4.2 + +NOTE There is a certain change against Q.1912.5, where the above note is formulated as normative procedures. However, this is very high level and not required if you look at the real interworking procedures later on. Therefore formulating this as a Note makes much more sense. + +##### 6.2.4.2.4 Special procedures related to outgoing INVITE + +###### 6.2.4.2.4.1 Overlap Signalling + +The O-IWU does not need to support procedures related to overlap signalling in Clause 7 of ITU-T Q.1912.5 [20]. + +NOTE: No overlap signalling is used in a 3GPP CS domain. + +###### 6.2.4.2.4.2 Coding of encapsulated ISUP IAM parameters in outgoing INVITE + +The O-IWU may choose to transcode media, or attempt to interwork media without transcoding. If the O-IWU transcodes, it should set the TMR/USI/HLC parameters according to the codec applied in the SIP-I network. Otherwise, it should provide the TMR/USI/HLC parameters as received in the incoming IAM. If the I-IWU offers several codecs within SDP, it should set the TMR/USI/HLC parameters according to the preferred codec, applying the rules above for this codec. + +NOTE: ITU-T Q.1912.5 [20] does not describe the relationship between TMR/USI/HLC and SDP codec negotiation. + +###### 6.2.4.2.4.3 Media offered in SDP of outgoing INVITE + +The O-IWU should offer codecs known to be supported within the external SIP-I network. + +## 6.3 Interworking between CS Domain using BICC signalling and external network using SIP-I signalling + +### 6.3.1 Control Plane Interworking + +The control plane between CS networks supporting BICC and the external network using SIP-I, where the underlying network is SS7 and IP respectively, is shown in figures 6.3.1 and 6.3.2 in accordance to TS 29.202 [37]. + +![Diagram of control plane interworking between CS networks supporting BICC/IP and an external network using SIP-I signalling. The diagram shows three main components: (G)MSC, Interworking Unit, and External SIP-I signalling function. The (G)MSC contains layers BICC, STCMTP, M3UA, SCTP, and IP. The Interworking Unit contains layers BICC, STCMTP, M3US, SCTP, and IP, with a SIP-I layer above M3US. The External SIP-I signalling function contains layers SIP-I, TCP/UDP/SCTP, and IP. Arrows show BICC and IP connections between (G)MSC and the Interworking Unit. A dashed vertical line labeled NNI separates the Interworking Unit from the External SIP-I signalling function. SIP-I and IP connections are shown across the NNI between the Interworking Unit and the External SIP-I signalling function. The label '3GPP PLMN' is at the bottom left, and 'External SIP-I Network' is at the bottom right.](704082cc3e11776bda29595c76411362_img.jpg) + +The diagram illustrates the control plane interworking between a (G)MSC and an External SIP-I signalling function via an Interworking Unit (IWU). The (G)MSC is part of the 3GPP PLMN and contains the following protocol layers: BICC, STCMTP, M3UA, SCTP, and IP. The IWU contains layers BICC, STCMTP, M3US, SCTP, and IP, with a SIP-I layer above M3US. The External SIP-I signalling function contains layers SIP-I, TCP/UDP/SCTP, and IP. Connections are shown as follows: + + +- A BICC connection between the (G)MSC and the IWU. +- An IP connection between the (G)MSC and the IWU. +- A SIP-I connection across the Network-to-Network Interface (NNI) between the IWU and the External SIP-I signalling function. +- An IP connection across the NNI between the IWU and the External SIP-I signalling function. + + The label '3GPP PLMN' is located at the bottom left, and 'External SIP-I Network' is at the bottom right. + +Diagram of control plane interworking between CS networks supporting BICC/IP and an external network using SIP-I signalling. The diagram shows three main components: (G)MSC, Interworking Unit, and External SIP-I signalling function. The (G)MSC contains layers BICC, STCMTP, M3UA, SCTP, and IP. The Interworking Unit contains layers BICC, STCMTP, M3US, SCTP, and IP, with a SIP-I layer above M3US. The External SIP-I signalling function contains layers SIP-I, TCP/UDP/SCTP, and IP. Arrows show BICC and IP connections between (G)MSC and the Interworking Unit. A dashed vertical line labeled NNI separates the Interworking Unit from the External SIP-I signalling function. SIP-I and IP connections are shown across the NNI between the Interworking Unit and the External SIP-I signalling function. The label '3GPP PLMN' is at the bottom left, and 'External SIP-I Network' is at the bottom right. + +Figure 6.3.1: Control plane interworking between CS networks supporting BICC/IP and an external network using SIP-I signalling + +![Diagram of control plane interworking between CS networks supporting BICC/ATM and an external network using SIP-I signalling. The diagram shows three main components: (G)MSC, Interworking Unit (I-WU), and External SIP-I Network. The (G)MSC contains layers BICC, STC, MTP3B, SSCF, SSCOP, and AAL5. The I-WU contains layers BICC, STC, MTP3B, SSCF, SSCOP, and AAL5, plus a stack of SIP-I, TCP/UDP/SCTP, and IP. The External SIP-I Network contains layers SIP-I, TCP/UDP/SCTP, and IP. Arrows indicate the flow of BICC and ATM signals between the (G)MSC and I-WU. A dashed line labeled NNI separates the I-WU from the External SIP-I Network. SIP-I and IP signals are shown crossing the NNI.](7efae06af3af43ffe5d4b956a679cf54_img.jpg) + +Diagram of control plane interworking between CS networks supporting BICC/ATM and an external network using SIP-I signalling. The diagram shows three main components: (G)MSC, Interworking Unit (I-WU), and External SIP-I Network. The (G)MSC contains layers BICC, STC, MTP3B, SSCF, SSCOP, and AAL5. The I-WU contains layers BICC, STC, MTP3B, SSCF, SSCOP, and AAL5, plus a stack of SIP-I, TCP/UDP/SCTP, and IP. The External SIP-I Network contains layers SIP-I, TCP/UDP/SCTP, and IP. Arrows indicate the flow of BICC and ATM signals between the (G)MSC and I-WU. A dashed line labeled NNI separates the I-WU from the External SIP-I Network. SIP-I and IP signals are shown crossing the NNI. + +**Figure 6.3.2: Control plane interworking between CS networks supporting BICC/ATM and an external network using SIP-I signalling** + +For signalling interactions between network entities in the control plane see Clause 6.2.3. + +### 6.3.2 SIP-BICC protocol interworking + +#### 6.3.2.1 General + +Specific rules for handling of the APM mechanism have been added, which are not specified in ITU-T Q.1912.5 [20]. + +The procedures in Clause 6.2.4 shall be applied with the modifications provided the present Clause. + +The text in Clause 6.2.4 is to be understood as follows: + +- Where "ISUP" is mentioned, this shall be understood as BICC. As an exception, references to ISUP encapsulated within SIP-I shall be understood without modification, i.e. they still refer to ISUP rather than BICC. + +#### 6.3.2.2 Incoming call interworking from SIP to BICC at I-IWU + +An APM messages received from the CS side (see ITU-T Q.765 [16]) that relates to the BICC APM user (see ITU-T Q.765.5 [17]) shall not be encapsulated in any triggered SIP message. + +#### 6.3.2.3 Outgoing Call Interworking from BICC to SIP at O-IWU + +If an IAM message is received, the APM information elements (see ITU-T Q.765 [16]) relating to the BICC APM user (see ITU-T Q.765.5 [17]) shall be removed before the IAM message is encapsulated in the triggered SIP INVITE message. + +An APM messages received from the CS side (see ITU-T Q.765 [16]) that relates to the BICC APM user (see ITU-T Q.765.5 [17]) shall not be encapsulated in any triggered SIP message. + +## 6.4 Supplementary services + +### 6.4.1 Special procedures for supplementary service interworking + +The supplementary services described in Table 6.1.1 are interworked by using the parameters of the (de)encapsulated ISUP. No other interworking is required, except if otherwise described within the clauses below. + +### 6.4.2 Interworking of CLIP/CLIR supplementary service + +At the O-IWU: the service shall be supported by encapsulation. + +At the I-IWU: ITU-T Q.1912.5 [20], Annex B.1, shall apply. + +### 6.4.3 Interworking of Call Hold (HOLD) supplementary service + +The Profile C procedures in ITU-T Q.1912.5 [20], Clause B.10, shall be followed. + +### 6.4.4 Interworking of Completion of Calls to Busy Subscriber (CCBS) supplementary service to SIP networks + +The Profile C procedures of ITU-T Q.1912.5 [20], Clause B.11 shall be applied. + +# 7 User plane Interworking + +## 7.1 ISUP based CS Domain + +Figure 7.1.1 shows the user plane protocol stacks within the SIP-I network and an ISUP based CS Domain. + +Apart from speech codecs, data call related codecs, e.g. as listed in Table 2a of 3GPP TS 29.163 [4], may be used. + +![Diagram of User Plane Interworking and ISUP based CS Domain. It shows a SIP-I network on the left connected to a central MGW (Media Gateway). The MGW contains a protocol stack with layers L1, L2, IP, UDP, RTP, and Codec (e.g., G.711). Above the MGW is a 'Transcoding or Relay' block. To the right of the MGW is a CS Domain. The MGW is connected to the CS Domain via a TDM interface. The SIP-I network is connected to the MGW via the L1 layer.](69f52512bb7387a5dc9f952279513019_img.jpg) + +The diagram illustrates the user plane protocol stack for interworking between a SIP-I network and an ISUP based CS Domain. On the left, a cloud labeled 'SIP-I network' is connected to a central 'MGW' (Media Gateway). The MGW contains a protocol stack with layers L1, L2, IP, UDP, RTP, and Codec (e.g., G.711). Above the MGW is a 'Transcoding or Relay' block. On the right, a cloud labeled 'CS Domain' is connected to the MGW via a TDM interface. The MGW is connected to the CS Domain via the L1 layer. + +Diagram of User Plane Interworking and ISUP based CS Domain. It shows a SIP-I network on the left connected to a central MGW (Media Gateway). The MGW contains a protocol stack with layers L1, L2, IP, UDP, RTP, and Codec (e.g., G.711). Above the MGW is a 'Transcoding or Relay' block. To the right of the MGW is a CS Domain. The MGW is connected to the CS Domain via a TDM interface. The SIP-I network is connected to the MGW via the L1 layer. + +Figure 7.1.1: User Plane Interworking and ISUP based CS Domain + +## 7.2 BICC based CS Domain + +Figure 7.2.1 shows the user plane protocol stacks within the SIP-I network and an BICC based CS Domain. + +Apart from speech codecs, data call related codecs, e.g. as listed in Table 2a of 3GPP TS 29.163 [4], may be used. + +Within the CS domain, the Nb interface as specified in 3GPP TS 29.414 [7] and 3GPP TS 29.415 [8] is used. + +If the same codec is used on both sides, no transcoding is required. If no transcoding is performed, the procedures in Clause 8.1.1 of 3GPP TS 29.163 [4] shall be applied to interwork the Nb framing Protocol, as specified in 3GPP TS 29.415 [8], with RTP, as specified in IETF RFC 3550 [36]. + +![Diagram of User Plane Interworking for BICC based CS Domain. It shows a SIP-I network on the left connected to a central MGW. The MGW has a stack of protocols: L1, L2, IP, UDP, RTP on the left side and L1, TNL, NbFP, Codec (e.g. AMR) on the right side. A 'Transcoding or Relay' label with a double-headed arrow is above the MGW stack. The MGW is connected to a CS Domain on the right via an Nb interface.](8307f6b04df072c9332f9987e034272c_img.jpg) + +The diagram illustrates the user plane interworking for a BICC based CS Domain. On the left, a cloud labeled 'SIP-I network' is connected to a central 'MGW' (Media Gateway). The MGW contains a protocol stack. The left side of the stack, from top to bottom, consists of: 'Codec, e.g. G.711', 'RTP', 'UDP', 'IP', 'L2', and 'L1'. The right side of the stack, from top to bottom, consists of: 'Codec, e.g. AMR', 'NbFP', 'TNL', and 'L1'. Above the MGW stack, a label 'Transcoding or Relay' has a double-headed arrow pointing to both the G.711 and AMR codecs. The MGW is connected to a 'CS Domain' cloud on the right via an interface labeled 'Nb'. + +Diagram of User Plane Interworking for BICC based CS Domain. It shows a SIP-I network on the left connected to a central MGW. The MGW has a stack of protocols: L1, L2, IP, UDP, RTP on the left side and L1, TNL, NbFP, Codec (e.g. AMR) on the right side. A 'Transcoding or Relay' label with a double-headed arrow is above the MGW stack. The MGW is connected to a CS Domain on the right via an Nb interface. + +Figure 7.2.1: User Plane Interworking for BICC based CS Domain + +# 8 Interactions between control node and MGW + +## 8.1 Overview + +ITU-T H.248.1 [11] with 3GPP specific extensions as detailed in 3GPP TS 29.332 [6] shall be applied as signalling protocol between IWU and MGW. + +The present specification describes the signalling procedures between IWU and MGW and their interaction with BICC/ISUP and SIP signalling in the control plane, and with user plane procedures. 3GPP TS 29.332 [6] maps these signalling procedures to H.248 messages and defines the required packages and parameters. + +## 8.2 Signalling interactions + +The procedures in Clause 9.2 of TS 29.163 shall be applied with modifications provided in the present Clause. + +### 8.2.1 Backward through-connection for outgoing call interworking from BICC to SIP at O-IWU. + +For the outgoing call interworking from BICC to SIP at O-IWU, the IWU shall not request the MGW to provide an awaiting answer indication (ringing tone) to the calling party, as specified in Clauses 9.2.3.1.5, 9.2.3.2.5 and 9.2.3.3.5 of 3GPP TS 29.163 [4]. The O-IWU shall instead request the MGW to backward-through connect using the "Change-IMS Through-Connection" procedure when the trigger conditions in those clauses apply. + +### 8.2.2 Handling of RTP telephone events + +The procedures in Clause 9.2.8 of 3GPP TS 29.163 [4], are applicable with the following modifications: + +It depends on the characteristics of the external SIP-I network if DTMF is transported within the codec or according to IETF RFC 4733 [28]. SIP-I transports DTMF within the RTP telephony event according to RFC 4733 [28] if the RTP telephony event payload type is negotiated between the peer SIP-I entities; alternatively, if the RTP telephony event payload has not been negotiated, SIP-I may transport the DTMF in-band ("within the codec") when the selected codec allows transparent DTMF transport. + +The control node indicates the transport mode of DTMF to the MGW as follows in the "Configure IMS Resources" procedure or "Reserve IMS Connection Point and Configure Remote Resources" procedure (signal 1 in figure 48 or figure 49 of 3GPP TS 29.163 [4]): + +- If the control node does not configure the RTP telephony event payload at the MGW, then the Detect DTMF procedure means in-band ("within the codec") detection and sending of DTMF. + +- If the control node configures the RTP telephony event payload at the MGW, then the Detect DTMF procedure means extracting and sending DTMF within the RTP payload type according to IETF RFC 4733 [28]. + +**Editor's Note:** The above reference contains sequences that require the MGW to forward partial digits to the Server. It is not yet agreed if this shall be permitted or if the MGW shall only forward complete and valid digits. + +## 8.3 Signalling procedures + +The procedures in Clause 9.3 of 3GPP TS 29.163 shall be applied with modifications provided in the present Clause. + +The support of the "Send TDM Tone", "Stop TDM Tone", "Send Tone" and "Stop Tone" procedures is optional. + +# --- Annex A (normative): Codec Negotiation between a BICC based CS Domain and an external SIP-I network + +The procedures in Annex B of TS 29.163 [4] are applicable when the IWU receives from the external SIP-I based network an SDP offer without the 3GPP\_OoBTC\_Indicator as defined in 3GPP TS 29.231 [38]. + +If the IWU receives from the external SIP-I based network a SIP request with an SDP offer containing a codec list with the 3GPP\_OoBTC\_Indicator, the IWU may apply the procedures in accordance to subclause 6.6.2 of 3GPP TS 29.235 [39]. + +When the IWU sends a SIP request with an SDP offer towards the external SIP-I based network, the IWU may include the 3GPP\_OoBTC\_Indicator in accordance to subclause 6.6.3 of 3GPP TS 29.235 [39]. + +# Annex B (informative): Change history + +| Change history | | | | | | | | +|----------------|-----------|-----------|-----|-----|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------|--------| +| Date | TSG # | TSG Doc. | CR | Rev | Subject/Comment | Old | New | +| 01/09/2006 | CT3#41 | C3-060509 | | | Agreed Skeleton of TR | | 0.0.0 | +| 15/10/2006 | | | | | Proposed update of the TR on CT3 email reflector NOT discussed or agreed by CT3, but put onto the 3GPP web server drafts folder by mistake. | 0.0.0 | 0.1.0 | +| 08/11/2006 | CT3#42 | C3-060877 | | | Includes the following TDOCs agreed by CT3:
C3-060761, C3-060667, C3-060837, C3-060763, C3-060765,
C3-060860, C3-040840, C3-040841, C3-040769, C3-060861,
C3-060847, C3-060813, C3-060678, C3-060679 | 0.0.0 | 0.2.0 | +| 22/02/2007 | CT3#43 | C3-070274 | | | Includes the following TDOCs agreed by CT3:
C3-070105, C3-070106, C3-070249, C3-070258 | 0.2.0 | 0.3.0 | +| 28/02/2007 | TSG#35 | CP-070100 | | | Editorial update by MCC for presentation to TSG CT for information | 0.3.0 | 1.0.0 | +| 19/04/2007 | CT3#43bis | | | | Includes the following TDOCs agreed by CT3:
C3-070355, C3-070373, C3-070374 | 1.0.0 | 1.1.0 | +| 15/05/2007 | CT3#44 | | | | Includes the following TDOC agreed by CT3: C3-070523 | 1.1.0 | 1.2.0 | +| 23/05/2007 | TSG#36 | CP-070427 | | | Editorial update by MCC for presentation to TSG CT for approval | 1.2.0 | 2.0.0 | +| 06/2007 | TSG#36 | CP-070427 | | | Approved to be made v7.0.0 and put under change control | 2.0.0 | 7.0.0 | +| 12/2008 | TSG#42 | | | | Upgraded to v8.0.0 due to simple upgrade without no technical change | 7.0.0 | 8.0.0 | +| 05/2009 | TSG#44 | CP-090350 | 001 | 2 | Codec negotiation when interworking with BICC based CS CN | 8.0.0 | 8.1.0 | +| 12/2009 | TSG#46 | | | | Automatic upgrade from previous Release | 8.1.0 | 9.0.0 | +| 06/2010 | TSG#48 | CP-100323 | 003 | 1 | Renumbering of duplicated subclauses | 9.0.0 | 9.1.0 | +| 10/2010 | TSG#49 | CP-100556 | 004 | | Correcting unspecific external reference | 9.1.0 | 9.2.0 | +| 03/2011 | TSG#51 | | | | Automatic upgrade from previous Release version 9.2.0 | 9.2.0 | 10.0.0 | +| 03/2011 | TSG#51 | | | | Correction of heading and numbering made by MCC | 10.0.0 | 10.0.1 | +| 09/2012 | TSG#57 | | | | Automatic upgrade from previous Release version 10.0.1 | 10.0.1 | 11.0.0 | \ No newline at end of file diff --git a/marked/Rel-11/29_series/29168/4dadfd8b8240e9d83f974e3f0fdd18df_img.jpg b/marked/Rel-11/29_series/29168/4dadfd8b8240e9d83f974e3f0fdd18df_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ef1bc04aa3e2d8f80da45e277464300174a30895 --- /dev/null +++ b/marked/Rel-11/29_series/29168/4dadfd8b8240e9d83f974e3f0fdd18df_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:98619a8ace17abf0314f7633da437524cc6216117d11a730d3b697083bd4c14b +size 20034 diff --git a/marked/Rel-11/29_series/29168/5a24ac755b962fd5f0183f13de0726de_img.jpg b/marked/Rel-11/29_series/29168/5a24ac755b962fd5f0183f13de0726de_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c999baef330f25e271c13a73513f87f31153363d --- /dev/null +++ b/marked/Rel-11/29_series/29168/5a24ac755b962fd5f0183f13de0726de_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:52671e83e3883ad2d5d7aba42e1ec1292ec4e9f77ebcea615d708e0eeff5e716 +size 23876 diff --git a/marked/Rel-11/29_series/29168/84e5b251aa38db522f76f5cc3afcb853_img.jpg b/marked/Rel-11/29_series/29168/84e5b251aa38db522f76f5cc3afcb853_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6ceaad49f14871915af887786e2dec27c043c8df --- /dev/null +++ b/marked/Rel-11/29_series/29168/84e5b251aa38db522f76f5cc3afcb853_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bb8f6880a43d55be55f191abbf7bb7c5ce7d97adc0522fc097fdb58ebb305875 +size 22039 diff --git a/marked/Rel-11/29_series/29168/d26959f4514c26ca19c3d6f00da85956_img.jpg b/marked/Rel-11/29_series/29168/d26959f4514c26ca19c3d6f00da85956_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0196a98784d76c32b5494acf5390d1a2ae0e0052 --- /dev/null +++ b/marked/Rel-11/29_series/29168/d26959f4514c26ca19c3d6f00da85956_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2f01814214b38d83875bf353a69daa109d8e64aba3232222a4c1db8a023a7b36 +size 21193 diff --git a/marked/Rel-11/29_series/29168/daa4a6fa7e2ba1954258f86b4928eb32_img.jpg b/marked/Rel-11/29_series/29168/daa4a6fa7e2ba1954258f86b4928eb32_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d36a998bf9050d7c3a39195f3c65f30dff0b9157 --- /dev/null +++ b/marked/Rel-11/29_series/29168/daa4a6fa7e2ba1954258f86b4928eb32_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:35a7e9b5bff5b4e66da6cb05ea7207b9af04af39383d09728689151038e874db +size 24262 diff --git a/marked/Rel-11/29_series/29168/ec98c4d2d93f28dfc8eb9d5e5730f62d_img.jpg b/marked/Rel-11/29_series/29168/ec98c4d2d93f28dfc8eb9d5e5730f62d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7937ab7a1a3ec7e14e9e08af306de576de03e5c9 --- /dev/null +++ b/marked/Rel-11/29_series/29168/ec98c4d2d93f28dfc8eb9d5e5730f62d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9fd9457899f7c1c13a0e3241470be137a9b49f005e871ba54523f4ee795e3ae9 +size 10963 diff --git a/marked/Rel-11/29_series/29168/f14e75bd1c6e2f234db4775dbf0dbf1a_img.jpg b/marked/Rel-11/29_series/29168/f14e75bd1c6e2f234db4775dbf0dbf1a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..620c9183f64595424270328f01f3249a32fb335c --- /dev/null +++ b/marked/Rel-11/29_series/29168/f14e75bd1c6e2f234db4775dbf0dbf1a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f14a1d50c06975a99441999e439233d2d3787f52291e416525d41bcabb9a5a35 +size 10551 diff --git a/marked/Rel-11/29_series/29168/raw.md b/marked/Rel-11/29_series/29168/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..e72efe79755706b1554e9361da265d5dffeae9ed --- /dev/null +++ b/marked/Rel-11/29_series/29168/raw.md @@ -0,0 +1,1760 @@ + + + + + + +# Contents + +| | | +|------------------------------------------------------------------------|----| +| Foreword ..... | 5 | +| 1 Scope..... | 6 | +| 2 References..... | 6 | +| 3 Definitions, symbols and abbreviations..... | 7 | +| 3.1 Definitions..... | 7 | +| 3.2 Symbols..... | 7 | +| 3.3 Abbreviations ..... | 7 | +| 4 SBc description ..... | 8 | +| 4.1 Transport ..... | 8 | +| 4.1.1 General ..... | 8 | +| 4.1.2 Network layer ..... | 8 | +| 4.1.3 Transport layer..... | 8 | +| 4.1.4 Services expected from signalling transport..... | 8 | +| 4.2 SBc-AP functions ..... | 8 | +| 4.2.1 Function of SBc-AP ..... | 8 | +| 4.3 SBc-AP procedure ..... | 9 | +| 4.3.1 General ..... | 9 | +| 4.3.2 List of SBc-AP elementary procedure ..... | 9 | +| 4.3.3 Write Replace Warning Procedure ..... | 9 | +| 4.3.3.1 General ..... | 9 | +| 4.3.3.2 Successful Operation..... | 9 | +| 4.3.3.3 Unsuccessful Operation..... | 10 | +| 4.3.3A Stop Warning Procedure..... | 10 | +| 4.3.3A.1 General..... | 10 | +| 4.3.3A.2 Successful Operation ..... | 10 | +| 4.3.3A.3 Unsuccessful Operation ..... | 11 | +| 4.3.3B Error Indication ..... | 11 | +| 4.3.3B.1 General..... | 11 | +| 4.3.3B.2 Successful Operation ..... | 11 | +| 4.3.3B.3 Abnormal Conditions..... | 12 | +| 4.3.4 Message functional definition and content..... | 12 | +| 4.3.4.1 Message contents ..... | 12 | +| 4.3.4.1.1 Presence..... | 12 | +| 4.3.4.1.2 Criticality..... | 12 | +| 4.3.4.1.3 Range..... | 12 | +| 4.3.4.1.4 Assigned Criticality..... | 12 | +| 4.3.4.2 Warning Message Transmission Messages ..... | 12 | +| 4.3.4.2.1 WRITE-REPLACE WARNING REQUEST ..... | 12 | +| 4.3.4.2.2 WRITE-REPLACE WARNING RESPONSE ..... | 13 | +| 4.3.4.2.3 STOP WARNING REQUEST ..... | 13 | +| 4.3.4.2.4 STOP WARNING RESPONSE ..... | 14 | +| 4.3.4.2A Management Messages..... | 14 | +| 4.3.4.2A.1 ERROR INDICATION..... | 14 | +| 4.3.4.3 Information element definition ..... | 14 | +| 4.3.4.3.1 Message Type..... | 14 | +| 4.3.4.3.2 Cause ..... | 15 | +| 4.3.4.3.3 Criticality Diagnostics..... | 15 | +| 4.3.4.3.4 OMC ID..... | 16 | +| 4.4 Message and information element abstract syntax..... | 16 | +| 4.4.1 General ..... | 16 | +| 4.4.2 Usage of protocol extension mechanism for non-standard use ..... | 17 | +| 4.4.3 Elementary procedure definitions..... | 17 | +| 4.4.4 PDU definitions ..... | 19 | +| 4.4.5 Information element definitions ..... | 22 | +| 4.4.6 Common definitions ..... | 25 | +| 4.4.7 Constant definitions..... | 25 | + +| | | | +|------------------------|----------------------------------------------------------------------------------------------------|----| +| 4.4.8 | Container Definitions ..... | 26 | +| 4.4.9 | Message transfer syntax..... | 29 | +| 4.5 | Handling of unknown, unforeseen or erroneous protocol data ..... | 29 | +| 4.5.1 | General ..... | 29 | +| 4.5.2 | Transfer Syntax Error ..... | 29 | +| 4.5.3 | Abstract Syntax Error ..... | 29 | +| 4.5.3.1 | General ..... | 29 | +| 4.5.3.2 | Criticality information ..... | 30 | +| 4.5.3.3 | Presence information ..... | 30 | +| 4.5.3.4 | Not comprehended IE/IE group ..... | 31 | +| 4.5.3.4.1 | Procedure code..... | 31 | +| 4.5.3.4.2 | Type of Message ..... | 31 | +| 4.5.3.4.3 | IEs other than the Procedure Code and Type of Message ..... | 31 | +| 4.5.3.5 | Missing IE or IE group ..... | 32 | +| 4.5.3.6 | IEs or IE groups received in wrong order or with too many occurrences or erroneously present ..... | 33 | +| 4.5.4 | Logical Error ..... | 34 | +| 4.5.5 | Exceptions ..... | 34 | +| Annex A (informative): | Change history: ..... | 35 | + +# --- Foreword + +This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +# --- 1 Scope + +The present document specifies the procedures and the SBc Application Part (SBc-AP) messages used on the SBc-AP interface between the Mobility Management Entity (MME) and the Cell Broadcast Centre (CBC). + +The present document supports the following functions. + +- Warning Message Transmission function in the EPS. + +# --- 2 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. +- For a specific reference, subsequent revisions do not apply. +- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. + +- [1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications". +- [2] IETF RFC 2460 (December 1998): "Internet Protocol, Version 6 (IPv6) Specification". +- [3] IETF RFC 791 (September 1981): "Internet Protocol". +- [4] IETF RFC 4960 (September 2007): "Stream Control Transmission Protocol". +- [5] Void +- [6] Void +- [7] 3GPP TS 36.413: "Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol (S1AP)" +- [8] ITU-T Recommendation X.680 (07/2002): "Information Technology - Abstract Syntax Notation One (ASN.1): Specification of basic notation". +- [9] ITU-T Recommendation X.681 (07/2002): "Information Technology - Abstract Syntax Notation One (ASN.1): Information object specification". +- [10] ITU-T Recommendation X.691 (07/2002): "Information Technology - ASN.1 encoding rules - Specification of Packed Encoding Rules (PER)". +- [11] 3GPP TS 29.002: "Mobile Application Part (MAP) specification". +- [12] Void +- [13] 3GPP TS 22.268: "Public Warning System (PWS) requirements". +- [14] 3GPP TS 23.041: "Technical realization of Cell Broadcast Service (CBS)". +- [15] Void + +# 3 Definitions, symbols and abbreviations + +## 3.1 Definitions + +For the purposes of the present document, the terms and definitions given in 3GPP TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in 3GPP TR 21.905 [1]. + +**Elementary Procedure:** SBc-AP consists of Elementary Procedures (EPs). An Elementary Procedure is a unit of interaction between MME and CBC. These Elementary Procedures are defined separately and are intended to be used to build up complete sequences in a flexible manner. If the independence between some EPs is restricted, it is described under the relevant EP description. Unless otherwise stated by the restrictions, the EPs may be invoked independently of each other as stand alone procedures, which can be active in parallel. Examples on using several SBc-APs together with each other and EPs from other interfaces can be found in reference [FFS]. + +An EP consists of an initiating message and possibly a response message. Two kinds of EPs are used: + +- **Class 1:** Elementary Procedures with response (success and/or failure). +- **Class 2:** Elementary Procedures without response. + +For Class 1 EPs, the types of responses can be as follows: + +Successful: + +- A signalling message explicitly indicates that the elementary procedure successfully completed with the receipt of the response. + +Unsuccessful: + +- A signalling message explicitly indicates that the EP failed. +- On time supervision expiry (i.e. absence of expected response). + +Successful and Unsuccessful: + +- One signalling message reports both successful and unsuccessful outcome for the different included requests. The response message used is the one defined for successful outcome. + +Class 2 EPs are considered always successful. + +## 3.2 Symbols + +For the purposes of the present document, the following symbols apply: + + + +**Editor's note:** To be completed or section removed. + +## 3.3 Abbreviations + +For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in 3GPP TR 21.905 [1]. + +| | | +|------|---------------------------------------| +| CMAS | Commercial Mobile Alert System | +| CBC | Cell Broadcast Center | +| CBS | Cell Broadcast Service | +| EPC | Evolved Packet Core | +| EPS | Evolved Packet System | +| ETWS | Earthquake and Tsunami Warning System | +| MME | Mobility Management Entity | +| PWS | Public Warning System | + +# --- 4 SBc description + +## 4.1 Transport + +### 4.1.1 General + +This subclause specifies the standards for signalling transport to be used across SBc-AP interface. SBc-AP interface is a logical interface between the MME and the CBC. All the SBc-AP messages described in the present document require an SCTP association between the MME and the CBC. + +### 4.1.2 Network layer + +The MME and the CBC shall support IPv6 (see IETF RFC 2460 [2]) and/or IPv4 (see IETF RFC 791 [3]). + +The IP layer of SBc-AP only supports point-to-point transmission for delivering SBc-AP messages. + +### 4.1.3 Transport layer + +SCTP (see IETF RFC 4960 [4]) shall be supported as the transport layer of SBc-AP messages. + +Semi-permanent SCTP associations shall be established between MME and CBC, i.e. the SCTP associations shall remain up under normal circumstances. + +Local multi-homing should be supported. Remote multi-homing shall be supported. + +Multiple local SCTP endpoints may be supported. Multiple remote SCTP endpoints shall be supported. When multiple local or remote SCTP endpoints are configured, several simultaneous SCTP associations shall be supported between MME and CBC. + +Checksum calculation for SCTP shall be supported as specified in RFC 4960 [4]. + +The CBC shall establish the SCTP association. + +The registered port number for SBc-AP is 29168. + +The registered payload protocol identifier for SBc-AP is 24. + +### 4.1.4 Services expected from signalling transport + +The signalling connection shall provide in-sequence delivery of SBc-AP messages. SBc-AP shall be notified if the signalling connection breaks. + +## 4.2 SBc-AP functions + +### 4.2.1 Function of SBc-AP + +SBc-AP has the following function: + +- Warning Message Transmission function: +This functionality provides the means to start, overwrite and stop the broadcasting of warning message in support of the Public Warning System (PWS) messages as defined in 3GPP TS 22.268 [13] which include Commercial Mobile Warning System (CMAS) and Earthquake and Tsunami (ETWS) messages. + +## 4.3 SBc-AP procedure + +### 4.3.1 General + +This sub-clause describes the parameters and detailed behaviors of different procedures. + +### 4.3.2 List of SBc-AP elementary procedure + +Table 4.3.2-1 lists the SBc-AP Elementary Procedures defined as a class 1 procedures. + +**Table 4.3.2-1: SBc-AP class 1 elementary procedures** + +| Elementary Procedure | Initiating Message | Successful Outcome | Unsuccessful Outcome | +|---------------------------------|-------------------------------|--------------------------------|----------------------| +| | | Response message | Response message | +| Write-Replace Warning procedure | WRITE-REPLACE WARNING REQUEST | WRITE-REPLACE WARNING RESPONSE | | +| Stop Warning Procedure | STOP WARNING REQUEST | STOP WARNING RESPONSE | | + +Table 4.3.2-2 lists the SBc-AP Elementary Procedures defined as a class 2 procedures. + +**Table 4.3.2-2: SBc-AP class 2 elementary procedures** + +| Elementary Procedure | Initiating Message | +|----------------------------|--------------------| +| Error Indication procedure | ERROR INDICATION | + +### 4.3.3 Write Replace Warning Procedure + +#### 4.3.3.1 General + +The purpose of Write-Replace Warning procedure is to start, overwrite the broadcasting of warning message, as defined in 3GPP TS 23.041 [14]. + +#### 4.3.3.2 Successful Operation + +![Sequence diagram showing the successful operation of the Write-Replace Warning procedure. The CBC (Cell Broadcast Center) sends a WRITE-REPLACE WARNING REQUEST message to the MME (Mobility Management Entity). The MME responds with a WRITE-REPLACE WARNING RESPONSE message. Both entities are represented by vertical lifelines with a horizontal bar at the bottom indicating their duration.](5a24ac755b962fd5f0183f13de0726de_img.jpg) + +``` + +sequenceDiagram + participant CBC + participant MME + Note left of MME: + Note right of CBC: + CBC->>MME: WRITE-REPLACE WARNING REQUEST + MME-->>CBC: WRITE-REPLACE WARNING RESPONSE + +``` + +Sequence diagram showing the successful operation of the Write-Replace Warning procedure. The CBC (Cell Broadcast Center) sends a WRITE-REPLACE WARNING REQUEST message to the MME (Mobility Management Entity). The MME responds with a WRITE-REPLACE WARNING RESPONSE message. Both entities are represented by vertical lifelines with a horizontal bar at the bottom indicating their duration. + +**Figure 4.3.3.2-1: Write-Replace Warning procedure. Successful operation.** + +The CBC initiates the procedure by sending a WRITE-REPLACE WARNING REQUEST message to the MME. + +Upon reception of WRITE-REPLACE WARNING REQUEST message, the MME shall forward the message towards the eNBs belonged to the tracking area as indicated in *List of TAIIs* IE. + +If none of *List of TAIIs* IE is present in WRITE-REPLACE WARNING REQUEST message, the MME shall forward the message towards all connected eNBs. + +The MME shall return a WRITE-REPLACE WARNING RESPONSE to the CBC immediately after the reception of the WRITE-REPLACE WARNING REQUEST message without waiting responses from eNBs. + +The MME shall set the cause IE to 'Message accepted' in the WRITE-REPLACE WARNING RESPONSE message. + +#### 4.3.3.3 Unsuccessful Operation + +![Sequence diagram for Unsuccessful Operation of Write-Replace Warning procedure.](daa4a6fa7e2ba1954258f86b4928eb32_img.jpg) + +``` +sequenceDiagram + participant MME + participant CBC + Note left of MME: + Note right of CBC: + CBC->>MME: WRITE-REPLACE WARNING REQUEST + MME-->>CBC: WRITE-REPLACE WARNING RESPONSE +``` + +The diagram shows a sequence of messages between an MME and a CBC. The MME is on the left and the CBC is on the right. The CBC sends a 'WRITE-REPLACE WARNING REQUEST' message to the MME. The MME responds with a 'WRITE-REPLACE WARNING RESPONSE' message to the CBC. Both entities have a horizontal bar at the bottom of their lifelines. + +Sequence diagram for Unsuccessful Operation of Write-Replace Warning procedure. + +**Figure 4.3.3.3-1: Write-Replace Warning procedure. Unsuccessful operation.** + +The CBC initiates the procedure by sending a WRITE-REPLACE WARNING REQUEST message to the MME. + +If MME cannot process the received WRITE-REPLACE WARNING REQUEST message, the MME shall return a WRITE-REPLACE WARNING RESPONSE message towards the CBC and the MME shall not forward the message towards the eNBs belonged to the tracking area as indicated in *List of TAIIs* IE. + +The MME shall indicate a reason of failure in the cause IE. + +### 4.3.3A Stop Warning Procedure + +#### 4.3.3A.1 General + +The purpose of Stop Warning Procedure is to stop the broadcasting of warning message. + +#### 4.3.3A.2 Successful Operation + +![Sequence diagram for Successful Operation of Stop Warning Procedure.](4dadfd8b8240e9d83f974e3f0fdd18df_img.jpg) + +``` +sequenceDiagram + participant MME + participant CBC + Note left of MME: + Note right of CBC: + CBC->>MME: STOP WARNING REQUEST + MME-->>CBC: STOP WARNING RESPONSE +``` + +The diagram shows a sequence of messages between an MME and a CBC. The MME is on the left and the CBC is on the right. The CBC sends a 'STOP WARNING REQUEST' message to the MME. The MME responds with a 'STOP WARNING RESPONSE' message to the CBC. Both entities have a horizontal bar at the bottom of their lifelines. + +Sequence diagram for Successful Operation of Stop Warning Procedure. + +**Figure 4.3.3A.2-1: Stop Warning Procedure, Successful Operation.** + +The CBC initiates the Stop Warning Procedure by sending a STOP WARNING REQUEST message to the MME. + +Upon reception of STOP WARNING REQUEST message, the MME shall forward the message towards the eNBs belonged to the tracking area as indicated in *List of TAIIs* IE. + +If none of *List of TAIIs* IE is present in STOP WARNING REQUEST message, the MME shall forward the message towards all connected eNBs. + +The MME shall return a STOP WARNING RESPONSE to the CBC immediately after the reception of the STOP WARNING REQUEST message without waiting responses from eNBs. + +The MME shall set the cause IE to 'Message accepted' in the STOP WARNING RESPONSE message. + +#### 4.3.3A.3 Unsuccessful Operation + +![Sequence diagram for Stop Warning procedure, Unsuccessful operation. The diagram shows two lifelines: MME and CBC. The CBC sends a STOP WARNING REQUEST message to the MME. The MME responds with a STOP WARNING RESPONSE message to the CBC. The MME and CBC are represented by vertical lines with horizontal bars at the bottom.](d26959f4514c26ca19c3d6f00da85956_img.jpg) + +``` +sequenceDiagram + participant MME + participant CBC + Note left of MME: + Note right of CBC: + CBC->>MME: STOP WARNING REQUEST + MME-->>CBC: STOP WARNING RESPONSE +``` + +Sequence diagram for Stop Warning procedure, Unsuccessful operation. The diagram shows two lifelines: MME and CBC. The CBC sends a STOP WARNING REQUEST message to the MME. The MME responds with a STOP WARNING RESPONSE message to the CBC. The MME and CBC are represented by vertical lines with horizontal bars at the bottom. + +**Figure 4.3.3A.3-1: Stop Warning procedure, Unsuccessful operation.** + +The CBC initiates the Stop Warning Procedure by sending a STOP WARNING REQUEST message to the MME. + +If MME cannot process the received STOP WARNING REQUEST message, the MME shall return a STOP WARNING RESPONSE message towards the CBC and the MME shall not forward the message towards the eNBs belonged to the tracking area as indicated in *List of TAs* IE. + +The MME shall indicate a reason of failure in the cause IE. + +### 4.3.3B Error Indication + +#### 4.3.3B.1 General + +The Error Indication procedure is initiated by a node to report detected errors in one incoming message, provided they cannot be reported by an appropriate failure message. + +#### 4.3.3B.2 Successful Operation + +![Sequence diagram for Error Indication procedure, CBC originated. Successful operation. The diagram shows two lifelines: MME and CBC. The CBC sends an ERROR INDICATION message to the MME. The MME and CBC are represented by vertical lines with horizontal bars at the bottom.](f14e75bd1c6e2f234db4775dbf0dbf1a_img.jpg) + +``` +sequenceDiagram + participant MME + participant CBC + Note left of MME: + Note right of CBC: + CBC->>MME: ERROR INDICATION +``` + +Sequence diagram for Error Indication procedure, CBC originated. Successful operation. The diagram shows two lifelines: MME and CBC. The CBC sends an ERROR INDICATION message to the MME. The MME and CBC are represented by vertical lines with horizontal bars at the bottom. + +**Figure 4.3.3B.2-1: Error Indication procedure, CBC originated. Successful operation.** + +![Sequence diagram for Error Indication procedure, MME originated. Successful operation. The diagram shows two lifelines: MME and CBC. The MME sends an ERROR INDICATION message to the CBC. The MME and CBC are represented by vertical lines with horizontal bars at the bottom.](ec98c4d2d93f28dfc8eb9d5e5730f62d_img.jpg) + +``` +sequenceDiagram + participant MME + participant CBC + Note left of MME: + Note right of CBC: + MME->>CBC: ERROR INDICATION +``` + +Sequence diagram for Error Indication procedure, MME originated. Successful operation. The diagram shows two lifelines: MME and CBC. The MME sends an ERROR INDICATION message to the CBC. The MME and CBC are represented by vertical lines with horizontal bars at the bottom. + +**Figure 4.3.3B.2-2: Error Indication procedure, MME originated. Successful operation.** + +When the conditions defined in subclause 4.5 are fulfilled, the Error Indication procedure is initiated by an ERROR INDICATION message sent from the receiving node. + +The ERROR INDICATION message shall contain at least either the *Cause* IE or the *Criticality Diagnostics* as indicated in subclause 4.5. + +#### 4.3.3B.3 Abnormal Conditions + +Not applicable. + +### 4.3.4 Message functional definition and content + +#### 4.3.4.1 Message contents + +##### 4.3.4.1.1 Presence + +All information elements in the message descriptions below are marked mandatory, optional or conditional according to table 4.3.4.1.1-1. + +**Table 4.3.4.1.1-1: Meaning of abbreviations used in SBc-AP messages** + +| Abbreviation | Meaning | +|--------------|------------------------------------------------------------------------------------------------------------------------------------------| +| M | IEs marked as Mandatory (M) shall always be included in the message. | +| O | IEs marked as Optional (O) may or may not be included in the message. | +| C | IEs marked as Conditional (C) shall be included in a message only if the condition is satisfied. Otherwise the IE shall not be included. | + +##### 4.3.4.1.2 Criticality + +Each Information Element or Group of Information Elements may have criticality information applied to it. Following cases are possible: + +**Table 4.3.4.1.2-1: Meaning of content within "Criticality" column** + +| Abbreviation | Meaning | +|---------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| – | No criticality information is applied explicitly. | +| YES | Criticality information is applied. This is usable only for non-repeatable IEs | +| GLOBAL | The IE and all its repetitions together have one common criticality information. This is usable only for repeatable IEs. | +| EACH | Each repetition of the IE has its own criticality information. It is not allowed to assign different criticality values to the repetitions. This is usable only for repeatable IEs. | + +##### 4.3.4.1.3 Range + +The Range column indicates the allowed number of copies of repetitive IEs/IE groups. + +##### 4.3.4.1.4 Assigned Criticality + +This column provides the actual criticality information as defined in subclause 4.5.3.2, if applicable. + +#### 4.3.4.2 Warning Message Transmission Messages + +##### 4.3.4.2.1 WRITE-REPLACE WARNING REQUEST + +This message is sent by the CBC to request start or overwrite of a warning message broadcast. + +Direction: CBC → MME + +**Table 4.3.4.2.1-1: WRITE-REPLACE WARNING REQUEST message contents** + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|--------------------------------------|----------|-------------------|-----------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 4.3.4.3.1 | | YES | reject | +| Message Identifier | M | | [7] | | YES | reject | +| Serial Number | M | | [7] | | YES | reject | +| List of TAIs | O | | | | YES | reject | +| >TAI List Item | | 1 to | | | | | +| >>TAI | M | | [7] | | | | +| Warning Area List | O | | [7] | | YES | ignore | +| Repetition Period | M | | [7] | | YES | reject | +| Extended Repetition Period | O | | [7] | | YES | reject | +| Number of Broadcast Requested | M | | [7] | | YES | reject | +| Warning Type | O | | [7] | | YES | ignore | +| Warning Security Information | O | | [7] | | YES | ignore | +| Data Coding Scheme | O | | [7] | | YES | ignore | +| Warning Message Contents | O | | [7] | | YES | ignore | +| OMC ID | O | | 4.3.4.3.4 | | YES | ignore | +| Concurrent Warning Message Indicator | O | | [7] | | YES | reject | + +**Table 4.3.4.2.1-2: RANGE explanation** + +| Range bound | Explanation | +|-------------|---------------------------------------------------------------------------| +| maxnoofTAI | Maximum no. of TAI subject for warning message broadcast. Value is 65535. | + +##### 4.3.4.2.2 WRITE-REPLACE WARNING RESPONSE + +This message is sent by the MME to acknowledge the CBC on the start or overwrite request of a warning message. + +Direction: MME → CBC + +**Table 4.3.4.2.2-1: WRITE-REPLACE WARNING RESPONSE message contents** + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|-------------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 4.3.4.3.1 | | YES | reject | +| Message Identifier | M | | [7] | | YES | reject | +| Serial Number | M | | [7] | | YES | reject | +| Cause | M | | 4.3.4.3.2 | | YES | ignore | +| Criticality Diagnostics | O | | 4.3.4.3.3 | | YES | ignore | + +##### 4.3.4.2.3 STOP WARNING REQUEST + +This message is sent by the CBC to stop a warning message broadcast. + +Direction: CBC → MME + +**Table 4.3.4.2.3-1: STOP WARNING REQUEST message contents** + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|---------------------|----------|-------------------|-----------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 4.3.4.3.1 | | YES | reject | +| Message Identifier | M | | [7] | | YES | reject | +| Serial Number | M | | [7] | | YES | reject | +| List of TAIs | O | | | | YES | reject | +| >TAI List Item | | 1 to | | | | | +| >>TAI | M | | [7] | | | | +| Warning Area List | O | | [7] | | YES | ignore | +| OMC ID | O | | 4.3.4.3.4 | | YES | ignore | + +**Table 4.3.4.2.1-2: RANGE explanation** + +| Range bound | Explanation | +|-------------|---------------------------------------------------------------------------| +| maxnoofTAI | Maximum no. of TAI subject for warning message broadcast. Value is 65535. | + +##### 4.3.4.2.4 STOP WARNING RESPONSE + +This message is sent by the MME to acknowledge the CBC on the stop request of a warning message. + +Direction: MME → CBC + +**Table 4.3.4.2.2-1: STOP WARNING RESPONSE message contents** + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|-------------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 4.3.4.3.1 | | YES | reject | +| Message Identifier | M | | [7] | | YES | reject | +| Serial Number | M | | [7] | | YES | reject | +| Cause | M | | 4.3.4.3.2 | | YES | ignore | +| Criticality Diagnostics | O | | 4.3.4.3.3 | | YES | ignore | + +#### 4.3.4.2A Management Messages + +##### 4.3.4.2A.1 ERROR INDICATION + +This message is sent by both the MME and the CBC and is used to indicate that some error has been detected in the node. + +Direction : MME → CBC and CBC → MME + +**Table 4.3.4.2A.1-1: ERROR INDICATION message contents** + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|-------------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 4.3.4.3.1 | | YES | ignore | +| Cause | O | | 4.3.4.3.2 | | YES | ignore | +| Criticality Diagnostics | O | | 4.3.4.3.3 | | YES | ignore | + +#### 4.3.4.3 Information element definition + +##### 4.3.4.3.1 Message Type + +The *Message Type* IE uniquely identifies the message being sent. It is mandatory for all messages + +**Table 4.3.4.3.1-1: Message Type information element** + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------------|----------|-------|----------------------------------------------------------------------------------------|------------------------------------| +| Message Type | | | | Assumed max no of messages is 256. | +| >Procedure Code | M | | (Write-Replace
Warning, Stop
Warning ...) | | +| >Type of Message | M | | CHOICE
(Initiating Message,
Successful Outcome,
Unsuccessful Outcome,
...) | | + +##### 4.3.4.3.2 Cause + +The purpose of the *Cause* IE is to indicate the reason for a particular event for the SBc-AP protocol. + +**Table 4.3.4.3.2-1: Cause information element** + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|---------------|----------|-------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------| +| Cause | M | | INTEGER (Message accepted,
Parameter not recognised, Parameter
value invalid, Valid message not
identified, Tracking area not valid,
Unrecognised message, Missing
mandatory element, MME capacity
exceeded, MME memory exceeded,
Warning broadcast not supported,
Warning broadcast not operational,
Message reference already used,
Unspecified error, Transfer syntax
error, Semantic error, Message not
compatible with receiver state,
Abstract syntax error reject, Abstract
syntax error ignore and notify,
Abstract syntax error falsely
constructed message, ...) | | + +##### 4.3.4.3.3 Criticality Diagnostics + +The *Criticality Diagnostics* IE is sent by the MME when parts of a received message have not been comprehended or were missing, or if the message contained logical errors. When applicable, it contains information about which IEs were not comprehended or were missing. + +**Table 4.3.4.3.3-1: Criticality Diagnostics information element** + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|----------------------------------------------------|----------|-----------------------|------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Procedure Code | O | | INTEGER (0..255) | Procedure Code is to be used if Criticality Diagnostics is part of Error Indication procedure, and not within the response message of the same procedure that caused the error | +| Triggering Message | O | | ENUMERATED( initiating message, successful outcome, unsuccessful outcome, outcome) | The Triggering Message is used only if the Criticality Diagnostics is part of Error Indication procedure. | +| Procedure Criticality | O | | ENUMERATED( reject, ignore, notify) | This Procedure Criticality is used for reporting the Criticality of the Triggering message (Procedure). | +| Information Element Criticality Diagnostics | | 0 to | | | +| >IE Criticality | M | | ENUMERATED( reject, ignore, notify) | The IE Criticality is used for reporting the criticality of the triggering IE. The value 'ignore' shall not be used. | +| >IE ID | M | | INTEGER (0..65535) | The IE ID of the not understood or missing IE | +| | | | | | +| >Type of Error | M | | ENUMERATED( not understood, missing, ...) | | + +**Table 4.3.4.3.3-2: RANGE explanation** + +| Range bound | Explanation | +|---------------|------------------------------------------------------------------------------------------------------------| +| maxnooferrors | Maximum no. of IE errors allowed to be reported with a single message. The value for maxnooferrors is 256. | + +##### 4.3.4.3.4 OMC ID + +The OMC ID IE indicates the identity of an Operation and Maintenance Centre to which Trace records shall be sent. + +**Table 4.3.4.3.4-1: OMC ID information element** + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|---------------|----------|-------|-----------------------------------------------------------------------------------|-----------------------| +| OMC ID | O | | OCTET STRING (SIZE (1..20))
Octets are coded according to 3GPP TS 29.002 [11]. | | + +## 4.4 Message and information element abstract syntax + +### 4.4.1 General + +SBC-AP ASN.1 definition conforms with [8] and [9]. + +The ASN.1 definition specifies the structure and content of SBC-AP messages. SBC-AP messages can contain any IEs specified in the object set definitions for that message without the order or number of occurrence being restricted by ASN.1. However, for this version of the standard, a sending entity shall construct a SBC-AP message according to the PDU definitions module and with the following additional rules (Note that in the following IE means an IE in the object set with an explicit id. If one IE needed to appear more than once in one object set, then the different occurrences have different IE ids): + +- IEs shall be ordered (in an IE container) in the order they appear in object set definitions. +- Object set definitions specify how many times IEs may appear. An IE shall appear exactly once if the presence field in an object has value "mandatory". An IE may appear at most once if the presence field in an object has value "optional" or "conditional". If in a tabular format there is multiplicity specified for an IE (i.e. an IE list) then in the corresponding ASN.1 definition the list definition is separated into two parts. The first part defines an IE container list where the list elements reside. The second part defines list elements. The IE container list appears as an IE of its own. For this version of the standard an IE container list may contain only one kind of list elements. + +If a SBC-AP message that is not constructed as defined above is received, this shall be considered as Abstract Syntax Error, and the message shall be handled as defined for Abstract Syntax error in subclause 4.5.3.6. + +### 4.4.2 Usage of protocol extension mechanism for non-standard use + +The protocol extension mechanism for non-standard use may be used: + +- for special operator- (and/or vendor) specific features considered not to be part of the basic functionality, i.e. the functionality required for a complete and high-quality specification in order to guarantee multivendor interoperability. +- by vendors for research purposes, e.g. to implement and evaluate new algorithms/features before such features are proposed for standardisation. + +The extension mechanism shall not be used for basic functionality. Such functionality shall be standardised. + +### 4.4.3 Elementary procedure definitions + +``` + +-- ***** +-- +-- Elementary Procedure definitions +-- +-- ***** + +SBC-AP-PDU-Descriptions { + itu-t (0) identified-organization (4) etsi (0) mobileDomain (0) + eps-Access (21) modules (3) sbc-AP (3) version1 (1) sbc-AP-PDU-Descriptions (0)} + +DEFINITIONS AUTOMATIC TAGS ::= + +BEGIN + +-- ***** +-- +-- IE parameter types from other modules. +-- +-- ***** + +IMPORTS + Criticality, + ProcedureCode +FROM SBC-AP-CommonDataTypes + + Write-Replace-Warning-Request, + Write-Replace-Warning-Response, + Stop-Warning-Request, + Stop-Warning-Response, + Error-Indication + +FROM SBC-AP-PDU-Contents + + id-Write-Replace-Warning, + id-Stop-Warning, + id-Error-Indication + +``` + +``` + +FROM SBC-AP-Constants; + +-- ***** +-- +-- Interface Elementary Procedure Class +-- +-- ***** + +SBC-AP-ELEMENTARY-PROCEDURE ::= CLASS { + &InitiatingMessage , + &SuccessfulOutcome OPTIONAL, + &UnsuccessfulOutcome OPTIONAL, + &procedureCode ProcedureCode UNIQUE, + &criticality Criticality DEFAULT ignore +} +WITH SYNTAX { + INITIATING MESSAGE &InitiatingMessage + [SUCCESSFUL OUTCOME &SuccessfulOutcome] + [UNSUCCESSFUL OUTCOME &UnsuccessfulOutcome] + PROCEDURE CODE &procedureCode + [CRITICALITY &criticality] +} + +-- ***** +-- +-- Interface PDU Definition +-- +-- ***** + +SBC-AP-PDU ::= CHOICE { + initiatingMessage InitiatingMessage, + successfulOutcome SuccessfulOutcome, + unsuccessfulOutcome UnsuccessfulOutcome, + ... +} + +InitiatingMessage ::= SEQUENCE { + procedureCode SBC-AP-ELEMENTARY-PROCEDURE.&procedureCode ({SBC-AP-ELEMENTARY-PROCEDURES}), + criticality SBC-AP-ELEMENTARY-PROCEDURE.&criticality ({SBC-AP-ELEMENTARY-PROCEDURES}{@procedureCode}), + value SBC-AP-ELEMENTARY-PROCEDURE.&InitiatingMessage ({SBC-AP-ELEMENTARY-PROCEDURES}{@procedureCode}) +} + +SuccessfulOutcome ::= SEQUENCE { + procedureCode SBC-AP-ELEMENTARY-PROCEDURE.&procedureCode ({SBC-AP-ELEMENTARY-PROCEDURES}), + criticality SBC-AP-ELEMENTARY-PROCEDURE.&criticality ({SBC-AP-ELEMENTARY-PROCEDURES}{@procedureCode}), + value SBC-AP-ELEMENTARY-PROCEDURE.&SuccessfulOutcome ({SBC-AP-ELEMENTARY-PROCEDURES}{@procedureCode}) +} + +UnsuccessfulOutcome ::= SEQUENCE { + procedureCode SBC-AP-ELEMENTARY-PROCEDURE.&procedureCode ({SBC-AP-ELEMENTARY-PROCEDURES}), + criticality SBC-AP-ELEMENTARY-PROCEDURE.&criticality ({SBC-AP-ELEMENTARY-PROCEDURES}{@procedureCode}), + value SBC-AP-ELEMENTARY-PROCEDURE.&UnsuccessfulOutcome ({SBC-AP-ELEMENTARY-PROCEDURES}{@procedureCode}) +} + +-- ***** +-- +-- Interface Elementary Procedure List +-- +-- ***** + +SBC-AP-ELEMENTARY-PROCEDURES SBC-AP-ELEMENTARY-PROCEDURE ::= { + SBC-AP-ELEMENTARY-PROCEDURES-CLASS-1 | + SBC-AP-ELEMENTARY-PROCEDURES-CLASS-2 , + ... +} + +SBC-AP-ELEMENTARY-PROCEDURES-CLASS-1 SBC-AP-ELEMENTARY-PROCEDURE ::= { + write-Replace-Warning | + stop-Warning , + ... +} + +``` + +``` + +SBC-AP-ELEMENTARY-PROCEDURES-CLASS-2 SBC-AP-ELEMENTARY-PROCEDURE ::= { + error-Indication , + ... +} + +write-Replace-Warning SBC-AP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE Write-Replace-Warning-Request + SUCCESSFUL OUTCOME Write-Replace-Warning-Response + + PROCEDURE CODE id-Write-Replace-Warning + CRITICALITY reject +} + +stop-Warning SBC-AP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE Stop-Warning-Request + SUCCESSFUL OUTCOME Stop-Warning-Response + + PROCEDURE CODE id-Stop-Warning + CRITICALITY reject +} + +error-Indication SBC-AP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE Error-Indication + PROCEDURE CODE id-Error-Indication + CRITICALITY ignore +} +END + +``` + +### 4.4.4 PDU definitions + +``` + +-- ************************************************************** +-- +-- PDU definitions for SBC-AP. +-- +-- ************************************************************** + +SBC-AP-PDU-Contents { +itu-t (0) identified-organization (4) etsi (0) mobileDomain (0) +eps-Access (21) modules (3) sbc-AP (3) version1 (1) sbc-AP-PDU-Contents (1)} + +DEFINITIONS AUTOMATIC TAGS ::= + +BEGIN + +-- ************************************************************** +-- +-- IE parameter types from other modules. +-- +-- ************************************************************** + +IMPORTS + + Cause, + Concurrent-Warning-Message-Indicator, + Criticality-Diagnostics, + Data-Coding-Scheme, + Message-Identifier, + Serial-Number, + List-of-TAIs, + Warning-Area-List, + Omc-Id, + Repetition-Period, + Extended-Repetition-Period, + Number-of-Broadcasts-Requested, + Warning-Type, + Warning-Security-Information, + Warning-Message-Content +FROM SBC-AP-IEs + + ProtocolExtensionContainer{}, + ProtocolIE-Container{}, + SBC-AP-PROTOCOL-EXTENSION, + SBC-AP-PROTOCOL-IES +FROM SBC-AP-Containers + + id-Concurrent-Warning-Message-Indicator, + id-Criticality-Diagnostics, + +``` + +``` + + id-Cause, + id-Data-Coding-Scheme, + id-List-of-TAIs, + id-Message-Identifier, + id-Serial-Number, + id-Number-of-Broadcasts-Requested, + id-Omc-Id, + id-Radio-Resource-Loading-List, + id-Recovery-Indication, + id-Repetition-Period, + id-Extended-Repetition-Period, + id-Warning-Area-List, + id-Warning-Message-Content, + id-Warning-Security-Information, + id-Warning-Type +FROM SBC-AP-Constants; + +-- ************************************************************** +-- +-- Write-Replace-Warning-Request +-- +-- ************************************************************** + +Write-Replace-Warning-Request ::= SEQUENCE { + protocolIEs ProtocolIE-Container { {Write-Replace-Warning-Request-IEs} }, + protocolExtensions ProtocolExtensionContainer { {Write-Replace-Warning-Request-Extensions} } +} OPTIONAL, + ... +} + +Write-Replace-Warning-Request-IEs SBC-AP-PROTOCOL-IES ::= { + { ID id-Message-Identifier CRITICALITY reject TYPE Message-Identifier PRESENCE mandatory } +| + { ID id-Serial-Number CRITICALITY reject TYPE Serial-Number PRESENCE mandatory } | + { ID id-List-of-TAIs CRITICALITY reject TYPE List-of-TAIs PRESENCE optional } | + { ID id-Warning-Area-List CRITICALITY ignore TYPE Warning-Area-List PRESENCE optional } +| + { ID id-Repetition-Period CRITICALITY reject TYPE Repetition-Period PRESENCE mandatory } +| + { ID id-Extended-Repetition-Period CRITICALITY reject TYPE Extended-Repetition-Period + PRESENCE optional } | + + { ID id-Number-of-Broadcasts-Requested + CRITICALITY reject TYPE Number-of-Broadcasts-Requested PRESENCE mandatory } | + { ID id-Warning-Type CRITICALITY ignore TYPE Warning-Type PRESENCE optional } | + { ID id-Warning-Security-Information CRITICALITY ignore TYPE Warning-Security- +Information PRESENCE optional } | + { ID id-Data-Coding-Scheme CRITICALITY ignore TYPE Data-Coding-Scheme PRESENCE optional } +| + { ID id-Warning-Message-Content + CRITICALITY ignore TYPE Warning-Message-Content PRESENCE optional } | + { ID id-Omc-Id CRITICALITY ignore TYPE Omc-Id PRESENCE optional } | + { ID id-Concurrent-Warning-Message-Indicator CRITICALITY reject TYPE Concurrent-Warning- +Message-Indicator PRESENCE optional }, + ... +} + +Write-Replace-Warning-Request-Extensions SBC-AP-PROTOCOL-EXTENSION ::= { + ... +} + +-- ************************************************************** +-- +-- Write-Replace-Warning-Response +-- +-- ************************************************************** + +Write-Replace-Warning-Response ::= SEQUENCE { + protocolIEs ProtocolIE-Container { {Write-Replace-Warning-Response-IEs} }, + protocolExtensions ProtocolExtensionContainer { {Write-Replace-Warning-Response-Extensions} } +} OPTIONAL, + ... +} + +Write-Replace-Warning-Response-IEs SBC-AP-PROTOCOL-IES ::= { + { ID id-Message-Identifier CRITICALITY reject TYPE Message-Identifier PRESENCE mandatory } +| + { ID id-Serial-Number CRITICALITY reject TYPE Serial-Number PRESENCE mandatory } | + +``` + +``` + + { ID id-Cause CRITICALITY ignore TYPE Cause PRESENCE mandatory } + | + { ID id-Criticality-Diagnostics CRITICALITY ignore TYPE Criticality-Diagnostics PRESENCE +optional }, + ... +} + +Write-Replace-Warning-Response-Extensions SBC-AP-PROTOCOL-EXTENSION ::= { + ... +} + +-- ***** +-- +-- Stop-Warning-Request +-- +-- ***** + +Stop-Warning-Request ::= SEQUENCE { + protocolIEs ProtocolIE-Container { {Stop-Warning-Request-IEs} }, + protocolExtensions ProtocolExtensionContainer { {Stop-Warning-Request-Extensions} } +OPTIONAL, + ... +} + +Stop-Warning-Request-IEs SBC-AP-PROTOCOL-IES ::= { + { ID id-Message-Identifier CRITICALITY reject TYPE Message-Identifier PRESENCE mandatory } +| + { ID id-Serial-Number CRITICALITY reject TYPE Serial-Number PRESENCE mandatory } | + { ID id-List-of-TAIs CRITICALITY reject TYPE List-of-TAIs PRESENCE optional } | + { ID id-Warning-Area-List CRITICALITY ignore TYPE Warning-Area-List PRESENCE optional } | + { ID id-Omc-Id CRITICALITY ignore TYPE Omc-Id PRESENCE optional }, + ... +} + +Stop-Warning-Request-Extensions SBC-AP-PROTOCOL-EXTENSION ::= { + ... +} + +-- ***** +-- +-- Stop-Warning-Response +-- +-- ***** + +Stop-Warning-Response ::= SEQUENCE { + protocolIEs ProtocolIE-Container { {Stop-Warning-Response-IEs} }, + protocolExtensions ProtocolExtensionContainer { {Stop-Warning-Response-Extensions} } +OPTIONAL, + ... +} + +Stop-Warning-Response-IEs SBC-AP-PROTOCOL-IES ::= { + { ID id-Message-Identifier CRITICALITY reject TYPE Message-Identifier PRESENCE mandatory } +| + { ID id-Serial-Number CRITICALITY reject TYPE Serial-Number PRESENCE mandatory } | + { ID id-Cause CRITICALITY ignore TYPE Cause PRESENCE mandatory } +| + { ID id-Criticality-Diagnostics CRITICALITY ignore TYPE Criticality-Diagnostics PRESENCE +optional }, + ... +} + +Stop-Warning-Response-Extensions SBC-AP-PROTOCOL-EXTENSION ::= { + ... +} + +-- ***** +-- +-- ERROR INDICATION ELEMENTARY PROCEDURE +-- +-- ***** + +-- ***** +-- +-- Error Indication +-- +-- ***** + +``` + +``` + +Error-Indication ::= SEQUENCE { + protocolIEs ProtocolIE-Container {{ErrorIndicationIEs}}, + ... +} + +ErrorIndicationIEs SBC-AP-PROTOCOL-IES ::= { + { ID id-Cause CRITICALITY ignore TYPE Cause PRESENCE +optional } | + { ID id-Criticality-Diagnostics CRITICALITY ignore TYPE Criticality-Diagnostics +PRESENCE optional } , + ... +} + +END + +``` + +### 4.4.5 Information element definitions + +``` + +-- ***** +-- +-- Information Element Definitions +-- +-- ***** + +SBC-AP-IEs { + itu-t (0) identified-organization (4) etsi (0) mobileDomain (0) + eps-Access (21) modules (3) sbc-AP (3) version1 (1) sbc-AP-IEs (2)} + +DEFINITIONS AUTOMATIC TAGS ::= + +BEGIN + +IMPORTS + maxNrOfErrors, + maxNrOfTAIs, + maxnoofTAIforWarning, + maxnoofCellID, + maxnoofEmergencyAreaID, + + id-TypeOfError + +FROM SBC-AP-Constants + + Criticality, + ProcedureCode, + TriggeringMessage, + ProtocolIE-ID + +FROM SBC-AP-CommonDataTypes + + ProtocolExtensionContainer{}, + + SBC-AP-PROTOCOL-EXTENSION + +FROM SBC-AP-Containers; + +-- A + +-- B + +-- C + +Cause ::= INTEGER { + message-accepted (0), + parameter-not-recognised (1), + parameter-value-invalid (2), + valid-message-not-identified (3), + tracking-area-not-valid (4), + unrecognised-message (5), + missing-mandatory-element (6), + mME-capacity-exceeded (7), + mME-memory-exceeded (8), + warning-broadcast-not-supported (9), + warning-broadcast-not-operational (10), + message-reference-already-used (11), + unspecified-error (12), +} + +``` + +``` + + transfer-syntax-error (13), + semantic-error (14), + message-not-compatible-with-receiver-state (15), + abstract-syntax-error-reject (16), + abstract-syntax-error-ignore-and-notify (17), + abstract-syntax-error-falsely-constructed-message (18) + } (0..255) + +CellIdentity ::= BIT STRING (SIZE (28)) + +Concurrent-Warning-Message-Indicator ::= ENUMERATED {true} + +Criticality-Diagnostics ::= SEQUENCE { + procedureCode ProcedureCode OPTIONAL, + triggeringMessage TriggeringMessage OPTIONAL, + procedureCriticality Criticality OPTIONAL, + iE-CriticalityDiagnostics CriticalityDiagnostics-IE-List OPTIONAL, + iE-Extensions ProtocolExtensionContainer { {CriticalityDiagnostics-ExtIEs} } OPTIONAL, + ... +} + +CriticalityDiagnostics-ExtIEs SBC-AP-PROTOCOL-EXTENSION ::= { + ... +} + +CriticalityDiagnostics-IE-List ::= SEQUENCE (SIZE (1..maxNrOfErrors)) OF + SEQUENCE { + iECriticality Criticality, + iE-ID ProtocolIE-ID, + typeOfError TypeOfError, + iE-Extensions ProtocolExtensionContainer { {CriticalityDiagnostics-IE-Item-ExtIEs} } + OPTIONAL, + ... +} + +CriticalityDiagnostics-IE-Item-ExtIEs SBC-AP-PROTOCOL-EXTENSION ::= { + ... +} + +-- D + +Data-Coding-Scheme ::= BIT STRING (SIZE (8)) + +-- E + +ECGIList ::= SEQUENCE (SIZE(1..maxnoofCellID)) OF EUTRAN-CGI + +Emergency-Area-ID-List ::= SEQUENCE (SIZE(1..maxnoofEmergencyAreaID)) OF Emergency-Area-ID + +Emergency-Area-ID ::= OCTET STRING (SIZE (3)) + +EUTRAN-CGI ::= SEQUENCE { + pLMNIdentity PLMNIdentity, + cell-ID CellIdentity, + iE-Extensions ProtocolExtensionContainer { {EUTRAN-CGI-ExtIEs} } OPTIONAL, + ... +} + +EUTRAN-CGI-ExtIEs SBC-AP-PROTOCOL-EXTENSION ::= { + ... +} + +Extended-Repetition-Period ::= INTEGER (4096..131071) + +-- F + +-- G + +-- H + +-- I + +-- J + +``` + +``` + +-- K + +-- L + +List-of-TAIs ::= SEQUENCE (SIZE (1..maxNrOfTAIs)) OF + SEQUENCE { + tai TAI + } + +-- M + +Message-Identifier ::= BIT STRING (SIZE (16)) + +-- N + +Number-of-Broadcasts-Requested ::= INTEGER (0..65535) + +-- For Number-of-Broadcasts-Requested = 0 and Repetition-Period = 0, then eNB action is no broadcast +-- for ETWS Secondary and CMAS. +-- +-- For Number-of-Broadcasts-Requested = 1 and Repetition-Period = 0, then eNB action is broadcast +-- only once for ETWS and CMAS. +-- +-- For Number-of-Broadcasts-Requested = 0 and Repetition-Period > 0, then eNB action is no broadcast +-- for the ETWS Secondary, and broadcast until further notice for the CMAS. +-- +-- For Number-of-Broadcasts-Requested > 0 and Repetition-Period > 0, then eNB action is normal +-- broadcast. +-- All other combinations of Number-of-Broadcasts-Requested and Repetition-Period are considered +-- invalid. + +-- O +Omc-Id ::= OCTET STRING (SIZE (1..20)) + +-- P +PLMNIdentity ::= TBCD-STRING + +-- Q + +-- R + +Repetition-Period ::= INTEGER (0..4096) +-- 1 to 4096: Each unit represents a repetition of one second to a maximum of +-- once per 4096 seconds (~1 hour). +-- 0: no repetition +-- A CBC compliant to this version or later of this specification shall not send a repetition period +-- greater than 4095. +-- For backwards compatibility with a CBC compliant to an earlier version of this specification the +-- maximum value of the repetition period defined in ASN.1 remains at 4096. +-- If the value of the Repetition Period IE received in the WRITE-REPLACE WARNING REQUEST message is +-- set to 4096, the MME shall set the Repetition Period IE to the maximum value 4095 supported on +-- the S1-MME interface as defined in [7] before forwarding to the selected eNBs. +-- S + +Serial-Number ::= BIT STRING (SIZE (16)) + +-- T + +TAC ::= OCTET STRING (SIZE (2)) + +TAI-List-for-Warning ::= SEQUENCE (SIZE(1.. maxnoofTAIforWarning)) OF TAI + +TAI ::= SEQUENCE { + pLMNIdentity PLMNIdentity, + tAC TAC, + iE-Extensions ProtocolExtensionContainer { {TAI-ExtIEs} } OPTIONAL +} + +TAI-ExtIEs SBC-AP-PROTOCOL-EXTENSION ::= { + ... +} + +TBCD-STRING ::= OCTET STRING (SIZE (3)) + +TypeOfError ::= ENUMERATED { + not-understood, + missing, +} + +``` + +``` + + ... + } + + -- U + + -- V + + -- W + + Warning-Area-List ::= CHOICE { + cell-ID-List ECGIList, + tracking-Area-List-for-Warning TAI-List-for-Warning, + emergency-Area-ID-List Emergency-Area-ID-List, + ... + } + + Warning-Message-Content ::= OCTET STRING (SIZE (1..9600)) + Warning-Security-Information ::= OCTET STRING (SIZE (50)) + Warning-Type ::= OCTET STRING (SIZE (2)) + + -- X + + -- Y + +END + +``` + +### 4.4.6 Common definitions + +``` + +-- ************************************************************** +-- +-- Common definitions +-- +-- ************************************************************** + +SBC-AP-CommonDataTypes { +itu-t (0) identified-organization (4) etsi (0) mobileDomain (0) +eps-Access (21) modules (3) sbc-AP (3) version1 (1) sbc-AP-CommonDataTypes (3)} + +DEFINITIONS AUTOMATIC TAGS ::= + +BEGIN + +Criticality ::= ENUMERATED { reject, ignore, notify } + +Presence ::= ENUMERATED { optional, conditional, mandatory } + +ProcedureCode ::= INTEGER (0..255) + +ProtocolExtensionID ::= INTEGER (0..65535) + +ProtocolIE-ID ::= INTEGER (0..65535) + +TriggeringMessage ::= ENUMERATED {initiating-message, successful-outcome, unsuccessful- +outcome, outcome} + +END + +``` + +### 4.4.7 Constant definitions + +``` + +-- ************************************************************** +-- +-- Constant definitions +-- +-- ************************************************************** + +SBC-AP-Constants { +itu-t (0) identified-organization (4) etsi (0) mobileDomain (0) +eps-Access (21) modules (3) sbc-AP (3) version1 (1) sbc-AP-Constants (4)} + +DEFINITIONS AUTOMATIC TAGS ::= + +BEGIN + +-- ************************************************************** +-- +-- Elementary Procedures + +``` + +``` + +-- +-- ***** + +id-Write-Replace-Warning INTEGER := 0 +id-Stop-Warning INTEGER := 1 +id-Error-Indication INTEGER := 2 + +-- +-- ***** +-- +-- IEs +-- +-- ***** + +id-Broadcast-Message-Content INTEGER := 0 +id-Cause INTEGER := 1 +id-Criticality-Diagnostics INTEGER := 2 +id-Data-Coding-Scheme INTEGER := 3 +id-Failure-List INTEGER := 4 +id-Message-Identifier INTEGER := 5 +id-Number-of-Broadcasts-Completed-List INTEGER := 6 +id-Number-of-Broadcasts-Requested INTEGER := 7 +id-Radio-Resource-Loading-List INTEGER := 8 +id-Recovery-Indication INTEGER := 9 +id-Repetition-Period INTEGER := 10 +id-Serial-Number INTEGER := 11 +id-Service-Areas-List INTEGER := 12 +id-TypeOfError INTEGER := 13 +id-List-of-TAIs INTEGER := 14 +id-Warning-Area-List INTEGER := 15 +id-Warning-Message-Content INTEGER := 16 +id-Warning-Security-Information INTEGER := 17 +id-Warning-Type INTEGER := 18 +id-Omc-Id INTEGER := 19 +id-Concurrent-Warning-Message-Indicator INTEGER := 20 +id-Extended-Repetition-Period INTEGER := 21 + +-- ***** +-- +-- Extension constants +-- +-- ***** + +-- ***** +-- +-- Lists +-- +-- ***** + +maxNrOfErrors INTEGER := 256 +maxnoofCellID INTEGER := 65535 +maxNrOfTAIs INTEGER := 65535 +maxnoofEmergencyAreaID INTEGER := 65535 +maxnoofTAIForWarning INTEGER := 65535 + +maxProtocolExtensions INTEGER := 65535 +maxProtocolIEs INTEGER := 65535 + +END + +``` + +### 4.4.8 Container Definitions + +``` + +-- ***** +-- +-- Container definitions +-- +-- ***** + +SBC-AP-Containers { + itu-t (0) identified-organization (4) etsi (0) mobileDomain (0) + eps-Access (21) modules (3) sbc-AP (3) version1 (1) sbc-AP-Containers (5)} + +DEFINITIONS AUTOMATIC TAGS := + +BEGIN + +``` + +``` + +-- ***** +-- +-- IE parameter types from other modules. +-- +-- ***** + +IMPORTS + Criticality, + Presence, + ProtocolExtensionID, + ProtocolIE-ID +FROM SBC-AP-CommonDataTypes + + maxProtocolExtensions, + maxProtocolIEs +FROM SBC-AP-Constants; + +-- ***** +-- +-- Class Definition for Protocol IEs +-- +-- ***** + +SBC-AP-PROTOCOL-IES ::= CLASS { + &id ProtocolIE-ID UNIQUE, + &criticality Criticality DEFAULT ignore, + &Value, + &presence Presence +} +WITH SYNTAX { + ID &id + CRITICALITY &criticality + TYPE &Value + PRESENCE &presence +} + +-- ***** +-- +-- Class Definition for Protocol Extensions +-- +-- ***** + +SBC-AP-PROTOCOL-EXTENSION ::= CLASS { + &id ProtocolExtensionID UNIQUE, + &criticality Criticality DEFAULT ignore, + &Extension, + &presence Presence +} +WITH SYNTAX { + ID &id + CRITICALITY &criticality + EXTENSION &Extension + PRESENCE &presence +} + +-- ***** +-- +-- Container for Protocol IEs +-- +-- ***** + +ProtocolIE-Container {SBC-AP-PROTOCOL-IES : IEsSetParam} ::= + SEQUENCE (SIZE (0..maxProtocolIEs)) OF + ProtocolIE-Field {{IEsSetParam}} + +ProtocolIE-Field {SBC-AP-PROTOCOL-IES : IEsSetParam} ::= SEQUENCE { + id SBC-AP-PROTOCOL-IES.&id {{IEsSetParam}}, + criticality SBC-AP-PROTOCOL-IES.&criticality {{IEsSetParam}{@id}}, + value SBC-AP-PROTOCOL-IES.&Value {{IEsSetParam}{@id}} +} + +-- ***** +-- +-- Container Lists for Protocol IE Containers +-- +-- ***** + +``` + +``` +ProtocolIE-ContainerList {INTEGER : lowerBound, INTEGER : upperBound, SBC-AP-PROTOCOL-IES : +IEsSetParam} ::= + SEQUENCE (SIZE (lowerBound..upperBound)) OF + ProtocolIE-Container {{IEsSetParam}} + +-- ***** +-- +-- Container for Protocol Extensions +-- +-- ***** + +ProtocolExtensionContainer {SBC-AP-PROTOCOL-EXTENSION : ExtensionSetParam} ::= + SEQUENCE (SIZE (1..maxProtocolExtensions)) OF + ProtocolExtensionField {{ExtensionSetParam}} + +ProtocolExtensionField {SBC-AP-PROTOCOL-EXTENSION : ExtensionSetParam} ::= SEQUENCE { + id SBC-AP-PROTOCOL-EXTENSION.&id ({ExtensionSetParam}), + criticality SBC-AP-PROTOCOL-EXTENSION.&criticality ({ExtensionSetParam}{@id}), + extensionValue SBC-AP-PROTOCOL-EXTENSION.&Extension ({ExtensionSetParam}{@id}) +} + +END +``` + +### 4.4.9 Message transfer syntax + +SBc-AP shall use the ASN.1 Basic Packed Encoding Rules (BASIC-PER) Aligned Variant as transfer syntax as specified in ref. [10]. + +## 4.5 Handling of unknown, unforeseen or erroneous protocol data + +### 4.5.1 General + +Protocol Error cases can be divided into three classes: + +- Transfer Syntax Error; +- Abstract Syntax Error; +- Logical Error. + +Protocol errors can occur in the following functions within a receiving node: + +![Diagram illustrating Protocol Errors in SBc-AP. It shows two boxes: 'SBc-AP functional entity' at the top and 'ASN.1 Decoding' at the bottom, connected by a double-headed arrow. To the right of the top box, a bracket groups 'Logical Errors' and 'Abstract Syntax Errors'. To the right of the bottom box, a bracket groups 'Transfer Syntax Errors'. A large vertical arrow on the far right points upwards, indicating the flow of error reporting from the decoding layer to the functional entity.](84e5b251aa38db522f76f5cc3afcb853_img.jpg) + +Diagram illustrating Protocol Errors in SBc-AP. It shows two boxes: 'SBc-AP functional entity' at the top and 'ASN.1 Decoding' at the bottom, connected by a double-headed arrow. To the right of the top box, a bracket groups 'Logical Errors' and 'Abstract Syntax Errors'. To the right of the bottom box, a bracket groups 'Transfer Syntax Errors'. A large vertical arrow on the far right points upwards, indicating the flow of error reporting from the decoding layer to the functional entity. + +**Figure 4.5.1-1: Protocol Errors in SBc-AP** + +The information stated in subclauses 4.5.2, 4.5.3 and 4.5.4, to be included in the message used when reporting an error, is what at minimum shall be included. Other optional information elements within the message may also be included, if available. This is also valid for the case when the reporting is done with a response message. + +### 4.5.2 Transfer Syntax Error + +A Transfer Syntax Error occurs when the receiver is not able to decode the received physical message. Transfer syntax errors are always detected in the process of ASN.1 decoding. If a Transfer Syntax Error occurs, the receiver should initiate Error Indication procedure with appropriate cause value for the Transfer Syntax protocol error. + +### 4.5.3 Abstract Syntax Error + +#### 4.5.3.1 General + +An Abstract Syntax Error occurs when the receiving functional SBc-AP entity: + +1. receives IEs or IE groups that cannot be understood (unknown IE id); +2. receives IEs for which the logical range is violated (e.g.: ASN.1 definition: 0 to 15, the logical range is 0 to 10 (values 11 to 15 are undefined), and 12 will be received; this case will be handled as an abstract syntax error using criticality information sent by the originator of the message); +3. does not receive IEs or IE groups but according to the specified presence of the concerning object, the IEs or IE groups should have been present in the received message; +4. receives IEs or IE groups that are defined to be part of that message in wrong order or with too many occurrences of the same IE or IE group; +5. receives IEs or IE groups but according to the conditional presence of the concerning object and the specified condition, the IEs or IE groups should not have been present in the received message. + +Cases 1 and 2 (not comprehended IE/IE group) are handled based on received Criticality information. Case 3 (missing IE/IE group) is handled based on Criticality information and Presence information for the missing IE/IE group specified in the version of the specification used by the receiver. Case 4 (IEs or IE groups in wrong order or with too many occurrences) and Case 5 (erroneously present conditional IEs or IE groups) result in rejecting the procedure. + +If an Abstract Syntax Error occurs, the receiver shall read the remaining message and shall then for each detected Abstract Syntax Error act according to the Criticality Information and Presence Information for the IE/IE group due to which Abstract Syntax Error occurred in accordance with subclauses 4.5.3.4 and 4.5.3.5. The handling of cases 4 and 5 is specified in subclause 4.5.3.6. + +#### 4.5.3.2 Criticality information + +In the SBc-AP messages there is criticality information set for individual IEs and/or IE groups. This criticality information instructs the receiver how to act when receiving an IE or an IE group that is not comprehended i.e. the entire item (IE or IE group) which is not (fully or partially) comprehended shall be treated in accordance with its own criticality information as specified in subclause 4.5.3.4. + +In addition, the criticality information is used in case of the missing IE/IE group abstract syntax error (see subclause 4.5.3.5). + +The receiving node shall take different actions depending on the value of the Criticality Information. The three possible values of the Criticality Information for an IE/IE group are: + +- Reject IE; +- Ignore IE and Notify Sender; +- Ignore IE. + +The following rules restrict when a receiving entity may consider an IE, an IE group or an EP not comprehended (not implemented), and when action based on criticality information is applicable: + +1. IE or IE group: When one new or modified IE or IE group is implemented for one EP from a standard version, then other new or modified IEs or IE groups specified for that EP in that standard version shall be considered comprehended by the receiving entity (some may still remain unsupported). +2. EP: The comprehension of different EPs within a standard version or between different standard versions is not mandated. Any EP that is not supported may be considered not comprehended, even if another EP from that standard version is comprehended, and action based on criticality shall be applied. + +#### 4.5.3.3 Presence information + +For many IEs/IE groups which are optional according to the ASN.1 transfer syntax, SBc-AP specifies separately if the presence of these IEs/IE groups is optional or mandatory with respect to MME/CBC application. + +The presence field of the indicated classes supports three values: + +1. Optional; +2. Conditional; +3. Mandatory. + +If an IE/IE group is not included in a received message and the presence of the IE/IE group is mandatory or the presence is conditional and the condition is true according to the version of the specification used by the receiver, an abstract syntax error occurs due to a missing IE/IE group. + +#### 4.5.3.4 Not comprehended IE/IE group + +##### 4.5.3.4.1 Procedure code + +The receiving node shall treat the different types of received criticality information of the *Procedure Code* according to the following: + +**Reject IE:** + +- If a message is received with a *Procedure Code* marked with "*Reject IE*" which the receiving node does not comprehend, the receiving node shall reject the procedure using the Error Indication procedure. + +**Ignore IE and Notify Sender:** + +- If a message is received with a *Procedure Code* marked with "*Ignore IE and Notify Sender*" which the receiving node does not comprehend, the receiving node shall ignore the procedure and initiate the Error Indication procedure. + +**Ignore IE:** + +- If a message is received with a *Procedure Code* marked with "*Ignore IE*" which the receiving node does not comprehend, the receiving node shall ignore the procedure. + +When using the Error Indication procedure to reject a procedure or to report an ignored procedure it shall include the *Procedure Code IE*, the *Triggering Message IE*, and the *Procedure Criticality IE* in the *Criticality Diagnostics IE*. + +##### 4.5.3.4.2 Type of Message + +When the receiving node cannot decode the *Type of Message IE*, the Error Indication procedure shall be initiated with an appropriate cause value. + +##### 4.5.3.4.3 IEs other than the Procedure Code and Type of Message + +The receiving node shall treat the different types of received criticality information of an IE/IE group other than the *Procedure Code IE* and *Type of Message IE* according to the following: + +**Reject IE:** + +- If a message *initiating* a procedure is received containing one or more IEs/IE groups marked with "*Reject IE*" which the receiving node does not comprehend; none of the functional requests of the message shall be executed. The receiving node shall reject the procedure and report the rejection of one or more IEs/IE groups using the message normally used to report unsuccessful outcome of the procedure. In case the information received in the initiating message was insufficient to determine a value for all IEs that are required to be present in the message used to report the unsuccessful outcome of the procedure, the receiving node shall instead terminate the procedure and initiate the Error Indication procedure. +- If a message *initiating* a procedure that does not have a message to report unsuccessful outcome is received containing one or more IEs/IE groups marked with "*Reject IE*" which the receiving node does not comprehend, the receiving node shall terminate the procedure and initiate the Error Indication procedure. +- If a *response* message is received containing one or more IEs marked with "*Reject IE*" which the receiving node does not comprehend, the receiving node shall consider the procedure as unsuccessfully terminated and initiate local error handling. + +###### Ignore IE and Notify Sender: + +- If a message *initiating* a procedure is received containing one or more IEs/IE groups marked with "*Ignore IE and Notify Sender*" which the receiving node does not comprehend, the receiving node shall ignore the content of the not comprehended IEs/IE groups, continue with the procedure as if the not comprehended IEs/IE groups were not received (except for the reporting) using the understood IEs/IE groups, and report in the response message of the procedure that one or more IEs/IE groups have been ignored. In case the information received in the initiating message was insufficient to determine a value for all IEs that are required to be present in the response message, the receiving node shall instead terminate the procedure and initiate the Error Indication procedure. +- if a message *initiating* a procedure that does not have a message to report the outcome of the procedure is received containing one or more IEs/IE groups marked with "*Ignore IE and Notify Sender*" which the receiving node does not comprehend, the receiving node shall ignore the content of the not comprehended IEs/IE groups, continue with the procedure as if the not comprehended IEs/IE groups were not received (except for the reporting) using the understood IEs/IE groups, and initiate the Error Indication procedure to report that one or more IEs/IE groups have been ignored. +- If a *response* message is received containing one or more IEs/IE groups marked with "*Ignore IE and Notify Sender*" which the receiving node does not comprehend, the receiving node shall ignore the content of the not comprehended IE/IE groups, continue with the procedure as if the not comprehended IEs/IE groups were not received (except for the reporting) using the understood IEs/IE groups and initiate the Error Indication procedure. + +###### Ignore IE: + +- If a message *initiating* a procedure is received containing one or more IEs/IE groups marked with "*Ignore IE*" which the receiving node does not comprehend, the receiving node shall ignore the content of the not comprehended IEs/IE groups and continue with the procedure as if the not comprehended IEs/IE groups were not received using only the understood IEs/IE groups. +- If a *response* message is received containing one or more IEs/IE groups marked with "*Ignore IE*" which the receiving node does not comprehend, the receiving node shall ignore the content of the not comprehended IEs/IE groups and continue with the procedure as if the not comprehended IEs/IE groups were not received using the understood IEs/IE groups. + +When reporting not comprehended IEs/IE groups marked with "*Reject IE*" or "*Ignore IE and Notify Sender*" using a response message defined for the procedure, the *Information Element Criticality Diagnostics* IE shall be included in the *Criticality Diagnostics* IE for each reported IE/IE group. + +When reporting not comprehended IEs/IE groups marked with "*Reject IE*" or "*Ignore IE and Notify Sender*" using the Error Indication procedure, the *Procedure Code* IE, the *Triggering Message* IE, *Procedure Criticality* IE, and the *Information Element Criticality Diagnostics* IE shall be included in the *Criticality Diagnostics* IE for each reported IE/IE group. + +#### 4.5.3.5 Missing IE or IE group + +The receiving node shall treat the missing IE/IE group according to the criticality information for the missing IE/IE group in the received message specified in the version of the present document used by the receiver: + +##### Reject IE: + +- if a received message *initiating* a procedure is missing one or more IEs/IE groups with specified criticality "*Reject IE*"; none of the functional requests of the message shall be executed. The receiving node shall reject the procedure and report the missing IEs/IE groups using the message normally used to report unsuccessful outcome of the procedure. In case the information received in the initiating message was insufficient to determine a value for all IEs that are required to be present in the message used to report the unsuccessful outcome of the procedure, the receiving node shall instead terminate the procedure and initiate the Error Indication procedure. +- if a received message *initiating* a procedure that does not have a message to report unsuccessful outcome is missing one or more IEs/IE groups with specified criticality "*Reject IE*", the receiving node shall terminate the procedure and initiate the Error Indication procedure. +- if a received *response* message is missing one or more IEs/IE groups with specified criticality "*Reject IE*", the receiving node shall consider the procedure as unsuccessfully terminated and initiate local error handling. + +##### Ignore IE and Notify Sender: + +- if a received message *initiating* a procedure is missing one or more IEs/IE groups with specified criticality "*Ignore IE and Notify Sender*", the receiving node shall ignore that those IEs are missing and continue with the procedure based on the other IEs/IE groups present in the message and report in the response message of the procedure that one or more IEs/IE groups were missing. In case the information received in the initiating message was insufficient to determine a value for all IEs that are required to be present in the response message, the receiving node shall instead terminate the procedure and initiate the Error Indication procedure. +- if a received message *initiating* a procedure that does not have a message to report the outcome of the procedure is missing one or more IEs/IE groups with specified criticality "*Ignore IE and Notify Sender*", the receiving node shall ignore that those IEs are missing and continue with the procedure based on the other IEs/IE groups present in the message and initiate the Error Indication procedure to report that one or more IEs/IE groups were missing. +- if a received *response* message is missing one or more IEs/IE groups with specified criticality "*Ignore IE and Notify Sender*", the receiving node shall ignore that those IEs are missing and continue with the procedure based on the other IEs/IE groups present in the message and initiate the Error Indication procedure to report that one or more IEs/IE groups were missing. + +##### Ignore IE: + +- if a received message *initiating* a procedure is missing one or more IEs/IE groups with specified criticality "*Ignore IE*", the receiving node shall ignore that those IEs are missing and continue with the procedure based on the other IEs/IE groups present in the message. +- if a received *response* message is missing one or more IEs/IE groups with specified criticality "*Ignore IE*", the receiving node shall ignore that those IEs/IE groups are missing and continue with the procedure based on the other IEs/IE groups present in the message. + +When reporting missing IEs/IE groups with specified criticality "*Reject IE*" or "*Ignore IE and Notify Sender*" using a response message defined for the procedure, the *Information Element Criticality Diagnostics* IE shall be included in the *Criticality Diagnostics* IE for each reported IE/IE group. + +When reporting missing IEs/IE groups with specified criticality "*Reject IE*" or "*Ignore IE and Notify Sender*" using the Error Indication procedure, the *Procedure Code* IE, the *Triggering Message* IE, *Procedure Criticality* IE, and the *Information Element Criticality Diagnostics* IE shall be included in the *Criticality Diagnostics* IE for each reported IE/IE group. + +#### 4.5.3.6 IEs or IE groups received in wrong order or with too many occurrences or erroneously present + +If a message with IEs or IE groups in wrong order or with too many occurrences is received or if IEs or IE groups with a conditional presence are present when the condition is not met (i.e. erroneously present), the receiving node shall behave according to the following: + +- If a message *initiating* a procedure is received containing IEs or IE groups in wrong order or with too many occurrences or erroneously present, none of the functional requests of the message shall be executed. The receiving node shall reject the procedure and report the cause value "Abstract Syntax Error (Falsely Constructed Message)" using the message normally used to report unsuccessful outcome of the procedure. In case the information received in the initiating message was insufficient to determine a value for all IEs that are required to be present in the message used to report the unsuccessful outcome of the procedure, the receiving node shall instead terminate the procedure and initiate the Error Indication procedure. +- If a message *initiating* a procedure that does not have a message to report unsuccessful outcome is received containing IEs or IE groups in wrong order or with too many occurrences or erroneously present, the receiving node shall terminate the procedure and initiate the Error Indication procedure, and use cause value "Abstract Syntax Error (Falsely Constructed Message)". +- If a *response* message is received containing IEs or IE groups in wrong order or with too many occurrences or erroneously present, the receiving node shall consider the procedure as unsuccessfully terminated and initiate local error handling. + +When determining the correct order only the IEs specified in the specification version used by the receiver shall be considered. + +### 4.5.4 Logical Error + +Logical error situations occur when a message is comprehended correctly, but the information contained within the message is not valid (i.e. semantic error), or describes a procedure which is not compatible with the state of the receiver. In these conditions, the following behaviour shall be performed (unless otherwise specified) as defined by the class of the elementary procedure, irrespective of the criticality information of the IE's/IE groups containing the erroneous values. + +#### Class 1: + +Where the logical error occurs in a request message of a class 1 procedure, and the procedure has a message to report this unsuccessful outcome, this message shall be sent with an appropriate cause value. Typical cause values are: + +- Semantic Error; +- Message not compatible with receiver state. + +Where the logical error is contained in a request message of a class 1 procedure, and the procedure does not have a message to report this unsuccessful outcome, the procedure shall be terminated and the Error Indication procedure shall be initiated with an appropriate cause value. The *Procedure Code* IE and the *Triggering Message* IE within the *Criticality Diagnostics* IE shall then be included in order to identify the message containing the logical error. + +Where the logical error exists in a response message of a class 1 procedure, the procedure shall be considered as unsuccessfully terminated and local error handling shall be initiated. + +#### Class 2: + +Where the logical error occurs in a message of a class 2 procedure, the procedure shall be terminated and the Error Indication procedure shall be initiated with an appropriate cause value. The *Procedure Code* IE and the *Triggering Message* IE within the *Criticality Diagnostics* IE shall then be included in order to identify the message containing the logical error. + +### 4.5.5 Exceptions + +The error handling for all the cases described hereafter shall take precedence over any other error handling described in the other subclauses of clause 4.5. + +- If any type of error (Transfer Syntax Error, Abstract Syntax Error or Logical Error) is detected in the ERROR INDICATION message, it shall not trigger the Error Indication procedure in the receiving Node but local error handling. +- In case a response message or Error Indication message needs to be returned, but the information necessary to determine the receiver of that message is missing, the procedure shall be considered as unsuccessfully terminated and local error handling shall be initiated. +- If an error that terminates a procedure occurs, the returned cause value shall reflect the error that caused the termination of the procedure even if one or more abstract syntax errors with criticality "ignore and notify" have earlier occurred within the same procedure. + +# Annex A (informative): Change history: + +| Change history | | | | | | | | +|----------------|-------|-----------|------|-----|----------------------------------------------------------------------------|--------|--------| +| Date | TSG # | TSG Doc. | CR | Rev | Subject/Comment | Old | New | +| 2008-12 | CT#42 | CP-080972 | | | V1.0.2 approved in CT#42 | 1.0.2 | 8.0.0 | +| 2009-03 | CT#43 | CP-090101 | 0001 | 3 | General clean-up to make an alignment with RAN specifications | 8.0.0 | 8.1.0 | +| | | CP-090022 | 0002 | - | General clean-up to make an alignment with RAN specifications | | | +| 2009-09 | CT#45 | CP-090543 | 0003 | 1 | Correct ASN.1 misalignment between SIAP and SB-AP | 8.1.0 | 8.2.0 | +| | | | 0004 | 1 | Fix the ASN.1 Object Identifiers (OID) descriptions for SBc-AP | | | +| | | | 0005 | 1 | Update port number and payload protocol identifier for SBc-AP | | | +| | | | 0006 | - | Fix incorrect IETF reference | | | +| 2009-12 | CT#46 | CP-090780 | 0008 | 1 | Missing OMC-ID and other corrections | 8.2.0 | 8.3.0 | +| | | | 0009 | - | Correction of Warning Message Transmission procedure | | | +| 2009-12 | CT#46 | CP-090799 | 0007 | 4 | Enhancements to Warning Notifications to support PWS/CMAS Requirements | 8.3.0 | 9.0.0 | +| 2010-06 | CT#48 | CP-100288 | 0011 | 2 | Number of Broadcasts | 9.0.0 | 9.1.0 | +| 2010-09 | CT#49 | CP-100446 | 0013 | - | Correction of the SCTP Payload Protocol value for the SBc-AP | 9.1.0 | 9.2.0 | +| 2010-12 | CT#50 | CP-100708 | 0014 | 3 | Correct WRITE-REPLACE-WARNING REQUEST misalignment between SIAP and SBc-AP | 9.2.0 | 9.3.0 | +| 2011-03 | CT#51 | CP-110080 | 0015 | 2 | SBc-AP Error Indication | 9.3.0 | 10.0.0 | +| 2011-09 | CT#53 | CP-110579 | 0016 | - | Error Indication procedure | 10.0.0 | 11.0.0 | +| 2011-12 | CT#54 | CP-110797 | 0018 | - | Error Indication | 11.0.0 | 11.1.0 | +| | | CP-110783 | 0020 | - | Extended Repetition Period | | | +| 2012-03 | CT#55 | CP-120021 | 0024 | - | Correction to Assigned Criticality | 11.1.0 | 11.2.0 | +| 2012-06 | CT#56 | CP-120246 | 0025 | - | Corrections to ASN.1 code | 11.2.0 | 11.3.0 | +| 2012-09 | CT#57 | CP-120460 | 0026 | - | Correction to ASN1 syntax | 11.3.0 | 11.4.0 | +| | | CP-120460 | 0027 | - | Editorial updates of references | | | +| | | CP-120463 | 0031 | | ETWS Secondary Notification | | | +| 2015-12 | CT#70 | CP-150741 | 0063 | | ASN.1 Corrections | 11.4.0 | 11.5.0 | \ No newline at end of file diff --git a/marked/Rel-11/29_series/29171/7affafe7362a2d2d072e9d4bf515f0bb_img.jpg b/marked/Rel-11/29_series/29171/7affafe7362a2d2d072e9d4bf515f0bb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d97158077ff71c4cc4c98df0ffcef08799d645d7 --- /dev/null +++ b/marked/Rel-11/29_series/29171/7affafe7362a2d2d072e9d4bf515f0bb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1b8e0001128ba190785fc5460b1f7d86eb3574d2e91a9ba94bb9f35f9549f6f7 +size 31477 diff --git a/marked/Rel-11/29_series/29171/af6be343f0c0a8f155f965dcf337b8af_img.jpg b/marked/Rel-11/29_series/29171/af6be343f0c0a8f155f965dcf337b8af_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6132ac5229394365c73c218a0fc0fa72b344127b --- /dev/null +++ b/marked/Rel-11/29_series/29171/af6be343f0c0a8f155f965dcf337b8af_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6b53ca07dfaffd7d2d5db8a69776023989c9fe7d9dbe415307ea46bed01b6a32 +size 24364 diff --git a/marked/Rel-11/29_series/29171/f20786b603b41e24b5d5899f710b5947_img.jpg b/marked/Rel-11/29_series/29171/f20786b603b41e24b5d5899f710b5947_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..97d4617127f133ee5955f53b8a9033a10ab46a42 --- /dev/null +++ b/marked/Rel-11/29_series/29171/f20786b603b41e24b5d5899f710b5947_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b25c28014e87d31f36dd9edfeff006aacbf6bb0f4c5f548fb5b0f3cd14df868b +size 20692 diff --git a/marked/Rel-11/29_series/29171/raw.md b/marked/Rel-11/29_series/29171/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..00372daad102302e20234f393998c1a9e5de8c57 --- /dev/null +++ b/marked/Rel-11/29_series/29171/raw.md @@ -0,0 +1,2513 @@ + + + + + + +# Contents + +| | | +|------------------------------------------------------------|----| +| Foreword ..... | 5 | +| 1 Scope..... | 6 | +| 2 References..... | 6 | +| 3 Definitions and abbreviations ..... | 6 | +| 3.1 Definitions..... | 6 | +| 3.2 Abbreviations ..... | 7 | +| 4 Functional Overview..... | 7 | +| 4.1 General ..... | 7 | +| 5 LCS-AP Message Transport ..... | 8 | +| 5.1 General ..... | 8 | +| 5.2 Protocol Layering..... | 8 | +| 5.3 Usage of SCTP Associations..... | 9 | +| 6 LCS-AP Procedures ..... | 9 | +| 6.1 General ..... | 9 | +| 6.2 Procedures Applicable to LCS-AP..... | 9 | +| 6.2.1 Location Service Request..... | 9 | +| 6.2.1.1 General..... | 9 | +| 6.2.1.2 Successful Operation ..... | 9 | +| 6.2.1.3 Unsuccessful Operation..... | 11 | +| 6.2.2 Location Information Exchange ..... | 11 | +| 6.2.2.1 Connection Oriented Information Transfer ..... | 11 | +| 6.2.2.1.1 General ..... | 11 | +| 6.2.2.1.2 Successful Operation..... | 11 | +| 6.2.2.1.3 Abnormal Conditions ..... | 12 | +| 6.2.2.2 Connectionless Information Transfer ..... | 12 | +| 6.2.2.2.1 General ..... | 12 | +| 6.2.2.2.2 Successful Operation..... | 12 | +| 6.2.2.2.3 Unsuccessful Operation..... | 12 | +| 6.2.2.2.4 Abnormal Conditions ..... | 13 | +| 6.3 Exception Procedures..... | 13 | +| 6.3.1 Location Abort..... | 13 | +| 6.3.1.1 General..... | 13 | +| 6.3.1.2 Normal Operation ..... | 13 | +| 6.3.1.3 Abnormal Conditions..... | 13 | +| 6.3.2 Reset ..... | 14 | +| 6.3.2.1 General..... | 14 | +| 6.3.2.2 Normal Operation ..... | 14 | +| 6.3.2.3 Abnormal Conditions..... | 14 | +| 6.4 Error Handling..... | 14 | +| 6.4.1 Abnormal Conditions ..... | 14 | +| 6.4.2 Overload ..... | 15 | +| 7 LCS-AP Messages and Message Formats ..... | 15 | +| 7.1 General ..... | 15 | +| 7.2 Message Formats..... | 15 | +| 7.3 LCS-AP Messages..... | 16 | +| 7.3.1 LCS-AP Location Request message..... | 16 | +| 7.3.2 LCS-AP Location Response message ..... | 16 | +| 7.3.3 LCS-AP Location Abort Request message ..... | 17 | +| 7.3.4 LCS-AP Connection Oriented Information message ..... | 17 | +| 7.3.5 LCS-AP Connectionless Information message ..... | 17 | +| 7.3.6 LCS-AP Reset Request message..... | 18 | +| 7.3.7 LCS-AP Reset Acknowledge message..... | 18 | +| 7.4 Information Elements..... | 18 | +| 7.4.1 General ..... | 18 | +| 7.4.2 Message Type..... | 19 | + +| | | | +|--------|------------------------------------------------------------------|----| +| 7.4.3 | Location Type..... | 19 | +| 7.4.4 | E-CGI ..... | 19 | +| 7.4.5 | LCS Client Type..... | 20 | +| 7.4.6 | LCS Priority..... | 20 | +| 7.4.7 | LCS QoS..... | 20 | +| 7.4.8 | UE Positioning Capability ..... | 21 | +| 7.4.9 | Include Velocity ..... | 21 | +| 7.4.10 | IMSI..... | 21 | +| 7.4.11 | IMEI ..... | 22 | +| 7.4.12 | Geographic Area..... | 23 | +| 7.4.13 | Positioning Data ..... | 24 | +| 7.4.14 | Velocity Estimate ..... | 27 | +| 7.4.15 | Accuracy Fulfilment Indicator..... | 27 | +| 7.4.16 | LCS Cause ..... | 28 | +| 7.4.17 | Payload Type..... | 29 | +| 7.4.18 | APDU ..... | 29 | +| 7.4.19 | Network Element..... | 29 | +| 7.4.20 | Return Error Request ..... | 29 | +| 7.4.21 | Return Error Cause ..... | 29 | +| 7.4.22 | Altitude and direction ..... | 30 | +| 7.4.23 | Geographical Coordinates ..... | 30 | +| 7.4.24 | Uncertainty Ellipse ..... | 31 | +| 7.4.25 | Horizontal Speed and Bearing..... | 31 | +| 7.4.26 | Vertical Velocity ..... | 31 | +| 7.4.27 | PLMN Identity..... | 32 | +| 7.4.28 | Correlation ID..... | 32 | +| 7.4.29 | eNB ID..... | 33 | +| 7.4.30 | LCS Service Type ID ..... | 33 | +| 7.5 | Message and information element abstract syntax..... | 33 | +| 7.5.1 | General ..... | 33 | +| 7.5.2 | Usage of protocol extension mechanism for non-standard use ..... | 33 | +| 7.5.3 | Elementary procedure definitions..... | 34 | +| 7.5.4 | PDU definitions ..... | 36 | +| 7.5.5 | Information element definitions ..... | 40 | +| 7.5.6 | Common definitions ..... | 46 | +| 7.5.7 | Constant definitions..... | 47 | +| 7.5.8 | Container Definitions ..... | 48 | +| 7.5.9 | Message transfer syntax ..... | 49 | +| 7.6 | Handling of unknown, unforeseen and erroneous protocol data..... | 50 | +| 8 | LCS-AP Timers..... | 50 | +| 8.1 | General ..... | 50 | +| 8.2 | Timers of LCS-AP ..... | 50 | + +| | | | +|------------------------|----------------|----| +| Annex A (informative): | Change history | 51 | +|------------------------|----------------|----| + +# --- Foreword + +This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +# --- 1 Scope + +The present document specifies the procedures and information coding for LCS Application Protocol (LCS-AP) that is needed to support the location services in E-UTRAN. The LCS-AP message set is applicable to the SLs interface between the E-SMLC and the MME. LCS-AP is developed in accordance to the general principles stated in 3GPP TS 23.271 [3]. + +# --- 2 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. + - For a specific reference, subsequent revisions do not apply. + - For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. +- [1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications". +- [2] 3GPP TS 36.305: "Stage 2 functional specification of User Equipment (UE) positioning in E-UTRAN". +- [3] 3GPP TS 23.271: "Functional stage 2 description of Location Services (LCS)". +- [4] IETF RFC 4960: "Stream Control Transmission Protocol". +- [5] TTA/EIA/IS-J-STD-036 (2000): "Wireless Enhanced Emergency Services". +- [6] 3GPP TS 23.032: "Universal Geographical Area Description (GAD)". +- [7] 3GPP TS 36.413: "S1 Application Protocol (S1AP)". +- [8] ITU-T Recommendation X.680 (07/2002): "Information Technology - Abstract Syntax Notation One (ASN.1): Specification of basic notation". +- [9] ITU-T Recommendation X.681 (07/2002): "Information Technology - Abstract Syntax Notation One (ASN.1): Information object specification". +- [10] 3GPP TS 22.071: "Location Services (LCS); Service Description; Stage1". +- [11] 3GPP TS 23.003: "Numbering, addressing and identification". +- [12] ITU-T Recommendation X.691 (07/2002): "Information Technology - ASN.1 encoding rules - Specification of Packed Encoding Rules (PER)". + +# --- 3 Definitions and abbreviations + +## 3.1 Definitions + +For the purposes of the present document, the terms and definitions given in TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905 [1]. + +**Elementary Procedure:** LCS-AP protocol consists of Elementary Procedures (EPs). An LCS-AP Elementary Procedure is a unit of interaction between the MME and the E-SMLC. An EP consists of an initiating message and possibly a response message. Two kinds of EPs are used: + +- **Class 1:** Elementary Procedures with response (success or failure), +- **Class 2:** Elementary Procedures without response. + +## 3.2 Abbreviations + +For the purposes of the present document, the abbreviations given in TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905 [1]. + +| | | +|---------|----------------------------------------------------| +| CID | Cell-ID (positioning method) | +| E-CID | Enhanced Cell-ID (positioning method) | +| E-SMLC | Enhanced Serving Mobile Location Centre | +| E-UTRAN | Evolved Universal Terrestrial Radio Access Network | +| GNSS | Global Navigation Satellite System | +| GPS | Global Positioning System | +| LCS | LoCation Services | +| LCS-AP | LCS Application Protocol | +| LPP | LTE Positioning Protocol | +| LPPa | LTE Positioning Protocol Annex | +| LTE | Long Term Evolution | +| MO-LR | Mobile Originated Location Request | +| MT-LR | Mobile Terminated Location Request | +| NI-LR | Network Induced Location Request | +| MME | Mobility Management Entity | +| OTDOA | Observed Time Difference Of Arrival | +| PDU | Protocol Data Unit | +| SCTP | Stream Control Transmission Protocol | +| SET | SUPL Enabled Terminal | +| SLP | SUPL Location Platform | +| SUPL | Secure User Plane Location | +| TA | Timing Advanced | +| UE | User Equipment | +| U-TDOA | Uplink Time Difference Of Arrival | + +# --- 4 Functional Overview + +## 4.1 General + +Figure 4.1-1 below shows the architecture applicable to the positioning of a UE with E-UTRAN access. The SLs interface is used to convey LCS-AP messages and parameters between the MME to the E-SMLC. It is also used for tunnelling LTE Positioning Protocols (LPP between the E-SMLC and the target UE, LPPa between the E-SMLC and the eNB), which are transparent to the MME as described in 3GPP TS 36.305 [2]. + +![Diagram of positioning interfaces in E-UTRAN showing UE, Serving eNB, Neighbor eNB, MME, and E-SMLC connected via LTE-Uu, S1, and SLs interfaces.](d0abac95583b52a3b35f74a215567334_img.jpg) + +The diagram illustrates the network architecture for positioning in E-UTRAN. A User Equipment (UE) is connected to a Serving eNB via the LTE-Uu interface. The Serving eNB is connected to an MME via an S1 interface. A Neighbor eNB is also connected to the MME via an S1 interface. The MME is connected to an E-SMLC via an SLs interface. + +Diagram of positioning interfaces in E-UTRAN showing UE, Serving eNB, Neighbor eNB, MME, and E-SMLC connected via LTE-Uu, S1, and SLs interfaces. + +Figure 4.1-1 Positioning Interfaces in E-UTRAN + +# 5 LCS-AP Message Transport + +## 5.1 General + +The LCS-AP is a logical interface between the MME and the E-SMLC. This section specifies the standards for signaling transport to be used across LCS-AP. + +## 5.2 Protocol Layering + +Figure 5.2-1 below shows the protocol layering used to support the transfer of LCS-AP PDUs between an E-SMLC and a MME. The LTE Positioning Protocols (LPP and LPPa) can be carried in LCS-AP messages which are transparent to the MME. + +![Protocol layering diagram for LCS-AP between MME and E-SMLC, showing layers like NAS, S1-AP, SCTP, IP, L2, and L1, with LCS-AP being transparent to the MME.](7affafe7362a2d2d072e9d4bf515f0bb_img.jpg) + +The diagram shows the protocol stack for the LCS-AP interface between the MME and the E-SMLC. The MME stack includes NAS, S1-AP, SCTP, IP, L2, and L1 layers. The E-SMLC stack includes LPP/LPPa, LCS-AP, SCTP, IP, L2, and L1 layers. The LCS-AP layer in the E-SMLC is shown as being transparent to the MME's NAS and S1-AP layers. The SCTP, IP, L2, and L1 layers are common to both stacks. The interface between the MME and E-SMLC is labeled SLs. + +Protocol layering diagram for LCS-AP between MME and E-SMLC, showing layers like NAS, S1-AP, SCTP, IP, L2, and L1, with LCS-AP being transparent to the MME. + +Figure 5.2-1 Protocol Layering for LCS-AP + +## 5.3 Usage of SCTP Associations + +SCTP (see IETF RFC 4960 [4]) shall be supported as the transport layer of LCS-AP messages. + +Semi-permanent SCTP associations shall be established between MME and E-SMLC, i.e. the SCTP associations shall remain up under normal circumstances. + +Local multi-homing should be supported. Remote multi-homing shall be supported. + +Multiple local SCTP endpoints may be supported. Multiple remote SCTP endpoints shall be supported. When multiple local or remote SCTP endpoints are configured, several simultaneous SCTP associations shall be supported between MME and E-SMLC. + +The MME shall establish the SCTP association. Since under normal operation there should always be an SCTP association established between an MME and an E-SMLC, if the E-SMLC needs to initiate a message towards an MME it shall do so over an existing SCTP association already established with that MME. + +When an entity detects that an SCTP association has been lost, all resources for transactions open on that association shall be released. + +The registered port number for LCS-AP is 9082. The registered payload protocol identifier for LCS-AP is 29. + +# 6 LCS-AP Procedures + +## 6.1 General + +The LCS-AP interface can be divided into the following procedures: + +- Location service request procedure +- Location information exchange procedure + +The E-UTRAN positioning capabilities are intended to be forward compatible to other access types and other position methods, in an effort to reduce the amount of additional positioning support needed in the future. + +## 6.2 Procedures Applicable to LCS-AP + +### 6.2.1 Location Service Request + +#### 6.2.1.1 General + +The purpose of the location service request procedure is to obtain the location estimate for a target UE in E-UTRAN. + +#### 6.2.1.2 Successful Operation + +![Sequence diagram showing the Location Service Request Procedure between an MME and an E-SMLC. The MME sends a LOCATION REQUEST to the E-SMLC, and the E-SMLC responds with a LOCATION RESPONSE.](88868e6be8ce57a97c045f188f7e363c_img.jpg) + +``` + +sequenceDiagram + participant MME + participant E-SMLC + Note left of MME: + MME->>E-SMLC: LOCATION REQUEST + Note right of E-SMLC: + E-SMLC-->>MME: LOCATION RESPONSE + Note left of MME: + +``` + +Sequence diagram showing the Location Service Request Procedure between an MME and an E-SMLC. The MME sends a LOCATION REQUEST to the E-SMLC, and the E-SMLC responds with a LOCATION RESPONSE. + +Figure 6.2.1.2-1 Location Service Request Procedure, Successful Operation + +The initiator (MME) of the location service request procedure sends a LCS-AP Location Request message to the E-SMLC associated with the current serving cell for the target UE and starts the timer T3x01. The message contains the following mandatory (M), conditional (C) and optional (O) information, where conditional parameters are required if available. + +- Correlation ID (M) +- Location Type (M) +- Cell Identifier (M) +- LCS Client Type (C) +- LCS Priority (C) +- LCS Service Type ID (C) +- LCS QoS (C) +- UE Positioning Capability (O) +- Include Velocity (O) +- IMSI of target UE (O) +- IMEI of target UE (O) +- APDU (O) + +The Correlation ID is assigned by the MME and enables association of the location response with the location request when more than one location service request procedure is ongoing for the UE with the same E-SMLC. + +The Location Type IE indicates the type of Location Information being requested. The following types are supported: + +- Current geographic location estimate +- Location assistance data for the target UE + +If the location estimate is requested, the E-SMLC performs positioning procedure on the target UE using a particular position method or a combination of more than one positioning method based on the UE capability. If UE capability is unknown, the E-SMLC may request UE position capability through LPP as defined in 3GPP TS 36.305 [2]. + +Alternatively, if assistance data was requested, the E-SMLC may provide positioning assistance data to the UE. The E-SMLC may invoke the following LCS-AP procedures to get assistance data: + +- Connection Oriented Information Transfer +- Connectionless Information Transfer + +If a location estimate was requested and was subsequently obtained, the E-SMLC shall return a LCS-AP Location Response to the initiator of the location request using the same SCTP association as the location request. This message contains the following mandatory (M), conditional (C) and optional parameters (O). + +- Correlation ID (M) +- Location Estimate (M). +- Accuracy Fulfilment Indicator (O). +- Velocity estimate (C). +- Positioning Data (C). + +If assistance data was instead requested for an UE and the E-SMLC was able successfully to transfer this to the UE, the E-SMLC shall return a LCS-AP Location Response to the initiator of the location request (MME). This message shall contain no parameters. The absence of a LCS Cause parameter in this case implies that the transfer was successful. + +If the MME receives the LCS-AP Location Response for corresponding request message, the MME shall stop the timer T3x01. + +#### 6.2.1.3 Unsuccessful Operation + +If the E-SMLC is unable to obtain any of the location information requested or if requested LCS assistance data could not be transferred, the E-SMLC shall return a LCS-AP Location Response to the initiator of the Location Request carrying the following parameters: + +- Correlation ID (M) +- LCS Cause (M) +- Positioning Data (O) + +The E-SMLC shall use the same SCTP association for the Location Response as was used for the request. + +If the MME receives the LCS-AP Location Response for corresponding request message, the MME shall stop the timer T3x01. + +On the expiry of the timer T3x01, the MME shall abort the procedure, release any resources allocated for this location request procedure and notify the node that triggered the Location Request about the error. + +### 6.2.2 Location Information Exchange + +#### 6.2.2.1 Connection Oriented Information Transfer + +##### 6.2.2.1.1 General + +The Connection Oriented Information transfer procedure enables two-way transfer of LPP and LPPa messages between an E-SMLC and a MME. The procedure is only valid while a location request procedure for the target UE is ongoing. This procedure makes use of the same SCTP association as the location request procedure for the particular target UE. + +##### 6.2.2.1.2 Successful Operation + +![Sequence diagram showing a successful operation for Connection Oriented Information transfer between Endpoint A and Endpoint B.](536951b2bbd94325ae266d8d1363df8f_img.jpg) + +The diagram illustrates a successful operation for Connection Oriented Information transfer. It features two vertical lifelines labeled 'Endpoint A' and 'Endpoint B'. A horizontal arrow points from Endpoint A to Endpoint B, labeled 'CONNECTION ORIENTED INFORMATION'. Both endpoints have a small black horizontal bar at the bottom of their lifelines. + +Sequence diagram showing a successful operation for Connection Oriented Information transfer between Endpoint A and Endpoint B. + +**Figure 6.2.2.1.2-1 Connection Oriented Information, Successful Operation** + +The initiator of the procedure (E-SMLC or MME) with a LPP or LPPa message to transfer concerning a particular target UE sends a LCS-AP Connection Oriented Information message to a recipient carrying the following parameters: + +- Correlation ID (M) +- Payload Type (M) +- APDU (M); + +The Correlation ID in this message is the Correlation ID used for the Location Request. It shall be present for a message transfer from the E-SMLC to the MME and for a message transfer from the MME to the E-SMLC. + +The Payload Type shall be present to indicate the type of the APDU. The supported information types are LPP and LPPa. + +The APDU shall contain an LPP APDU when communicating between the E-SMLC and the target UE or an LPPa APDU when communicating between the E-SMLC and serving eNB. The MME shall forward this to the serving eNB for the target UE. + +If the intended recipient is the E-SMLC for a target UE, the message is terminated in the E-SMLC. The E-SMLC shall then perform interpretation of the APDU. + +##### 6.2.2.1.3 Abnormal Conditions + +At an intermediate entity, if a received LCS-AP Connection Oriented Information message contains unrecognized information or if the message cannot be sent on, the message shall be discarded. + +#### 6.2.2.2 Connectionless Information Transfer + +##### 6.2.2.2.1 General + +The Connectionless Information transfer procedure enables two-way transfer of LPPa messages between an E-SMLC and a MME when there is no existing signalling connection association. This procedure can be used to query eNBs for the information not related to a UE connection, such as Timing information on the eNB. + +##### 6.2.2.2.2 Successful Operation + +![Sequence diagram illustrating the Connectionless Information Procedure for Successful Operation. Two vertical lifelines are shown: Endpoint A (left) and Endpoint B (right). Each lifeline has a solid rectangular block at its base. The first message is a horizontal arrow labeled 'CONNECTIONLESS INFORMATION' pointing from Endpoint A to Endpoint B. The second message is a horizontal arrow labeled 'CONNECTIONLESS INFORMATION' pointing from Endpoint B back to Endpoint A.](af6be343f0c0a8f155f965dcf337b8af_img.jpg) + +Sequence diagram illustrating the Connectionless Information Procedure for Successful Operation. Two vertical lifelines are shown: Endpoint A (left) and Endpoint B (right). Each lifeline has a solid rectangular block at its base. The first message is a horizontal arrow labeled 'CONNECTIONLESS INFORMATION' pointing from Endpoint A to Endpoint B. The second message is a horizontal arrow labeled 'CONNECTIONLESS INFORMATION' pointing from Endpoint B back to Endpoint A. + +**Figure 6.2.2.2.2-1 Connectionless Information Procedure, Successful Operation** + +The initiator of the procedure (either E-SMLC or MME) sends a LCS-AP Connectionless Information message to a recipient carrying the following parameters: + +- Source Entity (M) +- Destination Entity (M) +- APDU (M) +- Return Error Request (O) + +The source entity identifies the sender. The recipient entity identifies the final destination. The APDU contains a LPPa APDU to be transferred. The Return Error Request may be included to request notification in the event of unsuccessful transfer and indicate the type of notification needed. If the recipient entity is not the final destination, the recipient shall transfer the LCS-AP Connectionless Information message to either the final destination or an intermediate entity capable of forward it to the final destination. + +##### 6.2.2.2.3 Unsuccessful Operation + +If the message cannot be transferred by an intermediate entity or destination entity and the Return Error Request is not included, the message shall be discarded. If the Return Error Request is included, the intermediate or destination entity shall, depending on the Return Error Request type, send a LCS-AP Connectionless Information message to, or towards, the original source containing the following parameters: + +- Source Entity (M) +- Destination Entity (M) +- APDU (M) +- Return Error Cause (M) + +The Source entity shall indicate the Destination Entity in the original received message. The Destination Entity shall indicate the Source Entity in the original message. The Return Error cause shall indicate the reason for unsuccessful transfer. The APDU shall contain any originally received APDU. + +If a received LCS-AP Connectionless Information message containing a Return Error Cause cannot be transferred by an intermediate entity, it shall be discarded with no return error message. + +##### 6.2.2.2.4 Abnormal Conditions + +At an intermediate entity, if a received LCS-AP Connectionless Information message contains unrecognized or invalid information, the message shall be discarded. + +At the recipient entity, if a received LCS-AP Connectionless Information message contains invalid or unrecognized information as defined for LCS-AP, the message shall be discarded. + +## 6.3 Exception Procedures + +### 6.3.1 Location Abort + +#### 6.3.1.1 General + +The purpose of the Location Abort procedure is to cancel an ongoing positioning attempt or the request for assistance data. This message can be sent from the MME to the E-SMLC. This procedure makes use of the same SCTP association as the location request procedure for the particular target UE. + +#### 6.3.1.2 Normal Operation + +![Sequence diagram of the Location Abort Procedure, Normal Operation. The diagram shows two entities: MME and E-SMLC. The MME sends a 'LOCATION ABORT REQUEST' message to the E-SMLC. The E-SMLC responds with a 'LOCATION RESPONSE' message back to the MME.](f20786b603b41e24b5d5899f710b5947_img.jpg) + +``` +sequenceDiagram + participant MME + participant E-SMLC + Note left of MME: + MME->>E-SMLC: LOCATION ABORT REQUEST + Note right of E-SMLC: + E-SMLC-->>MME: LOCATION RESPONSE + Note left of MME: +``` + +Sequence diagram of the Location Abort Procedure, Normal Operation. The diagram shows two entities: MME and E-SMLC. The MME sends a 'LOCATION ABORT REQUEST' message to the E-SMLC. The E-SMLC responds with a 'LOCATION RESPONSE' message back to the MME. + +**Figure 6.3.1.2-1 Location Abort Procedure, Normal Operation** + +The MME sends a LCS-AP Location Abort Request message to the E-SMLC across the SLs interface. The message contains a LCS Cause parameter indicating the reason of cancellation. + +On receipt of this message, the E-SMLC shall stop the positioning transactions of the target UE and may release any resources previously allocated. The E-SMLC shall return a LCS-AP Location Response message containing the LCS Cause received in Location Abort Request and, optionally, positioning data. The E-SMLC may also optionally include in this response any “best-effort” location estimate that it has already determined prior to receiving the LCS-AP Location Abort Request. + +#### 6.3.1.3 Abnormal Conditions + +At the recipient entity, if no ongoing location transaction for the target UE is found, the recipient entity shall discard the received LCS-AP Location Abort Request message with no return error message. + +### 6.3.2 Reset + +#### 6.3.2.1 General + +The Reset procedure is an optional procedure applicable to the LCS-AP. It enables an E-SMLC or a MME that has undergone a failure with loss of location service transactions to indicate this to a partner entity. The recipient entity can then release its own connection and transaction resources. The Reset procedure may not be applicable when only a limited part of + +an E-SMLC or a MME has suffered a failure, since error recovery procedures specific to individual connections and transactions may then be used. The Reset procedure applies to all transactions initiated on a single SCTP association. + +#### 6.3.2.2 Normal Operation + +![Sequence diagram illustrating the Reset Procedure, Normal Operation. Endpoint A sends a RESET REQUEST to Endpoint B, and Endpoint B responds with a RESET ACKNOWLEDGE.](a26e142d3df5bef41a84a9dd099d7825_img.jpg) + +``` +sequenceDiagram + participant Endpoint A + participant Endpoint B + Note left of Endpoint A: + Endpoint A->>Endpoint B: RESET REQUEST + Note right of Endpoint B: + Endpoint B-->>Endpoint A: RESET ACKNOWLEDGE + Note left of Endpoint A: + Note right of Endpoint B: +``` + +Sequence diagram illustrating the Reset Procedure, Normal Operation. Endpoint A sends a RESET REQUEST to Endpoint B, and Endpoint B responds with a RESET ACKNOWLEDGE. + +**Figure 6.3.2.2-1 Reset Procedure, Normal Operation** + +In the event of a failure at an E-SMLC or a MME that results in the loss of location service transactions, a LCS-AP Reset Request message may be sent to the partner entity across the SLs interface. The message contains a LCS Cause parameter indicating the reason for the reset. The sending entity shall ensure that all information on location service transactions for the SCTP association on which the Reset Request was sent is reinitialized to indicate no existing transactions. + +On receiving a LCS-AP Reset Request message, the recipient entity (E-SMLC or MME) shall clear all references and state information for the location service transactions on the SCTP association on which the Reset Request was received and shall release any associated resources. The recipient entity shall then return a LCS-AP Reset Acknowledge message using the same SCTP association as the Reset Request. + +If the initiating entity (E-SMLC or MME) received the LCS-AP Reset Acknowledge message, it shall stop the timer T3x02. + +#### 6.3.2.3 Abnormal Conditions + +On the first expiry of the timer T3x02, the Source entity (E-SMLC or MME) shall resend the LCS-AP Reset Request message and shall reset and restart timer T3x02. This retransmission is repeated a maximum of "n" times, where "n" is an O&M administered parameter. Following "n" unsuccessful reset attempts, the procedure shall be terminated and maintenance shall be informed. + +## 6.4 Error Handling + +### 6.4.1 Abnormal Conditions + +If an ongoing location request is pre-empted at the initiator by an inter-eNB handover and MME relocation, or if the main signalling link to the target UE is released by the MME, or if a main signalling link failure indicated by the serving eNodeB persists for more than a certain timeout interval or if there is a timeout waiting for the positioning response, or any other abnormal conditions for which the positioning procedure cannot be maintained, the MME shall send a LCS-AP Location Abort message to the E-SMLC to terminate the positioning procedure. + +For Intra-MME handovers, the location session between the MME and E-SMLC is not affected. Application layer impacts on these handovers are handled by higher protocol layers. + +If the E-SMLC cannot proceed with positioning due to some protocol violation or error condition (e.g. inter-eNB handover), it shall return a LCS-AP Location Response message to the initiator containing a LCS cause and, optionally, positioning data. + +### 6.4.2 Overload + +If an E-SMLC is in overload condition, it may reject a LCS-AP Location Request by returning a LCS-AP Location Response containing a LCS Cause parameter indicating congestion. The initiator of the location requests (i.e. MME) may reduce the frequency of later location requests until rejection due to overload has ceased. In reducing the frequency of location service requests, the MME shall reduce lower priority requests, to zero if necessary, before reducing the frequency of higher priority requests. An E-SMLC shall similarly reject location requests of a lower priority, to zero if necessary, due to overload before + +rejecting location requests of a higher priority. An E-SMLC in overload condition may optionally employ the following procedures to alleviate overload: + +- a) Allow higher priority location service requests to pre-empt lower priority requests for which location service procedures are already in progress. +- b) Abort lower priority location service requests already in progress. +- c) Reduce the supported QoS for lower priority requests for a location estimate – e.g. by reducing accuracy or increasing response time. +- d) Employ UE based positioning methods, where supported by the target UE and the E-SMLC, rather than UE assisted or network based methods (except TA). + +The priority of a location request shall be defined according to the value in the LCS Priority parameter. If this parameter is absent in a LCS-AP Location Request, the lowest priority shall be assumed. + +# --- 7 LCS-AP Messages and Message Formats + +## 7.1 General + +This section describes the structure of the messages and information elements required for the LCS-AP messages. + +## 7.2 Message Formats + +LCS-AP ASN.1 definition conforms to ITU-T Recommendations ITU-T Recommendation X.680 (07/2002) [8] and ITU-T Recommendation X.681 (07/2002) [9]. The ASN.1 definition specifies the structure and content of LCS-AP messages. The LCS-AP messages may contain any IEs specified in the object set definitions for that message without the order or number of occurrence being restricted by ASN.1. However, for this version of the standard, a sending entity shall construct a LCS-AP message according to the PDU definitions module and with the following additional rules (Note that in the following IE means an IE in the object set with an explicit id. If one IE needed to appear more than once in one object set, then the different occurrences have different IE ids): + +- IEs shall be ordered (in an IE container) in the order they appear in object set definitions. +- Object set definitions specify how many times IEs may appear. An IE shall appear exactly once if the presence field in an object has value "mandatory". An IE may appear at most once if the presence field in an object has value "optional" or "conditional". If in a tabular format there is multiplicity specified for an IE (i.e. an IE list) then in the corresponding ASN.1 definition the list definition is separated into two parts. The first part defines an IE container list where the list elements reside. The second part defines list elements. The IE container list appears as an IE of its own. For this version of the standard an IE container list may contain only one kind of list elements. + +If a LCS-AP message that is not constructed as defined above is received, this shall be considered as Abstract Syntax Error, and the message shall be handled as defined for Abstract Syntax error. + +For the handling of unknown, unforeseen and erroneous protocol data, please refer to 3GPP TS 36.413 [7]. + +## 7.3 LCS-AP Messages + +The following attributes are used for the tabular description of the messages and information elements: Presence, Range Criticality and Assigned Criticality. Their definition and use can be found in 3GPP TS 36.413 [7]. + +### 7.3.1 LCS-AP Location Request message + +This message is sent by the MME to request a location estimate for a target UE and contains sufficient information to enable location according to the required QoS using any positioning method supported. The message is also used to request LCS assistance data transfer to an UE. + +Direction: MME → E-SMLC + +**Table 7.3.1-1: Location Request message contents** + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|---------------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 7.4.2 | | YES | reject | +| Correlation ID | M | | 7.4.28 | | YES | reject | +| Location Type | M | | 7.4.3 | | YES | reject | +| E-UTRAN Cell Identifier | M | | E-CGI / 7.4.4 | | YES | ignore | +| LCS Client Type | O | | 7.4.5 | | YES | reject | +| LCS Priority | O | | 7.4.6 | | YES | reject | +| LCS QoS | O | | 7.4.7 | | YES | reject | +| LCS Service Type ID | O | | 7.4.30 | | YES | ignore | +| UE Positioning Capability | O | | 7.4.8 | | YES | reject | +| Include Velocity | O | | 7.4.9 | | YES | reject | +| IMSI | O | | 7.4.10 | | YES | ignore | +| IMEI | O | | 7.4.11 | | YES | ignore | +| Multiple APDUs | | 0..3 | | | | | +| >APDU | M | | 7.4.18 | | YES | reject | + +NOTE: The IMSI should be sent preferably if known. The IMEI may be sent if the IMSI is not known, or in addition to the IMSI for the purpose of allowing correlation between the two identities. + +### 7.3.2 LCS-AP Location Response message + +This message is sent in response to a LCS-AP Location Request to return a successful location estimate for a target UE or to indicate some failure in obtaining this. The message is also sent in response to a LCS-AP Location Request to return an indication that LCS assistance data has been successfully delivered to an UE. + +Direction: E-SMLC → MME + +**Table 7.3.2-1: Location Response message contents** + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|-------------------------------|----------|-------|--------------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 7.4.2 | | YES | reject | +| Correlation ID | M | | 7.4.28 | | YES | reject | +| Location Estimate | O | | Geographic Area / 7.4.12 | | YES | reject | +| Positioning Data | O | | 7.4.13 | | YES | reject | +| Velocity Estimate | O | | 7.4.14 | | YES | reject | +| Accuracy Fulfilment Indicator | O | | 7.4.15 | | YES | reject | +| LCS Cause | O | | 7.4.16 | | YES | ignore | + +### 7.3.3 LCS-AP Location Abort Request message + +This message is sent by the MME to abort the positioning attempt or the request for assistance data. + +Direction: MME → E-SMLC + +**Table 7.3.3-1: Location Abort Request message contents** + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|----------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 7.4.2 | | YES | reject | +| Correlation ID | M | | 7.4.28 | | YES | reject | +| LCS Cause | M | | 7.4.16 | | YES | ignore | + +### 7.3.4 LCS-AP Connection Oriented Information message + +This message is sent in association with an existing signalling connection between an E-SMLC and another entity to transfer information between the E-SMLC and other entity belonging to a higher level protocol. + +Direction: E-SMLC → MME or MME → E-SMLC + +**Table 7.3.4-1: Connection Oriented Information message contents** + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|----------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 7.4.2 | | YES | reject | +| Correlation ID | M | | 7.4.28 | | YES | reject | +| Payload Type | M | | 7.4.17 | | YES | reject | +| APDU | M | | 7.4.18 | | YES | reject | + +### 7.3.5 LCS-AP Connectionless Information message + +This message conveys signalling information associated with a higher protocol level between an E-SMLC and another entity when there is no existing signalling connection association. + +Direction: E-SMLC → MME or MME → E-SMLC + +**Table 7.3.5-1: Connectionless Information message contents** + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|----------------------|----------|-------|--------------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 7.4.2 | | YES | reject | +| Source Identity | M | | Network Element / 7.4.19 | | YES | reject | +| Destination Identity | M | | Network Element / 7.4.19 | | YES | reject | +| APDU | M | | 7.4.18 | | YES | reject | +| Return Error Request | O | | 7.4.20 | | YES | reject | +| Return Error Cause | O | | 7.4.21 | | YES | ignore | + +### 7.3.6 LCS-AP Reset Request message + +This message is sent to indicate a failure in the sending entity with loss of location service transactions that were established or were being established. + +Direction: E-SMLC → MME or MME → E-SMLC + +**Table 7.3.6-1: Reset Request message contents** + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|---------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 7.4.2 | | YES | reject | +| LCS Cause | M | | 7.4.16 | | YES | ignore | + +### 7.3.7 LCS-AP Reset Acknowledge message + +This message is sent in response to a LCS-AP Reset message to indicate that references and resources associated with location service transactions towards the entity sending the LCS-AP Reset have been released. + +Direction: E-SMLC → MME or MME → E-SMLC + +**Table 7.3.7-1: Reset Acknowledge message contents** + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|---------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 7.4.2 | | YES | reject | + +## 7.4 Information Elements + +### 7.4.1 General + +When specifying information elements which are to be represented by bit strings, if not otherwise specifically stated in the semantics description of the concerned IE or elsewhere, the following principle applies with regards to the ordering of bits: + +- The first bit (leftmost bit) contains the most significant bit (MSB) +- The last bit (rightmost bit) contains the least significant bit (LSB) +- When importing bit strings from other specifications, the first bit of the bit string contains the first bit of the concerned information + +### 7.4.2 Message Type + +The *Message Type* IE uniquely identifies the message being sent. It is mandatory for all messages. + +**Table 7.4.2-1: Message Type** + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|-----------------|----------|-------|-----------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Procedure Code | M | | INTEGER (0..255) | "0" = LCS-AP LOCATION SERVICE REQUEST
"1" = LCS-AP CONNECTION ORIENTED INFORMATION TRANSFER
"2" = LCS-AP CONNECTIONLESS INFORMATION TRANSFER
"3" = LCS-AP LOCATION ABORT
"4" = LCS-AP RESET | +| Type of Message | M | | ENUMERATED
(Initiating Message, Successful Outcome, Unsuccessful Outcome, ...) | | + +### 7.4.3 Location Type + +This parameter defines the type of location information being requested. + +**Table 7.4.3-1: Location Type** + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------|----------|-------|------------------------------------------------------------------|-----------------------| +| Location Type | M | | ENUMERATED
(geographic location, assistance information, ...) | | + +### 7.4.4 E-CGI + +This parameter gives the current cell location of the target UE. The E-UTRAN Cell Global Identifier (ECGI) is used to globally identify a cell. + +**Table 7.4.4-1: ECGI** + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------|----------|-------|-----------------------|--------------------------------------------------------------------------------------| +| PLMN Identity | M | | 7.4.27 | | +| Cell Identity | M | | BIT STRING (28) | The leftmost bits of the Cell Identity correspond to the eNB ID (defined in 7.4.19). | + +### 7.4.5 LCS Client Type + +This parameter defines the type of the originating LCS Client. It shall be included if the Location Type indicates a request for a location estimate and may be included in other cases to assist an SMLC to appropriately prioritize a location request. + +**Table 7.4.5-1: LCS Client Type** + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------|----------|-------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------| +| Client Type | M | | ENUMERATED
(Emergency Services,
Value Added Services,
PLMN Operator
Services, Lawful
Intercept Services,
PLMN Operator -
broadcast services,
PLMN Operator - O&M,
PLMN Operator -
anonymous statistics,
PLMN Operator - Target
MS service support,
...) | Identifies the category of LCS client. | + +### 7.4.6 LCS Priority + +This parameter defines the priority of the location request. + +**Table 7.4.6-1: LCS Priority** + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------|----------|-------|---------------------------|-----------------------------------------------------------------------------------------------------------------------------| +| LCS Priority | M | | OCTET STRING
(SIZE(1)) | 0= highest priority
1= normal priority
all other values treated as 1
For details, refer to 3GPP TS 22.071
[10]. | + +### 7.4.7 LCS QoS + +This parameter provides the required Quality of Service for the LCS Request. Quality of Service may include horizontal accuracy, vertical accuracy and allowed response time. + +**Table 7.4.7-1: LCS QoS** + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------------|----------|-------|---------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Horizontal Accuracy | O | | INTEGER(0..127) | bit 8 = 0
bits 7-1 = 7 bit Uncertainty Code defined in 3GPP TS 23.032 [6].
The horizontal location error should be less than the error indicated by the uncertainty code with 67% confidence. | +| Vertical Requested | O | | ENUMERATED(Vertical Coordinate Is Not Requested (0), Vertical Coordinate Is Requested (1) ) | Default value if this IE is not present is: Vertical Coordinate Is Not Requested (0). | +| Vertical Accuracy | O | | INTEGER(0..127) | bit 8 = 0
bits 7-1 = 7 bit Vertical Uncertainty Code defined in 3GPP TS 23.032 [6].
The vertical location error should be less than the error indicated by the uncertainty code with 67% confidence.
If the vertical requested IE is not present or present with a value of 0, then this vertical accuracy will be ignored, if present. | +| Response Time | O | | ENUMERATED(Low Delay(0), Delay Tolerant (1), ...) | For details, refer to 3GPP TS 22.071 [10]. | + +### 7.4.8 UE Positioning Capability + +This parameter provides information about the LCS capabilities of the target UE. + +**Table 7.4.8-1: UE Positioning Capability** + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|---------------|----------|-------|-----------------------|-----------------------------------------------------------------|-------------|----------------------| +| LPP Support | M | | BOOLEAN | Defines if the UE supports LPP or not.
TRUE means supported. | – | | + +### 7.4.9 Include Velocity + +This parameter indicates if the Velocity of the target UE is requested in the Location Response. + +**Table 7.4.9-1: Include Velocity** + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|--------------------|----------|-------|-------------------------------------------|-----------------------------------------| +| Velocity Indicator | O | | ENUMERATED(requested, not requested, ...) | Specify if Velocity of UE is requested. | + +### 7.4.10 IMSI + +This parameter identifies the IMSI of the target UE. + +**Table 7.4.10-1: IMSI** + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|----------------------|-----------------|--------------|------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------| +| IMSI | M | | OCTET STRING (SIZE (3..8)) | The number of decimal digits shall be from 6 to 15 starting with the digits from the PLMN identity. It is encoded with TBCD String, two digits per octet. | + +### 7.4.11 IMEI + +This parameter identifies the IMEI of the target UE. + +**Table 7.4.11-1: IMEI** + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|----------------------|-----------------|--------------|------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| IMEI | M | | OCTET STRING (SIZE (8)) |

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

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

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

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

Coding of positioning method (bits 8-4):

00000 Cell ID

00001 Reserved

00010 E-CID

00011 Reserved

00100 OTDOA

00101 Reserved

00110 Reserved

00111 Reserved

01000 U-TDOA

01001 Reserved

01010 Reserved

01011 Reserved

01100 to 01111 reserved for other location technologies

10000 to 11111 reserved for network specific positioning methods

Coding of usage (bits 3-1):

000 Attempted unsuccessfully due to failure or interruption - not used.

001 Attempted successfully: results not used to generate location - not used.

010 Attempted successfully: results used to verify but not generate location - not used.

011 Attempted successfully: results used to generate location.

100 Attempted successfully: case where UE supports multiple mobile based positioning methods and the actual method or methods used by the UE cannot be determined.

| +| >GNSS Positioning Data Set | O | | | | + +| | | | | | +|----------------------------------------------|--|-------------------------|---------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| >>GNSS
Positioning
Method and
Usage | | 1..GNSS
Set> | OCTET
STRING (1) |

Coding of Method (Bits 8-7) :

00 : UE-Based
01 : UE-Assisted
10 : Conventional
11 : Reserved

Coding of GNSS ID (Bits 6-4) :

000 : GPS
001 : Galileo
010 : SBAS
011 : Modernized GPS
100 : QZSS
101 : GLONASS
other values reserved

Coding of usage (bits 3-1):

000 Attempted unsuccessfully due to failure or interruption

001 Attempted successfully: results not used to generate location

010 Attempted successfully: results used to verify but not generate location

011 Attempted successfully: results used to generate location

100 Attempted successfully: case where UE supports multiple mobile based positioning methods and the actual method or methods used by the UE cannot be determined.

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

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

  • -a filler digit plus 2 digits from MNC (in case of 2 digit MNC) or
  • -3 digits from MNC (in case of a 3 digit MNC).
| + +### 7.4.28 Correlation ID + +This IE indicates a specific location session. It is used in order to correlate request/response and an ongoing location session. + +**Table 7.4.28-1: Correlation ID** + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|----------------|----------|-------|-------------------------|-----------------------------------------------------------------------------------------------------------------------------------------| +| Correlation ID | M | | OCTET STRING (SIZE (4)) | The identifier of a location session in E-UTRAN. It should be unique for all concurrently active location sessions in a particular MME. | + +### 7.4.29 eNB ID + +This information element is used to identify an eNB. + +**Table 7.4.29-1: eNB ID** + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------|----------|-------|-----------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------| +| CHOICE eNB ID | | | | | +| >Macro eNB ID | M | | BIT STRING (20) | Equal to the 20 leftmost bits of the Cell Identity IE contained in the E-UTRAN CGI IE (see section 7.4.4) of each cell served by the eNB | +| >Home eNB ID | M | | BIT STRING (28) | Equal to the Cell Identity IE contained in the E-UTRAN CGI IE (see section 7.4.4) of the cell served by the eNB | + +### 7.4.30 LCS Service Type ID + +This parameter defines the service type ID for the location request. + +Table 7.4.30-1: LCS Service Type ID + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------------|----------|-------|-----------------------|-------------------------------------------------------------------------------------------------------------------------| +| LCS Service Type ID | O | | INTEGER(0..127) | Identifies the type of service requested. The meaning of the different service types is defined in 3GPP TS 22.071 [10]. | + +## 7.5 Message and information element abstract syntax + +### 7.5.1 General + +LCS-AP ASN.1 definition conforms to [8] and [9]. + +The ASN.1 definition specifies the structure and content of LCS-AP messages. LCS-AP messages can contain any IEs specified in the object set definitions for that message without the order or number of occurrence being restricted by ASN.1. However, for this version of the standard, a sending entity shall construct a LCS-AP message according to the PDU definitions module and with the following additional rules (Note that in the following IE means an IE in the object set with an explicit id. If one IE needed to appear more than once in one object set, then the different occurrences have different IE ids): + +- IEs shall be ordered (in an IE container) in the order they appear in object set definitions. +- Object set definitions specify how many times IEs may appear. An IE shall appear exactly once if the presence field in an object has value "mandatory". An IE may appear at most once if the presence field in an object has value "optional" or "conditional". If in a tabular format there is multiplicity specified for an IE (i.e. an IE list) then in the corresponding ASN.1 definition the list definition is separated into two parts. The first part defines an IE container list where the list elements reside. The second part defines list elements. The IE container list appears as an IE of its own. For this version of the standard an IE container list may contain only one kind of list elements. + +If a LCS-AP message that is not constructed as defined above is received, this shall be considered as Abstract Syntax Error, and the message shall be handled as defined for Abstract Syntax error in clause 10 of [7]. + +### 7.5.2 Usage of protocol extension mechanism for non-standard use + +The protocol extension mechanism for non-standard use may be used: + +- for special operator- (and/or vendor) specific features considered not to be part of the basic functionality, i.e. the functionality required for a complete and high-quality specification in order to guarantee multi-vendor interoperability. +- by vendors for research purposes, e.g. to implement and evaluate new algorithms/features before such features are proposed for standardisation. + +The extension mechanism shall not be used for basic functionality. Such functionality shall be standardised. + +### 7.5.3 Elementary procedure definitions + +``` +-- ***** +-- +-- Elementary Procedure definitions +-- +-- ***** +``` + +``` +LCS-AP-PDU-Descriptions { + itu-t (0) identified-organization (4) etsi (0) mobileDomain (0) + eps-Access (21) modules (3) lcs-AP (4) version1 (1) lcs-AP-PDU-Descriptions (0)} +``` + +``` +DEFINITIONS AUTOMATIC TAGS ::= +``` + +``` +BEGIN +``` + +``` +-- ***** +-- +-- IE parameter types from other modules. +``` + +``` + +-- +-- ****************************************************************************** + +IMPORTS + Criticality, + ProcedureCode +FROM LCS-AP-CommonDataTypes + + Location-Request, + Location-Response, + Location-Abort-Request, + Connection-Oriented-Information, + Connectionless-Information, + Reset-Request, + Reset-Acknowledge +FROM LCS-AP-PDU-Contents + + id-Location-Service-Request, + id-Connection-Oriented-Information-Transfer, + id-Connectionless-Information-Transfer, + id-Location-Abort, + id-Reset +FROM LCS-AP-Constants; + +-- ****************************************************************************** +-- +-- Interface Elementary Procedure Class +-- +-- ****************************************************************************** + +LCS-AP-ELEMENTARY-PROCEDURE ::= CLASS { + &InitiatingMessage, + &SuccessfulOutcome OPTIONAL, + &UnsuccessfulOutcome OPTIONAL, + &procedureCode ProcedureCode UNIQUE, + &criticality Criticality DEFAULT ignore +} +WITH SYNTAX { + INITIATING MESSAGE &InitiatingMessage + [SUCCESSFUL OUTCOME &SuccessfulOutcome] + [UNSUCCESSFUL OUTCOME &UnsuccessfulOutcome] + PROCEDURE CODE &procedureCode + [CRITICALITY &criticality] +} + +-- ****************************************************************************** +-- +-- Interface PDU Definition +-- +-- ****************************************************************************** + +LCS-AP-PDU ::= CHOICE { + initiatingMessage InitiatingMessage, + successfulOutcome SuccessfulOutcome, + unsuccessfulOutcome UnsuccessfulOutcome, + ... +} + +InitiatingMessage ::= SEQUENCE { + procedureCode LCS-AP-ELEMENTARY-PROCEDURE.&procedureCode ({LCS-AP-ELEMENTARY-PROCEDURES}), + criticality LCS-AP-ELEMENTARY-PROCEDURE.&criticality ({LCS-AP-ELEMENTARY-PROCEDURES}{@procedureCode}), + value LCS-AP-ELEMENTARY-PROCEDURE.&InitiatingMessage ({LCS-AP-ELEMENTARY-PROCEDURES}{@procedureCode}) +} + +SuccessfulOutcome ::= SEQUENCE { + procedureCode LCS-AP-ELEMENTARY-PROCEDURE.&procedureCode ({LCS-AP-ELEMENTARY-PROCEDURES}), + criticality LCS-AP-ELEMENTARY-PROCEDURE.&criticality ({LCS-AP-ELEMENTARY-PROCEDURES}{@procedureCode}), + value LCS-AP-ELEMENTARY-PROCEDURE.&SuccessfulOutcome ({LCS-AP-ELEMENTARY-PROCEDURES}{@procedureCode}) +} + +UnsuccessfulOutcome ::= SEQUENCE { + procedureCode LCS-AP-ELEMENTARY-PROCEDURE.&procedureCode ({LCS-AP-ELEMENTARY-PROCEDURES}), + criticality LCS-AP-ELEMENTARY-PROCEDURE.&criticality ({LCS-AP-ELEMENTARY-PROCEDURES}{@procedureCode}), + value LCS-AP-ELEMENTARY-PROCEDURE.&UnsuccessfulOutcome ({LCS-AP-ELEMENTARY-PROCEDURES}{@procedureCode}) +} + +``` + +``` + + criticality LCS-AP-ELEMENTARY-PROCEDURE.&criticality ({LCS-AP-ELEMENTARY- +PROCEDURES}{@procedureCode}), + value LCS-AP-ELEMENTARY-PROCEDURE.&UnsuccessfulOutcome ({LCS-AP-ELEMENTARY- +PROCEDURES}{@procedureCode}) +} + +``` + +``` + +-- ****************************************************************************** +-- +-- Interface Elementary Procedure List +-- +-- ****************************************************************************** + +``` + +``` + +LCS-AP-ELEMENTARY-PROCEDURES LCS-AP-ELEMENTARY-PROCEDURE ::= { + LCS-AP-ELEMENTARY-PROCEDURES-CLASS-1 | + LCS-AP-ELEMENTARY-PROCEDURES-CLASS-2 , + ... +} + +``` + +``` + +LCS-AP-ELEMENTARY-PROCEDURES-CLASS-1 LCS-AP-ELEMENTARY-PROCEDURE ::= { + location-Service-Request | + connectionless-Information-Transfer | + location-Abort | + reset , + ... +} + +``` + +``` + +LCS-AP-ELEMENTARY-PROCEDURES-CLASS-2 LCS-AP-ELEMENTARY-PROCEDURE ::= { + connection-Oriented-Information-Transfer , + ... +} + +``` + +``` + +-- ****************************************************************************** +-- +-- Interface Elementary Procedures +-- +-- ****************************************************************************** + +``` + +``` + +location-Service-Request LCS-AP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE Location-Request + SUCCESSFUL OUTCOME Location-Response + UNSUCCESSFUL OUTCOME Location-Response + PROCEDURE CODE id-Location-Service-Request + CRITICALITY reject +} + +``` + +``` + +connection-Oriented-Information-Transfer LCS-AP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE Connection-Oriented-Information + PROCEDURE CODE id-Connection-Oriented-Information-Transfer + CRITICALITY reject +} + +``` + +``` + +connectionless-Information-Transfer LCS-AP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE Connectionless-Information + UNSUCCESSFUL OUTCOME Connectionless-Information + PROCEDURE CODE id-Connectionless-Information-Transfer + CRITICALITY reject +} + +``` + +``` + +location-Abort LCS-AP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE Location-Abort-Request + SUCCESSFUL OUTCOME Location-Response + PROCEDURE CODE id-Location-Abort + CRITICALITY reject +} + +``` + +``` + +reset LCS-AP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE Reset-Request + SUCCESSFUL OUTCOME Reset-Acknowledge + PROCEDURE CODE id-Reset + CRITICALITY reject +} + +``` + +END + +### 7.5.4 PDU definitions + +``` + +-- ***** +-- +-- PDU definitions for LCS-AP. +-- +-- ***** + +LCS-AP-PDU-Contents { + itu-t (0) identified-organization (4) etsi (0) mobileDomain (0) + eps-Access (21) modules (3) lcs-AP (4) version1 (1) lcs-AP-PDU-Contents (1)} + +DEFINITIONS AUTOMATIC TAGS ::= + +BEGIN + +-- ***** +-- +-- IE parameter types from other modules. +-- +-- ***** + +IMPORTS + + APDU, + Accuracy-Fulfillment-Indicator, + Correlation-ID, + E-CGI, + Geographical-Area, + IMSI, + IMEI, + Include-Velocity, + LCS-Cause, + LCS-Client-Type, + LCS-Service-Type-ID, + LCS-Priority, + LCS-QoS, + Location-Type, + MultipleAPDUs, + Network-Element, + Payload-Type, + Positioning-Data, + Return-Error-Type, + Return-Error-Cause, + UE-Positioning-Capability, + Velocity-Estimate +FROM LCS-AP-IEs + + ProtocolExtensionContainer{}, + ProtocolIE-Container{}, + LCS-AP-PROTOCOL-EXTENSION, + LCS-AP-PROTOCOL-IEs +FROM LCS-AP-Containers + + id-Accuracy-Fulfillment-Indicator, + id-APDU, + id-Correlation-ID, + id-Destination-ID, + id-E-UTRAN-Cell-Identifier, + id-Include-Velocity, + id-IMEI, + id-IMSI, + id-LCS-Client-Type, + id-LCS-Priority, + id-LCS-QoS, + id-LCS-Cause, + id-LCS-Service-Type-ID, + id-Location-Estimate, + id-Location-Type, + id-MultipleAPDUs, + id-Payload-Type, + id-Positioning-Data, + id-Return-Error-Request, + id-Return-Error-Cause, + id-Source-Identity, + id-UE-Positioning-Capability, + id-Velocity-Estimate +FROM LCS-AP-Constants; + +``` + +``` + +-- ***** +-- +-- Location-Request +-- +-- ***** + +Location-Request ::= SEQUENCE { + protocolIEs ProtocolIE-Container { { Location-Request-IEs} }, + protocolExtensions ProtocolExtensionContainer { { Location-Request-Extensions} } OPTIONAL, + ... +} + +Location-Request-IEs LCS-AP-PROTOCOL-IES ::= { + { ID id-Correlation-ID CRITICALITY reject TYPE Correlation-ID PRESENCE +mandatory } | + { ID id-Location-Type CRITICALITY reject TYPE Location-Type PRESENCE +mandatory } | + { ID id-E-UTRAN-Cell-Identifier CRITICALITY ignore TYPE E-CGI PRESENCE +mandatory } | + { ID id-LCS-Client-Type CRITICALITY reject TYPE LCS-Client-Type PRESENCE +optional } | + { ID id-LCS-Priority CRITICALITY reject TYPE LCS-Priority PRESENCE +optional } | + { ID id-LCS-QoS CRITICALITY reject TYPE LCS-QoS PRESENCE +optional } | + { ID id-UE-Positioning-Capability CRITICALITY reject TYPE UE-Positioning-Capability PRESENCE +optional } | + { ID id-Include-Velocity CRITICALITY reject TYPE Include-Velocity PRESENCE +optional } | + { ID id-IMSI CRITICALITY ignore TYPE IMSI PRESENCE +optional } | + { ID id-IMEI CRITICALITY ignore TYPE IMEI PRESENCE +optional } | + { ID id-MultipleAPDUs CRITICALITY reject TYPE MultipleAPDUs PRESENCE +optional } , + ... +} + +Location-Request-Extensions LCS-AP-PROTOCOL-EXTENSION ::= { + { ID id-LCS-Service-Type-ID CRITICALITY ignore EXTENSION LCS-Service-Type-ID +PRESENCE optional } , + ... +} + +-- ***** +-- +-- Location-Response +-- +-- ***** + +Location-Response ::= SEQUENCE { + protocolIEs ProtocolIE-Container { { Location-Response-IEs} }, + protocolExtensions ProtocolExtensionContainer { { Location-Response-Extensions} } OPTIONAL, + ... +} + +Location-Response-IEs LCS-AP-PROTOCOL-IES ::= { + { ID id-Correlation-ID CRITICALITY reject TYPE Correlation-ID +PRESENCE mandatory } | + { ID id-Location-Estimate CRITICALITY reject TYPE Geographical-Area +PRESENCE optional } | + { ID id-Positioning-Data CRITICALITY reject TYPE Positioning-Data +PRESENCE optional } | + { ID id-Velocity-Estimate CRITICALITY reject TYPE Velocity-Estimate +PRESENCE optional } | + { ID id-Accuracy-Fulfillment-Indicator CRITICALITY reject TYPE Accuracy-Fulfillment-Indicator +PRESENCE optional } | + { ID id-LCS-Cause CRITICALITY ignore TYPE LCS-Cause +PRESENCE optional } , + ... +} + +Location-Response-Extensions LCS-AP-PROTOCOL-EXTENSION ::= { + ... +} + +``` + +``` + +-- -- +} + +-- ***** +-- +-- Location-Abort +-- +-- ***** + +Location-Abort-Request ::= SEQUENCE { + protocolIEs ProtocolIE-Container { {Location-Abort-Request-IEs} }, + protocolExtensions ProtocolExtensionContainer { {Location-Abort-Request-Extensions} } OPTIONAL, + ... +} + +Location-Abort-Request-IEs LCS-AP-PROTOCOL-IES ::= { + { ID id-Correlation-ID CRITICALITY reject TYPE Correlation-ID PRESENCE +mandatory } | + { ID id-LCS-Cause CRITICALITY ignore TYPE LCS-Cause PRESENCE +mandatory } , + ... +} + +Location-Abort-Request-Extensions LCS-AP-PROTOCOL-EXTENSION ::= { + ... +} + +-- ***** +-- +-- Connection-Oriented-Information +-- +-- ***** + +Connection-Oriented-Information ::= SEQUENCE { + protocolIEs ProtocolIE-Container { {Connection-Oriented-Information-IEs} }, + protocolExtensions ProtocolExtensionContainer { {Connection-Oriented-Information-Extensions} } +OPTIONAL, + ... +} + +Connection-Oriented-Information-IEs LCS-AP-PROTOCOL-IES ::= { + { ID id-Correlation-ID CRITICALITY reject TYPE Correlation-ID PRESENCE optional } | + { ID id-Payload-Type CRITICALITY reject TYPE Payload-Type PRESENCE optional } | + { ID id-APDU CRITICALITY reject TYPE APDU PRESENCE optional } , + ... +} + +Connection-Oriented-Information-Extensions LCS-AP-PROTOCOL-EXTENSION ::= { + ... +} + +-- ***** +-- +-- Connectionless-Information +-- +-- ***** + +Connectionless-Information ::= SEQUENCE { + protocolIEs ProtocolIE-Container { {Connectionless-Information-IEs} }, + protocolExtensions ProtocolExtensionContainer { {Connectionless-Information-Extensions} } +OPTIONAL, + ... +} + +Connectionless-Information-IEs LCS-AP-PROTOCOL-IES ::= { + { ID id-Source-Identity CRITICALITY reject TYPE Network-Element PRESENCE mandatory } +| + { ID id-Destination-ID CRITICALITY reject TYPE Network-Element PRESENCE mandatory } +| + { ID id-APDU CRITICALITY reject TYPE APDU PRESENCE mandatory } +| + { ID id-Return-Error-Request CRITICALITY reject TYPE Return-Error-Type PRESENCE optional } +| + { ID id-Return-Error-Cause CRITICALITY ignore TYPE Return-Error-Cause PRESENCE optional } +, + ... +} + +``` + +``` + +Connectionless-Information-Extensions LCS-AP-PROTOCOL-EXTENSION ::= { + ... +} + +-- ***** +-- +-- Reset-Request +-- +-- ***** + +Reset-Request ::= SEQUENCE { + protocolIEs ProtocolIE-Container { {Reset-Request-IEs} }, + protocolExtensions ProtocolExtensionContainer { {Reset-Request-Extensions} } OPTIONAL, + ... +} + +Reset-Request-IEs LCS-AP-PROTOCOL-IES ::= { + { ID id-LCS-Cause CRITICALITY ignore TYPE LCS-Cause PRESENCE mandatory } , + ... +} + +Reset-Request-Extensions LCS-AP-PROTOCOL-EXTENSION ::= { + ... +} + +-- ***** +-- +-- Reset-Acknowledge +-- +-- ***** + +Reset-Acknowledge ::= SEQUENCE { + protocolIEs ProtocolIE-Container { { Reset-Acknowledge-IEs} }, + protocolExtensions ProtocolExtensionContainer { { Reset-Acknowledge-Extensions} } OPTIONAL, + ... +} + +Reset-Acknowledge-IEs LCS-AP-PROTOCOL-IES ::= { + ... +} + +Reset-Acknowledge-Extensions LCS-AP-PROTOCOL-EXTENSION ::= { + ... +} + +END + +``` + +### 7.5.5 Information element definitions + +``` + +-- ***** +-- +-- Information Element Definitions +-- +-- ***** + +LCS-AP-IEs { + itu-t (0) identified-organization (4) etsi (0) mobileDomain (0) + eps-Access (21) modules (3) lcs-AP (4) version1 (1) lcs-AP-IEs (2)} + +DEFINITIONS AUTOMATIC TAGS ::= + +BEGIN + +IMPORTS + + max-No-Of-Points, + max-Set, + max-GNSS-Set +FROM LCS-AP-Constants + + Criticality, + +``` + +``` + + ProcedureCode, + TriggeringMessage, + ProtocolIE-ID +FROM LCS-AP-CommonDataTypes + + ProtocolExtensionContainer {}, + LCS-AP-PROTOCOL-EXTENSION +FROM LCS-AP-Containers; + +-- A + +APDU ::= OCTET STRING + +Accuracy-Fulfillment-Indicator ::= ENUMERATED { + requested-accuracy-fulfilled, + requested-accuracy-not-fulfilled, + ... +} + +Altitude ::= INTEGER (0..65535) +-- The valid value for this IE is 0 to 32767. +-- Reception of value greater than 32767 shall be mapped to the value 32767. + +Altitude-And-Direction ::= SEQUENCE { + direction-Of-Altitude Direction-Of-Altitude, + altitude Altitude, + ... +} + +Angle ::= INTEGER (0..179) + +-- B + +Bearing ::= INTEGER (0..359) + +-- C + +CellIdentity ::= BIT STRING (SIZE (28)) + +Confidence ::= INTEGER (0..100) + +Correlation-ID ::= OCTET STRING (SIZE (4)) + +-- D + +DegreesLatitude ::= INTEGER (0..8388607) -- 23 bit field + +DegreesLongitude ::= INTEGER (-8388608..8388607) -- 24 bit field + +Direction-Of-Altitude ::= ENUMERATED { + height, + depth +} + +-- E + +E-CGI ::= SEQUENCE { + pLMNidentity PLMN-ID, + cell-ID CellIdentity, + iE-Extensions ProtocolExtensionContainer { { E-CGI-ExtIEs} } OPTIONAL, + ... +} + +E-CGI-ExtIEs LCS-AP-PROTOCOL-EXTENSION ::= { + ... +} + +Ellipsoid-Point-With-Uncertainty-Ellipse ::= SEQUENCE { + geographical-Coordinates Geographical-Coordinates, + uncertainty-Ellipse Uncertainty-Ellipse, + confidence Confidence, +} + +``` + +``` + + iE-Extensions ProtocolExtensionContainer { { Ellipsoid-Point-With-Uncertainty-Ellipse- +ExtIEs } } OPTIONAL, + ... } + +Ellipsoid-Point-With-Uncertainty-Ellipse-ExtIEs LCS-AP-PROTOCOL-EXTENSION ::= { + ... +} + +Ellipsoid-Point-With-Altitude ::= SEQUENCE { + geographical-Coordinates Geographical-Coordinates, + altitude-And-Direction Altitude-And-Direction, + iE-Extensions ProtocolExtensionContainer { { Ellipsoid-Point-With-Altitude-ExtIEs } } +OPTIONAL, + ... } + +Ellipsoid-Point-With-Altitude-ExtIEs LCS-AP-PROTOCOL-EXTENSION ::= { + ... +} + +Ellipsoid-Point-With-Altitude-And-Uncertainty-Ellipsoid ::= SEQUENCE { + geographical-Coordinates Geographical-Coordinates, + altitude-And-Direction Altitude-And-Direction, + uncertainty-Ellipse Uncertainty-Ellipse, + uncertainty-Altitude Uncertainty-Altitude, + confidence Confidence, + iE-Extensions ProtocolExtensionContainer { { Ellipsoid-Point-With-Altitude-And- +Uncertainty-Ellipsoid-ExtIEs } } OPTIONAL, + ... } + +Ellipsoid-Point-With-Altitude-And-Uncertainty-Ellipsoid-ExtIEs LCS-AP-PROTOCOL-EXTENSION ::= { + ... +} + +Ellipsoid-Arc ::= SEQUENCE { + geographical-Coordinates Geographical-Coordinates, + inner-Radius Inner-Radius, + uncertainty-Radius Uncertainty-Code, + offset-Angle Angle, + included-Angle Angle, + confidence Confidence, + iE-Extensions ProtocolExtensionContainer { { Ellipsoid-Arc-ExtIEs } } OPTIONAL, + ... +} + +Ellipsoid-Arc-ExtIEs LCS-AP-PROTOCOL-EXTENSION ::= { + ... +} + +ENB-ID ::= CHOICE { + macro-eNB-ID Macro-eNB-ID, + home-eNB-ID Home-eNB-ID, + ... +} + +E-SMLC-ID ::= INTEGER (0..255) + +-- F +-- G + +Geographical-Area ::= CHOICE { + point Point, + point-With-Uncertainty Point-With-Uncertainty, + ellipsoidPoint-With-Uncertainty-Ellipse Ellipsoid-Point-With-Uncertainty-Ellipse, + polygon Polygon, + ellipsoid-Point-With-Altitude Ellipsoid-Point-With-Altitude, + ellipsoid-Point-With-Altitude-And-Uncertainty-Ellipsoid Ellipsoid-Point-With-Altitude-And- +Uncertainty-Ellipsoid, + ellipsoid-Arc Ellipsoid-Arc, + ... +} + +``` + +``` + +Geographical-Coordinates := SEQUENCE { + latitudeSign LatitudeSign, + degreesLatitude DegreesLatitude, + degreesLongitude DegreesLongitude, + iE-Extensions ProtocolExtensionContainer { {Geographical-Coordinates-ExtIEs} } OPTIONAL, + ... +} + +Geographical-Coordinates-ExtIEs LCS-AP-PROTOCOL-EXTENSION := { + ... +} + +Global-eNB-ID := SEQUENCE { + pLMN-ID PLMN-ID, + eNB-ID ENB-ID +} + +GNSS-Positioning-Method-And-Usage := OCTET STRING (SIZE (1)) + +GNSS-Positioning-Data-Set := SEQUENCE (SIZE (1..max-GNSS-Set)) OF GNSS-Positioning-Method-And-Usage + +-- H + +Home-eNB-ID := BIT STRING (SIZE (28)) + +Horizontal-Accuracy := INTEGER (0..127) + +Horizontal-Speed-And-Bearing := SEQUENCE { + bearing INTEGER (0..359), + horizontal-Speed INTEGER (0..2047) +} + +Horizontal-Velocity := SEQUENCE { + horizontal-Speed-And-Bearing Horizontal-Speed-And-Bearing, + iE-Extensions ProtocolExtensionContainer { { Horizontal-Velocity-ExtIEs} } OPTIONAL, + ... +} + +Horizontal-Velocity-ExtIEs LCS-AP-PROTOCOL-EXTENSION := { + ... +} + +Horizontal-With-Vertical-Velocity := SEQUENCE { + horizontal-Speed-And-Bearing Horizontal-Speed-And-Bearing, + vertical-Velocity Vertical-Velocity, + iE-Extensions ProtocolExtensionContainer { { Horizontal-With-Vertical-Velocity-ExtIEs} } OPTIONAL, + ... +} + +Horizontal-With-Vertical-Velocity-ExtIEs LCS-AP-PROTOCOL-EXTENSION := { + ... +} + +Horizontal-Velocity-With-Uncertainty := SEQUENCE { + horizontal-Speed-And-Bearing Horizontal-Speed-And-Bearing, + uncertainty-Speed INTEGER (0..255), + iE-Extensions ProtocolExtensionContainer { { Horizontal-Velocity-With-Uncertainty-ExtIEs} } OPTIONAL, + ... +} + +Horizontal-Velocity-With-Uncertainty-ExtIEs LCS-AP-PROTOCOL-EXTENSION := { + ... +} + +Horizontal-With-Vertical-Velocity-And-Uncertainty := SEQUENCE { + horizontal-Speed-And-Bearing Horizontal-Speed-And-Bearing, + vertical-Velocity Vertical-Velocity, + horizontal-Uncertainty-Speed INTEGER (0..255), + vertical-Uncertainty-Speed INTEGER (0..255), +} + +``` + +... -f + +... -f + +``` + + iE-Extensions + And-Uncertainty-ExtIEs } OPTIONAL, + ... + } + +``` + +``` + +Horizontal-With-Vertical-Velocity-And-Uncertainty-ExtIEs LCS-AP-PROTOCOL-EXTENSION ::= { + ... +} + +``` + +-- I + +``` + +IMSI ::= OCTET STRING (SIZE (3..8)) + +``` + +``` + +IMEI ::= OCTET STRING (SIZE (8)) + +``` + +``` + +Include-Velocity ::= ENUMERATED { + requested, + not-Requested, + ... +} + +``` + +``` + +Inner-Radius ::= INTEGER (0..65535) -- 16 bit field + +``` + +-- J + +-- K + +-- L + +``` + +LatitudeSign ::= ENUMERATED { + north, + south +} + +``` + +``` + +Location-Type ::= ENUMERATED { + geographic-Information, + assistance-Information, + ... +} + +``` + +``` + +LCS-Cause ::= CHOICE { + radio-Network-Layer Radio-Network-Layer-Cause, + transport-Layer Transport-Layer-Cause, + protocol Protocol-Cause, + misc Misc-Cause +} + +``` + +``` + +LCS-Client-Type ::= ENUMERATED { + emergency-Services, + value-Added-Services, + pLMN-Operator-Services, + lawful-Intercept-Services, + pLMN-Operator-broadcast-Services, + pLMN-Operator-OM, + pLMN-Operator-Anonymous-Statistics, + pLMN-Operator-Target-MS-Service-Support, + ... +} + +``` + +``` + +LCS-Priority ::= OCTET STRING (SIZE (1)) + +``` + +``` + +LCS-QoS ::= SEQUENCE { + horizontal-Accuracy Horizontal-Accuracy OPTIONAL, + vertical-Requested Vertical-Requested OPTIONAL, + vertical-Accuracy Vertical-Accuracy OPTIONAL, + response-Time Response-Time OPTIONAL, + ... +} + +``` + +``` + +LCS-Service-Type-ID ::= INTEGER (0..127) + +``` + +----- + +----- + +-- M + +Macro-eNB-ID ::= BIT STRING (SIZE (20)) + +Message-Identifier ::= BIT STRING (SIZE (16)) + +``` +Misc-Cause ::= ENUMERATED { + processing-Overload, + hardware-Failure, + o-And-M-Intervention, + unspecified, + ... +} +``` + +MultipleAPDUs ::= SEQUENCE (SIZE (1.. 3)) OF APDU + +-- N + +``` +Network-Element ::= CHOICE { + global-eNB-ID Global-eNB-ID, + e-SMLC-ID E-SMLC-ID +} +``` + +-- O + +Orientation-Major-Axis ::= INTEGER (0..89) + +-- P + +``` +Payload-Type ::= ENUMERATED { + lPP, + lPPa, + ... +} +``` + +PLMN-ID ::= TBCD-STRING + +``` +Point ::= SEQUENCE { + geographical-Coordinates Geographical-Coordinates, + iE-Extensions ProtocolExtensionContainer { {Point-ExtIEs} } OPTIONAL, + ... +} +``` + +``` +Point-ExtIEs LCS-AP-PROTOCOL-EXTENSION ::= { + ... +} +``` + +``` +Point-With-Uncertainty ::= SEQUENCE { + geographical-Coordinates Geographical-Coordinates, + uncertainty-Code Uncertainty-Code, + iE-Extensions ProtocolExtensionContainer { {Point-With-Uncertainty-ExtIEs} } OPTIONAL, + ... +} +``` + +``` +Point-With-Uncertainty-ExtIEs LCS-AP-PROTOCOL-EXTENSION ::= { + ... +} +``` + +Polygon ::= SEQUENCE (SIZE (1..max-No-Of-Points)) OF Polygon-Point + +``` +Polygon-Point ::= SEQUENCE { + geographical-Coordinates Geographical-Coordinates, + iE-Extensions ProtocolExtensionContainer { {Polygon-Point-ExtIEs} } OPTIONAL, + ... +} +``` + +``` +Polygon-Point-ExtIEs LCS-AP-PROTOCOL-EXTENSION ::= { + ... +} +``` + +``` +Positioning-Data ::= SEQUENCE { + positioning-Data-Set Positioning-Data-Set OPTIONAL, + gNSS-Positioning-Data-Set GNSS-Positioning-Data-Set OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { Positioning-Data-ExtIEs} } OPTIONAL, + ... +} +``` + +... -f + +... -f + +} + +Positioning-Data-ExtIEs LCS-AP-PROTOCOL-EXTENSION ::= { + ... +} + +Positioning-Data-Set ::= SEQUENCE (SIZE (1..max-Set)) OF Positioning-Method-And-Usage + +Positioning-Method-And-Usage ::= OCTET STRING (SIZE (1)) + +Protocol-Cause ::= ENUMERATED { + transfer-Syntax-Error, + abstract-Syntax-Error-Reject, + abstract-Syntax-Error-Ignore-And-Notify, + message-Not-Compatible-With-Receiver-State, + semantic-Error, + unspecified, + abstract-Syntax-Error, + ... +} + +-- Q + +-- R + +Radio-Network-Layer-Cause ::= ENUMERATED { + unspecified, + ... +} + +Response-Time ::= ENUMERATED { + low-Delay(0), + delay-Tolerant(1), + ... +} + +Return-Error-Type ::= ENUMERATED { + yes, + no +} + +Return-Error-Cause ::= ENUMERATED { + system-Failure, + protocol-Error, + destination-Unknown, + destination-Unreachable, + congestion, + ... +} + +-- S + +-- T + +TBCD-STRING ::= OCTET STRING (SIZE (3)) + +Transport-Layer-Cause ::= ENUMERATED { + transport-Resource-Unavailable, + unspecified, + ... +} + +-- U + +Uncertainty-Altitude ::= INTEGER (0..127) + +Uncertainty-Code ::= INTEGER (0..127) + +Uncertainty-Ellipse ::= SEQUENCE { + uncertainty-SemiMajor            Uncertainty-Code, + uncertainty-SemiMinor            Uncertainty-Code, + orientation-Major-Axis            Orientation-Major-Axis +} + +UE-Positioning-Capability ::= SEQUENCE { + lPP                                    BOOLEAN, + ... +} + +-- V + +``` + +Velocity-Estimate ::= CHOICE { + horizontal-Velocity Horizontal-Velocity, + horizontal-With-Vertical-Velocity Horizontal-With-Vertical-Velocity, + horizontal-Velocity-With-Uncertainty Horizontal-Velocity-With-Uncertainty, + horizontal-With-Vertical-Velocity-And-Uncertainty Horizontal-With-Vertical-Velocity-And-Uncertainty, + ... +} + +Vertical-Requested ::= ENUMERATED { + vertical-coordinate-Is-Not-Requested(0), + vertical-coordinate-Is-Requested(1) +} + +Vertical-Accuracy ::= INTEGER (0..127) + +Vertical-Velocity ::= SEQUENCE { + vertical-Speed INTEGER (0..255), + vertical-Speed-Direction Vertical-Speed-Direction +} + +Vertical-Speed-Direction ::= ENUMERATED { + upward, + downward +} + +-- W +-- X +-- Y + +END + +``` + +### 7.5.6 Common definitions + +``` + +-- ***** +-- +-- Common definitions +-- +-- ***** + +LCS-AP-CommonDataTypes { + itu-t (0) identified-organization (4) etsi (0) mobileDomain (0) + eps-Access (21) modules (3) lcs-AP (4) version1 (1) lcs-AP-CommonDataTypes (3)} + +DEFINITIONS AUTOMATIC TAGS ::= + +BEGIN + +Criticality ::= ENUMERATED { reject, ignore, notify } + +Presence ::= ENUMERATED { optional, conditional, mandatory } + +ProcedureCode ::= INTEGER (0..255) + +ProtocolExtensionID ::= INTEGER (0..65535) + +ProtocolIE-ID ::= INTEGER (0..65535) + +TriggeringMessage ::= ENUMERATED {initiating-message, successful-outcome, unsuccessful-outcome, +outcome} + +END + +``` + +### 7.5.7 Constant definitions + +``` + +-- ***** +-- +-- Constant definitions +-- +-- ***** + +LCS-AP-Constants { + +``` + +text of + +document. + +itu-t (0) identified-organization (4) etsi (0) mobileDomain (0) +eps-Access (21) modules (3) lcs-AP (4) version1 (1) lcs-AP-Constants (4)} + +DEFINITIONS AUTOMATIC TAGS ::= + +BEGIN + +``` + +-- ****************************************************************************** +-- +-- Elementary Procedures +-- +-- ****************************************************************************** + +``` + +``` + +id-Location-Service-Request INTEGER ::= 0 +id-Connection-Oriented-Information-Transfer INTEGER ::= 1 +id-Connectionless-Information-Transfer INTEGER ::= 2 +id-Location-Abort INTEGER ::= 3 +id-Reset INTEGER ::= 4 + +``` + +``` + +-- ****************************************************************************** +-- +-- IEs +-- +-- ****************************************************************************** + +``` + +``` + +id-Accuracy-Fulfillment-Indicator INTEGER ::= 0 +id-APDU INTEGER ::= 1 +id-Correlation-ID INTEGER ::= 2 +id-Destination-ID INTEGER ::= 3 +id-E-UTRAN-Cell-Identifier INTEGER ::= 4 +id-Include-Velocity INTEGER ::= 5 +id-IMEI INTEGER ::= 6 +id-IMSI INTEGER ::= 7 +id-LCS-Client-Type INTEGER ::= 8 +id-LCS-Priority INTEGER ::= 9 +id-LCS-QOS INTEGER ::= 10 +id-LCS-Cause INTEGER ::= 11 +id-Location-Estimate INTEGER ::= 12 +id-Location-Type INTEGER ::= 13 +id-MultipleAPDUs INTEGER ::= 14 +id-Payload-Type INTEGER ::= 15 +id-Positioning-Data INTEGER ::= 16 +id-Return-Error-Request INTEGER ::= 17 +id-Return-Error-Cause INTEGER ::= 18 +id-Source-Identity INTEGER ::= 19 +id-UE-Positioning-Capability INTEGER ::= 20 +id-Velocity-Estimate INTEGER ::= 21 +id-LCS-Service-Type-ID INTEGER ::= 22 + +``` + +``` + +-- ****************************************************************************** +-- +-- Extension constants +-- +-- ****************************************************************************** + +``` + +``` + +-- ****************************************************************************** +-- +-- Lists +-- +-- ****************************************************************************** + +``` + +``` + +max-No-Of-Points INTEGER ::= 15 +max-Set INTEGER ::= 9 +max-GNSS-Set INTEGER ::= 9 + +maxProtocolExtensions INTEGER ::= 65535 +maxProtocolIEs INTEGER ::= 65535 + +``` + +END + +### 7.5.8 Container Definitions + +``` + +-- ***** +-- +-- Container definitions +-- +-- ***** + +LCS-AP-Containers { + itu-t (0) identified-organization (4) etsi (0) mobileDomain (0) + eps-Access (21) modules (3) lcs-AP (4) version1 (1) lcs-AP-Containers (5)} + +DEFINITIONS AUTOMATIC TAGS ::= + +BEGIN + +-- ***** +-- +-- IE parameter types from other modules. +-- +-- ***** + +IMPORTS + Criticality, + Presence, + ProtocolExtensionID, + ProtocolIE-ID +FROM LCS-AP-CommonDataTypes + + maxProtocolExtensions, + maxProtocolIEs +FROM LCS-AP-Constants; + +-- ***** +-- +-- Class Definition for Protocol IEs +-- +-- ***** + +LCS-AP-PROTOCOL-IES ::= CLASS { + &id ProtocolIE-ID UNIQUE, + &criticality Criticality DEFAULT ignore, + &Value, + &presence Presence +} +WITH SYNTAX { + ID &id + CRITICALITY &criticality + TYPE &Value + PRESENCE &presence +} + +-- ***** +-- +-- Class Definition for Protocol Extensions +-- +-- ***** + +LCS-AP-PROTOCOL-EXTENSION ::= CLASS { + &id ProtocolExtensionID UNIQUE, + &criticality Criticality DEFAULT ignore, + &Extension, + &presence Presence +} +WITH SYNTAX { + ID &id + CRITICALITY &criticality + EXTENSION &Extension + PRESENCE &presence +} + +-- ***** +-- +-- Container for Protocol IEs +-- +-- ***** + +``` + +``` + +ProtocolIE-Container {LCS-AP-PROTOCOL-IES : IEsSetParam} ::= + SEQUENCE (SIZE (0..maxProtocolIEs)) OF + ProtocolIE-Field {{IEsSetParam}} + +ProtocolIE-Field {LCS-AP-PROTOCOL-IES : IEsSetParam} ::= SEQUENCE { + id LCS-AP-PROTOCOL-IES.&id {{IEsSetParam}}, + criticality LCS-AP-PROTOCOL-IES.&criticality {{IEsSetParam}{@id}}, + value LCS-AP-PROTOCOL-IES.&Value {{IEsSetParam}{@id}} +} + +-- ***** +-- +-- Container Lists for Protocol IE Containers +-- +-- ***** + +ProtocolIE-ContainerList {INTEGER : lowerBound, INTEGER : upperBound, LCS-AP-PROTOCOL-IES : IEsSetParam} + ::= + SEQUENCE (SIZE (lowerBound..upperBound)) OF + ProtocolIE-Container {{IEsSetParam}} + +-- ***** +-- +-- Container for Protocol Extensions +-- +-- ***** + +ProtocolExtensionContainer {LCS-AP-PROTOCOL-EXTENSION : ExtensionSetParam} ::= + SEQUENCE (SIZE (1..maxProtocolExtensions)) OF + ProtocolExtensionField {{ExtensionSetParam}} + +ProtocolExtensionField {LCS-AP-PROTOCOL-EXTENSION : ExtensionSetParam} ::= SEQUENCE { + id LCS-AP-PROTOCOL-EXTENSION.&id {{ExtensionSetParam}}, + criticality LCS-AP-PROTOCOL-EXTENSION.&criticality {{ExtensionSetParam}{@id}}, + extensionValue LCS-AP-PROTOCOL-EXTENSION.&Extension {{ExtensionSetParam}{@id}} +} + +END + +``` + +### 7.5.9 Message transfer syntax + +LCS-AP shall use the ASN.1 Basic Packed Encoding Rules (BASIC-PER) Aligned Variant as transfer syntax as specified in ITU-T Recommendation X.691 [12]. + +## 7.6 Handling of unknown, unforeseen and erroneous protocol data + +Section 10 of 3GPP TS 36.413 [7] is applicable for the purposes of the present document. + +# 8 LCS-AP Timers + +## 8.1 General + +The description of timers in the following tables should be considered a brief summary. + +## 8.2 Timers of LCS-AP + +**Table 8.2.1: LCS-AP timers** + +| TIMER NUM. | TIMER VALUE | CAUSE OF START | NORMAL STOP | ON EXPIRY | +|------------|-----------------------------------------------------------------------------------|--------------------------------------------------|---------------------------------------|-------------------------------------| +| T3x01 | This value can be operator configurable, based on the received QoS response time. | A Location Request procedure started in the MME. | Location Response message is received | Return error to requesting entity | +| T3x02 | 3 seconds | A Reset message is sent | Reset Acknowledge message is received | Retransmission of the Reset message | + + + +# Annex A (informative): Change history + +| Change history | | | | | | | | +|----------------|-------|-----------|------|-----|-----------------------------------------------------------------------------------------|--------|--------| +| Date | TSG # | TSG Doc. | CR | Rev | Subject/Comment | Old | New | +| 2010-03 | CP-47 | CP-100054 | | | 3GPP TS presented for approval in CT#47 | 2.0.0 | 9.0.0 | +| 2010-06 | CP-48 | CP-100286 | 0001 | | Correction to Positioning Data Element | 9.0.0 | 9.1.0 | +| | | | 0003 | | Correction to Cell ID Category | | | +| 2010-06 | CP-48 | CP-100417 | 0002 | 3 | Provide Service Type ID to E-SMLC | 9.1.0 | 10.0.0 | +| 2010-09 | CP-49 | CP-100463 | 0006 | 1 | Define message transfer syntax in LCS-AP | 10.0.0 | 10.1.0 | +| | | | | | Add LCS-AP port identifier, payload protocol identifier and Elementary Procedure number | | | +| 2011-03 | CP-51 | CP-110054 | 0014 | 2 | Fix mismatches between technical description and ASN.1 coding | 10.1.0 | 10.2.0 | +| 2011-06 | CP-52 | CP-110365 | 0016 | 1 | Protocol Layering for LCS-AP | 10.2.0 | 10.3.0 | +| 2011-09 | CP-53 | CP-110579 | 0020 | 1 | Polygon encoding correction | 10.3.0 | 11.0.0 | +| 2012-03 | CP-55 | CP-120038 | 0021 | 2 | Use of multiple SCTP associations between MME and E-SMLC | 11.0.0 | 11.1.0 | +| 2012-12 | CP-58 | CP-120880 | 0023 | 1 | Mandatory Correlation ID in Connection Oriented Information | 11.1.0 | 11.2.0 | +| 2013-06 | CP-60 | CP-130287 | 0024 | 1 | APDU in Connection Oriented Information message | 11.2.0 | 11.3.0 | +| 2015-12 | CP-70 | CP-150740 | 0031 | 1 | ASN.1 Corrections | 11.3.0 | 11.4.0 | \ No newline at end of file diff --git a/marked/Rel-11/29_series/29172/63e0c22852c26699d0bd095a2d796bab_img.jpg b/marked/Rel-11/29_series/29172/63e0c22852c26699d0bd095a2d796bab_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..10535dcb01bd8ac3fffdeb90a7715d8ccc83c3fb --- /dev/null +++ b/marked/Rel-11/29_series/29172/63e0c22852c26699d0bd095a2d796bab_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8b07d560a25a408dd26d05c072b931da6b27b74cc2c2f91b82787bc258f60f1e +size 23051 diff --git a/marked/Rel-11/29_series/29172/c2fc2621e8206d24427b56bcb2398fc0_img.jpg b/marked/Rel-11/29_series/29172/c2fc2621e8206d24427b56bcb2398fc0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2eaf66776f34ca64cd5ceea051e69afe9559a5b1 --- /dev/null +++ b/marked/Rel-11/29_series/29172/c2fc2621e8206d24427b56bcb2398fc0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9a9fc4938df61ddeecb5bced1e4657151d75b23a21228b92dfa9c1760f56111b +size 26729 diff --git a/marked/Rel-11/29_series/29172/d0abac95583b52a3b35f74a215567334_img.jpg b/marked/Rel-11/29_series/29172/d0abac95583b52a3b35f74a215567334_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fb63ade6468ba51e0274bd7ff64f5449a8174b88 --- /dev/null +++ b/marked/Rel-11/29_series/29172/d0abac95583b52a3b35f74a215567334_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:464995b5202cf889c90a70d1d5de4b17fa6dbf0932fa624f1f31d17c001cb387 +size 26311 diff --git a/marked/Rel-11/29_series/29172/raw.md b/marked/Rel-11/29_series/29172/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..e736ed463b2a60e18f783e433096b4fc5c95945c --- /dev/null +++ b/marked/Rel-11/29_series/29172/raw.md @@ -0,0 +1,1069 @@ + + + + +Error! No +text of + +Error! No text of specified style in +document. + +# Contents + +| | | +|----------------------------------------------------|----| +| Foreword ..... | 5 | +| 1 Scope..... | 6 | +| 2 References..... | 6 | +| 3 Definitions, symbols and abbreviations..... | 7 | +| 3.1 Definitions..... | 7 | +| 3.2 Symbols..... | 7 | +| 3.3 Abbreviations ..... | 7 | +| 4 Functional Overview..... | 7 | +| 4.1 General ..... | 7 | +| 5 ELP Message Transport..... | 8 | +| 5.1 General ..... | 8 | +| 5.2 Use of Diameter base protocol..... | 8 | +| 5.3 Securing Diameter Messages ..... | 8 | +| 5.4 Accounting functionality..... | 9 | +| 5.5 Use of sessions ..... | 9 | +| 5.6 Transport protocol..... | 9 | +| 5.7 Routing considerations..... | 9 | +| 5.8 Advertising Application Support ..... | 9 | +| 6 ELP Procedures..... | 10 | +| 6.1 General ..... | 10 | +| 6.2 Provide Subscriber Location ..... | 10 | +| 6.2.1 General ..... | 10 | +| 6.2.2 Successful Operation..... | 10 | +| 6.2.3 Unsuccessful Operation..... | 12 | +| 6.3 Subscriber Location Report..... | 12 | +| 6.3.1 General ..... | 12 | +| 6.3.2 Successful Operation..... | 13 | +| 6.3.3 Unsuccessful Operation..... | 15 | +| 7 ELP Messages and Message Formats ..... | 15 | +| 7.1 General ..... | 15 | +| 7.2 Message Formats..... | 15 | +| 7.3 ELP Messages ..... | 16 | +| 7.3.1 Provide-Location-Request (PLR) Command ..... | 16 | +| 7.3.2 Provide-Location-Answer (PLA) Command ..... | 16 | +| 7.3.3 Location-Report-Request (LRR) Command ..... | 17 | +| 7.3.4 Location-Report-Answer (LRA) Command..... | 17 | +| 7.4 Information Elements..... | 18 | +| 7.4.1 General ..... | 18 | +| 7.4.2 SLG-Location-Type ..... | 20 | +| 7.4.3 LCS-EPS-Client-Name..... | 20 | +| 7.4.4 LCS-Requestor-Name ..... | 20 | +| 7.4.5 LCS-Priority ..... | 21 | +| 7.4.6 LCS-QoS ..... | 21 | +| 7.4.7 Horizontal-Accuracy ..... | 21 | +| 7.4.8 Vertical-Accuracy..... | 21 | +| 7.4.9 Vertical-Requested ..... | 21 | +| 7.4.10 Velocity-Requested ..... | 21 | +| 7.4.11 Response-Time ..... | 22 | +| 7.4.12 Supported-GAD-Shapes ..... | 22 | +| 7.4.13 LCS-Codeword..... | 22 | +| 7.4.14 LCS-Privacy-Check..... | 22 | +| 7.4.15 Accuracy-Fulfilment-Indicator ..... | 22 | +| 7.4.16 Age-Of-Location-Estimate ..... | 22 | +| 7.4.17 Velocity-Estimate ..... | 23 | +| 7.4.18 EUTRAN-Positioning-Data ..... | 23 | + +| | | | +|------------------------|-------------------------------------------------------------|----| +| 7.4.19 | ECGI..... | 23 | +| 7.4.20 | Location-Event ..... | 23 | +| 7.4.21 | Pseudonym-Indicator..... | 23 | +| 7.4.22 | LCS-Service-Type-ID ..... | 23 | +| 7.4.23 | LCS-Privacy-Check-Non-Session..... | 23 | +| 7.4.24 | LCS-Privacy-Check-Session ..... | 24 | +| 7.4.25 | Feature-List-ID ..... | 24 | +| 7.4.26 | Feature-List..... | 24 | +| 7.4.27 | LCS-QoS-Class ..... | 24 | +| 7.4.28 | Serving-Node..... | 24 | +| 7.4.29 | void ..... | 25 | +| 7.4.30 | void ..... | 25 | +| 7.4.31 | void ..... | 25 | +| 7.4.32 | void ..... | 25 | +| 7.4.33 | void ..... | 25 | +| 7.4.34 | void ..... | 25 | +| 7.4.35 | void ..... | 25 | +| 7.4.36 | void ..... | 25 | +| 7.4.37 | void ..... | 25 | +| 7.4.38 | void ..... | 25 | +| 7.4.39 | void ..... | 25 | +| 7.4.40 | void ..... | 25 | +| 7.4.41 | void ..... | 25 | +| 7.4.42 | void ..... | 25 | +| 7.4.43 | void ..... | 25 | +| 7.4.44 | void ..... | 25 | +| 7.4.45 | void ..... | 25 | +| 7.4.46 | void ..... | 25 | +| 7.4.47 | void ..... | 25 | +| 7.4.48 | void ..... | 25 | +| 7.4.49 | void ..... | 25 | +| 7.4.50 | void ..... | 25 | +| 7.4.51 | void ..... | 25 | +| 7.4.52 | void ..... | 26 | +| 7.4.53 | void ..... | 26 | +| 7.4.54 | void ..... | 26 | +| 7.4.55 | void ..... | 26 | +| 7.4.56 | void ..... | 26 | +| 7.4.57 | void ..... | 26 | +| 7.4.58 | void ..... | 26 | +| 7.4.59 | 1xRTT-RCID..... | 26 | +| 7.5 | Result-Code AVP and Experimental-Result AVP Values ..... | 26 | +| 7.5.1 | General ..... | 26 | +| 7.5.2 | Success ..... | 26 | +| 7.5.3 | Permanent Failures ..... | 26 | +| 7.5.3.1 | DIAMETER_ERROR_USER_UNKNOWN (5001) ..... | 26 | +| 7.5.3.2 | DIAMETER_ERROR_UNAUTHORIZED_REQUESTING_NETWORK (5490) ..... | 26 | +| 7.5.4 | Transient Failures ..... | 27 | +| 7.5.4.1 | DIAMETER_ERROR_UNREACHABLE_USER (4221)..... | 27 | +| 7.5.4.2 | DIAMETER_ERROR_SUSPENDED_USER (4222) ..... | 27 | +| 7.5.4.3 | DIAMETER_ERROR_DETACHED_USER (4223)..... | 27 | +| 7.5.4.4 | DIAMETER_ERROR_POSITIONING_DENIED (4224)..... | 27 | +| 7.5.4.5 | DIAMETER_ERROR_POSITIONING_FAILED (4225) ..... | 27 | +| 7.5.4.6 | DIAMETER_ERROR_UNKNOWN_UNREACHABLE LCS_CLIENT (4226) ..... | 27 | +| Annex A (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. + +# --- 1 Scope + +The present document specifies the procedures and information coding for the EPC LCS Protocol (ELP) that is needed to support the location services in E-UTRAN. The ELP message set is applicable to the SLg interface between the MME and the GMLC. ELP is developed in accordance to the general principles stated in 3GPP TS 23.271 [3]. + +# --- 2 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. +- For a specific reference, subsequent revisions do not apply. +- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. + +- [1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications". +- [2] 3GPP TS 23.271: "Functional stage 2 description of Location Services (LCS)". +- [3] 3GPP TS 23.032: "Universal Geographical Area Description (GAD)". +- [4] IETF RFC 3588: "Diameter Base Protocol". +- [5] IETF RFC 2234: "Augmented BNF for syntax specifications". +- [6] 3GPP TS 23.003: "Numbering, addressing and identification". +- [7] 3GPP TS 29.171: "LCS Application Protocol (LCS-AP) between the MME and E-SMLC". +- [8] 3GPP TS 29.274: "Evolved General Packet Radio Service (GPRS) Tunnelling Protocol for Control plane (GTPv2-C)". +- [9] Void +- [10] 3GPP TS 32.299: "Charging management; Diameter charging applications". +- [11] 3GPP TS 29.272: "Evolved Packet System; MME and SGSN Related Interfaces Based on Diameter Protocol". +- [12] 3GPP TS 29.329: "Sh Interface based on the Diameter protocol". +- [13] 3GPP TS 33.210: "3G Security; Network Domain Security; IP Network Layer Security". +- [14] IETF RFC 4960: "Stream Control Transmission Protocol". +- [15] 3GPP TS 22.071: "Location Services (LCS); Service description". +- [16] IETF RFC 5778: "Diameter Mobile IPv6: Support for Home Agent to Diameter Server Interaction". +- [17] 3GPP TS 29.229: "Cx and Dx Interfaces based on the Diameter protocol; protocol details". +- [18] 3GPP TS 29.173: "Location Services; Diameter-based SLh interface for Control Plane LCS". +- [19] 3GPP TS 29.002: "Mobile Application Part (MAP) specification". +- [20] void +- [21] void + +[22] 3GPP2 A.S0014-D v5.0: "Interoperability Specification (IOS) for cdma2000 Access Network Interfaces – Part 4 (A1, A1p, A2, and A5 Interfaces) UTRAN Iu Interface RANAP signalling". + +# 3 Definitions, symbols and abbreviations + +## 3.1 Definitions + +For the purposes of the present document, the terms and definitions given in TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905 [1]. + +**EPC-MO-LR:** EPC Mobile Originating Location Request + +**EPC-MT-LR:** EPC Mobile Terminating Location Request + +**EPC-NI-LR:** EPC Network Induced Location Request + +**LCS:** LoCation Services + +**LCS Client:** software and/or hardware entity that interacts with a LCS Server (in this case, the GMLC) for the purpose of obtaining location information for one or more Mobile Stations. LCS Clients subscribe to LCS in order to obtain location information. LCS Clients may or may not interact with human users. The LCS Client is responsible for formatting and presenting data and managing the user interface (dialogue). The LCS Client may reside in the Mobile Station (UE). + +**LCS QoS:** The QoS class determines the degree of adherence to the quality of service information as required by the source of a location request. + +**Target:** UE being positioned + +## 3.2 Symbols + +For the purposes of the present document, the following symbols apply: + +| | | +|-----|--------------------------------| +| SLg | Interface between GMLC and MME | +|-----|--------------------------------| + +## 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]. + +| | | +|------|--------------------------------------------------| +| GMLC | Gateway Mobile Location Centre | +| EPC | Enhanced Packet Core | +| IMEI | International Mobile Equipment Identity | +| IMS | IP Multimedia Subsystem | +| IMSI | International Mobile Subscriber Identity | +| MME | Mobility Management Entity | +| UE | User Equipment, as defined in 3GPP TS 23.032 [3] | + +# 4 Functional Overview + +## 4.1 General + +This document defines the EPC LCS Protocol (ELP) used on the SLg interface between the GMLC and the MME in the Evolved Packet Core (EPC). + +The location of the SLg interface within the LCS logical architecture is shown in Figure 4.1-1. + +![Figure 4.1-1 SLg interface in the LCS Architecture diagram](d0abac95583b52a3b35f74a215567334_img.jpg) + +The diagram illustrates the LCS architecture. A User Equipment (UE) is connected to an eNB, which is connected to an MME. The MME is connected to an HSS and an E-SMLC. The MME is also connected to a Serving Gateway, which is connected to a PDN Gateway. The PDN Gateway is connected to an IMS, which is connected to a PSAP. The MME is connected to a GMLC via the SLg interface. The GMLC is connected to an LRF, which is connected to the IMS. The GMLC and LRF are enclosed in a dashed box. + +Figure 4.1-1 SLg interface in the LCS Architecture diagram + +**Figure 4.1-1 SLg interface in the LCS Architecture** + +The high level functions of the ELP protocol are described in 3GPP TS 23.271 [2]. + +The main functions of the protocol are: + +- To allow the GMLC to request position estimates for a particular target UE from the MME in order to support the EPC-MT-LR positioning procedures. This is achieved using the Provide Subscriber Location message; +- To allow the MME to return a position estimate or an error report to the GMLC in response to a Provide Subscriber Location request as part of an EPC-MT-LR positioning procedure; +- To allow the MME to forward an unsolicited position estimate to the GMLC as part of the EPC-MO-LR or EPC-NI-LR procedures; +- To allow the GMLC to acknowledge receipt of an unsolicited position estimate as part of the EPC-MO-LR or EPC-NI-LR procedures; +- To support the procedures for handover of an IMS emergency call with EPS/GPRS access. + +# 5 ELP Message Transport + +## 5.1 General + +The ELP protocol is defined as a Vendor Specific diameter application (SLg application). It reuses the basic mechanisms defined by the diameter base protocol, and it defines a number of additional commands and AVPs to implement the SLg specific procedures. + +## 5.2 Use of Diameter base protocol + +The Diameter Base Protocol as specified in IETF RFC 3588 [4] shall apply except as modified by the defined support of the methods and the defined support of the commands and AVPs, result and error codes as described in this specification. Unless otherwise specified, the procedures (including error handling and unrecognised information handling) shall be used unmodified. + +## 5.3 Securing Diameter Messages + +For secure transport of Diameter messages, see 3GPP TS 33.210 [13]. + +## 5.4 Accounting functionality + +Accounting functionality (Accounting Session State Machine, related command codes and AVPs) shall not be used on the SLg interface. + +## 5.5 Use of sessions + +Between the MME and the GMLC, Diameter sessions shall be implicitly terminated. An implicitly terminated session is one for which the server does not maintain state information. The client shall not send any re-authorization or session termination requests to the server. + +The Diameter base protocol includes the Auth-Session-State AVP as the mechanism for the implementation of implicitly terminated sessions. + +The client (server) shall include in its requests (responses) the Auth-Session-State AVP set to the value NO\_STATE\_MAINTAINED (1), as described in IETF RFC 3588 [4]. As a consequence, the server shall not maintain any state information about this session and the client shall not send any session termination request. Neither the Authorization-Lifetime AVP nor the Session-Timeout AVP shall be present in requests or responses. + +## 5.6 Transport protocol + +Diameter messages over the SLg interface shall make use of SCTP (see IETF RFC 4960 [14]). + +## 5.7 Routing considerations + +This clause specifies the use of the Diameter routing AVPs Destination-Realm and Destination-Host. + +Destination-Realm AVP shall always be included in all diameter requests, and therefore is declared as mandatory in the ABNF for all commands. + +When a request is initiated by the GMLC, the name of the MME shall be determined by querying the HSS over the SLh interface, and retrieve the specific MME that is currently serving the UE. Therefore, Destination-Host AVP shall always be included in the commands originated at the GMLC, and is declared as mandatory in the ABNF. + +When a request is initiated by the MME, the name of the GMLC may be either locally configured in the MME (e.g., in the intra-domain scenario, when the GMLC belongs to the same PLMN as the MME), or it is known from a previously received location procedure initiated at the GMLC. Therefore, the Destination-Host AVP is declared as mandatory in the ABNF of the commands originated at the MME. + +If the Vendor-Specific-Application-ID AVP is received in any of the commands, it may be ignored by the receiving node, and it shall not be used for routing purposes. + +## 5.8 Advertising Application Support + +The MME and GMLC shall advertise support of the Diameter SLg Application by including the value of the application identifier in the Auth-Application-Id AVP within the Vendor-Specific-Application-Id grouped AVP of the Capabilities-Exchange-Request and Capabilities-Exchange-Answer commands. + +The vendor identifier value of 3GPP (10415) shall be included in the Supported-Vendor-Id AVP of the Capabilities-Exchange-Request and Capabilities-Exchange-Answer commands, and in the Vendor-Id AVP within the Vendor-Specific-Application-Id grouped AVP of the Capabilities-Exchange-Request and Capabilities-Exchange-Answer commands. + +The Vendor-Id AVP included in Capabilities-Exchange-Request and Capabilities-Exchange-Answer commands that is not included in the Vendor-Specific-Application-Id AVPs as described above shall indicate the manufacturer of the Diameter node as per RFC 3588 [4]. + +# --- 6 ELP Procedures + +## 6.1 General + +The ELP procedures, between the GMLC and the MME, are used to exchange messages related to location services over the SLg interface. The ELP can be divided into the following sub-procedures. + +- Provide Subscriber Location +- Subscriber Location Report + +## 6.2 Provide Subscriber Location + +### 6.2.1 General + +The Provide Subscriber Location operation is used by a GMLC to request the location of a target UE from the MME at any time. The response contains a location estimate of the target UE and other additional information. + +### 6.2.2 Successful Operation + +![Sequence diagram showing the successful operation of the Provide Subscriber Location procedure. The GMLC sends a PROVIDE SUBSCRIBER LOCATION REQUEST to the MME, and the MME returns a PROVIDE SUBSCRIBER LOCATION RESPONSE.](c2fc2621e8206d24427b56bcb2398fc0_img.jpg) + +``` +sequenceDiagram + participant GMLC + participant MME + Note left of GMLC: + GMLC->>MME: PROVIDE SUBSCRIBER LOCATION REQUEST + Note right of MME: + MME-->>GMLC: PROVIDE SUBSCRIBER LOCATION RESPONSE + Note right of GMLC: +``` + +Sequence diagram showing the successful operation of the Provide Subscriber Location procedure. The GMLC sends a PROVIDE SUBSCRIBER LOCATION REQUEST to the MME, and the MME returns a PROVIDE SUBSCRIBER LOCATION RESPONSE. + +**Figure 6.2.2-1: Provide Subscriber Location procedure. Successful operation.** + +The GMLC initiates the procedure by sending a PROVIDE SUBSCRIBER LOCATION REQUEST message to the MME. This message carries the type of location information requested (e.g. current location and optionally, velocity), the UE subscriber's IMSI, LCS QoS information (e.g. accuracy, response time) and an indication of whether the LCS client has the override capability. + +Upon reception of PROVIDE SUBSCRIBER LOCATION REQUEST message, the MME shall perform authentication privacy verification on the location request. After that, the MME shall retrieve the location information of the target UE from E-UTRAN according to the procedures described in 3GPP TS 23.271 [2]. + +The MME returns a PROVIDE SUBSCRIBER LOCATION RESPONSE to the GMLC. The message shall contain the location estimate, its age and obtained accuracy. If the MME failed to get the current location and the LCS client is requesting the current or last known location, the MME may return the last known location of the target UE if this is known. + +This procedure is mapped to the commands Provide-Location-Request/Answer in the Diameter application specified in sections 7.3.1 and 7.3.2. + +**Table 6.2.2-1: Provide Subscriber Location Request** + +| Information element name | Mapping to Diameter AVP | Cat. | Description | +|----------------------------------------------|-------------------------------|------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Location Type | SLg-Location-Type | M | This Information Element shall contain the type of location measurement requested, such as current location, initial location, last known location, etc. (see 3GPP TS 22.071 [15]). | +| IMSI | User-Name | C | If present, this Information Element shall contain the IMSI of the user whose UE is to be positioned (see Note 1). | +| MSISDN | MSISDN | C | If present, this Information Element shall contain the MSISDN of the user whose UE is to be positioned (see Note 1). | +| IMEI | IMEI | C | If present, this Information Element shall contain the IMEI of the UE to be positioned (see Note 1). | +| Client Name | LCS-EPS-Client-Name | M | This Information Element shall contain the name of the LCS client issuing the positioning request. | +| Client Type | LCS-Client-Type | M | This Information Element shall contain the type of LCS client (Emergency, Lawful Interception ...) issuing the positioning request (see 3GPP TS 23.271 [2] and 3GPP TS 32.299 [10]). | +| Requestor Name | LCS-Requestor-Name | O | If present, this Information Element contains the identity of the originating entity which has requested the location of the target UE from the LCS Client. | +| Priority | LCS-Priority | O | If present, this Information Element shall contain the priority of the LCS client issuing the positioning request. | +| QoS | LCS-QoS | O | If present, this Information Element shall contain the quality of service requested, such as the accuracy of the positioning measurement and the response time of the positioning operation. | +| Velocity Requested | Velocity-Requested | O | If present, this information element shall contain an indication of whether or not the Velocity of the target UE is requested. | +| Supported GAD Shapes | LCS-Supported-GAD-Shapes | O | If present, this Information Element shall contain the list of supported GAD shapes by the LCS client. | +| Service Type ID | LCS-Service-Type-ID | O | If present, this Information Element shall contain the service type associated for the particular positioning request (the meaning of the different service types is defined in 3GPP TS 22.071 [15]). | +| Codeword | LCS-Codeword | O | If present, this Information Element shall contain the Codeword to be used between an LCS client and a target UE in order to check and accept or reject the positioning request. | +| APN | Service-Selection | C | If present, this Information Element shall contain the Access Point Name (APN) Network Identifier of the LCS client, as used by the target UE. It shall only be included in session-related location requests. | +| Session-Related Privacy Check | LCS-Privacy-Check-Session | O | If present, this Information Element shall contain an indication of how the positioning operation should proceed in the relation to the checking of the session-related privacy settings of the user. | +| Non-Session-Related Privacy Check | LCS-Privacy-Check-Non-Session | O | If present, this Information Element shall contain an indication of how the positioning operation should proceed in the relation to the checking of the non-session-related privacy settings of the user. | +| Supported Features (See 3GPP TS 29.229 [17]) | Supported-Features | O | If present, this information element shall contain the list of features supported by the origin host. | + +NOTE 1: At least one of these IEs shall be present in the message. + +**Table 6.2.2-2: Provide Subscriber Location Answer** + +| Information element name | Mapping to Diameter AVP | Cat. | Description | +|----------------------------------------------|-----------------------------------|------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Result | Result-Code / Experimental-Result | M | This Information Element shall contain the result of the operation. The Result-Code AVP shall be used to indicate success / errors as defined in the Diameter Base Protocol. The Experimental-Result AVP shall be used for ELP errors. This is a grouped AVP which shall contain the 3GPP Vendor ID in the Vendor-Id AVP, and the error code in the Experimental-Result-Code AVP. | +| Location Estimate | Location-Estimate | O | If present, this Information Element shall contain an estimate of the location of the UE in universal coordinates and the accuracy of the estimate. | +| Accuracy Fulfilment Indicator | Accuracy-Fulfilment-Indicator | O | If present, this Information Element shall contain an indication of whether the requested accuracy (as indicated in the LCS-QoS IE in the request message) was fulfilled or not. | +| Age of Location Estimate | Age-of-Location-Estimate | O | If present, this Information Element shall contain an indication of how long ago the location estimate was obtained. | +| Velocity Estimate | Velocity-Estimate | O | If present, this Information Element shall contain an estimate of the velocity of the target UE, composed by horizontal speed, vertical speed, and their respective uncertainty (see 3GPP TS 23.032 [3]). | +| EUTRAN Positioning Data | EUTRAN-Positioning-Data | O | If present, this Information Element shall indicate the usage of each positioning method that was attempted to determine the location estimate, either successfully or unsuccessfully. The internal structure and encoding is defined in 3GPP TS 29.171 [7]. | +| ECGI | ECGI | O | If present, this Information Element shall contain the current cell location of the target UE. The E-UTRAN Cell Global Identifier (ECGI) is used to globally identify a cell. | +| Target Serving Node Identity | Serving-Node | O | If present, this information element shall contain the address of the target side serving node for handover of an IMS Emergency Call. | +| Supported Features (See 3GPP TS 29.229 [17]) | Supported-Features | O | If present, this information element shall contain the list of features supported by the origin host. | + +### 6.2.3 Unsuccessful Operation + +On receipt of a PROVIDE SUBSCRIBER LOCATION RESPONSE with a Result-Code or Experimental-Result AVP indicating failure the GMLC considers the positioning request as failed. + +## 6.3 Subscriber Location Report + +### 6.3.1 General + +The Subscriber Location Report operation is used by an MME to provide the location of a target UE to a GMLC when a request for location has been implicitly issued. + +### 6.3.2 Successful Operation + +![Sequence diagram showing the successful operation of the Subscriber Location Report procedure between an MME and a GMLC.](63e0c22852c26699d0bd095a2d796bab_img.jpg) + +``` + +sequenceDiagram + participant MME + participant GMLC + Note left of MME: + MME->>GMLC: SUBSCRIBER LOCATION REPORT + Note right of GMLC: + GMLC->>MME: SUBSCRIBER LOCATION REPORT ACK + Note left of MME: + +``` + +The diagram illustrates the interaction between an MME (Mobility Management Entity) and a GMLC (Gateway Mobile Location Centre). The MME sends a 'SUBSCRIBER LOCATION REPORT' message to the GMLC. The GMLC responds with a 'SUBSCRIBER LOCATION REPORT ACK' message. Both entities have a vertical lifeline with a horizontal bar at the bottom indicating active periods. + +Sequence diagram showing the successful operation of the Subscriber Location Report procedure between an MME and a GMLC. + +**Figure 6.3.2-1: Subscriber Location Report procedure. Successful operation.** + +The MME initiates the procedure by sending a SUBSCRIBER LOCATION REPORT message to the GMLC. The message may carry the identity of the UE, the location estimate and its age, and the event causing the location report. + +Upon reception of SUBSCRIBER LOCATION REPORT message, the GMLC shall return a SUBSCRIBER LOCATION REPORT ACK to the MME and process the location report accordingly, e.g. transfer of the location estimate to an external LCS Client according to procedure described in 3GPP TS 23.271 [2]. + +This procedure is mapped to the commands Location-Report-Request/Answer in the Diameter application specified in sections 7.3.3 and 7.3.4. + +**Table 6.3.2-1: Subscriber Location Report** + +| Information element name | Mapping to Diameter AVP | Cat. | Description | +|----------------------------------------------|-------------------------------|------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Location Event | Location-Event | M | This Information Element shall contain the type of event that caused the location procedure to be initiated. | +| IMSI | User-Name | C | If present, this Information Element shall contain the IMSI of the user whose UE is to be positioned (see Note 1). | +| MSISDN | MSISDN | C | If present, this Information Element shall contain the MSISDN of the user whose UE is to be positioned (see Note 1). | +| IMEI | IMEI | C | If present, this Information Element shall contain the IMEI of the UE to be positioned (see Note 1). | +| Client Name | LCS-EPS-Client-Name | O | If present, this Information Element shall contain the name of the LCS client where the result of the positioning operation should be sent. | +| Location Estimate | Location-Estimate | O | If present, this Information Element shall contain an estimate of the location of the UE in universal coordinates and the accuracy of the estimate. | +| Accuracy Fulfilment Indicator | Accuracy-Fulfilment-Indicator | O | If present, this Information Element shall contain an indication of whether the requested accuracy was fulfilled or not. | +| Age of Location Estimate | Age-of-Location-Estimate | O | If present, this Information Element shall contain an indication of how long ago the location estimate was obtained. | +| Velocity Estimate | Velocity-Estimate | O | If present, this Information Element shall contain an estimate of the velocity of the UE, composed by horizontal speed, vertical speed, and their respective uncertainty (see 3GPP TS 23.032 [3]). | +| EUTRAN Positioning Data | EUTRAN-Positioning-Data | O | If present, this Information Element shall indicate the usage of each positioning method that was attempted to determine the location estimate, either successfully or unsuccessfully. The internal structure and encoding is defined in 3GPP TS 29.171 [7]. | +| ECGI | ECGI | O | If present, this Information Element shall contain the current cell location of the target UE. The E-UTRAN Cell Global Identifier (ECGI) is used to globally identify a cell. | +| Service Type ID | LCS-Service-Type-ID | O | If present, this Information Element shall contain the service type associated for the particular positioning report identifying the service at the receiving LCS Client (the meaning of the different service types is defined in 3GPP TS 22.071 [15]). | +| Pseudonym Indicator | Pseudonym-Indicator | O | If present, this Information Element shall contain an indication of whether or not a pseudonym must be allocated by the network and transferred to the LCS client as the identity of the UE. | +| Supported Features (See 3GPP TS 29.229 [17]) | Supported-Features | O | If present, this information element shall contain the list of features supported by the origin host. | +| LCS QoS Class | LCS-QoS-Class | O | If present, this Information Element shall contain the LCS-QoS-Class requested by the target UE. | +| Target Serving Node Identity | Serving-Node | O | If present, this information element shall contain the address of the target side serving node for handover of an IMS Emergency Call. | +| 1xRTT Reference Cell ID | 1xRTT-RCID | O | If present, this Information Element shall contain the 1xRTT Reference Cell ID uniquely identifying of the target cell location for handover of an IMS emergency call. This Information Element is applicable only when the UE is making handover to a cdma2000 1xRTT access and when the message is sent by the MME or the MME part of the combined MME/SGSN. | + +NOTE 1: At least one of these IEs shall be present in the message. + +**Table 6.3.2-2: Subscriber Location Report Ack** + +| Information element name | Mapping to Diameter AVP | Cat. | Description | +|----------------------------------------------|-----------------------------------|------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Result | Result-Code / Experimental-Result | M | This Information Element shall contain the result of the operation. The Result-Code AVP shall be used to indicate success / errors as defined in the Diameter Base Protocol. The Experimental-Result AVP shall be used for ELP errors. This is a grouped AVP which shall contain the 3GPP Vendor ID in the Vendor-Id AVP, and the error code in the Experimental-Result-Code AVP. | +| Supported Features (See 3GPP TS 29.229 [17]) | Supported-Features | O | If present, this information element shall contain the list of features supported by the origin host. | + +### 6.3.3 Unsuccessful Operation + +If for some reason the GMLC does not accept the SUBSCRIBER LOCATION REPORT APDU, the GMLC shall send a SUBSCRIBER LOCATION REPORT ACK message with a Result-Code or Experimental-Result AVP indicating failure. + +# 7 ELP Messages and Message Formats + +## 7.1 General + +The Diameter Base Protocol as specified in IETF RFC 3588 [4] shall apply except as modified by the defined support of the methods and the defined support of the commands and AVPs, result and error codes as specified in this specification. Unless otherwise specified, the procedures (including error handling and unrecognised information handling) shall be used unmodified. + +This clause specifies a Diameter application that allows a Diameter server and a Diameter client: + +- to retrieve the location information of a target UE +- to report the location information of a target UE + +The SLg interface protocol is defined as an IETF vendor specific Diameter application, where the vendor is 3GPP. The vendor identifier assigned by IANA to 3GPP () is 10415. + +The Diameter application identifier assigned to the SLg interface application is 16777255 (allocated by IANA). + +## 7.2 Message Formats + +This section defines Command-Code values for the SLg interface application. + +Every command is defined by means of the ABNF syntax IETF RFC 2234 [5], according to the rules in IETF RFC 3588 [4]. If the definition and use of an AVP is not specified in this document, the guidelines in IETF RFC 3588 [4] shall apply. + +For these commands, the Application-ID field shall be set to 16777255 (application identifier of the SLg interface application). + +**NOTE:** For this release, the Vendor-Specific-Application-ID is included as an optional AVP in all commands in order to ensure interoperability with diameter agents following a strict implementation of IETF RFC 3588, by which messages not including this AVP will be rejected. IETF RFC 3588 indicates that the AVP shall be present in all proxiable commands, such as those specified here, despite that the contents of this AVP are redundant since the Application ID is already present in the command header. This AVP may be removed in subsequent revisions of this specification, once the diameter base protocol is updated accordingly. + +The following Command Codes are defined in this specification: + +**Table 7.2-1: Command-Code values** + +| Command-Name | Abbreviation | Code | Section | +|--------------------------|--------------|---------|---------| +| Provide-Location-Request | PLR | 8388620 | 7.3.1 | +| Provide-Location -Answer | PLA | 8388620 | 7.3.2 | +| Location-Report-Request | LRR | 8388621 | 7.3.3 | +| Location-Report-Answer | LRA | 8388621 | 7.3.4 | + +## 7.3 ELP Messages + +### 7.3.1 Provide-Location-Request (PLR) Command + +The Provide-Location-Request (PLR) command, indicated by the Command-Code field set to 8388620 and the 'R' bit set in the Command Flags field, is sent by the GMLC in order to request subscriber location to the MME. + +Message Format + +``` +< Provide-Location-Request > ::= < Diameter Header: 8388620, REQ, PXY, 16777255 > + < Session-Id > + [ Vendor-Specific-Application-Id ] + { Auth-Session-State } + { Origin-Host } + { Origin-Realm } + {Destination-Host } + { Destination-Realm } + { SLg-Location-Type } + [ User-Name ] + [ MSISDN ] + [ IMEI ] + { LCS-EPS-Client-Name } + { LCS-Client-Type } + [ LCS-Requestor-Name ] + [ LCS-Priority ] + [ LCS-QoS ] + [ Velocity-Requested ] + [ Supported-GAD-Shapes ] + [ LCS-Service-Type-ID ] + [ LCS-Codeword ] + [ LCS-Privacy-Check-Non-Session ] + [ LCS-Privacy-Check-Session ] + [Service-Selection ] + *[ Supported-Features ] + *[ AVP ] + *[ Proxy-Info ] + *[ Route-Record ] +``` + +### 7.3.2 Provide-Location-Answer (PLA) Command + +The Provide-Location-Answer (PLA) command, indicated by the Command-Code field set to 8388620 and the 'R' bit cleared in the Command Flags field, is sent by the MME to the GMLC in response to the Provide-Location-Request command. + +Message Format + +``` +< Provide-Location-Answer > ::= < Diameter Header: 8388620, PXY, 16777255 > + < Session-Id > + [ Vendor-Specific-Application-Id ] + [ Result-Code ] + [ Experimental-Result ] + { Auth-Session-State } + { Origin-Host } + { Origin-Realm } +``` + +``` + +[ Location-Estimate ] +[ Accuracy-Fulfilment-Indicator ] +[ Age-Of-Location-Estimate ] +[ Velocity-Estimate ] +[ EUTRAN-Positioning-Data ] +[ ECGI ] +[ Serving-Node ] +*[ Supported-Features ] +*[ AVP ] +*[ Failed-AVP ] +*[ Proxy-Info ] +*[ Route-Record ] + +``` + +### 7.3.3 Location-Report-Request (LRR) Command + +The Location-Report-Request (LRR) command, indicated by the Command-Code field set to 8388621 and the 'R' bit set in the Command Flags field, is sent by the MME in order to provide subscriber location data to the GMLC. + +Message Format + +``` + +< Location-Report-Request > ::= < Diameter Header: 8388621, REQ, PXY, 16777255 > +< Session-Id > +[ Vendor-Specific-Application-Id ] +{ Auth-Session-State } +{ Origin-Host } +{ Origin-Realm } +{ Destination-Host } +{ Destination-Realm } +{ Location-Event } +[ LCS-EPS-Client-Name ] +[ User-Name ] +[ MSISDN ] +[ IMEI ] +[ Location-Estimate ] +[ Accuracy-Fulfilment-Indicator ] +[ Age-Of-Location-Estimate ] +[ Velocity-Estimate ] +[ EUTRAN-Positioning-Data ] +[ ECGI ] +[ LCS-Service-Type-ID ] +[ Pseudonym-Indicator ] +[ LCS-QoS-Class ] +[ Serving-Node ] +[ 1xRTT-RCID ] +*[ Supported-Features ] +*[ AVP ] +*[ Proxy-Info ] +*[ Route-Record ] + +``` + +### 7.3.4 Location-Report-Answer (LRA) Command + +The Location-Report-Answer (LRA) command, indicated by the Command-Code field set to 8388621 and the 'R' bit cleared in the Command Flags field, is sent by the GMLC to the MME in response to the Location-Report-Request command. + +Message Format + +``` + +< Location-Report-Answer > ::= < Diameter Header: 8388621, PXY, 16777255 > +< Session-Id > +[ Vendor-Specific-Application-Id ] +[ Result-Code ] +[ Experimental-Result ] +{ Auth-Session-State } + +``` + +``` +{ Origin-Host } +{ Origin-Realm } +*[ Supported-Features ] +*[ AVP ] +*[ Failed-AVP ] +*[ Proxy-Info ] +*[ Route-Record ] +``` + +## 7.4 Information Elements + +### 7.4.1 General + +The following table describes the Diameter AVPs defined for the SLg interface protocol, their AVP Code values, types, possible flag values and whether the AVP may or not be encrypted. + +**Table 7.4.1-1: Diameter ELP Application AVPs** + +| Attribute Name | AVP Code | Section defined | Value Type | AVP Flag rules | | | | | +|-------------------------------|----------|-----------------|-------------|----------------|-----|------------|----------|-------------| +| | | | | Must | May | Should not | Must not | May Encrypt | +| SLg-Location-Type | 2500 | 7.4.2 | Enumerated | M, V | | | | No | +| LCS-EPS-Client-Name | 2501 | 7.4.3 | Grouped | M, V | | | | No | +| LCS-Requestor-Name | 2502 | 7.4.4 | Grouped | M, V | | | | No | +| LCS-Priority | 2503 | 7.4.5 | Unsigned32 | M, V | | | | No | +| LCS-QoS | 2504 | 7.4.6 | Grouped | M, V | | | | No | +| LCS-QoS-Class | 2523 | 7.4.27 | Enumerated | M, V | | | | No | +| Horizontal-Accuracy | 2505 | 7.4.7 | Unsigned32 | M, V | | | | No | +| Vertical-Accuracy | 2506 | 7.4.8 | Unsigned32 | M, V | | | | No | +| Vertical-Requested | 2507 | 7.4.9 | Enumerated | M, V | | | | No | +| Velocity-Requested | 2508 | 7.4.10 | Enumerated | M, V | | | | No | +| Response-Time | 2509 | 7.4.11 | Enumerated | M, V | | | | No | +| Supported-GAD-Shapes | 2510 | 7.4.12 | Unsigned32 | M, V | | | | No | +| LCS-Codeword | 2511 | 7.4.13 | UTF8String | M, V | | | | No | +| LCS-Privacy-Check | 2512 | 7.4.14 | Enumerated | M, V | | | | No | +| Accuracy-Fulfilment-Indicator | 2513 | 7.4.15 | Enumerated | M, V | | | | No | +| Age-Of-Location-Estimate | 2514 | 7.4.16 | Unsigned32 | M, V | | | | No | +| Velocity-Estimate | 2515 | 7.4.17 | OctetString | M, V | | | | No | +| EUTRAN-Positioning-Data | 2516 | 7.4.18 | OctetString | M, V | | | | No | +| ECGI | 2517 | 7.4.19 | OctetString | M, V | | | | No | +| Location-Event | 2518 | 7.4.20 | Enumerated | M, V | | | | No | +| Pseudonym-Indicator | 2519 | 7.4.21 | Enumerated | M, V | | | | No | +| LCS-Service-Type-ID | 2520 | 7.4.22 | Unsigned32 | M, V | | | | No | +| LCS-Privacy-Check-Non-Session | 2521 | 7.4.23 | Grouped | M, V | | | | No | +| LCS-Privacy-Check-Session | 2522 | 7.4.24 | Grouped | M, V | | | | No | +| Reserved | 2523 | | | | | | | | +| Reserved | 2524 | | | | | | | | +| Reserved | 2525 | | | | | | | | +| Reserved | 2526 | | | | | | | | +| Reserved | 2527 | | | | | | | | +| Reserved | 2528 | | | | | | | | +| Reserved | 2529 | | | | | | | | +| Reserved | 2530 | | | | | | | | +| Reserved | 2531 | | | | | | | | +| Reserved | 2532 | | | | | | | | +| Reserved | 2532 | | | | | | | | +| Reserved | 2533 | | | | | | | | +| Reserved | 2534 | | | | | | | | +| Reserved | 2535 | | | | | | | | +| Reserved | 2535 | | | | | | | | +| Reserved | 2536 | | | | | | | | +| Reserved | 2537 | | | | | | | | +| Reserved | 2538 | | | | | | | | +| Reserved | 2539 | | | | | | | | +| Reserved | 2540 | | | | | | | | +| Reserved | 2541 | | | | | | | | +| Reserved | 2542 | | | | | | | | +| Reserved | 2543 | | | | | | | | +| Reserved | 2544 | | | | | | | | +| Reserved | 2545 | | | | | | | | +| Reserved | 2546 | | | | | | | | +| Reserved | 2547 | | | | | | | | +| Reserved | 2548 | | | | | | | | +| Reserved | 2549 | | | | | | | | +| Reserved | 2550 | | | | | | | | +| Reserved | 2551 | | | | | | | | +| Reserved | 2552 | | | | | | | | +| Reserved | 2553 | | | | | | | | +| 1xRTT-RCID | 2554 | 7.4.59 | OctetString | V | | | M | No | + +Note: The AVP header bit denoted as 'M', indicates whether support of the AVP is required. The AVP header bit denoted as 'V', indicates whether the optional Vendor-ID field is present in the AVP header. For further details, see IETF RFC 3588 [4]. + +**Table 7.4.1-2: Diameter ELP Application reused AVPs** + +| Attribute Name | AVP Code | Reference | Value Type | Comment | +|-------------------------|----------|--------------------------------------------|-------------|---------------------------------------| +| LCS-Format-Indicator | 1237 | 3GPP TS 32.299 [10] | Enumerated | | +| LCS-Name-String | 1238 | 3GPP TS 32.299 [10] | UTF8String | | +| LCS-Client-Type | 1241 | 3GPP TS 32.299 [10] | Enumerated | | +| LCS-Requestor-Id-String | 1240 | 3GPP TS 32.299 [10] | UTF8String | | +| Location-Estimate | 1242 | 3GPP TS 32.299 [10] | OctetString | | +| IMEI | 1402 | 3GPP TS 29.272 [11] | UTF8String | | +| MSISDN | 701 | 3GPP TS 29.329 [12] | OctetString | | +| Service-Selection | 493 | 3GPP TS 29.272 [11],
IETF RFC 5778 [16] | UTF8String | It is used to define the APN | +| User-Name | 1 | IETF RFC 3588 [4] | UTF8String | It is used to include the user's IMSI | +| Supported-Features | 628 | 3GPP TS 29.229 [17] | Grouped | | +| Feature-List-ID | 629 | 3GPP TS 29.229 [17] | Unsigned32 | See clause 7.4.25 | +| Feature-List | 630 | 3GPP TS 29.229 [17] | Unsigned32 | See clause 7.4.26 | +| Serving-Node | 2401 | 3GPP TS 29.173 [18] | Grouped | See clause 7.4.28 | + +### 7.4.2 SLg-Location-Type + +The SLg-Location-Type AVP is of type Enumerated. The following values are defined: + +CURRENT\_LOCATION (0) + +CURRENT\_OR\_LAST\_KNOWN\_LOCATION (1) + +INITIAL\_LOCATION (2) + +RESERVED (3) + +RESERVED (4) + +NOTIFICATION\_VERIFICATION\_ONLY (5) + +NOTE: Values (3) and (4) are reserved for future use. The other values are homogeneous with those defined for the equivalent information element in MAP. + +### 7.4.3 LCS-EPS-Client-Name + +The LCS-EPS-Client-Name AVP is of type Grouped. + +AVP format: + +LCS-EPS-Client-Name ::= + +[ LCS-Name-String ] +[ LCS-Format-Indicator ] + +The details of the LCS-Name-String AVP and the LCS-Format-Indicator AVP are described in 3GPP TS 32.299 [10]. + +### 7.4.4 LCS-Requestor-Name + +The LCS-Requestor-Name AVP is of type Grouped. + +AVP format: + +LCS-Requestor-Name ::= + +[ LCS-Requestor-Id-String ] +[ LCS-Format-Indicator ] + +The details of the LCS-Requestor-Id-String AVP and the LCS-Format-Indicator AVP are described in 3GPP TS 32.299 [10]. + +### 7.4.5 LCS-Priority + +The LCS-Priority AVP is of type Unsigned32. It indicates the priority of the location request. The value 0 shall indicate the highest priority, and the value 1 shall indicate normal priority. All other values shall be treated as 1 (normal priority). For details, refer to 3GPP TS 22.071 [15]. + +### 7.4.6 LCS-QoS + +The LCS-QoS AVP is of type Grouped. + +AVP format: + +LCS-QoS ::= +                    [ LCS-QoS-Class ] +                    [ Horizontal-Accuracy ] +                    [ Vertical-Accuracy ] +                    [ Vertical-Requested ] +                    [ Response-Time] + +### 7.4.7 Horizontal-Accuracy + +The Horizontal-Accuracy AVP is of type Unsigned32. Bits 6-0 corresponds to Uncertainty Code defined in 3GPP TS 23.032 [3]. The horizontal location error should be less than the error indicated by the uncertainty code with 67% confidence. Bits 7 to 31 shall be ignored. + +### 7.4.8 Vertical-Accuracy + +The Vertical-Accuracy AVP is of type Unsigned32. Bits 6-0 corresponds to Uncertainty Code defined in 3GPP TS 23.032 [3]. The vertical location error should be less than the error indicated by the uncertainty code with 67% confidence. Bits 7 to 31 shall be ignored. + +### 7.4.9 Vertical-Requested + +The Vertical-Requested AVP is of type Enumerated. The following values are defined: + +VERTICAL\_COORDINATE\_IS\_NOT\_REQUESTED (0) +VERTICAL\_COORDINATE\_IS\_REQUESTED (1) + +Default value if AVP is not present is: VERTICAL\_COORDINATE\_IS\_NOT\_REQUESTED (0). + +### 7.4.10 Velocity-Requested + +The Velocity-Requested AVP is of type Enumerated. The following values are defined: + +VELOCITY\_IS\_NOT\_REQUESTED (0) +VELOCITY\_IS\_REQUESTED (1) + +Default value if AVP is not present is: VELOCITY\_IS\_NOT\_REQUESTED (0). + +### 7.4.11 Response-Time + +The Response-Time AVP is of type Enumerated. The following values are defined: + +LOW\_DELAY (0) +DELAY\_TOLERANT (1) + +### 7.4.12 Supported-GAD-Shapes + +The Supported-GAD-Shapes AVP is of type Unsigned32 and it shall contain a bitmask. + +A node shall mark in the BIT STRING all Shapes defined in 3GPP TS 23.032 [3] it supports. + +Bits 6-0 in shall indicate the supported Shapes defined in 3GPP TS 23.032 [3]. Bits 7 to 31 shall be ignored. + +ellipsoidPoint (0) + +ellipsoidPointWithUncertaintyCircle (1) + +ellipsoidPointWithUncertaintyEllipse (2) + +polygon (3) + +ellipsoidPointWithAltitude (4) + +ellipsoidPointWithAltitudeAndUncertaintyEllipsoid (5) + +ellipsoidArc (6) + +### 7.4.13 LCS-Codeword + +The LCS-Codeword AVP is of type UTF8String. It indicates the potential codeword string to send in a notification message to the UE. + +### 7.4.14 LCS-Privacy-Check + +The LCS-Privacy-Check AVP is of type Enumerated. The following values are defined: + +ALLOWED\_WITHOUT\_NOTIFICATION (0) + +ALLOWED\_WITH\_NOTIFICATION (1) + +ALLOWED\_IF\_NO\_RESPONSE (2) + +RESTRICTED\_IF\_NO\_RESPONSE (3) + +NOT\_ALLOWED (4) + +Default value if AVP is not present is: ALLOWED\_WITHOUT\_NOTIFICATION (0). + +### 7.4.15 Accuracy-Fulfilment-Indicator + +The Accuracy-Fulfilment-Indicator AVP is of type Enumerated. The following values are defined: + +REQUESTED\_ACCURACY\_FULFILLED (0) + +REQUESTED\_ACCURACY\_NOT\_FULFILLED (1) + +### 7.4.16 Age-Of-Location-Estimate + +The Age-Of-Location-Estimate AVP is of type Unsigned32. It indicates how long ago the location estimate was obtained in minutes, as indicated in 3GPP TS 29.002 [19]. + +### 7.4.17 Velocity-Estimate + +The Velocity-Estimate AVP is of type OctetString. It is composed of 4 or more octets with an internal structure according to 3GPP TS 23.032 [3]. + +### 7.4.18 EUTRAN-Positioning-Data + +The EUTRAN-Positioning-Data AVP is of type OctetString. It shall contain the encoded content of the "Positioning-Data" Information Element as defined in 3GPP TS 29.171 [7]. + +### 7.4.19 ECGI + +The ECGI AVP is of type OctetString. It indicates the E-UTRAN Cell Global Identifier. It is coded according to clause 8.21.5, in 3GPP TS 29.274 [8]. + +### 7.4.20 Location-Event + +The Location-Event AVP is of type Enumerated. The following values are defined: + +EMERGENCY\_CALL\_ORIGINATION (0) + +EMERGENCY\_CALL\_RELEASE (1) + +MO\_LR (2) + +EMERGENCY\_CALL\_HANDOVER (3) + +RESERVED (4) + +RESERVED (5) + +NOTE: Values (4) and (5) are reserved for future use. + +### 7.4.21 Pseudonym-Indicator + +The Pseudonym-Indicator AVP is of type Enumerated. It defines if a pseudonym is requested. The following values are defined: + +PSEUDONYM\_NOT\_REQUESTED (0) + +PSEUDONYM\_REQUESTED (1) + +Default value if AVP is not present is: PSEUDONYM\_NOT\_REQUESTED (0). + +### 7.4.22 LCS-Service-Type-ID + +The LCS-Service-Type-ID is of type Unsigned32. It defines the identifier associated to one of the Service Types for which the LCS client is allowed to locate the particular UE. + +### 7.4.23 LCS-Privacy-Check-Non-Session + +The LCS-Privacy-Check-Non-Session AVP is of type Grouped. + +AVP format: + +LCS-Privacy-Check-Non-Session ::= + +{ LCS-Privacy-Check } + +Default value if AVP is not present is that AVP LCS-Privacy-Check take value: ALLOWED\_WITHOUT\_NOTIFICATION (0). + +### 7.4.24 LCS-Privacy-Check-Session + +The LCS-Privacy-Check-Session AVP is of type Grouped. + +AVP format: + +LCS-Privacy-Check-Session ::= + +{ LCS-Privacy-Check } + +Default value if AVP is not present is that AVP LCS-Privacy-Check take value: NOT\_ALLOWED (4). + +### 7.4.25 Feature-List-ID + +The syntax of this AVP is defined in 3GPP TS 29.229 [17]. For this release, the Feature-List-ID AVP value shall be set to 1. + +### 7.4.26 Feature-List + +The syntax of this AVP is defined in 3GPP TS 29.229 [17]. A null value indicates that there is no feature used by the application. + +NOTE: There are no features defined for this release. + +### 7.4.27 LCS-QoS-Class + +The LCS-QoS-Class AVP is of the type Enumerated. The following values are defined. + +ASSURED (0) + +BEST EFFORT (1) + +### 7.4.28 Serving-Node + +The Serving-Node AVP is of type Grouped. This AVP shall contain the information about the network node serving the targeted user. + +- 7.4.29 void +- 7.4.30 void +- 7.4.31 void +- 7.4.32 void +- 7.4.33 void +- 7.4.34 void +- 7.4.35 void +- 7.4.36 void +- 7.4.37 void +- 7.4.38 void +- 7.4.39 void +- 7.4.40 void +- 7.4.41 void +- 7.4.42 void +- 7.4.43 void +- 7.4.44 void +- 7.4.45 void +- 7.4.46 void +- 7.4.47 void +- 7.4.48 void +- 7.4.49 void +- 7.4.50 void +- 7.4.51 void +- 7.4.52 void +- 7.4.53 void +- 7.4.54 void +- 7.4.55 void +- 7.4.56 void + +### 7.4.57 void + +### 7.4.58 void + +### 7.4.59 1xRTT-RCID + +The 1xRTT-RCID AVP is of type OctetString. It indicates the 1xRTT Reference Cell Id that consists of a Cell Identification Discriminator and a Cell Identification and shall be formatted according to octets 3 through the end of the Cell Identifier element defined in subclause 4.2.17 in 3GPP2 A.S0014-D [22]. The allowable cell discriminator values are "0000 0010", and "0000 0111". + +## 7.5 Result-Code AVP and Experimental-Result AVP Values + +### 7.5.1 General + +This section defines result code values that shall be supported by all Diameter implementations that conform to this specification. + +### 7.5.2 Success + +Result codes that fall within the Success category shall be used to inform a peer that a request has been successfully completed. The Result-Code AVP values defined in Diameter Base Protocol RFC 3588 [4] shall be applied. + +### 7.5.3 Permanent Failures + +Errors that fall within the Permanent Failures category shall be used to inform the peer that the request has failed, and should not be attempted again. The Result-Code AVP values defined in Diameter Base Protocol RFC 3588 [5] shall be applied. When one of the result codes defined here is included in a response, it shall be inside an Experimental-Result AVP and the Result-Code AVP shall be absent. + +#### 7.5.3.1 DIAMETER\_ERROR\_USER\_UNKNOWN (5001) + +This result code shall be sent by the MME to indicate that the user is unknown. This error code is defined in 3GPP TS 29.229 [17] + +#### 7.5.3.2 DIAMETER\_ERROR\_UNAUTHORIZED\_REQUESTING\_NETWORK (5490) + +This result code shall be sent by the MME to indicate that the requesting GMLC's network is not authorized to request UE location information. This error code is defined in 3GPP TS 29.173 [18] + +### 7.5.4 Transient Failures + +Errors that fall within the transient failures category are those used to inform a peer that the request could not be satisfied at the time that it was received. The request may be able to be satisfied in the future. + +#### 7.5.4.1 DIAMETER\_ERROR\_UNREACHABLE\_USER (4221) + +This result code shall be sent by the MME to indicate that the user could not be reached in order to perform positioning procedure. + +#### 7.5.4.2 DIAMETER\_ERROR\_SUSPENDED\_USER (4222) + +This result code shall be sent by the MME to indicate that the user is suspended in the MME. + +#### 7.5.4.3 DIAMETER\_ERROR\_DETACHED\_USER (4223) + +This result code shall be sent by the MME to indicate that the user is detached in the MME. + +#### 7.5.4.4 DIAMETER\_ERROR\_POSITIONING\_DENIED (4224) + +This result code shall be sent by the MME to indicate that the positioning procedure was denied. + +#### 7.5.4.5 DIAMETER\_ERROR\_POSITIONING\_FAILED (4225) + +This result code shall be sent by the MME to indicate that the positioning procedure failed. + +#### 7.5.4.6 DIAMETER\_ERROR\_UNKNOWN\_UNREACHABLE LCS\_CLIENT (4226) + +This result code shall be sent by the GMLC to indicate that the LCS Client was not known or could not be reached. + +# Annex A (informative): Change history + +| Change history | | | | | | | | +|----------------|-------|-----------|------|-----|----------------------------------------------------------------------------|--------|--------| +| Date | TSG # | TSG Doc. | CR | Rev | Subject/Comment | Old | New | +| 2010-03 | CT-47 | CP-100055 | | | 3GPP TS presented for approval in CT#47 | 2.0.0 | 9.0.0 | +| 2010-06 | CT-48 | CP-100286 | 0001 | | Velocity-Requested IE | 9.0.0 | 9.1.0 | +| 2010-09 | CT-49 | CP-100463 | 0002 | 1 | Addition of Command Codes | 9.1.0 | 9.2.0 | +| | | | 0003 | 1 | Notification Verification Only in Location Type | | | +| | | | 0004 | 1 | SLg for Inter Domain Scenarios | | | +| | | | 0005 | | Editorial Updates | | | +| | | | 0007 | | Definition of EUTRAN-Positioning-Data | | | +| | | | 0009 | | Clarification of LCS-priority AVP | | | +| 2010-12 | CT-50 | CP-100681 | 0010 | | Correction of error code assignment | 9.2.0 | 9.3.0 | +| | | | 0011 | | Correction of bit numbering in Horizontal and Vertical Accuracy IEs in SLg | | | +| | | | 0012 | | Units of Age of Location Estimate IE in SLg | | | +| | | | 0013 | 1 | Add missing Vendor Specific Application Id | | | +| 2011-03 | CT-51 | CP-110054 | 0014 | 2 | Essential correction on the value type of the ELP Application AVPs | 9.3.0 | 9.4.0 | +| | | | | | Update to Rel-10 version (MCC) | | | +| 2011-03 | | | | | Update to Rel-10 version (MCC) | 9.4.0 | 10.0.0 | +| 2011-09 | CT-53 | CP-110565 | 0015 | 2 | Correction to references | 10.0.0 | 10.1.0 | +| 2012-09 | CT-57 | | | | Update to Rel-11 version (MCC) | 10.0.0 | 11.0.0 | +| 2013-09 | CT-61 | CP-130457 | 0022 | 1 | Defining reserved values of the Location-Event AVP | 11.0.0 | 11.1.0 | +| 2015-03 | CT-67 | CP-150015 | 0030 | - | Renaming of Location-Type AVP | 11.1.0 | 11.2.0 | +| | | CP-150018 | 0026 | 1 | Location reporting in emergency IxSRVCC | | | \ No newline at end of file diff --git a/marked/Rel-11/29_series/29173/d0abac95583b52a3b35f74a215567334_img.jpg b/marked/Rel-11/29_series/29173/d0abac95583b52a3b35f74a215567334_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c218207bb57e78b8602039d630ad7d9306e0a3cb --- /dev/null +++ b/marked/Rel-11/29_series/29173/d0abac95583b52a3b35f74a215567334_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d2371f58bbe56264c00030c1f2c2c2780397bcb21fd96ad6babc18da076d3098 +size 52815 diff --git a/marked/Rel-11/29_series/29173/raw.md b/marked/Rel-11/29_series/29173/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..23419248c3639e065c4d058523911687fef5242d --- /dev/null +++ b/marked/Rel-11/29_series/29173/raw.md @@ -0,0 +1,556 @@ + + + + +Error! No +text of + +Error! No text of specified style in +document. + +# Contents + +| | | +|---------------------------------------------------------------------|----| +| Foreword ..... | 5 | +| 1 Scope..... | 6 | +| 2 References..... | 6 | +| 3 Definitions, symbols and abbreviations..... | 7 | +| 3.1 Definitions..... | 7 | +| 3.2 Abbreviations ..... | 7 | +| 4 General Description ..... | 7 | +| 4.1 Introduction ..... | 7 | +| 4.2 Architecture Overview ..... | 7 | +| 4.3 Functional Requirements of SLh Interface ..... | 8 | +| 5 Diameter-based SLh Interface ..... | 8 | +| 5.1 Introduction ..... | 8 | +| 5.2 Procedure Descriptions ..... | 8 | +| 5.2.1 Send Routing Information for LCS ..... | 8 | +| 5.2.1.1 General..... | 8 | +| 5.2.1.2 Detailed Behaviour of the HSS..... | 9 | +| 5.2.1.3 Detailed Behaviour of the GLMC ..... | 10 | +| 6 Protocol Specification and Implementations ..... | 10 | +| 6.1 Introduction ..... | 10 | +| 6.1.1 Use of Diameter Base Protocol ..... | 10 | +| 6.1.2 Securing Diameter Messages ..... | 10 | +| 6.1.3 Accounting Functionality ..... | 10 | +| 6.1.4 Use of Sessions..... | 11 | +| 6.1.5 Transport Protocol..... | 11 | +| 6.1.6 Routing Considerations ..... | 11 | +| 6.1.7 Advertising Application Support..... | 11 | +| 6.1.8 Diameter Application Identifier..... | 11 | +| 6.1.9 User Identity to HSS resolution..... | 11 | +| 6.2 Commands..... | 12 | +| 6.2.1 Introduction ..... | 12 | +| 6.2.2 Command-Code values ..... | 12 | +| 6.2.3 LCS-Routing-Info-Request (RIR) Command ..... | 12 | +| 6.2.4 LCS-Routing-Info-Answer (RIA) Command..... | 13 | +| 6.3 Result-Code AVP and Experimental-Result AVP Values..... | 14 | +| 6.3.1 General ..... | 14 | +| 6.3.2 Success ..... | 14 | +| 6.3.3 Permanent Failures ..... | 14 | +| 6.3.3.1 DIAMETER_ERROR_USER_UNKNOWN (5001) ..... | 14 | +| 6.3.3.2 DIAMETER_ERROR_UNAUTHORIZED_REQUESTING_NETWORK (5490) ..... | 14 | +| 6.3.4 Transient Failures ..... | 14 | +| 6.3.4.1 DIAMETER_ERROR_ABSENT_USER (4201)..... | 14 | +| 6.4 AVPs ..... | 14 | +| 6.4.1 General ..... | 14 | +| 6.4.2 LMSI..... | 15 | +| 6.4.3 Serving-Node..... | 15 | +| 6.4.4 MME-Name..... | 16 | +| 6.4.5 MSC-Number ..... | 16 | +| 6.4.6 LCS-Capabilities-Sets ..... | 16 | +| 6.4.7 GMLC-Address ..... | 16 | +| 6.4.8 Additional-Serving-Node ..... | 16 | +| 6.4.9 PPR-Address..... | 17 | +| 6.4.10 Feature-List-ID AVP..... | 17 | +| 6.4.11 Feature-List AVP..... | 17 | +| 6.4.12 MME-Realm..... | 17 | + +Annex A (informative): Change history................................................................................................................ 18 + +# --- Foreword + +This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +# --- 1 Scope + +The present document describes the Diameter-based SLh interface between the GMLC and the HSS defined for the Control Plane LCS in EPC. + +LCS procedures over the SLh interface are defined in the 3GPP TS 23.271 [2]. + +This specification defines the Diameter application for the GMLC-HSS, SLh reference point. The interactions between the HSS and the GMLC are specified, including the signalling flows. As LCS procedures over the Diameter-based SLh interface are identical to the MAP-based Lh interface, the descriptions of the Lh MAP operations defined in the 3GPP TS 29.002 [3] are mapped into the descriptions of the SLh Diameter commands. + +# --- 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.271: "Functional stage 2 description of Location Services (LCS)". +- [3] 3GPP TS 29.002: "Mobile Application Part (MAP) specification". +- [4] 3GPP TS 29.228: "IP multimedia (IM) Subsystem Cx Interface; Signalling flows and Message Elements". +- [5] IETF RFC 3588: "Diameter Base Protocol". +- [6] 3GPP TS 33.210: "3G security; Network Domain Security (NDS); IP network layer security". +- [7] IETF RFC 4960: "Stream Control Transport Protocol". +- [8] 3GPP TS 29.229: "Cx and Dx Interfaces based on the Diameter protocol; protocol details". +- [9] 3GPP TS 29.329: "Sh Interface based on the Diameter protocol; protocol details". +- [10] 3GPP TS 23.003: "Numbering, addressing and identification ". +- [11] 3GPP TS 23.012: "Location Management Procedures". +- [12] 3GPP TS 29.272: "Mobility Management Entity (MME) and Serving GPRS Support Node (SGSN) related interfaces based on Diameter protocol". +- [13] IETF RFC 2234: "Augmented BNF for syntax specifications". +- [14] 3GPP TS 29.234: "3GPP system to Wireless Local Area Network (WLAN) Interworking; Stage 3". +- [15] ITU-T Recommendation E.164: "The international public telecommunication numbering plan". + +# --- 3 Definitions, symbols and abbreviations + +## 3.1 Definitions + +For the purposes of the present document, the terms and definitions given in 3GPP TR 21.905 [1], 3GPP TS 23.271 [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]. + +## 3.2 Abbreviations + +For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in 3GPP TR 21.905 [1]. + +| | | +|--------|-------------------------------------------| +| ABNF | Augmented Backus-Naur form | +| AVP | Attribute Value Pair | +| H-GMLC | Home-Gateway Mobile Location Centre | +| IANA | Internet Assigned Numbers Authority | +| PMD | Pseudonym mediation device functionality | +| PPR | Privacy Profile Register | +| R-GMLC | Requesting-Gateway Mobile Location Centre | +| RFC | Request For Comments | +| V-GMLC | Visited-Gateway Mobile Location Centre | + +# --- 4 General Description + +## 4.1 Introduction + +The SLh reference point between the GMLC and the HSS is defined in the 3GPP TS 23.271 [2]. + +This document describes the Diameter-based SLh interface related procedures, message parameters and protocol specifications. + +## 4.2 Architecture Overview + +The architecture for support of Location Services in GSM, UMTS and EPS has been defined in 3GPP TS 23.271 [2] and the relevant network elements and interfaces are shown in the figure 4.2-1. + +![Figure 4.2-1: Overview of the LCS Functional Architecture. The diagram shows a central GMLC connected to an HSS via the SLh interface. The GMLC is also connected to seven other entities via various interfaces: External LCS Client (Le), MME (SLg), SGSN (Lg), MSC/MSC Server (Lg), PPR (Lpp), PMD (Lid), and AAA Server (La).](d0abac95583b52a3b35f74a215567334_img.jpg) + +``` + +graph TD + HSS[HSS] -- SLh --> GMLC[GMLC] + GMLC -- Le --> ELCS[External LCS Client] + GMLC -- SLg --> MME[MME] + GMLC -- Lg --> SGSN[SGSN] + GMLC -- Lg --> MSC[MSC/MSC Server] + GMLC -- Lpp --> PPR[PPR] + GMLC -- Lid --> PMD[PMD] + GMLC -- La --> AAA[AAA Server] + +``` + +Figure 4.2-1: Overview of the LCS Functional Architecture. The diagram shows a central GMLC connected to an HSS via the SLh interface. The GMLC is also connected to seven other entities via various interfaces: External LCS Client (Le), MME (SLg), SGSN (Lg), MSC/MSC Server (Lg), PPR (Lpp), PMD (Lid), and AAA Server (La). + +**Figure 4.2-1: Overview of the LCS Functional Architecture** + +In this architecture, the SLh interface is defined between the Gateway Mobile Location Center (GMLC) and the Home Subscriber Server (HSS) to allow the GMLC to request routing information from the HLR or HSS. + +## 4.3 Functional Requirements of SLh Interface + +The requirements for SLh interface are defined in 3GPP TS 23.271 [2]. + +The SLh interface is used by the GMLC to request routing information from the HSS i.e. the address of the H-GMLC, and/or the address of the visited MSC/MSC server, SGSN, 3GPP AAA server or MME for a particular target UE whose location has been requested. + +# 5 Diameter-based SLh Interface + +## 5.1 Introduction + +This section describes the Diameter-based SLh interface related procedures and Information elements exchanged between functional entities. + +In the tables that describe the Information Elements transported by each Diameter command, each Information Element is marked as (M) Mandatory, (C) Conditional or (O) Optional in the "Cat." column. For the correct handling of the Information Element according to the category type, see the description detailed in section 6 of the 3GPP TS 29.228 [4]. + +## 5.2 Procedure Descriptions + +### 5.2.1 Send Routing Information for LCS + +#### 5.2.1.1 General + +This procedure is used between the GMLC and the HSS. The procedure is invoked by the GMLC and is used: + +- To retrieve routing information for LCS for a specified user from the HSS. + +This procedure is mapped to the commands LCS-Routing-Info-Request/Answer in the Diameter application specified in chapter 6. Tables 5.2.1.1/1 and 5.2.1.1/2 detail the involved information elements. + +**Table 5.2.1.1/1: Send Routing Information for LCS (SLh-LCS-SRI)** + +| Information element name | Mapping to Diameter AVP | Cat. | Description | +|---------------------------------------------|-------------------------|------|-------------------------------------------------------------------------------------------------------------------------| +| IMSI | User-Name | C | This information element shall contain the IMSI of the targeted user. This IE shall be present if the MSISDN is absent. | +| MSISDN | MSISDN | C | This information element shall contain the MSISDN of the targeted user. This IE shall be present if the IMSI is absent. | +| GMLC Number | GMLC-Number | O | This information element shall contain the ISDN (E.164) number of the requesting GMLC. | +| Supported Features (See 3GPP TS 29.229 [8]) | Supported-Features | O | If present, this information element shall contain the list of features supported by the origin host. | + +**Table 5.2.1.1/2: Send Routing Information for LCS (SLh-LCS-SRI) Resp** + +| Information element name | Mapping to Diameter AVP | Cat. | Description | +|---------------------------------------------|-----------------------------------|------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Result (See 5.3.5) | Result-Code / Experimental-Result | M | Result of the request.
Result-Code AVP shall be used for errors defined in the Diameter Base Protocol.
Experimental-Result AVP shall be used for SLh errors. This is a grouped AVP which contains the 3GPP Vendor ID in the Vendor-Id AVP, and the error code in the Experimental-Result-Code AVP. | +| IMSI | User-Name | C | This information element shall contain the IMSI of the targeted user. This IE shall be present if the MSISDN is absent. | +| MSISDN | MSISDN | C | This information element shall contain the MSISDN of the targeted user. This IE shall be present if the IMSI is absent. | +| LMSI | LMSI | C | This information element shall contain the LMSI allocated by the VLR. If available in the HSS, this IE shall be present only when the Result- Code is DIAMETER_SUCCESS and the serving node is a VLR. | +| Serving Node | Serving-Node | C | This information element shall contain the information about the network node serving the targeted user i.e. the name/number of the serving node (MME, SGSN, 3GPP AAA server or MSC/MSC server), the LCS capabilities sets supported by the serving node and the IP address of the visited GMLC associated with the serving node. This IE shall be present only when the Result- Code is DIAMETER_SUCCESS. | +| Additional Serving Node | Additional-Serving-Node | C | This information element shall contain the information about another network node serving the targeted user. This IE shall be present only when the Result- Code is DIAMETER_SUCCESS. There may be multiple instances of this IE in the response provided by the HSS. | +| Home GMLC Address | GMLC-Address | C | This information element shall contain the IP address of the H-GMLC. This IE shall be present only when the Result-Code is DIAMETER_SUCCESS. | +| PPR Address | PPR-Address | C | This information element shall contain the IP address of the Privacy Profile Register (PPR). If available in the HSS, this IE shall be present only when the Result-Code is DIAMETER_SUCCESS. | +| Supported Features (See 3GPP TS 29.229 [8]) | Supported-Features | O | If present, this information element shall contain the list of features supported by the origin host. | + +#### 5.2.1.2 Detailed Behaviour of the HSS + +Upon reception of the Send Routing Info for LCS request, the HSS shall, in the following order: + +1. Check whether the requesting GMLC belongs to a network authorized to request UE location information. If not, Experimental-Result shall be set to DIAMETER\_ERROR\_UNAUTHORIZED\_REQUESTING\_NETWORK in the Send Routing Information for LCS Response. +2. Check that the User Identity for whom data is asked exists in HSS. If not, Experimental-Result shall be set to DIAMETER\_ERROR\_USER\_UNKNOWN in the Send Routing Information for LCS Response. + +3. Check that there is serving node associated with the targeted user. If not, Experimental-Result shall be set to DIAMETER\_ERROR\_ABSENT\_USER in the Send Routing Information for LCS Response. + +If there is an error in any of the above steps then the HSS shall stop processing and shall return the error code specified in the respective step (see 3GPP TS 29.329 [9] and 3GPP TS 29.229 [8] for an explanation of the error codes). + +If the HSS cannot fulfil the received request for reasons not stated in the above steps, e.g. due to a database error or empty mandatory data elements, it shall stop processing the request and set Result-Code to DIAMETER\_UNABLE\_TO\_COMPLY. + +Otherwise, the requested operation shall take place and the HSS shall return the Result-Code AVP set to DIAMETER\_SUCCESS. The HSS returns one or several of the network addresses of the current MME, SGSN, 3GPP AAA server and/or VMSC/MSC server, the LCS capabilities of the serving nodes if available, the V-GMLC address associated with the serving nodes, if available, and whichever of the IMSI and MSISDN that was not provided in the Send Routing Info for LCS request. The HSS returns the address of the H-GMLC. The HSS also provides the address of the PPR, if available. + +Regarding the LCS capabilities of the serving nodes, if the HSS registered an SGSN via the S6d reference point (i.e., the registered serving node is an S4-SGSN), the HSS shall set the LCS-Capabilities-Set value to indicate support of Capability Set 5 (i.e., LCS release 7 or later version). If the HSS registered an MME, the HSS shall not indicate any LCS capability value to the GMLC (i.e., the LCS-Capabilities-Set AVP shall be absent over SLh when the serving node is an MME); in this case, the GMLC shall assume that the MME supports LCS Capability Set 5. + +#### 5.2.1.3 Detailed Behaviour of the GMLC + +If there are a serving node as well as additional serving nodes in a successful Send Routing Info for LCS response, the receiving shall use the serving node in preference to the additional serving nodes. + +# --- 6 Protocol Specification and Implementations + +## 6.1 Introduction + +### 6.1.1 Use of Diameter Base Protocol + +The Diameter Base Protocol as specified in IETF RFC 3588 [5] shall apply except as modified by the defined support of the methods and the defined support of the commands and AVPs, result and error codes as specified in this specification. Unless otherwise specified, the procedures (including error handling and unrecognised information handling) shall be used unmodified. + +### 6.1.2 Securing Diameter Messages + +For secure transport of Diameter messages, see 3GPP TS 33.210 [6]. + +### 6.1.3 Accounting Functionality + +Accounting functionality (Accounting Session State Machine, related command codes and AVPs) shall not be used on the SLh interface. + +### 6.1.4 Use of Sessions + +Between the GMLC and the HSS, Diameter sessions shall be implicitly terminated. An implicitly terminated session is one for which the server does not maintain state information. The client shall not send any re-authorization or session termination requests to the server. + +The Diameter base protocol includes the Auth-Session-State AVP as the mechanism for the implementation of implicitly terminated sessions. + +The client (server) shall include in its requests (responses) the Auth-Session-State AVP set to the value NO\_STATE\_MAINTAINED (1), as described in IETF RFC 3588 [5]. As a consequence, the server shall not maintain any state information about this session and the client shall not send any session termination request. Neither the Authorization-Lifetime AVP nor the Session-Timeout AVP shall be present in requests or responses. + +### 6.1.5 Transport Protocol + +Diameter messages over the SLh interface shall make use of SCTP IETF RFC 4960 [7] as transport protocol. + +### 6.1.6 Routing Considerations + +This clause specifies the use of the Diameter routing AVPs Destination-Realm and Destination-Host. + +If GMLC knows the address/name of the HSS for a certain user, both the Destination-Realm AVP and the Destination-Host AVP shall be present in the request. Otherwise, only the Destination-Realm AVP shall be present and the command shall be routed to the next Diameter node. Consequently, the Destination-Host AVP is declared as optional in the ABNF for all requests initiated by a GMLC. + +Destination-Realm AVP is declared as mandatory in the ABNF for all requests. + +### 6.1.7 Advertising Application Support + +The HSS and GMLC shall advertise support of the Diameter SLh Application by including the value of the application identifier in the Auth-Application-Id AVP within the Vendor-Specific-Application-Id grouped AVP of the Capabilities-Exchange-Request and Capabilities-Exchange-Answer commands. + +The vendor identifier value of 3GPP (10415) shall be included in the Supported-Vendor-Id AVP of the Capabilities-Exchange-Request and Capabilities-Exchange-Answer commands, and in the Vendor-Id AVP within the Vendor-Specific-Application-Id grouped AVP of the Capabilities-Exchange-Request and Capabilities-Exchange-Answer commands. + +The Vendor-Id AVP included in Capabilities-Exchange-Request and Capabilities-Exchange-Answer commands that is not included in the Vendor-Specific-Application-Id AVPs as described above shall indicate the manufacturer of the Diameter node as per RFC 3588 [5]. + +### 6.1.8 Diameter Application Identifier + +The SLh interface protocol shall be defined as an IETF vendor specific Diameter application, where the vendor is 3GPP. The vendor identifier assigned by IANA to 3GPP () is 10415. + +The Diameter application identifier assigned to the SLh interface application is 16777291 (allocated by IANA). + +### 6.1.9 User Identity to HSS resolution + +The User identity to HSS resolution mechanism enables the GMLC (for non-roaming case) or Diameter Relay/proxy agents in the home network (for roaming case) to find the identity of the HSS that holds the LCS subscription data and routing information for the target user when multiple and separately addressable HSSs have been deployed in the home network. The resolution mechanism is not required in networks that utilise a single HSS. + +This User identity to HSS resolution mechanism may rely on routing capabilities provided by Diameter and be implemented in the home operator network within dedicated Diameter Agents (Redirect Agents or Proxy Agents) responsible for determining the HSS identity based on the provided user identity. If this Diameter based implementation is selected by the Home network operator, the principles described in the 3GPP TS 29.272 [12] shall apply. + +NOTE: Alternatives to the user identity to HSS resolution Diameter based implementation are outside the scope of this specification. + +## 6.2 Commands + +### 6.2.1 Introduction + +This section defines the Command code values and related ABNF for each command described in this specification. + +### 6.2.2 Command-Code values + +This section defines Command-Code values for the SLh interface application as allocated by IANA. + +Every command is defined by means of the ABNF syntax IETF RFC 2234 [13], according to the rules in IETF RFC 3588 [5]. In the case, the definition and use of an AVP is not specified in this document, the guidelines in IETF RFC 3588 [5] shall apply. + +NOTE: For this release, the Vendor-Specific-Application-Id AVP is included as an optional AVP in all commands in order to ensure interoperability with diameter agents following a strict implementation of IETF RFC 3588 [5], by which messages not including this AVP will be rejected. IETF RFC 3588 [5] indicates that this AVP shall be present in all proxiable commands, such as those specified here, despite that the contents of this AVP are redundant since the application identifier is already present in the command header. This AVP may be removed in subsequent revisions of this specification, once the diameter base protocol is updated accordingly. + +The following Command Codes are defined in this specification: + +**Table 6.2.2/1: Command-Code values for SLh** + +| Command-Name | Abbreviation | Code | Section | +|--------------------------|--------------|---------|---------| +| LCS-Routing-Info-Request | RIR | 8388622 | 6.2.3 | +| LCS-Routing-Info-Answer | RIA | 8388622 | 6.2.4 | + +For these commands, the Application-ID field shall be set to 16777291 (application identifier of the SLh interface application, allocated by IANA). + +### 6.2.3 LCS-Routing-Info-Request (RIR) Command + +The LCS-Routing-Info-Request (RIR) command, indicated by the Command-Code field set to 8388622 and the "R" bit set in the Command Flags field, is sent from GMLC to HSS. + +Message Format + +``` +< LCS-Routing-Info-Request > ::= < Diameter Header: 8388622, REQ, PXY, 16777291 > + + < Session-Id > + + [ Vendor-Specific-Application-Id ] + + { Auth-Session-State } + + { Origin-Host } + + { Origin-Realm } + + [ Destination-Host ] + + { Destination-Realm } + + [ User-Name ] + + [ MSISDN ] + + [ GMLC-Number ] + + *[ Supported-Features ] + + *[ Proxy-Info ] + + *[ Route-Record ] + + *[ AVP ] +``` + +### 6.2.4 LCS-Routing-Info-Answer (RIA) Command + +The LCS-Routing-Info-Answer (RIA) command, indicated by the Command-Code field set to 8388622 and the 'R' bit cleared in the Command Flags field, is sent from HSS to GMLC. + +#### Message Format + +``` +< LCS-Routing-Info-Answer > ::= < Diameter Header: 8388622, PXY, 16777291 > + +< Session-Id > +[ Vendor-Specific-Application-Id ] +[ Result-Code ] +[ Experimental-Result ] +{ Auth-Session-State } +{ Origin-Host } +{ Origin-Realm } +*[ Supported-Features ] +[ User-Name ] +[ MSISDN ] +[ LMSI ] +[ Serving-Node ] +*[ Additional-Serving-Node ] +[ GMLC-Address ] +[ PPR-Address ] +*[ AVP ] +*[ Failed-AVP ] +*[ Proxy-Info ] +*[ Route-Record ] +``` + +## 6.3 Result-Code AVP and Experimental-Result AVP Values + +### 6.3.1 General + +This section defines result code values that shall be supported by all Diameter implementations that conform to this specification. + +### 6.3.2 Success + +Result codes that fall within the Success category shall be used to inform a peer that a request has been successfully completed. The Result-Code AVP values defined in Diameter Base Protocol RFC 3588 [5] shall be applied. + +### 6.3.3 Permanent Failures + +Errors that fall within the Permanent Failures category shall be used to inform the peer that the request has failed, and should not be attempted again. The Result-Code AVP values defined in Diameter Base Protocol RFC 3588 [5] shall be applied. When one of the result codes defined here is included in a response, it shall be inside an Experimental-Result AVP and the Result-Code AVP shall be absent. + +#### 6.3.3.1 DIAMETER\_ERROR\_USER\_UNKNOWN (5001) + +This result code shall be sent by the HSS to indicate that the user identified by the IMSI or the MSISDN is unknown. This error code is defined in 3GPP TS 29.229 [8] + +#### 6.3.3.2 DIAMETER\_ERROR\_UNAUTHORIZED\_REQUESTING\_NETWORK (5490) + +This result code shall be sent by the HSS to indicate that the requesting GMLC's network is not authorized to request UE location information. + +### 6.3.4 Transient Failures + +Errors that fall within the transient failures category are those used to inform a peer that the request could not be satisfied at the time that it was received. The request may be able to be satisfied in the future. + +#### 6.3.4.1 DIAMETER\_ERROR\_ABSENT\_USER (4201) + +This result code shall be sent by the HSS to indicate that the location of the targeted user is not known at this time to satisfy the requested operation. + +## 6.4 AVPs + +### 6.4.1 General + +The following table specifies the Diameter AVPs defined for the SLh interface protocol, their AVP Code values, types, possible flag values and whether or not the AVP may be encrypted. The Vendor-ID header of all AVPs defined in this specification shall be set to 3GPP (10415). + +**Table 6.4.1/1: SLh specific Diameter AVPs** + +| Attribute Name | AVP Code | Section defined | Value Type | AVP Flag rules | | | | | +|-------------------------|----------|-----------------|------------------|----------------|-----|------------|----------|-----------| +| | | | | Must | May | Should not | Must not | May Encr. | +| LMSI | 2400 | 6.4.2 | OctetString | M, V | | | | No | +| Serving-Node | 2401 | 6.4.3 | Grouped | M, V | | | | No | +| MME-Name | 2402 | 6.4.4 | DiameterIdentity | M, V | | | | No | +| MSC-Number | 2403 | 6.4.5 | OctetString | M, V | | | | No | +| LCS-Capabilities-Sets | 2404 | 6.4.6 | Unsigned32 | M, V | | | | No | +| GMLC-Address | 2405 | 6.4.7 | Address | M, V | | | | No | +| Additional-Serving-Node | 2406 | 6.4.8 | Grouped | M, V | | | | No | +| PPR-Address | 2407 | 6.4.9 | Address | M, V | | | | No | +| MME-Realm | 2408 | 6.4.12 | DiameterIdentity | V | | | M | No | + +NOTE 1: The AVP header bit denoted as "M", indicates whether support of the AVP is required. The AVP header bit denoted as "V", indicates whether the optional Vendor-ID field is present in the AVP header. For further details, see IETF RFC 3588 [5]. + +The following table specifies the Diameter AVPs re-used by the SLh interface protocol from existing Diameter Applications, including a reference to their respective specifications and when needed, a short description of their use within SLh. + +Any other AVPs from existing Diameter Applications, except for the AVPs from Diameter Base Protocol, do not need to be supported. The AVPs from Diameter Base Protocol are not included in table 6.4.1/2, but they may be re-used for the SLh protocol. + +**Table 6.4.1/2: SLh re-used Diameter AVPs** + +| Attribute Name | Reference | Comments | +|-----------------------|---------------------|--------------------| +| MSISDN | 3GPP TS 29.329 [9] | | +| SGSN-Number | 3GPP TS 29.272 [12] | | +| Supported-Features | 3GPP TS 29.229 [8] | | +| Feature-List-ID | 3GPP TS 29.229 [8] | See section 6.4.10 | +| Feature-List | 3GPP TS 29.229 [8] | See section 6.4.11 | +| GMLC-Number | 3GPP TS 29.272 [12] | | +| 3GPP-AAA-Server-Name | 3GPP TS 29.234 [14] | | + +### 6.4.2 LMSI + +The LMSI AVP is of type OctetString and it shall contain the Local Mobile Station Identity (LMSI) allocated by the VLR, as defined in 3GPP TS 23.003 [10]. For further details on the encoding of this AVP, see 3GPP TS 23.003[10]. + +### 6.4.3 Serving-Node + +The Serving-Node AVP is of type Grouped. This AVP shall contain the information about the network node serving the targeted user. + +AVP format + +Serving-Node ::= + +[ SGSN-Number ] + [ MME-Name ] + [ MME-Realm ] + [ MSC-Number ] + [ 3GPP-AAA-Server-Name ] + [ LCS-Capabilities-Sets ] + [ GMLC-Address ] + \*[AVP] + +The GMLC-Address AVP included in the Serving-Node grouped AVP shall contain, if present, the IPv4 or IPv6 address of the GMLC associated with the serving node (i.e., either the home GMLC or the visited GMLC, depending on the location of the serving node). + +### 6.4.4 MME-Name + +The MME-Name AVP is of type DiameterIdentity and it shall contain the Diameter identity of the serving MME. For further details on the encoding of this AVP, see IETF RFC 3588 [5]. + +### 6.4.5 MSC-Number + +The MSC-Number AVP is of type OctetString and it shall contain the ISDN number of the serving MSC or MSC server in international number format as described in ITU-T Rec E.164 [15] and shall be encoded as a TBCD-string. See 3GPP TS 29.002 [3] for encoding of TBCD-strings. + +### 6.4.6 LCS-Capabilities-Sets + +The LCS-Capabilities-Sets AVP is of type Unsigned32 and it shall contain a bit mask. The meaning of the bits shall be as defined in 3GPP 29.002 [3]. + +### 6.4.7 GMLC-Address + +The GMLC-Address AVP is of type Address and shall contain the IPv4 or IPv6 address of H-GMLC or the V-GMLC associated with the serving node. + +### 6.4.8 Additional-Serving-Node + +The Additional-Serving-Node AVP is of type Grouped. This AVP shall contain the information about the network node serving the targeted user. + +AVP format + +``` +Additional-Serving-Node ::= + [ SGSN-Number ] + [ MME-Name ] + [ MME-Realm ] + [ MSC-Number ] + [ 3GPP-AAA-Server-Name ] + [ LCS-Capabilities-Sets ] + [ GMLC-Address ] + *[AVP] +``` + +The GMLC-Address AVP included in the Additional-Serving-Node grouped AVP shall contain, if present, the IPv4 or IPv6 address of the GMLC associated with the serving node (i.e., either the home GMLC or the visited GMLC, depending on the location of the serving node). + +### 6.4.9 PPR-Address + +The PPR-Address AVP is of type Address and contains the IPv4 or IPv6 address of the Privacy Profile Register for the targeted user. + +### 6.4.10 Feature-List-ID AVP + +The syntax of this AVP is defined in 3GPP TS 29.229 [8]. For this release, the Feature-List-ID AVP value shall be set to 1. + +### 6.4.11 Feature-List AVP + +The syntax of this AVP is defined in 3GPP TS 29.229 [8]. A null value indicates that there is no feature used by the application. + +NOTE: There is no feature defined for this release. + +### 6.4.12 MME-Realm + +The MME-Realm AVP is of type DiameterIdentity and it shall contain the Diameter Realm Identity of the serving MME. For further details on the encoding of this AVP, see IETF RFC 3588 [5]. + +# Annex A (informative): Change history + +| Change history | | | | | | | | | +|----------------|-------|-----------|------|-----|----------------------------------------------------------------|--------|--------|--| +| Date | TSG # | TSG Doc. | CR | Rev | Subject/Comment | Old | New | | +| 2010-03 | CT#47 | CP-090815 | | | TS presented for approval in CT#47 | 2.0.0 | 9.0.0 | | +| 2010-09 | CT#49 | CP-100463 | 0002 | 1 | Application ID and Command code values | 9.0.0 | 9.1.0 | | +| 2011-03 | - | - | - | - | Update to Rel-10 version (MCC) | 9.1.0 | 10.0.0 | | +| 2011-12 | CT#54 | CP-11786 | 0004 | 2 | Identifications of MME in location procedures | 10.0.0 | 10.1.0 | | +| 2012-03 | CT#55 | CP-120023 | 0007 | 1 | MSC-Number format | 10.1.0 | 10.2.0 | | +| 2012-09 | CT#57 | CP-120490 | 0008 | 1 | LCS-Capabilities-Set AVP | 10.2.0 | 10.3.0 | | +| 2012-09 | - | - | - | - | Update to Rel-11 version (MCC) | 10.3.0 | 11.0.0 | | +| 2012-12 | CT#58 | CP-120719 | 0013 | 1 | Clarification on the use of Vendor-Specific-Application-Id AVP | 11.0.0 | 11.1.0 | | \ No newline at end of file diff --git a/marked/Rel-11/29_series/29202/0236eff05bcb8f3a343ea7933aaa306b_img.jpg b/marked/Rel-11/29_series/29202/0236eff05bcb8f3a343ea7933aaa306b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9b6befbbefc60e9bdd320d8a00f3fdc6a8788398 --- /dev/null +++ b/marked/Rel-11/29_series/29202/0236eff05bcb8f3a343ea7933aaa306b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ca7dca06d047c0d233817ddaa2400fbfe181f60879859292c5ebb089dcc72132 +size 6123 diff --git a/marked/Rel-11/29_series/29202/43fec6623ab9cb223a9ff74e2d2a4402_img.jpg b/marked/Rel-11/29_series/29202/43fec6623ab9cb223a9ff74e2d2a4402_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6f8cd51303ebc62e8d760f74ce313200863cd158 --- /dev/null +++ b/marked/Rel-11/29_series/29202/43fec6623ab9cb223a9ff74e2d2a4402_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7e731e96d16af3e6f9d6ca567506948b746723e0a92dbb30e171e9cc775d5859 +size 7046 diff --git a/marked/Rel-11/29_series/29202/78d5774278a3f4a614f8c0ae485ce8d9_img.jpg b/marked/Rel-11/29_series/29202/78d5774278a3f4a614f8c0ae485ce8d9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..299834891b17cbada260235bb1aff4c0b596b0c6 --- /dev/null +++ b/marked/Rel-11/29_series/29202/78d5774278a3f4a614f8c0ae485ce8d9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4be11fe56208b75731b4c0bcad77c5be49641db714dd77774c59d95ad03ff9da +size 28226 diff --git a/marked/Rel-11/29_series/29202/a9ed452e3e099e1505f7b9ad182a11e9_img.jpg b/marked/Rel-11/29_series/29202/a9ed452e3e099e1505f7b9ad182a11e9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6df2c2045bd93b9d4dfbadb57f8bb99235885bf3 --- /dev/null +++ b/marked/Rel-11/29_series/29202/a9ed452e3e099e1505f7b9ad182a11e9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:962f6e532c755b1158c6b9c63b5b1c199c0afa6a925c1cd5ed97ef9e601e477c +size 6825 diff --git a/marked/Rel-11/29_series/29202/b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg b/marked/Rel-11/29_series/29202/b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fc9aef705b1a18917f686df08eeb2f7f0e9716a6 --- /dev/null +++ b/marked/Rel-11/29_series/29202/b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f17eab39c27a9ae7fa2cf1fa05ef23f52769a94562bc5ba01caba45ea9e302aa +size 75639 diff --git a/marked/Rel-11/29_series/29202/e928f4874ed492d3ad4c6fa2d29aedbc_img.jpg b/marked/Rel-11/29_series/29202/e928f4874ed492d3ad4c6fa2d29aedbc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b00ad3e7372644e88eefccf734b76039b7cf757c --- /dev/null +++ b/marked/Rel-11/29_series/29202/e928f4874ed492d3ad4c6fa2d29aedbc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9bcc9e4bffe7eac320ca750988d5cb2e7aa66920a8004f661d93381411087bd1 +size 37761 diff --git a/marked/Rel-11/29_series/29202/raw.md b/marked/Rel-11/29_series/29202/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..ce3901fbd3d9cdd57f0258c0733ba411940cceba --- /dev/null +++ b/marked/Rel-11/29_series/29202/raw.md @@ -0,0 +1,564 @@ + + + + + + +# --- Contents + +| | | +|-------------------------------------------------------------------------------------------|-----------| +| Foreword ..... | 4 | +| 1 Scope..... | 4 | +| 2 References..... | 4 | +| 2.1 Normative references ..... | 4 | +| 2.2 Informative references..... | 5 | +| 3 Definitions and abbreviations ..... | 5 | +| 3.1 Definitions..... | 5 | +| 3.2 Abbreviations ..... | 5 | +| 4 Introduction..... | 6 | +| 5 Protocol architectures..... | 6 | +| 5.1 Protocol architecture in the case of MTP-based SS7 signalling transport network ..... | 6 | +| 5.2 Protocol architecture in the case of IP-based SS7 signalling transport network..... | 6 | +| 5.2.1 M3UA 6 | | +| 5.2.2 MTP3-M2PA..... | 7 | +| 5.3 Protocol architecture in the case of ATM-based SS7 signalling transport network ..... | 7 | +| Annex A (Normative): The use of M3UA in 3GPP networks..... | 8 | +| A.1 Scope..... | 8 | +| A.2 Introduction..... | 8 | +| A.3 Protocol conformance to RFC 4666..... | 9 | +| Annex B (Informative): The use of M2PA in 3GPP networks ..... | 17 | +| B.1 Scope..... | 17 | +| B.2 Introduction..... | 17 | +| B.3 Protocol conformance to RFC 4165..... | 17 | +| Annex C (informative): Change history..... | 21 | + +# --- Foreword + +This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +# --- 1 Scope + +The present document defines the possible protocol architectures for transport of SS7 signalling protocols in Core Network. + +# --- 2 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. +- For a specific reference, subsequent revisions do not apply. +- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. + +## 2.1 Normative references + +- [1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications". +- [2] ITU-T Recommendation Q.701: "Functional description of the message transfer part (MTP) of signalling system No. 7". +- [3] ITU-T Recommendation Q.702: "Signalling data link". +- [4] ITU-T Recommendation Q.703: "Signalling link". +- [5] ITU-T Recommendation Q.704: "Signalling network functions and messages". +- [6] ITU-T Recommendation Q.705: "Signalling network structure". +- [7] ITU-T Recommendation Q.706: "Message transfer part signalling performance". +- [8] RFC 2960: "Stream Control Transmission Protocol". + +- [9] ITU-T Recommendation G.804: "ATM cell mapping into Plesiochronous Digital Hierarchy (PDH)". +- [10] ITU-T Recommendation I.112: "Vocabulary of terms for ISDNs". +- [11] ITU-T Recommendation I.361: "B-ISDN ATM layer specification". +- [12] ITU-T Recommendation I.363.5: "B-ISDN ATM Adaptation Layer specification: Type 5 AAL". +- [13] ITU-T Recommendation Q.2110: "B-ISDN ATM adaptation layer - Service specific connection oriented protocol (SSCOP)". +- [14] ITU-T Recommendation Q.2140: "B-ISDN ATM adaptation layer - Service specific coordination function for signalling at the network node interface (SSCF at NNI)". +- [15] ITU-T Recommendation Q.2210: "Message transfer part level 3 functions and messages using the services of ITU-T Recommendation Q.2140". +- [17] RFC 3309: "SCTP Checksum Change". +- [18] RFC 4666: Signaling System 7 (SS7) Message Transfer Part 3 (MTP3) - User Adaptation Layer (M3UA)". +- [19] RFC 4165: Signaling System 7 (SS7) Message Transfer Part 2 (MTP2) -User Peer-to-Peer Adaptation Layer (M2PA)". + +## 2.2 Informative references + +- [16] RFC 2719: "Framework Architecture for Signalling Transport". + +# --- 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]. + +(no further terms defined) + +## 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]. + +| | | +|-------|-------------------------------------------------------------| +| AAL5 | ATM Adaptation Layer type 5 | +| ATM | Asynchronous Transfer Mode | +| IP | Internet Protocol | +| MTP | Message Transfer Part | +| MTP1 | Message Transfer Part layer 1 | +| MTP2 | Message Transfer Part layer 2 | +| MTP3 | Message Transfer Part layer 3 | +| M2PA | Message Transfer Part 2 -User Peer-to-Peer Adaptation Layer | +| M3UA | MTP3-User Adaptation | +| PDH | Plesiochronous Digital Hierarchy | +| SSCF | Service Specific Coordination Function | +| SSCOP | Service Specific Connection Oriented Protocol | +| SCCP | Signalling Connection Control Part | +| SCTP | Stream Control Transmission Protocol | +| SDH | Synchronous Digital Hierarchy | +| TCAP | Transaction Capabilities Application Part | + +# --- 4 Introduction + +The Core Network enables the transport of SS7 signalling protocols between two entities by means of different underlying networks (e.g. MTP-based, IP-based or ATM-based). + +The transport of SS7 signalling protocol messages of any protocol layer that is identified by the MTP level 3 layer, in SS7 terms, as a user part (MTP3-user) shall be accomplished in accordance with the protocol architecture defined in the following sub-clauses. The list of these protocol layers includes, but is not limited to, Signalling Connection Control Part (SCCP). + +The transport of protocols which can be identified as SCCP-users, like for example TCAP, and in turn the transport of TCAP-users like MAP and CAP, shall also be accomplished in accordance with the defined protocol architectures, since their protocol messages are transferred as SCCP payload. + +# --- 5 Protocol architectures + +## 5.1 Protocol architecture in the case of MTP-based SS7 signalling transport network + +The transport of an MTP3-user signalling messages shall be accomplished in accordance with the relevant ITU-T Recommendations [2], [3], [4], [5], [6], [7]. + +The protocol architecture applicable in the case of MTP-based SS7 signalling transport network is shown in Figure 5.1/1 + +![Diagram of MTP-based SS7 signalling transport network protocol architecture](43fec6623ab9cb223a9ff74e2d2a4402_img.jpg) + +A diagram showing a vertical stack of four protocol layers. From top to bottom, the layers are: MTP3-User, MTP3, MTP2, and MTP1. Each layer is represented by a rectangular box with a thin black border, and the boxes are stacked on top of each other. + +| | +|-----------| +| MTP3-User | +| MTP3 | +| MTP2 | +| MTP1 | + +Diagram of MTP-based SS7 signalling transport network protocol architecture + +**Figure 5.1/1: Protocol architecture in the case of MTP-based SS7 signalling transport network** + +## 5.2 Protocol architecture in the case of IP-based SS7 signalling transport network + +### 5.2.1 M3UA + +The transport of an MTP3-user signalling messages shall be accomplished in accordance with the architecture defined by the "Framework Architecture for Signalling Transport" [16], by "Stream Control Transmission Protocol" [8] and by the IETF document available in Annex A. An implementation of SCTP to this document shall use the checksum method specified in RFC 3309 [17] instead of the method specified in RFC 2960 [8]. + +The M3UA protocol architecture applicable in the case of IP-based SS7 signalling transport network is shown in Figure 5.2/1 + +![Diagram of IP-based SS7 signalling transport network protocol architecture](a9ed452e3e099e1505f7b9ad182a11e9_img.jpg) + +A diagram showing a vertical stack of four protocol layers. From top to bottom, the layers are: MTP3-User, M3UA, SCTP, and IP. Each layer is represented by a rectangular box with a thin black border, and the boxes are stacked on top of each other. + +| | +|-----------| +| MTP3-User | +| M3UA | +| SCTP | +| IP | + +Diagram of IP-based SS7 signalling transport network protocol architecture + +**Figure 5.2/1: M3UA architecture in the case of IP-based SS7 signalling transport network** + +The definition of the use of M3UA in 3GPP core network is provided in Annex A to this specification. + +### 5.2.2 MTP3-M2PA + +An MTP3 signalling message can also be transported by M2PA, which shall be accomplished in accordance with IETF RFC 4165[19]. + +The M2PA protocol architecture applicable in the case of IP-based SS7 signalling transport network is shown in Figure 5.2/2 + +![](0236eff05bcb8f3a343ea7933aaa306b_img.jpg) + +| | +|------| +| MTP3 | +| M2PA | +| SCTP | +| IP | + +**Figure 5.2/2: M2PA architecture in the case of IP-based SS7 signalling transport network** + +The definition of the use of M2PA in 3GPP core network is provided in Annex B to this specification. + +## 5.3 Protocol architecture in the case of ATM-based SS7 signalling transport network + +The transport of an MTP3-user signalling messages shall be accomplished in accordance with the relevant ITU-T Recommendations [9], [10], [11], [12], [13], [14], [15] + +The protocol architectures applicable in the case of ATM-based SS7 signalling transport network are shown in Figure 5.3/1. + +![](78d5774278a3f4a614f8c0ae485ce8d9_img.jpg) + +**ATM over SDH** + +| | +|-----------| +| MTP3-User | +| MTP3 B | +| SSCF | +| SSCOP | +| AAL5 | +| ATM | + +**ATM over PDH** + +| | +|-----------| +| MTP3-User | +| MTP3 B | +| SSCF | +| SSCOP | +| AAL5 | +| G.804 | + +**Figure 5.3/1: Protocol architectures in the case of ATM-based SS7 signalling transport network** + +# --- Annex A (Normative): The use of M3UA in 3GPP networks + +## A.1 Scope + +This annex defines the application of M3UA in 3GPP core networks. The purpose of the Annex is to ensure the interoperability of different implementations of M3UAs used by different operators and vendors. This is achieved by: + +- Clarifying certain concepts which are used in RFC 4666; +- Defining those features in RFC 4666 for which support is mandatory; +- Defining those features in the RFC 4666 for which support is optional; +- Defining those features in RFC 4666 which shall not be used; + +The specification is intended for interfaces between network domains, however, it can also be used inside one network domain, and constitutes a minimum set of M3UA requirements to be supported between IP nodes and between IP nodes and SGW nodes in a 3GPP network. + +## --- A.2 Introduction + +M3UA may be used on a number of interfaces in a 3GPP core network. The annex is intended for the interface called A and C in figure 1. A is the Interface between two IP nodes that are equipped with SCTP, M3UA and a M3UA user. Examples of M3UA user are BICC, H.248, SCCP and ISUP. The interface can be used inside one network domain but also to interconnect network domains. Interface B can be used between network domains and inside network domains. Interface B is not in the scope for this annex, however, use of Q.701-Q.705 or Q.2210 on interface B is already standardised; in addition, M2PA is also endorsed for interface B in accordance with Annex B. Interface C is the interface between a node including SCTP, M3UA and a M3UA user and a node including SCTP, M3UA and M3UA signalling gateway functions.. This interface is inside one network domain. + +Interfaces A and C are similar. The main difference is that interface C shall also allow for interworking with the SS 7 network and therefore provides functions for the interworking. + +The signalling gateways in this picture are pure MTP3/3B-M3UA signaling gateways. They do not include any M3UA users. Still there could be a node including an M3UA user (e.g. SCCP functions) and a M3UA signalling gateway functions. In that case, the node will support all the interfaces A, B and C. + +![Figure 1: Use of M3UA in 3GPP core network. The diagram shows three network domains (Network domain 1, Network domain 2, and Network domain 3) connected via SG (Signaling Gateways). IP nodes, some including M3UA users, are connected to these SGs. Connections are labeled with A, B, and C.](b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg) + +The diagram illustrates the use of M3UA in a 3GPP core network across three network domains. + +Network domain 1 (top left) contains three 'IP node including M3UA user' boxes. Two are connected to an 'SG' circle via links labeled 'A' and 'C'. The third is connected to the same 'SG' via a link labeled 'A'. + +Network domain 3 (top right) contains two 'IP node including M3UA user' boxes connected to another 'SG' circle via links labeled 'A' and 'C'. + +Network domain 2 (bottom) is enclosed in a large curved boundary and contains two 'IP node' boxes. One is labeled 'including \*\*\*\*\*' and the other 'including M3UA user'. They are connected to a third 'SG' circle via links labeled 'C' and 'A'. + +The three 'SG' circles are interconnected: the SG in domain 1 connects to the SG in domain 3 via a link labeled 'A'; the SG in domain 1 connects to the SG in domain 2 via a link labeled 'B'; and the SG in domain 3 connects to the SG in domain 2 via a link labeled 'B'. + +Figure 1: Use of M3UA in 3GPP core network. The diagram shows three network domains (Network domain 1, Network domain 2, and Network domain 3) connected via SG (Signaling Gateways). IP nodes, some including M3UA users, are connected to these SGs. Connections are labeled with A, B, and C. + +Figure 1: Use of M3UA in 3GPP core network + +## A.3 Protocol conformance to RFC 4666 + +A minimum implementation shall support sections marked mandatory in the table below. It shall be possible to configure all implementations to interoperate (no error messages returned) with the minimum set. + +The table below makes comment to the sections in RFC 4666. In the comment column the following terms are used: + +- Mandatory: When support of text in a section is marked mandatory: + - o On an information element, message or message class, it means that a receiver shall understand the information element, message or message class and carry out the requested action. + - o For a procedure, it means that the procedure is mandatory to be carried out by the involved network elements. +- Optional: When support of the text in a section is marked optional the feature involved is only guaranteed to work between peer entities which are subject to a bilateral agreement between operators of those entities. If one end uses an optional message or information element and the other does not support it, then either a silent discard takes place of an information element as a part of the message or the message is discarded and an error message is returned. This is described as part of the handling of the optionality in the table. +- Excluded: This means that the feature shall not be used in a 3GPP environment + +Descriptive text means that the section does not include any requirements for this specification. + +Note: The word "heading" means that the section consists only of subordinate sections. + +The comments column also defines the behaviour of a minimum implementation if it does not support a message or an information element in a mandatory message. + + + +| Section number in M3UA RFC | Comments | +|-------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Abstract | Descriptive text | +| 1.Introduction | Descriptive text | +| 1.1 Scope | Descriptive text | +| 1.2 Terminology | Descriptive text. | +| 1.3 M3UA overview | Descriptive text. | +| 1.4 Functional area | Descriptive text. | +| 1.5 Sample Configurations | Descriptive text | +| 1.6 Definition of M3UA Boundaries | Descriptive text | +| 2 Conventions | Descriptive text | +| 3. M3UA Protocol Elements | Mandatory | +| 3.1 Common message header | Mandatory | +| 3.1.1 M3UA Protocol Version: | The version number field shall be set to 1 | +| 3.1.2 Message classes and types | The values are classified as follow
0-4 Mandatory
5-8 Excluded
9 Optional (Routing Key Management (RKM) Messages)
10 to 255 Excluded | +| 3.1.2 (Management (MGMT) message) | The values are classified as follow
0 Mandatory
1 Optional (Notify). When received and not supported the message maybe silently discarded.
2-255 Excluded | +| 3.1.2 (Transfer messages) | The values are classified as follow
0 Excluded
1 Mandatory
2 to 255 Excluded | +| 3.1.2 (Signalling network management (SSNM) messages) | The values are classified as follow
0 Excluded
1-6 Mandatory
7- 255 Excluded. | +| 3.1.2 (ASP State Maintenance (ASPSM) Messages) | The values are classified as follow
0 Excluded
1-6 Mandatory
7-255 Excluded | +| 3.1.2 (ASP Traffic Maintenance (ASPTM) Messages) | The values are classified as follow
0 Excluded
1-4 Mandatory
5 to 255 Excluded | +| 3.1.2 (Routing key management (RKM)) messages | Optional
If any of these messages is received and not supported an error message with the error code 0x04 (Unsupported message type) shall be sent | +| 3.1.3 Reserved | Mandatory | +| 3.1.4 Message length | Mandatory | + +| Section number in M3UA RFC | Comments | +|---------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 3.2 Variable Length Parameter Format Common Parameters: |

The values are classified as follows

0x0000-- 0x0003, 0x0005, 0x0008, 0x000a, 0x000e, 0x000f, 0x0010 0x0014—0x01ff Excluded

0x0007, 0x0009, 0x000c and 0x0012 Mandatory

0x0004 optional (INFO String) if received and not supported the message is processed but the optional information element is silently discarded,

0x0006 optional (Routing Context if received and not supported the message is processed but the optional information element is silently discarded,

0x000b optional (Traffic Mode Type) if received and not supported the message is processed but the optional information element is silently discarded,

0x0011 (ASP Identifier) if received and not supported the message is processed but the optional information element is silently discarded,

0x0012 Affected point code is mandatory. The support of value 0 in the mask field is mandatory. All other values is outside the scope of this annex.

0x0013 (Correlation ID) if received and not supported the message is processed but the optional information element is silently discarded,

| +| 3.2 Variable Length Parameter Format M3UA Specific Parameters |

The values are classified as follows

0x0201, 0x0202, 0x0203, 0x0211, 0x020d and 0x0214 to 0xffff Excluded

0x0204--0x0205, 0x0210 Mandatory

0x0200 optional (Network Appearance) if received and not supported the message is processed but the optional information element is silently discarded,

0x0206 Optinal (Concerned Destination). If received and not supported the message is processed but the optional information element is silently discarded.

0x0207 (Routing Key), 0x0208 (Registration Result), 0x0209 (Deregistration Result) 0x020a (Local Routing Key Identifier), 0x020b (Destination Point Code), 0x020c (Service Indicators) 0x020d (Subsystem Numbers), 0x020e (Originating Point Code List), 0x020f (Circuit Range), 0x0212 (Registration Status), 0x0213 (Deregistration Status) are parameters in optional message, and therefore no action is specified.

| +| 3.3 Transfer messages | These messages are mandatory at the interfaces A and C. | +| 3.3.1 Payload Data Message (DATA) |

The parameters Network Appearance, Routing Context, Correlation ID are optional

The parameter Protocol data is mandatory.

| +| 3.4 SS7 signalling network management messages | Heading | +| 3.4.1 Destination Unavailable (DUNA) |

The message is mandatory at the interface C.

The parameters Network Appearance, Routing Context, and INFO String are optional

The parameter Affected Point Code is mandatory

| +| 3.4.2 Destination Available (DAVA) |

The message is mandatory at the interface C

The parameters Network Appearance, Routing Context, and INFO String are optional.

The parameter Affected Point Code is mandatory

| +| 3.4.3 Destination State Audit (DAUD) |

The message is mandatory at the interface C

The parameters Network Appearance, Routing Context, and INFO String are optional.

The parameter Affected Point Code is mandatory

| + +| Section number in M3UA RFC | Comments | +|---------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 3.4.4 Signalling Congestion (SCON) | The message is mandatory at the interface C
The parameters Network Appearance, Routing Context, Congestion Indications and INFO String are optional
The parameter Affected point code is mandatory. | +| 3.4.5 Destination User Part Unavailable (DUPU) | The message is mandatory at the interfaces A and C.
The parameters Network Appearance, Routing Context, and INFO String are optional.

The parameters Affected point code and User/Cause are mandatory | +| 3.4.6 Destination Restricted (DRST) message | This message is mandatory. | +| 3.5 ASP State Maintenance (ASPSM) Messages | These messages are mandatory at the interfaces A and C. | +| 3.5.1 ASP Up message | The ASP Identifier and Info String parameters are optional | +| 3.5.2 ASP Up Acknowledgement Message | The Info String parameter is optional. | +| 3.5.3 ASP Down message | The Info String parameter is optional. | +| 3.5.4 ASP Down Acknowledgement message | The Info String parameter is optional. | +| 3.5.5 Heartbeat message | The message is mandatory. | +| 3.5.6 Heartbeat Acknowledgement message | The message is mandatory | +| 3.6 Routing Key Management messages | These messages are optional at the interfaces A and C. | +| 3.7 ASP Traffic Maintenance (ASPTM) Messages | These messages are mandatory at the interfaces A and C. | +| 3.7.1 ASP Active message | The parameters Traffic Mode Type, Routing Context and INFO String are optional. | +| 3.7.2 ASP Active Acknowledgement message | The Traffic Mode Type, Routing Context and INFO String are optional. | +| 3.7.3 ASP inactive message | The parameters Routing Context and INFO String are optional. | +| 3.7.4 ASP Inactive Acknowledgement | The parameters Routing Context INFO String are optional. | +| 3.8 Management (MGMT) Messages | Heading | +| 3.8.1 Error message | The message is mandatory at the interfaces A and C | +| 3.8.2 Notify message | The message is optional at the interfaces A and C | +| 4 Procedure | The application of a particular procedure at a certain interface is detailed in the following sections | +| 4.1 Procedures to Support the M3UA-User | Heading | +| 4.1.1 Receipt of Primitives from the M3UA-User | The procedure is mandatory at the interfaces A and C. | +| 4.1.2 Receipt of Primitives from the Layer Management | This section is outside the scope of this annex. | +| 4.2 Procedures to Support the Management of SCTP Associations | The procedures are mandatory at the interfaces A and C | +| 4.2.1 Receipt of M3UA Peer Management Messages | The two first paragraphs are outside the scope of this annex.
Last paragraph is mandatory. | +| 4.3 AS and ASP State Maintenance | The procedure is mandatory at the interfaces A and C. | +| 4.3.1 ASP States | Mandatory | +| 4.3.2 AS States | Mandatory | + +| Section number in M3UA RFC | Comments | +|-------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 4.3.3 M3UA Management Procedures for Primitives | This section is outside the scope of this annex. | +| 4.3.4 ASPM Procedures for Peer-to-Peer Messages | Heading | +| 4.3.4.1 ASP Up Procedure |

This procedure is mandatory at the interface C and is a subset of the procedure used at interface A. See also 4.3.4.1.2.

Note: The registration procedure is optional.

A received ASP Up must be acknowledged by an ASP Up Ack message, if no restriction applies e.g. maintenance.

| +| 4.3.4.1.1 M3UA Version Control | This procedure is mandatory at the interfaces A and C. | +| 4.3.4.1.2 IPSP Considerations (Asp Up) |

This procedure is mandatory at the interface A.

All comments applicable for section 4.3.4.1 and 4.3.4.2 are also applicable for this section.

| +| 4.3.4.2 ASP-Down Procedure |

This procedure is mandatory at the interface C and is a subset of the procedure used at interface A. See also 4.3.4.1.2.

A received ASP Down message must be acknowledged by an ASP Down Ack message, if no restriction applies eg maintenance reason.

| +| 4.3.4.3 ASP Active Procedure |

This procedure is mandatory at interface C and is a subset of the procedure used at interface A. See also 4.3.4.3.1.

Configuration data define which AS an ASP is a member of. The ASP Active message does not contain a Routing Context parameter. Consequently, the ASP Active Ack message does not include any Routing Context(s) parameter.

The traffic state an ASP has, is configured within the associated Application Server. If more than one physical entity (ASPs, SGPs or IPSPs) implements a logical entity (SG, AS) then loadshare with 1+k is the mandatory traffic mode.

A received ASP Active must be acknowledged by an ASP Active Ack message, if no restriction applies e.g. maintenance reason.

If a Routing Context parameter is included in the ASP Active message it is not needed to include the Routing Context parameter in the ASP Active Ack message. Note: This is a deviation to RFC 4666.

| +| 4.3.4.3.1 IPSP Considerations (ASP Active) |

This procedure is mandatory at the interface A.

All comments applicable for section 4.3.4.3 are also applicable for this section.

| +| 4.3.4.4 ASP Inactive Procedures |

This procedure is mandatory at the interface C and is a subset of the procedure used at interface A. See also 4.3.4.4.1.

Configuration data defines which AS an ASP is a member of.

It is optional to send several ASP Active Ack messages in response to a single ASP Active message.

A received ASP Inactive must be acknowledged by an ASP Inactive Ack message, if no restriction applies e.g. maintenance.

The sending of Notify message is mandatory if the As state is changed.

| +| 4.3.4.4.1 IPSP Considerations (ASP Inactive) |

This procedure is mandatory at the interface A.

All comments applicable for section 4.3.4.4 are also applicable for this section.

| + +| Section number in M3UA RFC | Comments | +|----------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 4.3.4.5 Notify Procedures | The procedure is mandatory at the interfaces A and C to reflect an AS state change. | +| 4.3.4.6 Heartbeat Procedures | The procedure is optional. | +| 4.4 Routing Key management procedure | The procedure is optional. | +| 4.5 Procedures to Support the Availability or Congestion Status of SS7 Destination | Heading | +| 4.5.1 At an SGP |

Note: The use of Transfer restricted message is a national option and is about the scope of this specification.

If the SG knows that the ASP supports DRST, then SG shall Send a DRST message, if the SG does not know whether the ASP supports the DRST message the SGW shall send a DAVA message if the destination earlier was unavailable. If the destination was available then no action is required.

| +| 4.5.2 At an ASP | Heading | +| 4.5.2.1 Single SG Configurations | It is mandatory for an ASP to interoperate with one Signaling Gateway. | +| 4.5.2.2 Multiple SG Configurations | It shall be possible to configure an ASP to handle at least a configuration consisting of two Signalling Gateways. | +| 4.5.3 ASP Auditing | Only the part related to international use in Q.704 is inside the scope of this annex. | +| 4.6 MTP 3 restart | The procedure is mandatory. | +| 5. Examples of M3UA Procedures | Descriptive text | +| 5.1. Establishment of Association and Traffic between SGPs and ASPs | Note The procedures defined in the sub-sections to 5.1 are a subset of the procedures defined in section 5.5. | +| 5.1.1 Single ASP in an Application Server ("1+0" sparing) | Descriptive text | +| 5.1.1.1 Single ASP in an Application Server ("1+0" sparing), No Registration | The use of RCn is optional. | +| 5.1.1.2 Single ASP in Application Server ("1+0" sparing), Dynamic Registration | The use of dynamic registration is optional. | +| 5.1.1.3 Single ASP in Multiple Application Servers (each with "1+0" sparing), Dynamic Registration (Case 1 - Multiple Registration Requests) | The use of dynamic registration is optional. | +| 5.1.1.4 Single ASP in Multiple Application Servers (each with "1+0" sparing), Dynamic Registration (Case 2 - Single Registration Request) | The use of dynamic registration is optional. | +| 5.1.2 Two ASPs in Application Server ("1+1" sparing) | This procedure is optional. | +| 5.1.3 Two ASPs in an Application Server ("1+1" sparing, loadsharing case). | The traffic mode parameter is optional in ASP-Active message | +| 5.1.4 Three ASPs in an Application Server ("n+k" sparing, loadsharing case) | The procedure is optional. | +| 5.2 ASP Traffic Failover Examples | Heading | + +| Section number in M3UA RFC | Comments | +|---------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 5.2.1 (1+1 Sparing, Withdrawal of ASP, Backup Override) | The use of the procedure "backup override" is optional. | +| 5.2.2 (1+1 Sparing, Backup Override) | The use of the procedure "backup override" is optional. | +| 5.2.3 (n+k Sparing, Loadsharing case, Withdrawal of ASP) | The procedure is optional | +| 5.3 Normal Withdrawal of an ASP from an Application Server and Teardown of an Association | The registration procedure is optional. Routing Contexts (RC) is optional. | +| 5.3.X Normal Withdrawal of the ASP from an Application Server (1+1 sparing) loadsharing and Teardown of Association |

Image: Sequence diagram showing the withdrawal of ASP 2 and ASP 1 from an SGP. The sequence is: SGP sends ASP Inactive to ASP 2; ASP 2 responds with ASP Inactive Ack; SGP sends ASP Inactive to ASP 1; ASP 1 responds with ASP Inactive Ack; SGP sends Notify to ASP 2; ASP 2 responds with ASP Down; SGP sends ASP Down Ack to ASP 2; SGP sends ASP Down to ASP 1; ASP 1 responds with ASP Down Ack.

 sequenceDiagram     participant SGP     participant ASP2 as ASP 2     participant ASP1 as ASP 1     Note left of SGP: Withdrawal of ASP 2     SGP->>ASP2: ASP Inactive     ASP2-->>SGP: ASP Inactive Ack     Note left of SGP: Withdrawal of ASP 1     SGP->>ASP1: ASP Inactive     ASP1-->>SGP: ASP Inactive Ack     SGP->>ASP2: Notify     ASP2-->>SGP: ASP Down     SGP-->>ASP2: ASP Down Ack     SGP->>ASP1: ASP Down     ASP1-->>SGP: ASP Down Ack

The figure is added for clarification.

| +| 5.4. Auditing Examples | Heading | +| 5.4.1. SG State: Uncongested/Available | Descriptive text. | +| 5.4.2. SG State: Congested (Congestion Level=2) /Available | Descriptive text. | +| 5.4.3. SG State: Unknown/Available | Descriptive text. | +| 5.4.4. SG State: Unavailable | Descriptive text. | +| 5.5 M3UA/MTP3-User Boundary Examples | Heading | +| 5.5.1 At an ASP | Heading | +| 5.5.1.1 Support for MTP-TRANSFER Primitives at the ASP | Heading | +| 5.5.1.1.1 Support for MTP-TRANSFER Request Primitive | The procedure is mandatory at the interface A and C.
This description is also applicable for an IPSP, so replace the abbreviation ASP with ASP/IPSP and SGP with SGP/IPSP | +| 5.5.1.1.2 Support for the MTP-TRANSFER Indication Primitive | The support is mandatory at the interface A and C.
This description is also applicable for an IPSP, so replace the abbreviation ASP with ASP/IPSP and SGP with SGP/IPSP. | +| 5.5.1.1.3 Support for ASP Querying of SS7 Destination States | This procedure is mandatory at the interface C.
The querying of congestion states is an optional national procedure and outside the scope of this annex. | +| 5.5.2 At an SGP | Heading | +| 5.5.2.1 Support for MTP-TRANSFER Request Primitive at the SGP | The procedure is mandatory at the interface C.
Network Appearance is optional. | + +| Section number in M3UA RFC | Comments | +|-----------------------------------------------------------------------------|--------------------------------------------------------------------------------| +| 5.5.2.2 Support for MTP-TRANSFER Indication Primitive at the SGP | The procedure is mandatory at the interface C | +| 5.5.2.3 Support for MTP-PAUSE, MTP-RESUME, MTP-STATUS Indication Primitives | Heading | +| 5.5.2.3.1 Destination Unavailable | The procedure is mandatory at the interface C | +| 5.5.2.3.2 Destination Available | The procedure is mandatory at the interface C | +| 5.5.2.3.3 SS7 Network Congestion | The procedure is mandatory at the interface C | +| 5.5.2.3.4 Destination User Part Unavailable | The procedure is mandatory at the interface C and optional at the interface A. | +| 5.6 Examples for IPSP communication. | Descriptive text. | + +# Annex B (Informative): The use of M2PA in 3GPP networks + +## B.1 Scope + +This annex defines the application of M2PA in 3GPP core networks as an option on interface B. The purpose of the Annex is to ensure the interoperability of different implementations of M2PA as used by different operators and vendors. This is achieved by: + +- Clarifying certain concepts which are used in RFC 4165; +- Defining those features in RFC 4165 for which support is mandatory; +- Defining those features in the RFC 4165 for which support is optional; +- Defining those features in RFC 4165 which shall not be used; + +This specification is intended for interfaces between network domains. However, it can also be used inside one network domain, and constitutes, in that case, a minimum set of M2PA requirements to be supported between IP nodes and between SRP nodes in a 3GPP network. + +## B.2 Introduction + +M2PA may be used between SRPs, i.e. interface B (refer to Figure 1 of Annex A). + +Figure 2 recommends how M2PA is used in a 3GPP IP based signalling network. + +![Diagram illustrating the use of M2PA in 3GPP core networks. It shows two network domains connected via a series of nodes. The left domain is a 3GPP core network containing three SG (Signaling Gateway) nodes and two SP (Service Point) nodes. The SG nodes are connected in a chain: SG1 to SG2 via M2PA, SG2 to SG3 via MTP3/M2PA. The SP nodes are connected to the SG nodes. The right domain is an SS7 signalling network based on MTP3/MTP2. The SG3 node is connected to the SS7 network via MTP3/MTP2.](e928f4874ed492d3ad4c6fa2d29aedbc_img.jpg) + +Diagram illustrating the use of M2PA in 3GPP core networks. It shows two network domains connected via a series of nodes. The left domain is a 3GPP core network containing three SG (Signaling Gateway) nodes and two SP (Service Point) nodes. The SG nodes are connected in a chain: SG1 to SG2 via M2PA, SG2 to SG3 via MTP3/M2PA. The SP nodes are connected to the SG nodes. The right domain is an SS7 signalling network based on MTP3/MTP2. The SG3 node is connected to the SS7 network via MTP3/MTP2. + +Figure B2.1: Use of M2PA in 3GPP core networks + +## B.3 Protocol conformance to RFC 4165 + +A minimum implementation shall support sections marked mandatory in the table below. It shall be possible to configure all implementations to interoperate (no error messages returned) with the minimum set. + +The table below makes comment to the sections in RFC 4165. In the comment column the following terms are used: + +- Mandatory: When support of text in a section is marked mandatory: + - o On an information element, message or message class, it means that a receiver shall understand the information element, message or message class and carry out the requested action. + +- For a procedure, it means that the procedure is mandatory to be carried out by the involved network elements. +- Optional: When support of the text in a section is marked optional the feature involved is only guaranteed to work between peer entities which are subject to a bilateral agreement between operators of those entities. If one end uses an optional information element and the other does not support it, then a silent discard takes place of an information element as a part of the message. This is described as part of the handling of the optionality in the table. +- Excluded: This means that the feature shall not be used in a 3GPP environment + +Descriptive text means that the section does not include any requirements for this specification. + +Note: The word "heading" means that the section consists only of subordinate sections. + +The comments column also defines the behaviour of a minimum implementation if it does not support a message or an information element in a mandatory message. + + + +| Section number in M2PA RFC | Comments | +|--------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Abstract | Descriptive text | +| 1.Introduction | Descriptive text | +| 1.1 Scope | Descriptive text | +| 1.2 Terminology | Descriptive text. | +| 1.3 Abbreviations | Descriptive text. | +| 1.4 Conventions | Descriptive text. | +| 1.5. Signaling Transport Architecture | Descriptive text | +| 1.5.1 Point Code Representation | Mandatory | +| 1.6 Services Provided by M2PA | Descriptive text | +| 1.6.1 Support for MTP Level 2 / MTP Level 3 Interface Boundary | Mandatory | +| 1.6.2 Support for Peer-to-Peer Communication | Mandatory | +| 1.7. Functions Provided by M2PA | Heading | +| 1.7.1 MTP2 Functionality | Descriptive text | +| 1.7.2 Mapping of SS7 and IP Entities | Mandatory | +| 1.7.3 SCTP Association Management | Mandatory | +| 1.7.4 Retention of MTP3 in the SS7 Network | Descriptive text | +| 1.8. Definition of the M2PA Boundaries | Heading | +| 1.8.1 Definition of the M2PA/MTP Level3 Boundaries | Descriptive text | +| 1.8.2 Definition of the Lower Layer Boundary between M2PA and SCTP | Descriptive text | +| 1.9. Differences Between M2PA and M2UA | Descriptive text | +| 2. Protocol Elements | Mandatory | +| 2.1 Common message header | Mandatory | +| 2.1.1 Version: | Mandatory | +| 2.1.2 Spare | Mandatory | +| 2.1.3 Message class | Mandatory | +| 2.1.4 Message Type | Mandatory | +| 2.1.5 Message Length | Mandatory | +| 2.2 M2PA Header | Mandatory | +| 2.2.1 Backward Sequence Number (BSN) | Mandatory | +| 2.2.2 Forward Sequence Number (FSN) | Mandatory | +| 2.3 M2PA Messages | Mandatory | +| 2.3.1 User Data | Mandatory | +| 2.3.2 Link Status | Mandatory | +| 2.3.2.1 Link Status Proving | Mandatory | +| 3 State Control | Heading | +| 3.1 SCTP Association State Control | Descriptive text | +| 3.2 M2PA Link State Control | Descriptive text | +| 4 Procedures | Mandatory | +| 4.1 Procedures to Support MTP2 Feature | Heading | +| 4.1.1 Signal Unit Format, Delimitation, Acceptance | Descriptive text | +| 4.1.2 MTP and SCTP Entities |

The content about how M2PA relates MTP and SCTP entities is Descriptive text.

The relationship between the streams of SCTP and M2PA Messages is mandatory.

| +| 4.1.3 Link Alignment | The procedure is Mandatory. | +| 4.1.4 Processor Outage | Mandatory | +| 4.1.5 Level 2 Flow Control | Mandatory | +| 4.1.6 Link Out of Service | Mandatory | +| 4.1.7 SCTP Association Problems | Mandatory | +| 4.1.8 Transmission and Reception Priorities | Mandatory | +| 4.1.9 M2PA Version Control | Mandatory | +| 4.2. Procedures to Support the MTP3/MTP2 Interface | Heading | +| 4.2.1 Sending and Receiving Messages | Mandatory | +| 4.2.2 MTP3 Signaling Link Congestion | Mandatory | +| 4.2.3 Changeover | Mandatory | +| 4.2.3.1 Multiple User Data Streams and Changeover | Descriptive text | +| 4.3 SCTP Considerations | Descriptive text | +| 4.3.1 SCTP Slow Start |

Descriptive text

Avoiding the negative effects of slow start is Mandatory.

| + +| Section number in M2PA RFC | Comments | +|--------------------------------------------|------------------| +| 5 Examples of M2PA Procedures | Descriptive text | +| 5.1 Link Initialization (Alignment) | Descriptive text | +| 5.2 Message Transmission and Reception | Descriptive text | +| 5.3 Link Status Indication | Descriptive text | +| 5.4 Link Status Message (Processor Outage) | Descriptive text | +| 5.5 Level 2 Flow Control | Descriptive text | +| 5.6 MTP3 Signaling Link Congestion | Descriptive text | +| 5.7. Link Deactivation | Descriptive text | +| 5.8 Link Changeover | Descriptive text | + +# Annex C (informative): Change history + +| Change history | | | | | | | | +|----------------|-------|-----------|------|-------------|--------------------------------------------------------------------------------------------------------|--------|--------| +| Date | TSG # | TSG Doc. | CR | R
e
v | Subject/Comment | Old | New | +| Feb 2001 | | | | | Initial draft | 0.0.1 | 0.0.2 | +| Feb 2001 | | | | | Second draft | 0.0.2 | 0.1.0 | +| Feb 2001 | | | | | Contributions and comments from TSG-CN WG4#6.1 Madrid Ad Hoc incorporated | 0.1.0 | 0.2.0 | +| Feb 2001 | | | | | Contributions and comments from TSG-CN WG4#6.1 Madrid Ad Hoc incorporated and draft further elaborated | 0.2.0 | 2.0.0 | +| Mar 2001 | | | | | Comments from TSG-CN WG4#7 incorporated. | 2.0.0 | 2.1.0 | +| Mar 2001 | CN#11 | NP-010079 | | | Annex A: M3UA updated to the latest available version 6 Approved in CN#11 | 2.1.0 | 4.0.0 | +| May 2001 | | | | | Foreword added | 4.0.0 | 4.0.1 | +| Sep 2001 | CN#13 | NP-010452 | 001 | | Change of M 3UA version | 4.0.1 | 4.1.0 | +| Sep 2001 | CN#13 | | | | Editorial clean up | 4.0.1 | 4.1.0 | +| Jun 2002 | CN#16 | | | | Corrupted Figure 5.3/1 fixed | 4.1.0 | 4.1.1 | +| Jun 2002 | CN#16 | | | | Rel-5 created after CN#16 | 4.1.1 | 5.0.0 | +| Sep 2002 | CN#17 | NP-020445 | 003 | 1 | Add reference to new IETF RFC on SCTP Checksum | 5.0.0 | 5.1.0 | +| Dec 2002 | CN#18 | NP-020585 | 007 | 2 | M3UA for 3GPP networks | 5.1.0 | 5.2.0 | +| Dec 2002 | CN#18 | NP-020585 | 009 | | IETF RFC reference for M3UA | 5.1.0 | 5.2.0 | +| Dec 2004 | CN#26 | | | | Rel-6 created after CN#26 | 5.2.0 | 6.0.0 | +| Jun 2007 | CT#36 | | | | Upgraded unchanged from Rel-6 | 6.0.0 | 7.0.0 | +| Jun 2007 | CT#36 | CP-070330 | 0013 | 3 | Use of M2PA in 3GPP core network signalling system | 7.0.0 | 8.0.0 | +| Sep 2007 | CT#37 | CP-070545 | 0014 | 2 | Protocol conformance to RFC4165(M2PA) | 8.0.0 | 8.1.0 | +| Sep 2007 | CT#37 | CP-070545 | 0015 | 2 | Change of protocol conformance to M3UA | 8.0.0 | 8.1.0 | +| Dec 2008 | CT#42 | | | | Copyright Notification updated | 8.1.0 | 8.1.1 | +| 2009-12 | - | - | - | - | Update to Rel-9 version (MCC) | 8.1.1 | 9.0.0 | +| 2011-03 | - | - | - | - | Update to Rel-10 version (MCC) | 9.0.0 | 10.0.0 | +| 2011-03 | CT#52 | CP-110371 | 0016 | | Removing reference to draft-ietf-sigtran-m3ua-implementors-guide-01 | 10.0.0 | 10.1.0 | +| 2012-09 | - | - | - | - | Update to Rel-11 version (MCC) | 10.1.0 | 11.0.0 | \ No newline at end of file diff --git a/marked/Rel-11/29_series/29204/088921fa3f5a44c8551815122517eefd_img.jpg b/marked/Rel-11/29_series/29204/088921fa3f5a44c8551815122517eefd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1e65a07ada6f7afe5222334ef58c43fe17e9e561 --- /dev/null +++ b/marked/Rel-11/29_series/29204/088921fa3f5a44c8551815122517eefd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d9c8f8b053f627f7672e19095b8c60306289a1c0696f80476f7a23d5df9c6b9e +size 81803 diff --git a/marked/Rel-11/29_series/29204/08c7a76a7786bd08b99dd4cb41583ef4_img.jpg b/marked/Rel-11/29_series/29204/08c7a76a7786bd08b99dd4cb41583ef4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..109a7b2e8ebfc99981f9735ab02363a7c23ee7ea --- /dev/null +++ b/marked/Rel-11/29_series/29204/08c7a76a7786bd08b99dd4cb41583ef4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:26b81e468be6612b26928b7eb4d2c2cab0059307cd99ceca63be9bc8c842c990 +size 36341 diff --git a/marked/Rel-11/29_series/29204/0b87abe67b21a93777287649c33e755d_img.jpg b/marked/Rel-11/29_series/29204/0b87abe67b21a93777287649c33e755d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2122ea71066c06caecf6ed39e33003412c5fe2f7 --- /dev/null +++ b/marked/Rel-11/29_series/29204/0b87abe67b21a93777287649c33e755d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:eef669bdb0bee1265070ce0e680e4ae177ef31d534a17300cb4850aa2960f4c5 +size 67438 diff --git a/marked/Rel-11/29_series/29204/1a827b10290f33d4fec04d0e8ef7a897_img.jpg b/marked/Rel-11/29_series/29204/1a827b10290f33d4fec04d0e8ef7a897_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6643c87216d8402ce173098ebf4e920f63ed5ac2 --- /dev/null +++ b/marked/Rel-11/29_series/29204/1a827b10290f33d4fec04d0e8ef7a897_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:914cc397f7594b26b6378c879d9138c0a037cdfdcdf72588a865177e45fedd7f +size 81095 diff --git a/marked/Rel-11/29_series/29204/26d664119ad25250780f554633444e54_img.jpg b/marked/Rel-11/29_series/29204/26d664119ad25250780f554633444e54_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7ace3e96f9a656b62935eee2c5fe0d20adf5162b --- /dev/null +++ b/marked/Rel-11/29_series/29204/26d664119ad25250780f554633444e54_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:884d097ea545accb61c51c5db4835c8f676d9d8fa0cfd7ed973c66939f177c99 +size 72912 diff --git a/marked/Rel-11/29_series/29204/49ee89a1d5852ab005dbbab6de09a8a6_img.jpg b/marked/Rel-11/29_series/29204/49ee89a1d5852ab005dbbab6de09a8a6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b635b999bcbe12ae5578d97d185d5ca0c16137c6 --- /dev/null +++ b/marked/Rel-11/29_series/29204/49ee89a1d5852ab005dbbab6de09a8a6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1a631c2b288b70963dbcf661fdd2c9c22f3ae60d8529be71733a2f0b72dd3d00 +size 53806 diff --git a/marked/Rel-11/29_series/29204/5860ad6bd2a2dd8d1ab12864b8f90f37_img.jpg b/marked/Rel-11/29_series/29204/5860ad6bd2a2dd8d1ab12864b8f90f37_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..dd4119d3f3faa99545bb92c85e182ec98ecffe36 --- /dev/null +++ b/marked/Rel-11/29_series/29204/5860ad6bd2a2dd8d1ab12864b8f90f37_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c0c556159292eb30b2dd51d65ce873ca74e5652a14ba16e159756b177b803667 +size 54159 diff --git a/marked/Rel-11/29_series/29204/5a4e62bead259c258d069fd3663ea670_img.jpg b/marked/Rel-11/29_series/29204/5a4e62bead259c258d069fd3663ea670_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8b4282467c864965190794bc5dc917dd9b6764ba --- /dev/null +++ b/marked/Rel-11/29_series/29204/5a4e62bead259c258d069fd3663ea670_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d3b4e839c6b2cbe018c50fd7c9c6152ff15f78f4fdb38b3dc36bbb555d78493f +size 68698 diff --git a/marked/Rel-11/29_series/29204/6629e8a87e7552e2454b7c3e9f6d73a0_img.jpg b/marked/Rel-11/29_series/29204/6629e8a87e7552e2454b7c3e9f6d73a0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..383eac3e0732ce5904d1f5f40b37889b59b86068 --- /dev/null +++ b/marked/Rel-11/29_series/29204/6629e8a87e7552e2454b7c3e9f6d73a0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9942350b81e9c22ee3844b06c429f860d9a82ff9ff431289d85c9bc2f57b0a37 +size 34589 diff --git a/marked/Rel-11/29_series/29204/79e1709a7317ead45379cbb8ff3ba802_img.jpg b/marked/Rel-11/29_series/29204/79e1709a7317ead45379cbb8ff3ba802_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4bcaaf8ddf35c1e5214d57e13a7283439f38d92d --- /dev/null +++ b/marked/Rel-11/29_series/29204/79e1709a7317ead45379cbb8ff3ba802_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:183b64f8f1230295745482f3a743ea0984b9ff658579feb104e657aa6f672c9a +size 107306 diff --git a/marked/Rel-11/29_series/29204/7efae06af3af43ffe5d4b956a679cf54_img.jpg b/marked/Rel-11/29_series/29204/7efae06af3af43ffe5d4b956a679cf54_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3bc7aa7327cbb8d10781217bc4e3ad3597eedb85 --- /dev/null +++ b/marked/Rel-11/29_series/29204/7efae06af3af43ffe5d4b956a679cf54_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:832fe8d7c19f1e36c3672d9607f49e0a74721333e2702971218b5dcd95a9d92a +size 83725 diff --git a/marked/Rel-11/29_series/29204/7f17c430b9598e4d748a8041457810b3_img.jpg b/marked/Rel-11/29_series/29204/7f17c430b9598e4d748a8041457810b3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f6315e9e9916f88f85268c57f306638dbe798ff0 --- /dev/null +++ b/marked/Rel-11/29_series/29204/7f17c430b9598e4d748a8041457810b3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d4e146977ef4ec21b10c624413a58935cd5bee0518563062ab3217138e6ff2dc +size 72387 diff --git a/marked/Rel-11/29_series/29204/8307f6b04df072c9332f9987e034272c_img.jpg b/marked/Rel-11/29_series/29204/8307f6b04df072c9332f9987e034272c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..472addeb6a01f9a65bd92b84c083a3a9b8ac088f --- /dev/null +++ b/marked/Rel-11/29_series/29204/8307f6b04df072c9332f9987e034272c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7be9f1ae37c4396ebd379855e222aa7e4e450169b4ec0c76976344459dbe6848 +size 100379 diff --git a/marked/Rel-11/29_series/29204/8e14350b4b669119a3bdfca7869110ca_img.jpg b/marked/Rel-11/29_series/29204/8e14350b4b669119a3bdfca7869110ca_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5c2cf90675bef3fff07d806655d83b5a2e9407a6 --- /dev/null +++ b/marked/Rel-11/29_series/29204/8e14350b4b669119a3bdfca7869110ca_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:78526ddca7f81b89b61d70c35b79534d4a9637ac17dd39e37b9904e615dec2e5 +size 71412 diff --git a/marked/Rel-11/29_series/29204/8fa679f79a1bb1f527cba9f29e784e89_img.jpg b/marked/Rel-11/29_series/29204/8fa679f79a1bb1f527cba9f29e784e89_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a924c281bfe715fb9dd7a9df4e6f214fde3414ea --- /dev/null +++ b/marked/Rel-11/29_series/29204/8fa679f79a1bb1f527cba9f29e784e89_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:052a48fb8169559b2142c01bd072a192249d923fda7728e351a583bcbd5b2f52 +size 93128 diff --git a/marked/Rel-11/29_series/29204/9791722d75115ddcc599b07d7bc35d73_img.jpg b/marked/Rel-11/29_series/29204/9791722d75115ddcc599b07d7bc35d73_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f45af4642a26637e81e1ce13eb14178129a67c53 --- /dev/null +++ b/marked/Rel-11/29_series/29204/9791722d75115ddcc599b07d7bc35d73_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2d0e72348415bde4d561515b2785a315448c089c6cde6a0c2896be84d863d6b1 +size 50911 diff --git a/marked/Rel-11/29_series/29204/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg b/marked/Rel-11/29_series/29204/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8eeb2e2cf84db50e3defcdcf03662fb89ecaa0d1 --- /dev/null +++ b/marked/Rel-11/29_series/29204/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3cee35e8b9c5fd1ce67cf9a35f9304c5ae1d0bc40f58a6afc2ac14588739632d +size 94060 diff --git a/marked/Rel-11/29_series/29204/ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg b/marked/Rel-11/29_series/29204/ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b4dc3e24fa7d4c32b3ab77a3b7e29e02c621c3ea --- /dev/null +++ b/marked/Rel-11/29_series/29204/ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4ebe1270a3cb5ceba5cf2e7be90ed603346756774a6bd599576144b287f1ff1e +size 66841 diff --git a/marked/Rel-11/29_series/29204/b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg b/marked/Rel-11/29_series/29204/b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b1fba736f45dd7befc0759a83a48d1d3f6f00d8f --- /dev/null +++ b/marked/Rel-11/29_series/29204/b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f5d3239c9171294906623cacb714797aae6dcc889e89b5b4f33866952e440c6b +size 55801 diff --git a/marked/Rel-11/29_series/29204/daa4a6fa7e2ba1954258f86b4928eb32_img.jpg b/marked/Rel-11/29_series/29204/daa4a6fa7e2ba1954258f86b4928eb32_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4561639e3f023fb3df66db087569900723a3ff0c --- /dev/null +++ b/marked/Rel-11/29_series/29204/daa4a6fa7e2ba1954258f86b4928eb32_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f9a068f57805e185d26d05c4d3e5a5a7014fe4f822e222fdc174f933fdbdc28e +size 68883 diff --git a/marked/Rel-11/29_series/29204/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg b/marked/Rel-11/29_series/29204/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c4a6421d425dbbb8c1560dc1ae28554062fef00a --- /dev/null +++ b/marked/Rel-11/29_series/29204/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ae0655bb2b2c780042a149208ad6da8cba60c38a8b58ab83a8a1b28951c8eb8f +size 88585 diff --git a/marked/Rel-11/29_series/29204/e821c3d8a87ee2a9ff6b8644ffe6bdae_img.jpg b/marked/Rel-11/29_series/29204/e821c3d8a87ee2a9ff6b8644ffe6bdae_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9772ec5f10ae71b02857e172ddce1c5fc603a67f --- /dev/null +++ b/marked/Rel-11/29_series/29204/e821c3d8a87ee2a9ff6b8644ffe6bdae_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0c21746454e729e1b8b0ede07cf852cb8247d1c08dd37aed9c8cf68fc8aaf646 +size 65469 diff --git a/marked/Rel-11/29_series/29204/ff0952ef692c9d960ce5f6708bcc9711_img.jpg b/marked/Rel-11/29_series/29204/ff0952ef692c9d960ce5f6708bcc9711_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cd008e7b80f73151b3ad89102c252de3f93aba07 --- /dev/null +++ b/marked/Rel-11/29_series/29204/ff0952ef692c9d960ce5f6708bcc9711_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:386d4d5702f988597a499adb0053a81e3c7583b753b59446f1b971267e8ee15f +size 57856 diff --git a/marked/Rel-11/29_series/29204/raw.md b/marked/Rel-11/29_series/29204/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..0236826e5569d109799f8f1e628f4bc3315cc313 --- /dev/null +++ b/marked/Rel-11/29_series/29204/raw.md @@ -0,0 +1,1079 @@ + + + + + + +# Contents + +| | | +|--------------------------------------------------------------------------|----| +| Foreword ..... | 4 | +| Introduction ..... | 4 | +| 1 Scope..... | 5 | +| 2 References..... | 5 | +| 3 Definitions and abbreviations ..... | 5 | +| 3.1 Definitions..... | 5 | +| 3.2 Abbreviations ..... | 6 | +| 4 Network architecture..... | 6 | +| 4.1 Scenarios ..... | 6 | +| 4.1.1 Outbound traffic (not yet protected) from own to foreign NE ..... | 7 | +| 4.1.2 Inbound traffic from foreign to own NE ..... | 7 | +| 4.1.3 Inbound transit traffic ..... | 8 | +| 4.1.4 Outbound transit traffic (not relayed)..... | 9 | +| 4.1.5 Outbound traffic from own to own NE ..... | 9 | +| 4.1.6 Inbound traffic from own to own NE ..... | 10 | +| 4.1.7 Outbound traffic from foreign to own NE..... | 11 | +| 4.1.8 Inbound traffic from own to foreign NE ..... | 11 | +| 4.1.9 Outbound traffic (already protected) from own to foreign NE ..... | 12 | +| 4.1.10 Outbound transit traffic (relayed by SRF)..... | 13 | +| 5 Detailed Behaviour of the SS7 Security Gateway ..... | 13 | +| 5.1 TCAP user traffic ..... | 13 | +| 5.1.1 General ..... | 13 | +| 5.1.2 Interactions with Mobile Number Portability..... | 28 | +| 5.1.3 Interactions with SCCP segmentation..... | 28 | +| 5.1.4 Protocol details ..... | 29 | +| 5.1.4.1 Transformation of unprotected message to protected message ..... | 29 | +| 5.1.4.2 Transformation of protected message to unprotected message ..... | 33 | +| 5.1.4.3 Handling of received XUDTS messages and UDTs messages ..... | 36 | +| Annex A (informative): Change history..... | 39 | + +# --- Foreword + +This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +# --- Introduction + +The absence of security in Signalling System No. 7 (SS7) networks is an identified security weakness in 2G systems. This was formerly perceived not to be a problem, since the SS7 networks were the provinces of a small number of large institutions. This is no longer the case, and so there is now a need for security precautions. + +For 3G systems it is a clear goal to be able to protect inter-network SS7 signalling protocols. The protection is done by security gateways which are located at the network border. As a consequence intra network SS7 signalling is not protected and network elements other than Security Gateways are not impacted. + +# --- 1 Scope + +The present document provides functional description of the SS7 Security Gateway. The document covers also network architecture, routing considerations, and protocol details. + +# --- 2 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. +- For a specific reference, subsequent revisions do not apply. +- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. + +- [1] 3GPP TS 29.002: "Mobile Application Part (MAP) specification". +- [2] 3GPP TS 29.078: "Customized Applications for Mobile network Enhanced Logic (CAMEL) Phase 4; CAMEL Application Part (CAP) specification". +- [3] ETSI ETS 300 358: "ISDN Completion of Calls to Busy Subscriber (CCBS) supplementary service; Functional capabilities and information flows". +- [4] 3GPP TS 23.066: "Support of GSM Mobile Number Portability (MNP) stage 2". +- [5] ITU-T Recommendation Q.773: "Specifications of Signalling System No.7; Transaction capabilities formats and encoding". +- [6] 3GPP TS 33.200: "3G Security; Network Domain Security (NDS); Mobile Application Part (MAP) application layer security". +- [7] ITU-T Recommendation E.164: " The international public telecommunication numbering plan". +- [8] 3GPP TS 33.204: "3G Security; Network Domain Security (NDS); Transaction Capabilities Application Part (TCAP) user security". +- [9] ITU-T Recommendations Q.711 to Q.716 (07/96), White Book Signalling Connection Control Part (SCCP). +- [10] 3GPP TS 21.905: "Vocabulary for 3GPP Specifications". + +# --- 3 Definitions and abbreviations + +## 3.1 Definitions + +For the purposes of the present document, the terms and definitions given in TR 21.905 [10] 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 [10]. + +- TCAP user:                    Application Part identified by one of the following SCCP Subsystem Numbers: +- | | | +|-----------|-------------------------------------------------------------| +| 0000 0110 | HLR (MAP) | +| 0000 0111 | VLR (MAP) | +| 0000 1000 | MSC (MAP) | +| 0000 1001 | EIR (MAP) | +| 0000 1010 | is allocated for evolution (possible Authentication Centre) | +| 1001 0001 | GMLC (MAP) | +| 1001 0010 | CAP | +| 1001 0011 | gsmSCF (MAP) or IM-SSF (MAP) or Presence Network Agent | + +| | | +|-----------|------------| +| 1001 0101 | SGSN (MAP) | +| 1001 0110 | GGSN (MAP) | +| 0000 1011 | SSAP | + +## 3.2 Abbreviations + +For the purposes of the present document, the following abbreviations apply: + +| | | +|--------|-----------------------------------------------------| +| CC | Country Code | +| GSMA | Global System for Mobile communications Association | +| IV | Initialisation Vector | +| MAC | Message Authentication Code | +| MNP | Mobile Number Portability | +| MSISDN | Mobile Station International ISDN Number | +| NDC | National Destination Code | +| NE | Network Entit | +| PLMN | Public Land Mobile Network y | +| RN | Routeing Number | +| SAD | Security Association Database | +| SEG | Security Gateway | +| SPD | Security Policy Database | +| SPI | Security Parameter Index | +| SRF | Signalling Relay Functio | +| TCAP | Transcation Capabilities Application Part | +| UDT | SCCP Unidata message | +| XUDT | SCCP Extended Unidata message n | + +# --- 4 Network architecture + +In a PLMN that employs SS7 Security Gateways all TCAP user signalling messages entering or leaving the PLMN have to transit an SS7 Security Gateway which belongs to the PLMN and which performs the protection of leaving (i.e. outbound) messages and the protection checking and de-protection or blocking of entering (i.e. inbound) messages. + +One or several SS7 Security Gateways may be employed within a PLMN. + +An SS7 Security Gateway may be co-located with any TCAP user NE or it may stand alone. However, for the purpose of this document and without imposing any restrictions, it is assumed that the SS7 Security Gateways is a stand alone entity. + +It is further assumed that the SS7 Security Gateways are located at the boarder of the PLMN i.e. inbound messages transit an SS7 Security Gateway before they reach any other node within the PLMN, and outbound messages transit an SS7 Security Gateway immediately before reaching a node outside the PLMN. + +SS7 routeing is not impacted by the SS7 Security Gateway Architecture. As a consequence SS7 Security Gateways are stateless at TCAP level: No TCAP dialogue states are maintained in the SS7 Security Gateway since the outbound dialogue request message may transit a different SS7 Security Gateway than the corresponding inbound dialogue response message; similarly the inbound dialogue request message may transit a different SS7 Security Gateway than the corresponding outbound dialogue response message. + +## 4.1 Scenarios + +SS7 Security Gateways perform protection, de-protection, blocking and unmodified passing of TCAP user messages depending on the scenario as described below: + +Note that scenarios 4.1.5, 4.1.6, 4.1.7, 4.1.8, and 4.1.9 are not applicable if all PLMN's TCAP user NEs are interconnected by PLMN internal signalling links and routing tables are set up not to allow these scenarios. + +### 4.1.1 Outbound traffic (not yet protected) from own to foreign NE + +This scenario is shown in figure 4.1.1. The message is originated at a NE inside the PLMN. It may transit several transit nodes inside the PLMN before it reaches the SS7 Security Gateway. This SS7 Security Gateway protects the message + +according to the relevant Security Policy with the relevant Security Association. The message may then transit several nodes outside the PLMN (including an SS7 Security Gateway) before it reaches its destination. + +![Diagram of outbound traffic from own to foreign NE](49ee89a1d5852ab005dbbab6de09a8a6_img.jpg) + +The diagram illustrates the flow of an unprotected TCAP user message from a TCAP user NE within a PLMN cloud. The message path is: TCAP user NE → Transit Node → SS7 Security Gateway. From the SS7 Security Gateway, the message is shown as a protected TCAP user message exiting the PLMN towards a destination. Two lines from the label 'unprotected TCAP user message' point to the message path between the TCAP user NE and the SS7 Security Gateway. + +Diagram of outbound traffic from own to foreign NE + +Figure 4.1.1: Outbound traffic (not yet protected) from own to foreign NE + +### 4.1.2 Inbound traffic from foreign to own NE + +This scenario is shown in figure 4.1.2. The message is originated at a NE outside the PLMN. It may transit several transit nodes (including an SS7 Security Gateway) outside the PLMN before it reaches the PLMN's SS7 Security Gateway. This SS7 Security Gateway checks whether the message is correctly protected according to the relevant security association. If it is not, the message is blocked (discarded), otherwise it is de-protected. To determine the relevant security association the fact that the message may have been relayed by an MNP-SRF in a transit network (see Clause 4.1.10 and 5.1.2) needs to be taken into account. After successful de-protection the message may then transit several nodes inside the PLMN before it reaches the TCAP user NE. + +![Diagram of inbound traffic from foreign to own NE](9791722d75115ddcc599b07d7bc35d73_img.jpg) + +The diagram illustrates the flow of a protected TCAP user message from an origin outside the PLMN. The message path is: from origin → SS7 Security Gateway → Transit Node → TCAP user NE. The message is shown as a protected TCAP user message entering the PLMN through the SS7 Security Gateway. Two lines from the label 'unprotected TCAP user message' point to the message path between the SS7 Security Gateway and the TCAP user NE. + +Diagram of inbound traffic from foreign to own NE + +Figure 4.1.2: Inbound traffic from foreign to own NE + +### 4.1.3 Inbound transit traffic + +This scenario is shown in figure 4.1.3. The message is originated at a NE outside the transit PLMN. It may transit several transit nodes outside the transit PLMN before it reaches the SS7 Security Gateway in inbound direction. This SS7 Security Gateway passes the message unmodified. The message may then transit several transit nodes inside the transit PLMN, another SS7 Security Gateway of the transit PLMN in outbound direction (see Clause 4.1.4), and several transit nodes outside the transit and destination PLMN (potentially including an SS7 Security Gateway) before it reaches the destination PLMN. + +Note: A PLMN operator may decide not to act as transit network for specific or all combinations of origin and destination. In this case the SS7 Security Gateway may block the inbound message. + +![Diagram of Inbound transit traffic flow within a PLMN.](5860ad6bd2a2dd8d1ab12864b8f90f37_img.jpg) + +The diagram illustrates the flow of inbound transit traffic within a PLMN. An orange cloud represents the PLMN. An arrow labeled 'from origin' points to a red box labeled 'SS7 Security Gateway' located outside the cloud. From this gateway, an arrow points into the cloud to a cyan box labeled 'Transit Node'. From the 'Transit Node', an arrow points to a blue box labeled 'SS7 SEG' located at the bottom of the cloud. An arrow then points from the 'SS7 SEG' out of the cloud to the right, labeled 'to destination'. A label 'protected or unprotected TCAP user message' is shown with lines pointing to the traffic path both before the 'SS7 Security Gateway' and after the 'SS7 SEG'. + +Diagram of Inbound transit traffic flow within a PLMN. + +Figure 4.1.3: Inbound transit traffic + +### 4.1.4 Outbound transit traffic (not relayed) + +This scenario is shown in figure 4.1.4. The message is originated at a NE outside the transit PLMN. It may transit several transit nodes outside the transit PLMN (including an SS7 Security Gateway), an SS7 Security Gateway of the transit PLMN in inbound direction (see Clause 4.1.3), and several transit nodes inside the transit PLMN before it reaches the SS7 Security Gateway in outbound direction. This SS7 Security Gateway passes the message unmodified. The message may then transit several transit nodes outside the transit and destination PLMN (potentially including an SS7 Security Gateway) before it reaches the destination PLMN. + +![Diagram of outbound transit traffic (not relayed) within a PLMN.](b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg) + +The diagram illustrates a cloud representing a PLMN. An arrow labeled "from origin" points to a blue box labeled "SS7 SEG". From the "SS7 SEG", an arrow points to a cyan box labeled "Transit Node". From the "Transit Node", an arrow points to a red box labeled "SS7 Security Gateway". From the "SS7 Security Gateway", an arrow points out of the cloud to the right, labeled "to destination". A label "protected or unprotected TCAP user message" has lines pointing to the arrows between the "SS7 SEG", "Transit Node", and "SS7 Security Gateway". + +Diagram of outbound transit traffic (not relayed) within a PLMN. + +Figure 4.1.4: Outbound transit traffic (not relayed) + +### 4.1.5 Outbound traffic from own to own NE + +This scenario is shown in figure 4.1.5. The message is originated at a NE inside the PLMN. It may transit several transit nodes inside the PLMN before it reaches the SS7 Security Gateway in outbound direction. This SS7 Security Gateway protects the message according to the relevant Security Association. The message may then transit several transit nodes outside the PLMN, another SS7 Security Gateway of the PLMN in inbound direction (see Clause 4.1.6) and several transit nodes within the PLMN before it reaches the destination NE inside the PLMN. + +![Diagram of outbound traffic from own to own NE within a PLMN.](0b87abe67b21a93777287649c33e755d_img.jpg) + +The diagram shows a cloud representing a PLMN. Inside the cloud, there are two yellow boxes labeled "TCAP user NE". The top "TCAP user NE" has an arrow pointing to a cyan box labeled "Transit Node", which in turn points to a red box labeled "SS7 Security Gateway". The bottom "TCAP user NE" has an arrow pointing to a cyan box labeled "Transit Node", which points to a blue box labeled "SS7 SEG". From the "SS7 Security Gateway", a red arrow points out of the cloud to a cyan box labeled "Transit Node" outside the cloud. From this external "Transit Node", a red arrow points back into the cloud to the "SS7 SEG". From the "SS7 SEG", a red arrow points to the top "TCAP user NE". A label "unprotected TCAP user message" has lines pointing to the arrows from the "TCAP user NE"s. A label "protected TCAP user message" has lines pointing to the red arrows outside the cloud. + +Diagram of outbound traffic from own to own NE within a PLMN. + +Figure 4.1.5: Outbound traffic from own to own NE + +### 4.1.6 Inbound traffic from own to own NE + +This scenario is shown in figure 4.1.6. The message is originated at a NE inside the PLMN. It may transit several transit nodes inside the PLMN, an SS7 Security Gateway of the PLMN in outbound direction (see Clause 4.1.5), and several + +transit nodes outside the PLMN before it reaches the SS7 Security Gateway in inbound direction. This SS7 Security Gateway checks whether the message is correctly protected according to the relevant Security Association. If it is not, the message is blocked (discarded), otherwise it is de-protected. The message may then transit several transit nodes inside the PLMN before it reaches the destination NE inside the PLMN. + +![Diagram of inbound traffic from own to own NE within a PLMN.](daa4a6fa7e2ba1954258f86b4928eb32_img.jpg) + +The diagram illustrates the flow of an unprotected TCAP user message within a PLMN. Two yellow boxes labeled 'TCAP user NE' are shown inside an orange cloud labeled 'PLMN'. Arrows from these boxes point to cyan boxes labeled 'Transit Node'. From the top 'Transit Node', an arrow points to a purple box labeled 'SS7 SEG'. From the 'SS7 SEG', a red arrow points to another cyan 'Transit Node' outside the PLMN. From this external 'Transit Node', a red arrow points to a red box labeled 'SS7 Security Gateway'. From the 'SS7 Security Gateway', a red arrow points back to the external 'Transit Node', and then a red arrow points back into the PLMN to the bottom 'Transit Node'. Finally, an arrow points from the bottom 'Transit Node' to the second 'TCAP user NE'. The text 'unprotected TCAP user message' is on the left, and 'protected TCAP user message' is on the right. + +Diagram of inbound traffic from own to own NE within a PLMN. + +Figure 4.1.6: Inbound traffic from own to own NE + +### 4.1.7 Outbound traffic from foreign to own NE + +This scenario is shown in figure 4.1.7. The message is originated at a NE outside the PLMN. It may transit several transit nodes outside the PLMN, an SS7 Security Gateway of the PLMN in inbound direction (see Clause 4.1.2), and several transit nodes inside the PLMN before it reaches the SS7 Security Gateway in outbound direction. This SS7 Security Gateway protects the message according to the reverse relevant Security Association. The message may then transit several transit nodes outside the PLMN, another SS7 Security Gateway of the PLMN in inbound direction (see Clause 4.1.2) and several transit nodes within the PLMN before it reaches the destination NE inside the PLMN. + +![Diagram of outbound traffic from foreign to own NE](5a4e62bead259c258d069fd3663ea670_img.jpg) + +This diagram illustrates the flow of outbound traffic from a foreign network element (NE) to an own NE within a PLMN. The PLMN is represented by an orange cloud. The traffic originates from an external source labeled "from origin". It first enters the PLMN through an SS7 Security Gateway (SS7 SEG), then passes through a Transit Node. Inside the PLMN, it reaches a TCAP user NE, which generates an "unprotected TCAP user message". This message is then processed by another Transit Node and an SS7 SEG. Finally, it exits the PLMN through another SS7 Security Gateway, which protects the message, resulting in a "protected TCAP user message" that is then passed to an external Transit Node. + +Diagram of outbound traffic from foreign to own NE + +Figure 4.1.7: Outbound traffic from foreign to own NE + +### 4.1.8 Inbound traffic from own to foreign NE + +This scenario is shown in figure 4.1.8. The message is originated at a NE inside the PLMN. It may transit several transit nodes inside the PLMN, an SS7 Security Gateway of the PLMN in outbound direction (see Clause 4.1.1), and several transit nodes outside the PLMN before it reaches the SS7 Security Gateway in inbound direction. This SS7 Security Gateway checks whether the message is correctly protected according to the relevant security association. If it is not, the message is blocked (discarded); otherwise it is passed unmodified. The message may then transit several transit nodes inside the PLMN, another SS7 Security Gateway of the PLMN in outbound direction (see Clause 4.1.9) and several transit nodes outside the PLMN (including an SS7 Security Gateway) before it reaches the destination NE outside the PLMN. + +![Diagram of inbound traffic from own to foreign NE](8e14350b4b669119a3bdfca7869110ca_img.jpg) + +This diagram illustrates the flow of inbound traffic from an own NE within a PLMN to a foreign NE. The traffic originates at a TCAP user NE inside the PLMN (represented by an orange cloud) as an "unprotected TCAP user message". It passes through a Transit Node and an SS7 SEG, then another Transit Node, and finally an SS7 Security Gateway. The message is then passed to an external Transit Node, which outputs a "protected TCAP user message". This message is received by another SS7 Security Gateway (in inbound direction), which checks its protection. If valid, the message is passed back through the internal Transit Node and SS7 SEG, then through another Transit Node, and finally exits the PLMN towards the "to destination" as an unprotected message. + +Diagram of inbound traffic from own to foreign NE + +Figure 4.1.8: Inbound traffic from own to foreign NE + +### 4.1.9 Outbound traffic (already protected) from own to foreign NE + +This scenario is shown in figure 4.1.9. The message is originated at a NE inside the PLMN. It may transit several transit nodes inside the PLMN, an SS7 Security Gateway of the PLMN in outbound direction (see Clause 4.1.1), several transit nodes outside the PLMN, an SS7 Security Gateway of the PLMN in inbound direction (see Clause 4.1.8), and several transit nodes inside the PLMN before it reaches the SS7 Security Gateway. This SS7 Security Gateway passes the message unmodified. The message may then transit several transit nodes outside the PLMN (including an SS7 Security Gateway) before it reaches the destination NE outside the PLMN. + +![Diagram of outbound traffic (already protected) from own to foreign NE](7f17c430b9598e4d748a8041457810b3_img.jpg) + +The diagram illustrates the path of a TCAP user message within a PLMN cloud. A yellow box labeled 'TCAP user NE' originates an 'unprotected TCAP user message' (indicated by a black arrow). The message flows through a 'Transit Node' (cyan box) to an 'SS7 SEG' (purple box). From the 'SS7 SEG', the message is shown as a 'protected TCAP user message' (indicated by a red arrow) and passes through another 'Transit Node' (cyan box) to a second 'SS7 SEG' (purple box). Finally, the message exits the PLMN cloud through an 'SS7 Security Gateway' (purple box) towards the 'destination' (indicated by a red arrow pointing left). + +Diagram of outbound traffic (already protected) from own to foreign NE + +Figure 4.1.9: Outbound traffic (already protected) from own to foreign NE + +### 4.1.10 Outbound transit traffic (relayed by SRF) + +This scenario is shown in figure 4.1.10. The message (originally destined for the PLMN) is originated at a NE outside the transit PLMN. It may transit several transit nodes outside the transit PLMN (including an SS7 Security Gateway), an SS7 Security Gateway of the transit PLMN in inbound direction (see Clause 4.1.2), several transit nodes inside the transit PLMN, and an MNP-SRF which replaces the SCCP called party address of the message before it reaches the SS7 Security Gateway in outbound direction. This SS7 Security Gateway recognizes that the message was relayed by an SRF by analyzing the SCCP called party address and protects the message with the relevant Security Association. The message may then transit several transit nodes outside the transit and destination PLMN (potentially including an SS7 Security Gateway) before it reaches the destination PLMN. + +![Diagram of outbound transit traffic relayed by SRF within a PLMN.](ff0952ef692c9d960ce5f6708bcc9711_img.jpg) + +The diagram illustrates the flow of outbound transit traffic within a PLMN (orange cloud). A red arrow labeled 'from origin' points to an 'SS7 SEG' (blue box). From the 'SS7 SEG', a black arrow points to an 'MNP SRF' (pink box). From the 'MNP SRF', a black arrow points to an 'SS7 Security Gateway' (blue box with a red border). A red arrow labeled 'to destination' exits the 'SS7 Security Gateway'. A label 'protected TCAP user message' points to the path between the 'SS7 SEG' and the 'MNP SRF'. A label 'unprotected TCAP user message' points to the path between the 'MNP SRF' and the 'SS7 Security Gateway'. + +Diagram of outbound transit traffic relayed by SRF within a PLMN. + +Figure 4.1.10: Outbound transit traffic (relayed by SRF) + +# 5 Detailed Behaviour of the SS7 Security Gateway + +## 5.1 TCAP user traffic + +### 5.1.1 General + +With regard to TCAP user traffic the SS7 Security Gateway performs message protection, protection checking and de-protection, transparent passing, and blocking of messages depending on the message's origin (SCCP calling party address), the message's destination (SCCP called party address), and the message's direction (inbound or outbound) as shown in figure 5.1.1. + +![Flowchart for SS7 Security Gateway procedure](a33da0f14e456f92539ce3e9b7d81f9a_img.jpg) + +procedure SS7\_Security\_Gateway + +1(2) + +Procedure in the SS7 Security Gateway + +``` +graph TD; Idle([Idle]) --> TCAP{TCAP user message}; TCAP --> CheckDir[Check direction]; CheckDir -- INBOUND --> IN((IN)); CheckDir -- OUTBOUND --> OUT((OUT)); CheckDir -- not_crossing[not crossing PLMN boundary] --> pass1((pass)); IN --> CheckOrigin[check origin and destination]; CheckOrigin -- own_to_own --> InboundOwnOwn[Inbound own_to_own]; CheckOrigin -- own_to_foreign --> InboundOwnForeign[Inbound own_to_foreign]; CheckOrigin -- foreign_to_own --> InboundForeignOwn[Inbound foreign_to_own]; CheckOrigin -- foreign_to_foreign --> pass2((pass)); InboundOwnOwn --> Result{result = block}; InboundOwnForeign --> Result; InboundForeignOwn --> Result; Result -- yes --> block((block)); Result -- no --> pass3((pass)); +``` + +The flowchart illustrates the process for an SS7 Security Gateway. It begins with an 'Idle' state, followed by the receipt of a 'TCAP user message'. The system then checks the 'direction' of the message, which can be 'INBOUND', 'OUTBOUND', or 'not crossing PLMN boundary'. The 'INBOUND' path leads to an 'IN' state, which then proceeds to 'check origin and destination'. From this check, four scenarios are possible: 'own to own', 'own to foreign', 'foreign to own', and 'foreign to foreign'. The first three scenarios lead to specific inbound processing blocks: 'Inbound own\_to\_own', 'Inbound own\_to\_foreign', and 'Inbound foreign\_to\_own' respectively. These three paths converge at a decision diamond 'result = block'. If the result is 'yes', the message is 'block'; if 'no', it is 'pass'. The 'foreign to foreign' scenario from the origin check leads directly to a 'pass' state. + +Flowchart for SS7 Security Gateway procedure + +Figure 5.1.1 Process SS7 Security Gateway (sheet 1 of 2) + +![Flowchart for SS7_Security_Gateway procedure. It starts with 'OUT', followed by 'check origin and destination'. A decision point branches into four cases: 'own to own' (Outbound_own_to_own), 'own to foreign' (Outbound_own_to_foreign), 'foreign to own' (Outbound_foreign_to_own), and 'foreign to foreign' (Outbound_foreign_to_foreign). All four cases lead to a 'pass' connector. Below this, a 'block' connector and a 'pass' connector (leading to 'TCAP user message') both lead to an 'Idle' terminal.](7efae06af3af43ffe5d4b956a679cf54_img.jpg) + +procedure SS7\_Security\_Gateway 2(2) + +Procedure in +the SS7 Security +Gateway + +``` +graph TD; OUT((OUT)) --> check[check origin and destination]; check --> own_to_own[own to own]; check --> own_to_foreign[own to foreign]; check --> foreign_to_own[foreign to own]; check --> foreign_to_foreign[foreign to foreign]; own_to_own --> Outbound_own_to_own[Outbound_own_to_own]; own_to_foreign --> Outbound_own_to_foreign[Outbound_own_to_foreign]; foreign_to_own --> Outbound_foreign_to_own[Outbound_foreign_to_own]; foreign_to_foreign --> Outbound_foreign_to_foreign[Outbound_foreign_to_foreign]; Outbound_own_to_own --> pass1((pass)); Outbound_own_to_foreign --> pass1; Outbound_foreign_to_own --> pass1; Outbound_foreign_to_foreign --> pass1; pass1 --> block((block)); pass1 --> pass2((pass)); block --> Idle([Idle]); pass2 --> TCAP[TCAP user message]; TCAP --> Idle; +``` + +Flowchart for SS7\_Security\_Gateway procedure. It starts with 'OUT', followed by 'check origin and destination'. A decision point branches into four cases: 'own to own' (Outbound\_own\_to\_own), 'own to foreign' (Outbound\_own\_to\_foreign), 'foreign to own' (Outbound\_foreign\_to\_own), and 'foreign to foreign' (Outbound\_foreign\_to\_foreign). All four cases lead to a 'pass' connector. Below this, a 'block' connector and a 'pass' connector (leading to 'TCAP user message') both lead to an 'Idle' terminal. + +Figure 5.1.1 Process SS7 Security Gateway (sheet 2 of 2) + +![Flowchart for macro Check_Direction. It starts with a connector, then a decision 'previous node belongs to own PLMN'. If 'yes', it goes to another decision 'next node belongs to own PLMN'. If 'yes', it ends at 'not crossing PLMN boundary' (OUTBOUND). If 'no', it ends at 'OUTBOUND'. If 'no' from the first decision, it goes to another decision 'next node belongs to own PLMN'. If 'yes', it ends at 'INBOUND'. If 'no', it ends at 'not crossing PLMN boundary'.](1a827b10290f33d4fec04d0e8ef7a897_img.jpg) + +macrodefinition Check\_Direction + +1(1) + +``` +graph TD; Start([ ]) --> D1{previous node belongs to own PLMN}; D1 -- yes --> D2{next node belongs to own PLMN}; D1 -- no --> D3{next node belongs to own PLMN}; D2 -- yes --> E1(( )); E1 --> O1[not crossing PLMN boundary]; O1 --> OUTBOUND[OUTBOUND]; D2 -- no --> OUTBOUND; D3 -- yes --> E2(( )); E2 --> INBOUND[INBOUND]; D3 -- no --> E3(( )); E3 --> O2[not crossing PLMN boundary]; +``` + +Flowchart for macro Check\_Direction. It starts with a connector, then a decision 'previous node belongs to own PLMN'. If 'yes', it goes to another decision 'next node belongs to own PLMN'. If 'yes', it ends at 'not crossing PLMN boundary' (OUTBOUND). If 'no', it ends at 'OUTBOUND'. If 'no' from the first decision, it goes to another decision 'next node belongs to own PLMN'. If 'yes', it ends at 'INBOUND'. If 'no', it ends at 'not crossing PLMN boundary'. + +Figure 5.1.2 Macro Check\_Direction (sheet 1 of 1) + +![Flowchart for macrodefinition Inbound_own_to_own. The process starts with an oval connector, followed by a decision 'message contains protectable parameter'. If 'no', it goes to 'pass'. If 'yes', it goes to 'message is not protected'. If 'no', it goes to 'pass'. If 'yes', it goes to 'message should be protected according to SPD'. If 'no', it goes to 'pass'. If 'yes', it goes to 'Fall Back allowed according to SPD'. If 'yes', it goes to 'pass'. If 'no', it goes to 'block'. From 'message should be protected according to SPD', if 'no', it goes to 'calling party address consistent with SPI'. If 'no', it goes to 'protection mode acceptable according to SPD'. If 'yes', it goes to 'De-protect message'. From 'De-protect message', if 'no', it goes to 'success'. If 'yes', it goes to 'pass'. From 'success', if 'no', it goes to 'block'. From 'calling party address consistent with SPI', if 'yes', it goes to 'protection mode acceptable according to SPD'.](8307f6b04df072c9332f9987e034272c_img.jpg) + +macrodefinition Inbound\_own\_to\_own + +1(1) + +``` +graph TD; Start([ ]) --> D1{message contains protectable parameter}; D1 -- no --> P1((pass)); D1 -- yes --> D2{message is not protected}; D2 -- no --> P2((pass)); D2 -- yes --> D3{message should be protected according to SPD}; D3 -- no --> P3((pass)); D3 -- yes --> D4{Fall Back allowed according to SPD}; D4 -- yes --> P4((pass)); D4 -- no --> B1((block)); D3 -- no --> D5{calling party address consistent with SPI}; D5 -- no --> D6{protection mode acceptable according to SPD}; D5 -- yes --> D6; D6 -- yes --> DM[De-protect message]; DM -- no --> S{success}; DM -- yes --> P5((pass)); S -- no --> B2((block)); S -- yes --> P6((pass)); B1 --> B2; +``` + +Flowchart for macrodefinition Inbound\_own\_to\_own. The process starts with an oval connector, followed by a decision 'message contains protectable parameter'. If 'no', it goes to 'pass'. If 'yes', it goes to 'message is not protected'. If 'no', it goes to 'pass'. If 'yes', it goes to 'message should be protected according to SPD'. If 'no', it goes to 'pass'. If 'yes', it goes to 'Fall Back allowed according to SPD'. If 'yes', it goes to 'pass'. If 'no', it goes to 'block'. From 'message should be protected according to SPD', if 'no', it goes to 'calling party address consistent with SPI'. If 'no', it goes to 'protection mode acceptable according to SPD'. If 'yes', it goes to 'De-protect message'. From 'De-protect message', if 'no', it goes to 'success'. If 'yes', it goes to 'pass'. From 'success', if 'no', it goes to 'block'. From 'calling party address consistent with SPI', if 'yes', it goes to 'protection mode acceptable according to SPD'. + +**Figure 5.1.3 Macro Inbound\_own\_to\_own (sheet 1 of 1)** + +The decision box "message contains protectable parameter" takes the "yes"-exit if user-information is present in the Dialogue Portion, or a parameter is present in an Invoke or ReturnError Component, or a result is present in a ReturnResult Component. + +The decision box "message is not protected" takes the "no"-exit if user-information within the Dialogue Portion is identified by the object identifier ss7-ProtectedDialogueAS or + +operationCode within an Invoke or ReturnResult Component takes the global value ss7-ProtectedDialogueAS or errorCode within an ReturnError Component takes the global value ss7-ProtectedDialogueAS. + +The decision box "message should be protected according to SPD" takes the "yes"-exit if the message's SCCP calling party address identifies a PLMN for which an SPD entry for incoming messages exists. + +The decision box "fall back allowed according to SPD" takes the "yes"-exit if the SPD entry for incoming messages is marked "fall back allowed". + +The decision box "calling party address consistent with SPI" takes the "yes"-exit if the SPI within the message's Security Header points to an SA that was negotiated with the PLMN derived from the message's SCCP calling party address. + +The decision box "protection mode acceptable according to SPD" takes the "yes"-exit if the protection mode within the message's Security Header is found in the SPD-entry for incoming messages. + +![Flowchart for macrodefinition Inbound_own_to_foreign](8fa679f79a1bb1f527cba9f29e784e89_img.jpg) + +macrodefinition Inbound\_own\_to\_foreign + +1(1) + +``` +graph TD; Start([ ]) --> D1{message contains protectable parameter}; D1 -- no --> Pass1((pass)); D1 -- yes --> D2{message is not protected}; D2 -- no --> D3{message should be protected according to SPD}; D2 -- yes --> D4{Fall Back allowed according to SPD}; D3 -- no --> D5{called party address consistent with SPI}; D3 -- yes --> Pass2((pass)); D4 -- no --> D5; D4 -- yes --> Pass3((pass)); D5 -- no --> D6{protection mode correct}; D5 -- yes --> Pass4((pass)); D6 -- no --> Block((block)); D6 -- yes --> Pass5((pass)); +``` + +The flowchart illustrates the logic for the macrodefinition Inbound\_own\_to\_foreign. It begins with a start node leading to a decision box 'message contains protectable parameter'. If 'no', it leads to a 'pass' node. If 'yes', it leads to a decision box 'message is not protected'. If 'no', it leads to a decision box 'message should be protected according to SPD'. If 'yes', it leads to a decision box 'Fall Back allowed according to SPD'. If 'no', it leads to a decision box 'called party address consistent with SPI'. If 'yes', it leads to a 'pass' node. If 'yes' from 'message is not protected', it leads to a decision box 'Fall Back allowed according to SPD'. If 'no', it leads to a 'block' node. If 'yes', it leads to a 'pass' node. If 'no' from 'message should be protected according to SPD', it leads to a decision box 'called party address consistent with SPI'. If 'yes', it leads to a 'pass' node. If 'no', it leads to a decision box 'protection mode correct'. If 'yes', it leads to a 'pass' node. If 'no', it leads to a 'block' node. + +Flowchart for macrodefinition Inbound\_own\_to\_foreign + +**Figure 5.1.4 Macro Inbound\_own\_to\_foreign (sheet 1 of 1)** + +The decision box "message contains protectable parameter" takes the "yes"-exit if user-information is present in the Dialogue Portion, or a parameter is present in an Invoke or ReturnError Component, or a result is present in a ReturnResult Component. + +The decision box "message is not protected" takes the "no"-exit if user-information within the Dialogue Portion is identified by the object identifier ss7-ProtectedDialogueAS or + +operationCode within an Invoke or ReturnResult Component takes the global value ss7-ProtectedDialogueAS or errorCode within an ReturnError Component takes the global value ss7-ProtectedDialogueAS. + +The decision box "message should be protected according to SPD" takes the "yes"-exit if the message's SCCP called party address identifies a PLMN for which an SPD entry for outgoing messages exists. + +The decision box "fall back allowed according to SPD" takes the "yes"-exit if the SPD entry for outgoing messages is marked "fall back allowed". + +The decision box "called party address consistent with SPI" takes the "yes"-exit if the SPI within the message's Security Header points to an SA that was negotiated with the PLMN derived from the message's SCCP called party address. + +The decision box "protection mode correct" takes the "yes"-exit if the presence/absence of octets 10 and 11 within the message's Security Header is consistent with the protection mode in the SPD-entry for outgoing messages. Note that octets 10 and 11 of the Security Header are only used to construct the IV which is not needed (and shall therefore be absent) if the protection mode is "authenticity and integrity". + +![Flowchart for macrodefinition Inbound_foreign_to_own. The process starts with a connector, followed by a decision 'message contains protectable parameter'. If 'no', it goes to 'pass'. If 'yes', it goes to 'message is not protected'. If 'no', it goes to connector 'A'. If 'yes', it goes to 'relayed by SRF'. If 'no', it goes to a merge point. If 'yes', it goes to 'message should be protected according to SPD (relay network)'. If 'no', it goes to 'pass'. If 'yes', it goes to 'Fall Back allowed according to SPD (relay network)'. If 'no', it goes to a merge point. If 'yes', it goes to 'pass'. The merge point leads to 'message should be protected according to SPD (orig. network)'. If 'no', it goes to 'block'. If 'yes', it goes to 'Fall Back allowed according to SPD (orig. network)'. If 'no', it goes to a merge point. If 'yes', it goes to 'pass'.](79e1709a7317ead45379cbb8ff3ba802_img.jpg) + +macrodefinition Inbound\_foreign\_to\_own + +1(2) + +``` +graph TD; Start([ ]) --> D1{message contains protectable parameter}; D1 -- no --> P1((pass)); D1 -- yes --> D2{message is not protected}; D2 -- no --> A((A)); D2 -- yes --> D3{relayed by SRF}; D3 -- no --> Merge1(( )); D3 -- yes --> D4{message should be protected according to SPD (relay network)}; D4 -- no --> P2((pass)); D4 -- yes --> D5{Fall Back allowed according to SPD (relay network)}; D5 -- no --> Merge2(( )); D5 -- yes --> P3((pass)); Merge1 --> D6{message should be protected according to SPD (orig. network)}; D6 -- no --> B((block)); D6 -- yes --> D7{Fall Back allowed according to SPD (orig. network)}; D7 -- no --> Merge3(( )); D7 -- yes --> P4((pass)); Merge2 --> Merge3; +``` + +Flowchart for macrodefinition Inbound\_foreign\_to\_own. The process starts with a connector, followed by a decision 'message contains protectable parameter'. If 'no', it goes to 'pass'. If 'yes', it goes to 'message is not protected'. If 'no', it goes to connector 'A'. If 'yes', it goes to 'relayed by SRF'. If 'no', it goes to a merge point. If 'yes', it goes to 'message should be protected according to SPD (relay network)'. If 'no', it goes to 'pass'. If 'yes', it goes to 'Fall Back allowed according to SPD (relay network)'. If 'no', it goes to a merge point. If 'yes', it goes to 'pass'. The merge point leads to 'message should be protected according to SPD (orig. network)'. If 'no', it goes to 'block'. If 'yes', it goes to 'Fall Back allowed according to SPD (orig. network)'. If 'no', it goes to a merge point. If 'yes', it goes to 'pass'. + +Figure 5.1.5 Macro Inbound\_foreign\_to\_own (sheet 1 of 2) + +![Flowchart for macrodefinition Inbound_foreign_to_own (sheet 2 of 2). The process starts at node A. It enters a loop of decision boxes: 'calling party address consistent with SPI', 'relayed by SRF', and 'protection mode acceptable according to SPD (relay network)'. If 'yes' to the first, it proceeds to a fourth decision box 'protection mode acceptable according to SPD (orig. network)'. If 'no' to the first, it goes to 'relayed by SRF'. If 'yes' to 'relayed by SRF', it goes to the third decision box. If 'no' to 'relayed by SRF', it goes to a 'block' node. If 'yes' to the third decision box, it proceeds to 'De-protect message'. If 'no' to the third, it goes to a 'block' node. From the fourth decision box, if 'yes', it proceeds to 'De-protect message'. If 'no', it goes to a 'block' node. From 'De-protect message', it goes to a 'success' decision box. If 'yes', it goes to a 'pass' node. If 'no', it goes to a 'block' node.](e180f2b5fcbe8001554a7c0677cd3f82_img.jpg) + +macrodefinition Inbound\_foreign\_to\_own 2(2) + +``` +graph TD; A((A)) --> D1{calling party address consistent with SPI}; D1 -- yes --> D4{protection mode acceptable according to SPD (orig. network)}; D1 -- no --> D2{relayed by SRF}; D2 -- no --> B1((block)); D2 -- yes --> D3{protection mode acceptable according to SPD (relay network)}; D3 -- no --> B2((block)); D3 -- yes --> M[De-protect message]; D4 -- yes --> M; D4 -- no --> B3((block)); M --> D5{success}; D5 -- yes --> P((pass)); D5 -- no --> B4((block)); +``` + +Flowchart for macrodefinition Inbound\_foreign\_to\_own (sheet 2 of 2). The process starts at node A. It enters a loop of decision boxes: 'calling party address consistent with SPI', 'relayed by SRF', and 'protection mode acceptable according to SPD (relay network)'. If 'yes' to the first, it proceeds to a fourth decision box 'protection mode acceptable according to SPD (orig. network)'. If 'no' to the first, it goes to 'relayed by SRF'. If 'yes' to 'relayed by SRF', it goes to the third decision box. If 'no' to 'relayed by SRF', it goes to a 'block' node. If 'yes' to the third decision box, it proceeds to 'De-protect message'. If 'no' to the third, it goes to a 'block' node. From the fourth decision box, if 'yes', it proceeds to 'De-protect message'. If 'no', it goes to a 'block' node. From 'De-protect message', it goes to a 'success' decision box. If 'yes', it goes to a 'pass' node. If 'no', it goes to a 'block' node. + +**Figure 5.1.5 Macro Inbound\_foreign\_to\_own (sheet 2 of 2)** + +The decision box "message contains protectable parameter" takes the "yes"-exit if user-information is present in the Dialogue Portion, or a parameter is present in an Invoke or ReturnError Component, or a result is present in a ReturnResult Component. + +The decision box "message is not protected" takes the "no"-exit if user-information within the Dialogue Portion is identified by the object identifier ss7-ProtectedDialogueAS or + +operationCode within an Invoke or ReturnResult Component takes the global value ss7-ProtectedDialogueAS or errorCode within an ReturnError Component takes the global value ss7-ProtectedDialogueAS. + +The decision box "relayed by SRF" takes the "yes"-exit if the SCCP called party address consists of a Routing Number (RN) pointing to the own network and an MSISDN pointing to a relay network within the portability cluster. + +The decision box "message should be protected according to SPD (relay network)" takes the "yes"-exit if an SPD entry for incoming messages exists for the relay network. + +The decision box "Fall Back allowed according to SPD (relay network)" takes the "yes"-exit if the SPD entry for incoming messages (from the relay network) is marked "fall back allowed". + +The decision box "message should be protected according to SPD (orig. network)" takes the "yes"-exit if the message's SCCP calling party address identifies a PLMN for which an SPD entry for incoming messages exists. + +The decision box "Fall Back allowed according to SPD (relay network)" takes the "yes"-exit if the SPD entry for incoming messages (from the network identified by the SCCP calling party address) is marked "fall back allowed". + +The decision box "calling party address consistent with SPI" takes the "yes"-exit if the SPI within the message's Security Header points to an SA that was negotiated with the PLMN derived from the message's SCCP calling party address. + +The decision box "protection mode acceptable according to SPD (relay network)" takes the "yes"-exit if the presence/absence of octets 10 and 11 within the message's Security Header is consistent with a protection mode found in the SPD-entry (for incoming messages from the network identified by the SPI). Note that octets 10 and 11 of the Security Header are only used to construct the IV which is not needed (and shall therefore be absent) if the protection mode is "authenticity and integrity". + +The decision box "protection mode acceptable according to SPD (orig. network)" takes the "yes"-exit if the presence/absence of octets 10 and 11 within the message's Security Header is consistent with a protection mode found in the SPD-entry (for incoming messages from the network identified by the SCCP calling party address). Note that octets 10 and 11 of the Security Header are only used to construct the IV which is not needed (and shall therefore be absent) if the protection mode is "authenticity and integrity". + +![Flowchart for macrodefinition Outbound_own_to_own. It starts with a start symbol, followed by a decision 'message contains protectable parameter'. If 'no', it goes to a 'pass' symbol. If 'yes', it goes to another decision 'message needs to be protected according to SPD'. If 'no', it goes to a 'pass' symbol. If 'yes', it goes to a 'protect message' block, which then leads to a 'pass' symbol.](ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg) + +macrodefinition Outbound\_own\_to\_own + +1(1) + +``` +graph TD; Start([ ]) --> D1{message contains protectable parameter}; D1 -- no --> Pass((pass)); D1 -- yes --> D2{message needs to be protected according to SPD}; D2 -- no --> Pass; D2 -- yes --> P[protect message]; P --> Pass; +``` + +Flowchart for macrodefinition Outbound\_own\_to\_own. It starts with a start symbol, followed by a decision 'message contains protectable parameter'. If 'no', it goes to a 'pass' symbol. If 'yes', it goes to another decision 'message needs to be protected according to SPD'. If 'no', it goes to a 'pass' symbol. If 'yes', it goes to a 'protect message' block, which then leads to a 'pass' symbol. + +**Figure 5.1.6 Macro Outbound\_own\_to\_own (sheet 1 of 1)** + +The decision box "message contains protectable parameter" takes the "yes"-exit if user-information is present in the Dialogue Portion, or a parameter is present in an Invoke or ReturnError Component, or a result is present in a ReturnResult Component. + +The decision box "message needs to be protected according to SPD" takes the "yes"-exit if an SPD entry for outgoing messages exists (for messages sent to the own network). + +![Flowchart for macrodefinition Outbound_own_to_foreign. It starts with a start symbol, followed by a decision 'message contains protectable parameter'. If 'no', it goes to a 'pass' symbol. If 'yes', it goes to a decision 'message is protected'. If 'yes', it goes to a 'pass' symbol. If 'no', it goes to a decision 'message needs to be protected according to SPD'. If 'no', it goes to a 'pass' symbol. If 'yes', it goes to a process 'protect message', which then goes to a 'pass' symbol.](26d664119ad25250780f554633444e54_img.jpg) + +macrodefinition Outbound\_own\_to\_foreign 1(1) + +``` +graph TD; Start([ ]) --> D1{message contains protectable parameter}; D1 -- no --> Pass((pass)); D1 -- yes --> D2{message is protected}; D2 -- yes --> Pass; D2 -- no --> D3{message needs to be protected according to SPD}; D3 -- no --> Pass; D3 -- yes --> P[protect message]; P --> Pass; +``` + +Flowchart for macrodefinition Outbound\_own\_to\_foreign. It starts with a start symbol, followed by a decision 'message contains protectable parameter'. If 'no', it goes to a 'pass' symbol. If 'yes', it goes to a decision 'message is protected'. If 'yes', it goes to a 'pass' symbol. If 'no', it goes to a decision 'message needs to be protected according to SPD'. If 'no', it goes to a 'pass' symbol. If 'yes', it goes to a process 'protect message', which then goes to a 'pass' symbol. + +**Figure 5.1.7 Macro Outbound\_own\_to\_foreign (sheet 1 of 1)** + +The decision box "message contains protectable parameter" takes the "yes"-exit if user-information is present in the Dialogue Portion, or a parameter is present in an Invoke or ReturnError Component, or a result is present in a ReturnResult Component. + +The decision box "message is protected" takes the "yes"-exit if user-information within the Dialogue Portion is identified by the object identifier ss7-ProtectedDialogueAS or + +operationCode within an Invoke or ReturnResult Component takes the global value ss7-ProtectedDialogueAS or errorCode within an ReturnError Component takes the global value ss7-ProtectedDialogueAS. + +The decision box "message needs to be protected according to SPD" takes the "yes"-exit if an SPD entry for outgoing messages exists (for messages sent to the network identified by the SCCP called party address). + +![Flowchart for macrodefinition Outbound_foreign_to_own. It starts with an oval connector, followed by a decision diamond 'message contains protectable parameter'. If 'no', it goes to a 'pass' connector. If 'yes', it goes to another decision diamond 'message needs to be protected according to SPD'. If 'no', it goes to the 'pass' connector. If 'yes', it goes to a process box 'protect message with reverse SA', which then leads to the 'pass' connector.](e821c3d8a87ee2a9ff6b8644ffe6bdae_img.jpg) + +macrodefinition Outbound\_foreign\_to\_own 1(1) + +``` +graph TD; Start([ ]) --> D1{message contains protectable parameter}; D1 -- no --> Pass((pass)); D1 -- yes --> D2{message needs to be protected according to SPD}; D2 -- no --> Pass; D2 -- yes --> P[protect message with reverse SA]; P --> Pass; +``` + +Flowchart for macrodefinition Outbound\_foreign\_to\_own. It starts with an oval connector, followed by a decision diamond 'message contains protectable parameter'. If 'no', it goes to a 'pass' connector. If 'yes', it goes to another decision diamond 'message needs to be protected according to SPD'. If 'no', it goes to the 'pass' connector. If 'yes', it goes to a process box 'protect message with reverse SA', which then leads to the 'pass' connector. + +**Figure 5.1.8 Macro Outbound\_foreign\_to\_own (sheet 1 of 1)** + +The decision box "message contains protectable parameter" takes the "yes"-exit if user-information is present in the Dialogue Portion, or + +a parameter is present in an Invoke or ReturnError Component, or +a result is present in a ReturnResult Component. + +The decision box "message needs to be protected according to SPD" takes the "yes"-exit if an SPD entry for incoming messages exists (for messages received from the network identified by the SCCP calling party address). If more than one acceptable protection modes are present, one may be chosen. + +The task box "protect message with reverse SA" performs protection of the message with the SA that is to be used for de-protection when receiving messages from the network in question. + +![Flowchart for macro Outbound_foreign_to_foreign. It starts with an oval connector, followed by four decision diamonds: 'message contains protectable parameter', 'message is protected', 'relayed by SRF', and 'message needs to be protected according to SPD'. The 'yes' path from the last decision leads to a task box 'protect message' which is associated with 'with SA own to foreign'. All 'no' paths from the decisions and the task box lead to a final oval connector labeled 'pass'.](088921fa3f5a44c8551815122517eefd_img.jpg) + +macrodefinition Outbound\_foreign\_to\_foreign 1(1) + +``` +graph TD; Start([ ]) --> D1{message contains protectable parameter}; D1 -- no --> Pass([pass]); D1 -- yes --> D2{message is protected}; D2 -- yes --> Pass; D2 -- no --> D3{relayed by SRF}; D3 -- no --> Pass; D3 -- yes --> D4{message needs to be protected according to SPD}; D4 -- no --> Pass; D4 -- yes --> T1[protect message]; T1 --> T2[with SA own to foreign]; T1 --> Pass; +``` + +Flowchart for macro Outbound\_foreign\_to\_foreign. It starts with an oval connector, followed by four decision diamonds: 'message contains protectable parameter', 'message is protected', 'relayed by SRF', and 'message needs to be protected according to SPD'. The 'yes' path from the last decision leads to a task box 'protect message' which is associated with 'with SA own to foreign'. All 'no' paths from the decisions and the task box lead to a final oval connector labeled 'pass'. + +Figure 5.1.9 Macro Outbound\_foreign\_to\_foreign (sheet 1 of 1) + +The decision box "message contains protectable parameter" takes the "yes"-exit if user-information is present in the Dialogue Portion, or a parameter is present in an Invoke or ReturnError Component, or a result is present in a ReturnResult Component. + +The decision box "message is protected" takes the "yes"-exit if user-information within the Dialogue Portion is identified by the object identifier ss7-ProtectedDialogueAS or operationCode within an Invoke or ReturnResult Component takes the global value ss7-ProtectedDialogueAS or errorCode within an ReturnError Component takes the global value ss7-ProtectedDialogueAS. + +The decision box "relayed by SRF" takes the "yes"-exit if the SCCP called party address consists of a Routing Number (RN) pointing to the own network and an MSISDN pointing to a relay network within the portability cluster. + +The decision box "message needs to be protected according to SPD" takes the "yes"-exit if an SPD entry for outgoing messages exists (for messages sent to the network identified by the SCCP called party address). + +### 5.1.2 Interactions with Mobile Number Portability + +In Mobile Number Portability scenarios (see 3GPP TS 23.066 [4]) a Signalling Relay Function (SRF) may relay SCCP traffic by modifying the SCCP called party address as shown in figure 4.1.10. + +A relayed message's SCCP called party address consists of a Routing Number (RN) and an MSISDN (see 3GPP TS 23.066 [4]). + +An SS7 Security Gateway needs to recognize (by analyzing the SCCP called party address) whether or not a message was relayed in order to + +- a) distinguish outbound transit traffic relayed by an SRF in the own network (which needs to be protected) from other outbound transit traffic (which needs to be passed transparently), and to +- b) distinguish inbound terminating traffic relayed by an SRF within the portability cluster (where the check needs to be based on the policy identified by the MSISDN within the SCCP called party address) from other inbound terminating traffic (where the check needs to be based on the policy identified by the SCCP calling party address). + +NOTE : In MNP-SRF scenarios, when the relaying PLMN does not make use of TCAP-User Security, messages sent from a source PLMN to a destination PLMN via the relaying PLMN are unprotected although protection may be desired for messages sent from the source PLMN to the destination PLMN. Network operators may therefore want to negotiate use of TCAP-User Security with all PLMNs of a portability cluster. + +### 5.1.3 Interactions with SCCP segmentation + +When the incoming SCCP message makes use of SCCP segmenting (i.e. several XUDT messages are received rather than one UDT or a single XUDT message) the SS7 Security Gateway has to perform reassembling before processing the message, and it may have to perform segmenting before sending the processed message. + +It may happen that the received SCCP message (containing an unprotected TCAP user payload) is not segmented (UDT or single XUDT), but after security processing the message's length is increased, so that the processed message needs to be segmented before it is sent. This situation may be undesired (since transfer of XUDT messages is not guaranteed by all transit networks) but cannot be avoided by the SS7 Security Gateway (see note). + +Note: The support of message segmentation at the SCCP layer in all transit networks could be enforced by mandating the usage of the White Book SCCP [9]. GSMA would work with International Carriers to ensure that fully operationally-verified support of XUDT is available before TCAPsec gateways are deployed. + +It may also happen that the received (protected) message is segmented (several XUDTs), but after security processing the message's length is decreased, so that the processed message does not need to be segmented before it is sent. In this case the de-protecting SS7 Security Gateway needs to know some SCCP-details of the original unprotected message as sent from the originating NE to the protecting SS7 Security Gateway. These original SCCP information needs to be transported within the TCAP-user parameter of the protected message. Depending on this information the de-protecting SS7-Security Gateway can decide whether to send a UDT or a single XUDT message towards the destination. . + +In cases where the received unprotected message is not segmented but the (to be) sent protected message needs to be segmented, the SS7 Security Gateway has to replace the message's SCCP calling party address with its own address. This is to guarantee uniqueness of the combination of the SCCP calling party address and the Segmentation local reference in the (to be) sent message. The original SCCP calling party address needs to be transported within the TCAP-user parameter of the (first segment of the) protected message. + +If the received protected message contains an original SCCP calling party address within the TCAP-user parameter, the de-protecting SS7 Security Gateway has to replace the SCCP calling party address with the original SCCP calling party address before forwarding the de-protected message to the destination. + +An SS7 Security Gateway that has sent a segmented, protected message with a replaced SCCP calling party address may receive an SCCP XUDTS message with its own address as called party address. In this case the SS7 Security Gateway shall retrieve the original SCCP calling party address, the original TCAP Message type and TCAP transaction id from the data parameter of the received XUDTS message and construct a UDTS message with unmodified Return cause, called party address replaced with the retrieved original calling party address, unmodified calling party address, and Data parameter containing the retrieved TCAP message type and TCAP transaction id, and forward it to the destination. + +### 5.1.4 Protocol details + +#### 5.1.4.1 Transformation of unprotected message to protected message + +The unprotected TCAP-user message is either transported within an SCCP UDT message or it is transported within a single SCCP XUDT message or it is segmented over several SCCP XUDT messages. Other SCCP message types are not subject to protection. + +The transformation process is done in 3 steps: + +##### Step 1: SCCP re-assembly of the unprotected message + +In a first step the unprotected message is transformed into an intermediate unprotected representation which is made up of the following parameters: + +| | | +|-------------------------------------------------|--------------------------------------| +| SCCP Message type | | +| SCCP Protocol class | | +| SCCP Hop counter (optional) | | +| SCCP Called party address | | +| SCCP Calling party address | | +| SCCP Segmentation local reference (optional) | | +| SCCP Importance (optional) | | +| SCCP Data (made up of the following parameters: | TCAP Message type | +| | TCAP orig. Transaction Id (optional) | +| | TCAP dest. Transaction Id (optional) | +| | TCAP Dialogue Portion (optional) | +| | TCAP Component Portion (optional)) | + +If the unprotected message was transported within an SCCP UDT message, the intermediate unprotected representation of the message takes the following values: + +| | | +|-----------------------------------|-------------------------------------| +| SCCP Message type | UDT | +| SCCP Protocol class | same as in the received UDT message | +| SCCP Hop counter | absent | +| SCCP Called party address | same as in the received UDT message | +| SCCP Calling party address | same as in the received UDT message | +| SCCP Segmentation local reference | absent | +| SCCP Importance | absent | +| SCCP Data | same as in the received UDT message | + +If the unprotected message was transported within a single SCCP XUDT message, the intermediate unprotected representation of the message takes the following values: + +| | | +|-----------------------------------|--------------------------------------| +| SCCP Message type | XUDT | +| SCCP Protocol class | same as in the received XUDT message | +| SCCP Hop counter | same as in the received XUDT message | +| SCCP Called party address | same as in the received XUDT message | +| SCCP Calling party address | same as in the received XUDT message | +| SCCP Segmentation local reference | absent | +| SCCP Importance | same as in the received XUDT message | +| SCCP Data | same as in the received XUDT message | + +If the unprotected message was segmented over several SCCP XUDT messages, the intermediate unprotected representation of the message takes the following values: + +| | | +|-----------------------------------|-------------------------------------------------------------------------------------------------------| +| SCCP Message type | XUDT | +| SCCP Protocol class | same as in the first received XUDT message | +| SCCP Hop counter | same as in the first received XUDT message | +| SCCP Called party address | same as in the first received XUDT message | +| SCCP Calling party address | same as in the first received XUDT message | +| SCCP Segmentation local reference | same as in the first received XUDT message | +| SCCP Importance | same as in the first received XUDT message | +| SCCP Data | concatenation of the received segments (for details of the re-assembly procedure see ITU-T Q.714 [9]) | + +##### Step 2: Protection + +In a second step the intermediate unprotected representation is transformed into an intermediate protected representation which is made up of the following parameters: + +| | | +|----------------------------------------------------------|---------------------------------------------------------------------------------------------------------------| +| SCCP Hop counter (optional) | | +| SCCP Called party address | | +| SCCP Calling party address | | +| SCCP Segmentation local reference (optional) | | +| SCCP Importance (optional) | | +| Original SCCP info (made up of the following parameters: | Original SCCP Calling party address (optional)
Original SCCP Message type
Original SCCP Protocol class) | +| Original TCAP info (made up of the following parameters: | Original TCAP Message type
otid (optional)
dtid (optional)) | +| TCAPsec Security header | | +| TCAPsec Cipher- or Cleartext | | +| TCAPsecMAC | | + +The intermediate unprotected representation of the message takes the following values: + +| | | +|---------------------------------------------------------|----------------------------------------------------------------------------| +| SCCP Hop counter | same as SCCP Hop counter in the intermediate unprotected representation | +| SCCP Called party address | same as in the intermediate unprotected representation | +| SCCP Calling party address | same as in the intermediate unprotected representation | +| SCCP Segmentation local reference | same as in the intermediate unprotected representation | +| SCCP Importance | same as SCCP Importance in the intermediate unprotected representation | +| Original SCCP info made up of the following parameters: | | +| Original SCCP Message type | same as SCCP Message type in the intermediate unprotected representation | +| Original SCCP Protocol class | same as SCCP Protocol class in the intermediate unprotected representation | +| Original TCAP info made up of the following parameters: | | +| Original TCAP Message type | same as TCAP Message type in the intermediate unprotected representation | + +| | | +|------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TCAP otid | same as TCAP orig. Transaction Id in the intermediate unprotected representation | +| TCAP dtid | same as TCAP dest. Transaction Id in the intermediate unprotected representation | +| TCAPsec Security header | See 3GPP TS 33.204 [8] | +| TCAPsec Cipher- or Cleartext | result of applying the encryption function to the concatenation of Dialogue Portion and Component Portion of the intermediate unprotected representation (ciphertext), or concatenation of Dialogue Portion and Component Portion of the intermediate unprotected representation(cleartext) | +| TCAPsec MAC | result of applying the integrity function to the concatenation of Security header and Cipher- or Cleartext of the intermediate protected representation. | + +##### Step 3: SCCP segmentation of the protected message + +In a third step the intermediate protected representation is transformed into a single SCCP UDT message, a single SCCP XUDT message, or several SCCP XUDT messages depending on the Original SCCP Message type of the intermediate protected representation and the need for segmentation as follows: + +If the Original SCCP Message type in the intermediate protected representation takes the value "UDT" and the message need not be segmented, it is transformed into a single SCCP UDT message with following parameter values: + +| | | +|-----------------------|-----------------------------------------------------------------------------------| +| Message Type | UDT | +| Protocol class | same as Original SCCP Protocol class in the intermediate protected representation | +| Called party address | same as SCCP Called party address in the intermediate protected representation | +| Calling party address | same as SCCP Calling party address in the intermediate protected representation | +| Data | (see below) | + +If the Original SCCP Message type in the intermediate protected representation takes the value "XUDT" and the message need not be segmented, it is transformed into a single SCCP XUDT message with following parameter values: + +| | | +|-----------------------|-----------------------------------------------------------------------------------| +| Message Type | XUDT | +| Protocol class | same as Original SCCP Protocol class in the intermediate protected representation | +| Hop counter | same as Original SCCP Hop counter in the intermediate protected representation | +| Called party address | same as SCCP Called party address in the intermediate protected representation | +| Calling party address | same as SCCP Calling party address in the intermediate protected representation | +| Data | (see below) | +| Segmentation | absent | +| Importance | same as Original SCCP Importance in the intermediate protected representation | + +If the Original SCCP Message type in the intermediate protected representation takes the value "UDT" and the message needs to be segmented, it is transformed into several SCCP XUDT message with following parameter values: + +| | | +|-----------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Message Type | XUDT | +| Protocol class | first segment: class 1 (in sequence delivery), return option: same as in Original SCCP Protocol class in the intermediate protected representation
subsequent segment: class 1 (in sequence delivery), return option: no special options | +| Hop counter | absent | +| Called party address | same as SCCP Called party address in the intermediate protected representation | +| Calling party address | the SS7 Security Gateway's own address | +| Data | (segment of see below) | +| Segmentation | see [9] | +| Importance | absent | + +If the Original SCCP Message type in the intermediate protected representation takes the value "XUDT" and the message needs to be segmented, it is transformed into several SCCP XUDT message with following parameter values: + +| | | +|----------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Message Type | XUDT | +| Protocol class | first segment: class 1 (in sequence delivery), return option: same as in Original SCCP Protocol class in the intermediate protected representation
subsequent segment: class 1 (in sequence delivery), return option: no special options | +| Hop counter | same as Original SCCP Hop counter in the intermediate protected representation | + +| | | +|-----------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Called party address | same as SCCP Called party address in the intermediate protected representation | +| Calling party address | if SCCP Segmentation Local reference is present in the intermediate protected representation: same as SCCP Calling party address in the intermediate protected representation;
otherwise: the SS7 Security Gateway's own address | +| Data | (segment of see below) | +| Segmentation | see [9]; if SCCP Segmentation Local reference is present in the intermediate protected representation, the same value shall be used. | +| Importance | same as Original SCCP Importance in the intermediate protected representation. | + +The SCCP Data parameter (re-assembled) shall take the following value: + +| | | +|-----------------------|----------------------------------| +| TCAP Message type | unidirectional | +| TCAP DialoguePortion | absent | +| TCAP ComponentPortion | one invoke component with: | +| invokeId | (any legal value) | +| linkerId | absent | +| operationCode | local value 90 (secureTransport) | +| parameter | ANY DEFINED BY operationCode | + +``` + +SS7-Secure-Transport-Operation-and-DataTypes { + itu-t identified-organization (4) etsi (0) mobileDomain (0) + gsm-Network (1) modules (3) ss7-Secure-Transport-Operation-and-DataTypes (27) version1 (1)} + +DEFINITIONS +IMPLICIT TAGS +::= +BEGIN + +EXPORTS + secureTransport +; + +IMPORTS + OPERATION +FROM Remote-Operations-Information-Objects { + joint-iso-itu-t remote-operations(4) + informationObjects(5) version1(0)} + +; + +``` + +| | +|-----------------------------------------------------------------------------------------------------------------| +| 
 secureTransport OPERATION ::= {     ARGUMENT         SecureTransportArg     CODE local:90 }
| +|-----------------------------------------------------------------------------------------------------------------| + +| | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 
 SecureTransportArg ::= SEQUENCE {     originalSCCP-Info           [0] OriginalSCCP-Info      OPTIONAL,     originalTCAP-Info           [1] OriginalTCAP-Info,     protectedPayload            [2] ProtectedPayload }
| +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 
 OriginalSCCP-Info ::= SEQUENCE {     originalSCCP-MessageType      [0] OriginalSCCP-MessageType      OPTIONAL,     -- original SCCP-MessageType shall be present if it is different from the actual     -- SCCP-Message type; otherwise it may be absent     originalSCCP-ProtocolClass    [1] OriginalSCCP-ProtocolClass      OPTIONAL     -- originalSCCP-ProtocolClass shall be present if it is different from the actual     -- SCCP-Protocol class (first segment); otherwise it may be absent.     originalSCCP-CallingPartyAddress [2] OriginalSCCP-CallingPartyAddress OPTIONAL,     -- originalSCCP-CallingPartyAddress shall be present if and only if the actual     -- SCCP Calling party address is the SS7 Security Gateway's own address }
| +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +``` + +OriginalSCCP-MessageType ::= ENUMERATED { + udt (9), + xudt (17) } + -- this parameter shall take the value of the Original SCCP Message type from the + -- intermediate protected representation + +``` + +``` + +OriginalSCCP-ProtocolClass ::= OCTET STRING(SIZE(1)) + -- coded according to ITU-T Q.713 + +``` + +``` + +OriginalSCCP-CallingPartyAddress ::= OCTET STRING(SIZE(3..18)) + -- coded according to ITU-T Q.713 + -- Octet 1: Address indicator + -- Octets 2 - n: Address + +``` + +``` + +OriginalTCAP-Info ::= SEQUENCE { + originalTCAP-MessageType OriginalTCAP-MessageType, + otid OTID, OPTIONAL, + dtid DTID, OPTIONAL +} + +``` + +``` + +OriginalTCAP-MessageType ::= ENUMERATED { + unidirectional (97), + begin (98), + end (100), + continue (101), + abort (103) } + -- this parameter shall take the value of the Original TCAP Message type from the + -- intermediate protected representation + +``` + +``` + +OTID ::= OCTET STRING(SIZE(1..4)) + -- OTID shall take the value of the TCAP otid from the intermediate protected + -- representation + +``` + +``` + +DTID ::= OCTET STRING(SIZE(1..4)) + -- DTID shall take the value of the TCAP dtid from the intermediate protected + -- representation + +``` + +``` + +ProtectedPayload ::= OCTET STRING(SIZE(13..3438)) + -- The protected payload is the concatenation of + -- 9 or 11 octets SecurityHeader, + -- n octets ciphertext or cleartext, and + -- 4 octets MAC + + -- The SecurityHeader is coded as follows (see 3GPP TS 33.204 [8]): + -- Octets 1-4: SPI + -- Octets 5-8: TVP. The TVP is a 32 bit time stamp. Its value is binary coded + -- and indicates the number of intervals of 100 milliseconds + -- elapsed since 1st January 2002, 0:00:00 UTC + -- Octet 9: Indicator Byte with bits 7-1 spare and bit 0 if set indicates presence of + -- Octets 10-11 + -- Octet 10: SS7 SEG-Id + -- Octet 11: Prop + +``` + +END + +#### 5.1.4.2 Transformation of protected message to unprotected message + +The protected TCAP-user message is either transported within an SCCP UDT message or it is transported within a single SCCP XUDT message or it is segmented over several SCCP XUDT messages. Other SCCP message types are not subject to protection. + +The transformation process is done in 3 steps: + +##### Step 1: SCCP re-assembly of the protected message + +In a first step the protected message is transformed into the intermediate protected representation (see chapter 5.1.4.1): + +If the protected message was transported within an SCCP UDT message, the intermediate protected representation of the message takes the following values: + +| | | +|-------------------------------------|---------------------------------------------------------------------------------------------------| +| SCCP Hop counter | absent | +| SCCP Called party address | same as in the received UDT message | +| SCCP Calling party address | same as in the received UDT message | +| SCCP Segmentation local reference | absent | +| SCCP Importance | absent | +| Original SCCP info | | +| Original SCCP Calling party address | absent | +| Original SCCP Message type | UDT | +| Original SCCP Protocol class | same as SCCP Protocol class in the received UDT message | +| Original TCAP info | | +| Original TCAP Message type | same as Original TCAP Message type in the TCAP-invoke component parameter of the received message | +| otid | same as otid in the TCAP-invoke component parameter of the received message | +| dtid | same as dtid in the TCAP-invoke component parameter of the received message | +| TCAPsec Security header | same as received in the TCAP-invoke component parameter of the received message | +| TCAPsec Cipher- or Cleartext | same as received in the TCAP-invoke component parameter of the received message | +| TCAPsec MAC | same as received in the TCAP-invoke component parameter of the received message | + +If the protected message was transported within a single SCCP XUDT message, the intermediate protected representation of the message takes the following values: + +| | | +|-------------------------------------|---------------------------------------------------------------------------------------------------| +| SCCP Hop counter | same as in the received XUDT message | +| SCCP Called party address | same as in the received XUDT message | +| SCCP Calling party address | same as in the received XUDT message | +| SCCP Segmentation local reference | absent | +| SCCP Importance | same as in the received XUDT message | +| Original SCCP info | | +| Original SCCP Calling party address | absent | +| Original SCCP Message type | same as OriginalSCCP-Messagetype in the TCAP-invoke component parameter of the received message | +| Original SCCP Protocol class | same as OriginalSCCP-ProtocolClass in the TCAP-invoke component parameter of the received message | +| Original TCAP info | | +| Original TCAP Message type | same as Original TCAP Message type in the TCAP-invoke component parameter of the received message | +| otid | same as otid in the TCAP-invoke component parameter of the received message | +| dtid | same as dtid in the TCAP-invoke component parameter of the received message | +| TCAPsec Security header | same as received in the TCAP-invoke component parameter of the received message | +| TCAPsec Cipher- or Cleartext | same as received in the TCAP-invoke component parameter of the received message | +| TCAPsec MAC | same as received in the TCAP-invoke component parameter of the received message | + +If the protected message was transported within several SCCP XUDT message, the intermediate protected representation of the message takes the following values: + +| | | +|---------------------------|--------------------------------------------| +| SCCP Hop counter | same as in the first received XUDT message | +| SCCP Called party address | same as in the first received XUDT message | + +| | | +|-------------------------------------|---------------------------------------------------------------------------------------------------------------------| +| SCCP Calling party address | same as in the first received XUDT message | +| SCCP Segmentation local reference | same as in the first received XUDT message | +| SCCP Importance | same as in the first received XUDT message | +| Original SCCP info | | +| Original SCCP Calling party address | same as OriginalSCCP-CallingPartyAddress in the TCAP-invoke component parameter of the received reassembled message | +| Original SCCP Message type | same as OriginalSCCP-MessageType in the TCAP-invoke component parameter of the received reassembled message | +| Original SCCP Protocol class | same as OriginalSCCP-ProtocolClass in the TCAP-invoke component parameter of the received reassembled message | +| Original TCAP info | | +| Original TCAP Message type | same as OriginalTCAP-MessageType in the TCAP-invoke component parameter of the received reassembled message | +| otid | same as otid in the TCAP-invoke component parameter of the received reassembled message | +| dtid | same as dtid in the TCAP-invoke component parameter of the received reassembled message | +| TCAPsec Security header | same as received in the TCAP-invoke component parameter of the received reassembled message | +| TCAPsec Cipher- or Cleartext | same as received in the TCAP-invoke component parameter of the received reassembled message | +| TCAPsec MAC | same as received in the TCAP-invoke component parameter of the received reassembled message | + +##### Step 2: De-Protection + +In a second step the intermediate protected representation is transformed into an intermediate unprotected representation (see chapter 5.1.4.1): + +The intermediate unprotected representation of the message takes the following values: + +| | | +|-----------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| SCCP Message type | same as OriginalSCCP-MessageType from the TCAP-invoke component's parameter of the intermediate protected representation | +| SCCP Protocol class | same as OriginalSCCP-ProtocolClass from the TCAP-invoke component's parameter of the intermediate protected representation | +| SCCP Hop counter | same as SCCP Hop counter in the intermediate protected representation | +| SCCP Called party address | same as SCCP Called party address in the intermediate protected representation | +| SCCP Calling party address | if OriginalSCCP-CallingPartyAddress is present in the intermediate protected representation, its value is taken; otherwise same as SCCP Calling party address of the intermediate protected representation | +| SCCP Segmentation local reference | if SCCP Message type in the intermediate unprotected representation is XUDT, then same as in the intermediate protected representation; otherwise absent. | +| SCCP Importance | same as in the intermediate unprotected representation | +| SCCP Data : | | +| TCAP Message type | same as OriginalTCAP-MessageType in the intermediate protected representation | +| TCAP orig. Transaction Id | same as otid in the intermediate protected representation | +| TCAP dest. Transaction Id | same as dtid in the intermediate protected representation | +| TCAP Dialogue Portion (optional) | First part of the cleartext (as indicated by TAG and LENGTH according to BER). If encryption was applied then ciphertext needs to be converted first to cleartext | +| TCAP Component Portion (optional) | second part of the cleartext (as indicated by TAG and LENGTH according to BER). If encryption was applied then ciphertext needs to be converted first to cleartext | + +##### Step 3: SCCP segmentation of the unprotected message + +In a third step the intermediate unprotected representation is transformed into a single SCCP UDT message, a single SCCP XUDT message, or several SCCP XUDT messages depending on the SCCP Message type of the intermediate unprotected representation and the need for segmentation as follows: + +If the SCCP Message type in the intermediate unprotected representation is "UDT", it is transformed into a single SCCP UDT message with following parameter values: + +| | | +|-----------------------|-----------------------------------------------------------------------------------| +| Message Type | UDT | +| Protocol class | same as SCCP Protocol class in the intermediate unprotected representation | +| Called party address | same as SCCP Called party address in the intermediate unprotected representation | +| Calling party address | same as SCCP Calling party address in the intermediate unprotected representation | +| Data | same as SCCP Data in the intermediate unprotected representation | + +If the SCCP Message type in the intermediate unprotected representation is "XUDT" and the message does not need to be segmented, it is transformed into a single SCCP XUDT message with following parameter values: + +| | | +|-----------------------|-----------------------------------------------------------------------------------| +| Message type | XUDT | +| Protocol class | same as SCCP Protocol class in the intermediate unprotected representation | +| Hop counter | same as SCCP Hop counter in the intermediate unprotected representation | +| Called party address | same as SCCP Called party address in the intermediate unprotected representation | +| Calling party address | same as SCCP Calling party address in the intermediate unprotected representation | +| Data | same as SCCP Data in the intermediate unprotected representation | +| Segmentation | absent | +| Importance | same as SCCP Importance in the intermediate unprotected representation | + +If the SCCP Message type in the intermediate unprotected representation is "XUDT" and the message needs to be segmented, it is transformed into several SCCP XUDT message with following parameter values: + +| | | +|--------------------------------------|------------------------------------------------------------------------------------------------------------------------------| +| Message type (all segments) | XUDT | +| Protocol class (first segment) | class 1 (in sequence delivery), return option: same as in SCCP Protocol class of the intermediate unprotected representation | +| (subsequent segments) | class 1 (in sequence delivery), return option: no special options | +| Hop counter (all segments) | same as SCCP Hop counter in the intermediate unprotected representation | +| Called party address (all segments) | same as SCCP Called party address in the intermediate unprotected representation | +| Calling party address (all segments) | same as SCCP Calling party address in the intermediate unprotected representation | +| Data | segment of SCCP Data from the intermediate unprotected representation (see ITU-T Q.714 [9]) | +| Segmentation | see [9]. Local reference shall be taken from the intermediate unprotected representation | +| Importance (all segments) | same as SCCP Importance in the intermediate unprotected representation | + +#### 5.1.4.3 Handling of received XUDTS messages and UDTS messages + +An SS7 Security Gateway shall not try to re-assemble XUDTS messages, since the SCCP option "return on error" is not set for subsequent XUDT segments. As a consequence the SS7 Security Gateway shall not try to protect or de-protect XUDTS messages (fragments) or UDTS messages. However, special handling of XUDTS messages and UDTS messages is required as follows: + +##### Outbound direction + +Instead of re-assembling and protecting the XUDTS messages or protecting UDTS messages, the SS7 Security Gateway shall remove the TCAP Dialogue Portion and the TCAP Component Portion from the SCCP Data parameter before sending the XUDTS message or UDTS message. This is in order not to pass the cleartext (or fragment of the cleartext) in outbound direction. SCCP message type and addresses shall not be changed. + +An example is shown in figure 5.1.4.3-1: A transit node in PLMN 2 cannot deliver the UDT message and therefore returns an UDTS message. SS7 Security Gateway 2 in PLMN 2 removes the cleartext (TCAP dialogue portion and TCAP component portion) from the SCCP data parameter. SS7 Security Gateway 1 in PLMN 1 recognizes that the + +received UDTS message does not contain a TCAP unidirectional message with a secure transport invoke component and therefore it does not modify the SCCP message. + +![Sequence diagram showing message exchanges between NE 1, SS7 Sec Gateway 1, SS7 Sec Gateway 2, Transit Node, and NE 2 across PLMN 1 and PLMN 2.](08c7a76a7786bd08b99dd4cb41583ef4_img.jpg) + +``` + +sequenceDiagram + participant NE 1 + participant SGW1 as SS7 Sec Gateway 1 + participant SGW2 as SS7 Sec Gateway 2 + participant TN as Transit Node + participant NE 2 + + Note left of NE 1: PLMN 1 + Note right of NE 2: PLMN 2 + + NE 1->>SGW1: UDT + SGW1->>SGW2: XUDT + SGW1->>SGW2: XUDT + SGW2->>TN: UDT + TN->>SGW2: UDTS + SGW2->>SGW1: UDTS + SGW1->>NE 1: UDTS + +``` + +Sequence diagram showing message exchanges between NE 1, SS7 Sec Gateway 1, SS7 Sec Gateway 2, Transit Node, and NE 2 across PLMN 1 and PLMN 2. + +**Figure 5.1.4.3-1: XUDTS messages and UDTS messages (Outbound direction)** + +##### Inbound direction + +Instead of re-assembling and de-protecting the XUDTS messages or de-protecting UDTS messages, the SS7 Security Gateway shall analyze the SCCP Called party address. If it matches with the SS7 Security Gateway's own address, it shall recover the OriginalSCCP-CallingPartyAddress from the (fragment in the) data parameter and replace the SCCP Called party address with the recovered value. In any case the SS7 Security Gateway shall recover and analyze the TCAP Message type from the (fragment in the) data parameter. If the recovered value is "unidirectional" and a invoke component with operation code "secure transport" is included, the SS7 Security Gateway shall recover the originalTCAP-MessageType, otid, and dtid from the OriginalTCAP-Info, replace the TCAP Message type with the original TCAP-MessageType, insert otid and dtid and remove the remaining material from the SCCP data parameter. If the received message is an XUDTS message and the original SCCP Message type was UDT then the SS7 Security shall modify the SCCP Message type to UDTS. + +An example is shown in figure 5.1.4.3-2: A transit node in a transit network cannot deliver the XUDT messages and therefore returns an XUDTS message (note that the second XUDT does not have the SCCP return option set). SS7 Security Gateway 1 in PLMN 1 recognizes that the received XUDTS message does contain a TCAP unidirectional message with a secure transport invoke component and therefore, since the original SCCP-MessageType is UDT, modifies the SCCP Message type from XUDTS to UDTS. Furthermore, the TCAP Message type is modified from unidirectional to the original TCAP-MessageType, the Transaction Ids are inserted, and the remaining material (fragment of the ciphertext) is removed. + +In addition the SS7 Security Gateway 1 in PLMN 1 recognizes that the received XUDTS message does contain SS7 Security Gateway 1's own address as SCCP Called party address and therefore replaces it with the original SCCPCalling party address. + +![Sequence diagram showing message exchanges between NE 1, SS7 Sec Gateway 1, Transit Node, SS7 Sec Gateway 2, and NE 2 across PLMN 1 and PLMN 2.](6629e8a87e7552e2454b7c3e9f6d73a0_img.jpg) + +The diagram illustrates a sequence of messages between network elements (NEs) and SS7 security gateways across two PLMNs. PLMN 1 contains NE 1, SS7 Sec Gateway 1, and a Transit Node. PLMN 2 contains SS7 Sec Gateway 2 and NE 2. The message flow is as follows: + +- NE 1 sends a UDT message to SS7 Sec Gateway 1. +- SS7 Sec Gateway 1 sends two XUDT messages to the Transit Node. +- The Transit Node sends an XUDTS message back to SS7 Sec Gateway 1. +- SS7 Sec Gateway 1 sends a UDTS message to NE 1. + +``` +sequenceDiagram + participant NE1 as NE 1 + participant SS7G1 as SS7 Sec Gateway 1 + participant TN as Transit Node + participant SS7G2 as SS7 Sec Gateway 2 + participant NE2 as NE 2 + + Note left of NE1: PLMN 1 + Note right of NE2: PLMN 2 + + NE1->>SS7G1: UDT + SS7G1->>TN: XUDT + SS7G1->>TN: XUDT + TN->>SS7G1: XUDTS + SS7G1->>NE1: UDTS +``` + +Sequence diagram showing message exchanges between NE 1, SS7 Sec Gateway 1, Transit Node, SS7 Sec Gateway 2, and NE 2 across PLMN 1 and PLMN 2. + +Figure 5.1.4.3-2: XUDTS messages and UDTS messages (inbound direction) + +# --- Annex A (informative): Change history + +| Change history | | | | | | | | +|----------------|-------|-----------|------|-----|----------------------------------------------------|--------|--------| +| Date | TSG # | TSG Doc. | CR | Rev | Subject/Comment | Old | New | +| 2006-06 | CT#32 | CP-060320 | | | Approved as version 7.0.0 | 2.0.0 | 7.0.0 | +| 2006-09 | CT#33 | CP-060413 | 0001 | | Addition of abbreviations and correction of a note | 7.0.0 | 7.1.0 | +| 2008-12 | CT#42 | | | | Upgraded unchanged from Rel-7 | 7.1.0 | 8.0.0 | +| 2009-12 | - | - | - | - | Update to Rel-9 version (MCC) | 8.0.0 | 9.0.0 | +| 2011-03 | - | - | - | - | Update to Rel-10 version (MCC) | 9.0.0 | 10.0.0 | +| 2012-09 | - | - | - | - | Update to Rel-11 version (MCC) | 10.0.0 | 11.0.0 | \ No newline at end of file diff --git a/marked/Rel-11/29_series/29205/af6be343f0c0a8f155f965dcf337b8af_img.jpg b/marked/Rel-11/29_series/29205/af6be343f0c0a8f155f965dcf337b8af_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..515ca3e85bc8a4d9f9724cbbe08f30a610726d19 --- /dev/null +++ b/marked/Rel-11/29_series/29205/af6be343f0c0a8f155f965dcf337b8af_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3a06679540073f84cd3667fe3ab0881eb0a1e54ca311611da3ff0ae3879c0a4e +size 11544 diff --git a/marked/Rel-11/29_series/29205/raw.md b/marked/Rel-11/29_series/29205/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..7f3ee93f853d042cb39ad6d08395f326e38eb26f --- /dev/null +++ b/marked/Rel-11/29_series/29205/raw.md @@ -0,0 +1,931 @@ + + + + + + +# Contents + +| | | +|--------------------------------------------------------------------------|-----------| +| Foreword ..... | 5 | +| 1 Scope..... | 6 | +| 2 References..... | 6 | +| 3 Definitions, symbols and abbreviations ..... | 7 | +| 3.1 Definitions..... | 7 | +| 3.2 Symbols..... | 7 | +| 3.3 Abbreviations ..... | 7 | +| 4 Protocols..... | 8 | +| 4.1 Call control protocol (Nc interface) ..... | 8 | +| 4.2 Interworking with other protocols..... | 8 | +| 4.3 Resource control protocol (G)MSC and MGW (Mc Interface) ..... | 8 | +| 4.4 Bearer control protocol between MGWs (Nb interface)..... | 9 | +| 4.5 Signalling Transport..... | 9 | +| 4.5.1 Call Control protocols ..... | 9 | +| 4.5.2 Resource control protocol (G)MSC and MGW (Mc Interface) ..... | 9 | +| 4.5.3 Bearer control protocol between MGWs (Nb interface) ..... | 9 | +| Annex A: Void..... | 9 | +| Annex B (normative): Transparent Support of Mobile Services ..... | 9 | +| B.1 Introduction..... | 9 | +| B.2 Mobile Service Transport (MST) – Format and Codes ..... | 10 | +| B.2.1 Encapsulated Application Information..... | 10 | +| B.2.1.1 General Layout ..... | 10 | +| B.2.1.2 List of Identifiers ..... | 12 | +| B.2.1.3 Mobile Equipment Identifier ..... | 12 | +| B.2.1.4 LCLS Negotiation Request..... | 13 | +| B.2.1.5 LCLS Negotiation Response ..... | 13 | +| B.2.1.6 LCLS Status..... | 14 | +| B.2.1.7 LCLS Status Change ..... | 14 | +| B.2.1.8 LCLS Status Result ..... | 14 | +| B.2.1.9 LCLS Global Call Reference..... | 15 | +| B.2.1.10 LCLS Configuration Preference..... | 16 | +| B.2.1.11 LCLS Configuration Change Request..... | 17 | +| B.2.1.12 LCLS Configuration Change Result ..... | 17 | +| B.2.2 Application Transport Instruction Indicators ..... | 18 | +| Annex C (normative): LCLS Service Application ..... | 18 | +| C.1 Use of MST ASE ..... | 18 | +| C.2 Procedures..... | 18 | +| C.2.1 Indication of LCLS Capability ..... | 18 | +| C.2.1.1 LCLS Service Capability Indication ..... | 18 | +| C.2.1.2 Actions at Originating Serving Node ..... | 19 | +| C.2.1.3 Actions at Intermediate Serving Node..... | 19 | +| C.2.1.4 Actions at Destination Serving Node ..... | 19 | +| C.2.2 Backward LCLS Negotiation during Call Setup..... | 20 | +| C.2.2.1 Introduction ..... | 20 | +| C.2.2.2 Actions at Destination Serving Node ..... | 20 | +| C.2.2.3 Actions at Intermediate Serving Node..... | 20 | +| C.2.2.4 Actions at Originating Serving Node ..... | 20 | +| C.2.3 Answer message..... | 21 | +| C.2.3.1 Introduction ..... | 21 | +| C.2.3.2 Actions at Destination Serving Node ..... | 21 | +| C.2.3.3 Actions at Intermediate Serving Node..... | 21 | + +- C.2.3.4 Actions at Originating Serving Node ..... 21 +- C.2.4 LCLS Configuration Change Request..... 21 +- C.2.4.1 Introduction ..... 21 +- C.2.4.2 Actions at Initiating Serving Node ..... 22 +- C.2.4.3 Actions at Intermediate Serving Node..... 22 +- C.2.4.4 Actions at Terminating Serving Node ..... 22 +- C.2.5 LCLS Status Update..... 22 +- C.2.5.1 Introduction ..... 22 +- C.2.5.2 Actions at Initiating Serving Node ..... 23 +- C.2.5.3 Actions at Intermediate Serving Node..... 23 +- C.2.5.4 Actions at Terminating Serving Node ..... 23 +- C.2.6 LCLS Status Change Request..... 23 +- C.2.6.1 Introduction ..... 23 +- C.2.6.2 Actions at Initiating Serving Node ..... 23 +- C.2.6.3 Actions at Intermediate Serving Node..... 24 +- C.2.6.4 Actions at Terminating Serving Node ..... 24 + +Annex D (informative): Change history..... 25 + +# --- Foreword + +This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +# --- 1 Scope + +The present document describes the protocols to be used when ITU-T Q.1902 "Bearer Independent Call Control" is used as call control protocol in a 3GPP Bearer Independent CS core network 3GPP TS 23.205 [1]. The Q.1902 operates between (G)MSC servers. The BICC architecture as described in ITU-T Q.1902 [6]-[10] consists of a number of protocols. The following types of protocols are described: call control protocol, bearer control protocols and a resource control protocol for this architecture. The architecture complies with the requirements imposed by 3GPP TS 23.205 [1] and TS 23.153 [2]. + +The present document is valid for a 3rd generation PLMN (UMTS) complying with Release 4 and later. + +Note: Q.1902 can be used in other network architectures than the one defined in 3GPP TS 23.205 [1] + +# --- 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.205: "Bearer Independent CS Core Network – Stage 2". +- [2] 3GPP TS 23.153: "Out of Band Transcoder Control - Stage 2". +- [3] 3GPP TS 29.232: "Media Gateway Controller (MGC) – Media Gateway (MGW) Interface; Stage 3". +- [4] 3GPP TS 29.414: "Core Network Nb Data Transport and Signalling Transport". +- [5] ITU-T Recommendation Q.765.5 (06/2000): "Application Transport Mechanism". +- [6] ITU-T Recommendation Q.1902.1 (07/2001): "Bearer Independent Call Control CS2 Functional Description". Inclusive Amendment 3: "Support for the Customized Alerting Tone (CAT) service". +- [7] ITU-T Recommendation Q.1902.2 (07/2001): "Bearer Independent Call Control CS2 General functions of messages and parameters". Inclusive Amendment 5: "Support for the Customized Alerting Tone (CAT) service". +- [8] ITU-T Q.1902.3 (07/2001): "Bearer Independent Call Control CS2 Formats and Codes". Inclusive Amendment 5: "Support for the Customized Alerting Tone (CAT) service". +- [9] ITU-T Recommendation Q.1902.4 (07/2001): "Bearer Independent Call Control CS2 Basic Call Procedures". +- [10] ITU-T Recommendation Q.1902.5 (07/2001): "Exceptions to the Application Transport Mechanism in the Context of Bearer Independent Call Control". +- [11] ITU-T Recommendation Q.1902.6 (07/2001): "Generic Signalling Procedures for the support of the ISDN User Part Supplementary Services and for bearer redirection". +- [12] ITU-T Recommendation Q.1950 (07/2001): "Call Bearer Control Protocol". +- [13] ITU-T Recommendations Q.2630.1 (12/1999), Q.2630.2 (12/2000): "AAL type 2 signalling protocol". +- [14] ITU-T Recommendation Q.1990 (07/2001): "BICC Bearer Control tunnelling protocol". + +- [15] ITU-T Recommendation Q.1970 (07/2001): "BICC IP Bearer Control protocol". +- [16] ITU-T Recommendation Q.1912.1 (07/2001): "Interworking between Signalling System No. 7 ISDN user part and the Bearer Independent Call Control protocol". +- [17] ITU-T Recommendation Q.1912.2 (07/2001): "Interworking between selected Signalling System (PSTN Access DSS1, C5, R1, R2, TUP) and the Bearer Independent Call Control Protocol". +- [18] ITU-T Recommendation Q.2150.0 (05/2001): "Generic Signalling Transport Service". +- [19] ITU-T Recommendation Q.2150.1 (05/2001): "Signalling Transport Converter on MTP3 and MTP3b". +- [20] ITU-T Recommendation Q.2150.3 (12/2002): "Signalling Transport Converter on SCTP". +- [21] ITU-T Recommendation H.248.4 (11/2000): "Gateway Control Protocol: Transport over SCTP". +- [22] 3GPP TS 29.202: "SS7 signalling transport in core network". +- [23] ITU-T Recommendation H.248.5 (11/2000): "Gateway control protocol: Transport over ATM". +- [24] ITU-T Q.765 (06/2000): "Signalling system No. 7 – Application transport mechanism". +- [25] 3GPP TS 23.003: "Numbering, addressing and identification". +- [26] 3GPP TS 23.216: "Single Radio Voice Call Continuity (SRVCC); Stage 2". +- [27] 3GPP TS 23.237: "IP Multimedia subsystem (IMS) Service Continuity; Stage 2". +- [28] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications". +- [29] 3GPP TS 23.284: "Local Call Local Switch; Stage 2". + +# --- 3 Definitions, symbols and abbreviations + +## 3.1 Definitions + +## 3.2 Symbols + +For the purposes of the present document, the following symbols apply: + +| | | +|----|-----------------------------------------------------| +| Nc | Interface between the (G)MSC servers. | +| Mc | Interface between the server and the media gateway. | +| Nb | Interface between media gateways (MGW). | + +## 3.3 Abbreviations + +For the purposes of the present document, the abbreviations as defined in 3GPP TR 21.905 [28] 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 [28]. + +| | | +|------|----------------------------------| +| APM | Application Transport Mechanism | +| | Application Transport Message | +| APP | Application Transport Parameter | +| BAT | Bearer Association Transport | +| BICC | Bearer Independent Call Control | +| C5 | CCITT signalling system number 5 | +| GCR | Global Call Reference | +| LCLS | Local Call Local Switch | +| M3UA | MTP3 – User Adaptation Layer | +| MGC | Media Gateway Controller | +| MST | Mobile Service Transport | +| R1 | Regional Signalling System 1 | + +| | | +|------|--------------------------------------| +| R2 | Regional Signalling System 2 | +| SCTP | Stream Control Transmission Protocol | +| SN | Serving Node | +| TUP | Telephony User Part | + +# 4 Protocols + +Implementations providing any of the interfaces or protocols identified in the subclauses below shall implement the requirements of the specifications identified in those subclauses. + +## 4.1 Call control protocol (Nc interface) + +| | | +|----------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Q.1902.1 | BICC PROTOCOL (CS2) FUNCTIONAL DESCRIPTION [6] | +| Q.1902.2 | BICC PROTOCOL (CS2) AND SIGNALLING SYSTEM NO 7 ISUP
GENERAL FUNCTIONS OF MESSAGES AND PARAMETERS [7] | +| Q.1902.3 | BICC PROTOCOL (CS2) AND SIGNALLING SYSTEM NO 7 ISUP
FORMATS AND CODES [8] (NOTE) | +| Q.1902.4 | BICC (CS2) BASIC CALL PROCEDURES [9] | +| Q.1902.5 | EXCEPTIONS TO THE APM IN THE CONTEXT OF BICC [10]
AMENDMENT TO ITU-T RECOMMENDATION Q.765.5 FOR BICC CS2 [5] | +| Q.1902.6 | GENERIC SIGNALLING PROCEDURES AND SUPPORT OF THE ISDN USER PART SUPPLEMENTARY
SERVICES WITH THE BEARER INDEPENDENT CALL CONTROL PROTOCOL [11] | +| NOTE: | The "Backward CAT indicators" parameter shall be encoded as an optional 3-octet parameter in the ACM, CPG and SEG messages rather than as a 1-octet parameter as incorrectly defined in Amendment 5 of ITU-T Recommendation Q.1902.3 [8]. | + +## 4.2 Interworking with other protocols + +| | | +|----------|-------------------------------------------------------------------------------------------------------------------------------------------| +| Q.1912.1 | ISUP-BICC INTERWORKING [16] | +| Q.1912.2 | INTERWORKING BETWEEN SELECTED SIGNALLING SYSTEMS (PSTN ACCESS DSS1 C5 R1 R2 TUP)
AND THE BEARER INDEPENDENT CALL CONTROL PROTOCOL [17] | + +## 4.3 Resource control protocol (G)MSC and MGW (Mc Interface) + +| | | +|----------------|------------------------------------------------------------------------------| +| 3GPP TS 29.232 | "Media Gateway Controller (MGC) – Media Gateway (MGW) Interface;Stage 3" [3] | +|----------------|------------------------------------------------------------------------------| + +## 4.4 Bearer control protocol between MGWs (Nb interface) + +| | | +|----------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 3GPP TS 29.414 | "Core Network Nb Data Transport and Signalling Transport" [4]
including ITU-T Recommendation Q.1970 "IP bearer control protocol" [15] , ITU-T Recommendation Q.1990 "BICC tunneling control protocol" [14] , ITU-T Recommendation Q.2630.1-2 "AAL type 2 signalling protocol" [13]. | +|----------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +## 4.5 Signalling Transport + +### 4.5.1 Call Control protocols + +| | | +|----------------|--------------------------------------------------------------------------------------------| +| Q.2150.0 | "Generic Signalling Transport Service" [18] | +| Q.2150.1 | "Signalling Transport Converter on MTP3 and MTP3b" [19] | +| Q.2150.3 | "Signalling Transport Converter on SCTP" [20] | +| 3GPP TS 29.202 | "SS7 signalling transport in core network" [22] Annex A: The use of M3UA in 3GPP networks. | + +### 4.5.2 Resource control protocol (G)MSC and MGW (Mc Interface) + +| | | +|----------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 3GPP TS 29.232 | "Media Gateway Controller (MGC) – Media Gateway (MGW) Interface; Stage 3" [3] including ITU-T Recommendation H.248.4 "Transport over SCTP" [21], ITU-T Recommendation H.248.5 "Transport over ATM" [23], and 3GPP TS 29.202 "SS7 signalling transport in core network" [22] Annex A: The use of M3UA in 3GPP networks. | +|----------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +### 4.5.3 Bearer control protocol between MGWs (Nb interface) + +| | | +|----------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 3GPP TS 29.414 | "Core Network Nb Data Transport and signalling transport" [4] including ITU-T Recommendation Q.2630.1-2: "AAL type 2 signalling protocol" [13] and the tunnel-up and tunnel-down procedure in 3GPP TS 29.232 [31] | +|----------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +# --- Annex A: Void + +# --- Annex B (normative): Transparent Support of Mobile Services + +## B.1 Introduction + +This Annex specifies a new mobile APM usage "Transparent support of mobile services". + +In ITU-T Recommendation Q.1902.3 [8], for the Application Transport Parameter (APP), the following codepoint is defined to refer to this application context identifier (ACI): + +0 0 0 0 1 1 1 MST + +The text in ITU-T Recommendation Q.1902.5 [10] shall be followed when implementing this application with the following clarification: + +- where the text refers to BAT ASE this shall be interpreted to mean Mobile Service Transport (MST) service. + +The MST service shall use implicit addressing; see ITU-T Recommendation Q.765 [24]. + +## B.2 Mobile Service Transport (MST) – Format and Codes + +### B.2.1 Encapsulated Application Information + +#### B.2.1.1 General Layout + +The general layout of the Encapsulated Application Information field of the Application Transport parameter as defined in ITU-T Recommendation Q.1902.3 [8] is shown in Table B.2.1.1.1. + +**Table B.2.1.1.1: Encapsulated application information field** + +| MSB | | | | | | | | LSB | | Octet | +|-----------------------------|---|---|---|---|---|---|---|-----|--|-------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | | | +| Identifier 1 | | | | | | | | | | 1 | +| Length indicator 1 | | | | | | | | | | 2 | +| Compatibility information 1 | | | | | | | | | | 3 | +| Contents 1 | | | | | | | | | | 4 | +| | | | | | | | | | | | +| Identifier n | | | | | | | | | | m | +| Length indicator n | | | | | | | | | | | +| Compatibility information n | | | | | | | | | | | +| Contents n | | | | | | | | | | p | + +Each information element within the Encapsulated Application Information field has the same structure. An information element consists of four fields which always appear in the following order: Identifier (one octet), Length indicator, Compatibility information, Contents. + +The Identifier distinguishes one type from another one and governs the interpretation of the contents. There are two types of Identifiers: type "constructor" and type "simple", for which the contents are defined as follows: + +- For a "constructor" type, the Contents field shall again consist of one or more information elements, each of which is structured as described above, i.e., Identifier, Length indicator, Compatibility information, Contents. +- For a "simple" type, the Contents field contains one value only. + +When passing on an information element of type "constructor", the order of the information elements within this "constructor" shall be maintained. + +The Length indicator specifies the length (i.e., integral number of octets in pure binary representation) of the Compatibility information and Contents. The length does not include the Identifier nor the Length indicator. + +The format of the Length indicator is shown in Table B.2.1.1.2. Bit 8 is defined as Extension indicator and indicates whether or not the information on the length continues through the next octet. Value "0" of the Extension indicator means "*information continues through the next octet*", while value "1" means "*last octet*". The Length indicator itself has a maximum length of 2 octets, i.e., if octet 1a is needed, the Extension indicator of octet 1a is always set to value "1". + +**Table B.2.1.1.2: Length indicator** + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | Octet | +|--------|---|---|---|-----|---|---|---|-----|-------| +| ext. | | | | | | | | LSB | 1 | +| ext. 1 | 0 | 0 | 0 | MSB | | | | | 1a | + +The Compatibility information contains corresponding instructions for the case that the received information element is unrecognised. The format of this field is shown in Table B.2.1.1.3. + +**Table B.2.1.1.3: Compatibility information** + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | Octet | +|------|-----------------------------------------------------|---|-----------------------|----------|-----------------------------------------------|---|-----------------------|-------| +| ext. | pass-on not possible
send notification indicator | | instruction indicator | reserved | general action
send notification indicator | | instruction indicator | 1 | + +The following codes are used in the subfields of the Compatibility information field. + +Bits 2 1 *Instruction indicator for general action* + +- 0 0 Pass on information element +- 0 1 Discard information element +- 1 0 Discard MST data +- 1 1 Release call + +Bit 3 *Send notification indicator for general action* + +- 0 Do not send notification +- 1 Send notification + +Bit 4 reserved + +Bits 6 5 *Instruction indicator for pass-on not possible* + +- 0 0 Release call +- 0 1 Discard information element +- 1 0 Discard MST data +- 1 1 reserved (interpreted as 00) + +Bit 7 *Send notification indicator for pass-on not possible* + +- 0 Do not send notification +- 1 Send notification + +Bit 8 *Extension indicator* + +- 0 Information continues through the next octet +- 1 Last octet + +The Contents field is the substance of the element and contains the information the element is intended to convey. + +#### B.2.1.2 List of Identifiers + +Table B.2.1.2.1 contains the list of Identifiers. + +**Table B.2.1.2.1: List of identifiers** + +| Value | Information element name | Type | Reference | +|------------------------------|-----------------------------------|--------|-----------| +| 0000 0000 | spare | - | | +| 0000 0001 | Mobile Equipment Identifier | simple | B.2.1.3 | +| 0000 0010 | LCLS Negotiation Request | simple | B.2.1.4 | +| 0000 0011 | LCLS Negotiation Response | simple | B.2.1.5 | +| 0000 0100 | LCLS Status | simple | B.2.1.6 | +| 0000 0101 | LCLS Status Change | simple | B.2.1.7 | +| 0000 0110 | LCLS Status Result | simple | B.2.1.8 | +| 0000 0111 | LCLS Global Call Reference | simple | B.2.1.9 | +| 0000 1000 | LCLS Configuration Preference | simple | B.2.1.10 | +| 0000 1001 | LCLS Configuration Change Request | simple | B.2.1.11 | +| 0000 1010 | LCLS Configuration Change Result | simple | B.2.1.12 | +| 0000 1011
to
1101 1111 | reserved for 3GPP use | - | | +| 1110 0000
to
1111 1111 | reserved for national use | - | | + +#### B.2.1.3 Mobile Equipment Identifier + +The format of the Mobile Equipment Identifier is shown in Table B.2.1.3.1. + +**Table B.2.1.3.1: Mobile Equipment Identifier** + +![](af6be343f0c0a8f155f965dcf337b8af_img.jpg) + +| MSB | | | | | | | | LSB | | +|-----------------------------|---|---|---|---|---|---|---|-------|--| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | Octet | | +| Mobile Equipment Identifier | | | | | | | | 1 | | +| | | | | | | | | ... | | +| | | | | | | | | x | | + +The MEI contains either the International Mobile station Equipment Identity (IMEI) or the International Mobile station Equipment Identity and Software Version Number (IMEISV) as defined in subclause 6.2 of 3GPP TS 23.003 [25]. + +Both IMEI and IMEISV are TBCD encoded where IMEI is 15 digits and IMEISV is 16 digits. Bits 5 to 8 of octet n+1 (where n represents the octet of the IMEI(SV) being encoded) encodes digit 2n, bits 1 to 4 of octet n+1 encodes digit 2n-1 (i.e. the order of digits is swapped in each octet compared to the digit order defined in 3GPP TS 23.003 [25]). For IMEI, bits 5 to 8 of the last octet shall be filled with an end mark coded as '1111'. + +For the use of the Mobile Equipment Identifier (MEI) see 3GPP TS 23.216 [26] and 3GPP TS 23.237 [27]. + +#### B.2.1.4 LCLS Negotiation Request + +The format of the LCLS Negotiation Request is shown in Table B.2.1.4.1. + +**Table B.2.1.4.1: LCLS Negotiation Request** + +| MSB | | LSB | | | | | | Octet | +|---------------------|-------|-----|---|---|---|----------------------|---|-------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +| Extension Indicator | Spare | | | | | Permission Indicator | | 1 | + +The LCLS Negotiation Request is sent in the forward direction to indicate LCLS usage permission. + +##### **Bit 1 2        Permission Indicator** + +00            LCLS is allowed +01            LCLS is not allowed +10 – 11      Reserved for future use + +Bit 3 - 7      Spare + +##### **Bit 8          Extension Indicator** + +0              information continues in next octet +1              last octet + +For the use of the LCLS Negotiation Request IE see Annex C.2.1 and 3GPP TS 23.284 [29]. + +#### B.2.1.5 LCLS Negotiation Response + +The format of the LCLS Negotiation Response is shown in Table B.2.1.5.1. + +**Table B.2.1.5.1: LCLS Negotiation Response** + +| MSB | | LSB | | | | | | Octet | +|-------|---|-----|---|---|---|----------------------|---|-------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +| Spare | | | | | | Permission Indicator | | 1 | + +The LCLS Negotiation Response contains information sent in the backwards direction to indicate result of the LCLS Negotiation Request. The LCLS Negotiation Response is coded as follows: + +##### **Bits 1 2        Permission Indicator** + +00            LCLS is allowed +01            LCLS is not allowed +10            LCLS is not supported by a subsequent node +11            spare + +Bits 3 - 8      Spare + +For the use of the LCLS Negotiation Response IE see Annex C.2.2 and 3GPP TS 23.284 [29]. + +#### B.2.1.6 LCLS Status + +The format of the LCLS Status is shown in Table B.2.1.6.1. + +**Table B.2.1.6.1: LCLS Status** + +| • MSB | | | | | | | • LSB | Octet | +|-------------|---|---|---|---|---|---|-------|-------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +| LCLS Status | | | | | | | | 1 | + +The LCLS Status contains information sent in forward and backward directions to indicate LCLS connection status. The LCLS Status is coded as follows: + +| Value | Meaning | +|-----------|----------------------------------------| +| 0000 0000 | no indication | +| 0000 0001 | LCLS is feasible but not yet connected | +| 0000 0010 | LCLS not connected | +| 0000 0011 | LCLS connected | + +All other values are reserved. + +For the use of the LCLS Status IE see Annex C.2.3, C.2.5 and 3GPP TS 23.284 [29]. + +#### B.2.1.7 LCLS Status Change + +The format of the LCLS Status Change is shown in Table B.2.1.7.1. + +**Table B.2.1.7.1: LCLS Status Change** + +| MSB | | | | | | | LSB | Octet | +|--------------------|---|---|---|---|---|---|-----|-------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +| LCLS Status Change | | | | | | | | 1 | + +The LCLS Status Change Identifier contains information sent in forward and backward directions to indicate requested change of LCLS connection status. The LCLS Status Change Identifier is coded as follows: + +| Value | Meaning | +|-----------|---------------------------------------------| +| 0000 0000 | LCLS connection preparation | +| 0000 0001 | LCLS disconnection preparation | +| 0000 0010 | LCLS disconnection preparation for Handover | + +All other values are reserved. + +For the use of the LCLS Status Change IE see Annex C.2.6 and 3GPP TS 23.284 [29]. + +#### B.2.1.8 LCLS Status Result + +The format of the LCLS Status Result is shown in Table B.2.1.8.1. + +**Table B.2.1.8.1: LCLS Status Result** + +| MSB | | | | | | | LSB | Octet | +|-------|---|---|---------------------|---|---|----------------------|-----|-------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +| Spare | | | Rejection Indicator | | | Acceptance Indicator | | 1 | + +The LCLS Status Result contains information sent in forward and backward directions to indicate result of the LCLS Status Change Request. The LCLS Status Result is coded as follows: + +| Bit 1 | Acceptance Indicator | +|-------|-------------------------------------| +| 0 | LCLS Status Change request accepted | +| 1 | LCLS Status Change request rejected | + +| | | +|---------------------|-------------------------------| +| Bits 2 3 4 5 | Rejection Indicator | +| 0000 | No indication | +| 0001 | Ongoing supplementary service | +| 0010 – 1111 | Reserved for future use | +| Bits 6 - 8 | Spare | + +For the use of the LCLS Status Result IE see Annex C.2.6 and 3GPP TS 23.284 [29]. + +#### B.2.1.9 LCLS Global Call Reference + +The format of the LCLS Global Call Reference (GCR) is shown in Table B.2.1.9.1. + +**Table B.2.1.9.1: LCLS Global Call Reference** + +| MSB | | | | LSB | | | | Octet | +|------------------------------------|---|---|---|-----|---|---|---|---------------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +| Network ID length indicator | | | | | | | | 1 | +| Network ID | | | | | | | | 2 | +| (variable length 3 – 5 octets) | | | | | | | | 4+m (m=0,1,2) | +| Node ID length indicator | | | | | | | | 5+m | +| Node ID | | | | | | | | 6+m | +| (fixed length: 2 octets) | | | | | | | | 7+m | +| Call Reference ID length indicator | | | | | | | | 8+m | +| Call Reference ID | | | | | | | | 9+m | +| (fixed length: 5 octets) | | | | | | | |
13+m | + +The LCLS GCR is information sent in forward direction to uniquely identify a call and correlate activities associated with that call. The LCLS GCR is coded as follows: + +- Network ID length indicator +Binary coded information indicating the number of octets in the Network ID field. +- Network ID +Information identifying a network. The Network ID field is specified in ITU-T Recommendation Q.1902.3 [8]. +- Node ID length Indicator +Binary coded information indicating the number of octets in the Node ID field. +- Node ID +A binary number that uniquely identifies within the network the node which generates the call reference. +- Call Reference ID length indicator +Binary coded information indicating the number of octets in the Call Reference ID field. +- Call Reference ID +A binary number used for the call reference of the call. It is generated by the originating serving node for each call. + +NOTE: If the originating serving radio access is GERAN the format of the Call Reference ID subfield is shown in Table B.2.1.9.2. The originating BSS ID is an integer that uniquely identifies the Base Station Subsystem (BSS) Node within an operator's network. + +**Table B.2.1.9.2: Call Reference ID** + +| MSB | | LSB | | | | | | Octet | +|------------------------------------------------|---|-----|---|---|---|---|---|-------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +| Call Identifier
(fixed length: 3 octets) | | | | | | | | 1 | +| | | | | | | | | 2 | +| | | | | | | | | 3 | +| Originating BSS ID
(fixed length: 2 octets) | | | | | | | | 4 | +| | | | | | | | | 5 | + +For the use of the LCLS GCR IE see Annex C.2.1 and 3GPP TS 23.284 [29]. + +#### B.2.1.10 LCLS Configuration Preference + +The format of the LCLS Configuration Preference is shown in Table B.2.1.10.1. + +**Table B.2.1.10.1: LCLS Configuration Preference** + +| MSB | | | | LSB | | | | Octet | +|---------------------|-------|---|---|-----------------------------------|----------------------------------|---------------------------------|--------------------------------|-------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +| Extension Indicator | Spare | | | Backward Data Reception Indicator | Forward Data Reception Indicator | Backward Data Sending Indicator | Forward Data Sending Indicator | 1 | + +The LCLS Configuration Preference contains information sent in forward and backward directions to indicate negotiated LCLS configuration preference. + +##### Bit 1 Forward Data Sending Indicator + +0 not required +1 required + +##### Bit 2 Backward Data Sending Indicator + +0 not required +1 required + +##### Bit 3 Forward Data Reception Indicator + +0 not required +1 required + +##### Bit 4 Backward Data Reception Indicator + +0 not required +1 required + +##### Bits 5 - 7 Spare + +##### Bit 8 Extension Indicator + +0 information continues in next octet +1 last octet + +For the use of the LCLS Configuration Preference IE see Annex C.2.1, C.2.2, C.2.4 and 3GPP TS 23.284 [29]. + +#### B.2.1.11 LCLS Configuration Change Request + +The format of the LCLS Configuration Change Request is shown in Table B.2.1.11.1. + +**Table B.2.1.11.1: LCLS Configuration Change Request** + +| MSB | | | | | | | LSB | | | +|---------------------|-------|---|---|---|---|------|-----|-------|--| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | Octet | | +| Extension Indicator | Spare | | | | | Type | | 1 | | + +The LCLS Configuration Change Request contains information sent in the forward and backward directions to indicate type of LCLS Configuration Change Request. + +| | | +|----------------|----------------------------------------------------| +| Bit 1 2 | Type | +| 00 | LCLS Configuration Preference Modification Request | +| 01 - 11 | Spare | +|
| | +| Bit 3 - 7 | Spare | +|
| | +| Bit 8 | Extension Indicator | +| 0 | information continues in next octet | +| 1 | last octet | + +For the use of the LCLS Configuration Change Request IE see Annex C.2.4 and 3GPP TS 23.284 [29]. + +#### B.2.1.12 LCLS Configuration Change Result + +The format of the LCLS Configuration Change Result is shown in Table B.2.1.12.1. + +**Table B.2.1.12.1: LCLS Configuration Change Result** + +| MSB | | | | | | | | LSB | | +|-------|---|---|---------------------|---|---|---|----------------------|-------|---| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | Octet | | +| Spare | | | Rejection Indicator | | | | Acceptance Indicator | | 1 | + +The LCLS Configuration Change Result contains information sent in the backward direction to indicate result of the LCLS Configuration Change Request. The LCLS Configuration Change Result is coded as follows: + +| | | +|---------------------|-------------------------------------------------------------------------------------------------------| +| Bit 1 | Acceptance Indicator | +| 0 | LCLS Configuration Change request accepted | +| 1 | LCLS Configuration Change request rejected (if set then Rejection Indicator provides further details) | +|
| | +| Bits 2 3 4 5 | Rejection Indicator | +| 0000 | No indication | +| 0001 | Requested LCLS configuration not supported | +| 0010 | Ongoing supplementary service | +| 0011 – 1111 | Reserved for future use | +|
| | +| Bits 6 - 8 | Spare | + +For the use of the LCLS Configuration Change Result IE see Annex C.2.4 and 3GPP TS 23.284 [29]. + +### B.2.2 Application Transport Instruction Indicators + +For the MST service the Application Transport Instruction Indicators (ATII) shall be set as follows: + +| | | | +|------|---|-------------------------------------| +| Bits | 1 | Release call indicator (RCI) | +| | 0 | do not release call | + +| | | | +|-----|---|------------------------------------------| +| Bit | 2 | Send notification indicator (SNI) | +| | 0 | do not send notification | + +# --- Annex C (normative): LCLS Service Application + +LCLS Service is defined in 3GPP TS 23.284 [29] and is dependent on the following identifiers being included in BICC/ISUP messaging. The following sections describe the detailed protocol behaviour when these identifiers are included. + +## --- C.1 Use of MST ASE + +LCLS service makes use of the services of the MST ASE described in Annex B. The services of the MST ASE are accessed by means of primitives (such as "MST\_data") which are the same as BAT ASE primitives defined in ITU-T Recommendation Q.765.5 [5]. + +## --- C.2 Procedures + +### C.2.1 Indication of LCLS Capability + +#### C.2.1.1 LCLS Service Capability Indication + +LCLS service shall be used for a call if MST\_data primitive associated with an IAM includes LCLS Information Elements: a LCLS GCR, a LCLS Negotiation Request and a LCLS Configuration Preference. The absence of the LCLS Negotiation, the LCLS Configuration Preference and the LCLS GCR Information Elements in the IAM specifies that the LCLS service shall not be used. + +The compatibility information of the LCLS Negotiation Request, the LCLS Configuration Preference and the LCLS GCR Information Elements shall be set so as to cause the Information Element to be discarded by nodes that do not support LCLS service. + +The procedures for call establishment using the LCLS service are described in 3GPP TS 23.284 [29]. + +#### C.2.1.2 Actions at Originating Serving Node + +An originating Serving Node (SN) that supports the LCLS service shall indicate this within the IAM message of the mobile originating call by including the LCLS Negotiation Request, the LCLS Configuration Preference and the LCLS GCR Information Elements within the MST Application Transport Parameter (APP) within the IAM. + +When the LCLS service is allowed to be used the IAM is sent to the succeeding node with the Permission Indicator of the LCLS Negotiation Request Information Element set to "LCLS is allowed". + +Depending on network requirements the originating SN may additionally indicate required configurations for user plane connectivity towards originating or terminating UE within the LCLS Configuration Preference Information Element. If the originating MSC server needs to: + +- send data towards the terminating UE it shall set Forward Data Sending Indicator to "required"; +- send data towards the originating UE it shall set Backward Data Sending Indicator to "required"; +- receive data from the originating UE it shall set Forward Data Reception Indicator to "required"; +- receive data from the terminating UE it shall set Backward Data Reception Indicator to "required". + +The originating SN shall perform the setting of LCLS Configuration Preference Information Element according to rules specified in sub-clause 4.2 of 3GPP TS 23.284 [29] or it may determine that LCLS is not allowed and indicate this by setting the value of Permission Indicator of the LCLS Negotiation Request Information Element to "LCLS is not allowed". + +#### C.2.1.3 Actions at Intermediate Serving Node + +For the intermediate Serving Node (SN), LCLS service indication (i.e. LCLS GCR, LCLS Negotiation Request and LCLS Configuration Preference Information Elements) shall be included only if received from the preceding node and if the node itself supports the LCLS service. + +The intermediate SN shall not change the LCLS GCR Information Element. If the intermediate SN receives Permission Indicator of the LCLS Negotiation Request Information Element set to "LCLS is not allowed" it shall not change it. + +Depending on network requirements the intermediate SN may additionally indicate required configurations for user plane connectivity towards originating or terminating UE by changing the received LCLS Configuration Preference Information Element. If the intermediate SN needs to: + +- send data towards the terminating UE it shall set Forward Data Sending Indicator to "required"; +- send data towards the originating UE it shall set Backward Data Sending Indicator to "required"; +- receive data from the originating UE it shall set Forward Data Reception Indicator to "required"; +- receive data from the terminating UE it shall set Backward Data Reception Indicator to "required". + +If the intermediate SN receives any of these indicators set to "required" it shall not change them. + +#### C.2.1.4 Actions at Destination Serving Node + +For the destination Serving Node (SN), LCLS service shall be supported only if the IAM with the LCLS Negotiation Request, LCLS Configuration Preference and LCLS GCR Information Elements within the MST Application Transport Parameter (APP) is received from the preceding node and if the node itself supports the LCLS service. + +Depending on network requirements the destination SN may additionally modify received configurations for user plane connectivity towards originating or terminating UE, by changing the settings of the LCLS Configuration Preference Information Element. If the destination SN needs to: + +- send data towards the terminating UE it shall set Forward Data Sending Indicator to "required"; +- send data towards the originating UE it shall set Backward Data Sending Indicator to "required"; +- receive data from the originating UE it shall set Forward Data Reception Indicator to "required"; +- receive data from the terminating UE it shall set Backward Data Reception Indicator to "required". + +If the destination SN receives any of these indicators set to "required" it shall not change them. + +The destination SN shall perform modification of LCLS Configuration Preference Information Element according to rules specified in sub-clause 4.2 of 3GPP TS 23.284 [29] or it may determine that LCLS is not allowed and shall indicate this by setting the value of Permission Indicator of the LCLS Negotiation Response Information Element to "LCLS is not allowed". + +### C.2.2 Backward LCLS Negotiation during Call Setup + +#### C.2.2.1 Introduction + +LCLS service shall be used for a call if MST\_data primitive associated with first backward (APM or ACM) message includes a LCLS Negotiation Response and a LCLS Configuration Preference Information Elements. The absence of the LCLS Negotiation Response and the LCLS Configuration Preference Information Elements in the first backward message specifies that the LCLS service shall not be used. + +The compatibility information of the LCLS Negotiation Response and the LCLS Configuration Preference Information Elements shall be set so as to cause the Information Element to be discarded by nodes that do not support LCLS service. + +#### C.2.2.2 Actions at Destination Serving Node + +If LCLS service is supported according to conditions specified in sub-clause C.2.1.4 a destination SN shall include in the first backward message (APM or ACM) the LCLS Negotiation Response and the LCLS Configuration Preference Information Elements in the MST\_Data request primitive. + +#### C.2.2.3 Actions at Intermediate Serving Node + +If LCLS service is supported according to conditions specified in sub-clause C.2.1.3 but a succeeding node does not return LCLS Negotiation Response Information Element in the first backward message, an Intermediate SN shall include the LCLS Negotiation Response Information Element. The Permission Indicator of the LCLS Negotiation Response Information Element shall be set to "LCLS is not supported by a subsequent node". + +On receipt of a backward message (APM, ACM or CPG) with the LCLS Negotiation Response and the LCLS Configuration Preference Information Elements the Intermediate SN shall store the LCLS configuration settings from the LCLS Configuration Preference Information Element and shall forward the LCLS Negotiation Response and the LCLS Configuration Preference Information Elements unchanged. + +#### C.2.2.4 Actions at Originating Serving Node + +If the first backward message does not contain the LCLS Negotiation Response and the LCLS Configuration Preference Information Elements the originating SN shall assume that LCLS is not supported by succeeding node and LCLS shall not be performed for that call; no further LCLS signalling shall take place for that call. + +If the first backward message contains the LCLS Negotiation Response Information Element but the Permission Indicator is set to "LCLS Not Allowed" or "LCLS is not supported by a subsequent node" then the originating SN shall not request establishment of the LCLS connection at this time. + +NOTE: A subsequent LCLS Negotiation Response Information Element can be received from succeeding nodes, e.g. in the event of a call forwarding on no reply. + +### C.2.3 Answer message + +#### C.2.3.1 Introduction + +LCLS connection may be established for a call if MST\_data primitive associated with an ANM includes a LCLS Status Identifier Information Element. The absence of the LCLS Status Identifier Information Element in the ANM specifies that the LCLS connection shall not be requested. + +The compatibility information of the LCLS Status Identifier shall be set so as to cause the Information Element to be discarded by nodes that do not support LCLS service. + +#### C.2.3.2 Actions at Destination Serving Node + +If a destination SN determines that LCLS service is feasible according to the conditions specified in sub-clause 6.2.1.3.4 of 3GPP TS 23.284 [29] it shall include the LCLS Status Identifier Information Element set to "LCLS feasible but not yet connected" within the MST Application Transport Parameter (APP) within the ANM. + +#### C.2.3.3 Actions at Intermediate Serving Node + +An Intermediate SN shall pass the LCLS Status Identifier within the ANM unchanged. + +#### C.2.3.4 Actions at Originating Serving Node + +When an originating SN receives an ANM with the LCLS Status Identifier indicating the LCLS service is feasible it shall request LCLS connection. + +### C.2.4 LCLS Configuration Change Request + +#### C.2.4.1 Introduction + +Modification of a LCLS configuration can only occur after the LCLS negotiation has been performed during the call set-up phase according to the procedures described in sub-clauses C.2.1 and C.2.2. A SN involved in a LCLS Configuration Change procedure must not initiate a new LCLS Configuration Change Request until the existing LCLS Configuration Change procedure has been completed. + +A LCLS Configuration Change Request message may be sent in either direction and at any time during the active phase of a call, after the LCLS negotiation has been performed during the call establishment. A LCLS Configuration Change Request and a LCLS Configuration Preference Information Elements indicating the requested change of the LCLS configuration shall be included in a MST\_data primitive, corresponding to an APM message. + +A MST\_Data primitive, corresponding to the APM message shall be issued in response, including the LCLS Configuration Preference and the LCLS Configuration Change Result Information Elements indicating if the requested change of LCLS configuration has been accepted and if it has not been accepted the reason for rejection. + +The compatibility information of the LCLS Configuration Preference, the LCLS Configuration Change Request and LCLS Configuration Change Result Information Elements shall be set so as to cause the Information Element to be discarded and send notification by nodes that do not support LCLS service. + +NOTE: The term "initiating" SN in the following clauses refers to a SN which initiates the LCLS Configuration Change Request. The term "terminating" SN in the following clauses refers to a SN which terminates the LCLS Configuration Change Request. + +#### C.2.4.2 Actions at Initiating Serving Node + +If a SN determines that LCLS configuration needs to be changed it may send an APM message which includes a LCLS Configuration Change Request and the LCLS Configuration Preference Information Elements to its succeeding and/or preceding node. The initiating SN shall set the desired configurations as described in sub-clause C.2.1.2. + +The LCLS Configuration Change Request may only be initiated if LCLS Negotiation was performed during call establishment. + +NOTE: this does not require that LCLS was permitted during the call establishment. + +On receipt of an APM message containing the LCLS Configuration Preference and the LCLS Configuration Change Result Information Elements, if the result indicates "accepted" the modification of the LCLS Configuration settings has been successful. If the LCLS Configuration Change Result Information Element indicates "rejected" the initiating SN shall resume the LCLS connection with the LCLS configuration unchanged. + +#### C.2.4.3 Actions at Intermediate Serving Node + +When an intermediate SN receives an APM message with the LCLS Configuration Change Request and the LCLS Configuration Preference Information Elements requesting a certain LCLS Configuration Change the intermediate SN shall check if it can support the requested LCLS configuration. If the intermediate SN can support the proposed LCLS configuration it shall forward the LCLS Configuration Preference and the LCLS Configuration Change Request Information Elements to its succeeding or preceding node. If the intermediate SN cannot support/permit the proposed LCLS configuration it shall respond with a LCLS Configuration Change Result Information Element set to "LCLS Configuration Change request rejected" along with the Rejection Indicator detailing the reason for rejection. + +On receipt of an APM message with the LCLS Configuration Change Result and LCLS Configuration Preference Information Elements from its succeeding/preceding node if the LCLS Configuration Change Result Information Elements indicates "accepted" the intermediate SN shall store the LCLS configuration settings from the LCLS Configuration Preference Information Element and shall forward the APM message to its preceding/succeeding node. + +If the LCLS Configuration Change Result Information Element indicates "rejected" the intermediate SN shall resume the LCLS connection with the LCLS configuration unchanged and the intermediate SN shall forward the APM message to its preceding/succeeding node. + +#### C.2.4.4 Actions at Terminating Serving Node + +When an SN which is a terminating SN with respect to a LCLS Configuration Change Request receives an APM message with the LCLS Configuration Change Request and LCLS Configuration Preference Information Elements requesting a certain LCLS Configuration Change the terminating SN shall check if it can support the requested LCLS configuration. + +If the terminating SN can support the proposed LCLS configuration change it shall return the LCLS Configuration Preference Information Element and the LCLS Configuration Change Result Information Element indicating acceptance of the LCLS Configuration Change to its succeeding or preceding node. If the terminating SN cannot support/permit the proposed LCLS configuration it shall respond with a LCLS Configuration Change Result Information Element set to "LCLS Configuration Change request rejected" along with the Rejection Indicator detailing the reason for rejection. + +### C.2.5 LCLS Status Update + +#### C.2.5.1 Introduction + +A LCLS Status Update message may be sent in either direction to indicate that a LCLS connection status has been changed. A LCLS Status Identifier Information Element indicating the new LCLS connection status value shall be included in a MST\_data primitive, corresponding to an APM message. + +The compatibility information of the LCLS Status Identifier shall be set so as to cause the Information Element to be discarded and send notification by nodes that do not support LCLS service. + +NOTE: The term "initiating" SN in the following clauses refers to an originating SN or a destination SN that may initiate the LCLS Status Update message. The term "terminating" SN in the following clauses refers to an originating SN or a destination SN that may receive the LCLS Status Update message. + +#### C.2.5.2 Actions at Initiating Serving Node + +If a SN determines that the LCLS connection status has been changed it shall send the new LCLS connection status value to an adjacent SN. An initiating SN shall send the LCLS Status Identifier Information Element within the MST Application Transport Parameter (APP) within the APM message. + +#### C.2.5.3 Actions at Intermediate Serving Node + +When an intermediate SN receives the APM message with the LCLS Status Identifier Information Element from the preceding/succeeding SN and if the same LCLS connection status value has not been already received from the succeeding/preceding SN, the intermediate SN shall store the new LCLS Connection status value and shall pass the LCLS Status Identifier Information Element within the APM message unchanged to its succeeding/preceding SN. + +#### C.2.5.4 Actions at Terminating Serving Node + +When a terminating SN receives the APM message with the LCLS Status Identifier Information Element from the adjacent SN, it shall update its LCLS connection status value. + +### C.2.6 LCLS Status Change Request + +#### C.2.6.1 Introduction + +A LCLS Status Change Request message may be sent in either direction and at any time during the active phase of a call, after the LCLS has been initially established. A LCLS Status Change Identifier Information Element indicating the requested change of the LCLS connection status shall be included in a MST\_data primitive, corresponding to an APM message. + +An MST\_Data primitive, corresponding to the APM message shall be issued in response, including the LCLS Status Change Identifier Information Element and a LCLS Status Result Identifier Information Element indicating if the requested change of LCLS connection status has been accepted and if it has not been accepted the reason for rejection. + +The compatibility information of the LCLS Status Change Identifier and the LCLS Status Result Identifier shall be set so as to cause the Information Element to be discarded and send notification by nodes that do not support LCLS service. + +NOTE: The term "initiating" SN in the following clauses refers to a SN which initiates the LCLS Status Change. The term "terminating" SN in the following clauses refers to a SN which terminates the LCLS Status Change. + +#### C.2.6.2 Actions at Initiating Serving Node + +When a SN determines that the LCLS connection status needs to be changed, it shall request the change of the LCLS connection status from its preceding and/or succeeding SN. An initiating SN shall send the LCLS Status Change Identifier Information Element within the MST Application Transport Parameter (APP) within an APM message. + +An APM message containing the LCLS Status Change Identifier Information Element and a LCLS Status Result Identifier Information Element will be received in response from the succeeding and/or preceding SN. + +If initiating SN is an SN serving a Radio Network (originating SN or destination SN), upon reception of the LCLS Status Result Identifier Information Element indicating the acceptance of the requested LCLS connection status change, the initiating SN shall change the LCLS connection status. + +NOTE: This change of LCLS connection status can be deferred until signalling interaction with the served Radio Network Controller, which is outside of the scope of this specification. + +#### C.2.6.3 Actions at Intermediate Serving Node + +When an intermediate SN receives from a preceding/succeeding SN an APM message that includes a LCLS Status Change Identifier Information Element within the MST Application Transport Parameter (APP) it shall check if it can support the required change of the LCLS connection status. + +If the intermediate SN cannot support the requested change of the LCLS connection status it shall respond to the preceding/succeeding SN with the APM message containing the LCLS Status Change Identifier Information Element and a LCLS Status Result Identifier Information Element with an Acceptance indicator set to "LCLS Status Change request rejected" along with a Rejection Indicator detailing the reason for rejection. + +If the intermediate SN can support the required change of the LCLS connection status it shall pass the LCLS Status Change Identifier Information Element within the APM message unchanged to its succeeding/preceding SN. An APM message will be received in response, including the LCLS Status Change Identifier Information Element and a LCLS Status Result Identifier Information Element from its succeeding/preceding SN. The intermediate SN shall pass the LCLS Status Change Identifier Information Element and the LCLS Status Result Identifier Information Element within the APM message unchanged to its succeeding/preceding SN. + +#### C.2.6.4 Actions at Terminating Serving Node + +Upon reception of an APM message that includes a LCLS Status Change Identifier Information Element, from the adjacent SN, a terminating SN shall check if it can support the required change of the LCLS connection status. + +If the terminating SN can support the required change, it shall change the LCLS connection status. If the result of the LCLS connection status change is successful the terminating SN shall send to the adjacent SN the APM message with the LCLS Status Change Identifier Information Element and a LCLS Status Result Identifier Information Element indicating the acceptance of the requested LCLS connection status change. + +NOTE: If the terminating SN is an SN serving a Radio Network (originating SN or destination SN), there can be additional signalling with the served Radio Network Controller, prior to responding to the LCLS Status Change Request; this is, however, outside of the scope of this specification. + +If the result of the LCLS connection status change is unsuccessful or if the terminating SN cannot support the required change it shall respond to the adjacent SN with the APM message containing the LCLS Status Change Identifier Information Element and a LCLS Status Result Identifier Information Element with an Acceptance indicator set to "LCLS Status Change request rejected" along with a Rejection Indicator detailing the reason for rejection. + +# Annex D (informative): Change history + +| Change history | | | | | | | | +|----------------|---------------------------------|-----------|------|------|-----------------------------------------------------------------------------------|--------|--------| +| Date | TSG # | TSG Doc. | CR | Rev | Subject/Comment | Old | New | +| 17/1/01 | CN3/CN4
#66
Beijing | | | 0.1. | New Document approved | - | 0.1.0 | +| 15/2/01 | Ad hoc
CN 4#6 in
Madrid | | | 0.2 | Revised Document approved | 0.1.0 | 0.2.0 | +| 01/3/01 | CN 4 #7
Sophia—
Antopolis | | | 0.3 | Forwarded to TSG CN Plenary meeting #11 for approval | 0.2.0 | 2.0.0 | +| 03/2001 | CN#11 | NP-010083 | | | Modifications made during CN#11 | 2.0.0 | 2.1.0 | +| 03/2001 | CN#11 | NP-010214 | | | Approved in CN#11 | 2.1.0 | 4.0.0 | +| 06/2001 | CN#12 | NP-010285 | 0001 | 1 | Changes to provide interworking between signalling transport | 4.0.0 | 4.1.0 | +| 09/2001 | CN#13 | | | | Editorial clean up | 4.1.0 | 4.2.0 | +| 09/2001 | CN#13 | NP-010452 | 0002 | | Mc signalling transport in IP environment | 4.1.0 | 4.2.0 | +| 09/2001 | CN#13 | NP-010452 | 0003 | 1 | BICC signalling transport in IP environment | 4.1.0 | 4.2.0 | +| 09/2001 | CN#13 | NP-010452 | 0004 | | Status of ITU recommendation Q.2150.3 | 4.1.0 | 4.2.0 | +| 06/2002 | CN#16 | | | | Rel-5 created after CN#16 | 4.2.0 | 5.0.0 | +| 06/2003 | CN#20 | NP-030220 | 0006 | 2 | Alignment of references after renumbering of H248 by ITU-T | 5.0.0 | 5.1.0 | +| 12/2004 | CN#26 | | | | Rel-6 created after CN#26 | 5.1.0 | 6.0.0 | +| 06/2006 | CT#32 | CP-060298 | 0009 | 1 | | 6.0.0 | 6.1.0 | +| 06/2007 | CT#36 | | | | Upgraded unchanged from Rel-6 | 6.1.0 | 7.0.0 | +| 12/2008 | CT#42 | | | | Upgraded unchanged from Rel-7 | 7.0.0 | 8.0.0 | +| 06/2009 | CT#44 | CP-090312 | 0011 | 2 | Amendment for "multimedia Customized Alerting Tone (CAT) service in ITU ISUP/BICC | 8.0.0 | 8.1.0 | +| 06/2009 | CT#44 | CP-090499 | 0013 | 1 | Mobile Service Application Transport | 8.1.0 | 9.0.0 | +| 12/2009 | CT#46 | CP-090801 | 0017 | 2 | Introduction of IMEI IE to Mobile APM for SRVCC Emergency Call | 9.0.0 | 9.1.0 | +| 06/2010 | CT#48 | CP-100267 | 0020 | 1 | ITU amendments for Customized Alerting Tone (CAT) | 9.1.0 | 9.2.0 | +| 06/2010 | CT#48 | CP-100278 | 0018 | | IPBCP version | 9.1.0 | 9.2.0 | +| 03/2011 | CT#51 | CP-110041 | 0027 | 1 | Correcting non-specific external references | 9.2.0 | 9.3.0 | +| 03/2011 | CT#51 | CP-110081 | 0021 | 1 | Introduction of LCLS Application to Mobile Service Application Transport | 9.3.0 | 10.0.0 | +| 06/2011 | CT#52 | CP-110376 | 0028 | | Miscellaneous corrections | 10.0.0 | 10.1.0 | +| 09/2011 | CT#53 | CP-110571 | 0034 | | Indication of LCLS Negotiation type | 10.1.0 | 10.2.0 | +| 12/2011 | CT#54 | CP-110799 | 0036 | 1 | Correction to Procedures for Indication of LCLS Capability | 10.2.0 | 10.3.0 | +| 12/2011 | CT#54 | CP-110799 | 0037 | 2 | Correction to Procedures for Backward LCLS Negotiation | 10.2.0 | 10.3.0 | +| 12/2011 | CT#54 | CP-110799 | 0038 | 1 | Correction to Procedures for LCLS in Answer message | 10.2.0 | 10.3.0 | +| 12/2011 | CT#54 | CP-110799 | 0039 | 2 | Correction to Procedures for LCLS Negotiation Change | 10.2.0 | 10.3.0 | +| 12/2011 | CT#54 | CP-110799 | 0040 | 1 | Correction to Procedures for LCLS Status Update | 10.2.0 | 10.3.0 | +| 12/2011 | CT#54 | CP-110799 | 0041 | 1 | Correction to Procedures for LCLS Status Change | 10.2.0 | 10.3.0 | +| 12/2011 | CT#54 | CP-110799 | 0043 | 1 | Re-specify Information Elements for LCLS Negotiation and LCLS Negotiation Change | 10.2.0 | 10.3.0 | +| 12/2012 | CT#57 | | | | Upgraded unchanged from Rel-7 | 10.3.0 | 11.0.0 | \ No newline at end of file diff --git a/marked/Rel-11/29_series/29219/5860ad6bd2a2dd8d1ab12864b8f90f37_img.jpg b/marked/Rel-11/29_series/29219/5860ad6bd2a2dd8d1ab12864b8f90f37_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..512d767f948b783c2b8d8d7e2ba05c642d285c66 --- /dev/null +++ b/marked/Rel-11/29_series/29219/5860ad6bd2a2dd8d1ab12864b8f90f37_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:dff29f53fa334ce1ffea0650a21d4a9d0187df0d1fe36607b35f5a697da18b26 +size 82020 diff --git a/marked/Rel-11/29_series/29219/b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg b/marked/Rel-11/29_series/29219/b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7971e75be18877a1c892e276d5e4d8f075352756 --- /dev/null +++ b/marked/Rel-11/29_series/29219/b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:27d6116c733f2c1b46a005db5a614aa1190d436b35c1b8758d7d7dba57510cd7 +size 79979 diff --git a/marked/Rel-11/29_series/29219/raw.md b/marked/Rel-11/29_series/29219/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..471eddf9c085d4cc2e12e0c8d92413c9abd5e22c --- /dev/null +++ b/marked/Rel-11/29_series/29219/raw.md @@ -0,0 +1,755 @@ + + + + +Error! No +text of + +Error! No text of specified style in +document. + +# Contents + +| | | +|--------------------------------------------------------------------|----| +| Foreword ..... | 5 | +| 1 Scope..... | 6 | +| 2 References..... | 6 | +| 3 Definitions and abbreviations ..... | 7 | +| 3.1 Definitions..... | 7 | +| 3.2 Abbreviations ..... | 7 | +| 4 Sy reference point ..... | 7 | +| 4.1 Overview ..... | 7 | +| 4.2 Sy Reference model ..... | 8 | +| 4.3 Subscriber Spending Limits ..... | 9 | +| 4.4 Functional elements..... | 10 | +| 4.4.1 PCRF ..... | 10 | +| 4.4.2 OCS ..... | 10 | +| 4.5 Spending Limits procedures over Sy reference point ..... | 10 | +| 4.5.1 Initial/Intermediate Spending Limit Report Request..... | 10 | +| 4.5.1.1 General..... | 10 | +| 4.5.1.2 Detailed behaviour of the PCRF ..... | 11 | +| 4.5.1.3 The behaviour of the OCS ..... | 11 | +| 4.5.2 Spending Limit Report ..... | 12 | +| 4.5.2.1 General..... | 12 | +| 4.5.2.2 The behaviour of the OCS ..... | 13 | +| 4.5.2.3 Detailed behaviour of the PCRF ..... | 13 | +| 4.5.3 Final Spending Limit Report Request ..... | 13 | +| 4.5.3.1 General..... | 13 | +| 4.5.3.2 Detailed behaviour of the PCRF ..... | 13 | +| 4.5.3.3 The behaviour of the OCS ..... | 14 | +| 5 Sy protocol..... | 14 | +| 5.1 Protocol support ..... | 14 | +| 5.1.1 Use of Diameter base protocol ..... | 14 | +| 5.1.2 Void..... | 14 | +| 5.1.3 Accounting functionality ..... | 14 | +| 5.1.4 Transport protocol ..... | 14 | +| 5.1.5 Advertising Application Support..... | 14 | +| 5.1.6 Use of the Supported-Features AVP ..... | 15 | +| 5.2 Initialization and maintenance of connection and session ..... | 15 | +| 5.3 Sy specific AVPs..... | 15 | +| 5.3.1 Policy-Counter-Identifier AVP ..... | 16 | +| 5.3.2 Policy-Counter-Status AVP..... | 16 | +| 5.3.3 Policy-Counter-Status-Report AVP ..... | 16 | +| 5.3.4 SL-Request-Type AVP..... | 16 | +| 5.3.5 Pending-Policy-Counter-Information AVP ..... | 17 | +| 5.3.6 Pending-Policy-Counter-Change-Time AVP ..... | 17 | +| 5.4 Sy re-used AVPs ..... | 17 | +| 5.5 Sy specific Experimental-Result-Code AVP values ..... | 17 | +| 5.5.1 General ..... | 17 | +| 5.5.2 Permanent Failures ..... | 17 | +| 5.5.3 Transient Failures ..... | 18 | +| 5.6 Sy Messages ..... | 18 | +| 5.6.1 Command-Code Values..... | 18 | +| 5.6.2 Spending-Limit-Request (SLR) command..... | 18 | +| 5.6.3 Spending-Limit-Answer (SLA) command ..... | 19 | +| 5.6.4 Spending-Status-Notification-Request (SNR) command..... | 19 | +| 5.6.5 Spending-Status-Notification-Answer (SNA) command ..... | 19 | +| 5.6.6 Session-Termination-Request (STR) command..... | 20 | +| 5.6.7 Session-Termination-Answer (STA) command ..... | 20 | + +Annex A (informative): Change history................................................................................................ 21 + +# --- Foreword + +This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +# --- 1 Scope + +The present document provides the stage 3 specification of the Sy reference point for the present release. The functional requirements and the stage 2 specifications of the Sy reference point are contained in TS 23.203 [2]. The Sy reference point lies between the Policy and Charging Rule Function (PCRF) and the Online Charging System (OCS). The internal OCS functionality for policy counter provision management pertaining to Sy is specified in TS 32.296 [16]. + +# --- 2 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. + - For a specific reference, subsequent revisions do not apply. + - For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. +- [1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications". +- [2] 3GPP TS 23.203: "Policy Control and Charging architecture". +- [3] IETF RFC 3588: "Diameter Base Protocol". +- [4] IETF RFC 4005: "Diameter Network Access Server Application" +- [5] IETF RFC 4006: "Diameter Credit Control Application". +- [6] IETF RFC 5719: "Updated IANA Considerations for Diameter Command Code Allocations" +- [7] IETF RFC 2234: "Augmented BNF for syntax specifications". +- [8] 3GPP TS 29.213: "Policy and charging control signalling flows and Quality of Service (QoS) parameter mapping". +- [9] 3GPP TS 23.335: "User Data Convergence (UDC); Technical realization and information flows; Stage 2". +- [10] 3GPP TS 29.335: "User Data Convergence (UDC); User Data Repository Access Protocol over the Ud interface; Stage 3". +- [11] Void. +- [12] Void. +- [13] IETF RFC 791: "Transmission Control Protocol". +- [14] IETF RFC 4960: "Stream Control Transmission Protocol". +- [15] 3GPP TS 29.229: "Cx and Dx interfaces based on the Diameter protocol". +- [16] 3GPP TS 32.296: "Telecommunication management; charging management; Online Charging System (OCS) applications and interfaces". + +# 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]. + +**policy counter:** A mechanism within the OCS to track spending applicable for a subscriber. + +**policy counter identifier:** A reference to a policy counter in the OCS for a subscriber. + +**policy counter status:** A label whose values are not standardized and that is associated with a policy counter's value relative to the spending limit(s) (the number of possible policy counter status values for a policy counter is one greater than the number of thresholds associated with that policy counter, i.e policy counter status values describe the status around the thresholds). This is used to convey information relating to subscriber spending from OCS to PCRF. Specific labels are configured jointly in OCS and PCRF. + +**spending limit:** A spending limit is the usage limit of a policy counter (e.g. monetary, volume, duration) that a subscriber is allowed to consume. + +**spending limit report:** a notification, containing the current policy counter status generated from the OCS to the PCRF via the Sy reference point. + +## 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]. + +| | | +|------|----------------------------------------------------| +| OCS | Online charging system | +| OFCS | Offline charging system | +| PCEF | Policy and Charging Enforcement Function | +| PCRF | Policy and Charging Rule Function | +| SLA | Spending-Limit-Answer (SL-Answer) | +| SLR | Spending-Limit-Request (SL- Request) | +| SNA | Spending-Status-Notification-Answer (SN-Answer) | +| SNR | Spending-Status-Notification-Request (SN- Request) | +| STA | Session-Termination-Answer (ST-Answer) | +| STR | Session-Termination-Request (ST- Request) | + +# 4 Sy reference point + +## 4.1 Overview + +The Sy reference point is located between the Policy and Charging Rules Function (PCRF) and the Online Charging System (OCS). The Sy reference point enables transfer of policy counter status information relating to subscriber spending from OCS to PCRF and supports the following functions: + +- Request of policy counter status reporting from PCRF to OCS and subscribe to or unsubscribe from spending limit reports (i.e. notifications of policy counter status changes). +- Notification of spending limit reports from OCS to PCRF. +- Cancellation of spending limit reporting from PCRF to OCS. + +Since the Sy reference point resides between the PCRF and OCS in the HPLMN, roaming with home routed or visited access as well as non-roaming scenarios are supported in the same manner. + +The stage 2 level requirements for the Sy reference point are defined in TS 23.203 [2]. + +Signalling flows related to the Sy interface are specified in TS 29.213 [8]. + +## 4.2 Sy Reference model + +The Sy reference point is defined between the PCRF and the OCS. The relationships between the different functional entities involved are depicted in figures 4.2.1 and 4.2.2. + +![Diagram of the Sy reference point at the Policy and Charging Control (PCC) architecture with SPR. The central element is the Policy and Charging Rules Function (PCRF), which is connected to the Subscription Profile Repository (SPR) via the Sp interface, the Application Function (AF) via the Rx interface, the Online Charging System (OCS) via the Sy interface, the Bearer Binding and Event Reporting Function (BBRF) via the Gxx interface, the Traffic Detection Function (TDF) via the Sd interface, and the Policy and Charging Enforcement Function (PCEF) via the Gx interface. The BBRF is located within the AN-Gateway, and the PCEF is located within the Gateway. The OCS is also connected to the Offline Charging System (OFCS) via the Gy and Gz interfaces.](5860ad6bd2a2dd8d1ab12864b8f90f37_img.jpg) + +``` + +graph TD + SPR[Subscription Profile Repository (SPR)] -- Sp --> PCRF[Policy and Charging Rules Function (PCRF)] + AF[Application Function (AF)] -- Rx --> PCRF + PCRF -- Sy --> OCS[Online Charging System (OCS)] + PCRF -- Gxx --> BBRF[Bearer Binding and Event Reporting Function (BBRF)] + PCRF -- Sd --> TDF[Traffic Detection Function (TDF)] + PCRF -- Gx --> PCEF[Policy and Charging Enforcement Function (PCEF)] + BBRF --- AN_Gateway[AN-Gateway] + PCEF --- Gateway[Gateway] + OCS -- Gy --> OFCS[Offline Charging System (OFCS)] + OCS -- Gz --> OFCS + +``` + +Diagram of the Sy reference point at the Policy and Charging Control (PCC) architecture with SPR. The central element is the Policy and Charging Rules Function (PCRF), which is connected to the Subscription Profile Repository (SPR) via the Sp interface, the Application Function (AF) via the Rx interface, the Online Charging System (OCS) via the Sy interface, the Bearer Binding and Event Reporting Function (BBRF) via the Gxx interface, the Traffic Detection Function (TDF) via the Sd interface, and the Policy and Charging Enforcement Function (PCEF) via the Gx interface. The BBRF is located within the AN-Gateway, and the PCEF is located within the Gateway. The OCS is also connected to the Offline Charging System (OFCS) via the Gy and Gz interfaces. + +Figure 4.2.1: Sy reference point at the Policy and Charging Control (PCC) architecture with SPR + +With the UDC-based architecture, as defined in TS 23.335 [9] and applied in TS 23.203 [2], the UDR replaces SPR and the Ud reference point provides access to the subscription data in the UDR. The Ud interface as defined in TS 29.335 [10] is the interface between the PCRF and the UDR. The relationships between the different functional elements are depicted in figure 4.2.2. When UDC architecture is used, SPR and Sp, whenever mentioned in this document, is replaced by UDR and Ud. + +![Diagram of Sy reference point at the Policy and Charging Control (PCC) architecture with UDR. The diagram shows the Policy and Charging Rules Function (PCRF) connected to the User Data Repository (UDR) via the Ud interface, the Application Function (AF) via the Rx interface, the Online Charging System (OCS) via the Sy interface, the Bearer Binding and Event Reporting Function (BBERF) via the Gxx interface, the Traffic Detection Function (TDF) via the Sd interface, and the Policy and Charging Enforcement Function (PCEF) via the Gx interface. The BBERF is located in the AN-Gateway, and the PCEF is located in the Gateway. The OCS is also connected to the Offline Charging System (OFCS) via the Gy and Gz interfaces.](b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg) + +``` + +graph TD + UDR[User Data Repository (UDR)] -- Ud --> PCRF[Policy and Charging Rules Function (PCRF)] + AF[Application Function (AF)] -- Rx --> PCRF + OCS[Online Charging System (OCS)] -- Sy --> PCRF + PCRF -- Gxx --> BBERF[Bearer Binding and Event Reporting Function (BBERF)] + BBERF --- AN_Gateway[AN-Gateway] + PCRF -- Sd --> TDF[Traffic Detection Function (TDF)] + PCRF -- Gx --> PCEF[Policy and Charging Enforcement Function (PCEF)] + PCEF --- Gateway[Gateway] + OCS -- Gy --> OFCS[Offline Charging System (OFCS)] + OCS -- Gz --> OFCS + +``` + +Diagram of Sy reference point at the Policy and Charging Control (PCC) architecture with UDR. The diagram shows the Policy and Charging Rules Function (PCRF) connected to the User Data Repository (UDR) via the Ud interface, the Application Function (AF) via the Rx interface, the Online Charging System (OCS) via the Sy interface, the Bearer Binding and Event Reporting Function (BBERF) via the Gxx interface, the Traffic Detection Function (TDF) via the Sd interface, and the Policy and Charging Enforcement Function (PCEF) via the Gx interface. The BBERF is located in the AN-Gateway, and the PCEF is located in the Gateway. The OCS is also connected to the Offline Charging System (OFCS) via the Gy and Gz interfaces. + +**Figure 4.2.2: Sy reference point at the Policy and Charging Control (PCC) architecture with UDR** + +NOTE 1: The details associated with the Sp reference point are not specified in this Release. The SPR's relation to existing subscriber databases is not specified in this Release. + +NOTE 2: The UDC Application Informational Model related to the PCRF is not specified in this Release. + +NOTE 3: PCEF is located in the Gateway node implementing the IP access to the PDN. Refer to annexes of TS 23.203 [2] for application to specific IP-CAN types. + +NOTE 4: Refer to annexes A.5 and H.2 of TS 23.203 [2] for application of AN-Gateways. + +## 4.3 Subscriber Spending Limits + +Policy decisions based on spending limits is a function that allows the PCRF to make policy decisions based on the status of policy counters that are maintained in the OCS. The PCRF uses the policy counter statuses received from the OCS as input to its policy decisions, e.g. downgrade the QoS (e.g. APN-AMBR) or modify the PCC/QoS/ADC Rules. + +When the status of policy counters is first required to make a policy decision for a subscriber, the PCRF uses the Initial Spending Limit Report Request procedure. The PCRF may request specific or all policy counter statuses to be reported by the OCS for the user. The OCS provides the status to the PCRF of the requested policy counters, and will notify the PCRF of any changes in the status of those policy counters. Optionally, the OCS can provide one or more pending statuses for a requested policy counter with the times that have to be applied. The pending status of a policy counter shall autonomously become the current status of a policy counter at the PCRF when the indicated corresponding time is reached. Subsequently, the provided information for pending statuses of a policy counter shall overwrite the previously received information. + +NOTE 1: The mechanism for provisioning the policy counters in the OCS is out of scope of this document. + +NOTE 2: A policy counter in the OCS can represent the spending for one or more services, one or more devices, one or more subscribers, etc. The representation is operator dependent. There is no explicit relationship between Charging-Key and policy counter. + +The PCRF may request reporting for specific policy counter(s) that it is not currently subscribed and/or cancel reporting for specific policy counter status(es) using the Intermediate Spending Limit Report Request. The PCRF may cancel spending limit reporting for all policy counter(s) using the Final Spending Limit Report Request. + +The updated subscriber profile may also trigger the PCRF sending the Initial/Intermediate/Final Spending Limit Report Request to the OCS to subscribe and/or cancel reporting for policy counter status(es). If spending limit reporting for a policy counter is enabled, the OCS shall notify the PCRF of changes in the status of this policy counter (e.g. daily spending limit of \$2 reached) and optionally pending statuses of this policy counter with the activation time (e.g. due to a billing period that will expire at midnight). + +## 4.4 Functional elements + +### 4.4.1 PCRF + +The Policy Control and Charging Rules Function (PCRF) is a functional element that encompasses policy control decision and flow based charging control functionalities. + +The PCRF may take information on the subscriber's spending status into account in its policy decisions. The PCRF may request spending limit reporting for policy counters from the OCS using the Initial or Intermediate Spending Limit Report Request procedure as specified in clause 4.5.1. The PCRF may cancel spending limit reporting for specific policy counter(s) using the Intermediate Spending Limit Report Request procedure, or for all policy counter(s) using the Final Spending Limit Report Request procedure as specified in clause 4.5.3. + +The PCRF shall have at least one active IP-CAN session to be able to initiate an Sy session to be used when required for spending limit reporting for that subscriber. The PCRF shall terminate the Sy session when the last IP-CAN session for that subscriber is terminated or no IP-CAN session for the same user depends on the spending status information provided over Sy reference point. + +The PCRF may use the status of each relevant policy counter as input to its policy decision as required by the decision logic. + +### 4.4.2 OCS + +The Online Charging System (OCS), for the purpose of policy decisions based on the subscriber's spending, shall + +- maintain the policy counter statuses applicable for a subscriber +- report the policy counter status values for the subscriber when requested to the PCRF +- when a policy counter status changes, report the change to the PCRF + +## 4.5 Spending Limits procedures over Sy reference point + +### 4.5.1 Initial/Intermediate Spending Limit Report Request + +#### 4.5.1.1 General + +This procedure shall be used by the PCRF to request the status of policy counters available at the OCS, and to subscribe or unsubscribe to updates of policy counters by the OCS. + +This procedure is mapped to the Spending-Limit-Request/Answer commands specified in section 5.6. + +**Table 4.5.1.1/1: Initial/Intermediate Spending Limit Report Request** + +| Information element name | Mapping to Diameter AVP | Cat. | Description | +|-------------------------------------------|---------------------------|------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| User Identity | Subscription-Id | C | This IE shall contain the identity of the user. It shall be present in the initial request when the SL-Request-Type=INITIAL_REQUEST. | +| Request Type | SL-Request-Type | M | This IE shall indicate whether this is the initial or a subsequent request for the user. | +| Subscribed Policy Counter Identifier List | Policy-Counter-Identifier | O | This IE shall indicate the list of policy counter identifiers to be subscribed to. In the intermediate spending limit report request procedure, this list overrides a previously provisioned list. If omitted in either the Initial or Intermediate Spending Limit Report Request procedures the PCRF requests subscription to all available policy counters. | + +**Table 4.5.1.1/2: Initial/Intermediate Spending Limit Report Response** + +| Information element name | Mapping to Diameter AVP | Cat. | Description | +|------------------------------|------------------------------------|------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Policy Counter Status Report | Policy-Counter-Status-Report | O | If present, this information element shall contain a policy counter identifier, the current status value and if applicable pending policy counter statuses with the activation times. | +| Result | Result-Code or Experimental-Result | M | This IE shall contain the result of the operation. | + +#### 4.5.1.2 Detailed behaviour of the PCRF + +The PCRF shall make use of this procedure when it determines for a subscriber that + +- The status of policy counter(s) to which the PCRF does not have an existing subscription for status change notifications is/are required. +- The status of one or more, but not all, policy counter(s) to which the PCRF has an existing subscription for status change notifications are no longer required. + +NOTE: The Final Spending Limit Request procedure in clause 4.5.3 is used to remove all subscriptions. + +In the initial request, i.e. when the request is sent for the first time for the Subscriber, the PCRF shall set the SL-Request-Type AVP to the value INITIAL\_REQUEST (0). For subsequent requests for the same Subscriber, the PCRF shall set the SL-Request-Type AVP to INTERMEDIATE\_REQUEST (1). + +For each policy counter that the PCRF requires the current status and notifications of future status changes, the PCRF shall indicate the concerned policy counter identifiers in the request. Alternatively, the policy counter identifiers may be omitted if the PCRF requires the current status and notifications of future status changes of all available policy counters. + +#### 4.5.1.3 The behaviour of the OCS + +Upon reception of the request from the PCRF, the OCS shall check if there is an ongoing Sy session associated with the received Session-Id AVP. If there is no Sy session and the SL-Request-Type AVP is set to INITIAL\_REQUEST (0), an Sy session is created on the OCS. If there is an Sy session and the SL-Request-Type AVP is not set to INTERMEDIATE\_REQUEST (1), the OCS shall return a response with the Result-Code set to DIAMETER\_INVALID\_AVP\_VALUE and with the Failed-AVP AVP containing the SL-Request-Type AVP. If there is no Sy session and the SL-Request-Type AVP is not set to INITIAL\_REQUEST (0), the OCS shall return a response with the Result-Code AVP set to DIAMETER\_UNKNOWN\_SESSION\_ID. + +Upon reception of the request from the PCRF provided with explicit Policy Counter Identifier(s): + +If all the policy counter identifiers are known to the OCS, the OCS shall be able to subsequently notify the PCRF of any policy counter state changes and/or additions, removals or changes of pending policy counter statuses along with their activation time. + +If a policy counter identifier is known by the OCS, but is not applicable to the subscriber (e.g. not provisioned), the OCS may use an operator configured policy counter status to indicate this to the PCRF. + +If the OCS is configured to accept the request provided with unknown policy counter identifier(s) , and if the OCS determines that one or more policy counter identifiers are unknown, an operator configured policy counter status may be used to indicate the policy counter identifier(s) determined as unknown by OCS. The status of known policy counter identifier(s) shall be returned to the PCRF in the same procedure in this case. + +Alternatively, if the OCS is configured to reject the request provided with unknown policy counter identifier(s), and if the OCS determines that one or more policy counter identifiers are unknown, the OCS shall return a response with the Experimental-Result-Code AVP set to DIAMETER\_ERROR\_UNKNOWN\_POLICY\_COUNTERS and with the Failed-AVP AVP indicating the unknown policy counter identifiers. When this failure occurs, if the SL-Request-Type AVP is set to: + +- INITIAL\_REQUEST (0), then the Sy session is not created. +- INTERMEDIATE\_REQUEST (1), then none of the changes in the request take effect but the Sy session is maintained. + +NOTE 1: In order to avoid misbehaviors due to the policy counters maintained in the Sy session, the PCRF can terminate the Sy session invoking the Final Spending Limit Request procedure in clause 4.5.3. + +When the PCRF provides a new subscribed policy counter identifier list, the OCS shall remove any policy counter identifiers no longer in the list from association with the Sy session such that the OCS will no longer notify the PCRF of those policy counter state changes. + +If an initial or intermediate request contains no policy counter identifiers, the OCS shall subsequently notify the PCRF of all available policy counter state changes and optionally the pending policy counter statuses with the activation times. If the OCS has no available policy counters for that subscriber during the Initial or Intermediate Spending Limit Report Request procedure, it sets the Experimental-Result-Code to DIAMETER\_ERROR\_NO\_AVAILABLE\_POLICY\_COUNTERS. When this failure occurs, if the SL-Request-Type AVP is set to: + +- INITIAL\_REQUEST (0), then the Sy session is not created. +- INTERMEDIATE\_REQUEST (1), then none of the changes in the request take effect but the Sy session is maintained. + +NOTE 2: The PCRF can terminate the Sy session invoking the Final Spending Limit Request procedure in clause 4.5.3, or maintain the Sy session assuming that further available policy counters will be notified. + +If the user identified in an initial request is not known to the OCS, the OCS shall reject the Spending Limit Report Request by including the result code of DIAMETER\_USER\_UNKNOWN in the Spending Limit Report Answer. In this case, the Sy session is not created. + +Upon successful creation of an Sy session, the OCS shall include the current status of all subscribed policy counters (if any) in the response and set the Result-Code to DIAMETER\_SUCCESS. + +### 4.5.2 Spending Limit Report + +#### 4.5.2.1 General + +This procedure shall be used by the OCS to notify the PCRF of changes in the status of subscribed policy counter(s). + +This procedure is mapped to the Spending-Status-Notification-Request / Answer commands specified commands specified in section 5.6. + +**Table 4.5.2.1/1: Spending Limit Report Request** + +| Information element name | Mapping to Diameter AVP | Cat. | Description | +|------------------------------|------------------------------|------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Policy Counter Status Report | Policy-Counter-Status-Report | M | If present, this information element shall contain a policy counter identifier, the current status value and if applicable pending policy counter statuses with the activation times. | + +**Table 4.5.2.1/2: Spending Limit Report Response** + +| Information element name | Mapping to Diameter AVP | Cat. | Description | +|--------------------------|------------------------------------|------|----------------------------------------------------| +| Result | Result-Code or Experimental-Result | M | This IE shall contain the result of the operation. | + +#### 4.5.2.2 The behaviour of the OCS + +When the status of a specific policy counter changes or when pending statuses associated with the policy counter are added, removed or changed, the OCS shall determine the Sy sessions impacted by the change (i.e. those Sy sessions that have subscribed to status change notifications for the changed policy counter) and send a Spending Limit Report request including the current policy counter status, and if applicable pending policy counter statuses with the activation times to the PCRF associated with each affected Sy session. + +If several policy counters change status at the same time, the OCS may group the status change notifications into a single Spending Limit Report request to the PCRF by sending multiple Policy-Counter-Status-Report AVPs in the request. + +#### 4.5.2.3 Detailed behaviour of the PCRF + +The PCRF shall acknowledge the request by sending a response with a Result-Code AVP set to DIAMETER\_SUCCESS and use the status of the received policy counter(s) as input to its policy decision to apply operator defined actions, e.g. downgrade the QoS. + +The PCRF shall ignore an unknown policy counter status report for all unknown policy counter identifiers in an SLA or in an SNR from the OCS. + +If the PCRF receives a Policy-Counter-Status-Report with one or more Pending-Policy-Counter-Information AVPs, then at the time defined by the Pending-Policy-Counter-Change-Time AVP, the pending Policy-Counter-Status shall autonomously become the current status of a policy counter. Subsequently provided information for pending statuses of a policy counter shall overwrite the previously received information. If the pending policy counter statuses are applicable to a policy counter identifier but the Pending-Policy-Counter-Information AVPs are omitted in the new policy counter status report, the PCRF shall remove all the pending policy counter statuses. + +### 4.5.3 Final Spending Limit Report Request + +#### 4.5.3.1 General + +This procedure shall be used by the PCRF to unsubscribe to any future updates of policy counters for a given subscriber by the OCS. + +This procedure is mapped to the Session-Termination-Request/Answer commands specified in RFC3588 [3]. + +**Table 4.5.3.1/1: Final Spending Limit Report Request** + +| Information element name | Mapping to Diameter AVP | Cat. | Description | +|--------------------------|-------------------------|------|--------------------------------------------------------------------------------------------------------| +| Termination Cause | Termination-Cause | M | This IE shall contain the reason why the session was terminated. It shall be set to "DIAMETER_LOGOUT". | + +**Table 4.5.3.1/2: Final Spending Limit Report Response** + +| Information element name | Mapping to Diameter AVP | Cat. | Description | +|--------------------------|-------------------------|------|----------------------------------------------------| +| Result | Result-Code | M | This IE shall contain the result of the operation. | + +#### 4.5.3.2 Detailed behaviour of the PCRF + +When the PCRF decides that policy decisions for a given user no longer depend on policy counter(s) to which the PCRF has existing subscriptions for status change notifications, the PCRF shall send the Final Spending Limit Report Request to the OCS. + +#### 4.5.3.3 The behaviour of the OCS + +Upon reception of the request from the PCRF, the OCS shall check that there is an ongoing Sy session associated with the received Session-Id AVP. If there is no Sy session, the OCS shall return a response with the Result-Code AVP set to DIAMETER\_UNKNOWN\_SESSION\_ID. + +The OCS shall remove all policy counter subscriptions associated with the Sy session such that the OCS will no longer notify the PCRF of policy counter state changes and close the session by returning a response with the Result-Code AVP set to DIAMETER\_SUCCESS. + +# --- 5 Sy protocol + +## 5.1 Protocol support + +### 5.1.1 Use of Diameter base protocol + +The Diameter Base Protocol as specified in IETF RFC 3588 [3] shall apply except as modified by the defined support of the methods and the defined support of the commands and AVPs, result and error codes as specified in this specification. Unless otherwise specified, the procedures (including error handling and unrecognised information handling) shall be used unmodified. + +With regard to the Diameter protocol defined over the Sy interface, the OCS acts as a Diameter server, in the sense that it is the network element that handles policy counter status requests for a particular realm. The PCRF acts as the Diameter client, in the sense that it is the network element requesting policy counter status to the OCS. + +A Diameter routing table entry can have a different destination based on the application identifier of the command. The application identifier stored in the command header must match the value of any application identifier AVPs in the command body. Diameter agents (relay, proxy, redirection, translation agents) should use the application identifier in the command header to route to a suitable destination. + +### 5.1.2 Void + +### 5.1.3 Accounting functionality + +Accounting functionality (Accounting Session State Machine, related command codes and AVPs) shall not be used on the Sy interface. + +### 5.1.4 Transport protocol + +Diameter messages over the Sy interface shall make use of TCP IETF RFC 791 [13] or SCTP IETF RFC 4960 [14]. + +### 5.1.5 Advertising Application Support + +The Diameter application identifier assigned to the Sy interface application is 16777302. + +The PCRF and OCS shall advertise support of the Diameter Sy Application by including the value of the Sy application identifier in the Auth-Application-Id AVP within the Vendor-Specific-Application-Id grouped AVP of the Capabilities-Exchange-Request and Capabilities-Exchange-Answer commands. + +The vendor identifier value of 3GPP (10415) shall be included in the Supported-Vendor-Id AVP of the Capabilities-Exchange-Request and Capabilities-Exchange-Answer commands, and in the Vendor-Id AVP within the Vendor-Specific-Application-Id grouped AVP of the Capabilities-Exchange-Request and Capabilities-Exchange-Answer commands. + +The Vendor-Id AVP included in Capabilities-Exchange-Request and Capabilities-Exchange-Answer commands that is not included in the Vendor-Specific-Application-Id AVPs as described above shall indicate the manufacturer of the Diameter node as per RFC 3588 [3]. + +### 5.1.6 Use of the Supported-Features AVP + +The Supported-Features AVP is used during session establishment to inform the destination host about the required and optional features that the origin host supports. The client shall, in the first request in a Diameter session indicate the set of supported features. The server shall, in the first answer within the Diameter session indicate the set of features that it has in common with the client and that the server shall support within the same Diameter session. Any further command messages shall always be compliant with the list of supported features indicated in the Supported-Features AVPs during session establishment. Features that are not advertised as supported shall not be used to construct the command messages for that Diameter session. Unless otherwise stated, the use of the Supported-Features AVP on the Sy reference point shall be compliant with the requirements for dynamic discovery of supported features and associated error handling on the Cx reference point as defined in clause 7.2.1 of TS 29.229 [15]. + +The base functionality for the Sy reference point is the 3GPP Rel-11 standard and a feature is an extension to that functionality. If the origin host does not support any features beyond the base functionality, the Supported-Features AVP may be absent from the Sy commands. As defined in clause 7.1.1 of TS 29.229 [15], when extending the application by adding new AVPs for a feature, the new AVPs shall have the M bit cleared and the AVP shall not be defined mandatory in the command ABNF. + +As defined in TS 29.229 [15], the Supported-Features AVP is of type grouped and contains the Vendor-Id, Feature-List-ID and Feature-List AVPs. On the Sy reference point, the Supported-Features AVP is used to identify features that have been defined by 3GPP and hence, for features defined in this document, the Vendor-Id AVP shall contain the vendor ID of 3GPP (10415). If there are multiple feature lists defined for the Sy reference point, the Feature-List-ID AVP shall differentiate those lists from one another. + +On receiving an initial request application message, the destination host shall act as defined in clause 7.2.1 of TS 29.229 [15]. The following exceptions apply to the initial SLR/SLA command pair: + +- If the PCRF supports post-Rel-11 Sy, the SLR shall include the features supported by the PCRF within Supported-Features AVP(s) with the 'M' bit cleared. + +NOTE: One instance of Supported-Features AVP is needed per Feature-List-ID. + +- If the SLR command does not contain any Supported-Features AVP(s) and the OCS supports Rel-11 Sy functionality, the OCS shall not include the Supported-Features AVP in the SLA command. In this case, both PCRF and OCS shall behave as specified in the Rel-11 version of this document. + +Once the PCRF and OCS have negotiated the set of supported features during session establishment, the set of common features shall be used during the lifetime of the Diameter session. + +## 5.2 Initialization and maintenance of connection and session + +The Diameter protocol between the PCRF and the OCS, shall always keep the session state, and use the same Session-Id parameter for the lifetime of each Diameter session. + +Each Diameter session shall identify a Sy session for a given user. In order to indicate that the session state is to be maintained, the Diameter client and server shall not include the Auth-Session-State AVP, either in the request or in the response messages (see IETF RFC 3588 [3]). + +The PCRF shall link the Gx session(s) or S9 session with the Sy session at Sy session initialization and maintain that until the IP-CAN session(s) for that subscriber are terminated or no IP-CAN session for the same user depends on the spending status information provided over Sy reference point. + +## 5.3 Sy specific AVPs + +Table 5.3.1 describes the Diameter AVPs defined for the Sy reference point, their AVP Code values, types and possible flag values. The Vendor-Id header of all AVPs defined in the present document shall be set to 3GPP (10415). + +**Table 5.3.1: Sy specific Diameter AVPs** + +| Attribute Name | AVP Code | Clause defined | Value Type | AVP Flag rules (note 1) | | | | +|------------------------------------|----------|----------------|------------|-------------------------|-----|------------|----------| +| | | | | Must | May | Should not | Must not | +| Policy-Counter-Identifier | 2901 | 5.3.1 | UTF8String | M,V | P | | | +| Policy-Counter-Status | 2902 | 5.3.2 | UTF8String | M,V | P | | | +| Policy-Counter-Status-Report | 2903 | 5.3.3 | Grouped | M,V | P | | | +| SL-Request-Type | 2904 | 5.3.4 | Enumerated | M,V | P | | | +| Pending-Policy-Counter-Information | 2905 | 5.3.5 | Grouped | M,V | P | | | +| Pending-Policy-Counter-Change-Time | 2906 | 5.3.6 | Time | M,V | P | | | + +NOTE 1: The AVP header bit denoted as 'M', indicates whether support of the AVP is required. The AVP header bit denoted as 'V', indicates whether the optional Vendor-ID field is present in the AVP header. For further details, see RFC 3588 [3]. + +### 5.3.1 Policy-Counter-Identifier AVP + +The Policy-Counter-Identifier AVP (AVP code 2901) is of type UTF8String, and it uniquely identifies a policy counter that is maintained per subscriber within the OCS. + +### 5.3.2 Policy-Counter-Status AVP + +The Policy-Counter-Status AVP (AVP code 2902) is of type UTF8String, and identifies the policy counter status applicable for a specific policy counter and subscriber. + +NOTE: The valid values for the Policy-Counter-Status AVP are specific for each Policy-Counter-Identifier value. + +### 5.3.3 Policy-Counter-Status-Report AVP + +The Policy-Counter-Status-Report AVP (AVP code 2903) is of type Grouped. It is used by the OCS to report the status of a specific policy counter. + +Associated pending policy counter statuses shall always be provided within Pending-Policy-Counter-Information AVPs if the pending policy counter statuses are applicable to the policy counter identifier. If there are no Pending-Policy-Counter-Information AVPs provided within the Policy-Counter-Status-Report AVP, previously provided pending counter statuses are removed. In addition, newly provided pending policy counter statuses overwrite previously provided ones. + +AVP Format: + +``` +Policy-Counter-Status-Report ::= < AVP Header: 2903 > + { Policy-Counter-Identifier } + { Policy-Counter-Status } + *[ Pending-Policy-Counter-Information ] + *[ AVP ] +``` + +### 5.3.4 SL-Request-Type AVP + +The SL-Request-Type AVP (AVP code 2904) is of type Enumerated, and informs the OCS whether the SLR command is being sent as part of the initial or intermediate spending limit report request procedure. + +The following values are defined: + +INITIAL\_REQUEST (0) + +This value indicates that this is the first request in the Diameter session. + +INTERMEDIATE\_REQUEST (1) + +This value indicates that this is the second or subsequent request in the Diameter session. + +### 5.3.5 Pending-Policy-Counter-Information AVP + +The Pending-Policy-Counter-Information AVP (AVP code 2905) is of type Grouped, which contains the pending policy counter status and the active time. If multiple pending policy counter AVPs are included, they shall be sorted in order of change time. + +AVP Format: + +``` +Pending-Policy-Counter-Information ::= < AVP Header: 2905 > + { Policy-Counter-Status } + { Pending-Policy-Counter-Change-Time } + *[ AVP ] +``` + +NOTE: The valid values for the Pending-Policy-Counter-Information AVP are specific for each Policy-Counter-Identifier value. + +### 5.3.6 Pending-Policy-Counter-Change-Time AVP + +The Pending-Policy-Counter-Change-Time AVP (AVP code 2906) is of type Time. This value indicates the NTP time at which the pending policy counter status becomes the current status of a policy counter. + +## 5.4 Sy re-used AVPs + +Table 5.4 lists the Diameter AVPs re-used by the Sy reference point from existing Diameter Applications, reference to their respective specifications and a short description of their usage within the Sy reference point. Other AVPs from existing Diameter Applications, except for the AVPs from Diameter base protocol, do not need to be supported. The AVPs from Diameter base protocol are not included in table 5.4, but they are re-used for the Sy reference point. Unless otherwise stated, re-used AVPs shall maintain their 'M', 'P' and 'V' flag settings. Where 3GPP Radius VSAs are re-used, unless otherwise stated, they shall be translated to Diameter AVPs as described in RFC 4005 [4] with the exception that the 'M' flag shall be set and the 'P' flag may be set. + +**Table 5.4: Sy re-used Diameter AVPs** + +| Attribute Name | Reference | Description | +|-----------------|-------------------|------------------------------------------------------------| +| Subscription-Id | IETF RFC 4006 [5] | The identification of the subscription (IMSI, MSISDN, etc) | + +## 5.5 Sy specific Experimental-Result-Code AVP values + +### 5.5.1 General + +RFC 3588 [3] specifies the Experimental-Result AVP containing Vendor-ID AVP and Experimental-Result-Code AVP. The Experimental-Result-Code AVP (AVP Code 298) is of type Unsigned32 and contains a vendor-assigned value representing the result of processing a request. The Vendor-ID AVP shall be set to 3GPP (10415). + +### 5.5.2 Permanent Failures + +Errors that fall within the Permanent Failures category shall be used to inform the peer that the request failed, and the request should not be attempted again. + +The Result-Code AVP values defined in Diameter base protocol IETF RFC 3588 [3] are applicable. Also, the following Result-Code AVP value defined in IETF RFC 4006 [5] is applicable: + +DIAMETER\_USER\_UNKNOWN (5030) + +This error shall be used by the OCS to indicate to the PCRF that the end user specified in the request is unknown to the OCS and that the Sy session cannot be created. + +The following specific Sy Experimental-Result-Code value is defined for permanent failures: + +DIAMETER\_ERROR\_UNKNOWN\_POLICY\_COUNTERS (5570) + +This error shall be used by the OCS to indicate to the PCRF that the OCS does not recognize one or more Policy Counters specified in the request, when the OCS is configured to reject the request provided with unknown policy counter identifier(s). + +### 5.5.3 Transient Failures + +Errors that fall within the transient failures category are used to inform a peer that the request could not be satisfied at the time it was received, but may be able to satisfy the request in the future. + +The Result-Code AVP values defined in Diameter base protocol IETF RFC 3588 [3] are applicable. Also the following specific Sy Experimental-Result-Code value is defined for transient failures: + +DIAMETER\_ERROR\_NO\_AVAILABLE\_POLICY\_COUNTERS (4241) + +This error shall be used by the OCS to indicate to the PCRF that the OCS has no available policy counters for the subscriber. + +The PCRF may retry the request based on local configuration or operator policy on receipt of a transient failure. + +## 5.6 Sy Messages + +### 5.6.1 Command-Code Values + +This section defines the Command-Code values for the Sy interface application as allocated by IANA from the vendor-specific namespace defined in IETF RFC 5719 [6]. Every command is defined by means of the ABNF syntax IETF RFC 2234 [7], according to the rules in IETF RFC 3588 [3]. + +The following Command Codes are defined in this specification: + +**Table 5.6.1: Command-Code values for Sy** + +| Command-Name | Abbreviation | Code | Section | +|--------------------------------------|--------------|---------|---------| +| Spending-Limit-Request | SLR | 8388635 | 5.6.2 | +| Spending-Limit-Answer | SLA | 8388635 | 5.6.3 | +| Spending-Status-Notification-Request | SNR | 8388636 | 5.6.4 | +| Spending-Status-Notification-Answer | SNA | 8388636 | 5.6.5 | + +In addition, the Session-Termination-Request and Session-Termination-Answer commands are reused from IETF RFC 3588 [3]. + +For the commands defined in this specification and reused commands, the Application-ID field shall be set to 16777302. + +### 5.6.2 Spending-Limit-Request (SLR) command + +The SLR command, indicated by the Command-Code field set to 8388635 and the 'R' bit set in the Command Flags field, is sent by the PCRF to the OCS as part of the Initial or Intermediate Spending Limit Report Request procedure. + +Message Format: + +``` + ::= + < Session-Id > + { Auth-Application-Id } + { Origin-Host } + { Origin-Realm } + { Destination-Realm } + [ Destination-Host ] + [ Origin-State-Id ] + { SL-Request-Type } + *[ Subscription-Id ] + *[ Policy-Counter-Identifier ] + *[ Proxy-Info ] + *[ Route-Record ] + *[ AVP ] +``` + +NOTE: Multiple instances of the Subscription-Id AVP in the SLR command correspond to multiple types of identifier for the same subscriber, for example IMSI and MSISDN. + +### 5.6.3 Spending-Limit-Answer (SLA) command + +The SLA command, indicated by the Command-Code field set to 8388635 and the 'R' bit cleared in the Command Flags field, is sent by the OCS to the PCRF as part of the Initial or Intermediate Spending Limit Report Request procedure. + +Message Format: + +``` + ::= < Diameter Header: 8388635, PXY > + < Session-Id > + { Auth-Application-Id } + { Origin-Host } + { Origin-Realm } + [ Result-Code ] + [ Experimental-Result ] + * [ Policy-Counter-Status-Report ] + [ Error-Message ] + [ Error-Reporting-Host ] + * [ Failed-AVP ] + [ Origin-State-Id ] + * [ Redirect-Host ] + [ Redirect-Host-Usage ] + [ Redirect-Max-Cache-Time ] + * [ Proxy-Info ] + * [ AVP ] +``` + +### 5.6.4 Spending-Status-Notification-Request (SNR) command + +The SNR command, indicated by the Command-Code field set to 8388636 and the 'R' bit set in the Command Flags field, is sent by the OCS to the PCRF as part of the Spending Limit Report procedure. + +Message Format: + +``` + ::= < Diameter Header: 8388636, REQ, PXY > + < Session-Id > + { Origin-Host } + { Origin-Realm } + { Destination-Realm } + { Destination-Host } + { Auth-Application-Id } + [ Origin-State-Id ] + * [ Policy-Counter-Status-Report ] + * [ Proxy-Info ] + * [ Route-Record ] + * [ AVP ] +``` + +### 5.6.5 Spending-Status-Notification-Answer (SNA) command + +The SNA command, indicated by the Command-Code field set to 8388636 and the 'R' bit cleared in the Command Flags field, is sent by the PCRF to the OCS as part of the Spending Limit Report procedure. + +Message Format: + +``` + ::= < Diameter Header: 8388636, PXY > + < Session-Id > + { Origin-Host } + { Origin-Realm } + [ Result-Code ] + [ Experimental-Result ] + [ Origin-State-Id ] + [ Error-Message ] + [ Error-Reporting-Host ] + * [ Redirect-Host ] + [ Redirect-Host-Usage ] + [ Redirect-Max-Cache-Time ] + * [ Failed-AVP ] + * [ Proxy-Info ] + * [ AVP ] +``` + +### 5.6.6 Session-Termination-Request (STR) command + +The STR command, indicated by the Command-Code field set to 275 and the 'R' bit set in the Command Flags field, is sent by the PCRF to the OCS as part of the Final Spending Limit Report Request procedure. + +Message Format: + +``` + ::= < Diameter Header: 275, REQ, PXY > + < Session-Id > + { Origin-Host } + { Origin-Realm } + { Destination-Realm } + { Auth-Application-Id } + { Termination-Cause } + [ Destination-Host ] + [ Origin-State-Id ] + *[ Proxy-Info ] + *[ Route-Record ] + *[ AVP ] +``` + +### 5.6.7 Session-Termination-Answer (STA) command + +The STA command, indicated by the Command-Code field set to 275 and the 'R' bit cleared in the Command Flags field, is sent by the OCS to the PCRF as part of the Final Spending Limit Report Request procedure. + +Message Format: + +``` + ::= < Diameter Header: 275, PXY > + < Session-Id > + { Origin-Host } + { Origin-Realm } + [ Result-Code ] + [ Error-Message ] + [ Error-Reporting-Host ] + *[ Failed-AVP ] + [ Origin-State-Id ] + *[ Redirect-Host ] + [ Redirect-Host-Usage ] + [ Redirect-Max-Cache-Time ] + *[ Proxy-Info ] + *[ AVP ] +``` + +# Annex A (informative): Change history + +| Change history | | | | | | | | +|----------------|-------|-----------|------|-----|--------------------------------------------------------|--------|--------| +| Date | TSG # | TSG Doc. | CR | Rev | Subject/Comment | Old | New | +| 2012-03 | CP#55 | CP-120083 | - | - | v 11.0.0 was produced by MCC | 2.0.0 | 11.0.0 | +| 2012-06 | CP#56 | CP-120347 | 0002 | 1 | Sy Error Case | 11.0.0 | 11.1.0 | +| 2012-06 | CP#56 | CP-120347 | 0003 | 1 | Sy Corrections | 11.0.0 | 11.1.0 | +| 2012-06 | CP#56 | CP-120347 | 0004 | - | Parameters for Spending Limit Report Request | 11.0.0 | 11.1.0 | +| 2012-06 | CP#56 | CP-120347 | 0005 | - | Command Code for SLR & SLA (R11 29.219) | 11.0.0 | 11.1.0 | +| 2012-09 | CP#57 | CP-120536 | 0007 | - | Clean-up for spending limit description | 11.1.0 | 11.2.0 | +| 2012-12 | CP#58 | CP-120832 | 0008 | 1 | Clarification of Supported-Features AVP | 11.2.0 | 11.3.0 | +| 2012-12 | CP#58 | CP-120832 | 0010 | 4 | Addition of values to the Experimental-Result-Code AVP | 11.2.0 | 11.3.0 | +| 2013-03 | CP#59 | CP-130073 | 0013 | 3 | Addition of values to the Experimental-Result-Code AVP | 11.3.0 | 11.4.0 | +| 2013-06 | CP#60 | CP-130323 | 0016 | 1 | Time Based Sy Controls | 11.4.0 | 11.5.0 | +| 2013-12 | CP#62 | CP-130673 | 0017 | 1 | IE name mapping to Diameter AVP missing | 11.5.0 | 11.6.0 | +| 2015-06 | CP#68 | CP-150342 | 0021 | 3 | Notify a pending policy counter status change | 11.6.0 | 11.7.0 | +| 2015-06 | CP#68 | CP-150342 | 0024 | 1 | Correction to pending policy counters status report | 11.6.0 | 11.7.0 | + +| Change history | | | | | | | | +|----------------|---------|-----------|------|-----|-----|-------------------------------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2019-06 | CT#84 | CP-191093 | 0069 | 3 | F | Correction of OCS behaviour for unknown and unavailable Policy Counters | 11.8.0 | \ No newline at end of file diff --git a/marked/Rel-11/29_series/29229/raw.md b/marked/Rel-11/29_series/29229/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..b6a5db0af5b09dd0b5044e836356d9f8205409a1 --- /dev/null +++ b/marked/Rel-11/29_series/29229/raw.md @@ -0,0 +1,1616 @@ + + + + + + +# Contents + +| | | +|----------------------------------------------------------------|----| +| Foreword ..... | 6 | +| 1 Scope..... | 6 | +| 2 References..... | 6 | +| 3 Definitions, symbols and abbreviations..... | 7 | +| 3.1 Definitions..... | 7 | +| 3.2 Abbreviations ..... | 8 | +| 4 General..... | 8 | +| 5 Use of the Diameter base protocol..... | 8 | +| 5.1 Securing Diameter Messages ..... | 8 | +| 5.2 Accounting functionality..... | 8 | +| 5.3 Use of sessions ..... | 8 | +| 5.4 Transport protocol..... | 9 | +| 5.5 Routing considerations..... | 9 | +| 5.6 Advertising Application Support ..... | 9 | +| 6 Diameter application for Cx interface..... | 10 | +| 6.1 Command-Code values ..... | 10 | +| 6.1.1 User-Authorization-Request (UAR) Command..... | 10 | +| 6.1.2 User-Authorization-Answer (UAA) Command ..... | 11 | +| 6.1.3 Server-Assignment-Request (SAR) Command..... | 11 | +| 6.1.4 Server-Assignment-Answer (SAA) Command ..... | 12 | +| 6.1.5 Location-Info-Request (LIR) Command ..... | 12 | +| 6.1.6 Location-Info-Answer (LIA) Command ..... | 13 | +| 6.1.7 Multimedia-Auth-Request (MAR) Command ..... | 13 | +| 6.1.8 Multimedia-Auth-Answer (MAA) Command..... | 13 | +| 6.1.9 Registration-Termination-Request (RTR) Command ..... | 14 | +| 6.1.10 Registration-Termination-Answer (RTA) Command ..... | 14 | +| 6.1.11 Push-Profile-Request (PPR) Command ..... | 15 | +| 6.1.12 Push-Profile-Answer (PPA) Command..... | 15 | +| 6.2 Result-Code AVP values..... | 15 | +| 6.2.1 Success ..... | 16 | +| 6.2.1.1 DIAMETER_FIRST_REGISTRATION (2001) ..... | 16 | +| 6.2.1.2 DIAMETER_SUBSEQUENT_REGISTRATION (2002) ..... | 16 | +| 6.2.1.3 DIAMETER_UNREGISTERED_SERVICE (2003) ..... | 16 | +| 6.2.1.4 DIAMETER_SUCCESS_SERVER_NAME_NOT_STORED (2004) ..... | 16 | +| 6.2.1.5 Void ..... | 16 | +| 6.2.2 Permanent Failures ..... | 16 | +| 6.2.2.1 DIAMETER_ERROR_USER_UNKNOWN (5001) ..... | 16 | +| 6.2.2.2 DIAMETER_ERROR_IDENTITIES_DONT_MATCH (5002) ..... | 16 | +| 6.2.2.3 DIAMETER_ERROR_IDENTITY_NOT_REGISTERED (5003) ..... | 16 | +| 6.2.2.4 DIAMETER_ERROR_ROAMING_NOT_ALLOWED (5004)..... | 17 | +| 6.2.2.5 DIAMETER_ERROR_IDENTITY_ALREADY_REGISTERED (5005)..... | 17 | +| 6.2.2.6 DIAMETER_ERROR_AUTH_SCHEME_NOT_SUPPORTED (5006) ..... | 17 | +| 6.2.2.7 DIAMETER_ERROR_IN_ASSIGNMENT_TYPE (5007)..... | 17 | +| 6.2.2.8 DIAMETER_ERROR_TOO_MUCH_DATA (5008) ..... | 17 | +| 6.2.2.9 DIAMETER_ERROR_NOT_SUPPORTED_USER_DATA (5009) ..... | 17 | +| 6.2.2.10 Void ..... | 17 | +| 6.2.2.11 DIAMETER_ERROR_FEATURE_UNSUPPORTED (5011) ..... | 17 | +| 6.3 AVPs..... | 17 | +| 6.3.1 Visited-Network-Identifier AVP ..... | 19 | +| 6.3.2 Public-Identity AVP ..... | 19 | +| 6.3.3 Server-Name AVP..... | 19 | +| 6.3.4 Server-Capabilities AVP ..... | 19 | +| 6.3.5 Mandatory-Capability AVP..... | 19 | +| 6.3.6 Optional-Capability AVP ..... | 19 | +| 6.3.7 User-Data AVP..... | 20 | + +| | | | +|----------|------------------------------------------------------|----| +| 6.3.8 | SIP-Number-Auth-Items AVP ..... | 20 | +| 6.3.9 | SIP-Authentication-Scheme AVP ..... | 20 | +| 6.3.10 | SIP-Authenticate AVP..... | 20 | +| 6.3.11 | SIP-Authorization AVP..... | 20 | +| 6.3.12 | SIP-Authentication-Context AVP ..... | 20 | +| 6.3.13 | SIP-Auth-Data-Item AVP ..... | 21 | +| 6.3.14 | SIP-Item-Number AVP ..... | 21 | +| 6.3.15 | Server-Assignment-Type AVP..... | 21 | +| 6.3.16 | Deregistration-Reason AVP ..... | 22 | +| 6.3.17 | Reason-Code AVP..... | 22 | +| 6.3.18 | Reason-Info AVP ..... | 23 | +| 6.3.19 | Charging-Information AVP..... | 23 | +| 6.3.20 | Primary-Event-Charging-Function-Name AVP..... | 23 | +| 6.3.21 | Secondary-Event-Charging-Function-Name AVP..... | 23 | +| 6.3.22 | Primary-Charging-Collection-Function-Name AVP..... | 23 | +| 6.3.23 | Secondary-Charging-Collection-Function-Name AVP..... | 23 | +| 6.3.24 | User-Authorization-Type AVP ..... | 24 | +| 6.3.25 | Void ..... | 24 | +| 6.3.26 | User-Data-Already-Available AVP..... | 24 | +| 6.3.27 | Confidentiality-Key AVP..... | 24 | +| 6.3.28 | Integrity-Key AVP ..... | 24 | +| 6.3.29 | Supported-Features AVP..... | 24 | +| 6.3.30 | Feature-List-ID AVP ..... | 25 | +| 6.3.31 | Feature-List AVP..... | 25 | +| 6.3.32 | Supported-Applications AVP..... | 25 | +| 6.3.33 | Associated-Identities AVP ..... | 25 | +| 6.3.34 | Originating-Request AVP ..... | 25 | +| 6.3.35 | Wildcarded-Public-Identity AVP ..... | 26 | +| 6.3.36 | SIP-Digest-Authenticate AVP..... | 26 | +| 6.3.37 | Digest-Realm AVP ..... | 26 | +| 6.3.38 | Void ..... | 26 | +| 6.3.39 | Digest-Algorithm AVP..... | 26 | +| 6.3.40 | Digest-QoP AVP ..... | 26 | +| 6.3.41 | Digest-HA1 AVP..... | 26 | +| 6.3.42 | Line-Identifier AVP..... | 26 | +| 6.3.43 | Wildcarded-IMPU AVP ..... | 26 | +| 6.3.44 | UAR-Flags AVP..... | 26 | +| 6.3.45 | Loose-Route-Indication AVP..... | 27 | +| 6.3.46 | SCSCF-Restoration-Info AVP ..... | 27 | +| 6.3.47 | Path AVP ..... | 27 | +| 6.3.48 | Contact AVP..... | 27 | +| 6.3.49 | Subscription-Info AVP ..... | 27 | +| 6.3.49.1 | Call-ID-SIP-Header AVP ..... | 28 | +| 6.3.49.2 | From-SIP-Header AVP ..... | 28 | +| 6.3.49.3 | To-SIP-Header AVP ..... | 28 | +| 6.3.49.4 | Record-Route AVP ..... | 28 | +| 6.3.50 | Associated-Registered-Identities AVP..... | 28 | +| 6.3.51 | Multiple-Registration-Indication ..... | 28 | +| 6.3.52 | Restoration-Info AVP..... | 28 | +| 6.3.53 | Framed-IP-Address AVP..... | 29 | +| 6.3.54 | Framed-IPv6-Prefix AVP ..... | 29 | +| 6.3.55 | Framed-Interface-Id AVP..... | 29 | +| 6.3.56 | Session-Priority AVP ..... | 29 | +| 6.3.57 | Identity-with-Emergency-Registration AVP..... | 29 | +| 6.3.58 | Privileged-Sender-Indication AVP..... | 29 | +| 6.3.59 | LIA-Flags ..... | 30 | +| 6.4 | Use of namespaces ..... | 30 | +| 6.4.1 | AVP codes ..... | 30 | +| 6.4.2 | Experimental-Result-Code AVP values ..... | 30 | +| 6.4.3 | Command Code values ..... | 30 | +| 6.4.4 | Application-ID value ..... | 30 | + +- 7 Special Requirements..... 31 + - 7.1 Version Control..... 31 + - 7.1.1 Defining a new feature ..... 31 + - 7.1.2 Changing the version of the interface..... 33 + - 7.2 Supported features..... 33 + - 7.2.1 Dynamic discovery of supported features ..... 33 + - 7.3 Interface versions ..... 34 + - 7.3.1 Discovery of supported interface versions ..... 34 +- Annex A (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 defines a transport protocol for use in the IP multimedia (IM) Core Network (CN) subsystem based on Diameter. + +The present document is applicable to: + +- The Cx interface between the I-CSCF/S-CSCF and the HSS. +- The Dx interface between the I-CSCF/S-CSCF and the SLF. + +Whenever it is possible, this document specifies the requirements for this protocol by reference to specifications produced by the IETF within the scope of Diameter. Where this is not possible, extensions to Diameter are defined within this document. + +# --- 2 References + +The following documents contain provisions, which through reference in this text constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. + - For a specific reference, subsequent revisions do not apply. + - For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. +- [1] 3GPP TS 29.228: "IP Multimedia (IM) Subsystem Cx and Dx interface; signalling flows and message contents". +- [2] 3GPP TS 33.210: "3G Security; Network Domain Security; IP Network Layer Security". +- [3] IETF RFC 3261: "SIP: Session Initiation Protocol". +- [4] IETF RFC 2396: "Uniform Resource Identifiers (URI): generic syntax". + +- [5] Void +- [6] IETF RFC 3588: "Diameter Base Protocol". +- [7] IETF RFC 2234: "Augmented BNF for syntax specifications". +- [8] IETF RFC 3966: "The tel URI for Telephone Numbers". +- [9] Void +- [10] Void +- [11] 3GPP TS 29.329: "Sh Interface based on the Diameter protocol; protocol details". +- [12] IETF RFC 3589: "Diameter Command Codes for Third Generation Partnership Project (3GPP) Release 5". +- [13] 3GPP TS 23.003: "Numbering, addressing and identification". +- [14] IETF RFC 2617: "HTTP Authentication: Basic and Digest Access Authentication". +- [15] IETF RFC 4740: "Diameter Session Initiation Protocol (SIP) Application". +- [16] 3GPP TS 29.328: "IP Multimedia (IM) Subsystem Sh interface; Signalling flows and message contents". +- [17] IETF RFC 3327: "Session Initiation Protocol Extension Header Field for Registering Non-Adjacent Contacts". +- [18] 3GPP TS 29.273: "3GPP EPS AAA interfaces". +- [19] IETF RFC 4005: "Diameter Network Access Server Application". +- [20] IETF RFC 4590: " RADIUS Extension for Digest Authentication". +- [21] IETF RFC 4960: "Stream Control Transmission Protocol". +- [22] IETF RFC 3162: "RADIUS and IPv6". + +# --- 3 Definitions, symbols and abbreviations + +## 3.1 Definitions + +Refer to IETF RFC 3588 [6] for the definitions of some terms used in this document. + +For the purposes of the present document, the following terms and definitions apply. + +**Attribute-Value Pair:** see IETF RFC 3588 [6], it corresponds to an Information Element in a Diameter message. + +**Diameter Multimedia client:** a client that implements the Diameter Multimedia application. The client is one of the communicating Diameter peers that usually initiate transactions. Examples in 3GPP are the I-CSCF and S-CSCF. + +**Diameter Multimedia server:** a server that implements the Diameter Multimedia application. A Diameter Multimedia server that also supported the NASREQ and MobileIP applications would be referred to as a Diameter server. An example of a Diameter Multimedia server in 3GPP is the HSS. + +**Registration:** SIP-registration. + +**Server:** SIP-server. + +**User data:** user profile data. + +## 3.2 Abbreviations + +For the purposes of the present document, the following abbreviations apply: + +| | | +|--------|----------------------------------------------| +| AAA | Authentication, Authorization and Accounting | +| ABNF | Augmented Backus-Naur Form | +| AVP | Attribute-Value Pair | +| CN | Core Network | +| CSCF | Call Session Control Function | +| HSS | Home Subscriber Server | +| IANA | Internet Assigned Numbers Authority | +| I-CSCF | Interrogating CSCF | +| IETF | Internet Engineering Task Force | +| IMS | IP Multimedia Subsystem | +| NDS | Network Domain Security | +| RFC | Request For Comments | +| S-CSCF | Serving CSCF | +| SCTP | Stream Control Transport Protocol | +| SIP | Session Initiation Protocol | +| SLF | Server Locator Function | +| UCS | Universal Character Set | +| URL | Uniform Resource Locator | +| UTF | UCS Transformation Formats | + +# --- 4 General + +The Diameter Base Protocol as specified in IETF RFC 3588 [6] shall apply except as modified by the defined support of the methods and the defined support of the commands and AVPs, result and event codes specified in clause 5 of this specification. Unless otherwise specified, the procedures (including error handling and unrecognised information handling) are unmodified. + +# --- 5 Use of the Diameter base protocol + +With the clarifications listed in the following subclauses the Diameter Base Protocol defined by IETF RFC 3588 [6] shall apply. + +## 5.1 Securing Diameter Messages + +For secure transport of Diameter messages, see 3GPP TS 33.210 [2]. + +## 5.2 Accounting functionality + +Accounting functionality (Accounting Session State Machine, related command codes and AVPs) is not used on the Cx interface. + +## 5.3 Use of sessions + +Both between the I-CSCF and the HSS and between the S-CSCF and the HSS, Diameter sessions are implicitly terminated. An implicitly terminated session is one for which the server does not maintain state information. The client does not need to send any re-authorization or session termination requests to the server. + +The Diameter base protocol includes the Auth-Session-State AVP as the mechanism for the implementation of implicitly terminated sessions. + +The client (server) shall include in its requests (responses) the Auth-Session-State AVP set to the value NO\_STATE\_MAINTAINED (1), as described in IETF RFC 3588 [6]. As a consequence, the server does not maintain any state information about this session and the client does not need to send any session termination request. Neither the Authorization-Lifetime AVP nor the Session-Timeout AVP shall be present in requests or responses. + +## 5.4 Transport protocol + +Diameter messages over the Cx and the Dx interfaces shall make use of SCTP IETF RFC 4960 [21]. + +## 5.5 Routing considerations + +This clause specifies the use of the Diameter routing AVPs Destination-Realm and Destination-Host. + +If an I-CSCF or S-CSCF knows the address/name of the HSS for a certain user, both the Destination-Realm and Destination-Host AVPs shall be present in the request. Otherwise, only the Destination-Realm AVP shall be present and the command shall be routed to the next Diameter node, e.g. the SLF or a Diameter Proxy Agent (see 3GPP TS 29.228 [1]), based on the Diameter routing table in the client. + +If the next Diameter node is an SLF, then once the SLF has returned the address or the destination HSS (using Redirect-Host AVP), the redirected request to the HSS shall include both Destination-Realm and Destination-Host AVPs. If the next Diameter node is a Diameter Proxy Agent, the Diameter Proxy Agent shall determine the destination HSS. The Diameter Proxy Agent, based on the result of this determination of the destination HSS, shall modify the Destination-Realm AVP and Destination-Host AVP of the request appropriately. The Diameter Proxy Agent shall then append a Route-Record AVP to the request and shall send the request to the destination HSS. Consequently, the Destination-Host AVP is declared as optional in the ABNF for all requests initiated by an I-CSCF or an S-CSCF. + +If the response is routed back to a Diameter Proxy Agent, the Diameter Proxy Agent shall send the response back to the I-CSCF or S-CSCF without modifying the Origin-Realm AVP and Origin-Host AVP. The response shall contain the Origin-Realm AVP set to the realm of the HSS together with the Origin-Host AVP set to the HSS that sent the response. The S-CSCF shall store the HSS realm and HSS address for each Public Identity, after the first request sent to the User Identity to HSS resolution function. + +Requests initiated by the HSS towards an S-CSCF shall include both Destination-Host and Destination-Realm AVPs. The HSS obtains the Destination-Host AVP to use in requests towards an S-CSCF, from the Origin-Host AVP received in previous requests from the S-CSCF. Consequently, the Destination-Host AVP is declared as mandatory in the ABNF for all requests initiated by the HSS. + +Destination-Realm AVP is declared as mandatory in the ABNF for all requests. + +## 5.6 Advertising Application Support + +The HSS, S-CSCF and I-CSCF shall advertise support of the Diameter Multimedia Application by including the value of the application identifier (see chapter 6) in the Auth-Application-Id AVP within the Vendor-Specific-Application-Id grouped AVP of the Capabilities-Exchange-Request and Capabilities-Exchange-Answer commands. + +The vendor identifier value of 3GPP (10415) and ETSI (13019) shall be included in the Supported-Vendor-Id AVP of the Capabilities-Exchange-Request and Capabilities-Exchange-Answer commands, and in the Vendor-Id AVP within the Vendor-Specific-Application-Id grouped AVP of the Capabilities-Exchange-Request and Capabilities-Exchange-Answer commands. + +Note: The Vendor-Id AVP included in Capabilities-Exchange-Request and Capabilities-Exchange-Answer commands that is not included in the Vendor-Specific-Application-Id AVPs as described above shall indicate the manufacturer of the Diameter node as per RFC 3588 [6]. + +# 6 Diameter application for Cx interface + +This clause specifies a Diameter application that allows a Diameter Multimedia server and a Diameter Multimedia client: + +- to exchange location information +- to authorize a user to access the IMS +- to exchange authentication information +- to download and handle changes in the user data stored in the server + +The Cx interface protocol is defined as an IETF vendor specific Diameter application, where the vendor is 3GPP. The vendor identifier assigned by IANA to 3GPP () is 10415. + +The Diameter application identifier assigned to the Cx/Dx interface application is 16777216 (allocated by IANA). + +## 6.1 Command-Code values + +This section defines Command-Code values for this Diameter application. + +Every command is defined by means of the ABNF syntax IETF RFC 2234 [7], according to the rules in IETF RFC 3588 [6]. Whenever the definition and use of an AVP is not specified in this document, what is stated in IETF RFC 3588 [6] shall apply. + +The command codes for the Cx/Dx interface application are taken from the range allocated by IANA in IETF RFC 3589 [12] as assigned in this specification. For these commands, the Application-ID field shall be set to 16777216 (application identifier of the Cx/Dx interface application, allocated by IANA). + +The following Command Codes are defined in this specification: + +**Table 6.1.1: Command-Code values** + +| Command-Name | Abbreviation | Code | Section | +|----------------------------------|--------------|------|---------| +| User-Authorization-Request | UAR | 300 | 6.1.1 | +| User-Authorization-Answer | UAA | 300 | 6.1.2 | +| Server-Assignment-Request | SAR | 301 | 6.1.3 | +| Server-Assignment-Answer | SAA | 301 | 6.1.4 | +| Location-Info-Request | LIR | 302 | 6.1.5 | +| Location-Info-Answer | LIA | 302 | 6.1.6 | +| Multimedia-Auth-Request | MAR | 303 | 6.1.7 | +| Multimedia-Auth-Answer | MAA | 303 | 6.1.8 | +| Registration-Termination-Request | RTR | 304 | 6.1.9 | +| Registration-Termination-Answer | RTA | 304 | 6.1.10 | +| Push-Profile-Request | PPR | 305 | 6.1.11 | +| Push-Profile-Answer | PPA | 305 | 6.1.12 | + +### 6.1.1 User-Authorization-Request (UAR) Command + +The User-Authorization-Request (UAR) command, indicated by the Command-Code field set to 300 and the 'R' bit set in the Command Flags field, is sent by a Diameter Multimedia client to a Diameter Multimedia server in order to request the authorization of the registration of a multimedia user. + +Message Format + +``` +< User-Authorization-Request > ::= < Diameter Header: 300, REQ, PXY, 16777216 > + < Session-Id > + { Vendor-Specific-Application-Id } + { Auth-Session-State } + { Origin-Host } +``` + +``` + +{ Origin-Realm } +[ Destination-Host ] +{ Destination-Realm } +{ User-Name } +*[ Supported-Features ] +{ Public-Identity } +{ Visited-Network-Identifier } +[ User-Authorization-Type ] +[ UAR-Flags ] +*[ AVP ] +*[ Proxy-Info ] +*[ Route-Record ] + +``` + +### 6.1.2 User-Authorization-Answer (UAA) Command + +The User-Authorization-Answer (UAA) command, indicated by the Command-Code field set to 300 and the 'R' bit cleared in the Command Flags field, is sent by a server in response to the User-Authorization-Request command. The Experimental-Result AVP may contain one of the values defined in section 6.2. + +#### Message Format + +``` + +< User-Authorization-Answer> ::= < Diameter Header: 300, PXY, 16777216 > +< Session-Id > +{ Vendor-Specific-Application-Id } +[ Result-Code ] +[ Experimental-Result ] +{ Auth-Session-State } +{ Origin-Host } +{ Origin-Realm } +*[ Supported-Features ] +[ Server-Name ] +[ Server-Capabilities ] +*[ AVP ] +*[ Failed-AVP ] +*[ Proxy-Info ] +*[ Route-Record ] + +``` + +### 6.1.3 Server-Assignment-Request (SAR) Command + +The Server-Assignment-Request (SAR) command, indicated by the Command-Code field set to 301 and the 'R' bit set in the Command Flags field, is sent by a Diameter Multimedia client to a Diameter Multimedia server in order to request it to store the name of the server that is currently serving the user. + +#### Message Format + +``` + + ::= < Diameter Header: 301, REQ, PXY, 16777216 > +< Session-Id > +{ Vendor-Specific-Application-Id } +{ Auth-Session-State } +{ Origin-Host } +{ Origin-Realm } +[ Destination-Host ] +{ Destination-Realm } +[ User-Name ] +*[ Supported-Features ] +*[ Public-Identity ] +[ Wildcarded-Public-Identity ] +{ Server-Name } +{ Server-Assignment-Type } +{ User-Data-Already-Available } +[ SCSCF-Restoration-Info ] +[ Multiple-Registration-Indication ] +[ Session-Priority ] + +``` + +``` + +*[ AVP ] +*[ Proxy-Info ] +*[ Route-Record ] + +``` + +### 6.1.4 Server-Assignment-Answer (SAA) Command + +The Server-Assignment-Answer (SAA) command, indicated by the Command-Code field set to 301 and the 'R' bit cleared in the Command Flags field, is sent by a server in response to the Server-Assignment-Request command. The Experimental-Result AVP may contain one of the values defined in section 6.2. If Result-Code or Experimental-Result does not inform about an error, the User-Data AVP shall contain the information that the S-CSCF needs to give service to the user. + +#### Message Format + +``` + + ::= < Diameter Header: 301, PXY, 16777216 > + < Session-Id > + { Vendor-Specific-Application-Id } + [ Result-Code ] + [ Experimental-Result ] + { Auth-Session-State } + { Origin-Host } + { Origin-Realm } + [ User-Name ] + *[ Supported-Features ] + [ User-Data ] + [ Charging-Information ] + [ Associated-Identities ] + [ Loose-Route-Indication ] + *[ SCSCF-Restoration-Info ] + [ Associated-Registered-Identities ] + [ Server-Name ] + [ Wildcarded-Public-Identity ] + [ Privileged-Sender-Indication ] + *[ AVP ] + *[ Failed-AVP ] + *[ Proxy-Info ] + *[ Route-Record ] + +``` + +### 6.1.5 Location-Info-Request (LIR) Command + +The Location-Info-Request (LIR) command, indicated by the Command-Code field set to 302 and the 'R' bit set in the Command Flags field, is sent by a Diameter Multimedia client to a Diameter Multimedia server in order to request name of the server that is currently serving the user. + +#### Message Format + +``` + + ::= < Diameter Header: 302, REQ, PXY, 16777216 > + < Session-Id > + { Vendor-Specific-Application-Id } + { Auth-Session-State } + { Origin-Host } + { Origin-Realm } + [ Destination-Host ] + { Destination-Realm } + [ Originating-Request ] + *[ Supported-Features ] + { Public-Identity } + [ User-Authorization-Type ] + [ Session-Priority ] + *[ AVP ] + *[ Proxy-Info ] + *[ Route-Record ] + +``` + +### 6.1.6 Location-Info-Answer (LIA) Command + +The Location-Info-Answer (LIA) command, indicated by the Command-Code field set to 302 and the 'R' bit cleared in the Command Flags field, is sent by a server in response to the Location-Info-Request command. The Experimental-Result AVP may contain one of the values defined in section 6.2. + +#### Message Format + +``` + ::= < Diameter Header: 302, PXY, 16777216 > + < Session-Id > + { Vendor-Specific-Application-Id } + [ Result-Code ] + [ Experimental-Result ] + { Auth-Session-State } + { Origin-Host } + { Origin-Realm } + * [ Supported-Features ] + [ Server-Name ] + [ Server-Capabilities ] + [ Wildcarded-Public-Identity ] + [ LIA-Flags ] + * [ AVP ] + * [ Failed-AVP ] + * [ Proxy-Info ] + * [ Route-Record ] +``` + +### 6.1.7 Multimedia-Auth-Request (MAR) Command + +The Multimedia-Auth-Request (MAR) command, indicated by the Command-Code field set to 303 and the 'R' bit set in the Command Flags field, is sent by a Diameter Multimedia client to a Diameter Multimedia server in order to request security information. + +#### Message Format + +``` +< Multimedia-Auth-Request > ::= < Diameter Header: 303, REQ, PXY, 16777216 > + < Session-Id > + { Vendor-Specific-Application-Id } + { Auth-Session-State } + { Origin-Host } + { Origin-Realm } + { Destination-Realm } + [ Destination-Host ] + { User-Name } + * [ Supported-Features ] + { Public-Identity } + { SIP-Auth-Data-Item } + { SIP-Number-Auth-Items } + { Server-Name } + * [ AVP ] + * [ Proxy-Info ] + * [ Route-Record ] +``` + +### 6.1.8 Multimedia-Auth-Answer (MAA) Command + +The Multimedia-Auth-Answer (MAA) command, indicated by the Command-Code field set to 303 and the 'R' bit cleared in the Command Flags field, is sent by a server in response to the Multimedia-Auth-Request command. The Experimental-Result AVP may contain one of the values defined in section 6.2. + +#### Message Format + +``` +< Multimedia-Auth-Answer > ::= < Diameter Header: 303, PXY, 16777216 > + < Session-Id > + { Vendor-Specific-Application-Id } +``` + +``` + +[ Result-Code ] +[ Experimental-Result ] +{ Auth-Session-State } +{ Origin-Host } +{ Origin-Realm } +[ User-Name ] +*[ Supported-Features ] +[ Public-Identity ] +[ SIP-Number-Auth-Items ] +*[SIP-Auth-Data-Item ] +*[ AVP ] +*[ Failed-AVP ] +*[ Proxy-Info ] +*[ Route-Record ] + +``` + +### 6.1.9 Registration-Termination-Request (RTR) Command + +The Registration-Termination-Request (RTR) command, indicated by the Command-Code field set to 304 and the 'R' bit set in the Command Flags field, is sent by a Diameter Multimedia server to a Diameter Multimedia client in order to request the de-registration of a user. + +Message Format + +``` + + ::= < Diameter Header: 304, REQ, PXY, 16777216 > +< Session-Id > +{ Vendor-Specific-Application-Id } +{ Auth-Session-State } +{ Origin-Host } +{ Origin-Realm } +{ Destination-Host } +{ Destination-Realm } +{ User-Name } +[ Associated-Identities ] +*[ Supported-Features ] +*[ Public-Identity ] +{ Deregistration-Reason } +*[ AVP ] +*[ Proxy-Info ] +*[ Route-Record ] + +``` + +### 6.1.10 Registration-Termination-Answer (RTA) Command + +The Registration-Termination-Answer (RTA) command, indicated by the Command-Code field set to 304 and the 'R' bit cleared in the Command Flags field, is sent by a client in response to the Registration-Termination-Request command. The Experimental-Result AVP may contain one of the values defined in section 6.2. + +Message Format + +``` + + ::= < Diameter Header: 304, PXY, 16777216 > +< Session-Id > +{ Vendor-Specific-Application-Id } +[ Result-Code ] +[ Experimental-Result ] +{ Auth-Session-State } +{ Origin-Host } +{ Origin-Realm } +[ Associated-Identities ] +*[ Supported-Features ] +*[ Identity-with-Emergency-Registration ] +*[ AVP ] +*[ Failed-AVP ] +*[ Proxy-Info ] +*[ Route-Record ] + +``` + +### 6.1.11 Push-Profile-Request (PPR) Command + +The Push-Profile-Request (PPR) command, indicated by the Command-Code field set to 305 and the 'R' bit set in the Command Flags field, is sent by a Diameter Multimedia server to a Diameter Multimedia client in order to update the subscription data and for SIP Digest authentication the authentication data of a multimedia user in the Diameter Multimedia client whenever a modification has occurred in the subscription data or digest password that constitutes the data used by the client. + +#### Message Format + +``` +< Push-Profile-Request > ::= + < Diameter Header: 305, REQ, PXY, 16777216 > + < Session-Id > + { Vendor-Specific-Application-Id } + { Auth-Session-State } + { Origin-Host } + { Origin-Realm } + { Destination-Host } + { Destination-Realm } + { User-Name } + *[ Supported-Features ] + [ User-Data ] + [ Charging-Information ] + [ SIP-Auth-Data-Item ] + *[ AVP ] + *[ Proxy-Info ] + *[ Route-Record ] +``` + +### 6.1.12 Push-Profile-Answer (PPA) Command + +The Push-Profile-Answer (PPA) command, indicated by the Command-Code field set to 305 and the 'R' bit cleared in the Command Flags field, is sent by a client in response to the Push-Profile-Request command. The Experimental-Result AVP may contain one of the values defined in section 6.2. + +#### Message Format + +``` +< Push-Profile-Answer > ::= + < Diameter Header: 305, PXY, 16777216 > + < Session-Id > + { Vendor-Specific-Application-Id } + [Result-Code ] + [ Experimental-Result ] + { Auth-Session-State } + { Origin-Host } + { Origin-Realm } + *[ Supported-Features ] + *[ AVP ] + *[ Failed-AVP ] + *[ Proxy-Info ] + *[ Route-Record ] +``` + +## 6.2 Result-Code AVP values + +This section defines new result code values that must be supported by all Diameter implementations that conform to this specification. When one of the result codes defined here is included in a response, it shall be inside an Experimental-Result AVP and Result-Code AVP shall be absent. + +### 6.2.1 Success + +Result codes that fall within the Success category are used to inform a peer that a request has been successfully completed. + +#### 6.2.1.1 DIAMETER\_FIRST\_REGISTRATION (2001) + +The HSS informs the I-CSCF that: + +- The user is authorized to register this public identity; +- A S-CSCF shall be assigned to the user. + +#### 6.2.1.2 DIAMETER\_SUBSEQUENT\_REGISTRATION (2002) + +The HSS informs the I-CSCF that: + +- The user is authorized to register this public identity; +- A S-CSCF is already assigned and there is no need to select a new one. + +#### 6.2.1.3 DIAMETER\_UNREGISTERED\_SERVICE (2003) + +The HSS informs the I-CSCF that: + +- The public identity is not registered but has services related to unregistered state; +- A S-CSCF shall be assigned to the user. + +#### 6.2.1.4 DIAMETER\_SUCCESS\_SERVER\_NAME\_NOT\_STORED (2004) + +The HSS informs to the S-CSCF that: + +- The de-registration is completed; +- The S-CSCF name is not stored in the HSS. + +#### 6.2.1.5 Void + +### 6.2.2 Permanent Failures + +Errors that fall within the Permanent Failures category are used to inform the peer that the request failed, and should not be attempted again. + +#### 6.2.2.1 DIAMETER\_ERROR\_USER\_UNKNOWN (5001) + +A message was received for a user or a wildcarded identity that is unknown. + +#### 6.2.2.2 DIAMETER\_ERROR\_IDENTITIES\_DONT\_MATCH (5002) + +A message was received with a public identity and a private identity for a user, and the server determines that the public identity does not correspond to the private identity. + +#### 6.2.2.3 DIAMETER\_ERROR\_IDENTITY\_NOT\_REGISTERED (5003) + +A query for location information is received for a public identity that has not been registered before. The user to which this identity belongs cannot be given service in this situation. + +#### 6.2.2.4 DIAMETER\_ERROR\_ROAMING\_NOT\_ALLOWED (5004) + +The user is not allowed to roam in the visited network. + +#### 6.2.2.5 DIAMETER\_ERROR\_IDENTITY\_ALREADY\_REGISTERED (5005) + +The identity has already a server assigned and the registration status does not allow that it is overwritten. + +#### 6.2.2.6 DIAMETER\_ERROR\_AUTH\_SCHEME\_NOT\_SUPPORTED (5006) + +The authentication scheme indicated in an authentication request is not supported. + +#### 6.2.2.7 DIAMETER\_ERROR\_IN\_ASSIGNMENT\_TYPE (5007) + +The identity being registered has already the same server assigned and the registration status does not allow the server assignment type or the Public Identity type received in the request is not allowed for the indicated server-assignment-type. + +#### 6.2.2.8 DIAMETER\_ERROR\_TOO\_MUCH\_DATA (5008) + +The volume of the data pushed to the receiving entity exceeds its capacity. + +NOTE: This error code is also used in 3GPP TS 29.329 [11]. + +#### 6.2.2.9 DIAMETER\_ERROR\_NOT\_SUPPORTED\_USER\_DATA (5009) + +The S-CSCF informs HSS that the received subscription data contained information, which was not recognised or supported. + +#### 6.2.2.10 Void + +#### 6.2.2.11 DIAMETER\_ERROR\_FEATURE\_UNSUPPORTED (5011) + +A request application message was received indicating that the origin host requests that the command pair would be handled using a feature which is not supported by the destination host. + +## 6.3 AVPs + +The following table describes the Diameter AVPs defined by 3GPP for the Cx interface protocol, their AVP Code values, types, possible flag values and whether or not the AVP may be encrypted. The Vendor-ID header of all AVPs defined in this specification shall be set to 3GPP (10415) if not otherwise indicated. + +###### **Table 6.3.1: Diameter Multimedia Application AVPs** + +| Attribute Name | AVP Code | Section defined | Value Type | AVP Flag rules | | | | | +|---------------------------------------------|---------------|-----------------|-------------|----------------|-----|------------|----------|-----------| +| | | | | Must | May | Should not | Must not | May Encr. | +| Visited-Network-Identifier | 600 | 6.3.1 | OctetString | M, V | | | | No | +| Public-Identity | 601 | 6.3.2 | UTF8String | M, V | | | | No | +| Server-Name | 602 | 6.3.3 | UTF8String | M, V | | | | No | +| Server-Capabilities | 603 | 6.3.4 | Grouped | M, V | | | | No | +| Mandatory-Capability | 604 | 6.3.5 | Unsigned32 | M, V | | | | No | +| Optional-Capability | 605 | 6.3.6 | Unsigned32 | M, V | | | | No | +| User-Data | 606 | 6.3.7 | OctetString | M, V | | | | No | +| SIP-Number-Auth-Items | 607 | 6.3.8 | Unsigned32 | M, V | | | | No | +| SIP-Authentication-Scheme | 608 | 6.3.9 | UTF8String | M, V | | | | No | +| SIP-Authenticate | 609 | 6.3.10 | OctetString | M, V | | | | No | +| SIP-Authorization | 610 | 6.3.11 | OctetString | M, V | | | | No | +| SIP-Authentication-Context | 611 | 6.3.12 | OctetString | M, V | | | | No | +| SIP-Auth-Data-Item | 612 | 6.3.13 | Grouped | M, V | | | | No | +| SIP-Item-Number | 613 | 6.3.14 | Unsigned32 | M, V | | | | No | +| Server-Assignment-Type | 614 | 6.3.15 | Enumerated | M, V | | | | No | +| Deregistration-Reason | 615 | 6.3.16 | Grouped | M, V | | | | No | +| Reason-Code | 616 | 6.3.17 | Enumerated | M, V | | | | No | +| Reason-Info | 617 | 6.3.18 | UTF8String | M, V | | | | No | +| Charging-Information | 618 | 6.3.19 | Grouped | M, V | | | | No | +| Primary-Event-Charging-Function-Name | 619 | 6.3.20 | DiameterURI | M, V | | | | No | +| Secondary-Event-Charging-Function-Name | 620 | 6.3.21 | DiameterURI | M, V | | | | No | +| Primary-Charging-Collection-Function-Name | 621 | 6.3.22 | DiameterURI | M, V | | | | No | +| Secondary-Charging-Collection-Function-Name | 622 | 6.3.23 | DiameterURI | M, V | | | | No | +| User-Authorization-Type | 623 | 6.3.24 | Enumerated | M, V | | | | No | +| User-Data-Already-Available | 624 | 6.3.26 | Enumerated | M, V | | | | No | +| Confidentiality-Key | 625 | 6.3.27 | OctetString | M, V | | | | No | +| Integrity-Key | 626 | 6.3.28 | OctetString | M, V | | | | No | +| Supported-Features | 628 | 6.3.29 | Grouped | V | M | | | No | +| Feature-List-ID | 629 | 6.3.30 | Unsigned32 | V | | | M | No | +| Feature-List | 630 | 6.3.31 | Unsigned32 | V | | | M | No | +| Supported-Applications | 631 | 6.3.32 | Grouped | V | | | M | No | +| Associated-Identities | 632 | 6.3.33 | Grouped | V | | | M | No | +| Originating-Request | 633 | 6.3.34 | Enumerated | M, V | | | | No | +| Wildcarded-Public-Identity | 634 | 6.3.35 | UTF8String | V | | | M | No | +| SIP-Digest-Authenticate | 635 | 6.3.36 | Grouped | V | | | M | No | +| Digest-Realm | 104
NOTE 3 | 6.3.37 | UTF8String | M | | | V | No | +| Digest-Algorithm | 111
NOTE 3 | 6.3.39 | UTF8String | M | | | V | No | +| Digest-QoP | 110
NOTE 3 | 6.3.40 | UTF8String | M | | | V | No | +| Digest-HA1 | 121
NOTE 3 | 6.3.41 | UTF8String | M | | | V | No | +| UAR-Flags | 637 | 6.3.44 | Unsigned32 | V | | | M | No | +| Loose-Route-Indication | 638 | 6.3.45 | Enumerated | V | | | M | No | +| SCSCF-Restoration-Info | 639 | 6.3.46 | Grouped | V | | | M | No | +| Path | 640 | 6.3.47 | OctetString | V | | | M | No | +| Contact | 641 | 6.3.48 | OctetString | V | | | M | No | +| Subscription-Info | 642 | 6.3.49 | Grouped | V | | | M | No | +| Call-ID-SIP-Header | 643 | 6.3.49.1 | OctetString | V | | | M | No | +| From-SIP-Header | 644 | 6.3.49.2 | OctetString | V | | | M | No | +| To-SIP-Header | 645 | 6.3.49.3 | OctetString | V | | | M | No | +| Record-Route | 646 | 6.3.49.4 | OctetString | V | | | M | No | +| Associated-Registered-Identities | 647 | 6.3.50 | Grouped | V | | | M | No | +| Multiple-Registration-Indication | 648 | 6.3.51 | Enumerated | V | | | M | No | +| Restoration-Info | 649 | 6.3.52 | Grouped | V | | | M | No | +| Session-Priority | 650 | 6.3.56 | Enumerated | V | | | M | No | + +| | | | | | | | | | +|--------------------------------------|-----|--------|------------|---|--|--|---|----| +| Identity-with-Emergency-Registration | 651 | 6.3.57 | Grouped | V | | | M | No | +| Privileged-Sender-Indication | 652 | 6.3.58 | Enumerated | V | | | M | No | +| LIA-Flags | 653 | 6.3.59 | Unsigned32 | V | | | M | No | + +NOTE 1: The AVP header bit denoted as 'M', indicates whether support of the AVP is required. The AVP header bit denoted as 'V', indicates whether the optional Vendor-ID field is present in the AVP header. For further details, see IETF RFC 3588 [6]. + +NOTE 2: Depending on the concrete command. + +NOTE 3: The value of these attributes is defined in IETF RFC 4590 [20] + +### 6.3.1 Visited-Network-Identifier AVP + +The Visited-Network-Identifier AVP is of type OctetString. This AVP contains an identifier that helps the home network to identify the visited network (e.g. the visited network domain name). + +### 6.3.2 Public-Identity AVP + +The Public-Identity AVP is of type UTF8String. This AVP contains the public identity of a user in the IMS. The syntax of this AVP corresponds either to a SIP URL (with the format defined in IETF RFC 3261 [3] and IETF RFC 2396 [4]) or a TEL URL (with the format defined in IETF RFC 3966 [8]). Both SIP URL and TEL URL shall be in canonical form, as described in 3GPP TS 23.003 [13]. + +### 6.3.3 Server-Name AVP + +The Server-Name AVP is of type UTF8String. This AVP contains a SIP-URL (as defined in IETF RFC 3261 [3] and IETF RFC 2396 [4]), used to identify a SIP server (e.g. S-CSCF name). + +### 6.3.4 Server-Capabilities AVP + +The Server-Capabilities AVP is of type Grouped. This AVP contains information to assist the I-CSCF in the selection of an S-CSCF. + +AVP format + +Server-Capabilities ::= + +\*[Mandatory-Capability] + +\*[Optional-Capability] + +\*[Server-Name] + +\*[AVP] + +### 6.3.5 Mandatory-Capability AVP + +The Mandatory-Capability AVP is of type Unsigned32. Each value included in this AVP can be used to represent a single determined mandatory capability or a set of capabilities of an S-CSCF, as described in 3GPP TS 29.228 [1] (section 6.7). + +### 6.3.6 Optional-Capability AVP + +The Optional-Capability AVP is of type Unsigned32. Each value included in this AVP can be used to represent a single determined optional capability or a set of capabilities of an S-CSCF, as described in 3GPP TS 29.228 [1] (section 6.7). + +### 6.3.7 User-Data AVP + +The User-Data AVP is of type OctetString. This AVP contains the user data required to give service to a user. The exact content and format of this AVP is described in 3GPP TS 29.228 [1]. + +### 6.3.8 SIP-Number-Auth-Items AVP + +The SIP-Number-Auth-Items AVP is of type Unsigned32. + +When used in a request, the SIP-Number-Auth-Items indicates the number of authentication vectors the S-CSCF is requesting. This can be used, for instance, when the client is requesting several pre-calculated authentication vectors. In the answer message, the SIP-Number-Auth-Items AVP indicates the actual number of SIP-Auth-Data-Item AVPs provided by the Diameter server. + +### 6.3.9 SIP-Authentication-Scheme AVP + +The Authentication-Scheme AVP is of type UTF8String and indicates the authentication scheme used in the authentication of SIP messages. The following values are defined: + +- "Digest-AKA v1-MD5": it indicates IMS-AKA authentication scheme. + +NOTE 1: The S-CSCF uses the "Digest-AKA v1-MD5" authentication scheme towards the HSS for Digest-AKA v1 and Digest-AKA v2 versions, since they require from the HSS the same procedures that are already supported. + +- "SIP Digest": it indicates SIP Digest authentication scheme. +- "NASS-Bundled": it indicates NASS Bundled authentication scheme. +- "Early-IMS-Security": it indicates GPRS-IMS-Bundled authentication scheme. +- "Unknown": it indicates that the authentication scheme to be used is unknown at this point. + +### 6.3.10 SIP-Authenticate AVP + +The SIP-Authenticate AVP is of type OctetString and contains specific parts of the data portion of the WWW-Authenticate or Proxy-Authenticate SIP headers that are to be present in a SIP response. + +It shall contain, binary encoded, the concatenation of the authentication challenge RAND and the token AUTN. See 3GPP TS 33.203 [3] for further details about RAND and AUTN. The Authentication Information has a fixed length of 32 octets; the 16 most significant octets shall contain the RAND, the 16 least significant octets shall contain the AUTN. + +### 6.3.11 SIP-Authorization AVP + +The SIP-Authorization AVP is of type OctetString and contains specific parts of the data portion of the Authorization or Proxy-Authorization SIP headers suitable for inclusion in a SIP request. + +When included in an Authentication Request, it shall contain the concatenation of RAND, as sent to the terminal, and AUTS, as received from the terminal. RAND and AUTS shall both be binary encoded. See 3GPP TS 33.203 [3] for further details about RAND and AUTS. The Authorization Information has a fixed length of 30 octets; the 16 most significant octets shall contain the RAND, the 14 least significant octets shall contain the AUTS. + +When included in an Authentication Request Response, it shall contain, binary encoded, the expected response XRES. See 3GPP TS 33.203 [3] for further details about XRES. + +### 6.3.12 SIP-Authentication-Context AVP + +The SIP-Authentication-Context AVP is of type OctetString. + +### 6.3.13 SIP-Auth-Data-Item AVP + +The SIP-Auth-Data-Item is of type Grouped, and contains the authentication and/or authorization information for the Diameter client. + +AVP format + +SIP-Auth-Data-Item ::= < AVP Header : 612 10415 > + +[ SIP-Item-Number ] + +[ SIP-Authentication-Scheme ] +[ SIP-Authenticate ] +[ SIP-Authorization ] +[ SIP-Authentication-Context ] +[ Confidentiality-Key ] +[ Integrity-Key ] +[ SIP-Digest-Authenticate ] +[ Framed-IP-Address ] +[ Framed-IPv6-Prefix ] +[ Framed-Interface-Id ] +\* [ Line-Identifier ] +\* [AVP] + +### 6.3.14 SIP-Item-Number AVP + +The SIP-Item-Number AVP is of type Unsigned32. + +### 6.3.15 Server-Assignment-Type AVP + +The Server-Assignment-Type AVP is of type Enumerated, and indicates the type of server update being performed in a Server-Assignment-Request operation. The following values are defined: + +#### NO\_ASSIGNMENT (0) + +This value is used to request from HSS the user profile assigned to one or more public identities and to retrieve the S-CSCF restoration information for a registered Public User Identity, without affecting the registration state of those identities. + +#### REGISTRATION (1) + +The request is generated as a consequence of a first registration of an identity. + +#### RE\_REGISTRATION (2) + +The request corresponds to the re-registration of an identity or update of the S-CSCF Restoration Information. + +#### UNREGISTERED\_USER (3) + +The request is generated because the S-CSCF received a request for a public identity that is not registered, or because an AS sent an originating request on behalf of a public identity that is not registered. + +#### TIMEOUT\_DEREGISTRATION (4) + +The SIP registration timer of an identity has expired. + +#### USER\_DEREGISTRATION (5) + +The S-CSCF has received a user initiated de-registration request. + +##### TIMEOUT\_DEREGISTRATION\_STORE\_SERVER\_NAME (6) + +The SIP registration timer of an identity has expired. The S-CSCF keeps the user data stored in the S-CSCF and requests HSS to store the S-CSCF name. + +##### USER\_DEREGISTRATION\_STORE\_SERVER\_NAME (7) + +The S-CSCF has received a user initiated de-registration request. The S-CSCF keeps the user data stored in the S-CSCF and requests HSS to store the S-CSCF name. + +##### ADMINISTRATIVE\_DEREGISTRATION (8) + +The S-CSCF, due to administrative reasons, has performed the de-registration of an identity. + +##### AUTHENTICATION\_FAILURE (9) + +The authentication of a user has failed. + +##### AUTHENTICATION\_TIMEOUT (10) + +The authentication timeout has occurred. + +##### DEREGISTRATION\_TOO\_MUCH\_DATA (11) + +The S-CSCF has requested user profile information from the HSS and has received a volume of data higher than it can accept. + +#### AAA\_USER\_DATA\_REQUEST (12) + +Used in the SWx protocol, defined in 3GPP TS 29.273 [18]. This value is not used in the Cx protocol. + +##### PGW\_UPDATE (13) + +Used in the SWx protocol, defined in 3GPP TS 29.273 [18]. This value is not used in the Cx protocol. + +#### RESTORATION (14) + +Used in the SWx protocol, defined in 3GPP TS 29.273 [18]. This value is not used in the Cx protocol. + +### 6.3.16 Deregistration-Reason AVP + +The Deregistration-Reason AVP is of type Grouped, and indicates the reason for a de-registration operation. + +AVP format + +Deregistration-Reason ::= < AVP Header : 615 10415 > + +{ Reason-Code } + +[ Reason-Info ] + +\* [AVP] + +### 6.3.17 Reason-Code AVP + +The Reason-Code AVP is of type Enumerated, and defines the reason for the network initiated de-registration. The following values are defined: + +PERMANENT\_TERMINATION (0) + +NEW\_SERVER\_ASSIGNED (1) + +SERVER\_CHANGE (2) + +REMOVE\_S-CSCF (3) + +The detailed behaviour of the S-CSCF is defined in 3GPP TS 29.228 [1]. + +### 6.3.18 Reason-Info AVP + +The Reason-Info AVP is of type UTF8String, and contains textual information to inform the user about the reason for a de-registration. + +### 6.3.19 Charging-Information AVP + +The Charging-Information is of type Grouped, and contains the addresses of the charging functions. + +AVP format + +``` +Charging-Information ::= < AVP Header : 618 10415 > + [ Primary-Event-Charging-Function-Name ] + [ Secondary-Event-Charging-Function-Name ] + [ Primary-Charging-Collection-Function-Name ] + [ Secondary-Charging-Collection-Function-Name ] + *[ AVP] +``` + +### 6.3.20 Primary-Event-Charging-Function-Name AVP + +The Primary-Event-Charging-Function-Name AVP is of type DiameterURI. This AVP contains the address of the Primary Online Charging Function. The receiving network element shall extract the FQDN of the DiameterURI in this AVP and may use it as content of the Destination-Host AVP for the Diameter accounting requests. The parent domain of the FQDN in the DiameterURI shall be used as Destination-Realm. The number of labels used for the Destination-Realm shall be determined before the Charging Information is provisioned and may be a configuration option. + +NOTE: A FQDN is an absolute domain name including a subdomain and its parent domain. The subdomain and the parent domain contain one or more labels separated by dots. + +### 6.3.21 Secondary-Event-Charging-Function-Name AVP + +The Secondary-Event-Charging-Function-Name AVP is of type DiameterURI. This AVP contains the address of the Secondary Online Charging Function. The Destination-Host and Destination-Realm values for the Diameter accounting requests should be extracted from the DiameterURI in the way indicated in clause 6.3.20. + +### 6.3.22 Primary-Charging-Collection-Function-Name AVP + +The Primary-Charging-Collection-Function-Name AVP is of type DiameterURI. This AVP contains the address of the Primary Charging Data Function. The Destination-Host and Destination-Realm values for the Diameter accounting requests should be extracted from the DiameterURI in the way indicated in clause 6.3.20. + +### 6.3.23 Secondary-Charging-Collection-Function-Name AVP + +The Secondary-Charging-Collection-Function-Name AVP is of type DiameterURI. This AVP contains the address of the Secondary Charging Data Function. The Destination-Host and Destination-Realm for the Diameter accounting requests values should be extracted from the DiameterURI in the way indicated in clause 6.3.20. + +### 6.3.24 User-Authorization-Type AVP + +The User-Authorization-Type AVP is of type Enumerated, and indicates the type of user authorization being performed in a User Authorization operation, i.e. UAR command. The following values are defined: + +REGISTRATION (0) + +This value is used in case of the initial registration or re-registration. I-CSCF determines this from the Expires field or expires parameter in Contact field in the SIP REGISTER method if it is not equal to zero. + +This is the default value. + +DE\_REGISTRATION (1) + +This value is used in case of the de-registration. I-CSCF determines this from the Expires field or expires parameter in Contact field in the SIP REGISTER method if it is equal to zero. + +REGISTRATION\_AND\_CAPABILITIES (2) + +This value is used when the I-CSCF explicitly requests S-CSCF capability information from the HSS. The I-CSCF shall use this value when the user's current S-CSCF, which is stored in the HSS, cannot be contacted and a new S-CSCF needs to be selected + +### 6.3.25 Void + +### 6.3.26 User-Data-Already-Available AVP + +The User-Data-Already-Available AVP is of type Enumerated, and indicates to the HSS whether or not the S-CSCF already has the part of the user profile that it needs to serve the user. The following values are defined: + +USER\_DATA\_NOT\_AVAILABLE (0) + +The S-CSCF does not have the data that it needs to serve the user. + +USER\_DATA\_ALREADY\_AVAILABLE (1) + +The S-CSCF already has the data that it needs to serve the user. + +### 6.3.27 Confidentiality-Key AVP + +The Confidentiality-Key is of type OctetString, and contains the Confidentiality Key (CK). + +### 6.3.28 Integrity-Key AVP + +The Integrity-Key is of type OctetString, and contains the Integrity Key (IK). + +### 6.3.29 Supported-Features AVP + +The Supported-Features AVP is of type Grouped. If this AVP is present it may inform the destination host about the features that the origin host supports for the application. The Feature-List AVP contains a list of supported features of the origin host. The Vendor-Id AVP and the Feature-List-ID AVP shall together identify which feature list is carried in the Supported-Features AVP for the Application-ID present in the command header. + +Where a Supported-Features AVP is used to identify features that have been defined by 3GPP, the Vendor-Id AVP shall contain the vendor ID of 3GPP. Vendors may define proprietary features, but it is strongly recommended that the possibility is used only as the last resort. Where the Supported-Features AVP is used to identify features that have been defined by a vendor other than 3GPP, it shall contain the vendor ID of the specific vendor in question. + +If there are multiple feature lists defined by the same vendor and the same application, the Feature-List-ID AVP shall differentiate those lists from one another. The destination host shall use the value of the Feature-List-ID AVP to identify the feature list. + +AVP format + +Supported-Features ::= < AVP header: 628 10415 > + +{ Vendor-Id } + +{ Feature-List-ID } + +{ Feature-List } + +\*[AVP] + +### 6.3.30 Feature-List-ID AVP + +The Feature-List-ID AVP is of type Unsigned32 and it contains the identity of a feature list. + +### 6.3.31 Feature-List AVP + +The Feature-List AVP is of type Unsigned32 and it contains a bit mask indicating the supported features of an application. When the bit set, indicates the corresponding feature is supported by the application. For the Cx application, the meaning of the bits has been defined in 7.1.1. + +### 6.3.32 Supported-Applications AVP + +The Supported-Applications AVP is of type Grouped and it contains the supported application identifiers of a Diameter node. + +AVP format + +``` +Supported-Applications ::= < AVP header: 631 10415 > + *[ Auth-Application-Id ] + *[ Acct-Application-Id ] + *[ Vendor-Specific-Application-Id ] + *[ AVP ] +``` + +### 6.3.33 Associated-Identities AVP + +The Associated-Identities AVP is of type Grouped and it contains the private user identities associated to an IMS subscription. + +AVP format + +``` +Associated-Identities ::= < AVP header: 632, 10415 > + *[ User-Name ] + *[ AVP ] +``` + +### 6.3.34 Originating-Request AVP + +The Originating-Request AVP is of type Enumerated. The following value is defined: + +ORIGINATING (0) + +This value indicates to the HSS that the request is related to an AS originating SIP request in the Location-Information-Request operation. + +### 6.3.35 Wildcarded-Public-Identity AVP + +The Wildcarded-Public-Identity AVP is of type UTF8String. This AVP contains a Wildcarded PSI or Wildcarded Public User Identity stored in the HSS. The syntax of the contents of this AVP is described in 3GPP TS 23.003 [13]. + +### 6.3.36 SIP-Digest-Authenticate AVP + +The SIP-Digest-Authenticate is of type Grouped and it contains a reconstruction of either the SIP WWW-Authenticate or Proxy-Authentication header fields specified in IETF RFC 2617 [14]. + +AVP format + +``` +SIP-Digest-Authenticate ::= < AVP Header: 635 10415 > + { Digest-Realm } + [ Digest-Algorithm ] + { Digest-QoP } + { Digest-HA1 } + *[ AVP ] +``` + +### 6.3.37 Digest-Realm AVP + +The Digest-Realm AVP is defined in IETF RFC 4740 [15]. + +### 6.3.38 Void + +### 6.3.39 Digest-Algorithm AVP + +The Digest-Algorithm AVP is defined in IETF RFC 4740 [15]. + +### 6.3.40 Digest-QoP AVP + +The Digest-QoP AVP is defined in IETF RFC 4740 [15]. + +### 6.3.41 Digest-HA1 AVP + +The Digest-HA1 AVP is defined in IETF RFC 4740 [15]. + +### 6.3.42 Line-Identifier AVP + +The Line-Identifier AVP is of type OctetString. This AVP has Vendor Id ETSI (13019) and AVP code 500. This AVP contains a fixed broadband access line identifier associated with the user. + +### 6.3.43 Wildcarded-IMPU AVP + +The Wildcarded-IMPU AVP is of type UTF8String. This AVP contains a Wildcarded Public User Identity stored in the HSS. The syntax of the contents of this AVP is described in 3GPP TS 23.003 [13]. + +Note: This AVP is used by Sh interface as specified in the 3GPP TS 29.328 [16] and 3GPP TS 29.329 [11]. + +### 6.3.44 UAR-Flags AVP + +The UAR-Flags AVP is of type Unsigned32 and it contains a bit mask. The meaning of the bits is defined in the following table: + +**Table 6.3.44.1: UAR-Flags** + +| Bit | Name | Description | +|-----------------------------------------------------------------------------------------------------------|----------------------------|----------------------------------------------------------------------------------------------| +| 0 | IMS Emergency Registration | This bit, when set, indicates that the request corresponds to an IMS Emergency Registration. | +| Bits not defined in this table shall be cleared by the sending I-CSCF and discarded by the receiving HSS. | | | + +### 6.3.45 Loose-Route-Indication AVP + +The Loose-Route-Indication AVP is of type Enumerated and indicates to the S-CSCF whether or not the loose route mechanism is required to serve the registered Public User Identities. The following values are defined: + +LOOSE\_ROUTE\_NOT\_REQUIRED (0) + +LOOSE\_ROUTE\_REQUIRED (1) + +### 6.3.46 SCSCF-Restoration-Info AVP + +The SCSCF-Restoration-Info AVP is of type Grouped and it contains the information required for an S-CSCF to handle the requests for a user. + +AVP format + +SCSCF-Restoration-Info ::= < AVP Header: 639, 10415> + +``` +{ User-Name } +1*{ Restoration-Info } +[ SIP-Authentication-Scheme ] +*[ AVP ] +``` + +### 6.3.47 Path AVP + +The Path AVP is of type OctetString and it contains a comma separated list of SIP proxies in the Path header as defined in IETF RFC 3327 [17]. + +### 6.3.48 Contact AVP + +The Contact AVP is of type OctetString and it contains the Contact Addresses and Parameters in the Contact header as defined in IETF RFC 3261 [11]. + +### 6.3.49 Subscription-Info AVP + +The Subscription-Info AVP is of type Grouped and it contains the UE's subscription information. The Contact AVP contains the Contact Address and Parameters in the Contact header of the subscription request. + +AVP format + +``` +Subscription-Info ::= < AVP Header: 642, 10415> + { Call-ID-SIP-Header } + { From-SIP-Header } + { To-SIP-Header } + { Record-Route } + {Contact} + *[ AVP ] +``` + +#### 6.3.49.1 Call-ID-SIP-Header AVP + +The Call-ID-SIP-Header AVP is of type OctetString and it contains the information in the Call-ID header as defined in IETF RFC 3261 [11]. + +#### 6.3.49.2 From-SIP-Header AVP + +The From-SIP-Header AVP is of type OctetString and it contains the information in the From header as defined in IETF RFC 3261 [11]. + +#### 6.3.49.3 To-SIP-Header AVP + +The To-SIP-Header AVP is of type OctetString and it contains the information in the To header as defined in IETF RFC 3261 [11]. + +#### 6.3.49.4 Record-Route AVP + +The Record-Route AVP is of type OctetString and it contains a comma separated list of Record Route header(s) as defined in IETF RFC 3261 [11]. + +### 6.3.50 Associated-Registered-Identities AVP + +The Associated-Registered-Identities AVP is of type Grouped and it contains the Private User Identities registered with the Public User Identity received in the request command. + +AVP format + +``` +Associated-Registered-Identities ::= < AVP header: 647, 10415 > + *[ User-Name ] + *[ AVP ] +``` + +### 6.3.51 Multiple-Registration-Indication + +The Multiple-Registration-Indication AVP is of type Enumerated and indicates to the HSS whether or not the request is related to a multiple registration. The following values are defined: + +NOT\_MULTIPLE\_REGISTRATION (0) + +MULTIPLE\_REGISTRATION (1) + +### 6.3.52 Restoration-Info AVP + +The Restoration-Info AVP is of type Grouped and it contains the information related to a specific registration required for an S-CSCF to handle the requests for a user. The Contact AVP contains the Contact Address and Parameters in the Contact header of the registration request. + +AVP format + +Restoration-Info ::= < AVP Header: 649, 10415> + +{ Path } + +{ Contact } + +[ Subscription-Info ] + +\*[ AVP ] + +### 6.3.53 Framed-IP-Address AVP + +The Framed-IP-Address AVP is defined in IETF RFC 4005 [19]. + +### 6.3.54 Framed-IPv6-Prefix AVP + +The Framed-IPv6-Prefix AVP is defined in IETF RFC 4005 [19], and it shall be encoded as defined in IETF RFC 3162 [22]. + +### 6.3.55 Framed-Interface-Id AVP + +The Framed-Interface-Id AVP is defined in IETF RFC 4005 [19]. + +### 6.3.56 Session-Priority AVP + +The Session-Priority AVP is of type Enumerated and indicates to the HSS the session's priority. The following values are defined: + +PRIORITY-0 (0) + +PRIORITY-1 (1) + +PRIORITY-2 (2) + +PRIORITY-3 (3) + +PRIORITY-4 (4) + +PRIORITY-0 is the highest priority. + +The value of the AVP when sent to the HSS is mapped from the value received by the CSCF as described in 3GPP TS 24.229 table A.162. The mapping is operator specific. + +### 6.3.57 Identity-with-Emergency-Registration AVP + +The Identity-with-Emergency-Registration AVP is of type Grouped and it contains a pair of private/public user identities which are emergency registered. + +AVP format + +``` +Identity-with-Emergency-Registration ::= < AVP header: 651, 10415 > + { User-Name } + { Public-Identity } + *[ AVP ] +``` + +### 6.3.58 Privileged-Sender-Indication AVP + +The Privileged-Sender-Indication AVP is of type Enumerated and indicates to the S-CSCF whether or not the Private User Identity shall be considered as a privileged sender. The following values are defined: + +NOT\_PRIVILEGED\_SENDER (0)PRIVILEGED\_SENDER (1) + +### 6.3.59 LIA-Flags + +The LIA-Flags AVP is of type Unsigned32 and it shall contain a bit mask. The meaning of the bits shall be as defined in table 6.3.59.1. + +**Table 6.3.59.1: LIA-Flags** + +| Bit | Name | Description | +|-----------------------------------------------------------------------------------------------------------------|-------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------| +| 0 | PSI Direct Routing Indication | This bit, when set, indicates the request corresponds to PSI Direct Routing, what implies that HSS returns an AS name in Server-Name AVP. | +| NOTE: Bits not defined in this table shall be cleared by the sending HSS and discarded by the receiving I-CSCF. | | | + +## 6.4 Use of namespaces + +This clause contains the namespaces that have either been created in this specification, or the values assigned to existing namespaces managed by IANA. + +### 6.4.1 AVP codes + +This specification assigns the AVP values from the AVP Code namespace managed by 3GPP for its Diameter vendor-specific applications. See section 6.3 for the assignment of the namespace in this specification. + +### 6.4.2 Experimental-Result-Code AVP values + +This specification has assigned Experimental-Result-Code AVP values 2001-2005 and 5001-5011. See section 6.2. + +### 6.4.3 Command Code values + +This specification assigns the values 300-305 from the range allocated by IANA to 3GPP in IETF RFC 3589 [12]. + +### 6.4.4 Application-ID value + +IANA has allocated the value 16777216 for the 3GPP Cx interface application. + +# --- 7 Special Requirements + +## 7.1 Version Control + +New functionality - i.e. functionality beyond the Rel-5 standard - shall be introduced by post-Rel-5 versions of this specification to the Diameter applications as follows: + +1. If possible, the new functionality shall be defined optional. +2. If backwards incompatible changes can not be avoided, the new functionality should be introduced as a feature, see 7.1.1. +3. If the change would be backwards incompatible even as if it was defined as a feature, a new version of the interface shall be created by changing the application identifier of the Diameter application, see 7.1.2. + +### 7.1.1 Defining a new feature + +The base functionality for the Cx is the 3GPP Rel-5 standard and a feature is an extension to that functionality. A feature is a functional entity that has a significant meaning to the operation of a Diameter application i.e. a single new parameter without a substantial meaning to the functionality of the Diameter endpoints should not be defined to be a new feature. If the support for a feature is defined mandatory in a post-Rel-5 versions of this specification, the feature concept enables interworking between Diameter endpoints regardless of whether they support all, some or none of the features of the application. Features should be defined so that they are independent from one another. + +The content of a feature shall be defined as a part of the specification of the affected application messages. If new AVPs are added to the commands because of the new feature, the new AVPs shall have the 'M' bit cleared and the AVP shall not be defined mandatory in the command ABNF. The support for a feature may be defined to be mandatory behaviour of a node. + +As an option to defining a feature, an extension to S-CSCF functionality for post-Rel-5 version may be defined as part of the list of mandatory capabilities that is used by the I-CSCF during the process of selecting an S-CSCF, as described in 3GPP TS 29.228 [1]. Any new feature should be taken into account in the definition of the list of mandatory and optional S-CSCF capabilities. Guidelines for the definition of S-CSCF Capabilities are described in 3GPP TS 29.228 [1]. + +The following table of features shall apply to the Cx interface. + +**Table 7.1.1: Features of Feature-List-ID 1 used in Cx** + +| Feature bit | Feature | M/O | Description | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|-----|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 0 | SiFC | O |

Shared iFC sets

This feature is applicable for the SAR/SAA and PPR/PPA command pairs. If both the HSS and the S-CSCF support this feature, subsets of Initial Filter Criteria may be shared by several service profiles and the HSS shall download the shared iFC sets implicitly by downloading the unique identifiers of the shared iFC sets to the S-CSCF. By means of a locally administered database, the S-CSCF then maps the downloaded identifiers onto the shared iFC sets. If the DSAI feature, as defined in 3GPP TS 29.328 [16], is also active with the shared iFC sets feature then the HSS shall behave as described below: If the DSAI feature is active with the shared iFC sets feature and if all the iFCs bounding to a Shared iFC set are not masked by the DSAI, the HSS shall download the unique identifier of the shared iFC set to the S-CSCF. If some iFCs or all the iFCs bounding to a shared iFC set are masked by the DSAI, the HSS shall not download the identifier of the shared iFC set. Instead the HSS shall

  • - download the remaining non masked iFCs of the shared iFC set explicitly or
  • - download suitable identifiers of other shared iFC sets, i.e. those covering exactly the remaining non masked iFCs and which do not contain masked iFCs or
  • - download a combination of identifiers of shared iFC sets and explicit iFCs which cover exactly the remaining non masked iFCs.

If the S-CSCF does not support this feature, the HSS shall not download identifiers of shared iFC sets. Instead as a default behavior the HSS shall (by means of a locally administered database) download the iFCs of a shared iFC set explicitly.

If the HSS does not support this feature, no special default behaviour is required for the S-CSCF.

Note: In using this feature option, the network operator is responsible for keeping the local databases in the S-CSCFs and HSSs consistent.

| +| 1 | AliasInd | M |

Alias Indication

This feature is applicable for the SAR/SAA and PPR/PPA command pairs. If both the HSS and the S-CSCF support this feature, different aliases groups may be sent within the same service profile. Identities within the same service profile that are aliases shall be sent with identical alias group ID. If the S-CSCF does not support this feature, the HSS shall send within the service profile only those identities that are aliases. Public User Identities that are not aliases of each other shall be sent in different service profiles even if these service profiles have exactly the same Core Network Service Authorization, Initial Filter Criteria, and Shared iFC Set information and these service profiles only differ in the contained Public User Identities. This is done in order to allow backwards compatibility since part of the handling of aliases in the S-CSCF was there before this indication was required and it applied to identities that share the same service profile and implicit registration set. In this case, the S-CSCF does not provide any additional treatment of aliases than that which existed before this indication was required.

If the HSS does not support this feature, no special default behaviour is required for the S-CSCF.

Note: All identities included in a single SAA or PPR command are always within one implicit registration set.

| +| 2 | IMSRestorationInd | O |

IMS Restoration Indication

This feature is applicable for the UAR/UAA, LIR/LIA, SAR/SAA command pairs. If both the HSS and the I-CSCF support this feature, in case the S-CSCF currently assigned in the HSS to the Public User Identity cannot be contacted the I-CSCF shall trigger the assignment of a new S-CSCF. If both the HSS and the S-CSCF support this feature, the S-CSCF shall send S-CSCF Restoration Information to the HSS. The HSS shall send this information element in SAA to the S-CSCF when required. If the S-CSCF does not support this feature, the HSS shall not send the IMS Restoration Information to the S-CSCF.

| +|

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

| | | | + +The origin host may discover the supported features of the destination host with the dynamic discovery mechanism defined in 7.2 or via local O&M interfaces. + +### 7.1.2 Changing the version of the interface + +The version of an interface shall be changed by a future version of this specification only if there is no technically feasible means to avoid backwards incompatible changes to the Diameter application, i.e. to the current version of the interface. However, if the incompatible changes can be encapsulated within a feature, there is no need to change the version of the interface. The versioning of an interface shall be implemented by assigning a new application identifier for the interface. This procedure is in line with the Diameter base protocol (see IETF RFC 3588) which defines that if an incompatible change is made to a Diameter application, a new application identifier shall be assigned for the Diameter application. + +The following table shall apply to the Cx interface, column Application identifier lists the used application identifiers on Cx and 3GPP. + +**Table 7.1.2: Application identifiers used in Cx** + +| Application identifier | First applied | +|------------------------|---------------| +| 16777216 | 3GPP Rel-5 | + +The origin host may discover which versions of an interface the destination host supports within the capabilities exchange (i.e. CER/CEA command), via the error messages defined in the chapter 7.3 or via local O&M interfaces. + +## 7.2 Supported features + +Features that are not indicated in the Supported-Features AVPs within a given application message shall not be used to construct that message. A request application message shall always be compliant with the list of supported features indicated in the Supported-Features AVPs within the application message. If a feature does not have an effect on constructing an application message, the message is by definition compliant with the feature. If no features are indicated in the application message, no features - i.e. no extensions to Rel-5 - shall be used to construct the application message. An answer application message shall always indicate in the Supported-Features AVPs the complete set of features supported by the sender of the answer application message. An answer application message shall be compliant with the features commonly supported by the sender of the request and answer application messages. + +The sender of a request application message shall discover for a given application message pair which features a destination host supports as described in 7.2.1. The discovered features of one command pair may be applicable to other command pairs within the application. Different commands within an application may support a different set of features. After discovering the features a destination host supports for a given application message pair, the sender of the request application message may store the information on the supported features of the destination host and it may use the features the destination host supports to construct the subsequent request application messages sent to the destination host. + +### 7.2.1 Dynamic discovery of supported features + +When sending a request application message to a destination host whose supported features the sender does not know, the request application message shall include the Supported-Features AVP containing the set of features required to process the request and generate the answer. An exception to this is where the origin host does not use any features to construct the request application message and it is not prepared to accept an answer application message which is constructed by making use of any features. For this exception the origin host need not include the Supported-Features AVP within the message. + +The Supported-Features AVP within a request application message shall always have the 'M' bit set and within an answer application message the AVP shall never have the 'M' bit set. An exception to this is where the origin host does not use any supported feature to construct the request application message but is prepared to accept an answer application message which is constructed by making use of supported features. For this exception it is optional for the origin host to set the 'M' bit of the Supported-Features AVP within the request application message. + +On receiving a request application message, the destination host shall do one of the following: + +- If it supports all features indicated in the Supported-Features AVPs within the request message, the answer application message shall include Supported-Features AVPs identifying the complete set of + +features that it supports. The Experimental-Result-Code AVP shall not be set to DIAMETER\_ERROR\_FEATURE\_UNSUPPORTED. + +- If the request application message does not contain any Supported-Features AVPs, the answer application message shall include either Supported-Features AVPs identifying the complete set of features that it supports or, if it does not support any features, no Supported-Features AVPs shall be present. The Experimental-Result-Code AVP shall not be set to DIAMETER\_ERROR\_FEATURE\_UNSUPPORTED. +- If it does not support all the features indicated in the Supported-Features AVPs with the 'M' bit set, it shall return the answer application message with the Experimental-Result-Code AVP set to DIAMETER\_ERROR\_FEATURE\_UNSUPPORTED and it shall include also Supported-Features AVPs containing lists of all features that it supports. +- If it does not support Supported-Features AVP and it receives a request application message containing Supported-Features AVPs with the 'M' bit set, it will return the answer application message with the Result-Code AVP set to DIAMETER\_AVP\_UNSUPPORTED and a Failed-AVP containing at least one Supported-Features AVP as received in the request application message. + +If an answer application message is received with the Experimental-Result-Code AVP set to DIAMETER\_ERROR\_FEATURE\_UNSUPPORTED or with the Result-Code AVP set to DIAMETER\_AVP\_UNSUPPORTED, the sender of the request application message may, based on the information in the received Supported-Features AVP or the lack of the AVP in the message, re-send the Diameter message containing only the common supported features. + +## 7.3 Interface versions + +The sender of the request application message may discover which versions of an interface a destination host supports together with the capabilities exchange (i.e. CER/CEA command pair) and with error mechanisms defined to the application messages in 7.3.1. The sender of the request application message should store information on all versions of the interface the destination host supports. The sender of the request application message should use the latest common version of the application supported by the destination host to send the request. + +If the receiver of the request application message itself or the versions of the interface it supports are not yet known, the sender of the request application message should use the latest supported version of the interface of the Diameter peer (i.e. Diameter proxy, redirect or relay agent) discovered during the capabilities exchange. If the Diameter peer is a redirect or relay agent, which advertises the 0xffffffff as an application identifier, the sender of the request application message shall use its own latest supported version of the interface when initiating the request. + +### 7.3.1 Discovery of supported interface versions + +When a Diameter agent receives a request application message and the Diameter agent doesn't find any upstream peer that would support the application identifier indicated in the request, the Diameter agent shall return the result code DIAMETER\_UNABLE\_TO\_DELIVER and it may also return the list of the application identifiers, which are supported by the destination host of the request application message. The supported application identifiers are carried in the answer application message in the Supported-Applications grouped AVP. + +Message format for the answer application message (based on the RFC 3588, section 7.2) is as follows: + +``` + ::= < Diameter Header: code, ERR [PXY] > + 0*1< Session-Id > + { Origin-Host } + { Origin-Realm } + { Result-Code } + [ Origin-State-Id ] + [ Error-Reporting-Host ] + [ Proxy-Info ] + [ Supported-Applications ] + * [ AVP ] +``` + +If the receiver of a request application message does not support the application identifier indicated in the message, it shall return the result code DIAMETER\_APPLICATION\_UNSUPPORTED and it may also return the list of all + +application identifiers it supports. The supported application identifiers are carried in the Supported-Applications grouped AVP. The error message format is as specified above. + +If an answer application message is received with Result-Code AVP set to DIAMETER\_UNABLE\_TO\_DELIVER or Experimental-Result-Code AVP set to DIAMETER\_APPLICATION\_UNSUPPORTED and the message contains the Supported-Applications AVP, the receiver of the answer application message may select, based on the information in the Supported-Applications AVP, the latest common version of the interface with the destination host and re-send the Diameter message with a structure conforming to the ABNF of that release. + +# --- Annex A (informative): Change history + +| Date | TSG # | TSG Doc. | CR# | Rev | Subject/Comment | In | Out | +|----------|-------|-----------|------|-----|---------------------------------------------------------------------------------|-------|-------| +| Jun 2002 | CN#16 | NP-020265 | | | Version 2.0.0 approved at CN#16 | 2.0.0 | 5.0.0 | +| Sep 2002 | CN#17 | NP-020449 | 001 | - | Add a reference to the new IETF RFC on SCTP checksum | 5.0.0 | 5.1.0 | +| Sep 2002 | CN#17 | NP-020449 | 003 | - | Wrong format of Charging Function Addresses | 5.0.0 | 5.1.0 | +| Sep 2002 | CN#17 | NP-020449 | 005 | - | Editorial mistake in the definition of command MAA | 5.0.0 | 5.1.0 | +| Dec 2002 | CN#18 | NP-020587 | 006 | - | Addition of User-Name AVP to SAA | 5.1.0 | 5.2.0 | +| Dec 2002 | CN#18 | NP-020587 | 007 | - | Editorial correction of SIP-Auth-Data-Item AVP definition | 5.1.0 | 5.2.0 | +| Dec 2002 | CN#18 | NP-020589 | 008 | 1 | Clarification of REGISTRATION AND CAPABILITIES value | 5.1.0 | 5.2.0 | +| Dec 2002 | CN#18 | NP-020588 | 009 | - | Correction in charging information | 5.1.0 | 5.2.0 | +| Dec 2002 | CN#18 | NP-020590 | 010 | 1 | Error handling in S-CSCF when receiving too much data | 5.1.0 | 5.2.0 | +| Mar 2003 | CN#19 | NP-030101 | 012 | 1 | Update TS 29.229 after Diameter has become RFC | 5.2.0 | 5.3.0 | +| Mar 2003 | CN#19 | NP-030101 | 015 | 1 | Clarification on Re-allocation of S-CSCF | 5.2.0 | 5.3.0 | +| Mar 2003 | CN#19 | NP-030101 | 018 | 1 | Handling of non supported data in the S-CSCF when the profile is being updated. | 5.2.0 | 5.3.0 | +| Mar 2003 | CN#19 | NP-030101 | 014 | - | Correction to the values of User-Authorizatin-Type AVP | 5.2.0 | 5.3.0 | +| Mar 2003 | CN#19 | NP-030101 | 013 | - | Replacement of the NAS-Session-Key AVP | 5.2.0 | 5.3.0 | +| Jun 2003 | CN#20 | NP-030215 | 019 | - | Conditionality of User-Name AVP in Server-Assignment-Answer | 5.3.0 | 5.4.0 | +| Sep 2003 | CN#21 | NP-030383 | 022 | 1 | Critical Correction on the PPR command code | 5.4.0 | 5.5.0 | +| Dec 2003 | CN#22 | NP-030500 | 021 | 1 | The S-CSCF name needs to be checked always in MAR and SAR | 5.5.0 | 5.6.0 | +| Dec 2003 | CN#22 | NP-030500 | 027 | - | User-Authorization-Type | 5.5.0 | 5.6.0 | +| Dec 2003 | CN#22 | NP-030518 | 029 | - | Clarification of inclusion of elements in Charging Information | 5.5.0 | 5.6.0 | +| Dec 2003 | CN#22 | | | | Application IDs and references updated | 5.5.0 | 5.6.0 | +| Mar 2004 | CN#23 | NP-040055 | 035 | - | Error for no identification in SAR command | 5.6.0 | 6.0.0 | +| Jun 2004 | CN#24 | NP-040215 | 037 | 1 | Update of the charging addresses from HSS | 6.0.0 | 6.1.0 | +| Jun 2004 | CN#24 | NP-040215 | 043 | - | Multimedia-Auth-Request (MAR) Command Message Format Corrections | 6.0.0 | 6.1.0 | +| Jun 2004 | CN#24 | NP-040215 | 050 | 2 | Use of Vendor-Id by 3GPP | 6.0.0 | 6.1.0 | +| Sep 2004 | CN#25 | NP-040395 | 065 | 2 | Application version control | 6.1.0 | 6.2.0 | +| Sep 2004 | CN#25 | NP-040401 | 056 | - | Optimization of User Profile Download | 6.1.0 | 6.2.0 | +| Sep 2004 | CN#25 | NP-040396 | 058 | - | Simplification of the User Profile Split concept | 6.1.0 | 6.2.0 | +| Sep 2004 | CN#25 | NP-040401 | 061 | - | Correction of the Application-Id code | 6.1.0 | 6.2.0 | +| Sep 2004 | CN#25 | NP-040412 | 063 | 1 | Re-numbering of 3GPP specific AVP codes | 6.1.0 | 6.2.0 | +| Dec 2004 | CN#26 | NP-040523 | 070 | - | Cx ABNF corrections | 6.2.0 | 6.3.0 | +| Mar 2005 | CN#27 | NP-050030 | 078 | 2 | Correction of authentication-related AVPs | 6.3.0 | 6.4.0 | +| Mar 2005 | CN#27 | NP-050037 | 079 | - | TEL-URI reference update | 6.3.0 | 6.4.0 | +| Mar 2005 | CN#27 | NP-050030 | 082 | 1 | Introduction of Failed-AVP | 6.3.0 | 6.4.0 | +| Jun 2005 | CT#28 | CP-050086 | 087 | - | Correction of reference | 6.4.0 | 6.5.0 | +| Jun 2005 | CT#28 | CP-050086 | 089 | 1 | Editorial corrections | 6.4.0 | 6.5.0 | +| Jun 2005 | CT#28 | CP-050086 | 088 | 2 | Corrections to message parameters | 6.4.0 | 6.5.0 | +| Sep 2005 | CT#29 | CP-050440 | 091 | 2 | Private identities on the Cx | 6.5.0 | 6.6.0 | +| Sep 2005 | CT#29 | CP-050282 | 093 | 1 | Charging-Information correction | 6.5.0 | 6.6.0 | +| Sep 2005 | CT#29 | CP-050296 | 094 | - | Error code cleanup | 6.5.0 | 6.6.0 | +| Dec 2005 | CT#30 | CP-050611 | 095 | 1 | Removal of overhead in Private Identities handling in RTR | 6.6.0 | 6.7.0 | +| Dec 2005 | CT#30 | CP-050611 | 098 | 1 | Incorrect Definition of Supported-Applications AVP | 6.6.0 | 6.7.0 | +| Jan 2006 | | | | | Rel-7 version was created because of ETSI TISPAN references. | 6.7.0 | 7.0.0 | +| Mar 2006 | CT#31 | CP-060084 | 0099 | - | Supported Features Text missing | 7.0.0 | 7.1.0 | +| Jun 2006 | CT#32 | CP-060302 | 0108 | - | S-CSCF reselection removal | 7.1.0 | 7.2.0 | +| Jun 2006 | CT#32 | CP-060308 | 0110 | 3 | Definition of new Feature for Cx | 7.1.0 | 7.2.0 | +| Sep 2006 | CT#33 | CP-060417 | 0114 | 3 | AS originating requests on behalf of a user | 7.2.0 | 7.3.0 | +| Sep 2006 | CT#33 | CP-060405 | 0118 | 2 | Correction of discovery of supported features in Sh and Cx | 7.2.0 | 7.3.0 | +| Sep 2006 | CT#33 | CP-060417 | 0119 | 1 | Sharing feature support information between command pairs | 7.2.0 | 7.3.0 | +| Dec 2006 | CT#34 | CP-060566 | 0124 | 1 | Optimization of handling of Wildcarded PSIs | 7.3.0 | 7.4.0 | +| Mar 2007 | CT#35 | CP-070020 | 0125 | 1 | M-bit in SupportedFeatures AVP | 7.4.0 | 7.5.0 | +| Sep 2007 | CT#37 | CP-070520 | 0129 | - | Misalignment of Mandatory Items in the MAR | 7.5.0 | 7.6.0 | +| Nov 2007 | CT#38 | CP-070744 | 0132 | 6 | Add alias as a new feature | 7.6.0 | 7.7.0 | +| Nov 2007 | CT#38 | CP-070755 | 0130 | 4 | Updates to 29.229 for Digest on the Cx interface | 7.7.0 | 8.0.0 | +| Mar 2008 | CT#39 | CP-080022 | 0138 | 2 | Update 29.229 for Supporting NASS-Bundled-Authentication | 8.0.0 | 8.1.0 | +| Mar 2008 | CT#39 | CP-080019 | 0139 | - | SIP Digest password push | 8.0.0 | 8.1.0 | +| Mar 2008 | CT#39 | CP-080019 | 0141 | 2 | Wildcarded Public User Identities | 8.0.0 | 8.1.0 | +| Jun 2008 | CT#40 | CP-080261 | 0145 | 1 | Correction to the behavior of the HSS defined in the SiFC feature | 8.1.0 | 8.2.0 | +| Jun 2008 | CT#40 | CP-080261 | 0146 | 2 | Realm and Host to be used for Charging | 8.1.0 | 8.2.0 | +| Sep 2008 | CT#41 | CP-080456 | 0149 | 1 | Emergency Public User Identity Removal | 8.2.0 | 8.3.0 | +| Sep 2008 | CT#41 | CP-080460 | 0155 | 1 | Support of "Loose-Route" indication from HSS | 8.2.0 | 8.3.0 | +| Sep 2008 | CT#41 | CP-080463 | 0156 | 1 | Cx Impacts of IMS Restoration Procedures | 8.2.0 | 8.3.0 | +| Sep 2008 | CT#41 | CP-080463 | 0158 | - | Add IMS Restoration as a new feature | 8.2.0 | 8.3.0 | +| Sep 2008 | CT#41 | CP-080463 | 0159 | 1 | Addition of Registered Private Identities in SAA | 8.2.0 | 8.3.0 | +| Sep 2008 | CT#41 | CP-080460 | 0160 | 1 | Add Assigned S-CSCF name to SAA | 8.2.0 | 8.3.0 | +| Dec 2008 | CT#42 | CP-080708 | 0163 | - | Removal of Digest Domain | 8.3.0 | 8.4.0 | +| Dec 2008 | CT#42 | CP-080708 | 0166 | 2 | Diameter Proxy Agent - an alternative User Identity to HSS resolution mechanism | 8.3.0 | 8.4.0 | +| Mar 2009 | CT#43 | CP-090026 | 0167 | - | Multiple Registrations in Registration | 8.4.0 | 8.5.0 | + +| | | | | | | | | +|----------|-------|-----------|------|---|-------------------------------------------------------------------------------|--------|--------| +| Mar 2009 | CT#43 | CP-090026 | 0168 | 1 | Restoration Information for Multiple Registrations | 8.4.0 | 8.5.0 | +| Mar 2009 | CT#43 | CP-090026 | 0169 | | Update for Restoration | 8.4.0 | 8.5.0 | +| Mar 2009 | CT#43 | CP-090051 | 0170 | 1 | Definition of Server-Assignment-Type values in Cx | 8.4.0 | 8.5.0 | +| Mar 2009 | CT#43 | CP-090028 | 0171 | | Support for GPRS IMS Bundled Authentication (GIBA) in Cx | 8.4.0 | 8.5.0 | +| Mar 2009 | CT#43 | CP-090025 | 0172 | | Use of canonical form for SIP URI/tel URI in Cx interface | 8.4.0 | 8.5.0 | +| Mar 2009 | CT#43 | CP-090026 | 0175 | 1 | Comma separated list for Path, Contact and Record-Route AVPs | 8.4.0 | 8.5.0 | +| Jun 2009 | CT#44 | CP-090484 | 0176 | 2 | Contact storage in reg event subscription | 8.5.0 | 8.6.0 | +| Jun 2009 | CT#44 | CP-090303 | 0177 | 1 | Comma separated list for path AVP | 8.5.0 | 8.6.0 | +| Sep | CT#45 | CP-090526 | 0181 | | Dx over SCTP | 8.6.0 | 8.7.0 | +| Dec 2009 | CT#46 | CP-090784 | 0182 | 2 | SIP Digest AVP Flag Settings | 8.7.0 | 8.8.0 | +| Dec 2009 | CT#46 | CP-090781 | 0185 | 1 | Unregistered user clarification | 8.7.0 | 8.8.0 | +| Dec 2009 | CT#46 | CP-090778 | 0188 | 2 | Session-Priority AVP | 8.7.0 | 8.8.0 | +| Dec 2009 | CT#46 | CP-091030 | 0189 | | Validity of Feature Bit Value in Feature-List AVP | 8.7.0 | 8.8.0 | +| Dec 2009 | CT#46 | | | | Upgraded unchanged from Rel-8 | 8.8.0 | 9.0.0 | +| Mar 2010 | CT#47 | CP-100239 | 0195 | 1 | Wildcarded Public Identity | 9.0.0 | 9.1.0 | +| Mar 2010 | CT#47 | CP-100031 | 0199 | | Wildcarded Public Identities handling | 9.0.0 | 9.1.0 | +| Jun 2010 | CT#48 | CP-100412 | 0205 | 1 | Digest AVPs wrongly defined | 9.1.0 | 9.2.0 | +| Sep 2010 | CT#49 | CP-100447 | 0207 | 2 | Wildcarded Identities handling | 9.2.0 | 9.3.0 | +| Sep 2010 | CT#49 | CP-100442 | 0209 | 2 | Mandatory and optional capabilities handling | 9.2.0 | 9.3.0 | +| Sep 2010 | CT#49 | CP-100442 | 0212 | | Reference to SCTP IETF RFC obsolete | 9.2.0 | 9.3.0 | +| Sep 2010 | CT#49 | CP-100463 | 0213 | 2 | Restoration Data Backup | 9.2.0 | 9.3.0 | +| Sep 2010 | CT#49 | CP-100447 | 0216 | | Encoding of Framed-IPv6-Prefix AVP | 9.2.0 | 9.3.0 | +| 2011-03 | - | - | - | - | Update to Rel-10 version (MCC) | 9.3.0 | 10.0.0 | +| Jun 2011 | CT#52 | CP-110349 | 0224 | 2 | Handling of RTR for Emergency Registration | 10.0.0 | 10.1.0 | +| Jun 2011 | CT#52 | CP-110349 | 0227 | | Error in assignment type for backward compatibility scenarios | 10.0.0 | 10.1.0 | +| Jun 2011 | CT#52 | CP-110349 | 0230 | | User-Authorization-Type AVP error in description | 10.0.0 | 10.1.0 | +| Sep 2011 | CT#53 | CP-110566 | 0233 | 1 | Privileged sender | 10.1.0 | 10.2.0 | +| Dec 2011 | CT#54 | CP-110781 | 0240 | 1 | Restoration of Wildcarded-IMPU AVP | 10.2.0 | 10.3.0 | +| Dec 2011 | CT#54 | CP-110812 | 0235 | 2 | Server Assignment Type AVP definition | 10.3.0 | 11.0.0 | +| Sep 2012 | CT#57 | CP-120440 | 0247 | 1 | Emergency registrations do not affect registration status | 11.0.0 | 11.1.0 | +| Dec 2012 | CT#58 | CP-120743 | 0251 | 2 | PSI direct routing with restoration procedures | 11.1.0 | 11.2.0 | +| Mar 2013 | CT#59 | CP-130011 | 0258 | 1 | Originating-request AVP in LIR | 11.2.0 | 11.3.0 | +| Jun 2013 | CT#60 | CP-130374 | 0260 | 1 | Supported-Feature AVP carries list of features specific to the Application-ID | 11.3.0 | 11.4.0 | +| Sep 2015 | CT#69 | CP-150428 | 0278 | - | SIP-Auth-Data-Item sub AVPs clarifications | 11.4.0 | 11.5.0 | \ No newline at end of file diff --git a/marked/Rel-11/29_series/29231/raw.md b/marked/Rel-11/29_series/29231/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..0f59b9bd88448836709ce273a6056fa4a2ae15d1 --- /dev/null +++ b/marked/Rel-11/29_series/29231/raw.md @@ -0,0 +1,749 @@ + + + + + + +# Contents + +| | | +|--------------------------------------------------------------------------------------------------------------------------------------------------|----| +| Foreword ..... | 5 | +| 1 Scope..... | 6 | +| 2 References..... | 6 | +| 3 Definitions, symbols and abbreviations ..... | 7 | +| 3.1 Definitions..... | 7 | +| 3.2 Symbols..... | 7 | +| 3.3 Abbreviations ..... | 8 | +| 4 Protocols..... | 8 | +| 4.1 Introduction ..... | 8 | +| 4.2 Call control protocol (Nc interface) ..... | 9 | +| 4.3 Resource control protocol (G)MSC and MGW (Mc Interface) ..... | 9 | +| 4.4 Bearer Framing Protocol between MGWs (Nb interface) ..... | 10 | +| 4.5 Signalling Transport..... | 10 | +| 4.5.1 Call Control protocols ..... | 10 | +| 4.5.2 Resource control protocol (G)MSC and MGW (Mc Interface) ..... | 10 | +| 4.5.3 IP Transport between MGWs (Nb interface) ..... | 10 | +| 4.6 Payload Types ..... | 10 | +| 5 Amendments and Endorsements to Referenced Specifications ..... | 11 | +| 5.1 ITU-T Q.1912.5 (Interworking between Session Initiation Protocol (SIP) and Bearer Independent Call Control protocol or ISDN User Part) ..... | 11 | +| 5.2 IETF RFC 2046 (Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types)..... | 11 | +| 5.3 IETF RFC 4566 (SDP: Session Description Protocol) ..... | 11 | +| 5.4 IETF RFC 3966 (The tel URI for Telephone Numbers)..... | 12 | +| 5.5 IETF RFC 2976 (The SIP INFO method)..... | 12 | +| 5.6 IETF RFC 3204 (MIME media types for ISUP and QSIG Objects) ..... | 12 | +| 5.7 IETF RFC 3261(SIP: Session Initiation Protocol)..... | 12 | +| 5.8 IETF RFC 3262 (Reliability of Provisional Responses in the Session Initiation Protocol) ..... | 13 | +| 5.9 IETF RFC 3264 (An Offer/Answer Model with the Session Description Protocol) ..... | 13 | +| 5.9.1 Multicast Streams ..... | 13 | +| 5.9.2 3GPP Node Generating the Offer ..... | 13 | +| 5.9.3 3GPP Node Generating the Answer ..... | 13 | +| 5.9.4 3GPP Node as Offerer Processing of the Answer ..... | 13 | +| 5.9.5 Modifying the session..... | 14 | +| 5.9.6 Unspecified Connection Address ..... | 14 | +| 5.10 IETF RFC 3311 (The Session Initiation Protocol (SIP) UPDATE Method)..... | 14 | +| 5.11 IETF RFC 3312 (Integration of Resource Management and Session Initiation Protocol) ..... | 14 | +| 5.12 IETF RFC 3323 (A Privacy Mechanism for the Session Initiation Protocol) ..... | 14 | +| 5.13 IETF RFC 3325 (Private Extensions to the Session Initiation Protocol (SIP) for Network Asserted Identity within Trusted Networks) ..... | 15 | +| 5.14 IETF RFC 3326 (The Reason Header Field for the Session Initiation Protocol) ..... | 15 | +| 5.15 IETF RFC 4028 (Session Timers in the Session Initiation Protocol) ..... | 15 | +| 5.16 IETF RFC 4960 (Stream Control Transmission Protocol)..... | 15 | +| 5.17 Void..... | 15 | +| 5.18 IETF RFC 4168 (The Stream Control Transmission Protocol (SCTP) as a Transport for the Session Initiation Protocol) ..... | 15 | +| 5.19 IETF RFC 791 (Internet Protocol, Version 4)..... | 16 | +| 5.20 IETF RFC 2460 (Internet Protocol, Version 6)..... | 16 | +| 5.21 IETF RFC 4715 (The Integrated Services Digital Network (ISDN) Subaddress Encoding Type for tel URI)..... | 16 | +| 5.22 IETF RFC 4320 (Actions Addressing Identified Issues with the Session Initiation Protocol's (SIP) Non-INVITE Transaction) ..... | 16 | +| 5.23 IETF RFC 5079 (Rejecting Anonymous Requests in the Session Initiation Protocol (SIP)) ..... | 16 | +| 6 3GPP Extensions..... | 17 | +| 6.1 Codec Negotiation..... | 17 | +| 6.1.1 Encoding of 3GPP_OoBTC_Indicator ..... | 17 | + +| | | | +|-------------------------------|-------------------------------------------------------------|-----------| +| 6.1.2 | Encoding of SDP answer including 3GPP OoBTC Indicator ..... | 17 | +| 6.2 | MGW Identifier..... | 17 | +| 6.2.1 | Semantic and Usage of the MGW_Identifier ..... | 17 | +| 6.2.2 | Encoding of MGW_Identifier ..... | 17 | +| 6.2.3 | Procedures related to MGW_Identifier ..... | 18 | +| 6.3 | Additional MGW Ids..... | 18 | +| 6.3.1 | Semantic and Usage of the Additional_MGW_Ids ..... | 18 | +| 6.3.2 | Encoding of Additional_MGW_Ids ..... | 18 | +| 6.3.3 | Procedures related to Additional_MGW_Ids ..... | 18 | +| Annex A (informative): | IANA Registration of OoBTC Indicator ..... | 19 | +| A.1 | Introduction ..... | 19 | +| A.2 | Contact name, email address, and telephone number ..... | 19 | +| A.3 | Attribute Name (as it will appear in SDP) ..... | 19 | +| A.4 | Long-form Attribute Name in English ..... | 19 | +| A.5 | Type of Attribute..... | 19 | +| A.6 | Is Attribute Value subject to the Charset Attribute? ..... | 19 | +| A.7 | Purpose of the attribute ..... | 19 | +| A.8 | Appropriate Attribute Values for this Attribute ..... | 19 | +| Annex B (informative): | IANA Registration of MGW Identifier ..... | 20 | +| B.1 | Introduction ..... | 20 | +| B.2 | Contact name, email address, and telephone number ..... | 20 | +| B.3 | Attribute Name (as it will appear in SDP) ..... | 20 | +| B.4 | Long-form Attribute Name in English ..... | 20 | +| B.5 | Type of Attribute..... | 20 | +| B.6 | Is Attribute Value subject to the Charset Attribute? ..... | 20 | +| B.7 | Purpose of the attribute ..... | 20 | +| B.8 | Appropriate Attribute Values for this Attribute ..... | 20 | +| Annex C (informative): | IANA Registration of Additional MGW Ids..... | 20 | +| C.1 | Introduction ..... | 20 | +| C.2 | Contact name, email address, and telephone number ..... | 21 | +| C.3 | Attribute Name (as it will appear in SDP) ..... | 21 | +| C.4 | Long-form Attribute Name in English ..... | 21 | +| C.5 | Type of Attribute..... | 21 | +| C.6 | Is Attribute Value subject to the Charset Attribute? ..... | 21 | +| C.7 | Purpose of the attribute ..... | 21 | +| C.8 | Appropriate Attribute Values for this Attribute ..... | 21 | +| Annex D (informative): | Change history..... | 22 | + +# --- Foreword + +This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +# --- 1 Scope + +The present document describes the protocols to be used when SIP-I is optionally used as call control protocol in a 3GPP CS core network on Nc interface, see 3GPP TS 23.231 [1]. The SIP-I protocol operates between (G)MSC servers. The SIP-I architecture consists of a number of protocols. The following types of protocols are described: call control protocol, resource control protocols and user plane protocol for this architecture. The architecture complies with the requirements imposed by 3GPP TS 23.231 [1] and TS 23.153 [2]. + +Interworking of SIP-I on Nc to external networks is described by TS 29.235 [3]. + +The present document is valid for a 3rd generation PLMN (UMTS) complying with Release 8 and later. + +# --- 2 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. +- For a specific reference, subsequent revisions do not apply. +- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. + +- [1] 3GPP TS 23.231: "SIP-I based Circuit Switched Core Network ; Stage 2". +- [2] 3GPP TS 23.153: "Out of Band Transcoder Control; Stage 2". +- [3] 3GPP TS 29.235: "Interworking between the 3GPP CS domain with SIP-I as signalling protocol and other networks". +- [4] ITU-T Recommendation Q.1912.5: "Interworking between Session Initiation Protocol (SIP) and Bearer Independent Call Control protocol or ISDN User Part". +- [5] IETF RFC 2046: "Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types". +- [6] IETF RFC 3966: "The tel URI for Telephone Numbers". +- [7] IETF RFC 2976: "The SIP INFO method". +- [8] IETF RFC 3204: "MIME media types for ISUP and QSIG Objects". +- [9] IETF RFC 3261: "SIP: Session Initiation Protocol". +- [10] IETF RFC 3262: "Reliability of Provisional Responses in the Session Initiation Protocol (SIP)". +- [11] IETF RFC 3264: "An Offer/Answer Model with the Session Description Protocol (SDP)". +- [12] IETF RFC 3311: "The Session Initiation Protocol (SIP) UPDATE Method". +- [13] IETF RFC 3312: "Integration of Resource Management and Session Initiation Protocol (SIP)". +- [14] IETF RFC 3323: "A Privacy Mechanism for the Session Initiation Protocol (SIP)". +- [15] IETF RFC 3325: "Private Extensions to the Session Initiation Protocol (SIP) for Network Asserted Identity within Trusted Networks". +- [16] IETF RFC 3326: "The Reason Header Field for the Session Initiation Protocol (SIP)". +- [17] IETF RFC 4566: "SDP: Session Description Protocol". + +- [18] 3GPP TS 29.232: "Media Gateway Controller (MGC) - Media Gateway (MGW) interface; Stage 3". +- [19] 3GPP TS 29.415: "Core network Nb data transport and transport signalling". +- [20] 3GPP TS 29.414: "Core Network Nb data transport and transport signalling". +- [21] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications". +- [22] IETF RFC 3389: "Real-time Transport Protocol (RTP) Payload for Comfort Noise". +- [23] IETF RFC 4733: "RTP Payload for DTMF Digits, Telephony Tones and Telephony Signals". +- [24] IETF RFC 4028: "Session Timers in the Session Initiation Protocol (SIP)". +- [25] IETF RFC 4960: "Stream Control Transmission Protocol". +- [26] Void +- [27] IETF RFC 4168: "The Stream Control Transmission Protocol (SCTP) as a Transport for the Session Initiation Protocol (SIP)". +- [28] IETF RFC 5407: "Example Call Flows of Race Conditions in the Session Initiation Protocol (SIP)". +- [29] IETF RFC 791: "Internet Protocol (IP)". +- [30] IETF RFC 2460: "Internet Protocol, Version 6 (IPv6)". +- [31] IETF RFC 3550: "RTP: A Transport Protocol for Real-Time Applications". +- [31] 3GPP TS 26.102: "Mandatory speech codec; Adaptive Multi-Rate (AMR) speech codec;Interface to Iu, Uu and Nb". +- [32] 3GPP TS 26.103: "Speech codec list for GSM and UMTS". +- [33] 3GPP TS 23.003: "Numbering, addressing and identification". +- [34] IETF RFC 4715: " The Integrated Services Digital Network (ISDN) Subaddress Encoding Type for tel URI ". +- [35] IETF RFC 4320: "Actions Addressing Identified Issues with the Session Initiation Protocol's (SIP) Non-INVITE Transaction". +- [36] IETF RFC 5079: "Rejecting Anonymous Requests in the Session Initiation Protocol (SIP)". + +# --- 3 Definitions, symbols and abbreviations + +## 3.1 Definitions + +## 3.2 Symbols + +For the purposes of the present document, the following symbols apply: + +| | | +|----|-----------------------------------------------------| +| Nc | Interface between the(G)MSC servers. | +| Mc | Interface between the server and the media gateway. | +| Nb | Interface between media gateways (MGW). | + +## 3.3 Abbreviations + +For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [21] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in 3GPP TR 21.905 [21]. + +| | | +|-------|----------------------------------------| +| BCU | Bearer Control Unit | +| BICC | Bearer Independent Call Control | +| MGC | Media Gateway Controller | +| MIME | Multi-purpose Internet Mail Extensions | +| OoBTC | Out of Band Transcoder Control | + +# --- 4 Protocols + +## 4.1 Introduction + +Implementations providing any of the interfaces or protocols identified in the subclauses below shall implement the requirements of the specifications identified in those subclauses. + +## 4.2 Call control protocol (Nc interface) + +**Table 4.2.1: Call Control Protocol Specifications** + +| Identification | Protocol Name | Amendments and Endorsements to referenced specifications | Support | +|--------------------|-----------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------|-----------| +| Q.1912.5 [4] | Interworking between Session Initiation Protocol (SIP) and Bearer Independent Call Control protocol or ISDN User Part | See Clause 5.1 | Mandatory | +| IETF RFC 2046 [5] | Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types | See Clause 5.2 | Mandatory | +| IETF RFC 3966 [6] | URLs for Telephone Calls | See Clause 5.4 | Mandatory | +| IETF RFC 2976 [7] | The SIP INFO Method | See Clause 5.5 | Mandatory | +| IETF RFC 3204 [8] | MIME media types for ISUP and QSIG Objects | See Clause 5.6 | Mandatory | +| IETF RFC 3261 [9] | SIP: Session Initiation Protocol | See Clause 5.7 | Mandatory | +| IETF RFC 3262 [10] | Reliability of Provisional Responses in the Session Initiation Protocol (SIP) | See Clause 5.8 | Mandatory | +| IETF RFC 3264 [11] | An Offer/Answer Model with the Session Description Protocol (SDP) | See Clause 5.9 | Mandatory | +| IETF RFC 3311 [12] | The Session Initiation Protocol UPDATE Method | See Clause 5.10 | Mandatory | +| IETF RFC 3312 [13] | Integration of Resource Management and Session Initiation Protocol (SIP) | See Clause 5.11 | Mandatory | +| IETF RFC 3323 [14] | A Privacy Mechanism for the Session Initiation Protocol (SIP) | See Clause 5.12 | Mandatory | +| IETF RFC 3325 [15] | Private Extensions to the Session Initiation Protocol (SIP) for Asserted Identity within Trusted Networks | See Clause 5.13 | Mandatory | +| IETF RFC 3326 [16] | The Reason Header Field for the Session Initiation Protocol (SIP) | See Clause 5.14 | Mandatory | +| IETF RFC 4566 [17] | SDP: Session Description Protocol | See Clause 5.3 | Mandatory | +| IETF RFC 4028 [24] | Session Timers in the Session Initiation Protocol (SIP) | See Clause 5.15 | Optional | +| IETF RFC 4715 [34] | The Integrated Services Digital Network (ISDN) Subaddress Encoding Type for tel URI | See Clause 5.21 | Optional | +| IETF RFC 4320 [35] | Actions Addressing Identified Issues with the Session Initiation Protocol's (SIP) Non-INVITE Transaction | See Clause 5.22 | Mandatory | +| IETF RFC 5079 [36] | Rejecting Anonymous Requests in the Session Initiation Protocol (SIP) | See Clause 5.23 | Optional | + +## 4.3 Resource control protocol (G)MSC and MGW (Mc Interface) + +**Table 4.3.1: Resource Control Protocol Specifications** + +| Identification | Protocol Name | Amendments and Endorsements to referenced specifications | Support | +|--------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------|----------------------------------------------------------|-----------| +| 3GPP TS 29.232. [18] | Media Gateway Controller (MGC) – Media Gateway (MGW) Interface; Stage 3 | None (NOTE) | Mandatory | +| NOTE: IPv4 (IETF RFC 791 [29]) shall be supported on the Mc interface. IPv6 (IETF RFC 2460 [30]) may be supported. | | | | + +## 4.4 Bearer Framing Protocol between MGWs (Nb interface) + +**Table 4.4.1: Framing Protocol Specifications** + +| Identification | Protocol Name | Amendments and Endorsements to referenced specifications | Support | +|------------------------------------------------|------------------------------------------------------|----------------------------------------------------------|-----------| +| IETF RFC 3550[31] | RTP: A Transport Protocol for Real-Time Applications | None | Mandatory | +| NOTE: Further specified by 3GPP TS 29.414 [20] | | | | + +## 4.5 Signalling Transport + +### 4.5.1 Call Control protocols + +**Table 4.5.1.1: Call Control Signalling Transport** + +| Identification | Protocol Name | Amendments and Endorsements to referenced specifications | Support | +|--------------------|----------------------------------------------------------------------------------------------------------|----------------------------------------------------------|-----------| +| IETF RFC 791 [29] | Internet Protocol, Version 4 (IPv4) | See clause 5.19 | Mandatory | +| IETF RFC 2460 [30] | Internet Protocol, Version 6 (IPv6)" | See clause 5.20 | Optional | +| IETF RFC 4960 [25] | Stream Control Transmission Protocol | See clause 5.16 | Mandatory | +| IETF RFC 4168 [27] | The Stream Control Transmission Protocol (SCTP) as a Transport for the Session Initiation Protocol (SIP) | See clause 5.18 | Mandatory | + +### 4.5.2 Resource control protocol (G)MSC and MGW (Mc Interface) + +**Table 4.5.2.1: Resource Control Signalling Transport** + +| Identification | Protocol Name | Amendments and Endorsements to referenced specifications | Support | +|---------------------|------------------------------------------------------------------------|----------------------------------------------------------|-----------| +| 3GPP TS 29.232 [18] | Media Gateway Controller (MGC) – Media Gateway (MGW) Interface;Stage 3 | None | Mandatory | + +### 4.5.3 IP Transport between MGWs (Nb interface) + +**Table 4.5.3.1: Nb Interface Signalling Transport** + +| Identification | Protocol Name | Amendments and Endorsements to referenced specifications | Support | +|---------------------|---------------------------------------------------------|----------------------------------------------------------|-----------| +| 3GPP TS 29.414 [20] | Core Network Nb Data Transport and Transport Signalling | None | Mandatory | + +## 4.6 Payload Types + +The details of which payload types shall be supported for the SIP-I application are defined in 3GPP TS 26.102 [31] and the RTP attributes for each specific codecs are defined in 3GPP TS 26.103 [32]. + +# 5 Amendments and Endorsements to Referenced Specifications + +## 5.1 ITU-T Q.1912.5 (Interworking between Session Initiation Protocol (SIP) and Bearer Independent Call Control protocol or ISDN User Part) + +Only Profile C shall apply. + +## 5.2 IETF RFC 2046 (Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types) + +The "multipart" MIME type with the sub-type of "mixed" shall be supported as per IETF RFC 2046 [5] to allow exchange of multiple bodies in a single SIP message (e.g. initial INVITE message with ISUP IAM encapsulation and SDP bodies) between (G)MSC-Servers. Nested MIME message is not supported in the SIP-I based Nc interface. + +The following MIME types only shall be supported in the SIP-I based Nc interface: + +- The "application" MIME type as per IETF RFC 2046 [5] with the sub-type of "ISUP" as per IETF RFC 3204 [8] to allow exchange of ISUP encapsulation in SIP messages between (G)MSC-Servers. +- The "application" MIME type as per IETF RFC 2046 [5] with the sub-type of "SDP" as per IETF RFC 4566 [17] to allow exchange of SDP in SIP messages between (G)MSC-Servers. + +## 5.3 IETF RFC 4566 (SDP: Session Description Protocol) + +The following SDP properties are described for SIP-I call control procedures; use of SDP within H.248 MGW control protocol interface is described in the relevant profile specification, e.g. 3GPP TS 29.232 [18]. + +**Table 5.3.1: Support of SDP Fields** + +| field | Meaning | Support | Comments | +|------------|--------------------------|-------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| v | Protocol Version | Mandatory | The value shall be "v=0" | +| o | Origin | Mandatory | | +| s | Session Name | Mandatory | | +| c | Connection Data | Mandatory | | +| t | Timing | Mandatory | The value shall be "t=0 0" | +| a | Attributes | Conditional | See table 5.3.2. | +| m | Media Descriptions | Mandatory | | +| b=RS, b=RR | RTCP bandwidth modifiers | Conditional | A (G)MSC wishing to deactivate RTCP or using RTCP only to negotiate the use of RTP bearer multiplexing and RTP header compression (see 3GPP TS 29.414 [20]) shall set the RTCP bandwidth modifiers to zero.
If a (G)MSC receives SDP bandwidth modifiers for RTCP equal to zero, it should reply by setting its RTCP bandwidth using SDP bandwidth modifiers with values equal to zero. | + +NOTE: Fields not listed in the table may be ignored by the (G)MSC Server on receipt of the SDP. + +**Table 5.3.2: Support of Attributes** + +| attr | Meaning | Support | Comments | +|-------------|----------------------------|-------------------------|------------------------------------------------------------------------------------------| +| rtpmap | RTP map | Conditional | Mandatory for dynamic payload type and optional for static payload type. | +| recvonly | Receive only | Mandatory | | +| sendrecv | Send and receive | Mandatory | | +| sendonly | Send only | Mandatory | | +| inactive | Inactive | Mandatory | | +| fmtp | format specific parameters | Conditional | It is dependent upon the payload type if format specific parameters are required or not. | +| maxptime | Maximum packet size in ms | See 3GPP TS 26.102 [31] | | +| ptime | Packetisation length | See 3GPP TS 26.102 [31] | | + +NOTE: Attributes not listed in the table may be ignored by the (G)MSC Server on receipt of the SDP. + +## 5.4 IETF RFC 3966 (The tel URI for Telephone Numbers) + +The Tel-URI, in both global and local telephone formats, shall be supported as defined in IETF RFC 3966 [6]. + +The "isub" parameter defined within IETF RFC 3966 [6] may be used to include the ISDN sub-address as may be required within the MSISDN. See 3GPP TS 23.003 [33]. When the "isub" parameter is present, the "isub-encoding" parameter defined within IETF RFC 4715 [34] shall be used to define the ISDN subaddress encoding type. The procedures specified within ITU-T Q.1912.5 [4] Annex B.5 for profile C shall be applied for Sub-addressing. + +## 5.5 IETF RFC 2976 (The SIP INFO method) + +The SIP INFO method shall be supported as per IETF RFC 2976 [7] to allow exchange of ISUP signalling between (G)MSC-Servers. The contents of the message body shall not be encrypted. The SIP INFO method shall not be used to carry any other kind of information, e.g. DTMF digits. + +## 5.6 IETF RFC 3204 (MIME media types for ISUP and QSIG Objects) + +Only ISUP Media Type is supported in the SIP-I based Nc interface, see ITU-T Q.1912.5 [4] Clause 5.4.1.2. + +The "version" parameter is used to signal the ISUP version, as per ITU-T Q.1912.5 [4], sub-clause 5.4.1.2. + +## 5.7 IETF RFC 3261(SIP: Session Initiation Protocol) + +SIP-I initial and any subsequent INVITEs shall always include SDP. + +3GPP SIP-I entities shall apply loose routing on SIP-I based Nc. + +SIP forking is not supported in the SIP-I Nc interface. + +Race conditions for call clearing should be solved as described in clause 3.1.2 of the IETF RFC 5407 [28]. + +Non-INVITE transaction shall be implemented as specified in subclause 5.22 of the present specification. + +## 5.8 IETF RFC 3262 (Reliability of Provisional Responses in the Session Initiation Protocol) + +IETF RFC 3262 [10] specifies an extension to SIP in order to provide reliable provisional response messages. As support for PRACK's is required for a SIP-I based Nc interface to support preconditions, the support of 100rel is mandatory for the 3GPP SIP-I profile on the Nc interface. + +Procedures in clauses 3 and 4 of IETF RFC 3262 [10] apply on the Nc interface according to the following rules: + +- A (G)MSC Server originating a SIP INVITE shall advertise its preference of provisional reliable responses via a SUPPORTED header containing the tag "100Rel". +- A (G)MSC Server receiving a SIP INVITE will receive a SUPPORTED header containing the tag "100rel" and shall include a REQUIRE header with tag "100rel" and RSeq header field when sending a response in the range 101-199. +- A (G)MSC Server receiving a response in the range 101-199 with a REQUIRE header present with tag "100rel" shall generate a PRACK request for this provisional response. + +Authentication procedures are not required to be supported for PRACK (and any other) messages. + +## 5.9 IETF RFC 3264 (An Offer/Answer Model with the Session Description Protocol) + +### 5.9.1 Multicast Streams + +Procedures in Clauses 5.2 and 6.2 of IETF RFC 3264 do not need to be supported. + +### 5.9.2 3GPP Node Generating the Offer + +Procedures in Clause 5.1 of IETF RFC 3264 apply with the following modifications: + +- An MSC-S initiating an offer with multiple speech codec payload types in one m-line shall apply the related procedures in Clause 9 of 3GPP TS 23.153 [2], in particular the following requirement from IETF RFC 3264 Clause 5.1 is overruled: + +*"Once the offerer has sent the offer, it MUST be prepared to receive media for any recvonly streams described by that offer. It MUST be prepared to send and receive media for any sendrecv streams in the offer, and send media for any sendonly streams in the offer (ofcourse, it cannot actually send until the peer provides an answerwith the needed address and port information)."* + +### 5.9.3 3GPP Node Generating the Answer + +Procedures in Clause 6 of IETF RFC 3264 apply with the following modifications: + +- If the 3GPP MSC-S terminating the codec negotiation supports multiple speech codec payload types it shall apply the related procedures in Clause 9 of 3GPP TS 23.153 [2]. It does not need to be prepared to receive media encoded by speech codec payload types within the answered Available Codec List (see Clause 6.1.1). + +### 5.9.4 3GPP Node as Offerer Processing of the Answer + +Procedures in Clause 7 of IETF RFC 3264 apply with the following modifications: + +- If the offering MSC supports multiple speech codecs and the MSC-S receives an answer with multiple speech codec payload types in one m-line, it shall apply the related procedures in Clause 9 of 3GPP TS 23.153 [2]. It does not need to be prepared to receive media encoded by speech codec payload types within the Available Codec List (see Clause 6.1.1) received in the answer. + +### 5.9.5 Modifying the session + +Procedures in Clause 8 of IETF RFC 3264 apply with the same modifications as described in Clauses 5.9.2, 5.9.3, and 5.9.4. + +### 5.9.6 Unspecified Connection Address + +The use of an "unspecified connection address" may be used during initial call establishment, for deferred MGW selection where no user plane connection has been seized by the Offerer. + +No further applications for the use of an "unspecified connection address" are defined in SIP-I on Nc. + +The "unspecified connection address" shall not be sent within a re-INVITE message. + +For IPv6 implementations the "unspecified connection address" shall be defined by a domain name within the ".invalid" DNS top-level domain. + +For IPv4 implementations if the "unspecified connection address" shall be defined by the IPv4 unspecified address (c= IN IP4 0.0.0.0). + +## 5.10 IETF RFC 3311 (The Session Initiation Protocol (SIP) UPDATE Method) + +The SIP UPDATE method shall be supported to allow updating of session parameters (media streams, codecs) during early and confirmed dialog, and allow the support of preconditions. + +The support of the UPDATE method shall be negotiated on SIP-I based Nc according to the following rules: + +- A (G)MSC Server originating a SIP INVITE request shall advertise its support of the UPDATE method via the ALLOW header listing the UPDATE method. +- A (G)MSC Server receiving a SIP INVITE request shall include an ALLOW header listing the UPDATE method when sending a response in the range 101-199. The MSC-S is then allowed to generate the UPDATE method, for the purpose of session modification during early dialog. In addition the MSC-S shall include an ALLOW header listing the UPDATE method when sending a 2xx final response. +- A (G)MSC Server receiving a response to a SIP INVITE request with an ALLOW header present listing the UPDATE method is then allowed to generate the UPDATE method. + +Authentication and Integrity protection procedures are not required to be supported for the UPDATE message. + +## 5.11 IETF RFC 3312 (Integration of Resource Management and Session Initiation Protocol) + +Precondition type QoS only shall be supported using the segmented status type (therefore end-to-end status type e.g. Clause 13.1 does not apply) and the strength-tag value "mandatory" for the local segment and the strength-tag value "optional" for the remote segment. Precondition tag may be included in either REQUIRE or SUPPORTED header; the use of the SUPPORTED header is a deviation from this RFC when the strength-tag contains a "mandatory" value. + +## 5.12 IETF RFC 3323 (A Privacy Mechanism for the Session Initiation Protocol) + +IETF RFC 3323 [14] provides privacy requirements and mechanisms for SIP. + +The Privacy header shall be supported to signal privacy of the P-Asserted-Identity and allow or restrict the presentation of the network asserted identity, as specified in 3GPP TS 23.231 [1]. The following privacy values may be used: header, none, critical, id. + +## 5.13 IETF RFC 3325 (Private Extensions to the Session Initiation Protocol (SIP) for Network Asserted Identity within Trusted Networks) + +IETF RFC 3325 [15] provides for the existence and trust of an asserted identity within a trust domain. It shall be supported on the SIP-I based Nc interface with the following modifications: + +- a (G)MSC Server shall consider that neighbouring (G)MSC Servers connected via a Nc interface are trusted; +- the P-Preferred-Identity header and related requirements shall not be used. + +## 5.14 IETF RFC 3326 (The Reason Header Field for the Session Initiation Protocol) + +The SIP Reason header provides a means of transporting SIP or ISUP/BICC cause value in the SIP message; this is especially useful in SIP message without encapsulated ISUP information. + +The SIP Reason header shall be supported as specified by IETF RFC 3326 [16] and by ITU-T Q.1912.5 [4] (as endorsed by sub-clause 5.1 of the present specification), with the following modifications: + +- a Reason header field containing a Q.850 cause value shall be added to the SIP CANCEL message sent by the (G)MSC Server if the value is known; if unknown, the Q.850 cause value 31 (normal unspecified) shall be sent. +- the header field shall not be protected by any integrity mechanism. + +## 5.15 IETF RFC 4028 (Session Timers in the Session Initiation Protocol) + +SIP session continuity may be supported through the use of SIP Session Timer as per IETF RFC 4028 [24] with the following amendments. + +- Clause 4 indicates that the minimum value of the *Session-Expires* header field should not be less than 30 minutes. Since the vast majority of mobile calls are significantly less than 30 minutes, it may be desirable to use a minimum *Session-Expires* of less than 30 minutes within the 3GPP CS core network. The RFC states that the value SHOULD NOT be less then 30 minutes. That statement is modified to "...MAY choose values of less than 30 minutes but greater than the absolute minimum of 90 seconds." +- Clause 8 "Proxy Behavior" is not applicable to MSC Servers. + +## 5.16 IETF RFC 4960 (Stream Control Transmission Protocol) + +See sub-clause 5.18. + +## 5.17 Void + +## 5.18 IETF RFC 4168 (The Stream Control Transmission Protocol (SCTP) as a Transport for the Session Initiation Protocol) + +SCTP shall be the transport protocol for a SIP-I based Nc interface as per IETF RFC 4168 [27]. + +Semi-permanent SCTP associations shall be established between peer 3GPP SIP-I entities, i.e. the SCTP associations shall remain up under normal circumstances. + +Local multi-homing should be supported. Remote multi-homing shall be supported. + +Multiple local SCTP endpoints may be supported. Multiple remote SCTP endpoints shall be supported. When multiple local or remote SCTP endpoints are configured, several simultaneous SCTP associations shall be supported between peer 3GPP SIP-I entities. + +Published IP addresses and ports for SCTP associations are supported as specified below: + +- The (G)MSC Server shall support SCTP association setup, where an SCTP association request is performed to a published IP address and port. +- The (G)MSC Server may initiate SCTP association requests from a local published IP address and port. +- The (G)MSC Server shall accept incoming SCTP association requests from remote published IP address and port. +- When two endpoints are configured for a specific SCTP association between two published IP addresses and ports, one endpoint shall be configured as "server" and the peer endpoint as the "client" with respect to SCTP association setup. + +NOTE: Published IP addresses or ports can be configured via O&M or they can be obtained through a DNS enquiry. + +Dynamically assigned ports for SCTP associations are supported as specified below: + +- The (G)MSC Server may initiate a SCTP association from an ephemeral (non-published) port. +- The (G)MSC Server shall accept incoming SCTP association requests from remote ephemeral (non-published) ports. + +## 5.19 IETF RFC 791 (Internet Protocol, Version 4) + +IPv4 (IETF RFC 791 [29]) shall be supported on the Nc interface. + +## 5.20 IETF RFC 2460 (Internet Protocol, Version 6) + +IPv6 (IETF RFC 2460 [30]) may be supported on the Nc interface. + +## 5.21 IETF RFC 4715 (The Integrated Services Digital Network (ISDN) Subaddress Encoding Type for tel URI) + +The "isub-encoding" parameter defined within IETF RFC 4715 [yy] shall be present and include the ISDN subaddress encoding type when the "isub" parameter of the Tel-URI is present as defined in Clause 5.4. + +## 5.22 IETF RFC 4320 (Actions Addressing Identified Issues with the Session Initiation Protocol's (SIP) Non-INVITE Transaction) + +The actions specified in clause 4 of the IETF RFC 4320 [35] shall be supported with following modifications: + +- Actions which are not applicable for SCTP transport are not required to be supported. +- Actions specified for proxy are not applicable to MSC-S. + +## 5.23 IETF RFC 5079 (Rejecting Anonymous Requests in the Session Initiation Protocol (SIP)) + +The response code 433 (Anonymity Disallowed) defined by IETF RFC 5079 [36] shall be supported on SIP-I on Nc. + +# --- 6 3GPP Extensions + +## 6.1 Codec Negotiation + +### 6.1.1 Encoding of 3GPP\_OoBTC\_Indicator + +3GPP OoBTC Indicator shall be encoded as the following media-level SDP attribute with the following syntax (ABNF definition): + +3GPP\_OoBTC\_Indicator = "a=3gOoBTC" + +No attribute values to this SDP attribute are defined in the present Release. If attribute values for the attribute are received, they shall be ignored. + +The SDP offer and SDP answer signalling procedures for OoBTC Indicator are described in Clause 9 of 3GPP TS 23.153 [2]. + +**Editor's Note: The 3GPP\_OoBTC\_Indicator will be registered at IANA.** + +### 6.1.2 Encoding of SDP answer including 3GPP OoBTC Indicator + +If the 3GPP OoBTC Indicator is included in an SDP answer, the corresponding SDP m-line shall be encoded as follows: + +- The first codec in the m-line (indicated by RTP payload type) shall indicate the Selected Codec. +- Any subsequent codecs in the m-line (indicated by RTP payload type), which are not of "auxiliary" payload type (see next bullet), shall indicate the Available Codec List (ACL) +- Codecs of "auxiliary" payload type, i.e. RTP Telephony Event payload type (IETF RFC 4733 [23]) or the comfort noise codec (IETF RFC 3389 [22]), may be included as the last codecs in the m-line (indicated by RTP payload type). + +## 6.2 MGW Identifier + +### 6.2.1 Semantic and Usage of the MGW\_Identifier + +The MGW\_Identifier shall be used to encode a MGW Identity as used for the optional "optimised MGW selection " and "deferred MGW selection" procedures in Clauses 4.4.2 and 4.4.3 of TS 23.231 [3]. + +Additional MGW identities may be proposed in the Additional\_MGW\_Ids attribute (see subclause 6.3) for the deferred MGW selection procedure. + +The support of the MGW\_Identifier attribute is only required for a (G)MSC Server that supports at least one of the optional "optimised MGW selection " and "deferred MGW selection" procedures. + +### 6.2.2 Encoding of MGW\_Identifier + +The MGW\_Identifier shall be encoded as the following "session-level" value attribute with the following syntax (ABNF definition): + +``` + +MGW_Identifier = "a=MGW_Identifier: " + + = Octet string containing any octet value except 0x00 (Nul), 0x0A (LF), and 0x0D (CR). +Values are to be interpreted as in ISO-10646 character set with UTF-8 encoding. + +``` + +NOTE: The sub-field may be encoded for example in the same manner as BCU-ID in BICC, i.e. 4 Octets for representing Network ID field and Local BCU-ID field. + + shall contain an operator-defined unique identifier for a MGW. + +Attribute values of the SDP MGW\_Identifier attribute shall not be subject to the SDP "charset" attribute. + +**Editor's Note: The MGW\_Identifier will be registered at IANA.** + +### 6.2.3 Procedures related to MGW\_Identifier + +Provided that the (G)MSC Server supports the MGW\_Identifier attribute, it shall apply the following procedures: + +- For the optimised MGW selection, the (G)MSC Server shall apply the MGW Identity related procedures in Clause 4.4.2 of TS 23.231 [3]. +- For the deferred MGW selection, the (G)MSC Server shall apply the MGW Identity related procedures in Clause 4.4.3 of TS 23.231 [3]. + +## 6.3 Additional MGW Ids + +### 6.3.1 Semantic and Usage of the Additional\_MGW\_Ids + +The Additional\_MGW\_Ids shall be used to encode a list of MGW Identities that may be proposed in addition to the MGW Identity signalled in the MGW\_Identifier (see subclause 6.2.1), as used for the optional "deferred MGW selection" procedure in clause 4.4.3 of 3GPP TS 23.231 [3]. + +The support of the Additional\_MGW\_Ids attribute is only required for a (G)MSC Server that supports the "deferred MGW selection" procedure. + +### 6.3.2 Encoding of Additional\_MGW\_Ids + +The Additional MGW Ids shall be encoded as the following "session-level" value attribute with the following syntax (ABNF definition): + +Additional\_MGW\_Ids = "a=Additional\_MGW\_Ids: , , ..." + + = *Octet string containing any octet value except 0x00 (Nul), 0x0A (LF), and 0x0D (CR). Values are to be interpreted as in ISO-10646 character set with UTF-8 encoding.* + +NOTE: The sub-field may be encoded for example in the same manner as BCU-ID in BICC, i.e. 4 Octets for representing Network ID field and Local BCU-ID field. + + shall contain an operator-defined unique identifier for a MGW. + +Attribute values of the SDP Additional\_MGW\_Ids attribute shall not be subject to the SDP "charset" attribute. + +**Editor's Note: The Additional\_MGW\_Ids will be registered at IANA.** + +### 6.3.3 Procedures related to Additional\_MGW\_Ids + +Provided that the (G)MSC Server supports the Additional MGW Ids attribute, it shall apply the following procedures: + +- For the deferred MGW selection, the (G)MSC Server shall apply the Deferred MGW Ids related procedures in clause 4.4.3 of TS 23.231 [3]. + +# --- Annex A (informative): IANA Registration of OoBTC Indicator + +## A.1 Introduction + +This Annex describes information required for the IANA registration of the OoBTC Indicator SDP attribute, as required according to Clause 8.2.4 of IETF RFC 4566 [17] + +## A.2 Contact name, email address, and telephone number + +3GPP Specifications Manager + +[3gppContact@etsi.org](mailto:3gppContact@etsi.org) + ++33 (0)492944200 + +## A.3 Attribute Name (as it will appear in SDP) + +3gOoBTC + +## A.4 Long-form Attribute Name in English + +3GPP Out-of-band Transcoder Control Indicator + +## A.5 Type of Attribute + +Media level + +## A.6 Is Attribute Value subject to the Charset Attribute? + +Not applicable, as no attribute values are defined. + +## A.7 Purpose of the attribute + +The semantics of the 3GPP OoBTC Indicator are defined in Clause 9.4 of 3GPP TS 23.153 [2]. + +## A.8 Appropriate Attribute Values for this Attribute + +No attribute values are defined. + +# --- Annex B (informative): IANA Registration of MGW Identifier + +## B.1 Introduction + +This Annex describes information required for the IANA registration of the MGW Identifier SDP attribute, as required according to Clause 8.2.4 of IETF RFC 4566 [17] + +## B.2 Contact name, email address, and telephone number + +3GPP Specifications Manager + +[3gppContact@etsi.org](mailto:3gppContact@etsi.org) + ++33 (0)492944200 + +## B.3 Attribute Name (as it will appear in SDP) + +MGW\_Identifier + +## B.4 Long-form Attribute Name in English + +Media GateWay Identifier + +## B.5 Type of Attribute + +Session level + +## B.6 Is Attribute Value subject to the Charset Attribute? + +No + +## B.7 Purpose of the attribute + +As defined in Clause 6.2.1 + +## B.8 Appropriate Attribute Values for this Attribute + +As defined in Clauses 6.2.2 and 6.2.3 + +# --- Annex C (informative): IANA Registration of Additional MGW Ids + +## C.1 Introduction + +This Annex describes information required for the IANA registration of the Additional MGW Ids SDP attribute, as required according to clause 8.2.4 of IETF RFC 4566 [17] + +## C.2 Contact name, email address, and telephone number + +3GPP Specifications Manager + +[3gppContact@etsi.org](mailto:3gppContact@etsi.org) + ++33 (0)492944200 + +## C.3 Attribute Name (as it will appear in SDP) + +Additional\_MGW\_Ids + +## C.4 Long-form Attribute Name in English + +Additional Media GateWay Identifiers + +## C.5 Type of Attribute + +Session level + +## C.6 Is Attribute Value subject to the Charset Attribute? + +No + +## C.7 Purpose of the attribute + +As defined in clause 6.3.1 + +## C.8 Appropriate Attribute Values for this Attribute + +As defined in clauses 6.3.2 and 6.3.3 + +# Annex D (informative): Change history + +| Change history | | | | | | | | +|----------------|---------|-----------|------|-----|--------------------------------------------------------------|--------|--------| +| Date | TSG # | TSG Doc. | CR | Rev | Subject/Comment | Old | New | +| CT#36 | | | | | Agreed as base version for further work | | 0.0.0 | +| 10/2007 | | | | | Output from CT4#36bis | 0.0.0 | 0.1.0 | +| 11/2007 | | | | | Output from CT4#37 | 0.1.0 | 0.2.0 | +| 11/2007 | | | | | Updated with missing contribution from Kobe | 0.2.0 | 0.2.1 | +| 02/2008 | | | | | Output from CT4#38 | 0.2.1 | 0.3.0 | +| 03/2008 | TSG #39 | | | | Agreed as information | 0.3.0 | 1.0.0 | +| 04/2008 | | | | | Output from CT4#38Bis | 1.0.0 | 1.1.0 | +| 05/2008 | | | | | Output from CT4#39 | 1.1.0 | 1.2.0 | +| 07/2008 | | | | | Output from CT4#39bis | 1.2.0 | 1.3.0 | +| 08/2008 | | | | | Output from CT4#40 | 1.3.0 | 1.4.0 | +| 09/2008 | TSG#41 | CP-080484 | | | V2.0.0 was presented for approval | 1.4.0 | 2.0.0 | +| 09/2008 | TSG#41 | CP-080484 | | | V2.0.0 was approved in CT#41 | 2.0.0 | 8.0.0 | +| 12/2008 | TSG#42 | CP-080686 | 0002 | | Correction on definition of MGW identifier | 8.0.0 | 8.1.0 | +| | | CP-080686 | 0004 | 1 | Clean-up of tables, text and references | | | +| | | CP-080686 | 0005 | 2 | SCTP Usage for SIP-I on Nc | | | +| | | CP-080686 | 0006 | 1 | Format of the unspecified connection address | | | +| | | CP-080686 | 0007 | 2 | Non-Support of SIP forking in SIP-I CSCN | | | +| | | CP-080686 | 0011 | | Removal of Re-INVITE without SDP | | | +| 03/2009 | TSG#43 | CP-090029 | 0012 | | Reference update for SCTP | 8.1.0 | 8.2.0 | +| 09/2009 | TSG#45 | CP-090529 | 0015 | 1 | SIP-I Support of IETF RFC 3966 Tel-URI for Telephone Numbers | 8.2.0 | 8.3.0 | +| | | CP-090529 | 0017 | 1 | Reference update – IETF RFC 5407 | | | +| | | CP-090529 | 0018 | 1 | Endorsement of IETF RFC 3325 – SIP Asserted Identity | | | +| | | CP-090529 | 0019 | 1 | Endorsement of IETF RFC 3323 - Privacy Mechanism for SIP | | | +| 2009-12 | - | - | - | - | Update to Rel-9 version (MCC) | 8.3.0 | 9.0.0 | +| 2010-03 | TSG#47 | CP-100018 | 0022 | 1 | Non-INVITE transaction: handling according to RFC 4320 | 9.0.0 | 9.1.0 | +| | | | 0024 | | Support of response code 433 Anonymity Disallowed | | | +| 2011-03 | TSG#51 | CP-110069 | 0025 | 1 | Deferred MGW selection | 9.1.0 | 10.0.0 | +| 2012-06 | - | - | - | - | Update to Rel-9 version (MCC) | 10.0.0 | 11.0.0 | \ No newline at end of file diff --git a/marked/Rel-11/29_series/29232/0779125369ae9c0108101b54fe2428bf_img.jpg b/marked/Rel-11/29_series/29232/0779125369ae9c0108101b54fe2428bf_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6e12346bea93f00c102acbcb7d3e8ddc30fe141b --- /dev/null +++ b/marked/Rel-11/29_series/29232/0779125369ae9c0108101b54fe2428bf_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6a7a116abebb0d3c92e247505e9b4ebe7192a49371cdb3aa47a8607708cfe412 +size 60307 diff --git a/marked/Rel-11/29_series/29232/11f18bf0233d812ad2604f88f3385d60_img.jpg b/marked/Rel-11/29_series/29232/11f18bf0233d812ad2604f88f3385d60_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..41f48ad5e4bad7e06c2ee27219118537d8ab9fb1 --- /dev/null +++ b/marked/Rel-11/29_series/29232/11f18bf0233d812ad2604f88f3385d60_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:49d2fb869f991535c9d26b78e6237c6ab7ebecc68aa22716f2ee0d4c5dcf894b +size 16820 diff --git a/marked/Rel-11/29_series/29232/7c57192c514175021e4560a1a46126c1_img.jpg b/marked/Rel-11/29_series/29232/7c57192c514175021e4560a1a46126c1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..72f8fb628cd3866c7288ef4da645c68a38c420e5 --- /dev/null +++ b/marked/Rel-11/29_series/29232/7c57192c514175021e4560a1a46126c1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f5cd08ccf44b0286a3f933e563811acdbebf5514a5b02811f7bd2181faaa0345 +size 22215 diff --git a/marked/Rel-11/29_series/29232/869c547c11ac7e123c51aba22289f2cd_img.jpg b/marked/Rel-11/29_series/29232/869c547c11ac7e123c51aba22289f2cd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..34e47a7e2059caa0c18bdfd530ecedf7515306d3 --- /dev/null +++ b/marked/Rel-11/29_series/29232/869c547c11ac7e123c51aba22289f2cd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9a2e042060bcd388e2619c97a75f8bd6feb280552f9f6007317d2870cff9e5aa +size 14738 diff --git a/marked/Rel-11/29_series/29232/d9638e837004a4e09dbbc50b8aecbd5f_img.jpg b/marked/Rel-11/29_series/29232/d9638e837004a4e09dbbc50b8aecbd5f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0b8b093d89a259e1d64a8f3b3fa73d1be766fb04 --- /dev/null +++ b/marked/Rel-11/29_series/29232/d9638e837004a4e09dbbc50b8aecbd5f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:dbd1727d66d1fc9a83f00de2bcd6fe414dd0e125b7aa45d788eb49db4d098100 +size 16229 diff --git a/marked/Rel-11/29_series/29232/f1de68a4cbb9b92a1c0ffd919bbd199c_img.jpg b/marked/Rel-11/29_series/29232/f1de68a4cbb9b92a1c0ffd919bbd199c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6cf97bd23c398bd455e7bde1587d8ff5eb277cbb --- /dev/null +++ b/marked/Rel-11/29_series/29232/f1de68a4cbb9b92a1c0ffd919bbd199c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:47429245aa20d4f2409f89adc80d2ae9d03826c48975b051aabf292ef247bb27 +size 21393 diff --git a/marked/Rel-11/29_series/29232/f43d225d8fed2845b8d7e5afecbfe636_img.jpg b/marked/Rel-11/29_series/29232/f43d225d8fed2845b8d7e5afecbfe636_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e9662257edb2896704b5aeec3a4c949555ffcfb4 --- /dev/null +++ b/marked/Rel-11/29_series/29232/f43d225d8fed2845b8d7e5afecbfe636_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:282def0270424bdfc3f7cc0a2d88ea062acdef6d53898fc27270b30bf800bede +size 54422 diff --git a/marked/Rel-11/29_series/29232/fa6d4c394c470c63bca4c15b3c6db58e_img.jpg b/marked/Rel-11/29_series/29232/fa6d4c394c470c63bca4c15b3c6db58e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7da117a65c8b5127de1e274d1c2fa92fa07d80a4 --- /dev/null +++ b/marked/Rel-11/29_series/29232/fa6d4c394c470c63bca4c15b3c6db58e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:597adcfac6df76a09f54fda81bbc67a7d458c80132204dbb4b611d37318e383b +size 20761 diff --git a/marked/Rel-11/29_series/29232/raw.md b/marked/Rel-11/29_series/29232/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..2e3ae00e071c8369649bea3319d1d9c78b250824 --- /dev/null +++ b/marked/Rel-11/29_series/29232/raw.md @@ -0,0 +1,5555 @@ + + + + +**Error:** + +**2** + +**Error: Reference source not** + +# Contents + +| | | +|---------------------------------------------------------------------------|----| +| Foreword..... | 9 | +| 1 Scope..... | 10 | +| 2 References..... | 10 | +| 3 Definitions, symbols and abbreviations..... | 13 | +| 3.1 Definitions..... | 13 | +| 3.2 Symbols..... | 13 | +| 3.3 Abbreviations..... | 13 | +| 4 UMTS capability set..... | 14 | +| 4.1 Profile Identification..... | 14 | +| 4.2 Profile Registration..... | 14 | +| 5 Naming conventions..... | 14 | +| 5.1 MGC/MGW naming conventions..... | 14 | +| 5.2 Termination names..... | 14 | +| 6 Topology descriptor..... | 14 | +| 7 Transaction timers..... | 15 | +| 8 Transport..... | 15 | +| 9 Multiple Virtual MG..... | 15 | +| 10 Formats and codes..... | 15 | +| 10.1 Signalling Objects..... | 15 | +| 10.2 SDP Media Parameters for RTP Terminations..... | 20 | +| 10.2.1 Speech Codecs..... | 20 | +| 10.2.2 DTMF..... | 20 | +| 10.2.3 Auxiliary Payloads..... | 20 | +| 10.2.3.1 Void..... | 20 | +| 10.2.3.2 Void..... | 20 | +| 10.2.3.3 Clearmode Codec..... | 20 | +| 10.2.3.4 Silence suppression and Comfort Noise..... | 20 | +| 10.2.3.5 CS Data Service..... | 20 | +| 10.2.3.5.1 CS Data Service with no Redundancy..... | 20 | +| 10.2.3.5.2 CS Data Service with Redundancy..... | 21 | +| 10.2.4 Other Payload Types..... | 21 | +| 11 Mandatory Support of SDP and H.248.1 annex C information elements..... | 22 | +| 12 General on Packages and Transactions..... | 23 | +| 13 BICC packages..... | 23 | +| 13.1 Mandatory BICC packages..... | 23 | +| 13.2 Optional BICC packages..... | 23 | +| 14 H.248 standard packages..... | 24 | +| 14.1 Call independent H.248 transactions..... | 24 | +| 14.1.1 MGW Out of service/Maintenance Locking..... | 25 | +| 14.1.2 MGW Communication Up..... | 25 | +| 14.1.3 MGW Restoration..... | 25 | +| 14.1.4 MGW Register..... | 26 | +| 14.1.5 MGW Re-register..... | 26 | +| 14.1.6 (G)MSC Server Ordered Re-register..... | 26 | +| 14.1.7 (G)MSC Server Restoration..... | 26 | +| 14.1.8 Termination Out-of-Service..... | 27 | +| 14.1.9 Termination Restoration..... | 27 | +| 14.1.10 Audit Value..... | 28 | +| 14.1.11 Audit Capability..... | 30 | +| 14.1.12 MGW Capability Change..... | 30 | + +| | | | +|----------|----------------------------------------------------|----| +| 14.1.13 | (G)MSC Server Out of Service..... | 30 | +| 14.1.14 | MGW Resource Congestion Handling - Activate..... | 31 | +| 14.1.15 | MGW Resource Congestion Handling - Indication..... | 31 | +| 14.1.16 | Continuity Check Tone..... | 31 | +| 14.1.17 | Continuity Check Verify..... | 32 | +| 14.1.18 | Continuity Check Response..... | 32 | +| 14.1.19 | Inactivity Timeout - Activate..... | 32 | +| 14.1.20 | Inactivity Timeout – Indication..... | 32 | +| 14.1.21 | Realm Availability Change – Activation..... | 33 | +| 14.1.22 | Realm Availability Change – Indication..... | 33 | +| 14.2 | Call related H.248 transactions..... | 34 | +| 14.2.1 | Change Flow Direction..... | 36 | +| 14.2.2 | Isolate Bearer Termination..... | 36 | +| 14.2.3 | Join Bearer Termination..... | 36 | +| 14.2.4 | Establish Bearer..... | 36 | +| 14.2.5 | Prepare Bearer..... | 37 | +| 14.2.6 | Change Through Connection..... | 39 | +| 14.2.7 | Activate Interworking Function..... | 39 | +| 14.2.8 | Release procedures..... | 39 | +| 14.2.8.1 | Release Bearer..... | 39 | +| 14.2.8.2 | Release Termination..... | 39 | +| 14.2.9 | Bearer Released..... | 40 | +| 14.2.10 | Bearer Established..... | 40 | +| 14.2.11 | Send Tone..... | 40 | +| 14.2.12 | Play Announcement..... | 40 | +| 14.2.13 | Send DTMF..... | 41 | +| 14.2.14 | Detect DTMF..... | 41 | +| 14.2.15 | Report DTMF..... | 41 | +| 14.2.16 | Announcement Completed..... | 41 | +| 14.2.17 | Activate Voice Processing Function..... | 41 | +| 14.2.18 | Reserve Circuit..... | 42 | +| 14.2.19 | Tunnel Information Up..... | 43 | +| 14.2.20 | Tunnel Information Down..... | 43 | +| 14.2.21 | Tone Completed..... | 43 | +| 14.2.22 | Stop Announcement..... | 43 | +| 14.2.23 | Stop Tone..... | 43 | +| 14.2.24 | Stop DTMF Detection..... | 43 | +| 14.2.25 | Stop DTMF..... | 43 | +| 14.2.26 | Confirm Char..... | 43 | +| 14.2.27 | Modify Char..... | 44 | +| 14.2.28 | Reserve Char..... | 44 | +| 14.2.29 | Bearer Modified..... | 44 | +| 14.2.30 | Bearer Modification Failed..... | 44 | +| 14.2.31 | TFO Activation..... | 44 | +| 14.2.32 | Optimal Codec and Distant List_Notify..... | 44 | +| 14.2.33 | Codec Modify..... | 45 | +| 14.2.34 | Distant Codec List..... | 45 | +| 14.2.35 | Command Rejected..... | 46 | +| 14.2.36 | Modify Bearer Characteristics..... | 46 | +| 14.2.37 | Protocol Negotiation Result..... | 47 | +| 14.2.38 | Rate Change..... | 47 | +| 14.2.39 | Bearer Modification Support..... | 47 | +| 14.2.40 | CTM report..... | 48 | +| 14.2.41 | Prepare IP transport..... | 48 | +| 14.2.42 | Modify IP transport address..... | 50 | +| 14.2.43 | Reserve Bearer Characteristics..... | 50 | +| 14.2.44 | Confirm Bearer Characteristics..... | 51 | +| 14.2.45 | Trace activation/deactivation..... | 51 | +| 14.2.46 | Trace Activation result notification..... | 52 | +| 14.2.47 | Emergency Call Indication..... | 52 | +| 14.2.48 | TFO status Notify..... | 54 | + +| | | | +|----------|-------------------------------------------------------------|----| +| 14.2.49 | TFO Status..... | 54 | +| 14.2.50 | Termination heartbeat indication..... | 54 | +| 14.2.51 | Reserve RTP Connection Point..... | 55 | +| 14.2.52 | Configure RTP Connection Point..... | 57 | +| 14.2.53 | Reserve and Configure RTP Connection Point..... | 59 | +| 14.2.54 | ECN Failure Indication..... | 61 | +| 14.2.55 | Media Inactivity Notification..... | 62 | +| 15 | UMTS packages..... | 63 | +| 15.1 | Mandatory UMTS packages..... | 63 | +| 15.1.1 | 3GUP package..... | 63 | +| 15.1.1.1 | Properties..... | 63 | +| 15.1.1.2 | Events..... | 65 | +| 15.1.1.3 | Signals..... | 65 | +| 15.1.1.4 | Statistics..... | 65 | +| 15.1.1.5 | Procedures..... | 65 | +| 15.2 | Optional UMTS packages..... | 67 | +| 15.2.1 | Circuit Switched Data package..... | 68 | +| 15.2.1.1 | Properties..... | 68 | +| 15.2.1.2 | Events..... | 68 | +| 15.2.1.3 | Signals..... | 69 | +| 15.2.1.4 | Statistics..... | 70 | +| 15.2.1.5 | Procedures..... | 70 | +| 15.2.2 | TFO package..... | 71 | +| 15.2.2.1 | Properties..... | 71 | +| 15.2.2.2 | Events..... | 72 | +| 15.2.2.3 | Signals..... | 73 | +| 15.2.2.4 | Statistics..... | 73 | +| 15.2.2.5 | Procedures..... | 73 | +| 15.2.3 | 3G Expanded Call Progress Tones Generator Package..... | 73 | +| 15.2.3.1 | Properties..... | 74 | +| 15.2.3.2 | Events..... | 74 | +| 15.2.3.3 | Signals..... | 74 | +| 15.2.3.4 | Statistics..... | 74 | +| 15.2.3.5 | Procedures..... | 74 | +| 15.2.4 | Modification Of Link Characteristics Bearer Capability..... | 74 | +| 15.2.4.1 | Properties..... | 75 | +| 15.2.4.2 | Events..... | 75 | +| 15.2.4.3 | Signals..... | 75 | +| 15.2.4.4 | Statistics..... | 75 | +| 15.2.4.5 | Procedures..... | 75 | +| 15.2.5 | Enhanced Circuit Switched Data package..... | 75 | +| 15.2.5.1 | Properties..... | 75 | +| 15.2.5.2 | Events..... | 76 | +| 15.2.5.3 | Signals..... | 76 | +| 15.2.5.4 | Statistics..... | 76 | +| 15.2.5.5 | Procedures..... | 76 | +| 15.2.6 | Cellular Text telephone Modem Text Transport..... | 76 | +| 15.2.6.1 | Properties..... | 76 | +| 15.2.6.2 | Events..... | 77 | +| 15.2.6.3 | Signals..... | 78 | +| 15.2.6.4 | Statistics..... | 78 | +| 15.2.6.5 | Procedures..... | 78 | +| 15.2.7 | IP transport package..... | 78 | +| 15.2.8 | Flexible Tone Generator Package..... | 78 | +| 15.2.8.1 | Properties..... | 78 | +| 15.2.8.2 | Events..... | 78 | +| 15.2.8.3 | Signals..... | 79 | +| 15.2.8.4 | Statistics..... | 80 | +| 15.2.8.5 | Procedures..... | 80 | +| 15.2.9 | Trace Package..... | 80 | +| 15.2.9.1 | Properties..... | 80 | + +| | | | +|-----------|--------------------------------|----| +| 15.2.9.2 | Events..... | 82 | +| 15.2.9.3 | Signals..... | 83 | +| 15.2.9.4 | Statistics..... | 83 | +| 15.2.9.5 | Procedures..... | 83 | +| 15.2.10 | ASCI Group call package..... | 83 | +| 15.2.10.1 | Properties..... | 83 | +| 15.2.10.2 | Events..... | 84 | +| 15.2.10.3 | Signals..... | 84 | +| 15.2.10.4 | Statistics..... | 84 | +| 15.2.10.5 | Procedures..... | 84 | +| 15.2.11 | 3G Interface Type package..... | 84 | +| 15.2.11.1 | Properties..... | 84 | +| 15.2.11.2 | Events..... | 85 | +| 15.2.11.3 | Signals..... | 85 | +| 15.2.11.4 | Statistics..... | 85 | +| 15.2.11.5 | Procedures..... | 85 | + +# **Annex A (informative): Framing protocol Interworking Function (FPIF).....86** + +| | | | +|-------|----------------------------------------------------------|----| +| A.1 | Introduction..... | 86 | +| A.2 | FPIF procedures with respect to Iu framing protocol..... | 87 | +| A.2.1 | Payload..... | 87 | +| A.2.2 | RFCIs..... | 87 | +| A.2.3 | FQC..... | 87 | +| A.2.4 | Frame number..... | 87 | +| A.3 | Relay of status information..... | 88 | +| A.3.1 | Void..... | 88 | +| A.3.2 | Rate Control Frames..... | 88 | +| A.3.2 | Time Alignment..... | 88 | + +# **Annex B (informative): Examples for Usage of the 3GUP Package "Initialization Direction" Property..... 89** + +# **Annex C (Normative): Profile description.....91** + +| | | | +|-----------|---------------------------------------------------------------|----| +| C.1 | Profile Identification..... | 91 | +| C.2 | Summary..... | 91 | +| C.3 | Gateway Control Protocol Version..... | 91 | +| C.4 | Connection Model..... | 91 | +| C.5 | Context Attributes..... | 92 | +| C.6 | Terminations..... | 92 | +| C.6.1 | Termination Names..... | 92 | +| C.6.1.1 | General..... | 92 | +| C.6.1.2 | ASN.1 Coding..... | 93 | +| C.6.1.2.1 | General Structure..... | 93 | +| C.6.1.2.2 | Termination naming convention for TDM terminations..... | 93 | +| C.6.1.3 | ABNF Coding..... | 93 | +| C.6.1.3.1 | General Structure..... | 93 | +| C.6.1.3.2 | Termination naming convention for TDM terminations..... | 94 | +| C.6.1.3.3 | Termination naming convention for Ephemeral terminations..... | 94 | +| C.6.2 | Multiplexed terminations..... | 94 | +| C.7 | Descriptors..... | 94 | +| C.7.1 | Stream Descriptor..... | 94 | +| C.7.1.1 | LocalControl Descriptor..... | 94 | +| C.7.2 | Events Descriptor..... | 95 | +| C.7.3 | EventBuffer Descriptor..... | 96 | +| C.7.4 | Signals Descriptor..... | 97 | +| C.7.5 | DigitMap Descriptor..... | 98 | +| C.7.6 | Statistics Descriptor..... | 98 | +| C.7.7 | ObservedEvents Descriptor..... | 98 | +| C.7.8 | Topology Descriptor..... | 98 | +| C.7.9 | Error Descriptor..... | 98 | + +| | | | +|---------|--------------------------------------------------------------------------|-----| +| C.7.10 | TerminationState Descriptor..... | 99 | +| C.8 | Command API..... | 100 | +| C.8.1 | Add..... | 100 | +| C.8.2 | Modify..... | 100 | +| C.8.3 | Subtract..... | 100 | +| C.8.4 | Move..... | 101 | +| C.8.5 | AuditValue..... | 101 | +| C.8.6 | AuditCapability..... | 101 | +| C.8.7 | Notify..... | 102 | +| C.8.8 | ServiceChange..... | 102 | +| C.8.9 | Manipulating and auditing context attributes..... | 104 | +| C.9 | Generic command syntax and encoding..... | 104 | +| C.10 | Transactions..... | 104 | +| C.11 | Messages..... | 105 | +| C.12 | Transport..... | 105 | +| C.13 | Security..... | 106 | +| C.14 | Packages..... | 107 | +| C.14.1 | Generic Package..... | 110 | +| C.14.2 | Base Root Package..... | 111 | +| C.14.3 | Tone Generator Package..... | 112 | +| C.14.4 | Tone Detection Package..... | 113 | +| C.14.5 | Basic DTMF Generator Package..... | 114 | +| C.14.6 | Basic DTMF Detection Package..... | 115 | +| C.14.7 | Continuity Package..... | 116 | +| C.14.8 | TDM Circuit Package..... | 117 | +| C.14.9 | Text Telephony Package..... | 118 | +| C.14.10 | Call Discrimination Package..... | 119 | +| C.14.11 | Announcement Package..... | 121 | +| C.14.12 | Media Gateway Resource Congestion handling Package..... | 122 | +| C.14.13 | Hanging Termination Detection Package..... | 122 | +| C.14.14 | Bearer Characteristics Package..... | 123 | +| C.14.15 | Generic Bearer Connection Package..... | 124 | +| C.14.16 | Bearer Control Tunnelling Package..... | 125 | +| C.14.17 | Basic Call Progress Tones Generator with Directionality..... | 126 | +| C.14.18 | Expanded Call Progress Tones Generator Package..... | 127 | +| C.14.19 | Basic Services Tones Generation Package..... | 128 | +| C.14.20 | Expanded Services Tones Generation Package..... | 129 | +| C.14.21 | Intrusion Tones Generation Package..... | 130 | +| C.14.22 | Business Tones Generation Package..... | 131 | +| C.14.23 | 3GUP Package..... | 132 | +| C.14.24 | Modification of Link Characteristics Bearer Capability..... | 133 | +| C.14.25 | TFO package..... | 134 | +| C.14.26 | Circuit Switched Data package..... | 135 | +| C.14.27 | Enhanced Circuit Switched Data package..... | 136 | +| C.14.28 | 3G Expanded Call Progress Tones package..... | 136 | +| C.14.29 | Cellular Text Telephone Modem Text Transport Package..... | 137 | +| C.14.30 | Void..... | 138 | +| C.14.31 | Flexible Tone Generator package..... | 139 | +| C.14.32 | Trace Package..... | 140 | +| C.14.33 | ASCI Group call..... | 141 | +| C.14.34 | IP domain connection..... | 142 | +| C.14.35 | Inactivity Timer Package..... | 143 | +| C.14.36 | 3G Interface Type package..... | 144 | +| C.14.37 | Differentiated Services (ds)..... | 145 | +| C.14.38 | Gate Management (gm)..... | 146 | +| C.14.39 | Traffic management (tman)..... | 147 | +| C.14.40 | IP Realm Availability (ipra)..... | 148 | +| C.14.41 | RTCP Handling Package (rtcph)..... | 148 | +| C.14.42 | Application Data Inactivity Detection (adid)..... | 149 | +| C.14.43 | Explicit Congestion Notification for RTP-over-UDP Support (ecnrous)..... | 150 | +| C.15 | Mandatory support of SDP and Annex C information elements..... | 152 | + +C.16 Optional support of SDP and Annex C information elements..... 153 +Annex D (informative): Change history..... 154 + +# --- Foreword + +This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +# --- 1 Scope + +The present document describes the protocol to be used on the Media Gateway Controller (MGC) – Media Gateway (MGW) interface. The Media Gateway Controllers covered in this specification are the MSC server and the GMSC server. The basis for this interface profile is the H.248.1 [10] protocol as specified in ITU-T. The usage of this protocol is described in 3GPP TS 23.205 [2] and 3GPP TS 29.205 [7] for BICC circuit switched core network, in 3GPP TS 23.231 [54] and 3GPP TS 29.231 [57] for SIP-I circuit switched core network. + +This profile includes the support for the enhanced MSC server to provide access to IMS Centralised services as described in 3GPP TS 23.292 [59] and thus the procedures related to this interface are described in 3GPP TS 29.292 [60]. As a result the interworking with SIP and the associated MGW control procedures described in 3GPP TS 29.163[61] for the interworking between BICC/ISUP circuit switched core network and IP Multimedia core network are incorporated. + +This specification describes the changes to H.248 which are needed to handle 3GPP specific traffic cases. This is done by using the H.248 standard extension mechanism. In addition certain aspects of the base protocol H.248 are not needed for this interface and thus excluded by this profile. + +# --- 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.153: "Out of band transcoder control; Stage 2". +- [2] 3GPP TS 23.205: "Bearer independent circuit-switched core network; Stage 2". +- [3] 3GPP TS 24.008: "Mobile radio interface Layer 3 specification; Core network protocols; Stage 3". +- [4] 3GPP TS 25.415: "UTRAN Iu interface user plane protocols". +- [5] 3GPP TS 28.062: "Inband Tandem Free Operation (TFO) of speech codecs; Service description; Stage 3". +- [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 29.205: "Application of Q.1900 series to Bearer Independent circuit-switched network architecture; Stage 3". +- [8] 3GPP TS 29.415: "Core Network Nb interface user plane protocols". +- [9] 3GPP TS 48.008: "Mobile Switching Centre - Base Station System (MSC - BSS) interface; Layer 3 specification". +- [10] ITU-T Recommendation H.248.1 (05/2002): "Gateway control protocol: Version 2" including the Corrigendum1 for Version 2 (03/04). +- [11] ITU-T Recommendation Q.2210 (1996): "Message transfer part level 3 functions and messages using the services of ITU-T Recommendation Q.2140". +- [12] IETF RFC 2960: "Stream control transmission protocol". + +- [13] 3GPP TS 29.202: "Signalling System No. 7 (SS7) signalling transport in core network; Stage 3". +- [14] ITU-T Recommendation H.248.8 (09/2005): "Error codes and service change reason description". +- [15] ITU-T Recommendation H.248.10 (07/2001): "Media gateway resource congestion handling package". +- [16] 3GPP TS 26.103: "Speech codec list for GSM and UMTS". +- [17] ITU-T Recommendation H.248.2 (01/2005): "Facsimile, text conversation and call discrimination packages". +- [18] 3GPP TS 26.226: "Cellular text telephony; Transport of text in the voice channel". +- [19] ITU-T Recommendation T.140 (02/1998): "Protocol for multimedia application text conversation". +- [20] 3GPP TS 25.413: "UTRAN Iu interface RANAP signalling". +- [21] 3GPP TS 25.414: "UTRAN Iu interface data transport and transport signalling". +- [22] 3GPP TS 23.078: "Customized Applications for Mobile network Enhanced Logic (CAMEL); Stage 2". +- [23] ITU-T Recommendation Q.1950 (12/2002): "Bearer independent call bearer control protocol". +- [24] ITU-T Recommendation Q.765.5 (04/2004): "Signalling system No. 7 - Application transport mechanism: Bearer Independent Call Control (BICC)". +- [25] ITU-T Recommendation G.711 (11/1988): "Pulse code modulation (PCM) of voice frequencies". +- [26] 3GPP TS 26.102: "Mandatory speech codec; AMR speech codec; Interface to Iu, Uu and Nb". +- [27] 3GPP TS 23.014: "Support of Dual Tone Multi-Frequency (DTMF) signalling". +- [28] ITU-T Recommendation H.248.7 (03/2004): "Generic Announcement Package". +- [29] 3GPP TS 32.421: "Subscriber and equipment trace: Trace concepts and requirements ". +- [30] 3GPP TS 32.422: "Subscriber and equipment trace: Trace control and configuration management". +- [31] 3GPP TS 32.423: "Subscriber and equipment trace: Trace data definition and management". +- [32] 3GPP TS 29.414: "Core Network Nb data transport and transport signalling". +- [33] ITU-T Recommendation X.213 (11/95): "Information technology - Open systems interconnection - Network Service Definitions". +- [34] Void +- [35] 3GPP TS 43.045: "Technical Realization Of Facsimile Group 3 service - Transparent". +- [36] ITU-T Recommendation H.248.36 (09/2005): "Hanging Termination Detection Package". +- [37] 3GPP TS 23.172 : "Technical realization of Circuit Switched (CS);multimedia service UDI/RDI fallback and service modification;Stage 2". +- [38] 3GPP TS 33.210 : "3G Security; Network Domain Security; IP Network Layer Security". +- [39] 3GPP TS 43.068: " Voice Group Call Service (VGCS); Stage 2". +- [40] 3GPP TS 43.069: " Voice Broadcast Service (VBS); Stage 2". +- [41] ITU-T Recommendation X.690: "ASN.1 encoding rules: Specification of Basic Encoding Rules (BER), Canonical Encoding Rules (CER) and Distinguished Encoding Rules (DER)". +- [42] ITU-T Recommendation H.248.41 (05/2006): " IP Domain Connection package". + +- [43] 3GPP TS 23.003: "Numbering, addressing and identification". +- [44] IETF RFC 3309: "Stream Control Transmission Protocol (SCTP) Checksum Change" +- [45] ITU-T Recommendation H.248.14 (03/2009):"Inactivity timer package" +- [46] Void +- [47] Void +- [48] Void +- [49] Void +- [50] Void +- [51] 3GPP TS 29.332: "Media Gateway Control Function (MGCF) - IM Media Gateway; Mn Interface". +- [52] IETF RFC 3556: "Session Description Protocol (SDP) Bandwidth Modifiers for RTP Control Protocol (RTCP) Bandwidth". +- [53] IETF RFC 4566: "SDP: Session Description Protocol". +- [54] 3GPP TS 23.231: "SIP-I based circuit switched core network; stage 2". +- [55] IETF RFC 4040: "RTP Payload Format for a 64 kbit/s Transparent Call". +- [56] Void +- [57] 3GPP TS 29.231: "Application of SIP-I Protocols to Circuit Switched (CS) core network architecture; Stage 3". +- [58] 3GPP TS 32.407: "Telecommunication Management; Performance Management (PM) Performance measurements Core Network (CN) Circuit Switched (CS) domain". +- [59] 3GPP TS 23.292: "IP Multimedia Subsystem (IMS) Centralized Services; Stage 2". +- [60] 3GPP TS 29.292: "Interworking between the IP Multimedia (IM) Core Network (CN) subsystem and MSC Server for IMS Centralized Services (ICS)". +- [61] 3GPP TS 29.163: "Interworking between the IM CN subsystem and CS networks – Stage 3". +- [62] Void +- [63] 3GPP TS 26.236: "Packet switched conversational multimedia applications; Transport protocols". +- [64] IETF RFC 2198: "RTP Payload for Redundant Audio Data". +- [65] 3GPP TS 48.103: "Base Station System – Media GateWay (BSS-MGW) interface; User Plane transport mechanism". +- [66] ITU-T Recommendation H.248.57 (06/2008): "Gateway control protocol: RTP Control Protocol Package". +- [67] ITU-T Recommendation H.248.43 (06/2008): "Gateway control protocol: Gate Management and Gate Control packages". +- [69] ITU-T Recommendation H.248.53 (06/2008) inclusive *Revision 1* (03/2009): "Gateway control protocol: Traffic management packages". +- [70] ITU-T Recommendation H.248.52 (06/2008): "Gateway control protocol: QoS support packages". +- [71] ITU-T Recommendation H.248.40 (01/2007): "Gateway control protocol: Application Data Inactivity Detection package". +- [72] ITU-T Recommendation H.248.41 Amendment 1 (06/2008): "Gateway control protocol: IP domain connection package: IP Realm Availability Package". + +- [73] IETF RFC 2216: "Network Element Service Specification Template". +- [74] Void +- [75] Void +- [76] Void +- [77] 3GPP TS 26.114: "IP Multimedia Subsystem (IMS); Multimedia Telephony; Media handling and interaction". +- [78] 3GPP TS 22.153: "Multimedia Priority Service". +- [79] ITU-T Recommendation H.248.82 (03/2013): "Gateway control protocol: Explicit Congestion Notification Support". + +# --- 3 Definitions, symbols and abbreviations + +## 3.1 Definitions + +For the purposes of the present document, the following terms and definitions apply: + +**context (H.248):** association between a number of Terminations + +The context describes the topology (who hears/sees whom) and the media mixing and/or switching parameters if more than two terminations are involved in the association. + +**package (H.248):** different types of gateways may implement terminations which have differing characteristics + +Variations in terminations are accommodated in the protocol by allowing terminations to have optional properties. Such options are grouped into packages, and a termination may realise a set of such packages. + +**termination (H.248):** logical entity on an MGW which is the source and/or sink of media and/or control streams + +A termination is described by a number of characterising properties, which are grouped in a set of descriptors which are included in commands. Each termination has a unique identity (TerminationID). + +**termination property (H.248):** used to describe terminations + +Related properties are grouped into descriptors. Each termination property has a unique identity (PropertyID). + +## 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. | + +## 3.3 Abbreviations + +For the purposes of the present document, the following abbreviations apply: + +| | | +|------|----------------------------------------------------------------------------------------------------| +| BICC | Bearer Independent Call Control | +| CE | Congestion Experienced | +| ECN | Explicit Congestion Notification | +| M3UA | SS7 MTP3 – User Adaptation Layer | +| MGC | Media Gateway Controller | +| MPS | Multimedia Priority Service | +| MTP3 | Message Transfer Part layer 3 | +| RFC | Request For Comment; this includes both discussion documents and specifications in the IETF domain | +| SCTP | Stream Control Transmission Protocol | +| TFO | Tandem Free Operation | +| TrFO | Transcoder Free Operation | + +# --- 4 UMTS capability set + +The support of the Mc interface capability set shall be identified by the Mc profile and support of this profile shall then be indicated in ServiceChange procedure via the ServiceChangeProfile parameter as defined in H.248.1 [10] and clarified in section 4.2. The mandatory parts of this profile shall be used in their entirety. Failure to do so will result in a non-standard implementation. + +ITU-T Recommendation H.248.1 [10] shall be the basis for this profile. The compatibility rules for packages, signals, events, properties and statistics and the H.248 protocol are defined in ITU-T Recommendation H.248.1 [10] Their use or exclusion for this interface is clarified in clause 12. + +## 4.1 Profile Identification + +For Profile Identification see Annex C.1. + +## 4.2 Profile Registration + +The following description is based on H.248.1 profile registration procedure with some clarifications. The reply to the ServiceChange Request containing the SCP parameter indicates if the MSC Server supports the requested profile or if it does not support it and wants to propose an alternative profile. The profile (name and version) is only returned in the reply if the MGC cannot support the specified profile in the ServiceChangeRequest. The returned reply shall indicate the profile and version supported or "NoProfile" if no profile is supported. Upon reception of a profile in the reply, if the MGW supports the indicated profile, it shall issue a new ServiceChange Request with the agreed profile to explicitly confirm the acceptance of the profile to the MGC ; otherwise, if the MGW does not support the indicated profile, it may continue the registration or re-registration procedure by issuing a new ServiceChange Request with an alternative profile ; until such procedure is successfully completed the MGW shall remain out of service. In the instance that the MGW did not indicate a profile in the original ServiceChangeRequest and the MGC returned a profile in the reply, the MGW shall issue a new ServiceChangeRequest with the appropriate profile or "NoProfile" if no profile is supported. If the profile is not returned the MGC shall use the capabilities specified by the Profile indicated in the service change request. + +NOTE: It should be observed that the profile registration is not a "cold calling" negotiation; the operator shall have configured the network to support certain profiles and so the profile registration within the Mc interface permits network upgrade scenarios but otherwise is simply a means to confirm the connection of the profile to be used over the Mc interface between MGC and MGW. + +# --- 5 Naming conventions + +## 5.1 MGC/MGW naming conventions + +For definition see Annex C.11. + +## 5.2 Termination names + +For definition see Annex C.6.1. + +# --- 6 Topology descriptor + +For definition see Annex C.7.8. + +# --- 7 Transaction timers + +For definition see Annex C.10. + +# --- 8 Transport + +Each implementation of the Mc interface should provide the appropriate protocol options: MTP3B as defined in ITU-T Recommendation Q.2210 [11] (for ATM signalling transport) or SCTP as defined in RFC 2960 [12] and as updated by RFC3309 [44] (for IP signalling transport) and in the case where the signalling relation consists of both ATM signalling transport and IP signalling transport the M3UA protocol layer (3GPP TS 29.202 [13]) shall be added to SCTP to provide interworking. M3UA layer may also be added to SCTP for pure IP signalling transport. IPsec shall not be used by MSC Server or MGW for the Mc interface. Normally the Mc interface lies within a single operator's secure domain. If this is not the case then a Za interface (Security Gateway deploying IPSec) may be required, however this is a separate logical function/entity and thus is not attributed to Mc profile, the MSC Server or the MGW; for further details see 3GPP TS 33.210 [38]. For further definition see Annex C.12. + +# --- 9 Multiple Virtual MG. + +If an MGW is connected to more than one (G)MSC, the MGW shall fulfil the requirements outlined in the subclause "Multiple virtual MGW" in ITU-T Recommendation H.248.1 [10]. + +# --- 10 Formats and codes + +## 10.1 Signalling Objects + +Table 10.1 shows the parameters which are required, in addition to those defined in the subclause "Formats and Codes" of ITU-T Recommendation Q.1950 [23] (see 3GPP TS 29.205 [7]). + +The coding rules applied in ITU-T Recommendation H.248.1 [10] for the applicable coding technique shall be followed for the UMTS capability set. + +Unsupported values of parameters or properties may be reported by the MGW and shall be supported by the MSC as such by using H.248.1 error code #449 " Unsupported or Unknown Parameter or Property Value ". **Error Text in the error Descriptor:** The unsupported or unknown value is included in the error text in the error descriptor. + +**Table 10.1: Additional parameters required** + +| Signalling Object | H.248 Descriptor | Coding | +|---------------------------------------|-----------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| actprot | Signal descriptor | As for the signal "Activate protocol" in subclause 15. 2.1.3 | +| Bearer modification possible | ObservedEvent descriptor | As for the ObserverdEventDescriptor in "Bearer Modification Support" in subclause 15. 2.3.2. | +| Bearer Modification Support | EventDescriptor | As for the EventsDescriptor in "Bearer Modification Support" in subclause 15. 2.3.2. | +| Bitrate | Local control | As for the property "Bitrate" in subclause 15.1.7.1 | +| Cause | ObservedEvent descriptor | As for the ObservedEventsDescriptor parameter "Protocol Negotiation Result" in subclause 15. 2.1.2 | +| Changed Realms | Observed Events | According to Observed Events Parameters for Available Realms Changed event in ITU-T Recommendation H.248.41 [72]. | +| Codec List | Local Descriptor or Remote Descriptor | in a single SDP m-line.
For a static RTP payload type, the codec type should be implied by the RTP payload type, if not then each codec type shall be provided in a separate SDP "a=rtpmap"-line and possibly additional SDP "a=fmtp"-line(s). See Clause 10.2.
For a dynamic RTP payload type, for each codec information on the codec type shall be provided in a separate SDP "a=rtpmap"-line and possibly additional SDP "a=fmtp"-line(s). See Clause 10.2 | +| Coding | Local control | As for the property "GSM channel coding" in subclause 15. 2.1.1 | +| Connchng | ObservedEventDescriptor | As for the ObservedEventDescriptor "Connection State Change" in subclause 15.2.6.2 | +| Ctmbits | Statistics descriptor | As for the Statistics descriptor "Characters Transferred" in subclause 15.2.6.4 | +| Ctmstate | TerminationState | As for the TerminationState "Text termination connection state" in subclause 15. 2.6.1. | +| Ctmtext version | Local control | As for the property "Text Protocol Version" in subclause 15.2.6.1. | +| Ctmtransport | Local control | As for the property "Text Transport" in subclause 15.2.6.1. | +| Delay Variation Tolerance | Local Control | This is the tman/dvt property from ITU-T Recommendation H.248.53 [69] | +| Desired listener context terminations | Local control | As for the property "Number of desired listener context terminations" in subclause 15.2.10.1 | +| Diffserv Code Point | Local Control | Defined according to the Differentiated Services Code Point property in ITU-T Recommendation H.248.52 [70]. | +| Diffserv Tagging Behaviour | Local Control | Defined according to the Tagging Behaviour property in ITU-T Recommendation H.248.52 [70]. | +| Distlist | ObservedEvent descriptor | As for the ObservedEventDescriptor parameter "Distant TFO List" in subclause 15. 2.2.2 | +| ECN Enabled | Local Descriptor or Remote Descriptor | Defined according to the "ECN Enabled" property in ITU-T Recommendation H.248.82 [79]. | +| ECN Failure | Events, Observed Events | Defined according to the "ECN Failure" Event in ITU-T Recommendation H.248.82 [79]. | +| ECN Failure Type | ObservedEvents Descriptor | As for the ObservedEventsDescriptor Parameter "Failure Type" in ITU-T Recommendation H.248.82 [79]. | +| ECN Initiation Method | Local Descriptor or Remote Descriptor | Defined according to "Initiation Method" property in ITU-T Recommendation H.248.82 [79]. | +| Error | Error descriptor | As defined in the subclause "Command error code" in ITU-T Recommendation H.248.1 [10] | +| Flextone | Signal descriptor | As for the signal "Flexible Tone" in subclause 15.2.8.3 | +| IMEI(SV) | Local control | As for the property "IMEI(SV)" in subclause 15.2.9.1 | +| IMSI | Local control | As for the property "IMSI" in subclause 15.2.9.1 | +| inactivity timeout | EventDescriptor | As for the EventsDescriptor in subclause 6.2/H.248.14 "Inactivity Timeout" | +| Inactivity timeout | ObservedEvent descriptor | As for the ObserverdEventDescriptor in subclause 6.2/H.248.14 "Inactivity Timeout " | +| Initdirection | Local control | As for the property "Initialization Direction" in subclause 15.1.1.1 | +| Interface | Local control | As for the property "Interface" in subclause 15.1.1.1 | +| IP Address | Local Descriptor or Remote Descriptor | in SDP "c-line" | +| IP interface | Local Control | As for the property "IP interface type" in subclause 15.2.11.1 | +| IP realm identifier | Local control | As for the property "IP realm identifier" in subclause 5.1.1/H.248.41 | +| IP Version | Local Descriptor or Remote Descriptor |
in SDP "c-line", see C.16 | +| Iu IP Address | Local Descriptor or Remote Descriptor control | As defined in C.16 | + +| | | | +|-----------------------------------------------|---------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Iu IP Port | Local Descriptor or Remote Descriptor | As defined in C.16. Port Type is not defined in the Mc profile and shall be assumed always to be UDP. | +| List of interfaces | Local control | As for the property "List of interfaces" in subclause 15.2.9.1 | +| MGW Resource Congestion Handling - Indication | EventDescriptor | As for the EventDescriptor in subclause 4.2.1/H.248.10 "MGCongestion" | +| Maximum Burst Size | Local Control | This is the tman/mbs property from ITU-T Recommendation H.248.53 [69] | +| Media Inactivity Detection | Events, Observed Events | Defined according to IP Flow Stop Detection event in ITU-T Recommendation H.248.40 [71]. | +| Media Inactivity Detection Time | Events | As for the Event Parameter in ITU-T Recommendation H.248.40 [71] "Detection Time" | +| Media Inactivity Detection Direction | Events | As for the Event Parameter in ITU-T Recommendation H.248.40 [71] "Direction" | +| Mode | Local control | As for the property "UP mode of operation" in subclause 15.1.1.1 | +| Needed conference terminations | Local control | As for the property "Number of needed conference terminations" in subclause 15.2.10.1 | +| On/Off | Local control | As for the property "Echo cancelling" in subclause E.13.1 in ITU-T Recommendation H.248.1 [10] . Default value is Off. | +| Optimalcodec | ObservedEvent descriptor | As for the ObservedEventDescriptor parameter "Optimal Codec Type" in subclause 15. 2.2.2 | +| Peak Data Rate | Local Control | This is the tman/pdr property from ITU-T Recommendation H.248.53 [69]. | +| PLMN bearer capability | Local control | As for the property "PLMN BC" in subclause 15. 2.1.1 | +| Policing Required | Local Control | This is the tman/pol property from ITU-T Recommendation H.248.53 [69]. | +| Port | Local Descriptor or Remote Descriptor | in SDP m-line.
in SDP m-line shall be set to value "RTP/AVP" for voice service
Editor's note: the value for other services in FFS. | +| Priority Information | NA | Priority Indicator (subclause 6.1.1 of ITU-T Recommendation H.248.1 [10]).
Binary Encoding: Encoding as per ITU-T Recommendation H.248.1 [10] Annex A "priority" context attribute
Textual Encoding: Encoding as per ITU-T Recommendation H.248.1 [10] Annex B "priority" context attribute | +| Rate | ObservedEvent descriptor | As for the ObservedEventDescriptor parameter "Rate Change" in subclause 15. 2.1.2 | +| Realm Availability Change | Events, Observed Events | According to Available Realms Changed event in ITU-T Recommendation H.248.41 [72]. | +| Reduction | ObservedEvent descriptor | As for the ObservedEventDescriptor in subclause 4.2.1/H.248.10 "MGCongestion". | +| Remote Source Address Filtering | Local Control | Defined according to Remote Source Address Filtering property in ITU-T Recommendation H.248.43 [67]. | +| Remote Source Address Mask | Local Control | Defined according to Remote Source Address Mask property in ITU-T Recommendation H.248.43 [67]. | +| Remote Source Port Filtering | Local Control | Defined according to Remote Source Port Filtering property in ITU-T Recommendation H.248.43 [67]. | +| Remote Source Port | Local Control | Defined according to Remote Source Port property in ITU-T Recommendation H.248.43 [67]. | +| Remote Source Port Range | Local Control | Defined according to Remote Source Port Range property in ITU-T Recommendation H.248.43 [67]. | +| RTCP allocation | Local Control | Defined according to RTCP Allocation Specific Behaviour property in ITU-T Recommendation H.248.57 [66]. | +| Reserve_Value | Local Control | ITU-T Recommendation H.248.1 [10] Mode property.
Binary Encoding: Encoding as per ITU-T Recommendation H.248.1 Annex A "reserveValue"
Textual Encoding: Encoding as per ITU-T Recommendation H.248.1 Annex B "reservedValueMode". | +| Result | ObservedEvent descriptor | As for the ObservedEventDescriptor parameter "Protocol Negotiation Result" in subclause 15. 2.1.2 | +| RtcpbwRR | Local Descriptor or Remote Descriptor | in SDP "b:RR"-line as per IETF RFC 3556 [52]. | +| RtcpbwRS | Local Descriptor or Remote Descriptor | in SDP "b:RS"-line as per IETF RFC 3556 [52]. | +| RTPpayload | Local Descriptor or Remote Descriptor | in SDP m-line | + +| | | | +|----------------------------------------------------------|---------------------------|-----------------------------------------------------------------------------------------| +| Sustainable Data Rate | Local Control | This is the tman/sdr property from ITU-T Recommendation H.248.53 [69] | +| termination heartbeat | EventDescriptor | As for the EventsDescriptor in subclause 5.2.1/H.248.36 "Termination Heartbeat" | +| Termination heartbeat | ObservedEvent descriptor | As for the ObserverdEventDescriptor in subclause 5.2.1/H.248.36 "Termination Heartbeat" | +| tfoactvalue | Local control | As for the property "TFO activity control" in subclause 15. 2.2.1 | +| TFOcodeclist (NOTE) | Local control | As for the property "TFO Codec List" in subclause 15. 2.2.1 | +| TFO Status | EventDescriptor | As for the EventsDescriptor in "TFO_Status Event" in subclause 15.2.2.2 | +| tfostatus | ObservedEvent descriptor | As for the ObservedEventsDescriptor parameter "TFO Status" in subclause 15.2.2.2 | +| Trace activativity request | Local control | As for the property "Trace Activation Control" in subclause 15.2.9.1 | +| Trace Activation Result | ObservedEvents descriptor | As for the ObservedEventDescriptor "Trace Activation result" in subclause 15.2.9.2 | +| Trace Depth | Local control | As for the property "Trace Depth" in subclause 15.2.9.1 | +| Trace Recording Session Reference | Local control | As for the property "Trace Recording Session Reference" in subclause 15.2.1.1 | +| Trace reference | Local control | As for the property "Trace Reference" in subclause 15.2.9.1 | +| Triggering events | Local control | As for the property "Triggering events" in subclause 15.2.9.1 | +| Value | Local control | As for the property "Delivery of erroneous SDUs" in subclause 15.1.1.1 | +| Version | Local control | As for the property "Upversion" in subclause 15.1.1.1 | +| Warning tone | Signal descriptor | As for the signal "CAMEL Prepaid Warning Tone" in subclause 15.2.3.3 | +| NOTE: TFOcodeclist was named Codeclist in pre-release 8. | | | + +## 10.2 SDP Media Parameters for RTP Terminations + +### 10.2.1 Speech Codecs + +The speech codecs and their configuration permitted for use over SIP-I and AoIP are defined in 3GPP TS 26.102 [26], Clauses 9 and 10. The SDP parameters for those codecs are defined in 3GPP TS 26.103 [16], Clause 7. + +The speech codecs permitted for use for Enhanced MSC are defined in 3GPP TS 26.236 [63]. + +Codec types may have static or dynamic RTP payload types as defined by the above references. + +For dynamic payload type being used the codecs shall be signalled accordingly in the SDP "a=rtpmap"-line, where the selected options are expressed as MIME parameters in SDP "a=fmtp"-line. + +For static payloads type being used the codecs shall be allowed to be signalled accordingly in the SDP "a=rtpmap"-line, when the selected options are expressed as MIME parameters in SDP "a=fmtp"-line. Otherwise the codec type is implied by the RTP payload type. + +### 10.2.2 DTMF + +DTMF support is defined within 3GPP TS 23.231 [54] and the RTP Payload Type shall be supported as defined in 3GPP TS 26.102 [26]. + +### 10.2.3 Auxiliary Payloads + +#### 10.2.3.1 Void + +#### 10.2.3.2 Void + +#### 10.2.3.3 Clearmode Codec + +On RTP terminations, Clearmode codec is transported according to IETF RFC 4040[55]. + +When the MGC determines that a 64 kbit/s unrestricted bearer service is requested, the clearmode codec shall be used. A dynamic payload type with CLEARMODE as encoding name shall be included in both the local and remote descriptor. + +The behaviour of the MGW shall then conform to IETF RFC 4040[55]. All voice and signal processing functions such as silence suppression, comfort noise insertion and gain adjustment shall be automatically turned off. The MGW shall inherit the same QoS objectives as the ISDN bearer service. + +#### 10.2.3.4 Silence suppression and Comfort Noise + +Support of silence suppression and comfort noise is defined in 3GPP TS 26.102 [26]. + +#### 10.2.3.5 CS Data Service + +##### 10.2.3.5.1 CS Data Service with no Redundancy + +RTP transport for CS Data services on the A-Interface User Plane over IP (AoIP) is based on RFC 4040 (CLEARMODE) [55], when this payload type is used by itself it means no redundancy is offered, which results in a 64kbps net bit stream. + +A specific Payload Type value (120) is defined in TS 48.103 [65] in the range of dynamic Payload Types for CSData without redundancy. + +The SDP-syntax on the Mc interface for CS Data without redundancy is: + +``` +m=audio RTP/AVP 120 +a=rtpmap:120 CLEARMODE/8000 +``` + +##### 10.2.3.5.2 CS Data Service with Redundancy + +A second specific Payload Type value (121) is defined in TS 48.103 [65] in the range of dynamic Payload Types for RTP Payload for Redundant Audio Data over AoIP. Redundancy for the CS Data service on AoIP is realised according to IETF RFC 2198 [64]. The SDP-syntax (red, fmtp) defined in this RFC is used to inform the MGW about the negotiated redundancy level. The encapsulated payload structure for CS Data is based on IETF RFC 4040 [55]. On AoIP RTP terminations, IETF RFC 2198 [64] shall be used for redundant data of the CLEARMODE payload type being used for the CSD service. Only the redundancy level 2 and level 3 are supported on the AoIP RTP terminations. For details at start and stop of a redundant data stream as well as in handover cases see TS 48.103 [65]. + +The MGC determines by BSSMAP negotiation with the BSS, whether redundancy is used and if so which level to use for the CS Data service. A dynamic payload type with "red" as encoding name shall be included in both the local and remote descriptor with the fmtp attribute to signal the redundancy level. The same redundancy level shall be used in the Local Descriptor and the Remote Descriptor to use the same redundancy level in both directions between the MGW with the BSS. + +NOTE: Whether the RTP payload for Redundant Audio Data is supported by the MGW is known by the MSC due to configuration data. + +The MGC shall include both the CLEARMODE payload type and the Redundant RTP Payload for Audio Data in the Mc interface towards the MGW when the Redundant RTP Payload for Audio Data encapsulating the CLEARMODE payload shall be used. The MGW shall then apply the procedures for support of RTP redundancy as described in 3GPP TS 48.103 [65]. + +The SDP-syntax on the Mc interface for CS Data with redundancy level 2 is: + +``` +m=audio RTP/AVP 121 120 +a=rtpmap:120 CLEARMODE/8000 +a=rtpmap:121 red/8000 +a=fmtp:121 120/120 +``` + +The SDP-syntax on the Mc interface for CS Data with redundancy level 3 is: + +``` +m=audio RTP/AVP 121 120 +a=rtpmap:120 CLEARMODE/8000 +a=rtpmap:121 red/8000 +a=fmtp:121 120/120/120 +``` + +### 10.2.4 Other Payload Types + +On RTP terminations, other payload types such as additional ITU-T codecs can be transported according to the RTP payload formats in IETF but their support is outside the scope of 3GPP specifications. + +# 11 Mandatory Support of SDP and H.248.1 annex C information elements + +This section shall be in accordance with the subclause "Mandatory Support of SDP and H.248.1 annex C information elements" in ITU-T Recommendation Q.1950 [23] (see 3GPP TS 29.205 [7]) with the following requirements: + +- Mc Single Codec encoding: + +The ACodec property in H.248 binary encoding and codecconfig attribute in H.248 text encoding are set as defined in ITU-T Recommendation Q.765.5 [24], for single codec information (figure 14/Q.765.5), where the Codec Information is defined either in ITU-T Recommendation Q.765.5 [24] or in another specification for the given Organization Identifier. For 3GPP codecs these are defined in 3GPP TS 26.103 [16]. The codecconfig and ACodec parameters contain the contents of the Single Codec IE, excluding the Single Codec Identifier, Length Indication and Compatibility Information. + +The 'vsel' attribute is omitted in H.248 text encoding. + +Example of encoding of an AMR codec: + +ACodec = 0206959504 (binary encoding) + +codecconfig = 0206959504 (text encoding) + +where the AMR parameters are: ETSI, UMTS\_AMR\_2, [ACS={4.75, 5.90, 7.4, 12.2}, SCS={4.75, 5.90, 7.4, 12.2}, OM=0, MACS=4] + +Example of encoding of a G.711 codec: + +ACodec = 0101 (binary encoding) + +codecconfig = 0101 (text encoding) + +where the G.711 parameters are: ITU-T, G.711 64kps A-law + +NOTE: The "Mc Single Codec IE" differs from the ITU-T defined "Single Codec IE", while on the Nc interface (i.e. in OoBTC) the ITU-T Single Codec IE is used without deviation. + +The ACodec property or codecconfig attribute set to the MuMe Dummy codec denotes a multimedia call. The ACodec property and codecconfig attribute shall never be set to the MuMe2 Dummy codec. See 3GPP TS 26.103 [16] and 3GPP TS 23.172 [37]. + +For further definition see Annex C.15. + +# --- 12 General on Packages and Transactions + +The use of "Overspecified" (e.g. range of values) and "Underspecified" (e.g. "?") parameter specification shall not be permitted except where explicitly indicated in or referenced by the Mc interface specification. + +The use of wildcarding for the Termination Id shall be performed using 1 octet only. + +Notifications shall not be sent by the MGW in response to Release Termination procedure. + +Parameter modification and event notification shall not be permitted on non-ROOT Terminations in the NULL Context. + +Commands on ROOT Termination shall only use the NULL Context. + +If a command cannot be executed by the MSC Server due to a temporary congestion/ongoing task the error code 511 ("Temporarily Busy") may be returned; the MGW may then re-issue the command as the condition may have abated. + +NOTE: At the time of inclusion this error code did not exist in the H.248.8 further details of this error code see ITU-T Sub-series Implementors' Guide.(13 April 2006). + +If a circumstance arises at an MGW where a substantial number of notifications accumulate, either because of transmission difficulties or because the MGW recognised a number of events in a short time period, the MGW should send the notifications in a restricted manner (e.g. via configuration) until the backlog is cleared. + +For further definition see Annex C. + +# --- 13 BICC packages + +## 13.1 Mandatory BICC packages + +Mandatory BICC packages are listed in Annex C.14. + +## 13.2 Optional BICC packages + +Optional BICC packages are listed in Annex C.14. + +# 14 H.248 standard packages + +Mandatory and Optional H.248 packages are listed in Annex C.14. + +## 14.1 Call independent H.248 transactions + +Table 2 shows the relationship between each non call-related procedure in ITU-T Recommendation Q.1950 [23] (see 3GPP TS 29.205 [7]) and the corresponding stage 2 procedure defined in 3GPP TS 23.205 [2]. + +For further description of error codes and service change reasons, refer to ITU-T Recommendation H.248.8 [14]. + +**Table 14.1.1: Correspondence between ITU-T Recommendation Q.1950 [23] non call-related transactions and 3GPP TS 23.205 [2] procedures** + +| Transaction used in ITU-T Recommendation Q.1950 [23] | Procedure defined in 3GPP TS 23.205 [2] | Support | Comments | +|------------------------------------------------------|-----------------------------------------------|-----------|-----------------------------------------------------------------------------------------------------------------------------------------------------------| +| BIWF_Service_Cancellation_Indication | MGW Out of Service | Mandatory | | +| BIWF_Lost_Communication | MGW Communication Up | Mandatory | | +| BIWF_Service_Restoration_Indication | MGW Restoration | Mandatory | | +| BIWF_Registration | MGW Register | Mandatory | | +| BIWF_Re-Registration | MGW Re-register | Mandatory | | +| CCU Ordered BIWF Re-Registration | (G)MSC Server Ordered Re-register | Mandatory | | +| CCU Initiated Service Restoration | (G)MSC Server Restoration | Optional | | +| CCU Initiated Service Cancellation | (G)MSC Server Out of Service | Optional | | +| BIWF_Service_Cancellation_Indication | Termination Out-of-Service | Mandatory | Is a part of BIWF Service cancellation in Q.1950 | +| BIWF_Service_Restoration_Indication | Termination Restoration | Mandatory | Is a part of BIWF Service cancellation in Q.1950 | +| Audit_Values | Audit Value | Mandatory | Shall be supported for the audit of Termination State and for periodic audit of MGW (empty Audit descriptor). May be supported for the audit of packages. | +| Audit_Capabilities | Audit Capability | Optional | The capabilities to be audited shall be defined in clause 12. | +| BIWF_Capability_Change | Capability Update | Optional | This corresponds to MGW Capability Change in this document. | +| | MGW Resource Congestion Handling - Activate | Mandatory | | +| | MGW Resource Congestion Handling - Indication | Mandatory | | +| Continuity Check Tone | | Optional | | +| Continuity Check Verify | | Optional | | +| Continuity Check Response | | Optional | | +| Not Defined | Inactivity Timeout - Activate | Optional | | +| Not Defined | Inactivity Timeout - Indication | Optional | | +| Not Defined | Realm Availability Change - Activation | Optional | | +| Not Defined | Realm Availability Change - Indication | Optional | | + +### 14.1.1 MGW Out of service/Maintenance Locking + +This procedure is the same as described in the subclause "BIWF Service Cancellation Indication" in ITU-T Recommendation Q.1950 [23] (see 3GPP TS 29.205 [7]), with the following clarification. + +**Table 14.1.1.1: MGW Out of service/Maintenance Locking** + +| Address Information | Control information | Bearer information | +|---------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------| +| | Transaction ID = z
Context ID = Null
Termination ID = Root
Service Change Reason =
MGW impending failure
Termination Taken out of service
Service Change Method =
Graceful / Forced | | + +Delay is not used. + +NOTE: The termination that is taken out of service is a Media Gateway. + +### 14.1.2 MGW Communication Up + +This procedure is the same as described in the subclause "BIWF Lost Communication" in ITU-T Recommendation Q.1950 [23] (see 3GPP TS 29.205 [7]) with the following clarification. + +Use of time stamps is optional. + +Context Id value Null shall be used in this procedure. + +The ServiceChangeMGCId parameter may be returned in the MGW Communication Up response if the MGC does not wish to sustain an association with the MGW. If present in the response, the MGW shall not consider itself registered and should preferably attempt to re-register with the MGC specified in the ServiceChangeMgcID before any further alternate MGCs. + +### 14.1.3 MGW Restoration + +This procedure is the same as described in the subclause "BIWF Service Restoration Indication" in ITU-T Recommendation Q.1950 [23] (see 3GPP TS 29.205 [7]) with the following clarification. + +**Table 14.1.3: MGW Restoration** + +| Address Information | Control information | Bearer information | +|---------------------|------------------------------------------------------------------|--------------------| +| | Transaction ID = z
Context ID = Null
Termination ID = Root | | + +Delay is not used. + +The ServiceChangeMGCId parameter may be returned in the MGW Restoration response if the MGC does not wish to sustain an association with the MGW. If present in the response, the MGW shall not consider itself registered and should preferably attempt to re-register with the MGC specified in the ServiceChangeMgcID before any further alternate MGCs. + +### 14.1.4 MGW Register + +This procedure is the same as that described in the subclause "BIWF Registration" in ITU-T Recommendation Q.1950 [23] (see 3GPP TS 29.205 [7]) with the following clarification. + +#### 14.1.4: MGW Register + +| Address Information | Control information | Bearer information | +|---------------------|---------------------------------------------------|--------------------| +| | ServiceChangeProfile =
mcprofileName / version | | + +Use of time stamps is optional. + +Context Id value Null shall be used in this procedure. + +Non Standard Data is shall not be supported. + +Service Change Address shall not be used. + +The ServiceChangeMGCId parameter may be returned in the MGW Register response. If present in the Register response, the MGW shall not consider itself registered and should preferably attempt to re-register with the MGC specified in the ServiceChangeMgcID before any further alternate MGCs. + +### 14.1.5 MGW Re-register + +This procedure is the same as that described in the subclause "BIWF Re-Registration" in ITU-T Recommendation Q.1950 [23] (see 3GPP TS 29.205 [7]) with the following clarification. + +##### Table 14.1.5.1: MGW Re-register + +| Address Information | Control information | Bearer information | +|---------------------|---------------------------------------------------|--------------------| +| | ServiceChangeProfile =
mcprofileName / version | | + +Use of time stamps is optional. + +Context Id value Null shall be used in this procedure. + +Non Standard Data is shall not be supported. + +Service Change Address shall not be used. + +The ServiceChangeMGCId parameter may be returned in the MGW Re-register response. If present in the response, the MGW shall not consider itself registered and should preferably attempt to re-register with the MGC specified in the ServiceChangeMgcID before any further alternate MGCs. + +### 14.1.6 (G)MSC Server Ordered Re-register + +This procedure is the same as described in the subclause "CCU Ordered BIWF Re-registration" in ITU-T Recommendation Q.1950 [23] (see 3GPP TS 29.205 [7]) with the following clarifications: + +Context Id value Null shall be used in this procedure. + +### 14.1.7 (G)MSC Server Restoration + +This procedure is the same as described in the subclause "CCU Initiated Service Restoration" in ITU-T Recommendation Q.1950 [23] (see 3GPP TS 29.205 [7]) with the following clarification. + +**Table 14.1.7.1: (G)MSC Server Restoration** + +| Address Information | Control information | Bearer information | +|---------------------|--------------------------------------------------------------------------------------------------------------------------------|--------------------| +| | Context ID = Null
Termination ID = Root
Service Change Reason = Cold Boot / Warm Boot
Service Change Method = Restart | | + +Delay is not used. + +### 14.1.8 Termination Out-of-Service + +This procedure is the same as described in the subclause "BIWF Service Cancellation Indication" in ITU-T Recommendation Q.1950 [23] (see 3GPP TS 29.205 [7]) with the following clarifications. This procedure may be used to inform the MSC Server of the Service State of Terminations after MGW Restart or Registration. + +**Table 14.1.8.1: ServiceChange.req (Termination Out-of-Service) MGW to MGC** + +| Address Information | Control information | Bearer information | +|---------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------| +| | Transaction ID = z
Context ID = Contexts / Null / All
Termination ID = ALL/Termination(s)
Service Change Reason = Transmission failure / Termination malfunctioning / Loss of lower layer connectivity / Termination taken out of service
Service Change Method = Graceful / Forced

NOTE1: "All" shall refer to 1 TDM group. 1 TDM group is at a T1/E1. | | + +Delay is not used. + +The MGW shall delay initiating a TDM Termination Out-of-Service procedure till completion of any on-going Termination Restoration procedure for the same TDM termination, if any, unless the MGW considers the previous transaction request or reply lost, due to e.g. failure of the control association. + +The following table illustrates the allowed combinations that can be obtained with the ServiceChange Command: + +**Table 14.1.8.2: Combinations of ContextID and TerminationID in Termination Out-of- Service Procedure** + +| ContextID | TerminationID | Description | +|-----------|---------------|----------------------------------------------------------------------------------------------------------------------------------------| +| Specific | Specific | Service Change of a specific Termination in a specific Context | +| Null | Wildcard | Service Change of all matching TDM T1/E1 level terminations in the Null Context | +| Null | Specific | Service Change of a specific termination in the Null Context | +| All | Wildcard | Service Change of all matching TDM T1/E1 level terminations in specific (non-Null) contexts in which the terminations currently exist. | + +### 14.1.9 Termination Restoration + +This procedure is the same as described in the subclause "BIWF Service Restoration Indication" in ITU-T Recommendation Q.1950 [23] (see 3GPP TS 29.205 [7]) with the following clarification. This procedure may be used to inform the MSC Server of the Service State of Terminations after MGW Restart or Registration and shall be used when individual trunks are commissioned. + +**Table 14.1.9.1: Termination Restoration** + +| Address Information | Control information | Bearer information | +|---------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------| +| | Transaction ID = z
Context ID = Contexts / Null / All
Termination ID = ALL/Termination(s)
Service Change Reason = Service Restored
Service Change Method = Restart

NOTE1: "All" shall refer to 1 TDM group. 1 TDM group is at a T1/E1. | | + +Delay shall not be used. + +The MGW shall delay initiating a TDM Termination Restoration procedure till completion of any on-going Termination Out-of-Service procedure for the same TDM termination, if any, unless the MGW considers the previous transaction request or reply lost, due to e.g. failure of the control association. + +The following table illustrates the allowed combinations that can be obtained with the ServiceChange Command: + +**Table 14.1.9.2: Combinations of ContextID and TerminationID in Termination Restoration Procedure** + +| ContextID | TerminationID | Description | +|-----------|---------------|----------------------------------------------------------------------------------------------------------------------------------------| +| Specific | Specific | Service Change of a specific Termination in a specific Context | +| Null | Wildcard | Service Change of all matching TDM T1/E1 level terminations in the Null Context | +| Null | Specific | Service Change of a specific termination in the Null Context | +| All | Wildcard | Service Change of all matching TDM T1/E1 level terminations in specific (non-Null) contexts in which the terminations currently exist. | + +### 14.1.10 Audit Value + +This procedure is the same as described in the subclause "Audit Values" in ITU-T Recommendation Q.1950 [23] (see 3GPP TS 29.205 [7]), with the following clarifications. This procedure shall be used by the MSC Server to determine the service state of physical terminations when the MSC Server itself has restarted if it is subsequently unsure of the service state of terminations or when O&M procedures indicate new physical trunks have been commissioned to an in service MGW. It shall also be used for determining the Termination State after MGW Registration (Cold Boot) prior to unblocking devices in the network if the MSC Server has not been informed specifically by Termination Restoration or Termination Out Of Service Procedure. Table 14.1.10.1: AUD\_VAL.req (Audit\_Values) MGC to MGW + +| Address Information | Control information | Bearer information | +|---------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------| +| |

Transaction ID = z

Context ID = Null/Context ID/ALL

Termination ID =

Termination/Root/ALL(see NOTE1)

Audit Descriptor =

Empty/

IndAuditParameter:=

IndAudMediaDescriptor:=

TermStateDescriptor (NOTE3)

Packages (See NOTE2)

NOTE1: "All" shall refer to 1 TDM group. 1 TDM group is at a T1/E1 level It shall not be used for ATM or IP termination.
"Termination" may be used for individual TDM, IP or ATM terminations.

NOTE2: Packages is for
- Null/Root Combination

NOTE3: Pre Rel6 this is performed with Audit Token

| | + +Upon reception of the command in the MGW: + +- The Service State returns the current Service State +- When Packages are requested, the Package Names and Versions are returned + +The following table illustrates the allowed combinations that can be obtained with the AuditValue Command: + +**Table 14.1.10.2: Combinations of AuditValue Command** + +| ContextID | TerminationID | Information Obtained | +|-----------|---------------|-------------------------------------------------------------------------------------------------| +| Specific | Wildcard | Audit of matching Terminations in a Context | +| Specific | Specific | Audit of a single Termination in a Context | +| Null | Root | Audit of Media Gateway state and events | +| Null | Wildcard | Audit of all matching TDM T1/E1 level Terminations in the null Context | +| Null | Specific | Audit of a single Termination outside of any Context | +| All | Wildcard | Audit of all matching TDM T1/E1 level Terminations and the Context to which they are associated | +| All | Specific | (Non-null) ContextID in which the Termination currently exists | + +**Table 14.1.10.3: AUD\_VAL.resp MGW to MGC** + +| Address Information | Control information | Bearer information | +|---------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------| +| | Transaction ID = z
Context ID = Null/Context ID
Termination ID =
Termination/Root/All(seeNOTE1)
Empty Audit Descriptor:
-
AuditToken = Media/IndAudMediaDescriptor=TermStateDescriptor:
Service State = Current Service State
AuditToken = Packages:
Packages Descriptor =
Package Names + Versions
NOTE1: ALL may be returned for a TDM group. | | + +### 14.1.11 Audit Capability + +This procedure is the same as described in the subclause "Audit Capabilities" in ITU-T Recommendation Q.1950 [23] (see 3GPP TS 29.205 [7]). + +### 14.1.12 MGW Capability Change + +This procedure is the same as described in the subclause "BIWF Capability Change" in ITU-T Recommendation Q.1950 [23] (see 3GPP TS 29.205 [7]) with the following clarification:. + +For Capability changes concerning the whole MGW: + +Service Change Reason Media/Event or Signal Capability Failure shall not be used instead the following information shall be used: + +ServiceChange.req (MGW Capability Change) + +MGW to MGC + +**Table 14.1.12.1: MGW Capability Change** + +| Address Information | Control information | Bearer information | +|--------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------|--------------------| +| | Service Change Reason =
Packages Change/ Capability Change
Service Change Info = changed package/property/signal/event/ statistics | | +| Note: The changed package/property/signal/event/ statistics information is FFS | | | + +### 14.1.13 (G)MSC Server Out of Service + +This procedure is the same as that described in the subclause "CCU Initiated Service Cancellation" in ITU-T Recommendation Q.1950 [23] (see 3GPP TS 29.205 [7]) with the following clarification. + +**Table 14.1.13.1: (G)MSC Server Out of Service** + +| Address Information | Control information | Bearer information | +|---------------------|----------------------------------------------------------|--------------------| +| | Service Change Reason = Termination taken out of service | | + +Delay shall not be used. + +### 14.1.14 MGW Resource Congestion Handling - Activate + +If the procedure "MGW Resource Congestion Handling - Activate" is required the following procedure is initiated. + +The MGC sends a MOD.req command with the following information. + +**Table 14.1.14.1: MOD.req(MGW Resource Congestion Handling - Activate) MGC to MGW** + +| Address Information | Control information | Bearer information | +|---------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------| +| | Transaction ID = z
Context ID = Null
Termination ID = Root

NotificationRequested (Event ID = x, "MGW Resource Congestion Handling - Indication") | | + +When the processing of command (1) is complete, the MGW initiates the following procedure. + +**Table 14.1.14.2: MOD.resp (MGW Resource Congestion Handling - Activate) MGW to MGC** + +| Address Information | Control information | Bearer information | +|---------------------|-----------------------------------------------------------------|--------------------| +| | Transaction ID = z
Context ID = Null
TerminationID = Root | | + +### 14.1.15 MGW Resource Congestion Handling - Indication + +If the procedure "MGW Resource Congestion Handling - Indication" is required, the following procedure is initiated: + +The MGW sends a NOT.req command with the following information. + +**Table 14.1.15.1: NOT.req (MGW Resource Congestion Handling - Indication) MGW to MGC** + +| Address Information | Control information | Bearer information | +|---------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------| +| | Transaction ID = z
Context ID = Null
Termination ID = Root

Event_ID (Event ID = x, "MGW Resource Congestion Handling - Indication (Reduction)") | | + +When the processing of command (1) is complete, the MGC initiates the following procedure. + +**Table 14.1.15.2: NOT.resp (MGW Resource Congestion Handling - Indication) MGC to MGW** + +| Address Information | Control information | Bearer information | +|---------------------|------------------------------------------------------------------|--------------------| +| | Transaction ID = z
Context ID = Null
Termination ID = Root | | + +### 14.1.16 Continuity Check Tone + +This procedure is the same as described in Annex B.7.1.1 of ITU-T Recommendation Q.1950 [23] with the following clarification: + +The addition to "Prepare BNC Notify" defined in Annex B.7.1.1 of ITU-T Recommendation Q.1950 [23] shall be applied instead to "Reserve Circuit", as defined in Clause 13.2.2.1 + +Note: This does not preclude the use of the continuity check tone for other maintenance procedures. If the termination is audited it shall report state in service. + +### 14.1.17 Continuity Check Verify + +This procedure is the same as described in Annex B.7.2.1 of ITU-T Recommendation Q.1950 [23]. + +### 14.1.18 Continuity Check Response + +This procedure is the same as described in Annex B.7.1.2 of ITU-T Recommendation Q.1950 [23] with the following clarification: + +The addition to "Prepare BNC Notify" defined in Annex B.7.1.2 of ITU-T Recommendation Q.1950 [23] shall be applied instead to "Reserve Circuit", as defined in Clause 13.2.2.1 + +Note: This does not preclude the use of the continuity check response for other maintenance procedures. If the termination is audited is shall report state in service. + +### 14.1.19 Inactivity Timeout - Activate + +If the procedure "Inactivity Timeout - Activate" is required the following procedure is initiated. + +The MGC sends a MOD.req command with the following information. + +**Table 14.1.19.1: MOD.req (Inactivity Timeout - Activate) MGC to MGW** + +| Address Information | Control information | Bearer information | +|---------------------|-------------------------------------------------------------------------------------------------------------------------------------------------|--------------------| +| | Transaction ID = z
Context ID = Null
Termination ID = Root

NotificationRequested (Event ID = x, "Inactivity Timeout - Indication") | | + +When the processing of command (1) is complete, the MGW initiates the following procedure. + +**Table 14.1.19.2: MOD.resp (Inactivity Timeout - Activate) MGW to MGC** + +| Address Information | Control information | Bearer information | +|---------------------|-----------------------------------------------------------------|--------------------| +| | Transaction ID = z
Context ID = Null
TerminationID = Root | | + +### 14.1.20 Inactivity Timeout – Indication + +When the procedure "Inactivity Timeout indication" is required the following procedure is initiated: the MGW sends a NOT.req command with the following information. + +**Table 14.1.20.1: NOT.req (Inactivity Timeout - Indication) MGW to MGC** + +| Address Information | Control information | Bearer information | +|---------------------|----------------------------------------------------------------------------------------------------------------------------------------|--------------------| +| | Transaction ID = z
Context ID = NULL
Termination ID = Root

Event_ID (Event ID = x,
"Inactivity Timeout - Indication ") | | + +When the processing of command is complete, the MGC initiates the following procedure. + +**Table 14.1.20.2: NOT.resp (Inactivity Timeout - Indication) MGC to MGW** + +| Address Information | Control information | Bearer information | +|---------------------|------------------------------------------------------------------|--------------------| +| | Transaction ID = z
Context ID = NULL
Termination ID = Root | | + +### 14.1. 21 Realm Availability Change – Activation + +The MGC sends a MODIFY request command as in Table 14.1.221.1. + +**Table 14.1.21.1: Realm Availability Change – Activation** + +| Address Information | Control information | Bearer information | +|---------------------|---------------------------------------------------------------------------------------------------------------------------------------|--------------------| +| | Transaction ID = x
Context ID= -
Termination ID = ROOT

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

Event_ID (Event ID = x, "Realm Availability Change (Changed Realms)") | | +| NOTE: The ObservedEvent Parameters returned within the Changed Realms are defined as mandatory since it shall contain at minimum 1 parameter but may contain both Newly Available Realms and Newly Unavailable Realms. | | | + +The MGC responds as in Table 14.1.22.2 + +**Table 14.1.22.2: Realm Availability Change – Indication Ack** + +| Address Information | Control information | Bearer information | +|---------------------|---------------------------------------------------------------|--------------------| +| | Transaction ID = x
Context ID = -
Termination ID = ROOT | | + +## 14.2 Call related H.248 transactions + +Table 14.2.1 shows the relationship between each call-related procedure in ITU-T Recommendation Q.1950 [23] (see 3GPP TS 29.205 [7]) and the corresponding stage 2 procedure defined in 3GPP TS 23.205 [2] , as well as specifying the requirement for support of each procedure on the Mc interface. + +**Table 14.2.1: Correspondence between ITU-T Recommendation Q.1950 [23] call-related transactions and 3GPP TS 23.205 [2], 3GPP TS 23.153 [1], 3GPP TS 23.231 [54] and 3GPP TS 29.292 [60] procedures** + +| Transaction used in Q.1950 | Procedure defined in 3GPP TS 23.205 [2], 23.153 [1], 23.231 [54] or 29.292 [60] | Support | Comments | +|---------------------------------------|---------------------------------------------------------------------------------|-----------|------------------------------------------------------------------------------| +| Change_Topology | Change Flow Direction | Mandatory | | +| Join | Join Bearer Termination | Mandatory | | +| Isolate | Isolate Bearer Termination | Mandatory | | +| Establish_BNC_Notify+(tunnel) | Establish Bearer | Mandatory | | +| Prepare_BNC_Notify+(tunnel) | Prepare Bearer | Mandatory | | +| Cut_Through | Change Through Connection | Mandatory | | +| Not defined in Q.1950 | Activate Interworking Function | Optional | | +| Cut_BNC (include several procedures). | Release Bearer (Release Bearer and Release termination) | Mandatory | | +| BNC Established | Bearer Established | Mandatory | | +| BNC Release | Bearer Released | Mandatory | | +| Insert_Tone | Send Tone | Mandatory | | +| Insert_Announcement | Play Announcement | Mandatory | | +| Signal Completion | Announcement Completed | Mandatory | | +| Detect_Digit | Detect DTMF | Mandatory | | +| Insert_Digit | Send DTMF | Mandatory | | +| Digit Detected | DTMF | Mandatory | | +| Confirm_Char | Confirm Char | Optional | | +| Modify_Char | Modify Char | Optional | | +| Reserve_Char | Reserve Char | Optional | | +| BNC Modified | Bearer Modified | Optional | | +| Echo Canceller | Activate Voice Processing Function | Mandatory | | +| BNC Modification failed | Bearer Modified Failed | Optional | | +| Tunnel (MGC-MGW) | Tunnel Information Down | Optional | Shall be supported for BICC associated Nb interface transport protocol on IP | +| Tunnel (MGW-MGC) | Tunnel Information Up | Optional | Shall be supported for BICC associated Nb interface transport protocol on IP | +| Insert_Tone | Stop Tone | Mandatory | | +| Insert_Announcement | Stop Announcement | Mandatory | | +| Detect_Digit | Stop DTMF Detection | Optional | | +| Insert_Digit | Stop DTMF | Mandatory | | +| Signal Completion | Tone Completed | Optional | | +| Not defined | Reserve Circuit | Mandatory | | +| Not defined | Command Rejected | Mandatory | | +| Not defined | TFO Activation | Optional | | +| Not defined | Codec Modify | Optional | | +| Not defined | Optimal Codec and Distant List_Notify | Optional | | +| Not defined | Distant Codec List | Optional | | +| Not defined | TFO status Notify | Optional | | +| Not defined | TFO status | Optional | | +| Modify_Char | Modify Bearer Characteristics | Mandatory | | +| Not defined | Rate Change | Optional | | +| Not defined | Bearer Modification Support | Optional | | +| Not defined | Protocol Negotiation Result | Optional | | +| Reserve_Char | Reserve Bearer Characteristics | Optional | | +| Confirm_Char | Confirm Bearer Characteristics | Optional | | +| ECS_Indication | Emergency Call Indication | Optional | | +| Continuity Check Tone | Continuity Check Tone | Optional | See 14.1.16 | +| Continuity Check Verify | Continuity Check Verify | Optional | See 14.1.17 | +| Continuity Check Response | Continuity Check Response | Optional | See 14.1.18 | +| Not Defined | Prepare IP Transport | Optional | Shall be supported if IP used on Iu interface | +| Not Defined | Modify IP Transport Address | Optional | Shall be supported if IP used on Iu interface | + +| | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------|-----------|----------------------------------------------------------------------------------------------------------------------------------------------------| +| Not defined | Termination heartbeat | Mandatory | To allow detection of hanging contexts and terminations in the MGW that may result e.g. from a loss of communication between the MSC-S and the MGW | +| Not Defined | Reserve RTP Connection Point | Optional | Required for SIP-I associated Nb and A interface over IP | +| Not Defined | Configure RTP Connection Point | Optional | Required for SIP-I associated Nb and A interface over IP | +| Not defined | Reserve and Configure RTP Connection Point | Optional | Required for SIP-I associated Nb and A interface over IP | +| Not defined | Media Inactivity Notification | Optional | See 14.2.55 | +| Not defined | ECN Failure Indication (NOTE 2) | Optional | Only applicable if ECN support is required | +| NOTE 1: A procedure defined in table 3 can be combined with another procedure in the same action. This means that they can share the same contextID and termination ID(s). | | | | +| NOTE 2: ECN support is only applicable for MSC enhanced for ICS. | | | | + +### 14.2.1 Change Flow Direction + +This procedure is the same as that defined in the subclause "Change Connection Topology" in ITU-T Recommendation Q.1950 [23] (see 3GPP TS 29.205 [7]) with the following additions. + +**Table 14.2.1.1: Change Flow Direction request additions** + +| Address Information | Control information | Bearer information | +|---------------------|-------------------------------------------------------------------------------------------------------------------|--------------------| +| | Context ID = c1,?
Connection Configuration =
(TerminationID= x1, ?
TerminationID=x2,?
[type = x]),... | | + +This procedure shall not be used for Multiparty bridge contexts. + +The Change Flow Direction response shall contain the Context ID. + +A command is only required if this procedure is combined with some other procedure which changes a termination functionality. + +### 14.2.2 Isolate Bearer Termination + +This procedure is the same as that defined in the subclause "Isolate" in ITU-T Recommendation Q.1950 [23] (see 3GPP TS 29.205 [7]). + +### 14.2.3 Join Bearer Termination + +This procedure is the same as that defined in the subclause "Join" in ITU-T Recommendation Q.1950 [23] (see 3GPP TS 29.205 [7]). + +### 14.2.4 Establish Bearer + +This procedure is the same as that defined in the subclause "Establish BNC\_notify" in ITU-T Recommendation Q.1950 [23] (see 3GPP TS 29.205 [7]) except that the Command MOV shall not be used, BNC events are requested optionally and independently and with additions as shown below. If IPBCP Tunnel Option 1 is required then the Command Response shall always precede the IPBCP Notify Command. + +**Table 14.2.4.1: Establish Bearer additions** + +| Address Information | Control information | Bearer information | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

UP mode = Mode

UP version = version

Delivery of erroneous SDUs = value

Interface = interface

If support mode:
Initdirection = initdir

If indication on Protocol Negotiation Result requested:
NotificationRequested (Event ID = x, "Prot Negotiation Result")

If indication on Rate Change requested:
NotificationRequested (Event ID = x, "RateChange")

If detection of hanging termination is requested:
(NOTE 3)
NotificationRequested (Event ID = x, "termination heartbeat")

If Listener context: number of desired listener context terminations = required listener context terminations

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

If indication on BNC Established requested:
NotificationRequested (Event ID = x, "BNC Established")

If indication on BNC Modified requested:
NotificationRequested (Event ID = x, "BNC Modified")

If indication on BNC Mod Failed requested:
NotificationRequested (Event ID = x, "BNC Mod Failed")

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

|

If SCUDIF multimedia call :
MuMe codec (NOTE 1)

If data call other than SCUDIF multimedia call and Access Termination or Anchor MGW Network Termination:
PLMN bearer capability = PLMN capability (NOTE2)

If GSM data call other than SCUDIF multimedia call and (Anchor MGW Network Termination):
GSM channel coding = coding

| +|

NOTE1: Bearer Service Characteristics shall be excluded when this property is included.

NOTE2: Bearer Service Characteristics may be included.

NOTE3: Termination heartbeat notification shall be included when requesting a new bearer termination.

| | | + +### 14.2.5 Prepare Bearer + +This procedure is the same as that defined in the subclause "Prepare\_BNC\_notify" in ITU-T Recommendation Q.1950 [23] (see 3GPP TS 29.205 [7]) except that the Commands MOD and MOV shall not be used, the MGW shall not choose the BNC Characteristics, the BNC-cut-through-capability shall not be used, BNC events are requested optionally and independently and with additions as shown below. + +**Table 14.2.5.1: Prepare Bearer additions** + +| Address Information | Control information | Bearer information | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

UP mode = mode

UP version = version

Delivery of erroneous SDUs = value

Interface = interface

If support mode:
Initdirection = initdir

If CTM call and Access Termination:
State= ctmstate
Transport= ctmtransport
Version= ctmtext version

If data call and Non-Anchor MGW RAN-side termination:
Bitrate = bitrate (NOTE1)

If indication on Protocol Negotiation Result requested:
NotificationRequested (Event ID = x, "Prot Negotiation Result")

If indication on Rate Change requested:
NotificationRequested (Event ID = x, "RateChange")

If indication on Bearer Modification requested:
NotificationRequested (Event ID = x, "Bearer Modification Support")

If notification on CTM negotiation result requested:
NotificationRequested (Event ID = x, "connchange ")

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

If VGCS/VBS context: number of needed conference terminations = required conference terminations

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

If indication on BNC Established requested:
NotificationRequested (Event ID = x, "BNC Established")

If indication on BNC Modified requested:
NotificationRequested (Event ID = x, "BNC Modified")

If indication on BNC Mod Failed requested:
NotificationRequested (Event ID = x, "BNC Mod Failed")

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

|

If SCUDIF multimedia call and (network termination or Anchor MGW Access Termination):
MuMe codec (NOTE2)

If data call other than SCUDIF multimedia call and (Anchor MGW Access Termination or Anchor MGW Network Termination):
PLMN bearer capability = PLMN capability (NOTE3)

If GSM data call other than SCUDIF multimedia call and Anchor MGW Network Termination:
GSM channel coding = coding

| +|

NOTE1 : Bearer Service Characteristics shall be excluded when this property is included except for the case when bitrate = 64000 and then Bearer Service Characteristics may be included. Bitrate is optional for transparent data calls when the data rate is 64k bits/s.

NOTE2: Bearer Service Characteristics shall be excluded when this property is included.

NOTE3: Bearer Service Characteristics shall be excluded when this property is included, except for Anchor MGW network termination for which it may be included.

| | | + +### 14.2.6 Change Through Connection + +This procedure is the same as that defined in the subclause "Cut Through" in ITU-T Recommendation Q.1950 [23] (see 3GPP TS 29.205 [7]) with the following clarification and deletion. + +NotificationRequested = (Event ID = x, "Cut Through") is deleted and therefore only the Explicit (MGC Controlled Cut-Through procedure is supported. + +The MGW may support No\_Data RTP frames on RTP-A and RTP-CN terminations during the call establishment phase, i.e. when not in TrFO (see 3GPP TS 26.102 [26]), in which case it shall support it independently of the Stream Mode. + +### 14.2.7 Activate Interworking Function + +When the procedure "Activate Interworking Function" is required the following procedure is initiated: + +The MGC sends a MOD.req command with the following information. + +**Table 14.2.7.1: MOD.req (Activate Interworking function) MGC to MGW** + +| Address Information | Control information | Bearer information | +|---------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------| +| | Transaction ID = z
Context ID = c1
Termination ID = bearer1

Signal=actpro

If indication on Protocol Negotiation Result requested:
NotificationRequested (Event ID = x, "Prot Negotiation Result")

If indication on Rate Change requested:
NotificationRequested (Event ID = x, "RateChange") | | + +When the processing of command (1) is complete, the MGW initiates the following procedure. + +**Table 14.2.7.2: MOD.resp (Activate Interworking function) MGW to MGC** + +| Address Information | Control information | Bearer information | +|---------------------|------------------------------------------------------------------|--------------------| +| | Transaction ID = z
Context ID = c1
TerminationID = bearer1 | | + +### 14.2.8 Release procedures + +This subclause includes a number of procedures. + +#### 14.2.8.1 Release Bearer + +This procedure is the same as that defined in the subclause "Release" in ITU-T Recommendation Q.1950 [23] (see 3GPP TS 29.205 [7]) including the Modify command in the transaction with the clarification that the Termination ID and/or Context ID may be wildcarded (ALL). + +#### 14.2.8.2 Release Termination + +This procedure is the same as that defined in the subclause "Release" in ITU-T Recommendation Q.1950 [23] (see 3GPP TS 29.205 [7]) including a Subtract command in the transaction with the following additions. + +**Table 14.2.8.1 Sub.req (Release termination) MGC to MGW** + +| Address Information | Control information | Bearer information | +|---------------------|---------------------------------------------------------------------------|--------------------| +| | Transaction ID = z
Context ID = c1/ALL
Termination ID = bearer1/ALL | | + +**Table 14.2.8.2.2: Sub.resp (Release termination) MGW to MGC** + +| Address Information | Control information | Bearer information | +|---------------------|------------------------------------------------------------------------------------------------------------------|--------------------| +| | Transaction ID = z
Context ID = c1/ALL
Termination ID = bearer1/ALL
If requested
Statistics= Ctmbits | | + +### 14.2.9 Bearer Released + +This procedure is the same as that defined in the subclause "BNC Release" in ITU-T Recommendation Q.1950 [23] (see 3GPP TS 29.205 [7]) with the following clarification: + +Termination ID shall be provided in the response. . + +The MGW may, as a configurable option, inhibit the reporting of normal AAL2 bearer release on a Iu termination. + +### 14.2.10 Bearer Established + +This procedure is the same as that defined in the subclause "BNC Established" in ITU-T Recommendation Q.1950 [23] (see 3GPP TS 29.205 [7]) with the following clarification: + +Termination ID shall be provided in the response. + +### 14.2.11 Send Tone + +This procedure is the same as that defined in the subclause "Media Content Insertion" - "Insert Tone" in ITU-T Recommendation Q.1950 [23] (see 3GPP TS 29.205 [7]) with the following additions. + +**Table 14.2.11.1: Send Tone additions** + +| Address Information | Control information | Bearer information | +|---------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------| +| | If CAMEL Prepaid Warning Tone
Signal = warning tone
Or
Signal = flextone

If detection of hanging termination is requested:
NotificationRequested (Event ID = x,
"termination heartbeat") | | + +Signal Direction shall be either "internal" or "external". + +Only the Tone Signal Ids shall be used, not the Tone Ids within the PlayTone Signal Id. + +The termination heartbeat event shall be configured when requesting a new ephemeral bearer termination. + +### 14.2.12 Play Announcement + +This procedure is the same as that defined in the subclause "Media Content Insertion" - "Insert Announcement" in ITU-T Recommendation Q.1950 [23] (see 3GPP TS 29.205 [7]) with the following clarifications: + +**Table 14.2.12.1: Play Announcement additions** + +| Address Information | Control information | Bearer information | +|---------------------|-----------------------------------------------------------------------------------------------------------------------|--------------------| +| | If detection of hanging termination is requested:
NotificationRequested (Event ID = x,
"termination heartbeat") | | + +Signal Direction shall be either "internal" or "external". + +Stream mode may be maintained as for the ongoing call or may be restricted to "send only". + +Signal Lists shall be supported. + +The termination heartbeat event shall be configured when requesting a new ephemeral bearer termination. + +### 14.2.13 Send DTMF + +This procedure is the same as that defined in the subclause "Media Content Insertion" - "Insert Digit" in ITU-T Recommendation Q.1950 [23] (see 3GPP TS 29.205 [7]). The MGW shall ensure the minimum duration timing and minimum interval timing is achieved in accordance with the DTMF timing defined in TS 23.014 [27]. Maximum duration shall also be controlled by the MGW if required by the network. + +### 14.2.14 Detect DTMF + +This procedure is the same as that defined in the subclause "Media Content Detection" - "Detect Digit" in ITU-T Recommendation Q.1950 [23] (see 3GPP TS 29.205 [7]) with the exception that "long tone detected" (Event Id ltd) shall not be used. In addition "start tone detected" (EventId std) is optional and if not supported shall result in the command error code #449 "Unsupported or Unknown Parameter or Property Value". If both a request for "start tone detected" and "end tone detected" is received by the MGW that does not support "start tone detected" then it shall only report a notification upon detecting the end of a digit. + +Parameter *Duration* shall not be used. + +All digits shall be requested i.e. Tone\_Id shall be wildcarded. + +### 14.2.15 Report DTMF + +This procedure is the same as that defined in the subclause "Detected Digit" in ITU-T Recommendation Q.1950 [23] (see 3GPP TS 29.205 [7]) with the following clarification: + +Termination ID shall be provided in the response. + +### 14.2.16 Announcement Completed + +This procedure is the same as that defined in the subclause "Signal Completion" in ITU-T Recommendation Q.1950 [23] (see 3GPP TS 29.205 [7]) with the following clarification: + +Termination ID shall be provided in the response. + +The Signal List ID should be provided additionally if the completed Announcement belongs to a Signal List. + +### 14.2.17 Activate Voice Processing Function + +When the procedure "Activate Voice Processing Function" (VPF) is required the following procedure is initiated: + +The MGC sends an ADD.req, MOD.req or MOV.req command with the following information. + +**Table 14.2.17.1: ADD.req/MOD.req/MOV.req (Activate Voice Processing Function) MGC to MGW** + +| Address Information | Control information | Bearer information | +|---------------------|---------------------------------------------------------------------------------------------------|--------------------| +| | Transaction ID = z
Context ID = c1
Termination ID = bearer1

ActivateVPF "ec"= on/off | | + +When the MGW receives the command, it shall associate the relevant voice processing function resources with the specified termination. + +When the processing of command (1) is complete, the MGW may initiate the "Voice Processing Function Ack" procedure. + +**14.2.17.2: ADD.resp/MOD.resp/MOV.resp (Voice Processing Function Ack) MGW to MGC** + +| Address Information | Control information | Bearer information | +|---------------------|-------------------------------------------------------------------|--------------------| +| | Transaction ID = z
Context ID = c1
Termination ID = bearer1 | | + +### 14.2.18 Reserve Circuit + +This procedure is activated when the "Reserve Circuit" procedure is initiated. + +An ADD.req command is sent with the following information. + +**Table 14.2.18.1: ADD.req (Reserve\_Circuit) CSM to BIWF** + +| Address Information | Control information | Bearer information | +|---------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | Transaction ID = z
Termination ID = bearer1

Context Requested:
Context ID = ?
Context Provided:
Context ID = c1

If CTM call and Access Termination:
State= ctmstate
Transport= ctmtransport
Version= ctmtext version

If indication on Protocol Negotiation Result requested:
NotificationRequested (Event ID = x, "Prot Negotiation Result")

If indication on Rate Change requested:
NotificationRequested (Event ID = x, "RateChange")
If notification on CTM negotiation result requested:
NotificationRequested (Event ID = x, " connchange ")
If detection of hanging termination is requested:
NotificationRequested (Event ID = x, "termination heartbeat")

If indication on Bearer Released requested:
NotificationRequested (Event ID = x, "BNC Release (Cause)") – as defined in ITU-T Recommendation Q.1950 [23]

If Listener context: number of desired listener context terminations = required listener context terminations | Bearer Service Characteristics

If data call, Access Termination:
PLMN capabilities
If GSM data call, Access Termination:
GSM channel coding = coding | + +Upon completion of processing command (1) an ADD.resp command (2) is sent. + +**Table 14.2.18.2: ADD.resp BIWF to CSM** + +| Address Information | Control information | Bearer information | +|---------------------|------------------------------------------------------------------|--------------------| +| | Transaction ID = z
Context ID = c1
TerminationID = bearer1 | | + +### 14.2.19 Tunnel Information Up + +This procedure is the same as that defined in the subclause "Tunnel" in ITU-T Recommendation Q.1950 [23] (see 3GPP TS 29.205 [7]) with the clarification that BT/TunOpt = ? and BT/TunOpt = NO shall not be used. + +NOTE: This procedure is always initiated from the MGW. + +### 14.2.20 Tunnel Information Down + +This procedure is the same as that defined in the subclause "Tunnel" in ITU-T Recommendation Q.1950 [23] (see 3GPP TS 29.205 [7]) with the clarification that BT/TunOpt = ? and BT/TunOpt = NO shall not be used. + +NOTE: This procedure is always initiated from the MGC. + +### 14.2.21 Tone Completed + +This procedure is the same as that defined in the subclause "Signal.Completion" in ITU-T Recommendation Q.1950 [23] (see 3GPP TS 29.205 [7]) with the following clarification: + +Termination ID shall be provided in the response. + +### 14.2.22 Stop Announcement + +This procedure is the same as that defined in the subclause "Insert Announcement" in ITU-T Recommendation Q.1950 [23] (see 3GPP TS 29.205 [7]) with the following clarification. The signal descriptor shall not include any signal. + +### 14.2.23 Stop Tone + +This procedure is the same as that defined in the subclause "Insert Tone" in ITU-T Recommendation Q.1950 [23] (see 3GPP TS 29.205 [7]) with the following clarification. The signal descriptor shall not include any signal. + +### 14.2.24 Stop DTMF Detection + +This procedure is the same as that defined in the subclause "Detect Digit" in ITU-T Recommendation Q.1950 [23] (see 3GPP TS 29.205 [7]) with the following clarification. The eventDescriptor shall not include any event. + +### 14.2.25 Stop DTMF + +This procedure is the same as that defined in the subclause "Media Content Insertion" - "Insert Digit" in ITU-T Recommendation Q.1950 [23] (see 3GPP TS 29.205 [7]). The signal descriptor shall not include any signal. The MGW shall ensure the minimum duration timing and minimum interval timing is achieved in accordance with the DTMF timing defined in TS 23.014 [27]. Maximum duration shall also be controlled by the MGW if required by the network. + +### 14.2.26 Confirm Char + +This procedure is the same as that defined in the subclause "Confirm Char" in ITU-T Recommendation Q.1950 [23] (see 3GPP TS 29.205 [7]). + +### 14.2.27 Modify Char + +This procedure is the same as that defined in the subclause "Modify Char" in ITU-T Recommendation Q.1950 [23] (see 3GPP TS 29.205 [7]). + +### 14.2.28 Reserve Char + +This procedure is the same as that defined in the subclause "Reserve Char" in ITU-T Recommendation Q.1950 [23] (see 3GPP TS 29.205 [7]). + +### 14.2.29 Bearer Modified + +This procedure is the same as that defined in the subclause "BNC Modified" in ITU-T Recommendation Q.1950 [23] (see 3GPP TS 29.205 [7]). + +### 14.2.30 Bearer Modification Failed + +This procedure is the same as that defined in the subclause "BNC Modification failure" in ITU-T Recommendation Q.1950 [23] (see 3GPP TS 29.205 [7]). + +### 14.2.31 TFO Activation + +When the procedure "TFO activation" is required the following procedure is initiated: + +The MGC sends a ADD.req, MOD.req or MOV.req command with the following information. + +**Table 14.2.31.1: ADD.req/MOD.req/MOV.req (TFO activation) MGC to MGW** + +| Address Information | Control information | Bearer information | +|---------------------|-------------------------------------------------------------------------------------------------------------------------------------------------|--------------------| +| | Transaction ID = z
Context ID = c1
Termination ID =
bearer1
tfoenable = tfoactvalue
If TFO codec list:
Property= TFOcodecList | | + +When the processing of command (1) is complete, the MGW initiates the following procedure. + +**Table 14.2.31.2: ADD.resp/MOD.resp/MOV.resp (TFO activation) MGW to MGC** + +| Address Information | Control information | Bearer information | +|---------------------|----------------------------------------------------------------|--------------------| +| | Transaction ID = z
Context ID = c1
TerminationID=bearer1 | | + +### 14.2.32 Optimal Codec and Distant List\_Notify + +When the procedure "Optimal Codec and Distant List" is required the following procedure is initiated: + +The MGC sends a ADD.req, MOD.req or MOV.req command with the following information. + +**Table 14.2.32.1: ADD.req/MOD.req/MOV.req (Codec modify and distant list) MGC to MGW** + +| Address Information | Control information | Bearer information | +|---------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------| +| | Transaction ID = z
Context ID = c1
Termination ID = bearer1
Property= TFOcodecList

NotificationRequested (Event ID = x, "Codec modify")
NotificationRequested (Event ID = x, "Distant List") | | + +When the processing of command (1) is complete, the MGW initiates the following procedure. + +**Table 14.2.32.2: ADD.resp/MOD.resp/MOV.resp (Optimal codec and codec list) MGW to MGC** + +| Address Information | Control information | Bearer information | +|---------------------|-----------------------------------------------------------------|--------------------| +| | Transaction ID = z
Context ID = c1
TerminationID= bearer1 | | + +### 14.2.33 Codec Modify + +When the procedure "Codec Modify" is required the following procedure is initiated: + +The MGW sends a NOT.req command with the following information. + +**Table 14.2.33.1: NOT.req (Codec modify) MGW to MGC** + +| Address Information | Control information | Bearer information | +|---------------------|-------------------------------------------------------------------------------------------------------------------------------|--------------------| +| | Transaction ID = z
Context ID = c1
Termination ID = bearer1

Event ( Event Id = x, "codec_modify (optimalcodec)") | | + +When the processing of command (1) is complete, the MGC initiates the following procedure. + +**Table 14.2.33.2: NOT.resp (Codec modify) MGC to MGW** + +| Address Information | Control information | Bearer information | +|---------------------|-------------------------------------------------------------------|--------------------| +| | Transaction ID = z
Context ID = c1
Termination ID = bearer1 | | + +### 14.2.34 Distant Codec List + +When the procedure "Distant Codec List" is required the following procedure is initiated: + +The MGW sends a NOT.req command with the following information. + +**Table 14.2.34.1: NOT.req (Distant codec list) MGW to MGC** + +| Address Information | Control information | Bearer information | +|---------------------|--------------------------------------------------------------------------------------------------------------------------------|--------------------| +| | Transaction ID = z
Context ID = c1
Termination ID = bearer1

Event(Event ID = x, " distant_codec_list(distlist) ") | | + +When the processing of command (1) is complete, the MGC initiates the following procedure. + +**Table 14.2.34.2: NOT.resp (Distant codec list) MGC to MGW** + +| Address Information | Control information | Bearer information | +|---------------------|-------------------------------------------------------------------|--------------------| +| | Transaction ID = z
Context ID = c1
Termination ID = bearer1 | | + +### 14.2.35 Command Rejected + +When the procedure "Command Reject" is required the following procedure is initiated: + +The MGW/MGC sends .resp to any command.req with the following information. + +**Table 14.2.34.1: NYcommand.resp (command reject ) GW/MGC to MGC/MGW** + +| Address Information | Control information | Bearer information | +|---------------------|-------------------------------------------------------------------------|--------------------| +| | Transaction ID = z
Context ID = c1 or no context

Reason=Error | | + +### 14.2.36 Modify Bearer Characteristics + +This procedure is the same as that defined in the subclause "Modify Char" in ITU-T Recommendation Q.1950 [23] (see 3GPP TS 29.205 [7]) with additions as shown below. + +**Table 14.2.36.1: Modify bearer Characteristics additions** + +| Address Information | Control information | Bearer information | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | If framing protocol used:

UP mode = mode
UPversion =version
Delivery of erroneous SDUs=value
Interface=interface

If support mode:
Initdirection=initdir

If data call and Non-Anchor MGW RAN-side termination:
Bitrate = bitrate (NOTE1)
If indication on Protocol Negotiation Result requested:
NotificationRequested (Event ID = x, "Prot Negotiation Result")

If indication on Rate Change requested:
NotificationRequested (Event ID = x, "RateChange") | If SCUDIF multimedia call and (network termination or Anchor MGW Access Termination):
MuMe codec (NOTE 2)

If data call other than SCUDIF multimedia call and (Anchor MGW Access Termination or Anchor MGW Network Termination):

PLMN bearer capability = PLMN capability (NOTE3)

If GSM data call other than SCUDIF multimedia call and Anchor MGW Network Termination:
GSM channel coding=coding | +| NOTE1 : Bearer Service Characteristics shall be excluded when this property is included except for the case when bitrate = 64000 and then Bearer Service Characteristics may be included. Bitrate is optional for transparent data calls when the data rate is 64k bits/s.
NOTE2: Bearer Service Characteristics shall be excluded when this property is included.
NOTE3: Bearer Service Characteristics shall be excluded when this property is included, except for Anchor MGW network termination for which it may be included. | | | + +If the "Modify Bearer Characteristics" procedure contains a codec that is not currently in use at the Termination when it receives this procedure, and if the framing protocol is used in support mode, the MGW shall be prepared to handle a framing protocol initialisation. If the "Modify Bearer Characteristics" contains no codec or the codec that is already in use at the Termination when it receives this procedure, the MGW does not need to be prepared to handle a framing protocol initialisation. + +## 14.2.37 Protocol Negotiation Result + +When the procedure "Protocol Negotiation Result" is required the following procedure is initiated: + +The MGW sends a NOT.req command with the following information. + +**Table 14.2.37.1: NOT.req (Protocol negotiation result) MGW to MGC** + +| Address Information | Control information | Bearer information | +|---------------------|--------------------------------------------------------------------------------------------------------------------------|--------------------| +| | Transaction ID = z
Context ID = c1
Termination ID = bearer1

Event (Event ID = x, " protres (Result,Cause)") | | + +When the processing of command (1) is complete, the MGC initiates the following procedure. + +**Table 14.2.37.2: NOT.resp (Protocol negotiation result) MGC to MGW** + +| Address Information | Control information | Bearer information | +|---------------------|-------------------------------------------------------------------|--------------------| +| | Transaction ID = z
Context ID = c1
Termination ID = bearer1 | | + +## 14.2.38 Rate Change + +When the procedure "Rate Change" is required the following procedure is initiated: + +The MGW sends a NOT.req command with the following information. + +**Table 14.2.38.1: NOT.req (Rate change) MGW to MGC** + +| Address Information | Control information | Bearer information | +|---------------------|----------------------------------------------------------------------------------------------------------------|--------------------| +| | Transaction ID = z
Context ID = c1
Termination ID = bearer1

Event (Event ID = x, "ratechg(rate)") | | + +When the processing of command (1) is complete, the MGC initiates the following procedure. + +**Table 14.2.38.2: NOT.resp (Rate change) MGC to MGW** + +| Address Information | Control information | Bearer information | +|---------------------|-------------------------------------------------------------------|--------------------| +| | Transaction ID = z
Context ID = c1
Termination ID = bearer1 | | + +## 14.2.39 Bearer Modification Support + +When the procedure "Bearer Modification Support" is required, the following procedure is initiated: + +The MGW sends a NOT.req command with the following information to indicate that the bearer can be modified. + +**Table 14.2.39.1: NOT.req (Bearer Modification Support) MGW to MGC** + +| Address Information | Control information | Bearer information | +|---------------------|----------------------------------------------------------------------------------------------------------------|--------------------| +| | Transaction ID = z
Context ID = c1
Termination ID = bearer1

Event (Event ID = x, "mod_link_supp") | | + +When the processing of command (1) is complete, the MGC initiates the following procedure. + +**Table 14.2.39.2: NOT.resp (Bearer Modification Support) MGC to MGW** + +| Address Information | Control information | Bearer information | +|---------------------|-------------------------------------------------------------------|--------------------| +| | Transaction ID = z
Context ID = c1
Termination ID = bearer1 | | + +## 14.2.40 CTM report + +When the procedure "CTM report" is required the following procedure is initiated: + +The MGW sends a NOT.req command with the following information. + +**Table 14.2.40.1: NOT.req (CTM report) MGW to MGC** + +| Address Information | Control information | Bearer information | +|---------------------|-----------------------------------------------------------------------------------------------------------------------------|--------------------| +| | Transaction ID = z
Context ID = c1
Termination ID = bearer1

Event (Event ID = x, "connchange (connchnge
)") | | + +When the processing of command (1) is complete, the MGC initiates the following procedure. + +**Table 14.2.40.2: NOT.resp (CTM report) MGC to MGW** + +| Address Information | Control information | Bearer information | +|---------------------|-------------------------------------------------------------------|--------------------| +| | Transaction ID = z
Context ID = c1
Termination ID = bearer1 | | + +## 14.2.41 Prepare IP transport + +This procedure is activated when the "Prepare IP transport" procedure is initiated. + +An ADD.req command is sent with the following information. + +Table 14.2.41.1: ADD.req (Prepare IP transport) MGC to MGW + +| Address Information | Control information | Bearer information | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Local Descriptor {
lu IP Address
= ?
lu IP Port = ?
} | Transaction ID = z
Termination ID = ?
Logical Port ID = y
If Context Requested:
Context ID = ?
If Context Provided:
Context ID = c1

UP mode = mode
UP version = version
Delivery of erroneous SDUs = value
Interface = interface

If support mode:
Initdirection = initdir

If CTM call and Access Termination:
State= ctmstate
Transport= ctmtransport
Version= ctmtext version
If data call and Non-Anchor MGW RAN-side termination:
Bitrate = bitrate (NOTE1)

If indication of BNC Established requested:
Notification_Requested (Event ID = x, "BNC Connected")

If indication of BNC Release requested:
Notification_Requested (Event ID = x, "BNC Release (Cause)")

If indication of BNC Modified requested:
Notification_Requested (Event ID = x, "BNC Modified")

If indication of BNC Mod Failed requested:
Notification_Requested (Event ID = x, "BNC Mod Failed")

(all bearer change notifications as defined in ITU-T Recommendation Q.1950 [23])

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

NotificationRequested (Event ID = x, "termination heartbeat") | If SCUDIF multimedia call and Anchor MGW Access Termination:
MuMe codec (NOTE 2)

If data call other than SCUDIF multimedia call, Anchor MGW Access Termination:
PLMN bearer capability = PLMN capability (NOTE2)

If data call and Non-Achor RAN termination:
Bearer Service Characteristics (NOTE 1)

If speech call, Access Termination: Codec

Bearer Characteristics = "IP" | +| NOTE1 : Bearer Service Characteristics shall be excluded when this property is included except for the case when bitrate = 64000 and then Bearer Service Characteristics may be included. Bitrate is optional for transparent data calls when the data rate is 64k bits/s.. | | | +| NOTE2: Bearer Service Characteristics shall be excluded when this property is included. | | | + +When the processing of command (1) is complete, the MGW initiates the following procedure. + +**Table 14.2.41.2: ADD.resp (Prepare IP transport) MGW to MGC** + +| Address Information | Control information | Bearer information | +|------------------------------------------------------------------------------|-------------------------------------------------------------------|--------------------| +| Local Descriptor {
lu IP Address = IPaddress
lu IP Port = UDPport
} | Transaction ID = z
Context ID = c1
Termination ID = bearer1 | | + +## 14.2.42 Modify IP transport address + +This procedure is activated when the "Modify IP transport address" procedure is initiated. + +A MOD.req command is sent with the following information. + +**Table 14.2.42.1: MOD.req (Modify IP transport address) MSC to MGW** + +| Address Information | Control information | Bearer information | +|-------------------------------------------------------------------------------|-------------------------------------------------------------------|--------------------| +| Remote Descriptor {
lu IP Address = IPaddress
lu IP Port = UDPport
} | Transaction ID = z
Context ID = c1
Termination ID = bearer1 | | + +When the processing of command (1) is complete, the MGW initiates the following procedure. + +**Table 14.2.42.2: MOD.resp (Modify Ip transport address) MGW to MGC** + +| Address Information | Control information | Bearer information | +|---------------------|----------------------------------------------------------------|--------------------| +| | Transaction ID = z
Context ID = c1
TerminationID=bearer1 | | + +## 14.2.43 Reserve Bearer Characteristics + +This procedure is the same as that defined in the subclause "Reserve Char" in ITU-T Recommendation Q.1950 [23] (see 3GPP TS 29.205 [7]) with additions as shown below. + +**Table 14.2.43.1: Reserve Bearer Characteristics additions** + +| Address Information | Control information | Bearer information | +|---------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------| +| | If framing protocol used:

UP mode = mode
UPversion =version
Delivery of erroneous
SDUs=value
Interface=interface
Initdirection=initdirection | | + +If the "Reserve Bearer Characteristics" procedure contains a codec that is not currently in use at the Termination when it receives this procedure, and if the framing protocol is used in support mode, the MGW shall be prepared to handle a framing protocol initialisation. If the "Reserve Bearer Characteristics" contains no codec or the codec that is already in use at the Termination when it receives this procedure, the MGW does not need to be prepared to handle a framing protocol initialisation. + +## 14.2.44 Confirm Bearer Characteristics + +This procedure is the same as that defined in the subclause "Confirm Char" in ITU-T Recommendation Q.1950 [23] (see 3GPP TS 29.205 [7]) with additions as shown below. + +**Table 14.2.44: Confirm Bearer Characteristics additions** + +| Address Information | Control information | Bearer information | +|---------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------| +| | If framing protocol used:

UP mode = mode
UPversion =version
Delivery of erroneous SDUs=value
Interface=interface
Initdirerection=initdirection | | + +If the "Confirm Bearer Characteristics" procedure contains a codec that is not currently in use at the Termination when it receives this procedure, and if the framing protocol is used in support mode, the MGW shall be prepared to handle a framing protocol initialisation. If the "Confirm Bearer Characteristics" contains no codec or the codec that is already in use at the Termination when it receives this procedure, the MGW does not need to be prepared to handle a framing protocol initialisation. + +## 14.2.45 Trace activation/deactivation + +This procedure is activated when the "Trace activation/deactivation" procedure is initiated. + +An ADD.req command is sent with the following information. + +**Table 14.2.45.1: ADD.req/MOD.req (Trace activation/deactivation) MGC to MGW** + +| Address Information | Control information | Bearer information | +|---------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------| +| | Transaction ID = z
Termination ID = bearer1

Context ID = c1

Trace Reference
Trace Recording Session Reference
Trace Depth
Triggering events
List of interfaces

IMSI
IMEI(SV)

Trace activity control = trace activity request

If indication on Trace Activation Result requested:
NotificationRequested (Event ID = x, "Trace activation result") | | + +Upon completion of processing command (1) an ADD.resp or MOD.resp command (2) is sent. + +**Table 14.2.45.2: ADD.resp/MOD.resp/ MGW to MGC** + +| Address Information | Control information | Bearer information | +|---------------------|------------------------------------------------------------------|--------------------| +| | Transaction ID = z
Context ID = c1
TerminationID = bearer1 | | + +## 14.2.46 Trace Activation result notification + +When the procedure "Trace Activation result notification" is required, the following procedure is initiated: + +The MGW sends a NOT.req command with the following information to indicate the result of the trace activation. + +**Table 14.2.46.1: NOT.req (Trace Activation result Notification) MGW to MGC** + +| Address Information | Control information | Bearer information | +|---------------------|--------------------------------------------------------------------------------------------------------------------|--------------------| +| | Transaction ID = z
Context ID = c1
Termination ID = bearer1

Event_ID (Event ID = x, " tracact (res)") | | + +When the processing of command (1) is complete, the MGC initiates the following procedure. + +**Table 14.2.46.2: NOT.resp (Trace Activation result Notification) MGC to MGW** + +| Address Information | Control information | Bearer information | +|---------------------|----------------------------------------------------------------------|--------------------| +| | Transaction ID = z
Context ID = c1
Termination ID =
bearer1 | | + +## 14.2.47 Emergency Call Indication + +This procedure is the same as that defined in the subclause " ECS\_Indication " in ITU-T Recommendation Q.1950 Annex F [23] (see 3GPP TS 29.205 [7]) with additions as shown below. + +**Table 14.2.47.1: Emergency Call Indication additions** + +| Address Information | Control information | Bearer information | +|----------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------| +| Or as per flow 14.2.4
Establish Bearer | Or as per flow 14.2.4
Establish Bearer
With the following additions:
If Context Requested & Emergency Call:
Emergency Call Indication | Or as per flow 14.2.4
Establish Bearer | +| Or as per flow 14.2.5
Prepare Bearer | | Or as per flow 14.2.5
Prepare Bearer | +| Or as per flow 14.2.12
Play Announcement | Or as per flow 14.2.5
Prepare Bearer
With the following additions:
If Context Requested & Emergency Call:
Emergency Call Indication | Or as per flow 14.2.12
Play Announcement | +| Or as per flow 14.2.18
Reserve_Circuit | | Or as per flow 14.2.18
Reserve_Circuit | +| Or as per flow 14.2.41
Prepare_IP_transport | Or as per flow 14.2.12
Play Announcement
With the following additions:
If Context Requested & Emergency Call:
Emergency Call Indication | Or as per flow 14.2.41
Prepare_IP_transport | +| Or as per flow 14.2.2
Isolate Bearer Termination | | Or as per flow 14.2.2
Isolate Bearer Termination | +| Or as per flow 14.2.3
Join Bearer Termination | Or as per flow 14.2.18
Reserve_Circuit
With the following additions:
If Context Requested & Emergency Call:
Emergency Call Indication | Or as per flow 14.2.3
Join Bearer Termination | +| Or as per flow 14.2.51
Reserve RTP Connection Point | | Or as per flow 14.2.51
Reserve RTP Connection Point | +| Or as per flow 14.2.53
Reserve and Configure RTP Connection Point | Or as per flow 14.2.41
Prepare_IP_transport
With the following additions:
If Context Requested & Emergency Call:
Emergency Call Indication | Or as per flow 14.2.53
Reserve and Configure RTP Connection Point | +| | Or as per flow 14.2.2
Isolate Bearer Termination
With the following additions:
If Context Requested & Emergency Call:
Emergency Call Indication | | +| | Or as per flow 14.2.3
Join Bearer Termination
With the following additions:
If Context Requested & Emergency Call:
Emergency Call Indication | | +| | Or as per flow 14.2.51
Reserve RTP Connection Point
With the following additions:
If Context Requested & Emergency Call:
Emergency Call Indication | | +| | Or as per flow 14.2.53
Reserve and Configure RTP Connection Point
With the following additions:
If Context Requested & Emergency Call:
Emergency Call Indication | | + +## 14.2.48 TFO status Notify + +When the procedure "TFO status notify" is required the following procedure is initiated: + +The MGC sends a ADD.req, MOD.req or MOV req. command with the following information. + +**Table 14.2.48.1: ADD.req/MOD.req/MOV.req (TFO status) MGC to MGW** + +| Address Information | Control information | Bearer information | +|---------------------|-----------------------------------------------------------------------------------------------------------------------------|--------------------| +| | Transaction ID = z
Context ID = c1
Termination ID = bearer1

NotificationRequested (Event ID = x, "TFO Status") | | + +The support of the TFO status notification is optional in the TFO package. If supported, when the processing of command (1) is complete, the MGW initiates the following procedure. + +**Table 14.2.48.2: ADD.resp/MOD.resp/MOV.resp (TFO status) MGW to MGC** + +| Address Information | Control information | Bearer information | +|---------------------|-----------------------------------------------------------------|--------------------| +| | Transaction ID = z
Context ID = c1
TerminationID= bearer1 | | + +Otherwise it returns an error codec to the MGC indicating that the requested event is unsupported or unknown., as specified in ITU-T Recommendation H.248.8 [14]. + +## 14.2.49 TFO Status + +When the procedure "TFO Status" is required the following procedure is initiated: + +The MGW sends a NOT.req command with the following information. + +**Table 14.2.49.1: NOT.req (TFO Status) MGW to MGC** + +| Address Information | Control information | Bearer information | +|---------------------|-----------------------------------------------------------------------------------------------------------------------------|--------------------| +| | Transaction ID = z
Context ID = c1
Termination ID = bearer1

Event_ID (Event ID = x, " TFO_status(tfostatus) ") | | + +When the processing of command (1) is complete, the MGC initiates the following procedure. + +**Table 14.2.49.2: NOT.resp (TFO Status) MGC to MGW** + +| Address Information | Control information | Bearer information | +|---------------------|-------------------------------------------------------------------|--------------------| +| | Transaction ID = z
Context ID = c1
Termination ID = bearer1 | | + +## 14.2.50 Termination heartbeat indication + +When the procedure "Termination heartbeat indication" is required the following procedure is initiated: the MGW sends a NOT.req command with the following information. + +**Table 14.2.50.1: NOT.req (Termination heartbeat) MGW to MGC** + +| Address Information | Control information | Bearer information | +|---------------------|------------------------------------------------------------------------------------------------------------------------------|--------------------| +| | Transaction ID = z
Context ID = c1
Termination ID = bearer1

Event_ID (Event ID = x,
"termination heartbeat") | | + +When the processing of command is complete, the MGC initiates the following procedure. + +**Table 14.2.50.2: NOT.resp (Termination heartbeat) MGC to MGW** + +| Address Information | Control information | Bearer information | +|---------------------|----------------------------------------------------------------------|--------------------| +| | Transaction ID = z
Context ID = c1
Termination ID =
bearer1 | | + +The heartbeat timer shall be configured to a value much greater than the mean call holding time. + +The MSC-S is in charge of correcting any detected mismatch, by subtracting hanging terminations or clearing hanging contexts. + +## 14.2.51 Reserve RTP Connection Point + +This procedure is used to reserve an RTP bearer termination for a SIP-I associated Nb user plane, as defined in 3GPP TS 29.414 [32], or for a A interface over IP termination, as defined in 3GPP TS 3GPP TS 48.103 [65]. When the procedure "Reserve RTP Connection Point" is required the following procedure is initiated. + +The MGC sends an ADD.req command with the following information. + +**Table 14.2.51.1: ADD.req (Reserve RTP Connection Point Request) MGC to MGW** + +| Address Information | Control information | Bearer information | +|------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Local Descriptor {
Port = ?
IP Address = ?
IP Version = IPv4 or IPv6
} | Transaction ID = z
Termination ID = ?

If Context Requested:
Context ID = ?

If MPS call/session:
Priority Indicator = x

If Context Provided:
Context ID = c1

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

If CTM call and Access Termination:
State= ctmstate
Transport= ctmtransport
Version= ctmtext version

If Resources for multiple Codecs shall be reserved:
Reserve_Value

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

If indication on Bearer Released requested:
NotificationRequested (Event ID = x, "BNC Release (Cause)") – as defined in ITU-T Recommendation Q.1950

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

If indication on Protocol Negotiation Result requested:
NotificationRequested (Event ID = x, "Prot Negotiation Result")

If indication on Rate Change requested:
NotificationRequested (Event ID = x, "RateChange")

If access termination and notification on CTM negotiation result requested:
NotificationRequested (Event ID = x, "connchange ")

If access termination and Listener context: number of desired listener context terminations = required listener context terminations
If diffserv required (NOTE 1):-
Diffserv Code Point
If tagging behaviour
Diffserv Tagging Behaviour

If Remote Source Address Filtering required (NOTE 1):-
Remote Source Address Filtering
If Remote Source Address range required:-
Remote Source Address Mask
If Remote Source Port Filtering required:-
Remote Source Port Filtering
If individual port:-
Remote Source Port
If range of ports: | Local Descriptor {
Codec List
RTP Payloads
RtcpbwRS
RtcpbwRR
}

If data call other than SCUDIF multimedia call and if Access Termination or Anchor MGW Network Termination:
PLMN bearer capability =
PLMN capability

If GSM data call other than SCUDIF multimedia call and if Access Termination or Anchor MGW Network Termination:
GSM channel coding = coding | + +| | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--| +| |

Remote Source Port Range

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

If Sustainable Data Rate Policing Required (NOTE 1):-
Policing Required
Sustainable Data Rate
Maximum Burst Size

If peak data rate policing (NOTE 1)
Policing Required
Peak Data Rate
If Delay Variation required
Delay Variation Tolerance

If RTCP handling required (NOTE 1):
RTCP allocation

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

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

| | +| NOTE 1: Only for terminations with border control functions support.
NOTE 2: The event parameters "Media Inactivity Detection Time" and "Media Inactivity Detection Direction" are optional. | | | + +When the processing of command (1) is complete, the MGW initiates the following procedure. + +**Table 14.2.51.2: ADD.resp (Reserve RTP Connection Point Acknowledge) MGW to MGC** + +| Address Information | Control information | Bearer information | +|-------------------------------------------------------------|------------------------------------------------|-------------------------------------------------------------------------------| +| Local Descriptor {
Port
IP Address
IP Version
} | Transaction ID
Termination ID
Context ID | Local Descriptor {
Codec List
RTP Payloads
RtcpbwRS
RtcpbwRR
} | + +## 14.2.52 Configure RTP Connection Point + +This procedure is used to configure or reconfigure an RTP bearer termination for a SIP-I associated Nb user plane, as defined in 3GPP TS 29.414 [32], or for a A interface over IP termination, as defined in 3GPP TS 48.103 [65]. + +When the procedure "Configure RTP Connection Point" is required the following procedure is initiated: + +The MGC sends an MOD.req command with the following information. + +**Table 14.2.52.1: MOD.req (Configure RTP Connection Point Request) MGC to MGW** + +| Address Information | Control information | Bearer information | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| If local resources are modified:
Local Descriptor {
Port
IP Address
IP Version
}
If remote resources are modified:
Remote Descriptor {
Port
IP Address
IP Version
} | Transaction ID
Termination ID
Context ID

If IP Interface Type:
IP interface = "IP interface type"
(NOTE 1)

If Resources for multiple Codecs shall be reserved:
Reserve_Value

If CTM call and Access Termination:
State= ctmstate
Transport= ctmtransport
Version= ctmtext version

If indication on Protocol Negotiation Result requested:
NotificationRequested (Event ID = x, "Prot Negotiation Result")

If indication on Rate Change requested:
NotificationRequested (Event ID = x, "RateChange")

If access termination and notification on CTM negotiation result requested:
NotificationRequested (Event ID = x, "connchange ")

If access termination and Listener context: number of desired listener context terminations = required listener context terminations

If diffserv required (NOTE 2):-
Diffserv Code Point
If tagging behaviour
Diffserv Tagging Behaviour

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

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

If Sustainable Data Rate Policing Required (NOTE 2):-
Policing Required
Sustainable Data Rate
Maximum Burst Size

If peak data rate policing (NOTE 2)
Policing Required
Peak Data Rate
If Delay Variation required
Delay Variation Tolerance

If RTCP handling required (NOTE 2):
RTCP allocation | If local resources are modified:
Local Descriptor {
Codec List
RTP Payloads
RtcpbwRS
RtcpbwRR
}
If remote resources are modified:
Remote Descriptor {
Codec List
RTP Payloads
RtcpbwRS
RtcpbwRR
}

If data call other than SCUDIF multimedia call and if Access Termination or Anchor MGW Network Termination:
PLMN bearer capability =
PLMN capability

If GSM data call other than SCUDIF multimedia call and if Access Termination or Anchor MGW Network Termination:
GSM channel coding = coding | + +| | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--| +| | If ECN Endpoint support required
ECN Enable = "True"
Initiation Method = "ECN Initiation Method"

If notification of ECN Failure
Report:
NotificationRequested (Event ID = x, "ECN Failure") | | +| NOTE 1: If this property is included within the Reserve Connection Point procedure or the Reserve and Configure RTP Connection Point then it shall not be modified by this procedure.
NOTE 2: Only for terminations with border control functions support.
NOTE 3: The event parameters "Media Inactivity Detection Time" and "Media Inactivity Detection Direction" are optional. | | | + +When the processing of command (1) is complete, the MGW initiates the following procedure. + +**Table 14.2.52.2: MOD.resp (Configure RTP Connection Point Acknowledge) MGW to MGC** + +| Address Information | Control information | Bearer information | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| If local resources were provided in request:
Local Descriptor {
Port
IP Address
IP Version
}
If remote resources were provided in request:
Remote Descriptor {
Port
IP Address
IP Version
} NOTE | Transaction ID
Context ID
Termination ID | If local resources were provided in request:
Local Descriptor {
Codec List
RTP Payloads
RtcpbwRS
RtcpbwRR
}
If remote resources were provided in request:
Remote Descriptor {
Codec List
RTP Payloads
RtcpbwRS
RtcpbwRR
} NOTE | +| NOTE: Sending of the Remote Descriptor is optional | | | + +## 14.2.53 Reserve and Configure RTP Connection Point + +This procedure is used to reserve and configure an RTP bearer termination for a SIP-I associated Nb user plane, as defined in 3GPP TS 29.414 [32], or for a A interface over IP termination, as defined in 3GPP TS 48.103 [65]. + +When the procedure "Reserve and Configure RTP Connection Point" is required the following procedure is initiated: + +The MGC sends a ADD.req command with the following information. + +**Table 14.2.53.1: ADD.req (Reserve and Configure RTP Connection Point Request) MGC to MGW** + +| Address Information | Control information | Bearer information | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Local Descriptor {
Port = ?
IP Address = ?
IP Version = IPv4 or IPv6
}
Remote Descriptor {
Port
IP Address
IP Version = IPv4 or IPv6
} | Transaction ID
Termination ID = ?

If Context Requested:
Context ID = ?

If MPS call/session:
Priority Indicator = x

If Context Provided:
Context ID = c1

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

If Resources for multiple Codecs shall be reserved:
Reserve_Value

If CTM call and Access Termination:
State= ctmstate
Transport= ctmtransport
Version= ctmtext version

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

If indication on Bearer Released requested:
NotificationRequested (Event ID = x, "BNC Release (Cause)") – as defined in ITU-T Recommendation Q.1950

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

If indication on Protocol Negotiation Result requested:
NotificationRequested (Event ID = x, "Prot Negotiation Result")

If indication on Rate Change requested:
NotificationRequested (Event ID = x, "RateChange")

If access termination and notification on CTM negotiation result requested:
NotificationRequested (Event ID = x, " connchange ")

If diffserv required (NOTE 1):-
Diffserv Code Point
If tagging behaviour
Diffserv Tagging Behaviour

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

If Media Inactivity Detection Required (NOTE 1):
NotificationRequested (Event ID = x, "Media Inactivity Detection (Media Inactivity Detection Time, Media Inactivity Detection Direction) ") (NOTE2) | Local Descriptor {
Codec List
RTP Payloads
RtcpbwRS
RtcpbwRR
}
Remote Descriptor {
Codec List
RTP Payloads
RtcpbwRS
RtcpbwRR
}

If data call other than SCUDIF multimedia call and Anchor MGW Network Termination:
PLMN bearer capability = PLMN capability

If GSM data call other than SCUDIF multimedia call and Anchor MGW Network Termination:
GSM channel coding = coding | + +| | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--| +|

If Sustainable Data Rate Policing Required (NOTE 1):-

  • Policing Required
  • Sustainable Data Rate
  • Maximum Burst Size

If peak data rate policing (NOTE 1)

  • Policing Required
  • Peak Data Rate
  • If Delay Variation required
    • Delay Variation Tolerance

If RTCP handling required (NOTE 1):

  • RTCP allocation

If ECN Endpoint support required

  • ECN Enable = "True"
  • Initiation Method = "ECN Initiation Method"

If notification of ECN Failure

  • Report:
    • NotificationRequested (Event ID = x, "ECN Failure")
| | +|

NOTE 1: Only for terminations with border control functions support.
NOTE 2: The event parameters "Media Inactivity Detection Time" and "Media Inactivity Detection Direction" are optional.

| | + +When the processing of command (1) is complete, the MGW initiates the following procedure. + +**Table 14.2.53.2: ADD.resp(Reserve and Configure RTP Connection Point Acknowledge) MGW to MGC** + +| Address Information | Control information | Bearer information | +|----------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Local Descriptor {
Port
IP Address
IP Version
}
Remote Descriptor {
Port
IP Address
IP Version
} NOTE | Transaction ID
Termination ID
Context ID | Local Descriptor {
Codec List
RTP Payloads
RtcpbwRS
RtcpbwRR
}
Remote Descriptor {
Codec List
RTP Payloads
RtcpbwRS
RtcpbwRR
} NOTE | +| NOTE: Sending of the Remote Descriptor is optional | | | + +Editor's note: The usage of the Call Type Discrimination IE and Text Telephony IE is ffs. + +## 14.2.54 ECN Failure Indication + +The MGW sends a NOTIFY request command as in Table 14.2.54.1. + +**Table 14.2.54.1: ECN Failure Indication** + +| Address Information | Control information | Bearer information | +|---------------------|------------------------------------------------------------------------------------------------------------------------------|--------------------| +| | Transaction ID = x
Context ID= C1
Termination ID = T1

Event_ID (Event ID = x, "ECN Failure (ECN Failure Type)") | | + +The MGC responds as in Table 14.2.54.2 + +**Table 14.2.54.2: ECN Failure Indication Ack** + +| Address Information | Control information | Bearer information | +|----------------------------|--------------------------------------------------------------|---------------------------| +| | Transaction ID = x
Context ID = C1
Termination ID = T1 | | + +## 14.2.55 Media Inactivity Notification + +When the procedure "Media Inactivity Notification" is required the following procedure is initiated: the MGW sends a NOT.req command with the following information. + +**14.2.55.1 NOT.req (Media Inactivity) MGW to MGC** + +| Address Information | Control information | Bearer information | +|----------------------------|---------------------------------------------------------------------------------------------------------------------------|---------------------------| +| | Transaction ID = x
Context ID = C1
Termination ID = T1

Event_ID (Event ID = x, "Media Inactivity Detection") | | + +When the processing of command is complete, the MGC initiates the following procedure. + +**14.2.55.2 NOT.resp (Media Inactivity) MGC to MGW** + +| Address Information | Control information | Bearer information | +|----------------------------|--------------------------------------------------------------|---------------------------| +| | Transaction ID = x
Context ID = C1
Termination ID = T1 | | + +## 15 UMTS packages + +### 15.1 Mandatory UMTS packages + +The following package shall be supported for the UMTS Bearer Independent Circuit-Switched Core Network: + +- 3GUP (User Plane) package (see subclause 15.1.1). + +#### 15.1.1 3GUP package. + +PackageID: threegup (0x002f) + +Version: 1 + +Extends: None + +This package identifies that the User Plane package is used for the termination. It also contains some parameters for the User Plane functions in the MGW. + +The UP Protocol operates independently of the stream mode property, i.e. type 14 UP PDUs (which are used for inband UP signalling) can be transported between UP peers, irrespective of the stream mode direction. However, other types of UP PDUs shall be handled according to the stream mode property. + +#### 15.1.1.1 Properties + +UP Mode of operation: + +PropertyID: mode (0x0001). + +Description: Defines the mode of operation of the User Plane functions , for further definitions see 3GPP TS 25.415 [4] and 29.415 [8]. + +Type: Enumeration. + +Possible Values: + +- "Trans" (0x0001) Transparent mode. +- "Supp" (0x0002) Support mode for predefined SDU sizes. + +Default: "Trans" (0x0001) Transparent mode. + +Defined in: Local Control descriptor. + +Characteristics: Read/Write. + +UP versions: + +PropertyID: upversions (0x0002). + +Description: Defines the required versions of the UP mode of operation. + +Type: Sub-list of enumeration. + +Possible Values: + +- "1" (0x01) Version 1. +- "2" (0x02) Version 2. +- "3" (0x03) Version 3. +- "4" (0x04) Version 4. +- "5" (0x05) Version 5. + +- "6" (0x06) Version 6. +- "7" (0x07) Version 7. +- "8" (0x08) Version 8. +- "9" (0x09) Version 9. +- "10" (0x0A) Version 10. +- "11" (0x0B) Version 11. +- "12" (0x0C) Version 12. +- "13" (0x0D) Version 13. +- "14" (0x0E) Version 14. +- "15" (0x0F) Version 15. +- "16" (0x10) Version 16. +- Default: "1" (0x01) Version 1. + +Defined in: Local Control descriptor. + +Characteristics: Read/Write. + +Delivery of erroneous SDUs: + +PropertyID: delerrsdu (0x0003). + +Description: Indicates how erroneous SDUs should be handled. If it is set to YES then the UP entity implements error checking and sets Frame Quality Classification (FQC) bits accordingly; bad frames are delivered to the UP layer. If it is set to NO then the UP entity performs error checking and if a bad frame is detected then it is discarded. These settings are required only when the payload is to be examined by upper layer services; an MGW may ignore the settings of this parameter if it passes frames transparently through the UP entities. If it is set to NA then no checking is performed. + +Type: Enumeration. + +Possible Values: + +- "Yes" (0x0001) Yes. +- "No" (0x0002) No. +- "NA" (0x0003) Not Applicable. + +Default: "NA" (0x0003) Not Applicable. + +Defined in: Local Control descriptor. + +Characteristics: Read/Write. + +Interface: + +PropertyID: interface (0x0004). + +Description: Indicates the type of interface on which the termination is used. + +Type: Enumeration. + +Possible Values: + +- "RAN" (0x0001) Iu interface. +- "CN" (0x0002) Nb interface. + +Defined in: Local Control descriptor. + +Characteristics: Read/Write. + +Initialisation Direction: + +PropertyID: initdir (0x0005). + +Description: Indicates whether or not the termination in the MGW should expect initialisation information, or initiate UP initialisation itself. + +For a termination with property "interface = CN": + +- If Initialisation Direction is set to Incoming then the MGW shall expect to receive an initialisation either at this termination or from an other Nb or Iu termination in the same context. +- If Initialisation Direction is set to outgoing, then the MGW shall send out an initialisation procedure from this termination. If another termination in the same context is initialised with the same codec type and configuration the MGW should re-use the RFCI values for its Initialisation PDU, otherwise it must assign its own values. + +For a termination with property "interface = RAN": + +- If Initialisation Direction is set to "incoming", then the initialisation received at this termination is from the originating RAN and can be forwarded internally to other terminations for subsequent UP initialisations. +- If Initialisation Direction is set to "outgoing", then initialisations received are from the terminating RAN and cannot be forwarded internally. RFCI value correction can be performed at this termination, and initialisations can be sent out to the RAN. + +Examples for the usage of this property are given in annex B. + +Type: Enumeration. + +Possible Values: + +- "In" (0x0001) Incoming. +- "Out" (0x0002) Outgoing. + +Defined in: Local Control descriptor. + +Characteristics: Read/Write. + +#### 15.1.1.2 Events + +None. + +#### 15.1.1.3 Signals + +None. + +#### 15.1.1.4 Statistics + +None. + +#### 15.1.1.5 Procedures + +The MGC uses this package to indicate to the MGW that the Iu (or Nb) User Plane is used between the RNC (or distant MGW) and the MGW. The package is sent in the Establish bearer, Modify Bearer Characteristics and Prepare bearer procedures. For more information on the User Plane and for a description of 'UP mode of operation', 'UP versions' and 'Delivery of erroneous SDUs' see 3GPP TS 25.415 [4]. + +The following procedures are valid for UP in Support Mode: + +- The MGW shall be able to initiate and respond to the UP control procedures (PDU type 14 frames) independently of the Stream Mode during the call establishment phase, i.e. when not in TrFO. + +- Otherwise, during TrFO the MGW shall be able to forward UP control procedures (PDU type 14 frames) received at one termination to the other termination. +- The UP Initialisation procedure is always acknowledged between MGW peers. If an MGW receives a request for a notification for the bearer establishment then the MGW shall not send the notification until after it has either sent or received the acknowledgement for the UP initialisation. +- The MGW shall always store RFCI parameters against the MGW termination that received or that sent the UP initialisation. +- If an MGW has the UP termination property Initialisation Direction = Incoming then it expects to either receive an Initialisation (externally) or after receiving initialisation information internally send an initialisation (externally), based on what occurs first. +- If an MGW has UP termination property Initialisation Direction = Outgoing and interface CN, then it generates a network originated Initialisation PDU as soon as the bearer towards the succeeding node is successfully established, with RFCIs corresponding to the last codec configured on the termination. If another termination in the same context is initialised with the same codec type and configuration the MGW should re-use the RFCI values for its Initialisation PDU, otherwise it must assign its own values. The initialisation information sent by the MGW depends on the service that the bearer supports. For CSD service see 3GPP TS 29.007 [6] chapter 11.5. For speech service see 3GPP TS 26.102 [26] chapter 8. +- If an MGW has UP termination property Initialisation Direction = Outgoing and interface RAN, then it expects to receive an Initialisation externally. It shall not pass the initialisation parameters internally. It may initiate RFCI Value Correction out from this termination. +- A CN incoming or outgoing termination having already completed its UP initialisation towards a peer MGW shall not send externally any new UP initialisation except if a reserve / modify characteristic procedure occurred on that termination since the last initialisation. +- RAN Outgoing termination may perform, during its lifetime, subsequent RFCI Value corrections, e.g. due to changes of RFCIs on other terminations. +- If an MGW has two terminations in the same context defined as supporting the UP package and with Initialisation Direction incoming, then when it receives an Initialisation procedure from one side (provided the bearer connection from the other termination to its peer MGW is established) it shall start the UP initialisation procedure towards the peer MGW. The MGW shall perform this procedure independently of the through-connection of the terminations in the context. The MGW shall relay control information from the first initialisation to the UP peer for use at the subsequent initialisation. Also, subsequent control procedures received on one UP shall be relayed to the other UP entity when the two UP entities are connected within the MGW. This behaviour is described in more detail in Annex A. - When adding a new CN incoming termination to a context that has already a RAN or CN incoming termination, if the existing termination has already completed its UP initialisation, the MGW shall not start an initialisation procedure on the new termination based on the control information already stored at the initialised incoming termination in the context. +- If an MGW has one termination with properties "interface = RAN" and "initialisation direction = outgoing" and another termination with property "initialisation direction = Incoming" in the same context, then the MGW shall not forward the UP initialisation from the Incoming termination until it has received a UP initialisation at the "RAN"/"outgoing" side. If the codec type and codec modes configured on both terminations are identical, and if the RFCI values stored at the "incoming" termination do not match the RFCI values stored at the "outgoing" RAN side then "RFCI Value Correction" may be performed to the "outgoing" RAN side: The MGW starts UP initialisation with the RFCI values 'relayed' from the "Incoming" side. No "RFCI Value Correction" is permitted at an outgoing RAN termination whose Iu initialisation negotiates the version 1 of the support mode, at an "incoming" Iu termination or at any Nb termination. +- If a new RAN outgoing termination is added to a context that has already a RAN incoming or CN incoming termination, and if the existing termination has already completed its UP initialisation, the MGW may carry out a RFCI value correction on the new RAN outgoing termination., The control information to be used for the RFCI value correction shall be relayed from the initialised incoming termination in the context. +- No RFCI value correction shall be triggered for data call. +- As an implementation option, "RFCI Value Correction" may be delayed if terminations are not through-connected; it will be triggered by connection modification. Otherwise it shall be performed immediately + +- If "RFCI Value Correction" is not performed the MGW shall map the indexes for frames from one side to the RFCI indexes for frames from the other side. This behaviour is described in more detail in Annex A. +- If an MGW has two RAN terminations connected to the same context then the "RFCI Value Correction" is performed by the Outgoing termination. +- If an MGW has two terminations which support the UP package connected to the same context and both RFCI sets match then the MGW may pass frames transparently through the UP entities; no monitoring of the frames is performed, provided that the terminations are through-connected. This behaviour is described further in Annex A. +- If the MGW is passing frames transparently, no UP monitoring is performed. When the MGW receives an H.248 procedure request which requires interpretation or interaction with the UP, then it shall resume its UP protocol responsibilities, i.e. perform monitoring or termination of the UP protocol. +- If an MGW sends an FP UP initialization message from a termination, the MGW shall only offer versions of the FP UP, which are given in the property "UP versions" of this termination and which are supported by the MGW for this termination. +- If an MGW receives an FP UP initialization message at a termination, the MGW shall only positively acknowledge this initialization message, if versions of the FP UP are offered, which are given in the property "UP versions" and which are supported at the MGW for this termination. In the positive FP UP initialization acknowledge message, the MGW shall select one of these versions. If none of these versions are offered in the FP UP initialization message, the MGW shall send a negative FP UP acknowledge message and it shall not forward the initialization to a possible second FP UP termination in the same context. +- If PCM is used on the Nb then FP UP initialization shall be performed by the termination with property "Outgoing". If the termination property is "Incoming" then it shall receive the RFCI's from its IuFP peer (or from internal MGW termination with IuFP and same codec). If IuFP is defined on another termination in the MGW but the codec is different, i.e. not TrFO then the relaying of RFCI's shall not be performed. These IuFP peer connection shall be seen as completely separate. +- the UP initialisation information attached to a termination (RFCI values, codec type and mode(s), UP initialisation completed or not) are kept unchanged when the termination is moved to a new context. +- the initialisation direction may be changed during the lifetime of a termination ; upon such a change, the MGW shall apply the behaviour attached to the new initialisation direction. + +The procedures for a termination configured in UP Transparent Mode are those described in 3GPP TS 25.415 [4]. + +## 15.2 Optional UMTS packages + +The following packages may be supported by the UMTS Bearer Independent Circuit-Switched Core Network as required by the network services deployed in the network: + +- Circuit Switched Data package (see subclause 15.2.1); +- TFO package (see subclause 15.2.2); +- 3G Expanded Call Progress Tones Generator package (see subclause 15.2.3); +- Modification of Link Characteristics Bearer Capability package (see subclause 15.2.4); +- Enhanced Circuit Switched Data package (see subclause 15.2.5); +- Cellular Text telephone Modem Text Transport package (see subclause 15.2.6); +- IP transport package (see subclause 15.2.7); +- Flexible Tone Generator Package (see subclause 15.2.8); +- Trace Package (see subclause 15.2.9); +- ASCI Group Call package (see subclause 15.2.10); +- 3G Interface Type package. + +## 15.2.1 Circuit Switched Data package + +PackageID: threegcsd (0x0030) + +Version: 1 + +Extends: None + +This package contains the information needed to be able to support GSM and UMTS Circuit Switched Data from the media gateway. + +### 15.2.1.1 Properties + +PLMN BC: + +PropertyID: plmnbc (0x0001). + +Description: The PLMN Bearer Capability. + +Type: Octet string. + +Possible values: + +- Specified in the subclause "Bearer capability" in 3GPP TS 24.008 [3] , including the Bearer Capability IEI and Length. + +Defined in: Local Control Descriptor. + +Characteristics: Read/Write. + +GSM channel coding: + +PropertyID: gsmchancod (0x0002). + +Description: Channel information needed for GSM. + +Type: Octet string. + +Possible values: + +- The second octet of Chosen Channel as specified in the subclause "Chosen Channel" in 3GPP TS 48.008 [9]. + +Defined in: Local Control Descriptor. + +Characteristics: Read/Write. + +### 15.2.1.2 Events + +Protocol Negotiation Result: + +EventID: protres (0x0001). + +Description: This event is used to report the result of the protocol negotiation. + +EventsDescriptor Parameters: None. + +ObservedEventsDescriptor Parameters: + +- Negotiation Result: + - ParameterId: result (0x0001). + - Description: reports whether the protocol negotiation has been successful. + - Type: Enumeration. + - Possible Values: + +- "Success" (0x0001): the protocol negotiation on the termination has been successful. + - "Failure" (0x0000): the protocol negotiation on the termination has failed. +- Possible Failure Cause: +- ParameterId: cause (0x0002). + - Description: indicates the possible failure cause. + - Type: Enumeration. + - Possible Values: + - "Unsp" (0x0001): the protocol negotiation has failed for an unspecified reason. + - "V8V34" (0x0002): the V.8 or the V.34 protocol negotiation has failed (modem termination only). + +#### Rate Change: + +EventID: ratechg (0x0002). + +Description: This event is used to report a rate change. For example for GSM FAX if the detected rate does not match the channel rate the MGW shall use this to request a new channel rate. See CMM in 3GPP TS 43.045 [35]. + +EventsDescriptor Parameters: None. + +ObservedEventsDescriptor Parameters: + +- New Rate: +- ParameterId: rate (0x0001). + - Description: reports the new rate for the termination. + - Type: Integer. + - Possible Values: transmission rate in bits per second, rounded to the nearest integer value. The value must be a valid bitrate; one of the following rates: 2400, 4800, 9600, 14400, 28800, 57600. An invalid rate shall cause the call to be released by the MSC Server. + +### 15.2.1.3 Signals + +Activate Protocol: + +SignalID: actprot (0x0001). + +Description: Activate the higher layer protocol. + +Signal type: Brief. + +Duration: N/A. + +Additional parameter: + +- Local Peer Role: +- ParameterID: localpeer (0x0001). + - Type: Enumeration. + - Possible values: + - "Orig" (0x0000): originating. + - "Term" (0x0001): terminating. + +- Description: This parameter is optional, but is required for modem and fax calls. It is used to inform the modem whether it should act as originating or terminating peer. This parameter is only included within signal towards the radio access. This may either be an Access Termination or a CN Termination toward another MGW that serves the radio access. + +### 15.2.1.4 Statistics + +None. + +### 15.2.1.5 Procedures + +This package is used to set up data calls within the CS domain. For more information on the IWF, refer to 3GPP TS 29.007 [6]. + +When the Media Gateway Controller initiates the "Establish Bearer" procedure, the "Prepare Bearer" procedure, the "Modify Bearer Characteristics" procedure, the "Reserve Circuit" procedure, the "Reserve RTP Connection Point" procedure, the "Configure RTP Connection Point" procedure or the "Reserve and Configure RTP Connection Point" procedure, it shall provide the PLMN BC ("plmnbc" property above) for the termination on the mobile side and the ISDN BC (standard H.248 properties, subclause "Bearer Capabilities") for the termination on the fixed side. For a mobile-to-mobile call, it shall provide the PLMN BC on both terminations. + +The presence of the PLMN BC property may trigger the use of the IWF. + +Once the bearer has been established, after B-answer, the "Activate Interworking Function" procedure is used to activate the IWF. The Activate Protocol signal ("actprot") will start the negotiation of the layer 2 protocols on both sides. If a modem or fax service is requested, the signal shall contain the Local Peer Role parameter ("localpeer"), to tell the modem whether it should act as originating or terminating peer. + +**NOTE:** The Activate Protocol signal is needed only after B-answer as described above or after successful in-call modification from speech to fax, to activate the protocol timers at the correct time. This is the only time when this signal is needed (specifically, the signal is not used after a handover sequence or for lawful interception). + +The IWF Protocol Indication notifications are used by the MGW to inform the MSC server about IWF protocol events. The MSC has to request the detection of the events "Protocol Negotiation Result" and "Rate Change" in the "Activate IWF" procedure, the "Establish Bearer" procedure, the "Prepare Bearer" procedure, the "Modify Bearer Characteristics" procedure, the "Reserve Circuit" procedure, the "Reserve RTP Connection Point" procedure, the "Configure RTP Connection Point" procedure or the "Reserve and Configure RTP Connection Point" procedure. + +For handover to GSM, or change of channel characteristics within the GSM network, the property GSM Channel Coding ("gsmchancod"), which contains the information about the channel type and the number of channels, shall be transmitted to the termination on the mobile side in the "Establish Bearer", the "Prepare Bearer", the "Reserve Circuit", the "Reserve RTP Connection Point", the "Configure RTP Connection Point" and the "Reserve and Configure RTP Connection Point" procedures together with the PLMN BC. The presence of the GSM Channel Coding property also indicates that the termination is using a GSM access network. + +If the MGW has requested a rate change due to GSM fax rate mismatch (CMM procedure see 3GPP TS 43.045 [35]) then it shall suspend transmission until the MSC Server has modified the PLMN Bearer Capability and GSM Channel Coding property to match the required rate. If this occurs while other context manipulations are occurring the MGW shall only resume transmission when the streams are bothway connected and the PLMN Bearer Capability and Channel Coding are correct. The MGW shall not send subsequent rate change notifications while the outstanding rate change has not been performed by the MSC Server. + +## 15.2.2 TFO package + +PackageID: threegtfoc (0x0031) + +Version: 2 + +Extends: None + +This package defines events and properties for Tandem Free Operation (TFO) control. TFO uses inband signalling and procedures for Transcoders to enable compressed speech to be maintained between a tandem pair of transcoders. This package allows an MGW, which has inserted a transcoder, to support TFO. + +### 15.2.2.1 Properties + +TFO Activity Control: + +PropertyID: tfoenable (0x0001). + +Description: Defines if TFO is enabled or not. + +Type: Enumeration. + +Possible Values: + +- "On" (0x0001): TFO is enabled, TFO protocol is supported. +- "Off" (0x0002): TFO is not enabled, TFO protocol is not initiated or terminated. + +Defined in: Local Control descriptor. + +Characteristics: Read/Write. + +TFO Codec List: + +PropertyID: codeclist (0x0002). + +Description: List of codecs for use in TFO protocol, the Local Used Codec (see 3GPP TS 28.062 [5]) is always the first entry in the list. The MSC Server may enable TFO without providing a TFO Codec List ; in this case, the MGW shall behave as if it had received a TFO Codec List composed of the selected codec of the opposing termination within the Context. + +Type: Sub-list of Octet string. + +Possible Values: + +- List of codec types; each entry: + +Mc Single Codec, similar to as defined in ITU-T Recommendation Q.765.5 [24], for single codec information (figure 14/Q.765.5), where the Codec Information is defined either in ITU-T Recommendation Q.765.5 [24] or in another specification for the given Organization Identifier. For 3GPP codecs these are defined in 3GPP TS 26.103 [16]. The ACodec property in H.248 binary encoding or codecconfig attribute in H.248 text encoding contain the contents of the ITU-T Single Codec IE, excluding the Single Codec Identifier, Length Indication and Compatibility Information. + +In H.248 text encoding, the value of the codeclist property shall be encoded as: + +LBRKT codecconfig \*(COMMA codecconfig) RBRKT + +Example: H.248 text encoding of the TFO codec list (UMTS\_AMR\_2 with Preferred Configuration set 1, and UMTS\_AMR-WB with Preferred Configuration set 0): + +Threegtfc/codeclist = { 0206959504 , 020A00 } + +Where: + +- UMTS\_AMR\_2 parameters are: ETSI, UMTS\_AMR\_2, ACS={12.2, 7.4, 5.9, 4.75}, SCS={12.2, 7.4, 5.9, 4.75}, OM=0 plus MACS=4 +- UMTS\_AMR\_WB parameters are: ETSI, UTMS\_AMR\_WB, Config-WB-Code=00 + +Defined in: Local Control descriptor. + +Characteristics: Read/Write. + +### 15.2.2.2 Events + +Optimal Codec Event: + +EventID: codec\_modify (0x0010). + +Description: The event is used to notify the MGC that TFO negotiation has resulted in an optimal codec type being proposed. + +EventsDescriptor Parameters: None. + +ObservedEventsDescriptor Parameters: + +- Optimal Codec Type. + - ParameterID: optimalcodec (0x0011). + - Description: indicates which is the proposed codec type for TFO. + - Type: Octet string. + - Possible Values: +Mc Single Codec; + +Similar to as defined in ITU-T Recommendation Q.765.5 [24], for single codec information (figure 14/Q.765.5), where the Codec Information is defined either in ITU-T Recommendation Q.765.5 [24] or in another specification for the given Organization Identifier. For 3GPP codecs these are defined in 3GPP TS 26.103 [16]. The ACodec property in H.248 binary encoding or codecconfig attribute in H.248 text encoding contain the contents of the ITU-T Single Codec IE, excluding the Single Codec Identifier, Length Indication and Compatibility Information. + +Codec List Event: + +EventID: distant\_codec\_list (0x0012). + +Description: The event is used to notify the MGC of the distant TFO partner's supported codec list. + +EventsDescriptor Parameters: None. + +ObservedEventsDescriptor Parameters: + +- Distant Codec List: + - ParameterID: distlist(0x0013). + - Description: indicates the codec list for TFO. + - Type: Sub-list of Octet string. + - Possible Values: + +List of codec types; each entry: + +Mc Single Codec similar to as defined in ITU-T Recommendation Q.765.5 [24], for single codec information (figure 14/Q.765.5), where the Codec Information is defined either in ITU-T Recommendation Q.765.5 [24] or in another specification for the given Organization Identifier. For 3GPP codecs these are defined in 3GPP TS 26.103 [16]. The ACodec property in H.248 binary encoding or codecconfig attribute in H.248 text encoding contain the contents of the ITU-T Single Codec IE, excluding the Single Codec Identifier, Length Indication and Compatibility Information. + +The first Codec Type in the list is the Distant Used Codec, received from the distant TFO partner (see 3GPP TS 28.062 [5]). . + +In H.248 text encoding, the value of the distlist parameter shall be encoded as: + +LBKRT codecconfig \*(COMMA codecconfig) RBRKT + +TFO Status Event: + +EventID: TFO\_status (0x0014). + +Description: The event is used to notify the MGC that a TFO link has been established or broken. + +EventsDescriptor Parameters: None. + +ObservedEventsDescriptor Parameters: + +- TFO Status: + - ParameterId: tfostatus (0x0015). + - Description: reports whether TFO has been established or broken. Upon TFO activation, no notification is sent if TFO has not been established. A TFO\_Off notification is only reported when a TFO link previously established is broken. The MGW should not report transient TFO status change. + - Type: Boolean + - Possible Values: + - "TFO\_On" : TFO has been established. + - "TFO\_Off" : TFO is no more established. + +### 15.2.2.3 Signals + +None. + +### 15.2.2.4 Statistics + +None. + +### 15.2.2.5 Procedures + +For the procedures for TFO see 3GPP TS 28.062 [5]. + +To enable TFO, the MSC Server shall configure the properties of this package on a MGW Termination with the media stream property for Codec Type set to ITU-T Recommendation G.711 [25] (see annex C of ITU-T Recommendation H.248 [10]) or Bearer Service Characteristics set to "Speech" or "3.1 kHz Audio" in TMR or USI due to Reserve Circuit Procedure, see in ITU-T Recommendation Q.1950 (see 3GPP TS 29.205 [7]). + +The TFO protocol shall be disabled if the call configuration becomes no longer TFO compatible or if the Codec Type property of the media stream at the opposing termination in the Context is reconfigured to G.711 or if the Bearer Service Characteristics of the opposing Termination is reconfigured to "Speech" or "3.1 kHz Audio". The TFO protocol may be disabled either by the MSC Server by using the TFO Activity Control property of this package or by the MGW in accordance with the TFO rules as described in [5] when it detects that TFO operation is no longer possible (for example it has G.711 encoding at opposing Terminations). + +## 15.2.3 3G Expanded Call Progress Tones Generator Package + +PackageID: threeegxcg(0x0032) + +Version: 1 + +Extends: xcg version1 + +This package extends "Expanded Call Progress Tones Generator Package", as defined in ITU-T Recommendation Q.1950 [23] (see 3GPP TS 29.205 [7]). The package adds a new toneId for CAMEL prepaid warning tone. + +### 15.2.3.1 Properties + +None. + +### 15.2.3.2 Events + +None. + +### 15.2.3.3 Signals + +CAMEL Prepaid Warning Tone: + +SignalID: cpwd (0x004f). + +Description: Generate CAMEL prepaid warning tone to inform the party that the Max Call Period Duration is about to expire. CAMEL prepaid warning tone is defined in 3GPP TS 23.078 [22]. The physical characteristic of CAMEL prepaid warning tone is available in the gateway. + +Signal type: Brief. + +Duration: Provisioned, Not Auditable. + +Additional parameters: + +- Tone Direction. +- ParameterID: td (0x0010). +- Type: Enumeration. +- Values: + - "Ext" (0x01): external. + - "Int" (0x02): internal. + - "Both" (0x03): Both. +- Default: "Ext". + +#### 15.2.3.4 Statistics + +None. + +#### 15.2.3.5 Procedures + +None. + +### 15.2.4 Modification Of Link Characteristics Bearer Capability + +PackageName: Modification of Link Characteristics Bearer Capability + +PackageID: threegmlc(0x0046) + +Description: This package contains an event that when requested by the MGC will cause the MG to notify the MGC that modification of the link characteristics is allowed. This notification is typically generated when the bearer has been established. + +Version: 1 + +Extends: None + +#### 15.2.4.1 Properties + +None. + +#### 15.2.4.2 Events + +Bearer Modification Support Event. + +EventID: mod\_link\_supp (0x0001). + +Description: The event is used to notify the MGC that modification of the link characteristics of the current bearer connection is permitted. + +EventsDescriptor Parameters: None. + +ObservedEventsDescriptor Parameters: None. + +### 15.2.4.3 Signals + +None. + +### 15.2.4.4 Statistics + +None. + +### 15.2.4.5 Procedures + +If the MGC is interested in determining whether or not the bearer associated with a termination supports modification of its link characteristics it shall send a request (Add/Modify/Move) with the Bearer Modification Support Event. When the bearer is established the MG will indicate in a Notify request to the MGC if modification of link characteristics is supported. A notify will NOT be generated if modification is NOT supported on the bearer. + +## 15.2.5 Enhanced Circuit Switched Data package + +PackageID: threeegcsden (0x0082) + +Version: 1 + +Extends: threeegcsd (0x030) Version 1 + +This package extends "Circuit Switched Data Package", as defined in subclause 15.1.2. This package adds a new property to define the user bitrate at a Iu termination. + +### 15.2.5.1 Properties + +#### Bitrate + +PropertyID: bitrate (0x0003). + +Description: user bitrate. + +Type: Integer. + +Possible Values: transmission rate in bits per second, rounded to the nearest integer value. The value shall be a valid bitrate; one of the following rates: 2400, 4800, 9600, 14400, 28800, 57600, 64000. + +Defined in: Local Control Descriptor. + +Characteristics: Read/Write. + +### 15.2.5.2 Events + +None. + +### 15.2.5.3 Signals + +None. + +### 15.2.5.4 Statistics + +None. + +### 15.2.5.5 Procedures + +This package is used in addition to the 3GCSD package for CS data calls. It is used for indicating the user data rates for Inter-MSC SRNS Relocation and handover cases. If the Bitrate is not 64 kb/s at one termination in the MGW but its opposing termination has properties that define its bitrate to be 64 kb/s (e.g. TMR=UDI) then A-TRAU' protocol shall be applied by the MGW. For further details see 3GPP TS 29.007 [6]. + +## 15.2.6 Cellular Text telephone Modem Text Transport + +PackageName: CTM Text Transport + +PackageID: threectm (0x0068) + +Description: The CTM text transport package is intended for enabling robust real time text conversation through a voice channel primarily intended for communication over mobile networks. This package includes the mechanisms needed to transport T.140 text conversation streams [19] in a voice channel environment, using the CTM Cellular Text Telephone Modem specified in 3GPP TS 26.226 [18]. The transport mechanism allows for alternating transport of voice and text. + +Version: 1 + +Extends: None + +### 15.2.6.1 Properties + +Text termination connection state: + +PropertyID: connstate (0x0001). + +Description: The connection state property is used to reflect details of the achieved text connection. For each new session connstate should be reset to "Prepare". + +Type: Enumeration. + +Possible values: + +- "Idle" (0x0001) meaning that CTM availability negotiation has failed; CTM is disabled except for monitoring the incoming line for CTM signals. +- "Prepare" (0x0002) for CTM being enabled, monitoring for CTM signals and ready to send CTM signals. +- "Connected" (0x0006) for CTM being enabled and to have detected CTM availability in the current session. + +Defined in: TerminationState. + +Characteristics: Read/Write. + +Text Transport: + +PropertyID: trpt (0x0002) + +Description: The transport parameter reflects the transport mechanism selected for the Text Conversation termination. In 3GPP, one possible transport mechanism is the Cellular Text Telephone Modem as in 3GPP TS 26.226 [18]. It is used when it is desired to transport the text conversation in a voice channel. CTM enables alternating use of the voice channel for voice and text during the call. + +Type: Enumeration. + +Possible values: + +- "ctm" (0x0008) for text transport in mobile voice channel as in 3GPP TS 26.226 [18]. + +Defined in: LocalControl. + +Characteristics: Read/Write. + +Text Protocol Version: + +PropertyID: textproto (0x0003). + +Description: The version of the ITU-T Recommendation T.140 [19] protocol used in the connection. + +Type: Integer. + +Possible values: + +- Any integer corresponding to a T.140 version number (currently 1) as in ITU-T Recommendation H.248 .2 [17]. + +Defined in: LocalControl. + +Characteristics: Read/Write. + +### 15.2.6.2 Events + +Connection State Change: + +EventID: connchange (0x0001). + +Description: + +- This event will occur when the text connection state for the termination has changed. +- The parameter values are the same as the Connection State property. +- If a CTM availability request timed out, the state is returned to Idle. + +EventDescriptorParameters: + +None. + +ObservedEventDescriptorParameters: + +ParameterName: Connection Change. + +ParameterID: connchng (0x0001). + +Type: Enumeration. + +Possible Values: As property threegctm/connstate. + +### 15.2.6.3 Signals + +None. + +### 15.2.6.4 Statistics + +Characters Transferred: + +StatisticsID: chartrans (0x0001). + +Description: Number of bytes of ITU-T Recommendation T.140 [19] data transferred through the termination. + +Units: count. + +### 15.2.6.5 Procedures + +If the MGC detects a CTM indication it shall send a request (Add/Modify/Move) with the CTM Transport property. Upon receivable of it, the MGW shall allocate a termination with CTM capabilities. Normal usage is that the CTM enabled termination handles one text stream and one voice stream and alternates between transporting voice and text in the voice channel according to the functionality of CTM. This termination could for example be combined in a context with a termination with the txp and ctyp packages for gateway functionality between PSTN text telephony and mobile CTM based text telephony. These packages are described in ITU-T Recommendation H.248.2 [17]. + +The CTM algorithm has states. The states defined in the text termination connection state property are mapped into CTM states in the following way: + +- Idle: CTM disabled because of an unsuccessful CTM availability negotiation. +- Prepare: normal initial state with CTM monitoring active. +- Connected: CTM negotiation is completed. + +For each new call, the CTM termination shall be put in the Prepare state. + +When the CTM availability negotiation is completed, the state is Connected. + +The state transitions are automatic, except for setting Prepare state as described above. + +## 15.2.7 IP transport package + +This package has been replaced by the use of Annex C.6 IP and UDP properties (see subclauses 14.2.41 and 14.2.42). + +## 15.2.8 Flexible Tone Generator Package + +PackageID: threeegflex (0x0084) + +Version: 1 + +Extends: threeegxcg version 1 + +This package extends "3G Expanded Call Progress Tones Generator Package", as defined in chapter 15.1.4 above. This package adds a new tone for call duration control in CAMEL phase 4, supporting variable sequence of tones and burst list. + +### 15.2.8.1 Properties + +None. + +### 15.2.8.2 Events + +None. + +### 15.2.8.3 Signals + +Signal Name: Flexible Tone. + +SignalID: ft (0x0050). + +Description: Generate flexible 900 Hz tone. The physical characteristics of Flexible Tone is not described in the additional parameters. It shall be available in the Media Gateway. + +SignalType: Brief. + +Duration: Provisioned. + +Additional Parameters: + +- Parameter Name: Burst List Direction + +Description: Used to indicate the direction the tone is to be sent. External indicates that the tone is sent from the MG to an external point. Internal indicates that the tone is played into the Context to the other terminations. Both way indicates both internal and external behaviour. + +ParameterID: bld (0x0001). + +Type: Enumeration. + +Possible Values: + +- "Ext" (0x01): External. +- "Int" (0x02): Internal. +- "Both" (0x03): Both way. +- Default: "Ext" (0x01). + +Parameter Name: numberOfBursts. + +Description: Number of bursts in the burst list. + +ParameterID: nob (0x0002). + +Type: Integer. + +Possible values: 1 to 3. + +Default: 1. + +Parameter Name: burstInterval. + +Description: Time interval between two consecutive bursts expressed in amount of 100 ms units. + +ParameterID: bi (0x0003). + +Type: Integer. + +Possible values: 1 to 1200. + +Default: 2. + +Parameter Name: numberOfTonesInBurst. + +Description: Number of tones to be played in each burst. + +ParameterID: notib (0x0004). + +Type: Integer. + +Possible values: 1 to 3. + +Default: 3. + +Parameter Name: toneDuration. + +Description: Duration of each tone in a burst expressed in amount of 100 ms units. + +ParameterID: td (0x0005). + +Type: Integer. + +Possible values: 1 to 20. + +Default: 2. + +Parameter Name: toneInterval. + +Description: Time interval between two consecutive tones in a burst expressed in amount of 100 ms units. + +ParameterID: ti (0x0006). + +Type: Integer. + +Possible values: 1 to 20. + +Default: 2. + +#### 15.2.8.4 Statistics + +None. + +#### 15.2.8.5 Procedures + +The MGW should generate the tones using the above mentioned parameters as specified in 3GPP TS 23.078 [22] subclause 4.5.7.1.2 + +In case MGC requests to generate a flexible tone specifying a signal type "Timeout" and a "Duration" longer than the time needed to play the whole Burst List no action will be taken on the incoming stream to fill the gap. I.e. if any user plane stream is received on one side of the termination after the end of the burst list, it will be present, unchanged, on the other side of the termination as well (transparent mode). + +## 15.2.9 Trace Package + +PackageID: calltrace (0x0097) + +Version: 1 + +Extends: None + +This package defines properties for subscriber and equipment trace activation and deactivation properties to be attached to the trace record generated by MGW. + +### 15.2.9.1 Properties + +#### Trace Activation Control + +PropertyID: traceactivityrequest(0x0001) + +Description: Defines if trace is activated or deactivated. + +Type: Bool + +Possible Values: + +"on" (true): Trace Session is activated in MGW + +"off" (false): Trace Session is deactivated in MGW + +Defined in: Local Control descriptor + +Characteristics: Read/Write + +#### IMSI + +PropertyID: imsi(0x0002) + +Description: IMSI number of the traced subscriber to be attached to the trace record. Used for record identification like trace reference. + +Type: Octet string + +Possible Values: The IMSI is coded as defined in 3GPP TS 23.003 [43]. The IMSI is TBCD-coded with a fixed length of 8 octets. Two digits are encoded per octet, each digit is encoded 0000 to 1001 (0 to 9). Bits 8765 of octet n encodes digit 2n, bits 4321 of octet n encodes digit 2(n-1) +1 (i.e the order of digits is swapped in each octet compared to the digit order defined in 3GPP TS 23.003 [43]). 1111 is used as filler when there is an odd number of digits. Digits are packed contiguously with no internal padding. + +Defined in: Local Control descriptor + +Characteristics: Read/Write + +#### IMEI(SV) + +PropertyID: imei\_sv(0x0003) + +Description: IMEI(SV) number of the traced equipment to be attached to the trace record. Used for record identification like trace reference. + +Type: Octet string + +Possible Values: The IMEI(SV) is coded as defined in 3GPP TS 23.003 [43]. The IMEI(SV) is TBCD encoded. Two digits are encoded per octet, each digit is encoded 0000 to 1001 (0 to 9). Bits 8765 of octet n encodes digit 2n, bits 4321 of octet n encodes digit 2(n-1) +1 (i.e the order of digits is swapped in each octet compared to the digit order defined in 3GPP TS 23.003 [43]). 1111 is used as filler when there is an odd number of digits. Digits are packed contiguously with no internal padding. + +Defined in: Local Control descriptor + +Characteristics: Read/Write + +#### Trace Reference + +PropertyID: tracereference(0x0004) + +Description: Reference number to identify different Trace Session in OSS as defined in 3GPP TS 32.421 [29] and 3GPP TS 32.422 [30]. + +Type: Octet string + +Possible Values: OSS (EM) defines when activating a Trace Session + +Defined in: Local Control descriptor + +Characteristics: Read/Write + +#### Trace Recording Session Reference + +PropertyID: tracerecsessionref(0x0005) + +Description: A unique identifier within the Trace Session for identifying the Trace Recording sessions. Defined in 3GPP TS 32.421 [29] and in 3GPP TS 32.422 [30]. + +Type: Octet string + +Possible Values: Described in 3GPP 32.422 [30] + +Defined in: Local Control descriptor + +Characteristics: Read/Write + +#### Trace Depth + +PropertyID: tracedepth(0x0006) + +Description: Trace Depth as defined in 3GPP TS 32.421 [29] + +Type: Enumeration + +Possible Values: Defined in 3GPP TS 32.422 [30] + +Defined in: Local Control descriptor + +Characteristics: Read/Write + +#### Triggrering Events + +PropertyID: triggeringevent(0x0007) + +Description: Triggrering Events as defined in 3GPP TS 32.422 [30]. + +Type: Octet string + +Possible Values: Defined in 3GPP TS 32.422 [30]. + +Defined in: Local Control descriptor + +Characteristics: Read/Write + +#### List of interfaces + +PropertyID: listofinterfaces(0x0008) + +Description: List of interfaces to trace as defined in 3GPP TS 32.422 [30] + +Type: Octet string + +Possible Values: Defined in 3GPP TS 32.422 [30] + +Defined in: Local Control descriptor + +Characteristics: Read/Write + +### 15.2.9.2 Events + +Trace result + +EventID: tracact (0x0001) + +Description: Notification to the MSC Server if trace activation was successful/unsuccessful in the MGW. + +EventDescriptor parameters: None + +ObservedEventsDescriptor parameters: + +Result: Trace Activation Result + +res (0x0001) + +Type: enumeration + +Possible values: + +success (0x0001): "Trace Successfully activated" + +failure (0x0000): "Failure in trace activation" + +### 15.2.9.3 Signals + +None + +### 15.2.9.4 Statistics + +None + +### 15.2.9.5 Procedures + +For the network level procedures of the tracing see 3GPP TS 32.422 [30]. + +For the trace records of the MGW see 3GPP TS 32.423 [31]. + +In H.248 interface MSC Server uses 'Trace Activity Control' property to indicate MGW that a termination should be placed under trace or should be taken out of trace. In the call establishing phase MSC Server sets trace package information into proper command (Add or Modify) associated to the termination to be traced. Tracing can be activated either by giving IMEI(SV) or IMSI number as a further information. MSC Server shall also provide the values for all other properties described in this package that is IMSI if trace is activated based on IMSI, IMEI(SV) if trace is activated based on IMEI(SV), Trace reference, Trace recording session reference, Trace depth, triggering events in MGW, list of interfaces in MGW. When MSC Server activates the trace, it shall use 'Trace Activation Result' Event to detect if the Trace Activation was successful or not. MGW shall not reject the Add/Modify because of unsuccessful Trace Activation, but only send a Notification with this Event. Tracing is automatically deactivated in MGW when termination is taken out of the context in the end of the call. If the Termination is Moved to another Context, trace is automatically forwarded to new termination. + +## 15.2.10 ASCI Group call package + +PackageID: threeegasci (0x00b2) + +Version: 2 + +Extends: None + +This package contains the information needed to be able to support VGCS (3GPP TS 43.068 [39]) and VBS (3GPP TS 43.069 [40]) services. + +### 15.2.10.1 Properties + +Number of needed conference terminations + +PropertyID: nct (0x0001) + +Description: Indicates the number of needed conference terminations for the call. + +Type: Integer + +Defined in Descriptor: Local Control Descriptor + +Characteristics: Read/Write + +Number of desired listener context terminations + +PropertyID: nlct (0x0002) + +Description: Indicates the number of desired terminations for a listener context. + +Type: Integer + +Defined in Descriptor: Local Control Descriptor + +Characteristics: Read/Write + +### 15.2.10.2 Events + +None. + +### 15.2.10.3 Signals + +None. + +### 15.2.10.4 Statistics + +None + +### 15.2.10.5 Procedures + +The MSC server receives the number of needed conference terminations from GCR (see 3GPP TS 43.068 [39]) and 3GPP TS 43.069 [40]) and reserves the requested number of needed Conference terminations for that call. The parameter "Number of needed conference terminations" shall be included when allocating the first termination of an ASCI-conference context. It is optional when adding further terminations. If the MGW is unable to reserve the number of requested terminations for that call, it shall response with error code 510 "insufficien resources". + +The parameter "Number of desired listener context terminations" should be included when allocating the first termination of a Listener context. + +## 15.2.11 3G Interface Type package + +PackageID: threegint (0x00e3) + +Version: 1 + +Extends: None + +This package contains a property to specify the used interface type for IP terminations. + +### 15.2.11.1 Properties + +IP Interface Type + +PropertyID: ipint (0x0001) + +Description: Indicates the type of external interface used by the termination. + +Type: Enumeration. + +Possible Values: + +- "NboIP" (0x0001) Nb over IP with SIP-I based Nc, see 29.414 [32]. +- "AoIP" (0x0002) A interface over IP. +- "MboIP" (0x0003) Mb interface +- "ExtSIPT" (0x0004) External SIP-I based network + +All other values reserved. + +Defined in: Local Control descriptor. + +Characteristics: Read/Write. + +### 15.2.11.2 Events + +None. + +### 15.2.11.3 Signals + +None. + +### 15.2.11.4 Statistics + +None + +### 15.2.11.5 Procedures + +The MSC server may indicate the interface type (reference point) associated with the RTP bearer termination to the MGW with this package. This allows MGW to collect statistics per interface type associated with the RTP bearer termination as required by 3GPP TS 32.407[58]. The provision of these statistics is outside of the scope of this specification. + +## Annex A (informative): Framing protocol Interworking Function (FPIF) + +### A.1 Introduction + +SDUs transmitted over an Iu or Nb interface and received at a MGW whose outgoing UP is also Iu or Nb shall be relayed to the outgoing UP MGW termination. If no interworking function (other than the FPIF) or transcoder device is inserted by the MGW, and if UP terminations are present, then PDUs and control procedures are passed between MGW terminations by the FPIF. The FPIF is the functional entity responsible for aligning or mapping control procedures (including RFCIs, frame numbers etc) on the separate UP interfaces according to the package procedures described in the main text. The FPIF determines if the two UP configurations are identical and thus the UP PDUs may be passed transparently. If the FPIF determines that the two UP configurations are not identical it applies the required mapping. The relaying of PDUs transparently can also be considered as FPIF bypass. + +NOTE: the implementation in the MGW can perform a more efficient processing of the PDUs in this case. The MGW switching and bypassing of the protocol functions during TrFO is left to the manufacturer's implementation. + +UP initialisations are not handled by the FPIF, only receipt of the Subflow combinations and the RFCI allocations are received by the FPIF for each UP. + +The RFCIs are relayed by the FPIF as described in main text for the UP package procedures. + +![Diagram of the Framing Protocol Interworking Function (FPIF) architecture.](0779125369ae9c0108101b54fe2428bf_img.jpg) + +The diagram illustrates the FPIF architecture within a Media Gateway (MGW). At the top, two 'Iu/Nb Interface' blocks are shown. Below each interface is a box labeled 'Iu or Nb UP Support Mode Functions'. Between these boxes and the interfaces are double-headed arrows labeled 'Transfer of Iu FP protocol frames'. Below each 'Support Mode Functions' box is a 'RNL/CNL-SAP' interface, represented by a circle. Below each 'RNL/CNL-SAP' is a 'TNL-SAP' interface, also represented by a circle. At the bottom, a thick horizontal line represents the MGW transport plane. Arrows indicate the flow of data from the 'Iu or Nb UP Support Mode Functions' through the 'RNL/CNL-SAP' and 'TNL-SAP' interfaces into the MGW transport plane. A central pink box labeled 'FPIF' is positioned above the 'RNL/CNL-SAP' interfaces, with double-headed arrows connecting it to both. The entire structure is labeled 'MGW' at the bottom center. + +Diagram of the Framing Protocol Interworking Function (FPIF) architecture. + +Figure A.1: The Framing Protocol Interworking Function + +## A.2 FPIF procedures with respect to Iu framing protocol + +This clause handles relay of user data indicated to the FPIF in a Nb- or Iu-UP-data-indication message and transmitted between peer UP layer entities in PDU types 0 and 1. The FPIF passes this information to the UP layer on the sending side in a Nb- or Iu-UP-data-request message. + +### A.2.1 Payload + +Received SDUs shall be forwarded unmodified to the next MGW. Note that if "delivery of erroneous SDUs" is set to 'no', faulty SDUs are already discarded by the Iu or Nb support mode functions and, hence, not delivered to the FPIF. + +### A.2.2 RFCIs + +If the RFCI values on the outgoing UP interface match those initialised on the incoming UP interface then the RFCI indicated by the lower layer (i.e. Iu or Nb) on the receiving side shall be forwarded unmodified to lower layer on the sending side. + +If the RFCI sets on the outgoing UP interface do not match those initialised on the incoming UP interface then the FPIF performs mapping between the RFCIs on each UP for the same initialised Subflow Combination. + +The FPIF is the entity that may perform the RFCI value correction procedure as described in the main text, after this procedure then relaying of the received RFCI shall be performed. + +### A.2.3 FQC + +The FQC indicated by the lower layer (i.e. Iu or Nb) on the receiving side shall be forwarded unmodified to lower layer on the sending side. + +### A.2.4 Frame number + +The frame number indicated by the lower layer (i.e. Iu or Nb) on the receiving side shall be forwarded unmodified to lower layer on the sending side. + +A discontinuity in framing protocol support mode frame numbers is allowed at the end of the TrFO break. + +## A.3 Relay of status information + +This clause handles relay of status information indicated to the FPIF in a Nb- or Iu-UP-status-indication message and transmitted between peer UP layer entities in PDU type 14. The FPIF in general passes this information to the UP layer on the sending side. + +### A.3.1 Void + +### A.3.2 Rate Control Frames + +The FPIF shall pass rate control request and rate control acknowledgement frames transparently between incoming UP interface and outgoing UP interface. + +Before a MGW reverts from TrFO break operation (for example during handover or relocation where the rate control procedures may have been operating independently between each UP interface) the FPIF may perform rate control procedures to each UP peer. It shall then use the Maximum rate and Current rate settings from the opposite UP configurations. This is performed to align the UP's on each side of the MGW to enable relaying of all subsequent PDUs as described above. + +Optionally, the UP layer protocol entity on the sending side may substitute the frame number received in a status request by another number, but shall then substitute the initial number back in the status indication containing the acknowledgement. Figure A.2 shows an example of the relay of the rate control procedure. + +![Sequence diagram illustrating the relay of a control procedure between an Iu UP entity, a Relay Function, and an Nb UP entity.](f43d225d8fed2845b8d7e5afecbfe636_img.jpg) + +``` + +sequenceDiagram + participant Iu UP entity + participant Relay Function + participant Nb UP entity + + Note left of Iu UP entity: RC(0) + Iu UP entity->>Relay Function: RC(0) + Relay Function->>Nb UP entity: RC(0) + Nb UP entity->>Nb UP entity: RC(0) + Nb UP entity->>Nb UP entity: RC-NACK(0) + Nb UP entity->>Nb UP entity: RC(1) + Nb UP entity->>Nb UP entity: RC-ACK(1) + Nb UP entity->>Relay Function: RC-ACK(0) + Relay Function->>Iu UP entity: RC-ACK(0) + Note right of Nb UP entity: Not the same frame number as received in the status request + Note right of Nb UP entity: Frame number 0 is substituted back in the status indication + +``` + +The diagram shows a sequence of messages between three entities: Iu UP entity, Relay Function, and Nb UP entity. The sequence starts with an external RC(0) message to the Iu UP entity. The Iu UP entity sends RC(0) to the Relay Function, which then relays it to the Nb UP entity. The Nb UP entity sends its own RC(0) and RC-NACK(0) messages. It then sends RC(1) and RC-ACK(1) messages. The Nb UP entity sends RC-ACK(0) to the Relay Function, which relays it back to the Iu UP entity. Two callouts from the Nb UP entity indicate that the frame number in the RC-ACK(0) message is not the same as received in the status request and that frame number 0 is substituted back in the status indication. + +Sequence diagram illustrating the relay of a control procedure between an Iu UP entity, a Relay Function, and an Nb UP entity. + +Figure A.2: Relay of a control procedure + +### A.3.2 Time Alignment + +Time alignment frames shall be relayed unmodified. + +## Annex B (informative): Examples for Usage of the 3GUP Package "Initialization Direction" Property + +![Figure B.1: 3G to 3G Call (A to B) diagram. It shows a sequence of nodes: IRF, MGW A (with 'Incoming' label above), MGW B (with 'Outgoing' label above), and IRF. Above MGW B are labels 'Incoming', 'Outgoing', and 'Incoming'. Below MGW B are labels 'IRF', 'HRN', and 'GSM'. Below the main sequence are three boxes labeled 'I', 'N', and 'I'.](f1de68a4cbb9b92a1c0ffd919bbd199c_img.jpg) + +Figure B.1: 3G to 3G Call (A to B) diagram. It shows a sequence of nodes: IRF, MGW A (with 'Incoming' label above), MGW B (with 'Outgoing' label above), and IRF. Above MGW B are labels 'Incoming', 'Outgoing', and 'Incoming'. Below MGW B are labels 'IRF', 'HRN', and 'GSM'. Below the main sequence are three boxes labeled 'I', 'N', and 'I'. + +**Figure B.1: 3G to 3G Call (A to B) , originating RAB established after Nb bearer, same codec configuration on originating Iu and Nb bearers** + +NOTE: The Initialization Direction property of the Nb termination of MGW A could alternatively be set to 'Outgoing', but different RFCIs may then be initialized on the Iu and Nb bearers. + +![Figure B.2: 3G Originating Call diagram. It shows a sequence of nodes: IRF, MGW A (with 'Incoming' label above), MGW B (with 'Outgoing' label above), and IRF. Above MGW A is a label 'Incoming'. Below the main sequence are three boxes labeled 'I', 'N', and 'I'.](869c547c11ac7e123c51aba22289f2cd_img.jpg) + +Figure B.2: 3G Originating Call diagram. It shows a sequence of nodes: IRF, MGW A (with 'Incoming' label above), MGW B (with 'Outgoing' label above), and IRF. Above MGW A is a label 'Incoming'. Below the main sequence are three boxes labeled 'I', 'N', and 'I'. + +**Figure B.2: 3G Originating Call, originating RAB established after Nb bearer, same codec configuration on originating Iu and Nb bearers** + +NOTE: The Initialization Direction property of the Nb termination of MGW A could alternatively be set to 'Outgoing', but different RFCIs may then be initialized on the Iu and Nb bearers. + +![Figure B.3: 3G Terminating Call diagram. It shows a sequence of nodes: IRF, MGW A (with 'Incoming' label above), MGW B (with 'Outgoing' label above), and IRF. Above MGW A is a label 'Incoming'. Above MGW B are labels 'Incoming' and 'Outgoing'. Below MGW B are labels 'IRF', 'HRN', and 'GSM'. Below the main sequence are two boxes labeled 'N' and 'I'.](7c57192c514175021e4560a1a46126c1_img.jpg) + +Figure B.3: 3G Terminating Call diagram. It shows a sequence of nodes: IRF, MGW A (with 'Incoming' label above), MGW B (with 'Outgoing' label above), and IRF. Above MGW A is a label 'Incoming'. Above MGW B are labels 'Incoming' and 'Outgoing'. Below MGW B are labels 'IRF', 'HRN', and 'GSM'. Below the main sequence are two boxes labeled 'N' and 'I'. + +**Figure B.3: 3G Terminating Call** + +![Figure B.4: 3G to 3G Call (A to B) diagram. It shows a sequence of nodes: RNC A, MGW A (with 'Incoming' label above), MGW B (with 'Outgoing' label above), and RNC B. Above MGW A is a label 'Incoming'. Above MGW B are labels 'Incoming' and 'Outgoing'. Between MGW B and RNC B are labels 'RAB Init' and 'RFCI Value Correction'. Below the main sequence are three boxes labeled 'Iu', 'Nb', and 'Iu'.](fa6d4c394c470c63bca4c15b3c6db58e_img.jpg) + +Figure B.4: 3G to 3G Call (A to B) diagram. It shows a sequence of nodes: RNC A, MGW A (with 'Incoming' label above), MGW B (with 'Outgoing' label above), and RNC B. Above MGW A is a label 'Incoming'. Above MGW B are labels 'Incoming' and 'Outgoing'. Between MGW B and RNC B are labels 'RAB Init' and 'RFCI Value Correction'. Below the main sequence are three boxes labeled 'Iu', 'Nb', and 'Iu'. + +**Figure B.4: 3G to 3G Call (A to B), originating RAB established before or in parallel to the Nb bearer or different codec configuration on originating Iu and Nb bearers** + +![Diagram of 3G Originating Call flow](11f18bf0233d812ad2604f88f3385d60_img.jpg) + +This diagram illustrates a 3G originating call flow. It shows a sequence of components: RNC, SMGW, GMGW, and PSTN. The RNC is connected to the SMGW via an 'Iu' interface. The SMGW is connected to the GMGW via an 'Nb' interface. The GMGW is connected to the PSTN. Above the SMGW, there are labels 'Incoming' and 'Outgoing'. Above the GMGW, there is a label 'Incoming'. + +Diagram of 3G Originating Call flow + +Figure B.5: 3G Originating Call, originating RAB established before or in parallel to the Nb bearer or different codec configuration on originating Iu and Nb bearers + +![Diagram of 2G to 2G Call (A to B) flow](d9638e837004a4e09dbbc50b8aecbd5f_img.jpg) + +This diagram illustrates a 2G to 2G call flow between two base stations, BSC A and BSC B, through two media gateways, MGW A and MGW B. BSC A is connected to MGW A via an 'A' interface. MGW A is connected to MGW B via an 'Nb' interface. MGW B is connected to BSC B via an 'A' interface. Above MGW A, there is a label 'Outgoing'. Above MGW B, there is a label 'Incoming'. + +Diagram of 2G to 2G Call (A to B) flow + +Figure B.6: 2G to 2G Call (A to B) + +## Annex C (Normative): Profile description + +### C.1 Profile Identification + +| | | +|----------------------|--------------------| +| Profile name: | Threegbicsn | +| Version: | 6 | + +*The name and version of the profile that is sent in the service change command.* + +### C.2 Summary + +This Profile describes the minimum mandatory settings and procedures required to fulfil the requirements of the Mc interface media gateway control. In addition optional settings and procedures are described which fulfil optional features and where supported, the minimum mandatory settings within the optional procedures and packages are identified that must be supported in order to support that feature. + +"Optional" or "O" means that it is optional for either the sender or the receiver to implement an element. If the receiving entity receives an optional element that it has not implemented it should send an Error Code (e.g. 445" Unsupported or Unknown Property", 501"Not Implemented", etc.). "Mandatory" or "M" means that it is mandatory for the receiver to implement an element. Whether it is mandatory for the sender to implement depends on specific functions; detail of whether elements of the core protocol are mandatory to be sent are defined in the stage 2 procedures, stage 3 procedures and/or the descriptions of individual packages. + +The setting or modification of elements described in the profile under the heading "Used in Command" has the meaning that the property can be set/modified with that command. The property may be present in other commands (in order to preserve its value in accordance with ITU-T H.248.1[10]) when those commands are used for other procedures that affect the same descriptor. + +This profile supports Explicit Congestion Notification and Multimedia Priority Service. + +### C.3 Gateway Control Protocol Version + +#### ITU Recommendation H.248.1 Version 2 + +*The minimum H.248 version required to support the profile. This should be based upon base syntax support and not an arbitrary version assignment. This is related to the ServiceChangeVersion in clause C.8.8.* + +### C.4 Connection Model + +**Table C.4: Connection Model** + +| | | +|------------------------------------------------------------|----------------| +| Maximum number of contexts: | No restriction | +| Maximum number of terminations per context: | 32 | +| Allowed termination type combinations in a context: | All | + +## C.5 Context Attributes + +**Table C.5/1: Context attributes** + +| Context Attribute | Supported | Values Supported | +|---------------------------------------------|-------------------|--------------------------------------| +| Topology | Yes (NOTE 1) | See clause C.7.8 Topology Descriptor | +| Priority Indicator | Optional (NOTE 3) | 0-15 (NOTE 4) | +| Emergency Indicator | Yes | NA | +| IEPS Indicator (NOTE 2) | No | NA | +| ContextAttribute Descriptor (NOTE 2) | No | NA | +| ContextIDList Parameter (NOTE 2) | No | NA | + +NOTE 1: Stream ID in Topology Descriptor shall not be supported. +NOTE 2: This field requires at least version 3 of the H.248.1 protocol. +NOTE 3: This Context Attribute parameter is used for MPS as specified in 3GPP TS 22.153 [78]. +NOTE 4: Priority values 11 – 15 of the Priority Indicator are reserved for MPS. + +**Table C.5/2: AND/OR Context attributes** + +| AND/OR Context Attribute | No | NA | +|-----------------------------------------------------------------------|----|----| +| NOTE: This field requires at least version 3 of the H.248.1 protocol. | | | + +## C.6 Terminations + +### C.6.1 Termination Names + +#### C.6.1.1 General + +The Termination ID structure shall follow the guidelines of H.248 and the structure is either relevant or irrelevant for MGC and MGW. + +The relevance depends on the utilized bearer type for termination. With ephemeral ATM/AAL2 and IP endpoint bearer types the internal structure of Termination ID is irrelevant for MGW and MGC and therefore Termination ID is only numeric identifier for termination. When bearer type is physical timeslot within TDM circuit the Termination ID structure shall follow the Termination naming convention for TDM circuit bearer. + +Ephemeral terminations are further denoted in the profile by the following: + +- BICC (meaning applies to terminations towards BICC) +- BICC ATM (meaning applies to terminations towards BICC with ATM transport) +- BICC IP (meaning applies to terminations towards BICC with IP transport) +- Iu (meaning applies to terminations towards Iu interface) +- RTP (meaning applies to all IP terminations, e.g. SIP-I/Nb, Mb, AoIP) +- RTP-CN (meaning applies to terminations towards SIP-I) +- RTP-A (meaning applies to terminations towards A interface over IP) + +**Editor's Note:** it is FFS if specific handling in the profile for the RTP-CN or RTP-A types is needed. + +#### C.6.1.2 ASN.1 Coding + +##### C.6.1.2.1 General Structure + +The following general structure of termination ID shall be used: + +4 octets shall be used for the termination ID. The following defines the general structure for the termination ID: + +**Table C.6.1.2.1: ASN.1 coding** + +| | | +|------------------|---| +| Termination type | X | +|------------------|---| + +Termination type: + +Length 3 bits + +Values: + +000 Reserved + +001 Ephemeral termination + +010 TDM termination + +011 - 110 Reserved + +111 Reserved for ROOT termination Id (ROOT Termination ID = 0xFFFFFFFF) + +X: + +Length 29 bits. + +Usage dependent on Termination type. TDM terminations specified below in subclause C.6.1.2.2. Other usage un-specified. + +## C.6.1.2.2 Termination naming convention for TDM terminations + +**Table C.6.1.2.2 ASN.1 coding** + +| | | | +|-------------------------|------------|------------| +| Termination type (=010) | PCM system | Individual | +|-------------------------|------------|------------| + +PCM system: + +Length 24 bits + +Usage unspecified. Uniquely identifies PCM interface in MGW + +Individual: + +Length: 5 bits + +Max. of 32 individuals (timeslots) per PCM system (max. 24 for a 24 channel system) + +## C.6.1.3 ABNF Coding + +### C.6.1.3.1 General Structure + +The following general structure of termination ID shall be used: + +TerminationID = "ROOT" / pathName / "\$" / "\*" ; According to H.248.1 annex B + +### C.6.1.3.2 Termination naming convention for TDM terminations + +pathName = TDMToken UNDERSCORE ((PCMsystem / "\*") SLASH (Individual / "\*")) + +TDMToken = "TDM" + +UNDERSCORE = %x5F ;"\_" + +PCMsystem : Usage not specified + +Individual = 1 \* 2 (DIGIT) ; 0-31 + +### C.6.1.3.3 Termination naming convention for Ephemeral terminations + +pathName = EphTokenUNDERSCORE(EPHsystem/\*") + +EphToken = "Ephemeral" + +UNDERSCORE = %x5F ;"\_" + +EPHsystem : Usage is not specified + +## C.6.2 Multiplexed terminations + +Table C.6.2: Multiplexed terminations + +| | | +|------------------------------------------|----| +| Multiplex terminations supported? | No | +|------------------------------------------|----| + +## C.7 Descriptors + +### C.7.1 Stream Descriptor + +Table C.7.1: Stream descriptors + +| | | | +|-------------------------------------------------------|-----|---| +| Maximum number of streams per termination type | All | 1 | +|-------------------------------------------------------|-----|---| + +#### C.7.1.1 LocalControl Descriptor + +Table C.7.1.1/1: Local Control Descriptor + +| | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----|-------------------------|--------------------| +| If not generic list appropriate termination and stream types. | | Termination Type | Stream Type | +| ReserveGroup used: | No | - | - | +| ReserveValue used: | Yes | BICC (NOTE), RTP | Not Applicable | +| NOTE: The support is needed for the optional procedures Modify Char (see 14.2.27) and Reserve Char (see 14.2.28). These procedures use Q.1950 procedures which define the use of the Reserve Value. | | | | + +Table C.7.1.1/2: Allowed Stream Modes + +| Termination Type | Stream Type | Allowed StreamMode Values | +|-------------------------|--------------------|----------------------------------------| +| All | Not Applicable | SendOnly, RecvOnly, SendRecv, Inactive | + +### C.7.2 Events Descriptor + +All events contained in this profile may be set on any termination/stream with the following exceptions. + +Table C.7.2/1: Events Descriptor + +| | | | | +|---------------------------------------------------------------|--------------------------------|-------------------------|--------------------| +| Events settable on termination types and stream types: | Yes | | | +| If yes | EventID | Termination Type | Stream Type | +| | Cause (g/cause, 0x0001/0x0001) | All except ROOT | Not Applicable | + +| | | | +|---------------------------------------------------------------------------------------------|-----------------|----------------| +| Signal Completion (g/sc, 0x0001/0x0002) | All except ROOT | Not Applicable | +| Start tone detected (tonedet/std, 0x0004/0x0001) | All except ROOT | Not Applicable | +| End Tone detected (tonedet/etd, 0x0004/0x0002) | All except ROOT | Not Applicable | +| DTMF character 0
(dd/d0, 0x0006/0x0010)
to DTMF character D
(dd/dd, 0x0006/0x001d) | All except ROOT | Not Applicable | +| Completion (ct/cmp, 0x000a/0x0005) | TDM | Not Applicable | +| BNC Change (GB/BNCChange, 0x0021/0x01) | BICC, lu | Not Applicable | +| Tunnel Indication (BT/TIND, 0x0022/0x01) | BICC IP | Not Applicable | +| MGCon (chp/mgcon, 0x0029/0x0001) | ROOT | Not Applicable | +| Termination Heartbeat (hangterm/thb, 0x0098/0x0001) | All except ROOT | Not Applicable | +| Protocol Negotiation Result: (threegcd/protres, 0x0030/0x0001) | All except ROOT | Not Applicable | +| Rate Change (threegcd/ratechg, 0x0030/0x0002) | All except ROOT | Not Applicable | +| Optimal Codec Event (threegtoc/codec_modify, 0x0031/0x0010) | All except ROOT | Not Applicable | +| Codec List Event (threegtoc/distant_codec_list, 0x0031/0x0012) | All except ROOT | Not Applicable | +| TFO Status Event (threegtoc/TFO_status, 0x0031/0x0014) | All except ROOT | Not Applicable | +| Bearer Modification Support Event (threegmlc/mod_link_supp, 0x0046/0x0001) | lu | Not Applicable | +| Connection State Change (threegctm/connchange, 0x0068/0x0001) | All except ROOT | Not Applicable | +| Trace result (calltrace/ tracact, 0x0097/0x0001) | All except ROOT | Not Applicable | +| Inactivity Timeout (it/ito, 0x0045/0x0001) | ROOT | Not Applicable | +| Available Realms Changed (ipra/arc, 0x00e0/0x0001) | ROOT | Not Applicable | +| IP Flow Stop Detection (adid/ipstop, 0x009c/0x0001) | RTP-CN | Not Applicable | +| ECN Failure (ecnrous/fail, 0x010b/0x0001) | IP | Audio, Video | +| NOTE: Stream ID may be ignored in Events Descriptor | | | + +Table C.7.2/2: Event Buffer Control + +| | | +|---------------------------|----| +| EventBuffer Control used: | No | +|---------------------------|----| + +Table C.7.2/3: Keep active + +| | | +|----------------------------|-----| +| KeepActive used on events: | Yes | +|----------------------------|-----| + +**Table C.7.2/4: Embedded events and signals** + +| | | +|--------------------------------------------------|----| +| Embedded events in an Events Descriptor: | No | +| Embedded signals in an Events Descriptor: | No | + +**Table C.7.2/5: Regulated Embedded events** + +| | | +|-----------------------------------------------------------------------|------| +| Regulated Embedded events are triggered on: | None | +| NOTE: This field requires at least version 3 of the H.248.1 protocol. | | + +**Table C.7.2/6: ResetEventsDescriptor** + +| | | +|-----------------------------------------------------------------------|------| +| ResetEventsDescriptor used with events: | None | +| NOTE: This field requires at least version 3 of the H.248.1 protocol. | | + +**Table C.7.2/7: Notification Behaviour** + +| | | +|-----------------------------------------------------------------------|------------| +| NotifyImmediate: | ALL Events | +| NotifyRegulated: | None | +| NeverNotify: | None | +| NOTE: This field requires at least version 3 of the H.248.1 protocol. | | + +### C.7.3 EventBuffer Descriptor + +**Table C.7.3: Event Buffer Descriptor** + +| | | +|-------------------------------------|----| +| EventBuffer Descriptor used: | No | +|-------------------------------------|----| + +## C.7.4 Signals Descriptor + +**Table C.7.4/1: Signals Descriptor** + +| | | | | +|-----------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|-------------------------| +| The setting of signals is dependant on termination or streams types: | Yes

NOTE: "No" means that all signals can be played on any termination or stream. If "Yes", any signal not listed below may be played on any termination or stream, except Signals on ROOT termination shall not be supported. | | | +| If yes | SignalID | Termination Type | Stream Type / ID | +| | Establish BNC (GB/EstBNC, 0x0021/0x01) | BICC | Not Applicable | +| | Modify BNC (GB/ModBNC, 0x0021/0x02) | BICC | Not Applicable | +| | Release BNC (GB/RelBNC, 0x0021/0x03) | BICC ATM | Not Applicable | +| | Bearer Information Transport (BT/BIT, 0x0022/0x01) | BICC IP | Not Applicable | +| | Continuity Test (ct/ct, 0x000a/0x0003) | TDM | Not Applicable | +| | Respond (ct/rsp, 0x000a/0x0004) | TDM | Not Applicable | +| NOTE: Stream ID may be ignored for Signals Descriptor | | | | + +**Table C.7.4/2: Signal Lists** + +| | | | +|-----------------------------------------------------------------------|------------------------------------------------------|-----------------| +| Signals Lists supported: | Yes | | +| If yes | Termination Type Supporting Lists: | ALL except ROOT | +| | Stream Type Supporting lists: | ALL | +| | Maximum number of signals to a signal list: | FFS | +| | Intersignal delay parameter supported: (NOTE) | No | +| NOTE: This field requires at least version 3 of the H.248.1 protocol. | | | + +**Table C.7.4/3: Overriding Signal type and duration** + +| | | | +|--------------------------------------------|------------------------------------|----------------------------------| +| Signal type and duration supported: | Yes | | +| If yes | SignalID | Type or duration override | +| | All Tones, Announcements and DTMFs | Both | + +**Table C.7.4/4: Signal Direction** + +| | | +|-----------------------------------------------------------------------|----| +| Signal Direction supported: | No | +| NOTE: This field requires at least version 3 of the H.248.1 protocol. | | + +**Table C.7.4/5: Notify completion** + +| | | | +|-----------------------------------------------------------------------|-----------------------------|-------------------------------------| +| NotifyCompletion supported: | Yes | | +| If yes | SignalID | Type of completion supported | +| | All Tones and Announcements | TO, EV, SD, NC | +| RequestID Parameter supported: (NOTE) | No | | +| NOTE: This field requires at least version 3 of the H.248.1 protocol. | | | + +**Table C.7.4/6: Signals played simultaneously** + +| | | +|---------------------------------------|----| +| Signals played simultaneously: | No | +|---------------------------------------|----| + +Table C.7.4/7: Keep active + +| | | +|------------------------------------|-----| +| KeepActive used on signals: | Yes | +|------------------------------------|-----| + +## C.7.5 DigitMap Descriptor + +Table C.7.5: DigitMap Descriptor + +| | | +|-----------------------------|----| +| DigitMaps supported: | No | +|-----------------------------|----| + +## C.7.6 Statistics Descriptor + +Table C.7.6/1: Statistics Descriptor support + +| | | +|---------------------------------|-------------| +| Statistics supported on: | Termination | +|---------------------------------|-------------| + +Table C.7.6/2: Statistics Report on Subtract + +| | | | +|-----------------------------------------|---------------------------------|-------------------------------------------------------------------------------------------------| +| Statistics reported on Subtract: | Yes | | +| If yes | StatisticalIDs reported: | If Global Text Telephony used:
Characters Transferred (threeegctm/chartrans , 0x0068/0x0001) | + +## C.7.7 ObservedEvents Descriptor + +Table C.7.7: ObservedEvents Descriptor + +| | | +|----------------------------------------|----| +| Event detection time supported: | No | +|----------------------------------------|----| + +## C.7.8 Topology Descriptor + +Table C.7.8: Topology Descriptor + +| | | +|-------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Allowed triples: | (T1, T2, isolate) (T1, T2, oneway) (T1, T2, bothway) | +| NOTE: | The Topology Descriptor shall be supported by the MGW and MGC for VGCS, VBS, handover and lawful interception. It can also be used for sending tones and playing announcements. | + +## C.7.9 Error Descriptor + +Which H.248.8 and package defined error codes are supported? + +Table C.7.9/1: Error Codes Sent by MGC + +| | | +|---------------------------------------------------|--------------------------------------------------------------------------------------------------| +| Supported H.248.8 Error Codes: | ALL H.248.8, list of individual numbers> | +| Supported Error Codes defined in packages: | For a list of error codes see clauses 5.14.x | + +Table C.7.9/2: Error Codes Sent by MGW: + +| | | +|---------------------------------------------------|--------------------------------------------------------------------------------------------------| +| Supported H.248.8 Error Codes: | | +| Supported Error Codes defined in packages: | For a list of error codes see clauses 5.14.x | + +## C.7.10 TerminationState Descriptor + +**Table C.7.10/1: TerminationState Descriptor** + +| | | +|----------------------------------------------|------------------------| +| TerminationState: ServiceStates: | InService/OutOfService | +| TerminationState: EventBufferControl: | OFF | + +## C.8 Command API + +NOTE – It is assumed that an Error Descriptor may be returned in any command reply. + +### C.8.1 Add + +**Table C.8.1/1: Descriptors used by Command Add Request** + +| | | +|-----------------------------------------|----------------------------------------------------------------| +| Descriptors used by Add request: | Events, Signals, Media (LocalControl, Local And Remote), Audit | +|-----------------------------------------|----------------------------------------------------------------| + +**Table C.8.1/2: Descriptors used by Command Add Reply** + +| | | +|---------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Descriptors used by Add reply: |

Media (LocalControl, Local And Remote), Error

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

  • - The Error Descriptor
  • - SDP properties returned in "Reserve RTP Connection Point" and "Reserve and Configure RTP Connection Point" procedures, as specified in 14.2.51 and 14.2.53

The applicability of this restriction for text encoding is FFS.

| +|---------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +### C.8.2 Modify + +**Table C.8.2/1: Descriptors used by Command Modify Request** + +| | | +|--------------------------------------------|----------------------------------------------------------------| +| Descriptors used by Modify request: | Events, Signals, Media (LocalControl, Local And Remote), Audit | +|--------------------------------------------|----------------------------------------------------------------| + +**Table C.8.2/2: Descriptors used by Command Modify Reply** + +| | | +|------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Descriptors used by Modify reply: |

Media (LocalControl, Local And Remote), Error

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

  • - The Error Descriptor
  • - SDP properties returned in "Configure RTP Connection Point" in 14.2.52.

The applicability of this restriction for text encoding is FFS.

| +|------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +### C.8.3 Subtract + +**Table C.8.3/1: Descriptor used by Command Subtract Request** + +| | | +|----------------------------------------------|------| +| Descriptors used by Subtract request: | None | +|----------------------------------------------|------| + +**Table C.8.3/2: Descriptor used by Command Subtract Reply** + +| | | +|--------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Descriptors used by Subtract reply: |

None or Statistics

Ctmbits statistics are returned in the Subtract reply when related to a termination with CTM capabilities. Otherwise no statistics are returned.

| +|--------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +### C.8.4 Move + +**Table C.8.4/1: Command Move** + +| | | +|---------------------------|-----| +| Move command used: | Yes | +|---------------------------|-----| + +**Table C.8.4/2: Descriptors used by Move Request** + +| | | +|------------------------------------------|----------------------------------------------------------------| +| Descriptors used by Move request: | Events, Signals, Media (LocalControl, Local And Remote), Audit | +|------------------------------------------|----------------------------------------------------------------| + +**Table C.8.4/3: Descriptors used by Move Reply** + +| | | +|----------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Descriptors used by Move reply: | Media (LocalControl, Local And Remote), Error

When MOVE commands exclude an Audit Descriptor, the MGW response shall only include descriptors which contained underspecified or overspecified properties in the command request, with the exception of the Error Descriptor. Furthermore, only those properties that were underspecified or overspecified in the request shall be sent in the reply.
The applicability of this restriction for text encoding is FFS. | +|----------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +## C.8.5 AuditValue + +**Table C.8.5: Auditvalue** + +| Audited Properties: | Property Name and Identity | Descriptor | +|--------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------| +| Termination ID | TerminationState:
- TDM: ALL (indicating 1 TDM group) , individual termination (NOTE2)
- ATM/IP: individual termination
- Root (MGW Audit) | TerminationState Descriptor | +| Termination ID | For Packages:
- Root | Packages Descriptor (NOTE1) | +| Termination ID | None (MGW Audit) :
- Root | Audit (empty) Descriptor | +| Termination ID | IP Realm Availability :
- ipra/* (ROOT) | TerminationState Descriptor | +| Audited Statistics: | None | | +| Audited Signals: | None | | +| Audited Events: | None | | +| Packages Audit Possible | Yes | | + +NOTE1: Support of this capability is optional. +NOTE2: Auditing a single termination of a TDM group is an alternative to the wildcarded audit (TDM: ALL) to derive the service state of the TDM group (all the terminations of the TDM group share the same service state). + +## C.8.6 AuditCapability + +**Table C.8.6/1: Auditcapability** + +| Audited Properties: | Property Name and Identity | Descriptor | +|----------------------------|-----------------------------------|-------------------| +| | FFS | FFS | +| Audited Statistics: | None | | +| Audited Signals: | None | | +| Audited Events: | None | | + +**Table C.8.6/2: Scoped Auditing** + +| | | +|-------------------------------------------------------------------------|------| +| Audited Properties / ContextAttributes used for a scoped audit : | None | +| NOTE: This field requires at least version 3 of the H.248.1 protocol. | | + +## C.8.7 Notify + +**Table C.8.7: Descriptors Used Notify** + +| | | +|------------------------------------------------------------------|-----------------------| +| Descriptors used by Notify Request or Reply: | ObservedEvents, Error | +| NOTE : The Error Descriptor shall not be used in Notify Request. | | + +## C.8.8 ServiceChange + +**Table C.8.8/1: ServiceChangeMethods and ServiceChangeReasons sent by MGC:** + +| Service Change Methods Supported: | ServiceChange Reasons supported: | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------| +| Restart (NOTE1) | "901 Cold Boot" (Optional)
"902 Warm Boot" (Optional) | +| Handoff (NOTE 1, NOTE 2) | "903 MGC Directed Change" (Mandatory) | +| Forced (NOTE1) | "905 Termination Taken Out Of Service" (Optional) | +| Graceful (NOTE1) | "905 Termination Taken Out Of Service" (Optional) | +| NOTE: When a Service Change command on the Root termination with a method other than Graceful is sent, the command shall always be sent as the only command in a message. The sending node shall always wait for the reply to a Service Change command on the Root termination with a method other than Graceful before sending further command requests. A Service Change command on the Root termination with method Graceful may be combined with other commands in a single message. | | +| NOTE1: ROOT Only. | | +| NOTE2: Not involving more than 1 MSC-S. This does not preclude the use of the MGCIId in a ServiceChange (Handoff) scenario, nor does it change the expected MG behaviour upon receipt of such a message, as the MGW has actually no means to differentiate whether the ServiceChangeMgCIId parameter that may be received in a ServiceChange (handoff) message relates to a logical MGC inside the same MSC server or is part of another MSC-Server. | | + +**Table C.8.8/2: ServiceChangeMethods and ServiceChangeReasons sent by MG:** + +| Service Change Methods Supported: | ServiceChange Reasons supported: | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Restart | "900 Service Restored" (Mandatory)
"901 Cold Boot" (Mandatory) (NOTE1)
"902 Warm Boot" (Mandatory) (NOTE1)
"910 Media Capability Failure " ALL except ROOT (Optional)
"913 Signal Capability Failure " ALL except ROOT (Optional)"914 Event Capability Failure " ALL except ROOT (Optional)
"916 Packages Change" (Optional)
"917 Capability Change "(Optional) | +| Graceful | "904 Termination Malfunction" , ALL except ROOT,(Mandatory)
"905 Termination Taken Out Of Service" , ALL,(Mandatory)
"906 Loss Of Lower Layer Connectivity" , ALL except ROOT,(Mandatory)
"907 Transmission Failure" , ALL except ROOT,(Mandatory)
"908 MG Impending Failure" ROOT only (Mandatory) | +| Forced | "904 Termination Malfunction", ALL except ROOT (Mandatory)
"905 Termination Taken Out Of Service" , Mandatory)
"906 Loss Of Lower Layer Connectivity" , ALL except ROOT (Mandatory)
"907 Transmission Failure" , ALL except ROOT (Mandatory)
"908 MG Impending Failure" ROOT only (Mandatory) | +| Handoff (NOTE 1, NOTE 2) | "903 MGC Directed Change" (Mandatory) | +| Disconnected (NOTE 1) | "900 Service Restored" (Mandatory)
"916 Packages Change" (Optional)
"917 Capability Change" (Optional) | +| NOTE: When a Service Change command on the Root termination with a method other than Graceful is sent, the command shall always be sent as the only command in a message. The sending node shall always wait for the reply to a Service Change command on the Root termination with a method other than Graceful before sending further command requests. A Service Change command on the Root termination with method Graceful may be combined with other commands in a single message. | | +| NOTE 1: ROOT Only. | | +| NOTE 2: In response to a MGC Ordered Re-Register. | | + +**Table C.8.8/3: Service Change Address** + +| | | +|-----------------------------------|----| +| ServiceChangeAddress used: | No | +|-----------------------------------|----| + +**Table C.8.8/4: Service Change Delay** + +| | | +|---------------------------------|----| +| ServiceChangeDelay used: | No | +|---------------------------------|----| + +**Table C.8.8/5: Service Change Incomplete Flag** + +| | | +|-----------------------------------------------------------------------|----| +| ServiceChange Incomplete Flag used: | No | +| NOTE: This field requires at least version 3 of the H.248.1 protocol. | | + +**Table C.8.8/6: Service Change Version** + +| | | +|----------------------------------------------|---| +| Version used in ServiceChangeVersion: | 2 | +|----------------------------------------------|---| + +**Table C.8.8/7: Service Change Profile** + +| | | +|----------------------------------------|-----| +| ServiceChangeProfile mandatory: | Yes | +|----------------------------------------|-----| + +**Table C.8.8/8: Profile negotiation** + +| | | +|---------------------------------------------|----| +| Profile negotiation as per H.248.18: | No | +|---------------------------------------------|----| + +## C.8.9 Manipulating and auditing context attributes + +**Table C.8.9: Manipulating and auditing context attributes** + +| | | +|----------------------------------------|---------------------------------------------------| +| Context Attributes Manipulated: | Topology, Emergency Indicator, Priority Indicator | +| Context Attributes Audited: | None | + +## C.9 Generic command syntax and encoding + +**Table C.9.1: Encodings** + +| | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------| +| Supported Encodings: | Binary (optional) (NOTE 2)
Text (optional) (NOTE 1) | +| If binary encoding, is indefinite length encoding supported: | Yes (NOTE 3) | +| NOTE 1: For a BICC network with IP transport and IPBCP is transported within H.248 messages, text encoding is not recommended to be used on Mc interface until ITU has resolved the contradiction in RFC2327 [34] and H.248.1 [10] on the usage of CR (ASCII carriage return 0x0d) and/or LF (ASCII newline 0x0a) characters e.g. in SDP these Characters are missing when using the currently specified "quotedString" type.
NOTE 2: Binary encoding is strongly recommended if only one encoding is selected to ensure interoperability.
NOTE 3: The binary encoding rules which are applicable to the defined Abstract Syntaxes are the Basic Encoding Rules for Abstract Syntax Notation One, defined in ITU-T Recommendation X.690 [41]. Specifically in accordance with ITU-T Recommendation X.690 [41] section 7.3, alternative encodings based on the definite and indefinite form of length are permitted by the basic encoding rules as a sender's option. Receivers shall support both alternatives. | | + +## C.10 Transactions + +**Table C.10/1: Transactions per Message** + +| | | +|----------------------------------------------------------------------------------------------------------------------|----| +| Maximum number of TransactionRequests / TransactionReplies / TransResponseAcks / Segment Replies per message: | 10 | +|----------------------------------------------------------------------------------------------------------------------|----| + +**Table C.10/2: Commands per Transaction Requests** + +| | | +|-----------------------------------------------------------|-------------| +| Maximum number of commands per TransactionRequest: | Unspecified | +|-----------------------------------------------------------|-------------| + +**Table C.10/3: Commands per Transaction Reply** + +| | | +|------------------------------------------------------------------------------------------------------------------------------------------|-------------| +| Maximum number of commands per TransactionReply: | Unspecified | +| NOTE: For auditing with wildcarded requests (e.g TDM E1) then the reply may include up to 32 commands to indicate the termination state) | | + +**Table C.10/4: Optional Commands** + +| | | +|-----------------------------------------------|-----| +| Commands able to be marked "Optional": | ALL | +|-----------------------------------------------|-----| + +**Table C.10/5: Commands for Wildcarded Responses** + +| | | +|---------------------------------------------------|------------------------------| +| Wildcarded responses may be requested for: | Modify, Subtract, AuditValue | +|---------------------------------------------------|------------------------------| + +**Table C.10/6: Procedures for Wildcarded Responses** + +| | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------| +| Procedures that make use of wildcarded responses: | Release Bearer, Release Termination, Audit Value | +| NOTE: Used when multiple terminations are released with one command and in audit responses where multiple terminations are implied by the audit request. | | + +**Table C.10/7: Transaction Timers** + +| Transaction Timer: | Value | +|------------------------------------------|--------------| +| normalMGExecutionTime | Provisioned | +| normalMGCExecutionTime | Provisioned | +| MGOriginatedPendingLimit | Provisioned | +| MGCOriGINatedPendingLimit | Provisioned | +| MGProvisionalResponseTimerValue | Provisioned | +| MGCPProvisionalResponseTimerValue | Provisioned | + +## C.11 Messages + +The MGC/MGW shall be named according to the naming structure of the underlying transport protocol which carries the H.248 protocol. + +## C.12 Transport + +**Table C.12/1: Transport** + +| | | +|-----------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Supported Transports: |

1) For pure IP connections, H.248/SCTP/IP should be used. In addition, to allow for flexible implementations of gateways and controllers in order to offer efficient use of SCTP associations the M3UA layer may also be added on top of SCTP

2) For pure ATM connections, H.248/MTP3b/SSCF/SSCOP/AAL5/ATM should be used.

3) For mixed IP&ATM connections, H.248/M3UA/SCTP/IP shall be used as the IP transport.

| +| NOTE1: If using SCTP as defined in IETF RFC 2960 [12] the MGW shall always be the node to perform the "Initiation". | | +| NOTE2: Checksum calculation for SCTP shall be supported as specified in RFC 3309 [44] instead of the method specified in RFC 2960 [12]. | | + +**Table C.12/2: Segmentation** + +| | | +|-----------------------------------------------------------------------|----| +| Segmentation Supported: | No | +| NOTE: This field requires at least version 3 of the H.248.1 protocol. | | + +**Table C.12/3: Support of Control Association Monitoring** + +| | | +|--------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------| +| Control Association Monitoring Supported: |

1) Inherent in Transport

2) H.248.14 (optional MGW-driven monitoring)

3) Empty AuditValue on Root (MGC-driven monitoring)

| +|--------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------| + +## C.13 Security + +**Table C.13: Security** + +| | | +|----------------------------|------| +| Supported Security: | None | +|----------------------------|------| + +## C.14 Packages + +**Table C.14/1: Mandatory packages** + +| Mandatory Packages: | | | +|------------------------------------------------------------------------------------------------|-------------------------------|----------------| +| Package Name | PackageID | Version | +| Generic (see ITU-T Recommendation H.248.1 [10] annex E.1) | g, (0x0001) | v1 | +| Base Root Package (see ITU-T Recommendation H.248.1 [10] annex E.2) | root, (0x0002) | v2 | +| Tone Detection Package (see ITU-T Recommendation H.248.1 [10] annex E.4) | tonedet, (0x0004)
(NOTE 1) | v1 | +| Basic DTMF Generator Package (see ITU-T Recommendation H.248.1 [10] annex E.5) | dg, (0x0005) | v1 | +| DTMF Detection Package (see ITU-T Recommendation H.248.1 [10] annex E.6) | dd, (0x0006) | v1 | +| Generic Announcement Package (see ITU-T Recommendation H.248.7 [28]) – Fixed Announcements. | an, (0x001d) | v1 | +| TDM Circuit Package (see ITU-T Recommendation H.248.1 [10] annex E.13)
NOTE 2 | tdmc, (0x000d) | v1 | +| Media Gateway Resource Congestion Handling Package (see ITU-T Recommendation H.248.10 [15] ) | chp, (0x0029) | v1 | +| Hanging Termination Detection package (see ITU-T Recommendation H.248.36 [36]). | hangterm, (0x0098) | v1 | +| NOTE 1: This package is "for extension only" and shall not be published over the Mc interface. | | | +| NOTE 2: Network Package is not supported. | | | + +Table C.14/2: Optional packages + +| Optional Packages: | | | | +|-----------------------------------------------------------------------------------------------------------|----------------------|---------|---------------------------------------------| +| Package Name | PackageID | Version | Support dependent on: | +| Basic Call Progress Tones Generator with Directionality, (see ITU-T Recommendation Q.1950 [23] annex A.8) | bcg, (0x0023) | v1 | Services provided by network | +| Expanded Call Progress tones Generator Package (see ITU-T Recommendation Q.1950 [23] annex A.9) | xcg, (0x0024) | v1 | Services provided by network | +| Basic Services Tones Generation Package (see ITU-T Recommendation Q.1950 [23] annex A.10) | srvtn, (0x0025) | v1 | Services provided by network | +| Bearer Control Tunnelling Package (see ITU-T Recommendation Q.1950 [23] annex A.7) | Bt, (0x0022) | v1 | Interworking with BICC and IP transport | +| Expanded Services Tones Generation Package (see ITU-T Recommendation Q.1950 [23] annex A.11) | xsrvtn, (0x0026) | v1 | Services provided by network | +| Intrusion Tones Generation Package (see ITU-T Recommendation Q.1950 [23] annex A.12) | Int, (0x0027) | v1 | Services provided by network | +| Business Tones Generation Package (see ITU-T Recommendation Q.1950 [23] annex A.13) | BIZTN, (0x0028) | v1 | Services provided by network | +| Tone Generator Package (see ITU-T Recommendation H.248.1 [10] annex E.3) | tongen, (0x0003) | v1 | (NOTE) | +| Generic Announcement Package (see ITU-T Recommendation H.248.7 [28]) – Variable Announcements | an, (0x001d) | v1 | Variable Announcements | +| Text Telephony Package (see ITU-T Recommendation H.248.2 [17]). | txp, (0x0010) | v1 | Global text telephony support | +| Call Discrimination package (see ITU-T Recommendation H.248.2 [17]). | ctyp, (0x0011) | v2 | Global text telephony support | +| Basic Continuity Package (see ITU-T Recommendation H.248.1 [10] annex E.10). | ct, (0x000a) | v1 | Only required for TDM side terminations | +| Circuit Switched Data package (see subclause 15.2.1); | threegcd, (0x0030) | v1 | Circuit Switched Data support | +| TFO package (see subclause 15.2.2); | threegfoc, (0x0031) | v2 | TFO support | +| 3G Expanded Call Progress Tones Generator package (see subclause 15.2.3); | threegxcg, (0x0032) | v1 | Services provided by network | +| Modification of Link Characteristics Bearer Capability package (see subclause 15.2.4); | threegmlc, (0x0046) | v1 | | +| Enhanced Circuit Switched Data package (see subclause 15.2.5); | threegcden, (0x0082) | v1 | Circuit Switched Data support | +| Cellular Text telephone Modem Text Transport package (see subclause 15.2.6); | threegctm, (0x0068) | v1 | Global text telephony support | +| Flexible Tone Generator Package (see subclause 15.2.8). | threegflex, (0x0084) | v1 | Services provided by network | +| Trace Package (see subclause 15.2.9) | calltrace, (0x0097) | v1 | | +| ASCI Group call package (see subclause 15.2.10) | threegasci, (0x00b2) | v2 | VGCS and VBS services supported | +| IP Domain connection package (see ITU-T Recommendation H.248.41 [42]) | ipdc, (0x009d) | v1 | Multiple IP realms supported | +| Inactivity timer package (see ITU-T Recommendation H.248.14 [45]) | it, (0x0045) | v1 | UDP transport supported | +| 3GUP (User Plane) package (see subclause 15.1.1) | threegup, (0x002f) | v1 | Mandatory for BICC and Iu terminations | +| Bearer Characteristics Package (see ITU-T Recommendation Q.1950 [23] annex A.3) | bcp, (0x001e) | v2 | Mandatory for BICC terminations | +| Generic Bearer Connection Package (see ITU-T Recommendation Q.1950 [23] annex A.6) | Gb, (0x0021) | v1 | Mandatory only for BICC and Iu terminations | +| 3G Interface Type package (see subclause 15.2.11) | threegint (0x00e3) | v1 | | +| RTP Control Protocol Package (ITU-T Recommendation H.248.57 [66]) | rtcph, (0x00b5) | v1 | Border control functions support | +| Gate management Source Address/Port Filtering Package (ITU-T Recommendation H.248.43, Clause 7 [67]) | gm, (0x008c) | v2 | Border control functions support | +| Traffic management (ITU-T Recommendation H.248.53 [69]) | tman, (0x008d) | v1 | Border control functions support | +| Diffserv (ITU-T Recommendation H.248.52 [70]) | ds, (0x008b) | v2 | Border control functions support | + +| | | | | +|----------------------------------------------------------------------------------------------------|-----------------|----|----------------------------------| +| Application Data Inactivity Detection (ITU-T Recommendation H.248.40 [71]) | adid (0x009c) | v1 | Border control functions support | +| IP realm availability (ITU-T Recommendation H.248.41 Amendment 1) [72] | ipra (0x00e0) | v1 | Border control functions support | +| Explicit Congestion Notification for RTP-over-UDP Support (see ITU-T Recommendation H.248.82 [79]) | ecnrous(0x010b) | v1 | Support of ECN feature | +| NOTE: This package is "for extension only" and shall not be published over the Mc interface. | | | | + +#### Package Usage Information + +This table specifies how the packages above will be used. For example: + +- it lists whether the properties/signals/events/statistics are optional or mandatory +- if the value of the property/signal/event provisioned the provisioned value should be specified. (e.g. names and number of cycles for an H.248.7 announcement). + +Specifies the values of properties which are specified as provisioned + +Package Usage Information: + +## C.14.1 Generic Package + +Table C.14.1: Package Usage Information For Generic Package + +| Properties | Mandatory/Optional | Used in command: | Supported Values: | Provisioned Value: | | | +|------------------------------------------|--------------------------------------|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------|--|--| +| None | - | - | - | - | | | +| Signals | Mandatory/Optional | Used in command: | | Duration Provisioned Value: | | | +| None | - | - | - | - | | | +| | Signal Parameters | Mandatory/Optional | Supported Values: | Duration Provisioned Value: | | | +| | - | - | - | - | | | +| Events | Mandatory/Optional | Used in command: | | | | | +| | M | ADD, MOD, NOTIFY | | | | | +| | Event Parameters | Mandatory/Optional | Supported Values: | Provisioned Value: | | | +| | None | - | - | - | | | +| | ObservedEvent Parameters | Mandatory/Optional | Supported Values: | Provisioned Value: | | | +| Cause (g/cause, 0x0001/0x0001) | General Cause (GeneralCause, 0x0001) | M | "NR" (0x0001) Normal Release
"UR" (0x0002) Unavailable Resources
"FT" (0x0003) Failure, Temporary
"FP" (0x0004) Failure, Permanent
"IW" (0x0005) Interworking Error
"UN" (0x0006) Unsupported | Not Applicable | | | +| | Failure Cause (FailureCause, 0x0002) | O | Octet String | Not Applicable | | | +| Events | Mandatory/Optional | Used in command: | | | | | +| | M | ADD, MOD, MOVE, NOTIFY | | | | | +| | Event Parameters | Mandatory/Optional | Supported Values: | Provisioned Value: | | | +| | None | - | - | - | | | +| | ObservedEvent Parameters | Mandatory/Optional | Supported Values: | Provisioned Value: | | | +| Signal Completion. (g/sc, 0x0001/0x0002) | Signal Identity (SigID, 0x0001) | M | pkgdName syntax | Not Applicable | | | +| | Termination Method (Meth, 0x0002) | M | "TO" (0x0001) Signal timed out or otherwise completed on its own
"EV" (0x0002) Interrupted by event
"SD" (0x0003) Halted by new Signals descriptor
"NC" (0x0004) Not completed, other cause | Not Applicable | | | +| | Signal List Id | O | Integer | Not Applicable | | | +| Statistics | Mandatory/Optional | Used in command: | | Supported Values: | | | +| None | - | - | | - | | | +| Error Codes | Mandatory/Optional | | | | | | +| None | - | | | | | | + +## C.14.2 Base Root Package + +Table C.14.2: Package Usage Information For Base Root Package + +| Properties | Mandatory/Optional | Used in command: | Supported Values: | Provisioned Value: | | | +|------------------------------------------------------------------------------------------|--------------------------|---------------------|----------------------------------------------------------|-----------------------------|--|--| +| MaxNrOfContexts
(root/numberOfContexts, 0x0002/0x0001) | O | Not used in command | 1 and up | Not Applicable | | | +| MaxTerminationsPerContext
(root/maxTerminationPerContext, 0x0002/0x0002) | O | Not used in command | See C.4 | Not Applicable | | | +| normalMGExecutionTime
(root/normalMGExecutionTime, 0x0002/0x0003) | O | Not used in command | Integer | Operator Defined | | | +| normalMGExecutionTime
(root/normalMGExecutionTime, 0x0002/0x0004) | O | Not used in command | Integer | Operator Defined | | | +| MGProvisionalResponseTimerValue
(root/MGProvisionalResponseTimerValue, 0x0002/0x0005) | O | Not used in command | Integer (initially NormalMGExecutionTime + networkdelay) | Operator Defined | | | +| MGProvisionalResponseTimerValue
(root/MGProvisionalResponseTimerValue, 0x0002/0x0006) | O | Not used in command | Integer (initially NormalMGExecutionTime + networkdelay) | Operator Defined | | | +| MGOriginatedPendingLimit
(root/MGOriginatedPendingLimit, 0x0002/0x0007) | O | Not used in command | Integer | Operator Defined | | | +| MGOriginatedPendingLimit
(root/MGOriginatedPendingLimit, 0x0002/0x0008) | O | Not used in command | Integer | Operator Defined | | | +| Signals | Mandatory/Optional | Used in command: | | Duration Provisioned Value: | | | +| None | - | - | | - | | | +| | Signal Parameters | Mandatory/Optional | Supported Values: | Duration Provisioned Value: | | | +| | - | - | - | - | | | +| Events | Mandatory/Optional | Used in command: | | | | | +| None | - | - | | | | | +| | Event Parameters | Mandatory/Optional | Supported Values: | Provisioned Value: | | | +| | - | - | - | - | | | +| | ObservedEvent Parameters | Mandatory/Optional | Supported Values: | Provisioned Value: | | | +| Statistics | Mandatory/Optional | Used in command: | | Supported Values: | | | +| None | - | - | | - | | | +| Error Codes | Mandatory/ Optional | | | | | | +| None | - | | | | | | + +## C.14.3 Tone Generator Package + +Table C.14.3: Package Usage Information For Tone Generator Package + +| Properties | Mandatory/ Optional | Used in command: | Supported Values: | Provisioned Value: | | | +|-----------------------------------------|---------------------------------|----------------------------|--------------------------|------------------------------------|--|--| +| None | - | - | - | - | | | +| Signals | Mandatory/ Optional | Used in command: | | Duration Provisioned Value: | | | +| Play Tone
(tonegen/pt,0x0003/0x0001) | Not Used | - | - | - | | | +| | Signal Parameters | Mandatory/ Optional | Supported Values: | Duration Provisioned Value: | | | +| | - | - | - | - | | | +| Events | Mandatory/ Optional | Used in command: | | | | | +| None | - | - | | | | | +| | Event Parameters | Mandatory/ Optional | Supported Values: | Provisioned Value: | | | +| | - | - | - | - | | | +| | ObservedEvent Parameters | Mandatory/ Optional | Supported Values: | Provisioned Value: | | | +| | - | - | - | - | | | +| Statistics | Mandatory/ Optional | Used in command: | | Supported Values: | | | +| None | - | - | | - | | | +| Error Codes | Mandatory/ Optional | | | | | | +| None | - | | | | | | + +## C.14.4 Tone Detection Package + +Table C.14.4: Package Usage Information For Tone Detection Package + +| Properties | Mandatory/Optional | Used in command: | Supported Values: | Provisioned Value: | | | +|--------------------------------------------------|---------------------------------|---------------------------|--------------------------|------------------------------------|--|--| +| None | - | - | - | - | | | +| Signals | Mandatory/Optional | Used in command: | | Duration Provisioned Value: | | | +| None | - | - | - | - | | | +| | Signal Parameters | Mandatory/Optional | Supported Values: | Duration Provisioned Value: | | | +| | - | - | - | - | | | +| Events | Mandatory/Optional | Used in command: | | | | | +| Start tone detected (tonedet/std, 0x0004/0x0001) | O | ADD, MOD, MOVE, NOTIFY | | | | | +| | Event Parameters | Mandatory/Optional | Supported Values: | Provisioned Value: | | | +| | Tone ID List (tl,0x0001) | M | wildcard | Not Applicable | | | +| | ObservedEvent Parameters | Mandatory/Optional | Supported Values: | Provisioned Value: | | | +| | Tone ID (tid,0x0003) | M | Value | Not Applicable | | | +| Events | Mandatory/Optional | Used in command: | | | | | +| End Tone detected (tonedet/etd, 0x0004/0x0002) | M | ADD, MOD, MOVE, NOTIFY | | | | | +| | Event Parameters | Mandatory/Optional | Supported Values: | Provisioned Value: | | | +| | Tone ID List (tl,0x0001) | M | wildcard | Not Applicable | | | +| | ObservedEvent Parameters | Mandatory/Optional | Supported Values: | Provisioned Value: | | | +| | Tone ID (tid,0x0003) | M | Value | Not Applicable | | | +| | Duration (dur,0x0002) | O | Value | Not Applicable | | | +| Events | Mandatory/Optional | Used in command: | | | | | +| Long Tone detected (tonedet/ltd, 0x0004/0x0003) | Not Used | - | | | | | +| | Event Parameters | Mandatory/Optional | Supported Values: | Provisioned Value: | | | +| | - | - | - | - | | | +| | ObservedEvent Parameters | Mandatory/Optional | Supported Values: | Provisioned Value: | | | +| | - | - | - | - | | | +| Statistics | Mandatory/Optional | Used in command: | | Supported Values: | | | +| None | - | - | | - | | | +| Error Codes | Mandatory/ Optional | | | | | | +| None | - | | | | | | + +## C.14.5 Basic DTMF Generator Package + +Table C.14.5: Package Usage Information For Basic DTMF Generator Package + +| Properties | Mandatory/ Optional | Used in command: | Supported Values: | Provisioned Value: | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------|----------------------------|--------------------------|------------------------------------|--|--| +| None | - | - | - | - | | | +| Signals | Mandatory/ Optional | Used in command: | | Duration Provisioned Value: | | | +| DTMF character 0 (dg/d0,0x0005/0x0010)
DTMF character 1 (dg/d1,0x0005/0x0011)
DTMF character 2 (dg/d2,0x0005/0x0012)
DTMF character 3 (dg/d3,0x0005/0x0013)
DTMF character 4 (dg/d4,0x0005/0x0014)
DTMF character 5 (dg/d5,0x0005/0x0015)
DTMF character 6 (dg/d6,0x0005/0x0016)
DTMF character 7 (dg/d7,0x0005/0x0017)
DTMF character 8 (dg/d8,0x0005/0x0018)
DTMF character 9 (dg/d9,0x0005/0x0019)
DTMF character * (dg/ds,0x0005/0x0020)
DTMF character # (dg/do,0x0005/0x0021)
DTMF character A (dg/da,0x0005/0x001a)
DTMF character B (dg/db,0x0005/0x001b)
DTMF character C (dg/dc,0x0005/0x001c)
DTMF character D (dg/dd,0x0005/0x001d) | M | ADD, MOD, MOVE | | - | | | +| | Signal Parameters | Mandatory/ Optional | Supported Values: | Duration Provisioned Value: | | | +| | None | - | - | - | | | +| | | | | | | | +| | | | | | | | +| | | | | | | | +| | | | | | | | +| | | | | | | | +| | | | | | | | +| | | | | | | | +| | | | | | | | +| | | | | | | | +| | | | | | | | +| | | | | | | | +| | | | | | | | +| | | | | | | | +| Events | Mandatory/ Optional | Used in command: | | | | | +| None | - | - | | | | | +| | Event Parameters | Mandatory/ Optional | Supported Values: | Provisioned Value: | | | +| | - | - | - | - | | | +| | ObservedEvent Parameters | Mandatory/ Optional | Supported Values: | Provisioned Value: | | | +| | - | - | - | - | | | +| Statistics | Mandatory/ Optional | Used in command: | | Supported Values: | | | +| None | - | - | | - | | | +| Error Codes | Mandatory/ Optional | | | | | | +| None | - | | | | | | + +## C.14.6 Basic DTMF Detection Package + +Table C.14.6: Package Usage Information For Basic DTMF Detection Package + +| Properties | Mandatory/ Optional | Used in command: | Supported Values: | Provisioned Value: | +|------------|---------------------|------------------|-------------------|--------------------| +| None | - | - | - | - | + +| Signals | Mandatory/
Optional | Used in command: | | Duration Provisioned
Value: | | | +|-------------------------------------------|-----------------------------|------------------------|----------------------|--------------------------------|--|--| +| None | - | - | | - | | | +| | Signal Parameters | Mandatory/
Optional | Supported
Values: | Duration Provisioned
Value: | | | +| | - | - | - | - | | | +| Events | Mandatory/
Optional | Used in command: | | | | | +| DTMF character 0
(dd/d0,0x0006/0x0010) | M | ADD, MOD, NOTIFY | | | | | +| DTMF character 1
(dd/d1,0x0006/0x0011) | Event
Parameters | Mandatory/
Optional | Supported
Values: | Provisioned Value: | | | +| DTMF character 2
(dd/d2,0x0006/0x0012) | None | - | - | - | | | +| DTMF character 3
(dd/d3,0x0006/0x0013) | ObservedEvent
Parameters | Mandatory/
Optional | Supported
Values: | Provisioned Value: | | | +| DTMF character 4
(dd/d4,0x0006/0x0014) | None | - | - | - | | | +| DTMF character 5
(dd/d5,0x0006/0x0015) | | | | | | | +| DTMF character 6
(dd/d6,0x0006/0x0016) | | | | | | | +| DTMF character 7
(dd/d7,0x0006/0x0017) | | | | | | | +| DTMF character 8
(dd/d8,0x0006/0x0018) | | | | | | | +| DTMF character 9
(dd/d9,0x0006/0x0019) | | | | | | | +| DTMF character *
(dd/ds,0x0006/0x0020) | | | | | | | +| DTMF character #
(dd/d0,0x0006/0x0021) | | | | | | | +| DTMF character A
(dd/da,0x0006/0x001a) | | | | | | | +| DTMF character B
(dd/db,0x0006/0x001b) | | | | | | | +| DTMF character C
(dd/dc,0x0006/0x001c) | | | | | | | +| DTMF character D
(dd/dd,0x0006/0x001d) | | | | | | | +| Events | Mandatory/
Optional | Used in command: | | | | | +| | Not used | - | | | | | +| | Event
Parameters | Mandatory/
Optional | Supported
Values: | Provisioned Value: | | | +| | - | - | - | - | | | +| | ObservedEvent
Parameters | Mandatory/
Optional | Supported
Values: | Provisioned Value: | | | +| | - | - | - | - | | | +| Statistics | Mandatory/
Optional | Used in command: | | Supported Values: | | | +| None | - | - | | - | | | +| Error Codes | Mandatory/ Optional | | | | | | +| None | - | | | | | | + +## C.14.7 Continuity Package + +Table C.14.7: Package Usage Information For Basic Continuity Package + +| Properties | Mandatory/
Optional | Used in command: | Supported Values: | Provisioned Value: | +|------------|------------------------|------------------|-------------------|--------------------| +| None | - | - | - | - | + +| Signals | Mandatory/
Optional | Used in command: | | Duration Provisioned
Value: | | | +|---------------------------------------------------------------------------------------|-------------------------------------|--------------------------------|------------------------------|----------------------------------------|--|--| +| Continuity Test
(ct/ct,
0x000a/0x0003)
Respond
(ct/rsp,
0x000a/0x0004) | M | ADD, MOD, MOVE | | Default | | | +| | Signal Parameters | Mandatory/
Optional | Supported
Values: | Duration Provisioned
Value: | | | +| | None | - | - | - | | | +| Events | Mandatory/
Optional | Used in command: | | | | | +| Completion,
(ct/cmp,
0x000a/0x0005) | M | ADD, NOTIFY | | | | | +| | Event
Parameters | Mandatory/
Optional | Supported
Values: | Provisioned Value: | | | +| | None | - | - | - | | | +| | ObservedEvent
Parameters | Mandatory/
Optional | Supported
Values: | Provisioned Value: | | | +| | Result (res,0x0008) | M | success, failure | Not Applicable | | | +| Statistics | Mandatory/
Optional | Used in command: | | Supported Values: | | | +| None | - | - | | - | | | +| Error Codes | Mandatory/ Optional | | | | | | +| None | - | | | | | | + +## C.14.8 TDM Circuit Package + +Table C.14.8: Package Usage Information For TDM Circuit Package + +| Properties | Mandatory/ Optional | Used in command: | Supported Values: | Provisioned Value: | | | +|-------------------------------------------|--------------------------|---------------------|-------------------|-----------------------------|--|--| +| Echo Cancellation (tdmc/ec,0x000d/0x0008) | M | ADD, MOD, MOVE | ALL | Default=off (False) | | | +| Gain Control (tdmc/gain,0x000d/0x000a) | Not Used | - | - | - | | | +| Signals | Mandatory/ Optional | Used in command: | | Duration Provisioned Value: | | | +| None | - | - | | - | | | +| | Signal Parameters | Mandatory/ Optional | Supported Values: | Duration Provisioned Value: | | | +| | - | - | - | - | | | +| Events | Mandatory/ Optional | Used in command: | | | | | +| None | - | - | | | | | +| | Event Parameters | Mandatory/ Optional | Supported Values: | Provisioned Value: | | | +| | - | - | - | - | | | +| | ObservedEvent Parameters | Mandatory/ Optional | Supported Values: | Provisioned Value: | | | +| | - | - | - | - | | | +| Statistics | Mandatory/ Optional | Used in command: | | Supported Values: | | | +| None | - | - | | - | | | +| Error Codes | Mandatory/ Optional | | | | | | +| None | - | | | | | | + +## C.14.9 Text Telephony Package + +**Table C.14.9: Package Usage Information For Text Telephony Package** + +| Properties | Mandatory/Optional | Used in command: | Supported Values: | Provisioned Value: | | | +|---------------------------------------------------------------------------|--------------------------------------|------------------------|---------------------|-----------------------------|--|--| +| Conversation mode
(txp/convmode,
0x0010/0x0001) | O | ADD, MOD, MOVE | ALL | None | | | +| Communication Mode
(txp/commode,
0x0010/0x0002) | O | ADD, MOD, MOVE | ALL | None | | | +| Connection Mode
(txp/connmode,
0x0010/0x0003) | O | ADD, MOD, MOVE | ALL | None | | | +| Action at Loss of
Connection
(txp/lossconnection,
0x0010/0x0006) | O | ADD, MOD, MOVE | ALL | None | | | +| V18 Options
(txp/v18opt,
0x0010/0x0007) | O | ADD, MOD, MOVE | ALL | None | | | +| Character Set
(txp/characterset,
0x0010/0x0008) | O | ADD, MOD, MOVE | ALL | None | | | +| Signals | Mandatory/Optional | Used in command: | | Duration Provisioned Value: | | | +| None | - | - | | - | | | +| | Signal Parameters | Mandatory/Optional | Supported Values: | Duration Provisioned Value: | | | +| | - | - | | - | | | +| Events | Mandatory/Optional | Used in command: | | | | | +| Connection Mode Changed
(txp/connchg,
0x0010/0x0001) | O | ADD, MOD, MOVE, NOTIFY | | | | | +| | Event Parameters | Mandatory/Optional | Supported Values: | Provisioned Value: | | | +| | None | - | | - | | | +| | ObservedEvent Parameters | Mandatory/Optional | Supported Values: | Provisioned Value: | | | +| | Communication Mode (commode, 0x0002) | O | As property commode | - | | | +| Statistics | Mandatory/Optional | Used in command: | | Supported Values: | | | +| Number of Characters Transferred
(txp/chartrans,
0x0010/0x0001) | O | SUBTRACT | | | | | +| Number of Alternating Turns
(txp/altturns,
0x0010/0x0002) | O | SUBTRACT | | | | | +| Error Codes | Mandatory/ Optional | | | | | | +| None | - | | | | | | + +## C.14.10 Call Discrimination Package + +Table C.14.10: Package Usage Information For Call Discrimination Package + +| Properties | Mandatory/
Optional | Used in
command: | Supported
Values: | Provisioned
Value: | +|-----------------------------------------------------------------------------------|------------------------------------------------------|------------------------|----------------------|-----------------------------------| +| Call Types (ctyp/calltyp, 0x0011/0x0001) | O | ADD, MOD, MOVE | ALL | None | +| Text Call Types (ctyp/ttyp, 0x0011/0x0002) | O | ADD, MOD, MOVE | ALL | None | +| V8bis Support (ctyp/v8bsup, 0x0011/0x0003) | O | ADD, MOD, MOVE | ALL | None | +| Probe Message (ctyp/probmsg, 0x0011/0x0004) | O | ADD, MOD, MOVE | ALL | None | +| Probe Order (ctyp/probeorder, 0x0011/0x0005) | O | ADD, MOD, MOVE | ALL | None | +| Phase Reversal Detect (ctyp/phrevdet, 0x0011/0x0006) | O | ADD, MOD, MOVE | ALL | None | +| MG Responsible for Call Discrimination Signalling (ctyp/MGCallSig, 0x0011/0x0007) | O | ADD, MOD, MOVE | ALL | None | +| Signals | Mandatory/
Optional | Used in command: | | Duration
Provisioned
Value: | +| V8 Signal (ctyp/v8sig, 0x0011/0x0001) | O | MOD | | - | +| | Signal Parameters | Mandatory/
Optional | Supported
Values: | Duration
Provisioned
Value: | +| | V.8 Signal Type (ctyp/v8styp, 0x0011/0x0001) | O | ALL | - | +| | V8Sig Cont (ctyp/v8scont, 0x0011/0x0002) | O | ALL | - | +| | V18 XCI Enable (ctyp/v18xcien, 0x0011/0x0003) | O | ALL | - | +| Answer Signal (ctyp/ans, 0x0011/0x0002) | O | MOD | | - | +| | Signal Parameters | Mandatory/
Optional | Supported
Values: | Duration
Provisioned
Value: | +| | ANS Type (ctyp/AnsType, 0x0011/0x0001) | O | ALL | - | +| Calling Signal (ctyp/callsig, 0x0011/0x0003) | O | MOD | | - | +| | Signal Parameters | Mandatory/
Optional | Supported
Values: | Duration
Provisioned
Value: | +| | Call Signal Name (ctyp/csn, 0x0011/0x0001) | O | ALL | - | +| V8bis Signal | O | MOD | | - | +| | Signal Parameters | Mandatory/
Optional | Supported
Values: | Duration
Provisioned
Value: | +| | V8bisSigname (ctyp/V8bsn, 0x0011/0x0001) | O | ALL | - | +| | V8bis Signal Contents (ctyp/V8bscont, 0x0011/0x0002) | O | ALL | - | +| V18 Probe (ctyp/v18prob, 0x0011/0x0005) | O | MOD | | - | +| | Signal Parameters | Mandatory/
Optional | Supported
Values: | Duration
Provisioned
Value: | +| | None | - | - | - | + +| Events | Mandatory/
Optional | Used in command: | | | | | +|---------------------------------------------------------------------|------------------------------------------------|------------------------|----------------------|-----------------------|--|--| +| Discriminating Tone Detected
(ctyp/dtone, 0x0011/0x0001) | O | ADD, MOD, NOTIFY | | | | | +| | Event
Parameters | Mandatory/
Optional | Supported
Values: | Provisioned
Value: | | | +| | None | - | - | - | | | +| | ObservedEvent
Parameters | Mandatory/
Optional | Supported
Values: | Provisioned
Value: | | | +| | Discriminating Tone Type
(dtt,0x0001) | O | ALL | - | | | +| | Discriminating Tone Value
(dtvalue, 0x0002) | O | ALL | - | | | +| | V8bis Type (v8bist,
0x0003) | O | ALL | - | | | +| Call Type Discrimination Result
(ctyp/calldisres, 0x0011/0x0002) | O | ADD, MOD, NOTIFY | | | | | +| | Event
Parameters | Mandatory/
Optional | Supported
Values: | Provisioned
Value: | | | +| | None | - | - | - | | | +| | ObservedEvent
Parameters | Mandatory/
Optional | Supported
Values: | Provisioned
Value: | | | +| | Discriminated Call Type
(dct,0x0001) | O | ALL | - | | | +| Statistics | Mandatory/
Optional | Used in command: | | Supported
Values: | | | +| None | - | - | | - | | | +| Error Codes | Mandatory/ Optional | | | | | | +| None | - | | | | | | + +## C.14.11 Announcement Package + +Table C.14.11: Package Usage Information For Announcement Package + +| Properties | Mandatory/ Optional | Used in command: | Supported Values: | Provisioned Value: | | | +|----------------------------------------------------|--------------------------------------------------|----------------------------|--------------------------|------------------------------------|--|--| +| None | - | - | - | - | | | +| Signals | Mandatory/ Optional | Used in command: | | Duration Provisioned Value: | | | +| Fixed Announcement Play (an/apf, 0x001d/0x0001) | M | ADD, MOD, MOVE | | Signal Parameters | Mandatory/ Optional | Supported Values: | Duration Provisioned Value: | | | +| | Announcement name (an,0x0001) | M | enumeration | Not Applicable | | | +| | Number Of Cycles (noc,0x0002) | M | Any Integer | - | | | +| | Announcement Variant (av,0x0003) | O | string | - | | | +| | Announcement Direction (di,0x0004) | M | Internal, External | Default=External | | | +| Variable Announcement Play (an/apv, 0x001d/0x0002) | O | ADD, MOD, MOVE | | | | | +| | Signal Parameters | Mandatory/ Optional | Supported Values: | Duration Provisioned Value: | | | +| | Announcement name (an,0x0001) | M | enumeration | Not Applicable | | | +| | Number Of Cycles (noc,0x0002) | M | Any Integer | - | | | +| | Announcement Variant (av,0x0003) | O | string | - | | | +| | Number (num,0x0004) | O | integer | - | | | +| | Specific parameters interpretation (spi, 0x0005) | O | enumeration | - | | | +| | Specific parameters (sp,0x0006) | O | string | - | | | +| | Announcement Direction (di,0x0006) | M | Internal, External | Default=External | | | +| Events | Mandatory/ Optional | Used in command: | | | | | +| None | - | - | | | | | +| | Event Parameters | Mandatory/ Optional | Supported Values: | Provisioned Value: | | | +| | - | - | - | - | | | +| | ObservedEvent Parameters | Mandatory/ Optional | Supported Values: | Provisioned Value: | | | +| | - | - | - | - | | | +| Statistics | Mandatory/ Optional | Used in command: | | Supported Values: | | | +| None | - | - | | - | | | +| Error Codes | Mandatory/ Optional | | | | | | +| None | - | | | | | | + +## C.14.12 Media Gateway Resource Congestion handling Package + +Table C.14.12: Package Usage Information For Media Gateway Resource Congestion handling Package + +| Properties | Mandatory/ Optional | Used in command: | Supported Values: | Provisioned Value: | +|----------------------------------|---------------------------------|----------------------------|--------------------------|------------------------------------| +| None | - | - | - | - | +| Signals | Mandatory/ Optional | Used in command: | | Duration Provisioned Value: | +| None | - | - | - | - | +| | Signal Parameters | Mandatory/ Optional | Supported Values: | Duration Provisioned Value: | +| | - | - | - | - | +| Events | Mandatory/ Optional | Used in command: | | | +| MGCon (chp/mgcon, 0x0029/0x0001) | M | MOD, NOTIFY | | | +| | Event Parameters | Mandatory/ Optional | Supported Values: | Provisioned Value: | +| | None | - | - | - | +| | ObservedEvent Parameters | Mandatory/ Optional | Supported Values: | Provisioned Value: | +| | Reduction (reduction, 0x0001) | M | 0-100 | Not Applicable | +| Statistics | Mandatory/ Optional | Used in command: | | Supported Values: | +| None | - | - | - | - | +| Error Codes | Mandatory/ Optional | | | | +| None | - | | | | + +## C.14.13 Hanging Termination Detection Package + +Table C.14.13: Package Usage Information For Hanging Termination Detection Package + +| Properties | Mandatory/ Optional | Used in command: | Supported Values: | Provisioned Value: | +|-----------------------------------------------------|---------------------------------|------------------------------------|--------------------------|------------------------------------| +| None | - | - | - | - | +| Signals | Mandatory/ Optional | Used in command: | | Duration Provisioned Value: | +| None | - | - | - | - | +| | Signal Parameters | Mandatory/ Optional | Supported Values: | Duration Provisioned Value: | +| | - | - | - | - | +| Events | Mandatory/ Optional | Used in command: | | | +| Termination Heartbeat (hangterm/thb, 0x0098/0x0001) | M | ADD, MOD, MOVE, AUDITVALUE, NOTIFY | | | +| | Event Parameters | Mandatory/ Optional | Supported Values: | Provisioned Value: | +| | Timer X (timerx, 0x0001) | M | ALL | 0 (no heartbeat message) | +| | ObservedEvent Parameters | Mandatory/ Optional | Supported Values: | Provisioned Value: | +| | None | - | - | - | +| Statistics | Mandatory/ Optional | Used in command: | | Supported Values: | +| None | - | - | - | - | +| Error Codes | Mandatory/ Optional | | | | +| None | - | | | | + +## C.14.14 Bearer Characteristics Package + +**Table C.14.14: Package Usage Information For Bearer Characteristics Package** + +| Properties | Mandatory/ Optional | Used in command: | Supported Values: | Provisioned Value: | | | +|--------------------------------------------------|---------------------------------|----------------------------|--------------------------|------------------------------------|--|--| +| BNC Characteristics
(BCP/BNCChar,0x001e/0x01) | M | ADD | AAL type 2 /
IP/RTP | Not Applicable | | | +| Signals | Mandatory/ Optional | Used in command: | | Duration Provisioned Value: | | | +| None | - | - | | - | | | +| | Signal Parameters | Mandatory/ Optional | Supported Values: | Duration Provisioned Value: | | | +| | - | - | - | - | | | +| Events | Mandatory/ Optional | Used in command: | | | | | +| None | - | - | | | | | +| | Event Parameters | Mandatory/ Optional | Supported Values: | Provisioned Value: | | | +| | - | - | - | - | | | +| | ObservedEvent Parameters | Mandatory/ Optional | Supported Values: | Provisioned Value: | | | +| | - | - | - | - | | | +| Statistics | Mandatory/ Optional | Used in command: | | Supported Values: | | | +| None | - | - | | - | | | +| Error Codes | Mandatory/ Optional | | | | | | +| None | - | | | | | | + +## C.14.15 Generic Bearer Connection Package + +**Table C.14.15: Package Usage Information For Generic Bearer Connection Package** + +| Properties | Mandatory/ Optional | Used in command: | Supported Values: | Provisioned Value: | +|-------------------------------------------|--------------------------------------|----------------------------|--------------------------------------------------------------------------------------------------------------------------------|------------------------------------| +| None | - | - | - | - | +| Signals | Mandatory/ Optional | Used in command: | | Duration Provisioned Value: | +| Establish BNC
(GB/EstBNC, 0x0021/0x01) | M | | ADD, MOD | Not Applicable | +| | Signal Parameters | Mandatory/ Optional | Supported Values: | Duration Provisioned Value: | +| | Not Applicable | - | - | Not Applicable | +| Modify BNC
(GB/ModBNC, 0x0021/0x02) | O | | MOD | Not Applicable | +| | Signal Parameters | Mandatory/ Optional | Supported Values: | Duration Provisioned Value: | +| | Not Applicable | - | - | Not Applicable | +| Release BNC
(GB/RelBNC, 0x0021/0x03) | M (NOTE) | | MOD | Not Applicable | +| | Signal Parameters | Mandatory/ Optional | Supported Values: | Duration Provisioned Value: | +| | General cause
(Generalcause,0x01) | O | Normal Release/
Unavailable
Resources/ Failure
Temporary/ Failure
Permanent/
Interworking Error/
Unsupported | Not Applicable | +| | Failure Cause
(Failurecause,0x02) | O | OCTET STRING | Not Applicable | +| | Reset (Reset,0x03) | O | 0/ 1 | Not Applicable | +| Events | Mandatory/ Optional | Used in command: | | | +| BNC Change
(GB/BNCChange, 0x0021/0x01) | M | | ADD, MOD, NOTIFY | | +| | Event Parameters | Mandatory/ Optional | Supported Values: | Provisioned Value: | +| | Type (Type ,0x01) | M | Bearer Established /
Bearer Modified/
Bearer Modification
Failure | Not Applicable | +| | ObservedEvent Parameters | Mandatory/ Optional | Supported Values: | Provisioned Value: | +| | Type (Type,0x01) | M | Bearer Established /
Bearer Modified/
Bearer Modification
Failure | Not Applicable | +| Statistics | Mandatory/ Optional | Used in command: | | Supported Values: | +| None | - | | - | - | +| Error Codes | Mandatory/ Optional | | | | +| None | - | | | | + +NOTE: Mandatory for BICC ATM Terminations. If received as part of a wildcarded command including other types of terminations then for other type of terminations no action is required from MGW, but a successful command reply. + +## C.14.16 Bearer Control Tunnelling Package + +Table C.14.16: Package Usage Information For Bearer Control Tunnelling Package + +| Properties | Mandatory/Optional | Used in command: | Supported Values: | Provisioned Value: | | | +|----------------------------------------------------|------------------------------------------|---------------------------|--------------------------|------------------------------------|--|--| +| Tunneling Options (BT/TunOpt, 0x0022/0x01) | M | ADD | 1 /2 | Not Applicable | | | +| Signals | Mandatory/Optional | Used in command: | | Duration Provisioned Value: | | | +| Bearer Information Transport (BT/BIT, 0x0022/0x01) | M | ADD, MOD | | Not Applicable | | | +| | Signal Parameters | Mandatory/Optional | Supported Values: | Duration Provisioned Value: | | | +| | Bearer Information Tunnel (BIT, 0x01) | M | Octet String | Not Applicable | | | +| Events | Mandatory/Optional | Used in command: | | | | | +| Tunnel Indication (BT/TIND, 0x0022/0x01) | M | ADD, MOD, NOTIFY | | | | | +| | Event Parameters | Mandatory/Optional | Supported Values: | Provisioned Value: | | | +| | Not applicable | - | - | - | | | +| | ObservedEvent Parameters | Mandatory/Optional | Supported Values: | Provisioned Value: | | | +| | Bearer Information transport (BIT, 0x01) | M | Octet String | Not Applicable | | | +| Statistics | Mandatory/Optional | Used in command: | | Supported Values: | | | +| None | - | - | | - | | | +| Error Codes | Mandatory/ Optional | | | | | | +| None | - | | | | | | + +## C.14.17 Basic Call Progress Tones Generator with Directionality + +**Table C.14.17: Package Usage Information For Basic Call Progress Tones Generator with Directionality Package** + +| Properties | Mandatory/Optional | Used in command: | Supported Values: | Provisioned Value: | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------|---------------------------|--------------------------|------------------------------------|--|--| +| None | - | - | - | - | | | +| Signals | Mandatory/Optional | Used in command: | | Duration Provisioned Value: | | | +| Dial Tone (bcg/bdt, 0x0023/0x0040)
Ringing Tone (bcg/brt, 0x0023/0x0041)
Busy Tone (bcg/bbt, 0x0023/0x0042)
Congestion Tone (bcg/bct, 0x0023/0x0043)
Special Information Tone (bcg/bsit, 0x0023/0x0044)
Warning Tone (bcg/bwt, 0x0023/0x0045)
Payphone Recognition Tone (bcg/bpt, 0x0023/0x0046)
Call Waiting Tone (bcg/bcw, 0x0023/0x0047)
Caller Waiting Tone (bcg/bcr, 0x0023/0x0048)
Pay Tone (bcg/bpy, 0x0023/0x0049) | O | ADD, MOD, MOVE | | Value | | | +| | Signal Parameters | Mandatory/Optional | Supported Values: | Duration Provisioned Value: | | | +| | Tone Direction (btd, 0x0001) | M | Internal / External | Default=External | | | +| Events | Mandatory/Optional | Used in command: | | | | | +| None | - | - | | | | | +| | Event Parameters | Mandatory/Optional | Supported Values: | Provisioned Value: | | | +| | - | - | - | - | | | +| | ObservedEvent Parameters | Mandatory/Optional | Supported Values: | Provisioned Value: | | | +| Statistics | Mandatory/Optional | Used in command: | | Supported Values: | | | +| None | - | - | | - | | | +| Error Codes | Mandatory/ Optional | | | | | | +| None | - | | | | | | + +## C.14.18 Expanded Call Progress Tones Generator Package + +**Table C.14.18: Package Usage Information For Expanded Call Progress Tones Generator Package** + +| Properties | Mandatory/ Optional | Used in command: | Supported Values: | Provisioned Value: | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------|----------------------------|--------------------------|------------------------------------|--|--| +| None | - | - | - | - | | | +| Signals | Mandatory/ Optional | Used in command: | | Duration Provisioned Value: | | | +| Comfort Tone (xcg/cmft, 0x0024/0x004a)
Off-hook warning Tone (xcg/roh, 0x0024/0x004b)
Negative Acknowledgement (xcg/nack, 0x0024/0x004c)
Vacant Number Tone (xcg/vac, 0x0024/0x004d)
Special Conditions Dial Tone (xcg/spec, 0x0024/0x004e) | O | ADD, MOD, MOVE | | Value | | | +| | Signal Parameters | Mandatory/ Optional | Supported Values: | Duration Provisioned Value: | | | +| | Tone Direction (btd, 0x0001) | M | Internal / External | Default=External | | | +| Events | Mandatory/ Optional | Used in command: | | | | | +| None | - | - | | | | | +| | Event Parameters | Mandatory/ Optional | Supported Values: | Provisioned Value: | | | +| | - | - | - | - | | | +| | ObservedEvent Parameters | Mandatory/ Optional | Supported Values: | Provisioned Value: | | | +| | - | - | - | - | | | +| Statistics | Mandatory/ Optional | Used in command: | | Supported Values: | | | +| None | - | - | | - | | | +| Error Codes | Mandatory/ Optional | | | | | | +| None | - | | | | | | + +## C.14.19 Basic Services Tones Generation Package + +Table C.14.19: Package Usage Information For Basic Services Tones Generation Package + +| Properties | Mandatory/ Optional | Used in command: | Supported Values: | Provisioned Value: | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------|----------------------------|--------------------------|------------------------------------|--|--| +| None | - | - | - | - | | | +| Signals | Mandatory/ Optional | Used in command: | | Duration Provisioned Value: | | | +| Recall Dial Tone
(srvtn/rdt,0x0025/0x004f)
Confirmation Tone
(srvtn/conf,0x0025/0x0050)
Held Tone
(srvtn/ht,0x0025/0x0051)
Message Waiting Tone
(srvtn/mwt,0x0025/0x0052) | O | ADD, MOD, MOVE | | Value | | | +| | Signal Parameters | Mandatory/ Optional | Supported Values: | Duration Provisioned Value: | | | +| | Tone Direction
(btd, 0x0001) | M | Internal / External | Default=External | | | +| Events | Mandatory/ Optional | Used in command: | | | | | +| None | - | - | | | | | +| | Event Parameters | Mandatory/ Optional | Supported Values: | Provisioned Value: | | | +| | - | - | - | - | | | +| | ObservedEvent Parameters | Mandatory/ Optional | Supported Values: | Provisioned Value: | | | +| | - | - | - | - | | | +| Statistics | Mandatory/ Optional | Used in command: | | Supported Values: | | | +| None | - | - | | - | | | +| Error Codes | Mandatory/ Optional | | | | | | +| None | - | | | | | | + +## C.14.20 Expanded Services Tones Generation Package + +Table C.14.20: Package Usage Information For Expanded Services Tones Generation Package + +| Properties | Mandatory/ Optional | Used in command: | Supported Values: | Provisioned Value: | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------|----------------------------|--------------------------|------------------------------------|--|--| +| None | - | - | - | - | | | +| Signals | Mandatory/ Optional | Used in command: | | Duration Provisioned Value: | | | +| Call Transfer Dial Tone (xsrvtm/xferdt,0x0026/0x0053)
Call Forward Tone (xsrvtm/cft,0x0026/0x0054)
Credit Card service Tone (xsrvtm/ccst,0x0026/0x0055)
Special Recall Dial Tone (xsrvtm/srdt,0x0026/0x0056) | O | ADD, MOD, MOVE | | Value | | | +| | Signal Parameters | Mandatory/ Optional | Supported Values: | Duration Provisioned Value: | | | +| | Tone Direction (btd, 0x0001) | M | Internal / External | Default=External | | | +| Events | Mandatory/ Optional | Used in command: | | | | | +| None | - | - | | | | | +| | Event Parameters | Mandatory/ Optional | Supported Values: | Provisioned Value: | | | +| | - | - | - | - | | | +| | ObservedEvent Parameters | Mandatory/ Optional | Supported Values: | Provisioned Value: | | | +| Statistics | Mandatory/ Optional | Used in command: | | Supported Values: | | | +| None | - | - | | - | | | +| Error Codes | Mandatory/ Optional | | | | | | +| None | - | | | | | | + +## C.14.21 Intrusion Tones Generation Package + +Table C.14.21: Package Usage Information For Intrusion Tones Generation Package + +| Properties | Mandatory/ Optional | Used in command: | Supported Values: | Provisioned Value: | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------|----------------------------|--------------------------|------------------------------------|--|--| +| None | - | - | - | - | | | +| Signals | Mandatory/ Optional | Used in command: | | Duration Provisioned Value: | | | +| Intrusion Pending Tone (int/pend,0x0027/0x0057)
Intrusion Tone (int/int,0x0027/0x0058)
Intrusion Reminder Tone (int/rem,0x0027/0x0059)
Toll Break-In Tone (int/tbi,0x0027/0x005a)
Intrusion Queue Tone (int/intque,0x0027/0x005b)
Busy Verification Tone (int/bv,0x0027/0x005c) | O | ADD, MOD, MOVE | | Value | | | +| | Signal Parameters | Mandatory/ Optional | Supported Values: | Duration Provisioned Value: | | | +| | Tone Direction (btd, 0x0001) | M | Internal / External | Default=External | | | +| Events | Mandatory/ Optional | Used in command: | | | | | +| None | - | - | | | | | +| | Event Parameters | Mandatory/ Optional | Supported Values: | Provisioned Value: | | | +| | - | - | - | - | | | +| | ObservedEvent Parameters | Mandatory/ Optional | Supported Values: | Provisioned Value: | | | +| | - | - | - | - | | | +| Statistics | Mandatory/ Optional | Used in command: | | Supported Values: | | | +| None | - | - | | - | | | +| Error Codes | Mandatory/ Optional | | | | | | +| None | - | | | | | | + +## C.14.22 Business Tones Generation Package + +**Table C.14.22: Package Usage Information For Business Tones Generation Package** + +| Properties | Mandatory/Optional | Used in command: | Supported Values: | Provisioned Value: | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------|---------------------------|--------------------------|------------------------------------|--|--| +| None | - | - | - | - | | | +| Signals | Mandatory/Optional | Used in command: | | Duration Provisioned Value: | | | +| Off-Hook Queuing Tone (biztn/ofque,0x0028/0x005d)
Expensive Route Warning Tone (biztn/erwt,0x0028/0x005e)
Distinctive Dial Tone (biztn/ddt,0x0028/0x005f)
Internal Dial Tone (biztn/idt,0x0028/0x0060) | O | ADD, MOD, MOVE | | Value | | | +| | Signal Parameters | Mandatory/Optional | Supported Values: | Duration Provisioned Value: | | | +| | Tone Direction (btd, 0x0001) | M | Internal / External | Default=External | | | +| Events | Mandatory/Optional | Used in command: | | | | | +| None | - | - | | | | | +| | Event Parameters | Mandatory/Optional | Supported Values: | Provisioned Value: | | | +| | - | - | - | - | | | +| | ObservedEvent Parameters | Mandatory/Optional | Supported Values: | Provisioned Value: | | | +| | - | - | - | - | | | +| Statistics | Mandatory/Optional | Used in command: | | Supported Values: | | | +| None | - | - | | - | | | +| Error Codes | Mandatory/ Optional | | | | | | +| None | - | | | | | | + +## C.14.23 3GUP Package + +Table C.14.23: Package Usage Information For 3GUP Package + +| Properties | Mandatory/Optional | Used in command: | Supported Values: | Provisioned Value: | | | +|-------------------------------------------------------------------|--------------------------|--------------------|-------------------|-----------------------------|--|--| +| UP Mode of operation
(threegup/mode, 0x002f/0x0001) | M | ADD, MOD, MOVE | ALL | Default=1 (transparent) | | | +| UP versions
(threegup/upversions, 0x002f/0x0002) | M | ADD, MOD, MOVE | 1, 2 | Default = 1 | | | +| Delivery of erroneous SDUs
(threegup/delerrsdu, 0x002f/0x0003) | M | ADD, MOD, MOVE | ALL | Default = 3 (NA) | | | +| Interface
(threegup/interface, 0x002f/0x0004) | M | ADD, MOD, MOVE | ALL | None | | | +| Initialisation Direction
(threegup/initdir, 0x002f/0x0005) | M | ADD, MOD, MOVE | ALL | None | | | +| Signals | Mandatory/Optional | Used in command: | | Duration Provisioned Value: | | | +| None | - | - | | - | | | +| | Signal Parameters | Mandatory/Optional | Supported Values: | Duration Provisioned Value: | | | +| | - | - | - | - | | | +| Events | Mandatory/Optional | Used in command: | | | | | +| None | - | - | | | | | +| | Event Parameters | Mandatory/Optional | Supported Values: | Provisioned Value: | | | +| | - | - | - | - | | | +| | ObservedEvent Parameters | Mandatory/Optional | Supported Values: | Provisioned Value: | | | +| | - | - | - | - | | | +| Statistics | Mandatory/Optional | Used in command: | | Supported Values: | | | +| None | - | - | | - | | | +| Error Codes | Mandatory/ Optional | | | | | | +| None | - | | | | | | + +## C.14.24 Modification of Link Characteristics Bearer Capability + +Table C.14.24: Package Usage Information For Modification of Link Characteristics Package + +| Properties | Mandatory/Optional | Used in command: | Supported Values: | Provisioned Value: | +|-----------------------------------------------------------------------------|---------------------------------|---------------------------|--------------------------|------------------------------------| +| None | - | - | - | - | +| Signals | Mandatory/Optional | Used in command: | | Duration Provisioned Value: | +| None | - | - | - | - | +| | Signal Parameters | Mandatory/Optional | Supported Values: | Duration Provisioned Value: | +| | - | - | - | - | +| Events | Mandatory/Optional | Used in command: | | | +| Bearer Modification Support Event. (threegmlc/mod_link_supp, 0x0046/0x0001) | M | ADD, MOD, MOVE NOTIFY | | | +| | Event Parameters | Mandatory/Optional | Supported Values: | Provisioned Value: | +| | None | - | - | - | +| | ObservedEvent Parameters | Mandatory/Optional | Supported Values: | Provisioned Value: | +| Statistics | None | - | - | - | +| | Mandatory/Optional | Used in command: | | Supported Values: | +| None | - | - | - | - | +| Error Codes | Mandatory/ Optional | | | | +| None | - | | | | + +## C.14.25 TFO package + +Table C.14.25: Package Usage Information For TFO + +| Properties | Mandatory/Optional | Used in command: | Supported Values: | Provisioned Value: | | | +|--------------------------------------------------------------------|--------------------------|------------------------|----------------------------|-----------------------------|--|--| +| TFO Activity Control (threegtfoc /tfoenable, (0x0031/0x0001)) | M | ADD, MOD, MOVE | ALL | None (default =Off) | | | +| TFO Codec List (threegtfoc /codeclist, (0x0031/0x0002)) | M | ADD, MOD, MOVE | See 3GPP TS 29.232 §15.2.2 | None | | | +| Signals | Mandatory/Optional | Used in command: | | Duration Provisioned Value: | | | +| None | - | - | | - | | | +| | Signal Parameters | Mandatory/Optional | Supported Values: | Duration Provisioned Value: | | | +| | - | - | - | - | | | +| Events | Mandatory/Optional | Used in command: | | | | | +| Optimal Codec Event (threegtfoc /codec_modify, (0x0031/0x0010)) | O | ADD, MOD, MOVE, NOTIFY | | | | | +| | Event Parameters | Mandatory/Optional | Supported Values: | Provisioned Value: | | | +| | None | | | | | | +| | ObservedEvent Parameters | Mandatory/Optional | Supported Values: | Provisioned Value: | | | +| Codec List Event (threegtfoc /distant_codec_list, (0x0031/0x0012)) | O | ADD, MOD, MOVE, NOTIFY | | | | | +| | Event Parameters | Mandatory/Optional | Supported Values: | Provisioned Value: | | | +| | None | | | | | | +| | ObservedEvent Parameters | Mandatory/Optional | Supported Values: | Provisioned Value: | | | +| TFO Status Event (threegtfoc /TFO_status) (0x0031/0x0014) | O | ADD, MOD, MOVE, NOTIFY | | | | | +| | Event Parameters | Mandatory/Optional | Supported Values: | Provisioned Value: | | | +| | None | - | - | - | | | +| | ObservedEvent Parameters | Mandatory/Optional | Supported Values: | Provisioned Value: | | | +| Statistics | Mandatory/Optional | Used in command: | | Supported Values: | | | +| | None | - | | - | | | +| Error Codes | Mandatory/ Optional | | | | | | +| | - | | | | | | + +## C.14.26 Circuit Switched Data package + +Table C.14.26: Package Usage Information For CSD + +| Properties | Mandatory/Optional | Used in command: | Supported Values: | Provisioned Value: | | | +|--------------------------------------------------------------------|------------------------------------|--------------------|----------------------------------------------------------------------------------------------------------|-----------------------------|--|--| +| PLMNBC (threeegcsd /plmnb, 0x0030/0x0001) | M | ADD, MOD, MOVE | Specified in the subclause "Bearer capability" in 3GPP TS 24.008 [3]. | None | | | +| GSM Channel Coding (threeegcsd / gsmchancod, 0x0030/0x0002) | M | ADD, MOD, MOVE | The second octet of Chosen Channel as specified in the subclause "Chosen Channel" in 3GPP TS 48.008 [9]. | None | | | +| Signals | Mandatory/Optional | Used in command: | | Duration Provisioned Value: | | | +| Activate Protocol (threeegcsd/ actprot, 0x0030/0x0001) | M | MOD | | - | | | +| | Signal Parameters | Mandatory/Optional | Supported Values: | Duration Provisioned Value: | | | +| | Local Peer Role (Localpeer 0x0001) | O | ALL | None | | | +| Events | Mandatory/Optional | Used in command: | | | | | +| Protocol Negotiation Result (threeegcsd / protres, (0x0030/0x0001) | M | ADD, MOD, NOTIFY | | | | | +| | Event Parameters | Mandatory/Optional | Supported Values: | Provisioned Value: | | | +| | None | - | - | - | | | +| | ObservedEvent Parameters | Mandatory/Optional | Supported Values: | Provisioned Value: | | | +| | Negotiation Result (result 0x0001) | M | ALL | None | | | +| Rate Change (threeegcsd / ratechg, (0x0030/0x0002) | M | ADD, MOD, NOTIFY | | | | | +| | Event Parameters | Mandatory/Optional | Supported Values: | Provisioned Value: | | | +| | None | - | - | - | | | +| | ObservedEvent Parameters | Mandatory/Optional | Supported Values: | Provisioned Value: | | | +| | New Rate (rate 0x0001) | M | 2400, 4800, 9600, 14400, 28800, 57600 | None | | | +| Statistics | Mandatory/Optional | Used in command: | | Supported Values: | | | +| None | - | - | | - | | | +| Error Codes | Mandatory/ Optional | | | | | | +| None | - | | | | | | + +## C.14.27 Enhanced Circuit Switched Data package + +Table C.14.27: Package Usage Information For Enhanced CSD + +| Properties | Mandatory/ Optional | Used in command: | Supported Values: | Provisioned Value: | | | +|------------------------------------------------|---------------------------------|----------------------------|----------------------------------------------|------------------------------------|--|--| +| Bitrate (threeegcsden /bitrate, 0x0082/0x0003) | M | ADD, MOD, MOVE | 2400, 4800, 9600, 14400, 28800, 57600, 64000 | None | | | +| Signals | Mandatory/ Optional | Used in command: | | Duration Provisioned Value: | | | +| None | - | - | | - | | | +| | Signal Parameters | Mandatory/ Optional | Supported Values: | Duration Provisioned Value: | | | +| | - | - | - | - | | | +| Events | Mandatory/ Optional | Used in command: | | | | | +| None | - | - | | | | | +| | Event Parameters | Mandatory/ Optional | Supported Values: | Provisioned Value: | | | +| | - | - | - | - | | | +| | ObservedEvent Parameters | Mandatory/ Optional | Supported Values: | Provisioned Value: | | | +| | - | - | - | - | | | +| Statistics | Mandatory/ Optional | Used in command: | | Supported Values: | | | +| None | - | - | | - | | | +| Error Codes | Mandatory/ Optional | | | | | | +| None | - | | | | | | + +## C.14.28 3G Expanded Call Progress Tones package + +Table C.14.28: Package Usage Information For 3G Expanded Call Progress Tones + +| Properties | Mandatory/ Optional | Used in command: | Supported Values: | Provisioned Value: | | | +|-------------------------------------------------------------|---------------------------------|----------------------------|--------------------------|------------------------------------|--|--| +| None | | | | | | | +| Signals | Mandatory/ Optional | Used in command: | | Duration Provisioned Value: | | | +| CAMEL Prepaid Warning Tone (threeegxcg/cpwt, 0x0032/0x004f) | M | ADD, MOD, MOVE | | - | | | +| | Signal Parameters | Mandatory/ Optional | Supported Values: | Duration Provisioned Value: | | | +| | ToneDirection(td, 0x0010) | M | Ext, Int | Default=Ext | | | +| Events | Mandatory/ Optional | Used in command: | | | | | +| None | - | - | | | | | +| | Event Parameters | Mandatory/ Optional | Supported Values: | Provisioned Value: | | | +| | - | - | - | - | | | +| | ObservedEvent Parameters | Mandatory/ Optional | Supported Values: | Provisioned Value: | | | +| | - | - | - | - | | | +| Statistics | Mandatory/ Optional | Used in command: | | Supported Values: | | | +| None | - | - | | - | | | +| Error Codes | Mandatory/ Optional | | | | | | +| None | - | | | | | | + +## C.14.29 Cellular Text Telephone Modem Text Transport Package + +Table C.14.29: Package Usage Information For CTM + +| Properties | Mandatory/Optional | Used in command: | Supported Values: | Provisioned Value: | | | +|------------------------------------------------------------------------|--------------------------|------------------------|-----------------------|-----------------------------|--|--| +| Termination connection state(threeegctm/ connstate, 0x0068/0x0001) | M | ADD, MOD, MOVE | ALL | | | | +| Text Transport (threeegctm/ trpt (0x0068/0x0002 | M | ADD, MOD, MOVE | CTM | | | | +| Text Protocol Version (threeegctm/ textproto 0x0068/0x0003) | M | ADD, MOD, MOVE | ALL | Default=1 | | | +| Signals | Mandatory/Optional | Used in command: | | Duration Provisioned Value: | | | +| None | - | - | | - | | | +| | Signal Parameters | Mandatory/Optional | Supported Values: | Duration Provisioned Value: | | | +| | - | - | -- | - | | | +| Events | Mandatory/Optional | Used in command: | | | | | +| Connection State Change (threeegctm/ connchange 0x0068/0x0001) | M | ADD, MOD, MOVE, NOTIFY | | | | | +| | Event Parameters | Mandatory/Optional | Supported Values: | Provisioned Value: | | | +| | None | - | - | - | | | +| | ObservedEvent Parameters | Mandatory/Optional | Supported Values: | Provisioned Value: | | | +| | Connchng | M | As property connstate | - | | | +| Statistics | Mandatory/Optional | Used in command: | | Supported Values: | | | +| Number of Characters Transferred (threeegctm/ chartrans 0x0068/0x0001) | M | SUB | | | | | +| Error Codes | Mandatory/ Optional | | | | | | +| None | - | | | | | | + +C.14.30 Void + +## C.14.31 Flexible Tone Generator package + +Table C.14.31: Package Usage Information For Flexible Tone Generator + +| Properties | Mandatory/ Optional | Used in command: | Supported Values: | Provisioned Value: | | | +|-----------------------------------------------|-------------------------------------|----------------------------|--------------------------|------------------------------------|--|--| +| None | - | - | - | - | | | +| Signals | Mandatory/ Optional | Used in command: | | Duration Provisioned Value: | | | +| Flexible Tone (threeegflex/ft, 0x0084/0x0050) | M | ADD, MOD, MOVE | | - | | | +| | Signal Parameters | Mandatory/ Optional | Supported Values: | Duration Provisioned Value: | | | +| | Burst list direction(bld, 0x0001) | M | Int, Ext | Default=Ext | | | +| | NumberOfBursts (nob, 0x0002) | M | 1-3 | Default = 1 | | | +| | BurstInterval (bi, 0x0003) | M | 1-1200 | Default = 2 | | | +| | numberOfTonesInBurst (notib 0x0004) | M | 1-3 | Default=3 | | | +| | toneDuration (td 0x0005) | M | 1-20 | Default=2 | | | +| | toneInterval (ti 0x0006) | M | 1-20 | Default=2 | | | +| Events | Mandatory/ Optional | Used in command: | | | | | +| None | - | - | | | | | +| | Event Parameters | Mandatory/ Optional | Supported Values: | Provisioned Value: | | | +| | - | - | - | - | | | +| | ObservedEvent Parameters | Mandatory/ Optional | Supported Values: | Provisioned Value: | | | +| | - | - | - | - | | | +| Statistics | Mandatory/ Optional | Used in command: | | Supported Values: | | | +| None | - | - | | - | | | +| Error Codes | Mandatory/ Optional | | | | | | +| None | - | | | | | | + +## C.14.32 Trace Package + +Table C.14.32: Package Usage Information For Trace Package + +| Properties | Mandatory/Optional | Used in command: | Supported Values: | Provisioned Value: | | | +|---------------------------------------------------------------------------------------|-------------------------------------|--------------------|----------------------------------------------------------------------------|-----------------------------|--|--| +| Trace Activity Control
(calltrace/traceactivityrequest,
0x0097/0x0001) | M | ADD, MOD | Trace Session is activated in MGW /
Trace Session is deactivated in MGW | Not Applicable | | | +| IMSI (calltrace/imsi,
0x0097/0x0002) | M | ADD, MOD | Octet string | Not Applicable | | | +| IMEI(SV) (calltrace/imei_sv,
0x0097/0x0003) | M | ADD, MOD | Octet string | Not Applicable | | | +| Trace Reference
(calltrace/tracereference,
0x0097/0x0004) | M | ADD, MOD | Octet string | Not Applicable | | | +| Trace Recording Session Reference
(calltrace/tracerecsessionref,
0x0097/0x0005) | M | ADD, MOD | Octet string | Not Applicable | | | +| Trace Depth (calltrace/tracedepth,
0x0097/0x0006) | M | ADD, MOD | Octet string | Not Applicable | | | +| Triggering Events
(calltrace/triggeringevent,
0x0097/0x0007) | M | ADD, MOD | Octet string | Not Applicable | | | +| List of interfaces
(calltrace/listofinterfaces,
0x0097/0x0008) | M | ADD, MOD | Octet string | Not Applicable | | | +| Signals | Mandatory/Optional | Used in command: | | Duration Provisioned Value: | | | +| None | - | - | | - | | | +| | Signal Parameters | Mandatory/Optional | Supported Values: | Duration Provisioned Value: | | | +| | - | - | - | - | | | +| Events | Mandatory/Optional | Used in command: | | | | | +| Trace result
(calltrace/tracact,
0x0097/0x0001) | M | ADD, MOD, NOTIFY | | | | | +| | Event Parameters | Mandatory/Optional | Supported Values: | Provisioned Value: | | | +| | None | - | - | - | | | +| | ObservedEvent Parameters | Mandatory/Optional | Supported Values: | Provisioned Value: | | | +| | TraceActivation Result (res,0x0001) | M | Trace Successfully activated/ Failure in trace activation | Not Applicable | | | +| Statistics | Mandatory/Optional | Used in command: | | Supported Values: | | | +| None | - | - | | - | | | +| Error Codes | Mandatory/ Optional | | | | | | +| None | - | | | | | | + +## C.14.33 ASCI Group call + +Table C.14.33: Package usage information for ASCI Group Call package + +| Properties | Mandatory/Optional | Used in command: | Supported Values: | Provisioned Value: | | | +|----------------------------------------------------------------------------------|--------------------------|--------------------|-------------------|-----------------------------|--|--| +| Number of needed conference terminations (threegasci/nct, 0x00b2/0x0001) | M | ADD | upto 32 | None | | | +| Number of desired listener context terminations (threegasci/nlct, 0x00b2/0x0002) | O | ADD | upto 32 | None | | | +| Signals | Mandatory/Optional | Used in command: | | Duration Provisioned Value: | | | +| None | - | - | | - | | | +| | Signal Parameters | Mandatory/Optional | Supported Values: | Duration Provisioned Value: | | | +| | - | - | - | - | | | +| Events | Mandatory/Optional | Used in command: | | | | | +| None | - | - | | | | | +| | Event Parameters | Mandatory/Optional | Supported Values: | Provisioned Value: | | | +| | - | - | - | - | | | +| | ObservedEvent Parameters | Mandatory/Optional | Supported Values: | Provisioned Value: | | | +| | - | - | - | - | | | +| Statistics | Mandatory/Optional | Used in command: | | Supported Values: | | | +| None | - | - | | - | | | +| Error Codes | Mandatory/Optional | | | | | | +| None | - | | | | | | + +## C.14.34 IP domain connection + +Table C.14.34: Package usage information for IP domain connection package + +| Properties | Mandatory/Optional | Used in command: | Supported Values: | Provisioned Value: | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------|---------------------------|--------------------------|------------------------------------|--|--| +| IP Realm Identifier
(ipdc /realm, 0x009d /0x0001) | M | ADD | String | Operator Defined (NOTE) | | | +| Signals | Mandatory/Optional | Used in command: | | Duration Provisioned Value: | | | +| None | - | - | | - | | | +| | Signal Parameters | Mandatory/Optional | Supported Values: | Duration Provisioned Value: | | | +| | - | - | - | - | | | +| Events | Mandatory/Optional | Used in command: | | | | | +| None | - | - | | | | | +| | Event Parameters | Mandatory/Optional | Supported Values: | Provisioned Value: | | | +| | - | - | - | - | | | +| | ObservedEvent Parameters | Mandatory/Optional | Supported Values: | Provisioned Value: | | | +| | - | - | - | - | | | +| Statistics | Mandatory/Optional | Used in command: | | Supported Values: | | | +| None | - | - | | - | | | +| Error Codes | Mandatory/ Optional | | | | | | +| None | - | | | | | | +| NOTE: A default IP realm may be configured such that if the MGW has not received the IP realm identifier and the MGW supports multiple IP realms then the default IP realm shall be used. | | | | | | | + +## C.14.35 Inactivity Timer Package + +Table C.14.35: Package Usage Information for Inactivity Timer package + +| Properties | Mandatory/Optional | Used in command: | Supported Values: | Provisioned Value: | | | +|--------------------------------------------|---------------------------------------|---------------------------|--------------------------|-------------------------------------------------------|--|--| +| None | - | - | - | - | | | +| Signals | Mandatory/Optional | Used in command: | | Duration Provisioned Value: | | | +| None | - | - | | - | | | +| | Signal Parameters | Mandatory/Optional | Supported Values: | Duration Provisioned Value: | | | +| | - | - | - | - | | | +| Events | Mandatory/Optional | Used in command: | | | | | +| Inactivity Timeout (it/ito, 0x0045/0x0001) | M | MOD, NOTIFY | | | | | +| | Event Parameters | Mandatory/Optional | Supported Values: | Provisioned Value: | | | +| | Maximum Inactivity Time (mit, 0x0001) | M | Any integer | Unspecified, if not sent a value must be provisioned. | | | +| | ObservedEvent Parameters | Mandatory/Optional | Supported Values: | Provisioned Value: | | | +| | None | - | - | - | | | +| Statistics | Mandatory/Optional | Used in command: | | Supported Values: | | | +| None | - | - | | - | | | +| Error Codes | Mandatory/Optional | | | | | | +| None | - | | | | | | + +## C.14.36 3G Interface Type package + +Table C.14.36: Package Usage Information for 3G Interface Type package + +| Properties | Mandatory/Optional | Used in command: | Supported Values: | Provisioned Value: | | | +|-----------------------------------------------------------|---------------------------------|---------------------------|---------------------------------------------------------------------------------------------------|------------------------------------|--|--| +| IP interface type,
(threeoint/ipint,
0x00e3/0x0001) | M | ADD, MOD | "NboIP"
(0x0001)
"AoIP"
(0x0002)
"MboIP"
(0x0003)
"ExtSIPI"
(0x0004)
NOTE | None | | | +| Signals | Mandatory/Optional | Used in command: | | Duration Provisioned Value: | | | +| None | - | - | | - | | | +| | Signal Parameters | Mandatory/Optional | Supported Values: | Duration Provisioned Value: | | | +| | - | - | - | - | | | +| Events | Mandatory/Optional | Used in command: | | | | | +| None | - | - | | | | | +| | Event Parameters | Mandatory/Optional | Supported Values: | Provisioned Value: | | | +| | - | - | - | - | | | +| | ObservedEvent Parameters | Mandatory/Optional | Supported Values: | Provisioned Value: | | | +| | - | - | - | - | | | +| Statistics | Mandatory/Optional | Used in command: | | Supported Values: | | | +| None | - | - | | - | | | +| Error Codes | Mandatory/Optional | | | | | | +| None | - | | | | | | +| NOTE: Other values reserved | | | | | | | + +## C.14.37 Differentiated Services (ds) + +Table C.14.37: Differentiated Services package + +| Properties | Mandatory/Optional | Used in command | Supported Values | Provisioned Value | | | +|---------------------------------------------------------------|---------------------------------|---------------------------|-------------------------|-----------------------------------|--|--| +| Differentiated Services Code Point
(ds/dscp,0x008b/0x0001) | M | ADD, MODIFY | ALL | Yes | | | +| Tagging Behaviour
(ds/tb, 0x008b/0x0002) | O | ADD, MODIFY | ALL | Yes | | | +| Signals | Mandatory/Optional | Used in command | | Duration Provisioned Value | | | +| None | - | - | | - | | | +| | Signal Parameters | Mandatory/Optional | Supported Values | Duration Provisioned Value | | | +| | - | - | - | - | | | +| Events | Mandatory/Optional | Used in command | | | | | +| None | - | - | | | | | +| | Event Parameters | Mandatory/Optional | Supported Values | Provisioned Value | | | +| | - | - | - | - | | | +| | ObservedEvent Parameters | Mandatory/Optional | Supported Values | Provisioned Value | | | +| | - | - | - | - | | | +| Statistics | Mandatory/Optional | Used in command | Supported Values | | | | +| None | - | - | - | | | | +| Error Codes | Mandatory/Optional | | | | | | +| None | - | | | | | | + +## C.14.38 Gate Management (gm) + +Table C.14.38: Gate Management Package + +| Properties | Mandatory/Optional | Used in command | Supported Values | Provisioned Value | | | +|---------------------------------------------------------|--------------------------|--------------------|------------------|----------------------------|--|--| +| Remote Source Address Filtering (gm/saf,0x008c/0x0001) | M | ADD, MODIFY | ALL | Not Applicable | | | +| Remote Source Address Mask (gm/sam,0x008c/0x0002) | O | ADD, MODIFY | ALL | Not Applicable | | | +| Remote Source Port Filtering (gm/spf,0x008c/0x0003) | M | ADD, MODIFY | ALL | Not Applicable | | | +| Remote Source Port (gm/spr,0x008c/0x0004) | O | ADD, MODIFY | ALL | Not Applicable | | | +| Explicit Source Address Setting (gm/esas,0x008c/0x0005) | Not Supported | NONE | - | - | | | +| Local Source Address (gm/lsa,0x008c/0x0006) | Not Supported | NONE | - | - | | | +| Explicit Source Port Setting (gm/esps,0x008c/0x0007) | Not Supported | NONE | - | - | | | +| Local Source Port (gm/lsp,0x008c/0x0008) | Not Supported | NONE | - | - | | | +| Remote Source Port Range (gm/spr,0x008c/0x000A) | O | ADD, MODIFY | ALL | Not Applicable | | | +| Signals | Mandatory/Optional | Used in command | | Duration Provisioned Value | | | +| None | - | - | | - | | | +| | Signal Parameters | Mandatory/Optional | Supported Values | Duration Provisioned Value | | | +| | - | - | - | - | | | +| Events | Mandatory/Optional | Used in command | | | | | +| None | - | - | | | | | +| | Event Parameters | Mandatory/Optional | Supported Values | Provisioned Value | | | +| | - | - | - | - | | | +| | ObservedEvent Parameters | Mandatory/Optional | Supported Values | Provisioned Value | | | +| Statistics | Mandatory/Optional | Used in command | Supported Values | | | | +| Discarded Packets (gm/dp,0x008c/0x0001) | Not Supported | None | - | | | | +| Error Codes | Mandatory/Optional | | | | | | +| None | - | | | | | | + +NOTE : This package extends RTP Control Protocol package (ITU-T Recommendation H.248.57 [66]) and thus inherits RTCP Allocation Specific Behaviour property (rsb). + +## C.14.39 Traffic management (tman) + +Table C.14.39: Traffic Management Package + +| Properties | Mandatory/Optional | Used in command | Supported Values | Provisioned Value | | | +|-----------------------------------------------------|--------------------------|--------------------|------------------|----------------------------|--|--| +| Policing (tman/pol, 0x008d/0x0005) | M | ADD, MODIFY | ALL | Not Applicable | | | +| Peak Data Rate (tman/pdr, 0x008d/0x0001) | O | ADD, MODIFY | ALL | Not Applicable | | | +| Delay Variation Tolerance (tman/dvt, 0x008d/0x0004) | O | ADD, MODIFY | ALL | ANY | | | +| Sustainable Data Rate (tman/sdr, 0x008d/0x0002) | M | ADD, MODIFY | ALL | Not Applicable | | | +| Maximum burst size (tman/mbs, 0x008d/0x0003) | M | ADD, MODIFY | ALL | Not Applicable | | | +| Signals | Mandatory/Optional | Used in command | | Duration Provisioned Value | | | +| None | - | - | | - | | | +| | Signal Parameters | Mandatory/Optional | Supported Values | Duration Provisioned Value | | | +| | - | - | | - | | | +| Events | Mandatory/Optional | Used in command | | | | | +| None | - | - | | | | | +| | Event Parameters | Mandatory/Optional | Supported Values | Provisioned Value | | | +| | - | - | | | | | +| | ObservedEvent Parameters | Mandatory/Optional | Supported Values | Provisioned Value | | | +| Statistics | Mandatory/Optional | Used in command | | Supported Values | | | +| None | - | - | | - | | | +| Error Codes | Mandatory/Optional | | | | | | +| None | - | | | | | | + +NOTE: The data rate shall be calculated using the packet size from IP layer upwards. The Token Bucket method as described by ITU-T Recommendation H.248.53 [69] sub-clause 9.4.3 (as per IETF RFC 2216 [73]) shall be followed where SDR = "r" and MBS = "b" (i.e. the additional "M" value does not apply). + +## C.14.40 IP Realm Availability (ipra) + +Table C.14.40: IP Realm Availability Package + +| Properties | Mandatory/Optional | Used in command | Supported Values | Provisioned Value | | | +|-----------------------------------------------------|----------------------------------------|---------------------------|--------------------------|-----------------------------------|--|--| +| Available Realms, (ipra/ar, 0x00e0/0x0001) | M | AUDITVALUE | ALL | Not Applicable | | | +| Signals | Mandatory/Optional | Used in command | | Duration Provisioned Value | | | +| None | - | - | | - | | | +| | Signal Parameters | Mandatory/Optional | Supported Values | Duration Provisioned Value | | | +| | - | - | | - | | | +| Events | Mandatory/Optional | Used in command | | | | | +| Available Realms Changed, (ipra/arc, 0x00e0/0x0001) | M | MODIFY, NOTIFY | | | | | +| | Event Parameters | Mandatory/Optional | Supported Values: | Provisioned Value | | | +| | - | - | | - | | | +| | ObservedEvent Parameters | Mandatory/Optional | Supported Values | Provisioned Value | | | +| | Newly Available Realms (nar, 0x0001) | M | ALL | Not applicable | | | +| | Newly Unavailable Realms (nur, 0x0002) | M | ALL | Not applicable | | | +| Statistics | Mandatory/Optional | Used in command | | Supported Values | | | +| None | - | - | | - | | | +| Error Codes | Mandatory/Optional | | | | | | +| None | - | | | | | | + +## C.14.41 RTCP Handling Package (rtcph) + +Table C.14.41: RTCP Handling Package + +| Properties | Mandatory/Optional | Used in command | Supported Values | Provisioned Value | | | +|---------------------------------------------------------------|---------------------------------|---------------------------|-------------------------|-----------------------------------|--|--| +| RTCP Allocation Specific Behaviour (rtcph/rsb, 0x00b5/0x0009) | M | ADD, MODIFY | ALL | OFF | | | +| Signals | Mandatory/Optional | Used in command | | Duration Provisioned Value | | | +| None | - | - | | - | | | +| | Signal Parameters | Mandatory/Optional | Supported Values | Duration Provisioned Value | | | +| | - | - | | - | | | +| Events | Mandatory/Optional | Used in command | | | | | +| None | - | - | | | | | +| | Event Parameters | Mandatory/Optional | Supported Values | Provisioned Value | | | +| | - | - | | - | | | +| | ObservedEvent Parameters | Mandatory/Optional | Supported Values | Provisioned Value | | | +| | - | - | | - | | | +| Statistics | Mandatory/Optional | Used in command | | Supported Values | | | +| None | - | - | | - | | | +| Error Codes | Mandatory/Optional | | | | | | +| None | - | | | | | | + +## C.14.42 Application Data Inactivity Detection (adid) + +Table C.14.42: Application Data Inactivity Detection package + +| Properties | Mandatory/Optional | Used in command | Supported Values | Provisioned Value | +|-----------------------------------------------------|---------------------------------|---------------------|------------------|-----------------------------------| +| None | - | - | - | - | +| Signals | Mandatory/Optional | Used in command | | Duration Provisioned Value | +| None | - | - | | - | +| | Signal Parameters | Mandatory/Optional | Supported Values | Duration Provisioned Value | +| | - | - | - | - | +| Events | Mandatory/Optional | Used in command | | | +| IP Flow Stop Detection (adid/ipstop, 0x009c/0x0001) | M | ADD, MODIFY, NOTIFY | | | +| | Event Parameters | Mandatory/Optional | Supported Values | Provisioned Value | +| | Detection time (dt,0x0001) | M | ALL | Yes | +| | Direction (dir, 0x002) | M | ALL | Yes | +| | ObservedEvent Parameters | Mandatory/Optional | Supported Values | Provisioned Value | +| | - | - | - | - | +| Statistics | Mandatory/Optional | Used in command | Supported Values | | +| None | - | - | - | | +| Error Codes | Mandatory/Optional | | | | +| None | - | | | | + +## C.14.43 Explicit Congestion Notification for RTP-over-UDP Support (ecnrous) + +**Table C.14.43.1: Explicit Congestion Notification for RTP-over-UDP Support package** + +| Properties | Mandatory/Optional | Used in command | Supported Values | Provisioned Value | | | +|----------------------------------------------------------------|----------------------------------|---------------------|------------------|---------------------------------------------------------------------------------------------|--|--| +| ECN Enabled (ecnrous/ecn, 0x010b/0x0001) | M | ADD, MODIFY | True, False | - | | | +| Congestion Response Method (ecnrous/crm, 0x010b/0x0002) | Not Signalled | - | - | "RDCC"(0x0002)
NOTE | | | +| Initiation Method (ecnrous/initmethod, 0x010b/0x0003) | M | ADD, MODIFY | "leap" | "leap" | | | +| ECN Mode (ecnrous/mode, 0x010b/0x0004) | Not Signalled | - | - | "setonly" (0x0001) in the Remote Descriptor and "readonly" (0x0002) in the Local Descriptor | | | +| ECT Marking (ecnrous/ectmark, 0x010b/0x0005) | Not Signalled | - | - | "0" (0x0002) | | | +| ECN Congestion Marking (ecnrous/congestmark, 0x010b/0x0006) | Not Signalled | - | - | "nomark" (0x0003) | | | +| ECN SDP Usage (ecnrous/ecnsdp, 0x010b/0x0007) | Not Signalled | - | - | "P" (0x0001) | | | +| Signals | Mandatory/Optional | Used in command | | Duration Provisioned Value | | | +| None | - | - | | - | | | +| | Signal Parameters | Mandatory/Optional | Supported Values | Duration Provisioned Value | | | +| | - | - | - | - | | | +| Events | Mandatory/Optional | Used in command | | | | | +| ECN Failure (ecnrous/fail, 0x010b/0x0001) | M | ADD, MODIFY, NOTIFY | | | | | +| | Event Parameters | Mandatory/Optional | Supported Values | Provisioned Value | | | +| | - | - | - | - | | | +| | - | - | - | - | | | +| | ObservedEvent Parameters | Mandatory/Optional | Supported Values | Provisioned Value | | | +| | Failure Type (type, 0x0001) | Mandatory | INIT, USE | - | | | +| | Media Sender SSRC (ssrc, 0x0002) | Not Supported | - | - | | | +| Statistics | Mandatory/Optional | Used in command | | Supported Values | | | +| Source (ecnrous/ssrc, 0x010b/0x0001) | Not Supported | - | | - | | | +| CE Counter (ecnrous/cecount, 0x010b/0x0002) | Not Supported | - | | - | | | +| ECT0 Counter (ecnrous/ectzero, 0x010b/0x0003) | Not Supported | - | | - | | | +| ECT1 Counter (ecnrous/ectone, 0x010b/0x0004) | Not Supported | - | | - | | | +| Not-ECT Counter (ecnrous/notect, 0x010b/0x0005) | Not Supported | - | | - | | | +| Lost Packets Counter (ecnrous/lost, 0x010b/0x0006) | Not Supported | - | | - | | | +| Extended Highest Sequence number (ecnrous/ehsn, 0x010b/0x0007) | Not Supported | - | | - | | | +| Duplication Counter (ecnrous/dup, 0x010b/0x0008) | Not Supported | - | | - | | | +| Error Codes | Mandatory/Optional | | | | | | +| None | - | | | | | | + +NOTE: Application Specific Rate Adaptation shall be applied in accordance with 3GPP TS 26.114 [77]. For speech this requires support of CMR and TMMBR for video. + +## C.15 Mandatory support of SDP and Annex C information elements + +Mandatory support of SDP and Annex C information elements shall be in accordance with subclause 11. + +**Table C.15: Mandatory Annex C and SDP information elements** + +| Information Element | Annex C Support | SDP Support | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------|-------------| +| Bearer Service Characteristics | TMR | | +| ISDN BC | USI | | +| NOTE 1: When text encoding is used, all the Information Elements shall be supported via their corresponding SDP parameters, as specified in subclause 11. Annex C SDP equivalents shall not be used. | | | + +## C.16 Optional support of SDP and Annex C information elements + +Table C.16: Optional Annex C and SDP information elements + +| Information Element | Annex C Support | SDP Support | +|---------------------|-----------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| v-line | "SDP_V " | As in 3GPP TS 29.332 [51], clause A.15 (NOTE 1) | +| m-line | "SDP_M " | As in 3GPP TS 29.332 [51], clause A.15 (NOTE 1) | +| c-line | "SDP_C " | As in 3GPP TS 29.332 [51], clause A.15 (NOTE 1) | +| a-line | "SDP_A " | As in 3GPP TS 29.332 [51], clause A.15 (NOTE 1) (NOTE 7) | +| b-line | "SDP_B " | As in 3GPP TS 29.332 [51], clause A.15 (NOTE 1) (NOTE 8) | +| o-line | "SDP_O" | As in 3GPP TS 29.332 [51], clause A.15 | +| s-line | "SDP_S" |

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

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

| +| Codec | Acoder | Mandatory for BICC and Iu terminations. (NOTE 2) | +| BNC-Id | BIR (NOTE 3) | Mandatory for BICC-ATM (NOTE 2) | +| BIWF_Address | NSAP (NOTE 4) | Mandatory for BICC-ATM (NOTE 2) | +| Iu IP Address | IPv4
IPv6 | As defined in ITU-T Recommendation H.248.1 [10] C6. Mandatory for Iu termination with IP transport (NOTE 5) | +| Iu IP Port | Port | As defined in ITU-T Recommendation H.248.1 [10] C6. Mandatory for Iu termination with IP transport (NOTE 6) | + +NOTE 1: If the procedures Reserve RTP Connection Point, Configure RTP Connection Point, Reserve and Configure RTP Connection Point are supported, these properties shall be supported. + +NOTE 2: When text encoding is used, all the Information Elements shall be supported via their corresponding SDP parameters, as specified in subclause 11. Annex C SDP equivalents shall not be used. + +NOTE 3: The BIR length shall be fixed at 4 Octets. + +NOTE 4: The NSAP length shall be fixed at 20 Octets. The content of the RNC Transport Address or BIWF Address depends on the used transport interface but the principle is that NSAP format is used. See 3GPP TS 25.414 [21] for RNC and for core network see 3GPP TS 29.414 [32]. For IP the IANA ICP IDI format of the NSAP addressing format as specified in X.213 [33] shall be used. For IPv4 networks the IPv4 format recommended by X.213 shall be adopted. + +NOTE 5: The value is mapped to/from the first 4(or 16) octets of the IPv4 (or IPv6) address part of the Transport Layer Address in 3GPP TS 25.413 [20]. + +NOTE 6: The value is mapped to/from the Binding ID in the RANAP IE Iu transport Association, 3GPP TS 25.413 [20]. + +NOTE 7: For the RTP Payload for Redundant Audio Data, the encoding name with "red" and "fmtp" attributes shall be provided to indicate the redundancy level and shall always be signalled in conjunction with the CLEARMODE Payload type as described in 10.2.3.5.2. No other Payload types are currently defined for use with the Redundant RTP Payload. + +NOTE 8: For RTP flows, where RTCP resources are reserved together with the RTP resources using the "RTP Specific Behaviour" property of the Gate Management package (gm) property, the MGC may also supply additional RTCP bandwidth modifiers (i.e. RR and RS, see IETF RFC 3556 [52]). The AS *bandwidth* value will include the bandwidth used by RTP. In the absence of the RTCP bandwidth modifiers, the MGW shall allow an additional 5% of the AS bandwidth value for the bandwidth for RTCP, in accordance with IETF RFC 3556 [52]. + +--- + +## Annex D (informative): Change history + +| Change history | | | | | | | | | +|----------------|-------|-----------|-----|-----|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------|-------|--| +| Date | TSG # | TSG Doc. | CR | Rev | Subject/Comment | Old | New | | +| Sep 2000 | | | | | Initial draft created after N4#4 based on N4-000620 | 0.0.1 | 0.1.0 | | +| Oct 2000 | | | | | Updated after N4 R2000 Ad Hoc Stockholm based on N4-00823 and N4-000842 | 0.1.0 | 0.2.0 | | +| Nov 2000 | | | | | Reference for MTP 3B corrected; RFC reference for SCTP added | 0.2.0 | 0.3.0 | | +| Nov 2000 | | | | | Updated according to N4-000996, N4-000998, N4-000999, N4-001000, N4-001021, N4-001028 & N4-001097 as agreed in CN4 #5 | 0.3.0 | 1.0.0 | | +| Nov 2000 | CN#10 | | | | To TSG-CN Plenary #10 for information | 1.0.0 | 1.1.0 | | +| Jan 2001 | | | | | Updated according to NJ-010069, NJ-010030, NJ-010098, NJ-010094, NJ-010033, NJ-010097, NJ-010095, NJ-010112 as agreed in the Joint CN3/CN4 Meeting held during the CN4#6 | 1.1.0 | 1.1.1 | | +| Jan 2001 | | | | | References ordered by specification/recommendation number; references to 3GPP specifications include full titles as shown on the title page; literal reference numbers and references to subclauses replaced with fields; all table cells outlined with 0.5pt lines; appropriate 3GPP paragraph styles applied. | 1.1.1 | 1.2.0 | | +| Feb 2001 | | | | | Updated according to N4-010245, N4-010248, N4-010249, N4-010303, N4-010304, N4-010305, agreed in CN4 Release 4 ad hoc, Madrid. References to Q.1902.x replaced by references to 29.205; 3GPP styles applied consistently; form for ITU-T recommendations in text is now "ITU-T Recommendation A.NNNN". | 1.2.0 | 1.3.0 | | +| Mar 2001 | | | | | Updated according to N4-010384, N4-010401 (part) & N4-010472, agreed in CN4 in Sophia Antipolis. References to Q.1950, Q.1970 and Q.1990 replaced by reference to 29.205. Reference to SIP-T deleted. Editor's note in 15.1.2.3 deleted. Editorial clean-up. | 1.3.0 | 2.0.0 | | +| Mar 2001 | | | | | Sent to TSG CN#11 for approval | 2.0.0 | 2.1.0 | | +| Mar 2001 | CN#11 | | | | References updated after comments in TSG CN #11 Approved in CN#11 | 2.1.0 | 4.0.0 | | +| Jun 2001 | CN#12 | NP-010284 | 1 | 1 | Text encoding of codec information on Mc interface | 4.0.0 | 4.1.0 | | +| Jun 2001 | CN#12 | NP-010284 | 4 | 2 | ATM-IP signalling transport Interworking | 4.0.0 | 4.1.0 | | +| Jun 2001 | CN#12 | NP-010284 | 5 | 1 | Alignment of Procedure names to TS 23.205 and Q.1950 | 4.0.0 | 4.1.0 | | +| Jun 2001 | CN#12 | NP-010284 | 6 | 3 | Clarifications in 3GUP package | 4.0.0 | 4.1.0 | | +| Jun 2001 | CN#12 | NP-010284 | 7 | 1 | Clarification of Use of UP version property in 3GUP package | 4.0.0 | 4.1.0 | | +| Jun 2001 | CN#12 | NP-010284 | 8 | 1 | Updates to UP Relay Function, Appendix A | 4.0.0 | 4.1.0 | | +| Sep 2001 | CN#13 | | | | Editorial clean up | 4.1.0 | 4.2.0 | | +| Sep 2001 | CN#13 | NP-010452 | 009 | | Addition of package numbers allocated by IANA | 4.1.0 | 4.2.0 | | +| Sep 2001 | CN#13 | NP-010452 | 010 | 1 | Mc signalling transport in IP environment | 4.1.0 | 4.2.0 | | +| Dec 2001 | CN#14 | NP-010619 | 011 | 1 | Inclusion of H.248 Annex L, "Error Codes and Service Change Reason Description" | 4.2.0 | 4.3.0 | | +| Dec 2001 | CN#14 | NP-010619 | 012 | | Removal of the Reuse Idle Package | 4.2.0 | 4.3.0 | | +| Dec 2001 | CN#14 | NP-010619 | 014 | | Correction of Release Procedures | 4.2.0 | 4.3.0 | | +| Dec 2001 | CN#14 | NP-010619 | 015 | | Clarification Of Use Of 3GUP package For PCM | 4.2.0 | 4.3.0 | | +| Dec 2001 | CN#14 | NP-010619 | 016 | | Corrections to ABNF coding of PackageIDs | 4.2.0 | 4.3.0 | | +| Dec 2001 | CN#14 | NP-010619 | 017 | | Correction of BICC packages | 4.2.0 | 4.3.0 | | +| Dec 2001 | CN#14 | NP-010619 | 020 | 1 | Correction of 3GUP package sub-list type | 4.2.0 | 4.3.0 | | +| Dec 2001 | CN#14 | NP-010631 | 013 | 1 | Introduction of MGW Congestion Handling | 4.3.0 | 5.0.0 | | +| Dec 2001 | CN#14 | NP-010631 | 019 | 2 | Maintenance locking of MG | 4.3.0 | 5.0.0 | | +| Jan 2002 | | | | | A coverdheet fixed | 5.0.0 | 5.0.1 | | +| Mar 2002 | CN#15 | NP-020029 | 025 | 2 | Naming convention for TDM resources | 5.0.1 | 5.1.0 | | + +| Change history | | | | | | | | +|----------------|--------|------------|-----|------|---------------------------------------------------------------------------------------------|-------|-------| +| Date | TSG # | TSG Doc. | CR | Re v | Subject/Comment | Old | New | +| Mar 2002 | CN#1 5 | NP-02002 9 | 027 | 2 | Correction of Bearer Modification Handling | 5.0.1 | 5.1.0 | +| Jun 2002 | CN#1 6 | NP-02026 0 | 030 | 1 | GTT enhancement on Mc | 5.1.0 | 5.2.0 | +| Jun 2002 | CN#1 6 | NP-02026 0 | 032 | | Update to TFO package to explicitly reference TS 26.103 for 3GPP codecs | 5.1.0 | 5.2.0 | +| Jun 2002 | CN#1 6 | NP-02026 0 | 033 | 2 | CTM Text Transport package | 5.1.0 | 5.2.0 | +| Jun 2002 | CN#1 6 | NP-02026 0 | 034 | | Allow the usage of logical port | 5.1.0 | 5.2.0 | +| Jun 2002 | CN#1 6 | NP-02024 9 | 036 | | Correction subclause 14.1.6 of 3GPP TS 29.332 | 5.1.0 | 5.2.0 | +| Sep 2002 | CN#1 7 | NP-02045 9 | 037 | 1 | Misalignment between TS 23.226 and TS 29.232 for Global Text Telephony | 5.2.0 | 5.3.0 | +| Sep 2002 | CN#1 7 | NP-02045 9 | 038 | 1 | Alignment of text in TS 29.232 for Global Text Telephony | 5.2.0 | 5.3.0 | +| Sep 2002 | CN#1 7 | NP-02045 9 | 039 | 1 | Alignment between prepare bearer and reserve bearer in TS 29.232 for Global Text Telephony. | 5.2.0 | 5.3.0 | +| Sep 2002 | CN#1 7 | NP-02046 3 | 044 | 1 | Missing Properties For Circuit Switched Data Calls | 5.2.0 | 5.3.0 | +| Dec 2002 | CN#1 8 | NP-02057 9 | 041 | 2 | Termination ID Correction | 5.3.0 | 5.4.0 | +| Dec 2002 | CN#1 8 | NP-02059 7 | 042 | 3 | New Procedures/Package for handling IP transport for Iu interface | 5.3.0 | 5.4.0 | +| Dec 2002 | CN#1 8 | NP-02057 8 | 046 | 2 | Updates to support Codec Modification | 5.3.0 | 5.4.0 | +| Dec 2002 | CN#1 8 | NP-02059 4 | 052 | 2 | CAMEL4 flexible tone package | 5.3.0 | 5.4.0 | +| Mar 2003 | CN#1 9 | NP-03010 8 | 053 | | Update to 3GUP – clarification of IuUP Initialisation handling | 5.4.0 | 5.5.0 | +| Mar 2003 | CN#1 9 | NP-03010 8 | 054 | 1 | Update to 3GUP – addition of reference to SDU format definition for Nb interface | 5.4.0 | 5.5.0 | +| Jun 2003 | CN#2 0 | NP-03021 1 | 057 | 1 | Alignment of references after renumbering of H248 by ITU-T | 5.5.0 | 5.6.0 | +| Jun 2003 | CN#2 0 | NP-03021 1 | 059 | | Clarification of handling of DTMF in split architecture – DTMF timing | 5.5.0 | 5.6.0 | +| Mar 2004 | CN#2 3 | NP-04005 2 | 061 | | Addition of Package Id for CTM | 5.6.0 | 5.7.0 | +| Mar 2004 | | | | | Addition of Package Ids allocated by IANA (0082 - 0084) | 5.6.0 | 5.7.0 | +| Sep 2004 | CN#2 5 | NP-04039 2 | 063 | | Correction of Procedure "Activate Voice Processing Function" | 5.7.0 | 5.8.0 | +| Sep 2004 | CN#2 5 | NP-04041 8 | 075 | 2 | 3GUP package corrections | 5.7.0 | 5.8.0 | +| Sep 2004 | CN#2 5 | NP-04041 8 | 064 | | Provisioning Of Base Root package properties | 5.7.0 | 5.8.0 | +| Sep 2004 | CN#2 5 | NP-04041 8 | 065 | | Service Change Address | 5.7.0 | 5.8.0 | +| Sep 2004 | CN#2 5 | NP-04041 8 | 066 | | Use Of Event Buffers | 5.7.0 | 5.8.0 | +| Sep 2004 | CN#2 5 | NP-04041 8 | 067 | | Digit Maps | 5.7.0 | 5.8.0 | +| Sep 2004 | CN#2 5 | NP-04041 8 | 068 | | IP secured transport | 5.7.0 | 5.8.0 | +| Sep 2004 | CN#2 5 | NP-04041 8 | 074 | | Termination Restoration | 5.7.0 | 5.8.0 | +| Sep 2004 | CN#2 5 | NP-04039 2 | 072 | 1 | Use Of Statistics | 5.7.0 | 5.8.0 | +| Dec 2004 | CN#2 6 | NP-04052 1 | 078 | | Correction of distant codec list | 5.8.0 | 5.9.0 | +| Dec 2004 | CN#2 6 | NP-04052 8 | 079 | | IP transport package Duplicate property ID in ASN.1 encoding | 5.8.0 | 5.9.0 | +| Dec 2004 | CN#2 6 | NP-04052 9 | 080 | 1 | H.248 Scope | 5.8.0 | 5.9.0 | +| Dec 2004 | CN#2 6 | NP-04052 9 | 081 | 1 | Q.1950 reference | 5.8.0 | 5.9.0 | +| Dec 2004 | CN#2 6 | NP-04052 9 | 082 | | Emdedded events | 5.8.0 | 5.9.0 | +| Dec 2004 | CN#2 6 | NP-04052 9 | 084 | | Multiple streams | 5.8.0 | 5.9.0 | +| Dec | CN#2 | NP-04052 | 085 | 1 | Overspec/underspec parameters | 5.8.0 | 5.9.0 | + +| Change history | | | | | | | | +|----------------|--------|------------|-----|-----|------------------------------------------------------------------------------------------|-------|-------| +| Date | TSG # | TSG Doc. | CR | Rev | Subject/Comment | Old | New | +| 2004 | 6 | 9 | | | | | | +| Dec 2004 | CN#2 6 | NP-04052 9 | 088 | 2 | Procedures and Commands – removal of unwanted commands | 5.8.0 | 5.9.0 | +| Dec 2004 | CN#2 6 | NP-04054 7 | 092 | | Update of referenced H.248.1 version to version 2 | 5.9.0 | 6.0.0 | +| Mar 2005 | CN#2 7 | NP-05005 7 | 060 | 7 | Addition of the trace package | 6.0.0 | 6.1.0 | +| | | NP-05002 9 | 101 | 1 | Requirements for support of H.248 packages | | | +| | | NP-05002 9 | 104 | 1 | Completion of specification of UMTS Packages | | | +| | | NP-05003 6 | 106 | | Correction of implied option for Embedded Signals and Events | | | +| | | NP-05003 6 | 108 | 2 | Removal of the 'Test' ServiceStates value from the TerminationState Descriptor | | | +| | | NP-05003 6 | 111 | 1 | Removal of the usage of the ContextAttributeAuditReq construct | | | +| | | NP-05003 6 | 113 | | Removal of the Multiplex descriptor | | | +| | | NP-05003 6 | 115 | | Removal of the Modem descriptor | | | +| | | NP-05013 3 | 120 | 4 | Requirements for support of procedures | | | +| | | NP-05003 4 | 122 | 2 | Procedure for Emergency Call Indication | | | +| | | NP-05003 6 | 128 | | Removal of the Error Descriptor usage in NotifyRequest | | | +| | | NP-05003 6 | 130 | | Updating incomplete parameter definition for MGW Resource congestion handling procedures | | | +| | | NP-05005 5 | 131 | | Removal of Signals on ROOT | | | +| | | NP-05005 5 | 132 | | Removal of usage of Stream ID in Topology descriptor | | | +| | | NP-05005 5 | 133 | | H.248.1 version contradiction | | | +| | | NP-05003 6 | 135 | | Directionality of tones and announcements | | | +| | | NP-05003 6 | 138 | 1 | New 'TFO status' event | | | +| | | NP-05002 8 | 139 | 1 | TFO procedure clarification | | | +| | | NP-05002 8 | 142 | 1 | TFO activation without TFO Codec List | | | +| | | NP-05003 6 | 148 | 1 | Commands on ROOT | | | +| | | NP-05003 6 | 149 | 1 | Use Of Audit Value | | | +| | | NP-05003 6 | 151 | | Service Change Reasons Not supported | | | +| | | NP-05003 6 | 155 | 1 | Descriptors in command replies | | | +| | | NP-05003 6 | 157 | 1 | Introduction of formal profile name for Mc interface | | | +| | | NP-05003 6 | 158 | | Service Change for Failover not defined for Mc Interface | | | +| | | NP-05002 9 | 161 | | Removal Of VPF type | | | +| | | NP-05002 9 | 164 | | Alignment of TFO Activation Procedure and associated parameters | | | +| | | NP-05005 5 | 165 | 2 | Continuity Test | | | +| Jun 2005 | CT#28 | CP-05023 6 | 184 | 1 | BNC Cut-Through Capability Package Removed | 6.1.0 | 6.2.0 | +| | | CP-05023 6 | 187 | 1 | Format of IP address | | | +| | | CP-05010 1 | 188 | 2 | Profile Registration Mandatory/Negotiation Clarification | | | +| | | CP-05023 6 | 196 | 1 | Clarification of Maintenance Procedures | | | +| | | CP-05023 6 | 198 | 1 | Clarification of Use Of Topology and Multiparty | | | + +| Change history | | | | | | | | +|----------------|-------|-----------|------|-----|------------------------------------------------------------------------------------|-------|-------| +| Date | TSG # | TSG Doc. | CR | Rev | Subject/Comment | Old | New | +| | | CP-050236 | 200 | | Removal of Option in Prepare Bearer that the MGW can chose the BNC Characteristics | | | +| | | CP-050236 | 202 | 1 | Clarification Of Use of Wildcarding | | | +| | | CP-050080 | 209 | 2 | Text encoding of IPBCP for IP transport on Mc interface | | | +| | | CP-050080 | 212 | 2 | Definition of requirement for support of commands | | | +| | | CP-050238 | 213 | 1 | Correction to Profile registration procedures | | | +| Sep 2005 | CT#29 | CP-050435 | 218 | 1 | Codec IE and Codec List on the Mc interface | 6.2.0 | 6.3.0 | +| | | CP-050290 | 224 | | Value range for BIR/NSAP | | | +| | | CP-050290 | 229 | | Clarification of 'extended only' packages | | | +| | | CP-050290 | 231 | | Correction to Prepare IP Transport procedure | | | +| | | CP-050290 | 233 | 1 | Wildcarding of Release Procedures | | | +| | | CP-050290 | 235 | | Clarification to use of local peer for CSD | | | +| | | CP-050280 | 238 | 2 | Correction to clarify use of FAX and Channel Mode Modify | | | +| | | CP-050290 | 242 | 1 | Clarification to use of PLMN-BC, GSM-Chanel Coding for CSD | | | +| | | CP-050290 | 244 | 1 | Clarification to use of Init Dir parameter | | | +| | | CP-050290 | 246 | 1 | Clarification to Termination Restoration and Termination Out Of Service | | | +| | | CP-050290 | 248 | | Remove provisioning of Resource Congestion Event | | | +| | | CP-050290 | 250 | | Remove Priority property | | | +| | | CP-050290 | 252 | | Notifications for IP Bearer Establishment | | | +| | | CP-050290 | 254 | 1 | Clarification for Use of Stream Mode Property with Announcements | | | +| | | CP-050290 | 256 | | Removal of Stream Mode Loopback | | | +| | | CP-050290 | 258 | | Correction to IPBCP Tunnel Procedures | | | +| | | CP-050290 | 263 | | Exclusion of use of Signal ID Play Tone for DTMF | | | +| | | CP-050290 | 265 | 1 | Miscellaneous Open Mc corrections | | | +| | | CP-050308 | 266 | 1 | Use of Individual Audit Token | | | +| | | CP-050438 | 268 | 1 | Restriction of Service Change Address in MGW Restriction | | | +| | | CP-050308 | 271 | | Removal of BNC-cut-through-capability from Prepare Bearer procedure | | | +| | | CP-050308 | 272 | | Updating Mc interface profile "threeegbicsn" to version 2 | | | +| | | CP-050290 | 276 | | Defining a default value for "Echo cancelling" property | | | +| | | CP-050309 | 278 | 1 | Correction on Burst interval duration | | | +| | | CP-050308 | 281 | 1 | Clarification of "Normal Release" parameter | | | +| Dec 2005 | CT#30 | CP-050603 | 0261 | 2 | Correction to clarify TFO Package use | 6.3.0 | 6.4.0 | +| | | CP-050607 | 0288 | 1 | Clarification to client/server behaviour with regards to SCTP Initiation | | | +| | | CP-050607 | 0289 | 1 | Inclusion of Error Code #449 for unsupported parameter value | | | +| | | CP-050618 | 0290 | 1 | Correction to Continuity Test Procedure | | | +| | | CP-050607 | 0296 | 1 | Setting of CN/Outgoing Nb termination prior to bearer establishment | | | +| | | CP-05060 | 0304 | 2 | Correction to use of BITRATE for CSD calls | | | + +| Change history | | | | | | | | +|----------------|-------|----------|----|-----|-----------------|-----|-----| +| Date | TSG # | TSG Doc. | CR | Rev | Subject/Comment | Old | New | +| | | 7 | | | | | | + +| Change history | | | | | | | | +|----------------|-------|---------------|------|-----|-------------------------------------------------------------------------------------------------------------------|-------|-------| +| Date | TSG # | TSG Doc. | CR | Rev | Subject/Comment | Old | New | +| | | CP-05060
7 | 0308 | 1 | Bearer Released Event to Reserve Circuit procedure | | | +| | | CP-05060
7 | 0322 | 1 | Corrections to use of GSM-Channel Coding for CSD | | | +| | | CP-05061
8 | 0323 | 3 | Correct MCC Error in implementing CR #238 | | | +| 2005-12 | CT#30 | CP-05062
9 | 0302 | 2 | Clean-up of hanging contexts and terminations | 6.4.0 | 7.0.0 | +| | | CP-05062
9 | 0309 | 1 | Clarification of MGW capability change | | | +| 2006-03 | CT#31 | CP-06007
8 | 0307 | 2 | Clarification of Termination Restoration and Termination Out-of-Service procedures | 7.0.0 | 7.1.0 | +| | | CP-06006
4 | 0326 | 2 | Correction To Termination State Handling | | | +| | | CP-06006
4 | 0329 | 1 | Send Tone procedure | | | +| | | CP-06006
4 | 0330 | 1 | ContextID in Change Flow Direction response | | | +| | | CP-06006
4 | 0333 | 1 | Correction To DTMF Detection | | | +| | | CP-06007
8 | 0337 | 1 | Clarification to use of ServiceChangeMGCId | | | +| | | CP-06007
8 | 0338 | | Clarification to cut-through procedure | | | +| | | CP-06006
4 | 0345 | 2 | Adding missing termination ID to Acknowledgement part of notification procedures | | | +| | | CP-06007
8 | 0342 | 1 | Correction to syntax for event descriptions | | | +| | | CP-06006
4 | 0348 | | Adding missing Codec, Bearer Characteristics and Bearer Service Characteristics to Prepare IP transport procedure | | | +| | | CP-06006
7 | 0352 | 1 | Correction on the used descriptor for trace package | | | +| 2006-06 | CT#32 | CP-06031
5 | 0377 | 2 | Introduction of Profile Description Annex to Mc interface | 7.1.0 | 7.2.0 | +| | | CP-06031
5 | 0379 | | Corrections to Formats and Codes table | | | +| | | CP-06031
5 | 0382 | 1 | Clarification of H.248.2 version in references | | | +| | | CP-06031
5 | 0386 | | Correction of the error definition of Flextone | | | +| | | CP-06030
7 | 0370 | | Corrigendum for H.248.1 version 2 | | | +| | | CP-06030
1 | 0365 | 2 | DTMF Detection Type | | | +| | | CP-06030
1 | 0368 | 1 | Sequential Signal Lists | | | +| | | CP-06030
1 | 0374 | 2 | Multimedia & CSD calls | | | +| | | CP-06030
1 | 0385 | 1 | Clarification of ROOT termination naming | | | +| 2006-09 | CT#33 | CP-06041
1 | 0388 | 1 | Profile Description Annex: Connection model and Context Attributes | 7.2.0 | 7.3.0 | +| | | CP-06041
1 | 0389 | 2 | Profile Description Annex: Terminations | | | +| | | CP-06041
1 | 0390 | 2 | Profile Description Annex: Descriptors | | | +| | | CP-06041
1 | 0391 | 1 | Profile Description Annex: Message, Transport and Security | | | +| | | CP-06041
1 | 0392 | 1 | Profile Description Annex: Mandatory and optional packages | | | +| | | CP-06041
1 | 0393 | 2 | Profile Description Annex: H.248 packages | | | +| | | CP-06041
1 | 0394 | 2 | Profile Description Annex: BICC packages | | | +| | | CP-06041
1 | 0395 | 2 | Profile Description Annex: Mandatory and optional 3G packages | | | +| | | CP-06041
1 | 0396 | 1 | Profile Description Annex : Command API | | | +| | | CP-06041
1 | 0397 | 1 | Profile Description Annex : Generic command syntax and encoding | | | +| | | CP-06041
1 | 0398 | 1 | Profile Description Annex : Transactions | | | + +| Change history | | | | | | | | +|----------------|-------|----------|----|-----|-----------------|-----|-----| +| Date | TSG # | TSG Doc. | CR | Rev | Subject/Comment | Old | New | +| | | 1 | | | | | | + +| Change history | | | | | | | | +|----------------|-------|---------------|------|-----|---------------------------------------------------------------------------------------|-------|-------| +| Date | TSG # | TSG Doc. | CR | Rev | Subject/Comment | Old | New | +| | | CP-06041
1 | 0399 | 1 | Profile Description Annex : Mandatory support of SDP and Annex C information elements | | | +| | | CP-06041
1 | 0400 | 1 | Profile Description Annex : Optional support of SDP and Annex C information elements | | | +| | | CP-06041
1 | 0401 | | Encoding of G.711 codec | | | +| | | CP-06040
0 | 0404 | 3 | Profile registration procedure | | | +| | | CP-06041
1 | 0407 | 2 | Definition of the use of mandatory and optional in Mc Profile Template | | | +| | | CP-06040
2 | 0409 | | Trace Package ID | | | +| | | CP-06040
0 | 0412 | | AuditValue procedure | | | +| | | CP-06040
0 | 0415 | 1 | Use of topology for tones and announcements | | | +| | | CP-06039
7 | 0420 | | Modification of eventId named distant codec_list in threegtfc package | | | +| | | CP-06040
2 | 0427 | | Wildcarding of Release Termination Response | | | +| | | CP-06040
0 | 0430 | | Correction to Emergency Call Indication Procedure | | | +| | | CP-06040
0 | 0436 | 1 | Use of IPSec for Mc Interface | | | +| | | CP-06040
0 | 0439 | 2 | Correction to use of Local Peer for CSD when Anchor MGW | | | +| | | CP-06041
1 | 0441 | 2 | New Error Code for Temporary Busy | | | +| | | CP-06041
1 | 0442 | 1 | Profile Description Annex: Descriptors (complements) | | | +| | | CP-06041
1 | 0443 | | Profile Description Annex: Trace package | | | +| | | CP-06040
2 | 0447 | | Incomplete list of optional UMTS packages | | | +| 2006-12 | CT#34 | CP-06056
9 | 0376 | 6 | Enhancements for VGCS/VBS in SPLIT architecture | 7.3.0 | 7.4.0 | +| | | CP-06056
9 | 0452 | | Correct the initiator of NOT.resp command | | | +| | | CP-06056
9 | 0474 | 1 | Removal of TBD for Number of Commands Per Transaction | | | +| | | CP-06056
9 | 0485 | 1 | Event Tunnel indication for type BICC IP | | | +| | | CP-06056
9 | 0486 | | Tunnel Option shall be used with Add.Req only | | | +| | | CP-06056
9 | 0487 | | IP transport package properties not used within Mov.Req | | | +| | | CP-06055
2 | 0459 | | Encoding of PLMN BC | | | +| | | CP-06056
1 | 0461 | 1 | Trace package correction | | | +| | | CP-06055
4 | 0464 | | Commands in Change flow direction procedure | | | +| | | CP-06071
8 | 0481 | 3 | Definite vs Indefinite encoding rules for binary H.248 | | | +| 2007-03 | CT#35 | CP-07001
4 | 0490 | 3 | IP domain connection indication | 7.4.0 | 7.5.0 | +| | | CP-07001
4 | 0491 | | Commands Marked Optional | | | +| | | CP-07001
4 | 0494 | 1 | Prevention of signalling overload due to Notifications | | | +| | | CP-07000
9 | 0497 | | Exclusion of use of inherited properties from network package | | | +| | | CP-07001
4 | 0498 | 1 | Changing Profile description Annex C from Informative to Normative | | | +| | | CP-07000
9 | 0501 | 1 | Signal List ID to Announcement Completed procedure | | | +| | | CP-07001
4 | 0508 | 1 | Stream ID parameters in Signals and Events | | | +| 2007-06 | CT#36 | CP-07031
4 | 0511 | 1 | IMSI/IMEI encoding in trace package | 7.5.0 | 7.6.0 | +| | | CP-07032 | 0512 | | Adding package ID to ASCII package | | | + +| Change history | | | | | | | | +|----------------|-------|----------|----|-----|-----------------|-----|-----| +| Date | TSG # | TSG Doc. | CR | Rev | Subject/Comment | Old | New | +| | | 2 | | | | | | + +| Change history | | | | | | | | +|----------------|-------|---------------|------|-----|-------------------------------------------------------------------------------------|-------|-------| +| Date | TSG # | TSG Doc. | CR | Rev | Subject/Comment | Old | New | +| | | CP-07032
2 | 0513 | | ServiceChangeMGCId parameter | | | +| | | CP-07030
8 | 0520 | | RFC 3309 for SCTP checksum | | | +| | | CP-07032
2 | 0522 | | Modification to EventID name definition | | | +| 2007-09 | CT#37 | CP-07053
0 | 0524 | 3 | Service Change Methods and Reasons | 7.6.0 | 7.7.0 | +| | | CP-07053
0 | 0527 | | H.248 Message Encoding | | | +| | | CP-07053
0 | 0528 | 1 | General Corrections To Profile | | | +| | | CP-07053
0 | 0531 | 2 | Mc profile corrections | | | +| | | CP-07053
0 | 0535 | 2 | Support inactivity timer (H.248.14) for MGWs detecting the failure of MGC | | | +| | | CP-07053
0 | 0537 | 1 | Completion of Text Telephony and Call Discrimination Packages | | | +| 2007-09 | CT#37 | CP-07056
9 | 0536 | 3 | Mandatory use termination heartbeat (H.248.36) when establish bearer/prepare bearer | 7.7.0 | 8.0.0 | +| 2007-10 | | | | | Track marks removed | 8.0.0 | 8.0.1 | +| 2007-12 | CT#38 | CP-07075
2 | 0538 | 2 | Mc enhancements for SIP-I support | 8.0.1 | 8.1.0 | +| | | CP-07075
6 | 0539 | 1 | Examples for Usage of the 3GUP Package "Initialization Direction" Property | | | +| | | CP-07075
6 | 0541 | 1 | Optional reporting of normal AAL2 bearer release | | | +| | | CP-07075
6 | 0556 | 1 | Individual audit of TDM termination | | | +| | | CP-07074
9 | 0545 | | Heartbeat event in Send Tone and Play Announcement procedures | | | +| | | CP-07074
9 | 0551 | 1 | Event Descriptor correction in Mc profile | | | +| | | CP-07074
9 | 0553 | | Reference corrections | | | +| | | CP-07074
9 | 0555 | 1 | Number of needed listener context terminations to ASCI package | | | +| | | CP-07074
0 | 0549 | 1 | Sequencing of Termination Out-of-Service and Termination Restoration procedures | | | +| 2008-03 | CT#39 | CP-08002
0 | 0557 | 1 | Reserve / Configure RTP Connection Point, Modify Bearer Characteristics | 8.1.0 | 8.2.0 | +| | | CP-08002
0 | 0558 | 1 | Other codecs for SIP-I based Nc | | | +| | | CP-08001
1 | 0562 | 1 | BNC events in Prepare Bearer / Establish Bearer procedures | | | +| | | CP-08002
5 | 0564 | | CAMEL prepaid warning tone missing from formats and codes table | | | +| | | CP-08002
0 | 0575 | 1 | Applicability of descriptors to RTP terminations | | | +| 2008-06 | CT#40 | CP-08027
0 | 0585 | | Coding of the UDP Port Property | 8.2.0 | 8.3.0 | +| | | CP-08026
9 | 0581 | 1 | Use of Release Bearer Procedure | | | +| | | CP-08027
1 | 0576 | 1 | Correction of the inconsistencies in several procedures' description | | | +| | | CP-08026
4 | 0577 | 2 | A interface over IP support | | | +| | | CP-08026
2 | 0578 | 1 | Addition of SIP-I based Nc within the scope of TS 29.232 | | | +| 2008-09 | CT#41 | CP-08046
6 | 0591 | 3 | IP interface type indicator | 8.3.0 | 8.4.0 | +| | | CP-08046
6 | 0592 | 1 | Use of Global Text Telephony with A over IP | | | +| | | CP-08046
6 | 0593 | | Use of 'plmnb' and 'gsm channel coding' in AoIP | | | +| | | CP-08046
1 | 0594 | 1 | Expansion of scope for IMS Centralised Service Access | | | +| | | CP-08046
6 | 0599 | | Support of GSM codec | | | +| | | CP-08046
8 | 0601 | | CTM properties setting | | | + +| Change history | | | | | | | | +|----------------|-------|---------------|------|-----|------------------------------------------------------------------------------------|--------|--------| +| Date | TSG # | TSG Doc. | CR | Rev | Subject/Comment | Old | New | +| | | CP-08046
6 | 0604 | 1 | Emergency Call Indication for AoIP and SIP-I terminations | | | +| | | CP-08045
3 | 0608 | | Service Change Reason in (G)MSC Server Out of Service | | | +| 2008-12 | CT#42 | CP-08068
6 | 0610 | 1 | SDP Media Parameters For RTP Terminations | 8.4.0 | 8.5.0 | +| | | CP-08070
5 | 0611 | 1 | IP transport package properties handling | | | +| | | CP-08069
7 | 0612 | 2 | No_Data frame handling independent of Stream Mode property | | | +| | | CP-08070
5 | 0613 | - | Adding package ID to 3G Interface Type package | | | +| | | | 0617 | 2 | Support of Redundancy for CSD in Mc interface for AoIP | | | +| | | | 0618 | 1 | CTM transport property in the Reserve and Configure RTP connection Point procedure | | | +| | | | 0621 | | IP interface type for external SIP-I based network | | | +| 2009-03 | CT#43 | CP-09003
4 | 0622 | - | Solving Incorrect references | 8.5.0 | 8.6.0 | +| | | | 0623 | | Removing of IP transport package from packages chapter of Mc profile | | | +| 2009-06 | CT#44 | CP-09029
7 | 0624 | 1 | Missing Signalling Object in Formats and Codes table | 8.6.0 | 8.7.0 | +| 2009-09 | CT#45 | CP-09054
1 | 0625 | | Clarification of Use of Reserve and Configure RTP Connection Point | 8.7.0 | 8.8.0 | +| | | CP-09054
1 | 0626 | 1 | Missing RTP procedures from Circuit Switched Data package description | | | +| | | CP-09054
4 | 0627 | - | Audit of Hanging Termination Detection package | | | +| 2009-12 | CT#46 | CP-09076
3 | 0628 | - | Commands Using IP Interface Type | 8.8.0 | 8.9.0 | +| 2009-12 | CT#46 | | | | Upgraded unchanged from Rel-8 | 8.9.0 | 9.0.0 | +| 2010-04 | | | | | History table corrected | 9.0.0 | 9.0.1 | +| 2011-03 | CT#51 | CP-11010
0 | 0629 | 1 | Adding CS-Ix functionalities to Mc-profile | 9.0.1 | 9.1.0 | +| 2011-03 | CT#51 | CP-11027
7 | 0630 | 10 | ECN Support in Mc Interface | 9.1.0 | 10.0.0 | +| 2011-03 | CT#51 | CP-11007
0 | 0631 | 1 | Complete Inactivity Timeout Indication Procedure | | | +| 2011-06 | CT#52 | CP-11036
8 | 0635 | 1 | ECN Failure improvements | 10.0.0 | 10.1.0 | +| | | CP-11036
8 | 0637 | 1 | Alignment of 3GPP profiles with SG16 ECN package definition | | | +| 2011-09 | CT#53 | CP-11056
3 | 0639 | - | Media inactivity notification procedure | 10.1.0 | 10.2.0 | +| 2011-12 | CT#54 | CP-11078
9 | 0640 | 1 | ECN Improvements | 10.2.0 | 10.3.0 | +| 2012-06 | CT#56 | CP-12022
6 | 0641 | 1 | Reference update: draft-ietf-avtcore-ecn-for-rtp | 10.3.0 | 10.4.0 | +| 2012-09 | CT#57 | CP-12047
8 | 0642 | 1 | Support of Multimedia Priority Service (MPS) over Mc Interface – Stage 3 | 10.4.0 | 11.0.0 | +| 2012-12 | CT#58 | CP-12072
3 | 0646 | - | Mc interface updates of ECN Support Package | 11.0.0 | 11.1.0 | +| 2012-12 | CT#58 | CP-12072
7 | 0648 | 1 | H.248.52 Status Update | 11.0.0 | 11.1.0 | +| 2013-06 | CT#60 | CP-13029
4 | 0650 | 2 | ECN relying reference change | 11.1.0 | 11.2.0 | \ No newline at end of file diff --git a/marked/Rel-11/29_series/29234/02dfdcd208dbdc8fa4f645885e59dd17_img.jpg b/marked/Rel-11/29_series/29234/02dfdcd208dbdc8fa4f645885e59dd17_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a6244ff02eb58fe8c6ee165afbebafb0452d605a --- /dev/null +++ b/marked/Rel-11/29_series/29234/02dfdcd208dbdc8fa4f645885e59dd17_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6e5be515c3e8bec1a275e743e82ef0a4e0a00369d4c44d42a8ac795ed216c582 +size 76564 diff --git a/marked/Rel-11/29_series/29234/11f18bf0233d812ad2604f88f3385d60_img.jpg b/marked/Rel-11/29_series/29234/11f18bf0233d812ad2604f88f3385d60_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..50850269563a4bd52d21d3362faf2d0c9855e87c --- /dev/null +++ b/marked/Rel-11/29_series/29234/11f18bf0233d812ad2604f88f3385d60_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7d634fccc11eaa3e66533800b18bc3c5d976cea8aa1b504b164ef6a80ea71088 +size 124515 diff --git a/marked/Rel-11/29_series/29234/1e5a58dcaf0936bf18dc3dd0d9cd43ff_img.jpg b/marked/Rel-11/29_series/29234/1e5a58dcaf0936bf18dc3dd0d9cd43ff_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5ef523766054008dea0d4404ab12a04ef05def2d --- /dev/null +++ b/marked/Rel-11/29_series/29234/1e5a58dcaf0936bf18dc3dd0d9cd43ff_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ef53575565c0477f844a34d51afaf34905a85d5ef94b9cf17c7cb63495cf5351 +size 92393 diff --git a/marked/Rel-11/29_series/29234/d2417b04116c354deccb25d98a84a0fb_img.jpg b/marked/Rel-11/29_series/29234/d2417b04116c354deccb25d98a84a0fb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0da340753720af2085ee2d65cd9797968ccd985a --- /dev/null +++ b/marked/Rel-11/29_series/29234/d2417b04116c354deccb25d98a84a0fb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:062a0d44b36d4a9249c3c80594447611a07f0f324dbed4f18cc496c97c845e91 +size 108007 diff --git a/marked/Rel-11/29_series/29234/e60c2d24a97a2855d98671d27ea43d0f_img.jpg b/marked/Rel-11/29_series/29234/e60c2d24a97a2855d98671d27ea43d0f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ecd39f91b25ba11226df546e61cca96d8c72d64a --- /dev/null +++ b/marked/Rel-11/29_series/29234/e60c2d24a97a2855d98671d27ea43d0f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8ce705bcfd4834f60d871c3a17d0baa169a46bb05dc5ee14daa4b4139195f9aa +size 68779 diff --git a/marked/Rel-11/29_series/29234/ffe0fef452a0ae9a20253c319c54e13c_img.jpg b/marked/Rel-11/29_series/29234/ffe0fef452a0ae9a20253c319c54e13c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2bea676f3b4431d9fc68ad0ede8ec2de9e98d87d --- /dev/null +++ b/marked/Rel-11/29_series/29234/ffe0fef452a0ae9a20253c319c54e13c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:028b1a43f677952656ddf04d7f9bee3dcbaf12d9f943edb09d7ad60d203dfd61 +size 61000 diff --git a/marked/Rel-11/29_series/29234/raw.md b/marked/Rel-11/29_series/29234/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..cbe90a508542b74b465457c14d67d14c9f56a778 --- /dev/null +++ b/marked/Rel-11/29_series/29234/raw.md @@ -0,0 +1,3816 @@ + + + + + + +# Contents + +| | | +|----------------------------------------------------------------------------------------------------------|----| +| Foreword ..... | 7 | +| 1 Scope..... | 8 | +| 2 References..... | 8 | +| 3 Definitions, symbols and abbreviations ..... | 10 | +| 3.1 Definitions..... | 10 | +| 3.2 Symbols..... | 10 | +| 3.3 Abbreviations ..... | 10 | +| 4 Wa Description ..... | 11 | +| 4.1 Functionality..... | 11 | +| 4.2 Protocols..... | 11 | +| 4.3 Procedures Description ..... | 12 | +| 4.3.1 WLAN Access Authentication and Authorization ..... | 12 | +| 4.3.1.1 WLAN Access Authentication and Authorization for the Emergency Case..... | 13 | +| 4.3.2 Immediate Purging of a User from WLAN access..... | 13 | +| 4.3.2.1 Emergency Case ..... | 14 | +| 4.3.3 Ending a Session..... | 14 | +| 4.3.4 WLAN Access Authorization Information Update Procedure..... | 14 | +| 4.4 Information Element Contents ..... | 16 | +| 4.4.1 RADIUS based Information Elements Contents ..... | 16 | +| 4.4.2 Diameter based Information Elements Contents ..... | 18 | +| 4.4.2.1 DER and DEA Commands ..... | 18 | +| 4.4.2.2 Abort Session Request and Answer AVPs ..... | 19 | +| 4.4.2.3 Session Termination Request and Answer AVPs..... | 19 | +| 4.4.2.4 Re-Auth Request and Answer AVPs..... | 20 | +| 4.5 Accounting Signalling Across the Wa interface ..... | 20 | +| 4.5.1 RADIUS ..... | 20 | +| 4.5.1.1 RADIUS Attributes in accounting messages..... | 20 | +| 4.5.2 Diameter ..... | 22 | +| 4.5.2.1 Procedures Description ..... | 22 | +| 4.5.2.2 Information Element Contents..... | 23 | +| 5 Wd Description ..... | 25 | +| 5.1 Functionality..... | 25 | +| 5.2 Protocols..... | 25 | +| 5.3 3GPP AAA Proxy and 3GPP AAA Server behaviour when Interworking with RADIUS/Diameter
WLAN ANs..... | 26 | +| 5.3.1 Requirements in 3GPP AAA Proxy for RADIUS/Diameter "Translation Agent"..... | 26 | +| 5.3.1.1 Conversion of RADIUS Request to Diameter Request..... | 27 | +| 5.3.1.2 Conversion of Diameter Response to RADIUS Response ..... | 27 | +| 5.3.1.3 3GPP AAA Proxy advertisement of RADIUS or Diameter client to 3GPP AAA Server..... | 27 | +| 5.3.1.4 Managing the transaction state and session state information ..... | 28 | +| 5.4 Procedures description ..... | 28 | +| 5.4.1 WLAN Access Authentication and Authorization ..... | 28 | +| 5.4.2 Immediate Purging of a User from WLAN access..... | 30 | +| 5.4.3 Ending a Session..... | 31 | +| 5.4.4 Authorization Information Update Procedure ..... | 31 | +| 5.5 Information Elements Contents..... | 31 | +| 5.5.1 Authentication Procedures..... | 31 | +| 5.5.2 Abort Session Requests and Answer AVPs ..... | 32 | +| 5.5.3 Session Termination Request and Answer AVPs ..... | 32 | +| 5.5.3A Authorization Information Update Procedure ..... | 32 | +| 5.5.4 RADIUS based Information Elements Contents for Authentication and Authorization..... | 33 | +| 5.5.5 RADIUS based Information Elements Contents for Accounting..... | 35 | +| 6 Wx Description ..... | 37 | +| 6.1 Functionality..... | 37 | +| 6.2 Protocols..... | 37 | + +| | | | +|-----------|---------------------------------------------------------------------|----| +| 6.3 | Procedures Description ..... | 37 | +| 6.3.1 | Authentication Procedures..... | 37 | +| 6.3.1.1 | Detailed behaviour ..... | 40 | +| 6.3.2 | Location Management Procedures ..... | 41 | +| 6.3.2.1 | WLAN Registration/DeRegistration Notification ..... | 41 | +| 6.3.2.1.1 | Detailed behaviour ..... | 42 | +| 6.3.2.2 | Network Initiated De-Registration by HSS, Administrative ..... | 43 | +| 6.3.2.2.1 | Detailed behaviour ..... | 43 | +| 6.3.3 | User Data Handling ..... | 43 | +| 6.3.3.1 | Void ..... | 43 | +| 6.3.3.2 | HSS Initiated Update of User Profile ..... | 44 | +| 6.3.3.2.1 | Detailed behaviour ..... | 44 | +| 6.4 | Information Elements Contents..... | 45 | +| 6.4.1 | Authentication Procedures..... | 45 | +| 6.4.2 | HSS Initiated Update of User Profile ..... | 45 | +| 6.4.3 | Registration procedure and Profile download in Wx ..... | 46 | +| 6.4.4 | Registration Termination in Wx..... | 47 | +| 6.5 | Void..... | 47 | +| 6.6 | User identity to HSS resolution..... | 47 | +| 7 | Void..... | 47 | +| 8 | Wm Description ..... | 48 | +| 8.1 | Functionality..... | 48 | +| 8.2 | Protocols..... | 48 | +| 8.3 | Procedures Description ..... | 48 | +| 8.3.1 | Authentication and Authorization Procedures..... | 48 | +| 8.3.1.1 | 3GPP AAA Server Detailed Behaviour ..... | 50 | +| 8.3.1.2 | 3GPP AAA Proxy Detailed Behaviour..... | 51 | +| 8.3.1.3 | Authentication Procedures for the Emergency Case ..... | 52 | +| 8.3.2 | Authorization Procedures ..... | 52 | +| 8.3.2.1 | 3GPP AAA Server Detailed Behaviour ..... | 54 | +| 8.3.2.2 | AAA Proxy Detailed Behaviour..... | 56 | +| 8.3.2.3 | Authorization Procedures in the Emergency Case ..... | 56 | +| 8.3.2.3.1 | PDG Procedures ..... | 56 | +| 8.3.2.3.2 | 3GPP AAA Server Procedures..... | 56 | +| 8.3.3 | PDG Initiated Session Termination Procedure..... | 57 | +| 8.3.3.1 | 3GPP AAA Server Detailed behaviour ..... | 57 | +| 8.3.3.2 | 3GPP AAA Proxy Detailed Behaviour..... | 57 | +| 8.3.3.3 | PDG Initiated Session Termination Procedure in Emergency Case ..... | 57 | +| 8.3.4 | 3GPP AAA Server Initiated Tunnel Disconnect Procedure..... | 58 | +| 8.3.4.1 | Detailed Behaviour ..... | 58 | +| 8.3.4.2 | 3GPP AAA Proxy Behaviour ..... | 58 | +| 8.3.5 | Access and Service Authorization information Update Procedure ..... | 59 | +| 8.3.5.1 | Detailed behaviour ..... | 60 | +| 8.4 | Information Element Contents ..... | 60 | +| 8.4.1 | Authentication Request/Answer Messages ..... | 60 | +| 8.4.2 | Authorization Procedures ..... | 61 | +| 8.4.3 | PDG Initiated Session Termination Procedure..... | 63 | +| 8.4.4 | 3GPP AAA Server Initiated Tunnel Disconnect Procedure..... | 64 | +| 8.4.5 | Access and Service Authorization Information Update Procedure ..... | 64 | +| 9 | Wg Description ..... | 65 | +| 9.1 | Functionality..... | 65 | +| 9.2 | Protocols..... | 65 | +| 9.3 | Procedures Description ..... | 65 | +| 9.3.1 | Policy Download Procedures ..... | 65 | +| 9.3.1.1 | WAG Detailed Behaviour..... | 66 | +| 9.3.2 | Routing Policy Cancellation Procedure..... | 66 | +| 9.3.2.1 | Detailed Behaviour ..... | 67 | +| 9.3.3 | WAG Initiated Routing Policy Cancellation Procedure..... | 67 | +| 9.3.3.1 | Detailed Behaviour ..... | 67 | +| 9.4 | Information Element Contents ..... | 68 | + +| | | | +|----------|---------------------------------------------------------------|----| +| 9.4.1 | Policy Download Procedures ..... | 68 | +| 9.4.2 | Routing Policy Cancellation Procedure..... | 69 | +| 9.4.3 | WAG Initiated Routing Policy Cancellation Procedure..... | 70 | +| 10 | Information Elements Contents ..... | 71 | +| 10.1 | AVPs ..... | 71 | +| 10.1.1 | Auth-Session-State ..... | 71 | +| 10.1.2 | User-Name..... | 71 | +| 10.1.3 | Visited-Network-Identifier ..... | 72 | +| 10.1.4 | SIP-Auth-Data-Item ..... | 72 | +| 10.1.5 | Authentication-Method..... | 72 | +| 10.1.6 | Authentication-Information-SIM ..... | 72 | +| 10.1.7 | Authorization -Information-SIM ..... | 72 | +| 10.1.8 | WLAN-User-Data ..... | 72 | +| 10.1.9 | Void ..... | 73 | +| 10.1.10 | Charging-Data ..... | 73 | +| 10.1.11 | WLAN-Access ..... | 73 | +| 10.1.12 | WLAN-3GPP-IP-Access ..... | 73 | +| 10.1.13 | Session-Timeout..... | 73 | +| 10.1.14 | APN-Authorized..... | 73 | +| 10.1.15 | 3GPP-WLAN-APN-Id ..... | 74 | +| 10.1.16 | APN-Barring-Type ..... | 74 | +| 10.1.17 | WLAN Direct IP Access ..... | 74 | +| 10.1.18 | Server-Assignment-Type..... | 75 | +| 10.1.19 | Deregistration-Reason ..... | 75 | +| 10.1.20 | EAP-Payload ..... | 75 | +| 10.1.21 | Auth Req Type ..... | 75 | +| 10.1.22 | EAP-Master-Session-Key..... | 75 | +| 10.1.23 | Session-Request-Type ..... | 75 | +| 10.1.24 | Routing-Policy..... | 75 | +| 10.1.25 | Subscription-ID ..... | 76 | +| 10.1.26 | Max-Requested-Bandwidth..... | 76 | +| 10.1.27 | Charging-Characteristics ..... | 76 | +| 10.1.28 | Charging-Nodes..... | 76 | +| 10.1.29 | Primary-OCS-Charging-Function-Name ..... | 76 | +| 10.1.30 | Secondary-OCS-Charging-Function-Name ..... | 76 | +| 10.1.31 | Secondary-Charging-Collection-Function-Name..... | 77 | +| 10.1.32 | Framed-IP-Address..... | 77 | +| 10.1.33 | Framed-IPv6-Prefix ..... | 77 | +| 10.1.34 | 3GPP-AAA-Server-Name ..... | 77 | +| 10.1.35 | Void ..... | 77 | +| 10.1.36 | Primary-Charging-Collection-Function-Name..... | 77 | +| 10.1.37 | NAS-Port-Type..... | 77 | +| 10.1.38 | Maximum-Number-Accesses ..... | 77 | +| 10.1.39 | WLAN-Session-Id ..... | 77 | +| 10.1.40 | PDG-Charging-Id ..... | 78 | +| 10.1.41. | 3GPP-WLAN-QoS-Filter-Rule ..... | 78 | +| 10.1.42. | QoS-Resources ..... | 78 | +| 10.1.43 | QoS-Capability ..... | 78 | +| 10.1.44 | 3GPP-WLAN-QoS-Filter-Support ..... | 78 | +| 10.2 | Handling of Information Elements..... | 79 | +| 10.3 | Result-Code AVP values..... | 79 | +| 10.3.1 | Permanent Failures ..... | 80 | +| 10.3.1.1 | DIAMETER_ERROR_USER_NO_WLAN_SUBSCRIPTION (5041)..... | 80 | +| 10.3.1.2 | DIAMETER_ERROR_W-APN_UNUSED_BY_USER (5042)..... | 80 | +| 10.3.1.3 | DIAMETER_ERROR_NO_ACCESS_INDEPENDENT_SUBSCRIPTION (5043)..... | 80 | +| 10.3.1.4 | DIAMETER_ERROR_USER_NO_W-APN_SUBSCRIPTION (5044) ..... | 80 | +| 11 | Pr Description ..... | 81 | +| 11.1 | Functionality..... | 81 | +| 11.2 | Protocols..... | 81 | +| 11.3 | Procedures Description ..... | 81 | + +| | | | +|-------------------------------|---------------------------------------------------------------------|-----------| +| 11.3.1 | WLAN Attach/Detach Indication..... | 81 | +| 11.3.1.1 | Detailed behaviour ..... | 82 | +| 11.3.2 | W-APN Activation/De-Activation Indication ..... | 83 | +| 11.3.2.1 | W-APN Activation Indication..... | 83 | +| 11.3.2.1.1 | Detailed behaviour ..... | 83 | +| 11.3.2.2 | W-APN De-Activation Indication..... | 84 | +| 11.3.2.2.1 | Detailed behaviour ..... | 84 | +| 11.4 | Information Elements Contents..... | 84 | +| 11.4.1 | WLAN Attach/Detach Indication..... | 84 | +| 11.4.2 | W-APN Activation/DeActivation Indication ..... | 85 | +| 11.4.2.1 | W-APN Activation Indication ..... | 85 | +| 11.4.2.2 | W-APN Deactivation Indication..... | 86 | +| 12 | User identity to HSS resolution..... | 87 | +| Annex A (normative): | Wa and Wd Procedures Signalling Flows..... | 88 | +| A.1 | Authentication, Authorization and Key Delivery ..... | 88 | +| A.2 | Immediate Purging of a WLAN User from the WLAN Access Network ..... | 93 | +| Annex B (Informative): | Network configuration information ..... | 96 | +| Annex C (informative): | Change history..... | 97 | + +# --- Foreword + +This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +# --- 1 Scope + +The present document defines the stage-3 protocol description for several reference points in the WLAN-3GPP Interworking System. + +The present document is applicable to: + +- The Dw reference point between the 3GPP AAA Server and an SLF. +- The Wa reference point between the WLAN AN and the 3GPP AAA Proxy. +- The Wd reference point between the 3GPP AAA Proxy and 3GPP AAA Server. +- The Wx reference point between the 3GPP AAA Server and the HSS. +- The Wm reference point between the 3GPP AAA Server and the PDG. +- The Wg reference point between the 3GPP AAA Server/Proxy and the WAG. +- The Pr reference point between the 3GPP AAA Server and the PNA. + +# --- 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 TR 22.934: "Feasibility study on 3GPP system to Wireless Local Area Network (WLAN) interworking". +- [3] 3GPP TR 23.934: "3GPP system to Wireless Local Area Network (WLAN) interworking; Functional and architectural definition". +- [4] 3GPP TS 23.234: "3GPP system to Wireless Local Area Network (WLAN) interworking; System description". +- [5] 3GPP TS 29.228: "IP Multimedia (IM) Subsystem Cx and Dx interfaces; Signalling flows and message contents". +- [6] 3GPP TS 29.229: "Cx and Dx interfaces based on the Diameter protocol; Protocol details". +- [7] IETF RFC 3588: "Diameter Base Protocol". +- [8] IETF RFC 4072: "Diameter Extensible Authentication Protocol (EAP) Application". +- [9] IETF RFC 2869: "RADIUS Extensions". +- [10] Void +- [11] IETF RFC 3748: "Extensible Authentication Protocol (EAP) ". +- [12] IETF RFC 4005: "Diameter Network Access Server Application". + +- [13] IETF RFC 3576: "Dynamic Extensions to Remote Authentication Dial In User Service (RADIUS)". +- [14] IETF RFC 3579: "RADIUS (Remote Authentication Dial-In User Service) Support For Extensible Authentication Protocol (EAP) ". +- [15] IETF RFC 3580: "IEEE 802.1X Remote Authentication Dial In User Service (RADIUS) Usage Guidelines". +- [16] IETF RFC 5580: "Carrying Location Objects in RADIUS and Diameter ". +- [17] IETF RFC 2865: "Remote Authentication Dial In User Service (RADIUS)". +- [18] 3GPP TS 33.234: "3G security; Wireless Local Area Network (WLAN) interworking security". +- [19] IETF RFC 4006: "Diameter Credit-control Application". +- [20] IETF RFC 2866: "RADIUS Accounting". +- [21] IETF RFC 3748: "Extensible Authentication Protocol (EAP)". +- [22] 3GPP TS 23.003: "Numbering, addressing and identification". +- [23] 3GPP TS 32.240: "Charging architecture and principles". +- [24] 3GPP TS 32.215: "Charging data description for the Packet Switched (PS) domain". +- [25] GSMA PRD IR.61: "WLAN Roaming Guidelines". +- [26] IETF RFC 4372: "Chargeable User Identity". +- [27] Void +- [28] IETF RFC 4186: "Extensible Authentication Protocol Method for GSM Subscriber Identity Modules (EAP-SIM)" . +- [29] IETF RFC 4187: "Extensible Authentication Protocol Method for 3rd Generation Authentication and Key Agreement (EAP-AKA)". +- [30] IETF RFC 4849: "RADIUS Filter Rule Attribute". +- [31] 3GPP TS 23.141: "Presence Service; Architecture and functional description". +- [32] 3GPP TS 32.299: "Telecommunication management; Charging management; Diameter charging applications". +- [33] 3GPP TS 32.252: "Telecommunication management; Charging management; Wireless Local Area Network (WLAN) charging". +- [34] Void +- [35] IETF RFC 5777: "Quality of Service Attributes for Diameter". +- [36] IETF RFC 5729: "Clarifications on the Routing of Diameter Requests Based on the Username and the Realm". +- [37] IETF RFC 5216 (March 2008): "The EAP-TLS Authentication Protocol". +- [38] 3GPP TS 24.234: "3GPP System to Wireless Local Area Network (WLAN) interworking; WLAN User Equipment (WLAN UE) to network protocols". +- [39] IETF RFC 5080 (December 2007): "Common Remote Authentication Dial In User Service (RADIUS) Implementation Issues and Suggested Fixes". + +# 3 Definitions, symbols and abbreviations + +## 3.1 Definitions + +For the purposes of the present document, the following terms and definitions given in 3GPP TS 23.234 [4] apply. + +3GPP - WLAN Interworking + External IP Network/External Packet Data Network + Home WLAN + Interworking WLAN + Offline charging + Online charging + PS based services + Service Authorization + Visited WLAN + WLAN-UE + +In addition, for the purposes of the present document, the following terms and definitions given in 3GPP TS 23.141 [31] apply. + +Presence Network Agent + +## 3.2 Symbols + +For the purposes of the present document, the following symbols apply: + +| | | +|----|------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Dw | Reference point between the 3GPP AAA Server and an SLF | +| Wa | Reference point between a WLAN Access Network and a 3GPP AAA Proxy in the roaming case and a 3GPP AAA Server in the Non-Roaming case (charging and control signalling) | +| Wd | reference point between a 3GPP AAA Proxy and a 3GPP AAA Server (charging and control signalling) | +| Wg | Reference point between a 3GPP AAA Server/Proxy and a 3GPP WAG | +| Wm | Reference point between a Packet Data Gateway and a 3GPP AAA Server | +| Wn | Reference point between a WLAN Access Network and a 3GPP WAG | +| Wx | Reference point between an HSS and a 3GPP AAA Server | +| Pr | Reference point between a 3GPP AAA Server and a PNA | + +## 3.3 Abbreviations + +For the purposes of the present document, the following abbreviations apply: + +| | | +|---------|----------------------------------------------| +| AAA | Authentication, Authorization and Accounting | +| AVP | Attribute Value Pair | +| CCF | Charging Collection Function | +| CG | Charging Gateway | +| EAP | Extensible Authentication Protocol | +| HSS | Home Subscriber Server | +| IMS | IP Multimedia Subsystem | +| OCS | On-line Charging System | +| PDG | Packet Data Gateway | +| PNA | Presence Network Agent | +| RADIUS | Remote Authentication Dial-In User Service | +| WAG | WLAN Access Gateway | +| WLAN AN | WLAN Access Network | +| WLAN | Wireless Local Area Network | +| WLAN-UE | WLAN User Equipment | + +# --- 4 Wa Description + +## 4.1 Functionality + +The Wa reference point is defined between the I-WLAN and the 3GPP AAA Server or 3GPP AAA Proxy. The description of the reference point and its functionality is given in 3GPP TS 23.234 [4]. + +## 4.2 Protocols + +The Wa reference point inter-works between 3GPP networks and WLAN ANs. In early deployments of WLAN-3GPP inter-working, a significant amount of WLAN ANs will provide RADIUS-based interfaces. It is expected that WLAN ANs will migrate gradually towards Diameter-based interfaces. + +Therefore, in order to inter-work with the two kinds of WLAN ANs, the 3GPP AAA Proxy in the roaming case and the 3GPP AAA Server in the non-roaming case, both have to support Diameter-based and RADIUS-based protocols at the Wa reference point towards WLAN ANs. + +Therefore the Wa reference point shall contain the following protocols: + +- 1) RADIUS, as defined in IETF RFC 2865 [17], including the following extensions: + - IETF RFC 3579 [14], which provides RADIUS extensions to support the transport of EAP frames over RADIUS. + - IETF RFC 5580 [16], which provides RADIUS and Diameter Extensions for Public WLAN which are used in order to identify uniquely the owner and location of the WLAN. + - IETF RFC 3576 [13], which provides RADIUS extensions to support, amongst other capabilities, the capability to immediately disconnect a user from the WLAN AN. + - IETF RFC 4849 "RADIUS Filter Rule Attribute" [30], which provides RADIUS Extensions for Public WLAN including attributes to provide filtering and routing enforcement. + - IETF RFC 4372 "Chargeable User Identity" [26], which provides RADIUS Extensions for carrying a chargeable user identity from the Home PLMN to the WLAN AN. +- 2) Diameter Base, as defined in IETF RFC 3588 [7], including the following additional specifications: + - IETF RFC 4072 [8], which provides a Diameter application to support the transport of EAP (IETF RFC 3748 [21]) frames over Diameter. + - IETF RFC 4005 [12], which defines a Diameter protocol application used for Authentication, Authorization and Accounting (AAA) services in the Network Access Server (NAS) environment. + - IETF RFC 5580 [16], which provides RADIUS and Diameter Extensions for Public WLAN which are used in order to uniquely identify the owner and location of the WLAN. + - IETF RFC 5729 [36], which defines the procedures related to the routing of Diameter requests when the User-Name AVP contains a Decorated NAI as defined in 3GPP TS 23.003 [22]. + +The 3GPP AAA Proxy in the roaming case and 3GPP AAA Server in the non-roaming case shall support both 1) and 2) over Wa reference point. + +WLAN ANs, depending on their characteristics, shall use either 1) or 2) over Wa reference point. + +The Application-Id to be advertised over Wa reference point corresponds to the EAP or Diameter Base Protocol Application-Id, depending on the command sent over Wa. + +## 4.3 Procedures Description + +### 4.3.1 WLAN Access Authentication and Authorization + +This procedure is used to transport over RADIUS or Diameter, the WLAN Access (Re)Authentication and Authorization between the WLAN AN and the 3GPP AAA Proxy or Server. + +Diameter usage in Wa: + +- This procedure is mapped to the Diameter-EAP-Request and Diameter-EAP-Answer command codes specified in IETF RFC 4072 [8]. +- If the User-Name AVP contains a Decorated NAI as defined in 3GPP TS 23.003 [22], then the Diameter request routing shall follow the procedures defined in IETF RFC 5729 [36]. +- For (re)authentication procedures, the messaging described below is reused. + +**Table 4.3.1.1: WLAN Access Authentication and Authorization request** + +| Information element name | Mapping to Diameter AVP | Cat. | Description | +|---------------------------------|-------------------------|------|---------------------------------------------------------------------------------------------------------------------------------| +| User Identity | User-Name | M | This information element contains the identity of the user. | +| EAP payload | EAP-payload | M | Encapsulated EAP payload used for WLAN UE-3GPP AAA Server mutual authentication | +| Authentication Request Type | Auth Request-Type | M | Defines whether the user is to be authenticated only, authorized only or both. AUTHORIZE_AUTHENTICATE is required in this case. | +| NAS-IP address | NAS-IP Address | C | IP address of the hot-spot | +| NAS-Ipv6 address | NAS-Ipv6 address | C | Ipv6 address of the hot-spot | +| WLAN UE MAC address | Calling Station-ID | M | Carries the MAC address of the WLAN-UE. | +| Supported 3GPP WLAN QoS profile | QoS-Capability | O | If the WLAN AN supports QoS mechanisms, this information element may be included to contain the WLAN AN's QoS capabilities. | + +**Table 4.3.1.2: WLAN Access Authentication and Authorization response** + +| Information element name | Mapping to Diameter AVP | Cat. | Description | +|----------------------------------|-----------------------------|------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| User Identity | User-Name | M | This information element contains the identity of the user. | +| EAP payload | EAP payload | M | Encapsulated EAP payload used for UE- 3GPP AAA Server mutual authentication | +| Result code | Result-Code | M | Result of the operation. Result codes are as per in NASREQ. 1xxx should be used for multi-round, 2xxx for success. | +| Session Alive Time | Session-Timeout | O | Max no of seconds the user session should remain active | +| Accounting Interim - Interval | Accounting Interim-Interval | O | Charging duration | +| Pairwise Master Key | EAP-Master-Session-Key | C | Shall be sent if Result Code is set to "Success". | +| Filter Id | Filter-Id | O | This IE indicates the name of the filter list for the user. | +| NAS Filter Rule | NAS-Filter-Rule | O | This IE provides filter rules that need to be configured on the NAS for the user by 3GPP Server/Proxy. | +| Tunneling | Tunneling | O | This IE can be used to provide needed tunnelling configuration on the NAS for the user by 3GPP Server/Proxy. | +| Authorized 3GPP WLAN QoS profile | QoS - Resources | O | If both supported 3GPP WLAN QoS profile of the WLAN AN and subscribed QoS profile were received by the 3GPP AAA Server, this IE may be present.
This IE contains the 3GPP WLAN QoS Profile authorized by the 3GPP AAA Server based on the subscribed QoS parameters from the HSS, WLAN AN's QoS capabilities and other information, e.g. operators' policies. | + +RADIUS usage in Wa: + +- This procedure is mapped to the RADIUS Access Request, RADIUS Access Challenge, RADIUS Access Accept and RADIUS Access Reject specified in IETF RFC 3579 [14]. + +See Annex A.1 for signalling flow reference and section 4.4.1 for the RADIUS profiles for these messages. + +#### 4.3.1.1 WLAN Access Authentication and Authorization for the Emergency Case + +On receipt of a WLAN Access and Authentication Request from the WLAN AN with the realm part of the NAI in the User Identity populated with the emergency specific realm as defined in 3GPP TS 23.003 [22], the access authentication and authorization shall proceed as described in subclause 4.3.1 with the following exceptions: + +The 3GPP AAA Server shall set the Emergency\_Access flag and proceed with authentication. + +In order to support WLAN UE not equipped with a UICC for emergency service, as described in 3GPP TS 23.234 [4], the 3GPP AAA server shall support extensible authentication protocol (EAP) as specified in IETF RFC 3748 [21] and EAP TLS based authentication as specified in IETF RFC 5216 [37]. + +With the realm part of the NAI in the User Identity populated with the emergency specific realm as defined in 3GPP TS 23.003[22], the 3GPP AAA Server identifies that the user is requesting for an emergency call, based on the received identity. The 3GPP AAA Server shall set the Emergency\_Access flag. The 3GPP AAA server shall send an EAP-Request/TLS message (with the TLS start bit set and no data as specified in IETF RFC 5216 [37]) in order to initiate EAP TLS based authentication. + +Upon receipt of the EAP-Response/TLS message, the 3GPP AAA server checks the validity of the response. If the check is successful, the 3GPP AAA server shall complete the authentication procedure by sending the EAP-Success message. + +NOTE 1: It is open how to proceed if authentication fails but national regulations require the 3GPP AAA Server to proceed and grant access to the WLAN UE. It is FFS how to handle this requirement, in particular what PMK is sent to the WLAN AN. + +The 3GPP AAA Server shall prioritize this access over other accesses, where possible (e.g. expedite the signalling procedures in this case over those of normal accesses). + +### 4.3.2 Immediate Purging of a User from WLAN access + +This procedure is used to communicate between the WLAN AN and the 3GPP AAA Proxy that the 3GPP AAA Server has decided that a specific WLAN-UE shall be disconnected from accessing the WLAN interworking service. The procedure is Diameter or RADIUS based. In RADIUS case, the WLAN AN and the 3GPP AAA Proxy shall support the Disconnect Messages specified in RFC 3576 [13] in order to enable such a procedure. Diameter usage in Wa: + +- This procedure is mapped to the Diameter command codes Diameter-Abort-Session-Request and Diameter-Abort-Session-Answer specified in RFC 3588 [7]. Information element content for these messages are shown in tables 4.3.2.1 and 4.3.2.2. + +**Table 4.3.2.1: Information Elements passed in ASR message** + +| Information element name | Mapping to Diameter AVP | Cat. | Description | +|--------------------------|-------------------------|------|-------------------------------------------------------------| +| User Identity | User-Name | M | This information element contains the identity of the user. | + +**Table 4.3.2.2: Information Elements passed in ASA message** + +| Information element name | Mapping to Diameter AVP | Cat. | Description | +|--------------------------|-------------------------|------|-------------------------------------------------------------| +| User Identity | User-Name | M | This information element contains the identity of the user. | +| Result-Code | Result-Code | M | Result of the operation. | + +See Annex A.2 for signalling flow reference. + +RADIUS usage in Wa: + +- This procedure is mapped to the RADIUS messages Disconnect-Request and Disconnect-Response specified in RFC 3576 [13]. + +#### 4.3.2.1 Emergency Case + +The 3GPP AAA Server shall give preferential treatment to WLAN UEs that have access for emergency purposes in scenarios including (but not necessarily limited to) network overload (where the 3GPP AAA Server uses the Purging procedure). + +NOTE: It is FFS under what criteria if any, the 3GPP AAA Server shall use this procedure in the emergency case. In principle, 3GPP AAA Server shall not use this procedure, or shall do so only in very restricted circumstances. + +### 4.3.3 Ending a Session + +Session termination is initiated when the WLAN-AN needs to inform the 3GPP AAA Server of the WLAN-UEs disconnection from the hot-spot. This occurs via the Session Termination Request (STR) and Session Termination Answer commands (STA) from the base protocol RFC 3588 [7]. Information elements to be carried in the STR, STA messages are shown in tables 4.4.3.1 and 4.4.3.2. + +**Table 4.3.3.1: Information Elements passed in STR message** + +| Information element name | Mapping to Diameter AVP | Cat. | Description | +|--------------------------|-------------------------|------|-------------------------------------------------------------| +| User Identity | User-Name | M | This information element contains the identity of the user. | +| Termination-Cause | Termination Cause | M | Reason for termination of the session. | + +**Table 4.3.3.2: Information Elements passed in STA message** + +| Information element name | Mapping to Diameter AVP | Cat. | Description | +|--------------------------|-------------------------|------|-------------------------------------------------------------| +| User Identity | User-Name | M | This information element contains the identity of the user. | +| Result Code | Result-Code | M | Informs of success or failure of the procedure. | + +RADIUS usage in Wa: + +- This procedure is triggered by the last RADIUS Accounting Request of Acct.Status Type STOP correlated with this session. + +### 4.3.4 WLAN Access Authorization Information Update Procedure + +The WLAN access authorization information update procedure is used to modify the authorization parameters provided to the WLAN AN. This procedure is invoked by the 3GPP AAA Server when the subscriber's access authorization information has been modified and needs to be sent to the WLAN AN. The WLAN access authorization information update procedure shall trigger a new WLAN access authentication and authorization procedure towards to the WLAN-UE. This may happen due to a modification of WLAN subscriber profile in the HSS. + +The procedure is Diameter or RADIUS based. + +Diameter usage in Wa: + +This procedure is performed in two steps: + +- The 3GPP AAA server issues an unsolicited re-authentication and re-authorization request towards the WLAN AN. Upon receipt of such a request, the WLAN AN shall respond to the request and indicate the disposition of the request. This procedure is mapped to the Diameter command codes Re-Auth-Request and Re-Auth-Answer specified in RFC 3588 [7]. Information element content for these messages are shown in tables 4.3.4.1 and 4.3.4.2. +- Receiving the re-authentication and re-authorization request, the WLAN AN shall initiate a re-authentication procedure towards the WLAN-UE and shall then invoke the WLAN access authentication and authorization procedure as described in the section 4.3.1. Information element content for these messages are shown in tables 4.3.1.1 and 4.3.1.2. + +**Table 4.3.4.1: Re-Authentication and Re-Authorization request** + +| Information element name | Mapping to Diameter AVP | Cat. | Description | +|--------------------------|-------------------------|------|---------------------------------------------------------------------------------------------------------------------------------------| +| User Identity | User-Name | M | This information element contains the identity of the user. | +| Re-Auth Request Type | Re-Auth-Request-Type | M | Defines whether the user is to be re-authenticated only, re-authorized only or both. AUTHORIZE_AUTHENTICATE is required in this case. | +| Routing Information | Destination-Host | M | This information element is obtained from the Origin-Host AVP, which was included in a previous command received from the WLAN AN. | + +**Table 4.3.4.2: Re-Authentication and Re-Authorization response** + +| Information element name | Mapping to Diameter AVP | Cat. | Description | +|--------------------------|-----------------------------------|------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Result | Result-Code / Experimental-Result | M | Result of the operation.
Result-Code AVP shall be used for errors defined in the Diameter Base Protocol.
Experimental-Result AVP shall be used for Wa errors. This is a grouped AVP which contains the 3GPP Vendor ID in the Vendor-Id AVP, and the error code in the Experimental-Result-Code AVP. | +| User Identity | User-Name | M | This information element contains the identity of the user. | + +RADIUS usage in Wa: + +- This procedure is mapped to the RADIUS messages CoA-Request and CoA-Response specified in RFC 3576 [13]. + +## 4.4 Information Element Contents + +### 4.4.1 RADIUS based Information Elements Contents + +**Table 4.4.1: RADIUS based Information Elements Contents** + +| IE NAME | IE description | Access Request | Access Accept | Access Reject | Access Challenge | Attribute | +|--------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------|---------------|---------------|------------------|------------------------------------| +| USER ID | This Attribute indicates the identity of the user as defined in 3GPP TS 23.003 [22]. | Mandatory | Mandatory | NA | NA | User-Name | +| RADIUS Client Address | This Attribute indicates the identifying IP Address of the RADIUS Client. It should be unique to the RADIUS Client within the scope of the RADIUS server. More detailed description of the IE can be found in IETF RFC 3580 [15]. | Mandatory | NA | NA | NA | NAS-IP-Address
NAS-IPv6-Address | +| Operator Name | Hot Spot Operator Name as defined in IETF RFC 5580 [16]. | Mandatory | NA | NA | NA | Operator-Name | +| Location Information | This Attribute contains meta-data about the location information, such as sighting time, time-to-live, location-determination method, etc, as defined in IETF RFC5580 [16]. It also indicates the type of location profile (civic or geospatial) contained in the Location-Data Attribute. | Mandatory | NA | NA | NA | Location-Information | +| Location Data | This Attribute contains the civic or geospatial location of the hotspot operator as defined in IETF RFC 5580 [16]. | Mandatory | NA | NA | NA | Location-Data | +| Basic Location Policy Rules | This Attribute contains basic policy rules for controlling the distribution of location information as defined in IETF RFC 5580 [16], e.g. retention expiry, URI of human-readable privacy instructions. | Optional | Optional | NA | Optional | Basic-Location-Policy-Rules | +| Extended Location Policy Rules | This Attribute contains a URI that indicates where a richer set of policy rules for controlling the distribution of location information can be found as defined in IETF RFC 5580 [16]. | Optional | Optional | NA | Optional | Extended-Location-Policy-Rules | +| Location Capable | This Attribute allows the RADIUS client to indicate support for the functionality specified in IETF RFC 5580 [16]. | Mandatory | NA | NA | NA | Location-Capable | +| Requested Location Info | This Attribute allows the 3GPP AAA server to indicate which location information about which entity it wants to receive as specified in IETF RFC 5580 [16]. | NA | Optional | NA | Optional | Requested-Location-Info | +| Error Cause | The 3GPP AAA server shall include this attribute with a value of "Location-Info-Required" if it did not receive the requested location information as specified in IETF RFC 5580 [16].. | NA | NA | Optional | NA | Error-Cause | +| EAP Message | This attribute encapsulates Extensible Authentication Protocol packets so as to allow the NAS to authenticate users via EAP without having to understand the EAP protocol. More detailed description of the IE can be found in IETF RFC 3580 [15]. | Mandatory | Mandatory | Mandatory | Mandatory | EAP-Message | +| Diameter Session ID + 3GPP AAA Server Host AVP + prefix "Diameter" | This attribute is relayed from the 3GPP AAA Proxy to the WLAN-AN when the 3GPP AAA Proxy acts as translation agent. If the WLAN-AN receives such an attribute, it MUST include it in Access Requests. | Conditional | NA | NA | Conditional | State | +| Diameter Session ID + prefix "Diameter" | This attribute is sent by 3GPP AAA Proxy when acting as a translation agent. If WLAN-AN receives it, is should include it in subsequent accounting messages. | NA | Conditional | NA | NA | Class | +| State Information | A 3GPP AAA Server using RADIUS may include this attribute in Access Challenges. If the Radius Client in WLAN-AN receives such an attribute, it shall be present in Access-Request that is sent in response to the Access-Challenge. This IE is used when no Diameter-RADIUS translation takes place. | Conditional | NA | NA | Optional | State | + +| IE NAME | IE description | Access Request | Access Accept | Access Reject | Access Challenge | Attribute | +|---------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------|---------------|---------------|------------------|------------------------------------| +| Session ID | A 3GPP AAA Server using RADIUS shall include this attribute to facilitate charging correlation between accounting and authorization messaging. If the Radius Client in WLAN-AN receives it, it shall be included in subsequent accounting messages. This IE is used when no Diameter-RADIUS translation takes place. | NA | Conditional | NA | NA | Class | +| Session Alive Time | This Attribute sets the maximum number of seconds of service to be provided to the user before termination of the session or prompt. A more detailed description of the IE can be found in IETF RFC 3580 [15]. | NA | Optional | NA | Optional | Session-Time-Out | +| Charging Duration | This attribute indicates the time between each interim update in seconds for this specific session. A more detailed description of the IE can be found in IETF RFC 2869 [9]. | NA | Optional | NA | NA | Acct-Interim-Interval | +| Termination Action | This Attribute indicates what action the NAS should take when the specified service is completed. More detailed description of the IE can be found in IETF RFC 3580 [15]. | NA | Optional | NA | Optional | Termination-Action | +| Pairwise Master Key (PMK) | This IE is used to carry the Pairwise Master Key. More detailed description of the IE can be found in IETF RFC 4186 [28] and IETF RFC 4187 [29]. | NA | Mandatory | NA | NA | Vendor-Specific (MS-MPPE-Recv-Key) | +| Message Authenticator | Message Authenticator. | Mandatory | Mandatory | Mandatory | Mandatory | Message-Authenticator | +| WLAN-UE MAC address | Carries the MAC address of the WLAN-UE for verification at the 3GPP AAA Server. | Mandatory | NA | NA | NA | Calling-Station-Id | +| Chargeable User Identity | This Attribute shall contain the MSISDN and/or the IMSI of the user. The encoding of the MSISDN and the IMSI is defined in GSMA PRD IR.61 [25]. | Optional | Mandatory | NA | NA | Chargeable-User-Id | +| Filter ID | This IE indicates the name of the filter list for the user. Filter ID IE and NAS Filter Rule IE should not be used simultaneously in a same RADIUS message. | NA | Optional | NA | NA | Filter-Id | +| NAS Filter Rule | This IE enables the provisioning of Layer 2-4/7 filter and redirection rules on the NAS by 3GPP AAA Server/Proxy. More detailed description of the IE can be found in IETF RFC 4849 [30]. | NA | Optional | NA | NA | NAS-Filter-Rule | +| Tunnel Type | This IE contains the used tunnelling protocol. | NA | Optional | NA | NA | Tunnel-Type | +| Tunnel Medium Type | This IE contains the transport medium to use when creating a tunnel. | NA | Optional | NA | NA | Tunnel-Medium-Type | +| Tunnel Private Group Id | This IE indicates the group ID for a particular tunneled session. | NA | Optional | NA | NA | Tunnel-Private-Group-Id | +| Tunnel Client Endpoint | This IE indicates the address of the client end of the tunnel. | NA | Optional | NA | NA | Tunnel-Client-Endpoint | +| Tunnel Server Endpoint | This Attribute indicates the address of the server end of the tunnel. | NA | Optional | NA | NA | Tunnel-Server-Endpoint | +| Supported 3GPP WLAN QoS Profile | If the WLAN AN supports QoS mechanisms, this attribute may be used to indicate the supported WLAN AN's QoS capabilities. | Optional | NA | NA | NA | 3GPP-WLAN-QoS-Filter-Support | + +| IE NAME | IE description | Access Request | Access Accept | Access Reject | Access Challenge | Attribute | +|-----------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------|---------------|---------------|------------------|---------------------------| +| 3GPP WLAN QoS profile | If the WLAN AN supports QoS mechanisms, this IE may be present in the response. In that case, this IE contains the 3GPP WLAN QoS Profile authorized by the 3GPP AAA Server based on the subscribed QoS parameters from the HSS, WLAN AN's QoS capabilities and other information, e.g. operators' policies. | NA | Optional | NA | NA | 3GPP-WLAN-QoS-Filter-Rule | +| Reply Message | This attribute contains text that may be displayed to the user, indicating the reason for failure and prompting the user for a new access attempt. | NA | NA | Optional | NA | Reply-Message | + +The parameters listed above as 'mandatory' are only optional in the particular RADIUS (extension) specification in which they are originally defined. However, in order for 3GPP WLAN-IW to function, these attributes shall be passed in messaging over the Wa interface as per the definition in the table. In this sense they are mandatory. In practice, this means that, should any of these parameters labelled 'mandatory' be missing from the RADIUS messaging over Wa, this will result in a higher level failure of WLAN-IW procedures to function properly and consequently in a denial of the RADIUS request (even though this was a valid RADIUS message). + +### 4.4.2 Diameter based Information Elements Contents + +#### 4.4.2.1 DER and DEA Commands + +ABNF for the DER and DEA messages are given below: + +``` + ::= < Diameter Header: 268, REQ, PXY > + < Session-Id > + { Auth-Application-Id } + { Origin-Host } + { Origin-Realm } + { Destination-Realm } + { Auth-Request-Type } + { EAP-Payload } + [ Destination-Host ] + [ User-Name ] + [ NAS-IP-Address ] + [ NAS-IPv6-Address ] + [ Calling Station-ID ] + [ QoS-Capability ] + * [ Proxy-Info ] + * [ Route-Record ] + [ Operator-Name ] + * [ Location-Information ] + * [ Location-Data ] + [ Basic-Location-Policy-Rules ] + [ Extended-Location-Policy-Rules ] + [ Location-Capable ] + * [ AVP ] +``` + +For the DEA, the following are necessary: + +``` + ::= < Diameter Header: 268, PXY > + < Session-Id > + { Auth-Application-Id } + { Result-Code } + { Origin-Host } + { Origin-Realm } + { Auth-Request-Type } + { EAP-Payload } + [ User-Name ] + [ Session-Timeout ] + [ Accounting-Interim-Interval ] + [ EAP-Master-Session-Key ] + [ QoS-Resources ] + * [Filter-Id] + * [NAS-Filter-Rule] + * [Tunneling] + * [ Proxy-Info ] + [ Basic-Location-Policy-Rules ] +``` + +``` + +[ Extended-Location-Policy-Rules ] +[ Requested-Location-Info ] +[ Error-Cause ] +* [ AVP ] + +``` + +#### 4.4.2.2 Abort Session Request and Answer AVPs + +ABNF for the ASR and ASA commands are as follows: + +``` + + ::= < Diameter Header: 274, REQ, PXY > + < Session-Id > + { Origin-Host } + { Origin-Realm } + { Destination-Realm } + { Destination-Host } + { Auth-Application-Id } + [ User-Name ] + [ Origin-State-Id ] + * [ Proxy-Info ] + * [ Route-Record ] + * [ AVP ] + + ::= < Diameter Header: 274, PXY > + < Session-Id > + { Result-Code } + { Origin-Host } + { Origin-Realm } + [ User-Name ] + [ Origin-State-Id ] + [ Error-Message ] + [ Error-Reporting-Host ] + * [ Failed-AVP ] + * [ Redirected-Host ] + [ Redirected-Host-Usage ] + [ Redirected-Max-Cache-Time ] + * [ Proxy-Info ] + * [ AVP ] + +``` + +#### 4.4.2.3 Session Termination Request and Answer AVPs + +``` + + ::= < Diameter Header: 275, REQ, PXY > + < Session-Id > + { Origin-Host } + { Origin-Realm } + { Destination-Realm } + { Auth-Application-Id } + { Termination-Cause } + [ User-Name ] + [ Destination-Host ] + * [ Class ] + [ Origin-State-Id ] + * [ Proxy-Info ] + * [ Route-Record ] + * [ AVP ] + + ::= < Diameter Header: 275, PXY > + < Session-Id > + { Result-Code } + { Origin-Host } + { Origin-Realm } + [ User-Name ] + * [ Class ] + [ Error-Message ] + [ Error-Reporting-Host ] + * [ Failed-AVP ] + [ Origin-State-Id ] + * [ Proxy-Info ] + * [ AVP ] + +``` + +#### 4.4.2.4 Re-Auth Request and Answer AVPs + +ABNF for the RAR/RAA commands are as follows: + +``` + + ::= < Diameter Header: 258, REQ, PXY > + +``` + +``` + + < Session-Id > + { Origin-Host } + { Origin-Realm } + { Destination-Realm } + { Destination-Host } + { Auth-Application-Id } + { Re-Auth-Request-Type } + [ User-Name ] + [ Destination-Host ] + [ Origin-State-Id ] + * [ Proxy-Info ] + * [ Route-Record ] + [ Basic-Location-Policy-Rules ] + [ Extended-Location-Policy-Rules ] + [ Requested-Location-Info ] + * [ AVP ] + + ::= < Diameter Header: 258, PXY > + < Session-Id > + { Result-Code } + { Origin-Host } + { Origin-Realm } + [ User-Name ] + [ Origin-State-Id ] + [ Error-Message ] + [ Error-Reporting-Host ] + * [ Failed-AVP ] + * [ Redirect-Host ] + [ Redirect-Host-Usage ] + [ Redirect-Host-Cache-Time ] + * [ Proxy-Info ] + * [ AVP ] + +``` + +## 4.5 Accounting Signalling Across the Wa interface + +The Wa interface carries accounting signalling per WLAN user. This is implemented as described in the subclauses below either using RFC 2866 [20] or RFC 3588 [7]. + +### 4.5.1 RADIUS + +If the Wa interface is implemented using RADIUS, the WLAN-AN sends a RADIUS Accounting-Request message (start) on receipt of a RADIUS Access Accept Message successfully authenticating the user. + +The WLAN-AN sends a RADIUS Accounting-Request (stop) message when the WLAN session is terminated. + +If the Access Accept Message contained an Acc-Interim-Interval attribute, the WLAN-AN sends interim accounting records at intervals in accordance with the value of this attribute. + +During the lifetime of a WLAN session, the WLAN System may generate additional RADIUS Accounting-Request starts and stops messages. + +#### 4.5.1.1 RADIUS Attributes in accounting messages + +Table 4.5.1 gives the information elements included in the accounting messaging exchanged over the Wa interface. + +###### **Table 4.5.1: RADIUS based Information Elements Contents** + +| IE NAME | IE description | Accounting Request | Accounting Response | Attribute | +|--------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------|---------------------|------------------------------------| +| USER ID | This Attribute indicates the identity of the user. More detailed description of the IE can be found in IETF RFC 3580 [15] and 3GPP TS 23.234 [4]. | Mandatory | Mandatory | User-Name | +| RADIUS Client Address | This Attribute indicates the identifying IP Address of the RADIUS Client. It should be unique to the RADIUS Client within the scope of the RADIUS server. More detailed description of the IE can be found in IETF RFC 3580 [15]. | Mandatory | NA | NAS-IP-Address
NAS-IPv6-Address | +| Acc-Session-ID | According to IETF RFC 2866 [20], this attribute is an accounting ID which uniquely identifies the user's session. If the WLAN AN receives an Access Accept containing a Class attribute with prefix "Diameter", then the Session-ID contained therein is used as the Acc-Session-ID. | Mandatory | Mandatory | Acct-Session-Id | +| Operator Name | Hot Spot Operator Name as defined in IETF RFC 5580 [16]. | Mandatory | NA | Operator-Name | +| Location Information | This Attribute contains meta-data about the location information, such as sighting time, time-to-live, location-determination method, etc, as defined in IETF RFC 5580 [16]. It also indicates the type of location profile (civic or geospatial) contained in the Location-Data Attribute. | Mandatory | NA | Location-Information | +| Location Data | This Attribute contains the civic or geospatial location of the hotspot operator as defined in IETF RFC 5580 [16]. | Mandatory | NA | Location-Data | +| Basic Location Policy Rules | This Attribute contains basic policy rules for controlling the distribution of location information as defined in IETF RFC 5580 [16], e.g. retention expiry, URI of human-readable privacy instructions. | Optional | NA | Basic-Location-Policy-Rules | +| Extended Location Policy Rules | This Attribute contains a URI that indicates where a richer set of policy rules for controlling the distribution of location information can be found as defined in IETF RFC 5580 [16]. | Optional | NA | Extended-Location-Policy-Rules | +| Acct.Status Type | Indicates whether this is:
(i) Accounting Start.
(ii) Stop.
(iii) Interim Report. Accounting start indicates that this is the beginning of the user service, Account stop the end. | Mandatory | N/A | Acct-Status-Type | +| Acc-Input-octets | Indicates the number of octets sent by the WLAN UE over the course of the session. According to the IETF RFC 5080 [39], updating the IETF RFC 2866 [20], shall only be present if ACC Status Type is set to "Interim" or "Stop". | Conditional. Shall be present if Acct-Status-Type set to "Accounting Interim" or "Accounting Stop". | N/A | Acct-Input-Octets | +| Acc-Output Octets | Indicates the number of octets received by the WLAN-UE. According to the IETF RFC 5080 [39], updating the IETF RFC 2866 [20], shall only be present if ACC Status Type is set to "Interim" or "Stop". | Conditional. Shall be present if Acct-Status-Type set to "Accounting Interim" or "Accounting Stop". | N/A | Acct-Output-Octets | +| Acc-Session-Time | This attribute indicates how many seconds the user has received service for. According to the IETF RFC 5080 [39], updating the IETF RFC 2866 [20], shall only be present if ACC Status Type is set to "Interim" or "Stop". | Conditional. Shall be present if Acct-Status-Type set to "Accounting Interim" or "Accounting Stop". | N/A | Acct-Session-Time | +| Acc-Input-Packets | Indicates the number of packets sent by the WLAN UE over the course of the session. According to the IETF RFC 5080 [39], updating the IETF RFC 2866 [20], shall only be present if ACC Status Type is set to "Interim" or "Stop". | Optional | N/A | Acct-Input-Packets | +| Acc-Output-Packets | Indicates the number of packets received by the WLAN-UE over the course of the session. According to the IETF RFC 5080 [39], updating the IETF RFC 2866 [20], shall only be present if ACC Status Type is set to "Interim" or "Stop". | Optional | N/A | Acct-Output-Packets | +| Acc-Terminate-Cause | Indicates how the session was stopped. Cause values are as per specified in IETF RFC 3580 [15]. According to the IETF RFC 5080 [39], updating the IETF RFC 2866 [20], shall only be present if ACC Status Type is set to "Stop". | Conditional. Shall be present if Acct-Status-Type set to "Accounting Stop". | N/A | Acct-Terminate-Cause | + +| IE NAME | IE description | Accounting Request | Accounting Response | Attribute | +|--------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------|---------------------|-----------------------| +| Chargeable User Identity | This Attribute shall contain the MSISDN and/or the IMSI of the user. The encoding of the MSISDN and the IMSI is defined in GSMA PRD IR.61 [25]. | Mandatory | NA | Chargeable-User-Id | +| Event Time Stamp | Number of second elapsed since January 1 st 1970. UTC time. | Mandatory | NA | Event-Time-Stamp | +| Session ID | This attribute is used to link related authentication and accounting sessions and should be included unmodified to accounting request messages. This IE is used when no Diameter-RADIUS translation takes place. | Conditional. Shall be present if received in an Access Accept. | NA | Class | +| Acct-Input-Gigawords | This attribute indicates how many times the Acct-Input-Octets counter has wrapped around 2 32 and can only be present when Acct-Status-Type is set to Stop or Interim-Update. | Conditional. Shall be present if Acct-Input-Octets wraps around 2 32 . | NA | Acct-Input-Gigawords | +| Acct-Output-Gigawords | This attribute indicates how many times the Acct-Output-Octets counter has wrapped around 2 32 and can only be present when Acct-Status-Type is set to Stop or Interim-Update. | Conditional. Shall be present if Acct-Output-Octets wraps around 2 32 . | NA | Acct-Output-Gigawords | + +The parameters listed above as "mandatory" are only optional in the particular RADIUS (extension) specification in which they are originally defined. However, in order for 3GPP WLAN-IW to function, these attributes shall be passed in messaging over the Wa interface as per the definition in the table. In this sense they are mandatory. In practice, this means that, should any of these parameters labelled "mandatory" be missing from the RADIUS messaging over Wa, this will result in a higher level failure of WLAN-IW procedures to function properly and consequently in a denial of the RADIUS request (even though this was a valid RADIUS message). + +### 4.5.2 Diameter + +When Diameter is used on the Wa interface, the accounting messaging is as per defined in NASREQ IETF RFC 4005 [12] i.e. Accounting Request Message (ACR) is sent by the WLAN-AN after any authentication transaction and at the end of the session. + +In addition, the WLAN-AN may send Interim accounting records. + +#### 4.5.2.1 Procedures Description + +This procedure is used to transport over Diameter, the WLAN accounting specific information between the WLAN AN and the 3GPP AAA Proxy/Server. + +Diameter usage in Wa: + +- This procedure is mapped to the Diameter-Accounting Request and Accounting Response (ACR/ACA) command codes as defined in NASREQ IETF RFC 4005 [12]. The Diameter-ACR Message shall contain the following information elements. + +**Table 4.5.2.1: Accounting request** + +| Information element name | Mapping to Diameter AVP | Cat. | Description | +|--------------------------------|--------------------------------|------|-----------------------------------------------------------------------------------------------------------------------------------------| +| User Identity | User-Name | M | This information element contains the identity of the user. | +| NAS-IP address | NAS-IP Address | C | IPv4 address of the hot-spot | +| NAS-Ipv6 address | NAS-Ipv6 address | C | IPv6 address of the hot-spot | +| Accounting Record type | Accounting Record type | M | 2= Start, 4= Stop, 3= Interim Record | +| Accounting Session-ID | Accounting Session-ID | M | Uniquely Identifies the accounting session. May be the same Session-ID as for the authentication signalling over the Wa | +| Accounting-Input-Octets | Accounting-Input-Octets | O | Number of octets sent by the WLAN UE | +| Accounting-Output-Octets | Accounting-Output-Octets | O | Number of octets received by the WLAN UE | +| Accounting-Input-Packets | Accounting-Input-Packets | O | Number of packets sent by the WLAN UE | +| Accounting-Output-Packets | Accounting-Output-Packets | O | Number of packets received by the WLAN UE | +| Accounting-Session-Time | Accounting-Session-Time | C | Indicates the length of the current session in seconds. Shall only be present if Accounting-Record-Type is set to Stop or Interim | +| Termination-Cause | Termination-Cause | C | Shall be present only if Accounting-Record-Type is set to Stop. | +| Operator Name | Operator-Name | M | Hot Spot Operator Name. | +| Location Information | Location-information | M | Contains meta-data about the location information. | +| Location Data | Location-Data | M | Contains the civic or geospatial location of the hotspot operator. | +| Basic Location Policy Rules | Basic-Location-Policy-Rules | O | Contains basic policy rules for controlling the distribution of location information. | +| Extended Location Policy Rules | Extended-Location-Policy-Rules | O | Contains a URI that indicates where a richer set of policy rules for controlling the distribution of location information can be found. | + +The Diameter-Accounting response message shall contain the following. + +**Table 4.5.2.2: Accounting response** + +| Information element name | Mapping to Diameter AVP | Cat. | Description | +|--------------------------|-------------------------|------|--------------------------------------------------------------------------------------------------------------------| +| User Identity | User-Name | M | This information element contains the identity of the user. | +| Result code | Result Code | M | Result of the operation. Result codes are as per in NASREQ. 1xxx should be used for multi-round, 2xxx for success. | + +#### 4.5.2.2 Information Element Contents + +The ABNF for the Accounting Request and Accounting Response messages over the Wa interface are given below: + +``` + ::= < Diameter Header: 271, REQ, PXY > + < Session-Id > + { Origin-Host } + { Origin-Realm } + { Destination-Realm } + { Accounting-Record-Type } + { Accounting-Record-Number } + [ Acct-Application-Id ] + [ Vendor-Specific-Application-Id ] + [ User-Name ] + [ Accounting-Sub-Session-Id ] +``` + +[ Acct-Session-Id ] +[ Acct-Multi-Session-Id ] +[ Origin-State-Id ] +[ Destination-Host ] +[ Event-Timestamp ] +[ Acct-Delay-Time ] +[ NAS-Identifier ] +[ NAS-IP-Address ] +[ NAS-IPv6-Address ] +[Acc-Terminate-Cause ] +[ Accounting-Session-Time ] +[ NAS-Port ] +[ NAS-Port-Id ] +[ NAS-Port-Type ] +[ Operator-Name ] +\* [ Location-Information ] +\* [ Location-Data ] +[ Basic-Location-Policy-Rules ] +[ Extended-Location-Policy-Rules ] +\* [ AVP ] + + ::= < Diameter Header: 271, PXY > +  < Session-Id > +  { Result-Code } +  { Origin-Host } +  { Origin-Realm } +  { Accounting-Record-Type } +  { Accounting-Record-Number } +  [ Acct-Application-Id ] +  [ Vendor-Specific-Application-Id ] +  [ User-Name ] +  [ Accounting-Sub-Session-Id ] +  [ Acct-Session-Id ] +  [ Acct-Multi-Session-Id ] +  [ Event-Timestamp ] +  [ Error-Message ] +  [ Error-Reporting-Host ] +  \* [ Failed-AVP ] +  [ Origin-State-Id ] +  [ NAS-Identifier ] +  [ NAS-IP-Address ] +  [ NAS-IPv6-Address ] +  [ NAS-Port ] +  [ NAS-Port-Id ] +  [ NAS-Port-Type ] + +``` +[ Service-Type ] +[ Termination-Cause ] +[ Accounting-Realtime-Required ] +[ Acct-Interim-Interval ] +* [ Class ] +* [ Proxy-Info ] +* [ Route-Record ] +* [ AVP ] +``` + +# --- 5 Wd Description + +## 5.1 Functionality + +The Wd reference point is defined between the 3GPP AAA Proxy and the 3GPP AAA Server. The description of the reference point and its functionality is given in 3GPP TS 23.234 [4]. + +Therefore, this reference point is used in the roaming case only. + +## 5.2 Protocols + +The Wd reference point shall use only a single AAA protocol per WLAN session. RADIUS or Diameter based protocols shall be used. + +The Wd protocol reference point shall contain the following protocols: + +- 1) RADIUS, as defined in IETF RFC 2865 [17], including the following extensions: + - IETF RFC 2869 [9], which provides RADIUS extensions to support the transport of EAP frames over RADIUS. + - IETF RFC 5580 [16], which provides RADIUS and Diameter Extensions for Public WLAN to identify uniquely the owner and location of the WLAN. + - IETF RFC 3576 [13], which provides RADIUS extensions to supports, amongst other capabilities, the capability to immediately disconnect a user from the WLAN AN. + - GSMA PRD IR.61 [25], which provides a Visited-operator-id attribute and a detailed encoding of a chargeable user identity (e.g. MSISDN or IMSI) for the RADIUS Chargeable-User-Id attribute. + - IETF RFC 4372 "Chargeable User Identity" [26], which provides RADIUS Extensions for carrying a chargeable user identity from Home PLMN to Visited PLMN. +- 2) Diameter Base, as defined in IETF RFC 3588 [7], as well as IETF RFC 4072 [8], which provides a Diameter application to support the transport of EAP (IETF RFC 3748 [11]) frames over Diameter, and IETF RFC 5580 which provides RADIUS and Diameter Extensions for Public WLAN which are used in order to uniquely identify the owner and location of the WLAN. In addition, Diameter Base (IETF RFC 3588 [7]) and NASREQ (IETF RFC 4005 [12]) specify the accounting messaging to be exchanged. IETF RFC 5729 [36] defines the procedures related to the routing of Diameter requests when Decorated NAIs (as defined in 3GPP TS 23.003 [22]) are used. + +The 3GPP AAA Proxy and the 3GPP AAA Server shall support both 1) and 2) over the Wd reference point. The 3GPP AAA Proxy, depending on the WLAN ANs characteristics, shall use either 1) or 2) over the Wd reference point. See subclause 5.3 for more information of when either 1) or 2) is used. + +The Application-Id to be advertised over Wd reference point corresponds to the EAP, NASREQ or Diameter Base Protocol Application-Id, depending on the command sent over Wd. + +## 5.3 3GPP AAA Proxy and 3GPP AAA Server behaviour when Interworking with RADIUS/Diameter WLAN ANs + +If a WLAN AN attached to the 3GPP AAA Proxy is Diameter based, Diameter messages shall be passed on to the 3GPP AAA Server through the 3GPP AAA Proxy. If a WLAN AN attached to the 3GPP AAA Proxy is RADIUS + +based, the RADIUS messages sent by the WLAN AN shall be either passed on to the 3GPP AAA Server through the 3GPP AAA Proxy, or translated by the 3GPP AAA Proxy Translation Agent into Diameter messages to be sent on to the 3GPP AAA Server by the 3GPP AAA Proxy. This protocol translation shall be done as follows. + +The 3GPP AAA Server needs to be aware of what kind of client it is serving in order to adapt its operation to the capabilities of the WLAN AN. + +The 3GPP AAA Proxy is the only network element in direct contact with the WLAN AN and therefore it is the only network element aware of whether the WLAN AN is RADIUS or Diameter based. The following rules shall apply for the 3GPP AAA Server to determine this: + +If the Wd reference point uses RADIUS then: + +- The 3GPP AAA Server shall assume that the WLAN AN is RADIUS based. + +If the Wd reference point uses Diameter then: + +- The 3GPP AAA Server shall assume the WLAN AN to be Diameter- based unless the 3GPP AAA Proxy specifically indicates that the WLAN AN is RADIUS based (see subclause 5.3.1.3). + +Once the 3GPP AAA Server is aware of which AAA protocol that the WLAN AN is using, it shall adapt its operation over the Wd reference point. + +If the WLAN AN is determined to be Diameter based, the operation mode of the 3GPP AAA Server shall be the normal behaviour as described in Diameter (IETF RFC 4072 [8]) and the Diameter Base (IETF RFC 3588 [7]) for authentication and NASREQ (IETF RFC 4005 [12]) for accounting. + +If the WLAN AN is determined to be RADIUS based, the operation mode of the 3GPP AAA Server shall be the following: + +If the Wd reference point is using RADIUS then: + +- Normal behaviour for RADIUS as specified in the first bullet in subclause 5.2. + +If the Wd reference point is using Diameter then: + +- The normal behaviour for Diameter as specified in the second bullet in subclause 5.2, but shall be modified as follows to ensure RADIUS compatibility: + - Diameter AVPs to RADIUS attributes compatibility: + - 3GPP AAA Server shall restrict itself to use only Diameter AVPs that are compatible with RADIUS attributes. In general, 3GPP AAA Server shall use Diameter AVPs with codes not greater than 255. See section 9.5 in IETF RFC 4005 [12] for further detail. + - Diameter specific procedures when interacting with RADIUS clients: + - 3GPP AAA Server shall not attempt server-initiated re-authentication. + - 3GPP AAA Server may attempt server-initiated re-authorization and server-initiated session termination. + +### 5.3.1 Requirements in 3GPP AAA Proxy for RADIUS/Diameter "Translation Agent" + +A RADIUS/Diameter Translation Agent has the following requirements: + +- Receive RADIUS requests (sent to UDP port 1812); +- Diameter proxy functionality (communicate over TCP/SCTP port TBD, mandatory support for IPSec, optional support for TLS, etc.); +- Convert RADIUS requests to Diameter requests; +- Convert Diameter responses to RADIUS responses; + +- Advertise to the 3GPP AAA Server whether the client located in WLAN AN is RADIUS or Diameter based; +- Managing the transaction state information of the RADIUS requests. + +The Diameter protocol defines a common space for many RADIUS information elements (AVPs), so that no conversion is necessary when transporting them. However, there are certain AVPs that do need translation and differences of the message formats and transport protocols need to be handled. + +#### 5.3.1.1 Conversion of RADIUS Request to Diameter Request + +When receiving a RADIUS Request on the Wa reference point, the 3GPP AAA Proxy Translation Agent shall translate it into a Diameter Request to be forwarded on the Wd reference point, as described in IETF RFC 4005 [12]. + +If the RADIUS Request contains EAP frames, additional actions described in IETF RFC 4072 [8] are taken by the 3GPP AAA Proxy Translation Agent to convert this into a Diameter Request containing EAP frames. Typically, RADIUS Access Request command is translated into Diameter-EAP-Request command. + +If the RADIUS Request contains the 3GPP-WLAN-QoS-Filter-Support attribute indicating support of the 3GPP-WLAN-QoS-Filter-Rule attribute in the WLAN AN, the 3GPP AAA Proxy Translation Agent shall translate it into a Diameter QoS-Capability AVP indicating support of the QoS-Resources AVP. + +#### 5.3.1.2 Conversion of Diameter Response to RADIUS Response + +When receiving a Diameter Response on the Wd reference point, if the WLAN AN supports only RADIUS based Wa reference point, the 3GPP AAA Proxy Translation Agent shall translate it into a RADIUS Response to be forwarded on the Wa reference point, as described in IETF RFC 4005 [12]. + +If the Diameter Response contains EAP frames, additional actions described in IETF RFC 4072 [8] are taken by the 3GPP AAA Proxy Translation Agent to convert this into a RADIUS Response containing EAP frames. Typically, Diameter-EAP-Answer command is translated into RADIUS Access-Accept/Reject/Challenge command. + +If the Diameter Response contains the QoS-Resources AVP, the 3GPP AAA Proxy Translation Agent shall translate it into a RADIUS 3GPP-WLAN-QoS-Filter-Rule attribute. If the 3GPP AAA Server determines that the WLAN AN is RADIUS based (see section 5.3.1.3), it shall construct the Diameter QoS-Resources AVP such that it can be translated into a RADIUS 3GPP-WLAN-QoS-Filter-Rule attribute. + +#### 5.3.1.3 3GPP AAA Proxy advertisement of RADIUS or Diameter client to 3GPP AAA Server. + +Some Diameter AVPs are defined specifically for use in Diameter messages that result from the translation of a RADIUS message into a Diameter message, or for use in Diameter messages that are to be translated into RADIUS messages. When the 3GPP AAA Proxy receives RADIUS messages on the Wa reference point, it may use these AVP's in the Diameter message it sends to the 3GPP AAA Server on the Wd reference point to indicate to the 3GPP AAA Server that the WLAN AN is RADIUS based. The 3GPP AAA Server shall modify its Response to the Diameter command in such a way that the Diameter Response message can be translated into a RADIUS Response by the 3GPP AAA Proxy Translation Agent, to be sent on by the 3GPP AAA Proxy to the WLAN AN. + +The 3GPP AAA Proxy shall indicate to the 3GPP AAA Server that the WLAN AN that it is attached to is RADIUS based by including one or more of the following Diameter AVPs in the resultant Diameter command that is sent to the 3GPP AAA Server: + +- NAS-IP-Address AVP. +- NAS-IPv6-Address AVP. +- State AVP. +- Termination-Cause AVP. + +Further details on usage of these AVPs can be found in IETF RFC 4005 [12]. + +#### 5.3.1.4 Managing the transaction state and session state information + +The 3GPP AAA Proxy Translation Agent shall maintain the session state and transaction state, as indicated in IETF RFC 3588 [7]. + +The 3GPP AAA Proxy shall be able to keep the relationship between the RADIUS-Request and Diameter-Requests, as well as for Diameter-Responses to RADIUS-Responses. + +The 3GPP AAA Proxy for every RADIUS-Request received shall maintain RADIUS transaction state information as follows, see IETF RFC 4005 [12]: + +- RADIUS Identifier Field in the RADIUS-Request as described in IETF RFC 2685 [17]. +- Source IP address of the RADIUS-Request message. +- Source UDP port of the RADIUS-Request message. +- RADIUS Proxy-State in the RADIUS-Request as described in IETF RFC 2685 [17]. + +Additionally, for every Diameter-Request that is sent to the 3GPP AAA Server, the 3GPP AAA Proxy shall maintain a Diameter transaction state information based on the Diameter Hop-by-Hop Id as described in IETF RFC 3588 [7]. + +Upon the reception of a RADIUS-Request, translation of that RADIUS-Request to a Diameter-Request and sending out of that Diameter-Request to the 3GPP AAA Server, the 3GPP AAA Proxy shall create the RADIUS transaction state and link it to the Diameter transaction state. + +When receiving the Diameter-Response corresponding to the Diameter-Request sent to the 3GPP AAA Server, it should be possible for the 3GPP AAA Proxy to relate it to a RADIUS-Response based on the information available in the Diameter-transaction state and RADIUS transaction state. + +Every RADIUS-Request received, translated to Diameter-Request and sent to the 3GPP AAA Server by the 3GPP AAA Proxy, shall be linked to a Session State as described in IETF RFC 4005 [12]: + +- If the RADIUS-Request contains the State attribute and "Diameter/" prefixes its data, the data following the prefix is the Diameter Session Id. +- If the RADIUS-Request does not contain the State attribute and it is an Access\_Accept, a new Diameter Session Id is generated in the 3GPP AAA Proxy. + +The Diameter Session Id is included in the Session-Id AVP in the Diameter-Request. + +## 5.4 Procedures description + +### 5.4.1 WLAN Access Authentication and Authorization + +This procedure is used to transport the WLAN Access Authentication and Authorization information between the 3GPP AAA Proxy and the 3GPP AAA Server. + +Diameter usage in Wd: + +This procedure is mapped to the Diameter-EAP-Request and Diameter-EAP-Answer command codes specified in IETF RFC 4072 [8] tables 5.4.1.1 and 5.4.1.2 show the information elements that should be exchanged across Wd. If the User-Name AVP contains a Decorated NAI as defined in 3GPP TS 23.003 [22], then the Diameter request routing shall follow the procedures defined in IETF RFC 5729 [36]. + +**Table 5.4.1.1: Diameter EAP Request** + +| Information element name | Mapping to Diameter AVP | Cat. | Description | +|---------------------------------|--------------------------------|------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| User Identity | User Name | M | This information element shall contain the identity of the user | +| EAP payload | EAP payload | M | Encapsulated EAP payload used for WLAN-UE/3GPP AAA Server mutual authentication | +| Authentication Request Type | Auth-Request-Type | M | Defines whether the user is to be re-authenticated only, re-authorized only or both. AUTHORIZE_AUTHENTICATE is required in this case. | +| NAS-IP address | NAS-IP Address | C | IP address of the hot-spot | +| NAS-Ipv6 address | NAS-Ipv6 address | C | IPv6 address of the hot-spot | +| Visited-Network-Identifier | Visited-Network-Identifier | C | Identifies the VPLMN and shall be present during the first DER message of either authentication or reauthentication sent by the 3GPP AAA Proxy to 3GPP AAA Server. | +| WLAN UE MAC address | Calling Station-ID | | Carries the MAC address of the WLAN-UE. | +| Supported 3GPP WLAN QoS profile | QoS-Capability | O | If the WLAN AN supports QoS mechanisms, this information element may be included and shall contain the WLAN AN's QoS capabilities. | +| Operator Name | Operator-Name | M | Hot Spot Operator Name. | +| Location Information | Location-Information | M | Contains meta-data about the location information. | +| Location Data | Location-Data | M | Contains the civic or geospatial location of the hotspot operator. | +| Basic Location Policy Rules | Basic-Location-Policy-Rules | O | Contains basic policy rules for controlling the distribution of location information. | +| Extended Location Policy Rules | Extended-Location-Policy-Rules | O | Contains a URI that indicates where a richer set of policy rules for controlling the distribution of location information can be found. | +| Location Capable | Location-Capable | M | Allows the RADIUS client to indicate support for the functionality specified in IETF RFC 5580. | + +**Table 5.4.1.2: Diameter EAP answer message** + +| Information element name | Mapping to Diameter AVP | Cat. | Description | +|----------------------------------|--------------------------------|------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| User Identity | User Name | M | This information element contains the identity of the user. | +| EAP payload | EAP payload | M | Encapsulated EAP payload used for UE-3GPP AAA Server mutual authentication | +| Result code | Result Code | M | Result of the operation. Result code as per definition in NASREQ.1xxx shall be used for multi-round, 2xxx for success. | +| Session Alive Time | Session-Timeout | O | Max no of seconds the user session should remain active | +| Accounting Interim-Interval | Accounting Interim-Interval | O | Charging duration | +| Subscription-ID | Subscription-ID | C | This AVP shall contain the MSISDN and/or the IMSI of the user. This AVP shall be present if the result code is set to "Success", 2xxx. | +| Pairwise Master Key | EAP-Master-Session-Key | C | Shall be sent if Result Code is set to "Success". | +| Authorized 3GPP WLAN QoS profile | QoS-Resources | O | If both supported 3GPP WLAN QoS profile of the WLAN AN and subscribed QoS profile were received by the 3GPP AAA Server, this IE may be present.
This IE contains the 3GPP WLAN QoS Profile authorized by the 3GPP AAA Server based on the subscribed QoS parameters from the HSS, WLAN AN's QoS capabilities and other information, e.g. operators' policies. | +| Routing Policy | Routing-Policy | O | This AVP includes the routing policies and IP filtering. This AVP shall be present when Operator Determined Barring requires additional filtering information to be passed to the Access Network. The exact format of this AVP is specified in section 10.1.24. | +| Basic Location Policy Rules | Basic-Location-Policy-Rules | O | Contains basic policy rules for controlling the distribution of location information. | +| Extended Location Policy Rules | Extended-Location-Policy-Rules | O | Contains a URI that indicates where a richer set of policy rules for controlling the distribution of location information can be found. | +| Requested Location Info | Requested-Location-Info | O | Allows the 3GPP AAA Proxy to indicate which location information about which entity it wants to receive. | +| Error Cause | Error-Cause | O | The 3GPP AAA Proxy shall include this attribute with a value of "Location-Info-Required" if it did not receive the requested location information as specified in IETF RFC 5580 [16]. | + +RADIUS usage in Wd: + +- This procedure is mapped to the RADIUS Access Request, RADIUS Access Challenge, RADIUS Access Accept and RADIUS Access Reject specified in IETF RFC 3579 [14]. + +### 5.4.2 Immediate Purging of a User from WLAN access + +This procedure is used to communicate between the 3GPP AAA Proxy and the 3GPP AAA Server that the 3GPP AAA Server has decided that a specific WLAN-UE shall be disconnected from accessing the WLAN interworking service. The procedure is Diameter or RADIUS based. + +Diameter usage in Wd: + +- This procedure is mapped to the Diameter command codes Diameter-Abort-Session-Request and Diameter-Abort-Session-Answer specified in RFC 3588 [7]. Information elements are as per described in section 4.3.2. + +RADIUS usage in Wd: + +- This procedure is mapped to the RADIUS messages Disconnect-Request and Disconnect-Response specified in RFC 3576 [13]. + +### 5.4.3 Ending a Session + +Session termination occurs when a user de-registers from the 3GPP AAA Server. This occurs via the Session Termination Request (STR) and Session Termination Answer commands (STA), defined in the base protocol IETF RFC 3588 [7]. Information elements are as per described in subclause 4.3.3. + +### 5.4.4 Authorization Information Update Procedure + +The authorization information update procedure is used in roaming case to modify the authorization parameters provided either to the WLAN AN or to a PDG located in the visited network. This procedure is invoked by the 3GPP AAA Server and is used to communicate with the WLAN AN or the PDG through the 3GPP AAA proxy. + +The procedure is Diameter or RADIUS based. + +- Diameter usage in Wd: + - If the 3GPP AAA server issues an unsolicited re-authentication and/or re-authorization request towards the WLAN AN, the 3GPP AAA proxy shall forward the request to the WLAN AN, which triggers the WLAN access authentication and authorization information update procedure described in the section 4.3.4. + - If the 3GPP AAA server issues an unsolicited re-authentication and/or re-authorization request towards the PDG located in the visited network, the 3GPP AAA proxy shall forward the request to the PDG, which triggers the access and service authorization information update procedure described in the section 8.3.5. + +RADIUS usage in Wd: + +- The Wd interface is used to transport the RADIUS messages CoA-Request and CoA-Response only for communication between the WLAN AN and the 3GPP AAA server. These messages are specified in RFC 3576 [13]. + +## 5.5 Information Elements Contents + +### 5.5.1 Authentication Procedures + +ABNF for the Wd Diameter EAP Request/Answer messages are given below: + +``` + ::= < Diameter Header: 268, REQ, PXY > + < Session-Id > + { Auth-Application-Id } + { Origin-Host } + { Origin-Realm } + { Destination-Realm } + { Auth-Request-Type } + { EAP-Payload } + [ Destination-Host ] + [ User-Name ] + [ NAS-IP-Address ] + [ NAS-IPv6-Address ] + [ Calling Station-ID ] + [ Visited-Network-Identifier ] + [ QoS-Capability ] + * [ Proxy-Info ] + * [ Route-Record ] + [ Operator-Name ] + * [ Location-Information ] + * [ Location-Data ] + [ Basic-Location-Policy-Rules ] + [ Extended-Location-Policy-Rules ] + [ Location-Capable ] + * [ AVP ] +``` + +For the DEA, the following are necessary: + +``` + ::= < Diameter Header: 268, PXY > + < Session-Id > + { Auth-Application-Id } + { Result-Code } + { Origin-Host } + { Origin-Realm } + { Auth-Request-Type } + { EAP-Payload } + [ User-Name ] +``` + +``` +1* [ Subscription-ID ] +[ EAP-Master-Session-Key ] +[ QoS-Resources ] +* [ Proxy-Info ] +[ Basic-Location-Policy-Rules ] +[ Extended-Location-Policy-Rules ] +[ Requested-Location-Info ] +[ Error-Cause ] +* [ AVP ] +``` + +### 5.5.2 Abort Session Requests and Answer AVPs + +ABNF for the ASR and ASA commands on the Wd interface are identical to those on the Wa interface described in section 4.4.2.2 + +### 5.5.3 Session Termination Request and Answer AVPs + +ABNF for the STR and STA commands on the Wd interface are identical to those on the Wa interface described in section 4.4.2.3. + +### 5.5.3A Authorization Information Update Procedure + +ABNF for the RAR and RAA commands on the Wd interface are identical to those described in section 4.4.2.4. + +ABNF for the AAR/AAA commands on the Wd interface are identical to those described in section 8.4.2. + +### 5.5.4 RADIUS based Information Elements Contents for Authentication and Authorization + +**Table 5.5.4.1: RADIUS based Information Elements Contents** + +| IE NAME | IE description | Access Request | Access Accept | Access Reject | Access Challenge | Attribute | +|--------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------|---------------|---------------|------------------|------------------------------------| +| RADIUS Client Address | This Attribute indicates the identifying IP Address of the RADIUS Client. It should be unique to the RADIUS Client within the scope of the RADIUS server. More detailed description of the IE can be found in IETF RFC 3580 [15]. | Mandatory | NA | NA | NA | NAS-IP-Address
NAS-IPv6-Address | +| USER ID | This Attribute indicates the identity of the user to be authenticated. More detailed description of the IE can be found in IETF RFC 3580 [15] and 3GPP TS 23.234 [4]. | Mandatory | Mandatory | NA | NA | User-Name | +| Operator Name | Hot Spot Operator Name as defined in IETF RFC 5580 [16]. | Mandatory | NA | NA | NA | Operator-Name | +| Location Information | This Attribute contains meta-data about the location information, such as sighting time, time-to-live, location-determination method, etc, as defined in IETF RFC5580 [16]. It also indicates the type of location profile (civic or geospatial) contained in the Location-Data Attribute. | Mandatory | NA | NA | NA | Location-Information | +| Location Data | This Attribute contains the civic or geospatial location of the hotspot operator as defined in IETF RFC 5580 [16]. | Mandatory | NA | NA | NA | Location-Data | +| Basic Location Policy Rules | This Attribute contains basic policy rules for controlling the distribution of location information as defined in IETF RFC 5580 [16], e.g. retention expiry, URI of human-readable privacy instructions. | Optional | Optional | NA | Optional | Basic-Location-Policy-Rules | +| Extended Location Policy Rules | This Attribute contains a URI that indicates where a richer set of policy rules for controlling the distribution of location information can be found as defined in IETF RFC 5580 [16]. | Optional | Optional | NA | Optional | Extended-Location-Policy-Rules | +| Location Capable | This Attribute allows the RADIUS client to indicate support for the functionality specified in IETF RFC 5580 [16]. | Mandatory | NA | NA | NA | Location-Capable | +| Requested Location Info | This Attribute allows the RADIUS server to indicate which location information about which entity it wants to receive as specified in IETF RFC 5580 [16]. | NA | Optional | NA | Optional | Requested-Location-Info | +| Error Cause | The 3GPP AAA Proxy shall include this attribute with a value of "Location-Info-Required" if it did not receive the requested location information as specified in IETF RFC 5580 [16]. | NA | NA | Optional | NA | Error-Cause | +| EAP Message | This attribute encapsulates Extensible Authentication Protocol packets so as to allow the NAS to authenticate users via EAP without having to understand the EAP protocol. More detailed description of the IE can be found in IETF RFC 3580 [15]. | Mandatory | Mandatory | Mandatory | Mandatory | EAP-Message | +| State information | This attribute may be sent by the 3GPP AAA server to the WLAN-AN . If the RADIUS client in the WLAN-AN receives such an attribute, it shall be included in subsequent Access Requests. | Conditional | NA | NA | Optional | State | +| Session ID | This attribute is sent by 3GPP AAA server to the visited network. If the RADIUS client in the WLAN-AN receives it, it should be included in subsequent accounting messages. | NA | Mandatory | NA | NA | Class | +| Session Alive Time | This Attribute sets the maximum number of seconds of service to be provided to the user before termination of the session or prompt. A more detailed description of the IE can be found in IETF RFC 3580 [15]. | NA | Optional | NA | Optional | Session-Time-Out | +| Charging Duration | This attribute indicates the time between each interim update in seconds for this specific session. A more detailed description of the IE can be found in IETF RFC 2869 [9]. | NA | Optional | NA | NA | Acct-Interim-Interval | +| Termination Action | This Attribute indicates what action the NAS should take when the specified service is completed. More detailed description of the IE can be found in IETF RFC 3580 [15]. | NA | Optional | NA | Optional | Termination-Action | +| Pairwise Master Key (PMK) | This IE is used to carry the Pairwise Master Key. More detailed description of the IE can be found in IETF RFC 4186 [28] and IETF RFC 4187 [29]. | NA | Mandatory | NA | NA | Vendor-Specific (MS-MPPE-Recv-Key) | +| Message Authenticator | Message Authenticator. | Mandatory | Mandatory | Mandatory | Mandatory | Message-Authenticator | +| WLAN-UE MAC address | Carries the MAC address of the WLAN-UE for verification at the 3GPP AAA Server. | Mandatory | NA | NA | NA | Calling-Station-Id | + +| | | | | | | | +|---------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------|-----------|----------|----|---------------------------------------| +| Chargeable User Identity | This Attribute shall contain the MSISDN and/or the IMSI of the use. The encoding of the MSISDN and the IMSI is defined in GSMA PRD IR.61 [25]. | Optional | Mandatory | NA | NA | Chargeable-User-Id | +| Visited Operator Identity | Identifies the VPLMN as specified in GSMA PRD IR.61 [25] | Mandatory | NA | NA | NA | Vendor-Specific (Visited-Operator-Id) | +| Supported 3GPP WLAN QoS Profile | If the WLAN AN supports QoS mechanisms, this attribute may be used to indicate the supported WLAN AN's QoS capabilities. | Optional | NA | NA | NA | 3GPP-WLAN-QoS-Filter-Support | +| 3GPP WLAN QoS profile | If the WLAN AN supports QoS mechanisms, this IE may be present in the reponse. In that case, this IE contains the 3GPP WLAN QoS Profile authorized by the 3GPP AAA Server based on the subscribed QoS parameters from the HSS, WLAN AN's QoS capabilities and other information, e.g. operators' policies. | NA | Optional | NA | NA | 3GPP-WLAN-QoS-Filter-Rule | +| NAS Filter Rule | This IE enables the provisioning of Layer 2-4/7 filter and redirection rules on the NAS by 3GPP AAA Server/Proxy. More detailed description of the IE can be found in IETF RFC 4849 [30]. | NA | Optional | NA | NA | NAS-Filter-Rule | +| Reply Message | This attribute contains text that may be displayed to the user, indicating the reason for failure and prompting the user for a new access attempt. | NA | NA | Optional | NA | Reply-Message | + +The parameters listed above as 'mandatory' are only optional in the particular RADIUS (extension) specification in which they are originally defined. However, in order for 3GPP WLAN-IW to function, these attributes shall be passed in messaging over the Wd interface as per the definition in the table. In this sense they are mandatory. In practice, this means that, should any of these parameters labelled 'mandatory' be missing from the RADIUS messaging over Wd, this will result in a higher level failure of WLAN-IW procedures to function properly and consequently in a denial of the RADIUS request (even though this was a valid RADIUS message). + +### 5.5.5 RADIUS based Information Elements Contents for Accounting + +**Table 5.5.5.1: RADIUS based Information Elements Contents** + +| IE NAME | IE description | Accounting Request | Accounting Response | Attribute | +|--------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------|---------------------|---------------------------------------| +| USER ID | This Attribute indicates the identity of the user. More detailed description of the IE can be found in IETF RFC 3580 [15] and 3GPP TS 23.234 [4]. | Mandatory | Mandatory | User-Name | +| RADIUS Client Address | This Attribute indicates the identifying IP Address of the RADIUS Client. It should be unique to the RADIUS Client within the scope of the RADIUS server. More detailed description of the IE can be found in IETF RFC 3580 [15]. | Mandatory | NA | NAS-IP-Address
NAS-IPv6-Address | +| Acc-Session-ID | According to IETF RFC 2866 [20], this attribute is an accounting ID which uniquely identifies the user's session. | Mandatory | Mandatory | Acct-Session-Id | +| Operator Name | Hot Spot Operator Name as defined in IETF RFC 5580 [16]. | Mandatory | NA | Operator-Name | +| Location Information | This Attribute contains meta-data about the location information, such as sighting time, time-to-live, location-determination method, etc, as defined in IETF RFC 5580 [16]. It also indicates the type of location profile (civic or geospatial) contained in the Location-Data Attribute. | Mandatory | NA | Location-Information | +| Location Data | This Attribute contains the civic or geospatial location of the hotspot operator as defined in IETF RFC 5580 [16]. | Mandatory | NA | Location-Data | +| Basic Location Policy Rules | This Attribute contains basic policy rules for controlling the distribution of location information as defined in IETF RFC 5580 [16], e.g. retention expiry, URI of human-readable privacy instructions. | Optional | NA | Basic-Location-Policy-Rules | +| Extended Location Policy Rules | This Attribute contains a URI that indicates where a richer set of policy rules for controlling the distribution of location information can be found as defined in IETF RFC 5580 [16]. | Optional | NA | Extended-Location-Policy-Rules | +| Acct.Status Type | Indicates whether this is:
(i) Accounting Start.
(ii) Stop.
(iii) Interim Report. Accounting start indicates that this is the beginning of the user service, Account stop the end. | Mandatory | N/A | Acct-Status-Type | +| Acc-Input-octets | Indicates the number of octets sent by the WLAN UE over the course of the session. According to the IETF RFC 5080 [39], updating the IETF RFC 2866 [20], shall only be present if ACC Status Type is set to "Interim" or "Stop". | Conditional. Shall be present if Acct-Status-Type set to "Accounting Interim" or "Accounting Stop". | N/A | Acct-Input-Octets | +| Acc-Output Octets | Indicates the number of octets received by the WLAN-UE. According to the IETF RFC 5080 [39], updating the IETF RFC 2866 [20], shall only be present if ACC Status Type is set to Interim" or "Stop". | Conditional. Shall be present if Acct-Status-Type set to "Accounting Interim" or "Accounting Stop". | N/A | Acct-Output-Octets | +| Acc-Session-Time | This attribute indicates how many seconds the user has received service for. According to the IETF RFC 5080 [39], updating the IETF RFC 2866 [20], shall only be present if ACC Status Type is set to "Interim" or "Stop". | Conditional. Shall be present if Acct-Status-Type set to "Accounting Interim" or "Accounting Stop". | N/A | Acct-Session-Time | +| Acc-Input-Packets | Indicates the number of packets sent by the WLAN UE over the course of the session. According to the IETF RFC 5080 [39], updating the IETF RFC 2866 [20], shall only be present if ACC Status Type is set to Interim" or "Stop". | Optional | N/A | Acct-Input-Packets | +| Acc-Output-Packets | Indicates the number of packets received by the WLAN-UE over the course of the session. According to the IETF RFC 5080 [39], updating the IETF RFC 2866 [20], shall only be present if ACC Status Type is set to Interim" or "Stop". | Optional | N/A | Acct-Output-Packets | +| Acc-Terminate-Cause | Indicates how the session was stopped. Cause values are as per specified in IETF RFC 3580 [15]. According to the IETF RFC 5080 [39], updating the IETF RFC 2866 [20], shall only be present if ACC Status Type is set to "Stop". | Conditional. Shall be present if Acct-Status-Type set to "Accounting Stop". | N/A | Acct-Terminate-Cause | +| Event Time Stamp | Number of second elapsed since January 1 st 1970. UTC time. | Mandatory | NA | Event-Time-Stamp | +| Chargeable User Identity | This attribute shall contain the MSISDN and/or the IMSI of the user. The encoding of the MSISDN and the IMSI is defined in GSMA PDR IR.61 [25]. | Mandatory | NA | Chargeable-User-Id | +| Visited Operator Identity | Identifies the VPLMN as specified in GSMA PRD IR.61 [25] | Mandatory | NA | Vendor-Specific (Visited-Operator-Id) | +| Session ID | This attribute is used to link related authentication and accounting sessions and should be included unmodified to accounting request messages. | Conditional. Shall be present if received in an Access Accept. | NA | Class | + +| | | | | | +|-----------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------|----|-----------------------| +| Acct-Input-Gigawords | This attribute indicates how many times the Acct-Input-Octets counter has wrapped around 2 32 and can only be present when Acct-Status-Type is set to Stop or Interim-Update. See IETF RFC 2869 [9]. | Conditional. Shall be present if Acct-Input-Octets wraps around 2 32 . | NA | Acct-Input-Gigawords | +| Acct-Output-Gigawords | This attribute indicates how many times the Acct-Output-Octets counter has wrapped around 2 32 and can only be present when Acct-Status-Type is set to Stop or Interim-Update. See IETF RFC 2869 [9]. | Conditional. Shall be present if Acct-Output-Octets wraps around 2 32 . | NA | Acct-Output-Gigawords | + +The parameters listed above as 'mandatory' are only optional in the particular RADIUS (extension) specification in which they are originally defined. However, in order for 3GPP WLAN-IW to function, these attributes shall be passed in messaging over the Wd interface as per the definition in the table. In this sense they are mandatory. In practice, this means that, should any of these parameters labelled 'mandatory' be missing from the RADIUS messaging over Wd, this will result in a higher level failure of WLAN-IW procedures to function properly and consequently in a denial of the RADIUS request (even though this was a valid RADIUS message). + +# --- 6 Wx Description + +## 6.1 Functionality + +The Wx reference point is defined between the 3GPP AAA Server and the HSS. The description of the reference point and its functionality is given in 3GPP TS 23.234 [4]. + +## 6.2 Protocols + +The Wx reference point shall be Diameter based and shall have an application ID defined for it. It is defined as an IETF vendor specific Diameter application, where the vendor is 3GPP. The application identifier is to 16777219. It is assigned by IANA (). + +## 6.3 Procedures Description + +### 6.3.1 Authentication Procedures + +According to the requirements described in clause 6.1, Wx reference point shall enable: + +- Retrieval of authentication vectors (triplets and quintuplets) from HSS. +- Checking of user subscription information at the HSS + +This procedure is used between the 3GPP AAA Server and the HSS. The procedure is invoked by the 3GPP AAA Server when a new set of authentication information for a given subscriber is to be retrieved from an HSS. This can happen for example, when a new 3GPP subscriber has accessed the 3GPP AAA Server for authentication or when a new set of authentication information is required for one of the 3GPP subscribers already registered in the 3GPP AAA server. The procedure shall be invoked by 3GPP AAA Server when it detects that the VPLMN selected by a user has changed. This can happen, for example, when a user is performing a VPLMN re-selection procedure and is initiating a new authentication procedure via a new VPLMN. + +The Wx reference point performs the authentication data download based on the reuse of the existing Cx authentication command code set (MAR/MAA), see 3GPP TS 29.228 [5] and 3GPP TS 29.229 [6]. It corresponds to the combination of the operations Auth-Info-Request and Auth-Info-Response (see 3GPP TS 23.234 [4]) and is used: + +- To retrieve authentication vectors from the HSS. +- To resolve synchronization failures between the sequence numbers in the WLAN-UE and the HSS. + +**Table 6.3.1.1: Authentication request** + +| Information element name | Mapping to Diameter AVP | Cat. | Description | +|---------------------------------|--------------------------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Permanent User Identity | User-Name | M | This information element contains the permanent identity of the user, i.e. the IMSI. | +| Visited Network Identifier | Visited-Network-Identifier | C | Identifier that allows the home network to identify the Visited Network. The 3GPP AAA Server shall include this information element in the roaming case i.e. when 3GPP AAA Server receives this information element from signalling across the Wd.
Editor's note: See 3GPP TS 29.229 [6] for a description of this parameter | +| Number Authentication Items | SIP-Number-Auth-Items | M | This information element indicates the number of authentication vectors requested | +| Authentication Data | SIP-Auth-Data-Item | C | See tables 6.3.1.2 and 6.3.1.3 for the contents of this information element. The content shown in table 6.3.1.2 shall be used for a normal authentication request; the content shown in table 6.3.1.3 shall be used for an authentication request after synchronization failure. | +| Routing Information | Destination-Host | C | If the 3GPP AAA Server knows the HSS name, this AVP shall be present.
This information is available if the 3GPP AAA Server already has the HSS name stored. The HSS name is obtained from the Origin-Host AVP, which is received from a previous command from the HSS or from the SLF.
Otherwise only the Destination-Realm is included so that it is resolved to an HSS address in an SLF-like function. Once resolved the Destination-Host AVP is included with the suitable HSS address and it is stored in the 3GPP AAA Server for further usage. | +| Access Type | NAS-Port-Type | M | This AVP shall contain the value 19 (Wireless - IEEE 802.11) if the user accessed the I-WLAN network by WLAN Direct IP Access and shall contain the value 5 (Virtual) if the user accessed the I-WLAN network by WLAN 3GPP IP Access, according to IETF RFC 2865 [17]. | + +**Table 6.3.1.2: Authentication Data content - request** + +| Information element name | Mapping to Diameter AVP | Cat. | Description | +|---------------------------------|--------------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------| +| Authentication Method | Authentication Method | M | This information element indicates the authentication method compatible with the smart card (SIM or USIM).
It shall contain EAP/SIM or EAP/AKA values. | + +**Table 6.3.1.3: Authentication Data content - request, synchronization failure** + +| Information element name | Mapping to Diameter AVP | Cat. | Description | +|---------------------------------|--------------------------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Authentication Method | Authentication Method | M | This information element indicates the authentication method compatible with the smart card (SIM or USIM).
It shall contain EAP/SIM or EAP/AKA values. | +| Authorization Information | SIP-Authorization | M | It shall contain the concatenation of nonce, as sent to the terminal, and auts, as received from the terminal. Nonce and auts shall both be binary encoded. | + +**Table 6.3.1.4: Authentication answer** + +| Information element name | Mapping to Diameter AVP | Cat. | Description | +|-----------------------------|-----------------------------------|------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Permanent User Identity | User-Name | M | This information element contains the permanent identity of the user, i.e. the IMSI. | +| Number Authentication Items | SIP-Number-Auth-Items | C | This AVP indicates the number of authentication vectors delivered in the Authentication Data information element.
It shall be present when the result is DIAMETER_SUCCESS. | +| Authentication Data | SIP-Auth-Data-Item | C | If the SIP-Number-Auth-Items AVP is equal to zero or it is not present, then this AVP shall not be present.
See table 6.3.1.5 for the contents of this information element. | +| 3GPP AAA Server Name | 3GPP-AAA-Server-Name | C | This AVP contains the Diameter address of the 3GPP AAA Server.
This AVP shall be sent when the user has been previously authenticated by another 3GPP AAA Server and therefore there is another 3GPP AAA Server serving the user. | +| Result | Result-Code / Experimental-Result | M | Result of the operation.
Result-Code AVP shall be used for errors defined in the Diameter Base Protocol.
Experimental-Result AVP shall be used for Wx errors. This is a grouped AVP which contains the 3GPP Vendor ID in the Vendor-Id AVP, and the error code in the Experimental-Result-Code AVP. | + +**Table 6.3.1.5: Authentication Data content - response** + +| Information element name | Mapping to Diameter AVP | Cat. | Description | +|--------------------------------|--------------------------------|------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Item Number | SIP-Item-Number | C | This information element shall be present in a SIP-Auth-Data-Item grouped AVP in circumstances where there are multiple occurrences of SIP-Auth-Data-Item AVPs, and the order in which they should be processed is significant.
In this scenario, SIP-Auth-Data-Item AVPs with a low SIP-Item-Number value should be processed before SIP-Auth-Data-Items AVPs with a high SIP-Item-Number value. | +| Authentication Method | Authentication Method | M | This information element indicates the authentication method compatible with the smart card (SIM or USIM).
It shall contain EAP/SIM or EAP/AKA values. | +| Authentication Information AKA | SIP-Authenticate | C | It shall contain, binary encoded, the concatenation of the authentication challenge RAND and the token AUTN. See 3GPP TS 33.203 [3] for further details about RAND and AUTN.
It shall be present when SIP_Authentication_Scheme AVP is set to EAP/AKA. | +| Authorization Information AKA | SIP-Authorization | C | It shall contain binary encoded, the expected response XRES. See 3GPP TS 33.203 [3] for further details about XRES.
It shall be present when SIP_Authentication_Scheme AVP is set to EAP/AKA. | +| Confidentiality Key AKA | Confidentiality-Key | C | This information element, if present, shall contain the confidentiality key. It shall be binary encoded.
It shall be present when SIP_Authentication_Scheme AVP is set to EAP/AKA. | +| Integrity Key AKA | Integrity-Key | C | This information element shall contain the integrity key. It shall be binary encoded.
It shall be present when SIP_Authentication_Scheme AVP is set to EAP/AKA. | +| Authentication Information SIM | Authentication_Information_SIM | C | This information element shall contain the concatenation of authentication challenge RAND and the ciphering key Kc. It shall be binary encoded.
It shall be present when SIP_Authentication_Scheme AVP is set to EAP/SIM. | +| Authorization Information | Authorization_Information_SIM | C | This information element shall contain the response SRES. It shall be binary encoded.
It shall be present when SIP_Authentication_Scheme AVP is set to EAP/SIM. | + +#### 6.3.1.1 Detailed behaviour + +The HSS shall, in the following order (if there is an error in any of the steps, the HSS shall stop processing and return the corresponding error code): + +1. Check that the user exists in the HSS. If not Experimental-Result-Code shall be set to DIAMETER\_ERROR\_USER\_UNKNOWN. +2. Check that the user has 3GPP-WLAN subscription. If not Experimental-Result-Code shall be set to DIAMETER\_ERROR\_USER\_NO\_WLAN\_SUBSCRIPTION. +3. If a Visited-Network-Identifier is present, check that the user is allowed to roam in the visited network. If the user is not allowed to roam in the visited network, Experimental-Result-Code shall be set to DIAMETER\_ERROR\_ROAMING\_NOT\_ALLOWED. +4. Check NAS-Port-Type AVP. If the access type indicates WLAN Direct IP Access, the process continues as stated in step 5. If the access type indicates WLAN 3GPP IP access, the HSS shall check the dependence permissions that the user has with regard to the access type. + - If the Access\_Dependence flag of the user is set and the user has been already authenticated by WLAN Direct IP Access, the process continues as stated in step 5. + - If the Access\_Dependence flag of the user is set and the user has not been already authenticated by WLAN Direct IP Access, the authentication shall be denied by sending to the 3GPP AAA Server an answer message with Experimental-Result-Code set to DIAMETER\_ERROR\_NO\_ACCESS\_INDEPENDENT\_SUBSCRIPTION. + - If the Access\_Dependence flag of the user is cleared, the user is allowed to request WLAN 3GPP IP access authentication with no regard to any other previous authentication, so the process continues as stated in step 5. +5. The HSS shall check if there is an existing 3GPP AAA Server already assisting the user + - If there is a 3GPP AAA Server already serving the user, the HSS shall check the request type. + - If the request indicates there is a synchronization failure, the HSS shall compare the 3GPP AAA Server name received in the request to the 3GPP AAA Server name stored in the HSS. If they are identical, the HSS shall process AUTS as described in 3GPP TS 33.203 [3] and return the requested authentication information. The Result-Code shall be set to DIAMETER\_SUCCESS. + - If the request indicates authentication, the HSS shall return the old 3GPP AAA Server to the requester 3GPP AAA Server. The Result-Code shall be set to DIAMETER\_SUCCESS. + +The requester 3GPP AAA Server, upon detection of a 3GPP AAA Server name in the response assumes that the user already has a 3GPP AAA Server assigned, so makes use of Diameter redirect function to indicate the 3GPP AAA Server name where to address the authentication request. For cases where RADIUS is used over the Wa and Wd interfaces, the 3GPP AAA Server shall use procedures defined on Wa/Wd interface to refuse the connection request. For recommendations as to how to avoid the frequent occurrence of such situations and to mitigate them when they do, please refer to Annex X of this specification + +- If there is no a 3GPP AAA Server already serving the user, the HSS shall store the 3GPP AAA Server name. The HSS shall download Authentication-Data-Item stored up to a maximum specified in SIP-Number-Auth-Items received in the command Multimedia-Auth-Request. The Result-Code shall be set to DIAMETER\_SUCCESS. Exceptions to the cases specified here shall be treated by HSS as error situations, the Result-Code shall be set to DIAMETER\_UNABLE\_TO\_COMPLY. No authentication information shall be returned. + +NOTE: Origin-Host AVP shall contain the 3GPP AAA Server identity. + +### 6.3.2 Location Management Procedures + +#### 6.3.2.1 WLAN Registration/DeRegistration Notification + +According to the requirements described in clause 6.1, Wx reference point shall enable: + +- Registration of the 3GPP AAA Server of an authorized WLAN user in the HSS. +- Retrieval of online charging / offline charging function addresses from HSS. +- Purge procedure between the 3GPP AAA Server and the HSS. +- Retrieval of WLAN subscriber profile from HSS. + +This procedure is used between the 3GPP AAA Server and the HSS. + +- To register the current 3GPP AAA Server address in the HSS for a given 3GPP user. This procedure is invoked by the 3GPP AAA Server after a new subscriber has been authenticated by the 3GPP AAA Server. +- To de-register the current 3GPP AAA Server address in the HSS for a given 3GPP user. When WLAN UE has disappeared from WLAN coverage or when the OCS has initiated a disconnection, the 3GPP AAA Server informs the HSS about an ongoing disconnection process and the HSS de-registers the WLAN user. +- To download the subscriber profile under 3GPP AAA Server demand. This procedure is invoked when for some reason the subscription profile of a subscriber is lost. + +The Wx interface performs these functions based on the reuse of the existing Cx server assignment command code set (SAR/SAA), see 3GPP TS 29.228 [5] and 3GPP TS 29.229 [6]. It corresponds to the combination of the operations WLAN-Registration and WLAN-Registration-Confirm for the registration procedure, Purge\_WLAN\_INFO and Purge\_WLAN\_INFO\_Ack for the de-registration procedure initiated by the 3GPP AAA server and Subscriber-Profile-Request (see 3GPP TS 23.234 [4]) for the profile download procedure initiated by the 3GPP AAA server. + +**Table 6.3.2.1: WLAN Registration request** + +| Information element name | Mapping to Diameter AVP | Cat. | Description | +|---------------------------------------|-------------------------|------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Permanent User Identity | User-Name | M | This information element contains the permanent identity of the user, i.e. the IMSI. | +| Server Assignment Type | Server-Assignment-Type | M | Type of procedure the 3GPP AAA Server requests in the HSS.
When this IE contains REGISTRATION value, the HSS performs a registration of the WLAN user.
When this IE contains USER_DEREGISTRATION / ADMINISTRATIVE_DEREGISTRATION / AUTHENTICATION_FAILURE the HSS performs a de-registration of the WLAN user.
When this IE contains NO_ASSIGNMENT value, the HSS initiates the download of the subscriber user profile towards the 3GPP AAA Server, but no registration is performed.
Any other value is considered as an error case. | +| Routing Information (See clause 7.13) | Destination-Host | C | If the 3GPP AAA Server knows the HSS name this AVP shall be present. This information is available if the 3GPP AAA Server already has the HSS name stored. The HSS name is obtained from the Origin-Host AVP, which is received from the HSS, e.g. included in the MAA command. Otherwise only the Destination-Realm is included so that it is resolved to an HSS address in an SLF-like function. Once resolved the Destination-Host AVP is included with the suitable HSS address and it is stored in the 3GPP AAA Server for further usage. | + +**Table 6.3.2.2: Subscriber profile retrieval response** + +| Information element name | Mapping to Diameter AVP | Cat. | Description | +|--------------------------|-----------------------------------|------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Permanent User Identity | User-Name | M | This information element contains the permanent identity of the user, i.e. the IMSI. | +| Registration result | Result-Code / Experimental-Result | M | Result of the operation.
Result-Code AVP shall be used for errors defined in the Diameter Base Protocol.
Experimental-Result AVP shall be used for Wx errors. This is a grouped AVP which contains the 3GPP Vendor ID in the Vendor-Id AVP, and the error code in the Experimental-Result-Code AVP. | +| User Profile | WLAN-User-Data | C | Relevant user profile.
It shall be present when Server-Assignment-Type in the request is equal to NO_ASSIGNMENT. | +| Charging Information | Charging-Data | C | Addresses of the charging functions.
It shall be present when Server-Assignment-Type in the request is equal to REGISTRATION or NO_ASSIGNMENT and the Result-Code is equal to DIAMETER_SUCCESS.
When this parameter is included, the Primary-Charging-Collection-Function-Name or the Primary-OCS-Charging-Function-Name shall be included. All other elements shall be included if they are available. | + +##### 6.3.2.1.1 Detailed behaviour + +When a new 3GPP subscriber has been authenticated by the 3GPP AAA Server, the 3GPP AAA Server initiates the registration towards the HSS. The HSS shall, in the event of an error in any of the steps, stop processing and return the corresponding error code, see 3GPP TS 29.229 [6]. + +The 3GPP AAA server sends Server-Assignment-Request command to the HSS indicating the registration procedure. The subscriber is identified by the User-Name AVP. + +At reception of Server-Assignment-Request command, the HSS shall perform (in the following order): + +1. Check that the user is known. If not Experimental-Result-Code shall be set to DIAMETER\_ERROR\_USER\_UNKNOWN. +2. Check the Server Assignment Type value received in the request: + - If it indicates REGISTRATION, the HSS shall check that the 3GPP AAA Server name stored for the subscriber matches the 3GPP AAA Server name received in the request, set the subscribers User Status to REGISTERED for the authenticated and authorized 3GPP subscriber and set the Result-Code AVP to DIAMETER\_SUCCESS in the Server-Assignment-Response command. + - If it indicates USER\_DEREGISTRATION / ADMINISTRATIVE\_DEREGISTRATION / AUTHENTICATION\_FAILURE, the HSS shall remove the 3GPP AAA Server name previously assigned for the 3GPP subscriber, set the User Status for the subscriber to NOT\_REGISTERED and set the Result-Code AVP to DIAMETER\_SUCCESS in the Server-Assignment-Response command. + - If it indicates NO\_ASSIGNMENT, the HSS shall check that the 3GPP AAA Server name stored for the subscriber matches the 3GPP AAA Server name received in the request, download the relevant user identity information and set the Result-Code AVP to DIAMETER\_SUCCESS in the Server-Assignment-Response command. + - If it indicates any other value, the Result-Code shall be set to DIAMETER\_UNABLE\_TO\_COMPLY, and no registration/de-registration or profile download procedure shall be performed. + +NOTE: Origin-Host AVP shall contain the 3GPP AAA server identity. + +Once the 3GPP AAA server has downloaded the user profile data as a result of successful registration to the HSS, the 3GPP AAA server shall create appropriate routing policies and IP filtering information according to the retrieved operator defined barring information. These routing policies and IP filtering informations are used for the subsequent W-APN authorizations. + +#### 6.3.2.2 Network Initiated De-Registration by HSS, Administrative + +According to the requirements described in clause 6.1, Wx reference point shall enable: + +- Purge procedure between the 3GPP AAA Server and the HSS. + +This procedure is used between the 3GPP AAA Server and the HSS. When the purge procedure is initiated by the HSS, indicates that a subscription has to be removed from the 3GPP AAA Server, when the purge procedure is initiated by the 3GPP AAA Server see clause 6.3.2.1. + +The Wx interface performs the cancellation of a registration initiated by the HSS based on the reuse of the existing Cx registration termination command code set (RTR/RTA), see 3GPP TS 29.228 [5] and 3GPP TS 29.229[6]. It corresponds to the combination of the operations CANCEL\_WLAN\_REGISTRATION and CANCEL\_WLAN\_REGISTRATION\_ACK (see 3GPP TS 23.234 [4]). + +**Table 6.3.2.3: Network Initiated Deregistration by HSS request** + +| Information element name | Mapping to Diameter AVP | Cat. | Description | +|----------------------------|-------------------------|------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Permanent User Identity | User-Name | M | This information element contains the permanent identity of the user, i.e. the IMSI. | +| Reason for de-registration | Deregistration-Reason | M | The HSS shall send to the 3GPP AAA server a reason for the de-registration.
The de-registration reason is composed of two parts: one textual message (if available) that is intended to be forwarded to the user that is de-registered, and one reason code (see 3GPP TS 29.229 [6]) that determines the behaviour of the 3GPP AAA Server. | +| Routing Information | Destination-Host | M | The 3GPP AAA server name is obtained from the Origin-Host AVP, which is received from the 3GPP AAA Server, e.g. included in the MAR command. | + +**Table 6.3.2.4: Network Initiated Deregistration by HSS response** + +| Information element name | Mapping to Diameter AVP | Cat. | Description | +|--------------------------|-----------------------------------|------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Result | Result-Code / Experimental-Result | M | Result of the operation.
Result-Code AVP shall be used for errors defined in the Diameter Base Protocol.
Experimental-Result AVP shall be used for Wx errors. This is a grouped AVP which contains the 3GPP Vendor ID in the Vendor-Id AVP, and the error code in the Experimental-Result-Code AVP. | + +##### 6.3.2.2.1 Detailed behaviour + +The HSS shall de-register the affected identity and invoke this procedure to inform the 3GPP AAA server to remove the subscribed user from the 3GPP AAA Server. + +The HSS shall send in the Deregistration-Reason AVP the reason for the de-registration, composed by a textual message (if available) aimed for the user and a reason code that determines the action the 3GPP AAA server has to perform. The possible reason codes are: + +- PERMANENT\_TERMINATION: The WLAN subscription or service profile(s) has been permanently terminated. The HSS shall clear the user's 3GPP AAA Server name and set the User Status to NOT\_REGISTERED. The 3GPP AAA Server should start the network initiated de-registration towards the user. + +### 6.3.3 User Data Handling + +#### 6.3.3.1 Void + +#### 6.3.3.2 HSS Initiated Update of User Profile + +According to the requirements described in clause 6.1, Wx reference point shall enable: + +- Indication to 3GPP AAA Server of change of WLAN subscriber profile within HSS. + +This procedure is used between the 3GPP AAA Server and the HSS. The procedure is invoked by the HSS when the subscriber profile has been modified and needs to be sent to the 3GPP AAA Server. This may happen due to a modification in the HSS. + +The Wx reference point performs the download of the subscriber profile initiated by the HSS based on the reuse of the existing Cx profile download command code set (PPR/PPA), see 3GPP TS 29.228 [5] and 3GPP TS 29.229[6]. It corresponds to the combination of the operations SUBSCRIBER\_PROFILE and PROFILE\_ACK (see 3GPP TS 23.234 [4]). + +**Table 6.3.3.1: User Profile Update request** + +| Information element name | Mapping to Diameter AVP | Cat. | Description | +|--------------------------|-------------------------|------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Permanent User Identity | User-Name | M | This information element contains the permanent identity of the user, i.e. the IMSI. | +| User profile | WLAN-User-Data | C | Updated user profile.
It shall be present if the user profile is changed in the HSS. If the WLAN-User-Data AVP is not present, the Charging-Information AVP shall be present. | +| Charging Information | Charging-Data | C | Addresses of the charging functions.
If the Charging-Information AVP is not present, the WLAN-User-Data AVP shall be present. | +| Routing Information | Destination-Host | M | The 3GPP AAA Server name is obtained from the Origin-Host AVP, which is received from the 3GPP AAA Server, e.g. included in the MAR command. | + +**Table 6.3.3.2: User Profile Update response** + +| Information element name | Mapping to Diameter AVP | Cat. | Description | +|--------------------------|-----------------------------------|------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Result | Result-Code / Experimental-Result | M | Result of the operation.
Result-Code AVP shall be used for errors defined in the Diameter Base Protocol.
Experimental-Result AVP shall be used for Wx errors. This is a grouped AVP which contains the 3GPP Vendor ID in the Vendor-Id AVP, and the error code in the Experimental-Result-Code AVP. | + +##### 6.3.3.2.1 Detailed behaviour + +The HSS shall make use of this procedure to update relevant user profile or charging information in the 3GPP AAA server. + +The 3GPP AAA server shall overwrite, for the subscriber identity indicated in the request, current information with the information received from the HSS, except in the error situations detailed in table 6.3.3.3. + +After a successful user profile download the 3GPP AAA server shall initiate re-authentication procedure as described in sub-clause 4.3.4 if the subscriber has previously been authenticated and authorized to 3GPP Direct Access. If the subscriber has previously been authenticated and authorized to WLAN 3GPP IP Access then the 3GPP AAA server shall initiate a re-authorization procedure as described in sub-clause 8.3.5. + +Table 6.3.3.3 details the valid result codes that the 3GPP AAA server can return in the response. + +**Table 6.3.3.3: User profile response valid result codes** + +| Result-Code AVP value | Condition | +|-----------------------------|----------------------------------------------------------------------| +| DIAMETER_SUCCESS | The request succeeded. | +| DIAMETER_ERROR_USER_UNKNOWN | The request failed because the user is not found in 3GPP AAA Server. | +| DIAMETER_UNABLE_TO_COMPLY | The request failed. | + +## 6.4 Information Elements Contents + +### 6.4.1 Authentication Procedures + +The Multimedia-Authentication-Request (MAR) command, indicated by the Command-Code field set to 303 and the 'R' bit set in the Command Flags field, is sent by the 3GPP AAA Server to the HSS in order to request security information. + +#### Message Format + +``` +< Multimedia-Authentication-Request > ::= < Diameter Header: 303, REQ, 16777219 > + < Session-Id > + { Vendor-Specific-Application-Id } + { Auth-Session-State } + { Origin-Host } + { Origin-Realm } + { Destination-Realm } + [ Destination-Host ] + { NAS-Port-Type } + { User-Name } + [ Visited-Network-Identifier ] + [ SIP-Auth-Data-Item ] + [ SIP-Number-Auth-Items ] + * [ AVP ] + * [ Proxy-Info ] + * [ Route-Record ] +``` + +The Multimedia-Authentication-Answer (MAA) command, indicated by the Command-Code field set to 303 and the 'R' bit cleared in the Command Flags field, is sent by a server in response to the Multimedia-Authentication-Request command. The Result-Code or Experimental-Result AVP may contain one of the values defined in section 6.2 of 3GPP TS 29.229 [6] in addition to the values defined in RFC 3588 [7]. + +#### Message Format + +``` +< Multimedia-Authentication-Answer > ::= < Diameter Header: 303, 16777219 > + < Session-Id > + { Vendor-Specific-Application-Id } + [ Result-Code ] + [ Experimental-Result ] + { Auth-Session-State } + { Origin-Host } + { Origin-Realm } + { User-Name } + [ SIP-Number-Auth-Items ] + [ SIP-Auth-Data-Item ] + [ 3GPP-AAA-Server-Name ] + * [ AVP ] + * [ Proxy-Info ] + * [ Route-Record ] +``` + +### 6.4.2 HSS Initiated Update of User Profile + +The Push-Profile-Request (PPR) command, indicated by the Command-Code field set to 305 and the 'R' bit set in the Command Flags field, is sent by the HSS to the 3GPP AAA Server in order to update the subscription data of a WLAN user in the 3GPP AAA Server whenever a modification has occurred in the subscription data. + +``` +< Push-Profile-Request > ::= < Diameter Header: 305, REQ, 16777219 > + < Session-Id > + { Vendor-Specific-Application-Id } + { Auth-Session-State } + { Origin-Host } + { Origin-Realm } + { Destination-Host } + { Destination-Realm } + { User-Name } + [ WLAN-User-Data ] + [ Charging-Data ] + * [ AVP ] + * [ Proxy-Info ] + * [ Route-Record ] +``` + +The Push-Profile-Answer (PAA) command, indicated by the Command-Code field set to 305 and the 'R' bit cleared in the Command Flags field, is sent by the HSS in response to the Push-Profile-Request command. The Result-Code or Experimental-Result AVP may contain one of the values defined in section 6.2 of 3GPP TS 29.229 [6] in addition to the values defined in RFC 3588 [7]. + +``` +< Push-Profile-Answer > ::= < Diameter Header: 305, 16777219 > + < Session-Id > + { Vendor-Specific-Application-Id } + [Result-Code ] + [ Experimental-Result ] + { Auth-Session-State } + { Origin-Host } + { Origin-Realm } + *[ AVP ] + *[ Proxy-Info ] + *[ Route-Record ] +``` + +### 6.4.3 Registration procedure and Profile download in Wx + +The Server-Assignment-Request (SAR) command, indicated by the Command-Code field set to 301 and the 'R' bit set in the Command Flags field, is sent by the 3GPP AAA Server to the HSS in order to register or deregister a WLAN user or to download the WLAN User Profile. + +#### Message Format + +``` +< Server-Assignment-Request > ::= < Diameter Header: 301, REQ, PXY, 16777219 > + < Session-Id > + { Vendor-Specific-Application-Id } + { Auth-Session-State } + { Origin-Host } + { Origin-Realm } + [ Destination-Host ] + { Destination-Realm } + { User-Name } + { Server-Assignment-Type } + *[ AVP ] + *[ Proxy-Info ] + *[ Route-Record ] +``` + +The Server-Assignment-Answer (SAA) command, indicated by the Command-Code field set to 301 and the 'R' bit cleared in the Command Flags field, is sent by the HSS to the 3GPP AAA Server to confirm the registration, de-registration or user profile download procedure. The Result-Code or Experimental-Result AVP may contain one of the values defined in section 6.2 of 3GPP TS 29.229 [6] in addition to the values defined in RFC 3588 [7]. + +#### Message Format + +``` +< Server-Assignment-Answer > ::= < Diameter Header: 301, 16777219 > + < Session-Id > + { Vendor-Specific-Application-Id } + [ Result-Code ] + [ Experimental-Result ] + { Auth-Session-State } + { Origin-Host } + { Origin-Realm } + { User-Name } + [ WLAN-User-Data ] + [ Charging- Data ] + *[ AVP ] + *[ Proxy-Info ] + *[ Route-Record ] + *[ Route-Record ] +``` + +### 6.4.4 Registration Termination in Wx + +This procedure is an exact copy of the existing Registration-Termination-Request (RTR) / Registration-Termination-Answer (RTA) commands from Cx reference point. See 3GPP TS 29.229 [6]. + +WLAN Wx reference point shall not make use of the optional Public-Identity AVP defined in RTR command. + +## 6.5 Void + +## 6.6 User identity to HSS resolution + +The User identity to HSS resolution mechanism enables the 3GPP AAA Server to find the address of the HSS, that holds the subscriber data for a given user identity when multiple and separately addressable HSSs have been deployed by the network operator. The resolution mechanism is not required in networks that utilize a single HSS. + +The resolution mechanism described in 3GPP TS 23.234 [4] is based on the Subscription Locator Function (SLF), already used in the IMS architecture 3GPP TS 29.228 [5]. The subscription locator is accessed via the Dw interface. The Dw interface is only used in conjunction with the Wx interface. The Dw interface is based on Diameter. Its functionality is implemented by means of the routing mechanism provided by an enhanced Diameter redirect agent, which is able to extract the identity of the user from the received requests. + +To get the HSS address the 3GPP AAA Server sends to the SLF the Wx requests aimed for the HSS. On receipt of the HSS address from the SLF, the 3GPP AAA Server shall send the Wx requests to the HSS. Further requests associated to the same user shall make use the stored HSS address. + +In networks where the use of the user identity to HSS resolution mechanism is required, each 3GPP AAA Server shall be configured with the address/name of the SLF implementing this resolution mechanism. + +Note: The user identity to perform the HSS resolution is the IMSI. + +# --- 7 Void + +# --- 8 Wm Description + +## 8.1 Functionality + +The Wm reference point is defined between the 3GPP AAA Server and the PDG. The description of the reference point and its functionality is given in 3GPP TS 23.234 [4]. + +This clause specifies a Diameter application that supports the functionality of this reference point. + +In the roaming case, the 3GPP AAA Proxy shall act as a stateful proxy between the PDG and 3GPP AAA Server. + +The Wm reference point shall also support procedures in order that an IMS emergency call specific W-APN shall be supported. + +## 8.2 Protocols + +Diameter EAP application is used for authentication and optionally authorization of the user. In this case, the PDG shall act as the NAS, as described in 3GPP TS 33.234 [18]. For authorization only procedure and other Wm functionalities, NASREQ and base protocol procedures are used. + +The Application-Id to be advertised over Wm reference point corresponds to the EAP, NASREQ or Diameter Base Protocol Application-Id, depending on the command sent over Wm. + +## 8.3 Procedures Description + +### 8.3.1 Authentication and Authorization Procedures + +According to the requirements specified in chapter 8.1, Wm reference point shall enable: + +- Messaging for service authentication between WLAN UE and 3GPP AAA Server/Proxy. +- Carrying messages for service authorization between PDG and 3GPP AAA Server/Proxy. +- Allow the 3GPP AAA Server/Proxy to retrieve tunnelling attributes and WLAN UE's IP configuration parameters from/via Packet Data Gateway. + +The authentication and authorization procedure is used between the PDG and 3GPP AAA Server/Proxy. It is invoked by the PDG, on receipt from the WLAN-UE of a "tunnel establishment request" message. This takes the form of forwarding an IKE v2 (3GPP TS 33.234 [18]) exchange with the purpose of authenticating in order to set up an IKE Security Association (SA) between the UE and the PDG. The PDG may optionally request for Authorization in the same procedure by indicating so in the Authentication-Request-Type AVP. In this case, additional AVPs may be sent in the request. Once the IKE SA has been authenticated, more than one tunnel IPSec SA can be negotiated inside the IKE SA. Hence additional (IPSec) tunnels between the UE and PDG do not need to trigger further Diameter\_EAP authentication messaging to the 3GPP AAA Server. + +The UE may attempt to set up additional accesses (IKE SA) via the IKE\_SA procedure. In such cases, the authentication procedure is triggered over the Wm interface. Each new additional IKE SA shall be handled in a different Diameter session. + +The Wm reference point performs authentication based on the reuse of the DER/DEA command set defined in Diameter\_EAP (3GPP TS 33.234 [18]). + +**Table 8.3.1.1: Authentication and Authorization Request** + +| Information element name | Mapping to Diameter AVP | Cat. | Description | +|---------------------------------|----------------------------|------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| User Identity | User-Name | M | This information element contains the identity of the user. | +| EAP payload | EAP payload | M | Encapsulated EAP payload used for UE - 3GPP AAA Server mutual authentication | +| Authentication Request Type | Auth Req Type | M | Defines whether authentication only or authentication and authorization are required. AUTHENTICATION_ONLY is required in this case. Optionnaly AUTHORIZE_AUTHENTICATE may be used to indicate that Authorization is requested in the same procedure. | +| Visited Network Identifier | Visited-Network-Identifier | C | Identifier that allows the home network to identify the Visited Network. This AVP shall be present if the PDG is not in the WLAN-UE's home network i.e. the WLAN-UE is roaming. | +| Access Type | NAS-Port-Type | M | This AVP shall contain the value 5 (Virtual) to indicate that the user accessed the I-WLAN network by WLAN 3GPP IP Access, according to IETF RFC 2865 [17]. | +| W-APN-ID | 3GPP-WLAN-APN-Id | C | This information element contains the W-APN which the UE is requesting authorization. This AVP is present when Authentication-Request-Type AVP is set to AUTHORIZE_AUTHENTICATE. | +| PDG Charging Identifier | PDG-Charging-Id | C | The PDG charging identifier is generated by PDG and used to correlate PDG and WLAN AN charging data. This AVP is present when Authentication-Request-Type AVP is set to AUTHORIZE_AUTHENTICATE. | +| Supported 3GPP WLAN QoS profile | QoS-Capability | O | If the PDG supports QoS mechanisms, this information element may be included to contain PDG's QoS capabilities. This AVP is present when Authentication-Request-Type AVP is set to AUTHORIZE_AUTHENTICATE. | + +**Table 8.3.1.2: Authentication and Authorization Answer** + +| Information element name | Mapping to Diameter AVP | Cat. | Description | +|----------------------------------|----------------------------------------|------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| EAP payload | EAP payload | M | Encapsulated EAP payload used for UE - 3GPP AAA Server mutual authentication | +| Master-Session-Key | Master-Session-Key | C | It contains keying material for protecting the communication between the user and the NAS. Present when Result Code is set to "Success". | +| Result code | Result Code / Experimental-Result-Code | M | Result of the operation.
Result-Code AVP shall be used for errors defined in the Diameter Base Protocol or as per in NASREQ. 1xxx should be used for multi-round, 2xxx for success.
Experimental-Result AVP shall be used for Wm errors. This is a grouped AVP which contains the 3GPP Vendor ID in the Vendor-Id AVP, and the error code in the Experimental-Result-Code AVP. | +| Subscription-ID | Subscription-ID AVP | C | This AVP shall contain the MSISDN and/or the IMSI of the user.
This AVP shall be present if the Diameter Result Code is set to DIAMETER_SUCCESS | +| Max-Subscribed-Bandwidth | Max-Requested-Bandwidth | O | The Max requested bandwidth AVP. Can be sent by the 3GPP AAA Server to the PDG if it is present in the user subscription info held at the 3GPP AAA Server. | +| Charging Information | Charging-Data | C | Charging information for the W-APN for that user.
It shall be present when Result-Code is equal to DIAMETER_SUCCESS and when the received Session-Request-Type was set to AUTHORIZATION REQUEST. | +| Framed-IP-Address | Framed-IP-Address | O | This AVP contains the remote IPv4 address of the WLAN UE that the 3GPP AAA Server downloaded from the HSS.
This AVP shall not be present when the 3GPP AAA Server received an authorisation request with Session-Request-Type AVP set to ROUTING POLICY. | +| Framed-IP-Prefix | Framed-IP-Prefix | O | This AVP contains the remote IPv6 prefix of the WLAN UE that the 3GPP AAA Server downloaded from the HSS.
This AVP shall not be present when the 3GPP AAA Server received an authorisation request with Session-Request-Type AVP set to ROUTING POLICY. | +| Permanent User Identity | User-Name | □ | This information element contains the IMSI of the user. This shall be present if Registration Result Code is set to "Success" and the AAR did not contain the IMSI. | +| WLAN Session Identifier | WLAN-Session-Id | C | This information element contains the charging identifier generated by the 3GPP AAA Server.
It shall be present when Result-Code is equal to DIAMETER_SUCCESS and when the received Session-Request-Type was set to AUTHORIZATION REQUEST, and if WLAN access authentication and authorization procedure is done before tunnel establishment. | +| Authorized 3GPP WLAN QoS Profile | QoS-Resources | O | If both supported 3GPP WLAN QoS profile of the PDG and subscribed QoS profile were received by the 3GPP AAA Server, this IE may be present.
This IE contains the 3GPP WLAN QoS Profile authorized by the 3GPP AAA Server based on the subscribed QoS parameters from the HSS, PDG's QoS capabilities and other information, e.g. operators' policies. | +| Routing Policy | Routing-Policy | O | This AVP includes the routing policy (i.e. IP filters) needed for the Operator Determined Barring purposes. The exact format of this AVP is specified in section 10.1.24. It is up to the PDG implementation whether these routing policies are applied to Wi interface or applied at IPsec level using IKEv2 Traffic Selectors. | + +#### 8.3.1.1 3GPP AAA Server Detailed Behaviour + +On receipt of the DER message, the 3GPP AAA Server shall check if the Session-ID corresponds to an ongoing session. If it corresponds to an on-going session, the 3GPP AAA Server shall process the DER message according to 3GPP TS 33.234 [18] and no Diameter EAP authentication shall be triggered over the Wm interface. + +If, the PDG set the Authentication-Request-Type AVP to AUTHENTICATE\_ONLY and if the Session-ID does not correspond to an on-going session, the 3GPP AAA Server shall: + +- 1) Check that the user exists in the 3GPP AAA Server. If not, the 3GPP AAA Server shall use the procedures defined for the Wx interface to authenticate the user. + +- 2) Check that the user has a 3GPP-WLAN subscription. If not Experimental-Result-Code shall be set to DIAMETER\_ERROR\_USER\_NO\_WLAN\_SUBSCRIPTION. + +Otherwise, DIAMETER\_SUCCESS shall be returned to indicate successful authentication procedure and authentication information shall be returned. + +If the PDG sets the Authentication-Request-Type AVP to AUTHORIZE\_AUTHENTICATE and if the Session-ID does not correspond to an on-going session, the 3GPP AAA Server shall additionally: + +- 3) Check that the user subscription for the W-APN requested. If not, Experimental-Result-Code shall be set to DIAMETER\_ERROR\_USER\_NO\_W-APN\_SUBSCRIPTION. + - 4) Check whether the user has access to that W-APN. This information is obtained from the HSS within the APN-Authorized AVP. If not, Result-Code shall be set to DIAMETER\_AUTHORIZATION\_REJECTED. + - 5) If the user is roaming (indicated by the presence of the Visited-Network-Identifier AVP), the 3GPP AAA Server shall check if the user is allowed to access the W-APN from a VPLMN. This information is obtained from the HSS within the APN-Authorized AVP. If not, Experimental-Result-Code shall be set to DIAMETER\_ERROR\_ROAMING\_NOT\_ALLOWED. +- 6) If the WLAN UE does not already have an active access to this W-APN, the 3GPP AAA Server shall initiate an Access-Number counter for that W-APN and set it to one. If the Access-Number counter has already been initiated, the 3GPP AAA Server shall increment the counter by one. The 3GPP AAA Server shall then check the counter value against the Maximum-Number-Accesses for that W-APN from that user's data. If the Access-Number exceeds Maximum-Number-Accesses, the 3GPP AAA Server shall use the 3GPP AAA Server initiated disconnection procedures towards the PDG with which the user has the oldest established access in order to initiate the tear down of the SA associated with that access. The 3GPP AAA Server shall update accordingly the information of active accesses for the W-APN and shall store the PDG IP address and the Session-ID associated with the access. +- 7) The 3GPP AAA Server shall download user data relevant to the W-APN, e.g. WLAN UE remote IP address if present, routing policies related to barring and the charging information as received from the HSS. The Result-Code shall be set to DIAMETER\_SUCCESS. + +Otherwise, DIAMETER\_SUCCESS shall be returned to indicate successful authentication and authorization procedure and authentication and authorization information shall be returned. + +Exceptions to the cases specified here shall be treated by 3GPP AAA Server as error situations, the Result-Code shall be set to DIAMETER\_UNABLE\_TO\_COMPLY. No authentication information shall be returned. + +#### 8.3.1.2 3GPP AAA Proxy Detailed Behaviour + +The 3GPP AAA Proxy is required to handle roaming cases in which the PDG is in the VPLMN. The 3GPP AAA Proxy shall act as a stateful proxy. The 3GPP AAA server shall check the Request-Type AVP: + +- 1) If Request type indicates AUTHENTICATION\_ONLY, on receipt of the DEA message, it shall record the state of the connection. +- 2) If Request type indicates AUTHORIZE\_AUTHENTICATE, it indicates that the WLAN UE does not have a tunnel active to the particular APN at the PDG and is requesting authorization for such an APN. + - a) The 3GPP AAA Proxy shall check locally configured information whether users from the HPLMN are allowed to access to the W-APN requested from this (V)PLMN. If not, Experimental-Result-Code shall be set to DIAMETER\_ERROR\_ROAMING\_NOT\_ALLOWED and the DEA message sent to the PDG. In all other cases, the message shall be forwarded transparently to the 3GPP AAA Server. + +On receipt of the DEA message, the AAA Proxy shall record the state of the connection (i.e. Authentication Successful). . + +#### 8.3.1.3 Authentication Procedures for the Emergency Case + +For the case where the WLAN-UE is attempting to set up a tunnel (IPSec SA) to the emergency W-APN, authentication shall proceed as described in subclauses 8.3.1.1 and 8.3.1.2 with the following exceptions: + +For IMS emergency calls, authentication may be skipped entirely depending on the national regulations or the operator's preference. If the 3GPP AAA server skips the authentication, it shall send the Authentication Answer including an EAP failure to the PDG. Otherwise, when the checks for an IMS emergency call fail, the 3GPP AAA Server also sends the Authentication Answer including an EAP failure to the PDG. + +Depending on national regulations and operator preferences, in the case of IMS emergency calls, the PDG may continue the procedure even though authentication fails. + +When the WLAN UE is not equipped with a UICC: upon receiving the Authentication Request message from the PDG, the 3GPP AAA Server shall check whether the Emergency\_Access flag is set for the user. If the Emergency\_Access flag is not set or the W-APN is not that for emergency as defined in 3GPP TS 23.003 [22], the Result-Code shall be set to DIAMETER\_AUTHORIZATION\_REJECTED. + +### 8.3.2 Authorization Procedures + +According to the requirements stated in subclause 8.1, Wm reference point shall enable: + +- Carrying messages for service authorization between PDG and 3GPP AAA Server/Proxy. +- Allow the 3GPP AAA Server/Proxy to retrieve tunnelling attributes and WLAN UE's IP configuration parameters from/via Packet Data Gateway. + +This procedure is used between the PDG and 3GPP AAA Server and Proxy. It is invoked by the PDG, if Authentication-Request-Type AVP was set to AUTHENTICATION\_ONLY during the Authentication and Authorization procedure, on receipt from the WLAN-UE of a "tunnel establishment request" message and subsequent to the success of tunnel authentication i.e. on receipt of a DEA message from the 3GPP AAA Server with Result Code set to "Success". + +The Wm reference point performs authorization download based on the reuse of the NASREQ IETF RFC 4005 [12] AAR-AAA command set. + +**Table 8.3.2.1 Wm Authorization Request** + +| Information element name | Mapping to Diameter AVP | Cat. | Description | +|---------------------------------|----------------------------|------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Permanent User Identity | User-Name | M | This information element contains the identity of the user. | +| Diameter Session ID | Session-Id | M | This information element uniquely identifies the session. | +| Request-Type | Session-Request-Type | M | Type of Wm specific Diameter application request. The following values are to be used:
AUTHORIZATION REQUEST (0)
This value shall indicate the initial request for authorization of the user to the APN.
ROUTING POLICY (1)
This value shall indicate that routing policy AVP is present. | +| Visited Network Identifier | Visited-Network-Identifier | C | Identifier that allows the home network to identify the Visited Network. This AVP shall be present if the PDG is not in the WLAN-UE's home network, i.e. the WLAN-UE is roaming. | +| W-APN-ID | 3GPP-WLAN-APN-Id | C | This information element contains the W-APN which the UE is requesting authorization.
This AVP is present when Session-Request-Type AVP is set to AUTHORIZATION REQUEST. | +| Routing Policy | Routing-Policy | C | This AVP includes the routing policy of the tunnel set-up.
This AVP shall be present when Session-Request-Type AVP is set to ROUTING POLICY. The exact format of this AVP is specified in section 10.1.24. | +| Routing Information | Destination-Host | M | The 3GPP AAA Server name is obtained from the Origin-Host AVP of a previously received message. | +| PDG Charging Identifier | PDG-Charging-Id | C | The PDG charging identifier is generated by PDG and used to correlate PDG and WLAN AN charging data.
This AVP is present when Session-Request-Type AVP is set to AUTHORIZATION REQUEST. | +| Supported 3GPP WLAN QoS profile | QoS-Capability | O | If the PDG supports QoS mechanisms, this information element may be included to contain PDG's QoS capabilities. | + +**Table 8.3.2.2: AA-Answer** + +| Information element name | Mapping to Diameter AVP | Cat. | Description | +|----------------------------------|---------------------------------------|------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Diameter Session ID | Session-Id | M | This information element uniquely identifies the session. | +| Registration Result | Result Code/ Experimental Result Code | M | Result of the operation.
Result-Code AVP shall be used for errors defined in the Diameter Base Protocol.
Experimental-Result AVP shall be used for Wm errors. This is a grouped AVP which contains the 3GPP Vendor ID in the Vendor-Id AVP, and the error code in the Experimental-Result-Code AVP | +| Subscription-ID | Subscription-ID AVP | C | This AVP shall contain the MSISDN and/or the IMSI of the user.
This AVP shall be present if the Diameter Result Code is set to DIAMETER_SUCCESS | +| Max-Subscribed-Bandwidth | Max-Requested-Bandwidth | O | The Max requested bandwidth AVP. Can be sent by the 3GPP AAA Server to the PDG if it is present in the user subscription info held at the 3GPP AAA Server. | +| Charging Information | Charging-Data | C | Charging information for the W-APN for that user.
It shall be present when Result-Code is equal to DIAMETER_SUCCESS and when the received Session-Request-Type was set to AUTHORIZATION REQUEST. | +| Framed-IP-Address | Framed-IP-Address | O | This AVP contains the remote IPv4 address of the WLAN UE that the 3GPP AAA Server downloaded from the HSS.
This AVP shall not be present when the 3GPP AAA Server received an authorisation request with Session-Request-Type AVP set to ROUTING POLICY. | +| Framed-IP-Prefix | Framed-IP-Prefix | O | This AVP contains the remote IPv6 prefix of the WLAN UE that the 3GPP AAA Server downloaded from the HSS.
This AVP shall not be present when the 3GPP AAA Server received an authorisation request with Session-Request-Type AVP set to ROUTING POLICY. | +| Permanent User Identity | User-Name | C | This information element contains the IMSI of the user. This shall be present if Registration Result Code is set to "Success" and the AAR did not contain the IMSI. | +| WLAN Session Identifier | WLAN-Session-Id | C | This information element contains the charging identifier generated by the 3GPP AAA Server.
It shall be present when Result-Code is equal to DIAMETER_SUCCESS and when the received Session-Request-Type was set to AUTHORIZATION REQUEST, and if WLAN access authentication and authorization procedure is done before tunnel establishment. | +| Authorized 3GPP WLAN QoS Profile | QoS-Resources | O | If both supported 3GPP WLAN QoS profile of the PDG and subscribed QoS profile were received by the 3GPP AAA Server, this IE may be present.
This IE contains the 3GPP WLAN QoS Profile authorized by the 3GPP AAA Server based on the subscribed QoS parameters from the HSS, PDG's QoS capabilities and other information, e.g. operators' policies. | +| Routing Policy | Routing-Policy | O | This AVP includes the routing policy (i.e. IP filters) needed for the Operator Determined Barring purposes. The exact format of this AVP is specified in section 10.1.24. It is up to the PDG implementation whether these routing policies are applied to Wi interface or applied at IPsec level using IKEv2 Traffic Selectors. | + +#### 8.3.2.1 3GPP AAA Server Detailed Behaviour + +The 3GPP AAA Server shall, in the following order (if there is an error in any of the steps, the 3GPP AAA Server shall stop processing and return the corresponding error code): + +- 1) Check that the user exists in the 3GPP AAA Server. The check shall be based on Diameter Session-id. If not Experimental-Result-Code shall be set to DIAMETER\_ERROR\_USER\_UNKNOWN. +- 2) Check the Session-Request-Type AVP: + - If Request type is set to AUTHORIZATION REQUEST, it indicates that the WLAN-UE is attempting to access the particular W-APN at the PDG and is requesting authorization for such a W-APN access. + +- The 3GPP AAA Server shall check whether the Emergency\_Access flag is set. If the Emergency\_Access flag is set and the W-APN is not that for emergency as defined in 3GPP TS 23.003 [22], the Result-Code shall be set to DIAMETER\_AUTHORIZATION\_REJECTED. If the W-APN is that defined for emergency access, the behaviour is as described in subclause 8.3.2.3. +- The 3GPP AAA Server shall check whether the subscriber is barred from completely from Interworking WLAN interworked service capabilities. If the subscription is barred then Result-Code shall be set to DIAMETER\_AUTHORIZATION\_REJECTED. +- The 3GPP AAA Server shall check that the user has subscription for the W-APN requested. If not, Experimental-Result-Code shall be set to DIAMETER\_ERROR\_USER\_NO\_W-APN\_SUBSCRIPTION. +- The 3GPP AAA Server shall check whether the user has access to that W-APN. This information is obtained from the HSS within the APN-Authorized AVP. If not, Result-Code shall be set to DIAMETER\_AUTHORIZATION\_REJECTED. +- If the user is roaming (indicated by the presence of the Visited-Network-Identifier AVP), the 3GPP AAA Server shall check if the user is allowed to access the W-APN from a VPLMN. This information is obtained from the HSS within the APN-Authorized AVP. If not, Experimental-Result-Code shall be set to DIAMETER\_ERROR\_ROAMING\_NOT\_ALLOWED. +- If the WLAN UE does not already have an active access to this W-APN, the 3GPP AAA Server shall initiate an Access-Number counter for that W-APN and set it to one. If the Access-Number counter has already been initiated, the 3GPP AAA Server shall increment the counter by one. The 3GPP AAA Server shall then check the counter value against the Maximum-Number-Accesses for that W-APN from that user's data. If the Access-Number exceeds Maximum-Number-Accesses, the 3GPP AAA Server shall use the 3GPP AAA Server initiated disconnection procedures towards the PDG with which the user has the oldest established access in order to initiate the tear down of the SA associated with that access. The 3GPP AAA Server shall update accordingly the information of active accesses for the W-APN and shall store the PDG IP address and the Session-ID associated with the access. +- The 3GPP AAA Server shall download user data relevant to the W-APN, e.g. WLAN UE remote IP address if present, routing policies related to barring and the charging information as received from the HSS. The Result-Code shall be set to DIAMETER\_SUCCESS. +- If Request type is set to ROUTING POLICY, it indicates that the WLAN-UE already has an active tunnel to the given PDG and is informing the 3GPP AAA Server of the routing policy for the tunnel. The 3GPP AAA Server shall verify that routing policies received from the PDG do not conflict with Operator Determined Barring related routing policies. In a case of conflict the Result-Code shall be set to DIAMETER\_UNABLE\_TO\_COMPLY. The 3GPP AAA Server shall store the Routing-Policy AVP and use Wg procedures to install this policy at the WAG. If this is successful, 3GPP AAA Server shall set Result-Code AVP to DIAMETER\_SUCCESS in the AAA message. If not, Result-Code shall be set to DIAMETER\_UNABLE\_TO\_COMPLY. + +Exceptions to the cases specified here shall be treated by 3GPP AAA Server as error situations, the Result-Code shall be set to DIAMETER\_UNABLE\_TO\_COMPLY. No authorization information shall be returned. + +#### 8.3.2.2 AAA Proxy Detailed Behaviour + +The 3GPP AAA Proxy is required to handle roaming cases in which the PDG is in the VPLMN. On this interface, it may act to limit policy enforcement by modifying messages. It shall therefore maintain session state. The 3GPP AAA Proxy shall, in the following order (if there is an error in any of the steps, the 3GPP AAA Proxy shall stop processing and return the corresponding error code). + +Check the Request Type AVP: + +- 1) If Request type indicates AUTHORIZATION REQUEST, it indicates that the WLAN-UE does not have a tunnel active to the particular APN at the PDG and is requesting authorization for such an APN. + - a) The 3GPP AAA Proxy shall check locally configured information whether users from the HPLMN are allowed to access to the W-APN requested from this (V)PLMN. If not, Experimental-Result-Code shall be set to DIAMETER\_ERROR\_ROAMING\_NOT\_ALLOWED and the AA-A message sent to the PDG. In all other cases, the message shall be forwarded transparently to the 3GPP AAA Server. +- 2) If Request-Type indicates ROUTING POLICY: + - a) This indicates that the WLAN-UE already has an active tunnel to the given PDG and is informing the 3GPP AAA Server of the routing policy for the tunnel. The 3GPP AAA Proxy shall store the Routing-Policy AVP and use Wg procedures to download the policy to the WAG. If this is successful, 3GPP AAA Proxy shall set Result Code to "Success" and send the AAR reply. If not, Result Code shall be set to DIAMETER\_UNABLE\_TO\_COMPLY. + +Exceptions to the cases specified here shall be treated by 3GPP AAA Proxy as error situations, the Result-Code shall be set to DIAMETER\_UNABLE\_TO\_COMPLY and AA-A message sent to the PDG. + +#### 8.3.2.3 Authorization Procedures in the Emergency Case + +##### 8.3.2.3.1 PDG Procedures + +For the case where the WLAN-UE is attempting to set up a tunnel (IPSec SA) to the emergency W-APN authorization shall proceed as described in subclauses 8.3.2.1 and 8.3.2.2 with the following exceptions: + +National regulations define whether the access for emergencies shall still be granted to UE even if authentication fails. In such case PDG shall skip authentication procedures and W-APN authorization procedures on the Wm interface. + +When the WLAN UE is not equipped with a UICC, the authorization procedure is not performed. + +On receipt of an Authorization Answer from the 3GPP AAA Server with result code set to DIAMETER\_ERROR\_UNSUITABLE\_NETWORK, the PDG shall use procedures defined in 3GPP TS 24.234 [38] to reject the tunnel setup procedure + +##### 8.3.2.3.2 3GPP AAA Server Procedures + +For the case where the WLAN-UE is attempting to set up a tunnel (IPSec SA) to the emergency W-APN authorization shall proceed as described in subclauses 8.3.2.1 and 8.3.2.2 with the following exceptions: + +On receipt of the Authorization Request from the PDG containing the emergency W-APN, the 3GPP AAA Server shall in the following order: + +- check whether the user is roaming. If the user is roaming and the PDG is in the HPLMN, the 3GPP AAA Server shall reject the authorization request and set the Experimental-Result-Code to DIAMETER\_ERROR\_UNSUITABLE\_NETWORK +- if the WLAN-UE is not roaming, or is roaming and the PDG is in the VPLMN, the 3GPP AAA Server shall accept the authorization request without subscription check. The 3GPP AAA Server shall not update the Access-Number counter. For this access, the 3GPP AAA Server shall store the indication that this is for IMS emergency case and shall not use procedures described in subclause .8.3.4 to disconnect it (based on Diameter Session ID). + +### 8.3.3 PDG Initiated Session Termination Procedure + +This procedure is used between the PDG and the 3GPP AAA Server. It is invoked by the PDG when the user's tunnel associated with the W-APN has been disconnected. + +Where the user has several accesses (IKE\_SA) active, a separate Session Termination procedure shall be initiated for each access (even if the accesses are to the same W-APN). + +**Table 8.3.3.1: Session Termination Request** + +| Information element name | Mapping to Diameter AVP | Cat. | Description | +|--------------------------|-------------------------|------|-----------------------------------------------------------------------------------------------| +| User Identity | User-Name | M | This information element contains the identity of the user. | +| W-APN-ID | 3GPP-WLAN-APN-Id | M | This information element contains the W-APN which the UE is requesting access. | +| Routing Information | Destination-Host | M | The 3GPP AAA Server name is obtained from the Origin-Host AVP of a previous received message. | + +**Table 8.3.3.2: Session Termination Answer** + +| Information element name | Mapping to Diameter AVP | Cat. | Description | +|--------------------------|-----------------------------------|------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Result | Result-Code / Experimental-Result | M | Result of the operation.
Result-Code AVP shall be used for errors defined in the Diameter Base Protocol.
Experimental-Result AVP shall be used for Wm errors. | + +#### 8.3.3.1 3GPP AAA Server Detailed behaviour + +On receipt of the STR, the 3GPP AAA Server shall, in the following order (if there is an error in any of the steps, the 3GPP AAA Server shall stop processing and return the corresponding error code): + +- Check from the User Name AVP that this corresponds to a user. If not Experimental-Result-Code shall be set to DIAMETER\_ERROR\_USER\_UNKNOWN. +- Check that the user has an active session on the received W-APN. If not, Experimental-Result-Code shall be set to DIAMETER\_ERROR\_W-APN\_UNUSED\_BY\_USER. +- If the User is known and the W-APN corresponds to a known session, the 3GPP AAA Server shall remove any PDG specific information connected to that user on that W-APN, and update the status of the subscriber if needed. If the user was a home user, the 3GPP AAA Server shall signal to the WAG to initiate procedures to remove any filtering policy associated with that user's session. The Result Code shall be set to DIAMETER\_SUCCESS. + +#### 8.3.3.2 3GPP AAA Proxy Detailed Behaviour + +In the roaming case, the 3GPP AAA Proxy shall forward the STR message to the 3GPP AAA Server. On receipt of an STR with Result-Code set to DIAMETER\_SUCCESS, the 3GPP AAA Proxy shall remove any session specific information associated with that user at that W-APN. It shall signal to the WAG to initiate procedures to remove any filtering policy associated with that user's session. + +#### 8.3.3.3 PDG Initiated Session Termination Procedure in Emergency Case + +PDG shall not use the Session Termination procedures unless triggered by WLAN UE or until after the expiry of the underlying IKE and IPSec SA timers at the PDG associated with the emergency W-APN. + +### 8.3.4 3GPP AAA Server Initiated Tunnel Disconnect Procedure + +This procedure is used between the 3GPP AAA Server and the PDG. It is invoked by the 3GPP AAA Server when the WLAN subscription for the user has been deleted/prohibited in the 3GPP AAA Server or if the particular session must be terminated for any reason and the PDG must be updated with respect to these changes. + +For the case where the user has several accesses (IKE\_SA) active at a PDG, a separate Session Termination procedure shall be initiated for each. + +The Wm reference point performs the disconnection of user tunnel initiated by the 3GPP AAA Server based on the use of the RFC 3588 [7] Abort-Session-Request / Answer (ASR/ASA) commands. + +The 3GPP AAA Server shall not use this procedure in the emergency case. + +**Table 8.3.4.1: 3GPP AAA Server Initiated Tunnel Disconnection - Request** + +| Information element name | Mapping to Diameter AVP | Cat. | Description | +|----------------------------------|-------------------------|------|--------------------------------------------------------------------------------------------------------------------------------------------| +| User Identity | User-Name | M | This information element contains the identity of the user. | +| W-APN-Id
(see clause 10.5.15) | 3GPP-WLAN-APN-Id | M | W-APN Identification. | +| Routing Information | Destination-Host | M | The PDG name is obtained from the Origin-Host AVP of a previous message received from the PDG e.g. included in the authentication command. | + +**Table 8.3.4.2: 3GPP AAA Server Initiated Tunnel Disconnection - Answer** + +| Information element name | Mapping to Diameter AVP | Cat. | Description | +|--------------------------|-----------------------------------|------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Result | Result-Code / Experimental-Result | M | Result of the operation.
Result-Code AVP shall be used for errors defined in the Diameter Base Protocol.
Experimental-Result AVP shall be used for Wm errors. This is a grouped AVP which contains the 3GPP Vendor ID in the Vendor-Id AVP, and the error code in the Experimental-Result-Code AVP. | + +#### 8.3.4.1 Detailed Behaviour + +The 3GPP AAA Server shall make use of this procedure to instruct the PDG to disconnect a particular W-APN for a specific user. On receipt of the message, the PDG shall: + +- 1) Check from the user is known in the PDG. If not, Experimental-Result-Code shall be set to DIAMETER\_ERROR\_USER\_UNKNOWN. +- 2) Check that the user has an active session on the received W-APN. If not, Experimental-Result-Code shall be set to DIAMETER\_ERROR\_W-APN\_UNUSED\_BY\_USER. +- 3) If the User is known and the W-APN corresponds to a known session, the PDG shall perform tunnel disconnect procedure of the tunnels associated with that user on that W-APN. The PDG shall further remove any stored user information pertaining to that APN. +- 4) The PDG shall set the Result-Code to DIAMETER\_SUCCESS and send back the SAA command to the 3GPP AAA Server. + +On receipt of the message, the 3GPP AAA Server shall update the related service information and/or status of the subscriber and remove any filtering policy related to the disconnected tunnel from WAG if necessary. + +#### 8.3.4.2 3GPP AAA Proxy Behaviour + +On receipt of the ASA message with Diameter Result Code set to DIAMETER\_SUCCESS, the 3GPP AAA Proxy shall signal to the WAG to initiate procedures to remove any filtering policy associated with that user's session. + +### 8.3.5 Access and Service Authorization information Update Procedure + +This procedure is used between the 3GPP AAA Server and the PDG and is used to modify the authorization parameters provided to the PDG. This may happen due to a modification of WLAN subscriber profile in the HSS + +This procedure is performed in two steps: + +- The 3GPP AAA server issues an unsolicited re-authentication and/or re-authorization request towards the PDG. Upon receipt of such a request, the PDG shall respond to the request and indicate the disposition of the request. This procedure is mapped to the Diameter command codes Re-Auth-Request and Re-Auth-Answer specified in RFC 3588 [7]. Information element content for these messages are shown in tables 8.3.5.1 and 8.3.5.2. + +- Receiving the re-authorization request, the PDG shall invoke the authorization procedure as described in the sections 8. 3.2. Information element content for these messages are shown in tables 8.3.2.1 and 8.3.2.2. + +For emergency W-APN, 3GPP AAA Server shall not use the Access and Service Authorization information update Procedure. + +**Table 8.3.5.1: Access and Service Authorization Information Update request** + +| Information element name | Mapping to Diameter AVP | Cat. | Description | +|--------------------------|-------------------------|------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| User Identity | User-Name | M | This information element contains the identity of the user. | +| Re-Auth Request Type | Re-Auth-Request-Type | M | Defines whether the user is to be re-authenticated only, re-authorized only or both.
The following value can only be used:
AUTHORIZE_ONLY

Receiving entity may receive Re-Auth Request Type value other than AUTHORIZE_ONLY if the 3GPP AAA server is based on earlier releases. For more information see sub-clause 8.3.5.1. | +| Routing Information | Destination-Host | M | This information element is obtained from the Origin-Host AVP, which was included in a previous command received from the PDG. | + +**Table 8.3.5.2: Access and Service Authorization information Update response** + +| Information element name | Mapping to Diameter AVP | Cat. | Description | +|--------------------------|-----------------------------------|------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Result | Result-Code / Experimental-Result | M | Result of the operation.
Result-Code AVP shall be used for errors defined in the Diameter Base Protocol.
Experimental-Result AVP shall be used for Wm errors. This is a grouped AVP which contains the 3GPP Vendor ID in the Vendor-Id AVP, and the error code in the Experimental-Result-Code AVP. | +| User Identity | User-Name | M | This information element contains the identity of the user. | + +#### 8.3.5.1 Detailed behaviour + +The 3GPP AAA server shall make use of this procedure to indicate and update relevant service authorization information in the PDG. + +The PDG shall perform the following check and if there is an error detected, the PDG shall stop processing and return the corresponding error code. + +Check the Re-Auth-Request-Type AVP: + +- 1) If it indicates AUTHENTICATE\_ONLY, Result-Code shall be set to DIAMETER\_INVALID\_AVF\_VALUE. +- 2) If it indicates AUTHORIZE\_ONLY, the PDG shall just perform an authorization procedure as described in section 8.3.2. +- 3) If it indicates AUTHORIZE\_AUTHENTICATE, Result-Code shall be set to DIAMETER\_INVALID\_AVF\_VALUE. + +After successful authorization procedure, the PDG shall overwrite, for the subscriber identity indicated in the request, current information with the information received from the 3GPP AAA server. A deactivation of service may be initiated if the subscriber lost the authorization of the activated service. + +## 8.4 Information Element Contents + +### 8.4.1 Authentication Request/Answer Messages + +ABNF for the Wm Authentication and optionally Authorization Request and Authentication and optionally Authorization Answer are given below: + +``` + ::= < Diameter Header: 268, REQ, PXY > +< Session-Id > +{ Auth-Application-Id } +``` + +``` + +{ Origin-Host } +{ Origin-Realm } +{ Destination-Realm } +{ Auth-Request-Type } +{ EAP-Payload } +[ Destination-Host ] +[ User-Name ] +[ Visited-Network-Identifier ] +[ NAS-IP-Address ] +[ NAS-IPv6-Address ] +[ Calling Station-ID ] +[3GPP-WLAN-APN-ID] +[ QoS-Capability ] + +* [ Proxy-Info ] +* [ Route-Record ] +* [ AVP ] + +``` + +For the DEA, the following are necessary: + +``` + + ::= < Diameter Header: 268, PXY > + < Session-Id > + { Auth-Application-Id } + { Auth-Request-Type } + { Result-Code } + { Origin-Host } + { Origin-Realm } + [ User-Name ] + [ EAP-Master-Session-Key ] + [ EAP-Payload ] + 1*[ Subscription-ID-AVP ] + [ Max-Subscribed-Bandwidth ] + [ QoS-Resources ] + [ Charging-Data ] + [ Service-Type ] + * [ Class ] + * [ Configuration-Token ] + [ Acct-Interim-Interval ] + [ Error-Message ] + [ Error-Reporting-Host ] + * [ Failed-AVP ] + [ Idle-Timeout ] + [ Authorization-Lifetime ] + [ Auth-Grace-Period ] + [ Auth-Session-State ] + [ Re-Auth-Request-Type ] + [ Session-Timeout ] + [ State ] + * [ Reply-Message ] + [ Origin-State-Id ] + * [ Filter-Id ] + [ Password-Retry ] + [ Port-Limit ] + [ User-Name ] + [ Prompt ] + [ ARAP-Challenge-Response ] + [ ARAP-Features ] + [ ARAP-Security ] + * [ ARAP-Security-Data ] + [ ARAP-Zone-Access ] + [ Callback-Id ] + [ Callback-Number ] + [ Framed-Appletalk-Link ] + * [ Framed-Appletalk-Network ] + [ Framed-Appletalk-Zone ] + * [ Framed-Compression ] + [ Framed-Interface-Id ] + [ Framed-IP-Address ] + * [ Framed-IPv6-Prefix ] + [ Framed-IPv6-Pool ] + * [ Framed-IPv6-Route ] + [ Framed-IP-Netmask ] + * [ Framed-Route ] + [ Framed-Pool ] + [ Framed-IPX-Network ] + [ Framed-MTU ] + [ Framed-Protocol ] + [ Framed-Routing ] + +``` + +``` + +* [ Login-IP-Host ] +* [ Login-IPv6-Host ] +[ Login-LAT-Group ] +[ Login-LAT-Node ] +[ Login-LAT-Port ] +[ Login-LAT-Service ] +[ Login-Service ] +[ Login-TCP-Port ] +* [ NAS-Filter-Rule ] +* [ QoS-Filter-Rule ] +* [ Tunneling ] +* [ Redirect-Host ] +[ Redirect-Host-Usage ] +[ Redirect-Max-Cache-Time ] + +* [ Proxy-Info ] +* [ AVP ] + +``` + +### 8.4.2 Authorization Procedures + +The authorization request and response messages are mapped onto the NASREQ AAR/AAA messages. The ABNF are indicated below: + +``` + + ::= < Diameter Header: 265, REQ, PXY > + < Session-Id > + { Auth-Application-Id } + { Origin-Host } + { Origin-Realm } + { Destination-Realm } + { Auth-Request-Type } + { Destination-Host } + [ Session-Request-Type ] + [ Visited-Network-Identifier ] + [3GPP-WLAN-APN-ID] + [ QoS-Capability ] + * [ Routing-Policy ] + [ NAS-Identifier ] + [ NAS-IP-Address ] + [ NAS-IPv6-Address ] + [ NAS-Port ] + [ NAS-Port-Id ] + [ NAS-Port-Type ] + [ Origin-State-Id ] + [ Port-Limit ] + [ User-Name ] + [ User-Password ] + [ Service-Type ] + [ State ] + [ Authorization-Lifetime ] + [ Auth-Grace-Period ] + [ Auth-Session-State ] + [ Callback-Number ] + [ Called-Station-Id ] + [ Calling-Station-Id ] + [ Originating-Line-Info ] + [ Connect-Info ] + [ CHAP-Auth ] + [ CHAP-Challenge ] + * [ Framed-Compression ] + [ Framed-Interface-Id ] + [ Framed-IP-Address ] + [ Framed-IP-Netmask ] + [ Framed-MTU ] + [ Framed-Protocol ] + [ ARAP-Password ] + [ ARAP-Security ] + * [ ARAP-Security-Data ] + * [ Login-IP-Host ] + * [ Login-IPv6-Host ] + [ Login-LAT-Group ] + [ Login-LAT-Node ] + [ Login-LAT-Port ] + [ Login-LAT-Service ] + * [ Tunneling ] + * [ Proxy-Info ] + * [ Route-Record ] + +``` + +\* [ AVP ] + +The ABNF for the AAA is as follows: + +``` + ::= < Diameter Header: 265, PXY > + < Session-Id > + { Auth-Application-Id } + { Auth-Request-Type } + { Result-Code } + { Origin-Host } + { Origin-Realm } + 1*[ Subscription-ID-AVP ] + [ Max-Subscribed-Bandwidth ] + [ QoS-Resources ] + [ Framed-IP-Address ] + [ Framed-IP-Prefix ] + [ Charging-Data ] + [ Service-Type ] + * [ Class ] + * [ Configuration-Token ] + [ Acct-Interim-Interval ] + [ Error-Message ] + [ Error-Reporting-Host ] + * [ Failed-AVP ] + [ Idle-Timeout ] + [ Authorization-Lifetime ] + [ Auth-Grace-Period ] + [ Auth-Session-State ] + [ Re-Auth-Request-Type ] + [ Session-Timeout ] + [ State ] + * [ Reply-Message ] + [ Origin-State-Id ] + * [ Filter-Id ] + [ Password-Retry ] + [ Port-Limit ] + [ User-Name ] + [ Prompt ] + [ ARAP-Challenge-Response ] + [ ARAP-Features ] + [ ARAP-Security ] + * [ ARAP-Security-Data ] + [ ARAP-Zone-Access ] + [ Callback-Id ] + [ Callback-Number ] + [ Framed-Appletalk-Link ] + * [ Framed-Appletalk-Network ] + [ Framed-Appletalk-Zone ] + * [ Framed-Compression ] + [ Framed-Interface-Id ] + [ Framed-IP-Address ] + * [ Framed-IPv6-Prefix ] + [ Framed-IPv6-Pool ] + * [ Framed-IPv6-Route ] + [ Framed-IP-Netmask ] + * [ Framed-Route ] + [ Framed-Pool ] + [ Framed-IPX-Network ] + [ Framed-MTU ] + [ Framed-Protocol ] + [ Framed-Routing ] + * [ Login-IP-Host ] + * [ Login-IPv6-Host ] + [ Login-LAT-Group ] + [ Login-LAT-Node ] + [ Login-LAT-Port ] + [ Login-LAT-Service ] + [ Login-Service ] + [ Login-TCP-Port ] + * [ NAS-Filter-Rule ] + * [ QoS-Filter-Rule ] + * [ Tunneling ] + * [ Redirect-Host ] + [ Redirect-Host-Usage ] + [ Redirect-Max-Cache-Time ] + * [ Proxy-Info ] + * [ AVP ] +``` + +### 8.4.3 PDG Initiated Session Termination Procedure + +This procedure is mapped onto the STR/STA procedures. The ABNF are as follows: + +``` + ::= < Diameter Header: 275, REQ, PXY > + < Session-Id > + { Origin-Host } + { Origin-Realm } + { Destination-Realm } + { Auth-Application-Id } + { Termination-Cause } + [ User-Name ] + [3GPP-WLAN-APN-Id ] + [ Destination-Host ] + * [ Class ] + [ Origin-State-Id ] + * [ Proxy-Info ] + * [ Route-Record ] + * [ AVP ] +``` + +For the response: + +``` + ::= < Diameter Header: 275, PXY > + < Session-Id > + { Result-Code } + { Origin-Host } + { Origin-Realm } + [ User-Name ] + * [ Class ] + [ Error-Message ] + [ Error-Reporting-Host ] + * [ Failed-AVP ] + [ Origin-State-Id ] + * [ Redirect-Host ] + [ Redirect-Host-Usage ] + [ Redirect-Max-Cache-Time ] + * [ Proxy-Info ] + * [ AVP ] +``` + +### 8.4.4 3GPP AAA Server Initiated Tunnel Disconnect Procedure + +ABNF for the 3GPP AAA Server Initiated Tunnel Disconnect Procedure are mapped onto the ASR and ASA commands are as follows: + +``` + ::= < Diameter Header: 274, REQ, PXY > + < Session-Id > + { Origin-Host } + { Origin-Realm } + { Destination-Realm } + { Destination-Host } + { Auth-Application-Id } + [ User-Name ] + [3GPP-WLAN-APN-Id ] + [ Origin-State-Id ] + * [ Proxy-Info ] + * [ Route-Record ] + * [ AVP ] +``` + +``` + ::= < Diameter Header: 274, PXY > + < Session-Id > + { Result-Code } + { Origin-Host } + { Origin-Realm } + [ User-Name ] + [ Origin-State-Id ] + [ Error-Message ] + [ Error-Reporting-Host ] + * [ Failed-AVP ] + * [ Redirected-Host ] + [ Redirected-Host-Usage ] + [ Redirected-Max-Cache-Time ] + * [ Proxy-Info ] +``` + +\* [ AVP ] + +### 8.4.5 Access and Service Authorization Information Update Procedure + +ABNF for the RAR/RAA commands on the Wm interface are identical to those described in section 4.4.2.4. + +ABNF for the AAR/AAA commands on the Wm interface are identical to those described in section 8.4.2 + +# 9 Wg Description + +## 9.1 Functionality + +The Wg reference point is defined between the 3GPP AAA Server and the WAG or between the 3GPP AAA Proxy and the WAG depending on the location of the WAG. The description of the reference point and its functionality is given in 3GPP TS 23.234 [4]. + +This clause specifies a Diameter application supports the functionality of this reference point. + +The interface at this reference point is applicable only when a WLAN UE is allowed to access the 3GPP PS services from the I-WLAN. + +**Editor's Note:** Remaining functionalities on this interface e.g. the charging rules to be applied, sending of MSISDN to WAG, that are necessary for WLAN 3GPP IP Access functionality are not stable yet. + +## 9.2 Protocols + +Diameter NASREQ is used for the policy download to the WAG. In this case, the 3GPP AAA Server or Proxy shall act as the NAS client and the WAG as the Diameter Server. + +The Application-Id to be advertised over Wg reference point corresponds to the EAP, NASREQ or Diameter Base Protocol Application-Id, depending on the command sent over Wg. + +## 9.3 Procedures Description + +### 9.3.1 Policy Download Procedures + +The policy download procedure is used between the 3GPP AAA Server and the WAG in the case where the PDG is in the HPLMN and between the 3GPP AAA Proxy and the WAG in the case where the PDG is in the VPLMN + +The Wg reference point performs routing policy download based on the reuse of the NASREQ IETF RFC 4005 [12] AAR-AAA command set. If the WAG is located in the VPLMN the 3GPP AAA Server shall send the AAR command over the Wd interface to the 3GPP AAA Proxy and then it is 3GPP AAA Proxy's task to find the WAG serving the user. + +The way to find the WAG address in AAA proxy/ AAA server is implementation dependent. For example, based on the source IP address of DER command if the WAG has the NAT functionality or manual network configuration. + +**Table 9.3.1.1: Wg Policy Download Request** + +| Information element name | Mapping to Diameter AVP | Cat. | Description | +|--------------------------|-------------------------|------|-------------------------------------------------------------------------------------------| +| Permanent User Identity | User-Name | M | This information element contains the permanent identity of the user, i.e. the IMSI. | +| Routing Policy | Routing-Policy | M | This AVP includes the routing policy to apply for the user received in the User-Name AVP. | +| Routing Information | Destination-Host | C | This information element contains the WAG. | +| Subscription-ID AVP | Subscription-ID AVP | M | This AVP shall contain the MSISDN and/or the IMSI of the user. | + +**Table 9.3.1.2: Wg Policy Download Response** + +| Information element name | Mapping to Diameter AVP | Cat. | Description | +|--------------------------|---------------------------------------|------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Registration Result | Result Code/ Experimental Result Code | M | Result of the operation.
Result-Code AVP shall be used for errors defined in the Diameter Base Protocol.
Experimental-Result AVP shall be used for Wg errors. This is a grouped AVP which contains the 3GPP Vendor ID in the Vendor-Id AVP, and the error code in the Experimental-Result-Code AVP. | + +#### 9.3.1.1 WAG Detailed Behaviour + +On receipt of the Policy Download Request, the WAG shall check whether or not the user has already routing policies stored: + +- If it has, the WAG shall modify the routing policy accordingly. +- Otherwise, the WAG shall take necessary steps to provision the new routing policy indicated in the routing policy AVP for the user in order to allow data plane packet flows across the Wn interface. + +The Result-Code shall be set to DIAMETER\_SUCCESS and the WAG shall reply with the Policy Download Response message. + +Exceptions to the cases specified here shall be treated by WAG as error situations, the Result-Code shall be set to DIAMETER\_UNABLE\_TO\_COMPLY. + +### 9.3.2 Routing Policy Cancellation Procedure + +This procedure is used between the 3GPP AAA Server and the WAG. It is invoked by the 3GPP AAA Server when the session specific routing policy should be removed from the WAG (i.e. users tunnel has been disconnected and the tunnel specific routing policy configured at the WAG - the firewall "pinhole"- must be removed). + +The Wg reference point performs the routing policy cancellation procedure based on the use of RFC 3588 [7] Abort-Session-Request / Answer (ASR/ASA) commands. + +In the roaming case where the PDG is in the VPLMN, the 3GPP AAA Proxy shall perform the functions described below for the 3GPP AAA Server. + +**Table 9.3.2.1: Policy Cancellation - Request** + +| Information element name | Mapping to Diameter AVP | Cat. | Description | +|--------------------------|-------------------------|------|------------------------------------------------------------------------------------------------| +| Permanent User Identity | User-Name | M | This information element contains the permanent identity of the user, i.e. the IMSI. | +| Routing Information | Destination-Host | M | The WAG name is obtained from the Origin-Host AVP of a previous message received from the WAG. | + +**Table 9.3.2.2: Policy Cancellation- Answer** + +| Information element name | Mapping to Diameter AVP | Cat. | Description | +|--------------------------|-----------------------------------|------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Result | Result-Code / Experimental-Result | M | Result of the operation.
Result-Code AVP shall be used for errors defined in the Diameter Base Protocol.
Experimental-Result AVP shall be used for Wg errors. This is a grouped AVP which contains the 3GPP Vendor ID in the Vendor-Id AVP, and the error code in the Experimental-Result-Code AVP. | + +#### 9.3.2.1 Detailed Behaviour + +The 3GPP AAA Server shall make use of this procedure to instruct the WAG to remove a routing policy W-APN for a specific user. On receipt of the message, the WAG shall: + +- Check that the user is known in the WAG. If not, Experimental-Result-Code shall be set to DIAMETER\_ERROR\_USER\_UNKNOWN. +- If the User is known, the WAG shall remove all routing policies configured for that session. The WAG shall further remove any stored user information pertaining to that W-APN. +- The WAG shall set the Result-Code to DIAMETER\_SUCCESS and send back the ASA command to the 3GPP AAA Server. + +Exceptions to the cases specified here shall be treated by the WAG as error situations, the Result-Code shall be set to DIAMETER\_UNABLE\_TO\_COMPLY and no Wn flows shall be disabled. + +### 9.3.3 WAG Initiated Routing Policy Cancellation Procedure + +This procedure is used between the WAG and the 3GPP AAA Server. It is invoked by the WAG in the case whereby the session specific routing policy has been removed from the WAG and this action has not been preceded by any "Routing policy Cancellation Procedure" being sent from the 3GPP AAA Server to the WAG to instruct it to do so. + +The trigger for removal of the routing policy is implementation dependent, but it may e.g. result from a security attack on the PLMN using a corrupted WLAN-UE - PDG tunnel. + +The Wg reference point performs the routing policy cancellation procedure based on the use of RFC 3588 [7] Session Termination Request/ Answer (STR/STA) commands. + +In the roaming case where the PDG is in the VPLMN, the 3GPP AAA Proxy shall perform the functions described below for the 3GPP AAA Server. + +**Table 9.3.3.1: WAG Initiated Policy Cancellation - Notification** + +| Information element name | Mapping to Diameter AVP | Cat. | Description | +|--------------------------|-------------------------|------|---------------------------------------------------------------------------------------------------| +| Permanent User Identity | User-Name | M | This information element contains the permanent identity of the user, i.e. the IMSI. | +| Routing Information | Destination-Host | M | This information element contains the 3GPP AAA Server/Proxy name obtained from previous messages. | + +**Table 9.3.3.2: WAG Initiated Policy Cancellation- Response** + +| Information element name | Mapping to Diameter AVP | Cat. | Description | +|--------------------------|-----------------------------------|------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Result | Result-Code / Experimental-Result | M | Result of the operation.
Result-Code AVP shall be used for errors defined in the Diameter Base Protocol.
Experimental-Result AVP shall be used for Wg errors. This is a grouped AVP which contains the 3GPP Vendor ID in the Vendor-Id AVP, and the error code in the Experimental-Result-Code AVP. | + +#### 9.3.3.1 Detailed Behaviour + +The WAG shall make use of this procedure to instruct the 3GPP AAA Server of the fact that it has removed routing policy firewall pinhole at a specific W-APN for a specific user. On receipt of the message, the 3GPP AAA Server shall: + +- Check the user is known in the 3GPP AAA Server. If not, Experimental-Result-Code shall be set to DIAMETER\_ERROR\_USER\_UNKNOWN. +- If the User is known the 3GPP AAA Server behaviour is implementation dependent. The 3GPP AAA Server may: + - (i) try to reconfigure a routing policy at the WAG by initiating a new session using AA-R to the WAG; or + - (ii) take steps to remove the users session at the 3GPP AAA Server and the PDG. +- The 3GPP AAA Server shall set the Result-Code to DIAMETER\_SUCCESS and send back the ASA command to the WAG. + +Exceptions to the cases specified here shall be treated by 3GPP AAA Server as error situations, the Result-Code shall be set to DIAMETER\_UNABLE\_TO\_COMPLY. + +## 9.4 Information Element Contents + +### 9.4.1 Policy Download Procedures + +The Wg Policy Download Request/Response are mapped onto the NASREQ AAR/AAA messages. The ABNF are indicated below: + +``` + ::= < Diameter Header: 265, REQ, PXY > + < Session-Id > + { Auth-Application-Id } + { Origin-Host } + { Origin-Realm } + { Destination-Realm } + { Auth-Request-Type } + [Destination-Host] + * [ Routing Policy ] + 1*[ Subscription-ID ] + [ NAS-Identifier ] + [ NAS-IP-Address ] + [ NAS-IPv6-Address ] + [ NAS-Port ] + [ NAS-Port-Id ] + [ NAS-Port-Type ] + [ Origin-State-Id ] + [ Port-Limit ] + [ User-Name ] + [ User-Password ] + [ Service-Type ] + [ State ] + [ Authorization-Lifetime ] + [ Auth-Grace-Period ] + [ Auth-Session-State ] + [ Callback-Number ] + [ Called-Station-Id ] + [ Calling-Station-Id ] + [ Originating-Line-Info ] + [ Connect-Info ] + [ CHAP-Auth ] + [ CHAP-Challenge ] + * [ Framed-Compression ] + [ Framed-Interface-Id ] + [ Framed-IP-Address ] + [ Framed-IP-Netmask ] + [ Framed-MTU ] + [ Framed-Protocol ] + [ ARAP-Password ] + [ ARAP-Security ] + * [ ARAP-Security-Data ] + * [ Login-IP-Host ] + * [ Login-IPv6-Host ] + [ Login-LAT-Group ] + [ Login-LAT-Node ] + [ Login-LAT-Port ] + [ Login-LAT-Service ] + * [ Tunneling ] + * [ Proxy-Info ] + * [ Route-Record ] + * [ AVP ] +``` + +The ABNF for the AAA is as follows: + +``` + ::= < Diameter Header: 265, PXY > + < Session-Id > + { Auth-Application-Id } + { Auth-Request-Type } + { Result-Code } + { Origin-Host } + { Origin-Realm } + [ User-Name ] + [ Service-Type ] + * [ Class ] + * [ Configuration-Token ] +``` + +``` + +[ Acct-Interim-Interval ] +[ Error-Message ] +[ Error-Reporting-Host ] +* [ Failed-AVP ] +[ Idle-Timeout ] +[ Authorization-Lifetime ] +[ Auth-Grace-Period ] +[ Auth-Session-State ] +[ Re-Auth-Request-Type ] +[ Session-Timeout ] +[ State ] +* [ Reply-Message ] +[ Origin-State-Id ] +* [ Filter-Id ] +[ Password-Retry ] +[ Port-Limit ] +[ Prompt ] +[ ARAP-Challenge-Response ] +[ ARAP-Features ] +[ ARAP-Security ] +* [ ARAP-Security-Data ] +[ ARAP-Zone-Access ] +[ Callback-Id ] +[ Callback-Number ] +[ Framed-Appletalk-Link ] +* [ Framed-Appletalk-Network ] +[ Framed-Appletalk-Zone ] +* [ Framed-Compression ] +[ Framed-Interface-Id ] +[ Framed-IP-Address ] +* [ Framed-IPv6-Prefix ] +[ Framed-IPv6-Pool ] +* [ Framed-IPv6-Route ] +[ Framed-IP-Netmask ] +* [ Framed-Route ] +[ Framed-Pool ] +[ Framed-IPX-Network ] +[ Framed-MTU ] +[ Framed-Protocol ] +[ Framed-Routing ] +* [ Login-IP-Host ] +* [ Login-IPv6-Host ] +[ Login-LAT-Group ] +[ Login-LAT-Node ] +[ Login-LAT-Port ] +[ Login-LAT-Service ] +[ Login-Service ] +[ Login-TCP-Port ] +* [ NAS-Filter-Rule ] +* [ QoS-Filter-Rule ] +* [ Tunneling ] +* [ Redirect-Host ] +[ Redirect-Host-Usage ] +[ Redirect-Max-Cache-Time ] +* [ Proxy-Info ] +* [ AVP ] + +``` + +### 9.4.2 Routing Policy Cancellation Procedure + +The Policy Cancellation Request/Response messages are mapped onto ASR/ASA messages. The ABNF are given below: + +``` + + ::= < Diameter Header: 274, REQ, PXY > +< Session-Id > +{ Origin-Host } +{ Origin-Realm } +{ Destination-Realm } +{ Destination-Host } +{ Auth-Application-Id } +[ User-Name ] +[3GPP-WLAN-APN-Id ] +[ Origin-State-Id ] +* [ Proxy-Info ] +* [ Route-Record ] +* [ AVP ] + +``` + +``` + + ::= < Diameter Header: 274, PXY > + < Session-Id > + { Result-Code } + { Origin-Host } + { Origin-Realm } + [ User-Name ] + [ Origin-State-Id ] + [ Error-Message ] + [ Error-Reporting-Host ] + * [ Failed-AVP ] + * [ Redirected-Host ] + [ Redirected-Host-Usage ] + [ Redirected-Max-Cache-Time ] + * [ Proxy-Info ] + * [ AVP ] + +``` + +### 9.4.3 WAG Initiated Routing Policy Cancellation Procedure + +The WAG initiated Routing Policy Cancellation Procedure is mapped onto the STR/STA messages. The ABNF are given below: + +``` + + ::= < Diameter Header: 275, REQ, PXY > + < Session-Id > + { Origin-Host } + { Origin-Realm } + { Destination-Realm } + { Auth-Application-Id } + { Termination-Cause } + [ User-Name ] + [ Destination-Host ] + * [ Class ] + [ Origin-State-Id ] + * [ Proxy-Info ] + * [ Route-Record ] + * [ AVP ] + +``` + +For the response: + +``` + + ::= < Diameter Header: 275, PXY > + < Session-Id > + { Result-Code } + { Origin-Host } + { Origin-Realm } + [ User-Name ] + * [ Class ] + [ Error-Message ] + [ Error-Reporting-Host ] + * [ Failed-AVP ] + [ Origin-State-Id ] + * [ Redirect-Host ] + [ Redirect-Host-Usage ] + [ Redirect-Max-Cache-Time ] + * [ Proxy-Info ] + * [ AVP ] + +``` + +# 10 Information Elements Contents + +## 10.1 AVPs + +Table 10.1.1 describes the Diameter AVPs defined for the WLAN reference point, their AVP Code values, types, possible flag values and whether or not the AVP may be encrypted. The Vendor-Id header of all AVPs defined in this specification shall be set to 3GPP (10415). + +Only those AVPs initially defined by the reference points mentioned within this specification are listed in Table 10.1.1. + +**Table 10.1.1: Diameter Multimedia Application AVPs** + +| Attribute Name | AVP Code | Section defined | Value Type | AVP Flag rules | | | | May Encr. | +|--------------------------------------|----------|-----------------|------------------|----------------|-----|------------|----------|-----------| +| | | | | Shall | May | Should not | Must not | | +| 3GPP-WLAN-APN-Id | 100 | 10.1.15 | OctetString | M, V | | | | No | +| Authentication-Method | 300 | 10.1.5 | Enumerated | M, V | | | | No | +| Authentication-Information-SIM | 301 | 10.1.6 | OctetString | M, V | | | | No | +| Authorization -Information-SIM | 302 | 10.1.7 | OctetString | M, V | | | | No | +| WLAN-User-Data | 303 | 10.1.8 | Grouped | M, V | | | | No | +| Charging-Data | 304 | 10.1.10 | Grouped | M, V | | | | No | +| WLAN-Access | 305 | 10.1.11 | Enumerated | M, V | | | | No | +| WLAN- 3GPP-IP-Access | 306 | 10.1.12 | Enumerated | M, V | | | | No | +| APN-Authorized | 307 | 10.1.14 | Grouped | M, V | | | | No | +| APN-Barring-Type | 309 | 10.1.16 | Enumerated | M, V | | | | No | +| WLAN-Direct-IP-Access | 310 | 10.1.17 | Enumerated | M, V | | | | No | +| Session-Request-Type | 311 | 10.1.23 | Enumerated | M, V | | | | No | +| Routing-Policy | 312 | 10.1.24 | IPFilterRule | M, V | | | | No | +| Max-Requested-Bandwidth | 313 | 10.1.26 | OctetString | M, V | | | | No | +| Charging-Characteristics | 314 | 10.1.27 | Integer | M, V | | | | No | +| Charging-Nodes | 315 | 10.1.28 | Grouped | M, V | | | | No | +| Primary-OCS-Charging-Function-Name | 316 | 10.1.29 | DiameterIdentity | M, V | | | | No | +| Secondary-OCS-Charging-Function-Name | 317 | 10.1.30 | DiameterIdentity | M, V | | | | No | +| 3GPP-AAA-Server-Name | 318 | 10.1.34 | DiameterIdentity | M, V | | | | No | +| Maximum-Number-Accesses | 319 | 10.1.38 | Unsigned32 | M, V | | | | No | + +NOTE: The AVP header bit denoted as 'M', indicates whether support of the AVP is required. The AVP header bit denoted as 'V', indicates whether the optional Vendor-ID field is present in the AVP header. For further details, see IETF RFC 3588 [7]. + +### 10.1.1 Auth-Session-State + +Between the 3GPP AAA server and the HSS, Diameter sessions are implicitly terminated. An implicitly terminated session is one for which the server does not maintain state information. The client does not need to send any re-authorization or session termination requests to the server. + +The Diameter base protocol includes the Auth-Session-State AVP as the mechanism for the implementation of implicitly terminated sessions. + +The client (server) shall include in its requests (responses) the Auth-Session-State AVP set to the value NO\_STATE\_MAINTAINED (1), as described in RFC 3588 [7]. As a consequence, the server does not maintain any state information about this session and the client does not need to send any session termination request. Neither the Authorization-Lifetime AVP nor the Session-Timeout AVP shall be present in requests or responses. + +### 10.1.2 User-Name + +The User-Name AVP is defined in the RFC 3588 [7] and contains the NAI format User Identity as described in 3GPP TS 23.003 [22]. + +For the WLAN Wx reference point, the User-Name AVP contains the IMSI of the subscriber. + +### 10.1.3 Visited-Network-Identifier + +The Visited-Network-Identifier AVP is defined in 3GPP TS 29.229 [6] and indicates the 3GPP VPLMN where the user is roaming. + +### 10.1.4 SIP-Auth-Data-Item + +The SIP-Auth-Data-Item AVP is defined in 3GPP TS 29.229 [6]. However three new more conditional AVPs are needed for WLAN Wx reference point. + +#### AVP format + +``` +SIP-Auth-Data-Item ::= < AVP Header : 612 > + [ SIP-Item-Number ] + [ SIP-Authentication-Scheme ] + [ SIP-Authenticate ] + [ SIP-Authorization ] + [ SIP-Authentication-Context ] + [Confidentiality-Key] + [Integrity-Key] + [Authentication-Method] + [Authentication-Information-SIM] + [Authorization-Information-SIM] + * [AVP] +``` + +### 10.1.5 Authentication-Method + +The Authentication-Method AVP is of type Enumerated and indicates the authentication method required for the user. The following values are defined: + +#### WLAN\_EAP\_SIM (0) + +- The UE indicates to the HSS that the required authentication method is EAP/SIM. + +#### WLAN\_EAP\_AKA (1) + +- The UE indicates to the HSS that the required authentication method is EAP/AKA. + +### 10.1.6 Authentication-Information-SIM + +The Authentication-Information-SIM AVP is of type OctetString and contains the concatenation of authentication challenge RAND and the ciphering key Kc. + +### 10.1.7 Authorization -Information-SIM + +The Authentication-Information-SIM AVP is of type OctetString and contains the response SRES. + +### 10.1.8 WLAN-User-Data + +The WLAN-User-Data AVP is of type Grouped. This AVP contains the WLAN User Profile information for the 3GPP AAA Server to authorize the service. + +#### AVP format + +``` +WLAN-User-Data ::= + [Subscription-ID ] + { WLAN-Access } + { WLAN-3GPP-IP-Access } + [ Session-Timeout ] + * [ APN-Authorized ] + * [ Maximum-Number-Accesses ] + { WLAN-Direct-IP-Access } + [ QoS- Resources ] + * [AVP] +``` + +The QoS-Auth-Resources AVP in the WLAN-User-Data grouped AVP shall contain the subscribed QoS in WLAN Direct IP Access case. + +### 10.1.9 Void + +### 10.1.10 Charging-Data + +The Charging-Data AVP is of type Grouped, and contains the addresses of the charging functions. + +#### AVP format + +``` +Charging-Data ::= + { Charging-Characteristics } + { Charging-Nodes } + * [AVP] +``` + +When this AVP is present within the APN-Authorised AVP, charging data apply to the specific W-APN within the APN-Authorised AVP and shall prevail over the general received Charging-Data. + +### 10.1.11 WLAN-Access + +The WLAN-Access AVP is of type Enumerated, and allows operators to determine barring of 3GPP -WLAN interworking subscription. The following values are defined: + +WLAN\_SUBSCRIPTION\_ALLOWED (0) + +- The subscriber has WLAN subscription. + +WLAN\_SUBSCRIPTION\_BARRED (1) + +- The subscriber has no WLAN subscription. + +### 10.1.12 WLAN-3GPP-IP-Access + +The WLAN-3GPP-IP-Access AVP is of type Enumerated, and allows operator to disable all W-APNs for a subscriber at one time. If there is a conflict between this item and the "APN-Barring-type" flag of any W-APN, the most restrictive will prevail. The following values are defined: + +WLAN\_APNS\_ENABLE (0) + +- Enable all APNs for a subscriber. + +WLAN\_APNS\_DISABLE (1) + +- Disable all APNs for a subscriber. + +### 10.1.13 Session-Timeout + +The Session-TimeOut AVP is defined in RFC 3588 [7] and indicates the maximum period for a session measured in seconds. + +This AVP is used for re-authentication purposes. If this field is not used, the WLAN AN will apply default time intervals. + +### 10.1.14 APN-Authorized + +The APN-Authorized AVP is of type Grouped and contains authorization information for the APNs. This AVP indicates the list of allowed W-APNs and the environment where the access is allowed (visited or home PLMN). + +Also information is provided about the WLAN UE remote IP address when it has been statically assigned by the operator. + +#### AVP format + +``` +APN-Authorized ::= + { 3GPP-WLAN-APN-Id } + { APN-Barring-Type } + [ Framed-IP-Address ] + * [Framed-IPv6-Prefix] + [ Max-Requested-Bandwidth ] + [ QoS- Resources ] + * [AVP] +``` + +### 10.1.15 3GPP-WLAN-APN-Id + +The 3GPP-WLAN-APN-Id AVP is of type OctetString, and contains the W-APN for which the user will have services available. These W-APNs may be mapped to services in the home network or in the visited network. W-APN is defined in 3GPP TS 23.003 [22]. + +### 10.1.16 APN-Barring-Type + +The APN-Barring-Type AVP is of type Enumerated, and contains a flag indicating whether access is allowed in visited PLMNs or in the home PLMN. + +WLAN\_ APN\_ NO\_ BARRING (0) + +Access is allowed in visited PLMNs and home PLMN. + +WLAN\_ APN\_ HOME\_ BARRED\_ WHEN\_ ROAMING (1) + +The subscriber is barred to activate the W-APN that access a PDG within the HPLMN when he is located in VPLMN. + +WLAN\_ APN\_ VISITED\_ BARRED (2) + +The subscriber is barred to activate the W-APN that access a PDG within the VPLMN when he is located in a VPLMN. + +WLAN\_ APN\_ HOME\_ BARRED (3) + +The subscriber is barred to activate the W-APN that access a PDG within the HPLMN when he is located in the HPLMN. + +WLAN\_ APN\_ INTERNET\_ ACCESS\_ BARRED (4) + +The subscriber is barred to access internet through any W-APN regardless of whether he is located in a VPLMN or in the HPLMN. + +### 10.1.17 WLAN Direct IP Access + +The WLAN Direct IP Access AVP is of type Enumerated, and indicate whether the user has direct access to external IP networks, e.g. Internet, from the WLAN Access Network or not. + +WLAN\_ DIRECT\_ IP\_ ACCESS (0) + +- The user is allowed to access directly to external IP networks. + +WLAN\_ NO\_ DIRECT\_ IP\_ ACCESS (1) + +- The user is not allowed to access directly to external IP networks. + +### 10.1.18 Server-Assignment-Type + +The Server-Assignment-Type AVP is defined in 3GPP TS 29.229 [6] and indicates the type of procedure the 3GPP AAA Server is asking to the HSS. + +Wx reference point defines as valid only NO\_ ASSIGNMENT, REGISTRATION, USER\_ DEREGISTRATION, ADMINISTRATIVE\_ DEREGISTRATION and AUTHENTICATION\_ FAILURE. + +Pr reference point defines as valid only REGISTRATION, USER\_ DEREGISTRATION. + +### 10.1.19 Deregistration-Reason + +The Deregistration-Reason AVP is defined in 3GPP TS 29.229 [6] and indicates reason for a de-registration operation. + +This grouped AVP contains a Reason-Code AVP to indicate the reason for the de-registration. Reasons are listed in 3GPP TS 29.229 [6]. Wx reference point defines as valid only PERMANENT\_TERMINATION value. + +### 10.1.20 EAP-Payload + +The EAP-Payload AVP is defined in the IETF RFC 4072 [8] and contains the encapsulated EAP packet that is being exchanged between the EAP client and the home Diameter server. + +### 10.1.21 Auth Req Type + +The Auth Req Type AVP is of type Enumerated and indicates the action that the PDG is asking to the 3GPP AAA Server to perform (Authentication, authorization or both). Wm interface only makes use of the AUTHENTICATION\_ONLY value. It is defined in the IETF RFC 4072 [8]. + +### 10.1.22 EAP-Master-Session-Key + +The EAP-Master-Session-Key AVP is of type OctetString and contains keying material for protecting the communications between the user and the NAS, i.e. Pairwise Master Key (PMK) or Master Session Key (MSK). It is defined in the IETF RFC 4072 [8]. + +### 10.1.23 Session-Request-Type + +The Session-Request-Type AVP is of type Enumerated and indicates the action that the PDG is asking to the 3GPP AAA Server to perform (authorization or routing policy). The following values are defined: + +AUTHORIZATION REQUEST (0) + +- The PDG is requesting authorization for a user for a given W-APN. + +ROUTING POLICY (1) + +- The PDG is indicating that routing policy information is present. + +### 10.1.24 Routing-Policy + +The Routing Policy AVP is of type IPFilterRule, and defines a packet filter for an IP flow with the following information: + +- Direction (in or out). +- Source and destination IP address (possibly masked). +- Protocol. +- Source and destination port (list or ranges). + +Where the protocol type shall be set to ESP (50). The IPFilterRule type shall be used with the following restrictions: + +- Only the Action "permit" shall be used. +- No "options" shall be used. +- The invert modifier "!" for addresses shall not be used. +- The keyword "assigned" shall not be used. +- For direction "out", an IPv4 destination IP address shall not be wildcarded. For direction "out", the 64 bits network prefix of an IPv6 destination IP address shall not be wildcarded. + +The Routing-Policy AVP shall be used to describe a single IP flow. + +The direction "in" refers to uplink IP flows, and the direction "out" refers to downlink IP flows. + +### 10.1.25 Subscription-ID + +The Subscription-ID AVP is of type grouped and indicates the user identity to be used for charging purposes. It is defined in the IETF RFC 4006 [19]. + +WLAN shall make use only of the values MSISDN or IMSI. This grouped AVP shall set the sub-AVP Subscription-Id-Type to value "END\_USER\_E164" or to value "END\_USER\_IMSI" and shall set the sub-AVP Subscription-Id-Data to the MSISDN value. + +### 10.1.26 Max-Requested-Bandwidth + +The Max-Requested-Bandwidth AVP is of type OctetString and indicates the Max-Subscriber-Bandwidth. If present, shall be downloaded from HSS to 3GPP AAA Server, and sent from the 3GPP AAA Server to the PDG. + +### 10.1.27 Charging-Characteristics + +The Charging-Characteristics AVP is of type Integer, and contains the charging mode to be applied as described in 3GPP TS 32.215 [24]. + +### 10.1.28 Charging-Nodes + +The Charging-Nodes AVP is of type Grouped, and contains the addresses of the charging functions, as described in 3GPP TS 32.240 [23]. + +AVP format + +Charging-Nodes ::= + +[ Primary-OCS-Charging-Function-Name ] +[ Secondary-OCS-Charging-Function-Name ] +[ Primary-Charging-Collection-Function-Name ] +[ Secondary-Charging-Collection-Function-Name ] +\* [AVP] + +### 10.1.29 Primary-OCS-Charging-Function-Name + +The Primary-OCS-Charging-Function-Name AVP is of type DiameterIdentity, and defines the address of the Primary Online Charging System (OCS) + +### 10.1.30 Secondary-OCS-Charging-Function-Name + +The Secondary-OCS-Charging-Function-Name AVP is of type DiameterIdentity, and defines the address of the Secondary Online Charging System (OCS). + +When this value is not present, the PDG shall dynamically assign an IP address to the WLAN UE. + +### 10.1.31 Secondary-Charging-Collection-Function-Name + +The Secondary-Charging-Collection-Function-Name AVP is defined in 3GPP TS 29.229 [6] and contains the address of the Secondary Charging Collection Function. + +### 10.1.32 Framed-IP-Address + +The Framed-IP-Address AVP is of type OctetString, and defines the remote IPv4 address that the operator has statically assigned to the WLAN UE. + +When the Framed-IP-Address AVP is not present, the PDG shall dynamically assign, or ask some other node, e.g. a DHCP server, to assign, a remote IP address to the WLAN UE. + +The occurrence of this AVP is as per described in section 10.1 of NASREQ IETF RFC 4005 [12]: + +Framed-IP-Address | 0-1 | 0-1 | + +### 10.1.33 Framed-IPv6-Prefix + +The Framed-IPv6-Prefix AVP is of type OctetString, and defines the remote IPv6 prefix that the operator has statically assigned to the WLAN UE. + +When the Framed-IPv6-Prefix AVP is not present, the PDG shall dynamically assign, or ask some other node, e.g. a DHCP server, to assign, a remote IP address to the WLAN UE. + +The occurrence of this AVP is as per described in section 10.1 of NASREQ IETF RFC 4005 [12]: + +Framed-IPv6-Prefix | 0+ | 0+ | + +### 10.1.34 3GPP-AAA-Server-Name + +The 3GPP-AAA-Server-Name AVP is of type DiameterIdentity, and defines the Diameter address of the 3GPP AAA Server node. + +### 10.1.35 Void + +### 10.1.36 Primary-Charging-Collection-Function-Name + +The Primary-Charging-Collection-Function-Name AVP is defined in 3GPP TS 29.229 [6] and contains the address of the Primary Charging Collection Function. + +### 10.1.37 NAS-Port-Type + +The NAS-Port-Type AVP is the Diameter translation of the NAS-Port-Type RADIUS attribute and contains an indication of the type of access that the user is requesting (tunnel or WLAN access). + +### 10.1.38 Maximum-Number-Accesses + +The Maximum-Number-Accesses AVP is of type Unsigned32, and used to specify the maximum number of concurrent accesses (IKE security associations) per W-APN. + +### 10.1.39 WLAN-Session-Id + +The WLAN-Session-Id AVP is of type Unsigned32. It is specified in 3GPP TS 32.299 [32]. The identifier is used to correlate PDG and WLAN AN charging data (see 3GPP TS 32.252 [33]). + +The WLAN-Session-Id AVP contains the charging identifier generated by the 3GPP AAA Server when WLAN access authentication and authorization procedure is done successfully. + +The WLAN-Session-Id AVP is sent to PDG from 3GPP AAA Server during Wm authorization procedure and PDG includes the WLAN Session Id to PDG charging data. + +### 10.1.40 PDG-Charging-Id + +The PDG-Charging-Id AVP is of type Unsigned32. It is specified in 3GPP TS 32.299 [32]. The identifier is used to correlate PDG and WLAN AN charging data (see 3GPP TS 32.252 [33]). + +The PDG-Charging-Id AVP contains the charging identifier generated by the PDG for the tunnel. + +The PDG-Charging-Id AVP is sent to 3GPP AAA Server from PDG during Wm authorization procedure and 3GPP AAA Server includes the PDG Charging Id to WLAN AN charging data. + +### 10.1.41. 3GPP-WLAN-QoS-Filter-Rule + +The 3GPP-WLAN-QoS-Filter-Rule attribute contains the 3GPP WLAN QoS Profile formatted as a QoSFilterRule string as defined in IETF RFC 4005 [12]. This 3GPP vendor-specific RADIUS attribute is only applicable on the RADIUS-based Wa and Wd reference points and is encoded as follows (as per IETF RFC 2865 [17]). + +| Octets | Bits | | | | | | | | +|--------|------------------------------------------|---|---|---|---|---|---|---| +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +| 1 | Type = 26 | | | | | | | | +| 2 | Length = n | | | | | | | | +| 3 | 3GPP Vendor id octet 1 | | | | | | | | +| 4 | 3GPP Vendor id octet 2 | | | | | | | | +| 5 | 3GPP Vendor id octet 3 | | | | | | | | +| 6 | 3GPP Vendor id octet 4 | | | | | | | | +| 7 | 3GPP type = a | | | | | | | | +| 8 | 3GPP Length = (n-6) | | | | | | | | +| 9-n | QoSFilterRule (UTF-8 encoded characters) | | | | | | | | + +### 10.1.42. QoS-Resources + +The QoS-Resources AVP is defined in IETF RFC 5777 [35]. It includes the description of the resources that have been stored in the HSS as a part of a user's subscription or authorized by the 3GPP AAA Server. + +Over the Wx interface, this AVP is used to contain subscribed 3GPP WLAN QoS Profile, and over the Wm interface, this AVP is used to contain authorized 3GPP WLAN QoS profile. The following information shall be provided at least over the Wx interface: + +- DiffServ DSCP information. + +### 10.1.43 QoS-Capability + +The QoS-Capability grouped AVP is defined in IETF RFC 5777 [35]. It includes a list of supported Quality of Service profiles. The QoS-Profile sub-AVP shall have Vendor-ID and Specifier fields set to default value 0 (zero). + +### 10.1.44 3GPP-WLAN-QoS-Filter-Support + +The 3GPP-WLAN-QoS-Filter-Support attribute is a 3GPP vendor-specific attribute only applicable on the RADIUS-based Wa and Wd reference points. It indicates whether the WLAN AN supports the 3GPP-WLAN-QoS-Filter-Rule attribute and is encoded as follows (as per IETF RFC 2865 [38]). + +| Octets | Bits | | | | | | | | +|--------|-------------------------|---|---|---|---|---|---|---| +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +| 1 | Type = 26 | | | | | | | | +| 2 | Length = 9 | | | | | | | | +| 3 | 3GPP Vendor id octet 1 | | | | | | | | +| 4 | 3GPP Vendor id octet 2 | | | | | | | | +| 5 | 3GPP Vendor id octet 3 | | | | | | | | +| 6 | 3GPP Vendor id octet 4 | | | | | | | | +| 7 | 3GPP type = b | | | | | | | | +| 8 | 3GPP Length = 3 | | | | | | | | +| 9 | Support-Indicator octet | | | | | | | | + +The following values are defined for the Support-Indicator octet: + +- 0 - 3GPP-WLAN-QoS-Filter-Rule attribute is not supported by the WLAN AN. +- 1 - 3GPP-WLAN-QoS-Filter-Rule attribute is supported by the WLAN AN. + +If the 3GPP-WLAN-QoS-Filter-Support attribute is not present in the request, the 3GPP-WLAN-QoS-Filter-Rule attribute is not supported by the WLAN AN. + +## 10.2 Handling of Information Elements + +In the tables that describe the Information Elements transported by each Diameter command, each Information Element is marked as (M) Mandatory, (C) Conditional or (O) Optional. + +- A mandatory Information Element (marked as (M) in the table) shall always be present in the command. If this Information Element is absent, an application error occurs at the receiver and an answer message shall be sent back to the originator of the request with the Result-Code set to DIAMETER\_MISSING\_AVP. This message shall also include a Failed-AVP AVP containing the missing Information Element i.e. the corresponding Diameter AVP defined by the AVP Code and the other fields set as expected for this Information Element. +- A conditional Information Element (marked as (C) in the table) shall be present in the command if certain conditions are fulfilled. + - If the receiver detects that those conditions are fulfilled and the Information Element is absent, an application error occurs and an answer message shall be sent back to the originator of the request with the Result-Code set to DIAMETER\_MISSING\_AVP. This message shall also include a Failed-AVP AVP containing the missing Information Element i.e. the corresponding Diameter AVP defined by the AVP Code and the other fields set as expected for this Information Element. + - If those conditions are not fulfilled, the Information Element shall be absent. If however this Information Element appears in the message, it shall not cause an application error and it may be ignored by the receiver if this is not explicitly defined as an error case. Otherwise, an application error occurs at the receiver and an answer message with the Result-Code set to DIAMETER\_AVP\_NOT\_ALLOWED shall be sent back to the originator of the request. A Failed-AVP AVP containing a copy of the corresponding Diameter AVP shall be included in this message +- An optional Information Element (marked as (O) in the table) may be present or absent in the command, at the discretion of the application at the sending entity. Absence or presence of this Information Element shall not cause an application error and may be ignored by the receiver. + +## 10.3 Result-Code AVP values + +This subclause defines new result code values that shall be supported by all Diameter implementations that conform to this specification. When one of the result codes defined here is included in a response, it shall be inside an Experimental-Result AVP and Result-Code AVP shall be absent. + +### 10.3.1 Permanent Failures + +Errors that fall within the Permanent Failures category are used to inform the peer that the request failed, and should not be attempted again. + +Errors not defined in this specification may be found in 3GPP TS 29.229 [6] + +#### 10.3.1.1 DIAMETER\_ERROR\_USER\_NO\_WLAN\_SUBSCRIPTION (5041) + +A message was received for a user with no WLAN-subscription. + +#### 10.3.1.2 DIAMETER\_ERROR\_W-APN\_UNUSED\_BY\_USER (5042) + +A message was received for a user who has no subscription for a specified W-APN. + +#### 10.3.1.3 DIAMETER\_ERROR\_NO\_ACCESS\_INDEPENDENT\_SUBSCRIPTION (5043) + +A message was received requesting WLAN 3GPP IP access for a user whose subscription does not allow it if it was not previously authenticated by WLAN Direct IP Access. + +#### 10.3.1.4 DIAMETER\_ERROR\_USER\_NO\_W-APN\_SUBSCRIPTION (5044) + +A message was received requesting WLAN 3GPP IP access for a user whose subscription does not allow it if it was not previously authenticated by WLAN 3GPP direct access. + +# 11 Pr Description + +The Pr Reference Point is defined in 3GPP TS 23.141 [31] and allows the 3GPP AAA Server to report presence relevant events to the Presence Network Agent (PNA). + +## 11.1 Functionality + +The functionality of the Pr reference point is to enable: + +- Indication of the Attach/Detach to the PNA by the 3GPP AAA Server of a WLAN user. +- Indication of the W-APN Activation/DeActivation to the PNA by the 3GPP AAA Server of a WLAN user. + +## 11.2 Protocols + +The Pr reference point shall be Diameter based and shall have an application ID defined for it. It is defined as an IETF vendor specific Diameter application, where the vendor is 3GPP. The application identifier is to 16777230. It is assigned by IANA (). + +## 11.3 Procedures Description + +### 11.3.1 WLAN Attach/Detach Indication + +According to the requirements given in clause 11.1, the Pr reference point shall enable: + +- an indication of the Attach /Detach to the PNA. + +This procedure is used between the 3GPP AAA Server and the PNA. + +The procedure of Attach indication shall be invoked by the 3GPP AAA Server after a new subscriber has been authenticated and authorised successfully by the 3GPP AAA Server. + +The procedure of Detach indication shall be invoked by the 3GPP AAA Server when a WLAN user becomes detached, e.g. the WLAN UE has disappeared from WLAN coverage, or the OSC has initiated a disconnection. + +The Pr reference point performs these functions based on the reuse of the existing Cx Server Assignment command code set (SAR/SAA). + +**Table 11.3.1.1: WLAN Attach / Detach Indication Request** + +| Information element name | Mapping to Diameter AVP | Cat. | Description | +|----------------------------|----------------------------|------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Permanent User Identity | User-Name | M | This information element contains the permanent identity of the user, i.e. the IMSI. | +| Server Assignment Type | Server-Assignment-Type | M | Type of procedure the 3GPP AAA Server indicated to the PNA. When this IE contains REGISTRATION value, the 3GPP AAA Server indicates to the PNA a WLAN user is attached. When this IE contains USER_DEREGISTRATION, the 3GPP AAA Server indicates to the PNA a WLAN user is detached. Any other value is considered as an error case. | +| Visited Network Identifier | Visited-Network-Identifier | C | An identifier that allows the home network to identify the Visited Network. This AVP shall be present if the PDG is not in the WLAN-UE's home network i.e. the WLAN-UE is roaming. | +| Routing Information | Destination-Host | C | If the 3GPP AAA Server knows the PNA name, this AVP shall be present. This information is available if the 3GPP AAA Server already has the PNA name stored. The PNA name is obtained from the Origin-Host AVP, which is received from the PNA, e.g. included in the SAA command. Otherwise only the Destination-Realm is included, so that it is resolved to a PNA address. | + +**Table 11.3.1.2: WLAN Attach / Detach Indication Answer** + +| Information element name | Mapping to Diameter AVP | Cat. | Description | +|--------------------------|-----------------------------------|------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Result | Result-Code / Experimental-Result | M | Result of the operation.
A Result-Code AVP shall be used for errors defined in the Diameter Base Protocol.
An Experimental-Result AVP shall be used for Pr errors. This is a grouped AVP which contains the 3GPP Vendor ID in the Vendor-Id AVP, and the error code in the Experimental-Result-Code AVP. | + +#### 11.3.1.1 Detailed behaviour + +When a new 3GPP subscriber has been authenticated and authorized by the 3GPP AAA Server, the 3GPP AAA Server indicates the status of "Attach" towards the PNA. The PNA shall, in the event of an error in any of the steps, stop processing and return the corresponding error code, see 3GPP TS 29.229 [6]). + +When a WLAN user is in Detach status, the 3GPP AAA Server indicates the status of "Detach" towards the PNA. The PNA shall, in the event of an error in any of the steps, stop processing and return the corresponding error code, see 3GPP TS 29.229 [6]). + +The 3GPP AAA server sends Server-Assignment-Request command to the PNA indicating the Attach/Detach status. The subscriber is identified by the User-Name AVP. + +At reception of Server-Assignment-Request command, the PNA shall perform (in the following order): + +1. Check that the user is known. If not Experimental-Result-Code shall be set to DIAMETER\_ERROR\_USER\_UNKNOWN. +2. Check the Server Assignment Type value received in the request: + - If it indicates REGISTRATION, that means the WLAN user is in Attach status, the PNA shall store the 3GPP AAA Server name for the authenticated and authorized 3GPP subscriber and set the Result-Code AVP to DIAMETER\_SUCCESS in the Server-Assignment-Response command. + - If it indicates USER\_DEREGISTRATION, that means the WLAN user is in Detach status, the PNA shall remove the 3GPP AAA Server name previously assigned for the 3GPP subscriber and set the Result-Code AVP to DIAMETER\_SUCCESS in the Server-Assignment-Response command. + - If it indicates any other value, the Result-Code shall be set to DIAMETER\_UNABLE\_TO\_COMPLY, and no WLAN Attach/Detach indication procedure shall be performed. + +The Origin-Host AVP shall contain the 3GPP AAA server identity. + +### 11.3.2 W-APN Activation/De-Activation Indication + +#### 11.3.2.1 W-APN Activation Indication + +According to the requirements given in clause 11.1, the Pr reference point shall enable: + +- an indication of the W-APN Activation to the PNA. + +This procedure is used between the 3GPP AAA Server and the PNA. + +The procedure of W-APN Activation indication shall be invoked by the 3GPP AAA Server when a tunnel to a W-APN is established successfully as defined in section 7.9; see 3GPP TS 23.234 [4]. + +The W-APN Activation Indication Request/Response are mapped onto the NASREQ AAR/AAA messages. + +**Table 11.3.2.1: W-APN Activation Indication request** + +| Information element name | Mapping to Diameter AVP | Cat. | Description | +|----------------------------|----------------------------|------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Permanent User Identity | User-Name | M | This information element contains the identity of the user. | +| Visited Network Identifier | Visited-Network-Identifier | C | An identifier that allows the home network to identify the Visited Network. This AVP shall be present if the PDG is not in the WLAN-UE's home network, i.e. the WLAN-UE is roaming. | +| W-APN-ID | 3GPP-WLAN-APN-Id | M | This information element shall contain the W-APN for which the UE has been granted authorization. | +| Routing Information | Destination-Host | C | The PNA name is obtained from the Origin-Host AVP of a previously received message. | + +**Table 11.3.2.2:W-APN Activation Indication Answer** + +| Information element name | Mapping to Diameter AVP | Cat. | Description | +|--------------------------|-----------------------------------|------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Result | Result-Code / Experimental-Result | M | Result of the operation.
A Result-Code AVP shall be used for errors defined in the Diameter Base Protocol.
An Experimental-Result AVP shall be used for Pr errors. This is a grouped AVP which contains the 3GPP Vendor ID in the Vendor-Id AVP, and the error code in the Experimental-Result-Code AVP. | + +##### 11.3.2.1.1 Detailed behaviour + +If this message is received at the PNA, it indicates that the WLAN-UE now has been authorised for such a W-APN and has one (or more) tunnel(s) active to the particular W-APN at the PDG. The PNA shall, in the following order (if there is an error in any of the steps, the PNA shall stop processing and return the corresponding error code): + +- 1) Check that the user exists in the PNA. If not Experimental-Result-Code shall be set to DIAMETER\_ERROR\_USER\_UNKNOWN. +- 2) Store the current active W-APN +- 3) Optionally, the PNA shall store the PDG IP address associated with the W-APN. +- 4) The Result-Code shall be set to DIAMETER\_SUCCESS. + +Exceptions to the cases specified here shall be treated by a PNA as error situations, so the Result-Code shall be set to DIAMETER\_UNABLE\_TO\_COMPLY. No information shall be stored in PNA. + +#### 11.3.2.2 W-APN De-Activation Indication + +According to the requirements given in clause 11.1, Pr reference point shall enable: + +- an indication of the W-APN Deactivation to the PNA. + +This procedure is used between the 3GPP AAA Server and the PNA. + +The procedure of W-APN Deactivation indication is invoked by the 3GPP AAA Server when a particular W-APN is deactivated. + +The W-APN Deactivation Indication Request/Response are mapped onto the Abort Session Request/Answer (ASR/ASA) messages defined in RFC 3588 [7]. + +**Table 11.3.3.1: W-APN Deactivation Indication Request** + +| Information element name | Mapping to Diameter AVP | Cat. | Description | +|--------------------------|-------------------------|------|------------------------------------------------------------------------------------------------------| +| User Identity | User-Name | M | This information element shall contain the identity of the user. | +| W-APN-Id | 3GPP-WLAN-APN-Id | M | This information element shall contain the W-APN Identification associated with the deactivation. | +| Routing Information | Destination-Host | M | The PNA name shall be obtained from the Origin-Host AVP of a previous message received from the PNA. | + +**Table 11.3.3.2: W-APN DeActivation Indication Answer** + +| Information element name | Mapping to Diameter AVP | Cat. | Description | +|--------------------------|-----------------------------------|------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Result | Result-Code / Experimental-Result | M | Result of the operation.
A Result-Code AVP shall be used for errors defined in the Diameter Base Protocol.
An Experimental-Result AVP shall be used for Pr errors. This is a grouped AVP which contains the 3GPP Vendor ID in the Vendor-Id AVP, and the error code in the Experimental-Result-Code AVP. | + +##### 11.3.2.2.1 Detailed behaviour + +The 3GPP AAA Server shall make use of this procedure to indicate the PNA that a particular W-APN has no active tunnel left for a specific user. On receipt of the message, the PNA shall: + +- 1) Check that the user is known in the PNA. If not, Experimental-Result-Code shall be set to DIAMETER\_ERROR\_USER\_UNKNOWN. +- 2) The PNA shall set the Result-Code to DIAMETER\_SUCCESS and send back the SAA command to the 3GPP AAA Server. + +## 11.4 Information Elements Contents + +### 11.4.1 WLAN Attach/Detach Indication + +The **Server-Assignment-Request (SAR)** command, indicated by the Command-Code field being set to 301 and the 'R' bit set in the Command Flags field, is sent by the 3GPP AAA Server to the PNA, in order to indicate to the PNA a WLAN user is in the status of Attached or Detached. + +Message Format + +``` + ::= < Diameter Header: 301, REQ, PXY, XXXX> + < Session-Id > + { Vendor-Specific-Application-Id } + { Auth-Session-State } + { Origin-Host } + { Origin-Realm } + [ Destination-Host ] + { Destination-Realm } + [ User-Name ] + [Visited-Network-Identifier] + { Server-Assignment-Type } + *[ AVP ] + *[ Proxy-Info ] + *[ Route-Record ] +``` + +The **Server-Assignment-Answer (SAA)** command, indicated by the Command-Code field being set to 301 and the 'R' bit cleared in the Command Flags field, is sent by the PNA to the 3GPP AAA Server, to confirm the Attached or Detached indication. + +Message Format + +``` + + ::= < Diameter Header: 301, PXY, XXXX > + < Session-Id > + { Vendor-Specific-Application-Id } + [ Result-Code ] + [ Experimental-Result ] + { Auth-Session-State } + { Origin-Host } + { Origin-Realm } + [ User-Name ] + *[ AVP ] + *[ Proxy-Info ] + *[ Route-Record ] + +``` + +### 11.4.2 W-APN Activation/DeActivation Indication + +#### 11.4.2.1 W-APN Activation Indication + +The W-APN Activation Indication request and response messages are mapped onto the NASREQ AAR/AAA messages. The ABNF for this is defined below: + +``` + + ::= < Diameter Header: 265, REQ, PXY > + < Session-Id > + { Auth-Application-Id } + { Origin-Host } + { Origin-Realm } + { Destination-Realm } + { Auth-Request-Type } + [ Destination-Host ] + [ Visited-Network-Identifier ] + { 3GPP-WLAN-APN- Id } + [ User-Name ] + [ Authorization-Lifetime ] + [ Auth-Grace-Period ] + [ Auth-Session-State ] + [ Framed-IP-Address ] + [ Framed-IP-Netmask ] + * [ Tunneling ] + * [ Proxy-Info ] + * [ Route-Record ] + * [ AVP ] + +``` + +The ABNF for the AAA is defined as follows: + +``` + + ::= < Diameter Header: 265, PXY > + < Session-Id > + { Auth-Application-Id } + { Auth-Request-Type } + { Result-Code } + { Origin-Host } + { Origin-Realm } + [ Subscription-ID-AVP ] + [ Error-Message ] + [ Error-Reporting-Host ] + * [ Failed-AVP ] + * [ Proxy-Info ] + * [ AVP ] + +``` + +#### 11.4.2.2 W-APN Deactivation Indication + +The ABNF for the W-APN Deactivation Indication Procedure is mapped onto the ASR and ASA commands as defined below: + +``` + + ::= < Diameter Header: 274, REQ, PXY > + < Session-Id > + { Origin-Host } + { Origin-Realm } + { Destination-Realm } + { Destination-Host } + { Auth-Application-Id } + [ User-Name ] + +``` + +``` +{ 3GPP-WLAN-APN-Id } +[ Origin-State-Id ] +* [ Proxy-Info ] +* [ Route-Record ] +*[ AVP ] +``` + +``` + ::= < Diameter Header: 274, PXY > + < Session-Id > + { Result-Code } + { Origin-Host } + { Origin-Realm } + [ User-Name ] + [ Origin-State-Id ] + [ Error-Message ] + [ Error-Reporting-Host ] + * [ Failed-AVP ] + * [ Redirected-Host ] + [ Redirected-Host-Usage ] + [ Redirected-Max-Cache-Time ] + * [ Proxy-Info ] + * [ AVP ] +``` + +# 12 User identity to HSS resolution + +The User identity to HSS resolution mechanism enables the 3GPP AAA servers to find the identity of the HSS that holds the subscriber data for a given user identity when multiple and separately addressable HSSs have been deployed by the network operator. The resolution mechanism is not required in networks that utilise a single HSS or when a 3GPP AAA server is configured to use pre-defined HSS address/identity. + +In networks where more than one independently addressable HSS are utilized by a network operator, and the 3GPP AAA servers are not configured to use pre-defined HSS address/identity, each 3GPP AAA server shall be configured with the address/identity of the Diameter Agent (Redirect or Proxy) implementing this resolution mechanism. + +To get the HSS identity that holds the subscriber data for a given user identity, the 3GPP AAA server shall send the Diameter request normally destined to the HSS to a pre-configured address/identity of a Diameter agent supporting the User identity to HSS resolution mechanism. + +- If this Diameter request is received by a Diameter Redirect Agent, the Diameter Redirect Agent shall determine the HSS identity based on the provided user identity and shall send to the 3GPP AAA server a notification of redirection towards the HSS identity, in response to the Diameter request. Multiple HSS identities may be included in the response, as specified in IETF RFC 3588 [7]. In such a case, the 3GPP AAA server shall send the Diameter request to the first HSS identity in the ordered list received in the Diameter response from the Diameter Redirect Agent. If the 3GPP AAA server does not receive a successful response to the Diameter request, the 3GPP AAA server shall send a Diameter request to the next HSS identity in the ordered list. This procedure shall be repeated until a successful response from an HSS is received. +- If this Diameter request is received by a Diameter Proxy Agent, the Diameter Proxy Agent shall determine the HSS identity based on the provided user identity and shall forward the Diameter request directly to the HSS. The 3GPP AAA server shall determine the HSS identity from the response to the Diameter request received from the HSS. + +After the user identity to HSS resolution, the 3GPP AAA server shall + +# --- Annex A (normative): Wa and Wd Procedures Signalling Flows + +## A.1 Authentication, Authorization and Key Delivery + +The purpose of this signalling sequence is to carry WLAN-UE - 3GPP AAA Server authentication signalling over the Wa and Wd reference points. As a result of a successful authentication, authorization information and session keying material for the authenticated session is delivered from the 3GPP AAA Server to the WLAN. + +This Wa and Wd signalling sequence is initiated by the WLAN when authentication of a WLAN-UE is needed. This can take place when a new WLAN-UE accesses WLAN, when a WLAN-UE switches between WLAN APs or when a periodic re-authentication is performed. + +The signalling sequences shown are based on RADIUS and Diameter, as specified in clauses 4 and 5. For more information on proxying and protocol translation associated with using RADIUS and Diameter between the Wa and Wd reference points see subclause 5.3. + +![Sequence diagram showing Wa and Wd message flow for WLAN Session Authentication and Authorization. The diagram involves three main entities: WLAN, 3GPP AAA Proxy, and 3GPP AAA Server. The process starts with EAP authentication initiation between UE and WLAN. The WLAN sends a Wa: Access_Request to the 3GPP AAA Proxy. The proxy translates this to a Wd: Diameter_EAP_Request to the 3GPP AAA Server. The server responds with a Wd: Diameter_EAP_Answer (EAP Request). The proxy translates this to a Wa: Access_Challenge for the WLAN. The WLAN responds with a Wa: Access_Request. The proxy translates this to a Wd: Diameter_EAP_Request. The server responds with a Wd: Diameter_EAP_Answer (EAP Success, Authorization Info, Session Keying Material). The proxy translates this to a 2N Wa: Access_Accept for the WLAN.](11f18bf0233d812ad2604f88f3385d60_img.jpg) + +``` +sequenceDiagram + participant WLAN + participant 3GPP_AAA_Proxy as 3GPP AAA Proxy + participant 3GPP_AAA_Server as 3GPP AAA Server + + Note left of WLAN: EAP authentication is initiated between UE and WLAN + + WLAN->>3GPP_AAA_Proxy: 1. Wa: Access_Request (EAP Response/Identity(NAI)) + Note right of 3GPP_AAA_Proxy: RADIUS/Diameter Translator Agent + 3GPP_AAA_Proxy->>3GPP_AAA_Server: 2. Wd: Diameter_EAP_Request (EAP Response/Identity(NAI)) + Note right of 3GPP_AAA_Server: + 3GPP_AAA_Server-->>3GPP_AAA_Proxy: 3. Wd: Diameter_EAP_Answer (EAP Request) + Note right of 3GPP_AAA_Proxy: RADIUS/Diameter Translator Agent + 3GPP_AAA_Proxy-->>WLAN: 4. Wa: Access_Challenge (EAP Request) + Note right of WLAN: + WLAN->>3GPP_AAA_Proxy: 5. Wa: Access_Request (EAP Response) + Note right of 3GPP_AAA_Proxy: RADIUS/Diameter Translator Agent + 3GPP_AAA_Proxy->>3GPP_AAA_Server: 6. Wd: Diameter_EAP_Request (EAP Response) + Note right of 3GPP_AAA_Server: + 3GPP_AAA_Server-->>3GPP_AAA_Proxy: 2N Wd: Diameter_EAP_Answer (EAP Success, Authorization Info, Session Keying Material) + Note right of 3GPP_AAA_Proxy: RADIUS/Diameter Translator Agent + 3GPP_AAA_Proxy-->>WLAN: 2N Wa: Access_Accept (EAP Success, Authorization Info, Session Keying Material) + Note right of WLAN: +``` + +Sequence diagram showing Wa and Wd message flow for WLAN Session Authentication and Authorization. The diagram involves three main entities: WLAN, 3GPP AAA Proxy, and 3GPP AAA Server. The process starts with EAP authentication initiation between UE and WLAN. The WLAN sends a Wa: Access\_Request to the 3GPP AAA Proxy. The proxy translates this to a Wd: Diameter\_EAP\_Request to the 3GPP AAA Server. The server responds with a Wd: Diameter\_EAP\_Answer (EAP Request). The proxy translates this to a Wa: Access\_Challenge for the WLAN. The WLAN responds with a Wa: Access\_Request. The proxy translates this to a Wd: Diameter\_EAP\_Request. The server responds with a Wd: Diameter\_EAP\_Answer (EAP Success, Authorization Info, Session Keying Material). The proxy translates this to a 2N Wa: Access\_Accept for the WLAN. + +**Figure A.1: Wa and Wd message flow for WLAN Session Authentication and Authorization +Case a) Wa using RADIUS and Wd using Diameter** + +![Sequence diagram showing Wa and Wd message flow for WLAN Session Authentication and Authorization. Lifelines: WLAN, 3GPP AAA Proxy, 3GPP AAA Server. The process involves EAP authentication initiation, followed by a series of Access Requests, Challenges, and Accepts between the entities.](1e5a58dcaf0936bf18dc3dd0d9cd43ff_img.jpg) + +The diagram illustrates the message flow for WLAN Session Authentication and Authorization. It features three lifelines: WLAN, 3GPP AAA Proxy, and 3GPP AAA Server. The process begins with an EAP authentication initiation between the UE and WLAN. The subsequent steps are as follows: + +1. Wa: Access\_Request (EAP Response/Identity(NAI)) from WLAN to 3GPP AAA Proxy +2. Wd: Access\_Request (EAP Response/Identity(NAI)) from 3GPP AAA Proxy to 3GPP AAA Server +3. Wd: Access\_Challenge (EAP Request) from 3GPP AAA Server to 3GPP AAA Proxy +4. Wa: Access\_Challenge (EAP Request) from 3GPP AAA Proxy to WLAN +5. Wa: Access\_Request (EAP Response) from WLAN to 3GPP AAA Proxy +6. Wd: Access\_Request (EAP Response) from 3GPP AAA Proxy to 3GPP AAA Server +7. 2N Wd: Access\_Accept (EAP Success, Authorization Info, Session Keying Material) from 3GPP AAA Server to 3GPP AAA Proxy +8. 2N Wa: Access\_Accept (EAP Success, Authorization Info, Session Keying Material) from 3GPP AAA Proxy to WLAN + +A dashed box encloses steps 3 through 6, indicating a specific phase of the authentication process. + +Sequence diagram showing Wa and Wd message flow for WLAN Session Authentication and Authorization. Lifelines: WLAN, 3GPP AAA Proxy, 3GPP AAA Server. The process involves EAP authentication initiation, followed by a series of Access Requests, Challenges, and Accepts between the entities. + +**Figure A.2: Wa and Wd message flow for WLAN Session Authentication and Authorization +Case b) Wa and Wd using RADIUS** + +![Sequence diagram showing Wa and Wd message flow for WLAN Session Authentication and Authorization using Diameter between WLAN, 3GPP AAA Proxy, and 3GPP AAA Server.](d2417b04116c354deccb25d98a84a0fb_img.jpg) + +``` + +sequenceDiagram + participant WLAN + participant Proxy as 3GPP AAA Proxy + participant Server as 3GPP AAA Server + + Note over WLAN: EAP authentication is +initiated between UE +and WLAN + + WLAN->>Proxy: 1. Wa: Diameter_EAP_Request + Note over WLAN,Proxy: (EAP Response/Identity(NAI)) + Proxy->>Server: 2. Wd: Diameter_EAP_Request + Note over Proxy,Server: (EAP Response/Identity(NAI)) + + rect rgb(255, 255, 255) + Note over Proxy,Server: 3. Wd:Diameter_EAP_Answer + Server-->>Proxy: (EAP Resquest) + Note over WLAN,Proxy: 4. Wa: Diameter_EAP_Answer + Proxy-->>WLAN: + Note over WLAN,Proxy: 5. Wa: Diameter_EAP_Request + WLAN->>Proxy: (EAP Response) + Note over Proxy,Server: 6.Wd: Diameter_EAP_Request + Proxy->>Server: (EAP Response) + end + + Server-->>Proxy: 2N Wd:Diameter_EAP_Answer + Note over Proxy,Server: (EAP Success, Authorization +Info, Session Keying Material) + Proxy-->>WLAN: 2N+Wa: Diameter_EAP_Answer + Note over WLAN,Proxy: (EAP Success, Authorization +Info, Session Keying Material) + +``` + +Sequence diagram showing Wa and Wd message flow for WLAN Session Authentication and Authorization using Diameter between WLAN, 3GPP AAA Proxy, and 3GPP AAA Server. + +**Figure A.3: Wa and Wd message flow for WLAN Session Authentication and Authorization +Case c) Wa and Wd using Diameter** + +1. The WLAN AN initiates an authentication procedure towards the 3GPP network by sending to 3GPP AAA Proxy either: + - a) "Access\_Request" message; + - b) "Diameter\_EAP\_Request" message. + +The 3GPP AAA Proxy then sends to the 3GPP AAA Server either: + +- a) "Access\_Request" message; +- b) "Diameter\_EAP\_Request" message. + +Both messages carry encapsulated EAP Response/Identity message to the 3GPP AAA Server. The message also carries a Session-ID used to identify the session within the WLAN AN. + +2. The "Access\_Request" message sent by the 3GPP AAA Proxy is generated due to the proxying by the 3GPP AAA Proxy of the "Access\_Request" message originated in WLAN AN. The "Diameter\_EAP\_Request" message sent by 3GPP AAA Proxyis generated in the following two way: + - a) Conversion by the 3GPP AAA Proxy "Translator Agent" from the RADIUS "Access\_Request" to "Diameter\_EAP\_Message"; + - b) Proxying by the 3GPP AAA Proxy of the "Diameter\_EAP\_Message" originated in WLAN AN. + +3. The 3GPP AAA Server performs the authentication procedure based on information retrieved from HSS/HLR. The 3GPP AAA Server sends to the 3GPP AAA Proxy either the message "Access\_Challenge" if it received an "Access\_Request" message or an "Diameter\_EAP\_Answer" message if it received a "Diameter\_EAP\_Message". Both of these messages carry an encapsulated "EAP Request message". The content of the "EAP Request message" is dependent on the EAP type being used. +4. 3GPP AAA Proxy performs one of the following two different procedures: + - a) Converts the "Diameter\_EAP\_Answer" message to "Access\_Accept Message" by use of the RADIUS/Diameter "Translator Agent" and sends the "Access\_Accept" to the WLAN AN; + - b) Proxies the "Access\_Challenge" or "Diameter\_EAP\_Answer" message to the WLAN AN. + +The WLAN-AN then conveys the EAP Request message to the WLAN-UE. + +5. The WLAN-UE responds to the WLAN AN by an EAP Response message. The WLAN AN encapsulates it into either: + - a) "Access\_Request message" and sends it to 3GPP AAA Proxy; + - b) "Diameter\_EAP\_Request" message and sends it to 3GPP AAA Proxy. +6. The 3GPP AAA Proxy then performs one of following two procedures: + - a) Converts the "Access\_Request" to the "Diameter\_EAP\_Request" message by using the RADIUS/Diameter "Translator Agent" and sending one to the 3GPP AAA Server; + - b) Proxies the "Access\_Request" message or "Diameter\_EAP\_Request" message to 3GPP AAA Server. + +The contents of the EAP Response message are dependent on the EAP type being used. + +The number of roundtrip Diameter signalling exchanges similar to the signals 3 to 6 is dependent e.g. on the EAP type being used. + +2N. When the 3GPP AAA server has successfully authenticated the 3GPP subscriber, the 3GPP AAA Server sends to the 3GPP AAA Proxy either an "Access\_Accept" message, if it received an "Access\_Request" or a "Diameter\_EAP\_Answer" message, if it received a "Diameter\_EAP\_Request". Both messages carry an encapsulated EAP Success message. + +2N+1. The 3GPP AAA Proxy then acts in one of two ways: + +- a) Conversion of the "Diameter\_EAP\_Answer" message to "Access\_Accept" by the "Translator Agent" and sending one to the WLAN AN. +- b) Proxy the "Access\_Accept" or "Diameter\_EAP\_Answer" message to the WLAN AN. + +The WLAN AN then forwards the EAP Success message to the WLAN-UE. + +This "Diameter\_EAP\_Answer" message also carries the authorization information (e.g. NAS Filter Rule or Tunnelling attributes) for the authenticated session. The message also carries the keying material from the 3GPP AAA Server to the WLAN AN to be used for the authenticated session by WLAN AN. + +## A.2 Immediate Purging of a WLAN User from the WLAN Access Network + +The purpose of this signalling sequence is to indicate to the WLAN AN that a specific WLAN-UE needs to be disconnected from accessing the WLAN interworking service. + +This signalling sequence is initiated by the 3GPP AAA Server when a WLAN-UE needs to be disconnected from accessing the WLAN interworking service. For example, a WLAN-UE used by a 3GPP subscriber may need to be disconnected when the 3GPP subscriber's subscription is cancelled or when the 3GPP subscribers' online charging account expires. + +The signalling sequences shown are based on RADIUS and Diameter, as specified in clauses 4 and 5. For more information on proxying and protocol translation associated with RADIUS and Diameter between the Wa and Wd reference points see subclause 5.3. + +The 3GPP AAA Proxy/Server manipulates the Root/Decorated/Alternative NAI as defined in 3GPP TS 23.003 [22]. + +![Sequence diagram showing the message flow for User Purging. The diagram involves four main entities: WLAN, 3GPP AAA Proxy, 3GPP AAA, and HSS. The process starts with a message 'A UE needs to be disconnected' from 3GPP AAA to 3GPP AAA Proxy. The 3GPP AAA Proxy then sends a 'Wd: Diameter_Abort_Session_Request' to the 3GPP AAA. The 3GPP AAA translates this to a 'Wa: Disconnect_Request' via a RADIUS/Diameter Translator Agent and sends it to the WLAN. The WLAN responds with a 'Wa: Disconnect_Response' back to the Translator Agent, which then translates it to a 'Wd: Diameter_Abort_Session_Answer' for the 3GPP AAA. Finally, the 3GPP AAA sends a 'Wx: Diameter_Disconnection_Notification_Request' to the HSS, which responds with a 'Wx: Diameter_Disconnection_Notification_Answer'.](02dfdcd208dbdc8fa4f645885e59dd17_img.jpg) + +``` +sequenceDiagram + participant WLAN + participant 3GPP_AAA_Proxy as 3GPP AAA Proxy + participant 3GPP_AAA as 3GPP AAA + participant HSS + Note right of 3GPP_AAA: A UE needs to be disconnected + 3GPP_AAA->>3GPP_AAA_Proxy: 1. Wd: Diameter_Abort_Session_Request (Session_ID) + 3GPP_AAA_Proxy->>WLAN: 2. Wa: Disconnect_Request (Session_ID) + WLAN->>3GPP_AAA_Proxy: 3. Wa: Disconnect_Response (Session_ID) + 3GPP_AAA_Proxy->>3GPP_AAA: 4. Wd: Diameter_Abort_Session_Answer (Session_ID) + 3GPP_AAA->>HSS: 5. Wx: Diameter_Disconnection_Notification_Request (Session_ID) + HSS->>3GPP_AAA: 6. Wx: Diameter_Disconnection_Notification_Answer (Session_ID) +``` + +Sequence diagram showing the message flow for User Purging. The diagram involves four main entities: WLAN, 3GPP AAA Proxy, 3GPP AAA, and HSS. The process starts with a message 'A UE needs to be disconnected' from 3GPP AAA to 3GPP AAA Proxy. The 3GPP AAA Proxy then sends a 'Wd: Diameter\_Abort\_Session\_Request' to the 3GPP AAA. The 3GPP AAA translates this to a 'Wa: Disconnect\_Request' via a RADIUS/Diameter Translator Agent and sends it to the WLAN. The WLAN responds with a 'Wa: Disconnect\_Response' back to the Translator Agent, which then translates it to a 'Wd: Diameter\_Abort\_Session\_Answer' for the 3GPP AAA. Finally, the 3GPP AAA sends a 'Wx: Diameter\_Disconnection\_Notification\_Request' to the HSS, which responds with a 'Wx: Diameter\_Disconnection\_Notification\_Answer'. + +**Figure A.4: Wa and Wd message flow for User Purging. Case a) Wa using RADIUS and Wd using Diameter** + +![Sequence diagram for Figure A.5 showing Wa and Wd message flow for User Purging using RADIUS. Lifelines: WLAN, 3GPP AAA Proxy, 3GPP AAA, HSS. The process starts with a trigger 'A UE needs to be disconnected' at the 3GPP AAA server.](ffe0fef452a0ae9a20253c319c54e13c_img.jpg) + +``` + +sequenceDiagram + participant WLAN + participant 3GPP AAA Proxy + participant 3GPP AAA + participant HSS + Note right of 3GPP AAA: A UE needs to be disconnected + 3GPP AAA->>3GPP AAA Proxy: 1. Wd: Disconnect_Request (Session_ID) + 3GPP AAA Proxy->>WLAN: 2. Wa: Disconnect_Request (Session_ID) + WLAN->>3GPP AAA Proxy: 3. Wa: Disconnect_Response (Session_ID) + 3GPP AAA Proxy->>3GPP AAA: 4. Wd: Disconnect_Response (Session_ID) + 3GPP AAA->>HSS: 5. Wx: Diameter_Disconnection_Notification_Request (Session_ID) + HSS->>3GPP AAA: 6. Wx: Diameter_Disconnection_Notification_Answer (Session_ID) + +``` + +Sequence diagram for Figure A.5 showing Wa and Wd message flow for User Purging using RADIUS. Lifelines: WLAN, 3GPP AAA Proxy, 3GPP AAA, HSS. The process starts with a trigger 'A UE needs to be disconnected' at the 3GPP AAA server. + +Figure A.5: Wa and Wd message flow for User Purging. Case b) Wa and Wd using RADIUS + +![Sequence diagram for Figure A.6 showing Wa and Wd message flow for User Purging using Diameter. Lifelines: WLAN, 3GPP AAA Proxy, 3GPP AAA, HSS. The process starts with a trigger 'A UE needs to be disconnected' at the 3GPP AAA server.](e60c2d24a97a2855d98671d27ea43d0f_img.jpg) + +``` + +sequenceDiagram + participant WLAN + participant 3GPP AAA Proxy + participant 3GPP AAA + participant HSS + Note right of 3GPP AAA: A UE needs to be disconnected + 3GPP AAA->>3GPP AAA Proxy: 1. Wd: Diameter_Abort_Session_Request (Session ID) + 3GPP AAA Proxy->>WLAN: 2. Wa: Diameter_Abort_Session_Request (Session ID) + WLAN->>3GPP AAA Proxy: 3. Wa: Diameter_Abort_Session_Answer (Session_ID) + 3GPP AAA Proxy->>3GPP AAA: 4. Wd: Diameter_Abort_Session_Answer (Session_ID) + 3GPP AAA->>HSS: 5. Wx: Diameter_Disconnection_Notification_Request (Session_ID) + HSS->>3GPP AAA: 6. Wx: Diameter_Disconnection_Notification_Answer (Session_ID) + +``` + +Sequence diagram for Figure A.6 showing Wa and Wd message flow for User Purging using Diameter. Lifelines: WLAN, 3GPP AAA Proxy, 3GPP AAA, HSS. The process starts with a trigger 'A UE needs to be disconnected' at the 3GPP AAA server. + +Figure A.6: Wa and Wd message flow for User Purging. Case c) Wa and Wd using Diameter + +1. When the 3GPP AAA Server needs to disconnect (e.g. after receiving an external trigger) a 3GPP subscriber from the WLANAN, the 3GPP AAA Server sends to the 3GPP AAA Proxy either: + +- a) "Disconnect\_Request" message; +- b) "Diameter\_Abort\_Session\_Request" message. + +Both messages carry a Session-ID used to identify the session within the WLAN AN. + +- 2. The 3GPP AAA Proxy then performs one of the following two procedures: + +- a) Converts the "Diameter\_Abort\_Session\_Request" message to "Disconnect\_Request" by use of the "RADIUS/Diameter Translator Agent" and sends this "Disconnect\_Request" message to the WLAN AN; +- b) Proxies the "Disconnect\_Request" or "Diameter\_Abort\_Session\_Request" message to the WLAN AN. + +- 3. The WLAN AN responds to the 3GPP AAA Server via the 3GPP AAA Proxy with either: + +- a) "Disconnect\_Response" message; +- b) "Diameter\_Abort\_Session\_Answer" message. + +Both messages carry the Session-ID received in the request message. + +- 4. The 3GPP AAA Proxy then performs one of the following two procedures: + +- a) Converts the "Disconnect\_Response" message to a "Diameter\_Abort\_Session\_Answer" message by use of the "RADIUS/Diameter Translator Agent" and sends this "Diameter\_Abort\_Session\_Answer" message to the 3GPP AAA Server; +- b) Proxies the "Disconnect\_Response" or "Diameter\_Abort\_Session\_Answer" message to the 3GPP AAA Server. + +- 5. The 3GPP AAA Proxy then informs the HSS about a user de-registration (ADMINISTRATIVE\_REASON) when an on-line charging failure occurred, only in the case that the 3GPP AAA Server disconnects all tunnels for that user. + +# --- Annex B (Informative): Network configuration information + +This Annex describes how an operator may configure its network in order to avoid problems associated with 3GPP AAA Server Redirect for the case where the Wa / Wd interfaces are implemented with RADIUS. + +NOTE: Since Diameter provides redirect functionality, no such problems exist once Diameter is adopted on these interfaces. + +Four problem cases have been identified: + +1. WLAN UE makes a WLAN Direct IP connection via a given WLAN AN, which is directed to a given 3GPP AAA Server. This is subsequently followed by e.g. a (re)authentication by the WLAN UE from the same WLAN AN. This is redirected to a different 3GPP AAA Server. +2. WLAN UE makes a WLAN Direct IP connection via a given WLAN AN, which is directed to a given 3GPP AAA Server. The WLAN UE then goes out of coverage and then tries to reconnect for WLAN Direct IP Access to a different WLAN AN. This is directed to a different 3GPP AAA Server. +3. WLAN UE makes a WLAN Direct IP connection via a given WLAN AN, which is directed to a given 3GPP AAA Server via a VPLMN. The WLAN UE then tries to activate a WLAN 3GPP IP Access to a PDG in the VPLMN. The Wm signalling is then proxied across the Wd interface by the 3GPP AAA Proxy to a different 3GPP AAA Server than that to which the user is registered for WLAN Direct IP access. +4. WLAN UE activates a WLAN 3GPP IP Access to a PDG in a VPLMN without having first made a WLAN Direct IP Access connection. The associated Wm signalling will be proxied across the Wd interface by the 3GPP AAA Proxy to a given 3GPP AAA Server in the HPLMN. The WLAN UE then performs reauthentication and the Wm signalling is proxied across the Wd to a different 3GPP AAA Server than that to which the user is registered. + +In order to avoid cases (1), (3) and (4), it is recommended that the operator configures the network such that all incoming requests from a given external network are directed to the same 3GPP AAA Server + +NOTE: The external network in case (1) is the WLAN AN. In cases (3) and (4) it is the VPLMN. + +Avoidance of case (2) is more problematic, since it cannot be known a priori from which WLAN AN the new attach request will come. To avoid this case, it is recommended that the operator configures the same 3GPP AAA Server to serve all geographically close WLAN ANs. Since this mitigates rather than solves the problem entirely, it is further recommended that the reauthentication timer is set to a low value (of the order of minutes) in order to avoid any hang time associated with old Direct IP connections. + +# Annex C (informative): Change history + +| Change history | | | | | | | | | +|----------------|-------|-----------|------|-----|-------------------------------------------------------------------------------------|-------|-------|--| +| Date | TSG # | TSG Doc. | CR | Rev | Subject/Comment | Old | New | | +| 09-2004 | CN#25 | | | | Approved in CN#25 | 2.0.0 | 6.0.0 | | +| 12-2004 | CN#26 | NP-040581 | 001 | 1 | PLMN advertising and selection | 6.0.0 | 6.1.0 | | +| | | | 002 | | WLAN User Profile update | | | | +| | | | 003 | | Charging related data from 3GPP AAA Server to PDG | | | | +| | | | 004 | 1 | 3GPP WLAN IP Access parameter rename | | | | +| | | | 005 | 1 | Static Remote IP address | | | | +| | | | 006 | | Removal of "Scenario" wording | | | | +| | | | 007 | | Editorial correction on Auth-Req-Type AVP | | | | +| | | | 008 | 1 | Online charging failure report | | | | +| | | | 009 | | Rejection of Multiple WLAN connections | | | | +| | | | 010 | | Application-Ids to Wa, Wd, Wm and Wg | | | | +| | | | 012 | 2 | Wd Interface RADIUS profile clarifications | | | | +| | | | 014 | 2 | RADIUS Profile for Wa and Wd | | | | +| | | | 015 | 1 | Addition of ABNF definitions missing on Wa, Wd Wm, Wg interfaces | | | | +| | | | 016 | 1 | Access Independence for WLAN 3GPP IP access | | | | +| | | | 019 | 1 | Editorial Modifications | | | | +| | | | 021 | 1 | Clarification on the reauthorization and reauthentication procedures in Wa chapter | | | | +| | | | 021 | 1 | To replace "Permanent User ID" by "User Id" | | | | +| | | | 025 | 2 | To make VPLMN-Id Conditional in Wd interface | | | | +| | | | 026 | | Addition of calling station id in DEA. Deletion of the same from DER | | | | +| | | | 028 | 1 | Editorial Changes | | | | +| | | | 029 | | Handling of Information Element marked as (M), (C) or (O) | | | | +| 03-2005 | CN#27 | NP-050047 | 030 | 1 | Removal of material duplicating 23.234 in 29.234 | 6.1.0 | 6.2.0 | | +| | | | 031 | | Removal of Wn reference point Definition from the Stage 3 | | | | +| | | | 032 | | Wa Interface RADIUS profile corrections | | | | +| | | | 033 | | Wd Interface RADIUS profile corrections | | | | +| | | | 034 | 1 | Removal of unnecessary attributes on Wa | | | | +| | | | 035 | | Information Element corrections on Wd | | | | +| | | | 037 | 1 | Editorial corrections | | | | +| | | | 038 | 1 | Description of the RADIUS session termination procedure | | | | +| | | | 039 | 1 | WLAN Diameter AVP and result codes | | | | +| | | | 041 | 1 | WLAN Diameter AVP table and chapters coherence revision | | | | +| | | | 042 | 2 | PDG Behaviour on the Wm interface | | | | +| | | | 043 | | Editorial corrections | | | | +| | | | 047 | 1 | Wa Interface RADIUS profile Information Element corrections | | | | +| 06-2005 | CT#28 | CP-050196 | 049 | 1 | Addition of missing functionality to Wa Interface RADIUS profile | 6.2.0 | 6.3.0 | | +| | | | 050 | 1 | Addition of missing functionality to Wa Interface Diameter profile | | | | +| | | | 051 | 2 | Mandating RFC 3576 in WLAN-IW | | | | +| | | | 052 | | Removal of Reference to User Data AVP on the Wm interface | | | | +| | | | 053 | | Clean up of 29.234 | | | | +| | | | 054 | 1 | Visited Network Identifier on the Wx interface | | | | +| | | | 055 | | Reference to W-APN definition in 23.003 | | | | +| | | | 056 | 1 | Clarifications on Wa and Wd RADIUS profiles | | | | +| | | | 058 | 2 | WAG address resolution on Wg interface | | | | +| | | | 060 | 2 | Missing functionality in stage 3 | | | | +| | | | 061 | 2 | Pr Interface for Presence via I-WLAN | | | | +| | | | 062 | 2 | Limit on the number of session in WLAN 3GPP IP Access | | | | +| 09-2005 | CT#29 | CP-050303 | 064 | | Clean up of Chapters 4 & 5 | 6.3.0 | 6.4.0 | | +| | | | 065 | | Clarification of Location Management description in Section 6.3.2 | | | | +| | | | 066 | | Correction to handling of Maximum-Number-Accesses description | | | | +| | | | 067 | 2 | Clarifications to multiple sessions on the Wm interface | | | | +| | | | 068 | 2 | Correction to the utilization of the list of authorized visited network identifiers | | | | +| | | | 070 | 1 | Adding ABNF for STA command | | | | +| | | | 071 | 1 | Update references for EAP lower layer attributes | | | | +| | | | 072 | | IMSI handling at the PDG | | | | +| 12-2005 | CT#30 | CP-050610 | 0073 | 1 | Update of IETF references | 6.4.0 | 6.5.0 | | +| | | | 0074 | 1 | IETF references update | | | | +| | | | 0077 | 1 | Updating the Routing Policy | | | | +| 12-2005 | CT#30 | | | | Rel-7 version was created because of ETSI TISPAN references. | 6.5.0 | 7.0.0 | | +| 03-2006 | CT#31 | CP-060073 | 0080 | | Adding definition of Maximum-Number-Accesses AVP and some other corrections | 7.0.0 | 7.1.0 | | + +| | | | | | | | | +|---------|-------|-----------|------|---|-------------------------------------------------------------------------------|--------|--------| +| | | | 0082 | | Transfer of Max-Requested-Bandwidth AVP over Wx reference point | | | +| | | | 0084 | 1 | IETF references update | | | +| | | | 0086 | | Correction to Max-Requested-Bandwidth description in 29.234 | | | +| | | | 0088 | 1 | Correction to procedure for handling of Authorization Request in Wm interface | | | +| 06-2006 | CT#32 | CP-060309 | 0090 | 1 | IETF References Update for RADIUS Filter Rules | 7.1.0 | 7.2.0 | +| | | | 0092 | 2 | Charging Identity Correction | | | +| | | | 0094 | 1 | Diameter AVP naming correction | | | +| | | | 0101 | 1 | The corrections to the usage of Master Session Key | | | +| | | | 0103 | 1 | Handling of Redirects at 3GPP AAA Servers supporting only RADIUS on Wa/Wd | | | +| 09-2006 | CT#33 | CP-060406 | 0108 | | Removal of editor's note about Pr ref. point | 7.2.0 | 7.3.0 | +| 12-2006 | CT#34 | CP-060557 | 0110 | 2 | Charging identifier exchange between 3GPP AAA Server and PDG | 7.3.0 | 7.4.0 | +| | | | 0115 | | Correction to Charging Data handling over the Wx interface | | | +| | | | 0117 | 1 | Correction to the Charging-Nodes AVP of the Wx interface | | | +| | | | 0119 | | The storing of 3GPP AAA server name and User Status handling | | | +| | | | 0122 | 1 | IETF update on filtering | | | +| | | | 0124 | 1 | IETF update on location information | | | +| | | | 0126 | 1 | Identity usage correction on Wm | | | +| | | | 0113 | 1 | Correct the Access and service Authorization information update procedure | | | +| | | | 0120 | 2 | Modification of Wa interface to support emergency call case | | | +| | | | 0127 | 2 | Modification of Wm interface to support emergency call case | | | +| 03-2007 | CT#35 | CP-070012 | 0130 | | Correction on location information on RADIUS Wd | 7.4.0 | 7.5.0 | +| | | CP-070023 | 0132 | 1 | Operator Determined Barring for I-WLAN | | | +| | | CP-070024 | 0133 | 3 | QoS parameters definition and delivery | | | +| 06-2007 | CT#36 | CP-070311 | 0134 | 1 | IETF References Update | 7.5.0 | 7.6.0 | +| 09-2007 | CT#37 | CP-070526 | 0136 | - | Correction of the PPR/PPA behavior | 7.6.0 | 7.7.0 | +| 12-2007 | CT#38 | CP-070747 | 0137 | - | QoS attributes correction | 7.7.0 | 7.8.0 | +| 06-2008 | CT#40 | CP-080266 | 0139 | - | Correction of Server Assignment Type | 7.8.0 | 7.9.0 | +| 12-2008 | CT#42 | | | | Upgraded unchanged from Rel-7 | 7.9.0 | 8.0.0 | +| 03-2009 | CT#43 | CP-090037 | 0141 | 2 | User to HSS resolution | 8.0.0 | 8.1.0 | +| | | | 0140 | 1 | Correction to section Wm description | | | +| 12-2009 | CT#46 | CP-090759 | 0146 | - | IETF RFC 5580 Alignment | 8.1.0 | 8.2.0 | +| 12-2009 | CT#46 | | | | Upgraded unchanged from Rel-8 | 8.2.0 | 9.0.0 | +| 03-2010 | CT#47 | CP-100016 | 0148 | - | NAI decoration and realm-based routing clarifications | 9.0.0 | 9.1.0 | +| 2011-03 | - | - | - | - | Update to Rel-10 version (MCC) | 9.1.0 | 10.0.0 | +| 06-2011 | CT#52 | CP-110347 | 0161 | 1 | Clean up QSPEC references | 10.0.0 | 10.1.0 | +| 06-2011 | CT#52 | CP-110346 | 0162 | 1 | Alignment of AVP Codes | 10.0.0 | 10.1.0 | +| 06-2011 | CT#52 | CP-110346 | 0163 | 1 | Missing 3GPP-AAA-Server-Name AVP in MAA | 10.0.0 | 10.1.0 | +| 09-2011 | CT#53 | CP-110570 | 0172 | 2 | IMS Emergency Calls for UICC-less WLAN UE | 10.1.0 | 10.2.0 | +| 09-2012 | - | - | - | - | Update to Rel-11 version (MCC) | 10.2.0 | 11.0.0 | +| 11-2012 | | | | | Change history table corrected | 11.0.0 | 11.0.1 | +| 12-2012 | CT#58 | CP-120709 | 0178 | - | RADIUS Attributes Alignment | 11.0.1 | 11.1.0 | +| 06-2013 | CT#60 | CP-130277 | 0179 | 3 | Support of RFC 5080 | 11.1.0 | 11.2.0 | \ No newline at end of file diff --git a/marked/Rel-11/29_series/29235/030c758fd425016b03290c8f11bef69d_img.jpg b/marked/Rel-11/29_series/29235/030c758fd425016b03290c8f11bef69d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..46198633fdcec9241b8051c02b4793ed3f68ec4a --- /dev/null +++ b/marked/Rel-11/29_series/29235/030c758fd425016b03290c8f11bef69d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fb57b7bc0c632a2be8a52eb0ad58ef7ff3ee4f90cb79f39c54ff5ceddad76983 +size 74548 diff --git a/marked/Rel-11/29_series/29235/08e8bbb2a063a3935a0c649b39ade125_img.jpg b/marked/Rel-11/29_series/29235/08e8bbb2a063a3935a0c649b39ade125_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4f6e59eb0398d8d8c3be5a3e7b5985a002f3c425 --- /dev/null +++ b/marked/Rel-11/29_series/29235/08e8bbb2a063a3935a0c649b39ade125_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f16654676b29d83d1a8c653a297a23ed26fc9071c920fad489132373a444c713 +size 47296 diff --git a/marked/Rel-11/29_series/29235/132cff7e872feb31f629703959beddd7_img.jpg b/marked/Rel-11/29_series/29235/132cff7e872feb31f629703959beddd7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3335f9a4b1642c289add6b7c7e2fa8a906bd58df --- /dev/null +++ b/marked/Rel-11/29_series/29235/132cff7e872feb31f629703959beddd7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:dc42948a9c33bec5705104f152862993e31a6657c920d4f0df9190b0219fa172 +size 27002 diff --git a/marked/Rel-11/29_series/29235/205c14458d7f4e2d22c75354bb451e99_img.jpg b/marked/Rel-11/29_series/29235/205c14458d7f4e2d22c75354bb451e99_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..495c6434738a13be365781ffc898edeb9273d53e --- /dev/null +++ b/marked/Rel-11/29_series/29235/205c14458d7f4e2d22c75354bb451e99_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2bc067ec63db706f10d7683c188194ebd3453012cb952059e02bc607b33c6393 +size 19875 diff --git a/marked/Rel-11/29_series/29235/3198cdf0dbe501c46fe0e4073c7d8451_img.jpg b/marked/Rel-11/29_series/29235/3198cdf0dbe501c46fe0e4073c7d8451_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..de30722ecb8f4b4cd0782a8bec300b5f585a833b --- /dev/null +++ b/marked/Rel-11/29_series/29235/3198cdf0dbe501c46fe0e4073c7d8451_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8fb105a73206625274b4b7ba094a870437cf4b1111cfaa07bc838fd742071062 +size 136043 diff --git a/marked/Rel-11/29_series/29235/32ff77da4286b58c4778033acaa10836_img.jpg b/marked/Rel-11/29_series/29235/32ff77da4286b58c4778033acaa10836_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ba1d3dcea77d3da20fc52a0ef3bf6c018e2b07d6 --- /dev/null +++ b/marked/Rel-11/29_series/29235/32ff77da4286b58c4778033acaa10836_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:daf1714ef521d6f38f6fabcea3e546656e07b0e87b90e040f19aec356a52cca9 +size 53462 diff --git a/marked/Rel-11/29_series/29235/3337af75dfee8af7687b4f49914d6c93_img.jpg b/marked/Rel-11/29_series/29235/3337af75dfee8af7687b4f49914d6c93_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..803726c51b52b0622f553a525f92d3cf2f1a216a --- /dev/null +++ b/marked/Rel-11/29_series/29235/3337af75dfee8af7687b4f49914d6c93_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7c1dc7f20fc8c0b395fd70224f545c8b3fe0c8fca24e8c655895e29247c98d92 +size 77999 diff --git a/marked/Rel-11/29_series/29235/3ad00ce93ad9dea9ee0f47535e5355e6_img.jpg b/marked/Rel-11/29_series/29235/3ad00ce93ad9dea9ee0f47535e5355e6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6580096e414036f14826c667b211f5a121a2a23b --- /dev/null +++ b/marked/Rel-11/29_series/29235/3ad00ce93ad9dea9ee0f47535e5355e6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4a15b7e63558e49ab982f20403955d7ac6ad65d0344352037cbc06987f9ee20e +size 72776 diff --git a/marked/Rel-11/29_series/29235/3c04b14104f95eb8f7100f6d497d956e_img.jpg b/marked/Rel-11/29_series/29235/3c04b14104f95eb8f7100f6d497d956e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ea4d6628c9e666999cb32f5a81eae0b0436a4667 --- /dev/null +++ b/marked/Rel-11/29_series/29235/3c04b14104f95eb8f7100f6d497d956e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:af4fb263c6e7d4a0b267828af39841dbf0b415b778e5f4b5dce0b8c2426b38e0 +size 165293 diff --git a/marked/Rel-11/29_series/29235/3e2dcee303cecdd31b7f9ec0d8942fed_img.jpg b/marked/Rel-11/29_series/29235/3e2dcee303cecdd31b7f9ec0d8942fed_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fca9644aaf6783cde92a97d96f5d9d9d3845a132 --- /dev/null +++ b/marked/Rel-11/29_series/29235/3e2dcee303cecdd31b7f9ec0d8942fed_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d2cbd278f3f5f03ef2546b31406bde6dd43f48fc1f16b68fd57a36bb5f6adf41 +size 43440 diff --git a/marked/Rel-11/29_series/29235/408c4798ea60469e0728a7cbbd598668_img.jpg b/marked/Rel-11/29_series/29235/408c4798ea60469e0728a7cbbd598668_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7b2e2eaf76c954eeb94c9d7b2b6706ba603773ad --- /dev/null +++ b/marked/Rel-11/29_series/29235/408c4798ea60469e0728a7cbbd598668_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2387520dcc8204cf467aee5e2fa25c834b92960a7738fd5f84eb43a674fabf7e +size 156563 diff --git a/marked/Rel-11/29_series/29235/65e8c0628536d6d4245e9ab46ba070c3_img.jpg b/marked/Rel-11/29_series/29235/65e8c0628536d6d4245e9ab46ba070c3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..185cf5ddff9feda9646de2167492712c815ea135 --- /dev/null +++ b/marked/Rel-11/29_series/29235/65e8c0628536d6d4245e9ab46ba070c3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3f4dec4190222922ebd9341fd7185ea56a061dc6d92d31e8b0c6bb031c38f80d +size 187678 diff --git a/marked/Rel-11/29_series/29235/6d442ab678ed52045444b3ccd4c0ac9e_img.jpg b/marked/Rel-11/29_series/29235/6d442ab678ed52045444b3ccd4c0ac9e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..92b82502eb4bc7e085059436f83e5a5f212cb8a7 --- /dev/null +++ b/marked/Rel-11/29_series/29235/6d442ab678ed52045444b3ccd4c0ac9e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d7d2ebb59c2aa5ee988cb700d6b7e1c21b06635f39552bbde25fb48ea0edd312 +size 26091 diff --git a/marked/Rel-11/29_series/29235/719ef0f734259484038b2434e5dc3f24_img.jpg b/marked/Rel-11/29_series/29235/719ef0f734259484038b2434e5dc3f24_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6611839166bf78df660d0c61df2dd5ae79bd4f08 --- /dev/null +++ b/marked/Rel-11/29_series/29235/719ef0f734259484038b2434e5dc3f24_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c9512f94824b970a332749e642a246af3b7eb70c40fe8ca92631a4d1ba903c2c +size 29571 diff --git a/marked/Rel-11/29_series/29235/7ed5d5770331f31ade15439a21c31425_img.jpg b/marked/Rel-11/29_series/29235/7ed5d5770331f31ade15439a21c31425_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1d7a38f80bf3530083762ff81e5cddec03fe4849 --- /dev/null +++ b/marked/Rel-11/29_series/29235/7ed5d5770331f31ade15439a21c31425_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:51c93c58e90dde5f69e34920e3b288687c7463862c7b60b07ef032014da672e2 +size 97181 diff --git a/marked/Rel-11/29_series/29235/836b0790cef5469a167fa8931df4e408_img.jpg b/marked/Rel-11/29_series/29235/836b0790cef5469a167fa8931df4e408_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2ba9ba2b35c36316992584184534ae9dc1966f16 --- /dev/null +++ b/marked/Rel-11/29_series/29235/836b0790cef5469a167fa8931df4e408_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5f8444576189d7800fd37e24aa4764d8ffcda4c38582b7291ab7dddc4590d0b5 +size 28040 diff --git a/marked/Rel-11/29_series/29235/8e80de0cac529b2c3775d677c5203133_img.jpg b/marked/Rel-11/29_series/29235/8e80de0cac529b2c3775d677c5203133_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..25cdb827d3a0f36736b1deebc856a094e8b686c4 --- /dev/null +++ b/marked/Rel-11/29_series/29235/8e80de0cac529b2c3775d677c5203133_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6938943fdf4548e0657a93a29b42dbc9b82e0b7e0abff4c8012f1782715aa4af +size 26985 diff --git a/marked/Rel-11/29_series/29235/90ddb84c323b956e2d50a54d3f870566_img.jpg b/marked/Rel-11/29_series/29235/90ddb84c323b956e2d50a54d3f870566_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1ccad7929ce3798b790b22f2cd0539cb437d435c --- /dev/null +++ b/marked/Rel-11/29_series/29235/90ddb84c323b956e2d50a54d3f870566_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b34af2cbbb2b4cc034a5d359503ca9446bb29576a7d3d4c91652f0937a0e5ed7 +size 199937 diff --git a/marked/Rel-11/29_series/29235/9b1ec0090070bdf52ea28763b8d52477_img.jpg b/marked/Rel-11/29_series/29235/9b1ec0090070bdf52ea28763b8d52477_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..35fdc6614c94696e7399737581a90569391632e9 --- /dev/null +++ b/marked/Rel-11/29_series/29235/9b1ec0090070bdf52ea28763b8d52477_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3e5bbb032e353b96c1454c93a13ac545f8dff80879bed76249a4f98e70d3c448 +size 176172 diff --git a/marked/Rel-11/29_series/29235/9c1d3678db4a12d5864cb2a4def1135d_img.jpg b/marked/Rel-11/29_series/29235/9c1d3678db4a12d5864cb2a4def1135d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2c72d4a098f4770c072dc571daded8c8e3275726 --- /dev/null +++ b/marked/Rel-11/29_series/29235/9c1d3678db4a12d5864cb2a4def1135d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f70fbb64abf49ce2b71dbb919167bb9c413ba9cb6c2b002e68c59c458fa00045 +size 197546 diff --git a/marked/Rel-11/29_series/29235/a4bfa2343d75076b79f7e33d93915e00_img.jpg b/marked/Rel-11/29_series/29235/a4bfa2343d75076b79f7e33d93915e00_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..17818ff52443d36a73cb562c45e4c56e15043818 --- /dev/null +++ b/marked/Rel-11/29_series/29235/a4bfa2343d75076b79f7e33d93915e00_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c9e1582e0af59749098159a7debb62f6e793a197c501a9f9b1e55fc851082b81 +size 157185 diff --git a/marked/Rel-11/29_series/29235/ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg b/marked/Rel-11/29_series/29235/ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..55650e4662665d0fd5fc9a839b25c91d6a0924f1 --- /dev/null +++ b/marked/Rel-11/29_series/29235/ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8a7d6259c77d380b6db0efdbade6119fd17f871429b193e3ba38adefef48d5d4 +size 174803 diff --git a/marked/Rel-11/29_series/29235/b6ad8b32179842fca5ad086cf22b03eb_img.jpg b/marked/Rel-11/29_series/29235/b6ad8b32179842fca5ad086cf22b03eb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..40a25db1c7234af59b5d361a12df00b95eaae227 --- /dev/null +++ b/marked/Rel-11/29_series/29235/b6ad8b32179842fca5ad086cf22b03eb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:09d5972f7963a2becdfdebf79aac3c5228bcebf89edb95d9eb73b499153c9ca7 +size 55592 diff --git a/marked/Rel-11/29_series/29235/d074df4244ecf1bcd74fc55886a902f9_img.jpg b/marked/Rel-11/29_series/29235/d074df4244ecf1bcd74fc55886a902f9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bdb7ea980bcb8c657563f771b0e52985ded1fedf --- /dev/null +++ b/marked/Rel-11/29_series/29235/d074df4244ecf1bcd74fc55886a902f9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7844f61cc8fe7322b288a6cd9e34166783995e124d5469e6de65aa21fb836569 +size 17260 diff --git a/marked/Rel-11/29_series/29235/d8698aacaeead6dfed9a1e448670a2e4_img.jpg b/marked/Rel-11/29_series/29235/d8698aacaeead6dfed9a1e448670a2e4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0554cb082034d71b366e5c9a1204a4afbaf12c97 --- /dev/null +++ b/marked/Rel-11/29_series/29235/d8698aacaeead6dfed9a1e448670a2e4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:73d4ee66bfa650ae3ed6a9fcb3b17b27f97251332708664e4a5b5b6e6fc580e7 +size 38685 diff --git a/marked/Rel-11/29_series/29235/dbbc0baac7341cda76cc4f8355dce23f_img.jpg b/marked/Rel-11/29_series/29235/dbbc0baac7341cda76cc4f8355dce23f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..12568c877fcd1d9c7b5e7061a2cc32ad5cb45899 --- /dev/null +++ b/marked/Rel-11/29_series/29235/dbbc0baac7341cda76cc4f8355dce23f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ac422ec9cc6e490ec63159860c6ac164a108eb26b0ca3b3fce9afa658f487b7e +size 54844 diff --git a/marked/Rel-11/29_series/29235/dd5771673aececa53d42ece89218299d_img.jpg b/marked/Rel-11/29_series/29235/dd5771673aececa53d42ece89218299d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a0c6f1e420b2429cb09d98118fc995479af54bca --- /dev/null +++ b/marked/Rel-11/29_series/29235/dd5771673aececa53d42ece89218299d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fb27790d0e053c545c10b394d1ea0cbee160c962db0354348f8f1d487372b941 +size 183376 diff --git a/marked/Rel-11/29_series/29235/ddee3e67e0dfc22e25188fa635a19558_img.jpg b/marked/Rel-11/29_series/29235/ddee3e67e0dfc22e25188fa635a19558_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9acd3307cc2294de1f352c704956110a0106aac4 --- /dev/null +++ b/marked/Rel-11/29_series/29235/ddee3e67e0dfc22e25188fa635a19558_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:05f0b9a020f15447140f6fe83b34546b25ba0a0a0be393b935cd274cdccf9103 +size 69408 diff --git a/marked/Rel-11/29_series/29235/e05b36c0d46549e681ce6581422c66b2_img.jpg b/marked/Rel-11/29_series/29235/e05b36c0d46549e681ce6581422c66b2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5fafbadd46c36ef636518ad3074abb2c0b6ae6d4 --- /dev/null +++ b/marked/Rel-11/29_series/29235/e05b36c0d46549e681ce6581422c66b2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:41682469104402ffcce2667209844f9ff839324bafb1425c01b25ec7b37f36a5 +size 178791 diff --git a/marked/Rel-11/29_series/29235/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg b/marked/Rel-11/29_series/29235/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f00eeb7caf0270647fcc6d767829372847d74d8b --- /dev/null +++ b/marked/Rel-11/29_series/29235/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fc2ba915417749a1081382500c937c61a7ec1dcba643032a9286c39a2c349158 +size 35102 diff --git a/marked/Rel-11/29_series/29235/e5ded42f8e352da02ee86cb55550c45d_img.jpg b/marked/Rel-11/29_series/29235/e5ded42f8e352da02ee86cb55550c45d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e29ff1c08ca313a4b512785094a87c1197703535 --- /dev/null +++ b/marked/Rel-11/29_series/29235/e5ded42f8e352da02ee86cb55550c45d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a656ec0a965cc422ca86845fb3b3c348a278df13285814c402da37d85d9d4040 +size 18674 diff --git a/marked/Rel-11/29_series/29235/eb1a67ebd688e354edaacb7ec2abf5ad_img.jpg b/marked/Rel-11/29_series/29235/eb1a67ebd688e354edaacb7ec2abf5ad_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..63e77855b99df6574a4594c12a935b4b2a0731ad --- /dev/null +++ b/marked/Rel-11/29_series/29235/eb1a67ebd688e354edaacb7ec2abf5ad_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6dc7f4db5b24fac690570e5e1206848ff842327b9a91e5d655ae2a8819992695 +size 31101 diff --git a/marked/Rel-11/29_series/29235/ec31af936fa94a6917bf19f154df8ac3_img.jpg b/marked/Rel-11/29_series/29235/ec31af936fa94a6917bf19f154df8ac3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..00d655c4668fee04e915debe29e3e9b5136f92c9 --- /dev/null +++ b/marked/Rel-11/29_series/29235/ec31af936fa94a6917bf19f154df8ac3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f1e0fa76a5f2cf9a1df457b1ebc6f60d5979f0d8a4dba7d629727788d952f18e +size 42072 diff --git a/marked/Rel-11/29_series/29235/f468e577645d646f5157ce3eefb4ed96_img.jpg b/marked/Rel-11/29_series/29235/f468e577645d646f5157ce3eefb4ed96_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..815bc44eec0f74eac3a1705da058285248e31fa8 --- /dev/null +++ b/marked/Rel-11/29_series/29235/f468e577645d646f5157ce3eefb4ed96_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8535f57de6ca083e22cd066e63c49e408806dfa2ed0773a6a7da63cd965b4d8b +size 54716 diff --git a/marked/Rel-11/29_series/29235/raw.md b/marked/Rel-11/29_series/29235/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..8d3b2fd26003907b248e2a5e8ce86349e1ecf40b --- /dev/null +++ b/marked/Rel-11/29_series/29235/raw.md @@ -0,0 +1,3739 @@ + + + + + + +# Contents + +| | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------|----| +| Foreword ..... | 9 | +| 1 Scope..... | 10 | +| 2 References..... | 10 | +| 3 Definitions, symbols and abbreviations ..... | 12 | +| 3.1 Definitions..... | 12 | +| 3.2 Abbreviations ..... | 12 | +| 4 Interworking between a SIP-I based circuit-switched core network and an external SIP-I based network..... | 13 | +| 4.1 Reference Model ..... | 13 | +| 4.2 Signalling Interworking of a Call from the external SIP-I based network towards the SIP-I based circuit-switched core network..... | 14 | +| 4.2.1 Interworking of SIP-I messages received from external SIP-I network..... | 14 | +| 4.2.1.1 General..... | 14 | +| 4.2.1.2 Call Release from external SIP-I network when encapsulated REL is missing ..... | 14 | +| 4.2.2 Special Procedures for the reception of initial SIP INVITE requests ..... | 14 | +| 4.2.2.1 Receipt of SIP INVITE request ..... | 14 | +| 4.2.2.2 Receipt of SIP INVITE requests with SDP ..... | 15 | +| 4.2.2.3 Receipt of SIP INVITE request without SDP..... | 15 | +| 4.2.2.4 MGW Selection ..... | 15 | +| 4.2.3 Interworking of SIP-I messages received from succeeding 3GPP node ..... | 15 | +| 4.2.4 Special Procedures for Profile Interworking ..... | 15 | +| 4.2.4.1 Support of 100Rel..... | 15 | +| 4.2.4.2 Support for UPDATE method ..... | 16 | +| 4.2.4.3 Support for Preconditions ..... | 16 | +| 4.2.5 Support for Codec Negotiation..... | 16 | +| 4.2.6 Special Procedures for the reception of SIP Re-INVITE requests..... | 17 | +| 4.2.6.1 Receipt of SIP Re-INVITE request without SDP ..... | 17 | +| 4.3 Signalling Interworking of a Call from SIP-I based circuit-switched core network towards the external SIP-I based network ..... | 17 | +| 4.3.1 Interworking of SIP-I messages received from preceding 3GPP node ..... | 17 | +| 4.3.1.1 General..... | 17 | +| 4.3.1.2 Call Release from external SIP-I network when encapsulated REL is missing ..... | 17 | +| 4.3.2 Special Procedures for the reception of SIP INVITE requests..... | 17 | +| 4.3.3 Special Procedures for Profile Interworking ..... | 18 | +| 4.3.3.1 Support of 100Rel..... | 18 | +| 4.3.3.2 Support for UPDATE method ..... | 18 | +| 4.3.3.3 Support for Preconditions ..... | 18 | +| 4.3.4 Support for Codec Negotiation..... | 20 | +| 4.3.5 MGW Selection ..... | 20 | +| 4.4 DMTF Signalling Interworking applicable for all Calls between an external SIP-I based network and a SIP-I based circuit-switched core network..... | 20 | +| 4.4.1 General ..... | 20 | +| 4.4.2 DTMF support in SDP offer sent to External SIP-I network ..... | 20 | +| 4.4.3 DTMF support in SDP offer received from External SIP-I network ..... | 21 | +| 4.5 User Plane Interworking..... | 22 | +| 4.5.1 General ..... | 22 | +| 4.5.2 DTMF Interworking ..... | 22 | +| 4.6 Example Call flows ..... | 23 | +| 4.6.1 General ..... | 23 | +| 4.6.2 Incoming Call flows ..... | 23 | +| 4.6.2.1 Incoming Call – no preconditions in external network..... | 23 | +| 4.6.2.2 Incoming Call with preconditions not met ..... | 25 | +| 4.6.3 Outgoing Call flows ..... | 27 | +| 4.6.3.1 Outgoing Call with support for preconditions ..... | 27 | +| 4.6.3.2 Outgoing Call with support of 100rel but no support for preconditions ..... | 29 | +| 4.6.3.3 Outgoing Call without support for 100rel and preconditions ..... | 31 | + +| | | | +|-----------|------------------------------------------------------------------------------------------------------------------------------------|----| +| 5 | Interworking between a SIP-I based circuit-switched core network and an ISUP based network..... | 33 | +| 5.1 | Reference Model ..... | 33 | +| 5.2 | Control Plane Interworking ..... | 33 | +| 5.3 | Signalling Interworking of a Call from the ISUP based network towards the SIP-I based circuit-switched core network..... | 35 | +| 5.3.1 | General ..... | 35 | +| 5.3.1.1 | Sending of ISUP information to adjacent SIP nodes ..... | 35 | +| 5.3.1.2 | Receipt of encapsulated ISUP information within SIP-I ..... | 35 | +| 5.3.1.3 | Special procedures related to outgoing INVITE..... | 36 | +| 5.3.1.3.1 | Overlap Signalling..... | 36 | +| 5.3.1.3.2 | Coding of encapsulated ISUP IAM parameters in outgoing INVITE ..... | 36 | +| 5.3.1.3.3 | Media offered in SDP of outgoing INVITE..... | 36 | +| 5.4 | Signalling Interworking of a Call from SIP-I based circuit-switched core network towards the ISUP based network..... | 36 | +| 5.4.1 | General ..... | 36 | +| 5.4.2 | Interworking of received ISUP messages to SIP messages..... | 36 | +| 5.4.3 | Interworking of received SIP messages to ISUP messages..... | 36 | +| 5.4.3.1 | Receipt of encapsulated ISUP information within SIP..... | 36 | +| 5.4.3.2 | Special Procedures for the Reception of SIP INVITE request ..... | 37 | +| 5.4.3.2.1 | Propagation of overlap signalling toward the 3GPP CS domain ..... | 37 | +| 5.4.3.2.2 | Derivation of TMR, USI and HLC parameters within sent IAM message..... | 37 | +| 5.4.3.2.3 | Receipt of SIP INVITE without SDP offer ..... | 37 | +| 5.4.3.2.4 | Special Procedures for deferred MGW selection procedure..... | 37 | +| 5.5 | Supplementary services..... | 37 | +| 5.5.1 | Special procedures for supplementary service interworking..... | 37 | +| 5.5.2 | Interworking of CLIP/CLIR supplementary service ..... | 38 | +| 5.5.3 | Interworking of Call Hold (HOLD) supplementary service..... | 38 | +| 5.5.4 | Interworking of Completion of Calls to Busy Subscriber (CCBS) supplementary service to SIP networks ..... | 38 | +| 5.6 | User Plane Interworking..... | 38 | +| 5.6.1 | General ..... | 38 | +| 5.6.2 | DTMF ..... | 38 | +| 5.7 | Example Call flows ..... | 38 | +| 6 | Interworking between a SIP-I based circuit-switched core network and a BICC based network ..... | 39 | +| 6.1 | Reference Model ..... | 39 | +| 6.2 | Control Plane Interworking ..... | 40 | +| 6.2.1 | General ..... | 40 | +| 6.2.2 | Signalling interactions between network entities in the control plane ..... | 40 | +| 6.3 | Signalling Interworking of a Call from the BICC based network towards the SIP-I based circuit-switched core network..... | 41 | +| 6.4 | Signalling Interworking of a Call from SIP-I based circuit-switched core network towards the BICC based network..... | 41 | +| 6.5 | Supplementary services..... | 41 | +| 6.6 | Codec Negotiation between a BICC based network and a SIP-I based circuit-switched core network ..... | 42 | +| 6.6.1 | General ..... | 42 | +| 6.6.2 | Codec Negotiation from SIP-I on Nc to BICC Network..... | 42 | +| 6.6.2.1 | Sending of IAM ..... | 42 | +| 6.6.2.2 | Sending of SDP Answer ..... | 42 | +| 6.6.2.3 | Mid-call Codec Negotiation initiated from SIP-I on Nc..... | 42 | +| 6.6.3 | Codec Negotiation from BICC Network to SIP-I on Nc..... | 42 | +| 6.6.3.1 | Sending of initial SDP Offer..... | 42 | +| 6.6.3.2 | Responding to Serving Node initiating Codec Negotiation..... | 42 | +| 6.6.3.3 | Mid-call Codec Negotiation initiated from BICC ..... | 43 | +| 6.7 | DTMF Signalling Interworking applicable for all Calls between a BICC network and a SIP-I based circuit-switched core network ..... | 43 | +| 6.7.1 | General ..... | 43 | +| 6.7.2 | DTMF transfer from SIP-I on Nc to BICC network (Out-of-Band DTMF) ..... | 43 | +| 6.7.3 | DTMF transfer from BICC network (Out-of-Band DTMF) to SIP-I on Nc ..... | 44 | +| 6.7.4 | SIP-I on Nc interworking with BICC for Inband DTMF ..... | 45 | +| 6.8 | User Plane Interworking..... | 45 | +| 6.8.1 | General ..... | 45 | + +| | | | +|---------|--------------------------------------------------------------------------------------------------------------------------------------------------|----| +| 6.8.2 | DTMF Interworking ..... | 45 | +| 6.9 | Example Call flows ..... | 45 | +| 7 | Interworking between a SIP-I based circuit-switched core network and the IP Multimedia (IM) Core Network (CN) Subsystem ..... | 46 | +| 7.1 | Reference Model ..... | 46 | +| 7.1.1 | General ..... | 46 | +| 7.1.2 | Signalling interactions between network entities in the control plane ..... | 46 | +| 7.2 | Signalling Interworking of a Call from the IP Multimedia Subsystem towards the SIP-I based circuit-switched core network..... | 47 | +| 7.2.1 | General ..... | 47 | +| 7.2.2 | Exceptions from forwarding received SIP messages ..... | 48 | +| 7.2.3 | Sending SIP INVITE request ..... | 48 | +| 7.2.4 | Updating Precondition Information..... | 49 | +| 7.2.5 | SDP Codec Negotiation..... | 49 | +| 7.2.6 | MGW Selection ..... | 49 | +| 7.2.7 | Autonomous Release..... | 49 | +| 7.2.8 | Further setting of SIP header values..... | 49 | +| 7.3 | Signalling Interworking of a Call from SIP-I based circuit-switched core network towards the IP Multimedia Subsystem..... | 51 | +| 7.3.1 | General ..... | 51 | +| 7.3.2 | Exceptions from forwarding received SIP messages ..... | 51 | +| 7.3.3 | Sending SIP INVITE request ..... | 52 | +| 7.3.4 | Updating Precondition Information..... | 52 | +| 7.3.5 | Receipt of SIP redirect (3xx) response ..... | 53 | +| 7.3.6 | SDP Codec Negotiation..... | 53 | +| 7.3.7 | MGW Selection ..... | 53 | +| 7.3.8 | Autonomous Release..... | 54 | +| 7.3.9 | Handling of forked SIP Responses..... | 54 | +| 7.3.9.1 | SIP Dialogues ..... | 54 | +| 7.3.9.2 | Reception of non-100 provisional Responses to initial INVITE..... | 54 | +| 7.3.9.3 | Reception of final Responses to initial INVITE..... | 54 | +| 7.3.10 | Further setting of SIP header values..... | 55 | +| 7.4 | DMTF Signalling Interworking applicable for all Calls between an IP Multimedia CN Subsystem and a SIP-I based circuit-switched core network..... | 56 | +| 7.5 | User Plane Interworking..... | 56 | +| 7.5.1 | General ..... | 56 | +| 7.5.2 | DTMF Interworking ..... | 57 | +| 7.6 | Example Call flows ..... | 57 | +| 7.6.1 | General ..... | 57 | +| 7.6.2 | Incoming Call flows ..... | 57 | +| 7.6.2.1 | Successful Call Establishment and Call Release ..... | 57 | +| 7.6.2.2 | Autonomous Release at MGCF ..... | 59 | +| 7.6.3 | Outgoing Call flows ..... | 60 | +| 7.6.3.1 | Outgoing Call, Sending of INVITE is deferred ..... | 60 | +| 7.6.3.2 | Outgoing Call, Sending of INVITE is not deferred..... | 61 | +| 7.6.3.3 | Interworking with forked SIP INVITE Requests ..... | 63 | +| 7.7 | CS CN Supplementary Services and IMS Supplementary Services ..... | 66 | +| 7.7.0 | General ..... | 66 | +| 7.7.1 | Number Identification Services ..... | 66 | +| 7.7.1.1 | CS CN Supplementary Service - Calling Line Identification Presentation/Restriction (CLIP/CLIR)..... | 66 | +| 7.7.1.2 | CS CN Supplementary Service - Connected Line Identification Presentation /Restriction (COLP/COLR)..... | 66 | +| 7.7.1.3 | IMS Supplementary Service - Originating Identification Presentation (OIP) and Originating Identification Restriction (OIR)..... | 66 | +| 7.7.1.4 | IMS Supplementary Service - Terminating Identification Presentation (TIP) and Terminating Identification Restriction (TIR) ..... | 66 | +| 7.7.1.5 | CS CN Supplementary Service – Direct Dialling In ..... | 66 | +| 7.7.1.6 | CS CN Supplementary Service – Malicious Call Identification..... | 67 | +| 7.7.1.7 | IMS Supplementary Service – Malicious Communication Identification (MCID)..... | 67 | +| 7.7.1.8 | CS CN Supplementary Service – Subaddressing ..... | 67 | + +| | | | +|----------|------------------------------------------------------------------------------------------------------------------------------------------------|----| +| 7.7.2 | Diversion Services..... | 67 | +| 7.7.2.1 | CS CN Supplementary Service - Call Forwarding Services (CFU, CFB, CFNRy, CFNRc)..... | 67 | +| 7.7.2.2 | CS CN Supplementary Service – Call Deflection (CD)..... | 67 | +| 7.7.2.3 | IMS Supplementary Service – Communication Diversion (CDIV) ..... | 67 | +| 7.7.3 | Waiting Services..... | 67 | +| 7.7.3.1 | CS CN Supplementary Service – Call Waiting ..... | 67 | +| 7.7.3.2 | IMS Supplementary Service – Communication Waiting (CW) ..... | 67 | +| 7.7.4 | Hold Services..... | 67 | +| 7.7.4.1 | CS CN Supplementary Service – Call Hold ..... | 67 | +| 7.7.4.2 | IMS Supplementary Service – Communication Hold (HOLD)..... | 68 | +| 7.7.5 | Multipart Services ..... | 68 | +| 7.7.5.1 | CS CN Supplementary Services – Conference Calling (CONF) and Three-Party (3PTY)..... | 68 | +| 7.7.5.2 | IMS Supplementary Service – Conference (CONF) ..... | 68 | +| 7.7.6 | Closed User Group Service ..... | 68 | +| 7.7.6.1 | CS CN Supplementary Service – Closed User Group (CUG)..... | 68 | +| 7.7.6.2 | IMS Supplementary Service - Closed User Group (CUG)..... | 68 | +| 7.7.7 | Charging Services..... | 68 | +| 7.7.7.1 | CS CN Supplementary Service – Advice of Charge (AoC) ..... | 68 | +| 7.7.7.2 | IMS Supplementary Service – Advice of Charge (AOC)..... | 68 | +| 7.7.7.3 | CS CN Supplementary Service – International Telecommunication Charge Card (ITCC) ..... | 68 | +| 7.7.7.4 | CS CN Supplementary Service – Reverse Charging (REV) ..... | 68 | +| 7.7.8 | Barring Services ..... | 69 | +| 7.7.8.1 | CS CN Supplementary Service - Barring of Outgoing Calls..... | 69 | +| 7.7.8.2 | CS CN Supplementary Service - Barring of Incoming Calls ..... | 69 | +| 7.7.8.3 | CS CN Supplementary Service - Anonymous Call Rejection (ACR)..... | 69 | +| 7.7.8.4 | IMS Supplementary Service – Communication Barring (CB)..... | 69 | +| 7.7.8.5 | IMS Supplementary Service – Anonymous Communication Rejection (ACR)..... | 69 | +| 7.7.9 | Transfer Services ..... | 69 | +| 7.7.9.1 | CS CN Supplementary Service – Explicit Call Transfer (ECT)..... | 69 | +| 7.7.9.2 | IMS Supplementary Service – Explicit Communication Transfer (ECT)..... | 69 | +| 7.7.10 | Call Completion Services ..... | 70 | +| 7.7.10.1 | CS CN Supplementary Service – Completion of Calls to Busy Subscriber (CCBS) ..... | 70 | +| 7.7.10.2 | CS CN Supplementary Service – Completion of Calls on No Reply (CCNR) ..... | 70 | +| 7.7.10.3 | IMS Supplementary Service – Completion of Communications to Busy Subscriber (CCBS) and
Completion of Communication on No Reply (CCNR) ..... | 70 | +| 7.7.11 | Miscellaneous Services ..... | 70 | +| 7.7.11.1 | CS CN Supplementary Service - Multi-Level Precedence and Pre-emption (MLPP) ..... | 70 | +| 7.7.11.2 | CS CN Supplementary Service - Multiple Subscriber Profile (MSP) ..... | 70 | +| 7.7.11.3 | CS CN Supplementary Service - Multicall..... | 70 | +| 7.7.11.4 | CS CN Supplementary Service - Calling Name Presentation ..... | 70 | +| 7.7.11.5 | CS CN Supplementary Service – User-to-User Signalling (UUS)..... | 70 | +| 7.7.11.6 | IMS Supplementary Service – Message Waiting Indication (MWI)..... | 70 | +| 7.7.11.7 | CS CN Supplementary Service - Global Virtual Network Service (GVNS)..... | 70 | +| 7.7.11.8 | CS CN Supplementary Service - Terminal Portability (TP)..... | 71 | +| 7.7.12 | Customized Alerting Tones Services ..... | 71 | +| 7.7.12.1 | CS CN Supplementary Service - Customized Alerting Tones (CAT)..... | 71 | +| 7.7.12.2 | IMS Supplementary Service - Customized Alerting Tones (CAT) for early session model..... | 71 | +| 7.7.12.3 | IMS Supplementary Service - Customized Alerting Tones (CAT) for forking model ..... | 71 | +| 7.7.12.4 | IMS Supplementary Service - Customized Alerting Tones (CAT) for gateway model..... | 71 | +| 7.8 | MGCF – IM-MGW Interaction..... | 71 | +| 7.8.1 | General ..... | 71 | +| 7.8.2 | Call related Procedures for Terminations towards the IM CN Subsystem..... | 71 | +| 7.8.3 | Call related Procedures for Terminations towards SIP-I based Circuit-switched Core Network ..... | 71 | +| 7.8.4 | Non-call related procedures..... | 72 | + +| | | | +|-----------------------------|-------------------------------------------------------------------------------|-----------| +| Annex A (normative): | Interconnecting functionalities in SIP-I based CS domain ..... | 72 | +| A.1 | General ..... | 72 | +| A.2 | Stage 2 Requirements..... | 72 | +| A.3 | Border Control architecture ..... | 73 | +| A.4 | Void..... | 74 | +| A.5 | Procedures at the CS-IBCF ..... | 74 | +| A.5.1 | General ..... | 74 | +| A.5.2 | CS-IBCF as an exit point ..... | 75 | +| A.5.2.1 | Initial requests ..... | 75 | +| A.5.2.2 | Subsequent requests..... | 75 | +| A.5.2.3 | CS-IBCF-initiated call release..... | 76 | +| A.5.2.4 | THIG functionality in the CS-IBCF ..... | 76 | +| A.5.2.4.1 | General..... | 76 | +| A.5.2.4.2 | Encryption for network topology hiding ..... | 76 | +| A.5.2.5 | ALG functionality in the CS-IBCF ..... | 77 | +| A.5.2.6 | Screening of SIP-I signalling..... | 77 | +| A.5.2.6.1 | General..... | 77 | +| A.5.2.6.2 | CS-IBCF procedures for SIP headers ..... | 77 | +| A.5.2.6.3 | CS-IBCF procedures for SIP message bodies ..... | 78 | +| A.5.2.7 | Void..... | 78 | +| A.5.3 | CS-IBCF as an entry point ..... | 78 | +| A.5.3.1 | Initial requests ..... | 78 | +| A.5.3.2 | Subsequent requests..... | 78 | +| A.5.3.3 | CS-IBCF-initiated call release..... | 79 | +| A.5.3.4 | THIG functionality in the CS-IBCF ..... | 79 | +| A.5.3.4.1 | General..... | 79 | +| A.5.3.4.2 | Decryption for network topology hiding ..... | 80 | +| A.5.3.5 | ALG functionality in the CS-IBCF ..... | 80 | +| A.5.3.6 | Screening of SIP-I signalling..... | 80 | +| A.5.3.7 | Void..... | 81 | +| A.6 | Procedures at the CS-TrGW ..... | 81 | +| A.6.1 | Transport Plane Control procedures..... | 81 | +| A.7 | CS-IBCF – CS-TrGW Interaction..... | 81 | +| A.7.1 | General ..... | 81 | +| A.7.1.1 | Network Model..... | 81 | +| A.7.1.2 | Signalling flows ..... | 81 | +| A.7.1.2.1 | Basic Procedures..... | 81 | +| A.7.1.2.1.1 | Call Establishment..... | 81 | +| A.7.1.2.1.2 | Call Release..... | 83 | +| A.7.1.2.2 | Specific Use Cases..... | 84 | +| A.7.1.2.2.1 | CS-IBCF as Entry Point, Call Establishment with IP Version Interworking ..... | 84 | +| A.7.1.2.2.2 | Hanging Termination Detection..... | 84 | +| A.7.1.2.2.3 | Gate Management ..... | 85 | +| A.7.1.2.2.4 | QoS Packet Marking ..... | 85 | +| A.7.1.2.2.5 | IP Realms ..... | 86 | +| A.7.1.2.2.6 | Media Inactivity Detection..... | 87 | +| A.7.1.2.2.7 | RTCP Handling..... | 87 | +| A.7.1.2.2.8 | Bandwidth Policing ..... | 88 | +| A.7.1.2.2.8.1 | Overview ..... | 88 | +| A.7.1.2.2.8.2 | Bandwidth policing procedures..... | 88 | +| A.7.1.2.2.9 | Through-Connection ..... | 89 | +| A.7.1.2.2.10 | Emergency Call..... | 89 | +| A.7.2 | Ix Signalling Procedures ..... | 90 | +| A.7.2.1 | Introduction ..... | 90 | +| A.7.2.2 | Call Related Procedures ..... | 90 | +| A.7.2.2.1 | Reserve TrGW Connection Point ..... | 90 | +| A.7.2.2.2 | Configure TrGW Connection Point..... | 93 | + +| | | | +|-------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------| +| A.7.2.2.3 | Reserve and Configure TrGW Connection Point ..... | 95 | +| A.7.2.2.4 | Release TrGW Termination..... | 98 | +| A.7.2.2.5 | IP Bearer Released..... | 98 | +| A.7.2.2.6 | Media Inactivity Detection ..... | 99 | +| A.7.2.2.7 | Termination heartbeat indication ..... | 99 | +| A.7.2.2.8 | Change Through-Connection..... | 100 | +| A.7.2.3 | Non-Call Related Procedures ..... | 100 | +| A.7.2.3.1 | Introduction..... | 100 | +| A.7.2.3.2 | Realm Availability Change - Activate..... | 101 | +| A.7.2.3.3 | Realm Availability Change - Indication ..... | 102 | +| A.8 | (G)MSC – CS-MGW Interaction..... | 102 | +| A.8.1 | General ..... | 102 | +| A.8.1.1 | Network Model..... | 102 | +| A.8.1.2 | Signalling flows ..... | 102 | +| Annex B (normative): | Additional Interworking Procedures between a SIP-I based circuit-switched Core Network and the IP Multimedia (IM) Core Network (CN) Subsystem to Support Special Services..... | 103 | +| B.1 | General..... | 103 | +| B.2 | Global Text Telephony ..... | 103 | +| Annex C (informative): | Change history..... | 103 | + +--- + +## Foreword + +This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +--- + +# 1 Scope + +The present document specifies the interworking between SIP-I based circuit-switched core network, as specified in 3GPP TS 23.231 [3] and 3GPP TS 29.231 [4], with out-of-band transcoder control related procedures in 3GPP TS 23.153 [5], and: + +- an external SIP-I based signalling network compliant to ITU-T Recommendation Q.1912.5 [6], +- an ISUP (ITU-T Recommendations Q.761 to Q.764 [7]) based network such as an ISUP based 3GPP CS Domain or a PSTN, +- a BICC (ITU-T Recommendations Q.1902.1 to Q.1902.6 [8]) based network such as an BICC based 3GPP CS Domain as specified in 3GPP TS 23.205 [9] and 3GPP TS 29.205 [10], +- an IP Multimedia Subsystem, as specified in 3GPP TS 23.228 [11] and 3GPP TS 24.229 [12]. + +--- + +# 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.231: " SIP-I based circuit-switched core network; Stage 2". +- [4] 3GPP TS 29.231: "Application of SIP-I Protocols to Circuit Switched (CS) core network architecture; Stage 3". +- [5] 3GPP TS 23.153: "Out of Band Transcoder Control; Stage 2". +- [6] ITU-T Recommendation Q.1912.5 (03/04): "Interworking between Session Initiation Protocol (SIP) and Bearer Independent Call Control Protocol or ISDN User Part". +- [7] ITU-T Recommendations Q.761 to Q.764 (12/99): "Specifications of Signalling System No.7 ISDN User Part (ISUP)". +- [8] ITU-T Recommendations Q.1902.1 to Q.1902.6 (07/01): "Bearer Independent Call Control". +- [9] 3GPP TS 23.205: "Bearer-independent circuit-switched core network; Stage 2". +- [10] 3GPP TS 29.205: "Application of Q.1900 series to Bearer Independent CS Network architecture; Stage 3". +- [11] 3GPP TS 23.228: "IP Multimedia subsystem (IMS)". +- [12] 3GPP TS 24.229: "IP Multimedia Call Control Protocol based on SIP and SDP". +- [13] 3GPP TS 29.163: "Interworking between the IP Multimedia (IM) Core Network (CN) subsystem and Circuit Switched (CS) networks". +- [14] IETF RFC 791: "Internet Protocol". +- [15] IETF RFC 768: "User Datagram Protocol". + +- [16] IETF RFC 793: "Transmission Control Protocol". +- [17] IETF RFC 2460: "Internet Protocol, Version 6 (IPv6) Specification". +- [18] IETF RFC 4960: "Stream Control Transmission Protocol". +- [19] IETF RFC 3204: "MIME media types for ISUP and QSIG Objects". +- [20] IETF RFC 3261: "SIP: Session Initiation Protocol". +- [21] IETF RFC 3262: "Reliability of Provisional Responses in the Session Initiation Protocol (SIP)". +- [22] IETF RFC 3264: "An Offer/Answer Model with the Session Description Protocol (SDP)". +- [23] IETF RFC 3312: "Integration of Resource Management and Session Initiation Protocol (SIP)". +- [24] 3GPP TS 23.014: "Support of Dual Tone Multi-Frequency (DTMF) signalling". +- [25] 3GPP TS 24.629: "Explicit Communication Transfer (ECT) using IP Multimedia (IM) Core Network (CN) subsystem". +- [26] 3GPP TS 24.610: "Communication HOLD (HOLD) using IP Multimedia (IM) Core Network (CN) subsystem". +- [27] ITU-T Recommendation Q.765 (2000): "Signalling System No. 7 – Application transport mechanism". +- [28] ITU-T Recommendation Q.765.5 (2000): "Signalling system No. 7 – Application transport mechanism: Bearer Independent Call Control (BICC)". +- [29] 3GPP TS 29.238: "Interconnection Border Control Functions – Transition Gateway; H.248 Profile; Stage 3". +- [30] IETF RFC 3263: "Session Initiation Protocol (SIP): Locating SIP Servers". +- [31] IETF RFC 4028: "Session Timers in the Session Initiation Protocol (SIP)". +- [32] IETF RFC 3325: "Private Extensions to the Session Initiation Protocol (SIP) for Asserted Identity within Trusted Networks". +- [33] ITU-T Recommendation H.248.1 (2002): "Gateway control protocol: Version 3". +- [34] Void. +- [35] Void. +- [36] IETF RFC 5079: "Rejecting Anonymous Requests in the Session Initiation Protocol (SIP)". +- [37] 3GPP TS 29.162: "Interworking between the IM CN subsystem and IP networks". +- [38] IETF RFC 3550: "RTP: A Transport Protocol for Real-Time Applications". +- [39] IETF RFC 3556: "Session Description Protocol (SDP) Bandwidth Modifiers for RTP Control Protocol (RTCP) Bandwidth". +- [40] IETF RFC 3605: "Real Time Control Protocol (RTCP) attribute in Session Description Protocol (SDP)". +- [41] IETF RFC 2474: "Definition of the Differentiated Services Field (DS Field) in the IPv4 and IPv6 Headers". +- [42] IETF RFC 2216 (1997): "Network Element Service Template". +- [43] 3GPP TS 29.414: "Core network Nb data transport and transport signalling". +- [44] 3GPP TS 32.407: "Telecommunication Management; Performance Management (PM) Performance measurements Core Network (CN) Circuit Switched (CS) domain". + +- [45] 3GPP TS 23.226: "Global Text Telephony (GTT); stage 2". +- [46] ITU-T Recommendation T.140 (02/98): "Text conversation presentation protocol". +- [47] IETF RFC 4103: "RTP Payload for Text Conversation". +- [48] ITU-T Recommendation V.18 (11/00): "Operational procedures for modems in the text telephone mode". +- [49] 3GPP TS 26.226: "Cellular text telephone modem; General description". +- [50] 3GPP TS 26.235: "Packet switched conversational multimedia applications; Default codecs". +- [51] 3GPP TS 26.236: "Packet switched conversational multimedia applications; Transport protocols". +- [52] 3GPP TS 26.114: "IP Multimedia Subsystem (IMS); Multimedia Telephony; Media handling and interaction". +- [53] ITU-T Recommendation H.248.1 (05/2002): "Gateway control protocol: Version 2" including the Corrigendum1 for Version 2 (03/04). +- [54] 3GPP TS 29.332: "Media Gateway Control Function (MGCF) – IM-Media Gateway (IM-MGW) interface, Stage 3". +- [55] 3GPP TS 29.232: "Media Gateway Controller (MGC) - Media Gateway (MGW) interface; Stage 3". + +--- + +## 3 Definitions, symbols and abbreviations + +### 3.1 Definitions + +For the purposes of the present document, the terms and definitions given in 3GPP TR 21.905 [1] and the following apply: + +**Interworking Unit (IWU):** Logical entity that interworks SIP-I signalling in the 3GPP CS Domain with any of the following signalling: (a) SIP-I signalling of an external SIP-I network, (b) ISUP signalling of a PSTN, and (c) BICC or ISUP signalling of a 3GPP CS Domain. + +**User Plane Interworking Unit (UP-IWU):** Logical entity that performs user plane interworking between the SIP-I based CS Domain and an external SIP-I network, or external ISUP network, or BICC/ISUP based 3GPP CS network. + +### 3.2 Abbreviations + +For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [1] and the following apply: An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in 3GPP TR 21.905 [1]. + +| | | +|---------|----------------------------------------------------------------------------------| +| ALG | Application Level Gateway | +| ANM | ANswer Message | +| APM | Application Transport Mechanism | +| B2BUA | (SIP) Back-to-Back User Agent | +| BGCF | Breakout Gateway Control Function | +| BICC | Bearer Independent Call Control | +| CON | Connect message | +| COT | Continuity message | +| CPG | Call ProGress message | +| CS-IBCF | CS (domain) IBCF | +| CS-TrGW | CS (domain) TrGW | +| IBCF | Interconnection Border Control Function | +| ITU-T | International Telecommunication Union – Telecommunication Standardization Sector | +| IM-MGW | IP Multimedia Media Gateway Function | +| IW-MSC | Interworking MSC | +| MIME | Multi-purpose Internet Mail Extensions | + +| | | +|--------|--------------------------------------------------------------------| +| MRFP | Multimedia Resource Function Processor | +| NA(P)T | Network Address Translation / Network Address and Port Translation | +| NNI | Network to Network Interface | +| O-MSC | Originating MSC | +| OoB | Out of Band | +| OoBTC | Out of Band Transcoder Control | +| RES | RESume | +| RLC | Release Complete | +| SCTP | Stream Control Transmission Protocol | +| SIP-I | SIP with encapsulated ISUP | +| SUS | SUSpend | +| TDM | Time-Division Multiplexing | +| THIG | Topology Hiding Internetwork Gateway | +| TMR | Transmission Medium Requirement | +| TrGW | Transition Gateway | +| UA | (SIP) User Agent | +| UP-IWU | User Plane Interworking Unit | +| USI | User Service Information | + +## 4 Interworking between a SIP-I based circuit-switched core network and an external SIP-I based network + +### 4.1 Reference Model + +Figure 4.1.1 shows the interworking reference model for the interworking between a SIP-I based circuit-switched core network and an external SIP-I based network: + +![Figure 4.1.1: interworking reference model diagram showing the connection between an External SIP-I Network and a 3GPP CS Domain via a GMSC Server, MSC Server, and MGW.](3ad00ce93ad9dea9ee0f47535e5355e6_img.jpg) + +The diagram illustrates the interworking reference model. On the left, an 'External SIP-I Network' (represented by a grey oval) is connected to a 'GMSC Server, MSC Server' (a rectangular box). The connection consists of two lines: a dashed line for the control plane labeled 'SIP-I over TCP or UDP or SCTP' and a solid line for the user plane labeled 'Media/ RTP/ UDP/ IP'. Inside the GMSC Server, there is a shaded box labeled 'IWU' (Interworking Unit). Below the GMSC Server is an 'MGW' (Media Gateway) box, which contains a shaded box labeled 'UP-IWU'. A dashed line labeled 'Mc' connects the IWU in the GMSC Server to the UP-IWU in the MGW. To the right of the GMSC Server is an 'MSC Server' box, connected to the GMSC Server by a dashed line labeled 'SIP-I over SCTP' and 'Nc'. Below the MSC Server is another 'MGW' box, connected to the MSC Server by a dashed line labeled 'Mc'. A solid line labeled 'Media/ RTP/ UDP/ IP' and 'Nb' connects the MGW under the GMSC Server to the MGW under the MSC Server. The entire right side of the diagram, including the GMSC Server, MSC Server, and both MGWs, is enclosed in a dashed line and labeled '3GPP CS Domain' at the bottom. A legend at the bottom left indicates that a solid line represents the 'User Plane', a dashed line represents the 'Control Plane', and a shaded box represents the 'Scope'. + +Figure 4.1.1: interworking reference model diagram showing the connection between an External SIP-I Network and a 3GPP CS Domain via a GMSC Server, MSC Server, and MGW. + +**Figure 4.1.1: interworking reference model** + +The IWU provides the control plane interworking between the external network and the SIP-I based circuit-switched core network. The IWU is a logical function within the GMSC Server (for incoming calls) and the MSC Server (for outgoing calls) that may reside with other 3GPP logical functions. + +The user plane interworking is provided by the UP-IWU. The UP-IWU is a logical function within the MGW. + +**NOTE:** In call scenarios without the need for the (G)MSC server to manipulate the bearer, the (G)MSC server may perform call control signalling without any associated MGW by not inserting a MGW in the bearer path during the call establishment. Call scenarios where the (G)MSC server needs to manipulate the bearer, e.g. scenarios with insertion of tones or announcements, lawful interception, CAMEL services do not allow this optimisation. + +**Nb reference point:** The Nb reference point is defined in accordance with 3GPP TS 29.414 [43]. + +**Nc reference point:** The Nc reference point is defined in accordance with 3GPP TS 29.231 [4]. + +## 4.2 Signalling Interworking of a Call from the external SIP-I based network towards the SIP-I based circuit-switched core network + +### 4.2.1 Interworking of SIP-I messages received from external SIP-I network + +#### 4.2.1.1 General + +The IWU shall decapsulate the ISUP message from the received SIP message according to the rules for Profile C in ITU-T Recommendation Q.1912.5 [6]. + +The resulting ISUP message shall be encapsulated into the SIP message. The selected SIP Header fields relating to the handling of the ISUP body shall be set as specified in subclause 5.4.1.2 of ITU-T Recommendation Q.1912.5 [6]. The IWU sends the constructed SIP message to the succeeding 3GPP node. + +#### 4.2.1.2 Call Release from external SIP-I network when encapsulated REL is missing + +If the IWU receives a SIP BYE request without an encapsulated ISUP message then the IWU may construct an ISUP REL message according to the rules specified in ITU-T Recommendation Q.1912.5 [6] and encapsulate it into a SIP message, which is sent to the succeeding 3GPP node. + +**NOTE:** A SIP BYE request without an encapsulated ISUP message can be received from a CS-IBCF or from a node of an interconnect network when they initiate autonomous call release. It is expected that a generated ISUP REL won't add any additional information which is not available in the received SIP BYE request. + +The IWU shall send a 200 OK final response to the BYE request without an encapsulated RLC message towards the external SIP-I network. + +### 4.2.2 Special Procedures for the reception of initial SIP INVITE requests + +#### 4.2.2.1 Receipt of SIP INVITE request + +If the initial SIP-I INVITE request does not provide a complete number, then the IWU shall collect all digits required to identify the called subscriber in subsequent SIP INVITE requests as specified for Profile C in ITU-T Recommendation Q.1912.5 [6]. The IWU shall not propagate overlap signalling as described for Profile C in ITU-T Recommendation Q.1912.5 [6]. + +The IWU shall trigger GMSC functions after having constructed the ISUP message, as described in 4.2.1 above. The GMSC interrogates the HLR to get a roaming number (MSRN). The Called Party Number in the ISUP IAM message is changed by the GMSC function to the MSRN. The IWU shall include the MSRN into the Request-URI as the new target. + +#### 4.2.2.2 Receipt of SIP INVITE requests with SDP + +Based on configuration the IWU may choose to transcode media. But the IWU shall always provide the TMR/USI/HLC parameters as received on the incoming side. + +#### 4.2.2.3 Receipt of SIP INVITE request without SDP + +An IWU may reject receipt of SIP INVITE requests without SDP offer. Otherwise the rules of subclause 4.2.2.1 apply with the following deviations: + +The IWU shall construct an SDP offer with contents according to local policy, e.g. SDP for a G.711 speech call. The IWU may use the TMR and USI parameters of the encapsulated IAM to determine the desired service and construct the SDP offer accordingly. The IWU may then send to the succeeding 3GPP node the SIP INVITE request with the constructed SDP offer and encapsulated IAM. + +If reliable provisional responses (see IETF RFC 3262 [21]) are supported in the external SIP-I network, the IWU may immediately send the SDP offer within a 183 Session Progress message to the preceding node. When the IWU receives the SDP answer then the IWU should send to the succeeding 3GPP node the SIP INVITE request with an encapsulated IAM message. Otherwise, the IWU shall behave in accordance with the paragraph above. + +#### 4.2.2.4 MGW Selection + +The IWU may apply the optional "optimised MGW selection", "deferred MGW selection" or "MGW bypass" procedures towards the succeeding SIP-I based circuit switched core network as described in subclause 4.4 of TS 3GPP 23.231 [3]. + +If MGW bypass is implemented and the IWU receives a MGW identifier: + +- in a SDP offer from external SIP-I network the IWU shall remove the MGW identifier from the SDP offer before propagating the SDP offer to the succeeding 3GPP node; +- in a SDP answer from the succeeding 3GPP node the IWU shall remove the MGW identifier from the SDP answer before propagating back the SDP answer to the external network. + +NOTE: If MGW bypass is implemented and the external network does not include a specified connection address (0.0.0.0 for IPv4) then this will be interpreted as supporting deferred MGW selection by the succeeding node. The succeeding node will select a MGW accordingly and may return the MGW Identifier to the IWU). + +Otherwise the IWU shall seize a MGW and shall include the MGW connection address into the SDP offer of the initial SIP INVITE request it will send to the succeeding 3GPP node. + +### 4.2.3 Interworking of SIP-I messages received from succeeding 3GPP node + +Whenever the IWU receives from the succeeding 3GPP node a SIP message with an encapsulated CON, ACM, CPG, ANM, SUS, RES message then the IWU sends the SIP message in accordance with rules in accordance with ITU-T Recommendation Q.1912.5 [6] to the external SIP-I network and the encapsulated ISUP message shall not be modified. + +### 4.2.4 Special Procedures for Profile Interworking + +#### 4.2.4.1 Support of 100Rel + +The IWU receiving a SIP INVITE with or without tag "100Rel" in the SUPPORTED or the REQUIRED header from the external SIP-I network shall advertise its preference of provisional reliable responses to the succeeding 3GPP node via a SUPPORTED header in the initial SIP INVITE request. + +As an option the IWU may consider a received SIP INVITE request without "100Rel" as erroneous and reject the INVITE request with a 421 "Extension Required" response. + +NOTE: The option to forward a SIP INVITE request to the succeeding 3GPP node with or without tag "100Rel", if the external network does not support reliable provisional responses, is not specified in the present specification. + +#### 4.2.4.2 Support for UPDATE method + +The IWU receiving a SIP INVITE with or without the UPDATE method included in the ALLOW header shall advertise its support for the UPDATE method to the succeeding 3GPP node by listing the UPDATE method in the ALLOW header field. + +As an option the IWU may consider a received initial SIP INVITE request without listing UPDATE in the ALLOW header field as erroneous and reject the INVITE request with a 403 "Forbidden" response. + +NOTE: The option to forward a SIP INVITE request to the succeeding 3GPP node without indicating support of the UPDATE method, if the external network does not support the UPDATE method, is not specified in the present specification. + +#### 4.2.4.3 Support for Preconditions + +When the incoming SIP INVITE request indicates that remote preconditions are met and local preconditions are met then the IWU may either not include the tag "precondition" and exclude appropriate SDP lines, or include the tag "preconditions" in the SUPPORTED header and provide an SDP offer indicating that preconditions are met. + +When the incoming SIP INVITE request does not contain a "precondition" tag the IWU shall assume the preconditions have been met within the external SIP-I network. If local preconditions are met then the IWU may either not include the tag "precondition" and exclude appropriate SDP lines, or include the tag "precondition" in the SUPPORTED header and provide an SDP offer indicating that preconditions are met. + +When the incoming SIP INVITE request indicates that remote preconditions are not met or when local preconditions are not met then the IWU shall include the tag "precondition" in the REQUIRE header or SUPPORTED header in the SIP INVITE request and shall encode preconditions in the SDP offer that the related local preconditions for QoS are not met, using the segmented status type, as defined in IETF RFC 3312 [23], as well as the strength-tag value "mandatory" for the local segment and the strength-tag value "optional" for the remote segment when sending the message to the succeeding 3GPP node. Or the IWU may defer forwarding the SIP INVITE request until remote local preconditions are met. + +When the incoming SIP INVITE request indicates that preconditions have not been met and the IWU will not include a MGW the SDP with preconditions information shall be transited unchanged and the "precondition" tag shall be transited in the same header as received. + +NOTE 1: The use of the SUPPORTED header is a deviation from IETF RFC 3312 [23] when the strength-tag contains a "mandatory" value. + +NOTE 2: The support of preconditions is mandated at the Nc interface. Therefore a response without "precondition" can be considered as erroneous if preconditions were not met. + +NOTE 3: The setting of the "Continuity Check Indicator" in the "Nature of Connection Indicators" parameter within the encapsulated IAM by the IWU is of no significance. The value is ignored by the succeeding 3GPP node. + +#### 4.2.5 Support for Codec Negotiation + +If the IWU uses the MGW bypass option as defined in 3GPP TS 23.231 [3], then the IWU is not involved in the codec negotiation procedure and transits SDP offers and answers unchanged. Otherwise, the remaining text of this subclause applies: + +If the IWU receives from the external SIP-I based network a SIP request with an SDP offer containing a codec list with or without the 3GPP\_OoBTC\_Indicator, the IWU shall follow the procedures defined for a 3GPP Intermediate Node in clause 9 of 3GPP TS 23.153 [5]. + +If the IWU receives from the external SIP-I based network an INVITE or re-INVITE request without any codec information, the IWU shall send an SDP offer to the succeeding 3GPP SIP-I node, where it either shall follow the procedures defined for a 3GPP node originating SDP offer in clause 9 of 3GPP TS 23.153 [5], or shall create an SDP offer with the default PCM codec. The IWU shall send the selected codec within an SDP offer towards the preceding external node. + +NOTE: Which codecs are negotiable with the external SIP-I network may depend on operator choices and preferences (local policy). + +#### 4.2.6 Special Procedures for the reception of SIP Re-INVITE requests + +##### 4.2.6.1 Receipt of SIP Re-INVITE request without SDP + +Upon receipt of a SIP Re-INVITE request without SDP, the IWU shall + +- construct an SDP offer with contents reflecting the SDP already negotiated with the external SIP-I network for the call, including codec information as specified in subclause 4.2.5, and send the SDP offer within a 200 OK (INVITE) message to the external SIP-I network; or +- reject the SIP Re-INVITE request. + +## 4.3 Signalling Interworking of a Call from SIP-I based circuit-switched core network towards the external SIP-I based network + +### 4.3.1 Interworking of SIP-I messages received from preceding 3GPP node + +#### 4.3.1.1 General + +An IWU receiving SIP messages with encapsulated ISUP information shall apply any interworking procedures detailed for Profile C in ITU-T Recommendation Q.1912.5 [6] affecting parameters within the ISUP, and then proceed to encapsulate any ISUP information received (with the exception of the excluded messages detailed in 5.4.3 of ITU-T Recommendation Q.1912.5 [6]) in a SIP message in a MIME body according to IETF RFC 3204 [19]. The selected SIP Header fields relating to the handling of the ISUP body shall be set as specified in ITU-T Recommendation Q.1912.5 [6]. + +#### 4.3.1.2 Call Release from external SIP-I network when encapsulated REL is missing + +If the IWU receives a SIP BYE request or 4XX, 5XX, 6XX final response to the initial INVITE request without an encapsulated ISUP REL message then the IWU may construct the ISUP REL message according to the rules specified in ITU-T Recommendation Q.1912.5 [6] and encapsulate it into the SIP message, which is sent to the preceding 3GPP node. + +NOTE: A SIP BYE request without an encapsulated ISUP message can be received from a CS-IBCF or from a node of an interconnect network when they initiate autonomous call release. It is expected that a generated ISUP REL message won't add any additional information which is not available in the received SIP BYE request. + +The IWU shall send a 200 OK final response to the BYE request without an encapsulated ISUP REL message towards the external SIP-I network. + +### 4.3.2 Special Procedures for the reception of SIP INVITE requests + +The IWU shall decapsulate the ISUP message. The IWU forwards the ISUP information to the "IW-MSC" functions, which may result in a modified ISUP message. + +Based on configuration the IWU may choose to transcode media. If the IWU transcodes, it should set the TMR/USI/HLC parameters according to the codec applied in the SIP-I network. Otherwise, it should provide the TMR/USI/HLC parameters as received in the encapsulated IAM. + +The IWU shall proceed to encapsulate the ISUP message into the SIP-INVITE request. The request URI shall be aligned with the called party number. + +### 4.3.3 Special Procedures for Profile Interworking + +#### 4.3.3.1 Support of 100Rel + +An IWU shall consider an initial SIP INVITE request received from the preceding 3GPP node without the tag "100Rel" in the SUPPORTED header or REQUIRED header as erroneous and shall reject the call accordingly. + +An IWU sending a SIP INVITE request towards the external SIP-I network shall advertise its preference of provisional reliable responses via a SUPPORTED header containing the tag "100Rel". + +If an IWU receives a provisional 101-199 response from the external SIP-I network with a REQUIRE header present with tag "100rel" then it shall include the tag "100Rel" into the REQUIRE header when the IWU propagates the response to the preceding 3GPP node. + +If an IWU receives from the external SIP-I network a provisional 101-199 response without tag "100rel" in the REQUIRE header then the IWU shall + +- either includes the tag "100Rel" into the REQUIRE header when it forwards the response to the preceding 3GPP node, +- or consider the response as erroneous and reject the call accordingly. + +NOTE: The option to forward the response to the preceding 3GPP node without tag "100Rel", if the external network does not support reliable provisional responses, is not specified in the present specification. + +#### 4.3.3.2 Support for UPDATE method + +An IWU sending a SIP INVITE towards the external SIP-I network shall advertise its support of the UPDATE method via the ALLOW header listing the UPDATE method. + +The IWU receiving a response to a SIP INVITE request is allowed to generate the UPDATE method towards the external network if an ALLOW header is present listing the UPDATE method. Otherwise, the IWU is not allowed to generate UPDATE requests towards the external SIP-I network and one of the following options applies: + +- The IWU shall return the response to the preceding 3GPP node containing an ALLOW header listing the UPDATE method. +- The IWU shall consider the response received from the external network as erroneous and reject the call accordingly. + +NOTE: The option to forward the response to the preceding 3GPP node without UPDATE in the ALLOW header field, if the external network does not support the UPDATE method, is not specified in the present specification. + +#### 4.3.3.3 Support for Preconditions + +When the incoming SIP INVITE request indicates that preconditions have not been met or when local preconditions are not met, the IWU shall use one of the following options: + +- The IWU shall send a SIP INVITE request to a succeeding external SIP-I network and include the tag "precondition" in the SUPPORTED header. The IWU shall encode preconditions in the SDP offer indicating that the related local preconditions for QoS are not met, using the segmented status type, as defined in IETF RFC 3312 [23], as well as the strength-tag value "mandatory" for the local segment and the strength-tag value "optional" for the remote segment. The "precondition" tag shall be included in the SUPPORTED header. The IWU shall encapsulate the IAM message into the SIP INVITE request and should insert "continuity check not required" as the value of the Continuity check indicator within the Nature of Connection Indicators parameter in order to avoid that an external node, which does not support preconditions, is waiting for a COT message when the IWU is not able to send the COT message. + +NOTE 1: Such an external node is not compliant to ITU-T Recommendation Q.1912.5 [6]. + +NOTE 2: The use of the SUPPORTED header is a deviation from IETF RFC 3312 [23] when a "mandatory" strength-tag is used. + +The subsequent action depends on whether the response indicates support of preconditions: + +- If the IWU receives from the external SIP-I network a provisional 101-199 response with a REQUIRE header or SUPPORTED header containing tag "precondition", then the IWU shall progress the call and when preconditions are met it shall send an UPDATE message or PRACK message indicating that preconditions have been fulfilled. Preconditions are fulfilled when local preconditions are met and, if the incoming SIP INVITE request indicated that preconditions had not been met, the IWU has received an indication from the preceding 3GPP node that the preconditions are subsequently met. +- If the IWU receives from the external SIP-I network a provisional 101-199 response without a REQUIRE header or SUPPORTED header containing tag "precondition" and if a provisional response or successful final response carrying an encapsulated ISUP message is received from external SIP-I network prior to preconditions being met, then these responses shall be queued and later be propagated to the preceding 3GPP node once preconditions are met. If responses carrying encapsulated ISUP are to be queued and the response carrying an encapsulated ISUP message is the first response carrying an SDP answer then the IWU shall generate a 183 Progress with the SDP answer and send it to the preceding node. The IWU shall not encapsulate an ISUP message into the 183 Progress. + +NOTE 3: The option to allow the SIP response to be immediately forwarded is not specified in the present will result in the O-MSC receiving encapsulated ISUP prior to preconditions being met. In addition, reception of response without indication of support for preconditions at the O-MSC is not specified in the present specification. + +If the IWU receives a failure response from the external network, then this shall immediately be forwarded to the preceding 3GPP node. + +- b) Before sending the INVITE request to the external network the IWU shall wait until local preconditions are met and, if the incoming SIP INVITE request indicated that preconditions have not been met, it has received an indication from the preceding 3GPP node that the preconditions are met. + +The initial INVITE request to the external SIP-I network may include a precondition tag in SUPPORTED header and indicate that preconditions have been met. + +- c) The IWU shall send a SIP INVITE request to a succeeding external SIP-I network and include the tag "precondition" in the REQUIRE header. The IWU shall encode preconditions in the SDP offer indicating that the related local preconditions for QoS are not met, using the segmented status type, as defined in IETF RFC 3312 [23], as well as the strength-tag value "mandatory" for the local segment and the strength-tag value "optional" for the remote segment. The IWU shall encapsulate the IAM message into the SIP INVITE request and should insert "continuity check not required" as the value of the Continuity check indicator within the Nature of Connection Indicators parameter in order to avoid that an external node, which does not support preconditions, is waiting for a COT message when the IWU is not able to send the COT message. + +NOTE 4: Such an external node is not compliant to ITU-T Recommendation Q.1912.5 [6]. + +The subsequent action depends on whether the response indicates support of preconditions: + +- i) If the IWU receives from the external SIP-I network a provisional 101-199 response with a REQUIRE header or SUPPORTED header containing tag "precondition", then the IWU shall continue the call per response handling procedures described in option a) above. +- ii) If the IWU receives a 420 Bad Extension final response, then the IWU shall continue per option b) above by waiting for preconditions to be met before repeating the initial INVITE request. + +When the incoming SIP INVITE request indicates that precondition are met and local preconditions are met, the IWU shall set up the session and may include a precondition tag in the SUPPORTED header and indicate that preconditions have been met. + +When the incoming SIP INVITE request indicates that preconditions have not been met and the IWU will not include a MGW the SDP with preconditions information shall be transited unchanged and the "precondition" tag shall be transited in the same header as received. + +#### 4.3.4 Support for Codec Negotiation + +When the IWU receives an INVITE with an SDP offer containing a structured codec list, the IWU shall follow the procedures defined for a 3GPP Intermediate Node in clause 9 of 3GPP TS 23.153 [5], unless the IWU uses the MGW bypass option. + +NOTE: Which codecs are negotiable with the external SIP-I network may depend on operator choices and preferences (local policy). + +#### 4.3.5 MGW Selection + +The IWU shall not perform "optimised MGW selection", or "deferred MGW selection" towards an external SIP-I network. The IWU shall select a MGW and include the MGW connection address in the SDP offer of the initial SIP INVITE request it sends to the external SIP-I network. The "MGW bypass" option may be deployed but in the case that the preceding 3GPP node signals the MGW identifier this identifier shall not be signalled to the external SIP-I network. + +## 4.4 DMTF Signalling Interworking applicable for all Calls between an external SIP-I based network and a SIP-I based circuit-switched core network + +### 4.4.1 General + +DTMF signalling via the RTP Telephony Event (RTP Telephony Event) is mandated to be supported over the Nb interface for SIP-I based Circuit Switched Core Network on Nc Interface, see 3GPP TS 23.231 [3]. + +NOTE 1: According to 3GPP TS 23.231 [3] it is an option to choose either the RTP Telephony Event or inband DTMF transport within the PCM codec when only the default PCM codec is selected, however once RTP Telephony Event is chosen (indicated in the SDP answer) it must be used for any selected codec. + +If MGW bypass is supported within the CS CN (see 3GPP TS 23.231, subclause 4.4.5 [3]), a terminating MSC or a 3GPP SIP-I intermediate node controlling a MGW that interfaces directly to the external network shall behave as an IWU, as its MGW is providing an UP-IWU function and therefore the SIP-I Server shall also comply with the procedures in this subclause. A GMSC Server or SIP-I intermediate node which is applying the MGW Bypass option shall then relay the SDP media lines for codecs and RTP Telephony Event in the SDP offers and answers transparently between the external SIP-I network and the 3GPP CS CN and is therefore not constrained by the procedures described in this subclause. + +If the SDP answer sent towards the external SIP-I network or received from the external SIP-I network includes the RTP Telephony event, then the IWU shall request its MGW to transmit and receive the DTMF to/from the external SIP-I node within the RTP Telephony Event. + +If the SDP answer sent towards or received from the SIP-I based CS CN includes the RTP Telephony event, then the IWU shall request its MGW to transmit and receive the DTMF to/from the SIP-I based CS CN within the RTP Telephony Event. + +DTMF interworking is specified for interworking towards an external SIP-I network with the assumption that the following applies: + +- External SIP-I network includes RTP Telephony event within SDP offers or SDP answers together with non-PCM speech codecs; +- External SIP-I network includes default PCM codec in SDP offers or SDP answers. + +Therefore only the case where the external SIP-I network includes default PCM codec when not including the RTP Telephony event is described. + +### 4.4.2 DTMF support in SDP offer sent to External SIP-I network + +If an IWU receives an *initial* SDP offer from a preceding 3GPP SIP-I node with the RTP Telephony Event it shall forward the RTP Telephony Event in the offer to the succeeding (external) node. If the IWU then receives a SDP answer from the succeeding node (external network) including the RTP Telephony Event, the IWU shall include the RTP Telephony Event in the SDP answer it forwards to the SIP-I based CS CN independently of the selected codec type, i.e. any DTMF payload received would then be simply relayed through the interworking MGW, and the IWU shall also include the RTP-telephony event in possible subsequent SDP offers it sends towards the succeeding external network node. + +If an IWU receives an SDP offer from a preceding 3GPP SIP-I node without the RTP Telephony Event (only permitted if only default PCM codec offered) then it may: + +- Include additional non-PCM speech codecs and shall then include the RTP Telephony Event in the subsequent offer to the succeeding external SIP-I node; + +NOTE: If the answer from the external SIP-I node does not include the RTP Telephony Event then no interworking of DTMF Telephony Events or tones is required by the MGW. + +or: + +- send the SDP Offer to the external SIP-I node without the RTP Telephony Event (no compressed codecs included in the offer) and then no inband DTMF detection/insertion is required; or: + +- Send the SDP Offer to the external SIP-I node without any additional non-PCM speech codecs and include the RTP Telephony Event. + +If the answer from the external SIP-I node includes the RTP Telephony event and the RTP Telephony event has not been offered by the preceding 3GPP SIP-I network then the IWU shall request its MGW (UP-IWU) to detect/insert inband DTMF tones to/from its preceding 3GPP SIP-I node and send/receive the DTMF to the external SIP-I node within the RTP Telephony Event, see subclause 14.4.8 in 3GPP TS 23.231 [3], + +If an IWU receives a SDP offer from a preceding 3GPP SIP-I node with the RTP Telephony Event and then receives a SDP answer from the external SIP-I network which includes only the PCM speech codec and excludes the RTP Telephony Event the IWU may: + +- apply "transcoding at the PLMN border" by selecting another speech codec than the default PCM codec for the interface toward the SIP-I based CS CN (if included in the offer) and then the IWU shall include the RTP Telephony Event in the answer it forwards to the SIP-I based CS CN, or: +- select default PCM codec towards the SIP-I CS CN and may include the RTP Telephony Event in the reply to the preceding (3GPP SIP-I) node and shall then request its MGW to relay inband DTMF to the RTP Telephony Event to/from the external network, see subclause 14.4.8 in 3GPP TS 23.231 [3], or: +- select default PCM codec towards the SIP-I CS CN and exclude the RTP Telephony Event in the reply to the preceding (3GPP SIP-I) node and then no inband DTMF detection/insertion is required. + +#### 4.4.3 DTMF support in SDP offer received from External SIP-I network + +If an IWU receives an SDP offer from the external SIP-I network with the RTP Telephony Event it shall forward the RTP Telephony Event in the offer to the succeeding node. If the SDP answer from the succeeding (3GPP internal) SIP-I node includes the RTP Telephony Event the IWU shall configure its MGW to relay the RTP Telephony Events transparently as described in subclause 14.4.3 of 3GPP TS 23.231 [3]. + +If an IWU receives a SDP offer from the external SIP-I network without the RTP Telephony Event the IWU shall include the RTP Telephony Event in the offer to the succeeding node if any codec other than the default PCM speech codec is offered to the succeeding node. If only the default PCM speech codec is offered to the succeeding node, the IWU may include the RTP Telephony Event in the offer to the succeeding SIP-I CS CN node. + +If the IWU receives a SDP answer from the succeeding (3GPP internal) SIP-I node including the RTP Telephony Event and the RTP Telephony Event had not been received in the offer from the external network the IWU returns the default PCM codec in the SDP answer to the external SIP-I network. The IWU shall then request its MGW (UP-IWU) to detect any inband DTMF from the external SIP-I network and signal the DTMF to the succeeding 3GPP SIP-I node within the RTP Telephony Event and insert DTMF tones into the external SIP-I network if DTMF digits received via RTP Telephony Event from the succeeding 3GPP SIP-I node, see subclause 14.4.8 in 3GPP TS 23.231 [3]. + +If an IWU receives a SDP answer from the succeeding (3GPP internal) SIP-I node excluding the RTP Telephony Event (i.e. default PCM codec selected) but received an RTP Telephony Event in the SDP offer from the external SIP-I network it may return RTP Telephony Event in the SDP answer to the external SIP-I network. It shall then configure its MGW (UP-IWU) for transferring DTMF between inband PCM and RTP Telephony Events as described in subclause 14.4.8 in 3GPP TS 23.231 [3]. If the IWU chooses not to include the RTP Telephony Event in the SDP answer then default PCM codec shall be signalled in the SDP answer to the external SIP-I network. No inband DTMF detection or insertion is required; any DTMF tones received are passed transparently inband. + +If an IWU receives a SDP answer from the succeeding (3GPP internal) SIP-I node excluding the RTP Telephony Event (i.e. default PCM codec selected) and did not receive an RTP Telephony Event in the SDP offer from the external SIP-I network the IWU returns the default PCM codec as the selected codec in the SDP answer to the external network and shall not request its MGW to configure RTP Telephony Event; therefore any inband DTMF tones are passed transparently inband. + +## 4.5 User Plane Interworking + +### 4.5.1 General + +Figure 4.5.1.1 shows the user plane protocol stacks within the external SIP-I network and the 3GPP SIP-I based circuit switched core network. + +![Diagram of user plane interworking showing an External SIP-I Network connected to a table of protocol layers for two different codecs.](e180f2b5fcbe8001554a7c0677cd3f82_img.jpg) + +The diagram illustrates user plane interworking. On the left, an oval labeled "External SIP-I Network" is connected to a table. The table has two columns representing different codecs: "Codec, e.g. G.711" and "Codec, e.g. NB-AMR". The rows represent protocol layers: "RTP", "UDP", "IP", and "L2, L1". A line labeled "Nb" extends from the right side of the table. + +| | | +|-------------------|--------------------| +| Codec, e.g. G.711 | Codec, e.g. NB-AMR | +| RTP | RTP | +| UDP | UDP | +| IP | IP | +| L2, L1 | L2, L1 | + +Diagram of user plane interworking showing an External SIP-I Network connected to a table of protocol layers for two different codecs. + +**Figure 4.5.1.1: user plane interworking** + +If the same speech codec is used on both sides, no speech transcoding is required. + +## 4.5.2 DTMF Interworking + +For general information of DTMF interworking, see subclause 4.4.1. + +The IWU may configure its UP-IWU with RTP Telephony Event at the 3GPP SIP-I termination and the external SIP-I termination. The UP-IWU shall then relay any DTMF received within the RTP Telephony Event Payload Type from one network interface to the other. + +The IWU may configure the UP-IWU with only one network termination with RTP Telephony Event and the other termination configured for default PCM. The UP-IWU shall then detect DTMF tones from the PCM-encoded speech path and transmit them as RTP Telephony Events toward the other network and shall detect RTP Telephony Events and insert the DTMF as Tones in the corresponding PCM-encoded path. + +If the IWU does not configure RTP Telephony Event on either network terminations then the UP-IWU simply relays the PCM-encoded speech from one network to the other (which may contain and therefore relay DTMF tones). + +If RTP Telephony Event is selected for either the external SIP-I connection or for the internal 3GPP CS CN connection, but not for both, then the MGW shall filter out (delete) the DTMF from the default PCM-coded speech path (when relaying the DTMF via the RTP Telephony Event) to prevent potential double signalling of the same digit if a later insertion back to inband DTMF tone transmission were to occur. + +The related UP-IWU control procedures and UP-IWU behaviour is described in subclauses 14.4.3 and 14.4.8 of 3GPP TS 23.231 [3], where the MGW shall be understood as UP-IWU. + +## 4.6 Example Call flows + +### 4.6.1 General + +In this subclause call flows are shown as examples to demonstrate the signalling interworking of the IWU. Within the message sequence charts some content of the messages are shown in order to visualise some of the important interworking aspects, which were described in previous subclauses of this document. It is to be noted that the intention is neither to show the complete content of the SIP messages nor to use the exact syntax of SIP and SDP messages as it is defined in the respective RFCs. It is also not the intention to show all alternative options that are possible for a certain call flow. + +### 4.6.2 Incoming Call flows + +#### 4.6.2.1 Incoming Call – no preconditions in external network + +Figure 4.6.2.1.1 shows a terminating call where the external network does not indicate the support of preconditions and where the SDP body contains a list of codecs according to IETF RFC 3264 [22]. The IWU assumes that remote + +preconditions are met. The incoming side RTP bearer termination is yet not successfully reserved and configure and therefore local preconditions are not met. Thus the IWU initiates precondition signalling when sending the INVITE request to the succeeding 3GPP node. The IWU and the 3GPP node perform codec negotiation according to 3GPP rules as specified in 3GPP TS 23.153 [5]. The IWU answers to the external network with a single selected codec. If possible the selected codec is the same as received from the 3GPP node to avoid transcoding at the network border. + +The IWU changes the content of the Request URI (either a tel-URI or a SIP-URI with "user=phone") from the MSISDN of the called subscriber to the MSRN received from the HLR. The IWU inserts its own address into the From header of the initial SIP INVITE request being sent to the succeeding 3GPP node. + +![Sequence diagram for an incoming call from an external network to a 3GPP node via a GMSC Server IWU and an MGW UP-IWU. The diagram shows the flow of SIP messages (INVITE, TRYING, 183 Progress, PRACK, 200 OK, 180 Ringing, ACK) and internal actions like HLR interrogation and RTP bearer termination seizure. It also notes conditions for preconditions being met or not at various points.](ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg) + +Sequence diagram illustrating an incoming call scenario involving a GMSC Server IWU and an MGW UP-IWU. + +**Participants:** + +- External Network (left) +- GMSC Server IWU (center) +- MGW UP-IWU (right) +- 3GPP Node (far right) + +**Interfaces:** + +- NNI: Between External Network and GMSC Server IWU +- Nc: Between GMSC Server IWU and MGW UP-IWU +- Mc: Between GMSC Server IWU and 3GPP Node + +**Sequence of Events:** + +- The External Network sends an **INVITE [SDP, IAM]** message to the GMSC Server IWU. The Request URI is MSISDN, and it includes 100rel, UPDATE, IETF codec list, and IAM. +- The GMSC Server IWU responds with **TRYING**. +- The GMSC Server IWU performs an **HLR Interrogation** to fetch the MSRN. +- The GMSC Server IWU sends a message to the MGW UP-IWU to **Seize outgoing side RTP bearer terminations**. +- The GMSC Server IWU sends an **INVITE [SDP, IAM]** message to the 3GPP Node. The Request URI is MSRN, and it includes From: SIP URI of GMSC, 100rel, UPDATE, precondition tag, 3gOoBTC, supported codec list, and IAM (updated). + - If remote preconditions are met and local preconditions are met, the process continues. + - If remote preconditions are met but local preconditions are not met, the process continues with the next step. +- The 3GPP Node responds with **183 Progress [SDP]**, including 100rel, UPDATE, precondition tag, 3gOoBTC, selected codec, and available codecs. +- The GMSC Server IWU sends a message to the MGW UP-IWU for **Seizure of incoming side RTP bearer terminations, though-connection**. +- If local preconditions are met, the GMSC Server IWU sends **183 Progress [SDP]** to the External Network, including 100rel, UPDATE, and selected codec. +- The External Network responds with **PRACK**. +- The GMSC Server IWU sends **200 OK (PRACK)** to the External Network. +- The 3GPP Node sends **180 Ringing [ACM]** to the GMSC Server IWU. +- The GMSC Server IWU sends **180 Ringing [ACM]** to the External Network. +- The External Network sends another **PRACK**. +- The GMSC Server IWU sends **200 OK (PRACK)** to the External Network. +- The 3GPP Node sends **200 OK (INVITE) [ANM]** to the GMSC Server IWU. +- The GMSC Server IWU sends **ACK** to the 3GPP Node. +- The External Network sends **200 OK (INVITE) [ANM]** to the GMSC Server IWU. +- The GMSC Server IWU sends **ACK** to the External Network. + +Sequence diagram for an incoming call from an external network to a 3GPP node via a GMSC Server IWU and an MGW UP-IWU. The diagram shows the flow of SIP messages (INVITE, TRYING, 183 Progress, PRACK, 200 OK, 180 Ringing, ACK) and internal actions like HLR interrogation and RTP bearer termination seizure. It also notes conditions for preconditions being met or not at various points. + +Figure 4.6.2.1.1: Incoming Call (message sequence chart), +example without support for preconditions at the NNI + +#### 4.6.2.2 Incoming Call with preconditions not met + +In figure 4.6.2.2.1 the external network indicates that its preconditions are not met. Because support for preconditions is mandated at the interface to the succeeding 3GPP node, the IWU can immediately send the INVITE towards the destination. + +The IWU receives from the external network the information that preconditions are met either in the PRACK or UPDATE request, where the SDP parameters are set accordingly. The IWU sends the information that preconditions are met either within the PRACK or with an UPDATE request to the 3GPP node such that the called subscriber can be alerted. + +![Sequence diagram showing the interaction between a GMSC Server IWU and an MGW UP-IWU for a call setup. The diagram includes messages like INVITE, TRYING, HLR Interrogation, Seize outgoing side RTP bearer terminations, 183 Progress, PRACK, 200 OK, UPDATE, 180 Ringing, and ACK. It also shows interfaces NNI, Nc, and Mc, and connections to an External Network and a 3GPP Node.](90ddb84c323b956e2d50a54d3f870566_img.jpg) + +The sequence diagram illustrates the call setup process between a GMSC Server IWU and an MGW UP-IWU. The GMSC Server IWU is connected to an External Network via an NNI interface and to an MGW UP-IWU via Nc and Mc interfaces. The MGW UP-IWU is connected to a 3GPP Node. + +The sequence of messages is as follows: + +- The External Network sends an **INVITE [SDP, IAM]** to the GMSC Server IWU. The request URI is MSIDN, and it includes 100rel, UPDATE, precondition tag, and IETF codec list. Preconditions are not met. +- The GMSC Server IWU responds with **TRYING**. +- The GMSC Server IWU performs **HLR Interrogation**. +- The GMSC Server IWU sends a **Seize outgoing side RTP bearer terminations** message to the MGW UP-IWU. +- The GMSC Server IWU sends an **INVITE [SDP, IAM]** to the MGW UP-IWU. The request URI is MSRN, and it includes From: SIP URI of GMSC, 100rel, UPDATE, precondition tag, 3gOoBTC, supported codec list, and preconditions not met. +- The MGW UP-IWU responds with **183 Progress [SDP]**, which includes 100rel, UPDATE, precondition tag, gOoBTC, selected codec, and available codecs. +- The MGW UP-IWU sends a **Seizure of incoming side RTP bearer terminations, though-connection** message to the GMSC Server IWU. +- The MGW UP-IWU sends a **183 Progress [SDP]** to the GMSC Server IWU. A note indicates that the selected codec chosen from the succeeding 3GPP node may be supported on the external network. If not, then another codec must be chosen. +- The GMSC Server IWU sends **PRACK** to the MGW UP-IWU. +- The MGW UP-IWU responds with **200 OK (PRACK)**. +- The GMSC Server IWU sends **UPDATE [SDP]** to the MGW UP-IWU. Preconditions are met. +- The MGW UP-IWU responds with **200 OK (UPDATE[SDP])**. +- The MGW UP-IWU sends **180 Ringing [ACM]** to the GMSC Server IWU. +- The GMSC Server IWU sends **PRACK** to the MGW UP-IWU. +- The MGW UP-IWU responds with **200 OK (PRACK)**. +- The MGW UP-IWU sends **200 OK (INVITE) [ANM]** to the GMSC Server IWU. +- The GMSC Server IWU sends **ACK** to the MGW UP-IWU. + +Sequence diagram showing the interaction between a GMSC Server IWU and an MGW UP-IWU for a call setup. The diagram includes messages like INVITE, TRYING, HLR Interrogation, Seize outgoing side RTP bearer terminations, 183 Progress, PRACK, 200 OK, UPDATE, 180 Ringing, and ACK. It also shows interfaces NNI, Nc, and Mc, and connections to an External Network and a 3GPP Node. + +**Figure 4.6.2.2.1: Incoming Call (message sequence chart), +example with precondition update** + +## 4.6.3 Outgoing Call flows + +### 4.6.3.1 Outgoing Call with support for preconditions + +Figure 4.6.3.1.1 shows an outgoing call where the preconditions are not met when the IWU receives the initial SIP INVITE. Support for preconditions is confirmed from the external network. Within this example the external node provides a single codec, therefore no second SDP offer/answer is needed for codec negotiation. + +When the IWU receives from the preceding 3GPP node that preconditions are met, then it informs the external node that called subscriber can be alerted with an UPDATE request, where the SDP contains the appropriate precondition offer and the selected codec. + +![Sequence diagram for an outgoing call with preconditions. Lifelines: 3GPP Node, MGW UP-IWU, MSC Server / IWU, and External Network. The process involves INVITE, 100 TRYING, Seize outgoing side RTP bearer terminations, INVITE to External Network, 100 TRYING, 183 Progress, Seize incoming side RTP bearer terminations, 183 Progress, PRACK, 200 OK (PRACK), UPDATE, 200 OK (UPDATE), 180 Ringing, PRACK, 200 OK (PRACK), 200 OK (INVITE), and ACK messages.](9c1d3678db4a12d5864cb2a4def1135d_img.jpg) + +``` + +sequenceDiagram + participant 3GPP Node + participant MGW UP-IWU + participant MSC Server / IWU + participant External Network + + Note right of MGW UP-IWU: Nc + Note right of MGW UP-IWU: Mc + Note right of MSC Server / IWU: NNI + + 3GPP Node->>MGW UP-IWU: INVITE [SDP, IAM] + + Note right of MGW UP-IWU: 100rel, UPDATE, precondition tag + + 3gOoBTC, supported codec list + + preconditions not met + + MGW UP-IWU-->>3GPP Node: 100 TRYING + + Note right of MGW UP-IWU: Seize outgoing side RTP bearer terminations + + Note right of MGW UP-IWU: preconditions are not met + + MGW UP-IWU->>MSC Server / IWU: INVITE [SDP, IAM] + + Note right of MSC Server / IWU: 100rel, UPDATE, precondition tag + + 3gOoBTC, supported codec list (updated) + + preconditions not met + + MSC Server / IWU-->>External Network: 100 TRYING + + MSC Server / IWU-->>External Network: 183 Progress [SDP] + + Note right of MSC Server / IWU: 100rel, UPDATE, precondition tag + + IETF codec, local preconditions met + + Note right of MGW UP-IWU: Seize incoming side RTP bearer terminations + + MGW UP-IWU-->>3GPP Node: 183 Progress [SDP] + + Note right of MGW UP-IWU: 100rel, UPDATE, preconditions + + 3gOoBTC, selected codec, available codecs + + local preconditions met + + MGW UP-IWU->>MSC Server / IWU: PRACK + + MSC Server / IWU-->>External Network: PRACK + + MSC Server / IWU-->>3GPP Node: 200 OK (PRACK) + + MGW UP-IWU->>MSC Server / IWU: UPDATE [SDP] + + Note right of MGW UP-IWU: preconditions are met + + Note right of MSC Server / IWU: selected codec, preconditions are met + + MSC Server / IWU-->>3GPP Node: 200 OK (UPDATE) [SDP] + + Note right of MSC Server / IWU: selected codec, local preconditions met + + MSC Server / IWU-->>External Network: 180 Ringing [ACM] + + MGW UP-IWU-->>3GPP Node: 180 Ringing [ACM] + + MGW UP-IWU->>MSC Server / IWU: PRACK + + MSC Server / IWU-->>External Network: PRACK + + MSC Server / IWU-->>3GPP Node: 200 OK (PRACK) + + MSC Server / IWU-->>External Network: 200 OK (INVITE) [ANM] + + MGW UP-IWU-->>3GPP Node: 200 OK (INVITE) [ANM] + + MGW UP-IWU->>MSC Server / IWU: ACK + + MSC Server / IWU-->>External Network: ACK + +``` + +Sequence diagram for an outgoing call with preconditions. Lifelines: 3GPP Node, MGW UP-IWU, MSC Server / IWU, and External Network. The process involves INVITE, 100 TRYING, Seize outgoing side RTP bearer terminations, INVITE to External Network, 100 TRYING, 183 Progress, Seize incoming side RTP bearer terminations, 183 Progress, PRACK, 200 OK (PRACK), UPDATE, 200 OK (UPDATE), 180 Ringing, PRACK, 200 OK (PRACK), 200 OK (INVITE), and ACK messages. + +Figure 4.6.3.1.1: Outgoing call (message sequence chart), +example with support for preconditions + +#### 4.6.3.2 Outgoing Call with support of 100rel but no support for preconditions + +Figure 4.6.3.2.1 depicts an outgoing call where the external network supports reliable provisional responses and the UPDATE method but does not support preconditions. Therefore the IWU cannot exchange SDP precondition offers/answers with the external node. + +In this example the IWU receives more than one single codec in the 183 Progress from the external node. Therefore the IWU selects one of the received codecs and makes a second SDP offer to the external node in the PRACK in order to lock the codec. + +The IWU receives a 180 Ringing provisional response from the external network before preconditions are fulfilled. The IWU forwards the 180 Ringing response after preconditions have been fulfilled. + +NOTE 1: The IWU may also have received a successful final response to the INVITE before preconditions have been met. In this case the forwarding of the 180 Ringing response and of the final successful response towards the preceding 3GPP node is delayed until preconditions are fulfilled. + +NOTE 2: As an alternative the IWU could send PRACK to the external node when PRACK is received from the preceding 3GPP node acknowledging the 180 Ringing response. Since the sending of the 180 Ringing response to the 3GPP network may be delayed, this may lead to the retransmission of 180 Ringing response sent by the external node. + +![Sequence diagram for an outgoing call from a 3GPP Node to an External Network via an MGW UP-IWU and an MSC Server / IWU. The diagram shows the exchange of INVITE, TRYING, PRACK, UPDATE, and ACK messages, with specific SDP details and precondition handling.](dd5771673aececa53d42ece89218299d_img.jpg) + +The sequence diagram illustrates the signaling flow for an outgoing call. The participants are a 3GPP Node, an MGW UP-IWU, an MSC Server / IWU, and an External Network. The MGW UP-IWU is connected to the 3GPP Node via the Nc interface and to the MSC Server / IWU via the Mc interface. The MSC Server / IWU is connected to the External Network via the NNI interface. + +The call sequence is as follows: + +- The 3GPP Node sends an **INVITE [SDP, IAM]** message to the MGW UP-IWU. The message includes `100rel`, `UPDATE`, a precondition tag, `3gOoBTC`, a supported codec list, and indicates that the precondition is not met. +- The MGW UP-IWU responds with a **TRYING** message. +- The MGW UP-IWU then performs a **Seize outgoing side RTP bearer terminations** operation. +- Next, it sends an **INVITE [SDP, IAM]** message to the MSC Server / IWU. This message includes `100rel`, `UPDATE`, a precondition tag, `3gOoBTC`, an updated supported codec list, and indicates that the precondition is not met. +- The MSC Server / IWU responds with a **100 TRYING** message. +- Then, it sends a **183 Progress [SDP]** message. The message includes `100rel`, `UPDATE`, an IETF codec list, and indicates that the precondition is not met. +- The MGW UP-IWU receives the **183 Progress [SDP]** message and performs an **O-IWU selects codec** operation. +- It then performs a **Seize incoming side RTP bearer terminations** operation. +- The MGW UP-IWU sends a **183 Progress [SDP]** message to the 3GPP Node. This message includes `100rel`, `UPDATE`, a precondition tag, `3gOoBTC`, a selected codec, available codecs, and indicates that local preconditions are met. +- The MGW UP-IWU sends a **PRACK** message to the MSC Server / IWU. +- The MSC Server / IWU responds with a **PRACK [SDP]** message, indicating the selected codec. +- The MGW UP-IWU receives the **PRACK [SDP]** message and sends a **200 OK (PRACK)** message to the 3GPP Node. +- The MSC Server / IWU receives a **200 OK (PRACK) [SDP]** message, indicating the selected codec. +- Next, the MSC Server / IWU sends a **180 Ringing [ACM]** message. +- The MGW UP-IWU receives the **180 Ringing [ACM]** message and sends a **PRACK** message to the MSC Server / IWU. +- The MSC Server / IWU responds with a **200 OK (PRACK)** message. +- The MGW UP-IWU receives the **200 OK (PRACK)** message and sends a **200 OK (INVITE) [ANM]** message to the 3GPP Node. +- The MGW UP-IWU receives a **200 OK (INVITE) [ANM]** message from the MSC Server / IWU. +- Finally, the MGW UP-IWU sends an **ACK** message to the 3GPP Node, and the MSC Server / IWU sends an **ACK** message to the External Network. + +Key notes from the diagram: + +- At the MGW UP-IWU, after sending the initial INVITE, there is a note: "preconditions are not met". +- When the MGW UP-IWU sends the 183 Progress [SDP] to the 3GPP Node, there is a note: "local preconditions met". +- Between the 180 Ringing [ACM] and PRACK messages at the MGW UP-IWU, there is a note: "preconditions are still not met". +- When the MGW UP-IWU sends the UPDATE [SDP] message to the MSC Server / IWU, there is a note: "preconditions met". +- When the MGW UP-IWU receives the 200 OK (UPDATE) [SDP] message, there is a note: "local preconditions met". +- When the MSC Server / IWU receives the PRACK [SDP] message, there is a note: "preconditions are met". + +Sequence diagram for an outgoing call from a 3GPP Node to an External Network via an MGW UP-IWU and an MSC Server / IWU. The diagram shows the exchange of INVITE, TRYING, PRACK, UPDATE, and ACK messages, with specific SDP details and precondition handling. + +**Figure 4.6.3.2.1: Outgoing Call (message sequence chart), +example with support of 100rel but no support for preconditions** + +#### 4.6.3.3 Outgoing Call without support for 100rel and preconditions + +Figure 4.6.3.3.1 depicts an outgoing call where the external network does not support reliable provisional responses and therefore no SDP precondition signalling can be performed with the UPDATE method. With the 183 Progress the IWU receives an IETF codec list "unreliably". If the answer includes more than one codec the IWU cannot make a second offer to the external node (to lock the selected codec) during the early dialogue. However, the IWU can make use of the received information and start codec negotiation when forwarding the 183 Progress to the preceding 3GPP node. + +The IWU immediately sends 200 OK to PRACKs received from the 3GPP node, because it cannot forward them to the external node. The reliable provisional responses cannot be signalled end-to-end. + +The final response from the external network should include the same codecs as received previously within the Progress message. If this answer includes more than one codec the IWU makes a second offer to the external network with a re-INVITE request. + +![Sequence diagram for an outgoing call from a 3GPP Node to an External Network via an MGW UP-IWU and an MSC Server / IWU. The diagram shows the exchange of SIP messages including INVITE, TRYING, 100rel, UPDATE, 183 Progress, PRACK, 200 OK, 180 Ringing, and Re-INVITE. Key actions include RTP bearer terminations and codec selection.](e05b36c0d46549e681ce6581422c66b2_img.jpg) + +``` + +sequenceDiagram + participant 3GPP Node + participant MGW UP-IWU + participant MSC Server / IWU + participant External Network + + Note left of MGW: from 3GPP Node + Note right of MSC: to External Network + + MGW->>MSC: INVITE [SDP, IAM] +100rel, UPDATE, precondition tag +3gOoBTC, supported codec list, +preconditions not met + MSC-->>MGW: TRYING + Note right of MGW: Seize outgoing side RTP bearer terminations + MSC->>External: INVITE [SDP, IAM] +100rel, UPDATE, precondition tag +3gOoBTC, supported codec list (updated) +preconditions not met + External-->>MSC: 100 TRYING + External-->>MSC: 183 Progress [SDP] +IETF codec list + Note right of MGW: local preconditions are not met + Note right of MGW: O-IWU selects codec + Note right of MGW: Seize incoming side RTP bearer terminations + MGW->>3GPP: 183 Progress [SDP] +100rel, UPDATE, precondition tag +3gOoBTC, selected codec, available codecs +local preconditions met + MGW->>MSC: PRACK + 3GPP-->>MGW: 200 OK (PRACK) + MGW->>MSC: UPDATE [SDP] +preconditions met + 3GPP-->>MGW: 200 OK (UPDATE) [SDP] +local preconditions met + Note right of MSC: preconditions are met + External-->>MSC: 180 Ringing [ACM] + MGW-->>3GPP: 180 Ringing [ACM] + MGW->>MSC: PRACK + 3GPP-->>MGW: 200 OK (PRACK) + External-->>MSC: 200 OK (INVITE) [SDP, ANM] +IETF codec list + MGW-->>3GPP: 200 OK (INVITE) [ANM] + MGW->>MSC: ACK + MSC->>External: ACK + MSC->>External: Re-INVITE [SDP] +selected codec + External-->>MSC: 200 OK (re-INVITE) [SDP] +selected codec + MSC->>External: ACK + +``` + +Sequence diagram for an outgoing call from a 3GPP Node to an External Network via an MGW UP-IWU and an MSC Server / IWU. The diagram shows the exchange of SIP messages including INVITE, TRYING, 100rel, UPDATE, 183 Progress, PRACK, 200 OK, 180 Ringing, and Re-INVITE. Key actions include RTP bearer terminations and codec selection. + +Figure 4.6.3.3.1: Outgoing Call (message sequence chart), +example without support for 100rel and preconditions + +## 5 Interworking between a SIP-I based circuit-switched core network and an ISUP based network + +### 5.1 Reference Model + +Figure 5.1.1 details the interworking reference model for subclause 5 of the present specification + +![Figure 5.1.1: interworking reference model diagram. The diagram shows two main entities: 'SIP-I based CS CN' on the left and 'ISUP based network, either CS CN or external network' on the right. Between them is a light blue box labeled 'Scope of this TS' containing two sub-components: 'IWU' (top) and 'UP-IWU' (bottom). A dashed line connects the SIP-I based CS CN to the IWU, labeled 'SIP-I over Nc'. A solid line connects the SIP-I based CS CN to the UP-IWU, labeled 'media/ RTP/ UDP/IP/ over Nb'. Inside the 'Scope of this TS' box, a dashed line connects the IWU to the UP-IWU, labeled 'H.248'. From the IWU, a dashed line extends to the ISUP based network, labeled 'ISUP'. From the UP-IWU, a solid line extends to the ISUP based network, labeled 'TDM'. A legend at the bottom indicates that a solid line represents the 'User Plane' and a dashed line represents the 'Control Plane'.](dbbc0baac7341cda76cc4f8355dce23f_img.jpg) + +Figure 5.1.1: interworking reference model diagram. The diagram shows two main entities: 'SIP-I based CS CN' on the left and 'ISUP based network, either CS CN or external network' on the right. Between them is a light blue box labeled 'Scope of this TS' containing two sub-components: 'IWU' (top) and 'UP-IWU' (bottom). A dashed line connects the SIP-I based CS CN to the IWU, labeled 'SIP-I over Nc'. A solid line connects the SIP-I based CS CN to the UP-IWU, labeled 'media/ RTP/ UDP/IP/ over Nb'. Inside the 'Scope of this TS' box, a dashed line connects the IWU to the UP-IWU, labeled 'H.248'. From the IWU, a dashed line extends to the ISUP based network, labeled 'ISUP'. From the UP-IWU, a solid line extends to the ISUP based network, labeled 'TDM'. A legend at the bottom indicates that a solid line represents the 'User Plane' and a dashed line represents the 'Control Plane'. + +NOTE: The IWU is a logical function that may reside with other 3GPP logical functions in the same physical nodes, e.g. in an (G)MSC Server. The figure shows only the logical separation. + +**Figure 5.1.1: interworking reference model** + +**Nb reference point:** The Nb reference point is defined in accordance with 3GPP TS 29.414 [43]. + +**Nc reference point:** The Nc reference point is defined in accordance with 3GPP TS 29.231 [4]. + +### 5.2 Control Plane Interworking + +The following subclauses define the signalling interworking between the ISDN User Part (ISUP) protocols and Session Initiation Protocol (SIP) with its associated Session Description Protocol (SDP) and encapsulated ISUP at an IWU. + +The IWU shall act as a Type A or Type B exchange (ITU-T Recommendation Q.764 [7]) for the purposes of ISUP compatibility procedures. + +NOTE: An IWU may apply additional procedures to support interworking for national-specific capabilities. + +The ISUP capabilities or signalling information defined for national use are outside the scope of the present document. + +The services that can be supported through the use of the signalling interworking are limited to the services that are supported both within the ISUP based network and the SIP-I based CS CN. The IWU will originate and/or terminate services or capabilities that do not interwork seamlessly across domains according to the relevant protocol recommendation or specification. + +Table 5.2.1 lists the services seamlessly interworked within the scope of the present document. + +**Table 5.2.1: Seamlessly interworked Services** + +| Service | +|------------------------------------------------------------------| +| Speech/3.1 kHz audio | +| Data Calls (optional) | +| En bloc address signalling | +| Out of band transport of DTMF tones and information. (BICC only) | +| Inband transport of DTMF tones and information. (BICC and ISUP) | +| Multiple Subscriber Number (MSN) | +| Calling Line Identification Presentation (CLIP) | +| Calling Line Identification Restriction (CLIR) | +| Connected line presentation (COLP) | +| Connected line restriction (COLR) | +| Call Hold | +| Call Forwarding | +| Explicit Call Transfer (ECT) | +| User-to-User Signalling (UUS) | +| Call Deflection (CD) | +| Closed User Group (CUG) | +| Completion of Calls to Busy Subscriber (CCBS) | +| Multi-Level Precedence and Pre-emption (MLPP) | +| Call Waiting | + +The subclause 5.3.2 of ITU-T Recommendation Q.1912.5 [6] describes additional general principles specific to SIP-I. + +The interworking procedures in subclauses 5.3, 5.4 and 5.5 are based on ITU-T Recommendation Q.1912.5 [6] profile C. Clarifications are made within this specification on the application of ITU-T Recommendation Q.1912.5 [6] profile C. + +The control plane between the ISUP network and the SIP-I based CN is as shown in figure 5.2.1. + +![Diagram of control plane interworking between a SIP-I based circuit-switched core network and an ISUP based network. The diagram shows an 'Interworking Unit' (IWU) acting as a bridge. On the left, an 'ISUP based network' connects via 'TDM' to the IWU's 'L1' layer. The IWU contains stacked layers: 'L1' (connected to TDM), 'MTP2', 'MTP3', and 'ISUP'. On the right side of the IWU, there are layers 'SCTP' and 'SIP-I'. The 'SIP-I' layer connects to a 'SIP-I based CS CN' via 'IP'. Arrows indicate the flow of control plane signals: ISUP from the network to the IWU, and SIP-I from the IWU to the CS CN.](836b0790cef5469a167fa8931df4e408_img.jpg) + +Diagram of control plane interworking between a SIP-I based circuit-switched core network and an ISUP based network. The diagram shows an 'Interworking Unit' (IWU) acting as a bridge. On the left, an 'ISUP based network' connects via 'TDM' to the IWU's 'L1' layer. The IWU contains stacked layers: 'L1' (connected to TDM), 'MTP2', 'MTP3', and 'ISUP'. On the right side of the IWU, there are layers 'SCTP' and 'SIP-I'. The 'SIP-I' layer connects to a 'SIP-I based CS CN' via 'IP'. Arrows indicate the flow of control plane signals: ISUP from the network to the IWU, and SIP-I from the IWU to the CS CN. + +**Figure 5.2.1: Control plane interworking between a SIP-I based circuit-switched core network and an ISUP based network** + +## 5.3 Signalling Interworking of a Call from the ISUP based network towards the SIP-I based circuit-switched core network + +### 5.3.1 General + +The procedures for Profile C in clause 7 of ITU-T Recommendation Q.1912.5 [6] shall be applied with the modifications provided in this subclause. + +#### 5.3.1.1 Sending of ISUP information to adjacent SIP nodes + +The IWU receiving ISUP information shall apply any interworking procedures detailed in clause 7 of ITU-T Recommendation Q.1912.5 [6] affecting parameters within the ISUP, and then proceed to encapsulate any ISUP information received (with the exception of the excluded messages detailed in 5.4.3 of ITU-T Recommendation Q.1912.5 [6]) in a SIP message in a MIME body according to IETF RFC 3204 [19]. SIP Header fields relating to the handling of the ISUP body shall be set as specified in subclause 5.4.1.2 of ITU-T Recommendation Q.1912.5 [6]. + +NOTE 1: The text in the preceding paragraph has been derived from ITU-T Recommendation Q.1912.5 [6], subclause 5.4.1. + +For a basic call setup, the SIP message used to encapsulate the ISUP message shall be the SIP message that was first triggered to be sent from the IWU as a result of the interworking specified in clause 7 of ITU-T Recommendation Q.1912.5 [6]. As an example, this means that an ISUP IAM will be encapsulated within the INVITE message that is sent out from the IWU. For the ISUP messages listed in table 1 of ITU-T Recommendation Q.1912.5 [6], the special procedures in subclause 5.4.3 of ITU-T Recommendation Q.1912.5 [6] are applicable. + +NOTE 2: The text in the preceding paragraph has been derived from ITU-T Recommendation Q.1912.5 [6], subclause 5.4.1.3. + +#### 5.3.1.2 Receipt of encapsulated ISUP information within SIP-I + +On receipt of a SIP message containing encapsulated ISUP, the IWU shall de-encapsulate the ISUP message from the SIP message body. The received SIP message shall be mapped to an ISUP message and merged with the de-encapsulated ISUP information according to the rules in clause 7 of ITU-T Recommendation Q.1912.5 [6]. + +NOTE 1: The text in the preceding paragraph has been derived from ITU-T Recommendation Q.1912.5 [6], subclause 5.4.2. + +NOTE 2: These precedence rules have been derived from the following principles, which can also be applied for any ISUP information not covered by the present specification: + +- 1 Where a SIP header mapping to ISUP field(s) is possible (for example the mapping of Request-URI to Called Party Number), the SIP header is given precedence over the encapsulated ISUP value in the alignment process. (Conflicts can be caused by a possible service invocation within the SIP network.) +- 2 De-encapsulated ISUP information overrides ISUP information derived from default values (rather than SIP information). +- 3 Local ISUP procedures may modify information derived from SIP or default values. + +This Note has been derived from text in ITU-T Recommendation Q.1912.5 [6], subclause 5.4.2 + +NOTE 3: There is a certain change against ITU-T Recommendation Q.1912.5 [6], where the above note is formulated as normative procedures. However, this is very high level and not required if you look at the real interworking procedures later on. Therefore formulating this as a Note makes much more sense. + +#### 5.3.1.3 Special procedures related to outgoing INVITE + +##### 5.3.1.3.1 Overlap Signalling + +The IWU does not need to support procedures related to overlap signalling in clause 7 of ITU-T Recommendation Q.1912.5 [6]. + +NOTE: No overlap signalling is used in a 3GPP CS domain. A G-MSC acting as IWU will collect all digits required to identify the called party and not propagate the overlap signalling further. + +### 5.3.1.3.2 Coding of encapsulated ISUP IAM parameters in outgoing INVITE + +The IWU may choose to transcode media, or attempt to interwork media without transcoding. If the IWU transcodes, it should set the TMR/USI/HLC parameters according to the codec applied in the SIP-I network. Otherwise, it should provide the TMR/USI/HLC parameters as received in the incoming IAM. If the IWU offers several codecs within SDP, it should set the TMR/USI/HLC parameters according to the preferred codec, applying the rules above for this codec. + +NOTE: ITU-T Recommendation Q.1912.5 [6] does not describe the relationship between TMR/USI/HLC and SDP codec negotiation. + +### 5.3.1.3.3 Media offered in SDP of outgoing INVITE + +The IWU should offer codecs known to be supported within the SIP-I based CS CN network. If multiple speech codecs are offered, Out of Band Transcoder Control (OoBTC) procedures shall be applied by the IWU in accordance with 3GPP TS 23.153 [5]. Otherwise 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. + +If the IWU applies the optional "optimised MGW selection" procedure, it shall include a MGW Identifier in the SDP. Related signalling procedures are described in subclause 4.4 of 3GPP TS 23.231 [3] and the encoding of the MGW Identifier is defined in 3GPP TS 29.231 [4]. + +## 5.4 Signalling Interworking of a Call from SIP-I based circuit-switched core network towards the ISUP based network + +### 5.4.1 General + +The procedures for Profile C in clause 6 of ITU-T Recommendation Q.1912.5 [6] shall be applied with the modifications provided in this subclause. + +### 5.4.2 Interworking of received ISUP messages to SIP messages + +The IWU receiving backwards ISUP information shall apply any interworking procedures detailed in clause 6 of ITU-T Recommendation Q.1912.5 [6] affecting parameters within the ISUP, and then proceed to encapsulate any ISUP information received (with the exception of the excluded messages detailed in 5.4.3 of ITU-T Recommendation Q.1912.5 [6]) in a SIP message in a MIME body according to IETF RFC 3204 [19]. The selected SIP Header fields relating to the handling of the ISUP body shall be set as specified in subclause 5.4.1.2 of ITU-T Recommendation Q.1912.5 [6]. + +### 5.4.3 Interworking of received SIP messages to ISUP messages + +#### 5.4.3.1 Receipt of encapsulated ISUP information within SIP + +On receipt of a SIP message containing encapsulated ISUP, the IWU shall de-encapsulate the ISUP message from the SIP message body. The received SIP message shall be mapped to an ISUP message and merged with the de-encapsulated ISUP message according to the rules for Profile C in clause 6 of ITU-T Recommendation Q.1912.5 [6]. + +NOTE 1: These precedence rules have been derived from the following principles, which can also be applied for any ISUP information not covered by the present specification: + +- 1 Where a SIP header mapping to ISUP field(s) is possible (for example the mapping of Request-URI to Called Party Number), the SIP header is given precedence over the encapsulated ISUP value in the alignment process. +- 2 De-encapsulated ISUP information overrides ISUP information derived from default values (rather than SIP information). +- 3 Local ISUP procedures may modify information derived from SIP or default values. + +This note has been derived from text in ITU-T Recommendation Q.1912.5 [6], subclause 5.4.2. + +NOTE 2: There is a certain change against ITU-T Recommendation Q.1912.5 [6], where the above note is formulated as normative procedures. However, this is very high level and not required if you look at the real interworking procedures later on. Therefore formulating this as a note makes much more sense. + +### 5.4.3.2 Special Procedures for the Reception of SIP INVITE request + +#### 5.4.3.2.1 Propagation of overlap signalling toward the 3GPP CS domain + +The procedures in clause 6 of ITU-T Recommendation Q.1912.5 [6] related to the propagation of overlap signalling are not applicable, since no overlap signalling is used within the CS CN. + +#### 5.4.3.2.2 Derivation of TMR, USI and HLC parameters within sent IAM message + +The IWU may choose to transcode media and shall then set the parameters according to the coding applied within the CS Domain. Otherwise, the IWU shall select a codec for the SIP side termination using SDP offer-answer procedures, IETF RFC 3264 [22], and shall map the SDP information of this codec to the TMR/USI/HLC parameters according to table 2a of 3GPP TS 29.163 [13]. If the information derived from this mapping matches the information in the TMR/USI/HLC parameters in the encapsulated ISUP, the TMR/USI/HLC parameters from the encapsulated ISUP should be used as they may contain additional information. If the information derived from this mapping contradicts the information in the TMR/USI/HLC parameters in the encapsulated ISUP, the TMR/USI/HLC parameters derived by the mapping shall be used. + +NOTE: The procedures in this note are an amendment compared to ITU-T Recommendation Q.1912.5 [6], which simply states the TMR parameters in encapsulated ISUP shall take precedence, However this is inappropriate if an incompatible codec is selected. + +#### 5.4.3.2.3 Receipt of SIP INVITE without SDP offer + +An IWU may reject receipt of SIP INVITE without SDP offer, otherwise the procedures in section 4.2.2.3 shall be followed. + +NOTE: A SIP INVITE without SDP offer is not used within the CS CN. + +#### 5.4.3.2.4 Special Procedures for deferred MGW selection procedure. + +If the IWU supports the optional "deferred MGW selection" procedure and receives an unspecified connection address in the SDP offer contained in the INVITE request, it should include a MGW Identifier for the IWU-UP it selects in the corresponding SDP answer. Related signalling procedures are described in subclause 4.4 of 3GPP TS 23.231 [3] and the encoding of the MGW Identifier is defined in 3GPP TS 29.231 [4]. + +## 5.5 Supplementary services + +### 5.5.1 Special procedures for supplementary service interworking + +The supplementary services described in table 5.2.1 are interworked by using the parameters of the (de)encapsulated ISUP. No other interworking is required, except if otherwise described within the subclauses below. + +### 5.5.2 Interworking of CLIP/CLIR supplementary service + +For the interworking of call towards the SIP-I based CS CN: the service shall be supported by encapsulation. + +For the interworking of call from the SIP-I based CS CN: ITU-T Recommendation Q.1912.5 [6], Annex B.1, shall apply. + +### 5.5.3 Interworking of Call Hold (HOLD) supplementary service + +The Profile C procedures in ITU-T Recommendation Q.1912.5 [6], subclause B.10, shall be followed. + +### 5.5.4 Interworking of Completion of Calls to Busy Subscriber (CCBS) supplementary service to SIP networks + +The Profile C procedures of ITU-T Recommendation Q.1912.5 [6], subclause B.11 shall be applied. + +## 5.6 User Plane Interworking + +### 5.6.1 General + +This subclause describes user plane issues including interworking of DTMF. + +Figure 5.6.1.1 shows the user plane protocol stacks within the SIP-I based CS CN and an ISUP network. + +Apart from speech codecs, data call related codecs, e.g. as listed in table 2a of 3GPP TS 29.163 [13], may be used. + +![Diagram of User Plane Interworking and ISUP based CS Domain. It shows two network clouds, 'SIP-I based CS CN' on the left and 'ISUP based network' on the right, connected via a central 'UP-IWU' box. The UP-IWU contains a protocol stack with layers L1, L2, IP, UDP, RTP, and a 'Codec, e.g. AMR' / 'e.g. G.711' section. Above the stack is a 'Transcoding or Relay' label with a double-headed arrow. To the right of the stack, a 'TDM' label is present. The entire stack is enclosed in a box labeled 'UP-IWU' at the bottom.](d8698aacaeead6dfed9a1e448670a2e4_img.jpg) + +| | | +|-----------------------|---------------| +| Codec,
e.g.
AMR | e.g.
G.711 | +| RTP | TDM | +| UDP | | +| IP | | +| L2 | | +| L1 | | + +Diagram of User Plane Interworking and ISUP based CS Domain. It shows two network clouds, 'SIP-I based CS CN' on the left and 'ISUP based network' on the right, connected via a central 'UP-IWU' box. The UP-IWU contains a protocol stack with layers L1, L2, IP, UDP, RTP, and a 'Codec, e.g. AMR' / 'e.g. G.711' section. Above the stack is a 'Transcoding or Relay' label with a double-headed arrow. To the right of the stack, a 'TDM' label is present. The entire stack is enclosed in a box labeled 'UP-IWU' at the bottom. + +Figure 5.6.1.1: User Plane Interworking and ISUP based CS Domain + +### 5.6.2 DTMF + +If RTP Telephony Event is selected by the 3GPP CS CN the MGW shall filter out (delete) the DTMF from the default PCM codec when relaying the DTMF via the RTP Telephony Event to prevent potential double signalling of the same digit if a later insertion back to inband PCM transmission were to occur. + +## 5.7 Example Call flows + +The call flow examples in ITU-T Recommendation Q.1912.5 [6] Appendix III are applicable with the following exceptions for the reasons specified: + +- III.2.1.1 En bloc, subscriber free indication – flow does not include use of reliable provisional response within the SIP-I network +- III.2.1.2 En bloc, early ACM – flow does not include use of reliable provisional response within the SIP-I network +- III.2.1.3 En bloc, early media scenario – flow does not include use of reliable provisional response within the SIP-I network +- III.2.1.4 En bloc, simple segmentation procedures – flow does not include use of reliable provisional response within the SIP-I network +- III.2.1.10 Overlap signalling – 3GPP G-MSC will collect all digits before continuing the call +- III.2.2.1 Backward release during call setup – flow does not include use of reliable provisional response within the SIP-I network + +## 6 Interworking between a SIP-I based circuit-switched core network and a BICC based network + +### 6.1 Reference Model + +Figure 6.1.1 details the interworking reference model for clause 6 of the present specification + +![Figure 6.1.1: interworking reference model diagram. The diagram shows two main entities: 'SIP-I based CS CN' on the left and 'BICC based network, either CS CN or external network' on the right. They are connected via a central box containing two sub-components: 'IWU' (top) and 'UP-IWU' (bottom). The IWU is connected to the SIP-I based CS CN via a dashed line labeled 'SIP-I over Nc'. The UP-IWU is connected to the SIP-I based CS CN via a solid line labeled 'media/ RTP/ UDP/IP/ over Nb'. The IWU is connected to the BICC based network via a dashed line labeled 'BICC'. The UP-IWU is connected to the BICC based network via a solid line labeled 'TDM'. A vertical dashed line labeled 'H.248' connects the IWU and the UP-IWU. A legend at the bottom indicates that solid lines represent the 'User Plane' and dashed lines represent the 'Control Plane'. A light blue shaded area labeled 'Scope Of this TS' encompasses the IWU and UP-IWU components.](b6ad8b32179842fca5ad086cf22b03eb_img.jpg) + +Figure 6.1.1: interworking reference model diagram. The diagram shows two main entities: 'SIP-I based CS CN' on the left and 'BICC based network, either CS CN or external network' on the right. They are connected via a central box containing two sub-components: 'IWU' (top) and 'UP-IWU' (bottom). The IWU is connected to the SIP-I based CS CN via a dashed line labeled 'SIP-I over Nc'. The UP-IWU is connected to the SIP-I based CS CN via a solid line labeled 'media/ RTP/ UDP/IP/ over Nb'. The IWU is connected to the BICC based network via a dashed line labeled 'BICC'. The UP-IWU is connected to the BICC based network via a solid line labeled 'TDM'. A vertical dashed line labeled 'H.248' connects the IWU and the UP-IWU. A legend at the bottom indicates that solid lines represent the 'User Plane' and dashed lines represent the 'Control Plane'. A light blue shaded area labeled 'Scope Of this TS' encompasses the IWU and UP-IWU components. + +NOTE: The IWU is a logical function that may reside with other 3GPP logical functions in the same physical nodes, e.g. in an (G)MSC Server. The figure shows only the logical separation. + +**Figure 6.1.1: interworking reference model** + +**Nb reference point:** The Nb reference point is defined in accordance with 3GPP TS 29.414 [43]. + +**Nc reference point:** The Nc reference point is defined in accordance with 3GPP TS 29.231 [4]. + +## 6.2 Control Plane Interworking + +### 6.2.1 General + +The following subclauses define the signalling interworking between the Bearer Independent Call Control (BICC) protocol (see ITU-T Recommendation Q.1902.1 to Q.1902.6 [8]) and the Session Initiation Protocol (SIP) with its associated Session Description Protocol (SDP) and encapsulated ISUP at an IWU. + +The IWU shall act as a Type A or Type B exchange (ITU-T Recommendation Q.764 [7]) for the purposes of ISUP compatibility procedures. + +The BICC capabilities or signalling information defined for national use are outside the scope of the present document. + +NOTE: An IWU may apply additional procedures to support interworking for national-specific capabilities. + +The services that can be supported through the use of the signalling interworking are limited to the services that are supported both within the BICC based network and the SIP-I based CS CN. The IWU will originate and/or terminate services or capabilities that do not interwork seamlessly across domains according to the relevant protocol recommendation or specification. + +Table 5.2.1 in subclause 5.2 lists the services seamlessly interworked within the scope of the present document. + +The subclause 5.3.2 of ITU-T Recommendation Q.1912.5 [6] describes additional general principles specific to SIP-I. + +The interworking procedures in the subclauses 6.3 and 6.4 are based on ITU-T Recommendation Q.1912.5 [6] profile C. Clarifications are made within this specification on the application of ITU-T Recommendation Q.1912.5 [6] profile C. Specific rules for handling of the APM mechanism have been added, which are not specified in ITU-T Recommendation Q.1912.5 [6]. + +## 6.2.2 Signalling interactions between network entities in the control plane + +The control plane between a SIP-I based CS core networks and a BICC based network, where the underlying signalling transport is either IP or ATM respectively, is shown in figures 6.2.2.1 and 6.2.2.2. + +![Figure 6.2.2.1: Control plane interworking between SIP-I based CS CN and a BICC based network with IP signalling transport. The diagram shows a central 'Interworking Unit' box with two columns of protocol layers. The left column (BICC side) has layers: BICC, STCMTP, M3US, SCTP, and IP. The right column (SIP-I side) has layers: SIP-I, SCTP, and IP. Arrows indicate connections: BICC network to the left BICC layer, IP transport between the left IP layer and the right IP layer, and SIP-I based CS CN to the right SIP-I layer.](132cff7e872feb31f629703959beddd7_img.jpg) + +Figure 6.2.2.1: Control plane interworking between SIP-I based CS CN and a BICC based network with IP signalling transport. The diagram shows a central 'Interworking Unit' box with two columns of protocol layers. The left column (BICC side) has layers: BICC, STCMTP, M3US, SCTP, and IP. The right column (SIP-I side) has layers: SIP-I, SCTP, and IP. Arrows indicate connections: BICC network to the left BICC layer, IP transport between the left IP layer and the right IP layer, and SIP-I based CS CN to the right SIP-I layer. + +**Figure 6.2.2.1: Control plane interworking between SIP-I based CS CN and a BICC based network with IP signalling transport** + +![Figure 6.2.2.2: Control plane interworking between SIP-I based CS CN and a BICC based network with ATM signalling transport. The diagram shows a central 'Interworking Unit' box with two columns of protocol layers. The left column (BICC side) has layers: BICC, STC, MTP3B, SSCF, SSCOP, and AAL5. The right column (SIP-I side) has layers: SIP-I, SCTP, and IP. Arrows indicate connections: BICC network to the left BICC layer, ATM transport between the left AAL5 layer and the right IP layer, and SIP-I based CS CN to the right SIP-I layer.](eb1a67ebd688e354edaacb7ec2abf5ad_img.jpg) + +Figure 6.2.2.2: Control plane interworking between SIP-I based CS CN and a BICC based network with ATM signalling transport. The diagram shows a central 'Interworking Unit' box with two columns of protocol layers. The left column (BICC side) has layers: BICC, STC, MTP3B, SSCF, SSCOP, and AAL5. The right column (SIP-I side) has layers: SIP-I, SCTP, and IP. Arrows indicate connections: BICC network to the left BICC layer, ATM transport between the left AAL5 layer and the right IP layer, and SIP-I based CS CN to the right SIP-I layer. + +**Figure 6.2.2.2: Control plane interworking between SIP-I based CS CN and a BICC based network with ATM signalling transport** + +Signalling between the SIP-I based CS CN and the Interworking Unit uses the services of IP (IETF RFC 791 [14] or IETF RFC 2460 [17]), SCTP (IETF RFC 4960 [18]) and SIP-I. + +## 6.3 Signalling Interworking of a Call from the BICC based network towards the SIP-I based circuit-switched core network + +The procedures in subclause 5.3 shall be applied with the modifications provided in the present subclause. + +The text in subclause 5.3 is to be understood as follows: + +- Where "ISUP" is mentioned, this shall be understood as BICC. As an exception, references to ISUP encapsulated within SIP-I shall be understood without modification, i.e. they still refer to ISUP rather than BICC. + +If an IAM message is received, the APM information elements (see ITU-T Recommendation Q.765 [27]) relating to the BICC APM user (see ITU-T Recommendation Q.765.5 [28]) shall be removed before the IAM message is encapsulated in the triggered SIP INVITE message. + +An APM message received from the CS side (see ITU-T Recommendation Q.765 [27]) that relates to the BICC APM user (see ITU-T Recommendation Q.765.5 [28]) shall not be encapsulated in any triggered SIP message. + +## 6.4 Signalling Interworking of a Call from SIP-I based circuit-switched core network towards the BICC based network + +The procedures in subclause 5.4 shall be applied with the modifications provided in the present subclause. + +The text in subclause 5.4 is to be understood as follows: + +- Where "ISUP" is mentioned, this shall be understood as BICC. As an exception, references to ISUP encapsulated within SIP-I shall be understood without modification, i.e. they still refer to ISUP rather than BICC. + +An APM message received from the BICC side (see ITU-T Recommendation Q.765 [27]) that relates to the BICC APM user (see ITU-T Recommendation Q.765.5 [28]) shall not be encapsulated in any triggered SIP message. + +## 6.5 Supplementary services + +The procedures in subclause 5.5 shall be applied. + +## 6.6 Codec Negotiation between a BICC based network and a SIP-I based circuit-switched core network + +### 6.6.1 General + +The procedures in Annex B of 3GPP TS 29.163 [13] shall be applied with the modifications provided in the following subclauses. + +The text in Annex B of 3GPP TS 29.163 [13] is to be understood as follows: + +- Where "MGCF" is mentioned, this shall be understood as IWU. +- Where "IM-MGW" is mentioned, this shall be understood as UP-IWU. +- Where "IM CN subsystem" is mentioned, this shall be understood as SIP-I based circuit-switched 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]. + +### 6.6.2 Codec Negotiation from SIP-I on Nc to BICC Network + +#### 6.6.2.1 Sending of IAM + +When the IWU receives an initial INVITE request with SDP offer containing a codec list with the 3GPP\_OoBTC\_Indicator, the procedures defined for a 3GPP node terminating SDP offer in clause 9 of 3GPP TS 23.153 [5] shall be applied. The IWU shall follow the procedures of subclause B.2.5 of 3GPP TS 29.163 [13] to create a Supported Codec List for transmission in the outgoing IAM. + +#### 6.6.2.2 Sending of SDP Answer + +When the IWU receives the backward codec information, it shall apply the procedure defined in the subclause B.2.1.2 of 3GPP TS 29.163 [13] and shall create the SDP answer in accordance with the procedures defined for a 3GPP node terminating SDP offer in clause 9 of 3GPP TS 23.153 [5]. + +### 6.6.2.3 Mid-call Codec Negotiation initiated from SIP-I on Nc + +When the mid-call codec negotiation is initiated from the SIP-I based CS CN side the IWU: + +- shall apply the procedures defined for a 3GPP node terminating SDP offer in clause 9 of 3GPP TS 23.153 [5] for the SIP-I based CS CN side, and +- shall apply the procedures from the subclause B.2.3 of 3GPP TS 29.163 [13] for the BICC network side. + +## 6.6.3 Codec Negotiation from BICC Network to SIP-I on Nc + +### 6.6.3.1 Sending of initial SDP Offer + +When the IWU receives an IAM, the IWU shall follow the procedures of subclause B.2.5 of 3GPP TS 29.163 [13] to convert the Supported Codec List from the IAM into an SDP offer for transmission in the outgoing INVITE request. When generating the initial SDP offer, the IWU shall apply the procedures defined for a 3GPP node originating SDP offer in clause 9 of 3GPP TS 23.153 [5]. + +### 6.6.3.2 Responding to Serving Node initiating Codec Negotiation + +When the IWU receives the SDP answer it shall select a codec configuration for the SIP-I based CS CN side in accordance with clause 9 of 3GPP TS 23.153 [5]. For the BICC network side the IWU shall apply the procedure defined in the subclause B.2.2.2 of 3GPP TS 29.163 [13]. + +### 6.6.3.3 Mid-call Codec Negotiation initiated from BICC + +When the mid-call codec negotiation is initiated from the BICC side the IWU: + +- shall apply the procedures from the subclause B.2.4 of 3GPP TS 29.163 [13] for the BICC network side, and +- shall apply the procedures defined for a 3GPP node originating SDP offer in clause 9 of 3GPP TS 23.153 [5] for the SIP-I based CS CN side. + +## 6.7 DMTF Signalling Interworking applicable for all Calls between a BICC network and a SIP-I based circuit-switched core network + +### 6.7.1 General + +DTMF signalling via the RTP telephony-event is mandated to be supported over the Nb interface for SIP-I based Circuit Switched Core Network on Nc Interface, see 3GPP TS 23.231 [3]. However it is an option to use this transmission method when only the default PCM codec selected. + +BICC over Nc supports both inband DTMF and DTMF via OoB signalling within the BICC APM, see 3GPP TS 23.205 [9]. If OoB DTMF is supported then use of OoB DTMF is mandated, see 3GPP TS 23.153 [5]. External BICC networks may also transport DTMF either inband or via OoB signalling within the BICC APM. + +If the usage of the RTP Telephony Event has been negotiated within the SIP-I based CS CN, the IWU shall configure this payload type at the UP-IWU. + +### 6.7.2 DTMF transfer from SIP-I on Nc to BICC network (Out-of-Band DTMF) + +If RTP Telephony Event has been selected for the 3GPP SIP-I CS CN and OoB DTMF transmission is required in the succeeding BICC network the IWU shall use the Detect DTMF procedure to request the MGW to report DTMF Digits as described in subclause 14.4.6 of 3GPP TS 23.231 [3], i.e. RTP Telephony Event is configured in addition to the Detect DTMF Event. An example for the interworking with explicit duration reporting in BICC is shown in figure 6.7.2.1. + +NOTE 1: If the implicit duration is reported via the BICC Out Of Band procedure it can result in the duration being shorter than the original duration of the DTMF received at the MGW and even shorter than the minimum duration required by 3GPP TS 23.014 [24]. + +An example for the interworking with implicit duration reporting in BICC is shown in figure 6.7.2.2. + +NOTE 2: Support of "start of DTMF detection" is optional for the MGW (UP-IWU). + +![Figure 6.7.2.1: DTMF interworking: SIP-I to BICC, explicit duration (message sequence chart).](ddee3e67e0dfc22e25188fa635a19558_img.jpg) + +This sequence diagram illustrates the explicit duration DTMF interworking between an IWU and a UP-IWU over a BICC Network (PLMN or External) to a Server. The process involves two main steps: + +- Step 1:** The IWU detects a DTMF digit via an RTP Tel Event (start DTMF and StopDTMF). It sends a **MOD. Request [RTP Tel Event, Event = EndTone]** (Tx) to the UP-IWU. The UP-IWU responds with a **MOD. Reply** (Tx). Context (Cx) is maintained. +- Step 2:** The IWU sends an **RTP Telephony Event [(Digit), E=bit = 1, Duration = y]** to the UP-IWU. The UP-IWU then sends a **Notify.Request [Report DTMF, end tone, Digit, (duration=y)]** (Tx) to the Server, labeled as **Report DTMF Digit**. The Server responds with **BICC OoB DTMF (Digit (duration=y))**. The UP-IWU also sends a **Notify. Reply** (Tx) to the IWU. Context (Cx) is maintained. + +Figure 6.7.2.1: DTMF interworking: SIP-I to BICC, explicit duration (message sequence chart). + +Figure 6.7.2.1: DTMF interworking: SIP-I to BICC, explicit duration (message sequence chart) + +![Figure 6.7.2.2: DTMF interworking: SIP-I to BICC, implicit duration (message sequence chart).](030c758fd425016b03290c8f11bef69d_img.jpg) + +This sequence diagram illustrates the implicit duration DTMF interworking between an IWU and a UP-IWU over a BICC Network (PLMN or External) to a Server. The process involves three main steps: + +- Step 1:** The IWU detects a DTMF digit via an RTP Tel Event (start DTMF and StopDTMF). It sends a **MOD. Request [RTP Tel Event, Event = StartTone, EndTone]** (Tx) to the UP-IWU. The UP-IWU responds with a **MOD. Reply** (Tx). Context (Cx) is maintained. +- Step 2:** The IWU sends an **RTP Telephony Event [(Digit), E=bit = 0, Duration = x]** to the UP-IWU. The UP-IWU then sends a **Notify.Request [Report DTMF, start tone, Digit]** (Tx) to the Server, labeled as **Report start of DTMF Digit**. The Server responds with **BICC OoB DTMF (Start\_Digit)**. The UP-IWU also sends a **Notify. Reply** (Tx) to the IWU. Context (Cx) is maintained. +- Step 3:** The IWU sends an **RTP Telephony Event [(Digit), E=bit = 1, Duration = y]** to the UP-IWU. The UP-IWU then sends a **Notify.Request [Report DTMF, end tone, Digit]** (Tx) to the Server, labeled as **Report end of DTMF Digit**. The Server responds with **BICC OoB DTMF (Stop\_Digit)**. The UP-IWU also sends a **Notify. Reply** (Tx) to the IWU. Context (Cx) is maintained. + +Figure 6.7.2.2: DTMF interworking: SIP-I to BICC, implicit duration (message sequence chart). + +Figure 6.7.2.2: DTMF interworking: SIP-I to BICC, implicit duration (message sequence chart) + +If RTP Telephony Event has not been selected on 3GPP SIP-I CS CN interface and OoB DTMF is required in the BICC network the IWU shall request inband DTMF detection as described in subclause 14.4.2.1 of 3GPP TS 23.205 [9], i.e. the RTP Telephony Event is not configured. The same principles apply for signalling implicit or explicit DTMF digits. + +### 6.7.3 DTMF transfer from BICC network (Out-of-Band DTMF) to SIP-I on Nc + +If RTP Telephony Event has been selected for the 3GPP SIP-I CS CN and OoB DTMF transmission is selected in the succeeding BICC network the IWU shall use the "Send DTMF" procedure and may use the "Stop DTMF" procedures to request the MGW to play out DTMF to the IM CN subsystem whenever it receives out-of-band DTMF indications from the BICC network. + +The UP-IWU (MGW) shall signal the RTP Telephony event(s) in accordance with subclause 14.4.4 of 3GPP TS 23.231[3]. + +If implicit DTMF timing is deployed (as shown in example message sequence chart in figure 6.7.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. + +![Sequence diagram for DTMF Interworking: BICC to SIP-I, implicit duration. The diagram shows three lifelines: (G)MSC-S, (G)MSC-S, and MGW. The first (G)MSC-S sends a BICC Start DTMF (Digit) message to the second (G)MSC-S. The second (G)MSC-S sends a MOD. Request [RTP Tel Event, signal = Digit] (Tx) to the MGW. The MGW sends a 'Send DTMF Digit via RTP Tel Event, E=0' message to the right. The first (G)MSC-S sends a Stop DTMF (Digit) message to the second (G)MSC-S. The second (G)MSC-S sends a MOD. Request [RTP Tel Event, stop signal = Digit] (Tx) to the MGW. The MGW sends a 'Stop DTMF Digit via RTP Tel Event, E=1' message to the right. Context (Cx) labels are present on the messages between the (G)MSC-S entities.](32ff77da4286b58c4778033acaa10836_img.jpg) + +``` + +sequenceDiagram + participant (G)MSC-S1 as (G)MSC-S + participant (G)MSC-S2 as (G)MSC-S + participant MGW + Note right of (G)MSC-S1: BICC + (G)MSC-S1->>(G)MSC-S2: BICC Start DTMF (Digit) + + Note right of (G)MSC-S2: Context (Cx) + + (G)MSC-S2->>MGW: MOD. Request [RTP Tel Event, signal = Digit] (Tx) + + MGW->>: Send DTMF Digit via RTP Tel Event, E=0 + + (G)MSC-S1->>(G)MSC-S2: Stop DTMF (Digit) + + Note right of (G)MSC-S2: Context (Cx) + + (G)MSC-S2->>MGW: MOD. Request [RTP Tel Event, stop signal = Digit] (Tx) + + MGW->>: Stop DTMF Digit via RTP Tel Event, E=1 + + Note right of (G)MSC-S2: Context (Cx) + +``` + +Sequence diagram for DTMF Interworking: BICC to SIP-I, implicit duration. The diagram shows three lifelines: (G)MSC-S, (G)MSC-S, and MGW. The first (G)MSC-S sends a BICC Start DTMF (Digit) message to the second (G)MSC-S. The second (G)MSC-S sends a MOD. Request [RTP Tel Event, signal = Digit] (Tx) to the MGW. The MGW sends a 'Send DTMF Digit via RTP Tel Event, E=0' message to the right. The first (G)MSC-S sends a Stop DTMF (Digit) message to the second (G)MSC-S. The second (G)MSC-S sends a MOD. Request [RTP Tel Event, stop signal = Digit] (Tx) to the MGW. The MGW sends a 'Stop DTMF Digit via RTP Tel Event, E=1' message to the right. Context (Cx) labels are present on the messages between the (G)MSC-S entities. + +Figure 6.7.3.1: DTMF Interworking: BICC to SIP-I, implicit duration (message sequence chart) + +## 6.7.4 SIP-I on Nc interworking with BICC for Inband DTMF + +The interworking between inband and out-of-band transport shall be performed according to subclause 14.4.8 in 3GPP TS 23.231 [3], if required. + +If the RTP Telephony event has not been negotiated within the SIP-I based CS CN, the interworking MSC towards a BICC network with inband DTMF transport shall not configure the RTP Telephony event at the attached MGW. The MGW will then transfer DTMF within the speech codec without detecting it. + +## 6.8 User Plane Interworking + +### 6.8.1 General + +This subclause describes user plane issues including interworking of DTMF. + +### 6.8.2 DTMF Interworking + +If RTP Telephony Event is selected for the internal 3GPP CS CN connection and inband DTMF is selected for the BICC network the MGW shall filter out (delete) the DTMF from the default PCM codec when relaying the DTMF via the RTP Telephony Event to prevent potential double signalling of the same digit if a later insertion back to inband PCM transmission were to occur. + +## 6.9 Example Call flows + +See subclause 5.7. + +# 7 Interworking between a SIP-I based circuit-switched core network and the IP Multimedia (IM) Core Network (CN) Subsystem + +## 7.1 Reference Model + +### 7.1.1 General + +Figure 7.1.1.1 details the reference model required to support interworking between the 3GPP IM CN subsystem, as specified in 3GPP TS 23.228 [11] and 3GPP TS 24.229 [12] and a SIP-I based circuit-switched core network, as specified in 3GPP TS 23.231 [3] and 3GPP TS 29.231 [4]. + +![Figure 7.1.1.1: IM CN subsystem to CS network logical interworking reference model. The diagram shows the logical interworking between the IM CN subsystem and the CS network. On the left, three boxes (BGCF, CSCF, TrGW) are connected to an MGCF via control plane interfaces (dashed lines) labeled Mj, Mg, and Mn respectively. The MGCF is connected to an IM-MGW via a control plane interface labeled Mn. The IM-MGW is connected to a dashed box labeled (Note 1) via a user plane interface (solid line) labeled Mb. The IM-MGW is also connected to a CS network via a user plane interface labeled Nb. The MGCF is connected to a SIP-I interface via a control plane interface labeled Nc. A legend at the bottom indicates that solid lines represent the User Plane and dashed lines represent the Control Plane.](8e80de0cac529b2c3775d677c5203133_img.jpg) + +Figure 7.1.1.1: IM CN subsystem to CS network logical interworking reference model. The diagram shows the logical interworking between the IM CN subsystem and the CS network. On the left, three boxes (BGCF, CSCF, TrGW) are connected to an MGCF via control plane interfaces (dashed lines) labeled Mj, Mg, and Mn respectively. The MGCF is connected to an IM-MGW via a control plane interface labeled Mn. The IM-MGW is connected to a dashed box labeled (Note 1) via a user plane interface (solid line) labeled Mb. The IM-MGW is also connected to a CS network via a user plane interface labeled Nb. The MGCF is connected to a SIP-I interface via a control plane interface labeled Nc. A legend at the bottom indicates that solid lines represent the User Plane and dashed lines represent the Control Plane. + +NOTE 1: The IM-MGW may be connected via the Mb to various network entities, such as a UE (via a GTP Tunnel to a GGSN), an MRFP, or an application server. + +**Figure 7.1.1.1: IM CN subsystem to CS network logical interworking reference model** + +**Nb reference point:** The Nb reference point is defined in accordance with 3GPP TS 29.414 [43]. + +**Nc reference point:** The Nc reference point is defined in accordance with 3GPP TS 29.231 [4]. + +**Mg reference point:** The Mg reference point is defined in accordance with 3GPP TS 24.229 [12]. + +**Mj reference point:** The Mj reference point is defined in accordance with 3GPP TS 24.229 [12]. + +**Mb reference point:** The Mb reference point is defined in accordance with 3GPP TS 23.002 [2]. + +**Mn reference point:** The Mn reference point is defined in accordance with 3GPP TS 29.332 [54]. + +## 7.1.2 Signalling interactions between network entities in the control plane + +The control plane between the IM CN Subsystem supporting SIP and a 3GPP CS network supporting a SIP-I based Nc interface is as shown in figure 7.1.2. + +![Figure 7.1.2.1: Control plane interworking protocol stack between the IM CN subsystem and a 3GPP CS network supporting SIP-I based Nc interface. The diagram shows the protocol stack for the control plane. On the left, the 3GPP IMS DOMAIN contains a SIP signalling function. In the center, the MGCF contains SIP, TCP/UDP/SCTP, and IP layers. On the right, the 3GPP CS DOMAIN contains a SIP-I signalling function. The MGCF is connected to the SIP signalling function via IMS-SIP and IP interfaces. The MGCF is also connected to the SIP-I signalling function via SIP-I/Nc and IP interfaces. The MGCF's SIP layer is connected to the SIP-I layer via SIP-I. The MGCF's TCP/UDP/SCTP layer is connected to the SCTP layer via SCTP. The MGCF's IP layer is connected to the IP layer via IP.](08e8bbb2a063a3935a0c649b39ade125_img.jpg) + +Figure 7.1.2.1: Control plane interworking protocol stack between the IM CN subsystem and a 3GPP CS network supporting SIP-I based Nc interface. The diagram shows the protocol stack for the control plane. On the left, the 3GPP IMS DOMAIN contains a SIP signalling function. In the center, the MGCF contains SIP, TCP/UDP/SCTP, and IP layers. On the right, the 3GPP CS DOMAIN contains a SIP-I signalling function. The MGCF is connected to the SIP signalling function via IMS-SIP and IP interfaces. The MGCF is also connected to the SIP-I signalling function via SIP-I/Nc and IP interfaces. The MGCF's SIP layer is connected to the SIP-I layer via SIP-I. The MGCF's TCP/UDP/SCTP layer is connected to the SCTP layer via SCTP. The MGCF's IP layer is connected to the IP layer via IP. + +**Figure 7.1.2.1: Control plane interworking protocol stack between the IM CN subsystem and a 3GPP CS network supporting SIP-I based Nc interface** + +Signalling between the SIP signalling function and the MGCF uses the services of IP (RFC 2460 [17]), and transport protocol such as TCP (RFC 793 [16]) or UDP (RFC 768 [15]) or SCTP (RFC 4960 [18]) (see 3GPP TS 24.229 [12]), and SIP. + +Signalling between the SIP-I signalling function and the MGCF uses the services of IP (IETF RFC 791 [14] or IETF RFC 2460 [17]), SCTP (IETF RFC 4960 [18]) and SIP-I. + +## 7.2 Signalling Interworking of a Call from the IP Multimedia Subsystem towards the SIP-I based circuit-switched core network + +### 7.2.1 General + +If not otherwise stated within this subclause the MGCF shall follow the below listed procedures for interworking incoming SIP calls: + +Sending SIP messages to the succeeding SIP-I based circuit-switched core network: + +- When an incoming SIP message is received from the preceding IMS node then the MGCF shall send this SIP message to the succeeding SIP-I based circuit-switched core network unless otherwise specified in the subclauses below. +- The MGCF shall only send SIP methods, SIP headers, SDP body contents and other bodies as permitted by the profile for SIP-I on Nc as defined in 3GPP TS 29.231 [4]. +- The MGCF shall, if defined by 3GPP TS 29.163 [13], generate an ISUP message following 3GPP TS 29.163 [13] and include this ISUP message into the SIP message in a MIME body according to IETF RFC 3204 [19]. The Content-Type header field and the Content-Disposition header field shall be set as specified in subclause 5.4.1.2 of ITU-T Recommendation Q.1912.5 [6]. + +Sending SIP messages to the preceding IMS node: + +- When the MGCF receives a SIP-I message from the succeeding SIP-I based circuit-switched core network then the MGCF shall send this message to the preceding IMS node unless otherwise specified in the subclauses below. +- The MGCF shall only send SIP methods, SIP headers, SDP body contents and other bodies which are permitted by the IMS profile as defined in 3GPP TS 24.229 [12]. +- The MGCF shall construct IMS specific headers and bodies according to the procedures defined in 3GPP TS 29.163 [13]. + +### 7.2.2 Exceptions from forwarding received SIP messages + +If call clearing is initiated either from the preceding IMS network or from the succeeding SIP-I based circuit switched core network then the MGCF shall apply the call clearing procedures as defined within 3GPP TS 23.231 [3] subclause 7.3.1. + +When a BYE request, 4xx, 5xx or 6xx final response to an initial INVITE request is received from the succeeding SIP-I based circuit switched core network and if a Reason Header field was not received and encapsulated ISUP REL message is included, then the ISUP Cause value received in the encapsulated ISUP REL message shall be mapped into SIP Reason header fields as specified in 3GPP TS 29.163 [13]. If SIP message did not contain neither a Reason header nor encapsulated ISUP REL message, then a 4xx, 5xx, or 6xx final response shall be mapped to an ISUP cause value as specified in 3GPP TS 29.163 [13] table 18 or BYE request shall be mapped to cause value 16; this cause value shall be mapped into the SIP Reason header fields as specified in 3GPP TS 29.163[13]. + +When a SIP failure response to an initial INVITE request is to be sent to the preceding IMS node, the cause value contained in the Reason header to be sent shall be used to determine the SIP failure response code as specified in 3GPP TS 29.163 [13] table 9. + +If different SIP methods are used within the SIP-I based circuit switched core network and within the IMS network for basic call signalling or supplementary service signalling, then the MGCF shall map the received SIP message into the appropriate SIP message of the network the message is sent to. + +If the interworking procedures within 3GPP TS 29.163 [13] do not result in any mapping then the MGCF shall not send the SIP message, which is received either from the SIP-I based circuit switched core network or from the IMS network, towards the other side. + +If the MGCF supports overlap signalling from the preceding IMS node and the first incoming SIP INVITE request does not provide a complete number, then the MGCF shall not forward this first SIP INVITE request and additional SIP + +INVITE requests or SIP INFO requests, which are used by the MGCF to collect all digits required to identify the called subscriber. + +The MGCF shall generate 100 Trying provisional SIP responses to acknowledge the receipt of INVITE requests. The MGCF shall not forward received 100 Trying provisional SIP responses. + +### 7.2.3 Sending SIP INVITE request + +The MGCF may reject receipt of SIP INVITE without SDP offer. Otherwise the MGCF shall construct an SDP offer with contents according to local policy, e.g. SDP for a G.711 speech call, in accordance with the built encapsulated IAM message. In the constructed SDP offer the MGCF shall encode preconditions as not met. + +NOTE 1: A SIP-I INVITE always includes an SDP offer within the CS CN. + +The MGCF shall forward the SIP INVITE request with the SDP offer and encapsulate an IAM message after the reception of the SIP INVITE request irrespective of the status of local and remote preconditions: + +When the incoming SIP INVITE request indicates that remote preconditions are not met or when local preconditions are not met then the MGCF shall include the tag "precondition" in the SUPPORTED header and shall encode preconditions in the SDP offer that the related local preconditions for QoS are not met. + +If the incoming SIP INVITE request indicates that remote preconditions are met, or if the incoming SIP INVITE request does not contain a precondition tag, and if local preconditions are met then the MGCF may either not include the tag "precondition" and exclude appropriate SDP lines, or include the tag "preconditions" in the SUPPORTED header and provide an SDP offer indicating that preconditions are met. + +NOTE 2: The use of SUPPORTED header is a deviation from IETF RFC 3312 [23] when the strength-tag contains a "mandatory" value. + +NOTE 3: The setting of the "Continuity Check Indicator" in the "Nature of Connection Indicators" parameter within the encapsulated IAM is of no significance. The value is ignored by the succeeding node of the SIP-I based circuit-switched core network. + +The MGCF shall not use the MGW bypass option, because some functions will not work as the succeeding SIP-I node does not know that it is interworking any IMS function. For example an incoming multimedia call from IMS does not result in a CS multimedia telephony service on the SIP-I based circuit switched core network. + +If the incoming SIP INVITE request does not provide a complete number, then the MGCF shall defer sending the SIP INVITE request until the MGCF has collected all digits required to identify the called subscriber. The additional digits may either, as a network option, be received in in-dialog SIP INFO requests or in additional SIP INVITE requests with the same Call-ID and From tag as a previous SIP INVITE. The MGCF shall apply the signalling procedures on the IMS side as specified in 3GPP TS 29.163 [13]. + +### 7.2.4 Updating Precondition Information + +If the MGCF previously indicated to the succeeding SIP-I based circuit-switched core network that preconditions were not met, the MGCF shall send to the succeeding SIP-I based circuit-switched core network appropriate SDP lines indicating that local preconditions are met + +- when the MGCF receives from the preceding IMS network SDP indication that preconditions are met and local preconditions are met, +- or when remote preconditions at the preceding IMS network were already met and local precondition status of the MGCF changes to be met. + +NOTE: ISUP COT is not supported within SIP-I on Nc and therefore the ISUP COT message shall not be included into the SIP message. + +### 7.2.5 SDP Codec Negotiation + +When sending an SDP offer/answer to negotiate codecs with the succeeding SIP-I based circuit-switched core network the MGCF shall follow the procedures defined for a 3GPP Intermediate Node in clause 9 of 3GPP TS 23.153 [5]. + +When sending an SDP offer/answer to negotiate codecs with the preceding IMS network the MGCF shall send codec information in accordance to 3GPP TS 24.229 [12]. + +NOTE 1: Which codecs are negotiable with the IMS network may depend on operator choices and preferences (local policy). + +## 7.2.6 MGW Selection + +If the MGCF supports either the optional "Optimised MGW Selection" or the optional "Deferred MGW Selection" then the MGCF may include the SDP MGW Identifier into the SIP message being sent to the succeeding SIP-I based circuit switched core network in accordance to subclause 4.4 of 3GPP TS 23.231 [3]. + +Otherwise the MGCF shall seize a MGW and shall include the MGW connection address into the SDP offer of the initial SIP INVITE request it will send to the succeeding 3GPP SIP-I based circuit switched core network node. + +## 7.2.7 Autonomous Release + +For interworking towards the preceding IMS node the MGCF shall use the procedure as defined in 3GPP TS 29.163 [13]. + +For call clearing towards the succeeding SIP-I based circuit switched core network the MGCF shall use the procedures as defined within 3GPP TS 23.231[3] subclause 7.3. + +## 7.2.8 Further setting of SIP header values + +The MGCF shall act as a B2BUA as defined in IETF RFC 3261 [20]. The MGCF shall terminate the incoming SIP session and the MGCF shall originate an outgoing SIP-I call towards the SIP-I based circuit switched core network. Therefore the MGCF shall generate the SIP headers and values of Cseq, Call-ID, Via, Record-Route, Route and Contact independently from the received SIP message. For the generation of the Request-URI of an initial INVITE request and header fields To, From, Max-Forwards, and P-Asserted-Identity the MGCF shall use the information received from the preceding IMS node and perform the procedures specified below. + +The Request-URI of in-dialogue SIP requests will be populated with information received within the Contact header of previous responses according to SIP procedures. When sending a request towards the SIP-I based circuit switched core network the MGCF shall generate a From tag independent of the value received from the IMS. Furthermore, when sending a response towards the IMS, the MGCF shall generate a To tag independent of the value received from the SIP-I based circuit switched core network. + +The procedures for population of the Request-URI and header fields To, From, Max-Forwards, and P-Asserted-Identity are based on the mapping procedures specified in 3GPP TS 29.163 [13]. The text in 3GPP TS 29.163 [13] is to be understood as follows: + +- Where ISUP called party number is mentioned, this shall be understood as internal ISUP called party number. +- Where ISUP calling party number is mentioned, this shall be understood as internal ISUP calling party number. +- Where ISUP Generic Number (additional calling party number) is mentioned, this shall be understood as internal Generic Number (additional calling party number). +- Where ISUP Hop Counter parameter is mentioned, this shall be understood as internal ISUP Hop Counter parameter. + +NOTE: Only the userinfo component of the received SIP URI is used by mapping procedures according to 3GPP TS 29.163 [13] while the received host part is ignored and a new value is generated by the MGCF. + +When sending an initial INVITE request towards the SIP-I based circuit switched core network the MGCF shall perform the following actions to generate the Request-URI and the To header field: + +- Create an internal ISUP called party number from the received Request URI according to 3GPP TS 29.163 [13]. When Number Portability is supported the MGCF shall follow the procedures specified in subclause 7.2.3.1.2A of 3GPP TS 29.163 [13]. Otherwise the ISUP called party number is generated as specified in subclause 7.2.3.1.2.1 of 3GPP TS 29.163 [13]. +- Generate the new Request-URI and the new To header field from the internal ISUP called party number according to 3GPP TS 29.163 [13]. +When Number Portability is supported the MGCF shall follow the procedures specified in subclause 7.2.3.2.2A + +of 3GPP TS 29.163 [13]. Otherwise the Request-URI and the To header field are generated as specified in subclause 7.2.3.2.2.1 of 3GPP TS 29.163 [13]. + +When sending an initial INVITE request towards the SIP-I based circuit switched core network the MGCF shall perform the following actions to generate the P-Asserted-Identity and the From header fields: + +- create an internal ISUP calling party number and an internal Generic Number (additional calling party number) as specified in subclauses 7.2.3.1.2.6 and 7.2.3.1.2.7 of 3GPP TS 29.163 [13]; and +- generate the new P-Asserted-Identity and the From header from the internal ISUP calling party number and the internal Generic Number (additional calling party number) as specified in subclause 7.2.3.2.2.3 of 3GPP TS 29.163 [13]. + +When sending the initial SIP INVITE request to the SIP-I based circuit-switched core network and if the Hop Counter procedure is supported in the SIP-I based circuit switched core network (national option), then the MGCF shall perform the following actions: + +- create an internal ISUP Hop Counter parameter from the received Max-Forwards value according to subclause 7.2.3.1.2.9 of 3GPP TS 29.163 [13]; and +- either generate the new Max-Forwards value from the internal ISUP Hop Counter parameter by applying the rules in subclause 7.2.3.2.2.4 of 3GPP TS 29.163 [13] and decrementing the resulting value by one or forward the received Max-Forwards value decremented by one. + +Otherwise if the MGCF forwards SIP request, it shall either set the Max-Forwards header to a default value or forward the received Max-Forwards value decremented by one. + +When receiving any SIP request with a Max-Forwards field value of zero, and if request shall be propagated to the other side, the MGCF shall reject the request with a 483 (Too Many Hops) SIP final response, in accordance with IETF RFC 3261 [20]. + +## 7.3 Signalling Interworking of a Call from SIP-I based circuit-switched core network towards the IP Multimedia Subsystem + +### 7.3.1 General + +If not otherwise stated within this subclause the MGCF shall follow the below listed procedures for interworking outgoing SIP calls: + +Sending SIP messages to the succeeding IMS node: + +- When the MGCF receives a SIP-I message from the preceding SIP-I based circuit-switched core network then the MGCF shall send this message to the succeeding IMS network unless otherwise specified in the subclauses below. +- The MGCF shall only send SIP methods, SIP headers, SDP body contents and other bodies which are permitted by the IMS profile as defined in 3GPP TS 24.229 [12]. +- The MGCF shall construct IMS specific headers and bodies according to the procedures defined in 3GPP TS 29.163 [13]. + +NOTE 1: This implies that if the incoming SIP-I message contained an encapsulated ISUP message then the ISUP message is removed from the forwarded SIP message. But the ISUP information may be mapped into a PSTN XML body, if supported as a network option. + +- Within IMS the initial INVITE request may be routed to a forking proxy. The MGCF shall be ready to receive responses generated due to a forked request and behave according to the procedures specified in IETF RFC 3261 [20] and subclause 7.3.9 of the present specification. + +NOTE 2: The multiple early dialogues are not propagated to the preceding SIP-I based circuit-switched core network. + +NOTE 3: The MGCF does not, itself, perform forking. + +Sending SIP messages to the preceding SIP-I based circuit switched core network: + +- When the MGCF receives a SIP message from the succeeding IMS node then the MGCF shall send this SIP message to the preceding SIP-I based circuit-switched core network unless otherwise specified in the subclauses below. +- The MGCF shall only send SIP methods, SIP headers, SDP body contents and other bodies as permitted by the profile for SIP-I on Nc as defined in 3GPP TS 29.231 [4]. +- The MGCF shall, if defined by 3GPP TS 29.163 [13], construct an ISUP message following 3GPP TS 29.163 [13] and include this ISUP message into the SIP message in a MIME body according to IETF RFC 3204 [19]. The Content-Type header field and the Content-Disposition header field shall be set as specified in subclause 5.4.1.2 of ITU-T Recommendation Q.19.12.5 [6]. +- When sending an encapsulated ISUP ACM message or ISUP CPG message the MGCF shall follow the procedures defined within 3GPP TS 29.163 [13] for the handling of the ring tone and therefore may request the IM-MGW to send ring tone in the backwards direction. + +### 7.3.2 Exceptions from forwarding received SIP messages + +If call clearing is initiated either from the succeeding IMS node or from the preceding SIP-I based circuit switched core network then the MGCF shall apply the call clearing procedures as defined within 3GPP TS 23.231[3] subclause 7.3.1. + +When a BYE request is sent to the succeeding IMS node and if a Reason Header field was not received, then the received ISUP Cause value being received in the encapsulated ISUP REL message shall be mapped into SIP Reason header fields as defined by 3GPP TS 29.163 [13]. + +When a BYE request, 4xx, 5xx or 6xx final response to an initial INVITE request is received from the succeeding IMS Node and the SIP message did not contain a Reason header, then a 4xx, 5xx, or 6xx final response shall be mapped to an ISUP cause value as specified in 3GPP TS 29.163 [13] table 18 or BYE shall be mapped to cause value 16; this cause value shall be included in the encapsulated ISUP REL messages as specified in 3GPP TS 29.163[13]. + +When a SIP failure response to an initial INVITE request is to be sent to the preceding SIP-I node, the cause value contained in the encapsulated ISUP REL message to be sent shall be used to determine the SIP failure response code as specified in 3GPP TS 29.163 [13] table 9. + +If different SIP methods are used within the SIP-I based circuit switched core network and within the IMS network for basic call signalling or supplementary service signalling, then the MGCF shall map the received SIP message into the appropriate SIP message of the network the message is sent to. + +The MGCF shall modify the SDP it forwards to include local address information from the IM-MGW and to adjust the codec information if the IM-MGW is configured to transcode. + +The MGCF shall not forward the received 100 Trying provisional SIP responses, and shall generate 100 Trying provisional SIP responses to acknowledge the receipt of INVITE requests. + +If the MGCF defers sending an INVITE request until preconditions are met (see subclause 7.6.3.1), the MGCF shall reply to the INVITE request from the SIP-I based CS CN with a 183 Session Progress provisional response and shall not forward the subsequent PRACK and UPDATE requests from the SIP-I based CS CN, but reply with a final response to the received request. When the MGCF then receives from the preceding SIP-I based circuit-switched core network an SDP indication that preconditions are met and local preconditions are met, the MGCF shall forward to the succeeding IMS node the previously received INVITE request with appropriate SDP lines indicating that local preconditions are met. If MGCF then receives a 183 Session Progress provisional response, it shall either: + +- not forward this provisional response and acknowledge the receipt with a PRACK request toward the IMS; or +- if defined by 3GPP TS 29.163 [13], construct an ISUP message and include this ISUP message into the 183 Session Progress provisional response in a MIME body and remove the SDP answer from the 183 Session Progress provisional response and forward it toward the SIP-I based CS CN. + +### 7.3.3 Sending SIP INVITE request + +When the MGCF receives an incoming SIP INVITE request the MGCF shall ignore the value of the Continuity Check indicator in the Nature of Connection Indicators parameter in the included IAM. If the incoming SIP INVITE request + +indicates that remote preconditions are not met or when local preconditions are not met then the MGCF should defer sending the INVITE request until remote and local preconditions are met. + +NOTE: This recommendation follows 3GPP TS 29.163 [13] to avoid clipping and other obstacles, when the receiving IMS terminal does not support SIP preconditions and the SIP UPDATE method. + +As an option, instead of following the above procedure, the MGCF may include the tag "precondition" in the SUPPORTED header and encode preconditions in the SDP offer that the related local preconditions for QoS are not met. + +### 7.3.4 Updating Precondition Information + +If the MGCF previously indicated to the succeeding IMS node that preconditions were not met and a provisional response from the succeeding node indicated support for preconditions, then the MGCF shall send to the succeeding IMS node appropriate SDP lines indicating that local preconditions are met + +- when the MGCF receives from the preceding SIP-I based circuit-switched core network an SDP indication that preconditions are met and local preconditions are met, +- or when remote preconditions at the preceding SIP-I based circuit-switched core network were already met and local precondition status of the MGCF changes to be met. + +For each early SIP dialogue for which a provisional response has been received from the succeeding node indicating support for preconditions the MGCF, using an UPDATE or a PRACK request, shall send a confirmation that all the required preconditions have been met. This applies regardless of whether the early SIP dialogue existed prior to the preconditions being met or is subsequently created. The MGCF shall not interwork more than one 200 OK response to an UPDATE request sent in multiple early dialogues, and should select the 200 OK response for the early dialogue for which the resources at the IM-MGW are configured (see subclause 7.3.9.2) for interworking. + +A 580 Precondition Failure response might be received from the succeeding IMS node as a response either to the INVITE request, to the UPDATE request or to the PRACK request. All early dialogues are considered terminated upon reception of the 580 Precondition Failure response to the INVITE request. The MGCF shall release the call in accordance with 3GPP TS 29.163 [13], which also defines the coding of the REL message with Cause Code '127 Interworking' to be sent to the SIP-I based circuit-switched core network. The MGCF shall encapsulate the REL message into the 500 Server Internal Error response and send it to the SIP-I based circuit-switched 3GPP core network. + +Upon reception of the 580 Precondition Failure response to the UPDATE or to the PRACK request within early dialogue MGCF shall immediately send a BYE request to terminate this early dialogue. Only if there is no more early dialogues, the MGCF shall encapsulate the REL message with Cause Code '127 Interworking' into the 500 Server Internal Error response and send it to the SIP-I based circuit-switched 3GPP core network. + +### 7.3.5 Receipt of SIP redirect (3xx) response + +When receiving a SIP response with a response code 3xx, the default behaviour of the MGCF is to release the call, where the MGCF sends to the preceding SIP-I based circuit-switched core network 480 Temporarily unavailable and encapsulate an ISUP REL message with a cause code value 127 (Interworking unspecified). + +NOTE 1: The MGCF may also decide for example to redirect the call towards the URIs in the Contact header field of the response as an operator option, but such handling is outside of the scope of the present document. + +NOTE 2: Above default behaviour and Note 1 is adopted from 3GPP TS 29.163 [13]. + +### 7.3.6 SDP Codec Negotiation + +When sending an SDP offer/answer to negotiate codecs with the succeeding IMS network the MGCF shall send codec information in accordance with 3GPP TS 24.229 [12]. + +When sending an SDP offer/answer to negotiate codecs with the preceding SIP-I based circuit-switched core network the MGCF shall follow the procedures defined for a 3GPP Intermediate Node in clause 9 of 3GPP TS 23.153 [5]. + +NOTE: Which codecs are negotiable with the IMS network may depend on operator choices and preferences (local policy). + +If the MGCF received an SDP answer without the OoBTC Indicator and multiple codecs from the IMS, and initiates a second offer toward the IMS in accordance with the procedures for a 3GPP Intermediate Node in clause 9 of 3GPP TS 23.153 [5], the MGCF shall: + +- if it added the SDP offer to a SIP message received from the SIP-I based CS CN (e.g. a PRACK), remove the SDP answer from the corresponding response before sending it to the SIP-I based CS CN; and +- if it created a new SIP message (e.g. UPDATE or re-INVITE) to send the SDP offer to the IMS, not forward the SIP message with the SDP answer (e.g. a 200 OK) to the SIP-I based CS CN. + +If the MGCF receives from the IMS due to forking for one SDP offer multiple SDP answers in provisional SIP responses of different early dialogues, the MGCF shall only interwork the first SDP answer and the MGCF shall not include any SDP answers in any subsequent SIP early responses it decides to forward. + +If the MGCF sends an SDP offer within multiple UPDATE requests for different early dialogues towards the IMS side, it will receive an SDP answer in the response to each UPDATE request and the MGCF shall not interwork more than one 200 OK response to an UPDATE request sent in multiple early dialogues, and should select the 200 OK response for the early dialogue for which the resources at the IM-MGW are configured (see subclause 7.3.9.2) for interworking. + +### 7.3.7 MGW Selection + +If the MGCF supports either the optional "Optimised MGW Selection" or the optional "Deferred MGW Selection" then the MGCF shall not send a SDP MGW Identifier towards the succeeding IMS network. The MGCF shall seize an IM-MGW and shall then include the connection address in the SDP offer of the initial SIP INVITE request it will send to the succeeding IMS node. + +If the MGCF supports the optional "deferred MGW selection" procedure and receives an unspecified connection address in the SDP offer contained in the SIP INVITE request, it should include an MGW\_Identifier for the IM-MGW it selects in the corresponding answer. The encoding of the MGW\_Identifier is defined in 3GPP TS 29.231[4]. + +The MGCF shall not use the "MGW bypass" option. + +### 7.3.8 Autonomous Release + +For interworking towards the succeeding IMS node the MGCF shall use the procedure as defined in 3GPP TS 29.163 [13]. + +For call clearing towards the preceding SIP-I based circuit switched core network the MGCF shall use the procedures as defined within 3GPP TS 23.231[3] subclause 7.3 for call clearing towards the originating side. + +### 7.3.9 Handling of forked SIP Responses + +#### 7.3.9.1 SIP Dialogues + +The MGCF shall inspect the tag in the 'To' header field of a non-100 provisional and a 2xx final responses in accordance to SIP procedures specified in IETF RFC 3261 [20] to identify the SIP dialogue the response belongs to. If responses belonging to different dialogues are received, the initial INVITE request has been forked. + +#### 7.3.9.2 Reception of non-100 provisional Responses to initial INVITE + +Since the MGCF does not know that forking has occurred until a second non-100 provisional response creating a new early dialogue arrives the MGCF shall request the bearer resources as required by the first received SDP answer. + +For each subsequent non-100 provisional response within a new early dialogue that is received, the MGCF shall apply the following procedures: + +- Depending on the requirements in the SDP answer and the presence of P-Early-Media header the MGCF may either refrain from reconfiguring the IM-MGW, or it may use the Configure IMS Resources procedure. +- The MGCF shall construct an ISUP message in accordance to 3GPP TS 29.163 [13], and send it within the SIP message to the SIP-I based circuit-switched 3GPP core network. The MGCF shall use only one SIP dialogue within the SIP-I based circuit-switched 3GPP core network, and the MGCF shall thus supply the same 'To' header field in all SIP responses relating to a call it sends towards the SIP-I based circuit-switched 3GPP core network. + +- However, the MGCF may refrain from sending additional subsequent non-100 provisional response to the SIP-I based CS CN if they do not contain any new information compared to the last previous non-100 provisional response it sent towards the SIP-I based CS CN. +- If the MGCF already received an SDP answer in a previous non-100 provisional response within another early dialogue (and thus forwarded the SDP answer), the MGCF shall not include the SDP answers in any subsequent non-100 provisional response it decides to send towards the SIP-I based CS CN. +- The MGCF shall send a PRACK request to the IMS to acknowledge the receipt of the subsequent non-100 provisional response. The MGCF will receive a response to the PRACK and shall not forward this response to the SIP-I based CS CN. +- If multiple codecs were contained in the provisional response, the MGCF shall include an SDP offer with the codec configured at the IM-MGW within the PRACK request. + +### 7.3.9.3 Reception of final Responses to initial INVITE + +Upon reception of a non-2xx final response to initial INVITE all early dialogues are considered terminated. The MGCF shall acknowledge it with an ACK request. In addition the MGCF shall create an encapsulated REL message as described in 3GPP TS 29.163 [13] and shall send it within a non-2xx final response (initial INVITE) to the SIP-I based circuit-switched 3GPP core network. + +When a first 2xx final response is received for one of the early dialogues or when a received 2xx final response to an INVITE creates a new dialogue, the MGCF shall acknowledge it with the ACK request. If the remote IMS resources configured at the IM-MGW do not match the remote resources selected for the confirmed dialogue MGCF shall require updating the allocated resources. In addition the MGCF shall create an encapsulated ANM or CON message as described in 3GPP TS 29.163 [13] and shall send it within a final 200 OK response to the initial INVITE to the SIP-I based circuit-switched 3GPP core network. If the previously negotiated codecs in the SIP-I based CS CN differ from the remote resources selected for the confirmed dialogue, to avoid transcoding the MGCF should construct a new SDP offer based upon those remote resources and send it to the SIP-I based CS CN within an UPDATE or re-INVITE request. + +Upon the reception of a subsequent final 2xx response for any further dialogue for an INVITE request due to forking, the MGCF shall: + +- 1) acknowledge the response with the ACK request; and +- 2) send a BYE request to this dialogue in order to terminate it. + +The INVITE transaction is completed 64\*T1 seconds after the reception of the first 2xx response. At this point the MGCF shall terminate all early dialogs that have not been already transitioned to confirmed or terminated state. + +### 7.3.10 Further setting of SIP header values + +The MGCF shall act as a B2BUA as defined in IETF RFC 3261 [20]. The MGCF shall terminate the incoming SIP-I session and the MGCF shall originate an outgoing SIP session towards the succeeding IMS node. Therefore the MGCF shall generate the SIP headers and values of Cseq, Call-ID, Via, Record-Route, Route and Contact independently from the received SIP-I message. For the generation of the Request-URI of an initial INVITE requests and header fields To, From, Max-Forwards, and P-Asserted-Identity the MGCF shall use the information received from the SIP-I based circuit switched core network node and perform the procedures specified below. + +The Request-URI of in-dialogue SIP requests will be populated with information received within the Contact header of previous responses according to SIP procedures. When sending a request towards the IMS the MGCF shall generate a From tag independent of the value received from the SIP-I based circuit switched core network. Furthermore, when sending a response towards the SIP-I based circuit switched core network, the MGCF shall generate a To tag independent of the value received from the IMS. + +The procedures for population of the Request-URI and header fields To, From, Max-Forwards, and P-Asserted-Identity are based on the mapping procedures specified in 3GPP TS 29.163 [13]. The text in 3GPP TS 29.163 [13] is to be understood as follows: + +- Where ISUP called party number is mentioned, this shall be understood as internal ISUP called party number. +- Where ISUP calling party number is mentioned, this shall be understood as internal ISUP calling party number. + +- Where ISUP Generic Number (additional calling party number) is mentioned, this shall be understood as internal ISUP Generic Number (additional calling party number). + +NOTE: Only the userinfo component of the received SIP URI is used by mapping procedures according to 3GPP TS 29.163 [13] while the received host part is ignored and a new value is generated by the MGCF. + +When sending an initial INVITE request towards the IMS network the MGCF shall perform the following actions to generate the Request-URI and the To header field: + +- Create an internal ISUP called party number from the received Request URI according to 3GPP TS 29.163 [13]. When Number Portability is supported the MGCF shall follow the procedures specified in subclause 7.2.3.1.2A of 3GPP TS 29.163 [13]. Otherwise the internal ISUP called party number is generated as specified in subclause 7.2.3.1.2.1 of 3GPP TS 29.163 [13]. +- Generate the new Request-URI and the new To header field from the internal ISUP called party number according to 3GPP TS 29.163 [13]. When Number Portability is supported the MGCF shall follow the procedures specified in subclause 7.2.3.2.2A of 3GPP TS 29.163 [13]. Otherwise the Request-URI and the To header field are generated as specified in subclause 7.2.3.2.2.1 of 3GPP TS 29.163 [13]. + +When sending an initial INVITE request towards the IMS network the MGCF shall perform the following actions to generate the P-Asserted-Identity and the From header fields: + +- create an internal ISUP calling party number and an internal Generic Number (additional calling party number) as specified in subclauses 7.2.3.1.2.6 and 7.2.3.1.2.7 of 3GPP TS 29.163 [13]; and +- generate the new P-Asserted-Identity and the From header from the internal ISUP calling party number and the internal Generic Number (additional calling party number) as specified in subclause 7.2.3.2.2.3 of 3GPP TS 29.163 [13]. + +When sending the initial SIP INVITE request to the IMS network and if the Hop Counter procedure is supported in the SIP-I based circuit switched core network (national option), then the MGCF shall either generate the Max-Forwards value from the received ISUP Hop Counter parameter by applying the rules in subclause 7.2.3.2.2.4 of 3GPP TS 29.163 [13] and decrementing the resulting value by one or forward the received Max-Forwards value decremented by one. + +Otherwise if the MGCF forwards SIP request, it shall either set the Max-Forwards header to a default value or forward the received Max-Forwards value decremented by one. + +When receiving any SIP request with a Max-Forwards field value of zero, and if request shall be propagated to the other side, the MGCF shall reject the request with a 483 (Too Many Hops) SIP final response, in accordance with IETF RFC 3261 [20]. + +## 7.4 DMTF Signalling Interworking applicable for all Calls between an IP Multimedia CN Subsystem and a SIP-I based circuit-switched core network + +The procedures in subclause 4.4 are applicable with modifications described in the present subclause. + +Where the external SIP-I network is mentioned in the procedures in subclause 4.4, this shall be understood as IP Multimedia (IM) Core Network (CN) Subsystem. Where an "IWU" is mentioned in those procedures, this shall be understood as MGCF. + +The IMS need not include the PCM codec in SDP offers and answers it sends. + +However, it is assumed that the RTP Telephony Event will always be included in SDP offers and answers from the IMS. + +If an IWU receives an SDP offer from a preceding 3GPP SIP-I node without the RTP Telephony Event (only permitted if only default PCM codec offered) then it shall include the RTP Telephony Event in the subsequent offer to the IMS. + +Procedures in subclause 4.4 related to receiving SDP offers or answers from the external network without the RTP Telephony Event do not apply for the interworking towards the IMS. + +## 7.5 User Plane Interworking + +### 7.5.1 General + +This subclause describes user plane issues including interworking of DTMF. + +Figure 7.5.1.1 shows the user plane protocol stacks within the IP Multimedia Subsystem and the 3GPP SIP-I based circuit switched core network. + +![Diagram of user plane interworking between IMS and SIP-I based CS CN. The diagram shows two protocol stacks connected via Mb and Nb interfaces. The IMS stack on the left has layers: Codec (e.g. NB-AMR), RTP, UDP, IP, L2, L1. The SIP-I based CS CN stack on the right has the same layers. A 'Transcoding or Relaying' block is shown above the stacks, indicating the interworking point.](3e2dcee303cecdd31b7f9ec0d8942fed_img.jpg) + +The diagram illustrates the user plane protocol stacks for interworking between the IMS and a SIP-I based CS CN. The IMS stack on the left consists of the following layers from top to bottom: Codec (e.g. NB-AMR), RTP, UDP, IP, and L2, L1. The SIP-I based CS CN stack on the right consists of the same layers. A 'Transcoding or Relaying' block is positioned above the stacks, indicating the interworking point. The interfaces between the stacks are labeled Mb and Nb. + +| Transcoding or Relaying | | +|-------------------------|-----------------------| +| Codec,
e.g. NB-AMR | Codec,
e.g. NB-AMR | +| RTP | RTP | +| UDP | UDP | +| IP | IP | +| L2, L1 | L2, L1 | + +Diagram of user plane interworking between IMS and SIP-I based CS CN. The diagram shows two protocol stacks connected via Mb and Nb interfaces. The IMS stack on the left has layers: Codec (e.g. NB-AMR), RTP, UDP, IP, L2, L1. The SIP-I based CS CN stack on the right has the same layers. A 'Transcoding or Relaying' block is shown above the stacks, indicating the interworking point. + +Figure 7.5.1.1: user plane interworking + +If the same speech codec is used on both sides, no speech transcoding is required. + +### 7.5.2 DTMF Interworking + +The procedures in subclause 4.5.2 are applicable, however where the external SIP-I network is mentioned in those procedures, this shall be understood as IP Multimedia (IM) Core Network (CN) Subsystem. Where an "IWU" is mentioned in those procedures, this shall be understood as MGCF. + +## 7.6 Example Call flows + +### 7.6.1 General + +In this subclause call flows are shown as examples to demonstrate the signalling interworking of the MGCF. Within the message sequence charts some contents of the messages are shown in order to visualise some of the important interworking aspects, which were described in previous subclauses of this document. It is to be noted that the intention is neither to show the complete content of the SIP messages nor to use the exact syntax of SIP and SDP messages as it is defined in the respective RFCs. It is also not the intention to show all alternative options that are possible for a certain call flow. + +### 7.6.2 Incoming Call flows + +The first call flow shows the signalling for a successful basic call establishment and the later call release. The second call flow depicts a failed call setup. + +#### 7.6.2.1 Successful Call Establishment and Call Release + +Figure 7.6.2.1.1 shows the first part of the incoming call signalling until the called party is alerted and the MGCF is waiting for an answer message. + +Before the received SIP INVITE request is forwarded to SIP-I based circuit switched core network the MGCF removes the PSTN XML body (after content mapped into SIP-I message), replaces the received codec list by a 3GPP structured codec list, and encapsulates the ISUP IAM message, which the MGCF mapped from the received SIP INVITE request. + +The incoming side RTP bearer termination is not yet successfully reserved and configured and therefore local preconditions are not met. Thus the MGCF initiates precondition signalling when sending the INVITE request to the succeeding SIP-I based circuit-switched network. + +The MGCF and the succeeding node perform codec negotiation according to 3GPP rules as specified in 3GPP TS 23.153 [5]. The MGCF answers to the preceding IMS node with a single selected codec. If possible, the selected codec is the same as received from the 3GPP node to avoid transcoding at the network border. + +With the 183 Progress the MGCF authorizes the preceding node to use early media. Therefore, it is not necessary to include the P-Early-Media header in the 180 Ringing response. + +![Sequence diagram for Figure 7.6.2.1.1: Incoming Call (message sequence chart), Called Party alerted.](408c4798ea60469e0728a7cbbd598668_img.jpg) + +``` + +sequenceDiagram + participant IMS as IMS core node (CSCF, BGCF, TrGW) + participant MGCF + participant IM-MGW + participant SIP-I as SIP-I based circuit-switched core network + + Note over IMS, MGCF: Mj, Mg + Note over MGCF, SIP-I: Nc + Note over MGCF, IM-MGW: Mn + + IMS->>MGCF: INVITE [SDP, PSTN XML] + Note right of IMS: 100rel, UPDATE, P-Early-Media, IMS codec list, PSTN XML + MGCF->>IMS: 100 Trying + + Note right of MGCF: remote preconditions are met; local preconditions are not met + + rect rgb(192, 192, 192) + Note over MGCF, IM-MGW: Seize outgoing side RTP bearer terminations + end + + MGCF->>SIP-I: INVITE [SDP, IAM] + Note right of MGCF: 100rel, UPDATE, precondition tag, 3gOoBTC, supported codec list, preconditions not met, IAM + SIP-I->>MGCF: 100 Trying + + SIP-I->>MGCF: 183 Progress [SDP] + Note left of SIP-I: 100rel, UPDATE, precondition tag, 3gOoBTC, selected codec, available codecs + + rect rgb(192, 192, 192) + Note over MGCF, IM-MGW: Seizure of ingoing side RTP bearer terminations, though-connection + end + + MGCF->>IMS: 183 Progress [SDP] + Note right of MGCF: 100rel, UPDATE, P-Early-Media, selected codec + + Note right of MGCF: local preconditions are met, authorise early media + + IMS->>MGCF: PRACK + MGCF->>SIP-I: PRACK [SDP] + Note right of MGCF: preconditions met + SIP-I->>MGCF: 200 OK (PRACK) [SDP] + MGCF->>IMS: 200 OK (PRACK) + + SIP-I->>MGCF: 180 Ringing [ACM] + MGCF->>IMS: 180 Ringing + IMS->>MGCF: PRACK + MGCF->>SIP-I: PRACK + SIP-I->>MGCF: 200 OK (PRACK) + MGCF->>IMS: 200 OK (PRACK) + +``` + +Sequence diagram for Figure 7.6.2.1.1: Incoming Call (message sequence chart), Called Party alerted. + +**Figure 7.6.2.1.1: Incoming Call (message sequence chart), Called Party alerted** + +Figure 7.6.2.1.2 shows how the call setup is finalised and how the call is later released from the IMS side. + +![Sequence diagram for an incoming call continuation. Lifelines represent: IMS core node (CSCF, BGCF, TrGW), MGCF, IM-MGW, and SIP-I based circuit-switched core network. The diagram shows the following sequence: 1. A box indicates 'For preceding signalling sequences see Figure 7.6.2.1.1'. 2. 200 OK (INVITE) [ANM] is sent from the SIP-I network to MGCF, which then sends 200 OK (INVITE) to the IMS core node. 3. ACK is sent from the IMS core node to MGCF, and then from MGCF to the SIP-I network. 4. A large box labeled 'Active Session' spans all lifelines. 5. Call release starts with BYE sent from the IMS core node to MGCF, and BYE [REL] sent from MGCF to the SIP-I network. 6. 200 OK (BYE) [RLC] is sent from the SIP-I network to MGCF, and 200 OK (BYE) is sent from MGCF to the IMS core node. Interfaces Mj, Mg, Nc, Mn are indicated near the MGCF and IM-MGW nodes.](7ed5d5770331f31ade15439a21c31425_img.jpg) + +Sequence diagram for an incoming call continuation. Lifelines represent: IMS core node (CSCF, BGCF, TrGW), MGCF, IM-MGW, and SIP-I based circuit-switched core network. The diagram shows the following sequence: 1. A box indicates 'For preceding signalling sequences see Figure 7.6.2.1.1'. 2. 200 OK (INVITE) [ANM] is sent from the SIP-I network to MGCF, which then sends 200 OK (INVITE) to the IMS core node. 3. ACK is sent from the IMS core node to MGCF, and then from MGCF to the SIP-I network. 4. A large box labeled 'Active Session' spans all lifelines. 5. Call release starts with BYE sent from the IMS core node to MGCF, and BYE [REL] sent from MGCF to the SIP-I network. 6. 200 OK (BYE) [RLC] is sent from the SIP-I network to MGCF, and 200 OK (BYE) is sent from MGCF to the IMS core node. Interfaces Mj, Mg, Nc, Mn are indicated near the MGCF and IM-MGW nodes. + +**Figure 7.6.2.1.2: Incoming Call (message sequence chart), +Continuation of figure 7.6.2.1.1** + +## 7.6.2.2 Autonomous Release at MGCF + +In this example, the MGCF is waiting for an answer from the called subscriber, i.e. the final response to the SIP INVITE request. Figure 7.6.2.2.1 shows the signalling when the waiting timer expires. The MGCF initiates call clearing towards the succeeding SIP-I based circuit-switched network by sending an ISUP REL message included in a SIP BYE request. It also sends a final response for the SIP INVITE request towards the preceding IMS node indicating the error that happened. + +![Figure 7.6.2.2.1: Incoming Call Failure (message sequence chart), called subscriber does not answer. The diagram shows the interaction between an IMS core node (CSCF, BGCF, TrGW), an MGCF, an IM-MGW, and a SIP-I based circuit-switched core network. The sequence starts with the MGCF sending a BYE [REL] message to the IMS core node. The IMS core node responds with a 480 Temporarily Unavailable message. The MGCF then sends a BYE [REL] message to the IM-MGW. The IM-MGW responds with a 200 OK (BYE) [RLC] message. The MGCF also sends a BYE [REL] message to the SIP-I based circuit-switched core network. The IMS core node sends an ACK message to the MGCF. A timer T9 'waiting answer' expires at the MGCF. A note indicates that for preceding signalling sequences, see Figure 7.6.2.1.1.](3337af75dfee8af7687b4f49914d6c93_img.jpg) + +The diagram illustrates the message sequence for an incoming call failure where the called subscriber does not answer. The participants are an IMS core node (CSCF, BGCF, TrGW), an MGCF, an IM-MGW, and a SIP-I based circuit-switched core network. The sequence of messages is as follows: + +- The MGCF sends a **BYE [REL]** message to the IMS core node. +- The IMS core node responds with a **480 Temporarily Unavailable** message with a reason header: cause = 19. +- The MGCF sends a **BYE [REL]** message to the IM-MGW. +- The IM-MGW responds with a **200 OK (BYE) [RLC]** message. +- The MGCF also sends a **BYE [REL]** message to the SIP-I based circuit-switched core network. +- The IMS core node sends an **ACK** message to the MGCF. +- At the MGCF, **Timer T9 "waiting answer" expires**. +- A note at the bottom states: **For preceding signalling sequences see Figure 7.6.2.1.1**. + +Figure 7.6.2.2.1: Incoming Call Failure (message sequence chart), called subscriber does not answer. The diagram shows the interaction between an IMS core node (CSCF, BGCF, TrGW), an MGCF, an IM-MGW, and a SIP-I based circuit-switched core network. The sequence starts with the MGCF sending a BYE [REL] message to the IMS core node. The IMS core node responds with a 480 Temporarily Unavailable message. The MGCF then sends a BYE [REL] message to the IM-MGW. The IM-MGW responds with a 200 OK (BYE) [RLC] message. The MGCF also sends a BYE [REL] message to the SIP-I based circuit-switched core network. The IMS core node sends an ACK message to the MGCF. A timer T9 'waiting answer' expires at the MGCF. A note indicates that for preceding signalling sequences, see Figure 7.6.2.1.1. + +**Figure 7.6.2.2.1: Incoming Call Failure (message sequence chart), +called subscriber does not answer** + +## 7.6.3 Outgoing Call flows + +The first two call flows show the signalling for a successful basic call establishment. The third call flow shows interworking when the call is forked within the IMS. + +### 7.6.3.1 Outgoing Call, Sending of INVITE is deferred + +Figure 7.6.3.1.1 shows an outgoing call where the preconditions are not met when the MGCF receives the initial SIP INVITE. The MGCF defers sending of INVITE until preconditions are met. The MGCF selects a codec and sends back 183 Progress. When the MGCF receives the SIP UPDATE request remote preconditions are met. + +When the MGCF sends the SIP INVITE request to the next IMS node, it does not request the support for preconditions. The selected codec is inserted as the first one within the list of offered codecs. Shown, as a network option, is the inclusion of the PSTN XML body, which is mapped from the previously received ISUP information. The MGCF offers the support for early media which is confirmed by the IMS node in the 183 progress. In this example, the answer does not authorise early media because in-band tones or announcements are not provided. + +When a 180 Ringing provisional response is received from the succeeding IMS the MGCF orders the IM-MGW to start sending the ringing tone before it propagates the 180 Ringing, which includes the ISUP ACM, to the preceding SIP-I based circuit-switched core network. + +![Sequence diagram for Outgoing Call with deferred INVITE until preconditions are met.](9b1ec0090070bdf52ea28763b8d52477_img.jpg) + +The diagram illustrates the signaling flow for an outgoing call where the sending of the INVITE message is deferred until preconditions are met. The participants involved are a SIP-I based circuit-switched core network, an IM-MGW, an MGCF, and an IMS core node (CSCF, BGCF, TrGW). + +**Sequence of Events:** + +- The SIP-I based circuit-switched core network sends an **INVITE [SDP, IAM]** to the IM-MGW. +- The IM-MGW responds with **100rel, UPDATE, precondition tag 3gOoBTC, supported codec list**. A note indicates that **preconditions not met**. +- The IM-MGW sends a **100 TRYING** response to the core network. +- A shaded box indicates **Seize incoming side RTP bearer terminations** at the IM-MGW. +- The IM-MGW sends a **183 Progress [SDP]** response to the core network. It includes **100rel, UPDATE, preconditions 3gOoBTC, selected codec, available codecs**. A note indicates that **local preconditions met**. +- The IM-MGW sends a **PRACK** response to the core network. +- The IM-MGW receives a **200 OK (PRACK)** response from the core network. +- The IM-MGW sends an **UPDATE [SDP]** response to the core network. A note indicates that **preconditions are met**. +- The IM-MGW receives a **200 OK (UPDATE) [SDP]** response from the core network. A note indicates that **local preconditions met**. +- A shaded box indicates **Seize outgoing side RTP bearer terminations** at the IM-MGW. +- At this point, a note indicates that **IMS will not send inband ringing tone**. +- The IM-MGW sends a **Send Tone (Ringing)** message to the core network. +- The IM-MGW receives a **180 Ringing [ACM]** response from the core network. +- The IM-MGW sends a **PRACK** response to the core network. +- The IM-MGW receives a **200 OK (PRACK)** response from the core network. +- Simultaneously, the IM-MGW sends an **INVITE [SDP, PSTN XML]** to the IMS core node. The message includes **100rel, UPDATE, P-Early-Media, IMS codec list (selected codec, ...), PSTN XML**. +- The IMS core node responds with **100 TRYING**. +- The IMS core node sends a **183 Progress [SDP]** response. It includes **100rel, UPDATE, selected codec**. +- The IM-MGW sends a **PRACK [SDP]** response to the IMS core node. +- The IM-MGW receives a **200 OK (PRACK) [SDP]** response from the IMS core node. +- The IMS core node sends a **180 Ringing** response to the IM-MGW. +- The IM-MGW receives a **200 OK (INVITE)** response from the IMS core node. +- A shaded box indicates **Stop Tone (Ringing)** at the IM-MGW. +- The IM-MGW sends a **200 OK (INVITE) [ANM]** response to the core network. +- The IM-MGW receives an **ACK** response from the core network. +- Finally, the IM-MGW sends an **ACK** response to the IMS core node. + +Sequence diagram for Outgoing Call with deferred INVITE until preconditions are met. + +Figure 7.6.3.1.1: Outgoing Call, sending of INVITE is deferred until preconditions are met + +### 7.6.3.2 Outgoing Call, Sending of INVITE is not deferred + +Figure 7.6.3.2.1 shows an outgoing call where the preconditions are not met when the MGCF receives the initial SIP INVITE. When the MGCF sends the SIP INVITE request to the next IMS node before preconditions are fulfilled, it requests the support for preconditions. + +Support for preconditions is confirmed from the IMS node. The MGCF receives more than one codec in the 183 Progress from the external node. Therefore the MGCF selects one of the received codecs and makes a second SDP offer to the external node in the SIP PRACK request in order to lock the codec. + +When the MGCF receives from the incoming side an UPDATE message indicating that preconditions are fulfilled, it propagates the UPDATE message towards the IMS. + +When a 180 Ringing provisional response is received from the succeeding IMS the MGCF orders the IM-MGW to start sending the ringing tone before it propagates the 180 Ringing, which includes the ISUP ACM, to the preceding SIP-I based circuit-switched core network. + +![Sequence diagram for Outgoing Call (Figure 7.6.3.2.1) showing interactions between SIP-I based circuit-switched core network, IM-MGW, MGCF, and IMS core node.](65e8c0628536d6d4245e9ab46ba070c3_img.jpg) + +The sequence diagram illustrates the call flow for an outgoing call where the INVITE is not deferred. The participants are: + + +- SIP-I based circuit-switched core network** (left) +- IM-MGW** (Intermediate Media Gateway) +- MGCF** (Media Gateway Control Function) +- IMS core node (CSCF, BGCF, TrGW)** (right) + + The interfaces are labeled as Nc (between network and MGCF), Mn (between IM-MGW and MGCF), and Mj, Mg (between MGCF and IMS core node). + +**Sequence of messages:** + +- The SIP-I based circuit-switched core network sends an **INVITE [SDP, IAM]** to the MGCF. +- The MGCF responds with **100rel, UPDATE, precondition tag 3gOoBTC, supported codec list, preconditions not met**. +- The MGCF sends a **100 TRYING** response to the network. +- A shaded box indicates **Seize outgoing side RTP bearer terminations** at the MGCF. +- The MGCF sends an **INVITE [SDP, PSTN XML]** to the IMS core node. +- The IMS core node responds with **100rel, UPDATE, precondition tag, P-Early-Media, IMS codec list, preconditions not met, PSTN XML**. +- The IMS core node sends a **100 TRYING** response. +- The IMS core node sends a **183 Progress [SDP]** with **100rel, UPDATE, precondition tag, IMS IETF codec (modified), local preconditions met**. +- A note indicates: **IMS will not send inband ringing tone**. +- A shaded box indicates **Seize incoming side RTP bearer terminations** at the MGCF. +- The MGCF sends a **183 Progress [SDP]** to the network with **100rel, UPDATE, preconditions, 3gOoBTC, selected codec, available codecs, local preconditions met**. +- The MGCF sends a **PRACK** to the IMS core node. +- The IMS core node responds with **200 OK (PRACK)**. +- The MGCF sends a **200 OK (PRACK)** to the network. +- The MGCF sends an **UPDATE [SDP]** to the IMS core node with **preconditions are met**. +- The IMS core node responds with **UPDATE [SDP], selected codec, preconditions are met**. +- The IMS core node sends a **200 OK (UPDATE) [SDP], selected codec, local preconditions met**. +- The MGCF sends a **200 OK (UPDATE) [SDP], local preconditions met** to the network. +- The MGCF sends a **Send Tone (Ringing)** (shaded box). +- The IMS core node sends a **180 Ringing** response. +- The MGCF sends a **180 Ringing [ACM]** to the network. +- The MGCF sends a **PRACK** to the IMS core node. +- The MGCF sends a **200 OK (PRACK)** to the network. +- The IMS core node sends a **200 OK (INVITE)** response. +- A shaded box indicates **Stop Tone (Ringing)** at the MGCF. +- The MGCF sends a **200 OK (INVITE) [ANM]** to the network. +- The MGCF sends an **ACK** to the IMS core node. + +Sequence diagram for Outgoing Call (Figure 7.6.3.2.1) showing interactions between SIP-I based circuit-switched core network, IM-MGW, MGCF, and IMS core node. + +**Figure 7.6.3.2.1: Outgoing Call, sending of INVITE is not deferred until preconditions are met** + +### 7.6.3.3 Interworking with forked SIP INVITE Requests + +In this example, the SIP INVITE request is routed within the IMS to a forking proxy. Therefore the MGCF has to interwork with multiple early dialogues. This is shown in figures 7.6.3.3.1 and 7.6.3.3.2, where only those message contents are shown that are needed for the understanding of this call flow. + +When receiving the first 183 Session Progress within dialogue A, the handling is done as in the previous call flow example (figure 7.6.3.2.1). Afterwards the MGCF receives another 183 Session Progress but within a second dialogue + +B. In this example, the received codec list does not include the codec which is already selected for dialogue A. Therefore the MGCF can not directly send the selected codec to the succeeding IMS node within the second dialogue B. + +When the SIP UPDATE request is received, which indicates that preconditions are met, the MGCF sends two SIP UPDATE requests to the succeeding IMS node to signal within both dialogues that preconditions are met. + +![Sequence diagram for Outgoing Call, multiple early dialogues. The diagram shows the interaction between an SIP-I based circuit-switched core network (via IM-MGW), an MGCF, and an IMS core node (CSCF, BGCF, CS-IBCF). The MGCF initiates two parallel dialogues, A and B, with the IMS core node. Dialogue A completes its setup first, followed by Dialogue B. The MGCF then sends UPDATE messages to both dialogues when preconditions are met.](3c04b14104f95eb8f7100f6d497d956e_img.jpg) + +``` + +sequenceDiagram + participant CS as SIP-I based circuit-switched core network + participant IM-MGW as IM-MGW + participant MGCF as MGCF + participant IMS as IMS core node (CSCF, BGCF, CS-IBCF) + + Note right of MGCF: Nc, Mn + Note left of IMS: Mj, Mg + + CS->>IM-MGW: INVITE [SDP, IAM] +..... remote preconditions not met + IM-MGW-->>CS: 100 Trying + IM-MGW->>MGCF: Seize outgoing side RTP bearer terminations + MGCF->>IMS: INVITE [SDP] +....IMS codec list, preconditions not met, .... + IMS-->>MGCF: 100 Trying + IMS->>MGCF: 183 Session Progress [SDP] +To: tag A, IMS codec list A, ..... + IM-MGW->>MGCF: Seize incoming side RTP bearer terminations + IM-MGW->>CS: 183 Session Progress [SDP] +To: tag X +3gOoBTC, selected codec A, available +codecs XA + MGCF->>IMS: PRACK +To: tag X + CS-->>IM-MGW: 200 OK (PRACK) +To: tag X + IMS-->>MGCF: 200 OK (PRACK) [SDP] +To: tag A + IMS->>MGCF: 183 Session Progress [SDP] +To: tag B, IMS codec list B, ..... + MGCF->>IMS: PRACK +To: tag B + IMS-->>MGCF: 200 OK (PRACK) +To: tag B + MGCF->>CS: UPDATE [SDP] +To: tag X, preconditions are met + MGCF->>IMS: UPDATE [SDP] +To: tag A, preconditions are met + MGCF->>IMS: UPDATE [SDP] +To: tag B, preconditions are met + IMS-->>MGCF: 200 OK (UPDATE) [SDP] +To: tag A, local preconditions met + IMS-->>MGCF: 200 OK (UPDATE) [SDP] +To: tag B, local preconditions met + CS-->>IM-MGW: 200 OK (UPDATE) [SDP] +To: tag X, local preconditions met + +``` + +Sequence diagram for Outgoing Call, multiple early dialogues. The diagram shows the interaction between an SIP-I based circuit-switched core network (via IM-MGW), an MGCF, and an IMS core node (CSCF, BGCF, CS-IBCF). The MGCF initiates two parallel dialogues, A and B, with the IMS core node. Dialogue A completes its setup first, followed by Dialogue B. The MGCF then sends UPDATE messages to both dialogues when preconditions are met. + +Figure 7.6.3.3.1: Outgoing Call, multiple early dialogues + +Figure 7.6.3.3.2 shows that only the first 180 Ringing received from the IMS node is interworked with the SIP-I based circuit-switched core network. + +Finally, the SIP INVITE request is answered with a 200 OK within dialogue B. + +Any subsequent final response within dialogue A is acknowledged (with an ACK request) and immediately rejected by sending back a SIP BYE request. + +![Sequence diagram for Outgoing Call, multiple early dialogues. The diagram shows signaling between an SIP-I based circuit-switched core network (via IM-MGW), an MGCF, and an IMS core node (CSCF, BGCF, CS-IBCF). It details two dialogues, A and B, with messages like 180 Ringing, PRACK, 200 OK, INVITE, and BYE. A note indicates that for preceding signalling sequences, see Figure 7.6.3.3.1. Another note indicates that if the second 200 OK response is received for dialogue A, a BYE is sent. A third note indicates that if the received codec list for dialogue A did not include the previous selected codec A, a new INVITE with SDP is sent.](a4bfa2343d75076b79f7e33d93915e00_img.jpg) + +The diagram illustrates the signaling sequence for an outgoing call involving multiple early dialogues (A and B) between an SIP-I based circuit-switched core network and an IMS core node. + +**Participants:** + +- SIP-I based circuit-switched core network (via IM-MGW) +- MGCF +- IMS core node (CSCF, BGCF, CS-IBCF) + +**Interfaces:** + +- IM-MGW to MGCF: Nc, Mn +- MGCF to IMS core node: Mj, Mg + +**Sequence:** + +- The IMS core node sends a **180 Ringing** (To: tag B) to the MGCF. +- The MGCF sends a **Send Tone (Ringing)** to the IM-MGW. +- The IM-MGW sends a **180 Ringing [ACM]** (To: tag X) to the SIP-I based circuit-switched core network. +- The SIP-I based circuit-switched core network sends a **PRACK** (To: tag X) to the IM-MGW. +- The IM-MGW sends a **200 OK (PRACK)** (To: tag X) to the SIP-I based circuit-switched core network. +- The IMS core node sends a **180 Ringing** (To: tag A) to the MGCF. +- The MGCF sends a **PRACK** (To: tag A) to the IMS core node. +- The IMS core node sends a **200 OK (PRACK)** (To: tag A) to the MGCF. +- The MGCF sends a **200 OK (INVITE)** (To: tag B) to the IMS core node. +- The IMS core node sends an **ACK** (To: tag B) to the MGCF. +- The MGCF sends a **200 OK (INVITE)** (To: tag A) to the IMS core node. +- The IMS core node sends an **ACK** (To: tag A) to the MGCF. +- The MGCF sends a **BYE** (To: tag A) to the IMS core node. +- The IMS core node sends a **200 OK (BYE)** (To: tag A) to the MGCF. +- The MGCF sends an **INVITE [SDP]** (To: tag X, 3gOoBTC, selected codec XB, available codecs XB) to the SIP-I based circuit-switched core network. +- The SIP-I based circuit-switched core network sends a **200 OK (INVITE) [SDP]** (To: tag X) to the MGCF. +- The MGCF sends an **ACK** (To: tag X) to the SIP-I based circuit-switched core network. + +**Notes:** + +- For preceding signalling sequences see Figure 7.6.3.3.1 +- if second 200 OK response is received (for dialogue A) +- If received codec list for established dialogue did not include the previous selected codec A (for dialogue A) + +Sequence diagram for Outgoing Call, multiple early dialogues. The diagram shows signaling between an SIP-I based circuit-switched core network (via IM-MGW), an MGCF, and an IMS core node (CSCF, BGCF, CS-IBCF). It details two dialogues, A and B, with messages like 180 Ringing, PRACK, 200 OK, INVITE, and BYE. A note indicates that for preceding signalling sequences, see Figure 7.6.3.3.1. Another note indicates that if the second 200 OK response is received for dialogue A, a BYE is sent. A third note indicates that if the received codec list for dialogue A did not include the previous selected codec A, a new INVITE with SDP is sent. + +Figure 7.6.3.3.2: Outgoing Call, multiple early dialogues (continuation of figure 7.6.3.3.1) + +## 7.7 CS CN Supplementary Services and IMS Supplementary Services + +### 7.7.0 General + +The following subclauses describe the MGCF behaviour when: + +- Supplementary services are invoked within the SIP-I based circuit switched core network and +- Supplementary services are invoked within the IMS. + +The support of these supplementary services is optional. If the supplementary services are supported, the procedures described within this subclause shall be applied. + +Within the SIP-I based circuit switched core network: + +- Service information is carried within encapsulated ISUP messages. +- The procedures specified for the ISUP side in 3GPP TS 29.163 [13] subclauses 7.4 and 7.5 shall be applied to the encapsulated ISUP. + +### 7.7.1 Number Identification Services + +#### 7.7.1.1 CS CN Supplementary Service - Calling Line Identification Presentation/Restriction (CLIP/CLIR) + +There is no additional interworking beyond subclauses 7.2 and 7.3 when the Calling Line Identification Presentation or a Calling Line Identification Restriction supplementary service is invoked within the SIP-I based circuit switched core network. + +#### 7.7.1.2 CS CN Supplementary Service - Connected Line Identification Presentation/Restriction (COLP/COLR) + +When the Connected Line Identification Presentation or Connected Line Identification Restriction supplementary service is invoked within the SIP-I based circuit switched core network, the MGCF shall perform the mapping to the Terminating Identification Presentation / Restriction service as specified in 3GPP TS 29.163 [13] subclause 7.5.2. + +#### 7.7.1.3 IMS Supplementary Service - Originating Identification Presentation (OIP) and Originating Identification Restriction (OIR) + +There is no additional interworking beyond subclauses 7.2 and 7.3, when the Originating Identification Presentation or Originating Identification Restriction supplementary service is invoked within the IMS network. + +#### 7.7.1.4 IMS Supplementary Service - Terminating Identification Presentation (TIP) and Terminating Identification Restriction (TIR) + +When the Terminating Identification Presentation or Terminating Identification Restriction supplementary service is invoked within the IMS network, the MGCF shall perform the mapping to the Connected Line Identification Presentation / Restriction supplementary service as specified in 3GPP TS 29.163 [13] subclause 7.5.2. + +#### 7.7.1.5 CS CN Supplementary Service – Direct Dialling In + +There is no additional interworking beyond subclauses 7.2 and 7.3, when the Direct Dialling In supplementary service is invoked within the SIP-I based circuit switched core network. + +#### 7.7.1.6 CS CN Supplementary Service – Malicious Call Identification + +When the Malicious Call Identification supplementary service is invoked within the SIP-I based circuit switched core network the MGCF shall perform the mapping as specified in 3GPP TS 29.163 [13] subclause 7.5.9. + +### 7.7.1.7 IMS Supplementary Service – Malicious Communication Identification (MCID) + +When Malicious Communication Identification service is invoked within the IMS network, then as specified in 3GPP TS 29.163 [13] subclause 7.5.9.2, the interworking to the Malicious Call Identification supplementary service shall not be applied. + +### 7.7.1.8 CS CN Supplementary Service – Subaddressing + +When the Subaddressing supplementary service is invoked within the SIP-I based circuit switched core network, the procedures specified in 3GPP TS 29.163 [13] subclause 7.4.5 shall be applied. + +## 7.7.2 Diversion Services + +### 7.7.2.1 CS CN Supplementary Service - Call Forwarding Services (CFU, CFB, CFNRy, CFNRc) + +When any of the call forwarding supplementary services (CFU, CFB, CFNRy, and CFNRc) is invoked within the SIP-I based circuit switched core network, the MGCF shall perform the mapping to the Communication Diversion service as specified in 3GPP TS 29.163 [13] subclauses 7.5.4.2.2 and 7.5.4.3. + +### 7.7.2.2 CS CN Supplementary Service – Call Deflection (CD) + +When the Call Deflection supplementary service is invoked within the SIP-I based circuit switched core network the MGCF shall perform the mapping to the Communication Diversion service as specified in 3GPP TS 29.163 [13] subclauses 7.5.4.2.2 and 7.5.4.3. + +### 7.7.2.3 IMS Supplementary Service – Communication Diversion (CDIV) + +When a Communication Diversion supplementary service is invoked within the IMS network, the MGCF shall perform the mapping to a Call Diversion supplementary service as specified in 3GPP TS 29.163 [13] subclauses 7.5.4.2.1 and 7.5.4.3. + +## 7.7.3 Waiting Services + +### 7.7.3.1 CS CN Supplementary Service – Call Waiting + +When the Call Waiting supplementary service is invoked within the SIP-I based circuit switched core network, the MGCF shall perform the mapping to the Communication Waiting service as specified in 3GPP TS 29.163 [13] subclause 7.5.12.1. + +### 7.7.3.2 IMS Supplementary Service – Communication Waiting (CW) + +When the Communication Waiting supplementary service is invoked within the IMS network, the MGCF shall perform the mapping to the Call Waiting supplementary service as specified in 3GPP TS 29.163 [13] subclause 7.5.12.2. + +## 7.7.4 Hold Services + +### 7.7.4.1 CS CN Supplementary Service – Call Hold + +There is no additional interworking beyond subclauses 7.2 and 7.3, when the Call Hold supplementary service is invoked within the SIP-I based circuit switched core network. + +### 7.7.4.2 IMS Supplementary Service – Communication Hold (HOLD) + +There is no additional interworking beyond subclauses 7.2 and 7.3, when the Communication Hold supplementary service is invoked within the IMS network. + +NOTE: Call hold for IMS is specified in 3GPP TS 24.610 [26]. + +## 7.7.5 Multiparty Services + +### 7.7.5.1 CS CN Supplementary Services – Conference Calling (CONF) and Three-Party (3PTY) + +When the Conference Calling and Three-Party supplementary services are invoked within the SIP-I based circuit switched core network, the procedures specified in 3GPP TS 29.163 [13] subclause 7.4.14 shall be applied. + +### 7.7.5.2 IMS Supplementary Service – Conference (CONF) + +When the Conference supplementary service is invoked within the IMS network, the procedures specified in 3GPP TS 29.163 [13] subclause 7.5.6 shall be applied. + +## 7.7.6 Closed User Group Service + +### 7.7.6.1 CS CN Supplementary Service – Closed User Group (CUG) + +When the Closed User Group supplementary service is invoked within the SIP-I based circuit switched core network, the procedures specified in 3GPP TS 29.163 [13] subclause 7.5.10.2 shall be applied. + +### 7.7.6.2 IMS Supplementary Service - Closed User Group (CUG) + +When the Closed User Group supplementary service is invoked within the IMS network, the procedures specified in 3GPP TS 29.163 [13] subclause 7.5.10.1 shall be applied. + +## 7.7.7 Charging Services + +### 7.7.7.1 CS CN Supplementary Service – Advice of Charge (AoC) + +NOTE: Interworking for AoC is not specified in the present Release. + +### 7.7.7.2 IMS Supplementary Service – Advice of Charge (AOC) + +NOTE: Interworking for AOC is not specified in the present Release. + +### 7.7.7.3 CS CN Supplementary Service – International Telecommunication Charge Card (ITCC) + +When the International Telecommunication Charge Card supplementary service is invoked within the SIP-I based circuit switched core network no additional treatment is required by the MGCF. + +### 7.7.7.4 CS CN Supplementary Service – Reverse Charging (REV) + +When the Reverse Charging supplementary service is invoked within the SIP-I based circuit switched core network, the procedures specified in 3GPP TS 29.163 [13] subclause 7.4.17 shall be applied. + +## 7.7.8 Barring Services + +### 7.7.8.1 CS CN Supplementary Service - Barring of Outgoing Calls + +There is no additional interworking beyond subclauses 7.2 and 7.3, when the Barring of Outgoing Call supplementary service is invoked within the SIP-I based circuit switched core network. + +### 7.7.8.2 CS CN Supplementary Service - Barring of Incoming Calls + +There is no additional interworking beyond subclauses 7.2 and 7.3, when the Barring of Incoming Calls supplementary service is invoked within the SIP-I based circuit switched core network. + +### 7.7.8.3 CS CN Supplementary Service - Anonymous Call Rejection (ACR) + +When the Anonymous Call Rejection supplementary service is invoked within the SIP-I based circuit switched core network, the procedures specified in 3GPP TS 29.163 [13] subclause 7.4.23.1 shall be applied. + +#### 7.7.8.4 IMS Supplementary Service – Communication Barring (CB) + +NOTE: Interworking of Communication Barring is not specified in the present Release. + +#### 7.7.8.5 IMS Supplementary Service – Anonymous Communication Rejection (ACR) + +When the Anonymous Communication Rejection supplementary service is invoked within the IMS network, the procedures specified in 3GPP TS 29.163 [13] subclause 7.4.23.2 shall be followed with the following modifications at the SIP-I on Nc side: + +- The response code 433 (Anonymity Disallowed) defined by IETF RFC 5079 [36] is supported on SIP-I on Nc. + +### 7.7.9 Transfer Services + +#### 7.7.9.1 CS CN Supplementary Service – Explicit Call Transfer (ECT) + +When the Explicit Call Transfer supplementary service is invoked within the SIP-I based circuit switched core network and the MGCF receives from the SIP-I based circuit-switched core network an INFO message with encapsulated ISUP FAC for the notification of ECT invocation, then the MGCF shall: + +- map the FAC into a SIP re-INVITE request or SIP UPDATE request according to 3GPP TS 29.163 [13] if the call is in active state (after answer). +- map the FAC into a SIP UPDATE request according to 3GPP TS 29.163 [13] if the call is in active state (before answer). + +#### 7.7.9.2 IMS Supplementary Service – Explicit Communication Transfer (ECT) + +When the Explicit Communication Transfer supplementary service is invoked within the IMS network and if the transferee is another IMS terminal and the transfer target is a CS terminal, then the MGCF will receive a SIP INVITE request. No special interworking is required at the MGCF. + +NOTE: The protocol for ECT within IMS is specified in 3GPP TS 24.629 [25]. The IMS terminal, which invokes the ECT service, sends a SIP REFER request to the transferee. The transferee sends a SIP INVITE request to the transfer target. + +### 7.7.10 Call Completion Services + +#### 7.7.10.1 CS CN Supplementary Service – Completion of Calls to Busy Subscriber (CCBS) + +When the Completion of Calls to Busy Subscriber supplementary service is invoked within the SIP-I based circuit switched core network, the procedures specified in 3GPP TS 29.163 [13] subclause 7.4.11 shall be applied. + +#### 7.7.10.2 CS CN Supplementary Service – Completion of Calls on No Reply (CCNR) + +When the Completion of Calls on No Reply supplementary service is invoked within the SIP-I based circuit switched core network, the procedures specified in 3GPP TS 29.163 [13] subclause 7.4.12 shall be applied. + +#### 7.7.10.3 IMS Supplementary Service – Completion of Communications to Busy Subscriber (CCBS) and Completion of Communication on No Reply (CCNR) + +When the Completion of Communications to Busy Subscriber or Completion of Communication on No Reply supplementary service is invoked within the IMS network, the procedures specified in 3GPP TS 29.163 [13] subclause 7.5.11.1 shall be applied. + +### 7.7.11 Miscellaneous Services + +#### 7.7.11.1 CS CN Supplementary Service - Multi-Level Precedence and Pre-emption (MLPP) + +When the Multi-Level Precedence and Pre-emption (MLPP) supplementary service is invoked within the SIP-I based circuit switched core network the procedures specified in 3GPP TS 29.163 [13] subclause 7.4.17 shall be applied. + +#### 7.7.11.2 CS CN Supplementary Service - Multiple Subscriber Profile (MSP) + +There is no additional interworking beyond subclauses 7.2 and 7.3 when a Multiple Subscriber Profile supplementary service is invoked within the SIP-I based circuit switched core network. + +#### 7.7.11.3 CS CN Supplementary Service - Multicall + +There is no additional interworking beyond subclauses 7.2 and 7.3 when the Multicall supplementary service is invoked within the SIP-I based circuit switched core network. + +#### 7.7.11.4 CS CN Supplementary Service - Calling Name Presentation + +There is no additional interworking beyond subclauses 7.2 and 7.3, when the Calling Name Presentation supplementary service is invoked within the SIP-I based circuit switched core network. + +#### 7.7.11.5 CS CN Supplementary Service – User-to-User Signalling (UUS) + +NOTE: Interworking for User-to-User Signalling is not specified in the present Release. + +#### 7.7.11.6 IMS Supplementary Service – Message Waiting Indication (MWI) + +NOTE: Interworking for Message Waiting Indication is not specified in the present Release. + +#### 7.7.11.7 CS CN Supplementary Service - Global Virtual Network Service (GVNS) + +When the Global Virtual Network Service supplementary service is invoked within the SIP-I based circuit switched core network the procedures specified in 3GPP TS 29.163 [13] subclause 7.4.18 shall be applied. + +#### 7.7.11.8 CS CN Supplementary Service - Terminal Portability (TP) + +When the Terminal Portability supplementary service is invoked within the SIP-I based circuit switched core network, the procedures specified in 3GPP TS 29.163 [13] subclause 7.4.13 shall be applied. + +### 7.7.12 Customized Alerting Tones Services + +#### 7.7.12.1 CS CN Supplementary Service - Customized Alerting Tones (CAT) + +When the Customized Alerting Tones supplementary service is invoked within the SIP-I based circuit switched core network, the MGCF shall perform the mapping as specified in 3GPP TS 29.163 [13] subclause 7.4.24. + +#### 7.7.12.2 IMS Supplementary Service - Customized Alerting Tones (CAT) for early session model + +When the Customized Alerting Tones supplementary service is invoked within the IMS network using early session model, the MGCF shall perform the mapping for normal session SDP negotiation and early session SDP negotiation as specified in 3GPP TS 29.163 [13] subclause 7.5.13.2. + +#### 7.7.12.3 IMS Supplementary Service - Customized Alerting Tones (CAT) for forking model + +When the Customized Alerting Tones supplementary service is invoked within the IMS network using forking model, the MGCF shall perform the mapping as specified in 3GPP TS 29.163 [13] subclause 7.5.13x.3. + +#### 7.7.12.4 IMS Supplementary Service - Customized Alerting Tones (CAT) for gateway model + +When the Customized Alerting Tones supplementary service is invoked within the IMS network using gateway model, the MGCF shall perform the mapping as specified in 3GPP TS 29.163 [13] subclause 7.5.13.4. + +## 7.8 MGCF – IM-MGW Interaction + +### 7.8.1 General + +The present subclause describes signalling procedures that are applicable at the Mn interface when the MGCF and attached IM-MGW interwork between an IM CN Subsystem and a SIP-I based circuit-switched core network. + +The MGCF shall interact with the IM-MGW across the Mn reference point. The signalling interface across the Mn reference point is defined in accordance with ITU-T Recommendation H.248.1 [53] and shall conform to 3GPP specific extensions as detailed in 3GPP TS 29.332 [54]. + +### 7.8.2 Call related Procedures for Terminations towards the IM CN Subsystem + +Subclause 9.3.1 in 3GPP TS 29.163 [13] shall apply. + +### 7.8.3 Call related Procedures for Terminations towards SIP-I based Circuit-switched Core Network + +Those procedures defined in 3GPP TS 23.205 [9] that are listed in table 7.8.3.1 shall apply. + +**Table 7.8.3.1: Call related Procedures defined in 3GPP TS 23.205 [9] that are applicable at terminations towards SIP-I based circuit-switched core network** + +| Procedure defined in 3GPP TS 23.205 [9] | Remarks | +|--------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Change Flow Direction | NOTE 1 in that subclause is replaced by:

NOTE 1: This procedure may be combined with the "Reserve RTP Connection Point" procedure, the "Configure RTP Connection Point" procedure, or the "Reserve and Configure RTP Connection Point" procedure. | +| Change Through-Connection | The NOTE in that subclause is replaced by:

NOTE 2: This procedure may be combined with the "Reserve RTP Connection Point" procedure, the "Configure RTP Connection Point" procedure, or the "Reserve and Configure RTP Connection Point" procedure. | +| Bearer Released | | +| Release Termination | | +| Send Tone | | +| Stop Tone | | +| Play Announcement | Optional | +| Stop Announcement | Optional | +| Announcement Completed | Optional | +| Tone Completed | | +| Activate Voice Processing Function | Optional | +| Termination heartbeat indication | | +| Reserve RTP Connection Point | | +| Configure RTP Connection Point | | +| Reserve and Configure RTP Connection Point | | + +### 7.8.4 Non-call related procedures + +Subclause 9.3.4 in 3GPP TS 29.163 [13] shall apply. + +--- + +# Annex A (normative): Interconnecting functionalities in SIP-I based CS domain + +## A.1 General + +This annex describes a collection of functions that can be performed on interconnection boundaries between two SIP-I based 3GPP CS networks or between a SIP-I based CS network and other SIP-I based external network, based on operator configuration. + +In subclauses A.2 and A.3 Stage 2 requirements and border control architecture are described. + +--- + +## A.2 Stage 2 Requirements + +Based on operator preference, border control functions may be applied between two SIP-I based 3GPP CS domains or between a SIP-I based 3GPP CS domain and other SIP-I based external network. These functions, provided by the CS-IBCF, are: + +- Controlling transport plane functions; +- Supporting functions to allow establishing communication between disparate address realms' SIP-I applications; +- Providing network configuration hiding to restrict the following information from being passed outside of an operator's network: exact number of MSC servers, capacity and topology of the network, naming and addressing of the network nodes; +- Screening SIP signalling information based on source/destination and operator policy (e.g. remove information that is of local significance to an operator); +- Selecting the appropriate signalling interconnections (e.g. domain based routing). The IP interconnection between core networks may be supported either by direct connection or by using an intermediate carrier; +- Supporting network resources allocation taking into consideration the codec negotiation performed by (G)MSCs across one or multiple interconnects, remaining transparent to the SDP negotiation. + +In case border control concepts are to be applied in a SIP-I based CS network, the CS-IBCF acts as an entry point for this network, and also acts as an exit point for this network. + +On the media plane the following functions shall be supported by the CS-TrGW: + +- Gate Management: + - Opening/closing of gates; + - Remote source address filtering; + - Remote source port filtering; +- QoS packet marking (differentiated services); +- NA(P)T and IP Version Interworking; +- Bandwidth policing; +- Hanging termination detection; +- IP Realm Indication. + +Additionally, the following functions may be supported by the CS-TrGW: + +- IP Realm Availability. + +## A.3 Border Control architecture + +Figure A.3.1 presents a high-level architecture diagram showing how CS-IBCF and CS-TrGW logical functions fit into the SIP-I based CS domain. + +![Figure A.3.1: CS-IBCF and CS-TrGW in SIP-I based CS domain. High-level architecture diagram showing logical functions and reference points.](f468e577645d646f5157ce3eefb4ed96_img.jpg) + +The diagram shows the following components and connections: + +- IWU** (Interworking Unit) connects to **CS-IBCF** via a dashed line (Signalling) labeled **SIP-I**. +- IWU** connects to **UP-IWU** (User Plane Interworking Unit) via a dashed line labeled **Mc**. +- UP-IWU** connects to **CS-TrGW** via a solid line (Bearer) labeled **Media/RTP/UDP/IP**. +- CS-IBCF** and **CS-TrGW** are enclosed in a dashed box labeled **border control logical functions**. +- Inside **CS-IBCF**, there are sub-functions **ALG** and **THIG**. +- CS-IBCF** and **CS-TrGW** are connected via a dashed line labeled **CS-Ix**. +- The **border control logical functions** block connects to a large oval representing the **SIP-I based 3GPP CS domain/External SIP-I Network** via both Signalling (dashed) and Bearer (solid) lines. +- Legend:** Dashed line (---) = Signalling; Solid line (\_\_\_) = Bearer. + +Figure A.3.1: CS-IBCF and CS-TrGW in SIP-I based CS domain. High-level architecture diagram showing logical functions and reference points. + +**Figure A.3.1: CS-IBCF and CS-TrGW in SIP-I based CS domain** + +The CS-IBCF, which provides border control functions, shall be transparent to the call control application of the adjacent 3GPP SIP-I nodes. That is, outgoing SIP-I messages from a 3GPP MSC-IWU shall assume that it is signalling to an external network. The CS-IBCF shall not perform SIP-I profile interworking functions that are defined by the main text of this specification. The CS-IBCF is a logical function that either is co-located with IWU in a single physical (G)MSC-S node, or is within a separate physical node, e.g. when co-locating with IMS-IBCF. + +The Nb reference point allows CS-MGWs to communicate with a CS-TrGW in order to provide border control functions. The CS-TrGW is a logical function that may reside in the UP-IWU. The CS-TrGW, which provides border control functions, shall be transparent to adjacent 3GPP MGWs. The CS-TrGW shall not perform any SIP-I user plane interworking functions that are defined by the main text of this specification. The CS-TrGW is a logical function that can be co-located with UP-IWU in a single physical CS-MGW node, but can also be in a separate physical node, e.g. when co-locating with IMS-TrGW. + +If the logical functions are co-located with (G)MSC and CS-MGW then the Mc profile as defined by 3GPP TS 29.232 [55] shall provide the required functionality (described in subclause A.8). If CS-IBCF is physically separated then the CS-IBCF control function is connected to the CS-TrGW via the CS-Ix reference point (described in subclause A.7), which is realised by the Ix profile as defined by 3GPP TS 29.238 [29]. + +## A.4 Void + +## A.5 Procedures at the CS-IBCF + +### A.5.1 General + +Border control functions may be applied between two SIP-I based CS domains subsystems or between an SIP-I based CS domains and other SIP-I based networks based on operator preference. The CS-IBCF may act both as an entry point and as an exit point for a network. If it processes a SIP request received from other network it functions as an entry point (see subclause A.5.3) and it acts as an exit point whenever it processes a SIP request sent to other network (see subclause A.5.2). + +Depending on its rule, the functions of the CS-IBCF include: + +- network configuration hiding (described in subclauses A.5.2.4 and A.5.3.4); + +- application level gateway (in subclauses A.5.2.5 and A.5.3.5); +- screening of SIP signalling (in subclauses A.5.2.6 and A.5.3.6); +- charging (in subclauses A.5.2.7 and A.5.3.7). + +NOTE: The functions performed by the CS-IBCF are configured by the operator, and they are network specific. + +## A.5.2 CS-IBCF as an exit point + +### A.5.2.1 Initial requests + +Upon receipt of any request, the CS-IBCF shall: + +- 1) if the request is an INVITE request, respond with a 100 (Trying) provisional response; +- 2) if the request is an INVITE request and the CS-IBCF is configured to perform application level gateway and/or transport plane control functionalities, save the Contact, CSeq, From and Record-Route header field values received in the request such that the CS-IBCF is able to release the session if needed; +- 3) if network topology hiding is required, apply the procedures as described in subclause A.5.2.4; +- 4) if screening of SIP signalling is required, apply the procedures as described in subclause A.5.2.6; +- 5) select an entry point of the destination network and forward the request to that entry point; + +NOTE: The list of the entry points can be either obtained as specified in IETF RFC 3263 [30] or provisioned in the CS-IBCF. The entry point can be a CS-IBCF or an (G)MSC server. + +When the CS-IBCF receives an INVITE request, the CS-IBCF may require the periodic refreshment of the session to avoid hung states in the CS-IBCF. If the CS-IBCF requires the session to be refreshed, the CS-IBCF shall apply the procedures described in IETF RFC 4028 [31] clause 8. + +IETF RFC 3325 [32] provides for the existence and trust of an asserted identity within a trust domain. A CS-IBCF at the boundary of the trust domain will need to determine whether to remove the P-Asserted-Identity header according to IETF RFC 3325 [32] when SIP signalling crosses the boundary of the trust domain. + +When the CS-IBCF receives a response to the initial request and network topology hiding is required, then the CS-IBCF shall apply the procedures as described in subclause A.5.2.4. + +When the CS-IBCF receives a response to the initial request and screening of SIP signalling is applied, then the CS-IBCF shall apply the procedures as described in subclause A.5.2.6. + +When the CS-IBCF receives a response to the initial INVITE request that establishes a dialogue, and the CS-IBCF is configured to perform application level gateway and/or transport plane control functions, the CS-IBCF shall save the Contact, To and Record-Route header field values received in the response such that the CS-IBCF is able to release the session if needed. + +### A.5.2.2 Subsequent requests + +Upon receipt of any request, the CS-IBCF shall: + +- 1) if the request is an INVITE request, respond with a 100 (Trying) provisional response; +- 2) if the request is a target refresh request and the CS-IBCF is configured to perform application level gateway and/or transport plane control functions, save the Contact and CSeq header field values received in the request such that the CS-IBCF is able to release the session if needed; +- 3) if the subsequent request is other than a target refresh request (including requests relating to an existing dialogue where the method is unknown) and the CS-IBCF is configured to perform application level gateway and/or transport plane control functionalities, save the Contact and CSeq header field values received in the request such that the CS-IBCF is able to release the session if needed; +- 4) if network topology hiding is required, apply the procedures as described in subclause A.5.2.4; + +- 5) if screening of SIP signalling is required, apply the procedures as described in subclause A.5.2.6. + +When the CS-IBCF receives a response to the subsequent request and network topology hiding is required, then the CS-IBCF shall apply the procedures as described in subclause A.5.2.4. + +When the CS-IBCF receives a response to the subsequent request and screening of SIP signalling is required, then the CS-IBCF shall apply the procedures as described in subclause A.5.2.6. + +### A.5.2.3 CS-IBCF-initiated call release + +If the CS-IBCF provides transport plane control functionality and receives an indication of a transport plane related error the CS-IBCF may: + +- 1) if the CS-IBCF has already sent an initial INVITE request to the terminating side, apply SIP procedures detailed in IETF RFC 3261 [20] to terminate any corresponding SIP dialogue(s) or otherwise cancel the INVITE at the terminating side, making use of CANCEL and/or BYE request(s), based on information saved for the related dialogue; and +- 2) if the CS-IBCF has not yet sent out a final response for the initial INVITE request, send an appropriate failure response for the initial INVITE request to the originating side; and +- 3) if the CS-IBCF has already sent out a final response for the initial INVITE request, generate a BYE request for the originating side based on the information saved for the related dialogue. + +NOTE 1: Transport plane related errors can be indicated from TrGW. + +NOTE 2: Since the CS-IBCF does not handle the encapsulated ISUP, the BYE message(s) generated by the CS-IBCF will not contain any encapsulated ISUP REL message. + +If the CS-IBCF is able to determine an appropriate Q.850 cause value, then this may be included in a Reason header in the BYE message(s). + +### A.5.2.4 THIG functionality in the CS-IBCF + +#### A.5.2.4.1 General + +The following procedures shall only be applied if network topology hiding is required by the network. The network requiring network topology hiding is called the hiding network. + +NOTE 1: Requests and responses are handled independently; therefore, no state information is needed for that purpose within a CS-IBCF. + +The CS-IBCF shall apply network topology hiding to all headers which reveal topology information, such as Via, Route, Record-Route, and Path. Therefore, the CS-IBCF shall: + +- either act as a B2BUA, i.e. set above headers as defined for a SIP user agent client by IETF RFC 3261 [20], +- or as an option follow the procedures defined in A.5.2.4.2. + +The CS-IBCF shall not screen SIP parameters for which there is a related ISUP parameter defined within ITU-T Recommendation Q.1912.5 [6]. + +NOTE 2: SIP-I screening is normally done by the MSC, where the encapsulated ISUP message and the SIP headers are consistently screened. + +Upon receiving an incoming initial request for which network topology hiding has to be applied and which includes a Record-Route header, the CS-IBCF shall add its own routable SIP URI to the top of the Record-Route header. + +#### A.5.2.4.2 Encryption for network topology hiding + +Upon receiving a request/response, outgoing from the hiding network the CS-IBCF shall perform the encryption for network topology hiding purposes, i.e. the CS-IBCF shall: + +- 1) use the whole header values which were added by one or more specific entity of the hiding network as input to encryption; + +- 2) not change the order of the headers subject to encryption when performing encryption; +- 3) use for one encrypted string all received consecutive header entries subject to encryption, regardless if they appear in separate consecutive headers or if they are consecutive entries in a comma separated list in one header; +- 4) construct a hostname that is the encrypted string; +- 5) append a "tokenized-by" parameter and set it to the value of the encrypting network's name, after the constructed hostname; +- 6) form one valid entry for the specific header out of the resulting NAI, e.g. prepend "SIP/2.0/UDP" for Via headers or "sip:" for Path, Route and Record-Route headers; +- 7) if the CS-IBCF encrypted an entry in the Route header, then it also inserts its own URI before the topmost encrypted entry; and +- 8) if the CS-IBCF encrypted an entry in the Via header, then it also inserts its own URI before the topmost encrypted entry. + +NOTE: Even if consecutive entries of the same network in a specific header are encrypted, they will result in only one encrypted header entry. For example: + +``` +Via: SIP/2.0/UDP ibcf1.home1.net;lr, + SIP/2.0/UDP Token( SIP/2.0/UDP msc2.home1.net;lr, + SIP/2.0/UDP msc1.home1.net;lr); + tokenized-by=home1.net, + SIP/2.0/UDP [5555::aaa:bbb:ccc:ddd] +``` + +## A.5.2.5 ALG functionality in the CS-IBCF + +The CS-IBCF shall only apply the following procedures if application level gateway functionality is required by the network. + +The CS-IBCF acts as a B2BUA when it performs ALG functionality. The CS-IBCF, although acting as a UA, does not initiate any registration of its associated addresses. These are assumed to be known by peer-to-peer arrangements within the SIP-I based CS domain. + +In case the initial INVITE request is received from own network, i.e. the CS-IBCF acts as an exit point, the CS-IBCF shall generate a new initial INVITE request and forward it to the entry point of the other network. + +The internal function of the CS-IBCF as an ALG is equal to that one defined in 3GPP TS 29.162 [37]. + +## A.5.2.6 Screening of SIP-I signalling + +### A.5.2.6.1 General + +This section relates to the screening of the SIP headers and SDP of the SIP-I signalling for policing purposes. Inspection of ISUP MIME bodies is out of the scope of this specification. + +The CS-IBCF shall act as a B2BUA when it performs screening of SIP signalling functionality. In this case the B2BUA behaviour of the CS-IBCF shall comply with the description given in subclause A.5.2.5 for the ALG functionality. + +NOTE 1: Many headers are intended for end-to-end operation; removal of such headers will impact the intended end-to-end operation between nodes. Additionally security mechanisms covering SIP headers are not precluded; any such removal can prevent validation of all headers covered by the security mechanism. + +NOTE 2: SIP-I screening is normally done by the MSC, where the encapsulated ISUP message and the SIP headers are consistently screened. + +### A.5.2.6.2 CS-IBCF procedures for SIP headers + +If specified by local policy rules, the CS-IBCF may omit or modify any received SIP headers prior to forwarding SIP messages, with some exceptions. + +NOTE 1: If the CS-IBCF modifies SIP information elements (SIP headers, SIP message bodies) other than as specified by SIP procedures (e.g., IETF RFC 3261 [20]) caution needs to be taken that SIP functionality (e.g., routing using Route, Record-Route and Via) is not impacted in a way that could create interoperability problems with networks that assume that this information is not modified. + +NOTE 2: Where operator requirements can be achieved by configuration hiding, then these procedures can be used in preference to screening. + +#### A.5.2.6.3 CS-IBCF procedures for SIP message bodies + +If IP address translation (NA(P)T or IP version interworking) occurs on the user plane, the CS-IBCF shall modify SDP according to 3GPP TS 29.162 [37]. + +#### A.5.2.7 Void + +### A.5.3 CS-IBCF as an entry point + +#### A.5.3.1 Initial requests + +Upon receipt of any request, the CS-IBCF shall: + +- 1) if the request is an INVITE request, then respond with a 100 (Trying) provisional response; +- 2) if the request is an INVITE request and the CS-IBCF is configured to perform application level gateway and/or transport plane control functions, save the Contact, Cseq, From and Record-Route header field values received in the request such that the CS-IBCF is able to release the session if needed; +- 3) if network topology hiding is required, then apply the procedures as described in subclause A.5.3.4; +- 4) if screening of SIP signalling is required, apply the procedures as described in subclause A.5.3.6; +- 5) If CS-IBCF receives an initial request for a dialogue or standalone transaction that contains a single Route header pointing to itself, and it is co-located with an (G)MSC server, or it has a preconfigured (G)MSC server to be contacted, then forward the request to that (G)MSC server. Otherwise select an (G)MSC server and forward the request to that (G)MSC server. + +When the CS-IBCF receives an INVITE request, the CS-IBCF may require the periodic refreshment of the session to avoid hung states in the CS-IBCF. If the CS-IBCF requires the session to be refreshed, the CS-IBCF shall apply the procedures described in IETF RFC 4028 [31] clause 8. + +When the CS-IBCF receives a response to an initial request (e.g. 183 or 2xx), the CS-IBCF shall: + +- 1) if network topology hiding is required, apply the procedures as described in subclause A.5.3.4; +- 2) if screening of SIP signalling is applied, apply the procedures as described in subclause A.5.3.6; and +- 3) if the response establishes a dialogue, and the CS-IBCF is configured to perform application level gateway and/or transport plane control functions, the CS-IBCF shall save the Contact, To and Record-Route header field values received in the response such that the CS-IBCF is able to release the session if needed. + +#### A.5.3.2 Subsequent requests + +Upon receipt of any request, the CS-IBCF shall: + +- 1) if the request is an INVITE request, then respond with a 100 (Trying) provisional response; +- 2) if the request is a target refresh request and the CS-IBCF is configured to perform application level gateway and/or transport plane control functions, save the Contact and Cseq header field values received in the request such that the CS-IBCF is able to release the session if needed; +- 3) if the subsequent request is other than a target refresh request (including requests relating to an existing dialogue where the method is unknown) and the CS-IBCF is configured to perform application level gateway and/or transport plane control functions, save the Contact and Cseq header field values received in the request such that the CS-IBCF is able to release the session if needed; + +- 4) if network topology hiding is required, then apply the procedures as described in subclause A.5.3.4; +- 5) if screening of SIP signalling is required, apply the procedures as described in subclause A.5.3.6. + +When the CS-IBCF receives a response to the subsequent request and network topology hiding is required, then the CS-IBCF shall apply the procedures as described in subclause A.5.3.4. + +When the CS-IBCF receives a response to the subsequent request and screening of SIP signalling is required, then the CS-IBCF shall apply the procedures as described in subclause A.5.3.6. + +### A.5.3.3 CS-IBCF-initiated call release + +If the CS-IBCF provides transport plane control functionality and receives an indication of a transport plane related error the CS-IBCF may: + +- 1) if the CS-IBCF has already sent an initial INVITE request to the terminating side, apply SIP procedures detailed in IETF RFC 3261 [20] to terminate any corresponding SIP dialogue(s) or otherwise cancel the INVITE at the terminating side, making use of CANCEL and/or BYE request(s), based on information saved for the related dialogue; and +- 2) if the CS-IBCF has not yet sent out a final response for the initial INVITE request, send an appropriate failure response for the initial INVITE request to the originating side; and +- 3) if the CS-IBCF has already sent out a final response for the initial INVITE request, generate a BYE request for the originating side based on the information saved for the related dialogue. + +NOTE 1: Transport plane related errors can be indicated from e.g. TrGW. + +NOTE 2: Since the CS-IBCF does not handle the encapsulated ISUP, the BYE message(s) generated by the CS-IBCF will not contain any encapsulated ISUP REL message. + +If the CS-IBCF is able to determine an appropriate Q.850 cause value, then this may be included in a Reason header in the BYE message(s). + +### A.5.3.4 THIG functionality in the CS-IBCF + +#### A.5.3.4.1 General + +The following procedures shall only be applied if network topology hiding is required by the network. The network requiring network topology hiding is called the hiding network. + +NOTE 1: Requests and responses are handled independently; therefore, no state information is needed for that purpose within a CS-IBCF. + +The CS-IBCF shall apply network topology hiding to all headers which reveal topology information, such as Via, Route, Record-Route, and Path. Therefore, the CS-IBCF shall + +- either act as a B2BUA, i.e. set above headers as defined for a SIP user agent client by IETF RFC 3261 [20], +- or as an option follow the procedures defined in A.5.3.4.2. + +The CS-IBCF shall not screen SIP parameters for which there is a related ISUP parameter defined within ITU-T Recommendation Q.1912.5 [6]. + +NOTE 2: SIP-I screening is normally done by the GMSC, where the encapsulated ISUP message and the SIP headers are consistently screened. + +Upon receiving an incoming initial request for which network topology hiding has to be applied and which includes a Record-Route header, the CS-IBCF shall add its own routable SIP URI to the top of the Record-Route header. + +#### A.5.3.4.2 Decryption for network topology hiding + +Upon receiving a request/response, incoming to the hiding network, the CS-IBCF shall perform the decryption for network topology hiding purposes, i.e. the CS-IBCF shall: + +- 1) identify hostnames encrypted by the network this CS-IBCF belongs to within all headers of the incoming message; +- 2) use those hostnames that carry the identification of the hiding network within the value of the "tokenized-by" parameter as input to decryption; +- 3) use as encrypted string the hostname which follows the sent-protocol (for Via Headers, e.g. "SIP/2.0/UDP") or the URI scheme (for Route and Record-Route Headers, e.g. "sip:"); +- 4) replace all content of the received header which carries encrypted information with the entries resulting from decryption. + +EXAMPLE: An encrypted entry to a Via header that looks like: + +``` +Via: SIP/2.0/UDP Token(SIP/2.0/UDP msc2.home1.net;lr, +SIP/2.0/UDP msc1.home1.net;lr);tokenized-by=home1.net +``` + +will be replaced with the following entries: + +``` +Via: SIP/2.0/UDP msc2.home1.net;lr, SIP/2.0/UDP msc1.home1.net;lr +``` + +NOTE: Motivations for these decryption procedures are e.g. to allow the correct routing of a response through the hiding network, to enable loop avoidance within the hiding network, or to allow the entities of the hiding network to change their entries within e.g. the Record-Route header. + +### A.5.3.5 ALG functionality in the CS-IBCF + +The CS-IBCF shall only apply the following procedures if application level gateway functionality is required by the network. + +The CS-IBCF acts as a B2BUA when it performs ALG functionality. The CS-IBCF, although acting as a UA, does not initiate any registration of its associated addresses. These are assumed to be known by peer-to-peer arrangements within the SIP-I based CS domain. + +When the CS-IBCF receives an initial INVITE request from another SIP network, the CS-IBCF shall generate a new initial INVITE request and forward it to the (G)MSC Server. + +The internal function of the CS-IBCF as an ALG is equal to that one defined in 3GPP TS 29.162 [37]. + +### A.5.3.6 Screening of SIP-I signalling + +The text in subclause A.5.2.6 applies without changes. + +### A.5.3.7 Void + +--- + +## A.6 Procedures at the CS-TrGW + +### A.6.1 Transport Plane Control procedures + +--- + +## A.7 CS-IBCF – CS-TrGW Interaction + +### A.7.1 General + +#### A.7.1.1 Network Model + +Figure A.7.1.1.1 shows the network model. The broken line represents the call control signalling. The dotted line represents the bearer control signalling (if applicable) and the user plane. The CS-IBCF uses one context with two terminations in the TrGW. The termination T1 is used towards the 3GPP PLMN and the bearer termination T2 is used for the bearer towards the external IP network. + +![Diagram of the H.248 Context Model showing a 3GPP PLMN connected to a CS-IBCF, which is connected to a TrGW, which is connected to an External Network. The TrGW contains two terminations, T1 and T2, and a context (CTXI) represented by an 'X'.](719ef0f734259484038b2434e5dc3f24_img.jpg) + +The diagram illustrates the H.248 Context Model. On the left is a rounded rectangle labeled "3GPP PLMN". On the right is a rounded rectangle labeled "Ext Network". In the center, there are two stacked rounded rectangles. The top one is labeled "CS-IBCF" and has a double-headed arrow connecting it to the "3GPP PLMN" via a dashed green line and to the "Ext Network" via a dashed green line. The bottom one is labeled "TrGW" and contains two terminations, "T1" and "T2", and a context "CTXI" represented by an "X". The "TrGW" is connected to the "CS-IBCF" via a solid blue line. The "TrGW" is connected to the "3GPP PLMN" via a dashed red line and to the "Ext Network" via a dashed red line. + +Diagram of the H.248 Context Model showing a 3GPP PLMN connected to a CS-IBCF, which is connected to a TrGW, which is connected to an External Network. The TrGW contains two terminations, T1 and T2, and a context (CTXI) represented by an 'X'. + +Figure A.7.1.1.1: H.248 Context Model + +## A.7.1.2 Signalling flows + +### A.7.1.2.1 Basic Procedures + +#### A.7.1.2.1.1 Call Establishment + +Figure A.7.1.2.1.1.1 depicts the signalling flow for a call setup from external network towards 3GPP PLMN. The same signalling flow applies for a call setup from the 3GPP PLMN towards an external network with the exception that terminations T1 and T2 are then exchanged. + +![Sequence diagram showing the interaction between CS-TrGW and CS-IBCF for TrGW functionality. The diagram includes 16 steps: 1. SDP offer (IP2o, P2o) to CS-IBCF; 2. Use case X detected; 3. H.248 ADD req to CS-TrGW; 4. Create outgoing termination T1; 5. H.248 ADD resp; 6. Modify SDP offer; 7. SDP offer (IP1o, P1o) to network; 8. SDP answer (IP1a, P1a) from network; 9. H.248 MOD req to CS-TrGW; 10. Configure Outgoing Termination T1; 11. H.248 MOD Resp; 12. H.248 ADD req for T2; 13. Create incoming Termination T2; 14. H.248 ADD Resp; 15. Modify SDP answer; 16. SDP answer (IP2a, P2a) to network. Brackets on the right indicate 'Reserve TrGW Connection Point', 'Configure TrGW Connection Point', and 'Reserve And Configure TrGW Connection Point'.](3198cdf0dbe501c46fe0e4073c7d8451_img.jpg) + +``` + +sequenceDiagram + participant CS-TrGW + participant CS-IBCF + + Note over CS-IBCF: 1. SDP offer (IP2o, P2o) + Note over CS-IBCF: 2. Use case X detected +that needs TrGW +functionality + CS-IBCF->>CS-TrGW: 3. H.248 ADD req +(C= ?, T= ?, LAddr=?, LPort=?) + Note over CS-TrGW: 4. Create outgoing termination T1 + CS-TrGW->>CS-IBCF: 5. H.248 ADD resp. +(C=C1, T=T1, +LAddr=IP1o, LPort=P1o) + Note over CS-IBCF: 6. Modify SDP offer + Note over CS-IBCF: 7. SDP offer (IP1o, P1o) + Note over CS-IBCF: 8. SDP answer (IP1a, P1a) + CS-IBCF->>CS-TrGW: 9. H.248 MOD req +(C= C1, T= T1, +RAddr=IP1a, RPort=P1a) + Note over CS-TrGW: 10. Configure Outgoing Termination T1 + CS-TrGW->>CS-IBCF: 11. H.248 MOD Resp +(C= C1, T= T1) + CS-IBCF->>CS-TrGW: 12. H.248 ADD req +(C= C1, T= ?, LAddr=?, LPort=?, +RAddr=IP2o, RPort=P2o) + Note over CS-TrGW: 13. Create incoming Termination T2 + CS-TrGW->>CS-IBCF: 14. H.248 ADD Resp +(C= C1, T= T2, +LAddr=IP2a, LPort=P2a, +RAddr=IP1a, RPort=P1a) + Note over CS-IBCF: 15. Modify SDP answer + Note over CS-IBCF: 16. SDP answer (IP2a, P2a) + +``` + +Reserve +TrGW +Connection +Point (, +Change +Through- +Connection) + +Configure +TrGW +Connection +Point (, +Change +Through- +Connection) + +Reserve +And +Configure +TrGW +Connection +Point (, +Change +Through- +Connection) + +Sequence diagram showing the interaction between CS-TrGW and CS-IBCF for TrGW functionality. The diagram includes 16 steps: 1. SDP offer (IP2o, P2o) to CS-IBCF; 2. Use case X detected; 3. H.248 ADD req to CS-TrGW; 4. Create outgoing termination T1; 5. H.248 ADD resp; 6. Modify SDP offer; 7. SDP offer (IP1o, P1o) to network; 8. SDP answer (IP1a, P1a) from network; 9. H.248 MOD req to CS-TrGW; 10. Configure Outgoing Termination T1; 11. H.248 MOD Resp; 12. H.248 ADD req for T2; 13. Create incoming Termination T2; 14. H.248 ADD Resp; 15. Modify SDP answer; 16. SDP answer (IP2a, P2a) to network. Brackets on the right indicate 'Reserve TrGW Connection Point', 'Configure TrGW Connection Point', and 'Reserve And Configure TrGW Connection Point'. + +1. The CS-IBCF receives an SDP offer in SIP signalling. +2. The CS-IBCF detects that one of the CS-TrGW functions is required, e.g. NAPT/NAT +3. The CS-IBCF sends a H.248 ADD command to create the outgoing termination and to request resources to execute CS-TrGW function +4. The CS-TrGW creates the outgoing termination +5. The CS-TrGW replies to CS-IBCF with a H.248 Add reply command and provides the local address and port of the outgoing termination +6. The CS-IBCF replaces the IP address inside the SDP using the information coming from CS-TrGW +7. SDP offer is sent to the network at the outgoing side +8. SDP answer is received by CS-IBCF + +9. The CS-IBCF sends a H.248 MOD command to configure the outgoing termination with Address and port information received in the SDP answer + 10. The CS-TrGW configures the outgoing termination + 11. The CS-TrGW replies to CS-IBCF with a H.248 MOD reply command + 12. The CS-IBCF sends a H.248 ADD command to create the incoming termination and to request resources to execute CS-TrGW function + 13. The CS-TrGW creates the incoming termination + 14. The CS-TrGW replies to the CS-IBCF with a H.248 Add reply command and provides the local address and port of the incoming termination. +- Note: +- Steps 12 to 14 may also be executed after step 2. + 15. The CS-IBCF replaces the IP address inside the SDP using the information coming from CS-TrGW + 16. SDP answer is sent to the network at the incoming side + +**Figure A.7.1.2.1.1.1: CS-IBCF and CS-TrGW interaction at Call establishment.** + +When creating the termination T1, the CS-IBCF may also indicate that the IP Interface type is "NboIP". + +When creating the termination T2, the CS-IBCF may also indicate that the IP Interface type is "ExtSIPI". + +NOTE: The IP Interface Type allows the CS-TrGW to collect statistics per interface type associated with the RTP bearer termination as required by 3GPP TS 32.407 [44]. The provision of these statistics is outside of the scope of this specification. + +#### A.7.1.2.1.2 Call Release + +Figure A.7.1.2.1.2.1 depicts the signalling flow for a call release. + +![Sequence diagram showing the signalling flow for a call release between CS-TrGW and CS-IBCF.](ec31af936fa94a6917bf19f154df8ac3_img.jpg) + +``` +sequenceDiagram + participant CS-TrGW + participant CS-IBCF + Note right of CS-IBCF: 1. Event causing release + CS-IBCF->>CS-TrGW: 2. H.248 SUB req (C=C1, T=T1) + Note left of CS-IBCF: Release TrGW Termination + CS-TrGW->>CS-IBCF: 3. Destroy outgoing termination T1 + CS-IBCF->>CS-TrGW: 4. H.248 SUB resp. (C=C1, T=T1) + CS-IBCF->>CS-TrGW: 5. H.248 SUB req (C=C1, T=T2) + Note left of CS-IBCF: Release TrGW Termination + CS-TrGW->>CS-IBCF: 6. Destroy incoming termination T2 + CS-IBCF->>CS-TrGW: 7. H.248 SUB resp. (C=C1, T=T2) +``` + +The diagram illustrates the signalling flow for a call release between the CS-TrGW and the CS-IBCF. It begins with an event causing the release at the CS-IBCF. The CS-IBCF sends an H.248 SUB request (C=C1, T=T1) to the CS-TrGW. The CS-TrGW then destroys the outgoing termination T1 and responds with an H.248 SUB response (C=C1, T=T1). Next, the CS-IBCF sends an H.248 SUB request (C=C1, T=T2) to the CS-TrGW. The CS-TrGW destroys the incoming termination T2 and responds with an H.248 SUB response (C=C1, T=T2). Brackets on the right side of the diagram indicate that the first two steps (1-2) correspond to 'Release TrGW Termination' and the last two steps (5-6) also correspond to 'Release TrGW Termination'. + +Sequence diagram showing the signalling flow for a call release between CS-TrGW and CS-IBCF. + +1. The CS-IBCF identifies that the call is to be released. Typically this will be by the receipt of a SIP BYE request. +2. The CS-IBCF sends a H.248 SUB command to release the outgoing termination +3. The CS-TrGW destroys the outgoing termination +4. The CS-TrGW replies to CS-IBCF with a H.248 Sub reply command +5. The CS-IBCF sends a H.248 SUB command to release the incoming termination +6. The CS-TrGW destroys the incoming termination +7. The CS-TrGW replies to CS-IBCF with a H.248 Sub reply command + +Note 1: Steps 5 to 7 may also be executed before steps 2 to 4 or in parallel with steps 2 to 4. + +Note 2: Rather than releasing the two terminations separately, the CS-IBCF may request the CS-TrGW to release both terminations in a single request. + +**Figure A.7.1.2.1.2.1: CS-IBCF and CS-TrGW interaction at Call release** + +## A.7.1.2.2 Specific Use Cases + +### A.7.1.2.2.1 CS-IBCF as Entry Point, Call Establishment with IP Version Interworking + +This case considers the call establishment message flow for the CS-IBCF and CS-TrGW, when the CS-IBCF is acting as an Entry point and IP version interworking is required. The example assumes that the external SIP-I network uses IPv4 addressing and the CS CN uses IPv6 addressing. + +With reference to the steps in figure A.7.1.2.1.1.1, the following additions are required, specific to this use case: + +3. The CS-IBCF requests the CS-TrGW to choose an IPv6-based local connection address for the created outgoing termination. +5. The local address and port returned to the CS-IBCF are IPv6-based. +6. Specifically, the IPv6 address and port number received from the CS-TrGW in the local connection address of the outgoing termination replace the IPv4 address and port number received from the external SIP-I network. +9. Specifically, the CS-IBCF passes the IPv6 address and port number received in the SDP answer to the CS-TrGW as the remote connection address on the outgoing termination. +12. The CS-IBCF requests the CS-TrGW to choose an IPv4-based local connection address on the incoming termination. The CS-IBCF uses the IPv4 addresses and port numbers received in the initial SDP offer as the remote connection address on the incoming termination. +14. The local address and port returned to the CS-IBCF are IPv4-based. +15. Specifically, the IPv4 address and port number received from the CS-TrGW in the local connection address of the incoming termination replace the IPv6 address and port number received from the CS-CN. + +### A.7.1.2.2.2 Hanging Termination Detection + +This subclause considers the message flow for the CS-IBCF and CS-TrGW, when IP hanging termination detection is required. Hanging termination detection procedure allows the CS-IBCF to detect a hanging context and termination in the TrGW resulting, for example, from a loss of communication between the CS-IBCF and the CS-TrGW. + +When the CS-IBCF requests the CS-TrGW to reserve terminations, the CS-IBCF shall also request the CS-TrGW to periodically report termination heartbeat indications. If the CS-IBCF includes an indication of the periodicity of the termination heartbeat notifications, the specified period shall be much greater than the mean call holding time. + +The CS-IBCF and the CS-TrGW shall support detection of hanging terminations. + +The call is established as described in subclause A.7.1.2.1.1. With reference to the steps in figure A.7.1.2.1.1, the following additions are required, specific to this use case: + +3. The CS-IBCF requests the CS-TrGW to send termination heartbeat notifications for the created termination. It may also include an indication of the periodicity of the termination heartbeat notifications. +12. The CS-IBCF requests the CS-TrGW to send termination heartbeat notifications for the created termination. It may also include an indication of the periodicity of the termination heartbeat notifications. + +Subsequently, the CS-TrGW shall periodically send termination heartbeat notifications, as shown in figure A.7.1.2.2.2.1, until the call is released. + +When the CS-IBCF receives a termination heartbeat notification from the CS-TrGW via the Termination heartbeat - Indication procedure, the CS-IBCF shall return a Termination heartbeat -Indication Ack (without an error) if the context id / termination identity combination exists in the CS-IBCF. If this combination does not exist, the CS-IBCF + +shall return an error and shall correct the mismatch, for example by requesting the CS-TrGW to subtract the indicated termination and to clear any associated context. + +![Sequence diagram showing the interaction between CS-TrGW and CS-IBCF for termination heartbeat notifications. CS-TrGW sends a 'Termination Heartbeat Indication' to CS-IBCF, and CS-IBCF responds with a 'Termination Heartbeat Indication Ack'.](e5ded42f8e352da02ee86cb55550c45d_img.jpg) + +``` + +sequenceDiagram + participant CS-TrGW + participant CS-IBCF + Note left of CS-TrGW: CS-TrGW + Note right of CS-IBCF: CS-IBCF + CS-TrGW->>CS-IBCF: Termination Heartbeat Indication + CS-IBCF-->>CS-TrGW: Termination Heartbeat Indication Ack + +``` + +Sequence diagram showing the interaction between CS-TrGW and CS-IBCF for termination heartbeat notifications. CS-TrGW sends a 'Termination Heartbeat Indication' to CS-IBCF, and CS-IBCF responds with a 'Termination Heartbeat Indication Ack'. + +**Figure A.7.1.2.2.2.1: CS-IBCF and CS-TrGW interaction for termination heartbeat notifications** + +#### A.7.1.2.2.3 Gate Management + +This subclause considers the message flow for the CS-IBCF and CS-TrGW, when the CS-IBCF is acting as an Entry point and remote source address filtering is required for the termination towards the external SIP-I network. + +Gate Management shall be a mandatory feature of the CS-TrGW, but an optional feature of the CS-IBCF. + +As a security related option, on request from the CS-IBCF, filtering may be enabled to check/validate the source address or source address and port number of incoming packets from the external network. If the CS-IBCF requests address filtering, it may additionally provide an address specification, which may identify either a single address or a range of addresses, against which filtering is to be performed. The absence of such an address specification in the request implicitly requests filtering against the IP address of the remote connection address. In addition to address filtering, the CS-IBCF may also request port filtering. If the CS-IBCF requests port filtering, it may additionally include either a port or a range of ports, against which filtering is to be performed. The absence of a port specification in the request implicitly requests filtering against the port of the remote connection address. + +If the CS-TrGW is configured to apply source IP address and possibly source port filtering, it shall only pass incoming IP packets from the identified source, and discard IP packets from other sources. + +The call is established as described in subclause A.7.1.2.1.1. With reference to the steps in figure A.7.1.2.1.1.1, the following additions are required, specific to this use case: + +12. If remote source address filtering is required for the created termination, then the CS-IBCF includes the information element "Remote source address filtering" in the request sent to the CS-TrGW. In addition, it may also include the information element "Remote source address mask". +If remote source port filtering is required for the created termination (in addition to remote source address filtering), then the CS-IBCF includes the information element "Remote source port filtering" in the request sent to the CS-TrGW. It may also include one of the information elements "Remote source port" or "Remote source port range". + +Subsequently, the CS-TrGW applies filtering as requested to the packets arriving from the external network. Any packet arriving, which does not meet the filtering requirement, is discarded. + +#### A.7.1.2.2.4 QoS Packet Marking + +This subclause considers the message flow for the CS-IBCF and CS-TrGW, when the CS-IBCF requires the use of differentiated services (see IETF RFC 2474 [41]). + +It is optional for the CS-IBCF to support differentiated service controlled over the Ix Interface. It shall be mandatory for the CS-TrGW to support differentiated service controlled over the Ix Interface. A CS-TrGW can also support DiffServ Code Point marking based on local configuration. The CS-IBCF may request the CS-TrGW to set diffserv codepoints for outgoing packets on a termination. The CS-IBCF may either indicate the applicable DSCP value or configure the TrGW to copy the DSCP value in the corresponding received packet. When the CS-IBCF requests the CS-TrGW to create a termination and if differentiated services are required for the created termination, the CS-IBCF shall include the information elements "DiffServ Code Point" and/or "DiffServ Tagging Behaviour" in the request sent to the CS-TrGW. + +The call is established as described in subclause A.7.1.2.1.1. With reference to the steps in figure A.7.1.2.1.1.1, the following additions are required, specific to this use case: + +3. If differentiated services are required for the created termination, then the CS-IBCF includes the information elements "DiffServ Code Point" and/or "DiffServ Tagging Behaviour" in the request sent to the CS-TrGW. +12. If differentiated services are required for the created termination, then the CS-IBCF includes the information elements "DiffServ Code Point" and/or "DiffServ Tagging Behaviour" in the request sent to the CS-TrGW. + +Subsequently, for all egress packets, the CS-TrGW shall set the DiffServ Code Point in the IP header as specified by the CS-IBCF: + +- If the DiffServ Tagging Behaviour information element was received with a value to indicate that the DiffServ Code Point should be copied, then the CS-TrGW shall copy the DiffServ Code Point in the IP header of the egress packet from the ingress packet. +- If the DiffServ Tagging Behaviour information element was not received, or was received with a value to indicate that the DiffServ Code Point should be set to a specific value, then: + - If the DiffServ Code Point information element was received, then the CS-TrGW shall set the DiffServ Code Point in the IP header of the egress packet to the value received in the DiffServ Code Point information element. + - If the DiffServ Code Point information element was not received, then the CS-TrGW may set the DiffServ Code Point in the IP header of the egress packet to a configured default value. + +#### A.7.1.2.2.5 IP Realms + +This subclause considers the message flow for the CS-IBCF and CS-TrGW, when the two networks are in different IP realms. IP realms are described in 3GPP TS 23.205 [9] clause 20. + +The CS-IBCF and the CS-TrGW shall support IP realm indication. + +The call is established as described in subclause A.7.1.2.1.1. With reference to the steps in figure A.7.1.2.1.1.1, the following additions are required, specific to this use case: + +3. The CS-IBCF may specify the required IP Realm. +4. The CS-TrGW allocates resources from the appropriate IP realm as specified by the CS-IBCF in step 3. +12. The CS-IBCF may specify the required IP Realm. +13. The CS-TrGW allocates resources from the appropriate IP realm as specified by the CS-IBCF in step 12. + +If there is a change in the IP Realms that are available or if they are modified in the CS-TrGW then the CS-TrGW shall inform the CS-IBCF via the IP Realm Availability Procedure (see subclause A.7.2.3), if this procedure is supported by the CS-TrGW. The basic flow is depicted in figure A.7.1.2.2.5.1 + +![Sequence diagram showing the IP Realm Availability procedure between CS-TrGW and CS-IBCF.](d074df4244ecf1bcd74fc55886a902f9_img.jpg) + +``` +sequenceDiagram + participant CS-TrGW + participant CS-IBCF + Note left of CS-TrGW: CS-TrGW monitors IP realm availability + CS-TrGW->>CS-IBCF: IP Realm Availability Indication + CS-IBCF-->>CS-TrGW: IP Realm Availability Indication Ack +``` + +The diagram illustrates a sequence of messages between two entities: CS-TrGW and CS-IBCF. The CS-TrGW sends a message labeled "IP Realm Availability Indication" to the CS-IBCF. The CS-IBCF responds with a message labeled "IP Realm Availability Indication Ack" back to the CS-TrGW. + +Sequence diagram showing the IP Realm Availability procedure between CS-TrGW and CS-IBCF. + +**Figure A.7.1.2.2.5.1: IP Realm Availability** + +The monitoring of IP realm availability is optional and if supported by the CS-TrGW may be requested by the CS-IBCF. + +#### A.7.1.2.2.6 Media Inactivity Detection + +The CS-TrGW and the CS-IBCF may support the detection of inactive media flows. + +The CS-IBCF may request a CS-TrGW that supports media inactivity detection to detect if a media flow is inactive. + +NOTE: The decision to apply or not to apply media inactivity detection is general for all sessions with the same media characteristics (i.e. not user specific). Detailed conditions when media inactivity detection can be requested are not specified in the present release. + +When the CS-IBCF requests the CS-TrGW to reserve transport addresses/resources, the CS-IBCF may indicate to the CS-TrGW that detection of an inactive media flow is required and may additional specify inactivity detection time and inactivity detection direction. The IBCF may request the detection of media inactivity on a termination or a stream basis. + +The call is established as described in subclause A.7.1.2.1.1. With reference to the steps in figure A.7.1.2.1.1.1, the following additions are required, specific to this use case: + +3. The CS-IBCF indicates to the CS-TrGW that detection of an inactive media flow is required and can additional specify inactivity detection time and inactivity detection direction. +12. The CS-IBCF indicates to the CS-TrGW that detection of an inactive media flow is required and can additional specify inactivity detection time and inactivity detection direction. + +The CS- TrGW shall determine a media flow to be inactive if there is no media sent and/or received within the inactivity detection time period. + +When the CS-IBCF receives a notification of inactive media from the CS-TrGW via the Media Inactivity Notification procedure, the CS-IBCF shall return a Media Inactivity Notification Ack and shall take appropriate action (e.g. release the termination). + +![Sequence diagram showing Media Inactivity Notification between IBCF and TrGW.](205c14458d7f4e2d22c75354bb451e99_img.jpg) + +``` +sequenceDiagram + participant IBCF + participant TrGW + Note right of TrGW: Media Inactivity Notification + TrGW->>IBCF: Media Inactivity Notification + Note left of IBCF: Media Inactivity Notification - Ack + IBCF->>TrGW: Media Inactivity Notification - Ack +``` + +The diagram illustrates a sequence of messages between two entities, IBCF and TrGW. The IBCF is on the left and the TrGW is on the right. A message labeled 'Media Inactivity Notification' is sent from the TrGW to the IBCF. In response, a message labeled 'Media Inactivity Notification - Ack' is sent from the IBCF to the TrGW. + +Sequence diagram showing Media Inactivity Notification between IBCF and TrGW. + +**Figure A.7.1.2.2.6.1: Media Inactivity Notification** + +#### A.7.1.2.2.7 RTCP Handling + +The CS-IBCF and the CS-TrGW shall support control via the Ix interface of the specific RTCP behaviour associated to an RTP flow. + +When the CS-IBCF requests the CS-TrGW to reserve transport addresses/resources for an RTP flow, the CS-IBCF may indicate to the CS-TrGW whether to reserve corresponding RTCP resources should also request the CS-TrGW to reserve resources for the corresponding RTCP flow, but may alternatively request the CS-TrGW not to reserve resources for the corresponding RTCP flow. When the CS-IBCF requests the CS-TrGW to reserve transport addresses/resources for a non-RTP flow, the CS-IBCF shall not request the CS-TrGW to reserve resources for an RTCP flow. + +To request the CS-TrGW to reserve resources for an RTCP flow, the CS-IBCF shall provide the RTCP handling information element with a value indicating that resources for RTCP shall be reserved. + +To request the CS-TrGW not to reserve resources for an RTCP flow, the CS-IBCF shall either provide the RTCP handling information element with a value indicating that resources for RTCP shall not be reserved or omit the RTCP handling information element. + +If the CS-TrGW receives the indication to reserve RTCP resources, the TrGW shall allocate a local port with even number for an RTP flow also reserve the consecutive local port with odd number for the associated RTCP flow, and it shall send and be prepared to receive RTCP. + +If the CS-TrGW receives the indication to not reserve RTCP resources, or does not receive any indication, it shall not allocate an RTCP port when allocating a port for an RTP flow. The CS-TrGW shall not send any RTCP packets and shall silently discard any received RTCP packets. + +When RTCP resources are requested, the CS-IBCF may also specify: + +- the remote RTCP port, and optionally the remote address, where to send RTCP packets; if not specified, the CS-TrGW shall send RTCP packets to the port contiguous to the remote RTP port; +- bandwidth allocation requirements for RTCP, if the RTCP bandwidth level for the session is different than the default RTCP bandwidth as specified in RFC 3556 [39]. + +NOTE: In line with the recommendations of RFC 3605 [40], separate address or non-contiguous RTCP port numbers will not be allocated by the TrGW. + +The CS-TrGW shall return an error if it can not allocate the requested RTCP resources. + +The call is established as described in subclause A.7.1.2.1.1. With reference to the steps in figure A.7.1.2.1.1.1, the following additions are required, specific to this use case: + +3. The CS-IBCF may specify if RTCP handling is required. +4. The CS-TrGW allocates RTCP resources as specified by the CS-IBCF in step 3. +12. The CS-IBCF may specify if RTCP handling is required. +13. The CS-TrGW allocates RTCP as specified by the CS-IBCF in step 12. + +#### A.7.1.2.2.8 Bandwidth Policing + +##### A.7.1.2.2.8.1 Overview + +The CS-IBCF may support traffic policing of incoming media flows. + +The CS-TrGW shall support traffic policing of the maximum average bitrate, defined as sustainable data rate (see IETF RFC 2216 [42]) of incoming media flows and may support traffic policing of the peak data rate of incoming media flows. + +The CS-IBCF may require the CS-TrGW to police the media flows to ensure that they conform to the expected data rates. + +When the CS-IBCF requests the CS-TrGW to reserve transport addresses/resources, the CS-IBCF may indicate to the CS-TrGW that policing of the related media streams is required and provide traffic policing related parameters as detailed in subclause A.7.1.2.2.8.2. + +If such policing is requested, the CS-TrGW shall police the corresponding media streams as detailed in subclause A.7.1.2.2.8.2, by measuring the data rate for the received packets within that media stream. If the permissible data rate provided by the CS-IBCF is exceeded, the CS-TrGW shall discard packets to reduce their data rate to the permissible data rate. + +##### A.7.1.2.2.8.2 Bandwidth policing procedures + +The call is established as described in subclause A.7.1.2.1.1. With reference to the steps in figure A.7.1.2.1.1.1, the following additions are required, specific to this use case: + +3. If traffic policing is required for the created termination, then the CS-IBCF shall include the information element "Traffic Policing Required" in the request sent to the CS-TrGW. If policing of sustainable data rate is required, then the CS-IBCF shall include the information elements "Sustainable Data Rate" and "Maximum Burst Size" in the request. If policing of peak data rate is required, then the CS-IBCF shall include the information element "Peak Data Rate" in the request and may additionally include the information element "Delay Variation Tolerance". +12. If traffic policing is required for the created termination, then the CS-IBCF shall include the information element "Traffic Policing Required" in the request sent to the CS-TrGW. If policing of sustainable data rate is required, then the CS-IBCF shall include the information elements "Sustainable Data Rate" and "Maximum Burst Size" in the request. If policing of peak data rate is required, then the CS-IBCF shall include the information element "Peak Data Rate" in the request and may additionally include the information element "Delay Variation Tolerance". + +When requested by the CS-IBCF, the CS-TrGW shall police the media stream flow rates according to one or more of the following media policing(s), in accordance with IETF RFC 2216 [42]. + +The following media policing shall be supported at the CS-TRGW: + +- **Sustainable Data Rate (SDR) Policing:** + +To request policing of the sustainable data rate of a media stream, the CS-IBCF shall request media policing for that media stream and shall provide the sustainable data rate, and shall provide a maximum burst size (MBS) indicating the expected maximum size of packet bursts for that media stream. The CS-TrGW shall then measure the data rate for the received packets within that media stream as per IETF RFC 2216 [42] for "Token Bucket", where $r$ =SDR and $b$ =MBS. If the permissible sustainable data rate is exceeded, the CS-TRGW shall discard packets to reduce the data rate to the permissible sustainable data rate. + +NOTE 1: The CS-IBCF can derive the sustainable data rate from bandwidth parameters if it receives them within an SDP description. + +The following media policing may be supported in addition at the CS-TRGW; if supported, then the following applies: + +- **Peak Data Rate Policing:** + +To request policing of the peak data rate of a media stream, the CS-IBCF shall request media policing for that media stream and shall provide the peak data rate, and may provide a Delay Variation Tolerance indicating the expected maximum delay variation due to jitter for that media stream. The CS-TRGW shall then measure the data rate for the received packets within that media stream. If the permissible peak data rate is exceeded, the CS-TRGW shall discard packets to reduce the data rate to the permissible peak data rate. If both peak data rate and sustainable data rate have been provided for the same media stream, the CS-TRGW shall discard packets to reduce the data rate to the permissible peak data rate and should discard packets to reduce the data rate to the permissible sustainable data rate. + +NOTE 2: The decision to apply or not traffic policing is general for all sessions with the same media characteristics (i.e. not user specific). The conditions which media policings to apply are beyond the scope of the specification. This can be based on the media characteristics of the session (e.g. media type). + +#### A.7.1.2.2.9 Through-Connection + +The Change Through-Connection procedure is mandatory for CS-IBCF and CS-TrGW to support. + +The CS-IBCF sets the Stream mode parameter using the Change Through-Connection procedure to request the CS-TrGW to both-way or one-way through-connect or block media streams on a termination. + +The CS-IBCF may combine the Change Through-Connection procedure with the Reserve and Configure TrGW Connection Point, Reserve TrGW Connection Point or Configure TrGW Connection Point procedure in figure A.7.1.2.1.1.1., or may apply this procedure separately. + +#### A.7.1.2.2.10 Emergency Call + +This procedure is identical to that of subclause A.7.1.2.1.1 apart from the CS-IBCF requesting the CS-TrGW to treat the call as emergency call with a preferential handling by including the information element "Emergency Call Indicator" when creating a context within the "Reserve and Configure TrGW Connection Point" or "Reserve TrGW Connection Point" procedure. + +With reference to the steps in figure A.7.1.2.1.1, the following additions are required, specific to this use case: + +3. If step 3 is performed before step 13, the CS-IBCF requests the CS-TrGW to handle the call as emergency call by including the "Emergency Call Indicator". +13. If step 13 is performed before step 3, the CS-IBCF requests the CS-TrGW to handle the call as emergency call by including the "Emergency Call Indicator". + +## A.7.2 Ix Signalling Procedures + +### A.7.2.1 Introduction + +This subclause describes the logical signalling procedures (i.e. message identifiers are not part of the protocol) between the CS-IBCF and CS-TrGW. The procedures within this subclause are intended to be implemented using the standard H.248 procedure as defined in ITU-T Recommendation H.248.1 [33] with appropriate parameter combinations. + +## A.7.2.2 Call Related Procedures + +### A.7.2.2.1 Reserve TrGW Connection Point + +This procedure is used to reserve a termination at the CS-TrGW. + +**Table A.7.2.2.1.1: Reserve TrGW Connection Point** + +| Procedure | Initiated | Information element name | Information element required | Information element description | +|-------------------------------|-----------|----------------------------------|------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Reserve TrGW Connection Point | CS-IBCF | Context/Context Request | M | This information element indicates the existing context or requests a new context for the bearer termination. | +| | | Emergency Call Indicator | O | This information element identifies the call as emergency call that requires a preferential handling. | +| | | Termination Request | M | This information element requests a new termination for the bearer to be established. | +| | | IP Interface | O | This information element specifies the type of external interface to be used for the IP termination (e.g. ExtSIPI, NboIP). | +| | | Local IP Resources | O | This information element indicates the resource(s) (e.g. codec, auxiliary payload types) for which the CS-TrGW shall be prepared to receive user data. | +| | | ReserveValue | C | This information element indicates if multiple local resources are to be reserved.
This information element shall be included if a speech codec and auxiliary payload types are configured. | +| | | Local Connection Address Request | M | This information element requests an IP address and port number on the CS-TrGW that the remote end can send user plane data to. | +| | | Notify termination heartbeat | M | This information element requests termination heartbeat indications and may specify their periodicity. | +| | | Notify Released Bearer | O | This information element requests a notification of a released bearer. | +| | | IP Realm Identifier | O | This information element indicates the IP realm of the IP termination. | +| | | IP Version | C | This information element indicates the version of the internet protocol to be applied at the termination for the user plane. This is required for IP address translation. | +| | | DiffServ Code Point | O | This information element indicates a specific DiffServ code point to be used in the IP header in packets sent on the IP termination. | +| | | DiffServ Tagging Behaviour | O | This information element indicates whether the Diffserv code point in the IP header in packets sent on the IP termination should be copied from the received value or set to a specific value. | +| | | Remote Source Address Filtering | O | This information element indicates that remote source address filtering is required. | +| | | Remote Source Address Mask | C | This information element provides information on the valid remote source addresses. This may be included if remote source address filtering is included. It shall not be included if remote source address filtering is not included. | +| | | Remote Source Port Filtering | O | This information element indicates that remote source port filtering is required. | + +| | | | | | +|-----------------------------------|---------|-------------------------------------|---|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | | Remote Source Port | C | This information element identifies the valid remote source port. This may be included if remote source port filtering is included. It shall not be included if remote source port filtering is not included. (NOTE 1) | +| | | Remote Source Port Range | C | This information element identifies a range of valid remote source ports. This may be included if remote source port filtering is included. It shall not be included if remote source port filtering is not included. (NOTE 1) | +| | | Media Inactivity Detection Required | O | This information element indicates that detection of inactive media flows is required. | +| | | Inactivity Detection Time | C | This information element may be present if Inactive Media Detection is required and specifies the Inactivity Detection time. | +| | | Inactivity Detection Direction | C | This information element may be present if Inactive Media Detection is required and specifies the Inactivity Detection direction. | +| | | RTCP handling | O | Indicates whether or not the CS-TrGW shall reserve a port for an RTCP flow. | +| | | Traffic Policing Required | O | This information element indicates that policing of the media flow is required. | +| | | Peak Data Rate | O | This information element may be present if Policing is required and specifies the permissible peak data rate for a media stream. (NOTE 2) | +| | | Sustainable Data Rate | O | This information element may be present if Policing is required and specifies the permissible sustainable data rate for a media stream. (NOTE 2) | +| | | Delay Variation Tolerance | O | This information element may be present if Policing on Peak Data Rate is required and specifies the maximum expected delay variation tolerance for the corresponding media stream. | +| | | Maximum Burst Size | C | This information element shall be present if Policing on Sustainable Data Rate is required and specifies the maximum expected burst size for the corresponding media stream. | +| Reserve TrGW Connection Point Ack | CS-TrGW | Context | M | This information element indicates the context where the command was executed. | +| | | Termination | M | This information element indicates the termination where the command was executed. | +| | | Local IP Resources | C | This information element indicates the resources that the CS-TrGW has reserved to receive the user plane data from the remote peer. This IE shall be present if it was contained in the request. If the IE was not contained in the request, it may be present in the reply. | +| | | Local Connection Address | M | This information element indicates the IP address and port on the CS-TrGW that shall receive user plane data from the remote peer. | + +NOTE 1: Remote Source Port and Remote Source Port Range are mutually exclusive. + +NOTE 2: At least one of these IEs shall be present when policing is required. + +### A.7.2.2.2 Configure TrGW Connection Point + +This procedure is used to configure or reconfigure a termination at the CS-TrGW. + +**Table A.7.2.2.2.1: Configure TrGW Connection Point** + +| Procedure | Initiated | Information element name | Information element required | Information element description | +|---------------------------------|-----------|-------------------------------------|------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Configure TrGW Connection Point | CS-IBCF | Context | M | This information element indicates the existing context. | +| | | Termination | M | This information element indicates the existing bearer termination. | +| | | IP Interface | O | This information element specifies the type of external interface to be used for the IP termination (e.g. ExtSIPI, NboIP). | +| | | Local IP Resources | O | This information element indicates the resources (e.g. codec, auxiliary payload types) that the CS-TrGW may use on the reception of user plane data. | +| | | Remote IP Resources | O | This information element indicates the resources (e.g. codec, auxiliary payload types) that the CS-TrGW may send user plane data to. | +| | | Local Connection Address | O | This information element indicates the IP address and port on the CS-TrGW that the remote peer can send user plane data to. | +| | | Remote Connection Address | O | This information element indicates the IP address and port that the CS-TrGW can send user plane data to. | +| | | Reserve Value | O | This information element indicates if multiple resources are to be reserved. | +| | | Notify termination heartbeat | O | This information element requests termination heartbeat indications and may specify their periodicity. | +| | | DiffServ Code Point | O | This information element indicates a specific DiffServ code point to be used in the IP header in packets sent on the IP termination. | +| | | DiffServ Tagging Behaviour | O | This information element indicates whether the Diffserv code point in the IP header in packets sent on the IP termination should be copied from the received value or set to a specific value. | +| | | Remote Source Address Filtering | O | This information element indicates that remote source address filtering is required. | +| | | Remote Source Address Mask | C | This information element provides information on the valid remote source addresses. This may be included if remote source address filtering is included. It shall not be included if remote source address filtering is not included. | +| | | Remote Source Port Filtering | O | This information element indicates that remote source port filtering is required. | +| | | Remote Source Port | C | This information element identifies the valid remote source port. This may be included if remote source port filtering is included. It shall not be included if remote source port filtering is not included. (NOTE 1) | +| | | Remote Source Port Range | C | This information element identifies a range of valid remote source ports. This may be included if remote source port filtering is included. It shall not be included if remote source port filtering is not included. (NOTE 1) | +| | | Media Inactivity Detection Required | O | This information element indicates that detection of inactive media flows is required. | + +| | | | | | +|-------------------------------------|---------|--------------------------------|---|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | | Inactivity Detection Time | C | This information element may be present if Inactive Media Detection is required and specifies the Inactivity Detection time. | +| | | Inactivity Detection Direction | C | This information element may be present if Inactive Media Detection is required and specifies the Inactivity Detection direction. | +| | | RTCP handling | O | Indicates whether or not the CS-TrGW shall reserve a port for an RTCP flow. | +| | | Traffic Policing Required | O | This information element indicates that policing of the media flow is required. | +| | | Peak Data Rate | O | This information element may be present if Policing is required and specifies the permissible peak data rate for a media stream.(NOTE 2) | +| | | Sustainable Data Rate | O | This information element may be present if Policing is required and specifies the permissible sustainable data rate for a media stream.(NOTE 2) | +| | | Delay Variation Tolerance | O | This information element may be present if Policing on Peak Data Rate is required and specifies the maximum expected delay variation tolerance for the corresponding media stream. | +| | | Maximum Burst Size | C | This information element shall be present if Policing on Sustainable Data Rate is required and specifies the maximum expected burst size for the corresponding media stream. | +| Configure TrGW Connection Point Ack | CS-TrGW | Context | M | This information element indicates the context where the command was executed. | +| | | Termination | M | This information element indicates the termination where the command was executed. | +| | | Local IP Resources | O | This information element indicates the resources that the CS-TrGW has reserved to receive the user plane data from the far end. | +| | | Remote IP Resources | O | This information element indicates the resource (i.e. codec) that the CS-TrGW shall use to send user data to. | +| | | Local Connection Address | O | This information element indicates the IP address and port on the CS-TrGW that the remote end can send user plane data to. | +| | | Remote Connection Address | O | This information element indicates the IP address and port that the CS-TrGW can send user plane data to. May be present only if corresponding IE is present in the request. | + +NOTE 1: Remote Source Port and Remote Source Port Range are mutually exclusive. + +NOTE 2: At least one of these IEs shall be present when policing is required. + +### A.7.2.2.3 Reserve and Configure TrGW Connection Point + +This procedure is used to reserve and configure multimedia-processing resources for a termination at the CS-TrGW. + +**Table A.7.2.2.3.1: Reserve and Configure TrGW Connection Point** + +| Procedure | Initiated | Information element name | Information element required | Information element description | +|---------------------------------------------|-----------|----------------------------------|------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Reserve and Configure TrGW Connection Point | CS-IBCF | Context/Context Request | M | This information element indicates the existing context or requests a new context for the bearer termination. | +| | | Emergency Call Indicator | O | This information element identifies the call as emergency call that requires a preferential handling. | +| | | Termination/Termination Request | M | This information element indicates the existing bearer termination or requests a new termination for the bearer to be established. | +| | | IP Interface | O | This information element specifies the used interface type for the IP termination (e.g. ExtSIPI, NboIP). | +| | | Local IP Resources | O | This information element indicates the resource(s) (e.g. codec, auxiliary payload types) for which the CS-TrGW shall be prepared to receive user data, | +| | | Remote IP Resources | O | This information element indicates the resources (e.g. codec, auxiliary payload types) that the CS-TrGW shall use to send user data. | +| | | Reserve Value | O | This information element indicates if multiple IP resources are to be reserved. | +| | | Local Connection Address request | M | This information element requests an IP address and a port number on the CS-TrGW that the remote end can send user plane data to. | +| | | Remote Connection Address | M | This information element indicates the IP address and ports of the remote party that the CS-TrGW can send user plane data to. | +| | | Notify termination heartbeat | M | This information element requests termination heartbeat indications and may specify their periodicity. | +| | | Notify Released Bearer | O | This information element requests a notification of a released bearer. | +| | | IP Realm Identifier | O | This information element indicates the IP realm of the IP termination. | +| | | IP Version | C | This information element indicates the version of the internet protocol to be applied at the termination for the user plane. This is required for IP address translation. | +| | | DiffServ Code Point | O | This information element indicates a specific DiffServ code point to be used in the IP header in packets sent on the IP termination. | +| | | DiffServ Tagging Behaviour | O | This information element indicates whether the Diffserv code point in the IP header in packets sent on the IP termination should be copied from the received value or set to a specific value. | +| | | Remote Source Address Filtering | O | This information element indicates that remote source address filtering is required. | +| | | Remote Source Address Mask | C | This information element provides information on the valid remote source addresses. This may be included if remote source address filtering is included. It shall not be included if remote source address filtering is not included. | +| | | Remote Source Port Filtering | O | This information element indicates that remote source port filtering is required. | + +| | | | | | +|-------------------------------------------------|---------|-------------------------------------|---|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | | Remote Source Port | C | This information element identifies the valid remote source port. This may be included if remote source port filtering is included. It shall not be included if remote source port filtering is not included. (NOTE 1) | +| | | Remote Source Port Range | C | This information element identifies a range of valid remote source ports. This may be included if remote source port filtering is included. It shall not be included if remote source port filtering is not included. (NOTE 1) | +| | | Media Inactivity Detection Required | O | This information element indicates that detection of inactive media flows is required. | +| | | Inactivity Detection Time | C | This information element may be present if Inactive Media Detection is required and specifies the Inactivity Detection time. | +| | | Inactivity Detection Direction | C | This information element may be present if Inactive Media Detection is required and specifies the Inactivity Detection direction. | +| | | RTCP handling | O | Indicates whether or not the CS-TrGW shall reserve a port for an RTCP flow. | +| | | Traffic Policing Required | O | This information element indicates that policing of the media flow is required. | +| | | Peak Data Rate | O | This information element may be present if Policing is required and specifies the permissible peak data rate for a media stream. (NOTE 2) | +| | | Sustainable Data Rate | O | This information element may be present if Policing is required and specifies the permissible sustainable data rate for a media stream. (NOTE 2) | +| | | Delay Variation Tolerance | O | This information element may be present if Policing on Peak Data Rate is required and specifies the maximum expected delay variation tolerance for the corresponding media stream. | +| | | Maximum Burst Size | C | This information element shall be present if Policing on Sustainable Data Rate is required and specifies the maximum expected burst size for the corresponding media stream. | +| Reserve and Configure TrGW Connection Point Ack | CS-TrGW | Context | M | This information element indicates the context where the command was executed. | +| | | Termination | M | This information element indicates the termination where the command was executed. | +| | | Local IP Resources | C | This information element indicates the resources that the CS-TrGW has reserved to receive the user plane data from the remote side. This IE shall be present if it was contained in the request. If the IE was not contained in the request, it may be present in the reply. | +| | | Remote IP Resources | O | This information element indicates the resource (i.e. codec) that the CS-TrGW shall use to send user data. | +| | | Local Connection Addresses | M | This information element indicates the IP address and port on the CS-TrGW that shall receive user plane data. | +| | | Remote Connection Address | O | This information element indicates the IP address and port that the CS-TrGW can send user plane data to. May be present only if corresponding IE is present in the request. | + +NOTE 1: Remote Source Port and Remote Source Port Range are mutually exclusive. + +NOTE 2: At least one of these IEs shall be present when policing is required. + +#### A.7.2.2.4 Release TrGW Termination + +This procedure is used to release multimedia-processing resources for a termination at the CS-TrGW. + +**Table A.7.2.2.4.1: Release TrGW Termination** + +| Procedure | Initiated | Information element name | Information element required | Information element description | +|------------------------------|-----------|--------------------------|------------------------------|------------------------------------------------------------------------------------| +| Release TrGW Termination | CS-IBCF | Context | M | This information element indicates the existing context. | +| | | Termination | M | This information element indicates the existing bearer termination to be released. | +| Release TrGW Termination Ack | CS-TrGW | Context | M | This information element indicates the context where the command was executed. | +| | | Termination | M | This information element indicates the termination where the command was executed. | + +#### A.7.2.2.5 IP Bearer Released + +**Table A.7.2.2.5.1: IP Bearer Released** + +| Procedure | Initiated | Information element name | Information element required | Information element description | +|------------------------|-----------|--------------------------|------------------------------|-----------------------------------------------------------------------------------------------| +| IP Bearer Released | CS-TrGW | Context | M | This information element indicates the context for the bearer termination. | +| | | Termination | M | This information element indicates the bearer termination where the bearer was released. | +| | | Bearer Released | M | This information element notifies a bearer release. | +| | | Release Cause | M | This information element indicates the cause of a bearer release. | +| IP Bearer Released Ack | CS-IBCF | Context | M | This information element indicates all context are where the command was executed. | +| | | Termination | M | This information element indicates that Bearer termination is where the command was executed. | + +#### A.7.2.2.6 Media Inactivity Detection + +This command is used to notify the CS-IBCF of media inactivity on the CS-TrGW. + +**Table A.7.2.2.6.1: Media Inactivity Notification** + +| Procedure | Initiated | Information element name | Information element required | Information element description | +|-----------------------------------|-----------|--------------------------|------------------------------|-------------------------------------------------------------------------------------------------------------------| +| Media Inactivity Notification | CS-TrGW | Context | M | This information element indicates the existing context for the bearer termination. | +| | | Termination | M | This information element indicates that bearer termination is where the media inactivity detection was activated. | +| | | Media Inactivity | M | This information element notifies the CS-IBCF of Media inactivity detection on the bearer termination. | +| Media Inactivity Notification Ack | CS-IBCF | Context | M | This information element indicates the context where the command was executed. | +| | | Termination | M | This information element indicates the bearer termination where the command was executed. | + +### A.7.2.2.7 Termination heartbeat indication + +This command is used by the CS-TrGW to periodically notify the CS-IBCF of a termination heartbeat. + +**Table A.7.2.2.7.1: Termination heartbeat indication** + +| Procedure | Initiated | Information element name | Information element required | Information element description | +|--------------------------------------|-----------|--------------------------|------------------------------|------------------------------------------------------------------------------------------------------------| +| Termination heartbeat indication | CS-TrGW | Context | M | This information element indicates the context for the bearer termination. | +| | | Bearer Termination | M | This information element indicates the bearer termination for which the termination heartbeat is reported. | +| | | Termination heartbeat | M | Hanging Termination event | +| Termination heartbeat indication Ack | CS-IBCF | Context | M | This information element indicates the context where the command was executed. | +| | | Bearer Termination | M | This information element indicates the bearer termination where the command was executed. | + +### A.7.2.2.8 Change Through-Connection + +This procedure is used to change the Through-connection in the bearer termination. + +**Table A.7.2.2.8.1: Change Through-Connection** + +| Procedure | Initiated | Information element name | Information element required | Information element description | +|-------------------------------|-----------|-----------------------------------------------|------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------| +| Change Through-Connection | CS-IBCF | Context/Context Request | M | This information element indicates the existing context or requests a new context for the bearer termination. | +| | | Bearer Termination/Bearer Termination Request | M | This information element indicates the existing bearer termination or requests a new Bearer termination where the through connection is changed. | +| | | Through-Connection | M | This information element indicates the through-connection of the bearer termination | +| Change Through-Connection Ack | CS-TrGW | Context | M | This information element indicates the context where the command was executed. | +| | | Bearer Termination | M | This information element indicates the bearer termination where the command was executed. | + +NOTE: This procedure may be combined with Reserve and Configure TrGW Connection Point, Reserve TrGW Connection Point or Configure TrGW Connection Point procedure. This list of procedures is not exhaustive. + +## A.7.2.3 Non-Call Related Procedures + +### A.7.2.3.1 Introduction + +The procedures detailed in table A.7.2.3.1 shall be applied for the CS-TrGW handling component of the Ix interface. Where a corresponding procedure in 3GPP TS 23.205 [9] is specified, that procedure shall apply. Where no corresponding procedure in 3GPP TS 23.205 [9] is specified, the procedure is specified in a subclause of this specification. + +**Table A.7.2.3.1.1: Non-call related procedures** + +| Procedure defined in 3GPP TS 29.238 [29] | Corresponding Procedure defined in 3GPP TS 23.205 [9] | Remarks | +|-------------------------------------------------|--------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------| +| TrGW Out of service | MGW Out of Service | | +| TrGW Communication Up | MGW Communication Up | | +| TrGW Restoration | MGW Restoration | | +| TrGW Register | MGW Register | | +| TrGW Re-register | MGW Re-register | | +| CS-IBCF Ordered Re-register | (G)MSC Server Ordered Re-register | | +| CS-IBCF Restoration | (G)MSC Server Restoration | | +| CS-IBCF Out of Service | (G)MSC Server Out of Service | | +| Termination Out-of-Service | Termination Out-of-Service | The "Termination Out-of-Service procedure" is also used as a call-related H.248 command | +| Audit Value | Audit Value | | +| Command Rejected | Command Rejected | The "Command Rejected" procedure may be used in response both to call-related and non-call-related H.248 Commands. | +| TrGW Capability Change | Capability Update | | +| TrGW Resource Congestion Handling – Activate | MGW Resource Congestion Handling – Activate | | +| TrGW Resource Congestion Handling – Indication | MGW Resource Congestion Handling – Indication | | +| Inactivity timeout activation | Inactivity timeout activation | | +| Inactivity timeout indication | Inactivity timeout indication | | +| Realm Availability Change Activate | | See subclause A.7.2.3.2. | +| Realm Availability Change Indication | | See subclause A.7.2.3.3. | + +### A.7.2.3.2 Realm Availability Change - Activate + +This procedure is used to activate the realm availability notification mechanism. + +**Table A.7.2.3.2.1: Realm Availability Change - Activate** + +| Procedure | Initiated | Information element name | Information element required | Information element description | +|-----------------------------------------|------------------|------------------------------------|-------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------| +| Realm Availability Change – Activate | CS-IBCF | Context | M | This information element indicates the NULL context. | +| | | Root Termination | M | This information element indicates that root termination is where the realm availability change notification mechanism is activated. | +| | | Realm Availability Change Activate | M | This information element requests to activate the realm availability change notification mechanism. | +| Realm Availability Change -Activate Ack | TrGW | Context | M | This information element indicates the NULL context. | +| | | Root Termination | M | This information element indicates that root termination is where the command was executed. | + +### A.7.2.3.3 Realm Availability Change - Indication + +This procedure is used to inform the CS-IBCF that there has been a change to the list of currently available realms. + +**Table A.7.2.3.3.1: Realm Availability Change - Indication** + +| Procedure | Initiated | Information element name | Information element required | Information element description | +|--------------------------------------------|-----------|-------------------------------|------------------------------|---------------------------------------------------------------------------------------------------------------------------------------| +| Realm Availability Change - Indication | TrGW | Context | M | This information element indicates the NULL context. | +| | | Root Termination | M | This information element indicates that root termination is where the realm availability change notification mechanism was activated. | +| | | Changes to Realm Availability | M | This information element indicates the changes to the list of available realms. | +| Realm Availability Change - Indication Ack | CS-IBCF | Context | M | This information element indicates the NULL context. | +| | | Root Termination | M | This information element indicates that root termination is where the command was executed. | + +## A.8 (G)MSC – CS-MGW Interaction + +### A.8.1 General + +#### A.8.1.1 Network Model + +figure A.8.1.1.1 shows the network model. The squared line represents the call control signalling. The dotted line represents the bearer control signalling (if applicable) and the user plane. The (G)MSC uses one context with at least two terminations in the CS-MGW. The termination T1 is used towards the 3GPP PLMN and the bearer termination T2 is used for the bearer towards the external IP network. + +![Figure A.8.1.1.1: H.248 Context Model diagram showing a 3GPP PLMN connected to a (G)MSC, which is connected to a CS-MGW, which is connected to an External Network. The (G)MSC and CS-MGW are connected by a solid line. The CS-MGW has two terminations, T1 and T2, connected to the External Network by dotted lines.](6d442ab678ed52045444b3ccd4c0ac9e_img.jpg) + +The diagram illustrates the H.248 Context Model. On the left, a box labeled '3GPP PLMN' is connected to a central box labeled '(G)MSC' by a green dashed line. The (G)MSC is connected to a box labeled 'CS-MGW' by a solid blue line. The CS-MGW has two internal terminations, 'T1' and 'T2', marked with an 'X' between them. T1 is connected to the 3GPP PLMN by a red dotted line. T2 is connected to a box labeled 'External Network' on the right by a red dotted line. Additionally, a green dashed line connects the (G)MSC directly to the External Network. + +Figure A.8.1.1.1: H.248 Context Model diagram showing a 3GPP PLMN connected to a (G)MSC, which is connected to a CS-MGW, which is connected to an External Network. The (G)MSC and CS-MGW are connected by a solid line. The CS-MGW has two terminations, T1 and T2, connected to the External Network by dotted lines. + +**Figure A.8.1.1.1: H.248 Context Model** + +#### A.8.1.2 Signalling flows + +The signalling flows in A.7.1.2 apply with the following additions: + +- Instead of the procedure Reserve TrGW Connection Point the procedure Reserve RTP Connection Point as defined by 3GPP TS 23.205 [9] is used. +- Instead of the procedure Reserve and Configure TrGW Connection Point the procedure Reserve and Configure RTP Connection Point as defined by 3GPP TS 23.205 [9] is used. +- Instead of the procedure Configure TrGW Connection Point the procedure Configure RTP Connection Point as defined by 3GPP TS 23.205 [9] is used. + +## Annex B (normative): Additional Interworking Procedures between a SIP-I based circuit-switched Core Network and the IP Multimedia (IM) Core Network (CN) Subsystem to Support Special Services + +### B.1 General + +The present annex describes additional interworking between a SIP-I based circuit-switched core network and the IP Multimedia (IM) Core Network (CN) Subsystem to interwork special services such as global text telephony. Those procedures apply in combination with the procedures in clause 7. + +The procedures in the present Annex are optional. However, if a special service covered in this Annex is interworked, the procedures in the corresponding subclause of this Annex shall be applied. + +### B.2 Global Text Telephony + +Global Text Telephony (GTT) offers real time conversation in text, optionally combinable with voice. GTT is mainly used for distant conversation with hearing or speech impaired users. + +GTT is supported in IMS via the Real-Time Text protocol over RTP, using IETF SIP/SDP for the negotiation of the text media and IETF RFC 4103 [47] RTP-text for transport, with text coded according to ITU-T Recommendation T.140 [46]. See 3GPP TS 23.226 [45], 3GPP TS 26.114 [52], 3GPP TS 26.235 [50] and 3GPP TS 26.236 [51]. + +Within a SIP-I based circuit-switched Core Network the default PCM codec is used to transport the PTSN inband text telephony format. PCM will also be negotiated as codec within SIP-I /SDP, without further information allowing identifying a call using global text telephony. Different specified systems for text telephony exist as PTSN inband text telephony format and are used in different regions, e.g. Baudot (in US), EDT, V.21, Bell103, Minitel and V.18. They are described in the annexes of ITU-T V.18 [48]. + +The Interworking procedures in Annex I of TS 29.163 [13] shall be applied with the following clarifications: + +- Where ISUP signalling is mentioned or depicted, the corresponding SIP-I signalling is applicable. + +## Annex C (informative): Change history + +| Change history | | | | | | | | | +|----------------|-----------|-----------|----|-----|--------------------------------------------------------------------------|-----|-----|--| +| Date | TSG # | TSG Doc. | CR | Rev | Subject/Comment | Old | New | | +| 9/11/07 | CT3#46 | C3-071058 | | | Agreed skeleton | - | 000 | | +| 1/2/08 | CT3#47 | C3-080145 | | | Definitions and Terminology for SIP-I Interworking | 000 | 010 | | +| 1/2/08 | CT3#47 | C3-080243 | | | Reference model for interworking with external SIP-I network | 000 | 010 | | +| 1/2/08 | CT3#47 | C3-080257 | | | SIP-I to SIP-I basic signalling interworking | 000 | 010 | | +| 1/2/08 | CT3#47 | C3-080260 | | | Interworking of SIP-I profiles | 000 | 010 | | +| 1/2/08 | CT3#47 | C3-080149 | | | User plane interworking towards external SIP-I network | 000 | 010 | | +| 1/2/08 | CT3#47 | C3-080152 | | | Interworking Between SIP-I based CS domain and IMS | 000 | 010 | | +| 3/6/08 | CT3#48 | C3-080497 | | | Incoming call from external SIP-I network | 010 | 020 | | +| 3/6/08 | CT3#48 | C3-080669 | | | Outgoing call towards external SIP-I network | 010 | 020 | | +| 3/6/08 | CT3#48 | C3-080670 | | | Handling of Preconditions for incoming calls from external SIP-I network | 010 | 020 | | +| 3/6/08 | CT3#48 | C3-080821 | | | Handling of Preconditions for calls towards external SIP-I network | 010 | 020 | | +| 3/6/08 | CT3#48 | C3-080794 | | | Section for CS-IBCF and CS-TrGW definition | 010 | 020 | | +| 4/7/08 | CT3#48bis | C3-081192 | | | Handling of unrecognized preconditions by external SIP-I networks | 020 | 030 | | +| 4/7/08 | CT3#48bis | C3-080907 | | | Required preconditions | 020 | 030 | | +| 4/7/08 | CT3#48bis | C3-081075 | | | Interworking of Incoming Calls from IMS | 020 | 030 | | +| 4/7/08 | CT3#48bis | C3-081076 | | | Interworking of Outgoing Calls towards IMS | 020 | 030 | | + +| | | | | | | | | +|----------|-----------|-----------|-----|---|-----------------------------------------------------------------------------------------|-----|-----| +| 4/7/08 | CT3#48bis | C3-081077 | | | Incoming Call Flows from IMS | 020 | 030 | +| 4/7/08 | CT3#48bis | C3-080913 | | | Outgoing Call Flows towards IMS | 020 | 030 | +| 4/7/08 | CT3#48bis | C3-081079 | | | DTMF interworking procedures in SIP-I based Nc | 020 | 030 | +| 4/7/08 | CT3#48bis | C3-081207 | | | ISUP Interworking Procedures | 020 | 030 | +| 4/7/08 | CT3#48bis | C3-081242 | | | User Plane Interworking | 020 | 030 | +| 4/7/08 | CT3#48bis | C3-081080 | | | Stage 2 aspects for CS-IBCF and CS-TrGW | 020 | 030 | +| 27/8/08 | CT3#49 | C3-081661 | | | Call Clearing when interworking with IMS | 030 | 040 | +| 27/8/08 | CT3#49 | C3-081541 | | | Codec negotiation when interworking with IMS and with external SIP-I networks | 030 | 040 | +| 27/8/08 | CT3#49 | C3-081542 | | | MGW Selection Procedures | 030 | 040 | +| 27/8/08 | CT3#49 | C3-081543 | | | Updating precondition information when local preconditions are met | 030 | 040 | +| 27/8/08 | CT3#49 | C3-081544 | | | Generation of ringing tone when interworking with IMS | 030 | 040 | +| 27/8/08 | CT3#49 | C3-081545 | | | Clarification of sending received SIP messages to the other side | 030 | 040 | +| 27/8/08 | CT3#49 | C3-081548 | | | Alignment of Preconditions with TS 29.231 | 030 | 040 | +| 27/8/08 | CT3#49 | C3-081549 | | | Supplementary Service Interworking with IMS | 030 | 040 | +| 27/8/08 | CT3#49 | C3-081550 | | | DTMF Interworking towards IMS | 030 | 040 | +| 27/8/08 | CT3#49 | C3-081497 | | | Interworking to BICC networks | 030 | 040 | +| 27/8/08 | CT3#49 | C3-081663 | | | Terminology O-IWU and I-IWU | 030 | 040 | +| 27/8/08 | CT3#49 | C3-081498 | | | Interworking specification between SIP-I and IMS shall stay in TS 29.235 | 030 | 040 | +| 27/8/08 | CT3#49 | C3-081592 | | | Border Control Architecture | 030 | 040 | +| 01/9/08 | CT3#49 | | | | Version 2.0.0 created for presentation to TSG by MCC | 040 | 200 | +| 16/9/08 | TSG#41 | | | | Version 8.0.0 created by MCC | 200 | 800 | +| 11/12/08 | TSG#42 | CP-080754 | 001 | 1 | Interworking between SIP-I based CS and IMS when forking occurs | 800 | 810 | +| 11/12/08 | TSG#42 | CP-080754 | 002 | 1 | Update on MGW bypass | 800 | 810 | +| 11/12/08 | TSG#42 | CP-080754 | 003 | 1 | Incorrect rejection of INVITE request when ALLOW header does not contain UPDATE. | 800 | 810 | +| 11/12/08 | TSG#42 | CP-080754 | 004 | 3 | Miscellaneous clean-ups | 800 | 810 | +| 11/12/08 | TSG#42 | CP-080765 | 005 | 2 | CS-IBCF procedures as an exit and entry point | 800 | 810 | +| 11/12/08 | TSG#42 | CP-080765 | 006 | 4 | CS-IBCF – CS-TrGW Interaction Procedures | 800 | 810 | +| 11/12/08 | TSG#42 | CP-080754 | 012 | 1 | Service Interworking between SIP-I on Nc and IMS | 800 | 810 | +| 11/12/08 | TSG#42 | CP-080754 | 013 | 1 | Corrections and improvements in wording | 800 | 810 | +| 11/12/08 | TSG#42 | CP-080754 | 014 | | Minor editorial corrections | 800 | 810 | +| 11/12/08 | TSG#42 | CP-080754 | 015 | 2 | Removal of editor notes in chapter specifying interworking with external SIP-I networks | 800 | 810 | +| 11/12/08 | TSG#42 | CP-080754 | 016 | 3 | Removal of some editor notes in chapter specifying interworking with IMS | 800 | 810 | +| 11/12/08 | TSG#42 | CP-080754 | 018 | | Signaling of the MGW Identifier | 800 | 810 | +| 11/12/08 | TSG#42 | CP-080754 | 019 | 5 | Call release from external SIP-I network without encapsulated ISUP REL | 800 | 810 | +| 11/12/08 | TSG#42 | CP-080754 | 020 | 1 | Interworking with overlap signalling in IMS | 800 | 810 | +| 11/12/08 | TSG#42 | CP-080765 | 021 | 2 | CS-IBCF procedures | 800 | 810 | +| 03/2009 | TSG#43 | CP-090092 | 023 | 2 | CS-Ix – Minor corrections | 810 | 820 | +| 03/2009 | TSG#43 | CP-090092 | 024 | 2 | CS-Ix Update proposal for clause A.4 | 810 | 820 | +| 03/2009 | TSG#43 | CP-090092 | 028 | 2 | Clean-up of Annex A | 810 | 820 | +| 03/2009 | TSG#43 | CP-090080 | 030 | 2 | Receipt of Re-Invite with no SDP | 810 | 820 | +| 03/2009 | TSG#43 | CP-090080 | 031 | 2 | B2BUA: setting of SIP header values when interworking with IMS | 810 | 820 | +| 03/2009 | TSG#43 | CP-090080 | 032 | 1 | Supplementary Service Interworking with IMS | 810 | 820 | +| 03/2009 | TSG#43 | CP-090080 | 033 | 3 | Exception to message transiting when interworking failure response | 810 | 820 | +| 03/2009 | TSG#43 | CP-090097 | 034 | 4 | Ix procedures | 820 | 900 | +| 05/2009 | TSG#44 | CP-090335 | 037 | 2 | Codec negotiation when interworking with BICC based network | 900 | 910 | +| 05/2009 | TSG#44 | CP-090351 | 038 | 2 | Stage 2 requirements / use cases for CS-IBCF / CS-TrGW | 900 | 910 | +| 09/2009 | TSG#45 | CP-090581 | 040 | 1 | Addition of Release TrGW Termination to CS-IBCF procedures | 910 | 920 | +| 09/2009 | TSG#45 | CP-090581 | 041 | | Minor correction to A.7.1.2.2.5 | 910 | 920 | +| 09/2009 | TSG#45 | CP-090581 | 042 | 2 | Addition of IP Interface Type to CS-IBCF procedures | 910 | 920 | +| 09/2009 | TSG#45 | CP-090570 | 045 | | Text relates to wrong call direction | 910 | 920 | +| 09/2009 | TSG#45 | CP-090570 | 047 | | Text relates to wrong message direction | 910 | 920 | +| 09/2009 | TSG#45 | CP-090581 | 050 | 2 | Notification of released bearer | 910 | 920 | +| 09/2009 | TSG#45 | CP-090581 | 051 | | Remote Resources in responses optional | 910 | 920 | +| 12/2009 | TSG#46 | CP-090839 | 054 | | Handling of a MGW identifier from external SIP-I network | 920 | 930 | +| 12/2009 | TSG#46 | CP-090850 | 055 | 3 | Media Inactivity Detection | 920 | 930 | +| 12/2009 | TSG#46 | CP-090850 | 059 | 3 | RTCP Handling | 920 | 930 | +| 12/2009 | TSG#46 | CP-090850 | 061 | 1 | QoS Packet Marking | 920 | 930 | +| 12/2009 | TSG#46 | CP-090850 | 063 | 3 | Termination Heartbeat Procedure | 920 | 930 | +| 12/2009 | TSG#46 | CP-090850 | 065 | 3 | Mandatory Features in the CS-TrGW | 920 | 930 | +| 12/2009 | TSG#46 | CP-090850 | 066 | | Non-Call Related Procedure Alignment | 920 | 930 | +| 12/2009 | TSG#46 | CP-090850 | 067 | 2 | Traffic Policing | 920 | 930 | +| 12/2009 | TSG#46 | CP-090858 | 068 | 1 | Reference Tidy-Up | 920 | 930 | + +| | | | | | | | | +|---------|--------|-----------|-----|---|-------------------------------------------------------------------------|------|------| +| 12/2009 | TSG#46 | CP-090858 | 069 | 1 | Miscellaneous Corrections | 920 | 930 | +| 03/2010 | TSG#47 | CP-100091 | 071 | 1 | Abbreviations Tidy-Up | 930 | 940 | +| 03/2010 | TSG#47 | CP-100085 | 072 | | Use of IP Interface Type | 930 | 940 | +| 03/2010 | TSG#47 | CP-100083 | 074 | 1 | Global Text Telephony Interworking between IMS and SIP-I on NC based CN | 930 | 940 | +| 03/2010 | TSG#47 | CP-100084 | 075 | 1 | Mn Procedures when interworking between IMS and SIP-I on NC based CN | 930 | 940 | +| 06/2010 | TSG#48 | CP-100316 | 076 | 2 | Handling of Stream mode | 940 | 950 | +| 06/2010 | TSG#48 | CP-100316 | 077 | | RTCP handling correction | 940 | 950 | +| 06/2010 | TSG#48 | CP-100316 | 078 | 1 | Resolution of editors notes | 940 | 950 | +| 09/2010 | TSG#49 | CP-100550 | 079 | 1 | Local IP Resources IE: changing of property | 950 | 960 | +| 09/2010 | TSG#49 | CP-100557 | 080 | | Correcting unspecific external reference | 950 | 960 | +| 09/2010 | TSG#49 | CP-100550 | 081 | 1 | Procedures for Emergency indicator | 950 | 960 | +| 03/2011 | TSG#51 | CP-110112 | 084 | | Adding CS-Ix functionalities to Mc-profile | 960 | 970 | +| 03/2011 | TSG#51 | CP-110126 | 085 | 2 | Add the function of Interworking for supplementary service CAT | 970 | 1000 | +| 06/2012 | TSG#56 | CP-120338 | 091 | 1 | Forking and SDP offer-answer Interworking corrections | 1000 | 1010 | +| 09/2012 | TSG#57 | | | | Automatic upgrade from previous Release version 10.1.0 | 1010 | 1100 | +| 12/2012 | TSG#58 | CP-120843 | 092 | 1 | 100 Trying not interworked between IMS and SIP-I based CS CN | 1100 | 1110 | +| 06/2013 | TSG#60 | CP-130317 | 096 | 1 | MGCF behavior clarification | 1110 | 1120 | +| 09/2013 | TSG#61 | CP-130541 | 100 | 1 | INVITE without SDP | 1120 | 1130 | + +| Change history | | | | | | | | +|----------------|---------|-----------|------|-----|-----|-------------------------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2018-12 | CT #82 | CP-183121 | 0109 | 1 | A | Removal of Editor's notes for supplementary services interworking | 11.4.0 | \ No newline at end of file diff --git a/marked/Rel-11/29_series/29238/573c8f9e728e343b6864e1070c14b8cf_img.jpg b/marked/Rel-11/29_series/29238/573c8f9e728e343b6864e1070c14b8cf_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a4e0f3eb560d793c378796fb40b276021efaaf4d --- /dev/null +++ b/marked/Rel-11/29_series/29238/573c8f9e728e343b6864e1070c14b8cf_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ad9c425cc4a1d955abdc2348ea8a60e4316a29af9bf6feefa6f2dc3c160b7806 +size 54621 diff --git a/marked/Rel-11/29_series/29238/88b0f3f4393228e9ea4d6542aef7c399_img.jpg b/marked/Rel-11/29_series/29238/88b0f3f4393228e9ea4d6542aef7c399_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..602e874b1c80fc26e1820cd124d16394ec11b804 --- /dev/null +++ b/marked/Rel-11/29_series/29238/88b0f3f4393228e9ea4d6542aef7c399_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6b4b1913b5c5daa11ac8d8d55ba46a031a34150c759d5fd12ca3b8a655fb366d +size 71759 diff --git a/marked/Rel-11/29_series/29238/997233d405f0d4b89ddeb7683e047f66_img.jpg b/marked/Rel-11/29_series/29238/997233d405f0d4b89ddeb7683e047f66_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..76a26c1915c95aaf15654b117cb7b2fe9ff619e8 --- /dev/null +++ b/marked/Rel-11/29_series/29238/997233d405f0d4b89ddeb7683e047f66_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7db9af3bf3a7a68a71162b73fb26c6fbd6a0986bea8c4c0fd5bd6a6edc9ea723 +size 65045 diff --git a/marked/Rel-11/29_series/29238/a2586540d49d5665489c8b5a273f86d3_img.jpg b/marked/Rel-11/29_series/29238/a2586540d49d5665489c8b5a273f86d3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5befb3cc505999948e7f8ed91e608a6e0fed44cc --- /dev/null +++ b/marked/Rel-11/29_series/29238/a2586540d49d5665489c8b5a273f86d3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:677e30faffa62bcfb966ebc5164c550e057e65af23d6b78e0e5bf85e1d58de93 +size 15632 diff --git a/marked/Rel-11/29_series/29238/b82b870697ef3993804c839b298c0f4f_img.jpg b/marked/Rel-11/29_series/29238/b82b870697ef3993804c839b298c0f4f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8b1ed7995b79052b97f0552b0e07afdb86c71e25 --- /dev/null +++ b/marked/Rel-11/29_series/29238/b82b870697ef3993804c839b298c0f4f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b64a3e2530ce56dfbd4fd62023fd85940a8df0e2bd2222b01514d00691044d2d +size 16122 diff --git a/marked/Rel-11/29_series/29238/raw.md b/marked/Rel-11/29_series/29238/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..d7d8849ac1f23df2c36f0f8cb22209c4deb3e667 --- /dev/null +++ b/marked/Rel-11/29_series/29238/raw.md @@ -0,0 +1,2297 @@ + + + + + + +# Contents + +| | | +|---------------------------------------------------------------|----| +| Foreword ..... | 5 | +| 1 Scope..... | 5 | +| 2 References..... | 7 | +| 3 Definitions, symbols and abbreviations..... | 9 | +| 3.1 Definitions..... | 9 | +| 3.2 Symbols..... | 9 | +| 3.3 Abbreviations ..... | 9 | +| 4 Applicability..... | 10 | +| 4.1 Architecture ..... | 10 | +| 5 Profile Description ..... | 10 | +| 5.1 Profile Identification ..... | 10 | +| 5.2 Summary ..... | 10 | +| 5.3 Gateway Control Protocol Version ..... | 11 | +| 5.4 Connection model ..... | 11 | +| 5.5 Context attributes ..... | 12 | +| 5.6 Terminations..... | 12 | +| 5.6.1 Termination names ..... | 12 | +| 5.6.1.1 IP Termination ..... | 12 | +| 5.6.1.1.1 ABNF Coding Overview and prose specification..... | 12 | +| 5.6.1.1.2 ASN.1 Coding Overview and prose specification ..... | 13 | +| 5.6.2 Multiplexed terminations..... | 13 | +| 5.7 Descriptors ..... | 14 | +| 5.7.1 TerminationState Descriptor ..... | 14 | +| 5.7.2 Stream Descriptor ..... | 14 | +| 5.7.2.0 General..... | 14 | +| 5.7.2.1 LocalControl Descriptor ..... | 14 | +| 5.7.3 Events descriptor ..... | 15 | +| 5.7.4 EventBuffer descriptor ..... | 16 | +| 5.7.5 Signals descriptor ..... | 16 | +| 5.7.6 DigitMap descriptor..... | 17 | +| 5.7.7 Statistics descriptor..... | 18 | +| 5.7.8 ObservedEvents descriptor..... | 18 | +| 5.7.9 Topology descriptor..... | 18 | +| 5.7.10 Error descriptor..... | 19 | +| 5.8 Command API..... | 21 | +| 5.8.1 Add ..... | 21 | +| 5.8.2 Modify ..... | 21 | +| 5.8.3 Subtract..... | 22 | +| 5.8.4 Move..... | 22 | +| 5.8.5 AuditValue ..... | 22 | +| 5.8.6 AuditCapabilities ..... | 22 | +| 5.8.7 Notify..... | 23 | +| 5.8.8 ServiceChange..... | 23 | +| 5.8.9 Manipulating and auditing context attributes ..... | 25 | +| 5.9 Generic command syntax and encoding..... | 25 | +| 5.10 Transactions ..... | 25 | +| 5.11 Messages ..... | 26 | +| 5.12 Transport ..... | 26 | +| 5.13 Security..... | 27 | +| 5.14 Packages..... | 27 | +| 5.14.1 Mandatory Packages..... | 27 | +| 5.14.2 Optional Packages ..... | 28 | +| 5.14.3 Package usage information..... | 29 | +| 5.14.3.1 Generic (g) ..... | 29 | + +| | | | +|-------------------------------|---------------------------------------------------------------------------|-----------| +| 5.14.3.2 | Base root (root) ..... | 30 | +| 5.14.3.3 | Differentiated Services (ds) ..... | 31 | +| 5.14.3.4 | Gate Management (gm) ..... | 32 | +| 5.14.3.5 | Traffic management (tman) ..... | 33 | +| 5.14.3.6 | Inactivity Timer (it) ..... | 34 | +| 5.14.3.7 | IP Domain Connection (ipdc) ..... | 34 | +| 5.14.3.8 | Media Gateway Overload Control Package (ocp) ..... | 35 | +| 5.14.3.9 | Hanging Termination Detection (hangterm) ..... | 35 | +| 5.14.3.10 | Media Gateway Resource Congestion handling Package (chp) ..... | 36 | +| 5.14.3.11 | IP Realm Availability (ipra) ..... | 36 | +| 5.14.3.12 | 3G Interface Type package (threegint) ..... | 37 | +| 5.14.3.13 | RTCP Handling Package (rtcph) ..... | 37 | +| 5.14.3.14 | Application Data Inactivity Detection (adid) ..... | 38 | +| 5.14.3.15 | Explicit Congestion Notification for RTP-over-UDP Support (ecnrous) ..... | 39 | +| 5.15 | Mandatory support of SDP and Annex C information elements ..... | 41 | +| 5.16 | Optional support of SDP and Annex C information elements ..... | 43 | +| 5.17 | Procedures ..... | 43 | +| 5.17.1 | Formats and Codes ..... | 43 | +| 5.17.2 | Call Related Procedures ..... | 46 | +| 5.17.2.1 | General ..... | 46 | +| 5.17.2.2 | Reserve TrGW Connection Point ..... | 46 | +| 5.17.2.3 | Configure TrGW Connection Point ..... | 49 | +| 5.17.2.4 | Reserve and Configure TrGW Connection Point ..... | 52 | +| 5.17.2.5 | Release TrGW Termination ..... | 55 | +| 5.17.2.6 | Termination Heartbeat Indication ..... | 55 | +| 5.17.2.7 | IP Bearer Released ..... | 56 | +| 5.17.2.8 | Media Inactivity Notification ..... | 56 | +| 5.17.2.9 | Change Through Connection ..... | 57 | +| 5.17.2.10 | ECN FailureIndication ..... | 57 | +| 5.17.2.11 | Change Flow Direction ..... | 57 | +| 5.17.3 | Non-Call Related Procedures ..... | 58 | +| 5.17.3.1 | General ..... | 58 | +| 5.17.3.2 | TrGW Out Of Service ..... | 59 | +| 5.17.3.3 | TrGW Communication Up ..... | 60 | +| 5.17.3.4 | TrGW Restoration ..... | 60 | +| 5.17.3.5 | TrGW Register ..... | 61 | +| 5.17.3.6 | TrGW Re-Register ..... | 61 | +| 5.17.3.7 | IBCF Ordered Re-register ..... | 62 | +| 5.17.3.8 | IBCF Restoration ..... | 62 | +| 5.17.3.9 | IBCF Out of Service ..... | 63 | +| 5.17.3.10 | Audit Value ..... | 63 | +| 5.17.3.11 | Command Rejected ..... | 65 | +| 5.17.3.12 | TrGW Capability Change ..... | 65 | +| 5.17.3.13 | TrGW Resource Congestion Handling – Activate ..... | 65 | +| 5.17.3.14 | TrGW Resource Congestion Handling – Indication ..... | 66 | +| 5.17.3.15 | Inactivity Timeout – Activation ..... | 66 | +| 5.17.3.16 | Inactivity Timeout – Indication ..... | 67 | +| 5.17.3.17 | Realm Availability Change – Activation ..... | 67 | +| 5.17.3.18 | Realm Availability Change – Indication ..... | 68 | +| 5.17.3.19 | Termination Out Of Service ..... | 68 | +| Annex A (informative): | Illustration of Gate/Pinhole Concept ..... | 69 | +| A.1 | General ..... | 69 | +| A.2 | Relationships between gates and H.248 Streams ..... | 69 | +| Annex B (informative): | Void ..... | 71 | +| Annex C (informative): | Change history ..... | 72 | + +# --- Foreword + +This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +# --- 1 Scope + +The present document describes the protocol to be used on the Interconnection Border Control Function (IBCF) – Transition Gateway (TrGW) interface and the CS-IBCF – CS-TrGW interface. The basis for this protocol is the H.248 protocol as specified in ITU-T. The Profile provides MG control function for IMS and CS Border Control. The IMS architecture is described in 3GPP TS 23.228 [2]. The underlying reference model and stage 2 information is described in Annex I of 3GPP TS 23.228 [2] and in 3GPP TS 29.162 [18]. The CS architecture is described in Annex A of 3GPP TS 29.235 [17]. + +This specification describes the application of H.248 Ix profile for both Ix and CS-Ix interfaces (see Figure 1.1 and Figure 1.2). Required extensions use the H.248 standard extension mechanism. In addition certain aspects of the base protocol H.248 are not needed for this interface and thus excluded by this profile. + +![Reference model for IMS Border Control Functions diagram showing UE, IP-CAN, P-CSCF, S-CSCF, I-CSCF, BGCF, DNS, HSS, IBCF, and TrGW within an IMS network bordering an Other IMS/SIP network.](88b0f3f4393228e9ea4d6542aef7c399_img.jpg) + +This diagram illustrates the reference model for IMS Border Control Functions. On the left, a 'UE' (User Equipment) is connected to an 'IP-CAN' (IP Connectivity Access Network). The 'IP-CAN' connects to a 'P-CSCF' (PDN Gateway Control Function). The 'P-CSCF' connects to an 'S-CSCF' (Serving CSCF) via an 'Mx' interface. The 'S-CSCF' connects to an 'I-CSCF' (Interrogating CSCF) via an 'Mx' interface. The 'I-CSCF' connects to a 'BGCF' (Breakout Gateway Control Function) via an 'Mx' interface. The 'BGCF' connects to an 'IBCF' (IMS Border Control Function) via an 'Mx' interface. The 'IBCF' contains two internal components: 'IMS-ALG' and 'THIG'. The 'IBCF' connects to a 'TrGW' (Traffic Gateway) via an 'Ix' interface. The 'TrGW' is part of a 'Border Control Functions' block, which is located at the boundary of the 'IMS network'. The 'TrGW' connects to an 'Other IMS/SIP network' on the right. The 'DNS' (Domain Name System) and 'HSS' (Home Subscriber Server) are connected to the 'S-CSCF' and 'I-CSCF' respectively. A legend indicates that dashed lines represent 'Signalling' and solid lines represent 'Bearer'. + +Reference model for IMS Border Control Functions diagram showing UE, IP-CAN, P-CSCF, S-CSCF, I-CSCF, BGCF, DNS, HSS, IBCF, and TrGW within an IMS network bordering an Other IMS/SIP network. + +Figure 1.1: Reference model for IMS Border Control Functions + +![Reference model for CS Border Control Functions diagram showing IWU, UP-IWU, CS-IBCF, and CS-TrGW within border control logical functions interfacing with a SIP-I based 3GPP CS domain/External SIP-I Network.](573c8f9e728e343b6864e1070c14b8cf_img.jpg) + +This diagram illustrates the reference model for CS Border Control Functions. On the left, an 'IWU' (Interworking Unit) is connected to a 'UP-IWU' (User Plane Interworking Unit) via an 'Mc' interface. The 'UP-IWU' connects to a 'CS-TrGW' (CS Traffic Gateway) via a 'Media/RTP/UDP/IP' bearer. The 'IWU' connects to a 'CS-IBCF' (CS IMS Border Control Function) via a 'SIP-I' signalling interface. The 'CS-IBCF' contains two internal components: 'ALG' and 'THIG'. The 'CS-IBCF' connects to the 'CS-TrGW' via a 'CS-Ix' interface. The 'CS-IBCF' and 'CS-TrGW' are part of a 'border control logical functions' block, which is located at the boundary of the network. The 'CS-TrGW' connects to a 'SIP-I based 3GPP CS domain/External SIP-I Network' on the right. A legend indicates that dashed lines represent 'Signalling' and solid lines represent 'Bearer'. + +Reference model for CS Border Control Functions diagram showing IWU, UP-IWU, CS-IBCF, and CS-TrGW within border control logical functions interfacing with a SIP-I based 3GPP CS domain/External SIP-I Network. + +Figure 1.2: Reference model for CS Border Control Functions + +The reference model for the IBCF and the TrGW supporting the ATCF/ATGW function is shown in Figure 1.x below. + +![Figure 1.3: Reference model for IBCF/TrGW with ATCF/ATGW function. The diagram shows a User Equipment (UE) connected to a CS access and an IP-CAN. The CS access is connected to an MSC Server and an MGW. The IP-CAN is connected to the IMS network. The IMS network contains P-CSCF, S-CSCF, I-CSCF, and BGCF. The I-CSCF is connected to the IBCF (IMS-ALG (ATCF) and THIG). The IBCF is connected to the TrGW (ATGW) which is part of the Border Control Functions. The TrGW is connected to the Other IMS/SIP network. Signalling is shown as dashed lines, and Bearer as solid lines. Red arrows indicate 'Access Transfer' from the MGW to the IBCF and from the IP-CAN to the TrGW. DNS and HSS are also shown connected to the IMS network elements.](997233d405f0d4b89ddeb7683e047f66_img.jpg) + +Figure 1.3: Reference model for IBCF/TrGW with ATCF/ATGW function. The diagram shows a User Equipment (UE) connected to a CS access and an IP-CAN. The CS access is connected to an MSC Server and an MGW. The IP-CAN is connected to the IMS network. The IMS network contains P-CSCF, S-CSCF, I-CSCF, and BGCF. The I-CSCF is connected to the IBCF (IMS-ALG (ATCF) and THIG). The IBCF is connected to the TrGW (ATGW) which is part of the Border Control Functions. The TrGW is connected to the Other IMS/SIP network. Signalling is shown as dashed lines, and Bearer as solid lines. Red arrows indicate 'Access Transfer' from the MGW to the IBCF and from the IP-CAN to the TrGW. DNS and HSS are also shown connected to the IMS network elements. + +**Figure 1.3: Reference model for IBCF/TrGW with ATCF/ATGW function** + +See 3GPP TS 23.237 [38] subclause 5.2 for a comprehensive description of the reference model. + +NOTE: The Ix profile is applied over both IMS and CS Ix interfaces. + +In the following text the terms IBCF and TrGW also include respectively the CS-IBCF and CS-TrGW functionalities. + +# 2 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. +- For a specific reference, subsequent revisions do not apply. +- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. + +- [1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications". +- [2] 3GPP TS 23.228: "IP Multimedia Subsystem (IMS); Stage 2". +- [3] ITU-T Recommendation H.248.1 (2002): "Gateway Control Protocol: Version 2" including the Corrigendum 1 for Version 2 (03/04). +- [4] ETSI TS 183 018 V3.5.1(2009-07): "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Resource and Admission Control: H.248 Profile Version 3 for controlling Border Gateway Functions (BGF) in the Resource and Admission Control Subsystem (RACS); Protocol specification". +- [5] ITU-T Recommendation H.248.57 (06/2008): "Gateway control protocol: RTP Control Protocol Package". +- [6] ITU-T Recommendation H.248.43 (06/2008): "Gateway control protocol: Gate Management and Gate Control packages". +- [7] IETF RFC 3605 (2003): "Real Time Control Protocol (RTCP) attribute in Session Description Protocol (SDP)". +- [8] IETF RFC 4566 (2006): "SDP: Session Description Protocol". + +- [9] IETF RFC 4975 (2007): "The Message Session Relay Protocol (MSRP)". +- [10] IETF RFC 3551 (2003): "RTP Profile for Audio and Video Conferences with Minimal Control". +- [11] IETF RFC 4145 (2005): "TCP-Based Media Transport in the Session Description Protocol (SDP)". +- [12] ITU-T Recommendation H.248.52 (06/2008): "Gateway control protocol: QoS support packages ". +- [13] ITU-T Recommendation H.248.53 (06/2008) inclusive *Revision 1* (03/2009): "Gateway control protocol: Traffic management packages". +- [14] ITU-T Recommendation H.248.41 Amendment 1 (06/2008): "Gateway control protocol: IP domain connection package: IP Realm Availability Package". +- [15] ITU-T Recommendation H.248.36 (09/2005): "Gateway control protocol: Hanging Termination Detection package". +- [16] ITU-T Recommendation H.248.11 (11/2002): "Gateway control protocol: Media gateway overload control package". +Inclusive Corrigendum 1 (06/2008) to H.248.11 "Gateway control protocol: Media gateway overload control package: Clarifying MG-overload event relationship to ADD commands". +- [17] 3GPP TS 29.235: "Interworking between SIP-I based circuit-switched core network and other networks". +- [18] 3GPP TS 29.162: "Interworking between the IM CN subsystem and IP networks". +- [19] ITU-T Recommendation H.248.14 (03/2009): "Gateway control protocol: Inactivity timer package". +- [20] ITU-T Recommendation H.248.10 (07/2001): "Media gateway resource congestion handling package". +- [21] 3GPP TS 29.232: "Media Gateway Controller (MGC) - Media Gateway (MGW) interface; Stage 3". +- [22] 3GPP TS 33.210: "Technical Specification Group Services and System Aspects; 3G Security; Network Domain Security; IP Network Layer Security". +- [23] ITU-T Recommendation V.152 (01/2005): "Procedures for supporting voice-band data over IP networks". +- [24] ITU-T Supplement 7 to ITU-T H-series Recommendations H.Sup7 (05/2008): "Gateway control protocol: Establishment procedures for the H.248 MGC-MG control association". +- [25] IETF RFC 5234 (2008): "Augmented BNF for Syntax Specifications: ABNF ". +- [26] IETF RFC 4960 (2007): "Stream control transmission protocol". +- [27] ITU-T Recommendation H.248.40 (01/2007): "Gateway control protocol: Application Data Inactivity Detection package". +- [28] ITU-T Recommendation X.690 (11/2008): "ASN.1 encoding rules: Specification of Basic Encoding Rules (BER), Canonical Encoding Rules (CER) and Distinguished Encoding Rules (DER)". +- [29] IETF RFC 3556 (2003): "Session Description Protocol (SDP) Bandwidth Modifiers for RTP Control Protocol (RTCP) Bandwidth". +- [30] IETF RFC 4585 (2006): "Extended RTP Profile for Real-time Transport Control Protocol (RTCP) - Based Feedback (RTP/AVPF)". +- [31] 3GPP TS 26.114: "IP Multimedia Subsystem (IMS); Multimedia telephony; Media handling and interaction". +- [32] IETF RFC 2216 (1997): "Network Element Service Specification Template". + +- [33] IETF RFC 3711 (2004): "The Secure Real-time Transport Protocol (SRTP)". +- [34] IETF RFC 5124 (2008): "Extended Secure RTP Profile for Real-time Transport Control Protocol (RTCP)-Based Feedback (RTP/SAVPF)". +- [35] IETF RFC 6679 (2012): "Explicit Congestion Notification (ECN) for RTP over UDP". +- [36] IETF RFC 3611 (2003): "RTP Control Protocol Extended Reports (RTCP XR)". +- [37] IETF RFC 3168 (2001): "The Addition of Explicit Congestion Notification (ECN) to IP". +- [38] 3GPP TS 23.237: "IP Multimedia subsystem (IMS) Service Continuity; Stage 2". +- [39] 3GPP TS 22.153: "Multimedia Priority Service". +- [40] ITU-T Recommendation H.248.82 (03/2013): "Gateway control protocol: Explicit Congestion Notification Support". + +# --- 3 Definitions, symbols and abbreviations + +## 3.1 Definitions + +For the purposes of the present document, the terms and definitions given in TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905 [1]. + +**Address:** term used for "network address" (IP address) + +**CS-TrGW:** packet-to-packet gateway for user plane media traffic. The CS-TrGW performs both policy enforcement functions and NA(P)T functions under the control of the CS-IBCF + +**Port:** term used for "transport port" (L4 port). + +**TRANSCODING:** transcoding in general is the translation from one type of encoded media format to another different media format, e.g. G.711 A-law to $\mu$ -law or vice versa, G.729 to AMR with 4.75 rate. + +NOTE 1: The definition of "transcoding" is according clause 3.10/ITU-T Recommendation V.152 [23]. + +NOTE 2: Transcoding belongs to the category of "media aware" IP-to-IP interworking. + +**Transport Address:** term used for the combination of a *Network Address* and a *Transport Port*. + +**TrGW:** packet-to-packet gateway for user plane media traffic. The TrGW performs both policy enforcement functions and NA(P)T functions under the control of the IBCF + +NOTE 3: A Transition Gateway (TrGW) provides the interface between two IP-transport domains. The TrGW has the "H.248 MG" role in the scope of this Profile. + +## 3.2 Symbols + +For the purposes of the present document, the following symbols apply: + +| | | +|----|---------------------------------------------------------| +| Ix | Interface between IBCF and TrGW or CS-IBCF and CS-TrGW. | +|----|---------------------------------------------------------| + +## 3.3 Abbreviations + +For the purposes of the present document the abbreviations defined in 3GPP TR 21.905 [1] apply, with the following additions. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in 3GPP TR 21.905 [1]. + +| | | +|------|----------------------------------| +| ABNF | Augmented Backus-Naur Form | +| ATCF | Access Transfer Control Function | +| ATGW | Access Transfer Gateway | +| BGF | Border Gateway Function | +| CE | Congestion Experienced | + +| | | +|---------|------------------------------------------------------------------------------------------| +| ECN | Explicit Congestion Notification | +| GCP | Gateway Control Protocol | +| IBCF | Interconnect Border Control Function | +| LD | Local Descriptor (H.248 protocol element) | +| MG | Media Gateway | +| MGC | Media Gateway Controller | +| MPS | Multimedia Priority Service | +| NA | Not Applicable | +| NAPT | Network Address and Port Translation | +| NAPT-PT | NAPT and Protocol Translation | +| NAT | Network Address Translation | +| PCI | Protocol Control Information | +| RD | Remote Descriptor (H.248 protocol element) | +| RTCP | RTP Control Protocol | +| SRVCC | Single Radio Voice Call Continuity | +| ToS | Type-of-Service | +| TrGW | Transition Gateway | +| TISPAN | Telecommunications and Internet converged Services and Protocols for Advanced Networking | + +# 4 Applicability + +The support of the IMS and CS Ix interfaces capability sets shall be identified by the H.248 Ix profile and support of this profile shall be indicated in H.248 ServiceChange procedure (during the (re-)registration phase(s)). + +## 4.1 Architecture + +See Annex I of 3GPP TS 23.228 [2], Annex A of 3GPP TS 29.235 [17] and 3GPP TS 29.162 [18]. + +# 5 Profile Description + +## 5.1 Profile Identification + +**Table 5.1.1: Profile Identification** + +| | | +|----------------------|-----------------| +| Profile name: | threeglx | +| Version: | 2 | + +## 5.2 Summary + +This profile supports the control of the following functionality in (IP-to-IP) Transition Gateways: + +- Allocation and translation of IP addresses and port numbers (NA(P)T and NA(P)T-PT); +- Hanging termination detection; +- IP realm/domain indication; +- Media inactivity detection; +- Opening and closing gates (i.e. packets filtering depending on "IP address / port"); +- Policing of incoming traffic; +- QoS packet marking for outgoing traffic (differentiated services); +- RTCP handling; +- Explicit Congestion Notification support; +- Multimedia Priority Service; + +and when ATCF/ATGW is supported: + +- Handover of bearer connections between PS and CS access networks; +- IP version interworking; +- Audio transcoding. + +In addition, optional settings and procedures are described which fulfil optional features. The minimum mandatory settings within the optional procedures and packages are identified that must be supported in order to support that feature. + +"Optional" or "O" means that it is optional for either the sender or the receiver to implement an element. If the receiving entity receives an optional element that it has not implemented it should send an Error Code (e.g. 445 "Unsupported or Unknown Property", 501 "Not Implemented", etc.). "Mandatory" or "M" means that it is mandatory for the receiver to implement an element. Whether it is mandatory for the sender to implement depends on specific functions; detail of whether elements of the core protocol are mandatory to be sent are defined in the stage 2 procedures, stage 3 procedures and/or the descriptions of individual packages. + +The setting or modification of elements described in the profile under the heading "Used in Command" has the meaning that the property can be set/modified with that command. The property may be present in other commands (in order to preserve its value in accordance with ITU-T Recommendation H.248.1[3]) when those commands are used for other procedures that affect the same descriptor. + +## 5.3 Gateway Control Protocol Version + +Version 2 (ITU-T Recommendation H.248.1 [3]) shall be used as the minimum protocol version. + +## 5.4 Connection model + +**Table 5.4.1: Connection Model** + +| | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------| +| Maximum number of contexts: | Provisioned | +| Maximum number of terminations per context: | 3 | +| Allowed termination type combinations in a context: | (IP,IP) ;
(IP,IP,IP) (NOTE) | +| NOTE: This is only a temporary context configuration, occurring during bearer access transfer phase (between PS to CS access networks or vice versa). | | + +## 5.5 Context attributes + +**Table 5.5.1: Context Attributes** + +| Context Attribute | Supported | Values Supported | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|-------------------------| +| Topology | Yes (NOTE 1) | See clause 5.7.9 | +| Priority Indicator | Optional (NOTE 2) | 0-15 (NOTE 3) | +| Emergency Indicator | Yes | YES/NO | +| IEPS Indicator | No | NA | +| ContextAttribute Descriptor | No | NA | +| ContextIdList Parameter | No | NA | +| AND/OR Context Attribute | No | NA | +| NOTE 1: Stream ID in Topology Descriptor shall not be supported (because only used for SRVCC service support, which is a monomedia type of call ("voice call")). | | | +| NOTE 2: This Context Attribute parameter is allowed in ETSI TISPAN Ia Profile version 3. It is also used for MPS as specified in 3GPP TS 22.153 [39]. | | | +| NOTE 3: Priority values 11 – 15 of the Priority Indicator are reserved for MPS. | | | + +## 5.6 Terminations + +### 5.6.1 Termination names + +#### 5.6.1.1 IP Termination + +##### 5.6.1.1.1 ABNF Coding Overview and prose specification + +The Termination ID structure shall follow the guidelines of H.248 and shall be based on four fields: + +- "ip///". + +The individual fields are described and defined in table 5.6.1.1.1.1. + +**Table 5.6.1.1.1.1: IP Termination Fields** + +| Name | Description | Values | CHOOSE Wildcard | ALL Wildcard | +|-----------|-----------------------------------------------------------------------------------------------------------------------------|------------------------------------------|-----------------|--------------| +| ip | "ip" is a fixed prefix identifying the termination | "ip" | No | No | +| Group | Group of Interface and Id | Integer (0-65535) | Yes (NOTE 5) | Yes | +| Interface | Logical or physical interface to a network to/from which the termination will be sending/receiving media. (NOTE 1, NOTE 2). | String of max 51 alphanumeric characters | Yes (NOTE 4) | Yes | +| Id | Termination specific identifier (NOTE 3). | Non-zero 32 bit integer | Yes (NOTE 4) | Yes | + +NOTE 1: A specific may be used together with different groups. +NOTE 2: The generic field may relate specifically to an "IP interface", "protocol layer 2 interface" or others. +NOTE 3: The combination of Interface and Id is unique. +NOTE 4: The MGC shall always use CHOOSE in an ADD request command. If not, the MG shall reply with an error descriptor using error code #501 "Not Implemented". +NOTE 5: The CHOOSE wildcard on 'Group' is *not* allowed in ETSI TISPAN "Ia Profiles". + +NOTE: The IBCF has the ability to choose the address space in which the TrGW will allocate an IP address for the termination by using the *ipdc/realm* property defined in the ITU-T Recommendation H.248.41 [14] IP domain connection package. + +H.248 wildcarding may be applied on IP Termination Identifiers. Wildcarding is limited according the two columns on the right hand side. + +The corresponding ABNF grammar is given below: + +ABNF (IETF RFC 5234 [25]) is used for the syntax specification. The ABNF for TerminationID and relation to pathNAME is defined in Annex B.2 of ITU-T Recommendation H.248.1 [3]. + +###### ABNF coding: + +``` + +pathNAME = EphToken SLASH EPHsystem +EphToken = "ip" ; prefix +EPHsystem = WildcardALL + / WildcardALL SLASH Interface + / Group SLASH WildcardALL + / (Group / WildcardCHOOSE) SLASH (Interface / WildcardCHOOSE) SLASH +(Identifier / WildcardALL / WildcardCHOOSE) +Group = %d0-65535 ; data type: INT16 +Interface = 1*51ALPHANUM +Identifier = %d1-4294967295 ; data type: INT32 +ALPHANUM = ALPHA / DIGIT +WildcardCHOOSE = "$" +WildcardALL = "*" + +``` + +##### 5.6.1.1.2 ASN.1 Coding Overview and prose specification + +The following general structure of termination ID shall be used: + +4 octets shall be used for the termination ID. The following defines the general structure for the termination ID: + +**Table 5.6.1.1.2.1: ASN.1 coding** + +| | | +|------------------|---| +| Termination type | X | +|------------------|---| + +Termination type: + +Length 3 bits + +Values: + +000 Reserved + +001 IP (Ephemeral) termination + +010 Reserved (in 3GPP Mc and Mn profile used for TDM termination) + +011 - 110 Reserved + +111 Reserved for ROOT termination Id (ROOT Termination ID = 0xFFFFFFFF) + +X: + +Length 29 bits. + +For IP termination, its usage is un-specified. + +### 5.6.2 Multiplexed terminations + +**Table 5.6.2.1: Multiplexed Terminations** + +| | | +|------------------------------------------|----| +| Multiplex Terminations Supported? | No | +|------------------------------------------|----| + +*If yes then:* + +**Table 5.6.2.2: Multiplex Types** + +| | | +|--------------------------------------------------------------|------| +| Multiplex Types Supported | None | +| Maximum Number of Terminations Connected to Multiplex | - | + +## 5.7 Descriptors + +### 5.7.1 TerminationState Descriptor + +**Table 5.7.1.1: ServiceState property** + +| | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------| +| ServiceState property used: | Yes (InService/OutOfService) NOTE 1, NOTE 2 | +| NOTE 1: This is restricted to the ROOT termination (for MGW audit). | | +| NOTE 2: Ephemeral H.248 Terminations have a ServiceState property according to ITU-T Recommendation H.248.1 [3], but explicit usage of the TerminationState Descriptor ServiceState property is not required by this Profile. ServiceState changes can still occur, however, and can be indicated in ServiceChange Commands (i.e. this means that the value of the ServiceState property may be implicitly changed by ServiceChange procedures). | | + +**Table 5.7.1.2: EventBufferControl property** + +| | | +|------------------------------------------|----| +| EventBufferControl property used: | No | +|------------------------------------------|----| + +### 5.7.2 Stream Descriptor + +#### 5.7.2.0 General + +**Table 5.7.2.1: Stream descriptor** + +| | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----|--------------------| +| Maximum number of streams per termination type: | IP | Unspecified (NOTE) | +| NOTE: At least one stream for each media component (e.g. video+audio = 2 streams). If only one stream is applicable, then the IBCF may omit the Stream Descriptor and the TrGW shall assume that StreamID = 1. | | | + +**Table 5.7.2.2: Stream configuration** + +| | | +|------------------------------|--------------------------------| +| Stream Configuration: | ALL configurations are allowed | +|------------------------------|--------------------------------| + +#### 5.7.2.1 LocalControl Descriptor + +**Table 5.7.2.1.1: Reserve Group and Reserve Value** + +| | | Termination Type | Stream Type | +|----------------------------|-----|------------------|--------------| +| Reserve group used: | No | NA | NA | +| Reserve value used: | Yes | IP | Audio, Video | + +**Table 5.7.2.1.2: Stream Mode** + +| Termination Type | Stream Type | Allowed StreamMode Values | +|-----------------------------------------------------------------------------|-------------|----------------------------------------| +| IP | RTP/AVP | SendOnly, RecvOnly, SendRecv, Inactive | +| | RTP/SAVP | SendOnly, RecvOnly, SendRecv, Inactive | +| | RTP/AVPF | SendOnly, RecvOnly, SendRecv, Inactive | +| | RTP/SAVPF | SendOnly, RecvOnly, SendRecv, Inactive | +| | TCP | SendRecv, Inactive | +| | TCP/MSRP | SendRecv, Inactive | +| | udptl | SendRecv, Inactive | +| | udp | SendOnly, RecvOnly, SendRecv, Inactive | +| NOTE: See table 5.15.2 for the stream types applicable to IMS-Ix and CS-Ix. | | | + +### 5.7.3 Events descriptor + +**Table 5.7.3.1: Events Descriptor** + +| | | | | +|---------------------------------------------------------------|--------------------------------------------------------------------------------|-------------------------|--------------------| +| Events settable on termination types and stream types: | Yes | | | +| If yes | Event ID | Termination Type | Stream Type | +| | Cause (g/cause, 0x0001/0x0001) - See sub-clause 5.14.3.1 | ALL except ROOT | ANY | +| | Inactivity Timeout (it/ito, 0x0045/0x0001) - See sub-clause 5.14.3.6 | only ROOT | Not applicable | +| | MG_Overload (ocp/mg_overload, 0x0051/0x0001) - See sub-clause 5.14.3.8 | only ROOT | Not applicable | +| | Termination Heartbeat (hangterm/thb, 0x0098/0x0001) - See sub-clause 5.14.3.9 | ALL except ROOT | Not applicable | +| | MGCon (chp/mgcon, 0x0029/0x0001) - See sub-clause 5.14.3.10 | only ROOT | Not applicable | +| | Available Realms Changed (ipra/arc, 0x00e0/0x0001) - See sub-clause 5.14.3.11 | only ROOT | Not applicable | +| | IP Flow Stop Detection (adid/ipstop, 0x009c/0x0001) - See sub-clause 5.14.3.14 | ALL except ROOT | ANY | +| | ECN Failure (ecnrous/fail, 0x010b/0x0001) - See sub-clause 5.14.3.15 | IP | RTP Based | + +**Table 5.7.3.2: Event Buffer Control** + +| | | +|-----------------------------------|----| +| Event Buffer Control used: | No | +|-----------------------------------|----| + +**Table 5.7.3.3: Keep Active** + +| | | +|-----------------------------------|----| +| Keepactive used on events: | No | +|-----------------------------------|----| + +**Table 5.7.3.4: Embedding in event** + +| | | +|-------------------------------------------------|----| +| Embedded events in an event descriptor: | No | +| Embedded signals in an event descriptor: | No | + +**Table 5.7.3.5: Regulated Embedded Events** + +| | | +|----------------------------------------------------|------| +| Regulated Embedded events are triggered on: | None | +|----------------------------------------------------|------| + +**Table 5.7.3.6: Reset Events Descriptor Flag** + +| | | +|------------------------------------------------|------| +| ResetEventsDescriptor used with events: | None | +|------------------------------------------------|------| + +**Table 5.7.3.7: Notification Behaviour** + +| | | +|-------------------------|------------| +| NotifyImmediate: | ALL Events | +| NotifyRegulated: | None | +| NeverNotify: | None | + +NOTE: tables 5.7.3.4 – 5.7.3.7 apply to version 3 of ITU-T Recommendation H.248.1 [3]. + +### 5.7.4 EventBuffer descriptor + +**Table 5.7.4.1: Event Buffer** + +| | | +|--------------------------------------|-----------------| +| Event Buffer descriptor used: | No | +| If yes | EventIDs | + +### 5.7.5 Signals descriptor + +**Table 5.7.5.1: Signals dependant on termination or streams** + +| | | | | +|-----------------------------------------------------------------------------|--------------------------------------------------------------------------------------|-------------------------|-------------------------| +| The setting of signals is dependant on termination or streams types: | No
NOTE – "No" means that all signals can be played on any termination or stream. | | | +| If yes | Signal ID | Termination Type | Stream Type / ID | +| | - | - | - | + +**Table 5.7.5.2: Signal Lists** + +| | | +|---------------------------------|---------------------------------------------------| +| Signals Lists supported: | No | +| If yes | Termination Type Supporting Lists | +| | - | +| | Stream Type Supporting lists | +| | - | +| | Maximum number of signals to a signal list | +| | - | +| | Intersignal delay parameter supported: | +| | - | + +**Table 5.7.5.3: Overriding Signal type and duration** + +| | | +|--------------------------------------------|----------------------------------| +| Signal type and duration supported: | No | +| If yes | Signal ID | +| | Type or duration override | +| | - | + +**Table 5.7.5.4: Signal Direction** + +| | | +|------------------------------------|----| +| Signal Direction supported: | No | +|------------------------------------|----| + +**Table 5.7.5.5: Notify completion** + +| | | +|------------------------------------|-------------------------------------| +| NotifyCompletion supported: | No | +| If yes | Signal ID | +| | Type of completion supported | +| | - | + +**Table 5.7.5.6: RequestID Parameter** + +| | | +|---------------------------------------|----| +| RequestID Parameter Supported: | No | +|---------------------------------------|----| + +**Table 5.7.5.7: Signals played simultaneously** + +| | | | +|---------------------------------------|-----------------------------------------------------|---| +| Signals played simultaneously: | No | | +| If yes | SignalIDs that can be played simultaneously: | - | + +**Table 5.7.5.8: Keep Active** + +| | | +|------------------------------------|----| +| KeepActive used on signals: | No | +|------------------------------------|----| + +### 5.7.6 DigitMap descriptor + +**Table 5.7.6.1: DigitMap Descriptor** + +| | | | | +|-----------------------------|----------------------|------------------|---------------| +| DigitMaps supported: | No | | | +| If yes | DigitMap Name | Structure | Timers | +| | - | - | - | + +### 5.7.7 Statistics descriptor + +**Table 5.7.7.1: Statistics Descriptor** + +| | | +|---------------------------------|---| +| Statistics supported on: | - | +|---------------------------------|---| + +**Table 5.7.7.2: Statistics reported on Subtract** + +| | | | | +|-----------------------------------------|-------------------------------|-------------------------|--------------------| +| Statistics reported on Subtract: | No | | | +| If yes | Statistic IDs Reported | Termination Type | Stream Type | +| | - | - | - | + +### 5.7.8 ObservedEvents descriptor + +**Table 5.7.8.1: ObservedEvents Descriptor** + +| | | +|----------------------------------------|----| +| Event detection time supported: | No | +|----------------------------------------|----| + +### 5.7.9 Topology descriptor + +**Table 5.7.9.1: Topology descriptor** + +| | | +|------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------| +| Allowed triples: | (T1, T2, isolate)
(T1, T2, bothway) | +| NOTE: The Topology Descriptor shall be supported by the MGW and MGC for handover only, when PS-to-CS access transfer is supported. | | + +### 5.7.10 Error descriptor + +**Table 5.7.10.1: Error codes sent by the IBCF** + +| | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Supported H.248.8 Error Codes: | #400 "Syntax error in message"
#401 "Protocol Error"
#402 "Unauthorized"
#403 "Syntax Error in TransactionRequest"
#406 "Version Not Supported"
#410 "Incorrect identifier"
#411 "The transaction refers to an unknown ContextID"
#413 "Number of transactions in message exceeds maximum"
#421 "Unknown action or illegal combination of actions"
#422 "Syntax Error in Action"
#430 "Unknown TerminationID"
#431 "No TerminationID matched a wildcard"
#442 "Syntax Error in Command"
#443 "Unsupported or Unknown Command"
#444 "Unsupported or Unknown Descriptor"
#445 "Unsupported or Unknown property"
#446 "Unsupported or Unknown Parameter"
#447 "Descriptor not legal in this command"
#448 "Descriptor appears twice in a command"
#449 "Unsupported parameter or property value"
#450 "No such property in this package"
#451 "No such event in this package"
#454 "No such parameter value in this package"
#455 "Property illegal in this Descriptor"
#456 "Property appears twice in this Descriptor"
#457 "Missing parameter in signal or event"
#458 "Unexpected Event/RequestID"
#501 "Not Implemented"
#502 "Not ready"
#505 "Transaction Request Received before a ServiceChange Reply has been received"
#506 "Number of TransactionPendings Exceeded"
#533 "Response exceeds maximum transport PDU size" | +| Supported Error Codes defined in packages: | All error codes defined in supported packages are supported. | +| NOTE: the error codes listed need not be supplied by the IBCF to differentiate each and every error described by them. The TrGW shall be able to receive the error codes listed. | | + +**Table 5.7.10.2: Error codes sent by the TrGW** + +| | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Supported H.248.8 Error Codes: | #400 "Syntax error in message"
#401 "Protocol Error"
#402 "Unauthorized"
#403 "Syntax Error in TransactionRequest"
#406 "Version Not Supported"
#410 "Incorrect identifier"
#411 "The transaction refers to an unknown ContextID"
#412 "No ContextIDs available"
#413 "Number of transactions in message exceeds maximum"
#421 "Unknown action or illegal combination of actions"
#422 "Syntax Error in Action"
#430 "Unknown TerminationID"
#431 "No TerminationID matched a wildcard"
#432 "Out of TerminationIDs or No TerminationID available"
#433 "TerminationID is already in a Context"
#434 "Max number of Terminations in a Context exceeded"
#435 "Termination ID is not in specified Context"
#440 "Unsupported or unknown Package"
#441 "Missing Remote or Local Descriptor"
#442 "Syntax Error in Command"
#443 "Unsupported or Unknown Command"
#444 "Unsupported or Unknown Descriptor"
#445 "#Unsupported of Unknown property"
#446 "Unsupported or Unknown Parameter"
#447 "Descriptor not legal in this command"
#448 "Descriptor appears twice in a command"
#449 "Unsupported parameter or property value"
#450 "No such property in this package"
#451 "No such event in this package"
#452 "No such signal in this package"
#454 "No such parameter value in this package"
#455 "Property illegal in this Descriptor"
#456 "Property appears twice in this Descriptor"
#457 "Missing parameter in signal or event"
#471 "Implied Add for Multiplex failure"
#500 "Internal software Failure in MG or MGC"
#501 "Not Implemented"
#502 "Not ready"
#505 "Transaction Request Received before a ServiceChange Reply has been received"
#506 "Number of TransactionPendings Exceeded"
#510 "Insufficient resources"
#511 "Temporarily Busy"
#512 "Media Gateway unequipped to detect requested Event"
#513 "Media Gateway unequipped to generate requested Signals"
#515 "Unsupported Media Type"
#517 "Unsupported or invalid mode"
#522 "Functionality Requested in Topology Triple Not Supported"
#526 "Insufficient bandwidth"
#529 "Internal hardware failure in MG"
#530 "Temporary Network failure"
#531 "Permanent Network failure"
#532 "Audited Property, Statistic, Event or Signal does not exist"
#533 "Response exceeds maximum transport PDU size"
#534 "Illegal write of read only property"
#542 "Command is not allowed on this termination" | +| Supported Error Codes defined in packages: | All error codes defined in supported packages need to be supported. | +| NOTE: the error codes listed need not be supplied by the TrGW to differentiate each and every error described by them. The IBCF shall be able to receive the error codes listed. | | + +## 5.8 Command API + +### 5.8.1 Add + +**Table 5.8.1.1: Descriptors used by Add request** + +| | | +|-----------------------------------------|-------------------------------------------------------------| +| Descriptors used by Add request: | Media (Stream(LocalControl, Local, Remote)), Event, Signals | +|-----------------------------------------|-------------------------------------------------------------| + +**Table 5.8.1.2: Descriptors used by Add reply** + +| | | +|---------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Descriptors used by Add reply: |

Media (Stream (Local)), Error

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

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

Media (Stream(Local)), Error

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

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

, , and are required if the "m=" line is included.

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

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

Transport protocol
As in table 5.15.2.

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

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

If the MG does not support the requested media format value the MG shall reject the command with error code 449. | +| b-line | "SDP_B " | Shall not be used without an "m=" line.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

"t=0 0"

| +|

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

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

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

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

2) Application " Media interworking (transcoding)":
The "a=" line provides the complementary information for the "m=" line with regards to a specified media type/format (e.g. an optional SDP „a=ptime" line for a particular media format).
For a dynamic RTP payload type, for each media information on the codec type shall be provided in a separate SDP "a=rtpmap" line and possibly additional SDP "a=fmtp"-line(s). For AVPF transport, the "rtcp-fb" SDP attribute defined in IETF RFC 4585 [30] may be used to provide the feedback message types the TrGW is allowed to send and to indicate RTCP timing information. For ECN interworking, the "rtcp-xr" SDP attribute defined in IETF RFC 3611 [36] may be used with "ecn-sum" value as defined in IETF RFC 6679 [35]. (NOTE)

| +| NOTE: Media Interworking is optional for IMS-Ix and not required for CS-Ix. | | | + +## 5.17 Procedures + +### 5.17.1 Formats and Codes + +Table 5.17.1.1 shows the parameters which are required for the procedures defined in the following clauses. + +The coding rules applied in ITU-T Recommendation H.248.1 [3] for the applicable coding technique shall be followed for the UMTS capability set. + +The binary encoding rules which are applicable to the defined Abstract Syntaxes are the Basic Encoding Rules for Abstract Syntax Notation One, defined in ITU-T Recommendation X.690 [28]. Specifically in accordance with ITU-T Recommendation X.690 [28] section 7.3, alternative encodings based on the definite and indefinite form of length are permitted by the basic encoding rules as a sender's option. Receivers shall support both alternatives. + +Unsupported values of parameters or properties may be reported by the TrGW and shall be supported by the IBCF as such by using H.248.1 error code #449 "Unsupported or Unknown Parameter or Property Value". The unsupported or unknown value is included in the error text in the error descriptor. + +###### **Table 5.17.1.1: Information Elements Used in Procedures** + +| Signalling Object | H.248 Descriptor | Coding | +|----------------------------|------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Alternate MGC Id | ServiceChange | The MGCIdToTry parameter in ITU-T Recommendation H.248.1 [3]. | +| Available Realms | Termination State | According to Available Realms property in ITU-T Recommendation H.248.41 [14]. | +| BNC Release | Events,
ObservedEvents
Descriptor | As for the Events/ObservedEvents Descriptor in subclause E.1.2.1/ITU-T Recommendation H.248.1 [3] "Cause" | +| Cause | ObservedEvents
Descriptor | As for the ObservedEventsDescriptor Parameter in subclause E.1.2.1/ ITU-T Recommendation H.248.1 [3] "General cause" | +| Changed Realms | Observed Events | According to Observed Events Parameters for Available Realms Changed event in ITU-T Recommendation H.248.41 [14]. | +| Codec List | Local Descriptor or
Remote Descriptor | in a single SDP m-line.
For a static RTP payload type, the codec type should be implied by the RTP payload type, if not then each codec type shall be provided in a separate SDP "a=rtpmap"-line and possibly additional SDP "a=fmtp"-line(s).
For a dynamic RTP payload type, for each codec information on the codec type shall be provided in a separate SDP "a=rtpmap"-line and possibly additional SDP "a=fmtp"-line(s). | +| Connectivity Mode | Local Control | ITU-T Recommendation H.248.1 [3] Mode property.
Binary Encoding: Encoding as per ITU-T Recommendation H.248.1 Annex A [3] "streamMode"
Textual Encoding: Encoding as per ITU-T Recommendation H.248.1 Annex B [3]"streamMode". | +| Context ID | NA | Binary Encoding: As per ITU-T Recommendation H.248.1 [3] Annex A.
Textual Encoding: As per ITU-T Recommendation H.248.1 [3] Annex B. | +| Delay Variation Tolerance | Local Control | This is the tman/dvt property from ITU-T Recommendation H.248.53 [13] | +| Diffserv Code Point | Local Control | Defined according to the Differentiated Services Code Point property in ITU-T Recommendation H.248.52 [12]. | +| Diffserv Tagging Behaviour | Local Control | Defined according to the Tagging Behaviour property in ITU-T Recommendation H.248.52 [12]. | +| ECN Congestion Response | Local descriptor or
Remote Descriptor | Defined according to "Congestion Response Method" property in ITU-T Recommendation H.248.82 [40]. (NOTE) | +| ECN ECT Marking | Local descriptor or
Remote Descriptor | Defined according to "ECT Marking" property in ITU-T Recommendation H.248.82 [40].
(NOTE) | +| ECN Enabled | Local Descriptor or
Remote Descriptor | Defined according to the "ECN Enabled" property in ITU-T Recommendation H.248.82 [40]. | +| ECN Failure | Events,
Observed Events | Defined according to the "ECN Failure" Event in ITU-T Recommendation H.248.82 [40]. | +| ECN Failure Type | ObservedEvents
Descriptor | As for the ObservedEventsDescriptor Parameter "Failure Type" in ITU-T Recommendation H.248.82 [40]. | +| ECN Initiation Method | Local Descriptor or
Remote Descriptor | Defined according to "Initiation Method" property in ITU-T Recommendation H.248.82 [40]. | +| ECN Mode | Local Descriptor or
Remote Descriptor | Defined according to the "ECN Mode" property in ITU-T Recommendation H.248.82 [40].
(NOTE) | +| ECN RTCP Feedback | Local Descriptor or
Remote Descriptor | "rcfp-fb" SDP attribute with the "nack" feedback parameter as defined in IETF RFC 4585 and the "ecn" parameter value according to IETF RFC 6679 [35] | +| ECN XR Summary Report | Local Descriptor or
Remote Descriptor | "ecn-sum" value as defined in IETF RFC 6679 [35] within a "rtcp-xr" SDP attribute in accordance with IETF RFC 3611 [36] | +| Emergency Call Indication | NA | ITU-T Recommendation H.248.1 [3] 6.1.1 Emergency Call Indicator
Binary Encoding: Encoding as per ITU-T Recommendation H.248.1 [3] Annex A "Emergency" context attribute
Textual Encoding: Encoding as per ITU-T Recommendation H.248.1 [3] Annex B "EmergencyToken" context attribute | +| Inactivity Timeout | Events,
Observed Events | Defined according to Inactivity Timeout event in ITU-T Recommendation H.248.14 [19]. | +| IP Address | Local Descriptor or
Remote Descriptor | in SDP "c-line" | +| IP Interface | Local control | As for the property "IP interface type" in subclause 15.2.11.1 in 3GPP TS 29.232 [21] | + +| | | | +|--------------------------------------|---------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| IP Realm Identifier | Local Control | According to IP Realm Identifier property in ITU-T Recommendation H.248.41 [14]. | +| IP Version | Local Descriptor or Remote Descriptor |
in SDP "c-line", see 5.15 | +| Maximum Burst Size | Local Control | This is the tman/mbs property from ITU-T Recommendation H.248.53 [13] | +| Media Inactivity Detection | Events, Observed Events | Defined according to IP Flow Stop Detection event in ITU-T Recommendation H.248.40 [27]. | +| Media Inactivity Detection Time | Events | As for the Event Parameter in ITU-T Recommendation H.248.40 [27] "Detection Time" | +| Media Inactivity Detection Direction | Events | As for the Event Parameter in ITU-T Recommendation H.248.40 [27] "Direction" | +| Media Type | Local Descriptor or Remote Descriptor | in SDP m-line "audio", "video" or "-" | +| Overload Notification | Events, Observed Events | This is the chp/mgcon event from ITU-T Recommendation H.248.10 [20] or the ocp/mg_overload event from ITU-T Recommendation H.248.11 [16]. | +| Peak Data Rate | Local Control | This is the tman/pdr property from ITU-T Recommendation H.248.53 [13]. | +| Policing Required | Local Control | This is the tman/pol property from ITU-T Recommendation H.248.53 [13]. | +| Port | Local Descriptor or Remote Descriptor | in SDP m-line. | +| Priority Information | NA | Priority Indicator (subclause 6.1.1 of ITU-T Recommendation H.248.1 [3])
Binary Encoding: Encoding as per ITU-T Recommendation H.248.1 [3] Annex A "priority" context attribute
Textual Encoding: Encoding as per ITU-T Recommendation H.248.1 [3] Annex B "priority" context attribute | +| Realm Availability Change | Events, Observed Events | According to Available Realms Changed event in ITU-T Recommendation H.248.41 [14]. | +| Reduction | ObservedEvent Descriptor | As for the ObservedEventDescriptor in subclause 4.2.1/ ITU-T Recommendation H.248.10 [20] "MGCongestion". | +| Remote Source Address Filtering | Local Control | Defined according to Remote Source Address Filtering property in ITU-T Recommendation H.248.43 [6]. | +| Remote Source Address Mask | Local Control | Defined according to Remote Source Address Mask property in ITU-T Recommendation H.248.43 [6]. | +| Remote Source Port Filtering | Local Control | Defined according to Remote Source Port Filtering property in ITU-T Recommendation H.248.43 [6]. | +| Remote Source Port | Local Control | Defined according to Remote Source Port property in ITU-T Recommendation H.248.43 [6]. | +| Remote Source Port Range | Local Control | Defined according to Remote Source Port Range property in ITU-T Recommendation H.248.43 [6]. | +| Reserve_Value | Local Control | ITU-T Recommendation H.248.1 [3] Reserve property.
Binary Encoding: Encoding as per ITU-T Recommendation H.248.1[3] Annex A "reserveValue"
Textual Encoding: Encoding as per ITU-T Recommendation H.248.1 [3] Annex B "reservedValueMode". | +| ROOT Properties | Termination State | The properties in subclause E.2.1/ITU-T Recommendation H.248.1 [3] | +| RTCP allocation | Local Control | Defined according to RTCP Allocation Specific Behaviour property in ITU-T Recommendation H.248.57 [5]. | +| RtcpbwRR | Local Descriptor or Remote Descriptor | in SDP "b:RR"-line. see 5.15 | +| RtcpbwRS | Local Descriptor or Remote Descriptor | in SDP "b:RS"-line. see 5.15 | +| Rtpbw | Local Descriptor or Remote Descriptor | in SDP "b:AS"-line. see 5.15 | +| RTPpayload | Local Descriptor or Remote Descriptor | in SDP m-line. This may be set to CHOOSE (\$) in a LD sent from the IBCF toward the TrGW. | +| Stream Number | Stream | Encoding as per ITU-T Recommendation H.248.1 [3]Annex B "Stream"/"ST".
For a single stream, this may be omitted by the CS-IBCF. | +| Sustainable Data Rate | Local Control | This is the tman/sdr property from ITU-T Recommendation H.248.53 [13] | + +| | | | +|---------------------------------------------------------------------------------------|------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------| +| Termination heartbeat | Events
ObservedEvents | As per Termination Heartbeat defined in ITU-T Recommendation H.248.36 [15] Clause 5.2.1. | +| Termination ID | NA | Binary Encoding: As per ITU-T Recommendation H.248.1 [3] Annex A.
Textual Encoding: As per ITU-T Recommendation H.248.1 [3] Annex B. | +| Transaction ID | NA | Binary Encoding: As per ITU-T Recommendation H.248.1 [3] Annex A.
Textual Encoding: As per ITU-T Recommendation H.248.1 [3] Annex B. | +| Transport | Local Descriptor or
Remote Descriptor | in SDP m-line, see 5.15 | +| NOTE: This property is only signalled for IP terminations towards external IP network | | | + +### 5.17.2 Call Related Procedures + +#### 5.17.2.1 General + +This section describes the various call related procedures performed by the TrGW, which are listed in table 5.17.2.1.1 + +**Table 5.17.2.1.1: TrGW Call Related Procedures** + +| Transaction defined in 3GPP TS 29.235 [17] or 3GPP TS 29.162 [18] | Supported | Comment | +|-------------------------------------------------------------------|-----------|---------------| +| Reserve TrGW Connection Point | Mandatory | See 5.17.2.2 | +| Configure TrGW Connection Point | Mandatory | See 5.17.2.3 | +| Reserve and Configure TrGW Connection Point | Mandatory | See 5.17.2.4 | +| Release TrGW Termination | Mandatory | See 5.17.2.5 | +| Termination Heartbeat Indication | Mandatory | See 5.17.2.6 | +| IP Bearer Released | Mandatory | See 5.17.2.7 | +| Media Inactivity Notification | Optional | See 5.17.2.8 | +| Change Through Connection | Mandatory | See 5.17.2.9 | +| ECN Failure Indication | Optional | See 5.17.2.10 | +| Change Flow Direction | Optional | See 5.17.2.11 | + +#### 5.17.2.2 Reserve TrGW Connection Point + +The IBCF sends an ADD request command as in Table 5.17.2.2.1. + +##### **Table 5.17.2.2.1: Reserve TrGW Connection Point Request** + +| Address Information | Control information | Bearer information | +|----------------------------|----------------------------|---------------------------| +|----------------------------|----------------------------|---------------------------| + +| | | | +|--------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Local Descriptor {
Port = \$
IP Address = \$
IP Version = IPv4 or IPv6
} | Transaction ID = x
If Context Requested:
Context ID= \$
If Emergency Call:
Emergency Call Indication

If MPS call/session:
Priority Indicator = x

If Context Provided:
Context ID = c1

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

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

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

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

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

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

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

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

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

If peak data rate policing | Local Descriptor {
If media is "audio" or "video":
Codec List = Codec List
RTP Payloads = RTP Payload
Rtpbw
If RTCP bandwidth
RtcpbwRS
RtcpbwRR

} | +|--------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--| +| | Policing Required
Peak Data Rate
If Delay Variation required
Delay Variation Tolerance

If RTCP handling required:
RTCP allocation

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

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

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

RTCP Feedback = "ECN RTCP Feedback" NOTE 3

XR Summary Report = "ECN XR Summary Report" NOTE 3
If notification of ECN Failure Report:
NotificationRequested (Event ID = x, " ECN Failure") | | +| NOTE 1: The event parameters "Media Inactivity Detection Time" and "Media Inactivity Detection Direction" are optional.
NOTE 2: This shall be set to a value other than "inactive"
NOTE 3: For the IMS side/3GPP ECN profile terminations this property does not need to be signalled; default provisioned values are defined for this profile. For procedures to handle interworking between different ECN property settings see 3GPP TS 29.162 [18]. | | | + +Editor's Note: IP Interface Type needs to be further clarified in stage 2 – possible exclusion for IMS Ix. + +On reserving the termination, the TrGW responds as in Table 5.17.2.2.2. + +**Table 5.17.2.2.2: Reserve TrGW Connection Point Acknowledge** + +| Address Information | Control information | Bearer information | +|-------------------------------------------------------------|-------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------| +| Local Descriptor {
Port
IP Address
IP Version
} | Transaction ID = x
Context ID = C1
Termination ID = T1
Stream Number | Local Descriptor {
If media is "audio" or "video":

Codec List
RTP Payloads
Rtpbw
If RTCP bandwidth
RtcpbwRS
RtcpbwRR
} | + +#### 5.17.2.3 Configure TrGW Connection Point + +The IBCF sends a MODIFY request command as in Table 5.17.2.3.1. + +##### **Table 5.17.2.3.1: Configure TrGW Connection Point Request** + +| Address Information | Control information | Bearer information | +|----------------------------|----------------------------|---------------------------| +|----------------------------|----------------------------|---------------------------| + +| | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +|

If local resources are modified:
Local Descriptor {
  Port
  IP Address
  IP Version
}
If remote resources are modified:
Remote Descriptor {
  Port
  IP Address
  IP Version
}

|

Transaction ID = x
Context ID = C1
Termination ID = T1

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

If Stream Number specified:
  Stream Number

If Resources for multiple Codecs required:
  Reserve_Value

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

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

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

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

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

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

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

If RTCP handling required:
  RTCP allocation

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

If ECN Endpoint support required

|

If local resources are modified:
Local Descriptor {
  If media is "audio" or "video":
    Codec List
    RTP Payloads
    Rtpbw
    If RTCP bandwidth
      RtcpbwRS
      RtcpbwRR
}
If remote resources are modified:
Remote Descriptor {
  If media is "audio" or "video":
    Codec List
    RTP Payloads
    Rtpbw
    If RTCP bandwidth
      RtcpbwRS
      RtcpbwRR
}

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

ECN Enable = "True"
Initiation Method = "ECN Initiation Method" NOTE 3

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

RTCP Feedback = "ECN RTCP Feedback" NOTE 4

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

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

| | +|

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

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

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

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

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

| | | + +The TrGW responds as in Table 5.17.2.3.2. + +**Table 5.17.2.3.2: Configure TrGW Connection Point Request Acknowledge** + +| Address Information | Control information | Bearer information | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| If local resources were provided in request:
Local Descriptor {
Port
IP Address
IP Version
}
If remote resources are provided in request:
Remote Descriptor {
Port
IP Address
IP Version
} NOTE | Transaction ID = x
Context ID = C1
Termination ID = T1

If Stream Number Specified:
Stream Number | If local resources were provided in request:
Local Descriptor {
If media is "audio" or "video":
Codec List
RTP Payloads
Rtpbw
If RTCP bandwidth
RtcpbwRS
RtcpbwRR
}
If remote resources are provided in request:
Remote Descriptor {
If media is "audio" or "video":
Codec List
RTP Payloads
Rtpbw
If RTCP bandwidth
RtcpbwRS
RtcpbwRR
} NOTE | +| NOTE: Sending of the Remote Descriptor is optional | | | + +#### 5.17.2.4 Reserve and Configure TrGW Connection Point + +The IBCF sends an ADD request command as in Table 5.17.2.4.1. + +##### **Table 5.17.2.4.1: Reserve and Configure TrGW Connection Point Request** + +| Address Information | Control information | Bearer information | +|----------------------------|----------------------------|---------------------------| +|----------------------------|----------------------------|---------------------------| + +| | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Local Descriptor {
Port = \$
IP Address = \$
IP Version = IPv4 or IPv6
}
Remote Descriptor {
Port
IP Address
IP Version
} | Transaction ID = x
If Context Requested:
Context ID = \$
If Emergency Call:
Emergency Call Indication

If MPS call/session:
Priority Indicator = x

If Context Provided:
Context ID = c1

Termination ID = \$

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

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

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

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

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

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

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

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

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

If Sustainable Data Rate Policing
Required:-
Policing Required
Sustainable Data Rate
Maximum Burst Size | Local Descriptor {
If media is "audio" or "video":
Codec List
RTP Payloads
Rtpbw
If RTCP bandwidth
RtcpbwRS
RtcpbwRR

}
Remote Descriptor {
If media is "audio" or "video":
Codec List
RTP Payloads
Rtpbw
If RTCP bandwidth
RtcpbwRS
RtcpbwRR

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

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

If RTCP handling required:
RTCP allocation

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

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

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

RTCP Feedback = "ECN RTCP Feedback" NOTE 3

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

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

| | +|

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

| | | + +The TrGW responds as in Table 5.17.2.4.2. + +**Table 5.17.2.4.2: Reserve and Configure TrGW Connection Point Request Acknowledge** + +| Address Information | Control information | Bearer information | +|----------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Local Descriptor {
Port
IP Address
IP Version
}
Remote Descriptor {
Port
IP Address
IP Version
} NOTE | Transaction ID = x
Context ID = C1
Termination ID = T1
Stream Number | Local Descriptor {
If media is "audio" or "video":
Codec List
RTP Payloads
Rtpbw
If RTCP bandwidth
RtcpbwRS
RtcpbwRR
}
Remote Descriptor {
If media is "audio" or "video":
Codec List
RTP Payloads
Rtpbw
If RTCP bandwidth
RtcpbwRS
RtcpbwRR
}
} NOTE | +| NOTE: Sending of the Remote Descriptor is optional | | | + +#### 5.17.2.5 Release TrGW Termination + +The IBCF sends a SUBTRACT command as in Table 5.17.2.5.1. + +**Table 5.17.2.5.1: Release TrGW Termination Request** + +| Address Information | Control information | Bearer information | +|----------------------------|---------------------------------------------------------------------|---------------------------| +| | Transaction ID = x
Context ID= C1/ALL
Termination ID = T1/ALL | | + +On releasing the termination, the TrGW responds as in Table 5.17.2.5.2 + +**Table 5.17.2.5.2: Release TrGW Termination Request Acknowledge** + +| Address Information | Control information | Bearer information | +|----------------------------|----------------------------------------------------------------------|---------------------------| +| | Transaction ID = x
Context ID = C1/ALL
Termination ID = T1/ALL | | + +#### 5.17.2.6 Termination Heartbeat Indication + +When the procedure "Termination heartbeat indication" is required the following procedure is initiated: the TrGW sends a NOT.req command with the following information. + +**5.17.2.6.1 NOT.req (Termination heartbeat)** + +| Address Information | Control information | Bearer information | +|----------------------------|----------------------------------------------------------------------------------------------------------------------|---------------------------| +| | Transaction ID = x
Context ID = C1
Termination ID = T1

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

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

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

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

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

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

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

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

Audit Packages (NOTE 1)

Audit Descriptor =
IndAuditParameter:=
IndAudMediaDescriptor:=
IndAudTerminationStateDescriptor:=
serviceState

Audit Descriptor = Empty (NOTE 2)

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

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

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

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

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

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

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

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

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

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

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

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

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