ITU-T Q 1214-1995 DISTRIBUTED FUNCTIONAL PLANE FOR INTELLIGENT NETWORK CS-1 (Study Group 11)《IN分布功能平台结构(第11研究组)314页》.pdf

《ITU-T Q 1214-1995 DISTRIBUTED FUNCTIONAL PLANE FOR INTELLIGENT NETWORK CS-1 (Study Group 11)《IN分布功能平台结构(第11研究组)314页》.pdf》由会员分享，可在线阅读，更多相关《ITU-T Q 1214-1995 DISTRIBUTED FUNCTIONAL PLANE FOR INTELLIGENT NETWORK CS-1 (Study Group 11)《IN分布功能平台结构(第11研究组)314页》.pdf（314页珍藏版）》请在麦多课文档分享上搜索。

1、INTERNATIONAL TELECOMMUNICATION UNION ITU-T TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU INTELLIGENT NETWORK Q.1214 (1 0195) DISTRIBUTED FUNCTIONAL PLANE FOR INTELLIGENT NETWORK CS-1 ITU-T Recommendation Q.1214 (Previously “CCITT Recommendation”) FOREWORD The ITU-T (Telecommunication Standardizat

2、ion 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 St

3、andardization 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 Resolutio

4、n No. 1 (Helsinki, March 1-12, 1993). IT-T Recommendation Q.1214 was revised by ITU-T Study Group 11 (1993-1996) and was approved under the WTSC Resolution No. 1 procedure on the 17th of October 1995. NOTE I In this Recommendation, the expression “Administration” is used for conciseness to indicate

5、both a telecommunication administration and a recognized operating agency. O IT 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 ITU.

6、 CONTENTS 1 General . 2 Scope of IN distributed functional plane for capability set 1 . 2.1 End user access . 2.2 Service invocation and control . 2.3 End user interaction 2.4 Service management : Distributed functional model for CS-1 . . 3.1 Explanation of dia gram . 3.2 IN functional model 3.3 Def

7、inition of functional entities related to IN service execution 3 4 Functional entity calihervice logic processing models 4.1 Overview 4.2 SSFICCF model . 4.3 Specialized Resource Function (SRF) model . 4.4 Service Control Function (SCF) model 4.5 Service Data Function (SDF) model . 5 Stage 2 descrip

8、tions of Service Independent Building Blocks (SIBS) . 5.1 Introduction 5.2 SIB stage 2 descriptions 5.3 BASIC CALL PROCESS SIB 5.4 Stage 2 description of other distributed functionality . 5.5 Mapping of the global functional plane to the distributed functional plane . 6 Relationships between FES . 6

9、.1 General 6.2 Relationships . 6.3 Information flows between FES 6.4 SCF - SSF relationship . 6.5 SCF-SRF relationship . 6.6 SCF-SDF relationship . 6.7 Summary of information flows and related SIBS . Annex A . SSFISCF relationship scenarios Annex B - BCSM SDL diagrams Appendix I -Aspects of the dist

10、ributed functional plane identified as “for further study” (FFS) relative to IN cs-1 1.1 General 1.2 Information flows (IFS) . 1.3 Information elements (Es) . 1.4 1.5 Chart - IFS. ES . BCP SIB Stage 2 . Appendix II . Charging scenarios . II.1 Introduction II.2 Charging requirements II.3 Charging pro

11、cesses . II.5 Interactions . n.6 Framework for the charging information flows between SSF and SCF . II.4 Charging scenarios Page 1 1 1 1 2 2 2 2 3 3 5 5 5 72 75 79 81 81 83 159 166 171 183 183 183 184 184 243 247 252 260 267 292 292 292 296 297 299 305 305 305 305 306 308 309 Recommendation 4.1214 (

12、10/95) 1 SUMMARY This Recommendation defines the Intelligent Network (IN) Distributed Functional Plane FP) architecture for IN capability set 1 (IN CS-1). It does define the IN DFP for IN CS-1 based on the general framework for IN DFF studies provided in Recommendation 4.1204, consistent with the sc

13、ope of IN CS-1 defined in Recommendation Q.1211. This Recommendation provides: - the IN DFP architecture for IN CS-1, in terms of a subset of the general IN DFP architecture encompassing only the functional entities related to IN service execution; static and dynamic models of the functional entitie

14、s related to IN service execution (including service switchingkall control, service control, specialized resource, and service data functions), to define how IN service control interacts with basic call processing and to understand the nature of the functional entity relationships required for IN CS

