1 / 15

The New TIPHON Architecture

Paul Sijben Forward Looking work sijben@lucent.com. The New TIPHON Architecture. Outline. TIPHON Architecture evolution Why an abstract architecture? Overview of the new TIPHON architecture Making it work. First TIPHON architecture (1997/8). Physical H.323 oriented. G.

ankti
Download Presentation

The New TIPHON 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. Paul Sijben Forward Looking work sijben@lucent.com The New TIPHON Architecture

  2. Outline • TIPHON Architecture evolution • Why an abstract architecture? • Overview of the new TIPHON architecture • Making it work sijben@lucent.com

  3. First TIPHON architecture (1997/8) • Physical • H.323 oriented G Back-End Services D PSTN Gatekeeper Gatekeeper F A C E1 ISDN IP Network SCN Network E2 E3 GSM B E4 Terminal Gateway PISN sijben@lucent.com

  4. Second TIPHON Architecture (1998/9) • Includes decomposed gateways GK GK BackEnd D G A C F E.b J Media GW Signalling Controller GW N B Media GW H.323 E.a Terminal sijben@lucent.com

  5. Why something else? • Goal: universal service offering over multiple technologies • Physical architecture is constrained to one protocol, implementation technology or product concept • QoS is not an add-on, it should be dealt with everywhere • Security Aspects sijben@lucent.com

  6. New TIPHON architecture • Design principles: • standardize interfaces not business models • separate service application from transport technology • address manageability of network • Layered approach; one layer provides a service to the next sijben@lucent.com

  7. SCN Plane Management Plane Transport plane Transport Plane Application Plane Planes (Major Functional View) • Planes are a means to functionally structure the problem space • Interfaces between the planes may be interfaces between business entities • Implementations may span planes Service architecture, protocols sijben@lucent.com

  8. Transport Plane principles • Transport plane provides a service: QoS Transport • This service is provided commercially • The service needs to be protected from abuse • The service should be independent of the application (IP telephony, video streaming,…) • The application should be independent of the transport details (QoS mechanism, technology) sijben@lucent.com

  9. Endpoint Network Application Application Application TU TPE TU TPE T2 TRM T1 T2 I6 I4 I6 I4 I1 I2 TRM TRM I3 I3 I5 I3 I5 I3 I3 I5 TF ICF ICF ICF TF ICF ICF User transport domain Core transport domain Transport plane functionality Network Usage accounting Policy management The customer Application Plane TransportService TransportControl TF Transportflows Ingress transport domain Protection (e.g. firewalls) Transport Functionality (e.g. routers) Control of the system (access control, metering) sijben@lucent.com

  10. Application plane principles • Service application consists of service capabilities • service capabilities are distributed • user equipment, VoIP servers, ASP servers… • Layered approach • NOT T-model • capabilities are like LEGO sijben@lucent.com

  11. Static service related information. (e.g. databases for user profiles, call routing tables). Services Active service related functionality (e.g. terminal registration and call routing) Service Control Call 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 Layers of capabilities sijben@lucent.com

  12. User pushes control to the server Service Service Service Control Control Control Session Session Session Bearer Bearer Media Media Distributing Capabilities End UserDomain ServiceDomain End userDomain sijben@lucent.com

  13. 3rd party service domain ... User profile Call Route User profile Back-end Servers SC SC SoftSwitch Bearer Setup BC Media Gateway Media Gateway MC1 MC2 Media flow1 Media flow2 Media flow3 TDM Network IP Network ATM/MPLS Network TR1 TR2 TR3 TIPHON Architecture in practice Service provider domain End user domain End user domain Call Setup CC sijben@lucent.com

  14. Audio stream (with properties) Video stream (with properties) BC BC IP address 1a IP address 1b 2a 2b Video Video audio audio MC MC MC MC MC MC IP Addressing QoS signalling IP Addressing QoS signalling IP Network IP Network TIPHON Multimedia-ready User A User B CC sijben@lucent.com

  15. Conclusion • The TIPHON architecture is future-proof • Architecture provides stability in a dynamic world • Modular approach supports rapid development • The architecture supports universal service offering over multiple technologies • The architecture supports diverse business models • Encompasses end-to-end Quality of Service & Security • Architecture is implemented using available standard protocols • More information: • http://docbox.etsi.org/tech-org/tiphon/Document/tiphon/07-drafts/wg2/RTS02009/ sijben@lucent.com

More Related