1、INTERNATIONAL TELECOMMUNICATION UNION ITU=T TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU INTELLIGENT NETWORK Q.1213 (1 0/95) GLOBAL FUNCTIONAL PLANE FOR INTELLIGENT NETWORK CS-1 ITU=T Recommendation (2.1 21 3 (Previously “CCITT Recommendation”) FOREWORD The ITU-T (Telecommunication Standardizatio
2、n Sector) is a permanent organ of the International Telecommunication Union (). The ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommen- dations on them with a view to standardizing telecommunications on a worldwide basis. The World Telecommunication Stan
3、dardization 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 is covered by the procedure laid down in WTSC Resolution
4、No. 1 (Helsinki, March 1-12, 1993). ITU-T Recommendation 4.1213 was prepared by IT-T Study Group 11 (1993-1996) and was approved under the WTSC Resolution No. 1 procedure on the 17th of October 1995. NOTE In this Recommendation, the expression “Administration” is used for conciseness to indicate bot
5、h a telecommunication administration and a recognized operating agency. O ITU 1996 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 IT. CO
6、NTENTS General . Scope of IN global functional plane for capability set 1 IN CS-1 global functional plane modelling . Role of SIBS in the global functional plane References 4.1 4.2 Additional characteristics of a IN CS- 1 SIB . 4.3 IN CS-1 global functional plane model 4.4 Terminology . IN CS-1 Serv
7、ice Independent Building Blocks (SIBs) 5.1 5.2 5.3 5.4 5.5 5.6 5.7 5.8 5.9 5.10 5.1 1 5.12 5.13 5.14 5.15 5.16 Data parameters for SIBs Method to describe IN CS-1 SIBs ALGORITHM AUTHENTICATE CHARGE COMPARE . DISTRIBUTION LIMIT . LOG CALL INFORMATION QUEUE . SCREEN . SERVICE DATA MANAGEMENT STATUS NO
8、TIFICATION TRANSLATE . USER INTERACTION VERIFY Basic call process . 6.2 6.3 Global service logic 7.1 Relationship between GSL and BCP 7.2 Relationship between global service logic and SIBs Mapping of the service plane to the global functional plane 6.1 General Points of initiation and points of retu
9、rn BCP stage 1 description Page 1 1 1 2 2 2 2 2 3 3 4 6 7 9 12 13 15 17 19 21 23 26 29 31 33 35 35 36 37 38 39 39 40 Recommendation Q.1213 (10/95) i SUMMARY IN capability set 1 (IN CS-1) is the first standardized stage of the intelligent network as an architectural concept for the creation and provi
10、sion of telecommunication services. This Recommendation provides the Intelligent Network (IN) Global Functional Plane (GFP) architecture for IN capability set 1 (IN CS-1). This Recommendation defines the IN GFP for IN CS-1 based on the general framework for IN GFP provided in Recommendation Q.1203,
11、consistent with the scope of IN CS-1 defined in Recommendation 4.121 1. This Recommendation defines: - - the IN GFP model for IN CS-1; identifications and definition of the 15 IN CS-I service independent building-blocks (SIBS), including the Basic Call Process (BCP) specialized SIB; the use of globa
12、l service logic in IN CS-1. - Companion Recommendations include the Q. 1200 and Q. 1210 Senes Recommendations. 11 Recommendation Q.1213 (10/95) _- Recommendation Q.1213 GLOBAL FUNCTIONAL PLANE FOR INTELLIGENT NETWORK CS-1 (Helsinki, 1993; moijed in 1995) 1 General The concepts for the Intelligent Ne
13、twork (IN) are embodied in the Intelligent Network Conceptual Model (INCM) as described in associated Recommendations 1.3121Q.1201 il. The Global Functional Plane (GFP) of the INCM is described in associated Recommendations 1.329/Q. 1203 2. 2 Scope of IN global functional plane for capability set 1
14、iN Capability Set 1 (IN CS-1) is the first standardized stage of the intelligent network as an architectural concept for the creation and provision of telecommunication services. This Recommendation provides the functional characteristics ofthe GFP associated specifically with IN CS-1. General GFP a
15、spects are addressed in associated Recommendations 1.312Q.1201 i and I.329/Q.1203 2. The following functional characteristics are specific to IN CS-1 and are addressed in this Recommendation: - - IN CS-1 GFP Modelling (see clause 4). IN CS-1 SIBs (see clause 5). For IN CS-1, 14 Service Independent B
16、uilding Blocks (SIBS) are specified (not including the BCP SIB discussed below). These represent the minimum set of SIBs required to define the IN CS-1 targeted services, identified in Recommendation Q. 121 1 3. - BCP SIB (see clause 6). For IN CS-1 the basic call process has been defined as a speci
17、alized SIB which provides the basic call capabilities. Nine Points of Initiation (POIS) for Global Service Logic (GSL) interfaces have been specified. In addition, six Points of Return (PORs) for GSL interfaces have been specified. - Plane-to-plane mapping (see clause 8). The relationships between t
18、he service plane and the GFP are Specified for IN CS-1. - For IN CS-1, network time is assumed to be available to all SIBs in the GFJ? and it does not have to be passed through call instance data. Stage 1 SDL diagrams are provided for IN CS-1 SIBS only where the SDLs clarify the understanding of the
19、 SIB operation. - 3 References The following Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time, the editions indicated were valid. All Recommendations and other references are subject to revision:
20、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 valid ITU-T Recommendations is regularly published. Il CCIT Recommendation 1.3 1UQ. 1201 (199
21、2), Principles of intelligent network architecture. 121 CCIT Recommendation 1.329/Q. 1203 (1992), Intelligent network global functional plane architecture. Recommendation Q.1213 (10/95) 1 i31 141 51 4 4.1 ITU-T RECMN*Q.L2L3 95 48b259L ObL577L 428 ITU-T Recommendation Q.1211 (1993), Introduction to i
22、ntelligent network capability set 1, ITU-T Recommendation Q.1290 (19931, Glossary of tem used in the definition of intelligent networks. CC Recommendation I. 130 (1988), Method for the characterization of telecommunication services supported by an ISDN and network capabilities of an ISDN. ITU-T Reco
23、mmendation Z. 100 (1993), CCZT specification and description language (SDL). -T Recommendation 4.931 (1993), Digital subscriber Signalling System No. 1 (DSS I) - ISDN user- network inte$ace layer 3 specification for basic call control. IN CS-1 global functional plane modelling Role of SIBs in the gl
24、obal functional plane SIBS are abstract representations of network capabilities that exist in an IN structured network. Their definition enforces the concept of service and technology independence by decoupling the services from the technology on which services are provided. The 14 SIBs defined in t
25、his Recommendation identify the network capabilities which will be available to service designers in a CS-1 IN structured network. Their use will provide valuable insight on how service creation will be facilitated in CS-n Recommendations. 4.2 Additional characteristics of a IN CS-1 SIB Data require
26、d by each SIB is defined by SIB support data parameters and call instance data parameters. SIBS are global in nature and their location need not be considered as the whole network is regarded as a single entity in the GFP. 4.3 IN CS-1 global functional plane model The INCM described in Recommendatio
27、n 1.312/Q.1201 i models the GFP as shown in Figure 1. Normal or non-IN supported services are processed within the BCP. When an IN supported service is to be invoked, its GSL is launched at the POI by triggering mechanism from the BCP. The global functional plane models the network from a global, or
28、 a network wide, point of view. Contained in this view is the BCP SIB, including IN CS-1 POIS and PORs, the IN CS-I SIBs, and the GSL, which describes how SIBs are chained together to describe service features. This Recommendation specifies how the model can be used to fully define IN CS-1 service f
29、eatures in the GFP. 4.4 Terminology The following terminology used in this Recommendation, is more fully defined in Recommendation 4.1290 4: CID Call Instance Data CIDFP Call Instance Data Field Pointer CLI Calling Line Identification SSD Service Support Data 2 Recommendation Q.1213 (10195) POI POR
30、/ /T113597091/d01 FIGURE 1/Q.1213 Global functional plane model 5 IN CS-1 Service Independent Building Blocks (SIBs) The following list of SIBs have been identified as required to support the list of targeted IN CS-1 services and service features identified in Recommendation Q. 121 1 3: - ALGORITHM
31、- AUTHENTICATE - CHARGE - COMPARE - DISTRIBUTION - LIMIT - LOG CALL INFORMATION - QUEUE - SCREEN - SERVICE DATA MANAGEMENT - STATUS NOTIFICATION - TRANSLATE - USERINTERACTION - VERIFY The stage 1 SIB descriptions that follow reflect the understanding of the logical function of each SIB in its role o
32、f supporting IN CS-1 services and service features. The BCP, which is viewed as a specialized SIB, is described in clause 6. An explanation of the format of the stage 1 SIB descriptions is outlined below. 5.1 Data parameters for SIBs By deknition, SIBS are independent of the service/SF they are used
33、 to represent. They have no knowledge about previous or subsequent SIBs which are used to describe the service feature. In order to describe service features with these generic SIBs, some elements of service dependence is needed. Service dependence can be described using data parameters which enable
34、 a SIB to be tailored to perform the desired functionality. Data parameters are specified independently for each SIB and are made available to the SIB through global service logic. Two types of data parameters are required for each SIB, dynamic parameters called Call Instance Data (CID) and static p
35、arameters called Service Support Data (SSD). Recommendation Q.1213 (10/95) 3 ITU-T RECMN*Q.L2L3 95 48b25%3 Ob35773 2TO M 5.1.1 Cai1 Instance Data (CID) Call instance data defines dynamic parameters whose value will change with each call instance. They are used to specify subscriber specific details
36、like calling or called line information. This data can be: - made available from the BCP SIB (e.g. Calling Line Identification); - generated by a SIB (e.g. a translated number); or - entered by the subscriber (e.g. a dialled number or a PIN code). Associated with each CID value is a logical name whi
37、ch is referred to as the CID Field Pointer (CIDFP). If a SIB requires CID to perform its function, there will be an associated CIDFP assigned through SSD (refer to 5.1.2). For instance, the TRANSLATE SIBs CID which defines what is to be translated is called Information. The TRANSLATE SIBS SSD parame
38、ter which defines where this data can be found is CIDFP-Filter Value(s). Since the CID value can vary with each call instance, service features can be written with data flexibility. In the above TRANSLATE SIB example, one service feature may require translation of a calling number, while another ser
39、vice feature will require translation of the called number. In both cases, the data required by the SIB is specified by the information Calling Line Identity (CLI), but the CIDFP-Filter Value(s) changes. In the first service feature, the value of CIDFP-Filter Value(s) is set to CLI, while the second
40、 service feature sets the value of CIDFP-Filter Value(s) to Called Number. Once a CIDFP has been specified for a service feature, it can be referenced by subsequent SIBs, and the CID value can be made available to all subsequent SIBs in the SIB chain. This CIDFP is said to be fixed for that service
41、and is constant for all instances of that service. The actual value of the CID changes for each call instance of that service feature. 5.1.2 SeMce Support Data (SSD) Service support data defines data parameters required by a SIB which are specific to the service feature description. When a SIB is in
42、cluded in the GSL of a service description, the GSL will specify the SSD values for the SIB. SSD consists of: i) Fixed parameters These are data parameters whose values are fixed for ali call instances. For instance, the “File Indicator” SSD for the TRANSLATE SIB needs to be specified uniquely for e
43、ach occurrence of that SIB in a given service feature. The “File Indicator” SSD value is then said to be fixed, as its value is determined by the service/SF description, not by the call instance. If a servicelSF is described using multiple occurrences of the same SIB, then fixed SSD parameters are d
44、efined uniquely for each occurrence. ii) Field pointers Field pointers identify which CID is required by the SIB, and in doing so provide a logical location for that data. They are signified by “CIDFP-xxxx”, where xxxx” names the data required. For instance, “CIDFP-Filter Value(s)” for the TRANSLATE
45、 SIB will specify which CID element is to be translated. If more than one CID is required by a SIB to perform its function, then the SSD data parameters will contain multiple field pointers. 5.2 The following template applies to characterize and describe the SIBs. 5.2.1 Definition Prose description
46、of the SIB from the service creation point of view. Method to describe IN CS-1 SIBs I 4 Recommendation Q.1213 (10195) - ITU-T RECNN+Q.LZ13 95 4Ab2591 Ob15774 137 a 5.2.2 Operation Description of actions performed by the SIB. The operations section expands on the definition, to allow the reader to cl
47、early understand the operation that this SIB is intended to perform. 5.2.3 Potential service applications Service examples of where this SIB can be used. 5.2.4 Input Input to each SIB is specified as three distinct elements: - one logical start; - - Service Support Data which defines parameters whic
48、h are specified by the service description; Cali Instance Data which are specific to that call instance. 5.2.5 Output Output from each SIB is specified as two distinct elements: - one or more logical end; - call instance data which defines data parameters specific to that call instance which results
49、 from the execution of that SIB and are required by other SIBS or the BCP to complete the call service instance. 5.2.6 Graphic representation A graphic representation is used to describe input, operations and output of the SIB and is illustrated in Figure 2. Each SIB is characterized by having one logical start and one or more logical ends. These logic flows are shown by the solid arrows on the left and right of the diagram. Each logic flow is specified above each arrow. SSD parameters are identified by the dashed arrow at the top of the diagram
