ANSI TIA-41.520-E-1-2012 Mobile Application Part (MAP) C TCAP Application Signaling Protocols (Addendum to TIA-41.520-E).pdf

1、 TIA-41.520-E-1E (Addendum to TIA-41.520-E) August 2012Mobile Application Part (MAP) TCAP Application Signaling Protocols ANSI/TIA-41.520-E-1E-2012 APPROVED: AUGUST 8, 2012 NOTICE TIA Engineering Standards and Publications are designed to serve the public interest through eliminating misunderstandin

2、gs 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 such Standards and Publications shall not in any respect prec

3、lude 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, either domestically or internationally. Standards and Publica

4、tions 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 adopting the Standard or Publication. This Standard does not purpor

5、t 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 applicability of regulatory limitations before its use. (From Project No

6、. SP-3-3590.520-RV5-AD1-A, formulated under the cognizance of the TIA TR-45 Mobile and Personal Communications Systems Standards, TR-45.8 Subcommittee on Core Networks- Mobile and Personal Communications Standards). Published by TELECOMMUNICATIONS INDUSTRY ASSOCIATION Standards and Technology Depart

7、ment 2500 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 IHS, USA and Canada (1-877-413-5187) International (303-397-2896) or search online at http:/www.tiaonline.org/sta

8、ndards/catalog/ All rights reserved Printed in U.S.A. NOTICE OF COPYRIGHT This document is copyrighted by the TIA. Reproduction of these documents either in hard copy or soft copy (including posting on the web) is prohibited without copyright permission. For copyright permission to reproduce portion

9、s of this document, please contact the TIA Standards Department or go to the TIA website (www.tiaonline.org) for details on how to request permission. Details are located at: http:/www.tiaonline.org/standards/catalog/info.cfm#copyright or Telecommunications Industry Association Technology (b) there

10、is no assurance that the Document will be approved by any Committee of TIA or any other body in its present or any other form; (c) the Document may be amended, modified or changed in the standards development or any editing process. The use or practice of contents of this Document may involve the us

11、e of intellectual property rights (“IPR”), including pending or issued patents, or copyrights, owned by one or more parties. TIA makes no search or investigation for IPR. When IPR consisting of patents and published pending patent applications are claimed and called to TIAs attention, a statement fr

12、om the holder thereof is requested, all in accordance with the Manual. TIA takes no position with reference to, and disclaims any obligation to investigate or inquire into, the scope or validity of any claims of IPR. TIA will neither be a party to discussions of any licensing terms or conditions, wh

13、ich are instead left to the parties involved, nor will TIA opine or judge whether proposed licensing terms or conditions are reasonable or non-discriminatory. TIA does not warrant or represent that procedures or practices suggested or provided in the Manual have been complied with as respects the Do

14、cument or its contents. If the Document contains one or more Normative References to a document published by another organization (“other SSO”) engaged in the formulation, development or publication of standards (whether designated as a standard, specification, recommendation or otherwise), whether

15、such reference consists of mandatory, alternate or optional elements (as defined in the TIA Engineering Manual, 4thedition) then (i) TIA disclaims any duty or obligation to search or investigate the records of any other SSO for IPR or letters of assurance relating to any such Normative Reference; (i

16、i) TIAs policy of encouragement of voluntary disclosure (see Engineering Manual Section 6.5.1) of Essential Patent(s) and published pending patent applications shall apply; and (iii) Information as to claims of IPR in the records or publications of the other SSO shall not constitute identification t

17、o TIA of a claim of Essential Patent(s) or published pending patent applications. TIA does not enforce or monitor compliance with the contents of the Document. TIA does not certify, inspect, test or otherwise investigate products, designs or services or any claims of compliance with the contents of

18、the Document. 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 PARTICULAR PURPOSE OR USE, ITS MERCHANTABILITY AND ITS NONINFRINGEMENT OF ANY THIRD PARTYS INTELLECTUAL

