1、 TIA-41.650-E (Revision of TIA/EIA-41-D) December 2005Mobile Application Part (MAP)- Common Voice Features Procedures ANSI/TIA-41.650-E-2012 APPROVED: NOVEMBER 16, 2005 REAFFIRMED: MAY 3, 2012 NOTICE TIA Engineering Standards and Publications are designed to serve the public interest through elimina
2、ting 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
3、 in 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. S
4、tandards 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 Stan
5、dard 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 u
6、se. (From Project No. ANSI/TIA-PN-41.650-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
7、 standards 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 consis
8、ting 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
9、validity 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 rep
10、resent 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
11、 publication 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 inv
12、estigate 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) Inf
13、ormation 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, insp
14、ect, 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 APPROPRIATE
15、NESS 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
16、ANY 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
17、USE 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 NEGLIGE
18、NCE), 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 Telecommunicat
19、ions Industry Association 2005, All rights reserved.This document is subject to change.Revision Date RemarksIS-41-D December 1997 Initial ANSI publication.TIA-41.650-E July 2005 Initial publication with new part structure.TIA-41.650-E123456789101112131415161718192021222324252627282930313233343536373
20、839404142434445464748495051525354555657585960650 -1 Call Forwarding RoutingPART 650COMMON VOICE FEATURE PROCEDURES1 CALL FORWARDING ROUTING1.1 HLR Select Forward-To or Diversion Number Courtesy Call Point of ReturnUpon request, the HLR shall do the following:1 IF the selected forward-to number or di
21、version number indicates voice mail:(Courtesy call does not apply.)1-1 Set the PointOfReturn to ToneTermination.2 ELSE (directory number is specified):2-1 Include the Digits (Destination) parameter set to the forward-to number or diversion number.2-2 Set the PointOfReturn to PSTNTermination.3 ENDIF.
22、4 Return to calling task via the PointOfReturn.TIA-41.650-EHLR Select Forward-To or Diversion Number Point of Return123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960650 -21.2 HLR Select Forward-To or Diversion Number Point of ReturnUpon r
23、equest, the HLR shall do the following:1 IF the received TransactionCapability parameter has been received AND IF it indicates the system is termination list capable:1-1 IF the selected forward-to number or diversion number indicates voice mail:1-1-1 IF the voice mailbox is not the MIN of the called
24、 subscriber:1-1-1-1 Include the VoiceMailboxNumber set to the appropriate mailbox.1-1-2 ENDIF.1-1-3 IF the system launching the current request is the same as the voice mail system:1-1-3-1 Set the PointOfReturn to LocalTermination.1-1-3-2 Include the TerminationTreatment parameter set to VoiceMailDe
25、livery.1-1-4 ELSE:1-1-4-1 Include the TerminationTreatment set to VoiceMailDelivery.1-1-4-2 Execute the “HLR Initiating a Routing Request” task (see Part 640, sec. 62.1).1-1-4-3 IF Digits (Destination) is received:1-1-4-3-1 Relay the received Digits (Destination).1-1-4-3-2 Set the PointOfReturn to I
26、ntersystemTermination.1-1-4-4 ELSE (The voice mail box cannot be reached):1-1-4-4-1 Optionally, include the AnnouncementCode parameter in the AnnouncementList parameter set to an appropriate announcement.1-1-4-4-2 Set the PointOfReturn to ToneTermination.1-1-4-5 ENDIF.1-1-5 ENDIF.1-2 ELSE (a directo
27、ry number is specified):1-2-1 Include the Digits (Destination) parameter set to the selected forward-to number or diversion number.1-2-2 Set the PointOfReturn to PSTNTermination.1-3 ENDIF.2 ELSE (the system is not termination list capable):2-1 IF the selected forward-to number or diversion number in
28、dicates voice mail:2-1-1 Optionally, include the AnnouncementCode parameter in the AnnouncementList parameter set to an appropriate announcement.2-1-2 Set the PointOfReturn to ToneTermination.2-2 ELSE (a directory number is specified):2-2-1 Include the Digits (Destination) parameter set to the forwa
29、rd-to number or diversion number.2-2-2 Set the PointOfReturn to PSTNTermination.2-3 ENDIF.3 ENDIF.4 Return to calling task via the PointOfReturn.TIA-41.650-E123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960650 -3 Digit Analysis2 DIGIT ANA
30、LYSIS2.1 Termination Address Expansion1 IF extra digits are included with the feature code string:1-1 IF TransactionCapability parameter number of terminations is set to at least one:1-1-1 IF next digit is a pound (#) digit:1-1-1-1 Skip over the pound (#) digit.1-1-1-2 IF termination address can be
31、expanded into a destination address.1-1-1-2-1 Execute the “HLR SPINI Feature Request Invocation” task (see Part 651, sec. 24.4).1-1-1-2-2 IF the SPINI invocation failed:1-1-1-2-2-1 Return to the calling task via the PointOfReturn.1-1-1-2-3 ELSE:1-1-1-2-3-1 Include DestinationDigits parameter set to
32、the destination address.1-1-1-2-3-2 Set PointOfReturn to PSTN Termination.1-1-1-2-4 ENDIF.1-1-1-3 ELSE:1-1-1-3-1 Optionally, include the AnnouncementCode parameter in the AnnouncementList parameter set to an appropriate announcement.1-1-1-3-2 Set PointOfReturn to ToneTermination.1-1-1-4 ENDIF.1-1-2
33、ELSE:1-1-2-1 Optionally, include the AnnouncementCode parameter in the AnnouncementList parameter set to an appropriate announcement.1-1-2-2 Set PointOfReturn to ToneTermination.1-1-3 ENDIF.1-2 ELSE:(Ignore the extra digits, cannot do anything with them.)1-2-1 Set PointOfReturn to ToneTermination.1-
34、3 ENDIF.2 ENDIF.3 Return to the calling task.TIA-41.650-EWIN Voice Feature Procedures123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960650 -43 WIN VOICE FEATURE PROCEDURES3.1 MSC Check of Serial Trigger LimitUpon request, the MSC shall do
35、the following:1 Increment the NumberOfSerialTriggers counter for the current call.2 IF the NumberOfSerialTriggers counter value is greater than the MSC MaximumSerialTriggers value: 2-1 Execute “Local Recovery Procedures” task (see Part 630, sec. 5.1).2-2 Exit this task.3 ENDIF.4 Return to the callin
36、g task.TIA-41.650-E123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960650 -5 WIN Service Logic3.2 WIN Service LogicWhen WIN service logic is invoked, the SCF network entity shall perform the following1:1 Execute the WIN service logic progra
37、m.2 WAIT for completion of WIN service logic execution.3 WHEN execution of WIN service logic is complete:3-1 Include applicable parameters.3-2 Return to the calling task.4 WHEN data is to be retrieved from an SDF network entity:4-1 Execute the “SCF Initiating a Search” task (see Part 640, sec. 63.1)
38、.4-2 Remain in this state.5 WHEN data is to be updated in an SDF network entity:5-1 Execute the “SCF Initiating a Modify task.5-2 Remain in this state.6 WHEN user interaction is required:User interaction required:6-1 IF an SRF network entity external to the MSC is indicated:6-1-1 Execute “SCF Initia
39、ting a Seize Resource” task (see Part 640, sec. 65.1).6-1-2 IF the task was unsuccessful:6-1-2-1 Include parameters for default treatment.6-1-2-2 Return to the calling task.6-1-3 ELSE (the task was successful):6-1-3-1 Execute the ”SCF Initiating Connect Resource” task (see Part 640, sec. 12.1).6-1-3
40、-2 IF the task was unsuccessful:6-1-3-2-1 Include parameters for default treatment.6-1-3-2-2 Return to the calling task.6-1-3-3 ENDIF.6-1-3-4 IF further user interaction is required:6-1-3-4-1 Execute the “SCF Initiating Disconnect Resource” task (see Part 640, sec. 15.1).6-1-3-4-2 GOTO User Interact
41、ion Required.6-1-3-5 ELSEIF immediate disconnection of the MSC to the SRF network entity is required:6-1-3-5-1 Execute the “SCF Initiating Disconnect Resource” task (see Part 640, sec. 15.1).6-1-3-6 ENDIF.6-1-4 ENDIF.6-2 ELSE (an SRF network entity external to the MSC is not indicated):1This procedu
42、re identifies interactions with other procedures and may be different than actual implementations.TIA-41.650-EWIN Service Logic123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960650 -66-2-1 Execute “Initiation of Remote User Interaction Dir
43、ective” task (see Part 640, sec. 59.1).6-3 ENDIF.6-4 Remain in this state.7 WHEN remote service logic execution is required1:7-1 Execute “SCF Initiating Service Request” task (see Part 640, sec. 65.1).7-2 IF the remote service logic execution is unsuccessful:7-2-1 Include parameters for default trea
44、tment.7-2-2 Return to the calling task.7-3 ENDIF.7-4 Remain in this state.8 ENDWAIT.1If there is an interaction between the requesting MSC and an SRF network entity that may interfere with the remote servicelogic execution, the SCF network entity may have to disconnect the MSC from the SRF network e
45、ntity prior to invocation ofremote service logic. This potential interaction should be identified in agreements between the requesting and serving networkentities.THE TELECOMMUNICATIONS INDUSTRY ASSOCIATION TIA represents the global information and communications technology (ICT) industry through st
46、andards development, advocacy, tradeshows, business opportunities, market intelligence and world-wide environmental regulatory analysis. Since 1924, TIA has been enhancing the business environment for broadband, wireless, information technology, cable, satellite, and unified communications. TIA members products and services empower communications in every industry and market, including healthcare, education, security, public safety, transportation, government, the utilities. TIA is accredited by the American National Standards Institute (ANSI).
