TIA-41 640-E-1-2012 Mobile Application Part (MAP)- Intersystem Operations (Incorprated Addendum to TIA-41 640-E).pdf

1、 TIA-41.640-E-1E (Addendum to TIA-41.640-E) August 2012Mobile Application Part (MAP)- Intersystem Operations ANSI/TIA-41.640-E-1E-2012 APPROVED: AUGUST 2, 2012 NOTICE TIA Engineering Standards and Publications are designed to serve the public interest through eliminating misunderstandings between ma

2、nufacturers 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 preclude any memb

3、er 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 Publications are ado

4、pted 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 purport to address

5、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. SP-3-3590.6

6、40-RV5-AD1-E-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 Department 2500 W

7、ilson 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/standards/cata

8、log/ 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 portions of this d

9、ocument, 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 is no assur

10、ance 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 use of intell

11、ectual 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 from the hold

12、er 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, which are ins

13、tead 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 Document or i

14、ts 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 such refere

15、nce 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; (ii) TIAs pol

16、icy 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 to TIA of a

17、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 the Documen

18、t. 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 PROPERTY R

19、IGHTS. 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 SERVICE REFERRE

20、D 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 CONSEQUENTIAL

21、 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 OF DAMAGES I

22、S 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-640-E v2.0 July 2007 Incorporated changes from Miscel-laneous Rev. E standards.X.S0004-640-E v2.0123456789101112131415161

23、718192021222324252627282930313233343536373839404142434445464748495051525354555657585960640 -1 Analyzed InformationPART 640INTERSYSTEM PROCEDURES1 ANALYZED INFORMATION1.1 MSC Initiating an Analyzed InformationWhen the MSC determines that an active Advanced_Termination trigger orSpecific_Called_Party_

24、Digit_String trigger has been encountered requiring call processing to besuspended while an SCF network entity executes service logic, the MSC shall perform the following: 1 Include the BillingID parameter set to the billing identifier for the call assigned by the current Originating MSC.2 Include t

25、he Digits (Dialed) parameter set to the digits received from the MS.3 Include the MSCID parameter set to the identity of the Originating MSC.4 Include the TransactionCapability parameter set to identify the current capabilities.5 Include the TriggerType parameter set to identify the trigger that was

26、 encountered.6 Include the WINCapability parameter set to identify the current TriggerCapability and the current WINOperationsCapability.7 Send an AnalyzedInformation INVOKE to the SCF network entity address obtained from the TriggerAddressList parameter for the trigger that was encountered.8 Start

27、the Analyzed Information Timer (ANZT).9 WAIT for Analyzed Information response:10 WHEN a RETURN RESULT is received:10-1 Stop timer (ANZT).10-2 IF the message can be processed:10-2-1 IF the incoming call is still connected:10-2-1-1 IF the AnnouncementList parameter is received:10-2-1-1-1 Execute “Pla

28、y All Announcements in the AnnouncementList” task (seePart630,sec.2.5).10-2-1-2 ENDIF.10-2-1-3 IF the AccessDeniedReason parameter is received AND IF it can be acted upon:10-2-1-3-1 Execute the “Apply Access Denial Treatment” task (seePart630,sec.4.5).10-2-1-3-2 Exit this task.10-2-1-4 ENDIF10-2-1-5

29、 IF the ActionCode parameter is received:10-2-1-5-1 Execute the “MSC ActionCode Processing” task (seePart630,sec.2.9).10-2-1-6 ENDIF.10-2-1-7 IF the TerminationList parameter is received:X.S0004-640-E v2.0MSC Initiating an Analyzed Information123456789101112131415161718192021222324252627282930313233

30、343536373839404142434445464748495051525354555657585960640 -210-2-1-7-1 Return to the Calling Task.10-2-1-8 ENDIF.10-2-1-9 IF the Digits (Dialed) parameter is received:10-2-1-9-1 Set the MS dialed digits to the received Digits (Dialed) parameter value.10-2-1-9-2 IF the type of digits is unknown:10-2-

31、1-9-2-1 Process the dialed number locally to set the PointOfReturn.10-2-1-9-3 ENDIF.10-2-1-10 ELSE:10-2-1-10-1 Use the Digits (Dialed) parameter included in the AnalyzedInformation INVOKE as MS dialed digits.10-2-1-11 ENDIF.10-2-2 ELSE (call abandoned):10-2-2-1 Execute the “Local Recovery Procedures

32、” task (seePart630,sec.5.1).10-2-2-2 Exit this task.10-2-3 ENDIF.10-3 ELSE (the message cannot be processed):10-3-1 Execute the “Local Recovery Procedures” task (seePart630,sec.5.1).10-3-2 Exit this task.10-4 ENDIF.11 WHEN a RemoteUserInteractionDirective INVOKE is received:11-1 IF the call is still

33、 connected11-1-1 Stop timer (ANZT).11-1-2 Execute the “MSC Remote User Interaction” task (see Part 640, sec. 61.2).11-1-3 Start the AnalyzedInformation Timer (ANZT).11-2 ENDIF11-3 Remain in this state.12 WHEN a ConnectResource INVOKE is received:13 Stop the timer (ANZT).13-1 Execute the “MSC Receivi

