The IEEE P1520 - A presentation at OpenArch Conference, New York

1. The IEEE P1520 - A presentation at OpenArch Conference, New York • Jit Biswas IEEE P1520Application Programming Interfaces for Networks:An Introductionhttp://www.ieee-pin.org/ Kent Ridge Digital Labs, Singapore (Formerly: Institute of Systems Science) 27th March 1999

2. Outline • The problem domain and context • Open signalling • The IEEE P1520 project overview • P1520 Reference Model and its usage • Current status of P1520

3. The Problem • . • Signalling challenges arising from multimedia application/service demands • Multi-stream, multi-point, multi-media, high bandwidth, dynamic • Evolution of legacy telecommunication, data communications infrastructure towards broadband multimedia

4. Signalling Signaling functionality • . Multi-stream Multi-point Video Distribution Video Conferencing … ... … ... AIN INTERNET Call screening IN Call features # translation Call waiting Point to point POTS Transport Voice (64kbps) Data(Packets) Video (H261, MPEG...)

5. State of the Art • . Call routing, call set-up, LIJ, Dynamic QoS, ... Standard Node B Node A Signalling Stack Signalling Stack

6. Limitations • . • Lack of flexibility, variety • Leading to sub-optimal solutions • Slow in standardization (consensus) • Limiting the impact of new technologies (e.g., ATM) • Hard to extend • Limiting the growth

7. Need for Standardization • Agreement on Programming Interfaces • Allow signalling application developers to write software that runs on all opensig networks • All network equipment vendors to support BIB Signalling Applications Binding Interface Base Network “Hardware”

8. IEEE P1520 • “Application Programming Interfaces for Networks” or PIN • PAR approved on Dec 9, 1997 • Some major participants: • Columbia University, USA • Ericsson, Europe • KRDL (formerly ISS), Singapore • NEC Princeton, USA • Xbind Inc., USA • Nortel

9. Project Scope • To define the upper-edge and lower-edge of the BIB middle layer. • Target for ATM, IP, Telephony networks • Will not define new signalling protocols nor re-define existing signalling protocols • Co-existence and inter-operating with existing systems left as business and engineering decision by developers/users

10. V-Interface U-interface L-interface CCM-interface The P1520 Reference Model End User Applications Algorithms for value-added communication services created by network operators, users, and third parties Value-Added Services Level Algorithms for routing, connection management, admission control, etc. Network Generic Services Level Virtual Network Devices (Software Abstractions) Virtual Network Device Level Physical Elements (hardware, namespace) PE Level

11. CCM Interface An example of connection management using P1520 Interfaces . User host User Process U Interface CreateConnection (source, destination) host for R M connection getRoute factory Network Generic host for setupOp CF/ Services Level route manager CM setupOp setupOp setupOp Conn Destination Switch Control Switch Control agent Conn host Processor Processor Source agent host Conn Conn setupOp setupOp agent setupOp agent L Interface virtual switch Virtual Network virtual switch Device Level switch switch PE Level GSMP daemon GSMP daemon

12. Differentiated Services Scheduling Routing Algorithms Customized Routing Algorithms (e.g. Policy- based Routing) RSVP or Other per-flow Protocol Controller Routing table Hardware and other resources Mapping of P1520 Architecture to IP Routers/Switches Applications invoking methods on objects below U Interface L Interface Software representation of routing resources CCM Interface Data

13. Media Gateway Access • Signaling gateway between a telephony network and IP • Must incorporate SS7, POTS, IN architecture • MGCP, liaison with MSF

14. Relevant Efforts • MPEG 4 • Digital Storage Media - Command and Control, Multimedia Integration Framework (DMIF) • OMG Telecom Domain Task Force • CORBA-based Intelligent Network • MSF • VSI • MGCP • IETF - GSMP Working Group • IEEE - ETSI Liaison

15. Summary of P1520 • The project aims to define programming interfaces not algorithms • Standardize ‘horizontal’ interfaces instead of ‘vertical’ interfaces. • Promoting openness in signalling algorithms and control intelligence

16. P1520 - Brief History • Oct 5 1997 - First Pro-Tem WG meeting • Dec 9 1997 - Approval of PAR • Feb 12-13 1998 - First Official WG meeting at Columbia University • Apr 5-6 Second WG meeting at SF • Jul 27-28 Stockholm - Third WG meeting • Oct 7-8 Toronto - Fourth WG meeting • Jan 18-19 ‘99 Princeton - Fifth WG Meeting • March 28-29 ‘99 New York - Sixth WG Meeting

17. P1520 - Liaison Update • IEEE - ETSI Liaison • OSI MPEG 4 DMIF • IETF QGSMP Working Group • Multiservice Switching Forum

18. Membership Demography • 126 on mailing list for member@ieee-pin.org • North America 64 • Europe 42 • Australia 3 • Asia 17 • 30 attendees at Feb ‘98 meeting • 22 attendees at Apr ‘98 meeting • 15 attendees at July ‘98 meeting • 19 attendees at Oct ‘98 meeting • 27 attendees at Jan ‘99 meeting • 31 participants registered for March ‘99 meeting

19. P1520 - home page and aliases • http://www.ieee-pin.org • mailing lists: • member@ieee-pin.org • member-request@ieee-pin.org • Sub Working Group mailing lists: • pin-atm@ieee-pin.org • pin-ip@ieee-pin.org • pin-SS7@ieee-pin.org

22. Hardware Scenario

23. Software Scenario