Calypso Service Architecture for Broadband Networks

1
Calypso Service Architecture for Broadband
Networks

• 2IN97Paris, September 25 1997Petteri Koponen,
  Juhana Räsänen, Olli Martikainen

Laboratory of Telecommunications Software and
MultimediaHelsinki University of Technology
Petteri.Koponen,Juhana.Rasanen,Olli.Martikainen_at_
hut.fi
2
Background

• ATM and optical switching will increase the
  capacity of backbone networks.
• xDSL 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?

3
Possible services

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

4
Target scenario
backbone network
access network
residential user
ATM switch
server
control
5
How about the IN/ATM model?
Plusses
Minuses

• Good support and performance for stream-based
  data transfer.
• Based on international standards (although fairly
  complex ones).

• Heavyweight and rigid signalling that does not
  support heterogeneous services well (including
  user mobility and IP).
• Originally designed for dumb terminals, not set
  top boxes or PCs.

Þ Too heavyweight and lacks flexibility.
6
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.

SA1
SA2
SAn
...
Service Control Layer
Network Control Layer
Fabric Control Layer
SAk
Calypso network node
service agent
7
Layers

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

8
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.

9
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.

10
Implementation

• Network node Linux Pentium and Frame
  Synchronized Ring ATM switch.
• FCL for example, Ipsilons 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.

11
Example stream distribution
channel manager
channel requests
SA
viewer
SCL
launch
MW
SI
select
channels
STB / PC
infrared remote control
12
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.