Content for TR 24.802 Word version: 12.1.0
4 Scenarios
5 Requirements
6 Charging considerations
7 Possible solutions
8 Other interfaces that requires identification
9 Conclusion
A Determine II-NNI traversal scenario type
B Requirement for an explicit indication of the II-NNI traversal scenario type
$ Change history
4 Scenarios p. 8
4.1 Introduction p. 8
4.2 Roaming user on the originating side II-NNI traversal scenario types p. 9
4.2.1 Overview p. 9
4.2.2 Dialog creating SIP request and stand-alone SIP requests using the registration path p. 9
4.2.3 Subscription to user's registration-state event package p. 10
4.2.4 Initial INVITE request due to SRVCC p. 10
4.2.5 MRF/MRB to MRF/MRB p. 10
4.2.6 Loopback p. 11
4.3 Signalling between originating home and terminating home side II-NNI traversal scenario types p. 11
4.3.1 Overview p. 11
4.3.2 Dialog creating SIP request and stand-alone SIP requests between home A and home B p. 13
4.3.3 Dialog creating SIP request and stand-alone SIP requests between home A and an IMS transit network providing application services in the transit network p. 13
4.3.4 Dialog creating SIP request between visited A and home B p. 13
4.3.5 Dialog creating SIP request between visited A and an IMS transit network providing application services in the transit network p. 13
4.3.6 Dialog creating SIP request and stand-alone SIP requests between IMS transit network and home B p. 14
4.4 Roaming user on the terminating side II-NNI traversal scenario types p. 14
4.4.1 Overview p. 14
4.4.2 Dialog creating SIP request and stand-alone SIP requests using the registration path p. 14
4.4.3 SRVCC information p. 15
4.5 Usages of information on II-NNI traversal scenario types p. 15
4.5.1 Screening of SIP signalling p. 15
4.5.2 Disallowing communication related to certain II-NNI traversal scenario types p. 15
4.5.3 Tracking of interoperability errors p. 15
4.5.4 Enabling or disabling of OMR p. 16
4.5.5 Transcoding control p. 16
4.5.6 Collection of CDRs p. 16
4.5.7 Allowing the forwarding of incoming communication only to suitable nodes p. 16
4.6 Summary of identified issues p. 16
5 Requirements p. 17
5.1 Introduction p. 17
5.2 Interconnection requirements p. 18
6 Charging considerations p. 18
7 Possible solutions p. 18
7.1 Introduction p. 18
7.2 Implicit detection of II-NNI traversal scenario type p. 19
7.2.1 Procedure p. 19
7.2.2 Security aspects of the implicit detection of the II-NNI traversal scenario solution p. 20
7.3 Explicit indication of II-NNI traversal scenario type p. 20
7.3.1 Procedures p. 20
7.3.2 Encoding Options p. 21
7.3.2.1 General p. 21
7.3.2.2 New SIP header field p. 21
7.3.2.3 Enhancing P-Charging-Vector SIP header field p. 25
7.3.2.4 New value(s) for the SIP Feature-Caps header field p. 30
7.3.2.4.1 General p. 30
7.3.2.4.2 Example of usage of the g.3gpp.ii-nni feature capability indicator p. 32
7.3.2.5 URI parameters p. 35
7.3.2.6 Route header field parameter p. 40
7.3.3 Evaluation of compliance with the requirements in annex B p. 45
7.3.4 Security aspects of the explicit indication of the II-NNI traversal scenario solutions p. 47
8 Other interfaces that requires identification p. 47
9 Conclusion p. 47
9.1 General p. 47
9.2 Implicit detection of II-NNI traversal scenario - explicit indication of II-NNI traversal scenario p. 48
9.3 Explicit indication of II-NNI traversal scenario solutions p. 48
9.4 Recommendation p. 51
A Determine II-NNI traversal scenario type p. 52
A.1 Scope p. 52
A.2 Introduction p. 52
A.3 SUBSCRIBE request example p. 53
A.3.1 Introduction to the example p. 53
A.3.2 Implicit detection of the II-NNI traversal scenario type p. 55
A.3.2.1 SUBSCRIBE request content at different II-NNI traversal scenario types p. 55
A.3.2.2 IBCF acting as an exit point p. 57
A.3.2.3 IBCF acting as an entry point p. 57
A.3.3 Explicit indication of the II-NNI traversal scenario type p. 58
A.3.3.1 The "Subscribe to reg-event" II-NNI traversal scenario type between visited X and home A p. 58
A.3.3.2 The "Dialog creating SIP request and stand-alone SIP requests using the registration path" II-NNI traversal scenario type between visited X and home A p. 58
A.3.3.3 The "Dialog creating SIP request and stand-alone SIP requests between home A and home B" II-NNI traversal scenario type p. 59
A.3.3.4 The "Dialog creating SIP request and stand-alone SIP requests using the registration path" II-NNI traversal scenario type between home B and visited Y p. 59
A.3.3.5 The "Home A to transit Z" II-NNI traversal scenario type p. 59
A.3.3.6 The "Transit Z to home B" II-NNI traversal scenario type p. 59
A.3.3.7 Summary detection of the II-NNI traversal scenario types using explicit indication for the SUBSCRIBE request p. 59
B Requirement for an explicit indication of the II-NNI traversal scenario type p. 60
B.1 Scope p. 60
$ Change history p. 64
