1、 TIA-41.512-E (Revision of TIA-41.D) October 2010 Part 512: Wireless Radiotelecommunications Intersystem Operations IT/SS7 Transport Signaling Protocols ANSI/TIA-41.512-E-2004 APPROVED: APRIL 20, 2004 REAFFIRMATION: SEPTEMBER 1, 2010 NOTICE TIA Engineering Standards and Publications are designed to
2、serve the public interest through eliminating misunderstandings between manufacturers and purchasers, facilitating interchangeability and improvement of products, and assisting the purchaser in selecting and obtaining with minimum delay the proper product for their particular need. The existence of
3、such Standards and Publications shall not in any respect preclude any member or non-member of TIA from manufacturing or selling products not conforming to such Standards and Publications. Neither shall the existence of such Standards and Publications preclude their voluntary use by Non-TIA members,
4、either domestically or internationally. Standards and Publications are adopted by TIA in accordance with the American National Standards Institute (ANSI) patent policy. By such action, TIA does not assume any liability to any patent owner, nor does it assume any obligation whatever to parties adopti
5、ng the Standard or Publication. This Standard does not purport to address all safety problems associated with its use or all applicable regulatory requirements. It is the responsibility of the user of this Standard to establish appropriate safety and health practices and to determine the applicabili
6、ty of regulatory limitations before its use. (From Standards Proposal No. 3-3590.512-RV5, formulated under the cognizance of the TIA TR-45.2 Subcommittee on Wireless Intersystem Technology.) Published by TELECOMMUNICATIONS INDUSTRY ASSOCIATION Standards and Technology Department 2500 Wilson Boulevar
7、d Arlington, VA 22201 U.S.A. PRICE: Please refer to current Catalog of TIA TELECOMMUNICATIONS INDUSTRY ASSOCIATION STANDARDS AND ENGINEERING PUBLICATIONS or call Global Engineering Documents, USA and Canada (1-800-854-7179) International (303-397-7956) or search online at http:/www.tiaonline.org/sta
8、ndards/search_n_order.cfm All rights reserved Printed in U.S.A. PLEASE! DONT VIOLATE THE LAW! This document is copyrighted by the TIA and may not be reproduced without permission. Organizations may obtain permission to reproduce a limited number of copies through entering into a license agreement. F
9、or information, contact: Global Engineering Documents 15 Inverness Way East Englewood, CO 80112-5704 U.S.A. or call U.S.A. and Canada 1-800-854-7179, International (303) 397-7956 NOTICE OF DISCLAIMER AND LIMITATION OF LIABILITY The document to which this Notice is affixed has been prepared by one or
10、 more Engineering Committees of the Telecommunications Industry Association (“TIA”). TIA is not the author of the document contents, but publishes and claims copyright to the document pursuant to licenses and permission granted by the authors of the contents. TIA Engineering Committees are expected
11、to conduct their affairs in accordance with the TIA Engineering Manual (“Manual”), the current and predecessor versions of which are available at http:/www.tiaonline.org/standards/sfg/engineering_manual.cfm. TIAs function is to administer the process, but not the content, of document preparation in
12、accordance with the Manual and, when appropriate, the policies and procedures of the American National Standards Institute (“ANSI”). THE USE OR PRACTICE OF CONTENTS OF THIS DOCUMENT MAY INVOLVE THE USE OF INTELLECTUAL PROPERTY RIGHTS (“IPR”), INCLUDING PENDING OR ISSUED PATENTS, OR COPYRIGHTS, OWNED
13、 BY ONE OR MORE PARTIES. TIA MAKES NO SEARCH OR INVESTIGATION FOR IPR. WHEN IPR CONSISTING OF PATENTS AND PUBLISHED PATENT APPLICATIONS ARE CLAIMED AND CALLED TO TIAS ATTENTION, A STATEMENT FROM THE HOLDER THEREOF IS REQUESTED, ALL IN ACCORDANCE WITH THE MANUAL. TIA TAKES NO POSITION WITH REFERENCE
14、TO, AND DISCLAIMS ANY OBLIGATION TO INVESTIGATE OR INQUIRE INTO, THE SCOPE OR VALIDITY OF ANY CLAIMS OF IPR. ALL WARRANTIES, EXPRESS OR IMPLIED, ARE DISCLAIMED, INCLUDING WITHOUT LIMITATION, ANY AND ALL WARRANTIES CONCERNING THE ACCURACY OF THE CONTENTS, ITS FITNESS OR APPROPRIATENESS FOR A PARTICUL
15、AR PURPOSE OR USE, ITS MERCHANTABILITY AND ITS NON-INFRINGEMENT OF ANY THIRD PARTYS INTELLECTUAL PROPERTY RIGHTS. TIA EXPRESSLY DISCLAIMS ANY AND ALL RESPONSIBILITIES FOR THE ACCURACY OF THE CONTENTS AND MAKES NO REPRESENTATIONS OR WARRANTIES REGARDING THE CONTENTS COMPLIANCE WITH ANY APPLICABLE STA
16、TUTE, RULE OR REGULATION. TIA SHALL NOT BE LIABLE FOR ANY AND ALL DAMAGES, DIRECT OR INDIRECT, ARISING FROM OR RELATING TO ANY USE OF THE CONTENTS CONTAINED HEREIN, INCLUDING WITHOUT LIMITATION ANY AND ALL INDIRECT, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES (INCLUDING DAMAGES FOR LOSS OF BUSINESS
17、, LOSS OF PROFITS, LITIGATION, OR THE LIKE), WHETHER BASED UPON BREACH OF CONTRACT, BREACH OF WARRANTY, TORT (INCLUDING NEGLIGENCE), PRODUCT LIABILITY OR OTHERWISE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. THE FOREGOING NEGATION OF DAMAGES IS A FUNDAMENTAL ELEMENT OF THE USE OF THE CONTEN
18、TS HEREOF, AND THESE CONTENTS WOULD NOT BE PUBLISHED BY TIA WITHOUT SUCH LIMITATIONS. TIA-41-512-E123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960512-1 ITU-T SS7-BASED DATA TRANSFER SERVICESPART 5121 ITU-T SS7-BASED DATA TRANSFER SERVICE
19、S The ITU-T SS7-based Data Transfer Services are comprised of the InternationalTelecommunications Union Signaling System 7 Message Transfer Part (MTP) plus SignalingConnection Control Part (SCCP).1.1 MESSAGE TRANSFER PARTThe MTP is defined in ITU-T Q.701 - Q.710, with the following supplemental info
20、rmation.The MAP messages that are transported on an intersystem basis may be assigned a message priorityvalue of either 0 or 1. The INVOKE, RETURN RESULT, RETURN ERROR, and REJECTcomponents associated with the same operation (e.g., LocationRequest) shall have the samemessage priority value. The reco
21、mmended message priority values are as described inTIA-41-511-E Section 1 Message Transfer Part.The message priority value may be determined by the TIA-41 MAP based on the message type andmay be passed down to the MTP through the SCCP.TIA-41-512-ESIGNALING CONNECTION CONTROL PART12345678910111213141
22、5161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960512-21.2 SIGNALING CONNECTION CONTROL PARTFor TIA-41 applications, the SCCP is defined in ITU-T Q.711 - Q.714, with the following exceptionsand limitations: The SCCP Class 0 connectionless service is requested
23、 from the SCCP. (However, in accordancewith SCCP procedures, if a TIA-41 message is segmented by the SCCP, the sequence of XUDTmessages carrying the segments is sent using SCCP Class 1 sequenced connectionless service.The In-Sequence Delivery Option field of the segmentation parameter within each of
24、 the XUDTmessages is set to 0 to reflect the original request for Class 0 service) Whether to set the return message on error or discard message on error option in the ProtocolClass parameter of the UDT or XUDT message is at the discretion of the implementation. Ifreturn message on error is requeste
25、d by the SCCP user for a segmented message, then only thefirst XUDT message shall have return message on error requested. Use of the following SSN values is recommended:- 5:Mobile Application Part (MAP)- 6:Home Location Register (HLR)- 7:Visitor Location Register (VLR)- 8:Mobile Switching Center (MS
26、C)- 9:Equipment Identification Register(EIR)/Equipment Identification Center (EIC)(reserved)1- 10:Authentication Center (AC/AUC)- TBD: Short Message Service (SMS)2- TBD: Over-The-Air Service Provisioning Function3 In accordance with ITU-T Q.713 an SSN is recommended to be included in all messages ev
27、enif message routing is based on Global Title Translation (GTT). The null SSN (i.e., value 0)should be used when the subsystem is not known (e.g., before a global title translation takesplace). Global title addressing is required on the SCCP Called Party Address and the SCCP CallingParty Address for
28、 international roaming purposes. Global Title Translation on Mobile Identification Number (MIN) for communication with anHLR or MC is left to mutual agreement.1Detailed transactions relative to SSN value 9 are for further study.2The value to be assigned by the carrier.3The value to be assigned by th
29、e carrier.TIA-41-512-E123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960512-3 SIGNALING CONNECTION CONTROL PART Global Title Translation on International Mobile Subscriber Identity (IMSI) can be used forcommunication with the HLR on the sa
30、me or a different national SS7 network. It may also beused for communication to any network element that is identified by an E.212 formatted addresson the same or a different national SS7 network. The following encoding may be used: Table 1 ITU-T SS7 - E.212 Global TitleField Sub-field ValueAddress
31、Indicator Point Code Indicator (PCI) 0 or 1SSN Indicator (SSNI) 1Global Title Indicator (GTI)4 (01002)Routing Indicator (RI) 0Reserved for national use 0 (international use) or 1 (national use)Note: The national/international indicator is intended to indicate the “format“ of the encoding and not the
32、 national or international nature of the type of address. A national/international indicator = 0 means that both the address indicator and the address are encoded according to international specifications. A national/international indicator = 1 means that both the address indicator and the address a
33、re encoded according to national specifica-tions.Subsystem Number Include applicable value if known or zero.Global Title Translation Type 0 Encoding Scheme 1=odd number of digits, 2=evenNumbering Plan 6 (01102)Nature of address indicator4 (00001002)Address Information E.212 IMSI or other E.212 forma
34、tted addressTIA-41-512-ESIGNALING CONNECTION CONTROL PART123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960512-4 Global Title Translation on Mobile Identification Number or International Mobile StationIdentity can be used for communication
35、 with a Message Center based on mutual agreements. Global Title Translation on Mobile Directory Number can be used for routing messages to anHLR connected to the same or different national signaling networks. The following encodingmay be used: When an originating network entity sends an SS7 message
36、within a national SS7 signalingnetwork with a global title in the SCCP called party address field, the SCCP calling partyaddress field should include the point code and subsystem number of the originating networkentity.Table 2 ITU-T SS7 - E.164 Global TitleField Sub-field ValueAddress Indicator Poin
37、t Code Indicator (PCI) 0 or 1SSN Indicator (SSNI) 1Global Title Indicator (GTI)4 (01002)Routing Indicator (RI) 0Subsystem Number Reserved for national use 0 (international use) or 1 (national use)Note: The national/international indicator is intended to indicate the “format“ of the encoding and not
38、the national or international nature of the type of address. A national/international indicator = 0 means that both the address indicator and the address are encoded according to international specifications. A national/international indicator = 1 means that both the address indicator and the addres
39、s are encoded according to national specifica-tions.Subsystem Number Include applicable value if known or zero.Global Title Translation Type 0 Encoding Scheme 1=odd number of digits, 2=evenNumbering Plan 1 (00012)Nature of address indicator4 (00001002)Address Information E.164 Mobile directory numbe
40、rTIA-41-512-E123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960512-5 SIGNALING CONNECTION CONTROL PART When an originating network entity sends an SS7 message across a national SS7 signalingnetwork boundary, the SCCP calling party address
41、field should include an E.212 global titleaddress identifying the originating network entity to allow response messages (RETURNRESULT, RETURN ERROR, or REJECT) to be routed back to the originating network entity. Replies to messages shall use the received Calling Party Address as the Called Party Ad
42、dress.(An exception occurs, if the PC_SSN parameter is received in an AuthenticationRequestINVOKE or in a RegistrationNotification INVOKE. In this case,the address used for theresponse may be derived from the received PC_SSN parameter provided the INVOKE wasreceived from a network entity within the same national SS7 signaling network.) TIA-41-512-ESIGNALING CONNECTION CONTROL PART123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960512-6
