D1 - 04/10/2015 Present document contains informations proprietary to France Telecom. Accepting this document means for its recipient he or she recognizes

D1 - 21/04/23

Present document contains informations proprietary to France Telecom. Accepting this document means for its recipient he or she recognizes the confidential nature of its content and his or her engagement not to reproduce it, not to transmit it to a third party, not to reveal its content and not to use it for commercial purposes without previous FTR&D written consent.

confidential

An operator's view on NGN: commonalities and differences with the Internet

ITU-T Workshop on NGN – Geneva, 9-10 July

2003

Bruno Chatras (France Telecom R&D)

France Telecom R&D D2 - 21/04/23

Which Internet are we talking about ?

s Internet as a widespread multi-service technology (mainly based on IETF & W3C standards).

Or

s Internet as a fully open network of interconnected networks, and a philosophy where networks are almost dumb and where the intelligence resides at the edge.


Internet as a technology for the NGN

s Clear benefitsQLarge economies of scales due to the widespread deployment of the technologyQMulti-services technology -> Cost saving in both CAPEX and OPEXQCross-fertilisation of Internet services and telecommunication services naturally enabledQLarge community of application developers

s Barriers to carrier-grade deploymentsQAn overall architecture is missingQInteroperability between vendors is still a major issueQKey concerns not fully addressed (charging, service interactions...)


Internet as a philosophy for the NGN

s A good point: Forces the telecommunication industry to rethink the distribution of intelligence...

s But can’t be applied too literally: QThings that currently happen with the Internet, should no longer happen with the NGN! E.g. Call Forwarding activation status lost when a new software release is loaded on the end-user host.

QMost end users quickly tired of loading applications/patches themselves and/or troubleshooting problems. On the contrary, most users would pay for the complexity being handled for them...Today, people are ready to accept limited inconvenience because they have their PSTN line as a backup solution! This will no longer be true in case of full migration to the IP technology


From the Internet to the NGN

Internet Technolog

y

High speed access

Basic Operators

requirements

Managed IP

Networks

Next GenerationNetwork

sValued Added

ServicesBuilding Blocks

A significant effort in that direction has already been done by 3GPP and

PacketCable


Main operators’ requirements s NGN standards should build on IETF/W3C standards

to provide support for:

QNetwork ReliabilityQNetwork IntegrityQUser Privacy and data protectionQCharging and Usage meteringQSignalling Information Screening at network boundariesQEmergency Telecommunications, Lawful interception and other legal obligationsQSeamless interworking with legacy networksQEnd-to-end guaranteed QoS and bandwidth QGeneralized mobility accross access networks

Interoperability between network elements and network domains

AND


Interoperability: The danger sign is on!

s Increasing number of elements/interfaces involved in

the support and delivery of services

s Increasing number of competing protocols/variants

One of the key characteristics of the NGN is the availability of

open interfaces:

A major standardization effort is required to make the concept

a reality !


Interoperability Today: Too many tools for doing almost the same job !

s Controlling PSTN GatewaysQWhich base protocol? MGCP or H.248QWhich profile ? MSF, Q.1950, TGCP,...

s Accessing a user profileQDIAMETER (which application/AVPs ?)QLDAP (which information structure ?)

s Controlling access gates between IP networksQCOPS (which PIB structure ?)QSNMP (which MIB structure ?)QH.248 (which profile ?)

s ....


Interoperability: The SIP examples Lack of interoperability is known to be one of the major brakes on

large scale SIP deployments.

s Too many competing profiles are already available, with slightly

different scopes: Q.1912.SIP, 3GPP, MSF Profile, Packet Cable ,

ETSI TIPHON, ...

s The number of profile specifications should be kept limited (e.g. one per NGN service capability set)

s Profile specifications should be (at least) as precise as for

3GPP IMS(i.e. a list of supported methods and headers is not sufficient to ensure interoperability).

TO

DA

YTO

MO

RR

OW


From the Internet to the NGN

Internet Technolog

y

High speed access

Basic Operators

requirements

Managed IP

Networks

Next GenerationNetwork

sValued Added

ServicesBuilding Blocks


Intelligence at the edge or in the network?

Intelligence from the network where appropriate

The NGN View

Intelligence pushed at the

edge

The Internet View

Intelligence centralized

in the network

The Telephony View


Intelligence from the network where appropriate...

s QoS guaranteed multimedia session set-up

s Identification and Authentication

s Directory services / Address Book

s Presence and Availability Management

s Location Management

s Unified Messaging

s Secure payment

Even though answering machines

are cheap, network-based voice

messaging services are getting more

and more popular...

A major issue:

Service Interaction

Management


Service Interaction:An ever increasing complexity!

s Increasing number of service execution points QProxies, End User devices, Application Servers, Gateways, Media servers...

s Increasing number of service control mechanismsQInteractions between SIP-based services, between SIP-based services and IN or Parlay-based services, between SIP-based services and Web services...

s New actors involved in service creation QWeb application developers, 3rd party service providers, end users,...


Service Interactions

s A difficult issue, which has never been properly tackled by standards

s A major standardization effort is required to define basic mechanisms for handling: Qfeature precedence and feature compatibilityQinformation exchange between service features

s Such mechanisms should work in a highly distributed environment and should not be bound to a particular service control protocol or API.


Conclusionss The NGN will build on the Internet technology rather than

on its basic philosophy

s Technical roadblocks to provide carrier-grade services and enable operational deployments remain to be abolished

s To make the NGN a reality, standards are primarily required to:

QDefine an overall architecture that selects appropriate IETF/W3C building blocks, adds the missing pieces and the glue that

will bind them together to make a reliable and profitable network !QEnsure interoperability between major network elements and between network domains

Documents

D1 - 04/10/2015 Present document contains informations proprietary to France Telecom. Accepting this document means for its recipient he or she recognizes