1、 AMERICAN NATIONAL STANDARD FOR TELECOMMUNICATIONS ATIS-1000669.1999(R2015) Signalling System Number 7 (SS7) Intermediate Network Selection (INS) As a leading technology and solutions development organization, ATIS brings together the top global ICT companies to advance the industrys most-pressing b
2、usiness 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 d
3、evelopment 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 Organization
4、al 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-American Telecommunication Commission (CITEL). For more i
5、nformation, 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 Boar
6、d 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, and that a concerted effort be mad
7、e 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, or procedures not conforming to
8、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 National Standard in the name of
9、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. The procedures of the American Nat
10、ional 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 theirex
11、istence 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 circu
12、mstances give an interpretation of 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 secretari
13、at or sponsor 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 standar
14、d. Purchasers 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 2000 by Allian
15、ce for Telecommunications 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 AmericaiContentsPageForeword ii1 Scope, Purpose,
16、and Application . 12 Normative Reference 13 Definitions and Acronyms. 14 Description of Network Capability. 25 Functional Capabilities and Information Flows . 46 Protocol and procedures 9Figures1 INS Routing Scenario . 32 FE Model for INS 53 SDL Diagram for SEP. 74 SDL Diagram for SCCP Relay Node 85
17、 INS Parameter 96 Intermediate Network Selection SDL 16iiForeword (This foreword is not part of American National Standard T1.669-1999.)This document is entitled American National Standard for Telecommunications - Sig-nalling System Number 7 (SS7) - Intermediate Network Selection (INS). INS is a net
18、-work capability that allows an application process in the origination network to specifya single intermediate signalling network for non-circuit-associated signalling messag-es. This network capability also includes functionality to allow the selected intermedi-ate network to make use of the number
19、 portability routing information derived at anumber-portability-specific translation node. INS has been developed for use be-tween U.S. networks to meet the anticipated needs and applications of those entities.This standard is the result of extensive work by members of the T1S1.3 WorkingGroup on U.S
20、. Standards for Common Channel Signalling.This standard is intended for use in conjunction with American National Standard forTelecommunications - Signalling System Number 7 (SS7) - Signalling ConnectionControl Part (SCCP), T1.112-1996, which includes an overview, messages and sig-nals, protocol for
21、mats, procedures, and a chapter on performance. It should be not-ed, however, that some procedures specific to this standard are extensions beyondT1.112-1996.Footnotes are not officially part of this standard.Future control of this document will reside with Accredited Standards Committee onTelecommu
22、nications, T1. This control of additions to the specification, such as proto-col evolution, new applications and operational requirements, will permit compatibilityamong U.S. networks. Such additions will be incorporated in an orderly manner withdue consideration to the ITU-T layered model principle
23、s, conventions, and functionalboundaries.Suggestions for improvement of this standard will be welcome. These should be sentto the Alliance for Telecommunications Industry Solutions, T1 Secretariat, 1200 GStreet, NW, Suite 500, Washington DC 20005.This standard was processed and approved for submitta
24、l to ANSI by the AccreditedStandards Committee on Telecommunications, T1. Committee approval of this stan-dard does not necessarily imply that all committee members voted for its approval. Atthe time it approved this standard, the T1 Committee had the following members:G. H. Peterson, ChairmanE. R.
25、Hapeman, Vice-ChairmanS. M. Carioti, T1 DisciplinesS. D. Barclay, T1 SecretaryJim Lord, Senior EditorOrganization Represented Name of RepresentativeEXCHANGE CARRIERSAmeritech . Fred KujawskiLarry A. Young (Alt.)AT intermediate network B, intermediate network C, or; intermediate networks C and D (by
26、specifying network D).The INS network capability allows an application or network capability in the origination network(SEP X) to directly or indirectly choose a specific network (A, B, C or D) that the message shouldtraverse if an intermediate network is needed to route towards the destination.INS
27、information may “constrain” or “suggest” a route. Constrained routing information, if present,will allow INS-capable STPs in the message path to constrain the message to route into thespecified network. Suggested routing information, if present, will allow INS-capable signallingpoints in the end-to-
28、end message path to select an available intermediate network if an interme-diate network needs to be traversed toward the destination._3)Note the specification information may be dropped when the constrained routing is satisfied.T1.669-199944.2 Procedures4.2.1 Provision/WithdrawalFrom an end users v
29、iewpoint, services requiring specific intermediate network routing can berealized through the use of INS. An end user cannot directly subscribe to INS, but may sub-scribe to an end-user service that directly or indirectly invokes the INS capability.4.2.2 Normal Procedures4.2.2.1 Activation/Deactivat
30、ionActivation/deactivation may be done either on a service-by-service basis or on a network basisin the origination and destination networks. Activation/deactivation is on a network basis in theintermediate network.4.2.2.2 Invocation and OperationInvocation and operation of this network capability w
31、ill be handled by the application process.4.2.3 Exceptional Procedures (none identified)4.2.4 Alternate Procedures (none identified)4.3 Interworking Considerations (none identified)4.4 Network Capabilities for Charging (none identified)4.5 Interactions with Supplementary Services (none identified)5
32、Functional Capabilities and Information Flows5.1 Functional Entity ModelThis section describes a functional entity model to realize the INS network capability. The func-tional entity model allows for the INS network capability to be used in a number portability envi-ronment. A functional entity (FE)
33、 is a group of functions that cannot be split across multiplenodes. Multiple functional entities can be implemented in a single node. The functional entitymodel of the INS capability is shown in Figure 2.T1.669-19995FE 1 FE 2FE3FE 4Figure 2 FE Model for INS5.1.1 Description of Functional Entity (FE
34、1)FE 1 is a functional entity which, when invoked, determines specification information of a specificintermediate network. It specifies the network by including the specification information as INSrouting information and indicates whether it is constrained or suggested routing information.5.1.2 Desc
35、ription of Functional Entity (FE 2)FE 2 is a functional entity which, when invoked, uses specification information. If the route isconstrained, FE 2 uses the specification information to route toward to the specified network. Ifthe route is suggested and available, FE 2 uses the specification inform
36、ation if and only if anintermediate network must be traversed towards the destination. After using the specificationinformation, FE 2 may indicate that it has been used. Alternatively, FE 2 may delete suggestedinformation and delete constrained information if it has been used.5.1.3 Description of Fu
37、nctional Entity (FE 3)FE 3 is a functional entity which, when invoked by FE 2, may determine and specify a subse-quent SS7 network (e.g., terminating network as a result of GTT). If a subsequent network isspecified, any received suggested routing information becomes constrained routing information.5
38、.1.4 Description of Functional Entity (FE 4)FE 4 is a functional entity that is invoked to pass INS information to an application.5.2 Information Flow ModelFigure 2 illustrates the information flow model among the functional entities for the INS capabil-ity. FE 1 is invoked by an application process
39、 in a node initiating INS routing and it sends thespecification information to FE 2. The actions of FE 2 depend on whether the route is con-strained or suggested. If unused constrained routing information is present, FE 2 uses it to routetoward the specified network.If unused suggested information i
40、s present, FE 2 determines whether the message will leave thisnetwork. If the message will not leave this network, the suggested information is ignored. If themessage will leave this network, the suggested information will be taken into account.When invoked, FE 3 may determine and include specificat
41、ion information for an additional net-work and change the routing to constrained.T1.669-19996FE 4 is invoked in a node if INS routing information has to be passed to an application. If in-voked, FE 4 passes INS information to the application.5.2.1 Invoking the Routing FunctionThe originating applica
42、tion invokes the optional INS routing capability at the SEP and providesthe constrained or suggested routing information for the message. The message is routed fromthe origination network and through the selected intermediate network to the destination net-work.5.2.2 Activating and Deactivating the
43、INS CapabilityThe INS functions are network based. Therefore, activation and deactivation of the INS functionsare network implementation and provisioning activities that are done in each network.5.2.3 Exceptional ProceduresIf an INS-capable node cannot deliver a message to its proper destination thr
44、ough the specifiedintermediate network, or if the constrained or suggested routing information is found to be incor-rect, and a negative acknowledgment needs to be returned, then the negative acknowledgmentshould be sent though the intermediate network received in the INS routing information in theo
45、riginal message. In other instances of message discard, normal SS7 exceptional proceduresfor non-circuit-related messages apply.5.3 Allocation of Functions to EquipmentFE 1 will be invoked by an application process in an initiating node in the origination network.Therefore, FE 1 will reside at a SEP
46、. If INS information is received in a destination node wherethe application resides, FE 4 may be invoked to pass the INS information to the application.Therefore, FE 4 will also reside at a SEP.FE 2 and FE 3 are invoked in signalling points in the end-to-end message path where routingfunctions using
47、 INS information are performed. Therefore, FE 2 and FE 3 will reside at SCCPRelay nodes that are INS-capable.Figure 3 is the SDL diagram for the SEP at the origination or destination network. Figure 4 is theSDL diagram for a SCCP Relay node.5.4 Limiting Assumptions The INS routing function may be in
48、dependently invoked by the originating application on aper-message basis. The originating application specifies only one intermediate network.T1.669-19997IDLESS7MessageFollow currentProceduresApplicationindicationDestination SEPdetermine andincludespecificationinformation forone networkYesINSinvoked
49、?NoSS7MessageApplicationRequestOrgination SEPFollow currentproceduresIDLEFigure 3 SDL Diagram for SEPT1.669-19998IDLESS7 MessagePerform GTT onCdPA and routebased on currentproceduresNoINS-Capable?SuggestedSS7MessageConstrainedor suggestedrouting?YesYesUse constrainedrouting informationIDLEUse suggestedrouting informationPerform GTT onCdPAINSInvoked?NoYesResult of GTTis in anothernetwork?Route to DPCderived from GTT ofCdPAConstrainedNoFigure 4 SDL Diagram for SCCP Relay NodeT1.669-199996 Protocol and procedures6.1 Protocol and procedural assumptions No changes are
