ATIS 1000666A-2000 Supplement to ATIS-1000666 1999 Operator Services Network Capability (OSNC) and Release to Pivot (RTP) (Supplement to 1000666 Formerly ATIS T1 666a).pdf

1、 AMERICAN NATIONAL STANDARD FOR TELECOMMUNICATIONS ATIS-1000666.a.2000(R2014) Supplement to ATIS-1000666, Interactions Between the Operator Services Network Capability (OSNC) and Release to Pivot (RTP) As a leading technology and solutions development organization, ATIS brings together the top globa

2、l 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 of service, billing support, oper

3、ations, 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 the American National Standards I

4、nstitute (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 sectors, and a member of the Inter-A

5、merican 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 by the standards developer. Consensu

6、s 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. Consensus requires that all views and objec

7、tions 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 manufacturing, marketing, purchasing, or usin

8、g 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 right or authority to issue an interpre

9、tation 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 National Standard may be revised or wi

10、thdrawn 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 calling or writing the American Nat

11、ional Standards Institute. Notice of Disclaimer & Limitation of Liability The information provided in this document is directed solely to professionals who have the appropriate degree of experience to understand and interpret its contents in accordance with generally accepted engineering or other pr

12、ofessional standards and applicable regulations. No recommendation as to products or vendors is made or should be implied. NO REPRESENTATION OR WARRANTY IS MADE THAT THE INFORMATION IS TECHNICALLY ACCURATE OR SUFFICIENT OR CONFORMS TO ANY STATUTE, GOVERNMENTAL RULE OR REGULATION, AND FURTHER, NO REP

13、RESENTATION OR WARRANTY IS MADE OFMERCHANTABILITY OR FITNESS FOR ANY PARTICULAR PURPOSE OR AGAINST INFRINGEMENT OF INTELLECTUAL PROPERTY RIGHTS. ATIS SHALL NOT BE LIABLE, BEYOND THE AMOUNT OF ANY SUM RECEIVED IN PAYMENT BY ATIS FOR THIS DOCUMENT, AND IN NO EVENT SHALL ATIS BE LIABLE FOR LOST PROFITS

14、 OR OTHER INCIDENTAL OR CONSEQUENTIAL DAMAGES. ATIS EXPRESSLY ADVISES THAT ANY AND ALL USE OF OR RELIANCE UPON THE INFORMATION PROVIDED IN THIS DOCUMENT IS AT THE RISK OF THE USER. NOTE - The users attention is called to the possibility that compliance with this standard may require use of an invent

15、ion covered by patent rights. By publication of this standard, no position is taken with respect to whether use of an invention covered by patent rights will be required, and if any such use is required no position is taken regarding the validity of this claim or any patent rights in connection ther

16、ewith. Please refer to http:/www.atis.org/legal/patentinfo.asp to determine if any statement has been filed by a patent holder indicating a willingness to grant a license either without compensation or on reasonable and non-discriminatory terms and conditions to applicants desiring to obtain a licen

17、se. ATIS-1000666.a.2000(R2014), Supplement to ATIS-100066 Interactions Between the Operator Services Network Capability (OSNC) and Release to Pivot (RTP) Is an American National Standard developed by the Signaling, Architecture and Control (SAC) Subcommittee under the ATIS Packet Technologies and Sy

18、stems Committee (PTSC). Published by Alliance for Telecommunications Industry Solutions 1200 G Street, NW, Suite 500 Washington, DC 20005 Copyright 2014 by Alliance for Telecommunications Industry Solutions All rights reserved. No part of this publication may be reproduced in any form, in an electro

19、nic retrieval system or otherwise, without the prior written permission of the publisher. For information contact ATIS at 202.628.6380. ATIS is online at . ATIS-1000666.a.2000 (formerly T1.666a-2000) American National Standard for Telecommunications - Supplement to T1.666-1999, Interactions Between

20、the Operator Services Network Capability (OSNC) and Release to Pivot (RTP) Secretariat Alliance for Telecommunications Industry Solutions Approved November 15, 2000 American National Standards Institute, Inc. ii Table of Contents 1 Introduction. 1 2 Normative References 1 3 Abbreviations and Definit

21、ions.1 4 Originating Connection Functions 2 4.1 Normal Procedures . 2 4.2 Functional Entity Model. 2 4.3 Description of Functional Entity AC1 2 4.4 Description of Functional Entity AC2 3 5 Information Flow Model 3 6 Protocol and Procedures 4 6.1 Formats and Codes 4 6.1.1 Parameters for IAM 4 6.1.2 P

22、arameters for Release. 6 6.1.3 Protocol for Notification Message 7 6.2 Procedures 7 6.2.1 OSS Routing Identifier . 8 6.2.2 Returned Information . 8 6.2.3 Monitor Event Request 8 6.2.4 Notification Request. 8 6.2.5 Point Code . 8 6.2.6 Subsystem Number . 9 6.2.7 Accounting Information 9 Table of Figu

23、res Figure 1 - Operator Services Network Capability Functions . 2 Figure 2 - OSNC Forward Information parameter. 4 Figure 3 - Returned Information 5 Figure 4 - Collected Information 5 Figure 5 - OSNC Backward Information parameter 6 AMERICAN NATIONAL STANDARD ATIS-1000666.a.2000American National Sta

24、ndard for Telecommunications - Supplement to T1.666-1999, Interactions Between the Operator Services Network Capability (OSNC) and Release to Pivot (RTP) Annex T (normative) 1 Introduction This Annex describes the additional functions that the Operator Services Network Capability (OSNC) - described

25、in T1.666-1999 - will need to perform when invoking the Release to Pivot (RTP) network capability - described in T1.661-1997. These functions are activated on a per-switch basis and are only activated when the Release to Pivot network capability is also active. In particular, the originating end off

26、ice and the operator services switch may activate these functions independently, though RTP will not be invoked for a given call unless both switches have these functions active. This Annex applies to an OSNC Originating Connection or to a Type 2 Transfer Connection. No additional changes to the sco

27、pe, purpose and application of the Operator Services Network Capability are required. 2 Normative References The following documents contain provisions that, through reference in this text, constitute provisions of this American National Standard. These are in addition to the documents listed in cla

28、use 2 of other sections of this document. T1.114-2000, Signaling System Number 7 (SS7) - Transaction Capabilities Application Part (TCAP). T1.401-1993, Interface Between Carriers and Customer Installations - Analog Voicegrade Switched Access Lines Using Loop-Start and Ground-Start Signaling. T1.661-

29、2000, SS7 - Release to Pivot (RTP). 3 Abbreviations and Definitions IAM Initial Address Message ISDN Integrated Services Digital Network ISUP ISDN User Part ATIS-1000666.a.2000 2 OSNC Operator Services Network Capability OSS Operator Services System PIN Personal Identification Number RTP Release to

30、Pivot ST Start Signal TCAP Transaction Capabilities Application Part 4 Originating Connection Functions 4.1 Normal Procedures During establishment of the originating connection, the network may add an offer of RTP functionality to the call setup request that results from an operator services request

31、. The operator service may then invoke RTP when a new destination is determined for the call. Additional information may be exchanged to facilitate: returning the call to the RTP-invoking exchange, notification to the RTP-invoking exchange of the disposition of the call, and proper accounting1. 4.2

32、Functional Entity Model AC 2AC 2AC 1OC 2TC 1invoking serviceFE 1 FE 2 FE 3 FE 4 FE 5OC 1optional optionalUSERFE 6optionalTC 2FE 7Figure 1 - Operator Services Network Capability Functions 4.3 Description of Functional Entity AC1 AC1 provides operator-services specific functionality in support of the

33、invocation of RTP. During initial call establishment, AC1 is able to: 1Note that the internetwork exchange of accounting information may require agreements that are outside the scope of this standard. ATIS-1000666.a.2000 3 use RTP functionality to assure an offer of RTP is sent forward with “Redirec

34、tion Possible Any Time During the Call.” specify “OSNC” as a Reason why RTP may be invoked. indicate forward the specific OSNC-related functions that are allowed on the call. On invocation of RTP at AC1 by AC2, AC1 is able to: monitor the pivoted call to provide notification to AC2 of the dispositio

35、n of the call. store information from AC2 to be returned to AC2 in the event the call is returned to AC2. monitor the call for the “#” or “*” indication that the call should be returned to AC2 and optionally collect user digits to be forwarded with the call setup. The “#”and “*” indications are spec

36、ified in T1.401-1993, using the frequency pairs 1477/941 Hz and 1209/941 Hz, respectively. use the RTP “return to invoking exchange” function to return the call to AC2, optionally using routing information supplied by AC2. 4.4 Description of Functional Entity AC2 AC2 provides operator-services speci

37、fic functionality in support of the invocation of RTP. On receipt of a call offering RTP with a reason of “OSNC,” AC2 is able to: alert the invoking service of available OSNC-related functions allowed on the call. respond to a request from the invoking service to invoke RTP to deliver the call to a

38、new destination, including information required to support the desired OSNC-related functions. receive notification of disposition of the call after the call has been released to AC1. deliver to the invoking service a call received by FE3 with an indication the call is being returned to AC2 followin

39、g detection of a requested “#” or “*” signal from the user. The “#” and “*” indications are specified in T1.401-1993. 5 Information Flow Model During initial call setup, OC1 is enhanced by the functions of AC1 to invoke RTP. RTP functionality is used to indicate that RTP may be invoked “Any Time Dur

40、ing the Call” and to indicate “OSNC” as a reason for invoking RTP. Other services and network capabilities may add additional RTP reasons. AC1 functionality is used to pass additional information with the CALL REQest, as detailed in the protocol and procedures. When the call is released by AC2, RTP

41、functionality is used to indicate that the reason RTP is being invoked is OSNC. AC2 may pass additional information with the Call Disconnect, as detailed in the protocol and procedures. AC1 is an extension of, and resides in the same node as, OC1 functionality. AC2 is an extension of, and resides in

42、 the same node as, either OC2 or TC2. ATIS-1000666.a.2000 4 6 Protocol and Procedures 6.1 Formats and Codes 6.1.1 Parameters for IAM The format of the OSNC Forward Information parameter shall be a constructor as shown in Figure 2. 8 7 6 5 4 3 2 1 Information Type Tag Length Value M Information Type

43、Tag Length Value Figure 2 - OSNC Forward Information parameter The Tags in the OSNC Forward Information parameter are encoded as follows: 0000 0001 Version Control 0000 0010 Returned Information 0000 0011 Collected Information 0000 0100 to spare 0010 0000 0010 0001 Reserved for answer/no answer noti

44、fication version 0010 0010 Reserved for termination notification version 0010 0011 Reserved for notification version 0010 0100 Reserved for accounting information in Release version 0010 0101 Reserved for carrier in Release version 0010 0110 Reserved for monitor event version 0010 0111 to spare 1111

45、 1111 The following codes shall be used in the Version Control field: bit 1: Answer/No Answer support 0 not supported 1 supported bit 2: Termination notification 0 not supported 1 supported ATIS-1000666.a.2000 5 bit 3: Accounting information in Release 0 not supported 1 supported bit 4: Carrier info

46、rmation in Release 0 not supported 1 supported bit 5: Monitor Event 0 not supported 1 supported bit 6: Reserved for extension of Answer/No Answer bit 7-8: Reserved The Returned Information shall be a constructor with the following form: 8 7 6 5 4 3 2 1 First octet of returned information M Last octe

47、t of returned information Figure 3 - Returned Information The Collected Information shall have the following format 8 7 6 5 4 3 2 1 odd/even encoding scheme spare first digit “#” or “*” third digit second digit M filler (if needed) nth address signal Figure 4 - Collected Information The address sign

48、als shall be encoded as follows: 0000 digit 0 0001 digit 1 0010 digit 2 0011 digit 3 0100 digit 4 0101 digit 5 0110 digit 6 ATIS-1000666.a.2000 6 0111 digit 7 1000 digit 8 1001 digit 9 1010 spare (no interpretation) 1011 code 11 1100 code 12 1101 * 1110 # 1111 ST (Reserved) (no interpretation) 6.1.2

49、 Parameters for Release The format of the OSNC Backward Information parameter shall be a constructor as shown in Figure 5. 8 7 6 5 4 3 2 1 Information Type Tag Length Value M Information Type Tag Length Value Figure 5 - OSNC Backward Information parameter The Tags in the OSNC Backward Information parameter are encoded as follows: 0000 0001 OSS Routing Identifier 0000 0010 Returned Information 0000 0011 Monitor Event Accepted 0000 0100 Call Reference Notification Request 0000 0101 Answer/No Answer Notification Accepted 0000 0110 Termination Notification