1heechang@nca.or.kr, jkchoi@icu.ac.kr

Which Standards are needed toward Future Wireline and Wireless IP Network ?

Hee Chang Chung, Jun Kyun Choi

heechang@nca.or.kr, jkchoi@icu.ac.kr

2heechang@nca.or.kr, jkchoi@icu.ac.kr

Contents

Technical Aspects for NGN QoS for NGN Architectural Requirements for NGN IPv6-based Control and Management Architecture

of NGN Harmony between E.164 and IPv6 Address Conclusion

3heechang@nca.or.kr, jkchoi@icu.ac.kr

Technical Aspects for NGN – 1 Service and Application Aspects

Acceptable migration of Data, Voice, Audio, Video and TV Broadcast

Terminal/User/Service Mobility Billing according to SLA and Traffic Monitoring

Network Architecture AspectsManageable and Reliable Internet Separation of User-Plane and Control-/Management-

plane

4heechang@nca.or.kr, jkchoi@icu.ac.kr

Technical Aspects for NGN – 2 Routing and Packet Forwarding Aspects

Network Intelligence using State InformationForwarding Control

Differentiated QoS Class Differentiated Resource Allocation at Switch and

RouterQoS Negotiation at Global Network Domain

5heechang@nca.or.kr, jkchoi@icu.ac.kr

Quality of Service for NGN

6heechang@nca.or.kr, jkchoi@icu.ac.kr

TE Mechanisms for Providing QoS Reservation based (e.g., Connection-Oriented,

ATM) Admission control Dynamic resource reservation Congestion control ATM, LDP/CR-LDP

Reservation-less (e.g., Connectionless, IP) Traffic classification Priority based treatment Differentiated Service

7heechang@nca.or.kr, jkchoi@icu.ac.kr

How to provide QoS/NP Admission Control for Call, Connection, Flow, or Packet

User aspects : Select dynamically for their preferences and application types

Provider aspects: Guarantee the minimum, offer the average QoS Bandwidth Allocation

User aspects : Select dynamically based on acceptable billing Provider aspects: network performance according to Service and traffic clas

sification Buffer Management and Scheduling Algorithm

Provider aspects: Buffer separation per virtual channel or per flow and scheduling algorithm according to service priority

Converge between CO-TE and CL-TEAnswer

8heechang@nca.or.kr, jkchoi@icu.ac.kr

Architectural Requirements for NGN

9heechang@nca.or.kr, jkchoi@icu.ac.kr

Technical Problems for NGN Architecture - 1 How to implement and manage network state information ? Uniform architecture for naming, addressing and routing is

possible ? How to apply layer concepts of U-/C-/M-plane ? Can we divide user flows and application types depending o

n network resource boundary or domain ? How to join each specific division and domain ?

Could the user control (including join and leave) their boundaries ? Where is the security boundary or differentiated QoS boundary ? How to give fairness and how to solve congestion at each domain ? Where is the boundary of network management ?

10heechang@nca.or.kr, jkchoi@icu.ac.kr

Technical Problems for NGN Architecture - 2 Domain or Boundary Concepts for Single/Multiple

Specific Capabilities of NGN According to geographical area or logical VPN group According to flow class and service priority According to resource allocation and resource usage rules According to management domain of specific protocol According to ownership and administration domain According to security boundary According to naming, addressing, and language

11heechang@nca.or.kr, jkchoi@icu.ac.kr

Technical Requirements for NGN Architecture - 1

General Requirements of NGN Architecture Interworking

Existing networks must be interconnected Robustness

For loss of networks Heterogeneity

Consider a variety of networks including broadcast, satellite, and wireless/radio network

Distributed Management Permit distributed management of its resources

Ease of Attachment Permit host attachment with a low level of effort

Accountability Resources must be accountable

12heechang@nca.or.kr, jkchoi@icu.ac.kr

Technical Requirements for NGN Architecture - 2

General Requirements of NGN Architecture (continued) Mobility

User/Terminal/Service mobility, network mobility Policy-driven Network Management Intelligent Network/User Configuration Resource Allocation Rule

Ability to allocate capacity among users and applications based on the acceptable charging

Resources are highly variable over short time scales For operational and governmental activities (i.e, emergency), it

allocate the resource capacity based on priority Prioritized reservation at on-demand time or reservation time

13heechang@nca.or.kr, jkchoi@icu.ac.kr

IPv6-based Control and Management Architecture of NGN

14heechang@nca.or.kr, jkchoi@icu.ac.kr

IPv6 Performance Issues - 1 Data Transfer Performance

IPv6 Basic Header Processing Time Flow classification by traffic class and flow label, Hop Limit, etc.

Not acceptable at the existing IP router architecture Next Header Processing Performance

Hop-by-Hop Options header (mainly urgently changing, alerting or diverting user flows)

Destination Options header (transit) Routing header (for tunneling or changing the intermediate forwarding path) Fragment header Authentication header Encapsulating Security Payload header Destination Options header (final) Upper-layer header (TCP/UDP, etc.)

15heechang@nca.or.kr, jkchoi@icu.ac.kr

IPv6 Performance Issues - 2 Switching or Routing Performance

Done only by IPv6 addresses (or by flow label) Done both by IPv6 addresses and flow label

including IPv6 address (only routing prefix) including whole IPv6 address including EUI-64 identifier

Forwarding Performance for Mobile Users Handle Both Logical Address (e.g., Care-of-Address) and Ph

ysical Address (e,g, Home Address) at any time Look-up logic of forwarding table How to handle FA and HA functions including registration, a

dvertisement as well as tunneling

16heechang@nca.or.kr, jkchoi@icu.ac.kr

IPv6 Performance Issues - 3 Control and Management Performance

Independent on data transfer performance Sensitive to the hand-over performance for mobility on the

forwarding look-up table What are the specific applications to tightly align control

performance to user data transfer performances ? Security processing at the same data plane ?

17heechang@nca.or.kr, jkchoi@icu.ac.kr

Harmony between E.164 and IPv6 Address

18heechang@nca.or.kr, jkchoi@icu.ac.kr

Benefits to align Address Structure National administrative boundary on IPv6 address structure Easy conversion between Telco address and IPv6 address Utilize the existing Transport Infrastructure for IPv6 Easy Binding of Telco address at the IPv6 DNS Integration of Telco-based services and IP-based application

s (i.e, VoIP, mobile phone, etc.)

19heechang@nca.or.kr, jkchoi@icu.ac.kr

How to Harmonize ? How to get a Harmony between E.164 and IPv6

Step-wise migration of E.164 address and IPv6 address based on naming and directory service concept

Integration of Existing Telephony, ISDN, Cellular Address, IMT-2000 address, and ATM address

Dynamic address binding for User/Terminal/Service Mobility

20heechang@nca.or.kr, jkchoi@icu.ac.kr

A way to harmonize between E.164 and IPv6

sitetopology(16 bits)

interfaceidentifier(64 bits)

publictopology(45 bits)

interface IDsubnetNLA*TLA001

SubaddressSNNDCCCAFI

1 to 3 digits

Max (15-n) digits

15 digits (8 octets)

1 octets

64 bits (8 octets)

21heechang@nca.or.kr, jkchoi@icu.ac.kr

Conclusion

Next GenerationNetwork

Today(Pessimistic)

Today(Optimistic)

ITU-TITU-R

Global

Regional

SDOs

Tomorrow