TIA-41 600-E-2005 Mobile Application Part (MAP) - Introduction to Procedures《移动应用部分(MAP) -程序介绍》.pdf

1、 TIA-41.600-E (Revision of TIA/EIA-41-D) December 2005Mobile Application Part (MAP) - Introduction to Procedures ANSI/TIA-41.600-E-2012 APPROVED: NOVEMBER 16, 2005 REAFFIRMED: JUNE 22, 2012 NOTICE TIA Engineering Standards and Publications are designed to serve the public interest through eliminatin

2、g 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 such Standards and Publications shall not in

3、 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, either domestically or internationally. Stan

4、dards 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 adopting the Standard or Publication. This Standar

5、d 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 applicability of regulatory limitations before its use.

6、 (From Project No. ANSI/TIA-PN-41.600-E-RF1, formulated under the cognizance of the TIA TR-45 Mobile (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 st

7、andards development 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 consistin

8、g of patents and 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 val

9、idity of any claims 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 repres

10、ent that procedures or practices suggested or provided in the Manual have been complied with as respects the Document 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 pu

11、blication of standards (whether designated as a standard, specification, recommendation or otherwise), whether 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 invest

12、igate the records of any other SSO for IPR or letters of assurance relating to any such Normative Reference; (ii) 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) Inform

13、ation as to claims of IPR in the records or publications of the other SSO shall not constitute identification to 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

14、, test or otherwise investigate products, designs or services or any claims 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 APPROPRIATENES

15、S FOR A PARTICULAR PURPOSE OR USE, ITS MERCHANTABILITY AND ITS NONINFRINGEMENT 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, OR THE SAFETY OR HEALTH EFFECTS 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

17、 OF THE CONTENTS CONTAINED HEREIN, INCLUDING WITHOUT LIMITATION ANY AND 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

18、), 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 CONTENTS HEREOF, AND THESE CONTENTS WOULD NOT BE PUBLISHED BY TIA WITHOUT SUCH LIMITATIONS. REVISION HISTORY Copyright Telecommunication

19、s Industry Association 2005, All rights reserved.This document is subject to change.Revision Date RemarksIS-41-D December 1997 Initial ANSI publication.TIA-41.600-E July 2005 Initial publication with new part structure.TIA-41.600-E123456789101112131415161718192021222324252627282930313233343536373839

20、404142434445464748495051525354555657585960600 -1 OBJECTIVEPART 600 INTRODUCTION TO PROCEDURES1 OBJECTIVEThis document presents the recommendation by which a roaming cellular subscriber may beprovided with “Automatic Roaming,” defined to comprise the following mechanisms:1. Making the identity of the

21、 current serving, or visited system known to the home system.2. Establishing financial responsibility for the roaming subscriber.3. Establishing a valid roamer service profile in a visited system.4. Providing for voice features and Short Message Services to the subscriber and providing ofthose featu

22、re and services while the subscriber is roaming.The transactions are automatic in the sense that they operate in a manner that requires minimalintervention on the part of both the cellular subscriber and parties attempting to place a call to acellular subscriber.1.1 SCOPEThis document describes the

23、signaling and call processing procedures required to perform automaticroaming features and services. The messages required to perform the automatic roaming are definedin Part 540.Conformance with this document shall mean that a systems externally visible behavior is the sameas the externally visible

24、 behavior of the abstract system described here.TIA-41.600-EORGANIZATION123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960600 -21.2 ORGANIZATIONThe 6XX Series are organized as follows:1. This part, Part 600 provides an introduction to the

25、6xx Series.2. Part 630, entitled “Basic Call Processing,” describes the basic call processing states,transitions, actions and the detection points for feature processing.3. Part 640, entitled “Intersystem Procedures,” describes the procedures used betweensystems for handoff, mobility management, aut

26、hentication, voice services and shortmessage services.4. Part 650, entitled “Common Voice Feature Procedures,” describes common procedures forvoice feature control.5. Part 651, entitled “Voice Feature Procedures,” describes the procedures for individualvoice feature control.6. Part 690, entitled “Op

27、eration Timer Values,” summarizes the operation timers used.7. Part 691, entitled “Annexes” describes annex A, B, C, D and E of the 6xx Series.TIA-41.600-E123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960600 -3 DOCUMENTATION CONVENTIONS1.

28、3 DOCUMENTATION CONVENTIONSThe start of a task or procedure is always the first line of text.are statements enclosed in parentheses.: alone on line identifies a point in a task where control may be connected.are expressed as simple statements.CASE OF: DEFAULT: ENDCASE allows multiplebranching with a

29、 single test in a task or procedure. The result of the expression is compared againstthe values in the value labels. If a match is found, the subordinate statements for that value areexecuted up to the next label, default statement or the end of the case, whichever comes first. Whenthe last subordin

30、ate (indented) statement is executed, execution continues with the next statementafter the ENDCASE statement at the same indentation level. Some license can be taken in specifyingthe value for the CASE labels. Multiple values that receive the same processing may be formattedas a comma separated list

