An Intelligent Integrated Approach to Multi-Service

An Intelligent Integrated An Intelligent Integrated Approach to MultiApproach to Multi--Service Service

Residential Access NetworksResidential Access NetworksE. Scharf, P. Hamer, K. SmparounisDepartment of Electronic Engineering, Queen Mary, University of London (UK)

Wolfgang PayerInstitute of Communication Networks and Computer Engineering

(IND), University of Stuttgart (D)

John Ronan, Micheal CrottyThe Telecommunications Software Systems Group, Waterford

Institute of Technology

FITCE 2002 Intelligent Residential Access Networks

Slide 2

TORRENTTORRENT• TORRENT is an EU-Supported

Framework V project.• TORRENT is building a test-bed for

multi-service residential accessnetworks.

• With this system, home users will be able to choose, transparently, the most appropriate core transport network and physical access interfaces,

• … in order to meet their QoSexpectations for particular ranges and combinations of services.


Slide 3

TORRENT AimsTORRENT Aims

• Test BedTest BedTest BedTest Bed

for multi-service residential access networks.

• IntelligentIntelligentIntelligentIntelligent

control for the customer, NOs and SPs.

• TransparencyTransparencyTransparencyTransparency

in meeting a home user's QoS expectations.


Slide 4

TORRENTMain Contributions

byPartners

Arc

hite

ctur

eLA

P &

RG

+So

ftwar

eFi

eld

Tria

ls

1 Queen Mary & Westfield College UK2 Portugal Telecom P3 OTE Consulting GR4 Telenor N5 Tesion D6 Flextel I7 Intelsis E9 MultiComLab CH

10 Universität Stuttgart D11 Waterford Institute of Technology IRL

Man

agem

ent

Main WP


Slide 5

Intelligence in Intelligence in Residential Access NetworksResidential Access Networks

• The Challenge• A Way Forward• The Architecture• Service to Resource Management• Session Granularity• The Agent Approach• Field Trials• Conclusions


Slide 6

The ChallengeThe Challenge• Connection-Oriented Network - Services

– long holding times– few (e.g. two) parties in the call– low congestion tolerance– often - high QoS needs – often - and large data content

• Connectionless Networks - Services– high tolerance to congestion– non-critical QoS needs– low data content– multi-cast or broadcast

• A single integrated broadband comms network ?– unlikely to be the ideal solution for all types of services


Slide 7




Slide 8

A Way ForwardA Way Forward• A single physical access network

– access to many different core networks & service providers – range of different service and traffic types– connection-less AND connection-oriented transfer modes

• Advantage for the Customer– fosters simplicity

• Specifications for Customer– meet - in an optimal way - a user's service requirements– include QoS parameters for cell loss & delay statistics– include security, cost & availability

• Specifications for Operators– optimal bandwidth utilisation in access & core networks

• Technical Approach– put intelligence into access network


Slide 9




Slide 10

ArchitectureArchitecture

• Physical Architecture• Functional Architecture• Local Access Point• The Home Network• Division of Functionality


Slide 11

• Local Access Point (LAP)Local Access Point (LAP)Local Access Point (LAP)Local Access Point (LAP)• groups telecommunications, media and computing

technologies

• Residential Gateway (RG)Residential Gateway (RG)Residential Gateway (RG)Residential Gateway (RG)• connects home & access networks• has some intelligence• has a user interface

• CommunicationCommunicationCommunicationCommunication• between user, RG and LAP.

• SRM SoftwareSRM SoftwareSRM SoftwareSRM Software• architecture • communication between architectural entities• communication with the core network

Physical ArchitecturePhysical ArchitectureKey AspectsKey Aspects


Slide 12

RG

RG

RG

RG

IPIP

PSTNPSTN

ATMATM

home networks

core networks

core transfer modes

accesstransfer mode

LAP



Slide 13




Slide 14

linkIntracom RG

Driver Extensions

PH Extensions

RG LAP

IF Flextel Switch

Driver Extensions

PH Extensions

Proactive

Reactive

Support

Linux OS

Physical

API

PH HC

I

FIPA

-OS

API

PH HC

I

FIPA

-OS

Session/Call Control, Policy Enforcement

