SBC in NGN Architectures

Jonathan Cumming

SBC in NGN Architectures

NGN Standardisation
3GPP, ETSI, ITU, MSF

Evolution of SBC in IMS architecture

Deployment options

Remaining areas for standardisation

Copyright 2006 Data Connection Limited All Rights Reserved.

NGN Standardisation Process

Many organisations defining Next Generation Network

Standards Bodies

Industry Forums
Standards

Implementation Agreements
Trials and Interop Events

Requirements
Copyright 2006 Data Connection Limited All Rights Reserved.

3GPP Third Generation Partnership

Program

Standardization body for GSM mobile

Incorporated IMS in Release 5

Focused on 3G mobile phones
Centrally managed
Bandwidth plentiful except in radio access network

P-CSCF provides some SBC features on UNI

Access control
Enforces routing

Release 7 (in development) adds more SBC features

Support for fixed-line and legacy equipment
Non-IMS endpoints, e.g. PBX, Legacy Protocols
IPv4

Topology hiding, NAT and Access control on NNI

Copyright 2006 Data Connection Limited All Rights Reserved.

ETSI TISPAN

Charged with developing new architecture

for fixed telephony networks

Adopted IMS as underlying architecture

Extending/adapting IMS for requirements of fixed networks

TISPAN R1 requirements part of 3GPP Release 7

Planned releases
R1 (2005) Focused on DSL access
R2 (2007) Improved control of access resource usage
R3 (2009) Adds support for roaming (nomadicity)

Copyright 2006 Data Connection Limited All Rights Reserved.

ITU-T

Overarching architecture for NGN

Coordinated by SG-13

Working closely with ETSI, 3GPP and IETF

Also concerned about Internet use

End-to-end QoS without central control, i.e. no SBC

Copyright 2006 Data Connection Limited All Rights Reserved.

MSF

Promotes deployment of open and

interoperable equipment
Develops interoperability agreements reusing existing standards
where possible
Organizes interoperability events

MSF Architecture is based on fixed-line carrier requirements

Bandwidth management within the core
Migration of legacy services
NAT

Release 2 Architecture contains Session Border Gateway

Security
NAT
Access Control

Release 3 (in progress) migrates to IMS-based core

Copyright 2006 Data Connection Limited All Rights Reserved.

Evolution of SBC function

P-CSCF provides

Security

Protocol Conversion

Access Control

Legacy Devices

Routing
Control

Peering Control

IPv4 / NAT

3GPP
R5/6

Internet

No borders

SIP

IBCF adds

3GPP
R7

IMS still lacks

Core Bandwidth
Management

Explicit MPLS/VPN
support

SBG provides

Security

Access Control

NAT

MSF
R2

Migration to IMS core

MSF
R3

Copyright 2006 Data Connection Limited All Rights Reserved.

Evolution of SBC in IMS Architecture

IETF SIP

IMS R5/6

IMS R7

AS
S-CSCF
Proxy

S-CSCF
Proxy

P-CSCF
Proxy
PDF
UE

GGSN

P-CSCF
Proxy
IBCF

IBCF

TrGW

TrGW

SBG-NE

GGSN

UE

SBG-NC

Copyright 2006 Data Connection Limited All Rights Reserved.

Each architecture gives SBCs different

names

Network Edge

Network Core

Access (CPE)

MSF R2

TISPAN R1

IMS

S-SBG-NE

C-BCF

P-CSCF

D-SBG-NE

C-BGF

GGSN / BAS /
PDG

S-SBG-NC

I-BCF

IBCF

D-SBG-NC

I-BGF

TrGW

S-SBG-CE

A-MCF

Out of scope

D-SBG-CE

A-MGF

Copyright 2006 Data Connection Limited All Rights Reserved.

10

Deployment options

Some SBC function covered by IMS architecture

Real SBCs may incorporate additional function

CAC (off-loading work from S-CSCF)
Transcoding
Gateway function e.g. Protocol interworking
Firewall and NAT traversal (where not handled by CPE)

SBC function may be built into other devices

Routers providing media SBC function
Softswitches incorporating all CSCF and SBC signaling
functions

Copyright 2006 Data Connection Limited All Rights Reserved.

11

Areas for further standardisation

IMS assumes plentiful core network resources

SBC function needs interfaces to central Bandwidth Manager

S-CSCF
IBCF

P-CSCF
BM
UE

GGSN

TrGW

SBG-NE

SBG-NC
Copyright 2006 Data Connection Limited All Rights Reserved.

12

Areas for further standardisation

Policy configuration
Complex and only partially standardised

IBCF

BM

TrGW
Copyright 2006 Data Connection Limited All Rights Reserved.

13

Summary

Border Control is a requirement for carrier service

An SBC is a device that provides the set of functions

needed at the border

These functions are now appearing in IMS and other

standard architectures
This work is ongoing
Competing pressures for features

An SBC is not always a separate device

Parts of the function can be implemented by other devices:
edge routers, access network or softswitch

Copyright 2006 Data Connection Limited All Rights Reserved.

14

Data Connection (DCL)

Software technology since 1981

Portable network protocols
VoIP: SIP, MGCP, Megaco, SBC
MPLS, VPNs, IP Routing, ATM

Messaging / Directory / Conferencing

MetaSwitch

Private and consistently profitable

Revenue and Earnings

Effectively owned by employees

People
~20 recruits from ~3000 applications
Attrition rate <3%
Number of Employees

Copyright 2006 Data Connection Limited All Rights Reserved.

15

Thank you for listening

Jonathan Cumming
jonathan.cumming@dataconnection.co
m