Calypso Service Architecture for Broadband Networks 2 IN

Calypso Service Architecture for Broadband Networks 2 IN’ 97 Paris, September 2– 5 1997 Petteri Koponen, Juhana Räsänen, Olli Martikainen Laboratory of Telecommunications Software and Multimedia Helsinki University of Technology {Petteri. Koponen, Juhana. Rasanen, Olli. Martikainen}@hut. fi

Background • ATM and optical switching will increase the capacity of backbone networks. • x. DSL and wireless access technologies will provide the residential user with low-cost broadband connectivity. Þ Bandwidth becomes a commodity, which makes services the key success factor of the future broadband networks. • What are these services going to be?

Possible services • Internet access. • Distribution of broadband narrowband media streams (TV, radio, video conferencing, video on demand). • User mobility. Þ Networking requirements will remain heterogeneous. • What does all this require from the network?

Target scenario ? backbone network access network residential user ATM switch server ? control

How about the IN/ATM model? Plusses Minuses • Good support and • Heavyweight and rigid performance for streamsignalling that does not based data transfer. support heterogeneous services well (including • Based on international user mobility and IP). standards (although fairly complex ones). • Originally designed for dumb terminals, not set top boxes or PCs. Þ Too heavyweight and lacks flexibility.

Calypso architecture • Service-oriented. • Based on the Calypso network node that consists of three layers. • Allows flexible distribution of service logic between users, servers and network nodes. • Network node implementation is based on Java technology. SAk service agent SA 1 SA 2 . . . SAn Service Control Layer Network Control Layer Fabric Control Layer Calypso network node

Layers • Fabric Control Layer. – Manages the ATM switch (connection establishment, status queries, etc). • Network Control Layer. – Transfers control data and is responsible for end-toend connectivity. • Service Control Layer. – Executes and manages service agents. Provides an interface for resources of the network node.

Service agents • Java applications executed in network nodes by the SCL. • Responsible for service management. • Provide an interface to a specific service for service icons (SIs) executed in users’ set top boxes / PCs. • Operate the SCL directly. SA 2 SA 1 SAn SI 1 SI 2 SCL applications NCL FCL ATM/AAL

Distribution of service logic • Service Agents and Service Icons are used for flexible distribution of functionality. • Data transfer is provided by the NCL protocols. • Interfaces between agents and icons can be implemented using e. g. CORBA or Java RMI (Remote Method Invocation). • Icons can be implemented as Java applets.

Implementation • Network node: Linux Pentium and Frame Synchronized Ring ATM switch. • FCL: for example, Ipsilon’s GSMP. • NCL: Linux IP stack + RSVP-based connection management mechanism. • SCL: implementation with Java due to its support for code mobility and IP. Þ Java, IP and existing code enable rapid service development and prototyping.

Example: stream distribution nel chan viewer SI channel manager SA SCL MW ct sele launch s est requ STB / PC infrared remote control channels

Summary • Minimum statically defined functionality in the network node; the rest is defined by services. • Support for several service and control architectures simultaneously. • Flexible distribution of service logic between network nodes, users and servers. • Gaining experience by prototyping future services.