Negotiation, Strategy, Policy Creation

Functional ArchitectureFunctional ArchitectureFunctional ArchitectureFunctional ArchitectureFunctional ArchitectureFunctional ArchitectureFunctional ArchitectureFunctional Architecture


Slide 15

InfrastructureInfrastructure

RG LAP

• Local Access PointLocal Access PointLocal Access PointLocal Access Point– Flextel Switch Structure– ADSL Interfaces– Low Level Linux Extensions

• Residential GatewayResidential GatewayResidential GatewayResidential Gateway– RG Structure– ADSL Interfaces– ISDN - for POTS– Low Level Linux Extensions


Slide 16




Slide 17

LAP

Local Access PointLocal Access Point• Heart of TORRENT approachHeart of TORRENT approachHeart of TORRENT approachHeart of TORRENT approach• Physical AspectPhysical AspectPhysical AspectPhysical Aspect

– Computer Controlled Switching Fabrics– I/Fs to local loop technologies– I/Fs to core technologies– Can be channel to other LAPs

• Customer FunctionsCustomer FunctionsCustomer FunctionsCustomer Functions– Service Negotiation– Accounting– Security– Metering– Security Monitoring of Residential Devices– Activation of Residential Devices


Slide 18




Slide 19

Home Home NetworkNetwork

• StandardisationStandardisationStandardisationStandardisation– TORRENT equipment is based on a standard

protocol set (PS) being established for Linux. – Covers RG and the home distribution system.– Enables manufacturers to install standard

hardware and software interfaces on domestic equipment for its interconnection and control.

• Home NetworkHome NetworkHome NetworkHome Network– The home network may be built using

Ethernet, mains power lines or radio (e.g. HIPERLAN or Bluetooth) technology.

• Access Network Access Network Access Network Access Network –––– Local LoopLocal LoopLocal LoopLocal Loop– Copper-based ADSL strong contender – Baseline telephone service for emergency

situations in case of power failure.


Slide 20

The Home NetworkThe Home Network

residentialgateway

user control window• subscribe,• stop, start• modify/adjust• QoS

corenetwork

corenetwork

localaccess point

service &resource management

homedistribution system

accessnetwork

network topology & status


Slide 21




Slide 22

Distribution of Functionality Distribution of Functionality between LAP & RGbetween LAP & RG

• Bandwidth Bottlenecks – Minimise BBs between LAP and each RG. – Can use traffic shaping or priority queues.

• Processing Power – Concentrate in LAP– Cheaper to add processing power to the LAP than to the RG.– RG to be a simple-to-use, standard, low-cost device – Easier for authorised outside parties to update software in the LAP

• Challenge in shifting functionality from RG to LAP– LAP may be associated with 1,000 RGs, 1,000s of users, and

10,000s of information flows. – Performance drops sub-linearly with the scale of the task.

LAPRG

RGRG

?


Slide 23


• The Challenge• A Way Forward• The Architecture• Service & Resource Management• Session Granularity• The Agent Approach• Field Trials• Conclusions


Slide 24

Service to Resource Service to Resource ManagementManagement

• Key Features include ...– Changeable Per-service user-preferences– Tight state-full firewalls– Fine-grain monitoring

• Services– HTTP, VoD, VoIP

• Software Architecture– Agents, Databases

• Technical Issues– Decision Making– Packet Handling– Standards


Slide 25

Service to Resource Service to Resource FunctionalityFunctionality

• Choosing a Network Provider

• Housekeeping– service monitoring/control/management– accounting– user administration– technical administration

• Operational– RG Manager– software boot manager– packet handling


Slide 26

Agent FunctionalityAgent Functionality

• Proactive– Negotiation– Strategy– Policy Creation

• Reactive– Session/Call Control – Policy Enforcement

• Support– FIPA-OS Agent Platform RG LAP


Slide 27

Support FunctionalitySupport Functionality

RG LAP

• Support Layer– Applications Programming I/F– Human-Computer Interface– Packet Handling

• Linux OS– Packet Handling Extensions


Slide 28




Slide 29

Session GranularitySession Granularity

• Residential Gateway– Too coarse but easy to implement

• Online residential device– Should be straightforward

