1、 TIA-41.329-E August 2012Mobile Application Part (MAP) - Voice Feature Scenarios: Message Waiting Notification ANSI/TIA-41.329-E-2012 APPROVED: AUGUST 10, 2012 NOTICE TIA Engineering Standards and Publications are designed to serve the public interest through eliminating misunderstandings between ma
2、nufacturers 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 respect preclude any memb
3、er 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 and Publications are ado
4、pted 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 not purport to address
5、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 Project No. SP-3-3590.3
6、29-RV5-A, formulated under the cognizance of the TIA TR-45 Mobile and Personal Communications Systems Standards, TR-45.8 Subcommittee on Core Networks- Mobile and Personal Communications Standards). Published by TELECOMMUNICATIONS INDUSTRY ASSOCIATION Standards and Technology Department 2500 Wilson
7、Boulevard Arlington, VA 22201 U.S.A. PRICE: Please refer to current Catalog of TIA TELECOMMUNICATIONS INDUSTRY ASSOCIATION STANDARDS AND ENGINEERING PUBLICATIONS or call IHS, USA and Canada (1-877-413-5187) International (303-397-2896) or search online at http:/www.tiaonline.org/standards/catalog/ A
8、ll rights reserved Printed in U.S.A. NOTICE OF COPYRIGHT This document is copyrighted by the TIA. Reproduction of these documents either in hard copy or soft copy (including posting on the web) is prohibited without copyright permission. For copyright permission to reproduce portions of this documen
9、t, please contact the 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.tiaonline.org/standards/catalog/info.cfm#copyright or Telecommunications Industry Association Technology (b) there is no assurance t
10、hat 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 development or any editing process. The use or practice of contents of this Document may involve the use of intellectual
11、 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 and published pending patent applications are claimed and called to TIAs attention, a statement from the holder the
12、reof 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 claims of IPR. TIA will neither be a party to discussions of any licensing terms or conditions, which are instead l
13、eft 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 procedures or practices suggested or provided in the Manual have been complied with as respects the Document or its con
14、tents. If the Document contains one or more Normative References to a document published by another organization (“other SSO”) engaged in the formulation, development or publication of standards (whether designated as a standard, specification, recommendation or otherwise), whether such reference co
15、nsists 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 the records of any other SSO for IPR or letters of assurance relating to any such Normative Reference; (ii) TIAs policy of
16、 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 as to claims of IPR in the records or publications of the other SSO shall not constitute identification to TIA of a claim
17、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, test or otherwise investigate products, designs or services or any claims of compliance with the contents of the Document. ALL
18、 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 NONINFRINGEMENT OF ANY THIRD PARTYS INTELLECTUAL PROPERTY RIGHTS.
19、 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 OF THE CONTENTS OR ANY PRODUCT OR SERVICE REFERRED TO I
20、N 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 ALL INDIRECT, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAG
21、ES (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 SUCH DAMAGES. THE FOREGOING NEGATION OF DAMAGES IS A FU
22、NDAMENTAL ELEMENT OF THE USE OF THE CONTENTS HEREOF, AND THESE CONTENTS WOULD NOT BE PUBLISHED BY TIA WITHOUT SUCH LIMITATIONS. REVISION HISTORYRevision Date RemarksX.S0004-329-E v1.0 April 2008 Initial publication.X.S0004-329-E v1.01234567891011121314151617181920212223242526272829303132333435363738
23、39404142434445464748495051525354555657585960329-1 INTRODUCTION1 INTRODUCTIONUnless otherwise noted, the scenarios in this section depict features operating individually; i.e.,feature interactions are not considered unless specifically noted. Also, please note that the scenarios in this section do no
24、t include a complete listing of operationparameters, either in the figures or in the accompanying text descriptions. Parameters areincluded where they are deemed necessary to improve the understanding of the scenario. For acomplete description of the parameters associated with each operation, refer
25、to Parts 540 and550.2 MESSAGE WAITING NOTIFICATIONThis section depicts the interactions between network entities in various situations related toautomatic roaming and Message Waiting Notification (MWN). These scenarios are forillustrative purposes only.12.1 MWN Alert Pip Tone Activation or De-Activa
26、tionThe information flows required for the activation or de-activation of MWN Alert Pip Tone byan authorized MS are described in Part 311 Section 2.1.1Refer to Part-513 of FEAT for an explanation of MWN subscription options.X.S0004-329-E v1.0MESSAGE WAITING NOTIFICATION123456789101112131415161718192
27、021222324252627282930313233343536373839404142434445464748495051525354555657585960329-22.2 Temporary De-Activation of MWN PIP Tone(with call setup)This scenario describes the temporary de-activation of MWN PIP Tone by an authorized MS.The de-activation occurs coincident with the call origination.a. A
28、 call origination and dialed digits are received by the Serving MSC. During analysisof the dialed digits, the Serving MSC detects a feature code string.b. The dialed digits are included in a FEATREQ and sent from the Serving MSC to theHLR associated with the MS. The Serving MSC also includes theOneT
29、imeFeatureIndicator parameter if any of its status bits are set (i.e., if any specialfeature processing is active for the call).c. The HLR detects the authorized MWN Pip Tone de-activation request and sends afeatreq to the Serving MSC. The featreq includes call routing information inthe TerminationL
30、ist parameter. It also includes the OneTimeFeatureIndicatorparameter, with an indication that MWN Pip Tone is de-activated for the call.d. The Serving MSC stores the OneTimeFeatureIndicator, de-activates MWN Pip Tone,and provides treatment to the served MS as indicated in the featreq. In this case,t
31、he treatment is to apply feature confirmation.Figure 1 Temporary De-Activation of MWN PIP Tone (with call setup)Additional Parameters Usage TypeOTFI (Current Call) Indicates special feature processing active for duration of call in progress.OAdditional Parameters Usage TypeOTFI (Current Call) Modify
32、 feature processing for duration of call in progress = De-activate MWN Pip Tone.RabcdefMS HLR Serving System FEATREQ DGTSDIAL, OTFI feature confirmation featreq OTFI, TERMLIST *FC0+#+TA+ SEND MSCcall setup call release FRRT X.S0004-329-E v1.01234567891011121314151617181920212223242526272829303132333
33、43536373839404142434445464748495051525354555657585960329-3 MESSAGE WAITING NOTIFICATIONe. The Serving MSC extends the call using the call routing information in theTerminationList parameter.f. The OneTimeFeatureIndicator remains active until the end of the call, at which time itis discarded by the S
34、erving MSC. The MWN Pip Tone activation status then returns toits pre-call condition.2.3 MWN via Alert Pip TonesThis scenario describes message waiting notification via the alert pip tone option.a. An undelivered voice mail message is waiting to be delivered to the subscriber. TheHLR reports the cha
35、nge in the MSs message waiting status by sending a QUALDIR tothe VLR where the MS is registered.b. The VLR sends a qualdir to the HLR.Figure 2 MWN via Alert Pip ToneAdditional Parameters Usage TypeMWNTYPE Indicates that MWN Alert Pip Tone notification is required.RabcdefghijkMS VLR MSC HLR Serving S
36、ystem MWN alert RNT RNT REGNOT regnot regnot REGNOT MS not available for alert QUALDIR MWNTYPE qualdir QUALDIR MWNTYPE MS access qualdir QDT QDT X.S0004-329-E v1.0MESSAGE WAITING NOTIFICATION1234567891011121314151617181920212223242526272829303132333435363738394041424344454647484950515253545556575859
37、60329-4c. The VLR reports the change in the MSs message waiting status by sending aQUALDIR to the Serving MSC. Additional parameters are as in Step-b.d. The Serving MSC sends a qualdir to the VLR.e. The MS is not available for alerting, therefore the Serving MSC waits until .f. The Serving MSC recei
38、ves an indication that the MS is available for alerting (e.g., anMS access is received).g. The Serving MSC may send a REGNOT to the VLR to notify it of the MSs presence.h. The VLR may send a REGNOT to the HLR to notify it of the MSs presence.i. The HLR returns a regnot to the VLR.j. The VLR returns
39、a regnot to the Serving MSC.k. The Serving MSC then provides a MWN Alert Pip Tone to the MS.2.4 MWN via an MS IndicationThis scenario describes message waiting notification via the MS indication option.a. The HLR is notified that there is a message waiting for a served MS.Additional Parameters Usage
40、 TypeMWNTYPE Indicates that MWN Alert Pip Tone notification is required.OAdditional Parameters Usage TypeMWNTYPE Indicates that MWN Alert Pip Tone notification is required.OFigure 3 MWN via an MS Indication and/or MS CountabcdefMS VLR MSC HLR Serving System MWN alert qualdir QUALDIR MWNTYPE, MWNCOUN
41、T message waiting qualdir QUALDIR MWNTYPE, MWNCOUNT QDT QDT X.S0004-329-E v1.0123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960329-5 MESSAGE WAITING NOTIFICATIONb. The HLR reports the change in the MSs MWN status by sending a QUALDIR to t
42、heVLR where the MS is registered.c. The VLR sends a qualdir to the HLR.d. The VLR reports the change in the MSs MWN status by sending a QUALDIR to theServing MSC. Additional parameters are as in Step-b.e. The Serving MSC sends a qualdir to the VLR.f. The Serving MSC notifies the served MS of the cha
43、nge in the MSs MWN status viathe Message Waiting Indication.Additional Parameters Usage TypeMWNTYPE Indicates that notification via Message Waiting Indication is required.RMWNCOUNT Indicates the subscriber is authorized and active for message count indication, and the type (e.g., “Voice”, “SMS”, “G3
44、 Fax”) and number of messages of each type that are waiting.OX.S0004-329-E v1.0MESSAGE WAITING NOTIFICATION123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960329-62.5 MWN After HandoffThis scenario describes message waiting notification aft
45、er intersystem handoff. Notificationmay be via the Message Waiting Indication method, or the Count Indication method.a. A call involving the served MS is in progress.b. The HLR determines that MWN is required for the served MS.c-f. Same as MWN, Section 2.4, steps b-e, respectively.g. The Anchor MSC
46、sends an INFOFWD to the Tandem MSC, including the MWNinformation.h. The Tandem MSC adjusts the InterMSCCircuitID to identify the circuit between it andthe Serving MSC, and forwards the INFOFWD to the Serving MSC.i. The Serving MSC presents the MWN indication to the served MS in an appropriatefashion
47、.j. The Serving MSC acknowledges receipt by sending an infofwd to the TandemMSC.k. The Tandem MSC forwards the infofwd to the Anchor MSC.Figure 4 MWN After HandoffabcdefghijkMS MSC VLR Serving System MSC MSC MWN indication infofwd INFOFWD MWNTYPE, MWNCOUNT HLR Anchor System Tandem System qualdir MWN
48、 required call in progress qualdir QUALDIR MWNTYPE, MWNCOUNT QUALDIR MWNTYPE, MWNCOUNT infofwd INFOFWD MWNTYPE, MWNCOUNT IFT IFT QDT QDT X.S0004-329-E v1.0123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960329-7 MESSAGE WAITING NOTIFICATION
49、2.6 MWN via Pip Tone on MS Call OriginationThis scenario describes the origination of a call by the served MS with MWN pending (pip toneoption). a. The Serving MSC receives a call origination from the served MS.b. If the service profile of the MS is unknown to the MSC, it sends a QUALREQ to theVLR.c. If the service profile of the MS is unknown to the VLR, it sends a QUALREQ to theHLR associated with the MS. d. The HLR sends a qualreq to the Serving MSCs VLR, including an indication of theMSs MWN pending status.e. The VLR sends a qualreq to the Servin
