Project JAMES January 1998

1
Project JAMES - January 1998
Mick Palfrey JAMES Operational Board Chairman
2
JAMES

• Network Services
• Network Management
• Network Performance
• Other Activities/Issues

3
JAMES Topology
4
XCs used by JAMES
Newbridge 36170 Alcatel A1000AX Siemens
EWSXpress Lucent AXC2000 GDC Apex Siemens
ATM-CC62 Cisco LightStream 1010 Fore ASX-200BX
Switches from 7 different vendors
5
Network Services Available

• CBR
• VBR
• IP over ATM
• SVCs
• LANE
• SMDS

6
Service Capability
Reykjavik
CBR (all) IP over ATM VBR SVCs Multicast
(ATM) SMDS LANE
Helsinki
Oslo
Finnet
Helsinki
Cop.
Telecom Finland
Dublin
Helsingborg
Amst.
Lon.
Koln
Br.
Lux.
Paris
Vienna
Zur.
Lisbon
Madrid
Milan
AIMS Workshop
7
SVC connectivity
Telecom Finland
Milan
8
Network Services not Achievedin JAMES Core

• ABR (local tests started)
• UBR (tests started)
• IP Multicast

9
Network Management

• Automated Reservation
• Electronic interchange of connection requests
• Xcoop
• as above but including Network Element Manager to
  configure end-end PVCs (where available)
• implementation and test schedule in place
  (experiments still ongoing)

10
Network Management (user)

• WEB based Management Tools
• Customer Management Interface (CMI)
• Customer connection requests, modifications etc.
• Network Status
• Link and/or Node outages

11
Network Performance

• Extensive testing of JAMES network performed
  against I.356 standard
• SVC set up delay measurements

12
Network Performance
Example
13
Network Performance
14
Network Performance
15
Network Performance
16
Other Activities

• User Traffic Profiling for VBR service
• IP over ATM using SVCs
• Network Planning/Dimensioning
• Security

17
VBR Overbooking Trial
18
Issues

• Most users have used CBR PVCs only
• TEN-34 MERCI use of advanced services
• Actual throughput of data connections has been
  less than requested.