• User (login-id)– More challenging – need

authentication & accounting• Application Instance

– Not practical for now• User interface to an application

– Not practical for nowchal

leng

e IN

crea

ses

coar

sene

ss D

Ecre

ases


Slide 30

Login SupportLogin Support

• Computer Devices– Single login (e.g. Windows)– Multiple login (e.g. Linux)

• Media Devices– Single login– Multiple login


Slide 31




Slide 32

Intelligent Software AgentsIntelligent Software Agents

• Agents are software entities that:– act autonomously– are reactive - learn– are proactive - act & make decisions

independently of other agents– interact with other agents, other software

entities and humans

• Software Agents can:– be created & destroyed– be sociable, negotiate & travel (viruses?)


Slide 33

Negotiation & AuctionsNegotiation & Auctions

• Two-Party Negotiation– yield little and slowly– yield even-handedly– yield easily & quickly (submissively)

• Multi-Party Negotiation – Auctions– English (bid up)– Dutch (bid down)– Vickery


Slide 34

Why Use Agent Why Use Agent Technology ?Technology ?

• Flexibility– Distributed Control– Conceptually Scalable

• Standardised mechanism for s/w components– Standard I/Fs for developers & network providers– Location independence of components

• High-Level Abstractions– Agent platforms support “dialogues”.

Documentation & run-time enforcement of component inter working decisions.

– Agent model supports active objects

• Negotiation– Key feature of Agents and key to TORRENT– History of Successful Applications –

Routing, Provisioning, Accounting


Slide 35

Challenges for Agents?Challenges for Agents?

• Latency– Can be relevant for real-time activities agent

communication and scheduling

• Practical Scalability– A TORRENT LAP may have 1000 RGs connected,

and so could be running 1000s of agents

• Meeting the Challenge– Can use compiled JAVA, multiple processors &

careful design of agent system


Slide 36

AgentAgent--based Systembased System• Agents

– Customer Agents – represent interests of individual customers

– Trader Agents – represents offerings of network operators & service providers

– “Other” Agents – accounting, security, authentication, data-bases

• Horizontal Planes– Policy management – service level

agreements, data repositories– Control – protocols– User – user resources


Slide 37

residentialgateway

(RG)

multi-serviceaccess network

policy managertrader agent

policy managercustomer agent

policy managertrader agent

agentcommuni-cationlanguage(ACL)

localaccess point

(LAP)

LAP

policy managerQoS monitor agent

policy managerresource agents

integrated home

environment service provider ornetwork operator

service provider ornetwork operator

ACL

ACL


Slide 38

ImplementationImplementation

• FIPA Compliant Platform– e.g. FIPA-OS– create and delete– recommendations for communication

i.e. protocol and data formats

• JAVA– O-O Language– Libraries of Methods


Slide 39




Slide 40

Objectives of Field TrialsObjectives of Field Trials

• Does the TORRENT system– provide services to customers quickly and easily?– support the requirements of users, NOs and SPs?

• Metrics– timing– availability of resources– accuracy & precision of data– security and cost


Slide 41

Candidate ServicesCandidate Services

• HTTP - Internet Access• VOD – Video on Demand• VoIP – Voice over IP


Slide 42

Field TrialsField Trials

MultiComLab (CH)

Telenor (N)

PT Inovação (P)

Tesion (D/CH)

OTE Consulting (GR)


Slide 43

Field TrialsField Trials1. MultiComLab – Switzerland

– Functionality of LAP & RG – Communication between LAP & RG

2. Telenor – Norway - “House of the Future”– Residential Gateway & Home Network– Security

3. OTE Consulting – Greece– ADSL Scenario – Connection to ISPs

4. PT Inovação - Portugal– Integration of ADSL & Cable TV

5. Tesion - Germany/Switzerland– Connecting two LAPs across core networks


Slide 44




Slide 45

ConclusionsConclusions

• Intelligence– For the customer - intelligent control

over choice of appropriate SP and NO

• Service to Resource Mapping– Uses agent technology and IPv6

packet handling– Supports accounting and security


Slide 46

Thank you foryour attention !

Documents

An Intelligent Integrated Approach to Multi-Service