ITU-T Q 1236-1999 Intelligent Network Capability Set 3 - Management Information Model Requirements and Methodology Series Q Switching and Signalling Intelligent Network (Study Grou.pdf

《ITU-T Q 1236-1999 Intelligent Network Capability Set 3 - Management Information Model Requirements and Methodology Series Q Switching and Signalling Intelligent Network (Study Grou.pdf》由会员分享，可在线阅读，更多相关《ITU-T Q 1236-1999 Intelligent Network Capability Set 3 - Management Information Model Requirements and Methodology Series Q Switching and Signalling Intelligent Network (Study Grou.pdf（57页珍藏版）》请在麦多课文档分享上搜索。

1、 = 48b2591 Ob74794 537 INTERNATIONAL TELECOMMUNICATION UNION ITU-T TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU SERIES Q: SWITCHING AND SIGNALLING Intelligent Network Q.1236 (I 2/99) Intelligent Network Capability Set 3 - Management Information Model Requirements and Methodology ITU-T Recommendat

2、ion (Previously CCITT Recommendation) Q.1236 ITU-T Q-SERIES RECOMMENDATIONS SWITCHING AND SIGNALLING SIGNALLING IN THE INTERNATIONAL MANUAL SERVICE INTERNATIONAL AUTOMATIC AND SEMI-AUTOMATIC WORKING FUNCTIONS AND INFORMATION FLOWS FOR SERVICES IN THE ISDN SPECIFICATIONS OF SIGNALLING SYSTEMS No. 4 A

3、ND No. 5 SPECIFICATIONS OF SIGNALLING SYSTEM No. 6 SPECIFICATIONS OF SIGNALLING SYSTEM Ri SPECIFICATIONS OF SIGNALLING SYSTEM R2 DIGITAL EXCHANGES INTERWORKING OF SIGNALLING SYSTEMS SPECIFICATIONS OF SIGNALLING SYSTEM No. 7 DIGITAL SUBSCRIBER SIGNALLING SYSTEM No. 1 PUBLIC LAND MOBILE NETWORK INTERW

4、ORKING WITH SATELLITE MOBILE SYSTEMS CLAUSES APPLICABLE TO ITU-T STANDARD SYSTEMS Q.l-Q.3 Q.4-Q.59 Q.60-Q.99 Q.100-Q.119 Q. 120-Q.249 Q.250-Q.309 Q.310-Q.399 (2.4004.499 Q .50O-Q.599 Q.600-Q.699 Q.700-Q.849 Q.850-Q.999 Q. 1000-Q.l O99 Q.1100-Q.1199 NALLING REQUIREMENTS AND PROTO BROADBAND ISDN Q.200

5、0-Q.2999 Forjrther details, please refir to ITU-T List of Recommendations. 48b2591 Ob747b 30T ITU-T RECOMMENDATION Q.1236 INTELLIGENT NETWORK CAPABILITY SET 3 - MANAGEMENT INFORMATION MODEL REQUIREMENTS AND METHODOLOGY Summary Intelligent Network Capability Set 3 (IN CS-3) is the third standardized

6、stage of the Intelligent Network (IN) as an architectural concept for the creation and provision of services, including telecommunication services, service management services and service creation services. This Recommendation addresses IN CS-3 management based upon a sub-set of the IN CS-3 I“. It d

7、escribes the techniques to be used in providing the management requirements for the IN SSF Interface Information Model, the IN SMF-SCF functional decomposition and the applied methodology to develop the management requirements for any IN functional entity (FE). Source ITU-T Recommendation 4.1236 was

8、 prepared by ITU-T Study Group 11 (1997-2000) and was approved under the WTSC Resolution No. 1 procedure on 3 December 1999. I I Keywords IN CS-3, IN Management, SSF. Recommendation Q.1236 (12/99) i 48b2591 Ob74797 24b FOREWORD ITU (International Telecommunication Union) is the United Nations Specia

9、lized Agency in the field of telecommunications. The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of the ITU. The ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunicatio

10、ns on a worldwide basis. The World Telecommunication Standardization Conference (WTSC), which meets every four years, establishes the topics for study by the ITU-T Study Groups which, in their turn, produce Recommendations on these topics. The approval of Recommendations by the Members of the ITU-T

11、is covered by the procedure laid down in WTSC Resolution No. 1. in some areas of information 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 concisene

12、ss to indicate both a I telecommunication administration and a recognized operating agency. INTELLECTUAL PROPERTY RIGHTS The ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. The ITU takes n

13、o position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. As of the date of approval of this Recommendation, the U had not received notice of intellectual propert

14、y, protected by patents, which may be required to implement this Recommendation. However, implementors are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database. O ITU 2000 All rights reserved. No pari of this publication may

15、 be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm, without permission in writing from the ITU. Recommendation 4.1236 (12/99) 11 CONTENTS 1 2 3 4 5 5.1 5.2 5.3 5.4 6 Scope . References . Abbreviations General SMF-SSFKCF Interface .

16、SSF functional decomposition 5.1.1 Rationale 5.1.2 Method . SSF management requirements . 5.2.1 Rationale 5.2.2 Method . SSF management information model 5.3.1 SSF scenarios . 5.3.2 SSF management requirements and management functions . IN Management relationship with SS7 Management (4.751) 5.4.1 In

17、troduction 5.4.2 MTP related information . 5.4.3 SCCP related information 5.4.4 Comparison between Traffic Management and IN Management SMF-SCF relationship Appendix I . Management scenarios for service switching function I . 1 SSF scenarios 1.2 Basic IN Call scenarios . 1.2.1 Introduction 1.2.2 Tri

18、ggering of IN service control 1.2.3 Call Set-up Capabilities . 1.2.5 1.2.4 Event Report Capabilities Call party handling capabilities . 1.2.6 Release call capabilities . 1.3 Call Gapping and Service Filtering scenarios . 1.3.1 Introduction 1.3 -2 DFP description . 1.3.4 Description of the impacted S

19、SF sub-entities 1.3.3 SSF Model mapping Page 1 1 1 2 3 3 3 4 6 6 6 7 8 9 29 29 29 30 30 31 33 33 34 34 34 39 41 45 45 45 45 46 46 49 . Recommendation 4.1236 (12/99) 111 48b259L 0b7ii7 OL Recommendation Q.1236 INTELLIGENT NETWORK CAPABILITY SET 3 - MANAGEMENT INFORMATION MODEL REQUIREMENTS AND METHOD

20、OLOGY (Geneva, 1999) 1 Scope This Recommendation addresses IN CS-3 management based upon a sub-set of the IN CS-3 INAP. It describes the techniques to be used in providing the management requirements for the IN SSF Interface Information Model, the IN SMF-SCF functional decomposition and the applied

21、methodology to develop the management requirements for any IN functional entity (FE). 2 References The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions

22、 indicated were valid. All Recommendations and other references are subject to revision; all users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently vali

23、d -T Recommendations is regularly published. - ITU-T Recommendation M.3010 (1 996), Principles for a Telecommunications management network. ITU-T Recommendation M.3020 (1 999, TMN interface specification methodology. IT-T Recommendation 4.752 (1 997), Monitoring and measurements for Signalling Syste

24、m No. 7networks. ITU-T Recommendation Q. 1224 (1997), Distributed functional plane for Intelligent Network Capability Set 2. ITU-T Recommendation Q. 1228 (1997), Interface Recommendation for Intelligent Network Capability Set 2. I - - - - 3 Abbreviations This Recommendation uses the following abbrev

25、iations: BCSM Basic call state model CCF Call Control Function CMIP Common Management Interface Protocol CMISE cs Capability Set DFP Distributed Functional Plane EDP Event detection point FE Functional entity FIM Feature interaction manager Common Management Interface Service element Recommendation

26、4.1236 (12199) 1 IN INAP IP OR PIC SAP SCF SDF SIB SLP SMF SRF ss7 SSF TDP TMN 4 Intelligent Network Intelligent Network Application Part Intelligent Peripheral Operational Requirement Point in Call Service Access Point Service Control Function Service Data Function Service Independent Building Bloc

27、k Service Logic Program Service Management Function Service Resource Function Signalling System number 7 Service Switching Function Trigger Detection Point Telecommunications Management Network General The following subclauses address IN CS-3 management. IN CS-3 management has concentrated mainly up

28、on the management of the SSF. Management of the SCF (see clause 6) provides the functional decomposition needed to develop management requirements and the management information model of an SCF. The methodology used in the definition of the SMF-SSF interface should be used to develop the SCF managem

29、ent requirements and the SCF management information model. The text builds upon Annex UQ.1224, where the foundation for IN management was made. The Management specification is based upon a sub-set of IN CS-3. The methodology for the specification of management for IN FES has been repeated here for c

30、larity. These subclauses consider only stages 1 and 2 of the following methodology. Stage 3 (Information models and Object specifications) can be found in Recommendation Q. 183 1.1. The approach used to provide the specifications for management of the SSF is divided into three steps (see Figure 1):

31、2 Recommendation 4.1236 (12199) - 48b2591, Ob74801 5T7 Management requirements Management infomation model T11103-99 Figure UQ.1236 - Overview of the approach It should be noted that this form of technical approach can be used to define the management specification of each IN functional entity, Le.

32、the SSF, SCF, SRF and SDF. In the following subclauses, these steps will be described in more detail. 5 SMF-SSF/CCF Interface 5.1 SSF functional decomposition 5.1.1 Rationale In order to come to the specification of a management information model of an SSF, it should first of all be clear what is to

33、 be managed. Therefore, it is necessary to establish a common understanding of the functionality of an SSF. The basis for such a common understanding can be provided by a functional decomposition of the SSF functionality. This functional decomposition based on the definition of the SSF as given in t

34、he Distributed Functional Model for IN CS-3 in 4.1231. The purpose of the functional decomposition is to: provide the basis for the common understanding of the SSF basic functionality (the target of the management study); modelling; provide a basis for the identification of management requirements a

35、nd management improve the readability of the Recommendation. This functional decomposition could be compared with the computational viewpoint in Open Distributed Processing (ODP). It is more or less in the form of an identification of (computational) objects in he SSF. Note that this functional deco

36、mposition is one of many possible decompositions. It is possible for other SSF functionality to exist, which may impact the management information model. Recommendation 4.1236 (12199) 3 48b259L Ob74802 433 -1 5.1.2 Method The method used to come to the functional decomposition of the SSF contains th

37、e following steps: i .i Analyse SSF functionality Within the Distributed Functional Plane architecture, the SSF and its relationships with other IN-FES are described. Based on this description an initial functional decomposition of the SSF, i.e. a “SSF sub-entities model“, can be made. Analyse and s

38、elect INAP procedures In the Physical Plane specifications, the information flow exchange between the IN-FES is described in detail. Identie which of the operations involve the SSF. Describe DFP scenarios for these operations. Choose a scenario that has not yet been mapped. For the chosen scenario,

39、identis. the required data and functions in the SSF and try to map these to the identified SSF sub-entities. If the mapping can be made, detail and validate the decomposition by considering the detailed operations and parameters in the DFP scenarios. Check also whether specific functionality has alr

40、eady been studied elsewhere, such as charging or routing. If this is the case, try to harmonize/reuse these. If a mapping cannot be made, the functional decomposition should be adapted to allow the mapping. If all identified scenarios have been mapped, and the model appears complete (i.e. all SSF fu

41、nctions and data relevant for management seems to be identified sufficiently well), this model can be used as the basis for the requirements capture. If there are any scenarios left that have to be mapped, repeat steps 1.3 to 11.51. (See Figure 2.) 1.21 1.31 Pick scenario 1.41 Correcextend model 1.5

42、 Next Scenario 4 Recommendation 4.1236 (12/99) 48b259L Ob74803 37T / / I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I l l I I I I I I I I 1 I I I I I I I I 1 (1) SSF functional decomposition Analyse sources (e.g. 4.1214) procedures Initial SSF sub-entities DFP scenarios mo

43、del (1.3) Pick scenario 4- (1.4) CorrecVextend model I sub-entities model I I I l I I I I I I I I I I I I I I I I I I I I I I I I I I I I I l I I I I I I I I I I I I I I I I I I I I I U U O Process Result Decision 110397-Q 0 Step in technical approach Figure 2/Q.1236 - Method for SSF Functional deco

44、mposition related to the overall approach 5.2 SSF management requirements 5.2.1 Rationale For each SSF sub-entity as identified in the SSF functional decomposition, one should analyse which part of the identified functionality and data should be subject to management (bottom-up). In order Recommenda

45、tion 4.1236 (12/99) 5 to put these management requirements into perspective, and to check whether they are really required from an operational perspective, they should be related to real (or envisioned) operational requirements. It should be possible to map each operational requirement - at least pa

46、rtly - to operations on the data and functions of the SSF sub-entities. The operational requirements and the management activities that are derived in this sub process are completely arbitrary. These steps are only taken to categorize the management requirements. The only goal is to identifj the res

47、ulting management operations on SSF data. 5.2.2 Method In the process of SSF Management requirements capture, the following terminology is used: e operational requirement: a description of a management process that an IN operator would management Jirnctions: set of management (TMN) operations upon o

48、ne or more data be needing for its business; entities. e In this requirements capture phase, the following steps are identified: a) Identify operational requirements: The operational requirements are the basis for the top-down approach to derive the SSF management requirements. To identifj these ope

49、rational requirements, use can be made of the experience of operational staff in managing IN structured networks; the DFP scenarios identified in step 1.2 can be used as a starting point in this analysis. To fulfil an operational requirement, one or more “management activities“ need to be performed (a many to many containment relationship). The description of the operational requirements and the list of the containing management activities is recorded in an “operational requirement template“. The management activitie