TIA-41 640-E-2005 Mobile Application Part (MAP) - Intersystem Procedures《移动应用部分(MAP)-内部系统程序》.pdf

上传人:outsidejudge265 文档编号:1060372 上传时间:2019-03-31 格式:PDF 页数:484 大小:5.12MB
下载 相关 举报
TIA-41 640-E-2005 Mobile Application Part (MAP) - Intersystem Procedures《移动应用部分(MAP)-内部系统程序》.pdf_第1页
第1页 / 共484页
TIA-41 640-E-2005 Mobile Application Part (MAP) - Intersystem Procedures《移动应用部分(MAP)-内部系统程序》.pdf_第2页
第2页 / 共484页
TIA-41 640-E-2005 Mobile Application Part (MAP) - Intersystem Procedures《移动应用部分(MAP)-内部系统程序》.pdf_第3页
第3页 / 共484页
TIA-41 640-E-2005 Mobile Application Part (MAP) - Intersystem Procedures《移动应用部分(MAP)-内部系统程序》.pdf_第4页
第4页 / 共484页
TIA-41 640-E-2005 Mobile Application Part (MAP) - Intersystem Procedures《移动应用部分(MAP)-内部系统程序》.pdf_第5页
第5页 / 共484页
点击查看更多>>
资源描述

1、 TIA STANDARD Mobile Application Part (MAP) - Intersystem Procedures TIA-41.640-E (Revision of TIA/EIA-41-D) December 2005 TELECOMMUNICATIONS INDUSTRY ASSOCIATION Representing the telecommunications industry in association with the Electronic Industries Alliance ANSI/TIA-41.640-E-2005Approved: Novem

2、ber 16, 2005Copyright Telecommunications Industry Association Provided by IHS under license with EIANot for ResaleNo reproduction or networking permitted without license from IHS-,-,-NOTICE TIA Engineering Standards and Publications are designed to serve the public interest through eliminating misun

3、derstandings 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 re

4、spect 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, either domestically or internationally. Standards a

5、nd 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 adopting the Standard or Publication. This Standard does

6、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 applicability of regulatory limitations before its use. (From

7、Standards Proposal No. 3-3590.640-RV5, formulated under the cognizance of the TIA TR-45.2 Subcommittee on Core Networks). Published by TELECOMMUNICATIONS INDUSTRY ASSOCIATION Standards and Technology Department 2500 Wilson Boulevard Arlington, VA 22201 U.S.A. PRICE: Please refer to current Catalog o

8、f 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/standards/search_n_order.cfm All rights reserved Printed in U.S.A. Copyr

9、ight Telecommunications Industry Association Provided by IHS under license with EIANot for ResaleNo reproduction or networking permitted without license from IHS-,-,-NOTICE OF COPYRIGHT This document is copyrighted by the TIA. Reproduction of these documents either in hard copy or soft copy (includi

10、ng posting on the web) is prohibited without copyright permission. For copyright permission to reproduce portions of this document, please contact 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.tiaonli

11、ne.org/about/faqDetail.cfm?id=18 OR Telecommunications Industry Association Standards (b) there 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 develop

12、ment or any editing process. 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 by one or more parties. TIA makes no search or investigation for IPR. When IPR consisting of patents an

13、d published pending 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 to, and disclaims any obligation to investigate or inquire into, the scope or validity of any cl

14、aims of IPR. TIA will neither be a party to discussions of any licensing terms or conditions, which 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 proced

15、ures or practices suggested or provided in the Manual have been complied with as respects the Document or its contents. 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 clai

16、ms of compliance with the contents of 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 NON-INFRIN

17、GEMENT 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 STATUTE, RULE OR REGULATION, OR THE SAFETY OR HEALTH EFFECTS

18、 OF THE CONTENTS OR ANY PRODUCT OR SERVICE 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

19、ALL INDIRECT, SPECIAL, INCIDENTAL OR CONSEQUENTIAL 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

20、 SUCH DAMAGES. THE FOREGOING NEGATION OF DAMAGES IS A FUNDAMENTAL ELEMENT OF THE USE OF THE CONTENTS HEREOF, AND THESE CONTENTS WOULD NOT BE PUBLISHED BY TIA WITHOUT SUCH LIMITATIONS. Copyright Telecommunications Industry Association Provided by IHS under license with EIANot for ResaleNo reproductio

21、n or networking permitted without license from IHS-,-,-REVISION HISTORY Copyright Telecommunications Industry Association 2005, All rights reserved.This document is subject to change.Revision Date RemarksIS-41-D December 1997 Initial ANSI publication.TIA-41.640-E July 2005 Initial publication with n