19、 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 STATUTE, RULE OR REGULATION, OR THE SAFETY OR HEALTH EFFECTS OF THE CONTENTS OR ANY PRODUCT OR SERV

20、ICE REFERRED TO IN THE DOCUMENT OR PRODUCED OR RENDERED TO COMPLY WITH THE CONTENTS. 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 CO

21、NSEQUENTIAL DAMAGES (INCLUDING DAMAGES FOR LOSS 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 O

22、F DAMAGES IS A FUNDAMENTAL ELEMENT OF THE USE OF THE CONTENTS HEREOF, AND THESE CONTENTS WOULD NOT BE PUBLISHED BY TIA WITHOUT SUCH LIMITATIONS. REVISION HISTORYRevision Date RemarksX.S0004-520-E v2.0 July 2007 Incorporated changes from Miscel-laneous Rev. E standards.X.S0004-520-E v2.01234567891011

23、12131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960520 -1 APPLICATION SERVICESPART 5201 APPLICATION SERVICES1.1 APPLICATION SERVICES ARCHITECTUREThe Application Services architecture introduced in MAP-500 is reproduced in the following figure.Figure 1 A

24、pplication Services ArchitectureApplication Services are comprised of the ANSI Transaction Capabilities (TC) specified in ANSIT1.114, along with the Mobile Application Part (MAP).The TC Transport, Session, and Presentation layers are null layers in this Standard, just as they aredescribed in ANSI T1

25、.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 MAP Application Services. It is described inthe remainder of this part and in parts MAP-540, -550, -551.ANSI Transaction CapabilitiesApplication

26、 LayerPresentation LayerSession LayerTransport LayerTransaction Capabilities Application Part (TCAP)APPLICATION SERVICESMobile Application Part (MAP)X.S0004-520-E v2.0APPLICATION LAYER STRUCTURE1234567891011121314151617181920212223242526272829303132333435363738394041424344454647484950515253545556575

27、85960520 -21.2 APPLICATION LAYER STRUCTUREThe following figure illustrates the TIA-41 Application Layer Structure.Figure 2 TIA-41 Application Layer StructureAs illustrated, the Mobile Application Part (MAP) defined in this Standard is supported by the ANSITransaction Capabilities Application Part (T

28、CAP). 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-layer, which deals with the exchange of messages containing componentsbetween two MAP entities.Mobile Application Part (MAP)Component sub

29、-layerTransaction sub-layerANSI TCAPApplication Layerto and from underlying layersX.S0004-520-E v2.0123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960520 -3 TCAP FORMATS AND PROCEDURES1.3 TCAP FORMATS AND PROCEDURES1.3.1 Transaction Portio

30、nThis Standard employs the TCAP package formats and procedures defined in ANSI T1.114 with thefollowing exceptions and limitations: Special procedures for “Handover,” defined in the ANSI TCAP standard, are not supported.1.3.2 Component PortionThis Standard employs the TCAP component formats and proc

31、edures defined in ANSI T1.114 withthe following exceptions and limitations: Special procedures for “Handover,” defined in the ANSI TCAP standard, are not supported. The Operation Code Identifier is coded as Private TCAP. The Operation Code is partitioned into an Operation Family followed by a Specif

32、ier associatedwith each Operation Family member. For MAP the Operation Family is coded as decimal 9. BitH of the Operation Family is always coded as 0. A TCAP INVOKE component shall contain a Component ID Length greater than zero. A TCAP RETURN RESULT component shall only be transmitted in response

33、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 (i.e., the received message does not conform to ANSIT1.114.3), a TCAP REJECT component with one of the following Problem Specifie

34、rs shall besent:- All families, General, Transaction Portion: All specifiers.- INVOKE: Unrecognized Correlation ID.- RETURN RESULT: Unrecognized Correlation ID, Unexpected Return Result.- RETURN ERROR: Unrecognized Correlation ID, Unexpected Return Error. If a problem is detected by MAP (i.e., the r

35、eceived message does not conform to MAP), a TCAPREJECT component with one of the following TCAP Problem Specifiers shall be sent:- INVOKE: Duplicate Invoke ID, Unrecognized Operation Code or Incorrect Parameter.- RETURN RESULT: Incorrect Parameter.- RETURN ERROR: Incorrect Parameter, Unrecognized Er

36、ror, Unexpected Error. If an error is detected by a MAP user except SMSDeliveryBackward, SMSDeliveryForward,and SMSDeliveryPointToPoint, a TCAP RETURN ERROR component shall be sent. ForSMSDeliveryBackward, SMSDeliveryForward, and SMSDeliveryPointToPoint, a TCAPRETURN RESULT with an SMS_CauseCode par

37、ameter shall be sent.X.S0004-520-E v2.0TCAP FORMATS AND PROCEDURES123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960520 -4 As exceptions to the TCAP procedures related to the use of Component Types marked as “Last”if a ConnectResource INVO

38、KE, a DisconnectResource INVOKE, a InstructionRequestINVOKE, a RemoteUserInteractionDirective INVOKE, a ResetTimer INVOKE, or anSRFDirective INVOKE is received encoded as a response to the INVOKE component of someother MAP operation, it should not be treated as the final response to that other INVOK

39、Ecomponent. 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 final response to a SeizeResourceINVOKE component.1.3.2.1 TCAP INVOKE ComponentThe structure of an ANSI TCAP package containing an INVOKE com

40、ponent 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-formatted), it shall respond with a REJECT to report this error.2. If a network entity receives an INVOKE and is unable to initiate or complet

