NGN Work in ITU-T SG11NGN Work in ITU-T SG11

2004.5.11

Yukio Hiramatsu

Chairman of ITU-T SG11

1 GSC-9, Seoul

SOURCE: ITU-T

TITLE: NGN Work in ITU-T SG11

AGENDA ITEM: 5.0

CONTACT: Yukio Hiramatsu, hiramatsu.yukio@lab.ntt.co.jp,

Tel. +81-422-59-7061, Fax. +81-422-59-5561

GSC9/GTSC_005

GSC-9, Seoul2

OutlineOutline

• Major achievements during the current study period• NGN activities in SG11• New Questions of SG11 for the next study period• Work programme for NGN signalling requirements

and protocols• Draft Technical Reports on NGN• Draft Technical Report on IP QoS• Possible work on security

GSC-9, Seoul3

Major achievements during the Major achievements during the current study periodcurrent study period

• IN work completed with approval of CS4 (Interworking with IP) (Q.124x-series)

• BICC CS2 (support of IP bearer) approved. BICC CS3 (further enhancement) progressed. (Q.1902-series, etc.)

• Support of International Emergency Preferential Service (IEPS) step1 approved. (Amendments to the existing ISDN, B-ISDN, SS7 and BICC protocols)

• Interworking between SIP – BICC/ISUP CS1 approved. (Q.1912.5)

• ATM over MPLS signalling progressed. (Amd Q.2920)• Interworking between AAL2 signalling CS3 and IP control

signalling progressed. (Q.263x-series)• NGN related protocol work has been started.

GSC-9, Seoul4

NGN activities in SG11NGN activities in SG11

• Two brainstorming sessions (Feb 2002 and Nov 2002 SG11). • Initial idea for Draft 3 new Questions (Nov.2002 SG11).• TRQs identified at the NCAP Rapporteurs meeting in Paris

(April 2003)• Draft 3 new Questions developed (Sep 2003 SG11).• Work programme updated (March 2004 SG11). • Set of new Questions for the next study period (March 2004).• Existing Questions have been studying NGN related issues.

– Q.1/11 (Requirements for IP and IN based services) Draft TRQs.– Q.4/11 (API requirements) Q.supp.40, 48– Q.7/11 (IP telephony requirements) Q.supp.49 (TRQ.2840)– Q.8/11 (QoS requirements) Draft TRQ.

GSC-9, Seoul5

Draft new Draft new QuestionsQuestionsQ Title

AA Network control functional architectures in emerging NGN environment

BB Application control and signalling requirements and protocols

CC Session control and signalling requirements and protocols

DD Bearer control and signalling requirements and protocols

EE Resource control and signalling requirements and protocols

FF Assistance in preparation of handbooks for the deployment of packet based networks

GG Control architecture, requirements and protocols to support user nomadicity and mobility in NGN environments

GSC-9, Seoul6

Work programme for NGNWork programme for NGN

Reference Title

TRQ.NCAP1 High level functional requirements for Packet-based network control architecture

Q.NGN-NCA Network control architecture

TRQ.NCAP2 Gate control protocol requirements

TRQ.NCAPX Session control protocol requirements

TRQ.NGN-STM

Service Triggering Mechanisms in SIP environments

GSC-9, Seoul7

TRQ.NCAP1TRQ.NCAP1

Core Network

Access Network

Access Network

Customer Premises Network

Customer Premises Network

User

User

Scope of NGN

CATV network, ADSL/VDSL, fiber network, RITL (Radio in the loop), satellite and wireless network.

Telecommunication network, PSTN, N-ISDN, B-ISDN provided by carriers.

CPN comprising access unit, TV, PC, phone, wireless phone

GSC-9, Seoul8

High level functional requirementsHigh level functional requirementsExtract from TRQ.NCAP1:• Addressing, Naming and Directory Services features• User Profile Management• Terminal Management• Handling of Various Communication Patterns• Mobility Management and Nomadism• Multi-level Quality of Service Support • Security• Network Integrity• Service Creation• Failure Avoidance and Recovery Including from Congestion

and Failure (Network Reliability)• Public Safety (ETS/TDR)• OA&M Related Functions (Usage Control & Management)• Content Delivery Optimisation

GSC-9, Seoul9

Q.NGN-NCAQ.NGN-NCA• Description of various service control architecture

options in the context of a SIP-based Next Generation Network

• 2 scenarios for SIP server with abstract call state machine and trigger processing (INAP based and OSA/Parlay based)

• 4 scenarios for SIP server with trigger processing and without abstract call state machine (INAP based, OSA/Parlay based, full SIP and hybrid)

• Scenario for SIP server without trigger processing nor abstract call state machine

GSC-9, Seoul10

Some scenarios in Q.NGN-NCASome scenarios in Q.NGN-NCA

SIP signalling entity

Abstract Call State MachineCCFSIP SIP

Service access manager

SSF

Service Execution Environment

Service Logic ProgramSCF

INAP

SIP signalling entity

Service Access Manager

SIP signalling entity

SIP signalling entity

Service Execution Environment

Service Logic Program

SIP SIP

AS

SIP

Full SIPSIP-IN direct access

GSC-9, Seoul11

Signalling requirements for gate Signalling requirements for gate control interfaces (TRQ.ncap2)control interfaces (TRQ.ncap2)

IP Core NetworkIP Access Network GW GW IP Access Network

Session control signalling

Gatecontroller

Gatecontroller

Session

contro

l signallin

g

Session control signalling

GSC-9, Seoul12

Signalling requirements for NGN session Signalling requirements for NGN session control (TRQ.ncapx)control (TRQ.ncapx)

Bearer Level

ACSF SCSF SCSF ACSF

UNI UNI

NNI

NGN-SCF

These may be collocated in a single physical entity.

Access Domain Access DomainCore Domain

ACSF:NGN-SCF:

Access server functionNGN session control protocol

SCSF: Service call server function

GSC-9, Seoul13

Work on IP QoSWork on IP QoS

• QoS is one of the most important features in NGN signalling.• Draft TRQ.IPQOS.SIG.CS1 is under development in SG11.• Scope expanded to include both “On-path” and “Off-path”,

and to include various underlying technologies other than MPLS.

• Mr. Wei Feng (Huawei Technologies, China) has been nominated as Rapporteur on Q.8/11 dealing with QoS signalling in this study period.

• Interim Rapporteur meeting has been scheduled in July (in Shenzhen) with kind invitation by China members.

GSC-9, Seoul14

Possible work on securityPossible work on security

• Requirements for secured communication interface between PSTN and VoIP networks

• Analysis and examination of protocols and system interaction such as, but not limited to: SignTran, SS7, IPSec, H.248/Megaco, and SIP.

• The end result may be enhanced protocol specifications with additional security measures as well as raising awareness of industry best practices.

• Draft Recommendation X.805 - Security Architecture for Systems Providing End-to-End Communication be used as a sample tool for protocol security evaluation

GSC-9, Seoul15

Security requirements for NGNSecurity requirements for NGN

PSTN

Internet

NGN

ISDN

Private Networks

Trusted Networks

Secure operating concept

Untrusted Networks

Secureinterworking