ANSI TIA-41.651-E-2005 Mobile Application Part (MAP)- Voice Features Procedures《系统间无线电通信.声音特征》.pdf

《ANSI TIA-41.651-E-2005 Mobile Application Part (MAP)- Voice Features Procedures《系统间无线电通信.声音特征》.pdf》由会员分享，可在线阅读，更多相关《ANSI TIA-41.651-E-2005 Mobile Application Part (MAP)- Voice Features Procedures《系统间无线电通信.声音特征》.pdf（174页珍藏版）》请在麦多课文档分享上搜索。

1、 TIA-41.651-E (Revision of TIA/EIA-41-D) December 2005Mobile Application Part (MAP)- Voice Features Procedures ANSI/TIA-41.651-E-2012 APPROVED: NOVEMBER 16, 2005 REAFFIRMED: MAY 3, 2012 NOTICE TIA Engineering Standards and Publications are designed to serve the public interest through eliminating mi

2、sunderstandings 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. Standard

4、s 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 do

5、es 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. (Fr

6、om Project No. ANSI/TIA-PN-41.651-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 standa

7、rds 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 validit

9、y 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

10、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 public

11、ation 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 investigat

12、e 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) Informatio

13、n 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, te

14、st 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 FO

15、R 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 APP

16、LICABLE 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

17、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), P

18、RODUCT 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 In

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

20、42434445464748495051525354555657585960651-1 Call Delivery (CD)PART 651VOICE FEATURE PROCEDURESThis section describes modular procedures to implement individual features.1 CALL DELIVERY (CD)1.1 HLR CD ActivationUpon request, the HLR shall do the following:1 IF CD is authorized:1-1 Activate CD.1-2 Opt

21、ionally, include the AnnouncementCode parameter in the AnnouncementList parameter set to an appropriate announcement.1-3 Include the FeatureResult parameter set to Successful to indicate successful feature operation.2ELSE:2-1 Optionally, include the AnnouncementCode parameter in the AnnouncementList

22、 parameter set to an appropriate announcement.2-2 Include the FeatureResult parameter set to Unsuccessful to indicate unsuccessful feature operation.3 ENDIF.4 Set PointOfReturn to ToneTermination.5 Return to calling task via the PointOfReturn.TIA-41.651-EHLR CD De-Activation1234567891011121314151617

23、18192021222324252627282930313233343536373839404142434445464748495051525354555657585960651-21.2 HLR CD De-ActivationUpon request, the HLR shall do the following:1 IF CD is authorized:1-1 De-activate CD.1-2 Optionally, include the AnnouncementCode parameter in the AnnouncementList parameter set to an

24、appropriate announcement.1-3 Include the FeatureResult parameter set to Successful to indicate successful feature operation.2ELSE:2-1 Optionally, include the AnnouncementCode parameter in the AnnouncementList parameter set to an appropriate announcement.2-2 Include the FeatureResult parameter set to

25、 Unsuccessful to indicate unsuccessful feature operation.3 ENDIF.4 Set PointOfReturn to ToneTermination.5 Return to calling task via the PointOfReturn.TIA-41.651-E123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960651-3 HLR CD Incoming Call

26、 Invocation1.3 HLR CD Incoming Call InvocationWhen the HLR determines the need for CD incoming call routing, it shall perform the followingtasks:1 IF the addressed MS is at home or CD is active and the MS is roaming:1-1 IF the addressed MS is registered and active:1-1-1 (Load the parameters for the

27、called MS and common parameters outside the TerminationList parameter.)1-1-2 Include the ElectronicSerialNumber to identify the called MS.1-1-3 Include the MSID to identify the called MS.1-1-4 IF the preferred interexchange carrier is applicable for the call:1-1-4-1 Include the Digits (Carrier) para

28、meter.1-1-5 ENDIF.1-1-6 IF an account code is applicable for the call:1-1-6-1 Include the DMH_AccountCodeDigits parameter.1-1-7 ENDIF.1-1-8 IF an alternate billing number is applicable for the call:1-1-8-1 Include the DMH_AlternateBillingDigits parameter.1-1-9 ENDIF.1-1-10 IF a billing number is app

