1 / 14

SIP & SS7 (SIP-02) Monday - 09/10/07,  10:00-10:45am

SIP & SS7 (SIP-02) Monday - 09/10/07,  10:00-10:45am. SIP-SS7 Interworking @ the Application Layer. Vince Lesch VP of Product Marketing. Agenda. Network Evolution Key Transitional Challenges Seamless Connectivity Service Deployment and Access SCIM IM-SSF NGN Control Layer

sorley
Download Presentation

SIP & SS7 (SIP-02) Monday - 09/10/07,  10:00-10:45am

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. SIP & SS7 (SIP-02)Monday - 09/10/07,  10:00-10:45am

  2. SIP-SS7 Interworking @ the Application Layer Vince Lesch VP of Product Marketing

  3. Agenda • Network Evolution • Key Transitional Challenges • Seamless Connectivity • Service Deployment and Access • SCIM • IM-SSF • NGN Control Layer • The Build Out Steps • Summary

  4. PBX VoIP End-Point SIP PBX IAD VoIP SIP Services Edge Proxy A/Abis MG RAN SBC A/Abis MSC Server VoIP MG RAN Edge Proxy SBC VoIP PSTN Region Network Evolution - Growing the NGN • Cost Reduction at the Core through VoIP • Expansion of VoIP to Enterprise & Residential • Introduction of services based on SIP application servers • VoIP Peering • R4 MSC servers introduction PSTN Region PSTN Region

  5. Key Transitional Challenges • Technical Challenges • Mergers & acquisitions have resulted in operators supporting several versions and variants of the same product & protocol • Seamless service connectivity across hybrid networks • Legacy system connectivity to newer systems • Systems integration and multi-vendor interoperability • Stability of standards, vendor implementation of standards • Business Challenges • Investing in the future while supporting today’s users • Capping expenditures in the “pre-IMS” technology • Cost effectively running a hybrid network • Providing new services to subscribers on old & new networks • Making the business case for IMS work

  6. Seamless Connectivity TDM for access, IP at the core for transport Interworking between ISUP and SIP for call completion. BICC (Q.1902) used in 3G R4 architectures is based on ISUP which simplifies interworking IETF, ITU-T and 3GPP Standards for ISUP & SIP Interworking: RFC 3372/3398, Q.1912.5, 29.163 Media Media Gateway Gateway Media Media Gateway Gateway SIP AS Call Call BICC, SIP Server Server SS7 SS7 ISUP ISUP ATM, IP LE LE backbone PSTN/ PSTN/ PSTN/ PSTN/ ISDN ISDN ISDN ISDN 6

  7. IMS Architecture for Svc Provisioning Source: TS 23.218 IP Multimedia (IM) session handling; IM call model; Stage 2

  8. Service Orchestration & Mediation IMS-to-IN (SIP-SS7) Exposing legacy services into IMS domain (Ex. LNP in IMS domain) IN-to-IMS (SS7-SIP) Access to next generation applications (Ex. LHS & MHS) IN-to-IN (SS7-SS7) Mediates services implemented using different technologies (Ex. CAMEL Consolidation) IMS-to-IMS (SIP-SIP) SCIM functionality mediates SIP services in the IMS World (FMC, MM-IM & Presence) Voice AS CNAM AIN 1188 AIN Virtual SIP UA Virtual SSP Virtual SIP AS Virtual SCP LNP SSP MSC MGCF MM-IM Service Orchestration & Mediation AIN IN VCC Presence CSCF Function STP Function SSP MGCF SCIM Bridging IN/AIN & IMS Applications 8

  9. Service Orchestration & Mediation Subscriber • Service Orchestration (SCIM) • Interaction across multiple CAMEL and IMS Application Servers • Service Meditation (IM-SSF) • Mediate between CAMEL and SIP Service Clients/Server nodes • Mediate between SS7 variants • Variations • SS7 only • SIP only • SIP & SS7 Billing Control Vendor 1 MSC/SSP PRBT Virtual SCP VPN/LNP Vendor 2 MSC/SSP Interaction New Network Services Virtual SIP AS Presence SoftSwitch/ CSCF Mediation SIP App Server Expensive to add multiple protocols Network AND market requirement to combine SCIM and IM-SSF functionality into one product

  10. SIP STP SIP Signaling Router = SIP STP PBX VoIP End-Point SIP PBX IAD SIP AS (B2BUA) VoIP Edge Proxy A/Abis MG RAN SBC A/Abis MSC Server VoIP MG RAN Edge Proxy • Cost Reduction at the Core through VoIP • Expansion of VoIP to Enterprise & Residential • Introduction of services based on SIP application servers • VoIP Peering • R4 MSC servers introduction SBC VoIP PSTN • Scalable signaling infrastructure

  11. Current NGN Implementation SIP AS SIP AS MSC Servers IP PBX • IP layer routers • IP routing protocols • IP QOS controls SIP End-Points PSTN GW Softswitch Multimedia Servers Distributed policies and information 11

  12. NGN 2.0: Dedicated SSR Session Layer SIP AS SIP AS MSC Servers IP PBX • IP layer routers • IP routing protocols • IP QoS controls Session Routing Engine Session Routing Engine SIP End-Points PSTN GW Session Setup URI Routing Service Orchestration IOT Point Softswitch Multimedia Servers 12

  13. SIP AS SIP AS Multimedia IM SIP Media Server IMS Media Server STP Sigtran ISUP/INAP S-CSCF SSR P-CSCF I-CSCF MGC/ MGCF Softswitch Transit Softswitch Softswitch TDM MSC The Build Out Steps IMS Voice AS CAMEL INAP Service Orchestration (SCIM) AND Mediation (IM-SSF) SMSC

  14. Summary Network evolution present operators with many challenges Network – operating a hybrid network for many, many years Services – consistency across networks and transparency to the customer Business – proving in the business case (leverage what you’ve got) Migrating at the signaling control layer … a logical choice Service mediation (IM-SSF) & interaction (SCIM) across pre-IMS & IMS domains SIP signaling & session control layer in the NGN brings benefits now Unified Signaling Control Plane: SS7 STP = SIP STP = IMS CSCF Transitional technologies will be key for the next 3 - ? years Minimize investment in “pre-IMS” technologies Service continuity across hybrid networks Leverage existing investment in key IN/AIN applications (e.g., number portability) by making them available to both domains during transition to IMS A good transitional strategy is essential to making the IMS business case work 14

More Related