ITU-T Q 1300-1995 Telecommunication Applications for Switches and Computers (TASC) - General Overview - Intelligent Network (Study Group 11) 16 pp《交换和计算机领域的电信应用(TASC) 概述》.pdf

《ITU-T Q 1300-1995 Telecommunication Applications for Switches and Computers (TASC) - General Overview - Intelligent Network (Study Group 11) 16 pp《交换和计算机领域的电信应用(TASC) 概述》.pdf》由会员分享，可在线阅读，更多相关《ITU-T Q 1300-1995 Telecommunication Applications for Switches and Computers (TASC) - General Overview - Intelligent Network (Study Group 11) 16 pp《交换和计算机领域的电信应用(TASC) 概述》.pdf（16页珍藏版）》请在麦多课文档分享上搜索。

1、INTERNATIONAL TELECOMMUNICATION UN ION ITU-T TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU INTELLIGENT NETWORK Q.1300 (I 0/95) TELECOMMUNICATION APPLICATIONS GENERAL OVERVIEW FOR SWITCHES AND COMPUTERS (TASC) - ITU-T Recommendation Q.1300 (Previously “CCIlT Recommendation“) - ITU-T RECflN*Q.1300 9

2、5 Y862591 Ob15823 656 FOREWORD The ITU-T (Telecommunication Standardization Sector) is a permanent organ of the International Telecommunication Union (ITU). The ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommen- dations on them with a view to standardiz

3、ing 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 Recommendations by the M

4、embers of the IT-T is covered by the procedure laid down in WTSC Resolution No. 1 (Helsinki, March 1-12. 1993). ITU-T Recommendation 4.1300 was prepared 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 In this Recommenda

5、tion, the expression “Administration” is used for conciseness to indicate both 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, includ

6、ing photocopying and microfilm, without permission in writing from the ITU. . ITU-T RECMN*-L3QQ 95 E 48625%1 Ob15824 592 E CONTENTS Scope References Terms and definitions . 3.1 TASC 3.2 CCIT Recommendation X.200 . 3.3 CC Recommendation X.217 . 3.4 CCITT Recommendation X.219 . 3.5 ISO/IEC 9545 . Abbr

7、eviations . Overview 5.1 Problem space . 5.2 Messaging . 5.3 Functional service . 5.4 Interface architecture 5.5 Message encoding . 5.6 Functional services and objects 5.7 Monitoring 5.8 Management . Structure of Recommendation . Appendix I . Application context guidance Recommendation Q.1300 (10/95

8、) Page 1 1 1 1 3 3 3 3 3 4 4 7 8 9 9 9 10 10 11 12 i ITU-T RECMN*Q-3300 95 W 48b259L Ob35825 429 SUMMARY This Recommendation gives an overview to the Q. 1300-Senes of Recommendations which define Telecommunication Applications for Switches and Computers (TASC). The main purpose of TASC is to allow a

9、pplications running within the network users environment to integrate telecommunications services with computing facilities. This would typically allow business applications to use TASC to integrate the computer workstation and telephone at the users desktop. The overview contained in this Recommend

10、ation considers the requirements behind TASC and the key concepts leading to its definition. It also defines the vocabulary which is used by the other Recommendations in the TASC series. , 11 Recommendation Q.1300 (10195) Recommendation Q.1300 TELECOMMUNICATION APPLICATIONS FOR SWITCHES AND COMPUTER

11、S (TASC) - GENERAL OVERVIEW (Geneva, 1995) 1 Scope This Recommendation provides a general overview of Telecommunication Applications for Switches and Computers (TASC). The basic concepts, vocabulary and architecture upon which TASC is defined are presented. 2 References The following Recommendations

12、 and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision: ail users of this Recommendation are therefor

13、e 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. ITU-T Recommendation Q. 1301 (1995), Telecommunication Applications for switches and

14、computers (TASC) - TASC architecture. ITU-T Recommendation Q. 1302 (1995), Telecommunication Applications for switches and computers (TASC) - TASCjnctional services. IT-T Recommendation Q. 1303 (1 995), Telecommunication Applications for switches and computers (TASC) - TAX management: Architecture,

15、methodology and requirements. CCMT Recommendation X.200 (1988), Reference model of Open Systems Interconnection for CCIT applications. CCITT Recommendation X.208 (1988), Specijication of Abstract Syntax Notation One (ASN.1). CCITT Recommendation X.209 (1988), Specification of basic encoding rules fo

