1、 ATIS-1000607.2014 Integrated Services Digital Network (ISDN) Layer 3 Signaling Specification for Circuit Switched Bearer Service for Digital Subscriber Signaling System Number 1 (DSS1) AMERICAN NATIONAL STANDARD FOR TELECOMMUNICATIONS As a leading technology and solutions development organization,
2、ATIS brings together the top global ICT companies to advance the industrys most-pressing business priorities. Through ATIS committees and forums, nearly 200 companies address cloud services, device solutions, emergency services, M2M communications, cyber security, ehealth, network evolution, quality
3、 of service, billing support, operations, and more. These priorities follow a fast-track development lifecycle from design and innovation through solutions that include standards, specifications, requirements, business use cases, software toolkits, and interoperability testing. ATIS is accredited by
4、 the American National Standards Institute (ANSI). ATIS is the North American Organizational Partner for the 3rd Generation Partnership Project (3GPP), a founding Partner of oneM2M, a member and major U.S. contributor to the International Telecommunication Union (ITU) Radio and Telecommunications se
5、ctors, and a member of the Inter-American Telecommunication Commission (CITEL). For more information, 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 b
6、y the standards developer. Consensus is established when, 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. Consensu
7、s requires that all views and objections be considered, 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 manufactur
8、ing, marketing, purchasing, or using products, processes, 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 righ
9、t or authority to issue an interpretation of an American 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 Nat
10、ional Standard may be revised or withdrawn at any time. 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
11、calling or writing the American National Standards Institute. Notice of Disclaimer EXAMPLES OF INFORMATION ELEMENTS CODINGS . 248 H.1 INTRODUCTION 248 H.2 BEARER CAPABILITY INFORMATION ELEMENT 248 H.2.1 Voice Bearer Services 248 H.2.2 Unrestricted or Restricted Digital Information . 250 H.3 CHANNEL
12、IDENTIFICATION INFORMATION ELEMENT . 251 H.3.1 Basic Rate Interface, Circuit Mode, B-Channel 251 H.3.2 Primary Rate Interface, Circuit Mode, B-Channel 252 H.3.3 Primary Rate Interface, Circuit Mode, H0-Channel 254 H.3.4 Called and b) the information processing and actions that take place at the user
13、 side and the network side. Overview and detailed Specification and Description Language (SDL) diagrams for call control of circuit-switched calls are contained in Annex A. Throughout this standard, references are made to B-channels. For services using H-channels, the refer-ences to B-channels shoul
14、d be taken to refer to the appropriate H-channel. 2.1 Circuit-Switched Calls This clause defines the basic call control states for circuit-switched calls. The procedures for call control are given in clause 5. 2.1.1 Call States at the User Side of the Interface The states that may exist on the user
15、side of the user-network interface are defined in this subclause. 2.1.1.1 Null (U0) No call exists. 2.1.1.2 Call Initiated (U1) This state exists for an outgoing call when the user requests call establishment from the network. 2.1.1.3 Overlap Sending (U2) This state exists for an outgoing call when
16、the user has received acknowledgment of the call establish-ment request that permits the user to send additional call information to the network in overlap mode. 2.1.1.4 Outgoing Call Proceeding (U3) This state exists for an outgoing call when the user has received acknowledgment that the network ha
17、s received all call information necessary to effect call establishment. 7 ATIS-1000607.2014 2.1.1.5 Call Delivered (U4) This state exists for an outgoing call when the calling user has received an indication that remote user alerting has been initiated. 2.1.1.6 Call Present (U6) This state exists fo
18、r an incoming call when the user has received a call establishment request but has not yet responded. 2.1.1.7 Call Received (U7) This state exists for an incoming call when the user has indicated alerting but has not yet answered. 2.1.1.8 Connect Request (U8) This state exists for an incoming call w
19、hen the user has answered the call and is waiting to be awarded the call. 2.1.1.9 Incoming Call Proceeding (U9) This state exists for an incoming call when the user has sent acknowledgement that the user has re-ceived all call information necessary to effect call establishment. 2.1.1.10 Active (U10)
20、 This state exists for an incoming call when the user has received an acknowledgement from the network that the user has been awarded the call. This state exists for an outgoing call when the user has received an indication that the remote user has answered the call. 2.1.1.11 Disconnect Request (U11
21、) This state exists when the user has requested the network to clear the end-to-end connection (if any) and is waiting for a response. 2.1.1.12 Disconnect Indication (U12) This state exists when the user has received an invitation to disconnect because the network has discon-nected the end-to-end co
22、nnection (if any). 2.1.1.13 Release Request (U19) This state exists when the user has requested the network to release and is waiting for a response. 8 ATIS-1000607.2014 2.1.2 Network Call States The call states that may exist on the network side of the user-network interface are defined in this sub
23、-clause. 2.1.2.1 Null (N0) No call exists. 2.1.2.2 Call Initiated (N1) This state exists for an outgoing call when the network has received a call establishment request but has not yet responded. 2.1.2.3 Overlap Sending (N2) This state exists for an outgoing call when the network has acknowledged th
24、e call establishment request and is prepared to receive additional call information (if any) in the overlap mode. 2.1.2.4 Outgoing Call Proceeding (N3) This state exists for an outgoing call when the network has sent acknowledgement that the network has received all call information necessary to eff
25、ect call establishment. 2.1.2.5 Call Delivered (N4) This state exists for an outgoing call when the network has indicated that the remote user alerting has been initiated. 2.1.2.6 Call Present (N6) This state exists for an incoming call when the network has sent a call establishment request but not
26、yet received a satisfactory response. 2.1.2.7 Call Received (N7) This state exists for an incoming call when the network has received an indication that the user is alerting but has not yet received an answer. 2.1.2.8 Connect Request (N8) This state exists for an incoming call when the network has r
27、eceived an answer but the network has not yet awarded the call. 9 ATIS-1000607.2014 2.1.2.9 Incoming Call Proceeding (N9) This state exists for an incoming call when the network has received acknowledgement that the user has received all call information necessary to effect call establishment. 2.1.2
28、.10 Active (N10) This state exists for an incoming call when the network has awarded the call to the called user. This state exists for an outgoing call when the network has indicated that the remote user has answered the call. 2.1.2.11 Disconnect Request (N11) This state exists when the network has
29、 received a request from the user to clear the end-to-end connec-tion (if any). 2.1.2.12 Disconnect Indication (N12) This state exists when the network has disconnected the end-to-end connection (if any) and has sent an invitation to disconnect the user-network connection. 2.1.2.13 Release Request (
30、N19) This state exists when the network has requested the user to release and is waiting for a response. 2.1.2.14 Call Abort (N22) This state exists for an incoming call for the point-to-multipoint configuration when the call is being cleared before any user has been awarded the call. 2.2 States Ass
31、ociated with the Global Call Reference This subclause defines the states that the protocol may adopt using the global call reference. The proce-dures for use of the global call reference for restart procedures are contained in 5.5. 2.2.1 Call States at the User Side of Interface The states that may
32、exist on the user side of the user-network interface are defined in this subclause. 2.2.1.1 Null (Rest 0) No transaction exists. 10 ATIS-1000607.2014 2.2.1.2 Restart Request (Rest 1) This state exists for a restart transaction when the user has sent a restart request but has not yet re-ceived an ack
33、nowledgment response from the network. 2.2.1.3 Restart (Rest 2) This state exists when a request for a restart has been received from the network and the internal idling of the specified channels and clearing of call references have not yet been completed. 2.2.2 Call States at the Network Side of th
34、e Interface The states that may exist on the network side of the user-network interface are defined in this subclause. 2.2.2.1 Null (Rest 0) No transaction exists. 2.2.2.2 Restart Request (Rest 1) This state exists for a restart transaction when the network has sent a restart request but has not yet
35、 re-ceived an acknowledgment response from the user. 2.2.2.3 Restart (Rest 2) This state exists when a request for a restart has been received from the user and the internal idling of the specified channels and clearing of call references have not yet been completed. 3 Message Functional Definitions
36、 2) access significance, i.e., relevant in the originating and terminating access, but not in the network; 3) dual significance, i.e., relevant in either the originating or terminating access and in the network; or 4) global significance, i.e., relevant in the originating and terminating access and
37、in the network. b) A table listing the codeset 0 and 5 information elements in the order of their appearance in the mes-sage (same relative order for all message types). For each information element, the table indicates: 11 ATIS-1000607.2014 1) the subclause of this standard describing the informati
38、on element; 2) the direction in which it may be sent; i.e., user to network (u n), network to user (n u), or both; NOTE The user-network terminology in this clause refers to the TE -TE, TE - NT2, and NT2 - TE interface structures. Annex D contains a description of the information element usage for s
39、ymmetric NT2 - NT2 interfaces. 3) whether inclusion is mandatory (M) or optional (O), with a reference to notes explaining the cir-cumstances under which the information element shall be included; and 4) the length of the information element (or permissible range of lengths), in octets, where “*” de
40、-notes an undefined maximum length, which may be network- or service-dependent. NOTE All messages may contain information elements from codesets 5, 6, and 7 and corresponding locking shift in-formation elements that comply with the coding rules specified in 4.5.2 4.5.4. Codeset 6 and 7 information e
41、lements, however, are not listed in this clause. c) Further explanatory notes as necessary. 12 ATIS-1000607.2014 3.1 Messages for Circuit-Mode Connection Control Table 1 summarizes the messages for circuit-mode connection control. Table 1 Messages for circuit-mode connection control Message Referenc
42、e Message Reference Call establishment messages: Call Clearing Messages: ALERTING 3.1.1 DISCONNECT 3.1.5 CALL PROCEEDING 3.1.2 RELEASE 3.1.9 CONNECT 3.1.3 RELEASE COMPLETE 3.1.10 CONNECT ACKNOWLEDGE 3.1.4 PROGRESS 3.1.8 Miscellaneous messages: SETUP 3.1.11 INFORMATION 3.1.6 SETUP ACKNOWLEDGE 3.1.12
43、NOTIFY 3.1.7 STATUS 3.1.13 STATUS ENQUIRY 3.1.14 NOTE In ATIS-1000607, support of user-user signaling was included for a number of reasons, including support of additional compatibility checking upon bilateral agreement with other users, or in accordance with other standards (e.g., ITU-T Recommendat
44、ion X.213). To utilize this capability, the user-user information element may be included in the ALERTING, CONNECT, DISCONNECT, PROGRESS, RELEASE, RE-LEASE COMPLETE, and SETUP messages. Details of this capability (implicit type 1 user-user signaling) are given ATIS-1000621. 3.1.1 ALERTING This messa
45、ge is sent by the called user to the network and by the network to the calling user to indicate that called user alerting has been initiated. Table 2 - ALERTING message content Type: ALERTING Significance: global Direction: both Information Element Reference Direction Type Length Protocol discrimina
46、tor 4.2 both M 1 Call reference 4.3 both M 2-* Message type 4.4 both M 1 Bearer capability 4.5.5 both O (Note 1) 2-12 Channel Identification 4.5.12 both (Note 2) O (Note 3) 2-* Progress indicator 4.5.21 both O (Note 4) 2-4 Display 4.5.15 n u O (Note 5) 2-82 Signal 4.5.24 n u O (Note 6) 2-3 13 ATIS-1
47、000607.2014 High layer compatibility 4.5.16 both O (Note 7) 2-5 Locking shift 4.5.3 n u O (Note 8) 1 Display text 4.6.2 n u O (Note 5) 2-* NOTES 1 Included if the optional procedures of 5.11 for bearer capability selection apply. When present, progress description value 5 “interworking has occurred
48、and has resulted in a telecommunication service change“ shall also be present. 2 May be included in the network-to-user direction for support of the procedures in Annex D. 3 Mandatory if this message is the first message in response to a SETUP message. 4 Included in the event of interworking. Includ
49、ed in the network-to-user direction in connection with the provision of in-band information and patterns. Included in the user-to-network direction in connection with the provision of in-band information and patterns if Annex N is implemented or in accordance with the procedures of 5.11.3 and 5.12.3. 5 Included if the network provides information that can be presented to the user. 6 Included if the network optionally provides additional information describing tones. 7 Included if the optional procedures of 5.12 for high layer compatibility selection apply. W
