ANSI TIA-41.334-E-2012 Mobile Application Part (MAP) - Voice Feature Scenarios Voice Message Retrieval《移动应用部分 音频特征场景.音频信息检索》.pdf

1、 TIA-41.334-E August 2012Mobile Application Part (MAP) - Voice Feature Scenarios: Voice Message Retrieval ANSI/TIA-41.334-E-2012 APPROVED: AUGUST 9, 2012 NOTICE TIA Engineering Standards and Publications are designed to serve the public interest through eliminating misunderstandings between manufact

2、urers 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 member or

3、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 adopted b

4、y 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 all sa

5、fety 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.334-RV5

6、-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 Boulev

7、ard 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/ All rig

8、hts 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 document, ple

9、ase 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 that th

10、e 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 prope

11、rty 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 thereof i

12、s 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 left to

13、 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 contents.

14、 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 consists

15、 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 encou

16、ragement 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 of Ess

17、ential 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 WARRA

18、NTIES, 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. TIA E

19、XPRESSLY 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 IN THE

20、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 DAMAGES (IN

21、CLUDING 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 FUNDAMEN

22、TAL 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-334-E v1.0 January 2009 Initial publication.X.S0004-334-E v1.012345678910111213141516171819202122232425262728293031323334353637383940

23、4142434445464748495051525354555657585960334-1 INTRODUCTION1 INTRODUCTIONUnless otherwise noted, the scenarios in this section depict features operating individually; i.e.,feature interactions are not considered unless specifically noted.The scenarios in this part do not include a complete listing of

24、 operation parameters, either in thefigures or in the accompanying text descriptions. Parameters are included where they aredeemed necessary to improve the understanding of the scenario. For a complete description ofthe parameters associated with each operation, refer to Parts 540 and 550.2 VOICE ME

25、SSAGE RETRIEVALThis section depicts the interactions between network entities in various situations related toautomatic roaming and Voice Message Retrieval (VMR). These scenarios are for illustrativepurposes only.2.1 Normal Operation: Invocation via Feature CodeThis scenario describes the invocation

26、 of the VMR feature via the entry of a feature code stringby the served MS.a. Dialed digits are received by the Serving MSC. During analysis of 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 assoc

27、iated with the MS.Figure 1 Normal Operation: Invocation via Feature CodeabcdefghMSC MSC HLR VMS Serving System VMS Host System FEATREQ DGTSDIALMS call setup featreq TERMLIST ROUTREQ MSID, TERMTRMT, DGTSDEST, VMBOX, VMSPINroutreq TLDN call answered at VMS TLDNATRRTFRRTcall setup to VMS (DGTSDEST, MIN

28、 or VMBOX, VMSPIN) *FC (+ VMS password number) + SEND X.S0004-334-E v1.0VOICE MESSAGE RETRIEVAL123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960334-2c. Based on its internal data, the HLR identifies the system which controls the VMS onwhi

29、ch the served MS is enrolled (i.e., the VMS Host System). The HLR sends aROUTREQ to this systems MSC (i.e., the VMS-MSC), including an indication that thisrequest is for VMR purposes.d. The VMS-MSC associates the information received with a TLDN and returns this tothe HLR in a routreq.e. The HLR rel

30、ays the TLDN to the Serving MSC via the TerminationList parameter ina featreq. f. The Serving MSC provides treatment to the served MS as indicated in the featreq.In this case, the treatment is to route the call based on the TLDN information.g. The VMS-MSC sets up a call to the VMS.h. When the VMS an

31、swers, it is connected to the served MS.Additional Parameters Usage TypeTERMTRMT Reason for RoutingRequest operation = VMR. RDGTSDEST VMS identification number. RVMBOX Served MSs voice mailbox number, if not the MIN.OVMSPIN Served MSs VMS PIN. OX.S0004-334-E v1.01234567891011121314151617181920212223

32、24252627282930313233343536373839404142434445464748495051525354555657585960334-3 VOICE MESSAGE RETRIEVAL2.2 Normal Operation: Invocation via Revertive CallThis scenario describes the invocation of the VMR feature via entry by the served MS of its ownMIN (i.e., a revertive call).a. Dialed digits are r

33、eceived by the Serving MSC. The Serving MSC detects that thedialed digits correspond to the served MSs MSID.b. The dialed digits are included in a ORREQ and sent from the Serving MSC to the HLRassociated with the MS.c-d. Same as VMR, Section 2.1, Steps c-d.e. The HLR relays the TLDN to the Serving M

34、SC via the TerminationList parameter in a orreq.f-h. Same as VMR, Section 2.1, Steps f-h.Figure 2 Normal Operation: Invocation via Revertive CallabcdefghMSC MSC HLR VMS Serving System VMS Host System ORREQ DGTSDIALMS call setup orreq TERMLIST ROUTREQ MSID, TERMTRMT, DGTSDEST, VMBOX, VMSPINroutreq TLDN call answered at VMS TLDNATRRTORTcall setup to VMS (DGTSDEST, MIN or VMBOX, VMSPIN) *FC (+ VMS password number) + SEND X.S0004-334-E v1.0VOICE MESSAGE RETRIEVAL123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960334-4