Voice over Long Term Evolution (VoLTE) and the IMS

Voice over Long Term Evolution (VoLTE) and the IMSVOLTEA3Alta3A3-VOLTE11. IMS Architecture & SIP Proxies <ul> <li>Standards Bodies <ul> <li>Understanding the 3GPP</li><li>3rd Generation Partnership Project</li><li>The Network Operators Strike Back: ETSI TISPAN NGN, 3GPP2, & Cablelabs</li><li>IETF & RFCs</li></ul></li><li>VoLTE Introduction <ul> <li>VoLTE + IMS Advantages</li><li>Legacy vs. IMS</li><li>Traditional User Database Management</li><li>Why VoIP Central Control Can Not Compete with IMS</li><li>The 3GPP IMS Architecture</li><li>VoLTE and IMS Architecture Analysis</li></ul></li><li>The Building Blocks <ul> <li>The IMS Core (IP Multimedia Subsystem)</li><li>IMS Core Components</li><li>IBCF and TrGW</li><li>The HSS (Home Subscriber Server)</li><li>The SLF (Subscription Locator Function)</li><li>The EPC (Evolved Packet Core)</li><li>The E-UTRAN (Evolved UMTS Radio Access Network)</li><li>The UTRAN (UMTS Terrestrial Radio Access Network)</li><li>PCRF</li><li>PCRF and its Interfaces</li></ul></li><li>Call Control Paths <ul> <li>The SERVICE PATH = The Half Call – AS Formed by the SIP REGISTRATION</li><li>An IMS to IMS Call Analysis</li><li>Call Control and Media Paths</li><li>The IMS Half Call Concept</li><li>Application Servers (AS)</li><li>Serving Call Session Function (S-CSCF)</li></ul></li><li>Roaming and Visited <ul> <li>Visited Network vs. Home Network</li><li>Proxy Call Session Function (P-CSCF)</li><li>S5 (Local Breakout) and Registration</li><li>S8 Access and Registration</li></ul></li><li>VoLTE Access <ul> <li>Intro to Bearers & APNs</li><li>The Evolved Packet Core Component Analysis</li><li>PDCP, RLC, MAC, PHY, and the LTE Grid</li></ul></li><li>Call Flow <ul> <li>Intra Domain Service Path Originating</li><li>Intra Domain Service Path Terminating</li><li>Intra Domain Call</li><li>Intra Domain Routing</li><li>Intra Domain Routing Decision</li><li>Intra Domain Call End to End</li><li>Inter-domain Call, Intra-domain Service Paths</li><li>Inter-domain Call Routing</li><li>Cross Domain Routing Decision</li><li>IMS Border Control Function and Transition Gateway</li><li>Inter-domain Roaming</li><li>Inter-domain Call While Roaming</li><li>Both UEs Roaming Plus Inter-Domain Call</li><li>Both UEs Roaming Plus Inter-Domain Call Control Path</li></ul></li></ul>2. IMS Identifiers <ul> <li>IMS IDs <ul> <li>IMS Identifiers</li><li>UML Model of the Data Downloaded over Cx Interface</li></ul></li><li>UICC <ul> <li>UICC (Universal Integrated Circuit Card)</li></ul></li><li>IMS URI <ul> <li>IMSI – International Mobile Subscriber Identity [im-zee]</li><li>IMS Specific Numbering, Addressing and ID</li><li>Home Network Domain Name</li></ul></li></ul>3. VoLTE and IMS Architecture <ul> <li>HSS <ul> <li>The HSS (Home Subscriber Server)</li><li>The SLF (Subscription Locator Function)</li><li>CSCF (Call/Session Control Function)</li><li>P-CSCF (Proxy-Call/Session Control Function)</li><li>I-CSCF (Interrogating-Call/Session Control Function)</li><li>S-CSCF (Serving-Call/Session Control Function )</li><li>Breakout Gateway Control Function (BGCF)</li><li>AS (Application Server)</li><li>MRF - MRFC / MRFP (Media Resource Function Controller / Processor)</li><li>Policy and Charging Rules Function and the EPC</li><li>Mobility Management Entity (MME)</li><li>Serving Gateway (S-GW)</li><li>PDN Gateway (P-GW)</li></ul></li></ul>4. Bearer and APNs <ul> <li>Commonly Utilized Bearers <ul> <li>Bearer Components from the E-UTRAN through the EPC</li><li>VoLTE Bearers from the E-UTRAN through the EPC</li><li>Internet Bearers from E-UTRAN through the EPC</li></ul></li></ul>5. Power up Process <ul> <li>Overview <ul> <li>Frequency Scanning and UE Categories</li></ul></li><li>System Acquisition and RRC Connection Setup <ul> <li>Primary Synchronization Signal (PSS)</li><li>Cell-ID & Secondary Synchronization Signal (SSS)</li><li>Physical Broadcast Channel (PBCH)</li><li>Master Information Block (MIB)</li><li>Transport Downlink Shared Channel (DL-SCH) for SIB1</li><li>System Information Block type 1 (SIB1)</li><li>Downlink Shared Channel (DL-SCH) & SIB2</li><li>Uplink Synchronization</li><li>RRC CONNECTED and RRC IDLE</li><li>SIB1 – SIB12</li><li>Cell Selection</li></ul></li><li>Network Attach <ul> <li>The IMS APN Bearer Establishment</li><li>Attach Request, NAS, Authentication Process</li><li>Encryption and ESM Info</li><li>Location Request and Response</li><li>Create Session Request and Response</li><li>CCR AAA Request and Response</li><li>Create Session Response SGW to MME to eNB</li><li>Initial Context Setup and RRC Reconfiguration</li><li>UE Capability and ICR</li><li>Modify Bearer and EMM Info</li><li>Modify Bearer Response, AAA Responses and the SIP REGISTER</li><li>The Spreading Sequence</li><li>How does a UE request bandwidth in order to gain access to request bandwidth?</li></ul></li></ul>6. Handover Between eNodeBs <ul> <li>Idle Mode <ul> <li>Cell Reselection</li><li>Discontinuous Reception (DRX) with Long and Short DRX</li><li>How DRX Timers Apply the LTE Grid</li><li>Idle Mode Within and Beyond the UE</li></ul></li><li>Active UE <ul> <li>Intra-frequency Mobility (3GPP TS 23.401)</li><li>Intra MME SGW Handover Using the X2 Interface</li><li>S1-based Handover with S-GW & MME Relocation</li></ul></li></ul> 7. Tracking and Paging A UE <ul> <li>Overview <ul> <li>Tracking Area Defined</li><li>Tracking Area Identifiers</li><li>Tracking Area Lists</li><li>Relationship of MME Pool Areas, TA, and S-GW Service Areas</li></ul></li><li>Tracking and Paging a UE <ul> <li>Tracking Area Update (TAU)</li><li>Idle Mode</li><li>UE Entering Idle Mode</li><li>Paging an Idle UE</li></ul></li></ul>8. SIP Architecture <ul> <li>The Big Picture <ul> <li>Key VoLTE and IMS Protocols</li></ul></li><li>SIP Message Format <ul> <li>SIP User Agent (UA)</li><li>SIP Request and Response Format</li></ul></li><li>IMS SIP Transactions <ul> <li>SIP Requests (Methods)</li><li>SIP Response Codes</li><li>A SIP Transaction Defined</li><li>PRACK and The 100rel Process (RFC 3262)</li><li>VoLTE to VoLTE SIP Transactions</li></ul></li><li>SIP Control Path <ul> <li>Trust Chain</li><li>SIP Architecture</li><li>B2BUA Example: TAS</li><li>Mapping SIP dialogs through an Application Server</li></ul></li><li>Proxy vs. B2BUA <ul> <li>User Identities: Address-of-Records and Contact-URIs</li></ul></li><li>SIP URI <ul> <li>SIP and SIPS URI Structure Components (RFC 3261)</li></ul></li></ul>9. SIP Via Paths <ul> <li>The Via Header <ul> <li>The “Via:” Path: How A Response Finds Its Way Back</li></ul></li><li>The SIP Transaction <ul> <li>Via: Lifetime = per Transaction! (Not the Entire Duration of the Dialog)</li></ul></li><li>Impact of Via Path on the SIP Dialog <ul> <li>What Path Does the ACK Take?</li></ul></li></ul>10. SIP Route Headers <ul> <li>RR and Route <ul> <li>The Record-Route and Route Function</li></ul></li><li>Looping <ul> <li>Loop Detection</li></ul></li></ul>11. Basic SIP & IMS Specific Headers <ul> <li>Start Line</li><li>Via:</li><li>Via: branch parameter</li><li>From:</li><li>To:</li><li>Call-ID:</li><li>SIP Dialog ID</li><li>Contact:</li><li>CSeq: (Command Sequence)</li><li>Content-Type: <ul> <li>Content-Type: message/sipfrag RFC 3420</li><li>Content-Length:</li></ul></li><li>Max-Forwards:</li><li>Allow:</li><li>OPTIONS</li><li>User-Agent:</li><li>Supported:</li><li>P-Preferred-Identity: and Privacy: RFC 3325 (UA to P-CSCF)</li><li>P-Preferred-Identity: to P-Asserted-Identity:</li><li>P-Access-Network-Info: RFC 3455</li><li>Authorization: RFC 3261 Section 22.2</li><li>Path: RFC 3327</li><li>Service-Route: RFC 3608</li><li>Introduction to SigComp <ul> <li>SigComp Example</li></ul></li></ul>12. Diameter <ul> <li>Overview <ul> <li>RADIUS vs DIAMETER</li><li>Diameter Protocol</li></ul></li><li>Diameter Message Structure <ul> <li>The AVP Chain: Type – Length - Value</li><li>AVPs Encapsulated Inside an AVP</li><li>Diameter Header Structure</li><li>AVP Structure</li><li>Diameter Message Example</li><li>Diameter Message as Wireshark Would Display it</li></ul></li><li>Customization <ul> <li>Diameter Code Customization</li><li>IMS’s Diameter Cx Command Codes Values</li><li>Diameter AVPs Defined for the Cx Interface</li><li>Diameter AVPs: Rx Interface Codes</li></ul></li><li>Registration Call Flow <ul> <li>Challenge</li><li>Authorization</li><li>Registration Status</li><li>Registration Termination Request</li><li>Registration Status at the P-CSCF</li></ul></li><li>SCTP <ul> <li>Traditional Transport Layers (OSI Layer 4)</li><li>Stream Control Transmission Protocol (RFC 4960)</li><li>SCTP High Durability Connections</li><li>Setting Up An Association</li><li>The SCTP Protocol Data Unit</li><li>Head-of-Line-Blocking Avoidance</li><li>Chunking & Bundling</li></ul></li></ul>13. H.248 <ul> <li>Overview <ul> <li>H.248 Call Flow Example</li><li>H.248 Common Controller</li><li>H.248 Call Control Model</li></ul></li><li>H.248 in the IMS Core <ul> <li>H.248 Call Control Model</li></ul></li></ul>14. Initial Filter Criteria (iFC) <ul> <li>iFC Function <ul> <li>iFC Logic</li></ul></li><li>Data Structure <ul> <li>UML Model of the Data Downloaded Over Cx Interface</li></ul></li><li>iFC Logic <ul> <li>Disjunctive Normal Form</li><li>Conjunctive Normal Form</li></ul></li><li>iFC Example <ul> <li>Setting Up A TAS for Feature Enablement – (Using three.ims Domain)</li><li>Service Profile</li></ul></li></ul>15. Presence <ul> <li>The Presence Model <ul> <li>Presentity and Watcher</li><li>PUBLISH</li><li>SUBSCRIBE</li><li>NOTIFY</li></ul></li><li>IMS Call Flow <ul> <li>Cross Domain SUBSCRIBE Example</li><li>PUBLISH presentity and Cross Domain NOTIFY to Watchers</li></ul></li><li>Basic vs. Rich Presence <ul> <li>Presence Information Data Format (PIDF) RFC 3863</li><li>Rich Presence Information Data format (RPID) RFC 4480</li></ul></li><li>Message Examples <ul> <li>PUBLISH (Initial)</li><li>SUBSCRIBE (Watcher)</li><li>NOTIFY (Initial Status)</li><li>PUBLISH (Updated status)</li><li>NOTIFY (Updated status)</li></ul></li></ul>16. Session Description Protocol (SDP) <ul> <li>Overview <ul> <li>SDP Establishes ½ the Media Channel</li><li>SDP: RFC 4566</li><li>RTP is “simplex”</li><li>a=sendonly means what?</li><li>Media Direction’s Impact on RTCP</li></ul></li><li>Lines <ul> <li>Version, v=</li><li>Origin, o=</li><li>Session, s=</li><li>Connection, c=</li><li>Time, t=</li><li>Media Description, m=</li><li>Bandwidth, b=</li><li>The “a=” Attribute Header (Extends SDP)</li><li>Attribute, a=fmtp, Format Specific Parameters</li><li>Mode</li><li>Packet Interval</li></ul></li><li>Offer/Answer <ul> <li>Overview of Offer/Answer</li><li>OFFER/ANSWER Examples</li><li>SDP Offer/Answer Model</li><li>UPDATE RFC 3311</li><li>Preconditions <ul> <li>Preconditions; a=curr and a=des</li><li>Preconditions Call Flow</li><li>Preconditions E2E and Segmented</li></ul></li></ul> 17. QoS <ul> <li>Enforcing QoS <ul> <li>Linking the IMS Core to the EPC</li><li>PCRF Interfaces: Sp Ud, Np, Rx, Sy, Gy, Gyn, Gzn, Gz, Sd, Gx, Gxx</li><li>3GPP Policy Architecture (Simplified)</li><li>Roaming scenarios: H-PCRF and V-PCRF</li><li>PGW Gate/Pinhole Defined</li><li>Converting SDP to a Gate</li><li>VoIP Service Requirements and the QoS Solution</li><li>Default Bearer, Dedicated Bearer, QCI, ARP, GBR</li><li>Rx and Gx Messages</li><li>IMS Dedicated Bearer Setup</li><li>LTE Dedicated Bearer Setup AAR, CCR, Create Bearer Req</li></ul></li></ul> 18. IMS Call Flow Examples <ul> <li>SIP REGISTER <ul> <li>Initial IMS REGISTRATION</li><li>IMS SIP Registration and the DIAMETER Query</li><li>IMS SIP Registration and DIAMETER Response</li><li>IMS SIP Registration REGISTRATION to SCSCF</li><li>IMS SIP Registration aka MD5 CHALLENGE (401)</li><li>IMS SIP Registration Challenge Response</li><li>IMS SIP Registration Confirmed; 200</li><li>IMS SIP Registration; SERVICE PATH Determination</li></ul></li><li>De-Registration <ul> <li>UE Initiated De-Registration</li><li>Network Initiated De-Registration</li></ul></li><li>Media Relay <ul> <li>IMS Call Setup with Media Relay</li><li>Terminal Initiated Session Release</li></ul></li></ul> 19. Circuit Switched Fallback <ul> <li>CSFB Originating <ul> <li>3G and 4G Update Message Review: LAU, TAU, RAU</li><li>Combined EPS/IMSI Message</li><li>How SR-VCC Interoperates with the Combined Attach</li><li>Extended Service Request</li><li>Connection Management Service Request</li></ul></li><li>CSFB Terminating <ul> <li>The IAM and Paging</li><li>Service Request and Context Mod with CSFB</li><li>CCO and Context Release</li><li>Suspend an Update Bearers</li><li>Paging Response</li><li>Active Call</li></ul></li><li>Ladder Diagram <ul> <li>CSFB Ladder Diagram End to End</li></ul></li></ul> 20. SR-VCC <ul> <li>Overview <ul> <li>Comparing VCC, ICS, and IMS-SC</li><li>Apply VCC, ICS, and IMS-SC technology to CSFB and SR-VCC</li></ul></li><li>Routing Number <ul> <li>Mobile Station International Subscriber Directory Number (MSISDN)</li><li>Routing Number</li><li>Which number “Wins” when Routing?</li><li>Which number does the server need?</li><li>STN-SR, IMRN, and gsmSCF Routing Numbers</li><li>How MSISDN and STN are included in SIP messages</li></ul></li><li>SR-VCC Control Paths <ul> <li>Services that must be optimized for SRVCC</li></ul></li><li>The Media Path <ul> <li>Direct Media</li><li>The Role of the ATCF/ATGW and Media Anchoring</li><li>Interoperation between ATCF/ATGW and MSC (4G to 3G Media)</li><li>SR-VCC example: UTRAN to UTRAN Call Control and Media Paths</li><li>Interfacing SR-VCC with a MSC not optimized for SRVCC</li></ul></li><li>SR-VCC Call Flow <ul> <li>SR-VCC PS to CS Transfer Message by Message</li><li>SRVCC PS to CS Transfer</li><li>Control and Media Paths Following SR-VCC-controlled PS to CS Transfer</li><li>SRVCC from E-UTRAN to GERAN without DTM Support</li></ul></li></ul> 21. Emergency Call Flow <ul> <li>References <ul> <li>3GPP Emergency</li></ul></li><li>Components <ul> <li>IMS Emergency Sessions Topology and Message Flow</li><li>IP Multimedia Subsystem (IMS) Emergency Sessions Call Flow</li></ul></li></ul> 22. Charging in the IMS <ul> <li>Charging Systems Overview <ul> <li>Charging in the IMS</li><li>IMS Charging Mechanisms</li><li>Charging Interworking Functions & Reference Points</li><li>Offline Charging Functions</li><li>Online Charging Functions</li><li>Online (Ro) and Offline (Rf) Charging Commands</li></ul></li><li>Charging and Call Flow <ul> <li>P-Charging-Vector: RFC 3455</li><li>P-Charging-Function-Addresses</li><li>IMS Call Setup</li></ul></li></ul> 23. DNS <ul> <li>Zone File <ul> <li>DNS root zone has 13 named authorities</li><li>How a Zone file appears in Linux – Bind9</li><li>How $ORIGIN Impacts the Zone File</li><li>Sample Zone File Organized into a Table (strictly for teaching)</li><li>“SOA” Record – The Start of Authority</li></ul></li><li>Locating SIP Servers <ul> <li>NS-record</li><li>A-record</li><li>SRV-record</li><li>NAPTR – Naming Authority Pointer</li><li>RFC 3263 – Locating SIP Servers - NAPTR</li><li>RFC 3263 – Locating SIP Servers - SRV</li><li>RFC 3263 – Locating SIP Servers - A-record</li><li>RFC 3263 – Locating SIP Servers – INVITE</li></ul></li></ul> LABS: Wireshark Traces, Call Flows & Examples <ul> <li>Lab 0. Understanding the Lab Environment</li><li>Lab 1. Using Wireshark</li><li>Lab 2. SIP User Agent Configuration</li><li>Lab 3. Direct UA to UA Routing with No Proxy</li><li>Lab 4. Proxy Based SIP Routing</li><li>Lab 5. Adding Authorized UAs to a Domain</li><li>Lab 6. Registering a SIP UA (Capturing a SIP REGISTER with Wireshark)</li><li>Lab 7. Intra Domain Routing (SIP routing within the same domain)</li><li>Lab 8. Inter Domain Routing (SIP routing to different domains)</li><li>Lab 9. Digit translation</li><li>Lab 10. Prefix domain transfer (PDT) management</li><li>Lab 11. Capturing a “normal’ SIP call via Wireshark</li><li>Lab 12. Capturing a call to a vacant seat via Wireshark</li><li>Lab 13. Capturing a call to a busy seat via Wireshark</li><li>Lab 14. Capturing a call-forward (3xx response) via Wireshark</li><li>Lab 15. Via, Route, and Record-Route headers</li><li>Lab 16. Examining and manipulating Max-Forwards header</li><li>Lab 17. Capturing SDP offer and answer</li><li>Lab 18. Silence suppression</li><li>Lab 19. DTMF RFC 2833 and SIP INFO</li><li>Lab 20. SIP Back-to-Back UA configuration example (Asterisk)</li><li>Lab 21. REGISTER SIP device to Back-to-Back UA</li><li>Lab 22. Capture SIP call through a Back-to-Back UA and compare to a Proxy</li><li>Lab 23. RTP Relay</li><li>Lab 24. Real-Time Control Protocol (RTCP)</li><li>Lab 25. Routing with DNS / ENUM</li><li>Lab 26. Testing Connectivity using SIP OPTIONS</li><li>Lab 27. SIP testing with SIP-p</li><li>Lab 28: IMS Service Profile</li><li>Lab 29: Roaming</li><li>Lab 30: Exploring the Home S-CSCF Set</li><li>Lab 31: Registration Termination Request (RTR)</li><li>Lab 32: Push Profile Request</li></ul></li></ul>1. IMS Architecture & SIP Proxies - Standards Bodies - Understanding the 3GPP - 3rd Generation Partnership Project - The Network Operators Strike Back: ETSI TISPAN NGN, 3GPP2, & Cablelabs - IETF & RFCs - VoLTE Introduction - VoLTE + IMS Advantages - Legacy vs. IMS - Traditional User Database Management - Why VoIP Central Control Can Not Compete with IMS - The 3GPP IMS Architecture - VoLTE and IMS Architecture Analysis - The Building Blocks - The IMS Core (IP Multimedia Subsystem) - IMS Core Components - IBCF and TrGW - The HSS (Home Subscriber Server) - The SLF (Subscription Locator Function) - The EPC (Evolved Packet Core) - The E-UTRAN (Evolved UMTS Radio Access Network) - The UTRAN (UMTS Terrestrial Radio Access Network) - PCRF - PCRF and its Interfaces - Call Control Paths - The SERVICE PATH = The Half Call – AS Formed by the SIP REGISTRATION - An IMS to IMS Call Analysis - Call Control and Media Paths - The IMS Half Call Concept - Application Servers (AS) - Serving Call Session Function (S-CSCF) - Roaming and Visited - Visited Network vs. Home Network - Proxy Call Session Function (P-CSCF) - S5 (Local Breakout) and Registration - S8 Access and Registration - VoLTE Access - Intro to Bearers & APNs - The Evolved Packet Core Component Analysis - PDCP, RLC, MAC, PHY, and the LTE Grid - Call Flow - Intra Domain Service Path Originating - Intra Domain Service Path Terminating - Intra Domain Call - Intra Domain Routing - Intra Domain Routing Decision - Intra Domain Call End to End - Inter-domain Call, Intra-domain Service Paths - Inter-domain Call Routing - Cross Domain Routing Decision - IMS Border Control Function and Transition Gateway - Inter-domain Roaming - Inter-domain Call While Roaming - Both UEs Roaming Plus Inter-Domain Call - Both UEs Roaming Plus Inter-Domain Call Control Path 2. IMS Identifiers - IMS IDs - IMS Identifiers - UML Model of the Data Downloaded over Cx Interface - UICC - UICC (Universal Integrated Circuit Card) - IMS URI - IMSI – International Mobile Subscriber Identity [im-zee] - IMS Specific Numbering, Addressing and ID - Home Network Domain Name 3. VoLTE and IMS Architecture - HSS - The HSS (Home Subscriber Server) - The SLF (Subscription Locator Function) - CSCF (Call/Session Control Function) - P-CSCF (Proxy-Call/Session Control Function) - I-CSCF (Interrogating-Call/Session Control Function) - S-CSCF (Serving-Call/Session Control Function ) - Breakout Gateway Control Function (BGCF) - AS (Application Server) - MRF - MRFC / MRFP (Media Resource Function Controller / Processor) - Policy and Charging Rules Function and the EPC - Mobility Management Entity (MME) - Serving Gateway (S-GW) - PDN Gateway (P-GW) 4. Bearer and APNs - Commonly Utilized Bearers - Bearer Components from the E-UTRAN through the EPC - VoLTE Bearers from the E-UTRAN through the EPC - Internet Bearers from E-UTRAN through the EPC 5. Power up Process - Overview - Frequency Scanning and UE Categories - System Acquisition and RRC Connection Setup - Primary Synchronization Signal (PSS) - Cell-ID & Secondary Synchronization Signal (SSS) - Physical Broadcast Channel (PBCH) - Master Information Block (MIB) - Transport Downlink Shared Channel (DL-SCH) for SIB1 - System Information Block type 1 (SIB1) - Downlink Shared Channel (DL-SCH) & SIB2 - Uplink Synchronization - RRC CONNECTED and RRC IDLE - SIB1 – SIB12 - Cell Selection - Network Attach - The IMS APN Bearer Establishment - Attach Request, NAS, Authentication Process - Encryption and ESM Info - Location Request and Response - Create Session Request and Response - CCR AAA Request and Response - Create Session Response SGW to MME to eNB - Initial Context Setup and RRC Reconfiguration - UE Capability and ICR - Modify Bearer and EMM Info - Modify Bearer Response, AAA Responses and the SIP REGISTER - The Spreading Sequence - How does a UE request bandwidth in order to gain access to request bandwidth? 6. Handover Between eNodeBs - Idle Mode - Cell Reselection - Discontinuous Reception (DRX) with Long and Short DRX - How DRX Timers Apply the LTE Grid - Idle Mode Within and Beyond the UE - Active UE - Intra-frequency Mobility (3GPP TS 23.401) - Intra MME SGW Handover Using the X2 Interface - S1-based Handover with S-GW & MME Relocation 7. Tracking and Paging A UE - Overview - Tracking Area Defined - Tracking Area Identifiers - Tracking Area Lists - Relationship of MME Pool Areas, TA, and S-GW Service Areas - Tracking and Paging a UE - Tracking Area Update (TAU) - Idle Mode - UE Entering Idle Mode - Paging an Idle UE 8. SIP Architecture - The Big Picture - Key VoLTE and IMS Protocols - SIP Message Format - SIP User Agent (UA) - SIP Request and Response Format - IMS SIP Transactions - SIP Requests (Methods) - SIP Response Codes - A SIP Transaction Defined - PRACK and The 100rel Process (RFC 3262) - VoLTE to VoLTE SIP Transactions - SIP Control Path - Trust Chain - SIP Architecture - B2BUA Example: TAS - Mapping SIP dialogs through an Application Server - Proxy vs. B2BUA - User Identities: Address-of-Records and Contact-URIs - SIP URI - SIP and SIPS URI Structure Components (RFC 3261) 9. SIP Via Paths - The Via Header - The “Via:” Path: How A Response Finds Its Way Back - The SIP Transaction - Via: Lifetime = per Transaction! (Not the Entire Duration of the Dialog) - Impact of Via Path on the SIP Dialog - What Path Does the ACK Take? 10. SIP Route Headers - RR and Route - The Record-Route and Route Function - Looping - Loop Detection 11. Basic SIP & IMS Specific Headers - Start Line - Via: - Via: branch parameter - From: - To: - Call-ID: - SIP Dialog ID - Contact: - CSeq: (Command Sequence) - Content-Type: - Content-Type: message/sipfrag RFC 3420 - Content-Length: - Max-Forwards: - Allow: - OPTIONS - User-Agent: - Supported: - P-Preferred-Identity: and Privacy: RFC 3325 (UA to P-CSCF) - P-Preferred-Identity: to P-Asserted-Identity: - P-Access-Network-Info: RFC 3455 - Authorization: RFC 3261 Section 22.2 - Path: RFC 3327 - Service-Route: RFC 3608 - Introduction to SigComp - SigComp Example 12. Diameter - Overview - RADIUS vs DIAMETER - Diameter Protocol - Diameter Message Structure - The AVP Chain: Type – Length - Value - AVPs Encapsulated Inside an AVP - Diameter Header Structure - AVP Structure - Diameter Message Example - Diameter Message as Wireshark Would Display it - Customization - Diameter Code Customization - IMS’s Diameter Cx Command Codes Values - Diameter AVPs Defined for the Cx Interface - Diameter AVPs: Rx Interface Codes - Registration Call Flow - Challenge - Authorization - Registration Status - Registration Termination Request - Registration Status at the P-CSCF - SCTP - Traditional Transport Layers (OSI Layer 4) - Stream Control Transmission Protocol (RFC 4960) - SCTP High Durability Connections - Setting Up An Association - The SCTP Protocol Data Unit - Head-of-Line-Blocking Avoidance - Chunking & Bundling 13. H.248 - Overview - H.248 Call Flow Example - H.248 Common Controller - H.248 Call Control Model - H.248 in the IMS Core - H.248 Call Control Model 14. Initial Filter Criteria (iFC) - iFC Function - iFC Logic - Data Structure - UML Model of the Data Downloaded Over Cx Interface - iFC Logic - Disjunctive Normal Form - Conjunctive Normal Form - iFC Example - Setting Up A TAS for Feature Enablement – (Using three.ims Domain) - Service Profile 15. Presence - The Presence Model - Presentity and Watcher - PUBLISH - SUBSCRIBE - NOTIFY - IMS Call Flow - Cross Domain SUBSCRIBE Example - PUBLISH presentity and Cross Domain NOTIFY to Watchers - Basic vs. Rich Presence - Presence Information Data Format (PIDF) RFC 3863 - Rich Presence Information Data format (RPID) RFC 4480 - Message Examples - PUBLISH (Initial) - SUBSCRIBE (Watcher) - NOTIFY (Initial Status) - PUBLISH (Updated status) - NOTIFY (Updated status) 16. Session Description Protocol (SDP) - Overview - SDP Establishes ½ the Media Channel - SDP: RFC 4566 - RTP is “simplex” - a=sendonly means what? - Media Direction’s Impact on RTCP - Lines - Version, v= - Origin, o= - Session, s= - Connection, c= - Time, t= - Media Description, m= - Bandwidth, b= - The “a=” Attribute Header (Extends SDP) - Attribute, a=fmtp, Format Specific Parameters - Mode - Packet Interval - Offer/Answer - Overview of Offer/Answer - OFFER/ANSWER Examples - SDP Offer/Answer Model - UPDATE RFC 3311 - Preconditions - Preconditions; a=curr and a=des - Preconditions Call Flow - Preconditions E2E and Segmented 17. QoS - Enforcing QoS - Linking the IMS Core to the EPC - PCRF Interfaces: Sp Ud, Np, Rx, Sy, Gy, Gyn, Gzn, Gz, Sd, Gx, Gxx - 3GPP Policy Architecture (Simplified) - Roaming scenarios: H-PCRF and V-PCRF - PGW Gate/Pinhole Defined - Converting SDP to a Gate - VoIP Service Requirements and the QoS Solution - Default Bearer, Dedicated Bearer, QCI, ARP, GBR - Rx and Gx Messages - IMS Dedicated Bearer Setup - LTE Dedicated Bearer Setup AAR, CCR, Create Bearer Req 18. IMS Call Flow Examples - SIP REGISTER - Initial IMS REGISTRATION - IMS SIP Registration and the DIAMETER Query - IMS SIP Registration and DIAMETER Response - IMS SIP Registration REGISTRATION to SCSCF - IMS SIP Registration aka MD5 CHALLENGE (401) - IMS SIP Registration Challenge Response - IMS SIP Registration Confirmed; 200 - IMS SIP Registration; SERVICE PATH Determination - De-Registration - UE Initiated De-Registration - Network Initiated De-Registration - Media Relay - IMS Call Setup with Media Relay - Terminal Initiated Session Release 19. Circuit Switched Fallback - CSFB Originating - 3G and 4G Update Message Review: LAU, TAU, RAU - Combined EPS/IMSI Message - How SR-VCC Interoperates with the Combined Attach - Extended Service Request - Connection Management Service Request - CSFB Terminating - The IAM and Paging - Service Request and Context Mod with CSFB - CCO and Context Release - Suspend an Update Bearers - Paging Response - Active Call - Ladder Diagram - CSFB Ladder Diagram End to End 20. SR-VCC - Overview - Comparing VCC, ICS, and IMS-SC - Apply VCC, ICS, and IMS-SC technology to CSFB and SR-VCC - Routing Number - Mobile Station International Subscriber Directory Number (MSISDN) - Routing Number - Which number “Wins” when Routing? - Which number does the server need? - STN-SR, IMRN, and gsmSCF Routing Numbers - How MSISDN and STN are included in SIP messages - SR-VCC Control Paths - Services that must be optimized for SRVCC - The Media Path - Direct Media - The Role of the ATCF/ATGW and Media Anchoring - Interoperation between ATCF/ATGW and MSC (4G to 3G Media) - SR-VCC example: UTRAN to UTRAN Call Control and Media Paths - Interfacing SR-VCC with a MSC not optimized for SRVCC - SR-VCC Call Flow - SR-VCC PS to CS Transfer Message by Message - SRVCC PS to CS Transfer - Control and Media Paths Following SR-VCC-controlled PS to CS Transfer - SRVCC from E-UTRAN to GERAN without DTM Support 21. Emergency Call Flow - References - 3GPP Emergency - Components - IMS Emergency Sessions Topology and Message Flow - IP Multimedia Subsystem (IMS) Emergency Sessions Call Flow 22. Charging in the IMS - Charging Systems Overview - Charging in the IMS - IMS Charging Mechanisms - Charging Interworking Functions & Reference Points - Offline Charging Functions - Online Charging Functions - Online (Ro) and Offline (Rf) Charging Commands - Charging and Call Flow - P-Charging-Vector: RFC 3455 - P-Charging-Function-Addresses - IMS Call Setup 23. DNS - Zone File - DNS root zone has 13 named authorities - How a Zone file appears in Linux – Bind9 - How $ORIGIN Impacts the Zone File - Sample Zone File Organized into a Table (strictly for teaching) - “SOA” Record – The Start of Authority - Locating SIP Servers - NS-record - A-record - SRV-record - NAPTR – Naming Authority Pointer - RFC 3263 – Locating SIP Servers - NAPTR - RFC 3263 – Locating SIP Servers - SRV - RFC 3263 – Locating SIP Servers - A-record - RFC 3263 – Locating SIP Servers – INVITE LABS: Wireshark Traces, Call Flows & Examples - Lab 0. Understanding the Lab Environment - Lab 1. Using Wireshark - Lab 2. SIP User Agent Configuration - Lab 3. Direct UA to UA Routing with No Proxy - Lab 4. Proxy Based SIP Routing - Lab 5. Adding Authorized UAs to a Domain - Lab 6. Registering a SIP UA (Capturing a SIP REGISTER with Wireshark) - Lab 7. Intra Domain Routing (SIP routing within the same domain) - Lab 8. Inter Domain Routing (SIP routing to different domains) - Lab 9. Digit translation - Lab 10. Prefix domain transfer (PDT) management - Lab 11. Capturing a “normal’ SIP call via Wireshark - Lab 12. Capturing a call to a vacant seat via Wireshark - Lab 13. Capturing a call to a busy seat via Wireshark - Lab 14. Capturing a call-forward (3xx response) via Wireshark - Lab 15. Via, Route, and Record-Route headers - Lab 16. Examining and manipulating Max-Forwards header - Lab 17. Capturing SDP offer and answer - Lab 18. Silence suppression - Lab 19. DTMF RFC 2833 and SIP INFO - Lab 20. SIP Back-to-Back UA configuration example (Asterisk) - Lab 21. REGISTER SIP device to Back-to-Back UA - Lab 22. Capture SIP call through a Back-to-Back UA and compare to a Proxy - Lab 23. RTP Relay - Lab 24. Real-Time Control Protocol (RTCP) - Lab 25. Routing with DNS / ENUM - Lab 26. Testing Connectivity using SIP OPTIONS - Lab 27. SIP testing with SIP-p - Lab 28: IMS Service Profile - Lab 29: Roaming - Lab 30: Exploring the Home S-CSCF Set - Lab 31: Registration Termination Request (RTR) - Lab 32: Push Profile Request5 days2195.003030.00