1、 TIA-41.331-E August 2012Mobile Application Part (MAP) - Voice Feature Scenarios: Priority Access and Channel Assignment (PACA) ANSI/TIA-41.331-E-2012 APPROVED: AUGUST 8, 2012 NOTICE TIA Engineering Standards and Publications are designed to serve the public interest through eliminating misunderstan
2、dings between manufacturers 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 p
3、reclude any member 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 Publ
4、ications are adopted 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 pur
5、port to address 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
6、 No. SP-3-3590.331-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 Departm
7、ent 2500 Wilson 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/stan
8、dards/catalog/ All 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
9、 of this document, 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 i
10、s no assurance that 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
11、 of intellectual 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 fro
12、m the holder thereof 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, whi
13、ch are instead left 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 Doc
14、ument or its contents. 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 s
15、uch reference consists 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
16、) TIAs policy of 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
17、 TIA of a claim 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 t
18、he Document. ALL 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
19、PROPERTY RIGHTS. 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 SERVI
20、CE REFERRED TO IN 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 CON
21、SEQUENTIAL DAMAGES (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
22、 DAMAGES IS A FUNDAMENTAL 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-331-E v1.0 April 2008 Initial publication.X.S0004-331-E v1.0123456789101112131415161718192021222324252627282930
23、313233343536373839404142434445464748495051525354555657585960331-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 thi
24、s section do not 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 op
25、eration, refer to Parts 540 and550.2 PRIORITY ACCESS AND CHANNELASSIGNMENTThis section depicts the interactions between network entities in various situations related toautomatic roaming and Password Call Acceptance (PCA). These scenarios are for illustrativepurposes only. 2.1 Successful PACA Activa
26、tionThis scenario describes the successful activation of PACA by an authorized MS. Figure 1 Successful PACA Activation abcdefghMSC HLR Serving System FEATREQ DGTSDIAL, OTFI FRRT MS *FC+#+TA+ SEND PACA alert extend the call Channel is available PACA alert response PACA indication featreq OTFI, PACAIN
27、D, TERMLIST X.S0004-331-E v1.0PRIORITY ACCESS AND CHANNEL ASSIGNMENT123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960331-2a. A call origination and dialed digits are received by the Serving MSC. During analysisof the dialed digits, the Se
28、rving 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 theOneTimeFeatureIndicator parameter if any of its status bits are set (i.e., if any specialfeature processing is activ
29、e for the call).c. The HLR detects the authorized PACA request and sends a featreq to the ServingMSC. The featreq includes the PACA OneTimeFeatureIndicator and call routinginformation and the PACA indicator in the TerminationList parameter. The ServingMSC initiates PACA feature processing for the se
30、rved MS using the informationprovided in the response.d. The Serving MSC queues the request and sends a successful PACA indication to theserved MS.e. When a voice or traffic channel becomes available, the oldest and highest priority callrequest is identified. In this scenario, this corresponds to th
31、e served MS.f. The Serving MSC alerts the served MS using the automatic recall distinctive alertingcadence.g. The served MS answers the PACA alert.h. The Serving MSC allows the originating call to proceed and discards the PACAOneTimeFeatureIndicator.Additional Parameters Usage TypeOTFI (Current Call
32、) Indicates special feature processing active for duration of call in progress.OAdditional Parameters Usage TypeOTFI (Current Call) Modify feature processing for duration of call in progress = Activate PACA.RPACA Indicator (Current Call)Activate PACA at the indicated priority level.RX.S0004-331-E v1
33、.0123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960331-3 PRIORITY ACCESS AND CHANNELASSIGNMENT2.2 Aborted PACA ActivationThis scenario describes an aborted activation of PACA by an authorized MS. a-d. Same as PACA, Section 2.1, Steps a-d.
34、e. The served MS chooses to abort the PACA call by pressing the key. At thispoint, the priority call request is removed from the Serving MSCs queue.Figure 2 Aborted PACA Activation abcdeMSC HLR Serving System FEATREQ DGTSDIAL, OTFI FRRT MS *FC+#+TA+ SEND END PACA indication featreq OTFI, DGTSDEST EN
35、DX.S0004-331-E v1.0PRIORITY ACCESS AND CHANNEL ASSIGNMENT123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960331-42.3 Unsuccessful PACA ActivationThis scenario describes an unsuccessful attempt to activate PACA by an MS. a-b. Same as PACA, S
36、ection 2.1, Steps a-b.c. The HLR sends a featreq to the Serving MSC, indicating an unsuccessful featurerequest. The featreq also includes the AnnouncementList parameter, indicatingthat a mobile reorder tone should be applied to the MS.d. Since the featreq indicates that an unsuccessful feature reque
37、st has been made, theServing MSC provides treatment to the served MS as indicated in the ACTCODEparameter. In this case, the treatment is to apply mobile reorder. Figure 3 Unsuccessful PACA Activation with CallabcdMSC HLR Serving System FEATREQ DGTSDIAL, OTFI FRRT MS *FC+#+TA+ SEND mobile reorder featreq FEATRESULT=Failure, ANNLIST
