ANSI TIA-41.333-E-2012 Mobile Application Part (MAP) - Voice Feature Scenarios Subscriber PIN Access Subscriber PIN Intercept《移动应用部分 语音特征场景 订购用户PIN接入 订购用户PIN拦截》.pdf

1、 TIA-41.333-E August 2012Mobile Application Part (MAP) - Voice Feature Scenarios: Subscriber PIN Access/Subscriber PIN Intercept ANSI/TIA-41.333-E-2012 APPROVED: AUGUST 10, 2012 NOTICE TIA Engineering Standards and Publications are designed to serve the public interest through eliminating misunderst

2、andings 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

3、 preclude 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 Pu

4、blications 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 p

5、urport 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 Proje

6、ct No. SP-3-3590.333-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 Depar

7、tment 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/st

8、andards/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 portio

9、ns 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

10、 is 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 u

11、se 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 f

12、rom 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, w

13、hich 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 D

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

15、 such 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; (

16、ii) 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

17、to 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

18、 the 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 INTELLECTUA

19、L 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 SER

20、VICE 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 C

21、ONSEQUENTIAL 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

22、OF 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-333-E v1.0 January 2009 Initial publication.X.S0004-333-E v1.012345678910111213141516171819202122232425262728

23、2930313233343536373839404142434445464748495051525354555657585960333-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 i

24、n this 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 ea

25、ch operation, refer to Parts 540 and550.2 Subscriber PIN AccessThis section depicts the interactions between network entities in various situations related toautomatic roaming and Subscriber PIN Access (SPINA). These scenarios are for illustrativepurposes only.2.1 SPINA Variable RegistrationThis sce

26、nario describes a SPINA PIN registration change by an authorized MS.X.S0004-333-E v1.0Subscriber PIN Access123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960333-2a. Dialed digits are received by the Serving MSC. During analysis of the dial

27、ed digits, theServing 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 TransactionCapability parameter is also included inthe FEATREQ, indicating that the Serving MSC supports receiving RUIDIRs.Figure

28、 1 SPINA Variable RegistrationabcdefghijklmnopqrMSC HLR Serving System RUIDIR ANNLIST, DGTCC connect call FEATREQ DGTSDIAL, TRANSCAP ruidir DGTSDIAL prompt for new PIN *FC+SEND QUERY w/ PERMISSION Old PIN prompt for old PIN RUIDIR ANNLIST, DGTCC New PIN ruidir DGTSDIAL RUIDIR ANNLIST, DGTCC prompt t

29、o re-enter new PIN New PIN ruidir DGTSDIAL featreq FEATRESULT FRRTfeature confirmation call release CONV w/o PERMISSION CONV w/ PERMISSION CONV w/o PERMISSION CONV w/ PERMISSION RESPONSE SINGLETCAP TRANSACTION CONV w/o PERMISSION CONV w/ PERMISSION RUDTRUDTFRRTFRRTRUDTFRRTMS X.S0004-333-E v1.0123456

30、789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960333-3 Subscriber PIN Accessc. The HLR recognizes the SPINA registration request and sends a RUIDIR to theServing MSC.d. On receipt of the RUIDIR, the Serving MSC turns off the FEATREQ timer andpr

31、ovides call treatment as indicated in the received message. In this case, the treatmentis to answer the call (i.e., connect the calling party to subsystem capable of userinteraction).e. The Serving MSC prompts the user based on the information in the received RUIDIR(in the DigitCollectionControl par

32、ameter) and waits for digits.f. The user responds with his or her old PIN.g. The Serving MSC sends a ruidir to the HLR, containing the digits dialed by theuser, and restarts the FRRT timer.h. The HLR sends a RUIDIR to the Serving MSC, directing the Serving MSC (a) toprompt the calling user for its n

33、ew PIN, and (b) to collect digits from user.i. The Serving MSC prompts the user based on the information in the received RUIDIR.j. The user responds with his or her new PIN digits.k. The Serving MSC sends a ruidir to the HLR, containing the digits dialed by theuser, and restarts the FRRT timer.l. Th

34、e HLR sends a RUIDIR to the Serving MSC, directing the Serving MSC (a) toprompt the calling user to re-enter its new PIN, and (b) to collect digits from the user.m. The Serving MSC prompts the user based on the information in the received RUIDIR.n. The user responds by re-entering its new PIN.o. The

