1、 TIA-41.630-E (Revision of TIA/EIA-41-D) December 2005Mobile Application Part (MAP)- Basic Call Procedures ANSI/TIA-41.630-E-2012 APPROVED: NOVEMBER 16, 2005 REAFFIRMED: APRIL 12, 2012 NOTICE TIA Engineering Standards and Publications are designed to serve the public interest through eliminating mis
2、understandings 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
3、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. Standards
4、 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 Standard doe
5、s 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. (Fro
6、m Project No. ANSI/TIA-PN-41.630-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 standar
7、ds 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 consisting of
8、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 validity
9、 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 represent t
10、hat 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 publica
11、tion 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 investigate
12、 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) Information
13、 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, tes
14、t 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 APPROPRIATENESS FOR
15、 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 APPL
16、ICABLE 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 OF T
17、HE 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), PR
18、ODUCT 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 Telecommunications Ind
19、ustry Association 2005, All rights reserved.This document is subject to change.Revision Date RemarksIS-41-D December 1997 Initial ANSI publication.TIA-41.630-E July 2005 Initial publication with new part structure.TIA-41.630-E12345678910111213141516171819202122232425262728293031323334353637383940414
20、2434445464748495051525354555657585960630 -1 Registration Call TasksPART 630BASIC CALL PROCESSING1 REGISTRATION CALL TASKS1.1 Autonomous or Power-On RegistrationWhen the MSC becomes aware of the presence of an MS through registration, the Serving MSCshould do the following:1 IF the MS is not authenti
21、cated and authentication is active:1-1 IF the MSs AuthenticationCapability indicates the MS shall be authenticated1:1-1-1 Include the SystemAccessType parameter set to Autonomous registration.1-1-2 Execute the “MSC Initiating an Authentication Request” task (see Part 640, sec. 5.1).1-1-3 IF the Anal
22、ogRedirectRecord parameter is received OR IF the CDMARedirectRecord parameter is received (MS is being redirected):1-1-3-1 Send the MS the AnalogRedirectRecord or the CDMARedirectRecord, and the ServiceRedirectionInfo parameter if received.1-1-3-2 Exit this task.1-1-4 ENDIF.1-1-5 IF authentication f
23、ails:1-1-5-1 Execute “Local Recovery Procedures” task (see Part 630, sec. 5.1).1-1-5-2 Exit this task.1-1-6 ENDIF.1-2 ENDIF.2 ENDIF.3 IF the MS is not registered:3-1 Execute the “MSC Initiating MS Registration” task (see Part 640, sec. 57.1).3-2 IF the AnalogRedirectRecord parameter is received OR I
24、F the CDMARedirectRecord parameter is received (MS is being redirected):3-2-1 Send the MS the AnalogRedirectRecord or the CDMARedirectRecord, and the ServiceRedirectionInfo parameter if received.3-2-2 Exit this task.3-3 ENDIF.3-4 IF the MS is not authorized:3-4-1 Execute “Local Recovery Procedures”
25、task (see Part 630, sec. 5.1).3-5 ENDIF.1In addition the MSC shall initiate authentication procedures if there is no AuthenticationCapability information for the MS.TIA-41.630-EPower-Off Deregistration123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354
26、555657585960630 -23-6 Send the MS the RoamingIndication parameter if received, in addition to other messages.4 ENDIF.5 IF the last received MessageWaitingNotificationType is MWI ON and the MessageWaitingNotificationCount indicates that at least one message is waiting:5-1 Execute the “MSC MWN Status
27、Change Invocation” task (see Part 651, sec. 16.9) indicating that message waiting notification is required.6 ENDIF.7 Exit this task.1.2 Power-Off DeregistrationWhen the MSC receives a power-off deregistration, the Serving MSC shall do the following:1 IF the MS is not authenticated and authentication
28、 is active:1-1 IF the MSs AuthenticationCapability indicates the MS shall be authenticated1:1-1-1 Include the SystemAccessType parameter set to Power down registration.1-1-2 Execute the “MSC Initiating an Authentication Request” task (see Part 640, sec. 5.1).1-1-3 IF authentication fails:1-1-3-1 Exe
29、cute “Local Recovery Procedures” task (see Part 630, sec. 5.1).1-1-3-2 Exit this task.1-1-4 ENDIF.1-2 ENDIF.2 ENDIF.3 Execute the “MSC Initiating an MS Inactive” task (see Part 640, sec. 39.1) indicating a power down deregistration.4 Exit this task.1.3 Loading of Profile ParametersUpon request, the
30、HLR or VLR shall do the following:1 Include the AuthenticationCapability parameter set appropriately.2 Include the CallingFeaturesIndicator parameter set appropriately.3 IF carrier selection digits are applicable:3-1 IF the Profile is supported for this transaction:3-1-1 Include the CarrierDigits pa
31、rameter set to the carrier selection digits.3-2 ELSE:3-2-1 Include the Digits (Carrier) parameter set to the carrier selection digits.3-3 ENDIF.4 ENDIF.5 IF default account code digits are applicable for calls by the subscriber:1In addition the MSC shall initiate authentication procedures if there i
32、s no AuthenticationCapability information for the MS.TIA-41.630-E123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960630 -3 Loading of Profile Parameters5-1 IF the Profile is supported for this transaction:5-1-1 Include the DMH_AccountCodeDi
33、gits parameter set to the appropriate default account code digits.5-2 ELSE:5-2-1 (Consider restricting originations.)5-3 ENDIF.6 ENDIF.7 IF billing digits are applicable for calls by the subscriber:7-1 IF the Profile is supported for this transaction:7-1-1 Include the DMH_BillingDigits parameter set
34、 to the appropriate alternate billing digits.7-2 ELSE:7-2-1 (Consider restricting originations.)7-3 ENDIF.8 ELSEIF alternate billing digits are applicable for calls by the subscriber:8-1 IF the Profile is supported for this transaction:8-1-1 Include the DMH_AlternateBillingDigits parameter set to th
35、e appropriate alternate billing digits.8-2 ELSE:8-2-1 (Consider restricting originations.)8-3 ENDIF.9 ENDIF.10 IF multiple Service Types are applicable and authorized for calls by the subscriber:10-1 IF the Profile is supported for this transaction:10-1-1 IF a CDMA MS:10-1-1-1 Include the CDMAServic
36、eOptionList parameter for Service Types authorized for the subscriber.10-1-2 ELSEIF a TDMA MS:10-1-2-1 Include the TDMADataFeaturesIndicator parameter for Service Types authorized for the subscriber.10-1-3 ELSE (Service Types are not Authorized for the subscriber):10-1-3-1 (Consider restricting orig
37、inations)10-1-4 ENDIF.10-2 ENDIF.11 ENDIF.12 IF the subscribers current privileges are geographically restricted:12-1 IF the Profile is supported for this transaction:12-1-1 Include the GeographicAuthorization parameter set appropriately.12-2 ELSE:12-2-1 (Consider restricting originations.)12-3 ENDI
38、F.13 ENDIF.TIA-41.630-ELoading of Profile Parameters123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960630 -414 IF the subscriber is authorized for message waiting notification:14-1 IF the Profile is supported for this transaction:14-1-1 In
39、clude the MessageWaitingNotificationCount parameter set appropriately.14-1-2 Include the MessageWaitingNotificationType parameter set appropriately.14-2 ENDIF.15 ENDIF.16 If a directory number is assigned to the subscriber include the MobileDirectoryNumber parameter set to the subscribers current di
40、rectory number.17 Include the OriginationIndicator parameter set appropriately.18 IF WIN triggers can be processed by the requesting MSC (as indicated by the TransactionCapability parameter):18-1 Include the TriggerAddressList1parameter.19 ENDIF.20 IF origination triggers are required:20-1 IF the Pr
41、ofile is supported for this transaction:20-1-1 Include the OriginationTriggers parameter set appropriately.20-2 ELSE:20-2-1 (Consider restricting originations.)20-3 ENDIF.21 ENDIF.22 IF the subscriber is authorized for PACA:22-1 IF the Profile is supported for this transaction:22-1-1 Include the PAC
42、AIndicator parameter set appropriately.22-2 ENDIF.23 ENDIF.24 IF the subscriber has a preferred language:24-1 IF the Profile is supported for this transaction:24-1-1 Include the PreferredLanguageIndicator parameter set appropriately.24-2 ENDIF.25 ENDIF.26 IF restriction digits are required (as reque
43、sted by the OriginationIndicator parameter):26-1 IF the Profile is supported for this transaction:26-1-1 Include the RestrictionDigits parameter set to the restriction digits.26-2 ELSE:26-2-1 Include the Digits (Destination) parameter set to the restriction digits.26-3 ENDIF.27 ENDIF.28 IF routing d
44、igits are applicable for all calls by the subscriber:1A WIN trigger shall not be set in the TriggerAddressList parameter if the MSCs WINCapability parameter indicates the WINtrigger is not supported.TIA-41.630-E12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849
45、5051525354555657585960630 -5 Loading of Profile Parameters28-1 IF the Profile is supported for this transaction:28-1-1 Include the RoutingDigits parameter set to the appropriate routing digits.28-2 ELSE:28-2-1 (Consider restricting originations.)28-3 ENDIF.29 ENDIF.30 IF the MS is registered to an S
46、MS capable system:30-1 IF the Profile is supported for this transaction:30-1-1 Include the SMS_OriginationRestrictions parameter set appropriately.30-1-2 Include the SMS_TerminationRestrictions parameter set appropriately.30-2 ELSE:30-2-1 (Consider restricting originations.)30-3 ENDIF.31 ENDIF32 IF
47、the current transaction supports local SPINI operation AND IF local SPINI operation is desirable:32-1 Include the SPINITriggers parameter set with the appropriate triggers for local SPINI operation.32-2 Include the SPINIPIN parameter set to the SPINI PIN.33 ENDIF.34 Include the TerminationRestrictio
48、nCode parameter set appropriately.35 IF termination triggers are required:35-1 IF the Profile is supported for this transaction:35-1-1 Include the TerminationTriggers parameter set appropriately.35-2 ELSE:35-2-1 (Consider restricting terminations.)35-3 ENDIF.36 ENDIF.37 IF the subscriber is authoriz
49、ed for Non-Public (NP) mode operation:37-1 IF Profile is supported for this transaction:37-1-1 Include the NonPublicData parameter with the Non-Public Info Display field set to the appropriate value for this MS.37-2 ENDIF.38 ENDIF.39 Return to the calling task.TIA-41.630-EOrigination Call Tasks123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960630 -62 ORIGINATION CALL TASKS2.1 Idle MS OriginationWhen the MS attempts to originate a call, the Serving MSC shall do the following:1 IF an appropriate idle voice or traffic channel