34、ng ConnectResource INVOKE” task (see Part 640, sec. 12.3).13-2 CASE MSC Connect Resource result OF:13-3 Disconnect Resource received:13-3-1 Start the timer (ANZT).13-3-2 Remain in this state.13-4 AnalyzedInformation RETURN RESULT received:13-4-1 GOTO AnalyzedInformation RETURN RESULT Treatment.13-5

35、SSFT expiration:13-5-1 Start the timer (ANZT).13-5-2 Remain in this state.13-6 call abandoned:13-6-1 Execute the “Local Recovery Procedures” task (seePart630,sec.5.1).13-6-2 Exit this task.X.S0004-640-E v2.0123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051

36、525354555657585960640 -3 MSC Initiating an Analyzed Information13-7 resource disconnect:13-7-1 Start the timer (ANZT).13-7-2 Remain in this state.13-8 failure at MSC:13-8-1 Start the timer (ANZT).13-8-2 Remain in this state.13-9 message error:13-9-1 Start the timer (ANZT).13-9-2 Remain in this state

37、.13-10 ENDCASE.14 WHEN the incoming call disconnects:14-1 Stop the timer (ANZT).14-2 Execute the “Local Recovery Procedures” task (seePart630,sec.5.1).14-3 Exit this task.15 WHEN a RETURN ERROR or REJECT is received:15-1 Stop timer (ANZT).15-2 Execute the “Local Recovery Procedures” task (seePart630

38、,sec.5.1).15-3 Exit this task.16 WHEN timer (ANZT) expires:16-1 Execute the “Local Recovery Procedures” task (seePart630,sec.5.1).16-2 Exit this task.17 ENDWAIT.18 Return to the calling task.X.S0004-640-E v2.0SCF Receiving AnalyzedInformation INVOKE123456789101112131415161718192021222324252627282930

39、313233343536373839404142434445464748495051525354555657585960640 -41.2 SCF Receiving AnalyzedInformation INVOKE When an SCF network entity receives an AnalyzedInformation INVOKE, it shall perform thefollowing:1 IF the received message can be processed:1-1 Execute “WIN Service Logic” task (see Part 65

40、0, sec 3.2).1-2 Relay parameters received from the service logic task.1-3 Send a RETURN RESULT to the requesting MSC.2 ELSE (the received message cannot be processed):2-1 Send a RETURN ERROR with the proper Error Code value (see the following table) to the requesting MSC.3 ENDIF.4 Exit this task.Tab

41、le 1 SCF AnalyzedInformation ResponseProblem Detection and Recommended Response from SCF to MSCRETURN ERRORError CodePROBLEM DEFINITIONUnrecognizedMINThe network entity does not presently have a record for the supplied MobileIdentificationNumber parameter.UnrecognizedESNThe network entity presently

42、has a record for the supplied MobileIdentificationNumber or IMSI parameter, but the supplied ElectronicSerialNumber parameter does not match the ESN in that record.ID/HLRMismatchThe supplied MobileIdentificationNumber or IMSI parameter is not in the network entitys range of MobileIdentificationNumbe

43、rs or IMSIs or the supplied MDN parameter is not in the network entitys range of MDNs.ResourceShortageA required resource (e.g., internal memory record, network entity is fully occupied) is temporarily not available (e.g., congestion).OperationNotSupportedThe requested MAP operation is recognized, b

44、ut not supported by the receiving network entity, or the requesting network entity is not authorized.Note: It is recommended that an SCF network entity support AnalyzedInformation transactions.ParameterErrorA supplied parameter has an encoding problem (e.g., the Digits (Dialed) parameter has an inco

45、nsistent length, digits in the Digits (Dialed) parameter do not meet the BCD specification).Note: Include the Parameter Identifier in question as the FaultyParameter parameter.SystemFailureA required resource (e.g., data base access, functional entity) is not presently accessible due to a failure. H

46、uman intervention may be required for resolution.X.S0004-640-E v2.0123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960640 -5 SCF Receiving AnalyzedInformation INVOKEUnrecognizedParameter-ValueA supplied parameter value is unrecognized or ha

47、s nonstandard values (e.g., Not used, the supplied Digits (Dialed) parameter contain an unexpected Code 11, Code 12, Spare, *, # or ST digit, the supplied Digits (Dialed) parameter is an unexpected length, the Digits (Dialed) parameter is using an unrecognized value for numbering plan, encoding, or

48、type of digits).Note: Include the Parameter Identifier in question as the FaultyParameter parameter.MissingParameterAn expected or required optional parameter (e.g., MSID) was not received.Note: Include the Parameter Identifier in question as the FaultyParameter parameter.UnrecognizedIMSI/TMSI The n

49、etwork entity does not presently have a record for the supplied IMSI parameter.RETURN RESULTAccessDeniedReasonNote: Only RETURN RESULT parameter values needing clarification have been included.Unassigned Directory NumberThe supplied Digits (Dialed) parameter corresponds to a Mobile Directory Number that is within the range of the network entity, but the MobileDirectoryNumber is not presently assigned to an MS.InactiveThe supplied Digits (Dialed) parameter corresponds to an MS within the network entity, but the MS is Inactive (powered down, failed to autono-mously register, has c