29、licable for the call:1-1-10-1 Include the DMH_BillingDigits parameter.1-1-11 ENDIF.1-1-12 IF a called mobile directory number is applicable for the call:1-1-12-1 Include the MobileDirectoryNumber parameter.1-1-13 ENDIF.1-1-14 IF custom no answer timing is applicable for the call:1-1-14-1 Include the

30、 NoAnswerTime parameter.1-1-15 ENDIF.1-1-16 IF special features are applicable to the called party for the incoming call:1-1-16-1 Include the OneTimeFeatureIndicator parameter.1-1-17 ENDIF.1-1-18 IF special routing is applicable for the incoming call:1-1-18-1 Include the RoutingDigits parameter.1-1-

31、19 ENDIF.1-1-20 IF triggers should be set for the terminating party at the originating switch for the incoming call:1-1-20-1 Include the TerminationTriggers parameter.1-1-21 ENDIF.1-1-22 IF the MS is served by the requesting system:1-1-22-1 Include the DMH_RedirectionIndicator parameter set to CD lo

32、cal.TIA-41.651-EHLR CD Incoming Call Invocation123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960651-41-1-22-2 Optionally, include the AnnouncementCode parameter in the AnnouncementList parameter set to an appropriate announcement.1-1-22-3

33、 IF the requesting MSC is capable of at least one MultipleTerminations according to the TransactionCapability received with the LocationRequest INVOKE:1-1-22-3-1 Include the ElectronicSerialNumber parameter set to identify the called MS within a LocalTermination parameter within a TerminationList pa

34、rameter.1-1-22-3-2 Include the MobileIdentificationNumber parameter, if available, and the IMSI parameter, if available, set to identify the called MS within a LocalTermination parameter within a TerminationList parameter.1-1-22-3-3 Include the TerminationTreatment parameter set to MS Termination wi

35、thin a LocalTermination parameter within a TerminationList parameter.1-1-22-3-4 IF custom alerting is applicable for the call:1-1-22-3-4-1 Include the AlertCode parameter set appropriately.1-1-22-3-5 ENDIF.1-1-22-3-6 IF triggers should be set for the terminating party at the originating switch for t

36、he redirecting call:1-1-22-3-6-1 Include the TerminationTriggers parameter.1-1-22-3-7 ENDIF.1-1-22-3-8 Set the PointOfReturn to MultipleTerminations.1-1-22-4 ELSE (multiple terminations are not allowed):1-1-22-4-1 (Applicable parameter should be already be included.)1-1-22-4-2 Set the PointOfReturn

37、to LocalTermination.1-1-22-5 ENDIF.1-1-23 ELSE (IntersystemTermination applies):1-1-23-1 Include the TerminationTreatment parameter set to MSTermination.1-1-23-2 IF custom alerting is applicable for the call:1-1-23-2-1 Include the AlertCode parameter set appropriately.1-1-23-3 ENDIF.1-1-23-4 IF trig

38、gers should be set for the terminating party at the terminating switch for this call:1-1-23-4-1 Include the TerminationTriggers parameter.1-1-23-5 ENDIF.1-1-23-6 Execute the “HLR Initiating a Routing Request” task (see Part 640, sec. 62.1).1-1-23-7 IF the AccessDeniedReason parameter is received and

39、 it can be acted upon:1-1-23-7-1 Set the denied reason to the received AccessDeniedReason value.1-1-23-8 ENDIF.1-1-23-9 IF the ConditionallyDeniedReason parameter is received and it can be acted upon:1-1-23-9-1 IF the ConditionallyDeniedReason is Waitable:1-1-23-9-1-1 IF Call Waiting is possible bas

40、ed upon the received OneTimeFeatureIndicator:1-1-23-9-1-1-1 Set the denied reason to Allowed.1-1-23-9-1-2 ELSE:1-1-23-9-1-2-1 Set the denied reason to Busy.TIA-41.651-E123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960651-5 HLR CD Incoming

