ANSI TIA-41.372-E-2012 Mobile Application Part (MAP) - Border MSC SMS Scenarios《移动应用部分(MAP).边界MSC SMS场景》.pdf

1、 TIA-41.372-E August 2012Mobile Application Part (MAP) - Border MSC SMS Scenarios ANSI/TIA-41.372-E-2012 APPROVED: AUGUST 8, 2012 NOTICE TIA Engineering Standards and Publications are designed to serve the public interest through eliminating misunderstandings between manufacturers and purchasers, fa

2、cilitating 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-member of TIA from m

3、anufacturing 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 in accordance with

4、 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 problems associated

5、 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.372-RV5-A, formulated under the

6、 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 Arlington, VA 22201

7、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 reserved Printed in

8、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 contact the TIA Stan

9、dards 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 Document will be appro

10、ved 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 rights (“IPR”), incl

11、uding 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 requested, all in acco

12、rdance 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 parties involved, n

13、or 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 the Document contain

14、s 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 mandatory, alternate

15、 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 encouragement of voluntary di

16、sclosure (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 Essential Patent(s) or publ

17、ished 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, EXPRESS OR IMPLIE

18、D, 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 EXPRESSLY DISCLAIMS ANY A

19、ND 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 DOCUMENT OR PRODUCED OR

20、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 (INCLUDING DAMAGES FOR LOSS

21、 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 ELEMENT OF THE USE O

22、F THE CONTENTS HEREOF, AND THESE CONTENTS WOULD NOT BE PUBLISHED BY TIA WITHOUT SUCH LIMITATIONS. REVISION HISTORYRevision Date RemarksX.S0004-372-E v1.0 January 2009 Initial publication.X.S0004-372-E v1.012345678910111213141516171819202122232425262728293031323334353637383940414243444546474849505152

23、5354555657585960372-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 operation parameters, e

24、ither 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 SMS delivery to Border MSC This

25、 section depicts the interactions between network entities in various situations related to thedelivery of SMS messages to an MS that responds to a page in a Border MSC. These scenariosare for illustrative purposes only.2.1 Border MSC SMS Termination - Successful Delivery of Single Message to MS-Bas

26、ed SMEThis scenario illustrates successful delivery of an SMS message to an MS-based SME that islocated in a Border MSC at the time of the delivery attempt. The Message Center indicates thatthere are no SMS messages pending.X.S0004-372-E v1.0SMS delivery to Border MSC12345678910111213141516171819202

27、1222324252627282930313233343536373839404142434445464748495051525354555657585960372-2a. The MC initiates an “SMS termination to MS-based SME” by sending an SMDPP to thenetwork address of record for the destination MS. The MC sets the SMSMSGCNTparameter to zero to indicate that there is a single messa

28、ge to deliver.b. Upon receipt of the SMDPP, the Serving MSC pages the destination MS both locally and,since the MS last registered while on or near the system border, in a single Border MSC bymeans of an ISPAGE2. The Serving MSC sets the CDMASO parameter in to indicate theSMS service.c. The Border M

29、SC pages the indicated MS with the SMS CDMA service option.d. The MS responds to the page.e. The Border MSC assigns the MS to a traffic channel.Figure 1 Border MSC SMS Termination - Successful Delivery of Single Message to MS-Based SMEispage2 AuthParameterssmdpppage (SMS)ISMDWTISPRTHome BorderMSC MS

30、CabcdefghiMSServingMC HLRSMDPP SMSMSGCNT=0ISPAGE2 CDMASO=SMSpage responsetraffic channel assignmentMS authenticationISSMTdata burstackissmdppSMTjklmnRNTREGNOT MSIDregnototraffic channel releaseISSMDPP SMSMSGCNT=0X.S0004-372-E v1.01234567891011121314151617181920212223242526272829303132333435363738394

31、04142434445464748495051525354555657585960372-3 SMS delivery to Border MSCNote: From the network perspective, the receipt of the page response and the assignment of the MS to a traffic channel is regarded as an implicit registration event.f. The Border MSC returns an ispage2 to the Serving MSC. If au

32、thentication is to beperformed, the ispage2 contains the appropriate authentication parameters received fromthe MS. The Border MSC sets the ISMDWT timer in anticipation of the receipt of anISSMDPP g. If authentication is indicated, the Serving MSC initiates MS authentication procedures.h. The Servin

33、g MSC sends an ISSMDPP to the Border MSC to with the SMS message. TheSMSMSGCNT parameter is set to zero indicating that no further message deliveries belongto this delivery context.Note: The absence of the SMSMSGCNT parameter in the ISSMDPP also indicates that no additional messages remain to be del

34、ivered.i. The Border MSC delivers the SMS message to the destination MS.j. The MS acknowledges receipt of the SMS message.k. The Border MSC releases the MS from the traffic channel.l. The Border MSC returns an issmdpp to the Serving MSC.m. The Serving MSC returns an smdpp to the MC.n. The Border MSC

35、 sends a REGNOT toward the MSs HLR to register the MS.Note: the Border MSC may initiate registration notifications procedures at any time after Step-h.o. The HLR returns a regnot to the Serving VLR/MSC.X.S0004-372-E v1.0SMS delivery to Border MSC123456789101112131415161718192021222324252627282930313

36、233343536373839404142434445464748495051525354555657585960372-42.2 Border MSC SMS Termination - Successful Delivery of Multiple MessagesThis scenario illustrates successful delivery of an SMS message, with a message pending, to anMS-based SME that is located in a Border MSC at the time of the deliver

37、y attempt.X.S0004-372-E v1.0123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960372-5 SMS delivery to Border MSCFigure 2 Border MSC SMS Termination - Successful Delivery of Multiple Messagesispage2 AuthParameterssmdpppage (SMS)ISMDWTISPRTHom

38、e BorderMSC MSCabcdefghiMSServingMC HLRSMDPP SMSMSGCNT0ISPAGE2 CDMASO=SMSpage responsetraffic channel assignmentISSMDPP SMSMSGCNT0MS authenticationISSMTdata burstackissmdppSMTjklmnRNTREGNOT MSIDregnotopqrstuSMDPP SMSMSGCNT=0SMTISSMDPP SMSMSGCNT=0data burstackissmdppISSMTsmdpptraffic channel releaseI

39、nactivity TimerX.S0004-372-E v1.0SMS delivery to Border MSC123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960372-6a. The MC initiates an “SMS termination to MS-based SME” by sending an SMDPP to thenetwork address of record for the destinat

40、ion MS. The MC sets the SMSMSGCNTparameter to a value greater than zero to indicate that there are multiple messages to deliver.b. Upon receipt of the SMDPP, the Serving MSC pages the destination MS both locally and,since the MS last registered while on or near the system border, in a single Border

41、MSC bymeans of an ISPAGE2. The Serving MSC sets the CDMASO parameter in to indicate theSMS service.c. The Border MSC pages the indicated MS with the SMS CDMA service option.d. The MS responds to the page.e. The Border MSC assigns the MS to a traffic channel.Note: From the network perspective, the re

42、ceipt of the page response and the assignment of the MS to a traffic channel is regarded as an implicit registration event.f. The Border MSC returns an ispage2 to the Serving MSC. If authentication is to beperformed, the ispage2 contains the appropriate authentication parameters received fromthe MS.

43、 The Border MSC sets the ISMDWT timer in anticipation of the receipt of anISSMDPP g. If authentication is indicated, the Serving MSC initiates MS authentication procedures.h. The Serving MSC sends an ISSMDPP to the Border MSC to with the SMS message. TheSMSMSGCNT parameter is set to the value receiv

44、ed from the MC.i. The Border MSC delivers the SMS message to the destination MS.j. The MS acknowledges receipt of the SMS message.k. The Border MSC returns an issmdpp to the Serving MSC.l. The Serving MSC returns an smdpp to the MC.m. The MC sends another SMDPP to the registered MSC for the MS-based

45、 SME. The MC setsthe SMSMSGCNT parameter to zero.n. The Serving MSC sends an ISSMDPP to the Border MSC to with the SMS message. TheSMSMSGCNT parameter is set to zero to indicate that there are no more messages todeliver.o. The Border MSC delivers the SMS message to the destination MS.p. The MS ackno

46、wledges receipt of the SMS message.q. The Border MSC releases the MS from the traffic channel.r. The Border MSC returns an issmdpp to the Serving MSC.s. The Serving MSC returns an smdpp to the MC.t. The Border MSC sends a REGNOT toward the MSs HLR to register the MS.Note: the Border MSC may initiate

47、 registration notifications procedures at any time after Step-h.u. The HLR returns a regnot to the Serving VLR/MSC.X.S0004-372-E v1.0123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960372-7 SMS delivery to Border MSC2.3 Unsuccessful Deliver

48、y of SMS Message to MS in Border MSC: Authentication FailureThis scenario illustrates unsuccessful delivery of an SMS message to an MS in a Border MSCdue to an authentication failure.a. The MC initiates an “SMS termination to MS-based SME” by sending an SMDPP to thenetwork address of record for the

49、destination MS.b. The Serving MSC pages the destination MS both locally and, since the MS last registeredwhile on or near the system border, in a single Border MSC by means of an ISPAGE2. TheServing MSC sets the CDMASO parameter in to indicate the SMS service.c. The Border MSC pages the indicated MS with the SMS CDMA service option.d. The destination MS responds to the page.e. The Border MSC assigns the MS to a traffic channel.f. The Border MSC returns an ispage2 to the Serving MSC. The ispage2 contains theappropriate authentication parameters received from the