1、 AMERICAN NATIONAL STANDARD FOR TELECOMMUNICATIONS ATIS-1000667.2002(R2012) Intelligent Network ATIS is the leading technical planning and standards development organization committed to the rapid development of global, market-driven standards for the information, entertainment and communications in
2、dustry. More than 200 companies actively formulate standards in ATIS Committees and Forums, covering issues including: IPTV, Cloud Services, Energy Efficiency, IP-Based and Wireless Technologies, Quality of Service, Billing and Operational Support, Emergency Services, Architectural Platforms and Eme
3、rging Networks. In addition, numerous Incubators, Focus and Exploratory Groups address evolving industry priorities including Smart Grid, Machine-to-Machine, Connected Vehicle, IP Downloadable Security, Policy Management and Network Optimization. ATIS is the North American Organizational Partner for
4、 the 3rd Generation Partnership Project (3GPP), a member and major U.S. contributor to the International Telecommunication Union (ITU) Radio and Telecommunications Sectors, and a member of the Inter-American Telecommunication Commission (CITEL). ATIS is accredited by the American National Standards
5、Institute (ANSI). For more information, please visit .AMERICAN NATIONAL STANDARD Approval of an American National Standard requires review by ANSI that the requirements for due process, consensus, and other criteria for approval have been met by the standards developer. Consensus is established when
6、, in the judgment of the ANSI Board of Standards Review, substantial agreement has been reached by directly and materially affected interests. Substantial agreement means much more than a simple majority, but not necessarily unanimity. Consensus requires that all views and objections be considered,
7、and that a concerted effort be made towards their resolution. The use of American National Standards is completely voluntary; their existence does not in any respect preclude anyone, whether he has approved the standards or not, from manufacturing, marketing, purchasing, or using products, processes
8、, or procedures not conforming to the standards. The American National Standards Institute does not develop standards and will in no circumstances give an interpretation of any American National Standard. Moreover, no person shall have the right or authority to issue an interpretation of an American
9、 National Standard in the name of the American National Standards Institute. Requests for interpretations should be addressed to the secretariat or sponsor whose name appears on the title page of this standard. CAUTION NOTICE: This American National Standard may be revised or withdrawn at any time.
10、The procedures of the American National Standards Institute require that action be taken periodically to reaffirm, revise, or withdraw this standard. Purchasers of American National Standards may receive current information on all standards by calling or writing the American National Standards Insti
11、tute. Notice of Disclaimer Support of Timeout and O_DTMF_Entered events; Support of emergency calling service; Support of direct SCF-SRF communications; Removal of Annex B. This standard was prepared by Working Group T1S1.7 on Services, Architecture, and Control of T1S1, the Technical Subcommittee o
12、n Services, Architectures and Signaling. There are five annexes to this standard. Annex A is normative and is considered part of this standard; Annexes B through E are informative and are not considered part of this standard. Similarly, footnotes are not part of this standard. Future control of this
13、 document will reside with Accredited Standards Committee Telecommunications, T1. This control of additions to the specification, such as protocol evolution, new applications, and operational requirements, will permit compatibility among U.S. networks. Such additions will be incorporated in an order
14、ly manner with due consideration to the ITU-T layered model principles, conventions, and functional boundaries. Suggestions for improvement of this standard will be welcome. These should be sent to the Alliance for Telecommunications Industry Solutions, T1 Secretariat, 1200 G Street, NW, Suite 500,
15、Washington DC 20005. This standard was processed and approved for submittal to ANSI by Accredited Standards Committee on Telecommunications, T1. Committee approval of the standard does not necessarily imply that all committee members voted for its approval. At the time, it approved this standard; th
16、e T1 Committee had the following members: E.R. Hapeman, T1 Chair W.R. Zeuch, T1 Vice-Chair J.A. Crandall, T1 Director S.M. Carioti, T1 Disciplines S.D. Barclay, T1 Secretary C.A. Underkoffler, T1 Chief Editor C. Brownmiller, T1 Editor Tung-Hai Hsiao, T1 Technical Editor EXCHANGE CARRIERS Organizatio
17、n Represented Name of Representative AT service invocation and control; end user interaction with service control; and service management. The scope of each of these aspects is addressed below. 1.3.1 End user access End user access to call/service processing for T1 IN will be provided via the follow
18、ing access arrangements: analog line interfaces; ISDN BRI and PRI; and traditional trunk and SS7 interfaces. Note that this does not preclude the use of these interfaces to support access from private or mobile networks. 1.3.2 Service invocation and control Call/service processing for T1 IN builds u
19、pon the current call-processing infrastructure 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
20、 is executed under the control of service control functionality, in conjunction with service data functionality. With this distributed approach to call/service processing, the existing call control functionality retains ultimate responsibility for the integrity of calls, as well as for the control o
21、f call processing resources. The following call/service processing constraints apply: A. Call control and service switching functionality are tightly coupled; thus, the relationship between SSF and CCF is not standardized. B. A call is either between two or more end users that are external to the ne
22、twork and addressable via a directory number or combination of directory number and bearer capability, or a call is between one or more end users and the network itself. 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 serv
23、ice 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 multiple exchanges. As such, each exchange only controls the portion of the call in that exchange call processing is functionally separated between exchanges. IN se
24、rvice logic invoked on IN exchanges in such an inter-exchange call are managed independently by each IN exchange. E. Existing exchanges can 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
25、call. This functional separation is provided between the originating portion of the call and the terminating portion of the call. This functional separation should be maintained in an IN exchange to allow IN ATIS-1000667.2002 4 service logic invoked on the originating portion of the call (i.e., on b
26、ehalf 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). F. It is desirable to allow multiple IN-supported service logic instances to be simultaneously active for a given end user. It is also rec
27、ognized that non-IN service logic will continue to exist in the network. As such, service feature logic instances mechanisms for T1 IN should: determine which service logic to invoke for a given service request. This mechanism should select the appropriate IN-supported service logic or non-IN-suppor
28、ted service logic, and block the invocation of any other service logic for that particular service request; limit simultaneously active IN- and non-IN-supported service logic instances; ensure that simultaneously active IN-supported service logic instances adhere to the single-ended, single point of
29、 control restriction. G. The distributed approach and added complexity of call/service processing for T1 IN requires mechanisms for fault detection and recovery, allowing graceful termination of calls and appropriate treatments for end users. 1.3.3 End user interaction End user interaction with the
30、network to send and receive information is provided by service switching and call control resources, augmented by specialized resources. These specialized resources are controlled by service control functionality, and are connected to end users via call control and service switching functionality. 1
31、.3.4 Service management Service management functionality is used to provision and manage the service control functionality, service data functionality, and specialized resource functionality in the network, outside the context of call/service processing. Standardized interfaces for this functionalit
32、y are outside the scope of T1 IN. However, the ability of a service subscriber to interact directly with subscriber-specific service management information is not excluded or constrained for T1 IN. 1.4 Scope of Intelligent Network physical plane The scope of the IN Physical plane of the IN architect
33、ure for T1 IN is consistent with the IN conceptual model. The physical plane identifies the different physical entities and the interfaces between these entities. It shall also meet the following criteria: service implementation independence; network implementation independence; vendor and technolog
34、y independence. ATIS-1000667.2002 5 2 Normative references The following standards contain provisions, which through reference in this text, constitute provisions of this American National Standard. At the time of publication, the editions indicated were valid. All standards are subject to revision
35、and parties to agreements based on this American National Standard are encouraged to investigate the possibility of applying the most recent editions of the standards indicated below. T1.111-2001, Signaling System No.7, Message Transfer Part 1T1.112-1996, Telecommunications - Signalling System No. 7
36、 - Signaling Connection Control Part (SCCP)1T1.113-2000, Telecommunications - Signalling System No. 7 - Integrated Services Digital Network (ISDN) User Part1T1.114-2000, Telecommunications - Signalling System No. 7 (SS7) - Transaction Capability Application Part (TCAP)1T1.607-2000, Telecommunication
37、s - Integrated Services Digital Network (ISDN) - Layer 3 Signaling Specification for Circuit-Switched Bearer Service for Digital Subscriber Signaling System No. 1 (DSS1)1T1.610-1998, Telecommunications - Generic Procedures for the Control of ISDN Supplementary Services1T1.628-2000, Emergency Calling
38、 Service 1T1.701-1994 (R1999), Telecommunications - Universal Personal Telecommunication (UPT) - Service Description (Service Set One)1T1.702-1995 (R1999), Telecommunications - Personal Communications Technology1ITU-T Recommendation E.164 (05/97), The international public telecommunication numbering
39、 plan 2ITU-T Recommendation Q.763 (12/99), Signalling System No. 7 - ISDN User Part formats and codes2ITU-T Recommendation Q.931 (05/98), ISDN user-network interface layer 3 specification for basic call control2ITU-T Recommendation Q.773 (06/97), Signalling System No. 7 - Transaction capabilities fo
40、rmats and encoding)2ITU-T Recommendation X.200 (07/94), Information technology - Open Systems Interconnection Basic reference model 2)2ITU-T Recommendation X.680 (07/02) | ISO/IEC 8824-1:1994, Information technology - Abstract Syntax Notation One (ASN.1): Specification of basic notation 2)2_ 1This d
41、ocument is available from the Alliance for Telecommunications Industry Solutions, 1200 G Street N.W., Suite 500, Washington, DC 20005. 2This document is available from the International Telecommunications Union. ATIS-1000667.2002 6 ITU-T Recommendation X.681 (07/02) | ISO/IEC 8824-2:1994, Informatio
42、n technology - Abstract Syntax Notation One (ASN.1): Information object specification 2)2ITU-T Recommendation X.682 (07/02) | ISO/IEC 8824-3:1994, Information technology - Abstract Syntax Notation One (ASN.1): Constraint specification 2)2ITU-T Recommendation X.683 (07/03) | ISO/IEC 8824-4:1994, Info
43、rmation technology - Abstract Syntax Notation One (ASN.1): Parameterization of ASN.1 specifications 2)2ITU-T Recommendation X.690 (07/02) | ISO/IEC 8825-1:1994, Information technology - ASN.1 encoding rules: Specification of Basic Encoding Rules (BER), Canonical Encoding Rules (CER), and Distinguish
44、ed Encoding Rules (DER) 2)2ITU-T Recommendation X.880 (07/94) | ISO/IEC 13712-1:1994, Information technology - Remote Operations: Concepts, model and notation 2)2(For extensive informative references, see Bibliography) 3 Definitions This clause provides a glossary of terms and definitions studied fo
45、r application in the documentation of Intelligent Networks. To the extent practicable, terms that have been defined previously are used unchanged and reference to the source of the definition is shown next to the term in parentheses. The definitions that have been changed to make them appropriate fo
46、r this application are considered to be new definitions; however, reference to the source definition is also shown in parentheses. 3.1 Terms and definitions For the purpose of this standard, the following definitions apply: 3.1.1 access channel: A designated part of the information transfer capabili
47、ty having specified characteristics, provided at the user-network interface. 3.1.2 access code: A code(s) for “customized numbering plan(s)”: attendant access, escapes to public network, etc. 3.1.3 access function: A set of processes in a network that provide for interaction between the user and a n
48、etwork. 3.1.4 adjunct (AD): An entity in the intelligent network that is functionally equivalent to a service control point but is directly connected to a service switching point. 3.1.5 agent: An entity acting on behalf of another. 3.1.6 alerting pattern: a specific pattern used to alert a subscribe
49、r (e.g., distinctive ringing, tones, etc.). 3.1.7 application context (AC): An Application Context describes the functions which are to be used for a particular instance of communication, 3.1.8 application context negotiation (ACN): Context negotiation establishes at the beginning of a transaction that set of user protocol ASEs will be potentially exchanged during a transaction. ATIS-1000667.2002 7 3.1.9 application entity (AE): The system-independent application activities that are made available as application services to the application agent, e.
