23-04-19

NGN related Standardization IssuesNGN related Standardization Issues(Architecture and Protocol)(Architecture and Protocol)

Chae-Sub, LEE

TTA 1 GSC-9, Seoul

SOURCE: TTA

TITLE: NGN for Global Generation (Architecture and Protocol)

AGENDA ITEM: 5.1

CONTACT: Chae-Sub, LEE, +8216 93200270, jaeseop@kt.co.kr

GSC9/GTSC-010

DOCUMENT FOR:

Decision

Discussion X

Information

GSC-9, Seoul

ContentsContents

1. Definition and Objective of NGN

2. Features of NGN

3. Architectural views of NGN

4. Protocol views of NGN

5. Discussion

GSC-9, Seoul 323-04-19

1. Definition and Objective of NGN

A Next Generation Network (NGN) is a packet-based network able to provide services including Telecommunication Services and able to make use of multiple broadband, QoS-enabled transport technologies and in which service-related functions are independent from underlying transport-related technologies. It offers unrestricted access by users to different service providers. It supports generalized mobility which will allow consistent and ubiquitous provision of services to users.

A Next Generation Network (NGN) is a packet-based network able to provide services including Telecommunication Services and able to make use of multiple broadband, QoS-enabled transport technologies and in which service-related functions are independent from underlying transport-related technologies. It offers unrestricted access by users to different service providers. It supports generalized mobility which will allow consistent and ubiquitous provision of services to users.

• To promote fair competition;• To encourage private investment;• To define a framework for architecture and capabilities to be able to meet various regulatory requirements;• To provide open access to networks,

• To promote fair competition;• To encourage private investment;• To define a framework for architecture and capabilities to be able to meet various regulatory requirements;• To provide open access to networks,

Objective

GSC-9, Seoul 423-04-19

2. Features of NGN

• Packet-based transfer• Separation of control functions among bearer capabilities, call/session, and application/ service• Decoupling of service provision from network, and provision of open interfaces• Support for a wide range of services, applications and mechanisms based on service building blocks (incl. real time/ streaming/ non-real time services & MM)• Broadband capabilities with end-to-end QoS and transparency• Interworking with legacy networks via open interfaces• Generalized mobility• Unrestricted access by users to different service providers• A variety of identification schemes which can be resolved to IP addresses for the purposes of routing in IP networks• Unified service characteristics for the same service as perceived by the user• Converged services between Fixed/Mobile• Independence of service-related functions from underlying transport technologies• Compliant with all Regulatory requirements, for example concerning emergency communications and security/privacy, etc.

• Packet-based transfer• Separation of control functions among bearer capabilities, call/session, and application/ service• Decoupling of service provision from network, and provision of open interfaces• Support for a wide range of services, applications and mechanisms based on service building blocks (incl. real time/ streaming/ non-real time services & MM)• Broadband capabilities with end-to-end QoS and transparency• Interworking with legacy networks via open interfaces• Generalized mobility• Unrestricted access by users to different service providers• A variety of identification schemes which can be resolved to IP addresses for the purposes of routing in IP networks• Unified service characteristics for the same service as perceived by the user• Converged services between Fixed/Mobile• Independence of service-related functions from underlying transport technologies• Compliant with all Regulatory requirements, for example concerning emergency communications and security/privacy, etc.

GSC-9, Seoul 523-04-19

3. Architectural views of NGN

TelephoneServices

DataServices(WWW,

e-mail, etc)

VideoServices

(TV, movie, etc)

TelephoneServicesNetwork

VideoServicesNetwork

DataServicesNetwork

Pre-NGN

Policy Area 1 Policy Area 2 Policy Area 3

Internet Protocol(IP)

Anything & Everything

Everything

Two Policy Domains

(Any & All Network technologies)

(Any/All Applicationse.g. voice , data , video)

ScopeOf

“Internet”

Services

Transport

Effect of IP into NGN Architecture

Break of Vertical Integrated Architecture

Horizontal Binding Architecture

Transport

Services

Telephone Services

Data Services (WWW, e-mail, etc)

Video Services (TV, movie, etc)

Point to point, Point to multipoint, Multipoint to multipoint

Point to point, Point to multipoint, Multipoint to multipoint

TransportPolicyArea

Content&

ServicesPolicyArea

GSC-9, Seoul

ApplicationServer

ApplicationServer

SwitchedCore

PacketNetwork(s)

SwitchedAccess

Network(s)

TransportProtocol

Interworking

SwitchedAccess

Network(s)

TransportProtocol

Interworking

Single pointOr

DistributedApplication

UsersUsers

Separation of Services from Network

GSC-9, Seoul

Migration ofService Intelligence

User

DomainCore

Domain

Access

DomainUser

Domain

Access

Domain

EdgeServiceNode

QoS awarecore

Best EffortCore

EdgeServiceNode

Fix/Mob.Acc. Net.

Fix./Mob.Acc. Net.

Re-Distribution of Service Intelligence : QoS, User Convenience etc.

QoS aware

Service Provision

GSC-9, Seoul

• The separation facilitates the unbundling of services and facilities

(in both access and core).

• Each vertical stratum of NGN has its own horizontal architecture.

• The location of service platforms is not restricted.

• Telecom industry will bifurcate to reflect the new NGN architecture.

• NGN architecture will facilitate competition and innovation among

service providers.

• Service intelligence will migrate to the edges.

• Telephone service will not follow the traditional centrex, local or

long distance approaches.

• Policy frameworks designed for vertically-integrated networks

are not transferable to a horizontally-integrated NGN.

• In an NGN, two separate policy frameworks are required:

