1、 TIA-41.520-E (Revision of TIA-41.D) October 2010 Part 520: Wireless Radiotelecommunications Intersystem Operations TCAP Application Transport Signaling Protocols ANSI/TIA-41.520-E-2004 APPROVED: APRIL 20, 2004 REAFFIRMATION: SEPTEMBER 1, 2010 NOTICE TIA Engineering Standards and Publications are de
2、signed to 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 exi
3、stence of 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
4、 members, 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 part
5、ies adopting 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 a
6、pplicability of regulatory limitations before its use. (From Standards Proposal No. 3-3590.520-RV5, formulated under the cognizance of the TIA TR-45.2 Subcommittee on Wireless Intersystem Technology.) Published by TELECOMMUNICATIONS INDUSTRY ASSOCIATION 2002 Standards and Technology Department 2500
7、Wilson Boulevard 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.ti
8、aonline.org/standards/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 licen
9、se agreement. For 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 pre
10、pared by one or 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 Committee
11、s are expected 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
12、preparation in 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 CO
13、PYRIGHTS, OWNED 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
14、WITH REFERENCE 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
15、 FOR A PARTICULAR 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
16、 APPLICABLE STATUTE, 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 L
17、OSS OF BUSINESS, 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 US
18、E OF THE CONTENTS HEREOF, AND THESE CONTENTS WOULD NOT BE PUBLISHED BY TIA WITHOUT SUCH LIMITATIONS. TIA-41-520-E123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960520-1 APPLICATION SERVICESPART 5201 APPLICATION SERVICES1.1 APPLICATION SERV
19、ICES ARCHITECTUREThe Application Services architecture introduced in TIA-41-500 is reproduced in the followingfigure.Figure 1 Application Services ArchitectureApplication Services are comprised of the ANSI Transaction Capabilities (TC) specified in ANSIT1.114, along with the TIA-41 Mobile Applicatio
20、n Part (MAP).The TC Transport, Session, and Presentation layers are null layers in this Standard, just as they aredescribed in ANSI T1.114. They are included here for completeness; future revisions of this Standardmay make use of them.The Application Layer contains the working part of the TIA-41 App
21、lication Services. It is describedin the remainder of this part and in parts TIA-41-540, -550, -551.ANSI Transaction CapabilitiesApplication LayerPresentation LayerSession LayerTransport LayerTransaction Capabilities Application Part (TCAP)APPLICATION SERVICESMobile Application Part (MAP)TIA-41-520-
22、EAPPLICATION LAYER STRUCTURE123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960520-21.2 APPLICATION LAYER STRUCTUREThe following figure illustrates the TIA-41 Application Layer Structure.Figure 2 TIA-41 Application Layer StructureAs illustr
23、ated, the Mobile Application Part (MAP) defined in this Standard is supported by the ANSITransaction Capabilities Application Part (TCAP). TCAP, in turn, is structured in two sub-layers: the component sub-layer, which deals with individual actions or data, called components. the transaction sub-laye
24、r, which deals with the exchange of messages containing componentsbetween two MAP entities.Mobile Application Part (MAP)Component sub-layerTransaction sub-layerANSI TCAPApplication Layerto and from underlying layersTIA-41-520-E1234567891011121314151617181920212223242526272829303132333435363738394041
25、42434445464748495051525354555657585960520-3 TCAP FORMATS AND PROCEDURES1.3 TCAP FORMATS AND PROCEDURES1.3.1 Transaction PortionThis Standard employs the TCAP package formats and procedures defined in ANSI T1.114 with thefollowing exceptions and limitations: Special procedures for “Handover,” defined
26、 in the ANSI TCAP standard, are not supported.1.3.2 Component PortionThis Standard employs the TCAP component formats and procedures defined in ANSI T1.114 withthe following exceptions and limitations: Special procedures for “Handover,” defined in the ANSI TCAP standard, are not supported. The Opera
27、tion Code Identifier is coded as Private TCAP. The Operation Code is partitioned into an Operation Family followed by a Specifier associatedwith each Operation Family member. For TIA-41 the Operation Family is coded as decimal 9.Bit H of the Operation Family is always coded as 0. A TCAP INVOKE compo
28、nent shall contain a Component ID Length greater than zero. A TCAP RETURN RESULT component shall only be transmitted in response to an INVOKEComponent. A TCAP RETURN ERROR component shall only be sent in response to an INVOKEcomponent, not a RETURN RESULT component. If a problem is detected by TCAP
29、(i.e., the received message does not conform to ANSIT1.114.3), a TCAP REJECT component with one of the following Problem Specifiers shall besent:- All families, General, Transaction Portion: All specifiers.- INVOKE: Unrecognized Correlation ID.- RETURN RESULT: Unrecognized Correlation ID, Unexpected
30、 Return Result.- RETURN ERROR: Unrecognized Correlation ID, Unexpected Return Error. If a problem is detected by TIA-41 MAP (i.e., the received message does not conform toTIA-41), a TCAP REJECT component with one of the following TCAP Problem Specifiersshall be sent:- INVOKE: Duplicate Invoke ID, Un
31、recognized Operation Code or Incorrect Parameter.- RETURN RESULT: Incorrect Parameter.- RETURN ERROR: Incorrect Parameter, Unrecognized Error, Unexpected Error. If an error is detected by a TIA-41 MAP user except SMSDeliveryBackward,SMSDeliveryForward, and SMSDeliveryPointToPoint, a TCAP RETURN ERRO
32、R componentshall be sent. For SMSDeliveryBackward, SMSDeliveryForward, andSMSDeliveryPointToPoint, a TCAP RETURN RESULT with an SMS_CauseCode parametershall be sent.TIA-41-520-ETCAP FORMATS AND PROCEDURES123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525
33、354555657585960520-4 As exceptions to the TCAP procedures related to the use of Component Types marked as “Last”if a ConnectResource INVOKE, a DisconnectResource INVOKE, a InstructionRequestINVOKE, a RemoteUserInteractionDirective INVOKE, a ResetTimer INVOKE, or anSRFDirective INVOKE is received enc
34、oded as a response to the INVOKE component of someother TIA-41 operation, it should not be treated as the final response to that other INVOKEcomponent. As exceptions to the TCAP procedures related to the use of Component Types marked as “Last”a SeizeResource RETURN RESULT should not treated as the f
35、inal response to a SeizeResourceINVOKE component.1.3.2.1 TCAP INVOKE ComponentThe structure of an ANSI TCAP package containing an INVOKE component is shown in thefollowing table.1.3.2.1.1 INVOKE Response Philosophy1. If a network entity receives an INVOKE with an incorrect TCAP message (e.g., ill-fo
36、rmatted), it shall respond with a REJECT to report this error.2. If a network entity receives an INVOKE and is unable to initiate or complete the operation,it shall respond with a RETURN ERROR.Table 1 Structure of TCAP Package with INVOKE ComponentPackage Type IdentifierTotal TCAP Message LengthTran
37、saction ID IdentifierTransaction ID LengthTransaction IDsComponent Sequence IdentifierComponent Sequence LengthComponent Type IdentifierComponent LengthComponent ID IdentifierComponent ID LengthComponent IDsOperation Code IdentifierOperation Code LengthOperation CodeParameter Set IdentifierParameter
38、 Set LengthParameter SetTIA-41-520-E123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960520-5 TCAP FORMATS AND PROCEDURES3. If a network entity receives an INVOKE and is able to complete the operation, it shallrespond with a RETURN RESULT to
39、 report the completion of the operation, except for themessages HandoffMeasurementRequest and MobileOnChannel.1.3.2.2 TCAP RETURN RESULT ComponentThe structure of a TCAP package containing a RETURN RESULT component is shown in thefollowing table.Table 2 Structure of TCAP Package with RETURN RESULT C
40、omponentPackage Type IdentifierTotal TCAP Message LengthTransaction ID IdentifierTransaction ID LengthTransaction IDsComponent Sequence IdentifierComponent Sequence LengthComponent Type IdentifierComponent LengthComponent ID IdentifierComponent ID LengthComponent IDsParameter Set IdentifierParameter
41、 Set LengthParameter SetTIA-41-520-ETCAP FORMATS AND PROCEDURES123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960520-61.3.2.3 TCAP RETURN ERROR ComponentThe structure of a TCAP package containing a RETURN ERROR component is shown in thefol
42、lowing table.The Parameter Set is encoded as follows:Notes:a. Include if the error involved a specific parameter.1.3.2.3.1 Error DefinitionsThe detailed handling of operation errors is specified in the operations procedures.Table 3 Structure of TCAP Package with RETURN ERROR ComponentPackage Type Id
43、entifierTotal TCAP Message LengthTransaction ID IdentifierTransaction ID LengthTransaction IDsComponent Sequence IdentifierComponent Sequence LengthComponent Type IdentifierComponent LengthComponent ID IdentifierComponent ID LengthComponent IDsError Code IdentifierError Code LengthError CodeParamete
44、r Set IdentifierParameter Set LengthParameter SetRETURN ERROR ParametersField Value Type Reference NotesIdentifier Set NATIONAL 18 MLength variable octets MContentsFaultyParameter O 550-2.120 aTIA-41-520-E12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849505152
45、5354555657585960520-7 TCAP FORMATS AND PROCEDURESThe following definitions for errors are not exhaustive, but are included so that differentmanufacturers and users have a common understanding of the mapping between a reported error andthe occurrence which generates it. The detection of the errors is
46、 not mandatory, however, if an erroris detected for one of the examples given, then the indicated error code should be used.Implementations should not give cause for these reasons to be generated. ForSMSDeliveryBackward, SMSDeliveryForward, and SMSDeliveryPointToPoint, detected errorsshould be mappe
47、d into the SMS_CauseCode parameter returned in the RETURN RESULT.UnrecognizedMINa. Supplied MIN is not currently served by the VLR.b. Supplied MIN is not currently served by the HLR.c. Supplied MIN is not currently served by the Serving MSC.d. Supplied MIN does not currently have an active call on a
48、n originating MSC.UnrecognizedESNa. Supplied ESN does not match HLRs stored value for subscribers ESN.b. Supplied ESN does not match VLRs stored value for subscribers ESN.c. Supplied ESN is negative listed.ID/HLRMismatcha. Supplied MSID is not resident on the HLR.b. Supplied MDN is not resident on t
49、he HLR.OperationSequenceProblema. Unexpected INVOKE in response to an INVOKE.b. Operation is not allowed in the current state.ResourceShortagea. Network entity congestion.b. Application (or function) congestion.c. Network congestion.d. No transaction IDs available.e. Internal processing resource shortage (memory, I/O, disk, processor, etc.)f. No TLDNs available.OperationNotSupporteda. Operation is not supported on the addressed network entity.TrunkUnavailablea. Specific requested trunk is not available.b. No trunks are available, but are required to perform the op
