1 / 32

Creation and Operation of Hybrid Services

Jean-Pierre Hubaux Institute for computer Communications and Applications (ICA) Swiss Federal Institute of Technology, Lausanne (EPFL) Currently on leave at UC Berkeley, EECS Department Note: This work was initiated at the IBM T.J. Watson Research Division, Hawthorne, NY, in Spring 1998

keona
Download Presentation

Creation and Operation of Hybrid Services

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. Jean-Pierre Hubaux Institute for computer Communications and Applications (ICA) Swiss Federal Institute of Technology, Lausanne (EPFL) Currently on leave at UC Berkeley, EECS Department Note: This work was initiated at the IBM T.J. Watson Research Division, Hawthorne, NY, in Spring 1998 Other contributors: Giovanni Pacifici, Asser Tantawi (IBM Research) Constant Gbaguidi, Maher Hamdi (EPFL/ICA) Creation and Operation of Hybrid Services

  2. Example of Hybrid Network: GSM, PSTN and Internet Web Server Air interface: - circuit (GSM) - packet (IMT-2000) Internet BS MSC Gateway MS PSTN MS: Mobile Station BS: Base Station MSC: Mobile Services Switching Center

  3. Definitions Hybrid network: internetworking of both the Internet and the telecom network (including the cellular network) Teleinformation Service: set of features, provided end-to-end by a service provider with a commitment in terms of QoS:Teleinf. Service = Contract/QoS + Distributed Application + Connectivity Hybrid service: teleinformation service running on a hybrid networkNote: by “Internet” we intend the broad family of IP-based networks, including the Intranets Problem: how do we define, create, operate and manage hybrid services? Problem Statement

  4. B1: “The services will continue to be primarily provided by the network rather than by the terminals” ==> evolution of the IN: CS-1, CS-2,... B2: “The TMN is the solution for network management” B3: “Protocols and services are such complex systems that they require to be fully specified before being developed” B4: “The B-ISDN will be based on end-to-end ATM” B5: “In order to cope with the complexity and diversity of the new services, with the need to integrated network and service management and with deregulation, a distributed, object-oriented platform is required” ==> TINA Old Telecom Beliefs related to Network and Service Architectures

  5. CT2 DECT CT2+ DECT+ GSM-1 GSM-2 CS-1 CS-2 CS-3 UMTS (ETSI) IMT-2000 (ITU) UPT-1 UPT-2 B1: “The services will continue to be primarily provided by the network rather than by the terminals” Probably true for voice-oriented mobility services Functionality of the IN: - location information, registration and retrieval - call routing - authentication - charging - handover CT : Cordless Telephony DECT : Digital Equipment for Cordless Telephony UPT : Universal Personal Telecommunication UMTS : Universal Mobile Telephony System IMT-2000 : International Mobile Telecommunications 2000

  6. Example of Hybrid IN-based Service: the WebIN/NEXUS Project of HP Labs (1/2) Service data/control function SCF/SMF Internet Service control function SCF SCF Service switching function SSP SSP (Adapted from Colin Low: “Integrating Communication Services”, IEEE Comm. Mag., June 1997)

  7. Example of Hybrid IN-based Service: the WebIN/NEXUS Project of HP Labs (2/2) Implementing call redirection: Service provider Web server Incoming call PSTN HTTP GET: Incoming call Redirection Number Service switching point Service control function Subscriber Web server INAP Redirected call Enterprise Web server

  8. True or false, but most probably false The driving idea behind the TMN is that network management is such a complex task that it necessitates a complex solution However, the TMN protocols are OSI-minded and have the OSI drawbacks Large (data) networks are managed with simpler solutions (SNMP) B2: “The TMN is the solution for network management”

  9. False Committee work based on consensus has led to the high complexity of ITU and ISO proposals The Internet development has proved that it is possible to do first and standardize later; incremental development Hence, some traditional ideas of software engineering such as the waterfall model are questionable when applied to protocol development Speed to the market is now a key factor for the success of a new technology B3: “Protocols and services are such complex systems that they require being fully specified before being implemented”

  10. False The integrated services network will be the Internet, enriched by: resource reservation mechanisms additional mobility mechanisms appropriate billing mechanisms additional security mechanisms ATM will be confined to the backbone In the end-system, ATM may still have a chance for some mission-critical applications (telemedicine, defense,...) B4: “The B-ISDN will be based on end-to-end ATM”

  11. Strengths of TINA Backed by many network operators and computer manufacturers Strong connection with the OMG (OMG TELSIG) Proposes an elegant solution to network and service management in a deregulated market Weaknesses of TINA Lack of clear added value to either network provider or equipment supplier Concerns about the maturity of base technology (CORBA performance: ?) Many services have already been provided over the Internet without a specific service architecture B5: “In order to cope with the complexity and diversity of the new services, with the need to integrated network and service management and with deregulation, a distributed, object-oriented platform is required” ==> TINA

  12. Architectural Separation of TINA Information network (based on CORBA) X X X Transport network (ATM) Information Network = kernel Transport Network (kTN) + set of applications

  13. X X X X Services with reservations A Possible Integration Network operator 1 Network operator 2 Billing, Management, VPNs, other sophisticated services IIOP IIOP To the ORBs of other stakeholders Information network (CORBA) Information network (CORBA) R R R R R R TransportNetwork Best-effort-services Best-effort services X X X X Services with reservations IIOP: Internet Inter-Orb Protocol

  14. Retailer IDL Third Party Service Provider IDL High-speed Network Interface If CORBA proves to be Successful... (maybe a simpler, Web-based interface would be enough here) Consumer IDL High-speed Network Interface IIOP Operated by the Telcos Information network (CORBA) Information network (CORBA) R R R R R R Best-effort services Best-effort services Services with reservations Services with reservations

  15. The things the TINA-C did right: explore the concept of service in all its generality base the architecture on an object oriented middleware (CORBA) try to integrate service provisioning and service management The things the TINA-C did wrong: consider for too long that ATM was the end to end support of the B-ISDN ignore for too long the Internet remain for too long a closed community of incumbent telcos not have a clear migration path from existing networks to the envisioned architecture Conclusion on TINA

  16. The proved capacity of the Internet to run multimedia services (including telephony...) dramatically changes the landscape for the Telcos The IN should survive, especially for the provision of voice services related to terminal mobility Network management requires further investigations and probably new paradigms Some fundamental TINA principles need to be revised A possible way to cope with the contradictory expectations (flexibility at the level of the Internet and availability at the level of the telecommunication services) is to split the WAN resources into 2 parts: One devoted to best-effort services The other one devoted to services with reservations These resources would be controlled by the Information Network Conclusion on Telecommunication Architectures

  17. In 2-3 years, a smart phone could feature: CPU: 200MHz RAM: 16 MB Hard disk: 1 GB Bandwidth: up to 1 or 2 Mb/s (IMT-2000, UMTS) Small screen: typically 600x200 pixels Keyboard and/or handwriting recognition and/or voice recognition (monospeaker is enough); voice recognition is local or on a server Such a smart phone could be the “mobile office” of the nomadic worker. Ideally, it should be able to roam in-building (WLAN, DECT), in small cells (DECT, GSM or CDMA), in large cells (GSM or CDMA) and in remote areas (satellite) The Integrated Services Digital Terminalis Wireless

  18. 1. The telecom (PSTN and cellular) and Internet networks will coexist for many years (hybrid network) 2. Hybrid services make sense and have a potential market 3. Mobile terminals will foster the development of hybrid services (“Integrated Services Digital Terminal”) 4. Speech synthesis and speech recognition will also fuel this development Assumptions for our Migration Scenario

  19. Service Creation in the Hybrid Network Service Creation Environment Java Service Layer (built up by assembling beans) API Internet Cellular Network PSTN (and N-ISDN) API: Application Programming Interface

  20. Service Creation (cont’d) Beans Archive 1. Identify a sufficient set of Beans Service Creation Environment Service Factory 2. Identify service components used by the Beans and map them onto physical resources Service Instance SC SC SC Controller Controller Controller Controller Java Service Layer CC/S1 CC/S3 CT/S1 CT/S3 CN/S1 CN/S3 CG/S1 CG/S3 3. Build the middleware Middleware Middleware Middleware Middleware Gateway Terminal Network Node Control Server CG/Si: Component on Gateway for Service #i SC: Service Component CT/Si: Component on Terminal for Service #i CN/Si: Component on Network node for Service #i CC/Si: Component on Control server for Service #i

  21. Why Java? • Pros: • Platform neutrality: increased portability • Object-orientation: increased re-usability • Simplicity: better garbage collection, no pointer manipulation nightmare • Multi-threading: a few lines for creating threads • Distribution: possibility for Java applets to interact with their home site • Dynamicity: use of servlets (“applets” executed in Web servers) • Security: still more secure than most widely used languages • Extensibility: sharing of Java packages among developers • Cons: • Performance: lesser than with other languages such as C or C++

  22. Service Modeling: A Way to Identify Components • A Service is composed of features, each of which is associated with an object model. Classes in the models are the sought components Key: Object class Service Customer Inheritance defines * Composition Association class sets Permission Feature interacts with involves User User Interaction Call control Charging Connectivity Security Address Translation

  23. End-system is a generic concept that embraces terminals, gateways, information converters, multipoint control units, etc. The user makes use of a device (e.g., a Smart Card) that has an address The user may have a higher level address (e.g., email address) The user can bind addresses with one another End-system Example: Address Translation End-system Device Address Info Converter Device Terminal Gateway has 1 1 * uses 1 Address Binding User Address 1 * manages Key: 1 Object class 1 has Device Address User Address * Inheritance User Address Composition Association class

  24. Example: IP Telephony with H.323 from ITU-T • Foundation for audio, video, and data communication over IP • Point-to-Point and conferencing • Products from VocalTec, Microsoft,… • Key technology for “New Telcos” IP Phone 2 IP Ph. H.323 Gateway IP Ph. Internet PSTN H.323 H.323 IP Phone 1

  25. Provision of Hybrid Services (Call Center, VPN,…) in a PSTN-Internet (H.323) Interworking Jar of beans Service Creation Environment Downloadable application PSTN IP Network Gateway

  26. Call Forwarding in a PSTN - H.323 Scenario Java Service Layer SCP H.323 GK IP Network H.323 GW Intelligent Network SSP SSP SCP: Service Control Point GK: Gatekeeper SSP: Service Switching Point GW: Gateway

  27. Trigger-Event-Source and Trigger-Event-Listener model Java Service Layer Network element Trigger-Event-Listener (implements methods to handle the events caught) Trigger-Event-Source

  28. Generic Information Flow fires goes to fires TriggerEvent CnxAttempt Event TriggerEvent Listener Event Source goes to goes to creates goes to ConnectionFactory ConnectionBinding CnxCompleteEvent creates fires fires Connection CnxFailEvent : Service component : Event

  29. Closed User Group in a PSTN - H.323 Scenario Java Service Layer Intelligent Network SCP CUGS IP Network H.323 GW MSC SSP SSP BSS G1 G1 G2 G1 G1 G1 G2 G2 GW: Gateway SCP: Service Control Point SSP: Service Switching Point BSS: Base Station System MSC: Mobile Switching Center CUGS: Closed User Group Server Gi: member of CUGi Functions provided by the Closed User Group Server: - Group management: create/delete group, add/remove user,… - Authentication and access control: according to the characteristics of each terminal, activate the appropriate procedures - Paging: retrieve where an end-user, member of the CUG, is located; based on this information, activate the appropriate terminal

  30. Teleinformation services, and in particular hybrid services, are going to play a major role for residential and business users Too little attention is devoted to the huge legacy of the telecommunication networks: these networks will continue to expand The telecommunication architectures need to be substantially revised in order to integrate the flexibility of IP networks In the presented proposal, services are being implemented in the different elements of the network: terminal, node, information server, control server, gateways By opening key elements of the network (notably SCPs and gateways), it is possible to provide a wealth of hybrid services Unlike TINA, this approach leverages on existing networks and mechanisms to gracefully introduce new services Conclusion

  31. For more information, see C. Gbaguidi, JP Hubaux, G. Pacifici, A. Tantawi:“An Architecture for the Integration of Internet and Telecommunication Services”,Technical Report TR 98/025, downloadable from http://sscwww.epfl.chOn the same Web site, see also “The Impact of the Internet on Telecommunication Architectures”, JP Hubaux et al., Computer Networks and ISDN Systems, Special Issue on Internet Telephony, December 1998, Technical Report TR 98/001 References

  32. CFP IEEE Communication Magazine

More Related