1、I NT E RN AT I ON AL TE LEC0 M M U N I CAT I ON U N I ON ITU-T TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU SERIES Q: SWITCHING AND SIGNALLING Intelligent Network Q.1222 (O 9/97) Service plane for Intelligent Network Capability Set 2 ITU-T Recommendation Q.1222 (Previously CCITT Recommendation) I
2、TU-T Q-SERIES RECOMMENDATIONS SWITCHING AND SIGNALLING SIGNALLING IN THE INTERNATIONAL MANUAL SERVICE INTERNATIONAL AUTOMATIC AND SEMI-AUTOMATIC WORKING Q.i-Q.3 4.44.59 FUNCTIONS AND INFORMATION FLOWS FOR SERVICES IN THE ISDN Q .60-Q .99 CLAUSES APPLICABLE TO ITU-T STANDARD SYSTEMS Q. 1 004.1 1 9 SP
3、ECIFICATIONS OF SIGNALLING SYSTEMS No. 4 AND No. 5 Q.120-Q.249 SPECIFICATIONS OF SIGNALLING SYSTEM No. 6 Q.25o-Q.309 SPECIFICATIONS OF SIGNALLING SYSTEM R1 Q.310-Q.399 SPECIFICATIONS OF SIGNALLING SYSTEM R2 Q .400-Q .499 DIGITAL EXCHANGES Q.500-Q.599 INTERWORKING OF SIGNALLING SYSTEMS Q.600-Q.699 SP
4、ECIFICATIONS OF SIGNALLING SYSTEM No. 7 DIGITAL SUBSCRTBER SIGNALLING SYSTEM No. 1 PUBLIC LAND MOBILE NETWORK Q.700-4.849 Q.850-Q.999 Q. 1000-Q. 1099 INTERWORKING WITH SATELLITE MOBILE SYSTEMS Q. 1 lOO-Q.1199 Q.1200-Q.1999 BROADBAND ISDN Q.20004.2999 For further details, please refer to ITU-TList of
5、 Recommendations ITU-T RECOMMENDATION Q.1222 SERVICE PLANE FOR INTELLIGENT NETWORK CAPABILITY SET 2 Summary This Recommendation provides the architecture of the IN CS-2 service plane. The service plane is the “top“ plane in the IN conceptual model which is defined in Recommendation Q. 1201 “Principl
6、es of Intelligent Network architecture“. This Recommendation provides the first view of the “top-down approach where the services and service features are defined first and then the network capabilities to support/provide these capabilities are developed and realized on the lower pianes (global func
7、tional plane, distributed functional plane and physical plane, respectively) of the IN conceptual model. This Recommendation further discusses the subjects of feature interactions, cooperations and interferences which were not addressed in the first issue of IN, i.e. IN CS-1. This Recommendation rep
8、resents the users view of services supported by an IN. Source ITU-T Recommendation Q.1222 was prepared by ITU-T Study Group 11 (1997-2000) and was approved under the WTSC Resolution No. 1 procedure on the 12th of September 1997. Recommendation Q.1222 (09/97) i FOREWORD IT (International Telecommunic
9、ation Union) is the United Nations Specialized Agency in the field of telecommuni- cations. 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 wi
10、th a view to standardizing telecommunications 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 R
11、ecommendations by the Members of the ITU-T 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 expres
12、sion “Administration” is used for conciseness to indicate both a 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 Int
13、ellectual Property Right. The ITU takes no 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 ITU had
14、not received notice of intellectual property, 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 1998 All right
15、s reserved. No part of this publication may 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. 11 Recommendation Q.1222 (09197) CONTENTS 1 General i 2 Service plane architecture 2.1 Genera
16、l 2.2 Characterization of services and service capability requirement 2.2.1 Service and service feature requirements 2.3 Service and service feature interaction . 2.3.1 Types of features considered for interactions . 2.3.2 Mechanisms for handling feature interactions 2.4 Service plane modelling Reco
17、mmendation Q.1222 (09/97) Page 1 1 1 2 3 3 3 4 5 . 111 Recommendation Q.1222 SERVICE PLANE FOR INTELLIGENT NETWORK CAPABILITY SET 2 (Geneva, I 9 9 7) 1 General Recommendation 1.3 12/Q. 1201 “Principles of Intelligent Network architecture“ presents the Intelligent Network Conceptual Model (INCM), as
18、based on a four-plane structure. The objective of this Recommendation is to provide the architecture of the IN CS-2 service plane. This architecture provides a reference to identify IN functionalities and their interactions. These functionalities and interactions are then described in subsequent IN
19、CS-2 Recommendations. IN CS-1 did not address the service plane because IN CS-I was developed based on the existing network evolution into the IN concepts. IN CS-2 provides the first view of the “top-down approach where the services and service features are defined first and then the network capabil
20、ities to support/provide these capabilities are developed and realized on the lower planes of IN conceptual model. IN CS-2 also addresses the subjects of feature interactions, cooperations and interferences which were not included in IN CS-1. Recommendation 4.1221 provides a complete listing of the
21、services and service features for IN CS-2. 2 Service plane architecture 2.1 General The service plane illustrates that IN-supported services can be described to the end user or subscriber by means of a set of generic blocks called “service features“. To aid in the discussion of the service plane, th
22、e following definitions apply: A service is a stand-alone commercial offering, characterized by one or more core service features and can be optionally enhanced by other service features. A service feature is a specific aspect of a service that can also be used in conjunction with other services/ser
23、vice features as part of a commercial offering. It is either a core part of a service or an optional part offered as an enhancement to a service. Interactions may occur between service features within a single service, or between the service features in different services. There is no visible distin
24、ction to the user of interactions that occur between services or service features. Therefore from the users perspective, the terminology “service interaction“ or “feature interaction“ is interchangeable. Feature interaction is a situation that occurs when an action of one feature affects an action o
25、r capability of another. This situation is sometimes referred to as a service interaction. This situation may be undesirable or desirable. A desirable feature interaction is referred to as a feature cooperation. An undesirable feature interaction is referred to as a feature interference. Feature coo
26、peration is a desirable feature interaction where two or more features or instances of a feature operate together to achieve a desired result. Feature interference is an undesirable feature interaction where a service fails to perform as expected and where the failure is due to the presence of other
27、 services, service features or of multiple instances of a single service. The service plane represents an exclusively service-oriented view. This view contains no information whatsoever regarding the implementation of the services in the network (for instance, an IN type of implementation is invisib
28、le). All that is perceived is the networks service-related behaviour as seen, for example, by a service user. Recommendation Q.1222 (09/97) 1 For IN CS-2, telecommunications services, management services and service creation services are contained in the service plane; they can be described to the e
29、nd user by means of telecommunications service features, management service features and service creation service features. The services and service features included in IN CS-2 are a superset of those included in IN CS-1, i.e. they include additional services and features, while still supporting th
30、ose identified in IN CS-1. (See Recommendation Q.1221 for a discussion of these services and service features.) The definitions of these three types of service features are as follows: - Telecommunications service features Specific aspects of telecommunications services that can be used individually
31、 or in conjunction with other telecommunication services/service features as part of a commercial offering. These may be either core or optional parts offered as enhancements to the telecommunication service. - Management service features IN CS-2 introduces this category of service features. This in
32、cludes the management features that support the activity performed by network operators and service providers. This includes such activities as monitoring, maintenance, traffic management, audit administration and billing. These service features include: service customization features; 0 service con
33、trol features; 0 service monitoring features. - Service creation service features IN CS-2 introduces this category of service features. These features include the activities required for the network operator and/or service provider to specify, develop, deploy and verify new services to end users. Th
34、ese service features include: service specification features; 0 service development features; service verification features; 0 service deployment features; 0 service creation management features. There may be relationships between services in one category and features in different categories. An exa
35、mple of this case is service creation output including service logic for the management aspects of a service. This requires a partitioning of functionality between service management and service creation, when developing network capabilities for the lower planes of the IN conceptual model. Figure 1
36、illustrates these three types of service features on the service plane. 2.2 Characterization of services and service capability requirement Characterization of services and service features is to identify service independent capabilities that are required to construct and/or customize services by th
37、e users or network operators. A structured approach, as described in Recommendation Q. 1202, is applied to classify service characteristics and identify service capabilities. This structured approach is a high-level approach for analyzing services and identifying SIBS to support these services. Thes
38、e reusable service independent building blocks form the basis for global functional plane modelling and distributed functional plane modelling. It is recommended that activities involving functional modelling make use of the results of such service analysis, based on the characterization of services
39、 for verification of their models, and to ensure a unified model for service processing. 2 Recommendation Q.1222 (09/97) Telecommunications Service creation Figure VQ.1222 - In service plane 2.2.1 Service and service feature requirements IN CS-2 introduces service management service requirements and
40、 service creation service requirements to provide service management service and service creation service capabilities. The services reflect what information is required by service creation and service management. Service management service enables the management of telecommunica- tion services. Ser
41、vice creation service enables a fast and consistent way of introducing telecommunication services, including customerhser-specific services. 2.3 Service and service feature interaction The IN service plane is ideal for the identification of expected interactions between services supported by the IN
42、and for the definition of potential interaction solutions between these services. Also, with the development of the Unified Functional Model (UFM), which is not limited to IN, it is possible to define, and examine, interactions with non-IN- supported services. As services are mapped to service featu
43、res, a reverse mapping will indicate which service features may be used by multiple services. This is one method to identify interactions that must be examined. The identification of these interactions in the service plane allows the definition of a set of potential interaction solutions that minimi
44、ze negative interactions or maximize positive or desired interactions, based on the combination of services assigned to a given subscriber or affecting a different call. 2.3.1 Types of features considered for interactions Feature interactions may occur between IN-supported features as well as betwee
45、n IN-supported and non-IN switch- based features. Within each category of feature interaction IN CS-2 provides mechanisms for the handling of the following types of (feature) interactions. 2.3.1.1 Interactions between IN-supported features IN CS-2 provides mechanisms for the handling of the followin
46、g types of (feature) interactions between IN-supported features: - call-related IN-supported features to call-related IN-supported features; - call-related IN-supported features to call-unrelated IN-supported features; - call-unrelated IN-supported features and call-related IN-supported features; an
47、d - call-unrelated IN-supported features to call-unrelated IN-supported features. Recommendation Q.1222 (09/97) 3 2.3.1.2 Interactions between IN-supported features and non-IN switch-based features IN CS-2 provides mechanisms for the handling of the following types of (feature) interactions between
48、IN-supported features and non-IN switch-based features: - call-related IN-supported features to call-related non-IN switch-based features; - call-related IN-supported features to call-unrelated non-IN switch-based features; - call-unrelated IN-supported features to call-related non-IN switch-based f
49、eatures; and - call-unrelated IN-features to call-unrelated non-IN switch-based features. 2.3.2 Mechanisms for handling feature interactions The mechanisms for handling feature interactions in IN CS-2 support both intra-network and internetworking cases. IN CS-2 identifies two general types of mechanisms to handle Feature Interactions (FI): “static“ and “dynamic“. Static mechanisms are applicable during the time period extending from the initial design of a feature up to the point of feature execution (e.g. during a call). This time period includes feature design, feature provisioning
