1、 TIA-41.336-E August 2012Mobile Application Part (MAP) - Voice Feature Scenarios: Wireless Emergency Services ANSI/TIA-41.336-E-2012 APPROVED: AUGUST 9, 2012 NOTICE TIA Engineering Standards and Publications are designed to serve the public interest through eliminating misunderstandings between manu
2、facturers 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
3、 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 adopt
4、ed 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 al
5、l 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.336
6、-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 Bo
7、ulevard 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
8、 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 document,
9、 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 tha
10、t 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 p
11、roperty 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 there
12、of 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 lef
13、t 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 conte
14、nts. 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 cons
15、ists 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 e
16、ncouragement 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
17、 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 W
18、ARRANTIES, 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. T
19、IA 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 IN
20、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 DAMAGES
21、 (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 FUND
22、AMENTAL 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-336-E v1.0 January 2009 Initial publication.X.S0004-336-E v1.01234567891011121314151617181920212223242526272829303132333435363738
23、39404142434445464748495051525354555657585960336-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 listi
24、ng of 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 Eme
25、rgency ServicesThis section depicts the interactions between network entities in various situations related to anEmergency Services Call. These scenarios are for illustrative purposes only.2.1 Emergency Services Call Initiated During a Call After Intersystem HandoffThis scenario describes an Emergen
26、cy Services Call initiated during a call causing a three-waycall (with call processing modifications) following an intersystem handoff. This call will be setup from the Anchor MSC (if an intersystem handoff has occurred). This scenario depicts the 3-flash method along with the alternative 4-flash th
27、ree-way calling method. X.S0004-336-E v1.0Emergency Services123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960336-2a. A call is handed off from one MSC to another.b. Later and optionally, the user initiates a multi-way call. Without this o
28、ption, skip to Step-f.c. The Serving MSC forwards a FLASHREQ to the Anchor MSC, which determines that theMS has the Three-Way Calling feature active and is in a state able to invoke Three-WayCalling.d. The Anchor MSC places the non-controlling party on hold and may provide dialtone to theMS.Figure 1
29、 Emergency Services Call Initiated During a Call After Intersystem HandoffabcdefghijklmnopqrstuS/R MSC MS Serving System PSAP MSC call setup ES Routing Digits,Callback Number Put non-controlling party on hold ES Invocation FLASHREQ ES Digits, ESRD flashreq SHH FLASHREQ SEND flashreq Anchor System FL
30、ASHREQ FRT FRT PSAP answers call handoff FRT FRT no action FLASHREQ flashreq flashreq call setup ES Routing Digits,Callback Number PSAP answers call PSAP communicates with Emergency Services Caller SEND SEND Join 3 parties X.S0004-336-E v1.012345678910111213141516171819202122232425262728293031323334
31、3536373839404142434445464748495051525354555657585960336-3 Emergency Servicese. The Anchor MSC responds with a flashreq to the Serving MSC.f. The user initiates an Emergency Services Call.g. The Serving MSC forwards the ES invocation (e.g., flash digits 9-1-1) to the Anchor MSCin a FLASHREQ, containi
32、ng the following parameters set to specific values for thisscenario:.h. The Anchor MSC responds with a flashreq to the Serving MSC, containing thefollowing parameters set to specific values for this scenario:.i. The Anchor MSC, recognizing that an emergency call is being dialed, routes thecall to th
33、e appropriate Selective/Router (S/R), transmitting the followinginformation:j. The S/R forwards the call to the appropriate PSAP. This routing decision may take intoaccount the location of the MS, time-of-day, etc. Information passed is same as Step-i.Note: interfaces between S/R, PSAP and other eme
34、rgency services network elements areoutside the scope of this standard and are shown for illustrative purposes only.k. The PSAP answers by connecting to the Emergency Services Caller and returning answersupervision to the S/R.Parameters Usage TypeDigits (Dialed) These are the digits dialed by the su
35、bscriber accompanying the flash. These digits are used by the Anchor MSC to determine if the flash event represents an attempt to place an emergency call.RESRD EmergencyServicesRoutingDigits. A unique identifier of a specific base station, cell site or sector.If the Anchor MSC determines that an eme
36、rgency call is being placed, the Anchor MSC uses the ESRD to supply information that will cause PSTN routing to terminate at the appropriate ESNE.RParameters Usage TypeSHH SpecialHandling. Included if the Anchor MSC has determined that the call is an emergency call. The Serving MSC may use this info
37、rmation to provide Emergency Call Reconnect if radio contact with the MS is lost.OInofrmation Usage TypeES Routing Digits Emergency Services Routing Digits. A unique identifier of a specific base station, cell site or sector. The parameter carrying this information should be encoded as per the proto
38、col used to route the call.Information may also be included that will cause PSTN routing to terminate at the appro-priate ESNE. This number need not be a dialable number. For example, the office code of 911 could be used (e.g., 403-911-1234) to allow routing without the consumption of directory numb
39、ers.RCallback Number The Directory Number used to call back the caller.RX.S0004-336-E v1.0Emergency Services123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960336-4l. The S/R forwards the PSAPs answer supervision signal to the Anchor MSC. m
40、. The PSAPs agent communicates with the Emergency Services Caller.n. The user presses SEND again.o. The Serving MSC forwards a FLASHREQ to the Anchor MSC.p. The Anchor MSC bridges the trunk to the MS, the trunk to the S/R and the trunk to the heldparty to allow a three-way conversation.q. The Anchor
41、 MSC responds with a flashreq to the Serving MSC.r. The user presses SEND again.s. The Serving MSC forwards a FLASHREQ to the Anchor MSC.t. The Anchor MSC takes no action to avoid disconnecting the PSAP from the call.u. The Anchor MSC responds with a flashreq to the Serving MSC.X.S0004-336-E v1.0123
42、456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960336-5 Emergency Services2.2 Emergency Call Reconnect After Intersystem HandoffThis scenario describes a reconnect to the PSAP after loss of radio contact to the MS during anEmergency Services
43、Call.a. An MS user initiates as Emergency Services Call (e.g., dials 9-1-1).b. An emergency call is setup (using any of the previous scenarios).c. An intersystem handoff is initiated through the FACDIR2. It contains the SHH parameterto indicate that an emergency call is being handed off. Note that t
44、he SHH parameter is alsorequired in the HANDBACK2 and HANDTHIRD2 messages to support all inter-MSChandoff scenarios.d. The Serving MSC acknowledges with a facdir2.e. The Serving MSC reports the arrival of the MS on the new channel with an MSONCH.f. The MS disconnects due to an abnormal condition (e.
45、g., loss of radio synchronization).g. The Serving MSC, based on the SHH indicator received from the Anchor MSC at Step-c,determines that emergency reconnect should be provided. It may provide an in-bandwarning tone to the PSAP (e.g., low tone).h. The Serving MSC attempts to reconnect the MS (e.g., b
46、y paging).i. If the MS is reconnected, the warning tone is removed by the Serving MSC. If the MS wasunable to be reconnected, the PSAP trunk could be connected to a recorded announcementor a distinct tone (e.g., reorder).Figure 2 Emergency Call Reconnect After Intersystem Handoff abcdefghiS/R MSC MS
47、 Serving System PSAP MSC ES Invocation FACDIR2 SHH warning tone Anchor System MSONCH Emergency Services Call Established HOT remove tone facdir2 loss of radio contact reconnect X.S0004-336-E v1.0Emergency Services123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960336-6
