Content for TS 29.165 Word version: 18.3.0
...
1 Scope p. 9
The objective of this document is to address the Inter-IMS Network to Network Interface (II-NNI) consisting of Ici and Izi reference points between IMS networks in order to support end-to-end service interoperability.
The present document addresses the issues related to control plane signalling (3GPP usage of SIP and SDP protocols, required SIP header fields) as well as other interconnecting aspects like security, numbering/naming/addressing and user plane issues as transport protocol, media and codecs actually covered in a widespread set of 3GPP specifications. A profiling of the Inter-IMS Network to Network Interface (II-NNI) is also provided.
Charging aspects are addressed as far as SIP signalling is concerned.
IMS emergency session establishment between IMS networks is addressed as far as SIP signalling is concerned.
SIP signalling traversing the NNI between a CSCF and MRB, e.g. for media control or Voice Interworking with Enterprise IP-PBX, and SIP signalling traversing the NNI on the Mr interface between the CSCF and the MRFC, or on the Mr' interface between the AS and MRFC, or on the Rc interface between AS and MRB is not considered in the present release of this specification.
SIP signalling traversing the NNI between an application server and the remaining IMS functional entities (e.g. for MCPTT interface SIP-2 in Figure 7.3.1-2 in TS 23.280) is not considered in the present release of this specification.
SIP signalling traversing the NNI between an ISC gateway and an AS in an enterprise network, e.g. for media control and voice interworking with enterprise IP-PBX, on the ISC interface between the ISC gateway and the enterprise network is not considered in the present release of this specification.
2 References p. 9
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]
TR 21.905: "Vocabulary for 3GPP Specifications".
[2]
RFC 791: "Internet Protocol".
[3]
TS 23.002: "Network architecture".
[4]
TS 23.228: "IP Multimedia Subsystem (IMS); Stage 2".
[5]
TS 24.229: "Internet Protocol (IP) multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3".
[6]
TR 24.930: "Signalling flows for the session setup in the IP Multimedia core network Subsystem (IMS) based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3".
[7]
RFC 2460: "Internet Protocol, Version 6 (IPv6) Specification".
[8]
TS 29.162: "Interworking between the IM CN subsystem and IP networks".
[9]
TS 22.228: "Service requirements for the IP multimedia core network subsystem".
[10]
TS 33.210: "3G security; Network Domain Security (NDS); IP network layer security".
[11]
TS 26.114: "IP Multimedia Subsystem (IMS); Multimedia Telephony; Media handling and interaction".
[12]
ETSI TS 181 005 V1.1.1: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Services and Capabilities Requirements".
[13]
RFC 3261: "SIP: Session Initiation Protocol".
[14]
RFC 3966: "The tel URI for Telephone Numbers".
[15]
RFC 3860: "Common Profile for Instant Messaging (CPIM)".
[16]
RFC 3859: "Common Profile for Presence (CPP)".
[17]
RFC 4975: "The Message Session Relay Protocol (MSRP)".
[18]
RFC 3262: "Reliability of provisional responses in Session Initiation Protocol (SIP)".
[19]
RFC 3428: "Session Initiation Protocol (SIP) Extension for Instant Messaging".
[20]
RFC 6665: "SIP-Specific Event Notification".
[21]
RFC 3903: "An Event State Publication Extension to the Session Initiation Protocol (SIP)".
[22]
RFC 3515: "The Session Initiation Protocol (SIP) REFER method".
[23]
RFC 3311: "The Session Initiation Protocol (SIP) UPDATE method".
[24]
RFC 7315: "Private Header (P-Header) Extensions to the Session Initiation Protocol (SIP) for the 3GPP".
[24A]
RFC 7976: "Updates to Private Header (P-Header) Extension Usage in Session Initiation Protocol (SIP) Requests and Responses".
[24B]
RFC 7913: "P-Access-Network-Info ABNF Update".
[25]
RFC 7044: "An Extension to the Session Initiation Protocol (SIP) for Request History Information".
[26]
RFC 6050: "A Session Initiation Protocol (SIP) Extension for the Identification of Services".
[27]
RFC 4168: "The Stream Control Transmission Protocol (SCTP) as a Transport for the Session Initiation Protocol (SIP)".
[28] Void.
[29]
TS 32.260: "Telecommunication management; Charging management; IP Multimedia Subsystem (IMS) charging".
[30]
TS 22.173: "IP Multimedia Core Network Subsystem (IMS); Multimedia Telephony Service and supplementary services; Stage 1".
[31]
TS 24.173: "IMS multimedia telephony communication service and supplementary services; Stage 3".
[32]
TS 24.607: "Originating Identification Presentation (OIP) and Originating Identification Restriction (OIR) using IP Multimedia (IM); Core Network (CN) subsystem".
[33]
TS 24.616: "Malicious Communication Identification (MCID) using IP Multimedia (IM) Core Network (CN) subsystem".
[34]
RFC 3323: "A Privacy Mechanism for the Session Initiation Protocol (SIP)".
[35]
TS 23.003: "Numbering, addressing and identification".
[36]
TS 24.610: "Communication HOLD (HOLD) using IP Multimedia (IM) Core Network (CN) subsystem".
[37]
TS 24.615: "Communication Waiting (CW) using IP Multimedia (IM) Core Network (CN) subsystem".
[38]
TS 24.628: "Common Basic Communication procedures using IP Multimedia (IM) Core Network (CN) subsystem".
[39]
RFC 6086: "Session Initiation Protocol (SIP) INFO Method and Package Framework".
[40]
RFC 3312: "Integration of resource management and Session Initiation Protocol (SIP)".
[41]
RFC 4032: "Update to the Session Initiation Protocol (SIP) Preconditions Framework".
[42]
RFC 3313: "Private Session Initiation Protocol (SIP) Extensions for Media Authorization".
[43]
RFC 3327: "Session Initiation Protocol Extension Header Field for Registering Non-Adjacent Contacts".
[44]
RFC 3325: "Private Extensions to the Session Initiation Protocol (SIP) for Network Asserted Identity within Trusted Networks".
[45]
RFC 3608: "Session Initiation Protocol (SIP) Extension Header Field for Service Route Discovery During Registration".
[46]
RFC 3486: "Compressing the Session Initiation Protocol (SIP)".
[47]
RFC 3329: "Security Mechanism Agreement for the Session Initiation Protocol (SIP)".
[48]
RFC 3326: "The Reason Header Field for the Session Initiation Protocol (SIP)".
[49]
RFC 6432: "Carrying Q.850 Codes in Reason Header Fields in SIP (Session Initiation Protocol) Responses".
[50]
RFC 3581: "An Extension to the Session Initiation Protocol (SIP) for Symmetric Response Routing".
[51]
RFC 3841: "Caller Preferences for the Session Initiation Protocol (SIP)".
[52]
RFC 4028: "Session Timers in the Session Initiation Protocol (SIP)".
[53]
RFC 3892: "The Session Initiation Protocol (SIP) Referred-By Mechanism".
[54]
RFC 3891: "The Session Initiation Protocol (SIP) 'Replaces' Header".
[55]
RFC 3911: "The Session Initiation Protocol (SIP) 'Join' Header".
[56]
RFC 3840: "Indicating User Agent Capabilities in the Session Initiation Protocol (SIP)".
[57]
RFC 5079: "Rejecting Anonymous Requests in the Session Initiation Protocol (SIP)".
[58]
RFC 4458: "Session Initiation Protocol (SIP) URIs for Applications such as Voicemail and Interactive Voice Response (IVR)".
[59]
RFC 4320: "Actions Addressing Identified Issues with the Session Initiation Protocol's (SIP) Non-INVITE Transaction".
[60]
RFC 4457: "The Session Initiation Protocol (SIP) P-User-Database Private-Header (P-header)".
[61]
RFC 5031: "A Uniform Resource Name (URN) for Emergency and Other Well-Known Services".
[62]
RFC 5627: "Obtaining and Using Globally Routable User Agent (UA) URIs (GRUU) in the Session Initiation Protocol (SIP)".
[63] Void.
[64]
RFC 5002: "The Session Initiation Protocol (SIP) P-Profile-Key Private Header (P-Header)".
[65]
RFC 5626: "Managing Client-Initiated Connections in the Session Initiation Protocol (SIP)".
[66]
RFC 5768: "Indicating Support for Interactive Connectivity Establishment (ICE) in the Session Initiation Protocol (SIP)".
[67]
RFC 5365: "Multiple-Recipient MESSAGE Requests in the Session Initiation Protocol (SIP)".
[68]
RFC 6442: "Location Conveyance for the Session Initiation Protocol".
[69]
RFC 5368: "Referring to Multiple Resources in the Session Initiation Protocol (SIP)".
[70]
RFC 5366: "Conference Establishment Using Request-Contained Lists in the Session Initiation Protocol (SIP)".
[71]
RFC 5367: "Subscriptions to Request-Contained Resource Lists in the Session Initiation Protocol (SIP)".
[72]
RFC 4967: "Dial String Parameter for the Session Initiation Protocol Uniform Resource Identifier".
[73]
RFC 4964: "The P-Answer-State Header Extension to the Session Initiation Protocol for the Open Mobile Alliance Push to Talk over Cellular".
[74]
RFC 5009: "Private Header (P-Header) Extension to the Session Initiation Protocol (SIP) for Authorization of Early Media".
[75]
RFC 4694: "Number Portability Parameters for the 'tel' URI".
[76] Void.
[77]
RFC 4411: "Extending the Session Initiation Protocol (SIP) Reason Header for Preemption Events".
[78]
RFC 4412: "Communications Resource Priority for the Session Initiation Protocol (SIP)".
[79]
RFC 5393: "Addressing an Amplification Vulnerability in Session Initiation Protocol (SIP) Forking Proxies".
[80]
RFC 5049: "Applying Signaling Compression (SigComp) to the Session Initiation Protocol (SIP)".
[81]
RFC 5688: "A Session Initiation Protocol (SIP) Media Feature Tag for MIME Application Sub-Types".
[82]
RFC 5360: "A Framework for Consent-Based Communications in the Session Initiation Protocol (SIP)".
[83]
RFC 7433: "A Mechanism for Transporting User-to-User Call Control Information in SIP".
[83A]
RFC 7434: "Interworking ISDN Call Control User Information with SIP".
[84]
RFC 7316: "The Session Initiation Protocol (SIP) P-Private-Network-Indication Private Header (P-Header)".
[85]
RFC 5502: "The SIP P-Served-User Private-Header (P-Header) for the 3GPP IP Multimedia (IM) Core Network (CN) Subsystem".
[86] Void.
[87]
RFC 8497: "Marking SIP Messages to Be Logged".
[88]
RFC 6228: "Response Code for Indication of Terminated Dialog".
[89]
RFC 5621: "Message Body Handling in the Session Initiation Protocol (SIP)".
[90]
RFC 6223: "Indication of support for keep-alive".
[91]
RFC 5552: "SIP Interface to VoiceXML Media Services".
[92]
RFC 3862: "Common Presence and Instant Messaging (CPIM): Message Format".
[93]
RFC 5438: "Instant Message Disposition Notification".
[94]
RFC 5373: "Requesting Answering Modes for the Session Initiation Protocol (SIP)".
[95] Void.
[96]
RFC 3959: "The Early Session Disposition Type for the Session Initiation Protocol (SIP)".
[97] Void.
[98]
TS 24.183: "Customized Ringing Signal (CRS) using IP Multimedia (IM) Core Network (CN) subsystem".
[99]
TS 24.259: "Personal Network Management (PNM) using IP Multimedia (IM) Core Network (CN) subsystem".
[100]
TS 24.238: "Session Initiation Protocol (SIP) based user configuration".
[101]
TS 24.239: "Flexible Alerting (FA) using IP Multimedia (IM) Core Network (CN) subsystem".
[102] Void.
[103]
TS 24.654: "Closed User Group (CUG) using IP Multimedia (IM) Core Network (CN) subsystem".
[104] Void.
[105]
TS 24.605: "Conference (CONF) using IP Multimedia (IM) Core Network (CN) subsystem".
[106]
TS 24.147: "Conferencing using the IP Multimedia (IM) Core Network (CN) subsystem".
[107] Void.
[108] Void.
[109]
TS 24.642: "Completion of Communications to Busy Subscriber (CCBS) Completion of Communications by No Reply (CCNR) using IP Multimedia (IM) Core Network (CN) subsystem".
[110] Void.
[111] Void.
[112]
TS 24.606: "Message Waiting Indication (MWI) using IP Multimedia (IM) Core Network (CN) subsystem".
[113]
TS 24.608: "Terminating Identification Presentation (TIP) and Terminating Identification Restriction (TIR) using IP Multimedia (IM); Core Network (CN) subsystem".
[114]
TS 24.611: "Communication Barring (CB) using IP Multimedia (IM); Core Network (CN) subsystem".
[115] Void.
[116]
TS 24.629: "Explicit Communication Transfer (ECT) using IP Multimedia (IM) Core Network (CN) subsystem".
[117]
TS 24.604: "Communication DIVersion (CDIV) using IP Multimedia (IM) Core Network (CN) subsystem".
[118] Void.
[119] Void.
[120]
TS 23.292: "IP Multimedia Subsystem (IMS) Centralized Services; Stage 2".
[121]
TS 24.292: "IP Multimedia Core Network subsystem Centralized Services (ICS); Stage 3".
[122]
TS 24.647: "Advice Of Charge (AOC) using IP Multimedia (IM) Core Network (CN) subsystem".
[123] Void.
[124]
RFC 7989: "End-to-End Session Identification in IP-Based Multimedia Communication Networks".
[125]
RFC 6026: "Correct Transaction Handling for 2xx Responses to Session Initiation Protocol (SIP) INVITE Requests".
[126]
RFC 5658: "Addressing Record-Route issues in the Session Initiation Protocol (SIP)".
[127]
RFC 5954: "Essential correction for IPv6 ABNF and URI comparison in RFC3261".
[128] Void.
[129]
TS 24.182: "IP Multimedia Subsystem (IMS) Customized Alerting Tones (CAT)".
[130]
TS 29.292: "Interworking between the IP Multimedia (IM) Core Network (CN) subsystem and MSC Server for IMS Centralized Services (ICS)".
[131]
TS 24.237: "IP Multimedia (IM) Core Network (CN) subsystem; IP Multimedia Subsystem (IMS) Service Continuity".
[132]
TS 24.141: "Presence service using the IP Multimedia (IM) Core Network (CN) subsystem".
[133]
RFC 6794: "A Framework for Session Initiation Protocol (SIP) Session Policies".
[134]
RFC 5875: "An Extensible Markup Language (XML) Configuration Access Protocol (XCAP) Diff Event Package".
[135]
RFC 4488: "Suppression of Session Initiation Protocol (SIP) REFER Method Implicit Subscription".
[136]
RFC 7462: "URNs for the Alert-Info Header Field of the Session Initiation Protocol (SIP)".
[137] Void.
[138]
OMA-TS-Presence_SIMPLE-V2_0-20120710-A: "Presence SIMPLE Specification".
[139]
TS 24.247: "Messaging service using the IP Multimedia (IM) Core Network (CN) subsystem".
[140]
RFC 4538: "Request Authorization through Dialog Identification in the Session Initiation Protocol (SIP)".
[141]
RFC 5318: "The Session Initiation Protocol (SIP) P-Refused-URI-List Private-Header (P-Header)".
[142]
OMA-TS-Presence_SIMPLE-V1_1_1-20100225-A: "Presence SIMPLE Specification".
[143]
RFC 6809: "Mechanism to Indicate Support of Features and Capabilities in the Session Initiation Protocol (SIP)".
[144]
RFC 5839: "An Extension to Session Initiation Protocol (SIP) Events for Conditional Event Notification".
[145] Void.
[146]
RFC 3264: "An Offer/Answer Model with the Session Description Protocol (SDP)".
[147]
RFC 4566: "SDP: Session Description Protocol".
[148]
TS 29.079: "Optimal Media Routeing within the IP Multimedia Subsystem; Stage 3".
[149]
TS 24.337: "IP Multimedia Subsystem (IMS) inter-UE transfer".
[150]
RFC 3960: "Early Media and Ringing Tone Generation in the Session Initiation Protocol (SIP)".
[151]
RFC 3550: "RTP: A Transport Protocol for Real-Time Applications".
[152]
RFC 768: "User Datagram Protocol".
[153]
RFC 3551: "RTP Profile for Audio and Video Conferences with Minimal Control".
[154]
RFC 3556: "Session Description Protocol (SDP) Bandwidth Modifiers for RTP Control Protocol (RTCP) Bandwidth".
[155]
RFC 4585: "Extended RTP Profile for Real-time Transport Control Protocol (RTCP)-Based Feedback (RTP/AVPF)".
[156]
RFC 793: "Transmission Control Protocol".
[157]
RFC 4733: "RTP Payload for DTMF Digits, Telephony Tones, and Telephony Signals".
[158]
RFC 4916: "Connected Identity in the Session Initiation Protocol (SIP)".
[159]
TS 23.237: "IP Multimedia Subsystem (IMS) Service Continuity".
[160]
RFC 6140: "Registration for Multiple Phone Numbers in the Session Initiation Protocol (SIP)".
[161]
RFC 6230: "Media Control Channel Framework".
[162]
RFC 4145: "TCP-Based Media Transport in the Session Description Protocol (SDP)".
[163]
TS 24.390: "Unstructured Supplementary Service Data (USSD)".
[164]
RFC 6357: "Design Considerations for Session Initiation Protocol (SIP) Overload Control".
[165]
RFC 7339: "Session Initiation Protocol (SIP) Overload Control".
[166]
RFC 7415: "Session Initiation Protocol (SIP) Rate Control".
[167]
RFC 7200: "A Session Initiation Protocol (SIP) Load-Control Event Package".
[168]
TS 29.163: "Interworking between the IP Multimedia (IM) Core Network (CN) subsystem and Circuit Switched (CS) networks".
[169]
RFC 2046: "Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types".
[170]
RFC 2387: "The MIME Multipart/Related Content-type".
[171]
RFC 3420: "Internet Media Type message/sipfrag".
[172]
RFC 3842: "A Message Summary and Message Waiting Indication Event Package for the Session Initiation Protocol (SIP)".
[173]
RFC 3858: "An Extensible Markup Language (XML) Based Format for Watcher Information".
[174]
RFC 3863: "Presence Information Data Format (PIDF)".
[175]
RFC 3994: "Indication of Message Composition for Instant Messaging".
[176]
RFC 4661: "An Extensible Markup Language (XML) Based Format for Event Notification Filtering".
[177]
RFC 4662: "A Session Initiation Protocol (SIP) Event Notification Extension for Resource Lists".
[178]
RFC 4826: "Extensible Markup Language (XML) Formats for Representing Resource Lists".
[179]
RFC 5262: "Presence Information Data Format (PIDF) Extension for Partial Presence".
[180]
RFC 5874: "An Extensible Markup Language (XML) Document Format for Indicating a Change in XML Configuration Access Protocol (XCAP) Resources".
[181] Void.
[182]
OMA-SUP-XSD_prs_suppnotFilter-V1_0-20120710-A: "Presence - Event notification suppression filter".
[183]
TS 32.240: "Telecommunication management; Charging management; Charging architecture and principles".
[184]
RFC 7090: "Public Safety Answering Point (PSAP) Callback".
[185]
RFC 8055: "Session Initiation Protocol (SIP) Via Header Field Parameter to Indicate Received Realm".
[186]
TS 29.658: "SIP Transfer of IP Multimedia Service Tariff Information".
[187]
TS 22.153: "Multimedia priority service".
[188]
RFC 7549: "3GPP SIP URI Inter Operator Traffic Leg parameter".
[189]
TS 24.103: "Telepresence using the IP Multimedia (IM) Core Network (CN) Subsystem (IMS); Stage 3".
[190]
RFC 8841: "Session Description Protocol (SDP) Offer/Answer Procedures for Stream Control Transmission Protocol (SCTP) over Datagram Transport Layer Security (DTLS) Transport".
[191]
TS 24.315: "IP Multimedia Subsystem (IMS) Operator Determined Barring (ODB)".
[192]
TR 29.949: "Study on Technical aspects on Roaming End-to-end scenarios with VoLTE IMS and other networks".
[193]
RFC 8119: "SIP "cause" URI Parameter for Service Number Translation".
[194]
RFC 7647: "Clarifications for the Use of REFER with RFC6665".
[195]
RFC 7614: "Explicit Subscriptions for the REFER Method".
[196]
RFC 7621: "A Clarification on the Use of Globally Routable User Agent URIs (GRUUs) in the Session Initiation Protocol SIP Event Notification Framework".
[197]
RFC 2646: "The Text/Plain Format Parameter".
[198]
RFC 1866: "Hypertext Markup Language - 2.0".
[199]
TS 22.179: "Mission Critical Push To Talk (MCPTT); Stage 1".
[200]
TS 23.280: "Common functional architecture to support mission critical services; Stage 2".
[201]
TS 24.379: "Mission Critical Push To Talk (MCPTT) call control Protocol specification".
[202]
TS 24.380: "Mission Critical Push To Talk (MCPTT) floor control Protocol specification".
[203]
RFC 8498: "A P-Served-User Header Field Parameter for an Originating Call Diversion (CDIV) Session Case in the Session Initiation Protocol (SIP)".
[204]
RFC 4575: "A Session Initiation Protocol (SIP) Event Package for Conference State".
[205]
RFC 4354: "A Session Initiation Protocol (SIP) Event Package and Data Format for Various Settings in Support for the Push-to-Talk over Cellular (PoC) Service".
[206]
RFC 8224: "Authenticated Identity Management in the Session Initiation Protocol (SIP)".
[207]
RFC 8197: "A SIP Response Code for Unwanted Calls".
[208]
RFC 6910: "Completion of Calls for the Session Initiation Protocol (SIP)".
[209]
TS 22.280: "Mission Critical Services Common Requirements".
[210]
TS 24.281: "Mission Critical Video (MCVideo) signalling control; Protocol specification".
[211]
TS 24.282: "Mission Critical Data (MCData) signalling control; Protocol specification".
[212]
TS 24.581: "Mission Critical Video (MCVideo) media plane control; Protocol specification".
[213]
TS 24.582: "Mission Critical Data (MCData) media plane control; Protocol specification".
[214]
RFC 8606: "ISDN User Part (ISUP) Cause Location Parameter for the SIP Reason Header Field".
[215]
TS 23.167: "IP Multimedia Subsystem (IMS) emergency sessions".
[216]
RFC 8262: "Content-ID Header Field in the Session Initiation Protocol (SIP)".
[217]
TS 24.196: "Technical Specification Group Core Network and Terminals; Enhanced Calling Name".
[218]
TS 24.174: "Support of Multi-Device and Multi-Identity in IMS; Stage 3".
[219]
TS 23.218: "IP Multimedia (IM) Session Handling; IM call model".
[220]
RFC 9410: "Handling of Identity Header Errors for Secure Telephone Identity Revisited (STIR)".
[221]
RFC 9366: "Multiple SIP Reason Header Field Values".
[222]
TS 24.186: "IMS Data Channel applications; Protocol specification".
3 Definitions, symbols and abbreviations p. 17
3.1 Definitions p. 17
For the purposes of the present document, the terms and definitions given in TR 21.905 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.
IM CN subsystem:
(IP Multimedia CN subsystem) comprises of all CN elements for the provision of IP multimedia applications over IP multimedia sessions, as specified in TS 22.228.
IP multimedia session:
as specified in TS 22.228 an IP multimedia session is a 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 can invoke concurrent IP multimedia sessions.
non-roaming II-NNI:
the II-NNI between IMS home networks, or, if the Roaming Architecture for Voice over IMS with Local Breakout is used, alternatively the II-NNI between the caller's visited network and the callee's home network.
roaming II-NNI:
the II-NNI between a visited IMS network and the IMS home network; for the Roaming Architecture for Voice over IMS with Local Breakout, the loopback traversal scenario is excluded.
loopback traversal scenario:
for the Roaming Architecture for Voice over IMS with Local Breakout, the scenario where the II-NNI between the caller's home network and the caller's visited network is being traversed by an initial INVITE request from the caller's home network to the caller's visited network or any subsequent SIP message within the same dialogue on the same call leg.
home-to-visited request on roaming II-NNI:
SIP request being sent from the callee's home network to the callee's visited network.
home routeing:
the scenario when the caller's home network routes a dialog creating SIP request directly to the callee's home network without using the loopback traversal scenario.
visited-to-home request on roaming II-NNI:
SIP request being sent from the caller's visited network to the caller's home network.
home-to-visited response on roaming II-NNI:
SIP response being sent from the caller's home network to the caller's visited network.
visited-to-home response on roaming II-NNI:
SIP response being sent from the callee's visited network to the callee's home network.
For the purposes of the present document, the following terms and definitions given in TS 23.228 apply:
Bootstrap data channel
For the purposes of the present document, the following terms and definitions given in TS 23.292 apply:
MSC Server enhanced for ICS
For the purposes of the present document, the following terms and definitions given in TS 23.237 apply:
MSC server enhanced for SRVCC
For the purposes of the present document, the following terms and definitions given in TS 24.237 apply:
MSC server enhanced for dual radio
For the purposes of the present document, the following term and definition given in TS 23.218 apply:
Standalone transaction
3.2 Symbols p. 18
For the purposes of the present document, the following symbols apply:
I2
Reference point between the MSC Server enhanced for ICS and the home IMS
Ici
Reference Point between an IBCF and another IBCF belonging to a different IM CN subsystem network
Ix
Reference Point between an IBCF and TrGW
Izi
Reference Point between a TrGW and another TrGW or media handling node belonging to a different IM CN subsystem network
Mi
Reference Point between a BGCF and CSCF
Mm
Reference Point between a CSCF/BGCF/IMS ALG and an IP multimedia network
Mw
Reference Point between a CSCF and another CSCF
Mx
Reference Point between a CSCF/BGCF/MSC Server enhanced for ICS/ MSC Server enhanced for SRVCC / MSC server enhanced for dual radio and IBCF
3.3 Abbreviations p. 19
For the purposes of the present document, the abbreviations given in TR 21.905 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.
18x
A SIP status-code in the range 180 through 189
2xx
A SIP status-code in the range 200 through 299
3PTY
Three-Party
3xx
A SIP status-code in the range 300 through 399
4xx
A SIP status-code in the range 400 through 499
5GS
5G System
5xx
A SIP status-code in the range 500 through 599
6xx
A SIP status-code in the range 600 through 699
ACR
Anonymous Communication Rejection
AOC
Advice Of Charge
AS
Application Server
ATCF
Access Transfer Control Function
B2BUA
Back 2 Back User Agent
BGCF
Breakout Gateway Control Function
CAT
Customized Alerting Tone
CB
Communication Barring
CCBS
Completion of Communications to Busy Subscriber
CCNL
Completion of Communications on Not Logged-in
CCNR
Communication Completion on No Reply
CDIV
Communication Diversion
CONF
Conference
CRS
Customized Ringing Signal
CSCF
Call Session Control Function
CW
Communication Waiting
DRVCC
Dual Radio Voice Call Continuity
eCNAM
Enhanced Calling Name
E-CSCF
Emergency CSCF
ECT
Explicit Communication Transfer
FA
Flexible Alerting
GRUU
Globally Routable User agent URIs
HOLD
Communication HOLD
IBCF
Interconnection Border Control Function
ICB
Incoming Communication Barring
ICID
IMS Charging Identifier
ICS
IMS Centralized Services
I-CSCF
Interrogating CSCF
II-NNI
Inter-IMS Network to Network Interface
IM
Instant Messaging
IMS-ALG
IMS Application Level Gateway
IOI
Inter Operator Identifier
IUT
Inter UE Transfer
MBMS
Multimedia Broadcast Multicast Service
MCData
Mission Critical Data
MCID
Malicious Communication IDentification
MCPTT
Mission Critical Push-To-Talk
MCVideo
Mission Critical Video
MiD
Multi-iDentity
MMTEL
Multimedia Telephony
MPS
Multimedia Priority Service
MRB
Media Resource Broker
MRFC
Media Resource Function Controller
MRFP
Multimedia Resource Function Processor
MSD
Minimum Set of Data
MSRP
Message Session Relay Protocol
MTSI
Multimedia Telephony Service for IMS
MuD
Multi-Device
MWI
Message Waiting Indication
NA(P)T-PT
Network Address (Port-Multiplexing) Translation-Protocol Translation
NNI
Network to Network Interface
OCB
Outgoing Communication Barring
OIP
Originating Identification Presentation
OIR
Originating Identification Restriction
OMA
Open Mobile Alliance
OMR
Optimal Media Routeing
P-CSCF
Proxy CSCF
PCF
Policy Control Function
PCRF
Policy and Charging Rules Function
PNM
Personal Network Management
PRES
Presence
PSAP
Public Safety Answering Point
PSI
Public Service Identity
RLOS
Restricted Local Operator Services
RTT
Round-trip Time
S-CSCF
Serving CSCF
SRVCC
Single Radio Voice Call Continuity
STN
Session Transfer Number
TIP
Terminating Identification Presentation
TIR
Terminating Identification Restriction
TRF
Transit and Roaming Function
TrGW
Transition Gateway
UDM
Unified Data Management
vSRVCC
Single Radio Video Call Continuity