- one applicable to transport networks, and

- another applicable to content-based services

• The separation facilitates the unbundling of services and facilities

(in both access and core).

• Each vertical stratum of NGN has its own horizontal architecture.

• The location of service platforms is not restricted.

• Telecom industry will bifurcate to reflect the new NGN architecture.

• NGN architecture will facilitate competition and innovation among

service providers.

• Service intelligence will migrate to the edges.

• Telephone service will not follow the traditional centrex, local or

long distance approaches.

• Policy frameworks designed for vertically-integrated networks

are not transferable to a horizontally-integrated NGN.

• In an NGN, two separate policy frameworks are required:

- one applicable to transport networks, and

- another applicable to content-based services

Impacts and Effects of NGN on Service Provision

GSC-9, Seoul 923-04-19

4. Protocol views of NGN

Protocol A

Protocol B

Protocol X

Service Mapping&

Protocol Translation

Peering Relationship

Layering Relationship

Service Mapping&

Adaptation

Protocol A

Protocol B

Protocol X

Service Mapping&

Protocol Translation

Peering Relationship

Layering Relationship

Service Mapping&

Adaptation

Principles of Protocol Relationship

GSC-9, Seoul

IP

Applications

Application Helpers (UDP, TCP, RTP, etc)

Non-IPServices

MPLS or shim Ethernet

Optical Bit Transport

(Optional)LANor

MAN

Simplified Protocol Model of NGN

Current protocol standards activity mainly focus on two aspects - one is how to use IP layer economically - the other is how to support IP layer efficiently

Current protocol standards activity mainly focus on two aspects - one is how to use IP layer economically - the other is how to support IP layer efficiently

GSC-9, Seoul

Physical Media

TransmissionConvergence

(downstream only)

MAC

Linksecurity

LLC/DIX

IP & ICMP

ARP

SNMP TFTP DHCPSecurity

Management

UDP

PPPoA

PPP

DSL

ATM

AAL5

LLC or VC Mux

Ethernet Ethernet

PPPoE

PPP

L2TP

PPP

IP

PPPoA IP/Eth PPPoE IP/AAL5 L2TPoA

PPPoA

PPP

DSL

ATM

AAL5

LLC or VC Mux

Ethernet Ethernet

PPPoE

PPP

L2TP

PPP

IP

PPPoA IP/Eth PPPoE IP/AAL5 L2TPoA

Broadband Protocol Model of Today

DSL Systems Protocol ModelCable Systems Protocol Model

GSC-9, Seoul

One of possible Fixed-Mobile Broadband Protocol Standards

802.16 Physical Layer

Transmission Convergence

Privacy

MAC

IPConvergence

ATMConvergence

EthernetConvergence

• Variable diversity in usage of Physical Medium• Convergence always request at the entrance of Networks and Services• End-End Protocol could be globalize

• Variable diversity in usage of Physical Medium• Convergence always request at the entrance of Networks and Services• End-End Protocol could be globalize

GSC-9, Seoul

5. DiscussionKey Mission of NGN

• Provide QoS aware services to End-End (any-where, any-time, any-device)• Provide Convergence : Fixed-Mobile, Telecom-Broadcasting etc.• Happy Business Model for Everyone : Balance btw. Growth and Share

• Provide QoS aware services to End-End (any-where, any-time, any-device)• Provide Convergence : Fixed-Mobile, Telecom-Broadcasting etc.• Happy Business Model for Everyone : Balance btw. Growth and Share

Questions after NGN

• Still Free charge / Fixed Rate / Free Riding…?• Still everybody use same quality services ?• Still I am only belong to public or I get my own private ?• Still separated subscription for Fixed and Mobile services ?• Still use separated Terminals for Fixed and Mobile ?• Still access separated contents for Fixed and Mobile ?• Still dominant operator control most of ?

• Still Free charge / Fixed Rate / Free Riding…?• Still everybody use same quality services ?• Still I am only belong to public or I get my own private ?• Still separated subscription for Fixed and Mobile services ?• Still use separated Terminals for Fixed and Mobile ?• Still access separated contents for Fixed and Mobile ?• Still dominant operator control most of ?

Ways to protect further difficulties

• Need Global Standard Collaboration• Common Vision, Common Requirements, Common Business Model Common Architecture and Common Protocols are basic to start

• Need Global Standard Collaboration• Common Vision, Common Requirements, Common Business Model Common Architecture and Common Protocols are basic to start

GSC-9, Seoul

Principles for further development of Architecture and Protocols

Principle 1The variation between protocol stacks should be reduced to a minimum.Principle 2The commonality between protocol stacks should be maximized.Principle 3Tunneling should be used “interwork” non-compatible network segments.Principle 4The protocol stack should be consistent with independent provision of any of peering points at any layer in the protocol stack.Principle 5The protocol stack should facilitate the provision of value-added services.Principle 6The protocol stack should facilitate access security.Principle 7The protocol stack should facilitate QoS provision (involving quantifiable and measurable levels of service).Principle 8The protocol stack should provide flexibility for mixing and matching different underlying physical media.

Principle 1The variation between protocol stacks should be reduced to a minimum.Principle 2The commonality between protocol stacks should be maximized.Principle 3Tunneling should be used “interwork” non-compatible network segments.Principle 4The protocol stack should be consistent with independent provision of any of peering points at any layer in the protocol stack.Principle 5The protocol stack should facilitate the provision of value-added services.Principle 6The protocol stack should facilitate access security.Principle 7The protocol stack should facilitate QoS provision (involving quantifiable and measurable levels of service).Principle 8The protocol stack should provide flexibility for mixing and matching different underlying physical media.