1、INTERNATIONAL TELECOMMUNICATION UNION CCITT THE INTERNATIONAL TELEGRAPH AND TELEPHONE CONSULTATIVE COMMITTEE INTEGRATED SERVICES DIGITAL NETWORK (ISDN) 1.31 2 (1 0/92) OVERALL NETWORK ASPECTS AND FUNCTIONS, Q.1201 (10/92) ISDN USER-NETWORK INTERFACES 1.31 2lQ.1201 (1 0/92) PRINCIPLES OF INTELLIGENT
2、NETWORK ARCHITECTURE Recommendation 1.312 / Q.1201 Y8b251 0576804 131 FOREWORD The CCITT (the International Telegraph and Telephone Cotisultative Committee) is a permanent organ of the International Telecommunication Union (ITU). CCITT is responsible for studying technical, operating and tariff ques
3、tions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. The Plenary Assembly of CCITT which meets every four years, establishes the topics for study and approves Recommendations prepared by its Study Groups. The approval of Recommendations by t
4、he members of CCITT between Plenary Assemblies is covered by the procedure laid down in CCITT Resolution No. 2 (Melbourne, 1988). No. 2 procedure on the 1st of October 1992. Recommendation 1.3 12/Q.1201 was prepared by Study Group XVIII and was approved under the Resolution CCITT NOTES 1) telecommun
5、ication administration and a recognized private operating agency. 2) In this Recommendation, the expression “Administration” is used for conciseness to indicate both a A list of abbreviations used in this Recommendation can be found in Annex A. o ITU 1993 All rights reserved. No part of this publica
6、tion may be reproduced or utilized in any form or by any means, electronic or tnechaiical, including photocopying and microfilm, without permission in writing from the ITU. _- . 4862591 0576805 078 CONTENTS Objectives. overall description . 1.1 Motivation. objectives. scope of Intelligent Network .
7、1.2 Definition of Intelligent Network . 1.3 Evolution of Intelligent Network Recommendations IN frrnctional requirements 2.0 Introduction . 2.1 Service requirements 2.2 Network requirements IN architectural concept 3.1 IN Conceptual Model (INCM) . Intelligent Network (IN) long-term architectiire frn
8、mework . 4.1 Introduction . 4.2 Intelligent Network Conceptual Model 4.3 Architecture structure 4.4 Service considerations . 4.5 Technology basis . Annex A . Alphabetical list of . Recommendation 1.312 / Q.1201 (10192) Page 1 1 1 2 4 4 5 11 19 20 26 26 26 26 27 28 32 i - - - - - . m 4862591 0576806
9、TO4 Recommendation 1.312 / Q.1201 PRINCIPLES OF INTELLIGENT NETWORK ARCHITECTURE (1992) 1 Objectives, overall description 1.1 Motivation, objectives, scope of Intelligent Network 1.1.1 Motivution The term Intelligent Network (IN) is used to describe an architectural concept which is intended to be a
10、pplicable to all telecommunications networks. IN aims to ease the introduction of new services (Le. Universal Personal Telecommunication (Um), Virtual Private Network (VPN), Freephone, etc.) based on greater flexibility and new capabilities. IN Recommendations are motivated by the interests of telec
11、ommunication services providers to rapidly, cost effectively and differentially satisfy their existing and potential market needs for services. Also, these service providers seek to improve the quality and reduce the cost of network service operations and management. Additionally, current trends in
12、technology permit a greater degree of intelligence and greater freedom in die allocation of intelligence in the telecommunications network. For example, the improved mobility derived from miniaturization of electronic components allows for a greater degree of distributed functionality within and bet
13、ween service provider networks. Factors permitting such intelligence include: advances in digital transmission and switching, common channel signalling, distributed data processing, data base management and expert systems. 1.1.2 Objectives of Intelligent Network The objective of IN is to allow the i
14、nclusion of additional capabilities to facilitate provisioning of service, independent of the servicehetwork implementation in a multi-vendor environment. Service implementation independence allows service providers to define their own services independent of service specific developments by equipme
15、nt vendors. Network implementation independence aliows network operators to allocate functionality and resources within their nehvorks and to efficiently manage their nehvorks independent of network implementation specific developments by equipment vendors. 1.1.3 Scope of Intelligent Network Types o
16、f networks: IN is applicable to a wide variety of networks, including but not limited to: public switched telephone network (PSTN) mobile, packet switched public data network (ESPDN) and integrated services digital network (ISDN) - both narrow-band-ISDN (N-ISDN) and broadband-ISDN (B-ISDN). Type of
17、services: IN supports a wide variety of services, including supplementary services, and utilizes existing constraints on FIGURE 1 Relationship between the aspects of the standardization process 1.3.2.3 Area 3 - IN czrchitectcrre arid iriterfuces for each phuse In this area the specifications are pro
18、vided that are necessary for the implementation of IN equipment, interfaces etc. For each phase an evolving set of Recommendations will be developed. This area is documented in the Q.12xy-Series (i I x I9,2 I y 5 9). The relationship between the areas is shown in Figure 2. 7 (2.121 1 Area 1 IN archi
19、tectural concepts and modelling (1.320-Seried Q.l POY-Series) I I Phasex A Phase 2 Phase 1 IN architecture and interfaces for phase 1 FIGURE 2 Recommendations areas 3 Recommendation I312 / Q.1201 (10/92) 4862593 0576809 733 H 1.3.3 Phased standardization and definition of capability sets Capability
20、sets (CS) are defined as sets of IN capabilities which are to be subjects of standardization activities and for which the availability of Recommendations will be targeted for a particular evolution phase. The long-term capability set (LTCS) is the CS for the target IN architecture. The sequencing of
21、 CSs is shown in Figure 3. The figure also indicates the relationship between the previous defined areas and the definition of each capability set. Capability sets cs3 - - - cs2 - - - CSl - - - I l l Time TO TI T2 Tx T1 1 3340-91 IN concept and modelling Definition of CS x Recommendations for CS x F
22、IGURE 3 Sequencing of Capability sets (CSs) 2 IN functional requirements 2.0 Introduction IN functional requirements arise as a result of the need to provide network capabilities for both - customer needs (service requirements); and - network operator needs (network requirements). A service user is
23、an entity external to the network that uses its services. A service is that which is offered by an Administration to its customers in order to satisfy a telecommunications requirement. Part of the service used by customers may be providedmanaged by other customers of the network. 4 Recommendation 1.
24、312 / Q.1201 (10/92) - _. = 48bi593 0576810 435 Service requirements will assist in identifying specific services that are offered to the customer. These service capabilities are also referred to as (telecommunication) services. Network requirements span the ability to create, deploy, operate and ma
25、intain network Capabilities to provide services. The categorization of service requirements versus network requirements is schematically shown in Figure 4. I Telecommunication services Creation, deployment, operation and maintenance of network capabilities I Network capabilities TI 81 3350-91 . -_,
26、Service requirements Network requirements FIGURE 4 Service requirements versus network requirements Service and network requirements can be identified for the following areas of servicehetwork capabilities: - Service creation: 4n activity whereby supplementary services are brought into being through
27、 service creation, service management, network management, service processing and network interworking. specification phase, development phase and verification phase. Service manugemeat: An activity to support the proper operation of a service and the administration of information relating to the us
28、erkustomer and/or the network operator. Service management can support the following processes: service development, service provisioning, service control, billing and service monitoring. Nenvork mcitiugemetit: An activity to support the proper operation of an IN-structured network. Service processi
29、ng: Consists of basic call and supplementary service processing which are the serial and/or parallel executions of network functions in a coordinated way, such that basic and supplementary services are provided to the customers. Network intenvorking: A process through which several networks (IN to I
30、N or IN to non-IN) cooperate to provide a service. - - - - Figure 5 gives a general overview of these capability areas including their relation to service and nehvork requirements. The network interworking capabilities are not shown in this figure as these are indirectly contained in the other capab
31、ility areas. 2.1 Service requirements 2.1.1 Overdl requirements The following requirements may also apply to existing nehvorks. Nevertheless, they are stated here to underline their importance when defining the IN architecture: - - it should be possible to access services by the usual user network i
32、nterface (e.g. POTS, ISDN); it should be possible to access services that span multiple networks; Recommendation 1.312 / Q.1201 (10/92) 5 9 4862573 0576833 373 - it should be possible to invoke a service on a cati-by-call basis or for a period of time, in the latter case the service may be deactivat
33、ed at the en8 of the period; it should be possible to perform some access control to a service; it should be easy to define and introduce services; it should be possible to support services involving calls between two or more parties; it should be possible to record service usage in the network (ser
34、vice supervision, tests, performance information, charging); it should be possible to provide services that imply the use of functions in several networks; it should be possible to control the interactions between different invocations of the same service. - - - - - - _._.-_ Telecommunication servic
35、es Service creation services Service creation capabilities I I I, I Service management I services Customer o b i Service processing capabilities 4: Basic and supplementary , services _._- management Network operator T1813360-91 + Service requirements +- Network requirements FIGURE 5 Ketwork Capabili
36、ties in IN-structured network l 2.1.2 Sewice creation A subset of the service creation capabilities used by the network operator (described in 2.2.2) may be offered to customers. Service requirements for service creation refer to the nehvork capabilities that are used by network operators for the pr
37、ovision of service creation services to customers. This is schematically shown in Figure U. 2.1.3 Service manageinent Service requirements for service management refer to the network capabilities that are necessary for the provision, from a customers point of view, of service management services to
38、customers. This is schematically shown in Figure 7. A subset of the service management capabilities used by the network operator may be offered to customers. 2.1.3.1 Service management during deployment phase (For further study.) 6 Recommendation 1.312 I Q.1201 (10/92) - = - - - -_ I 4862593 05b832
39、208 Customer Network capabilities _. management services I b Service management capabilities 4 I I Service creation capabilities -_-_ - T1813370-91 Service requirements FIGURE 6 Service requirements for service creation Network capabilities _ Other capabilities li -1 Provisionof service II I , -_-_
40、A TI 81 33130.91 Service requirements FIGURE 7 Service requirements for service management 2.1.3.2 Service inariagetneiit during provisioning phase Service provisioning is the activity of instaling and deploying the necessary functionality in appropriate network elements to realize a service to a sp
41、ecific customer along with the initiai activation and customization. After provisioning the customers service is administered. Recommendation 1.312 / Q.1201 (10/92) 7 2.1.3.3 Service management during utilization phase This activity includes: activation, deactivation, service maintenance and service
42、 customization, after the service provisioning has taken place; service activation, which is the activity to make the service usable by a specific customer (e.g. call forwarding activation); service customization, which is the activity of setting up the appropriate service parameters to control the
43、operation of service to meet the specific needs of the customer (e.g. setting Call Distribution percentages); charging, which is mainly to collect data on service usage and to generate reports thereon for billing either on demand or automatically. It includes the alteration of charge within the fram
44、ework of agreement with a network operator. Other requirements include the preparation of customer-specific billing reports and data which are accessible to the customer; service monitoring, which provides the capability to collect and accumulate statistics on a given service with a view to determin
45、e the Quality of Service operation an8 adjust the operation to suit the prevailing conditions; also, the data may be used in the process of service creation to determine if an implementation of an IN supported supplementary service meets the service?s performance requirements. 2.1.4 Service processi
46、ng Service requirements for service processing refer to the network capabilities that are necessary for the provision, from a customer?s point of view, of basic and supplementary services by an IN-structured network. This is schematically shown in Figure 8. _ Other capabilities I and supplementary ?
47、 services Service processing Provisionofbasic i Customer _- T1813390-91 A Service requirements FIGURE 8 Service requirements for service processing The IN is primarily a network concept that aims for efficient creation, deployment and management of supplementary services that enhance basic services.
48、 With regard to the provision of basic and supplementary services, the IN concept is ?transparent? to the customer, i.e. the customer is unaware of whether a service is provided in an IN I 8 Recommendation 1.312 / 4.1201 (10/92) m 4862591 0576814 080 m way. This “transparency” basically implies that
49、, from a customers point of view, no service processing requirements c,m be identified that have specific reference to the IN as such. Notwithstanding this, the IN should be capable of supporting a broad range of basic and supplementary services. Service processing requirements can be identified for the following capabilities: - - The relationship between service capabilities and access capabilities is visualized in Figure 9. service capabilities th
