ANSI ATIS 1000610-1998 Generic Procedures for the Control of ISDN Supplementary Services.pdf

1、 AMERICAN NATIONAL STANDARD FOR TELECOMMUNICATIONS ATIS-1000610.1998(R2013) Generic Procedures for the Control of ISDN Supplementary Services As a leading technology and solutions development organization, ATIS brings together the top global ICT companies to advance the industrys most-pressing busin

2、ess priorities. Through ATIS committees and forums, nearly 200 companies address cloud services, device solutions, emergency services, M2M communications, cyber security, ehealth, network evolution, quality of service, billing support, operations, and more. These priorities follow a fast-track devel

3、opment lifecycle from design and innovation through solutions that include standards, specifications, requirements, business use cases, software toolkits, and interoperability testing. ATIS is accredited by the American National Standards Institute (ANSI). ATIS is the North American Organizational P

4、artner 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 sectors, and a member of the Inter-American Telecommunication Commission (CITEL). For more infor

5、mation, 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, in the judgment of the ANSI Board of

6、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, and that a concerted effort be made tow

7、ards 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, or procedures not conforming to the s

8、tandards. 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 National Standard in the name of the A

9、merican 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. The procedures of the American National

10、 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 Institute. Notice of Disclaimer theirexisten

11、ce does not in any respect preclude anyone, whether he has approvedthe standards or not, from manufacturing, marketing, purchasing, or usingproducts, processes, or procedures not conforming to the standards.The American National Standards Institute does not develop standards andwill in no circumstan

12、ces give interpretation on any American NationalStandard. Moreover, no person shall have the right or authority to issue aninterpretation of an American National Standard in the name of the AmericanNational Standards Institute. Requests for interpretations should beaddressed to the secretariat or sp

13、onsor whose name appears on the titlepage of this standard.CAUTION NOTICE:This American National Standard may be revised orwithdrawn at any time. The procedures of the American National StandardsInstitute require that action be taken periodically to reaffirm, revise, orwithdraw this standard. Purcha

14、sers of American National Standards mayreceive current information on all standards by calling or writing the AmericanNational Standards Institute.American National StandardPublished byAmerican National Standards Institute, Inc.11 West 42nd Street, New York, NY 10036Copyright 1998 by Alliance for Te

15、lecommunications Industry SolutionsAll rights reserved.No part of this publication may be reproduced in anyform, in an electronic retrieval system or otherwise,without prior written permission of the publisher.Printed in the United States of AmericaiContentsPageForewordii1Purpose, scope, and applica

16、tion 12Normative references . 13Requirements . 2Tables7-10CALL PROCEEDING message content 67-11CONNECT message content. 77-12RELEASE message content 87-13RELEASE COMPLETE message content . 97-14SETUP message content. 108-2Information elements specific to supplementary service control 118-5Facility i

17、nformation element . 138-17Bearer capability information element for NCICS 198-18Channel identification information element 218-19Reason for Redirection codepoints 22Figures8-2Facility information element . 128-2aNFE Component ASN.1 Structure . 158-2bNetwork Protocol Profile Component ASN.1 Structur

18、e 168-2cInterpretation Component ASN.1 Structure . 188-10Bearer capability information element 198-11Channel identificaion information element . 208-12Redirecting number information element . 228-13Redirecting subaddress information element. 238-14Redirection number information element . 238-15Redir

19、ection subaddress information element. 24AnnexesDDisplay Procedures 25ECall Independent Signaling Procedures . 32F Bibliography 37iiForeword(This foreword is not part of American National Standard T1.610-1998.)This standard specifies the generic procedures applicable for the control of Integrat-ed S

20、ervices Digital Network (ISDN) supplementary services at the usernetwork in-terface. This standard was developed by Working Group T1S1.1 of Accredited StandardsCommittee T1 Telecommunications. This standard contains three annexes. Annexes D and E are normative and are con-sidered part of the standar

21、d. Annex F is informative and is not considered part of thestandard.Suggestions for improvement of this standard will be welcome. They should be sentto the Alliance for Telecommunications Industry Solutions, T1 Secretariat, 1200 GStreet NW, Suite 500, Washington, DC 20005.This standard was processed

22、 and approved for submittal to ANSI by Accredited Stan-dards Committee T1 Telecommunications. Committee approval of the standard doesnot imply that all committee members voted for its approval. At the time it approved thisstandard, Accredited Standards Committee T1 had the following members:G. H. Pe

23、terson, ChairmanE. R. Hapeman, Vice-ChairmanA. Lai, SecretaryRobin Rossow, Senior EditorSelvan Rengasami, Technical EditorOrganization Represented Name of RepresentativeEXCHANGE CARRIERSAmeritech L. Richard WoodLarry A. Young (Alt.)ATb. an active services timer expires, requiring service deactivatio

24、n;c. an action or operation by a user requires that a service be deactivated;d. an interaction with another supplementary service causes deactivation; that is, anotherservice takes precedence over an active service causing it to be deactivated.ANSI T1.610-19983If the network needs to activate or dea

25、ctivate a supplementary service and the Keypadprotocol applies to the served users interface, then the network may send an appropriatemessage (e.g., INFORMATION message) to the user that includes a Display text informationelement containing an appropriate indication that a supplementary service has

26、been activatedor deactivated. Networks supporting both the Keypad and the Feature key managementprotocols per access, in the network-to-user direction, may choose to send to the user aFeature indication information element in an INFORMATION message that identifies thefeature and whether it is being

27、activated or deactivated. Additional indications may beprovided to the user via the Display text information element in appropriate messages.5.2.3.3 Network initiated service activation or deactivationIt may be necessary for the network to either activate a supplementary service for a user, orto dea

