1 / 29

TIPHON NGN approach and architecture

TIPHON NGN approach and architecture. SCN Plane. Problem: Too Many Protocols. T erminal/ SIP client. Back-End Server. Soft Switch. Gateway. SE. SE. SE. RAS Annex G OSP. RAS Annex G OSP. MGC. SG. RAS. INAP. SC. SC. SC. SC. SC. SIP. SoftSwitch. H.225.0. H.225.0.

bela
Download Presentation

TIPHON NGN approach and architecture

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. TIPHON NGN approach and architecture

  2. SCN Plane Problem: Too Many Protocols Terminal/ SIP client Back-End Server Soft Switch Gateway SE SE SE RAS Annex G OSP RAS Annex G OSP MGC SG RAS INAP SC SC SC SC SC SIP SoftSwitch H.225.0 H.225.0 ISUP/Q.931 H.225 CC CC CC CC CC SIP SIP, BICC SIP, BICC QSIG H.245 H.245 H.245 BC BC BC BC SDP SDP SDP H.248/MEGACO H.248/MEGACO MG MG MC MC RTP RTP MC Packet transport plane

  3. Changes in business landscape • Changes in technology • Changes in regulation • Changes in customer perception

  4. New Commercial Framework • Multi-service is the future • spread costs of infrastructure over many services • Services are rendered in a commercial context • user pays for the use of the service • Access provider profits from new services

  5. Authorization & Accounting Service integration Content delivery Video Telephony Telephony Instant messaging Presence E-commerce Generic broadband TDM GPRS UMTS 10BT 100BT WLAN Transport service (access & core) NGN scope

  6. New Technology Framework • Internet model is not the way forward! • Base technology framework on business relationships • Separate application services and transport services in orthogonal planes • Use a meta-protocol to specify the technology and interwork all applicable protocols • Shape technology by requirements on QoS, Accountability and Security

  7. TIPHON Services Approach • Release 3: • Simple Call • Release 4: • Small-Office/Home-Office (SOHO) & High-end Residential (HiRes) • Release 5: • Next Generation (NextGen)

  8. Protocol Independence • Goal: Seamless Service Availability • Desired Result:TIPHON services available on several technologies • H.323 • SIP • H.248 / MEGACO • BICC • etc… • Method: Meta-protocol (stage 2) driven from Service Capabilities • Technology: Profiles of existing and emerging protocols

  9. QoS Considerations • QoS is based on subjective requirements and is Application Specific • Technical framework ensures QoS can be requested and delivered, even inter-domain • Maintain QoS even for high network load

  10. Application Construction Some applications may be standardised (e.g. telephony) Service Applications Service Application Layer Registration Capability Service Abstraction Layer Routing Capability Service Capabilities Proprietary extensions provide differentiation and interoperability.

  11. Interworking on common capabilities Extra Service Capabilities Extra Service Capabilities Extra Service Capabilities Extended Service Applications Hierarchy of applications Base Service Application

  12. SCN Plane Management Plane Transport plane Transport Plane Application Plane Planes: Major Functional View Service architecture, protocols

  13. Application plane • Provides applications over generic transport • This service needs to be protected from abuse • Structured for re-use • Design process: • Who • Identifying roles in the end to end service • What • Identifying functionality per role • Where • Mapping the role to possible physical architectures

  14. Essential elements • Quality of Service • Determined for the application • Drives the transport plane • Transport plane is subservient to application plane • Security • Protects the user • Protects the infrastructure • Maintains performance

  15. Transit Network FG Serving Network FG Home Network FG Transit Network FG Serving Network FG Transit Network FG Home Network FG Functional Groups Originating Terminal Terminating Terminal

  16. Transport Plane • Transport plane provides a service • QoS aware Transport (for streamed media and signaling) • Service has access control • Transport requirement is driven by the application • How the requirement is met is not of interest to the application • Open transport interface • QoS enabled transport request • Open reporting facility

  17. Application plane Orig./ Term Terminal FG Serv. NW FG Home NW FG Inter. NW FG Term./ Orig. NW FG Services layer Service control layer Call/Session Control Layer Bearer Control Layer Media control layer Transport plane Service layer Control layer Transport layer TIPHON Architecture

  18. Originating/Terminating Network FG Originating/ Terminating Terminal FG Terminating/ OriginatingGateway FG IntermediateNetwork FG ServingNetwork FG Home Network FG Service QoSPE ServiceProfile Call Routing QoSPE User profile Call Routing QoSPE Call Routing QoSPE S4 S4 S3 S2 S4 S1 S2 S3 S3 S4 S1 Service control SC2’ SC SC SC SC SC SC2’ SC2’ R1 R2 HREG TREG SREG SC1 SC2 SC2 SC2 SC2 Call control CC CC CC CC CC C3 C2 C2 C1 C2 Bearer Control C2 SCNPlane C3 C1 C2 C2 BC BC BC BC BC N2 N2 N2 N1 N3 Media Control MC MC MC MC MC M1 M2 M2 M2 M3 TransportService T2 TU TPE TU TPE T2 TU T2 T1 TPE T1 I6 I4 I6 I4 I6 I4 I1 I1 I2 I2 TRM TRM TRM TRM TRM TransportControl I3 I3 I5 I3 I3 I5 I3 I3 I5 ICF TF ICF TF ICF ICF TF ICF ICF Transportflows Originating/ Terminating Terminal FG Egress/Ingress transport Domain Ingress/Egress transport Domain Core transport Domain TIPHON Architecture

  19. Services Static service related information. (e.g. databases for user profiles, call routing tables). Active service related functionality (e.g. terminal registration and call routing) Service Control Call/ Session Control Binds a set of users and a group of bearers together and maintains call state Bearer Control Control of media flow properties and media end-point addresses (e.g codec type, packetization, QoS Requirements) Media Control Media stream transmission and reception QoS Characterization & Control Call Setup Paul desires a Telephony session with Mike with “Good” Quality Paul is at terminal 192.168.1.9 in realm ServiceProvider1-NL, Mike is at ServiceProvider2-UK, create a call Call between terminal 192.168.1.9 in realm ServiceProvider1-NL, and realm Mike at ServiceProvider2-UK, create call between them with “Good” Quality bidirectional audio bearer between terminal 192.168.1.9 in realm ServiceProvider1 -NL and B-party in realm ServiceProvider2 -UK, delay < 150ms, loss<….. G711 over RTP flow, 20 ms audio per packet from 192.168.1.9 to ServiceProvider1-NL interconnect, transcode at interconect to G.723, send to ServiceProvider2 -UK interconnect .etc. Transport: arranges link-link QoS packet transport for flows with given packet size with appropriate delay, loss etc

  20. I want a session with user Mike with quality level “Good” and have CODECS G.711, G.723, G.729 I want a session to user “Mike” at your network from user “Paul” with budgets; delay <80ms, jitter < …, loss < …, offering CODECS G.711, G.723, G729, GSM I have a session for you from user “Paul” with choice of CODECS G.711, G.723, G729 , GSM Calls across Domains OK, you’re my customer and this falls within our contract. OK, we have a hand-off contract and this falls within our contract. Thank you, I will pick G.711 Originating Terminal FG Originating Network FG Terminating Network FG Terminating Terminal FG

  21. CallRequest Meta-protocol NextDomain PreviousDomain Transport MC BC CC SC Services Access Routing Request 1.A requests call Access &Routing Request SC200 2. Authorize call CC200 Validate RouteConfirm SC201 Access Routing Request BearerRequest BC200 4.request bearer 3.route call Validate RouteConfirm BearerRequest Access &RoutingConfirm MediaCapRequest SC202 TransportCapRequest 6.reserve transp. 5.reserve media MC200 BC200 CC203 BearerEstabl.Report MediaCapConfirm TransportCapConfirm CallRequest 7. Forward to B MC201 BC201 CC204 BearerRequest 8. B confirms bearer MediaEstReqeust TransportEstRequest BearerConfirm 10.establish transp. MC202 9.establish media BC202 MediaEstConfirm BearerEstabl.Confirm TransportEstConfirm MC203 BC203 CC209 CallReport{Alerting} CallReport{Alerting} CC210 13.Activate transp. 12.Activate media 11. B accepts call MediaIndication BearerIndication TransportIndication CallConfirm CC211 MC204 BC204 CallConfirm ACTIVE PHASE 14.media flows

  22. H.323 flows IP Transport NextDomain Terminal MG Gatekeeper Gate- keeper H.225 Annex G Access Request H.225 Setup + FastStart (so + H.245 tokens) 2 1 4 H.225 Annex G Access Confirm RSVP PATH H.225 LRQ H.248 Context Add 3 H.225 LCF 6 5 H.248 Context Reply RSVPRESV H.225 Setup + FastStart (so + H.245 tokens) 7 RSVP PATH H.248 Modify H.225 Alerting + H245 tokens 10 9 8 H.248 Modify Reply RSVPRESV H.225 Alerting + H.245 tokens H.248 Modify 12 H.225 Connect + H.245 tokens 11 H.225 Connect + H.245 tokens ACTIVE PHASE 14

  23. H.248 Context Add SIP flows Next Domain IP Transport SIP Client SIP Server MG SIP Proxy Server 1 INVITE (+ SDP) 4 Not available in SIP, other protocol needed 2 INVITE RSVP PATH 3 REDIRECT 6 5 7 H.248 RSVPRESV INVITE (+SDP) Reply Context Add RSVP PATH H.248 Modify 8 180 –RINGING + SDP 10 9 RSVPRESV H.248 Modify Reply 180 - RINGING + SDP 11 200 - OK 12 H.248 Modify 200 - OK ACTIVE PHASE 14

  24. H.248 Context Add BICC/ISUP flows Previous domain IP Transport Next Domain BIWF IN CSF 1 IAM 4 Not available in BICC 2 other protocol needed 3 DSS2 Setup Not available in BICC other protocol needed 5 6 IAM 7 DSS2 H.248 Connect Context Add Reply DSS2 Setup H.248 Modify ACM 8 9 10 DSS2 H.248 Connect Modify Reply ACM ANM H.248 12 11 Modify ANM 14 ACTIVE PHASE

  25. Interworking using TIPHON • Existing call setup protocols use similar approaches • All are consistent with the TIPHON architecture

  26. H.323 to SIP Interworking Next Domain IP Transport Terminal MG SIP Server IWF H.225 Setup + FastStart (so + H.245 tokens) Not available in SIP, other protocol needed 1 4 2 INVITE RSVP PATH H.248 Context Add 3 REDIRECT 6 5 H.248 Context Reply RSVPRESV 7 INVITE (+SDP) RSVP PATH H.248 Modify 8 180 –RINGING + SDP 10 9 H.248 Modify Reply RSVPRESV H.225 Alerting + H.245 tokens H.248 Modify 12 H.225 Connect + H.245 tokens 11 200 - OK ACTIVE PHASE 14

  27. H.248 Context Add BICC and SIP Interworking Previous domain Next Domain IP Transport SIP Server BIWF IWF 1 IAM 4 Not available in SIP, other protocol needed 2 INVITE 3 DSS2 Setup REDIRECT 5 6 7 INVITE (+SDP) DSS2 H.248 Connect Context Add Reply DSS2 Setup H.248 Modify 8 180 –RINGING + SDP 9 10 DSS2 H.248 Connect Modify Reply ACM H.248 12 11 200 - OK Modify ANM ACTIVE PHASE 14

  28. H.248 Context Add BICC to H.323 Interworking Previous domain NextDomain IP Transport Gatekeeper BIWF IWF H.225 Annex G Access Request 1 IAM 4 2 H.225 Annex G Access Confirm H.225 LRQ 3 DSS2 Setup H.225 LCF 5 6 H.225 Setup + FastStart (so + H.245 tokens) DSS2 H.248 7 Connect Context Add Reply DSS2 Setup H.248 Modify H.225 Alerting + H245 tokens 9 8 10 DSS2 H.248 Connect Modify Reply ACM H.225 Connect + H.245 tokens 11 H.248 12 Modify ANM ACTIVE PHASE 14

  29. Conclusion • TIPHON addresses the technology based on business goals. • TIPHON may provide the pieces to help the industry out of the crisis • TIPHON is much more than simply Voice over IP • TIPHON enables new and differentiated services • Not recreating the ISDN on every technology • TIPHON is technology agnostic where possible • TIPHON abstract Architecture is mappable to physical architectures of 3G, Cable, BICC, H.323 • TIPHON achieves Seamless Service Availability • TIPHON meta-protocol is an excellent vehicle for interworking • TIPHON Enabler of convergence

More Related