ITU-T I 328-1997 Intelligent Network - Service Plane Architecture - Series I Integrated Services Digital Network - Overall Network Aspects and Functions - Reference Models《智能网络 服务平.pdf

1、STD-ITU-T RECMN 1.328-ENGL 1777 II qSb1.571 Ob4bqOb 535 B INTERNATIONAL TELECOMMUN CATION UN ION ITU-T TELECOMMUNICATION STAN DARD IZATI ON SECTOR OF ITU 1.3281Q.1202 SERIES I: INTEGRATED SERVICES DIGITAL NETWORK Overall network aspects and functions - Reference models SERIES Q: SWITCHING AND SIGNAL

2、LING I n tel I ig ent Network (09/97) Intelligent Network - Service plane architecture ITU-T Recommendation 1.3281Q.1202 (Previously CCITT Recommendation) ITU-T I-SERIES RECOMMENDATIONS GENERAL STRUCTURE Terminology Description of ISDNs General modelling methods Telecommunication network and service

3、 attributes General description of asynchronous transfer mode Scope General aspects of services in ISDN Common aspects of services in the ISDN Bearer services supported by an ISDN Teleservices supported by an ISDN Supplementary services in ISDN I SERVICE CAPABILITIES OVERALL NETWORK ASPECTS AND FUNC

4、TIONS INTEGRATED SERVICES DIGITAL NETWORK I. 1 10-1.1 19 I. 120-1.129 1.130-1.139 I. 140-1.149 I. 150-1.199 1.200-1.209 1.2 10-1.2 19 1.220-1.229 1.230-1.239 1.240-1.249 1.250-1.299 Network functional principles 1.3 10-1.3 19 Reference models 1.320-1.329 Numbering, addressing and routing Connection

5、types Performance objectives Protocol layer requirements General network requirements and functions ISDN USER-NETWORK INTERFACES Application of I-series Recommendations to ISDN user-network interfaces Layer 1 Recommendations Layer 2 Recommendations Layer 3 Recommendations Multiplexing, rate adaption

6、 and support of existing interfaces Aspects of ISDN affecting terminal requirements INTERNETWORK INTERFACES MAINTENANCE PRINCIPLES B-ISDN EQUIPMENT ASPECTS ATM equipment Management of ATM equipment 1.330-1.339 1.340-1.349 1.350-1.359 I. 360-1.369 1.370-1.399 1.420-1.429 1.430-1.439 1.440-1.449 1.450

7、-1.459 1.460-1.469 1.470-1.499 1.500-1.599 I. 600-1.699 1.730-1.749 1.750-1.799 If For further details, please refer to ITU-T List ofRecommendations. ITLJ-T Q-SERIES RECOMMENDATIONS SWITCHING AND SIGNALLING SIGNALLING IN THE INTERNATIONAL MANUAL SERVICE INTERNATIONAL AUTOMATIC AND SEMI-AUTOMATIC WOR

8、KING FUNCTIONS AND INFORMATION FLOWS FOR SERVICES IN THE ISDN 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 SYSTEM R2 DIGITAL EXCHANGES IN

9、TERWORIUNG OF SIGNALLING SYSTEMS SPECIFICATIONS OF SIGNALLING SYSTEM No. 7 DIGITAL SUBSCRIBER SIGNALLING SYSTEM No. 1 PUBLIC LAND MOBILE NETWORK Q.l-Q.3 Q.4-Q.59 Q.60-Q.99 Q.lOO-Q.119 Q.120-Q.249 4.2504.309 4.3 104.399 4.400-4.499 Q.500-Q.599 Q.600-Q.699 Q.700-Q.849 Q.850-Q.999 Q.l0-Q. 1099 INTERWOR

10、KING WITH SATELLITE MOBILE SYSTEMS Q.llOO-Q.1199 ICNTELLIGENT NETWORK Q.120eQ.1999 BROADBAND ISDN Q.2000-Q.2999 For further details, please refer to ITU-T List of Recommendations. ITU-T RECOMMENDATION I.32WQ.1202 INTELLIGENT NETWORK - SERVICE PLANE ARCHITECTURE Summary This Recommendation has been u