28、ctivate a service that had been previously activated. See 4.5.2.4 for examples of whenthe network may need to activate or deactivate a service.If the network needs to activate or deactivate a supplementary service and the Feature keymanagement protocol applies to a served users interface, then the n

29、etwork shall send to theuser a Feature indication information element in an appropriate message (e.g.,INFORMATION message) that identifies the feature and whether it is being activated ordeactivated. Additional indications may be provided to the user via the Display textinformation element in approp

30、riate messages.10) The following shall be added after the third paragraph of 6.2.1:Enhancements to the procedures may be required for users requesting that no B-Channel bereserved or that the reserved B-Channel be released on a per call basis.11) The following shall be added to 6.2.1.1:Auxillary sta

31、tes v and vi are not supported.12) The following shall be added to 6.2.2.1 at the end of the second paragraph (i.e.,immediately after the line “Active (U10), (N10)”):The Hold function is not applicable to call termination states other than the active state.13) Subclause 6.3.2.1 and its subclauses sh

32、all be replaced with the following text:For supplementary service procedures independent of an active call, the initiating side mustfirst establish a reliable data link connection between the network and the user according tothe data link services described in ANSI T1.602. Once the data link connect

33、ion is established,the user or the network starts the establishment of the signalling connection by transferring aREGISTER message across the usernetwork interface. This signalling connection isidentified by the call reference associated with the REGISTER message. The requestedsupplementary service

34、is identified by the operation value within the Facility informationelement. This signalling connection may be released by the exchange of return result, returnerror or reject component types contained in the Facility information element within aRELEASE COMPLETE message. Alternatively, the Networked

35、 Call Independent, ConnectionOriented procedures of Annex E may be used. The choice of signaling mechanisms isnetwork and application dependent.Examples of message exchange for supplementary service control for various scenarios isdescribed by means of arrow diagrams in Appendix I.To assign a call r

36、eference value and convey the supplementary service invocation, aREGISTER message with a Facility information element is used. The invoke operationcontained in the Facility information element present in the REGISTER message identifies thesupplementary service involved. One of the following will occ

37、ur:ANSI T1.610-199841) When the REGISTER message containing a Facility information element is sent andthe requested service is available, a FACILITY message containing the Facility informationelement may be returned. One or more exchanges of FACILITY messages maysubsequently occur. To terminate the

38、service interaction and release the call referencevalue, a RELEASE COMPLETE message is sent by either side of the interface. TheRELEASE COMPLETE message may also contain the Facility information element.2) If the content of the Facility information element is not understood, then a FACILITYmessage o

39、r a RELEASE COMPLETE message operation with the Facility informationelement is returned with the Reject component type. When the rejection has been returnedin a FACILITY message, the Facility information element can be resent in anotherFACILITY message or the call reference value released with a REL

40、EASE COMPLETEmessage.3) If the content of the Facility information element is understood, but the supplementaryservice request cannot be provided, then a FACILITY message or a RELEASE COMPLETEmessage with the Facility information element is returned with the component return error.When the rejection

41、 has been returned in a FACILITY message, the Facility informationelement can be resent in another FACILITY message or the call reference value releasedwith a RELEASE COMPLETE message.14) The following text shall be added as a new subclause 6.3.7:6.3.7 Invoke ID ReuseThe user or network may begin to

42、 reuse the invoke identifier value after a correlated responseis received or sent (either a Return result, Return error, or Reject component).If a response is not expected, the user or network may begin to reuse the invoke identifiervalue after sending the invoke component.If the operation is of the

43、 class “report failure only” or “report success only,” the operation willdefine when the invoke identifier can be reused.15) The following Note shall be added at the end of 6.3:NOTE Operation classes 2, 3, 4, and 5 as defined in CCITT Recommendation X.219 are valid for use inSupplementary Services d

44、efined in American National Standards.16) The following text shall be added to the end of the next-to-last paragraph of 6.3.6.3.If call clearing was initiated by the requester (e.g., the user), the recipient (e.g., the network)shall continue with the clearing procedures. If the call reference is rel

45、eased before a responsecan be sent, the requestor may not receive a response. In this case, ANSI SupplementaryService Standards will specify additional service-specific procedures.17) The following new paragraph shall be added after the next-to-last paragraph of 6.3.6.4.If a REGISTER message does no

46、t contain the Facility information element, the REGISTERmessage shall be discarded and a RELEASE COMPLETE message containing cause value#96, “mandatory information element is missing” shall be sent.ANSI T1.610-1998518) Replace Table 7-2 with the following (text addition is underlined):Message type:

47、FACILITYSignificance: local or global (Note 1)Direction: bothInformation element Reference Direction Type LengthProtocol discriminator 4.2/T1.607 both M 1Call reference 4.3/T1.607 both M 2-*Message type 8.1 both M 1Facility 8.2 both M (Note 4) 8-*Display 4.5/T1.607 both O (Note 2) (Note 3)M Mandator

48、yO OptionalNOTES1 This message has local significance, however, it may carry information of globalsignificance. This message may have a global significance when it contains a facilityinformation element with a protocol profile coded “Networking Extensions” and for someapplications may need to be con

49、veyed unchanged to the remote user side.2 Included if the network provides information that can be presented to the user.3 The minimum length is 2 octets. The maximum length is network dependent and is either34 or 82 octets.4 Extended Facility information element may be used instead.19) Change the inclusion condition for the Facility information element in Table 7-6 to“Mandatory.” In addition, Note 4 shall be deleted.20) Add the following subclauses to the end of clause 7:7.2 Messages for Call Independent, Connection-Oriented SignallingThis clause defines the messages