22、ew part structure.Copyright Telecommunications Industry Association Provided by IHS under license with EIANot for ResaleNo reproduction or networking permitted without license from IHS-,-,-Copyright Telecommunications Industry Association Provided by IHS under license with EIANot for ResaleNo reprod

23、uction or networking permitted without license from IHS-,-,-TIA-41.640-E123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960640 -1 Analyzed InformationPART 640INTERSYSTEM PROCEDURES1 ANALYZED INFORMATION1.1 MSC Initiating an Analyzed Informa

24、tionWhen the MSC determines that an active Advanced_Termination trigger orSpecific_Called_Party_Digit_String trigger has been encountered requiring call processing to besuspended while an SCF network entity executes service logic, the MSC shall perform thefollowing: 1 Include the BillingID parameter

25、 set to the billing identifier for the call assigned by the current Originating MSC.2 Include the 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 th

26、e current capabilities.5 Include the TriggerType parameter set to identify the trigger that was 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 addre

27、ss obtained from the TriggerAddressList parameter for the trigger that was encountered.8 Start 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

28、 still connected:10-2-1-1 IF the AnnouncementList parameter is received:10-2-1-1-1 Execute “Play All Announcements in the AnnouncementList” task (see Part 630, 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

29、Access Denial Treatment” task (see Part 630, sec. 4.5).10-2-1-3-2 Exit this task.10-2-1-4 ENDIF10-2-1-5 IF the ActionCode parameter is received:10-2-1-5-1 Execute the “MSC ActionCode Processing” task (see Part 630, sec. 2.9).10-2-1-6 ENDIF.Copyright Telecommunications Industry Association Provided b

30、y IHS under license with EIANot for ResaleNo reproduction or networking permitted without license from IHS-,-,-TIA-41.640-EMSC Initiating an Analyzed Information123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960640 -210-2-1-7 IF the Termin

31、ationList parameter is received:10-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-1-9-2-1 Process the dialed n

32、umber 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” task (see Part 630, sec. 5

33、.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 (see Part 630, 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 connected11-1-1 Sto

34、p timer (ANZT).11-1-2 Execute the “MSC Remote User Interaction” task (see Part 640, sec. 59.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 Receiving ConnectResource I

35、NVOKE” 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 SSFT expiration:13-5

36、-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 (see Part 630, sec. 5.1).Copyright Telecommunications Industry Association Provided by IHS under license with EIANot for ResaleNo reproduction or networking permitted without

37、 license from IHS-,-,-TIA-41.640-E123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960640 -3 MSC Initiating an Analyzed Information13-6-2 Exit this task.13-7 resource disconnect:13-7-1 Start the timer (ANZT).13-7-2 Remain in this state.13-8

38、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.13-10 ENDCASE.14 WHEN the incoming call disconnects:14-1 Stop the timer (ANZT).14-2 Execute the “Local Recovery Procedures” task (see Part 630, sec. 5

39、.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 (see Part 630, sec. 5.1).15-3 Exit this task.16 WHEN timer (ANZT) expires:16-1 Execute the “Local Recovery Procedures” task (see Part 630, sec. 5.1).16-2 Exit

40、 this task.17 ENDWAIT.18 Return to the calling task.Copyright Telecommunications Industry Association Provided by IHS under license with EIANot for ResaleNo reproduction or networking permitted without license from IHS-,-,-TIA-41.640-ESCF Receiving AnalyzedInformation INVOKE1234567891011121314151617

41、18192021222324252627282930313233343536373839404142434445464748495051525354555657585960640 -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 Servic

42、e Logic” task (see Part 650, 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

43、ENDIF.4 Exit this task.Table 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

44、 network entity presently 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

45、 MobileIdentificationNumbers 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

46、operation is recognized, but 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 (Dia

47、led) parameter has an inconsistent 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 acce

48、ssible due to a failure. Human intervention may be required for resolution.Copyright Telecommunications Industry Association Provided by IHS under license with EIANot for ResaleNo reproduction or networking permitted without license from IHS-,-,-TIA-41.640-E123456789101112131415161718192021222324252

49、627282930313233343536373839404142434445464748495051525354555657585960640 -5 SCF Receiving AnalyzedInformation INVOKEUnrecognizedParameter-ValueA supplied parameter value is unrecognized or has nonstandard values (e.g., Not used, the supplied Digits (Dialed) parameter contain an unexpected Code 11, Code 12, Spare, *, # or ST di

展开阅读全文
相关资源
猜你喜欢
相关搜索

当前位置:首页 > 标准规范 > 国际标准 > 其他

copyright@ 2008-2019 麦多课文库(www.mydoc123.com)网站版权所有
备案/许可证编号:苏ICP备17064731号-1