11、pdated to include new capabilities and fnctionalities included in the IN CS-2 series (Q.122) of Recommendations. It provides a general architecture of the IN service plane in a way that specific functionalities and their interactions can be identified and described in other Recommendations which mak

12、e reference to the service plane. The service plane illustrates that IN-supported services can be described to the end user or subscriber by means of a set of generic building blocks called “service features“. This Recommendation describes this process of supporting services in an IN-structured netw

13、ork and the service planes relationship to the other planes in the IN Conceptual Model. Source ITU-T Recommendation I.328/Q. 1202 was revised by ITU-T Study Group 1 1 (1997-2000) and was approved under the WTSC Resolution No. 1 procedure on the 12th of September 1997. Recommendation I.328/Q.1202 (09

14、197) - 1 FOREWORD ITU (International Telecommunication 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

15、 questions and issuing Recommendations on them with 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 R

16、ecommendations on these topics. The approval of Recommendations 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

17、 and IEC. NOTE In this Recommendation, the expression “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 Re

18、commendation may involve the use of a claimed Intellectual Property Right. The IT 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

19、of approval of this Recommendation, the ITU had 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 consu

20、lt the TSB patent database. O ITU 1998 All rights 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 1.328/Q.1202 (09197) STD-IT

21、U-T RECMN 1.328-ENGL 1997 m q86257L OblibllLL 7T2 = CONTENTS 1 General . 2 Service plane architecture . 2.0 General : 2.1 2.3 Characterization of services and service capability requirements Service and service feature interaction . Annex A - Alphabetical list of abbreviations used in this Recommend

22、ation . B.l General B.2 Call Forwarding Unconditional and Terminating Key Code Screening . B.3 Call Forwarding Unconditional and Automatic Call Back . B.4 Call Forwarding Unconditional and Terminating Call Screening 2.2 Service plane modelling Annex B - A thesaurus of examples . Recommendation 1.328

23、/Q.1202 (09/97) Page 1 1 1 1 1 2 14 15 15 15 15 17 . 111 Recommendation I.32WQ.1202 INTELLIGENT NETWORK - SERVICE PLANE ARCHITECTURE (revised in 1997) 1 General Recommendation 1.3 12/Q. 120 1 “Principles of intelligent network architecture“ presents the Intelligent Network Conceptual Model (INCM), a

24、s based on a four-plane structure. The objective of this Recommendation is to provide a general architecture of the IN service plane in a way that specific hctionalities and their interactions can be identified and described in other Recommendations making reference to the IN service plane architect

25、ure contained in this Recommendation. 2 Service plane architecture 2.0 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“. A service is a stand-alone commercial offering, charac

26、terized 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/service features as part of commercial offering. It is either a core part of a service

27、or an optional part offered as an enhancement to a 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 invisible). All that

28、is perceived is the networks service-related behaviour as seen, for example, by a service user. Furthermore, management services are contained in the service plane; they can be described to the end user by means of service management features. 2.1 Characterization of services and service capability

29、requirements Characterization of services and service features is to identifj service independent capabilities that are required to construct and/or customize services by the users or network operators. Examples of service capabilities required from the user point of view are call queueing, customiz

30、ed announcement, etc. There is a need for a structured approach with which to classify service characteristics and identie service capabilities. The structured approach shown in Figure 1 below demonstrates a high level approach for analizing services and decomposing services into Service Independent

31、 Building Blocks (SIBs) These reusable service independent building blocks (such as TRANSLATE, USER INTERACTION or CHARGE) will form the basis for input to global functional plane modelling and distributed functional plane modelling. It is recommended that activities involving functional modelling m

32、ake use of the results of such service analysis, based on the characterization of services for verification of their models, and to ensure a unified model for service processing. 2.2 Service plane modelling Services are comprised of one or more Service Features (SF). A service feature is the smalles

