ANSI TIA-41.328-E-2012 Mobile Application Part (MAP) - Voice Feature Scenarios Mobile Access Hunting《移动应用部分(MAP).音频特征场景 移动台接入寻找》.pdf

1、 TIA-41.328-E August 2012Mobile Application Part (MAP) - Voice Feature Scenarios: Mobile Access Hunting ANSI/TIA-41.328-E-2012 APPROVED: AUGUST 13, 2012 NOTICE TIA Engineering Standards and Publications are designed to serve the public interest through eliminating misunderstandings between manufactu

2、rers 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 n

3、on-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 by

4、 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 saf

5、ety 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.328-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 Bouleva

7、rd 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 righ

8、ts 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, plea

9、se 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 the

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

11、ty 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 is

12、 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 encour

16、agement 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 Esse

17、ntial 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 WARRAN

18、TIES, 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 EX

19、PRESSLY 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 D

20、OCUMENT 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 (INC

21、LUDING 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 FUNDAMENT

22、AL 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-328-E v1.0 April 2008 Initial publication.X.S0004-328-E v1.012345678910111213141516171819202122232425262728293031323334353637383940414

23、2434445464748495051525354555657585960328-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 op

24、eration 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 Mobile Acce

25、ss HuntingThis section depicts the interactions between network entities in various situations related toautomatic roaming and Mobile Access Hunting (MAH). These scenarios are for illustrativepurposes only.2.1 MAH Membership Activation or De-ActivationThe information flows required for the activatio

26、n or de-activation of membership in themembers default or specified MAH group by an authorized MS are described in Part 311Section 2.1.2.2 MAH Ordering Change RequestThe information flows required for a request to change the members order in its default orspecified MAH group, by an authorized MS, ar

27、e described in Part 311 Section 2.1.2.3 MAH InvocationThis scenario describes the invocation of MAH. The MAH group is comprised of threemembers: one member is a PSTN DN, MAH-DN1; the other two members are MSs, served bythe same HLR and currently served by the same MSC. These two MSs will be referred

28、 to asMIN1 and MIN2 throughout this part.X.S0004-328-E v1.0Mobile Access Hunting123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960328-2a. A call origination and the dialed MS address digits (i.e., directory number) are receivedby the Origi

29、nating MSC.b. The Originating MSC sends a LOCREQ to the MSs HLR and includes the BillingIDand Digits (Dialed) parameters.Figure 1 MAH InvocationabcdefghijklmnopqrstuvwxyMSC VLR HLR MSC Serving System LRT Call is not completedstart call progress treatment routreq TLDN1 call origination Originating Sy

30、stem LOCREQ BILLID, DGTSDIAL locreq GRPINFO, NATIME, REDIND, TERMLIST, TERMTRIG call setup to MAH-DN1 release call to MAH-DN1 TRANUMREQ BILLID, GRPINFO, PILOT, REDREASON, TRANSCAP ROUTREQ MIN1, LegInfo1 ROUTREQ MIN1, LegInfo1 routreq TLDN1 tranumreq GRPINFO, NATIME, REDIND, TERMLIST, TERMTRIG Call i

31、s not completedROUTREQ MIN2, LegInfo2 ROUTREQ MIN2, LegInfo2 routreq TLDN2 routreq TLDN2 tranumreq GRPINFO, NATIME, REDIND, TERMLIST, TERMTRIG timeout MAHT RRT RRT TTNRT MAHT TLDNAT MAHT call setup to TLDN2 call answered byTLDN2 TTNRT RRT RRT TRANUMREQ BILLID, GRPINFO, PILOT, REDREASON, TRANSCAP rel

32、ease call to TLDN1 call setup to TLDN1 X.S0004-328-E v1.0123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960328-3 Mobile Access Huntingc. The HLR recognizes the called number as an MAH Pilot DN. The HLR sends alocreq to the Originating MSC,

33、 containing the first MAH group members routinginformation in the form of the TerminationList parameter, along with an indication ofthe reason for extending the incoming call (i.e., for MAH) in theDMH_RedirectionIndicator parameter. d. On receipt of the locreq, the Originating MSC may start call pro

34、gress treatment tothe calling party, if it has not already done so.e. The Originating MSC provides call treatment as indicated in the locreq. In this case,the treatment is to attempt to establish a call to the first DN in the MAH group,MAHDN1. For each call attempt, the Originating MSC monitors call

35、 progress; basedon this information, it applies appropriate call progress treatment to the calling party.f. The call to MAH-DN1 is not completed due to busy, no answer time-out or othercauses.g. The Originating MSC releases the call to MAH-DN1.h. Based on the instructions in the TerminationTriggers

36、parameter received in Step-c, theOriginating MSC sends a TRANUMREQ to the HLR, containing the BillingIDassociated with the original MAH call (step b) and the RedirectionReason parameter.Additional Parameters Usage TypeGRPINFO Information associated with the MAH Pilot DN. ONATIME Indication of how lo

37、ng, in seconds, the Origi-nating MSC should wait before applying noanswer treatment. Include to override Origi-nating MSC default.OTERMTRIG Indicates active termination trigger points formembers not having TerminationTriggersinside the TerminationList.OAdditional Parameters Usage TypeBILLID May be u

38、sed by HLR to relate the transfer request to the original MAH call invocation.RPILOT May be used by the HLR to relate the transfer request to the original MAH invocation.RGRPINFO May be used by HLR for further processing of the MAH call. Include if available.OTRANSCAP Indicates the Originating MSCs

39、transaction capability at the current time. (Allow routing information.)OX.S0004-328-E v1.0Mobile Access Hunting123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960328-4i. The HLR may use the BillingID or the PilotNumber and LegInformation t

40、o relate thetransfer request to the original MAH call. It sends a ROUTREQ to the VLR where theMS corresponding to the next entry in the MAH group list is registered, that of MIN1.j. The VLR forwards the ROUTREQ to the current Serving MSC.k. In reaction to the ROUTREQ, the Serving MSC checks its inte

41、rnal data structures anddetermines that the MS is currently idle. The Serving MSC allocates TLDN1 andreturns this information to the VLR in a routreq.l. The VLR sends the routreq to the HLR.m. The HLR sends a tranumreq to the Originating MSC, including TLDN1 in theTerminationList parameter, along wi

42、th an indication of the reason for extending theincoming call (i.e., for MAH) in the DMH_RedirectionIndicator parameter.n. The Originating MSC provides call treatment as indicated in the tranumreq. In thiscase, the treatment is to attempt to establish a call to TLDN1.o. The call to TLDN1 is not comp

43、leted due to busy, no answer time-out or other causes.p. The Originating MSC releases the call to TLDN1.q. Based on the instructions in the TerminationTriggers parameter received in Step-c, theOriginating MSC sends a TRANUMREQ to the HLR, containing the BillingIDassociated with the original MAH call

44、 (step b) and the RedirectionReason parameter.Additional Parameters Usage TypeLegInfo1: MAH parameters for call leg to MIN1:AlertCode Include for distinctive alerting of MS. OLegInformation Used for HLR identification of call leg to MIN1. Include at HLR option.OOneTimeFeature-Indicator Modify featur

45、e processing for the duration of this call leg.OTerminationTriggers Include if termination trigger points are active for call leg.OAdditional Parameters Usage TypeGRPINFO See description in Step-c. ONATIME See description in Step-c. OTERMTRIG See description in Step-c. RAdditional Parameters Usage T

46、ypeBILLID See description in Step-h. RPILOT See description in Step-h. RGRPINFO See description in Step-h. OTRANSCAP See description in Step-h. OX.S0004-328-E v1.0123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960328-5 Mobile Access Huntin

47、gr. The HLR may use the BillingID or PilotNumber and GroupInformation to relate thetransfer request to the original MAH call. It sends a ROUTREQ to the VLR where theMS corresponding to the next entry in the MAH group list is registered, that of MIN2.s. s. The VLR forwards the ROUTREQ to the current

48、Serving MSC.t. In reaction to the ROUTREQ, the Serving MSC checks its internal data structures anddetermines that the MS is currently idle. The Serving MSC allocates TLDN2 andreturns this information to the VLR in a routreq.u. The VLR sends the routreq to the HLR.v. The HLR sends a tranumreq to the

49、Originating MSC, including TLDN2 in theTerminationList parameter, along with an indication of the reason for extending theincoming call (i.e., for MAH) in the DMH_RedirectionIndicator parameter.w. The Originating MSC provides call treatment as indicated in the tranumreq. case,the treatment is to attempt to establish a call to TLDN2.x. The party at TLDN2 answers. The Originating MSC connects the calling party atTLDN2.y. On MAHT timer time-out, the HLR concludes MAH processing.Additional Parameters Usage TypeLegInfo2: MAH parameters for call leg