16、r Abstract Syntax Notation One (ASN. I ). CCIT Recommendation X.217 (1988), Association control service definition for Open Systems Interconnection for CCIT applications. - - - - - - - - - CCIT Recommendation X.219 (1988), Remote operations: Model, notation and service definition. CC Recommendation

17、X.227 (1988), Association control protocol specification for Open Systems Interconnection for CCIT applications. CC Recommendation X.229 (1 988), Remote operations: Protocol specification. ISO/IEC 9545: 1994, Information technology - Open Systems Interconnection - Application hyer structure (AU). -

18、- 3 Terms and definitions The following vocabulary and terms are used: 3.1 TASC 3.1.1 3.1.2 client: A component of an application which invokes a functional service. data terminai: A device to allow a user to communicate with a computer. Recommendation Q.1300 (10/95) 1 3.1.3 functional service: An i

19、nteraction between a communicating pair of functional entities at their application layer that provides benefit to the entities involved. The functional service is an operation or service available to a client which can be used to invoke a remote operation performed by the server. 3.1.4 server: A co

20、mponent of an application which performs a functional service. 3.1.5 headset. telecommunication device: A device that allows communication between users such as a telephone or 3.1.6 first party call control: The ability for a computer application to manipulate a telecommunication device by acting on

21、 that device which is directly connected. The application has access to the same information as the device and can only perform the same functions as the device. 3.1.7 third party call control: The ability for a computer application to indirectly manipulate a telecommunication device on a switch via

22、 a communication protocol, e.g. TASC. The application can indirectly manipulate a collection of telecommunication devices connected to that switch on behalf of application users. The application has access to information provided by the switch and can request operations to be performed by that switc

23、h. 3.1.8 operation domain: An Operation Domain defines the set of all possible instances of TASC objects for which the TASC application running on the host computer has visibility via the TASC interface. This includes transitory object instances which cannot be specifically determined during the ini

24、tial association of the host application with the switch. 3.1.9 working domain: A Working Domain is a subset of (or equal to) the Operation Domain. It identifies the set of all instances of TASC objects with which the TASC application wishes to operate (i.e. monitor). This includes transitory object

25、 instances which cannot be specifically determined during the initial association of the host application with the switch. 3.1.10 visible in a call. communication entity (CE): A communication entity (e.g. telephone) that originates, terminates or becomes 3.1.11 communication party (CP): An associati

26、ve object that maintains the relationship between a call and a CE. 3.1.12 end users. A call will be released and all resources returned by act of either the user or the network. call: The sequence of actions by the network which results in the end-to-end communications path between 3.1.13 basic call

27、: A call involving exactly two CES. 3.1.14 involved in the call. call view: An abstraction of a call which represents the progression of a basic call from the standpoint of a CE 3.1.15 user: An entity that makes use of a CE (e.g. initiates or answers a call). 3.1.16 on to systems which coordinate an

28、d distribute calls. agent: A type of user which is registered and distinguished from other users by their ability to sign-on or log- 3.1.17 such information to the Switch. Represented as a CE in TASC. device: An entity that serves as an endpoint for a call and accepts signalling information from, an

29、d provides 3.1.18 by event report messages. event: A change in the state of a TASC object which is visible to TASC. The application is notified of events 3.1.19 of its attributes and functions. object: An intrinsic representation of an entity that is described at an appropriate level of abstraction

30、in terms 3.1.20 states: An indication of an objects current condition that permits prediction of the objects future behaviour. 2 Recommendation 4.1300 (10/95) ITU-T RECPlN*Q=L300 95 m 48b2591 Ob15828 138 3.2 3.2.1 3.2.2 3.2.3 3.2.4 3.3 3.3.1 3.3.2 3.3.3 3.4 3.4.1 3.4.2 3.4.3 3.4.4 3.4.5 3.4.6 I 3.5

31、I 3.5.1 3.5.2 4 CCITT Recommendation X.200 application-entity appcation-process application-service-element open system CCITT Recommendation X.217 application-association; association application context association control service element CCITT Recommendation X.219 invoker-application-entity; invok

