| |
Figure 4.0 | Reference Architecture of the IP Multimedia Core Network Subsystem |
Figure 4.1 | Service Platform in Home Network |
Figure 4.2 | External Service Platform |
Figure 4.3a | Application Server acting as terminating UA, or redirect server |
Figure 4.3b | Application Server acting as originating UA |
Figure 4.3c | Application Server acting as a SIP proxy |
Figure 4.3d | Application Server performing 3rd party call control |
Figure 4.3e | A SIP leg is passed through the S-CSCF without Application Server involvement |
Figure 4.2.4b-1 | Service Control Model with Incoming Leg Control and Outgoing Leg Control |
Figure 4.3f | I-CSCF forwarding a SIP request destined to a Public Service Identity to an Application Server hosting this Public Service Identity |
Figure 4.3g | Application Server originating a session on behalf of a user or a Public Service Identity, having no knowledge of the S-CSCF to use |
Figure 4.5 | Relationship of the Private User Identity and Public User Identities |
Figure 4.6 | The relation of a shared Public User Identity (Public-ID-2) and Private User Identities |
Figure 4.6a | The relationship of Public User Identities, GRUUs and UEs |
Figure 4.7 | Architecture of MRF |
Figure 4.13-1 | IMS applications on top of an IMS communication service |
Figure 4.15.3-1 | IMS application services reference point for transit network scenarios |
Figure 5.0a | P-CSCF discovery using DHCP and DNS |
Figure 5.0b | Subscription data updating |
Figure 5.0c | Relationship of Public User Identities when implicitly registered |
Figure 5.0d | The relation of two shared Public User Identities (Public-ID-3 and 4) and Private User Identities |
Figure 5.1 | Registration - User not registered |
Figure 5.2 | Re-registration - user currently registered |
Table 5.1 | Information Storage before, during and after the registration process |
Figure 5.3 | De-registration - user currently registered |
Figure 5.4 | Network initiated application de-registration, registration timeout |
Figure 5.5 | Network initiated application de-registration by HSS, administrative |
Figure 5.5a | Network initiated application de-registration, service platform |
Figure 5.5b | Example tunnelling of IPv6 traffic over IPv4 networks |
Figure 5.6 | Network based PSTN interworking breakout process |
Figure 5.7 | Bearer establishment showing optional pre-alerting |
Figure 5.8 | Providing service event related information to related endpoint |
Figure 5.8a | Subscription to event in AS |
Figure 5.9 | Overview of Session Flow Sections |
Table 5.2 | Combinations of session procedures |
Figure 5.9a | Overview of Session Flow Sections for transit scenarios |
Table 5.2a | Combinations of IMS transit network procedures |
Figure 5.10 | Serving to serving procedure - different operators |
Figure 5.11 | Serving to serving procedure - same operator |
Figure 5.12 | Serving to PSTN procedure - same operator |
Figure 5.13 | Serving to PSTN procedure - different operator |
Figure 5.14 | Mobile origination procedure - roaming |
Figure 5.15 | Mobile origination procedure - home |
Figure 5.16 | PSTN origination procedure |
Figure 5.16a | Originating session from external SIP client |
Figure 5.16b | Application Server origination procedure |
Figure 5.16c | S-CSCF selection by I-CSCF for AS Originating call procedure |
Figure 5.17 | Mobile termination procedure - roaming |
Figure 5.18 | Mobile termination procedure - home |
Figure 5.18a | Mobile Terminating procedures to a user that is unregistered for IMS services but is registered for CS services |
Figure 5.19 | PSTN termination procedure |
Figure 5.19b | Terminating session towards external SIP client, initiate session set up not requiring precondition capabilities and with inactive media |
Figure 5.19c | Continuation of terminating session towards external SIP client, session set up with active media |
Figure 5.19d | Incoming session, direct route towards the AS |
Figure 5.19e | Incoming session, indirect route to AS via S-CSCF |
Figure 5.19f | Incoming session, direct route to AS using DNS |
Figure 5.19g | Application Server termination |
Figure 5.19h | End-to-end session flow procedure without preconditions - no resource reservation required before session becomes active |
Figure 5.20 | SLF on register (1st case) |
Figure 5.20a | SLF on register (2nd case) |
Figure 5.21 | SLF on UE invite |
Figure 5.21a | SLF on AS access to HSS |
Figure 5.22 | Terminal initiated session release |
Figure 5.23 | PSTN initiated session release |
Figure 5.26 | Network initiated session release - P-CSCF initiated - after removal of IP-CAN bearer |
Figure 5.27 | Network initiated session release - S-CSCF initiated |
Figure 5.28 | Mobile to Mobile session hold and resume |
Figure 5.29 | Mobile-initiated Hold and Resume of a Mobile-PSTN Session |
Figure 5.29a | PSTN-initiated Hold and Resume of a Mobile-PSTN Session |
Figure 5.30 | Codec negotiation during initial session establishment |
Figure 5.31 | Codec or media flow change - same reservation |
Figure 5.32 | Codec or media flow change - new reservation |
Figure 5.33 | Multimedia session flow - addition of another media |
Figure 5.34 | Providing the authenticated Identity of the originating party |
Figure 5.35 | Blocking the identity of the originating party |
Figure 5.36 | Session redirection initiated by S-CSCF to IMS |
Figure 5.37 | Session redirection to PSTN Termination (S-CSCF #2 forwards INVITE) |
Figure 5.37a | Session redirection to PSTN Termination (REDIRECT to originating UE#1) |
Figure 5.38 | Session redirection initiated by S-CSCF to general endpoint |
Figure 5.39 | Session redirection initiated by P-CSCF |
Figure 5.40 | Session redirection initiated by UE |
Figure 5.41 | Session redirection after bearer establishment |
Figure 5.42 | Refer operation |
Figure 5.11.6.2.1-1 | |
Figure 5.11.6.2.2-1 | |
Figure 5.11.6.2.3-1 | |
Figure 5.43 | Mobile Terminating call procedures to unregistered IMS Public User Identity that has services related to unregistered state |
Figure 5.44 | Mobile Terminating call procedures to unregistered Public User Identity that has no services related to unregistered state |
Figure 5.45 | HSS determination of unknown user |
Figure 5.46 | SLF determination of unknown user |
Figure 5.47 | Immediate Messaging procedure to registered Public User Identity |
Figure 5.48 | Immediate messaging to unregistered Public User Identity, service control invoked |
Figure 5.48a | Message session establishment |
Figure 5.48b | Session based messaging using a chat server |
Figure 5.48c | Session based messaging with an intermediate node |
Figure 5.48d | Message session release procedure |
Figure 5.48e | Message session release procedure with intermediate node |
Figure 5.49 | IMS transit network |
Figure 5.50 | Terminating IMS network with transit support, Transit Functions first |
Figure 5.50a | Terminating/Transit IMS network, Transit Functions first |
Figure 5.50b | Terminating/Transit IMS network, I-CSCF first |
Figure 5.50c | IMS application services in transit network |
Figure 5.22.1-1 | Information flow for Overload Control with next-hop monitoring |
Figure 5.22.2-1 | Information flow for AS Overload Control using a filter based mechanism |
Figure A.1 | Information Flow Template |
Figure E.1 | P-CSCF discovery using PDP Context Activation signalling |
Figure E.2 | P-CSCF discovery using EPS bearer activation signalling |
Figure E.3 | Network initiated session release - P-CSCF initiated after loss of radio coverage |
Figure G.1 | Reference model for IMS access when both the signalling and media traverses NAT |
Figure G.2 | Reference model for IMS access when NAT is needed between the IP-CAN and the IMS domain |
Figure G.2a | Reference model for ICE and Outbound Methodology |
Figure G.3 | Session establishment procedure with NAT traversal |
Figure G.4 | Session release procedure with NAT traversal |
Figure G.5 | Packet forwarding in the IMS Access Gateway |
Figure G.7 | Flow Establishment Procedures for Outbound |
Figure G.8 | Session Establishment procedure for NAT Traversal using ICE and Outbound |
Figure G.9 | Session Release Procedure with STUN Relay Resources |
Figure H.1 | HSS functional decomposition |
Figure I.1 | Border Control Functions |
Figure I.2 | Originating IMS session towards an IPv4 end point |
Figure I.3 | Terminating IPv4 SIP session towards an IPv6 IMS user |
Figure I.4 | Proactive transcoding invocation |
Figure I.5 | Reactive transcoding invocation |
Figure J.2.1 | Dynamic User Allocation using Representative AS |
Figure J.2.2 | Bypassing Representative AS procedure |
Figure J.3.2.1 | Assignment of AS via DNS query during first service request |
Figure J.3.2.2 | S-CSCF has stored assigned AS for following service requests |
Figure K.1 | Inter-IMS Network to Network Interface between two IM CN subsystem networks |
Figure L.1 | HSS in 3GPP2 |
Figure M.1.1.1 | EPS/5GS architecture for IMS Local Breakout with P-CSCF located in visited network |
Figure M.1.1.2 | Example scenario with P-CSCF located in visited network and IBCF and TrGW in home network |
Figure M.2.1.1-1 | EPS/5GS architecture for IMS Local breakout with P-CSCF located in home network |
Figure M.2.1.2 | Example scenario with P-CSCF located in home network |
Figure M.3.1.2 | Overall architecture for IMS Local Breakout with P-CSCF located in visited network and with VPLMN loopback possibility |
Figure M.3.1.3 | Example scenario with P-CSCF located in visited network and with VPLMN routing |
Figure M.3.1.4 | Example scenario with P-CSCF located in visited network and with home routing |
Figure N.1.1 | Fixed xDSL originating - home (example flow) |
Figure N.2.1 | Fixed xDSL terminating - home (example flow) |
Figure P.1.3.2-1 | Proactive transcoding triggering logic |
Figure P.1.3.3-1 | Reactive transcoding triggering logic |
Figure Q.1 | IMS-ALG bypasses its TrGW and one or more prior TrGWs |
Figure Q.2 | IMS-ALG bypasses its TrGW using secondary realm from prior IMS-ALG |
Figure Q.3 | IMS-ALG bypasses one or more prior TrGWs using a secondary realm |
Figure Q.4 | IMS-ALG bypasses TrGWs performing NAT traversal |
Figure Q.5 | Proactive transcoding where transcoding not required |
Figure Q.6 | IMS-ALG bypasses prior unrequired proactive transcoder |
Figure Q.7 | IMS-ALG bypasses its TrGW and prior unrequired proactive transcoder |
Figure Q.8 | IMS-ALG replaces prior proactive transcoder |
Figure R.2-1 | Mobile origination (user location and/or UE Time Zone information included within INVITE) |
Figure R.3-1 | Mobile origination (user location and/or UE Time Zone information included within Response Confirmation) |
Figure R.4-1 | Mobile termination |
Figure R.5-1 | User location and/or UE Time Zone information Distribution by an IMS AS |
Figure R.6-1 | IMS Session Release |
Figure S.2-1 | High level Static mode business trunking Architecture |
Figure S.2.2.2-1 | Originating procedures for IP-PBXs using static mode business trunking and served by the S-CSCF. |
Figure S.2-2 | Originating procedures for IP-PBXs using static mode business trunking and served by the Transit Function |
Figure S.2-3 | Terminating procedures for IP-PBXs using static mode business trunking and served by the S-CSCF |
Figure S.2-4 | Terminating procedures for IP-PBXs using static mode business trunking and served by the Transit Function |
Figure U.1.2-1 | WebRTC IMS architecture and reference model |
Figure U.1.5.1-1 | Protocol architecture for MSRP |
Figure U.1.5.1-2 | Protocol architecture for MSRP acting as transport relay function |
Figure U.1.5.2-1 | Protocol architecture for BFCP |
Figure U.1.5.3-1 | Protocol architecture for T.140 |
Figure U.1.5.4-1 | Protocol architecture for Voice and Video |
Figure U.2.1.2-1 | WIC registration of individual Public User Identity using IMS authentication |
Figure U.2.1.3-1 | WIC registration of individual Public User Identity based on web authentication |
Figure U.2.4-1 | Media plane Optimization |
Figure W.2-1 | IMS traffic home routed |
Figure W.4.1-1 | Subscription by P-CSCF to changes in PLMN ID during initial IMS Registration |
Figure W.4.2-1 | Procedure for PLMN change |
Figure W.4.3-1 | PLMN change detected by EPC/5GC |
Figure Y.0-1 | UDM and HSS collocated or HSS as part of UDM |
Figure Y.3 | Network initiated session release - P-CSCF initiated after loss of radio coverage |
Figure Y.9.2-1 | IMS traffic home routed |
Figure Y.9.4-1 | Subscription by P-CSCF to changes in PLMN ID during initial IMS Registration |
Figure Z.3.1-1 | RLOS IMS Registration procedures for roaming users without roaming agreements with their home network |
Figure Z.3.2.1-1 | Unsuccessful RLOS IMS Registration procedure |
Figure AA.1.1-1 | System Architecture to support SBA in IMS |
Figure AA.1.1-2 | System Architecture to support SBA in IMS in reference point representation |
Table AA.2.1.1-1 | IMS Services provided by an SBI capable HSS |
Table AA.2.1.3.1-1 | IMS Subscriber data types |
Table AA.2.1.3.1-2 | IMS Subscriber data types keys |
Table AA.2.2.2-1 | Cx messages to HSS SBI services and service operations mapping |
Table AA.2.2.3-1 | Sh messages to HSS SBI services and service operations mapping |
Table AA.2.4.1-1 | NF services provided by the IMS AS |
Table AA.2.4.2.2-1 | List of events and Related Optional parameters |
Table AA.2.4.4.5-1 | List of events and related optional parameters |
Table AA.2.5.1-1 | NF services provided by the MF |
Figure AA.2.5.2.1-1 | Media Context Resource Example |
Figure AA.3.3.2-1 | HSS discovery and selection |
Figure AB.1.2.1-1 | Potential deployment architecture for IMS services in SNPN provided by independent IMS provider |
Figure AC.2.1-1 | Architecture option of IMS supporting DC usage with MF |
Figure AC.6-1 | MF "HTTP Proxy" Media Configurations |
Figure AC.6-2 | MF "UDP Proxy" Media Configurations |
Figure AC.7.1-1 | Bootstrap Data Channel set up Signalling Procedure |
Figure AC.7.2.1-1 | Person-to-Person Application Data Channel set up Signalling Procedure |
Figure AC.7.2.2-1 | Person-to-Application (P2A) Application Data Channel set up Signalling Procedure |
Figure AC.7.2.3-1 | Symmetric Application Data Channel Establishment |
Figure AC.7.9.1-1 | Bootstrap Data Channel set up Signalling Procedure for IMS data channel interworking with MTSI UE |
Figure AC.7.9.2-1 | Application Data Channel set up signalling procedure for IMS data channel interworking with MTSI UE via MF |
Figure AC.7.9.3-1 | Application Data Channel set up signalling procedure for IMS data channel interworking with MTSI UE via DC application server |
Figure AC.7.9.4-1 | Application Data Channel set up signalling procedure for IMS data channel interworking with originating MTSI UE via DC application server |
Figure AC.7.10.4.1.1-1 | Multiplexing bootstrap data channels in originating network |
Figure AC.7.10.4.1.2-1 | Multiplexing bootstrap data channels in terminating network |
Figure AC.7.10.4.2.1-1 | Application data channel multiplexing when both originating and terminating networks support data channel multiplexing |
Figure AC.7.10.4.2.2-1 | Application data channel multiplexing when terminating network does not support data channel multiplexing |
Figure AC.9.2-1 | Architecture to support AR communication |
Figure AC.9.3.1-1 | Establishment of UE Centric AR communication session |
Figure AC.9.3.2-1 | Establishment of Network Centric AR communication session |
Figure AC.10.2.1-1 | Originating Standalone Bootstrap DC Setup using PSI |
Figure AC.10.2.2-1 | Originating Standalone IMS DC Session if Application not Available in Originating UE |
Figure AC.10.2.3-1 | Originating Standalone IMS DC Session if Application Available in Originating UE |
Figure AC.10.2.4-1 | Adding MMTel Media to standalone IMS data channel session |
Figure AC.10.2.5-1 | Removing all MMTel Media from IMS data channel session |
Figure AC.11.2-1 | Architecture to support Avatar communication |
Figure AC.11.3.1-1 | Procedures of Avatar ID List Download through Bootstrap Data Channel |
Figure AC.11.3.2.1-1 | Procedures of Sending UE centric IMS Avatar communication |
Figure AC.11.3.2.2-1 | Procedures of Receiving UE centric IMS Avatar communication |
Figure AC.11.3.3-1 | Procedures of network centric IMS Avatar communication |
Figure AD.2.1-1 | Subscribe/Notify Framework for event monitoring in IMS |
Table AD.2.5.3-1 | List of events for monitoring capability |
Figure AD.3.1-1 | IMS AS Instance Registration in HSS |
Figure AD.3.2-1 | SUBSCRIBE/NOTIFY Procedure for Subscriber specific IMS events |
Figure AD.3.3-1 | SUBSCRIBE/NOTIFY Procedure for non-subscriber specific IMS events |
Figure AE.2.1.1-1 | Reference architecture of IMS satellite media plane optimization |
Figure AE.5.1-1 | Session establishment procedure with activation of optimized media routing |
Figure AF.2.1-1 | System architecture to support authorization, signing and verification of third party user identity information in IMS |
Table AF.2.2.1-1 | RCD properties |
Figure AF.3-1 | Procedure for signing and verification of third party user identity information in IMS |
Figure AF.4-1 | IMS user specific properties provisioning procedure |
Figure AG.2.1-1 | Procedure of adding data channel(s) to an existing IMS session |
Figure AG.2.2-1 | Establishment procedure of a standalone data channel session |
Figure AG.2.3-1 | Terminating of a standalone data channel session |