1、 TIA-1055 APPROVED: MARCH 1, 2006 REAFFIRMED: JUNE 21, 2012 TIA-1055 March 2006MAP Enhancements to Support Enhanced Message Waiting Notification (MWN) NOTICE TIA Engineering Standards and Publications are designed to serve the public interest through eliminating misunderstandings between manufacture
2、rs 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
3、-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 adopted by T
4、IA 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 safet
5、y 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. 3-0183, formulated u
6、nder the cognizance of the TIA TR-45 Mobile (b) there 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 pr
7、actice of contents of this Document may involve the use 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 ar
8、e claimed and called to TIAs attention, a statement from 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 t
9、o discussions of any licensing terms or conditions, which 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
10、 the Manual have been complied with as respects the Document 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,
11、 specification, recommendation or otherwise), whether 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
12、assurance relating to any such Normative Reference; (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
13、of the other SSO shall not constitute identification 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 serv
14、ices or any claims of compliance with the contents of 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 AN
15、D ITS NONINFRINGEMENT OF ANY THIRD PARTYS INTELLECTUAL 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
16、 HEALTH EFFECTS OF THE CONTENTS OR ANY PRODUCT OR SERVICE 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 LIMI
17、TATION ANY AND ALL INDIRECT, SPECIAL, INCIDENTAL OR CONSEQUENTIAL 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
18、 POSSIBILITY OF SUCH DAMAGES. THE FOREGOING NEGATION 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. TIA-1055123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051
19、525354555657585960i ContentsMAP Enhancements to SupportEnhanced Message Waiting Notification (MWN)CONTENTSList of FiguresiiiList of Tables.ivForewordvRevision HistoryviIntroduction11 Objective12 Scope.13 Normative References.14 Editorial Conventions1Part 000 - Introduction to TIA-4134 Symbols and Ab
20、breviations 3Automatic Roaming Information Flows46.13 Message Waiting Count Notification .46.13.T Successful Message Waiting Count Notification.46.13.U Message Waiting Count Notification: Initial MS Registration66.13.V No Message Waiting Count Notification: Initial MS Registration.86.13.W No Message
21、 Waiting Count Notification106.13.X Successful MSInactive: MS Declared Inactive126.13.Y Successful MSInactive: MS Deregistered13MAP Operations Signaling Protocol.142 Operation Definitions. 142.39 MSInactive142.49 RegistrationCancellation.16MAP Parameters Signaling Protocol.171 General. 171.2 Paramet
22、er Identifiers.172 Parameter Definitions. 182.182 Profile18TIA-1055Contents123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960ii2.xxx MessageWaitingCountAcknowledged.19Signaling Procedures.203.1 Registration Call Tasks203.1.3 Loading of Pro
23、file Parameters.204.30 MS Inactive234.30.1 MSC Initiating an MS Inactive234.30.2 VLR Receiving MSInactive INVOKE244.30.3 VLR Detection of MS Inactivity244.30.4 HLR Receiving MSInactive INVOKE254.37 Registration Cancellation.274.37.1 HLR Initiating Registration Cancellation274.37.4 MSC Receiving Regi
24、strationCancellation INVOKE.284.38 Registration Notification314.38.1 MSC Initiating MS Registration314.38.2 VLR Receiving RegistrationNotification INVOKE334.38.3 HLR Receiving RegistrationNotification INVOKE385.13 Message Waiting Notification (MWN)425.13.6 HLR MWN Status Change Invocation425.13.9 MS
25、C MWN Status Change Invocation42TIA-1055123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960iii List of FiguresLIST OF FIGURESAutomatic Roaming Information FlowsFigure 1 Successful Message Waiting Count Notification4Figure 2 Message Waiting
26、Count Notification: Initial MS Registration6Figure 3 No Message Waiting Count Notification: Initial MS Registration8Figure 4 No Message Waiting Count Notification: Initial MS Registration10Figure 5 Successful MSInactive: MS Declared Inactive12Figure 6 Successful MSInactive: MS Declared Inactive13TIA
27、-1055List of Tables123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960ivLIST OF TABLESPart 000 - Introduction to TIA-41Table 2 Symbols and Abbreviations3MAP Parameters Signaling ProtocolTable 1 MAP Parameter Identifiers.17TIA-10551234567891
28、01112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960v ForewordFOREWORD(This foreword is not part of this Standard.)This Standard describes the modifications and additions to MAP for enhanced Message WaitingNotification (MWN) operation. The enhanced MW
29、N operations can reduce the load on theforward control channel that is associated with updating the MSs Message Waiting Count.This Standard is organized into the following sections:Introduction. This section describes the scope of this document and providesdocument references and editorial conventio
30、ns.Part 000 - Introduction to TIA-41. This section describes the additions andmodifications to MAP Part 000 (Introduction to TIA-41) needed for enhancedMessage Waiting Count Notification.Automatic Roaming Information Flows. This section provides automatic roaminginformation flows that illustrate enh
31、anced Message Waiting Count Notification.MAP Signaling Protocol. This sections provides the additions and modifications toMAP Operations Signaling Protocol and MAP Parameters Signaling Protocol neededfor enhanced Message Waiting Count Notification.MAP Signaling Procedures. This section provides the
32、additions and modifications toMAP Signaling Procedures for enhanced Message Waiting Count Notification.TIA-1055Revision History123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960viREVISION HISTORYRevision Date Remarks0 October 2005 Initial
33、PublicationTIA-1055 1234567891011121314151617181920212223242526272829303132333435363738394041424344454647484950515253545556575859601Objective IntroductionINTRODUCTION1ObjectiveThe purpose of this document is to describe enhanced Message Waiting Notification (MWN)operation that reduces the load on th
34、e forward control (paging) channel associated withupdating the MSs Message Waiting Count.2 ScopeThis document provides automatic roaming information flows that illustrate enhanced MessageWaiting Count operation. This document also describes the signaling protocol and signalingprocedure modifications
35、 needed for enhanced Message Waiting Count operation. 3 Normative ReferencesThe following specifications and standards contain provisions which, through reference in thistext, constitute provisions of this Standard. At the time of publication, the editions indicatedwere valid. All standards and spec
36、ifications are subject to revision, and parties to agreementsbased on this document are encouraged to investigate the possibility of applying the most recenteditions of the standards indicated below. ANSI and TIA maintain registers of currently validnational standards published by them.1 TIA/EIA-41-
37、D, Cellular Radiotelecommunications Intersystem Operations,Telecommunications Industry Association; December 19972 TI-41-000-E, Introduction to TIA-41, Telecommunications Industry Association;March 20043 TIA-41-540-E; MAP Operations Signaling Protocols, TelecommunicationsIndustry Association; March
38、20044 TIA-41-550-E, MAP Parameters Signaling Protocols, TelecommunicationsIndustry Association; March 20045 TIA-751, TIA/EIA-41-D Modifications to Support IMSI, TelecommunicationsIndustry Association; January 20026 TIA/EIA/IS-807, TIA/EIA-41-D Enhancements for Internationalization,Telecommunications
39、 Industry Association; August 19994 Editorial ConventionsThe following editorial conventions are applicable for this document: underline: additioncross out: deletion change bar: indicates additions or deletionsTIA-1055Introduction1234567891011121314151617181920212223242526272829303132333435363738394
40、041424344454647484950515253545556575859602 Editorial Conventions new sub-sections are identified in the sub-section heading for clarity, new sub-sections are shown with vertical change bars but are not underlinedTIA-1055 1234567891011121314151617181920212223242526272829303132333435363738394041424344
41、454647484950515253545556575859603 Part 000 - Introduction to TIA-41PART 000 - INTRODUCTION TO TIA-41The section describes the modifications to 2 needed for enhanced Message Waiting Countoperation.4 Symbols and Abbreviations(see 2, page 000-28)Table 2 Symbols and AbbreviationsSymbol or Abbreviation M
42、eaningMWCACKMessageWaitingCountAcknowledged parameterTIA-1055Automatic Roaming Information Flows1234567891011121314151617181920212223242526272829303132333435363738394041424344454647484950515253545556575859604AUTOMATIC ROAMING INFORMATION FLOWSThis section provides automatic roaming information flows
43、 that illustrate enhanced intersystemoperations for message waiting count notification.6.13 Message Waiting Count Notification6.13.T Successful Message Waiting Count NotificationThis scenario illustrates successful message waiting count notification. The Serving MSC storesinformation on the message
44、waiting count acknowledged by the MS.a. The HLR is notified that there is a message waiting for a served MS.b. The HLR reports the change in the MSs MWN status by sending a QUALDIRto the VLRwhere the MS is registered.c. The VLR sends a qualdirto the HLR.d. The VLR reports the change in the MSs MWN s
45、tatus by sending a QUALDIRto theServing MSC. Additional parameters are as in Step-b.e. The Serving MSC sends a qualdirto the VLR.Figure 1 Successful Message Waiting Count NotificationParameters Usage TypeMWNTYPE Indicates that notification via Message Waiting CountIndicationis required.RMWNCOUNT Ind
46、icates the type and number of messages waiting. RMS MSC VLR HLRmessage waitingQUALDIR MWNTYPE, MWNCOUNTaQDTqualdirQDTqualdirMWN indication, MWN countServing SystembcdefgMWN acknowledgementhQUALDIR MWNTYPE, MWNCOUNTUpdate MWNCount AcknowledgedTIA-1055 1234567891011121314151617181920212223242526272829
47、303132333435363738394041424344454647484950515253545556575859605 Automatic Roaming Information Flowsf. The Serving MSC compares the received MWNCOUNT and MWCACK parametervalues. The parameter values are not equal and the Serving MSC notifies the served MS ofthe change in the MSs MWN status via the ap
48、propriate notification method (i.e., MessageWaiting Indication and Count Indication).g. The MS acknowledges the notification.h. The MSC updates the Message Waiting Count Acknowledgedfor the MS.TIA-1055Automatic Roaming Information Flows1234567891011121314151617181920212223242526272829303132333435363
49、7383940414243444546474849505152535455565758596066.13.U Message Waiting Count Notification: Initial MS RegistrationThis scenario illustrates successful message waiting count notification when the MS roams to anew system. The Serving MSC stores information on the message waiting count acknowledgedby the MS.a. The MS accesses the new Serving MSC (MSC-2).b. After determining that a roaming MS is now within its service area, the new Serving MSC(MSC-2) sends a REGNOTto its VLR (VLR-2); MSC-2 may detect the MSs presencethrough autonomous registratio