33、t part of a service that can be perceived by the service user. These SFs can also be used as building blocks in the specification and design of new, more complex services. SFs are comprised of one or more SIBs which are described in Recommendation 1.329/Q.1203. Recommendation 1.328/Q.1202 (09/97) 1

34、Step 1: Set of services and service features I f Step 2: Characterization of services 1 I Step 3: Identification of service independent building blocks Step 4: Verification of global functional plane modelling, distributed functional plane modelling and physical plane modelling -i I L I l T1813550-9

35、1/dO Step 1 Step 2 Step 3 Existing service descriptions (Stage 1, Service description) as well as emerging service descriptions are selected as candidates for analysis. These services are characterized based on the principle of decomposition of services into functions. The analysis in step 2 results

36、 in requirements in the form of service independent building blocks as the input to global functional plane modelling, distributed functional plane modelling and physical plane modelling. Verification of the global functional plane modelling, distributed functional plane modelling and physical plane

37、 modelling results in improved SIBS through feedback to step 2. Step 4 Figure UQ.1202 - An approach for analyzing services All individual telecommunication services identified in the service plane should be described as seen from the users viewpoint without reference to how the services are implemen

38、ted in the network. In the service plane architecture, it is stressed that all capabilities experienced by a service user of the network represent telecommunication services (basic or supplementary). The service user may make use of the service for his own communication needs or may combine a number

39、 of services together and with perhaps additional capabilities, use the combination as a means of providing communications to other (third) parties. 2.3 Service and service feature interaction This subclause focuses on the interaction between IN supported services and other supplementary services an

40、d not between basic services. The service interactions are described from the customer and user point of view. There are often many ways to deal with an interaction between two or more services. In an IN-structured network, service interactions may be customized. Example of service interactions are

41、given below: - - - - - - - Meet-me Conference and CUG. Abbreviated Dialling and Number Screening; Freephone and Call Forwarding Unconditional; CLIR (Calling Line Identification Restriction) and CLIP (Calling Line Identification Presentation); Call Forwarding and Premium Rate Service; Call Waiting an

42、d Call Forwarding Busy; Conference Call and CUG (Closed User Group); 2 Recommendation 1.32fVQ.1202 (09/97) Examples of different ways to treat interactions between Freephone and Call Forwarding Unconditional are: 1) Freephone call attempts shall be forwarded like other terminating calls. 2) A Feepho

43、ne destination shall be selected for Freephone calls, even if it has activated Call Forwarding Unconditional. 3) A Freephone destination shall not be selected for Freephone calls if it has activated Call Forwarding Unconditional. 2.3.1 The service and feature interaction problem NOTE - In the follow

44、ing text, in order to facilitate the reading, the term “service“ is currently used instead of “service feature“. 2.3.1.1 General introduction This subclause provides a definition of the interaction problem and a setting of the scope of interaction studies. IN-structured networks are used to provide

45、rapid deployment of new services and service features to telecommunications users. These services and service features are mostly specified by different designers and implemented on different networks. This increases problems occUmng during the life cycle of each service because the resources (netwo

46、rk resources, services data) are influenced by other services and service features and thus such a service behaves differently. For the services to behave according to their specification and to fulfil the constraints imposed by sharing of resources among different services, methods for the detectio

47、n and resolution of interaction situations must be found. It is to be noted that a service is supported within a service addressing domain. Consequently, interaction can only be addressed (and solved) within such a given addressing domain. Interaction between two network-specific services, e.g. inte

48、raction between a call rerouting in a PBX and a service in the public network, cannot be solved as far as the services are not to be considered as multi-network, i.e. applied to a multi-network addressing domain. Service interaction applies to all interactions of the service being described with oth

49、er services which have been already identified. Service feature interactions may occur (for example): 1) among different features associated with the same service; 2) between features associated with a service for a given service user and features associated with other services the same user may have requested or been assigned; 3) between features associated with a service for a given service user and features associated with possible services related to the terminaYcalling line that the user is currently using, e.g. in case terminal mobility and/or personal mobility are invo