31、. For example:1 CASE the color of roses OF:2 Red:2-1 A1.2-2 A2.3 White, Grey, Purple:3-1 B1.3-2 B2.4 DEFAULT:4-1 C1.4-2 C2.5 ENDCASE.6D1.If roses are red, then A1, A2, and D1 are executed.If roses are white, grey, or purple then B1, B2, and D1 are executed.If roses are not red and not white and not

32、grey and not purple then C1, C2, and D1 are executed.Clear is used to reset the value of a message or state variable. If a binaryvalue is not specified it may be assumed to use the value 0.Discard removes a received parameter to prevent it from being relayed.Execute causes a self contained procedure

33、 to be executed.Exit causes the current task to terminate its own operation. The task and all associated variablescease to exist.FOR ENDFOR is used to process multiple iterations of a particularsequence of subordinate processing steps.GOTO is used to transfer execution control to a specified label o

34、r task name.TIA-41.600-EDOCUMENTATION CONVENTIONS123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960600 -4IF ELSEIF ELSEIF ELSE ENDIF allowsbranching in a task or procedure. When the condition is true, the subordinate statements areexecuted

35、, otherwise execution proceeds with the next statement at the same indentation as thecurrent statement. When the last subordinate (indented) statement is executed, execution continueswith the statement after the ENDIF statement at the same indentation level. ELSEIF allows fortesting of multiple rela

36、ted conditions. ELSE allows for processing when the condition(s) are false.For example:7 IF roses are red then:7-1 A1.7-2 A2.8 ELSEIF roses are white then:8-1 B1.8-2 B2.9ELSE:9-1 C1.9-2 C2.10 ENDIF.11 D1.If roses are red then A1, A2, and D1 are executed.If roses are not red, but are white then B1, B

37、2, and D1 are executed.If roses are not red and not white, then C1, C2, and D1 are executed.Include is used to include the particular parameter in an outgoing message.Order is used to indicate the communication of a command to a mobile station (MS) using localdefined procedures and procedures specif

38、ic to the air interface being used by the mobile station.Pass to causes the named message to be transferred from the current taskto the named destination task. The destination task must be on the same functional entity as thesender.Process is used to indicate the execution of locally defined procedu

39、res that are currently not subjectto standardization.Relay is used to include one or more received parameter(s) in the next outgoingmessage.Remain in this state transfers execution control to the containing WAIT statement.Replace is used to change the values of an incoming parameter for use with the

40、 nextoutgoing message.Return causes the current procedure to exit and return control to the calling task or procedure.Send to causes the named message to be transferred from the current taskto the named destination task. The destination may be on any functional entity. RETURN RESULTs,RETURN ERRORs,

41、or REJECTs are understood to be sent to the functional entity sending acorresponding INVOKE.Set is used to change the value of a message parameter or an internal statevariable. If a binary value is not specified it may be assumed to use the value 1.TIA-41.600-E123456789101112131415161718192021222324

42、252627282930313233343536373839404142434445464748495051525354555657585960600 -5 DOCUMENTATION CONVENTIONSSpawn creates an instance of the named task which executes independently of the currenttask.Start causes the named timer to be started from zero.Stop causes the named timer to be stopped.WAIT WHEN

43、 WHEN ENDWAIT identifiesa state where a task waits for the occurrence of one or more possible events. Each WHEN identifiesan event causing a state transition, such as, the arrival of a message or the expiry of a timer. Allstatements subordinate (indented) to the WHEN statement are executed. When the

44、 last subordinate(indented) statement is executed, execution continues with the statement after the ENDWAITstatement at the same indentation level. For example:12 WAIT for message to arrive:13 WHEN message arrives:13-1 A1.13-2 A2.14 WHEN error response arrives:14-1 B1.14-2 B2.15 WHEN timer expires:1

45、5-1 C1.15-2 C2.16 ENDWAIT.17 D1.If the message arrives, then A1, A2, and D1 are executed.If an error response arrives, then B1, B2, and D1 are executed.If the timer expires, then C1, C2, and D1 are executed.WHILE ENDWHILE is used to process zero or more iterations of a particularsequence of subordin

46、ate processing steps while the condition remains true. All subordinate(indented) statements are executed while the condition is true. When the condition is false, executionbegins with the statement following the ENDWHILE statement.WITH : ENDWITH is used to specify the data that is to beoperated on b

47、y the enclosed statement list.TIA-41.600-EINTERSYSTEM HANDOFF PROCEDURES123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960600 -61.4 INTERSYSTEM HANDOFF PROCEDURESAll intersystem handoff messages and associated parameters are defined in Par

48、ts 540 and 550. Part640 provides the transaction procedures defined for the Intersystem Handoff. Timer values arespecified in Part 690. Intersystem handoff uses dedicated voice and data facilities between the MSCs. Future versions mayuse other facilities. Handoffs are allowed to traverse from system

49、 to system with the total number ofinter-MSC facilities in the sequence limited to the value of a parameter (MAXHANDOFF) which isprogrammed by the service providers. Path minimization is used to keep the number of MSCsinvolved in a call to a minimum. Handoff Back and Handoff-To-Third are actions taken to performpath minimization. The number of systems that can be involved in path minimization is limited tothe value of a parameter (TANDEMDEPTH) which is programmed by the service providers.This feature is manufacturer and system independent. This protocol does not preclude h