32、er performer-appiication-entity; performer requestor acceptor remote operations remote operation service element ISOrnC 9545 single association control function single association object Abbreviations For the purposes of this Recommendation, the following abbreviations are used: ACSE AE AP ASE ASN B

33、ER CPE FS GDMO ISDN IS0 os1 PC ROSE SNMP TASC TMN Association Control Service Element Application Entity Application Process Application Service Element Abstract Syntax Notation Basic Encoding Rules Customer Premises Equipment Functional Service Guidelines for the Definition of Managed Objects Integ

34、rated Services Digital Network International for Standardization Organization Open Systems Interconnection Personal Computer Remote Operations Service Element Simple Network Management Protocol Telecommunication Applications for Switches and Computers Telecommunication Management Network Recommendat

35、ion Q.1300 (10/95) 3 ITU-T RECnN*Q.L300 95 m 4862593 Ob35829 074 m 5 Overview 5.1 Problem space TASC is a set of telecommunication services supported by a communication interface between a switch and a computer (see Figure 1). The scope of the services centres around telecommunication calls and enti

36、ties associated with telecommunication calls such as devices, agents and users. TASC consists of a set of messages which allows a computer to control and have visibility of calls and devices at a switch and a switch to have access to infomation at a computer. Additional messages provide for agent op

37、erations, feature manipulation, supplementary service access, information exchange and management of resources. TI 168270-WdO1 FIGURE 1/Q.1300 Communication interface TASC can be envisioned at a desktop with an agent or other user having telephony capability (e.g. the ability to make and/or receive

38、telephone calls) and data capability (e.g. a terminal screen or personal computer). In a business scenario, information about inbound and outbound calls can be passed to the computer via the TASC interface, the computer can access its database given the information about the call (e.g. calling or ca

39、lled party) received from the switch, and information related to the call and customer can be composed by the computer for presentation to the agents screen. The TASC control functions can then be used by the computer to coordinate the delivery of the voice and data to the desktop or agent. By using

40、 a combination of call visibility and call control functions, switch-computer applications can be developed to meet the industry needs. The switch provides visibility about calls associated with a telecommunication device. In addition, call control operations can be issued by the computer or user at

41、 a data terminal to manipulate inbound and outbound calls. From a functional perspective, a user at a computer terminal communicates and interacts with an application in the computer (see Figure 2). The computer application in turn communicates with its peer application in the switch to initiate fun

42、ctions for a telecommunications device (e.g. make-a-call, answer-a-call and transfer-a-call). The switch application in turn communicates with the computer application to inform the computer of events happening relative to the telecommunications device (e.g. call-initiated, call-arrived, device aler

43、ting, call-establishment). Based on the information received from the switch and the call control functions available to the computer terminal user, the computer can effectively support a wide range of computer applications. The ability of a computer application to indirectly manipulate a line or de

44、vice on a switch is referred to as third party call control. This is in contrast to a user directly controlling calls at a telecommunications device via the keypad of the device which is referred to as first party call control. TASC is designed to provide third party call control but can also be use

45、d for first party call control. 4 Recommendation Q.1300 (10/95) I Cali Visibility Third Party Cali Control Telecommunication FIGURE UQ.1300 Logical configuration The relationship between the computer and the switch is a high-level relationship. The computer issues high-level functions to the switch

46、and the switch then performs low-level operations, which are typically switch dependent, to perform the function. For example, the computer can issue a function to transfer a call and it is then the responsibility of the switch to manipulate the segments or legs of the calls to accomplish the transf

47、er. With TASC, the computer does not attempt to control or manipulate calls on a call segment or call leg basis. This is the province of the switch. In the same sense, the switch issues high-level functions to the computer. For example, the switch may seek an alternate address to route a call and is

48、sue a route request to the computer. It is the function of the computer to find, by whatever means, an alternate address and return it to the switch. The switch does not issue database search and retrieval functions to the computer. This is the province of the computer. The goal of TASC is to provid

49、e a general set of messages which can be used to support a wide range of applications. These applications include: 1) Agent Support; 2) Call Management; 3) Customer Support; 4) Message desk; 5) Emergency Services; 6) Security Services; 7) User Support. The applications typically involve agents or other users with both telecommunication and computer access. TASC is not dependent upon the equipment configuration and supports a variety of physical configurations (see Figure 3) including: Type 1 - The case where the end-user has a voice terminal and a d