NGN standardization activities in ITU-T

advertisement
NGN standardization activities in ITU-T
- Global interoperability for NGN deployment -
Kaoru Kenyoshi
Vi
Vice-chairman
h i
off ITU
ITU-T
T SG11
NEC Corporation
13 September 2010
1
Contents
1.
2.
3.
4
4.
Introduction
Current status on NGN
standardization & Future Direction
Activities to improve interoperability
Conclusion
13 September 2010
2
Contents
1.
2.
3.
4
4.
Introduction
Current status on NGN
standardization & Future Direction
Activities to improve interoperability
Conclusion
13 September 2010
3
Relationship of NGN Standard Organizations
Global Standard body
y
Final discussion to set
global standards
Regional Standard body
Adopting IMS into NGN
making consensus in Asian
region before ITU-T
Supporting TISPAN in
NGN standardization
CJK&ASTAP
De-facto Standard in industry
Developing
l i
IMS for
f
3G
network
Developing
p g IP&SIP
FG-NGN (Focus Group on NGN)
13(Alliance
September
2010
ATIS
for Telecommunications
Industry Solutions)
TIA(Telecommunications Industry Association )
ETSI (European Telecommunications Standards Institute),
4
CJK (China, Japan, Korea)
IETF (The Internet Engineering Task Force)
Vigorous activity to standardize NGN
• Since 2003, a study group dedicated to NGN has been organized in
each standards body.
• The 2nd release documents were prepared by ITU-T in 2009.
Invented “SIP” for
voice and video
communication on
the Internet
Supports TISPAN and focuses
on filling the gaps and
promoting implementation (IP
interoperability, triple play)
Final discussions
to create global
standards
CJK
Is the pioneer in studying
all-IP networks, and has
completed
p
“IMS” for
mobile
SIP:
Session Initiation
13 September
2010 protocol
TISPAN leads global
discussions on NGN, and
adopted
p
IMS for fixed
IMS: IP Multimedia Subsystem
Rich experience in VoIP
and broadband, which
helps
p g
generate
consensus in Asia
5
Timeline of NGN Standardization
• Thirteen ITU-T recommendations about NGN basic concepts were published in Jul. 2006.
• In Jan. 2008, the core part of NGN Release 1 was completed for practical purposes.
• NGN specific services, such as IPTV, FMC, etc., are being discussed now.
2003
2004
2005
2006
NTT’s NGN
ITU-T
SG
13
SG
11
▲NGN
Workshop FG-NGN
(Jul. 2003) (2004/5-2005/12)
Service
requirements
and
q
architecture
Concept
Co cep
2007
Field trial
13 September 2010
IETF
Release 1
▲SIP standard RFC3261
(Jun. 2002)
Signaling
protocols
Release 2
End of 2003~early 2006
~ end of 2004
Future
Network
Release 2
Release 1
Release 6
Mar 2008
Mar.
2008~
FG-IPTV
(2006/4-2007/11)
Signaling protocols
3GPP
2009
Commercial service
Dec 2006 ~
Dec.
Structure
ETSI TISPAN
2008
Release 7
~ mid 2007
Release 3
Early 2006 ~ mid 2008
Common IMS
Release 8
~ end of 2008
6
NGN capability set 2 (Y.2007)
• At Sept.
Sept 2009,
2009 in addition to session
session-based
based basic communication services which
were summarized in Y.2006, ITU-T Recommendation Y.2007 was established for
providing IPTV basic service (linear TV and VoD).
• A capability set Recommendation specifies ITU-T Recommendations and
standards of other SDOs to realize some specific services.
Scope of Y.2007 (Extracted major documents from 155 docs in Y.2007)
Services
Stage 1
(Requirements)
Stage 2
(Architecture)
Stage 3
(Signaling)
Note
Basic
telecommunicat
ion services
(Ph
(Phone,
Vid
Video
phone,
Conference,
etc)
Y.2201 (NGN
Requirements)
Y.2262 (PSTN
Simulation)
Y.2701 (Security)
Q.1706 (Nomadism),
etc
Y.2012 (NGN
architecture)
Y.2021 (IMS)
Y.2111 (RACF)
282.007*1 (IMS), etc
Q.3300series (RACF)
Q.3401 (NNI)
Q.3402
Q
3 0 (UNI)
(U )
283.003*1 (IMS), etc
Y.2006
(NGN
capability
set 1)
IPTV basic
service (Liner
TV and VoD)
over NGN
Y.1901
Y
1901 (IPTV
requirements)
G.1080 (QoE
requirements)
X.1191 (Content
protection)
Y.2236 (Multicast), etc
Y.1910
Y
1910 (IPTV
architecture)
Y.2017 (Multicast)
H.622.1 (Home network)
H.721 (Basic terminal),
etc
H.750
H
750 (Metadata)
H.762 (LIME)
H.770 (Service
discovery)
RFC2326*2 (RTSP), etc
IPTV-FJ
IPTV
FJ
specificati
on shown
in
underline
13 September 2010
7
New functional architecture (Y.2012)
SNI (Service
Network Interface)
ID management
functions based
on Y.2720
Content delivery
functions for IPTV
Upgrading
Upgrading NACF
NACF(Y
NACF(Y.2014)
and RACF
2014)forand
RACF(Y.2111)
FMC and IPTV
for
FMC and IPTV
13 September 2010
Mobility
management and
control functions
(Y 2018) for FMC
(Y.2018)
8
Strategic direction for the future
Remaining enhanced network related capabilities
Transport control capabilities: Mobility, Multicasting and
QoS control over interworking
Networking capabilities: Ad-Hoc Networks, DSN, Multiconnection and Ubiquitous Networking
Security related: Support of IdM and DPI (Deep Packet
I
Inspection)
ti )
Service related capabilities
Service support: SIDE (Service Integration and Delivery
E i
Environments)
t )
Provider support: OSE (Open Service Environment), Mobile
IPTV and Web based IPTV
Continue to develop Testing Specification:
From methodology, testing model, architecture to detailed
service testing such as VOIP service.
Monitoring parameters set becomes the important part for
NGN testing and interoperability.
13 September 2010
9
GSC15-GTSC8-05 ITU NGN,Testing specification and Beyond
Contents
1.
2.
3.
4
4.
Introduction
Current status on NGN
standardization & Future Direction
Activities to improve interoperability
Conclusion
13 September 2010
10
Resolution 76 approved in WTSA08
Studies related to conformance and
interoperability testing, assistance to
developing countries[1], and a possible
f t
future
ITU Mark
M k programme
(Johannesburg, 2008)
The World Telecommunication Standardization Assembly
(Johannesburg, 2008),
[1] These include the least developed countries, small island
developing states and countries with economies in transition.
13 September 2010
11
Testing methodology
Conformance testing
Conformance testing comes first. This type of testing strives to
determine if the implementation of a standard does what the standard says
it is supposed to do. Each implementation is tested against the same
conformance
co
o a ce test su
suite
te developed
de e oped for
o that
t at standard.
sta da d The
e basic
bas c test
configuration is shown in Figure 1.
T t Suite
Test
S it (for
(f a given
i
b
base
standard)
t d d)
Product
Figure 1 - Conformance testing using a standardized conformance test suite.
Interoperability testing
Interoperability testing follows next.
next This type of testing checks two
implementations at a time, to determine if the pair is capable of
communicating by exchanging useful data at the functional level.
Conformance testing or Interoperability testing
The ultimate objective of conformance testing is to achieve interoperability,
given that interoperability has been written into the standards. The
objective of interoperability testing is to check if interoperability has been
achieved through conformance. Conformance and interoperability
testing are complementary, and should be done in that order.
13 September 2010
12
JCA-CIT Draft “Conformance and Interoperability Testing Roadmap”
Appendix I Providing interoperability with ITU Recommendations
Conformance Testing
Definition of conformance
compliance with requirements specified in applicable series
Recommendations. [ITU-T X.290]
S
Scope
off C
Conformance
f
ttesting
ti
Test subject is connected to the tester or reference machine and
examines the conformity with reference recommendations.
Certifications or type of approval may be given to the products
passed by the testing authority. This is not a mandatory function
of conformance testing.
The documents which describe test specifications for the
conformance testing are specified in the test specification
language such as PICS, PIXIT etc.
General configuration for Conformance testing
Test Subject
(Product)
Tester
e.g. UNI/NNI
13 September 2010
13
Interoperability Testing
Definition of interoperability testing
testing to assess the ability of two or more systems to exchange
information and to make mutual use of the information that has
been exchanged. [ITU-T Z.450]
Scope of Interoperability testing
Multiple products of multiple vendors are connected and tested
for interoperability at the service level and/or transport level.
Interoperability testing will be conducted in the following
steps,
steps
Define service scenario (service use case).
Define configuration, products and interfaces to be tested.
Define implementation agreements for each test interface.
Examine interoperability
p
y tests according
g to the test scenario and
implementation agreement and analyze the test output.
The documents for Interoperability testing are service
scenario (service use case) and implementation agreements
for each test interfaces.
Interoperability testing (e.g. IOT configuration for IMS based IPTV)
Vendor A
IPTV-AS
UE
13 September
Geneva,
18 - 22
2010
May 2009
IMS
IPTV-VS
QoS/Router
Vendor B
Test interface
14 14
New draft Recommendations in SG11
Generic framework
Detailed Technical Spec. for VoIP
Draft Recommendation Q.NGN interoperability
NGN interoperability
e ope b y
1
2
3
4
5
11. SCOPE
2. REFERENCES
3. DEFINITIONS
4. ABBREVIATIONS
5. CONVENTIONS
6. G
GENERAL
N
PRINCIPLES
NC
S
7. PREPARATION FOR TESTING
8. TEST OPERATIONS
9. TEST REPORT PRODUCTION
Add specifications for other services in future
Draft Recommendation Q.***
(Newly proposed in this meeting)
VoIP interoperability Testing
1. SCOPE
2. REFERENCES
3. DEFINITIONS
4. ABBREVIATIONS
5. CONVENTIONS
6. GENERAL PRINCIPLES
7 PREPARATION FOR TESTING
7.
8. TEST OPERATIONS
9. TEST REPORT PRODUCTION
・・
13 September 2010
VoIP conformance Testing
・・
SCOPE
REFERENCE
DEFINITIONS
ABBREVIATONAS AND ACRONYMS
INTEROPERABILITY TESTING AND
CONFORMANCE TESTING
6 CONFORMANCE TESTING
6.1 GENERAL
6.2 RWQUIREMENTS
6.3 PHYSICAL CONFIGURATION
6 4 CONFORMANCE TESTING FOR NGN
6.4
PROCEDURE
6.5 DOCUMENT SETS
7 INTEOPERABILITY TESTING
7.1 GENERAL
7.2 REQUIREMWNTS
7.
QU
WN S
7.3 PHYSICAL CONFIGURATION
7.4 DOCUMENT SETS
7.5 INTEROPERABILITY TESTING FOR
NGN PROCEDURE
Draft Recommendation Q.**
15
Add specifications for other services in future
Proposal in accordance of Japan
experience on VoIP service testing
TTC developed Technical Reports to specify the detailed
protocol specifications at NGN UNI and NNI for
interoperability between Japanese operators
operators.
TTC developed TTC standards JT-Q3401 and JT-Q3402 which
consist of the translation part of ITU-T Recommendations
and TTC original specifications as Annex and Appendix.
ITU-T Q.3402
TTC TR-9024
Main text
Annex
Appendix
TTC JT-Q3402
Main text
Annex
Appendix
ITU-T
Service
specificat
ions for
Up stream
VoIP
TTC additional spec.
Annex
Technical information
SDOa
13 September 2010
ITU-T draft Rec.
Q.VoIP conformance
Testing at NGN UNI
SDOb
SDOc
16
ITU Interop Event on IPTV
The first event took place in ITU in Geneva from 20 to 23 July 2010
Interoperability testing: 20-21, showcasing:22-23
Participations
NEC, NTT, Mitsubishi Electric, OKI, Pontifical Catholic University of
Rio de Janeiro (PUC-RIo), Sumitomo Electric Industries
Cisco:showcase only
Observers: Institute for Inforcomm Research(I2R, Singapore),
Global ICT Standardization Forum of India (GSIFI)
Certificates of participation were awarded to all participating
organizations.
Target Recommendations
H.721 (IPTV
basic terminal),
(
) H.750 ((metadata)) , H.762
(lightweight interactive multimedia), H.770 (service discovery) )
Next Events
Singapore, September 2010; India, December 2010
ii) showcasing
testing
http://www.itu.int/net/ITU-T/cdb/interop.aspx
i) Interoperability
13 September
2010
17
Conclusion
This presentation introduces the current
status and future direction of the
standardization in the ITU-T NGN-GSI
meeting.
NGN interoperability became serious
problems because SIP protocol has many
options. And assuring interoperability based
th global
l b l standard
t d d iis strong
t
d
i ffrom
on the
desire
the developing countries.
ITU
T NGN-GSI
NGN GSI continues to develop
ITU-T
enhanced services and functions and
improve NGN interoperability.
13 September 2010
18
Thank you!
y
Kaoru Kenyoshi
NEC Corporation
Email k-kenyoshi@cb.jp.nec.com
Phone +81-90-2217-8288
13 September 2010
19
Download