15、-1; SIB stage 2 descriptions to identify information flows and functional entity actions for IN CS-1; detailed information flow descriptions, including information elements and functional descriptions, as the basis for specifying IN protocols; a starting point for the study of call party handling ca

16、pabilities beyond two-party call Set-up and clearing. - - - - This Recommendation forms a useful basis for gaining implementation experience with the IN DFF. As with any project of this size and complexity, it can be anticipated that there may be difficulties in interworking the various implementati

17、ons of physical elements based on IN CS-1 DFP functionality. To achieve the IN objective of a multi- vendor environment, this Recommendation may go through some future revision in the light of implementation experience. Within the Q. 1210-series Recommendations, this Recommendation describes the dis

18、tribution of global functional plane functionality defined in Recommendation 4.1213 (Le. service independent building blocks SIBS for IN CS-1) in a service and vendor/implementation independent manner, as constrained by the capabilities of the embedded base of evolvable network technology. This prov

19、ides the flexibility to allocated distributed functionality into multiple physical network configurations, as described in Recommendation Q.1215, and to evolve IN from CS-1 to some future CS-N. It also provides a framework from which IN protocols are specified for IN CS-1, as described in Recommenda

20、tion Q.1218. ii Recommendation Q.1214 (10/95) Recommendation Q.1214 DISTRIBUTED FUNCTIONAL PLANE FOR INTELLIGENT NETWORK CS-1 (Helsinki, 1993; revised at Geneva, 1995) 1 General General aspects of the DFP are contained in clause UQ.1204. 2 The scope of the IN distributed functional plane (DFP) archi

21、tecture for IN capability set 1 (CS-1) is driven by the service requirements of desired CS-1 services, and constrained by the capabilities of the embedded base of evolvable network technology. The scope of functionality required to support desired CS-I services includes functionality to provide: Sco

22、pe of IN distributed functional plane for capability set 1 - - service invocation and control; - - service management. end user access to calYservice processing; end user interaction with service control; and The scope of each of these aspects is addressed below, 2.1 End user access End user access

23、to calVservice processing for CS-1 will be provided via the following access arrangements:*) - analogue line interfaces; - ISDN BRI and PRI; and - traditional trunk and SS No. 7 interfaces. 2.2 Service invocation and control CalVservice processing for CS-1 builds upon the current call processing inf

24、rastructure of existing digital exchanges. It does so by using a generic model of existing call control functionality to process basic two-party calls, then adding service switching functionality to invoke and manage IN service logic. Once invoked, IN service logic is executed under the control of s

25、ervice control functionality, in conjunction with service data functionality. With this distributed approach to callhervice processing, the existing call control functionality retains ultimate responsibility for the integrity of calls, as well as for the control of call processing resources. The fol

26、lowing calYservice processing constraints apply for CS-I: Call control and service switching functionality are tightly coupled, thus the relationship between SSF and CCF is not standardized in CS-1. A call is either between two or more end users that are external to the network and addressable via a

27、 directory number or combination of directory number and bearer capability, or a call is between one or more end users and the network itself. a) b) *) This does not preclude the use of these interfaces to support access from private or mobile networks. Recommendation Q.1214 (10/95) 1 ITU-T RECMN*Q-

28、1214 75 4862.571 Oh14381 85b M c) A call may be initiated by an end user, or by an SCF within the network on behalf of an end user. To supplement a call, IN service logic may either be invoked by an end user served by an IN exchange, or by the network on behalf of an end user. d) A call may span mul

29、tiple exchanges. As such, each exchange only controls the portion of the call in that exchange - call processing is functionally separated between exchanges. IN service logic invoked on IN exchanges in such an inter-exchange call are managed independently by each IN exchange. e) Existing exchanges c

30、an be viewed as having two functionally separate sets of call processing logic that coordinate call processing activities to create and maintain a basic two-party call. This functional separation is provided between the originating portion of the call and the terminating portion of the call. This fu

31、nctional separation should be maintained in an IN exchange to allow IN service logic invoked on the originating portion of the call (i.e. on behalf of the calling party) to be managed independently of IN service logic invoked on the terminating portion of the call (i.e. on behalf of the called party

32、). - f) It is desirable to allow multiple IN-supported service logic instances to be simultaneously active for a given end user. It is also recognized that non-IN service logic will continue to exist in the network. As such, service feature logic instances mechanisms for CS-1 should: - determine whi