35、 Serving MSC sends a ruidir to the HLR, containing the digits dialed by theuser, and restarts the FRRT timer.p. The HLR updates the served MSs SPINA registration information and sends afeatreq including the FeatureResult parameter indicating successful featureoperation to the Serving MSC.q. The Serv

36、ing MSC provides treatment to the served MS as indicated in the featreq.In this case, the treatment is to provide feature confirmation.r. The Serving MSC releases the call.X.S0004-333-E v1.0Subscriber PIN Access12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849

37、5051525354555657585960333-42.2 SPINA Demand Activation or De-ActivationThis scenario describes the demand activation or de-activation of SPINA by an authorized MS.a. Dialed digits are received by the Serving MSC. During analysis of the dialed digits, theServing MSC detects a feature code string.b. T

38、he dialed digits are included in a FEATREQ and sent from the Serving MSC to theHLR associated with the MS. The TransactionCapability parameter is also included inthe FEATREQ, indicating that the Serving MSC supports receiving RUIDIRs. TheHLR recognizes the SPINA activation or de-activation request.

39、If the subscribers PINis included in the feature code string received then go to Step h.c. Otherwise, the HLR sends a RUIDIR to the Serving MSC. The message directs theServing MSC (a) to answer the call, (b) to prompt the calling user for its PIN, and (c)to collect digits from the user.Figure 2 SPIN

40、A Demand Activation or De-Activation or*FC0abcdefghijklmnMS VLR MSC HLR ruidir DGTSDIAL Serving System featreq FEATRESULT FEATREQ DGTSDIAL, TRANSCAP connect call FRRT QDT RUDT feature confirmation (*FC or *FC0) + (optional PIN) + SENDRUIDIR ANNLIST, DGTCC prompt for PIN digits QDT call release QUALD

41、IR QUALDIR qualdir qualdir FRRT X.S0004-333-E v1.0123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960333-5 Subscriber PIN Accessd. On receipt of the RUIDIR, the Serving MSC turns off the FEATREQ timer andprovides call treatment as indicated

42、 in the received message. In this case, the treatmentis to answer the call (i.e., connect the calling party to subsystem capable of userinteraction).e. The Serving MSC prompts the user based on the information in the received RUIDIR(in the DigitCollectionControl parameter) and waits for digits.f. Th

43、e user responds with his or her PIN.g. The Serving MSC sends a ruidir to the HLR, containing the digits dialed by theuser, and restarts the FRRT timer.h. After validating the PIN, the HLR updates the served MSs SPINA activation statusand sends a featreq including the FeatureResult parameter indicati

44、ng successfulfeature operation to the Serving MSC.i. The Serving MSC provides treatment to the served MS as indicated in the featreq.In this case, the treatment is to provide feature confirmation.j. The Serving MSC releases the call.k. The HLR reports the change in the MSs service profile by sending

45、 a QUALDIR,including the OriginationIndicator parameter indicating origination denied or allowed,to the VLR where the MS is registered.l. The VLR returns an empty qualdir to the HLR.m. The VLR reports the change in the MSs service profile by relaying theOriginationIndicator parameter in a QUALDIR se

46、nt to the Serving MSC.n. The Serving MSC returns an empty qualdir to the VLR.X.S0004-333-E v1.0Subscriber PIN Access123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960333-62.3 Call Origination with SPINA ActiveThis scenario describes the no

47、rmal operation of the SPINA feature when it is active and theserved MS attempts a call origination. If SPINA is active, the previously receivedOriginationIndicator for the subscriber shall have indicated that originations were denied.a. Dialed digits are received by the Serving MSC. The Serving MSC

48、determines that thisrepresents an call origination and that SPINA is active (i.e., the OriginationIndicator isset to deny the call).b. Therefore, the Serving MSC notifies the served MS that origination is denied.c. The Serving MSC releases the call.Figure 3 Call Origination with SPINA Active abcMS M

49、SC Serving Systemorigination denied call origination call release X.S0004-333-E v1.0123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960333-7 Subscriber PIN Access2.4 Feature Request with SPINA ActiveThis scenario describes the normal operation of the SPINA feature when it is active and theserved MS issues a feature request.a. Dialed digits are received by the Serving MSC. During analysis of the dialed digits, theServing MSC detects a feature code string.b. The dialed digits are included in a F