41、e the operation,it shall respond with a RETURN ERROR.Table 1 Structure of TCAP Package with INVOKE ComponentPackage Type IdentifierTotal TCAP Message LengthTransaction ID IdentifierTransaction ID LengthTransaction IDsComponent Sequence IdentifierComponent Sequence LengthComponent Type IdentifierComp

42、onent LengthComponent ID IdentifierComponent ID LengthComponent IDsOperation Code IdentifierOperation Code LengthOperation CodeParameter Set IdentifierParameter Set LengthParameter SetX.S0004-520-E v2.012345678910111213141516171819202122232425262728293031323334353637383940414243444546474849505152535

43、4555657585960520 -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 report the completion of the operation, except for themessages HandoffMeasurementRequest and MobileOnChannel.1.3.2.2 TCAP RETURN RES

44、ULT 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 ComponentPackage Type IdentifierTotal TCAP Message LengthTransaction ID IdentifierTransaction ID LengthTransaction IDsComponent Sequen

45、ce IdentifierComponent Sequence LengthComponent Type IdentifierComponent LengthComponent ID IdentifierComponent ID LengthComponent IDsParameter Set IdentifierParameter Set LengthParameter SetX.S0004-520-E v2.0TCAP FORMATS AND PROCEDURES1234567891011121314151617181920212223242526272829303132333435363

46、73839404142434445464748495051525354555657585960520 -61.3.2.3 TCAP RETURN ERROR ComponentThe structure of a TCAP package containing a RETURN ERROR component is shown in thefollowing table.The Parameter Set is encoded as follows:Notes:a. Include if the error involved a specific parameter.1.3.2.3.1 Err

47、or DefinitionsThe detailed handling of operation errors is specified in the operations procedures.Table 3 Structure of TCAP Package with RETURN ERROR ComponentPackage Type IdentifierTotal TCAP Message LengthTransaction ID IdentifierTransaction ID LengthTransaction IDsComponent Sequence IdentifierCom

48、ponent Sequence LengthComponent Type IdentifierComponent LengthComponent ID IdentifierComponent ID LengthComponent IDsError Code IdentifierError Code LengthError CodeParameter Set IdentifierParameter Set LengthParameter SetRETURN ERROR ParametersField Value Type Reference NotesIdentifier Set NATIONA

49、L 18 MLength variable octets MContentsFaultyParameter O 550-2.120 aX.S0004-520-E v2.0123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960520 -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 not mandatory, however, if an erroris detected for one of the examples given, then the in