33、ch service logic to invoke for a given service request. This mechanism should select the appropriate IN-supported service logic or non-IN-supported service logic, and block the invocation of any other service logic for that particular service request; . .I - limit simultaneously active IN- and non-I

34、N-supported service logic instances; - ensure that simultaneously active IN-supported service logic instances adhere to the single-ended, single point of control restriction on CS-1 service processing. g) The distributed approach and added complexity of callhervice processing for CS-1 requires mecha

35、nisms for fault detection and recovery, allowing graceful termination of calls and appropriate treatments for end users. 2.3 End user interaction End user interaction with the network to send and receive information is provided by service switching and call control resources, augmented by specialize

36、d resources. These specialized resources are controlled by service control functionality, and are connected to end users via call control and service switching functionality. 2.4 Service management Service management functionality is used to provision and manage the service control functionality, se

37、rvice data functionality, and specialized resource functionality in the network, outside of the context of call/service processing. Standardized interfaces for this functionality are outside the scope of CS-1. However, the ability of a service subscriber to interact directly with subscriber-specific

38、 service management information will not be excluded or constrained for CS- 1. 3 Distributed functional model for CS-1 3.1 Explanation of diagram Figure 3-1 identifies the IN DFP model for CS-1. This diagram depicts the functional entities and relationships applicable to CS-1. This diagram is a subs

39、et of the generic IN DFP model described in clauseZQ.1204. A general explanation of functional entities, relationships, and the diagram are contained in 2.UQ.1204. 2 Recommendation 4.1214 (10/95) ITU-T RECMN*Q.L214 95 = 4862591 0614382 792 T1143830921dl CCAF Call Control Agent Function CCF Call Cont

40、rol Function SCF Service Control Function SDF Service Data Function SRF Specialized Resource Function SSF Service Switching Function NOTES 1 2 The two SSFKCF have identical functionality and are only shown for some procedures like assist. The definition of CCAF and CCF are based on corresponding Q.7

41、1 ISDN definitions, but may be modified for use in IN. FIGURE 3-114.1214 IN distributed functional plane model for CS-1 3.2 IN functional model As stated in 3.1, the IN DFP for CS-1 is a subset of the general IN-DFP. In particular: - only the CCAF, CCF, SSF, SCF, SDF, and SRF functional entities are

42、 included; - SCF-SCF and SDF-SDF relationships are not addressed; - only the relationships related to IN service execution are addressed, as shown in the diagram; - service management and administration aspects of each functional entity are implied, but not specifically addressed in CS-1. No attempt

43、 has been made in CS-1 to limit an individual Administrations implementation of the service management functionality associated with the functional entities. 3.3 Definition of functional entities related to IN service execution 3.3.1 It is the interface between user and network cai1 control function

44、s. It: CCA function (CCAF): The CCAF is the Call Control Agent (CCA) function that provides access for users. a) provides for user access, interacting with the user to establish, maintain, modify and release, as required, a call or instance of service; 3 Recommendation Q. 1214 (10/95) b) accesses th

45、e service-providing capabilities of the Call Control Function (CCF), using service requests (e.g. setup, transfer, hold, etc.) for the establishment, manipulation and release of a call or instance of service; c) receives indications relating to the call or service from the CCF and relays them to the

46、 user as required; d) maintains callhervice state information as perceived by this functional entity. 3.3.2 processing and control. It: CC function (CCF): The CCF is the Call Control (CC) function in the network that provides callhervice a) establishes, manipulates and releases calkonnection as “req

47、uested” by the CCAF; b) provides the capability to associate and relate CCAF functional entities that are involved in a particular call and/or connection instance (that may be due to SSF requests); c) manages the relationship between CCAF functional entities involved in a call (e.g. supervises the o

48、verall perspective of the call and/or connection instance); d) provides trigger mechanisms to access IN functionality (e.g. passes events to the SSF). 3.3.3 the set of functions required for interaction between the CCF and a service control function (SCF). It: SS function (SSF): The SSF is the Servi

49、ce Switching (SS) function, which, associated with the CCF, provides a) extends the logic of the CCF to include recognition of service control triggers and to interact with the SCF b) manages signalling between the CCF and the SCF; c) modifies calkonnection processing functions (in the CCF) as required to process requests for IN provided service usage under the control of the SCF. 3.3.4 SC function (SCF): The SCF is a function that commands call control functions in the processing of IN provided and/or custom service requests. The SCF may interact with other functional entities to