41、 Call Invocation1-1-23-9-1-3 ENDIF.1-1-23-9-2 ENDIF.1-1-23-10 ENDIF.1-1-23-11 IF denied reason value is not Allowed and the AccessDeniedReason parameter can be acted upon:1-1-23-11-1 CASE denied reason OF:1-1-23-11-2 Busy: (This is the Busy PointOfDetection.)1-1-23-11-2-1 Execute the “HLR CFB Busy M

42、S Invocation” task (see Part 651, sec. 2.5).1-1-23-11-2-2 IF the PointOfReturn is indicated:1-1-23-11-2-2-1 GOTO CDPointOfReturn.1-1-23-11-2-3 ENDIF.1-1-23-11-2-4 Execute the “HLR CFD Busy MS Invocation” task (see Part 651, sec. 3.9).1-1-23-11-2-5 IF the PointOfReturn is indicated:1-1-23-11-2-5-1 GO

43、TO CDPointOfReturn.1-1-23-11-2-6 ENDIF.1-1-23-11-2-7 Optionally, include the AnnouncementCode parameter in the AnnouncementList parameter set to an appropriate announcement.1-1-23-11-2-8 Relay the received AccessDeniedReason parameter.1-1-23-11-2-9 Set PointOfReturn to ToneTermination.1-1-23-11-3 Un

44、available: (This is the Unavailable PointOfDetection.)1-1-23-11-3-1 Execute the “HLR CFNA Unavailable MS Invocation” task (see Part 651, sec. 4.7).1-1-23-11-3-2 IF the PointOfReturn is indicated:1-1-23-11-3-2-1 GOTO CDPointOfReturn.1-1-23-11-3-3 ENDIF.1-1-23-11-3-4 Execute the “HLR CFD Unavailable M

45、S Invocation” task (see Part 651, sec. 3.7).1-1-23-11-3-5 IF the PointOfReturn is indicated:1-1-23-11-3-5-1 GOTO CDPointOfReturn.1-1-23-11-3-6 ENDIF.1-1-23-11-3-7 Optionally, include the AnnouncementCode parameter in the AnnouncementList parameter set to an appropriate announcement.1-1-23-11-3-8 Rel

46、ay the received AccessDeniedReason parameter.1-1-23-11-3-9 Set PointOfReturn to ToneTermination.1-1-23-11-4 No Page Response: (This is the Unresponsive PointOfDetection.)1-1-23-11-4-1 Execute the “HLR CFNA Unresponsive MS Invocation” task (see Part 651, sec. 4.8).1-1-23-11-4-2 IF the PointOfReturn i

47、s indicated:1-1-23-11-4-2-1 GOTO CDPointOfReturn.1-1-23-11-4-3 ENDIF.TIA-41.651-EHLR CD Incoming Call Invocation123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960651-61-1-23-11-4-4 Execute the “HLR CFD Unresponsive MS Invocation” task (see

48、 Part 651, sec. 3.8).1-1-23-11-4-5 IF the PointOfReturn is indicated:1-1-23-11-4-5-1 GOTO CDPointOfReturn.1-1-23-11-4-6 ENDIF.1-1-23-11-4-7 Optionally, include the AnnouncementCode parameter in the AnnouncementList parameter set to an appropriate announcement.1-1-23-11-4-8 Relay the received AccessD

49、eniedReason parameter.1-1-23-11-4-9 Set PointOfReturn to ToneTermination.1-1-23-11-5 Inactive: 1-1-23-11-5-1 This is the Inactive PointOfDetection, which is the same as the DEFAULT treatment.1-1-23-11-6 Unassigned directory number:1-1-23-11-6-1 This value is not expected, give DEFAULT treatment.1-1-23-11-7 Termination Denied:1-1-23-11-7-1 This value is not expected, give DEFAULT treatment1-1-23-11-8 DEFAULT: (This is the DEFAULT PointOfDetection.)1-1-23-11-8-1 Set the MS state to inactive.1-1-23-11-8-2 Execute the “HLR CFNA Inactive MS Invocation” task (see Part 651, sec. 4.6).1-1-23-