1、INTERNATIONAL TELECOMMUNICATION UNION ITU=T TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU Q.65 (06/2000) SERIES Q: SWITCHING AND SIGNALLING Functions and information flows for services in the ISDN - Methodology The unified functional methodology for the characterization of services and network cap
2、abilities including alternative object-oriented techniques ITU-T Recommendation Q.65 (Formerly CCITT Recommendation) I ITU-T Q-SERIES RECOMMENDATIONS SWITCHING AND SIGNALLING I SIGNALLING IN THE INTERNATIONAL MANUAL SERVICE FUNCTIONS AND INFORMATION FLOWS FOR SERVICES IN THE ISDN INTERNATIONAL AUTOM
3、ATIC AND SEMI-AUTOMATIC WORKING -_ Methodology Basic services Supplementary services Il CLAUSES APPLICABLE TO ITU-T STANDARD SYSTEMS SPECIFICATIONS OF SIGNALLING SYSTEMS No. 4 AND No. 5 SPECIFICATIONS OF SIGNALLING SYSTEM No. 6 SPECIFICATIONS OF SIGNALLING SYSTEM R1 SPECIFICATIONS OF SIGNALLING SYST
4、EM R2 DIGITAL EXCHANGES INTERWORKMG OF SIGNALLING SYSTEMS SPECIFICATIONS OF SIGNALLING SYSTEM No. 7 DIGITAL SUBSCFUBER SIGNALLING SYSTEM No. 1 PUBLIC LAND MOBILE NETWORK INTERWORKING WITH SATELLITE MOBILE SYSTEMS INTELLIGENT NETWORK BROADBAND ISDN SIGNALLING REQUIREMENTS AND PROTOCOLS FOR IMT-2000 Q
5、. 1-4.3 4.4-4.59 4.60-4.99 Q.60-Q.67 4.68-4179 Q.80-Q.99 Q.100-Q.119 4.120-4.249 Q.250-4.309 4.3 10-4.399 4.400-4.499 Q.500-Q.599 Q.600-4.699 4.700-4.849 Q.850-Q.999 Q. 1000-Q. 1099 Q. I 100-Q. 1 199 Q. 1200-4.1699 Q. 1700-4. 1799 Q.2000-4.2999 For further details, please refer to the list of ITU-TR
6、ecommendations. ITU-T Recommendation 4.65 The unified functional methodology for the characterization of services and network capabilities including alternative object-oriented techniques Summary This ITU-T Recommendation contains the Unified Functional Methodology (UFM), superseding the existing IT
7、U-T 4.65 (06/97), describing a common functional architecture for providing services and addressing signalling requirements for service implementation. The overall method for deriving switching and signalling Recommendations for ISDN services, consisting of three stages, is described in ITU-T 1.130.
8、 The method has been generalized beyond ISDN to include services provided in and among networks of various types. The UFM combines the traditional approach of the 1988 version of this Recommendation with some of the approaches traditionally used in the Intelligent Network (IN) description method. Th
9、e detailed method for deriving the Stage 2 portion of these Recommendations is described in this Recommendation. The main text of this Recommendation presents background information on the unified functional methodology, the steps of the method, the conventions used in description techniques, and gu
10、idelines for usage. Source ITU-T Recommendation Q.65 was revised by ITU-T Study Group 11 (1997-2000) and approved under the WTSC Resolution 1 procedure on 15 June 2000. FOREWORD The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunication
11、s. The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. The World Telecommunication S
12、tandardization Conference (WTSC), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. The approval of ITU-T Recommendations is covered by the procedure laid down in WTSC Resolution 1. In some areas of infor
13、mation technology which fall within ITU-Ts purview, the necessary standards are prepared on a collaborative basis with IS0 and IEC. NOTE In this Recommendation, the expression “Administration“ is used for conciseness to indicate both a telecommunication administration and a recognized operating agen
14、cy. INTELLECTUAL PROPERTY RIGHTS ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property R
15、ights, whether asserted by ITU members or others outside of the Recommendation development process. As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implemen
16、tors are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database. o ITU 2001 All rights reserved. No part of this publication may be reproduced or utilized in any form or by any means, electronic or mechanical, including photoc
17、opying and microfilm, without permission in writing from ITU. CONTENTS 1 1.1 1.2 2 2.1 2.2 2.3 2.5 3, . 1 3.2 3.3 Introduction Unified Functional Methodology (UFM): Summary . The Stage 2 definition (Summary) . Steps of the method Step 1 - Functional model 2.1.1 Unified functional model 2.1.2 Functio
18、nal entities . 2.1.3 Functional entity relationships 2.1.4 Derivation of the functional model . 2.1.5 Step 2 (Optional) - SIB description of service features (see 3.1 for alternative Step 2 utilizing Object oriented techniques) . 2.2.1 SIB definitions . 2.2.2 SIB data parameters 2.2.3 SIB modelling
19、conventions . 2.2.4 SIB modelling of service features . 2.2.5 List of available SIBS 2.2.6 Mapping SIBS to FES Step 3 - Information flow diagrams (see 3.2 for alternative Step 3 utilizing Object Oriented techniques) . 2.3.1 Identification of information flows . 2.3.2 Definition of individual informa
20、tion flows . Step 4 - Functional entity actions (see 3.3 for alternative Step 4 utilizing Object Oriented techniques) . Step 5 (optional) - SDL diagrams for functional entities . 2.5 i 1 SDL general aspects 2.5.2 Adding functionality to existing Stage 2 service descriptions 2.5.3 Packages Step 6 - A
21、llocation of functional entities to physical locations (scenarios) . Alternative steps utilizing Object Oriented techniques Alternative Step 2 . Alternative Step 3 . 3.2.1 Interface Classes 3.2.2 Class diagrams . 3.2.3 Interface Sequence diagrams (Optional) . Alternative Step 4 . Relationship betwee
22、n basic and supplementary service models . Page 1 1 5 6 6 7 7 14 14 15 17 18 19 20 21 22 22 23 23 24 25 26 26 36 41 41 43 43 44 44 45 47 48 . Page Appendix I . Format and outline of a Stage 2 description using the unified functional methodology . Appendix II . Functional architecture . 4.65 evolutio
23、n . Appendix III . Examples of Interface Classes formed from Service/Application requirements . III . 1 Introduction 111.2 Service/Application Example . 111.2.1 Third Party Initiated Call . 111.3 Class Diagrams . Generic call control service class diagram 111.3.1 111.3.2 Method Invocations . 111.3.3
24、 IDL Where to go now? . 111.4 49 50 52 52 52 52 53 53 53 54 56 1 ITU-T Recommendation Q.65 The unified functional methodology for the characterization of services and network capabilities including alternative object-oriented techniques 1 Introduction This revised Recommendation contains a summary o
25、f the Unified Functional Methodology (UFM), describing a common functional architecture for providing services and addressing signalling requirements for service implementation. The overall method for deriving switching and signalling Recommendations for ISDN services, consisting of three stages, is
26、 described in ITU-T 1.130. The method has been generalized beyond ISDN to include services provided in and among networks of various types. This new UFM combines the traditional approach of the 1988 version of this Recommendation with some of the approaches traditionally used in the Intelligent Netw
27、ork (IN) description method and those used in the Unified Functional Methodology (UFM). It gives the user of the Recommendation a choice of either using the methods described in the 1997 version of ITU-T Q.65 or of adopting techniques used in the computing industry. The detailed methods for deriving
28、 the Stage 2 portion of these Recommendations is described in this Recommendation. The main text of this Recommendation presents background information on the unified functional methodology, the steps of the method, the conventions used in description techniques, and guidelines for usage. Appendix I
29、 presents an outline for drafting a Stage 2 service description using the SIB Methodology. Appendix II contains the Unified Functional model including Broadband Call and bearer separation. Appendix III contains “Examples of interface Classes formed from ServicelApplication requirements“. 1.1 Unified
30、 Functional Methodology (UFM): Summary Unified Functional Methodology (UFM) allows for functional descriptions of services with information flows, Functional Entity Actions (FEA) and Specification Description Language , or Interface Class Descriptions, Generic IDL descriptions and Specification Desc
31、ription anguage (SDL), starting from a single unified functional architecture. In the former case the concept of Service Independent Building Blocks (SIB) has been adopted to address service creation needs as well as to introduce re-usable blocks of flows, SDL, and FEAS which can be catalogued. also
32、 free to use the Unified Modelling Language (UML), along with a comprehensive of Interface class descriptions to produce method invocations mapping onto APIS and IDL. This new concept better facilitates the production of SDL. The user may make use of both thods along side each other, choosing the me
33、thod that better facilitates the description of a interface. The unified model enables all network architectures (i.e. ISDN, B-ISDN, IN, , and TMN) to be described in a similar manner. e methodology needs to address current needs, but must also evolve to include improvements and new technology. The
34、method includes many elements of the 1988 version of this Recommendation, t can be used immediately, even as it evolves. The use of the SIB concept or Object Oriented . (0-0) technique to describe the relationship between Objects streamlines the work of Stage 2 service definition. New SIBS or Interf
35、ace classes will be created as needed. A SIB or Interface Class catalogue can be maintained as a reference for service creation and definition. Principles defining the scope of UFM include: The unified functional methodology allows creation of functional descriptions where Stage 1 service descriptio
36、ns are available or where network capabilities are specified for service creation. The methodology is based mainly on experience from using ISDN Stage 2 methodology (ITU-T Q.65 (1 988), IN methodology (ITU-T Q.1210, (1995) and distributed computing techniques derived fi-om Rumbaugh, Booch et al and
37、refined using the UML. ITU-T Q.65 (1 997 version) provides much background in service description utilizing a functional model, functional entities, and functional entity actions. The IN method provides the flexibility, service independence, and re-use characteristics which are desirable. UML is the
38、 tool through which a comprehensive description of the Interface Classes is developed, along with their relationships. This, along with several different types of standard tools, facilitates the production of the IDL making up the Application Programming Interface (MI). The unified functional archit
39、ecture is expanded to include new requirements and may be further expanded to suit the users needs. For each service description, an appropriate set of functional entities is selected to compose the model. This leads to a consistent set of flows, andor APIS and SDLs. The method is based on a unified
40、 functional model. Maintain a library of SIBs (with corresponding information flows and SDL) which are used to determine the functional architecture in the distributed functional plane (see Figure i). SIB sets are being created to support the capability sets in IN Recommendations. SIBs are mapped on
41、to the functional architecture complete with pre-defined functional entity actions, pre-defined SDL, and pre-defined information flows. SIBs can be useful tools for Stage 2 creation; other aspects (e.g. SDL descriptions, information flows) can potentially be automated. Maintain a library of Packages
42、, interface classes and IDL, which defines the API across a particular interface. These are also used to determine the functional architecture in the distributed functional plane (see Figure 1). The methodology addresses current needs, but must evolve to include improvements and new technology. Meth
43、od can be used even as it evolves. Phased approach for use across the ITU-T, using the unified architecture. New SIBs will be needed (existing services; new target services). New API calls will be developed. New relationships need to be defined. New target services must be considered (e.g. multipart
44、y calls). Not yet an automated process, but re-use plays a major role. New expertise must be developed for describing services from SIBs. Additional verification of existing services will be useful (for accuracy of the method and learning curve). 7) The unified methodology for creating Stage 2 descr
45、iption should include the following: identification of service or network capability; functional model and functional entity definition (Unified Functional Model); SIB andor Package identification (optional); functional entity actions and/or IDL-definition; information flows andor APIS; SDL (Dynamic
46、 Description) (optional); Define physical scenarios at an appropriate time. scenarios (physical allocation of functional entities). 8) Decisions must be made as to the recommended network implementations. With extension to IN, B-ISDN, IMT-2000, and other networks, the catalogue of physical entities
47、is increased. This greatly increases the number of potential scenarios. Work to provide Recommendations for tool improvements and automation of the functional description process. ITU-T 2.100 (SDL) and 2.120 (Message Sequence Chart - information flows) can be utilized more effectively. Tools can pro
48、vide validation of SDL and flows. automation of this process may be possible. 9) Communicate rules and conventions for SIB definition and combination; some / / Application/ Service Plane Interface Distributed Functional Physical Plane i Inter-network SCP TI 1107000-00 Figure 1/Q.65 - Conceptual meth
49、odology model showing relationships between services, global functions/service-independent building blocks, service packages, interface classes, functional entities and physical entities Figure 1 above is the modified IN functional model. The functional model is designed to give the user a choice of either using the SIB approach or of using 0-0 methods. The results are somewhat the same. If one uses the SIB path the output results in information flows which are mapped onto functional entities, whereas using the 0-0 method, the result is a set of MI calls which are also mapped onto functi
