ANSI TIA-41.327-E-2012 Mobile Application Part (MAP) - Voice Feature Scenarios Flexible Alerting《移动应用部分 声音特征场景 灵活报警》.pdf

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

2、 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 non-m

3、ember 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 TIA

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

5、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.327-RV5-A, f

6、ormulated 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 Boulevard A

7、rlington, 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 rights r

8、eserved 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, please c

9、ontact 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 Doc

10、ument 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 property r

11、ights (“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 req

12、uested, 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 the

13、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. If t

14、he 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 of m

15、andatory, 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 encouragem

16、ent 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 Essentia

17、l 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 WARRANTIES

18、, 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 EXPRES

19、SLY 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 DOCUM

20、ENT 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 (INCLUDI

21、NG 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 FUNDAMENTAL E

22、LEMENT OF THE USE OF THE CONTENTS HEREOF, AND THESE CONTENTS WOULD NOT BE PUBLISHED BY TIA WITHOUT SUCH LIMITATIONS. REVISION HISTORYRevision Date RemarksX.S0004-327-E v1.0 April 2008 Initial publication.X.S0004-327-E v1.0123456789101112131415161718192021222324252627282930313233343536373839404142434

23、445464748495051525354555657585960327-1 INTRODUCTION1 INTRODUCTIONUnless otherwise noted, the scenarios in this part 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 operation

24、 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 FLEXIBLE ALERTINGT

25、his section depicts the interactions between network entities in various situations related toautomatic roaming and Flexible Alerting (FA). These scenarios are for illustrative purposesonly.2.1 FA Membership Activation or De-ActivationThe information flows required for the activation or de-activatio

26、n of membership in the mem-bers default or specified FA group by an authorized MS are described in Part 311 Section 2.1.X.S0004-327-E v1.0FLEXIBLE ALERTING123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960327-22.2 FA InvocationThis scenari

27、o describes an invocation of FA. The FA group is comprised of three members: onemember is a PSTN DN, FA-DN1; the other two members are MSs, served by the same HLR andcurrently served by the same MSC. These two MSs will be referred to as MIN1 and MIN2throughout this part. Figure 1 FA Invocationabcdef

28、ghijklmnopqrMSC VLR HLR MSC call origination Serving System Originating System routreq TLDN1 LOCREQ DGTSDIAL, TRANSCAPcall setup start call progress treatment release call leg to TLDN2 call leg setup to TLDN1 call leg answered by TLDN1 ROUTREQ MIN1, LegInfo1 routreq TLDN1 ROUTREQ MIN2, LegInfo2 rout

29、req TLDN2 call leg setup to TLDN2 release call leg to FA-DN1call leg setup to FA-DN1ROUTREQ MIN1, LegInfo1 locreq GRPINFO, NATIME, TERMLIST, REDIND, TERMTRIG ROUTREQ MIN2, LegInfo2 LRT RRT RRT RRT RRT TLDNAT TLDNAT routreq TLDN2 X.S0004-327-E v1.012345678910111213141516171819202122232425262728293031

30、3233343536373839404142434445464748495051525354555657585960327-3 FLEXIBLE ALERTINGa. A call origination and the dialed MS address digits (i.e., directory number) are receivedby the Originating MSC.b. The Originating MSC sends a LOCREQ to the HLR associated with the MS; thisassociation is made through

31、 the dialed MS address digits (which may not be the MIN).The Originating MSC may optionally include the TransactionCapability parameter tospecify the appropriate termination handling.c-f. The HLR recognizes the called number as an FA Pilot DN and that, based on the received TransactionCapability par

32、ameter, the Originating MSC is capable of supporting an FA call. In this case, the two MSs in the FA group are registered in the same system; therefore, two ROUTREQs are sent to the Serving VLR and the VLR forwards the ROUTREQs to the Serving MSC.g-j. In reaction to each ROUTREQ, the Serving MSC che

33、cks its internal data structures and determines that the MS is currently idle, then allocates a TLDN and returns this infor-mation to the VLR in a routreq. The VLR sends each routreq to the HLR.k. When all routreqs are received by the HLR, it returns a locreq to the OriginatingMSC. The locreq includ

34、es multiple-termination routing information in the form ofthe TerminationList parameter, along with an indication of the reason for extending theincoming call (i.e., for FA) in the DMH_RedirectionIndicator parameter.Additional Parameters Usage TypeLegInfo1: FA parameters for call leg to MIN1:AlertCo

35、de Include for distinctive alerting of MIN1. OLegInformation Used for HLR identification of call leg to MIN1. Include at HLR option.OOneTimeFeature-IndicatorModify feature processing for the duration of this call leg.OTerminationTriggers Include if termination trigger points are active for call leg

36、to MIN1.OLegInfo2: FA parameters for call leg to MIN2:AlertCode Include for distinctive alerting of MIN2. OLegInformation Used for HLR identification of call leg to MIN2. Include at HLR option.OOneTimeFeature-IndicatorModify feature processing for the duration of this call leg.OTerminationTriggers I

37、nclude if termination trigger points are active for call leg to MIN2.OAdditional Parameters Usage TypeTERMLIST List of FA group members identification infor-mation, from first member to last.RGRPINFO Information associated with the FA Pilot DN. ONATIME Indication of how long, in seconds, the Origi-n

38、ating MSC should wait before applying no answer treatment. Include to override Origi-nating MSC default.OTERMTRIG Indicates active termination trigger points for members not having TerminationTriggers inside the TerminationList.OX.S0004-327-E v1.0FLEXIBLE ALERTING123456789101112131415161718192021222

39、324252627282930313233343536373839404142434445464748495051525354555657585960327-4l. On receipt of the locreq, the Originating MSC may start call progress treatment tothe calling party, if it has not already done so.m. The Originating MSC provides call treatment as indicated in the locreq. In this cas

40、e,the treatment is to attempt to establish, in parallel, calls to the FA-DN1.n. .to the TLDN1, and .o. .to the TLDN2. In general, these calls may require outgoing trunks or be internal tothe Originating MSC. For each call attempt, the Originating MSC monitors callprogress; based on this information,

41、 it applies appropriate call progress treatment to thecalling party.p. The party at TLDN1 answers. The Originating MSC connects the calling party to theparty at TLDN1.q. The Originating MSC releases the call to TLDN2, and.r. The Originating MSC releases the call to FA-DN1.X.S0004-327-E v1.0123456789

42、101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960327-5 FLEXIBLE ALERTING2.3 FA Invocation with a Busy FA Group Member (Single-User Type)This scenario describes an invocation of FA where a member busy condition is encountered.The FA group is compri

43、sed as described in Section 2.2. The FA group is the single-user type(i.e., the FA group is considered busy when a member of the FA group is busy).a-f. Same as FA, Section 2.2, Steps a-f.g-h. In reaction to the ROUTREQ received in Step-d, the Serving MSC checks its internal data structures and deter

44、mines that the MS is currently idle, then allocates a TLDN and returns this information to the VLR in a routreq. The VLR sends the routreq to the HLR.i-j. In reaction to the ROUTREQ received in Step-f, the Serving MSC checks its internal data structures and determines that the MS is currently busy i

45、n another call. The status of the MS is returned to the VLR by the Serving MSC in the routreq. The VLR sends the routreq to the HLR.Figure 2 FA Invocation with a Busy FA Group Member (Single-User Type)abcdefghijklmMSC VLR HLR MSC call origination Serving System locreq ACCDEN=Busy Originating System

46、routreq TLDN1 LOCREQ DGTSDIAL, TRANSCAPbusy indication ROUTREQ MIN1, LegInfo1 routreq ACCDEN=Busy LRT TLDNAT RRT RRT RRT RRT ROUTREQ MIN1, LegInfo1 ROUTREQ MIN2, LegInfo2 routreq ACCDEN=Busy ROUTREQ MIN2, LegInfo2 routreq TLDN1 Timeout X.S0004-327-E v1.0FLEXIBLE ALERTING12345678910111213141516171819

47、2021222324252627282930313233343536373839404142434445464748495051525354555657585960327-6k. The HLR determines from the service profile that the FA group is a single-user type;therefore, the group is considered busy (i.e., since MIN2 is busy). The HLR returnsthe busy status to the Originating MSC in t

48、he locreq.l. The Originating MSC then returns a busy indication to the calling party.m. The Serving MSC detects that the TLDN Association Timer (TLDNAT) set for a MSexpires; therefore, it frees the TLDN for other use and removes the record associatedwith that TLDN.X.S0004-327-E v1.012345678910111213

49、1415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960327-7 FLEXIBLE ALERTING2.4 FA Invocation with a Busy FA Group Member(Multiple-User Type)This scenario describes an invocation of FA where a member busy condition is encountered.The FA group is comprised as described in Section 2.2. The FA group is the multiple-user type(i.e., the FA group is considered busy when all members of the FA group are busy). a-f. Same as FA, Section 2.2, Steps a-f.g-j. Same as FA, Section 2.3, Steps g-j.k. T