Download MTS_RAN5 Oct05 Presentation sam - Docbox

Requirements Catalog
Scott A. Moseley
Farbum Scotus
1
Why a Requirements Catalog?
Why not write TPs immediately?
 To answer the question: What are the core IPv6 requirements?
 RFCs not written using the same rules as ETSI uses; e.g. extensive
use of MAYs, SHOULDs, and NOTs. Thus, fuzzier requirements (for
us).
 Language and meaning are important.
 Multiple sources: RFCs, 3GPP, “industry practice,” IPv6 Forum
label work
 Same requirement expressed across multiple source documents
 Requirements for Node, Router, and Host where Node can be either
Router or Host
 Need a link between requirement source and resulting test purpose
and test case/description
 A functional classification system is useful
 This is not easy
 Who can use? Developers, manufacturers, procurement, test
writers.
2
Requirements Sources
3G Mobile
Specifications
Industry
Practice
IPv6 Forum &
other sources
RFC
RFC
RFC
Requirements
Catalogue
3
3GPP Requirements Sources
[email protected] (Basu)
























*
3GPP TS 23.218: IP Multimedia (IM) session handling; IM call model (CN1)
*
3GPP TS 23.228: IP Multimedia Subsystem (IMS); Stage 2 (SA2).
*
3GPP TS 24.229: IP Multimedia Call Control Protocol based on SIP and SDP; Stage 3 (CN1)
*
3GPP TS 29.228: IP Multimedia (IM) Subsystem Cx Interface; Signalling flows and message contents (CN4)
*
3GPP TS 29.229: Cx Interface based on the Diameter protocol; Protocol details (CN4)
*
3GPP TS 29.328: IP Multimedia Subsystem (IMS) Sh Interface; Signalling flows and message contents (CN4)
*
3GPP TS 29.329: Sh interface based on the Diameter protocol; Protocol details (CN4)
*
3GPP TS 22.228: IP multimedia subsystem; Stage 1 (SA1)
*
3GPP TS 23.002: Network Architecture (SA2)
*
3GPP TS 23.003: Numbering, addressing, and identification (CN4)
*
3GPP TS 23.008: Organization of subscriber data (CN4)
*
3GPP TS 23.221: Architectural requirements (SA2)
*
3GPP TS 27.060: Mobile Station (MS) supporting Packet Switched Services (CN3)
*
3GPP TS 23.207: End-to-end QoS Concepts and Architecture (SA2)
*
3GPP TS 29.207: Policy Control over Go Interface (CN3)
*
3GPP TS 29.208: End-to-end Quality of Service (QoS) signalling flows (CN3)
*
3GPP TS 32.200: Telecommunications management; Charging management; Charging principles (SA5)
*
3GPP TS 32.225: Telecommunications management; Charging management; Charging data description for the IMS
domain (SA5)
*
3GPP TS 33.203: 3G security; Access security for IP-based services (SA3)
*
3GPP TS 33.210: 3G security; Network Domain Security (NDS); IP network layer security (SA3)
*
3GPP TS 24.228: Signaling flows for the IP multimedia call control based on SIP and SDP; Stage 3 (CN1)
*
3GPP TS 23.278: Customized Applications for Mobile network Enhanced Logic (CAMEL) - IP Multimedia System
(IMS) interworking; Stage 2
*
3GPP TS 29.278: Customized Applications for Mobile network Enhanced Logic (CAMEL); CAMEL Application Part
(CAP) specification for
IP Multimedia Subsystems (IMS)
4
The Requirements Catalog (cont’d)
 Basic Concepts
 A scalable database containing all requirement elements
 HTML view of selected database elements
 HTML links between RFC, requirement, test purpose,
and test case/description
 Mapping between RFC and IPv6 Logo requirements
 A user-extendable tool to identify requirements for
procurement or implementation
5
Extract from Requirements DB
6
Example Requirement
7