Embed Size (px)
Citation preview
2
Introduction
Japan submitted a contribution “Discussion on NGN interoperability” (COM 11 – C 79) to the NGN-GSI meeting (Geneva, Switzerland, 11- 22 May 2009). It was agreed to hold a tutorial work shop for NGN interoperability during the next NGN-GSI event in and “Seminar on ITU-T hot topics for Standardization” was held on 2nd September in Argentina. The tile of the session 3 of this seminar is “Interoperability aspects coordinated by SG11”.TTC proposed a new Resolution “NGN Interoperability” (GSC-PLEN-062) to the GSC-14 meeting (Geneva, Switzerland, 13-16 July 2009 ). It was agreed to create a new Resolution on “Interoperability” (with a broader scope than just NGN Interoperability) and revise the existing resolution on “NGN” to add articles for interoperability.Japan submitted a contribution “Discussion on NGN interoperability” (COM 11 – C110) to the NGN-GSI event in Argentina and proposes to define the standard reference and develop test suites for “conformance testing” and “interoperability testing”. This contribution was discussed in WP4/11 and proposed principle was agreed. Report of director of TSB (Document C09/28-E ) was reported in the Council 2009 (Geneva, 20-30 October 2009) (See the summary in the next slide)
3
Report of director of TSB
SummaryA major concern raised at WTSA-08 was the lack of conformance and interoperability of equipment being placed on the market, especially in developing countries. This resulted in the adoption of Resolution 76 which instructed the Director TSB to Report to Council-09 on assistance to developing countries in identifying human and institutional capacity-building and training opportunities in conformity and interoperability testing; and in establishing regional or sub-regional test centres; and study introducing the use of an ITU Mark programme as a voluntary programme permitting manufacturers and service providers to make a visible declaration that their equipment conforms to ITU-T Recommendations.This report summarizes studies conducted and proposes actions for implementing conformity assessment and interoperability testing programmes utilizing database references rather than Marks, and actions on capacity building and assisting establishment of test centres in developing countries in collaboration with BDT.
Reference document C09/28-E 14 September 2009
4
According to agreement of the NGN-GSI meeting in Argentina, we would like to propose to develop a draft recommendation for the interoperability testing and conformance testing in the next NGN-GSI meeting in January, 2010. The proposed draft recommendation for the interoperability testing and conformance testing will be composed with the recommendation main body and appendixes. Appendix includes the detail descriptions for the specific service ant it will be added according to progress of study of interoperability for each service as a technical information.The proposed draft recommendation includes the requirements, architecture and detail protocol specifications. Therefore the contribution will be submitted to SG11 and SG13. It is expected to be addressed to WP4/11, Q.2/13 and Q.3/13 in the January meeting. It is supposed that the recommendation may be approved with dabble numbering as Q series and Y series recommendation.The discussion based on this contribution should align and cooperate with the relevant existing discussions such as test specifications in WP4/11, physical architecture in SG13 and IPTV interoperability in SG16.
Considerations and proposals
5
Positioning of the document - There are several possibilities of the positioning of the proposed new
documents, such as draft recommendation, technical report and hand book etc. The contribution proposes as a new draft recommendation to the next NGN-GSI event. And it will be discussed again when the contents of this document become clear and concrete in the future.
Structure of the document- The main body includes the service common specifications and each
appendix include the service specific descriptions. It proposes that specifications for the interoperability testing and conformance testing for VoIP in the first appendix as the first priority.
- As a common part in the main body of the document includes specifications for both the interoperability testing and conformance testing. An individual part for the interoperability testing and conformance testing is divided into the internal sub clauses.
Responsible Q and SG- Each of SG11 and SG13 discusses this document for the time being, and
approval process in each SG will be discussed in parallel. Cooperation of CJK
- If CJK Sanya meeting agree with this proposal, I would like to put three contacts names from C, J and K to the contributions.
Discussion points in CJK meeting
6
NGN interoperability1. Scope2. Definition3. Reference4. Conformance testing4.1 Procedure4.2 Requirements4.3 Architecture4.4 Document5. Interoperability testing5.1 Procedure5.2 Requirements5.3 Architecture5.4 DocumentAppendixI. Test suites for VoIP interoperability testingII. Test suites for VoIP conformance testing
Body
Test suites for VoIP interoperability Testing1. Target service2. Test profile3. Physical architecture4. Implementation agreement5. Test scenarios
Test suites for VoIP conformance Testing 1. Target service2. Test profile3. Physical architecture4. Implementation agreement5. Test scenarios
・・・・ Add specifications for other services in future
Appendix I
Appendix II
Proposed structure of the document
7
Annex
Contribution to the last NGN-GSI meeting “Discussion on NGN interoperability” (COM 11 – C110)
Discussion on NGN interoperability
September 2009NEC Corporation
COM 11 – C110
IntroductionJapan submitted a contribution “Discussion on NGN interoperability” (COM 11 – C 79) to the NGN-GSI meeting (Geneva, Switzerland, 11- 22 May 2009). It was agreed to hold a tutorial work shop for NGN interoperability during the next NGN-GSI event in Argentina.TTC proposed a new Resolution “NGN Interoperability” (GSC-PLEN-062) to the GSC-14 meeting (Geneva, Switzerland, 13-16 July 2009 ). It was agreed to create a new Resolution on “Interoperability” (with a broader scope than just NGN Interoperability) and revise the existing resolution on “NGN” to add articles for interoperability.Japan MIC provided a presentation “Overview of MRA and Framework for Interoperability Testing” in the ITU Consultation on Conformance Assessment and Interoperability Testing (Geneva, Switzerland, 20 - 21 July 2009) See detail from
http://www.itu.int/ITU-T/worksem/wtsa-08/res76/200907/programme.htmlJapan (NEC) will submit a contribution to the next NGN-GSI event in Argentina and proposes to define the standard reference and develop test suites for “conformance testing” and “interoperability testing”.
1. Standard reference
10
What’s the issues should be solved?
Many questions were raised in the discussion.What is the definition, scope and output of “conformance testing” and “interoperability testing”?How we can examine the standard process of “conformance testing” and “interoperability testing”? Which kind of the standard documents need for “conformance testing” and “interoperability testing”?
We need standard reference for “conformance testing” and “interoperability testing” .This contribution discusses the standard reference includes Definitions, Process and Documentations for “conformance testing” and “interoperability testing”.
Conformance Testing
Definition of conformancecompliance with requirements specified in applicable series Recommendations. [ITU-T X.290]
Scope of Conformance testingTest 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, PICSIT etc.
Test Subject(Product)Tester
General configuration for Conformance testing
e.g. UNI/NNI
Geneva, 18 - 22 May 2009
Interoperability TestingDefinition 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 testingMultiple 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,Define service scenario (service use case).Define configuration, products and interfaces to be tested.Define implementation agreements for each test interface.Examine interoperability tests according 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)
UE IMS IPTV-VS
IPTV-AS
QoS/Router
Vendor A
Vendor B
Test interface13
Selection & Prioritization of Application
VoIP, IP Video Phone,
Service & applicationon NGN
Protocol
Service
Build test bed Test Environment-Temporary or permanent installation- w/wo remote connection ▪ ▪ ▪
-Execute tests-Examine results-Feedback to test specifications
-SDP-Selection options▪ ▪ ▪
- Session Control: SIP- Application: ?
IPTV, FMC ▪ ▪ ▪ ▪
-Define specifications -Define profile▪ ▪ ▪ Examine tests
Step 1 Step 2 Step 3
•Step 1: Define the target (service, application, protocol, function..)•Step 2: Define test specifications for the defined scenario in step 1•Step 3: Build up test bed and examine tests
Geneva, 20-21 July 2009 14
Standard Procedure for NGN Testing
QoS-Selection parameter-Define profile▪ ▪ ▪
・・
Geneva, 20-21 July 2009 15
Service scenario and/or protocolsBearer (Transport) Layer: RTP, RTSP, MPLS ▪▪▪Session Layer: SIP, HTTP ▪▪▪Application Layer (Service Scenario, Use case): IP Phone (VoIP), IP Video Phone, IPTV, FMC ▪▪▪
Test SpecificationTest Profile
List of the Recommendations related to testing.Physical Architecture
Physical Architecture is defined depending on service scenario. Implementation Agreement
Implementation agreement is defined for each interface such as UNI, NNI, and I/F between equipments.
Test ScenarioDetailed procedure of the testing and items for vilifications.
Test suiteA complete set of test cases, possibly combined into nested test groups, that is needed to perform dynamic conformance testing for one or more OSI protocols. [ITU-T X.290]
Standard Documents
Proposals
This contribution proposes Three step methodology to develop a standard procedure for interoperability testing and conformance testing shown in page 6.Create test suites (standard documents set includes Test Profile, Physical Architecture, Implementation Agreement and Test Scenario) for NGN interoperability testing and conformance testing shown in page 7.Test suites should be developed for each service in case of interoperability testing (e.g. VoIP, Video telephony, IPTV etc) or for each Recommendation in case of conformance testing (e.g. Q.3401, Q.3402 etc).Priority of the service or Recommendation is to be discussed.
2. Case Study for VoIP
17
Step1 Define the targetTarget
Quality of the serviceClass A (same level with fixed phone), class B (same level with mobile phone) and class C (internet telephony) is defined in JJ-201.01 in Japan.
Audio codec G.711,G.722 、 G.711.1 etc
Service scenarioBasic call, supplementary service (defined in H.450.1 ～ H.450.12)
Issues to be discussedThe physical configuration is deference very much whether “terminal testing” or “network equipment testing”There are several level of the testing (e.g. protocol testing, functional testing, service testing etc).The scope of the service testing is wider rather than protocol testing, QoS testing and functional testing. It covers end to end testing.The service testing usually includes protocol testing, QoS testing and functional testing. (Protocol testing, QoS testing and functional testing is a part of the service testing)
18
Step2-a Test Profile
Reference RecommendationRFC 3261 SIP: Session initiation protocolRFC 2543 SIP: Session initiation protocolRFC 2327 SDP: Session description protocolRFC 3550 RTP: A Transport Protocol for Real-Time ApplicationsITU-T G.711 Pulse code modulation (PCM) of voice frequencies ITU-T G.728 Coding of speech at 16 kbit/s using low-delay code excited linear prediction ITU-T G.723.1 Dual rate speech coder for multimedia communications transmitting at 5.3 and 6.3 kbit/s ITU-T G.729 Coding of speech at 8 kbit/s using conjugate-structure algebraic-code-excited linear prediction (CS-ACELP)
19
Step2-b Physical Architecture (1/2)
Reference RecommendationITU-T Y.2012 Functional requirements and architecture of the NGN release 1
Mandatory element for basic call with red color P/S/I-CSCF 、 NACF 、 Switch/Router 、 NGN terminal
Optional element Elements fo QoS control testing with blue color: RACFTerminal variation with green color ： Access Media GW 、 Access GW control 、 RGW 、 Legacy terminalSoA/SDP （ Click to dial etc ） with yellow color ： Application support function & service support function
Issues to be discussedITU-T Y.2012 defined the logical architecture. Real products in the market should be taken into consideration to develop the physical architecture because the logical architecture and physical architecture is not a one to one mapping. At the same time, target interface for testing should be defined. Some interface may be implemented as the internal interface in the product.
20
①
②
21
Step2-b Physical Architecture (2/2)
Regarding NNI and UNI for VoIP, JT-3401 、 JT-3402 can be used as the implementation agreements in Japan.The implementation agreement needs to define for each interface for testing.Issues to be discussed
The implementation agreement needs to be defined for each testing interface based on the physical architecture.JT-3401 、 JT-3402 are the implementation agreements for VoIP service, it need to define the service specific implementation agreement for each service.
22
Step2-c Implementation agreement
Geneva, 18 - 22 May 2009 23
NGN NNI/UNI signalling profile
Scope of NGN NNI/UNI signalling profile documentsThese documents specify the service layer profile: the specifications for the SIP/SDP interface at the UNI and NNI. Transport layer profiles such as RTP are specified if media information is included in the service layer signalling.
IP telephony
VoIP Service Provider
B
PSTN PSTN
MG MGSS7
SS7
Bearer (RTP/IP)Signalling (SIP)
LogicalInterface
VoIP Service
Provider A
Service Control Function
Service Control Function
Transport Function
Transport Function
Interface in the scope of the NNI document
IP telephony
Interface in the scope of the UNI document
Interface in the scope of the UNI document
Geneva, 18 - 22 May 2009 24
JT-Q3401 NGN NNI signalling profile
SIP Signalling profileCall Signalling flow
Q.3401 (ITU-T)
SIP Signalling profileCall Signalling flow
JT-Q3401 (TTC)
+
Supplement technical documentsAnnex a. Clarifications of the JT-Q3401 text and option itemsAnnex b. Parameter setting of SIP messageAnnex c. Originating number indicationAnnex d. SDP non transparency in the Early dialogueAnnex e. Null member talkieAnnex f. Originating user identificationAnnex g. Congestion controlAnnex h. Numbering SIP-ISUP interworkAppendix i. Fall back connectionAppendix ii. TCP transport connection at the NGN-NGN interfaceAppendix iii. ISUP->SIP interwork for number portability Appendix iv. Option listAppendix v. SIP message and header informationAppendix vi. Message examples
TTC additional Specifications
P1-43
P44-127
JT-Q3401 aims to assure interoperability amongst VoIP service providers in Japan. This document is developed based on the ITU-T Recommendation Q.3401 NGN NNI signalling profile and TTC adding the TTC specifications (national standard) in the annexes and appendixes.
ITU-T Rec. TTC Standard
Translation
Geneva, 18 - 22 May 2009 25
JT-Q3402 NGN UNI signalling profile
SIP Signalling profileCall Signalling flow
Q.3402 (ITU-T)
SIP Signalling profileCall Signalling flow
JT-Q3402 (TTC)
+ TTC additional SpecificationsTranslation
P1-58
P59-161
JT-Q3402 aims to assure interoperability of the multimedia communications between NGN and terminals such as SIP telephony, SIP IP-PBX and SIP residential GW. This document is developed based on the ITU-T Recommendation Q.3402 NGN UNI signalling profile and TTC adding the TTC specifications (national standard) in the annexes and appendixes.
ITU-T Rec. TTC Standard (under consideration)
Supplement technical documentsAnnex a. Clarifications of the JT-Q3402 text and option itemsAnnex b. Originating number indication and relevant headerAnnex c. Terminal registrationAnnex d. SIP capability exchangeAnnex e. SIP and media handlingAnnex f. Congestion controlAnnex g. Band width controlAnnex h. Character length and parameter range of SIP messageAnnex i,. Specifications for the behavior of voice terminalAppendix i. Option items listAppendix ii. Use of response codeAppendix iii. Mapping to the quality class with SDP descriptionAppendix iv. SecurityAppendix v. SCF address acquisitionAppendix vi. SIP message and header informationAppendix vii. Message examples
Q.3901Distribution of tests and services for NGN technical means testing in the model and operator networks
1 ScopeThis Recommendation defines the list of checks to be performed during the testing of NGN (NGN TM local testing, NUT and services) in model and operator networks.This Recommendation defines the tasks for NGN TM, NUT and services testing on NGN for model and operator network, a tests list for model network and operator network, and the reasons for using one or the other network for carrying out the specified test groups.
Issues to be discussedQ.3901 specifies the test scenarios with function bases. It can be applied to the conformance testing.Around 40 draft Recommendations are studied under WP4/11. We need to check these documents.
26
Step2-d Test Scenario
