TIA EIA IS-841-2000 TIA EIA-41-D Based Network Enhancements for MDN Based Message Centers《MDN基信息中心用TIA EIA-41-D基网络增强》.pdf

1、 TIA/EIAINTERIM STANDARDTIA/EIA-41-D Based NetworkEnhancements for MDN BasedMessage CentersTIA/EIA/IS-841SEPTEMBER 2000TELECOMMUNICATIONS INDUSTRY ASSOCIATIONRepresenting the telecommunications industry inassociation with the Electronic Industries Alliance TIA/EIA/IS-841NOTICETIA/EIA Engineering Sta

2、ndards and Publications are designed to serve the public interest through eliminatingmisunderstandings between manufacturers and purchasers, facilitating interchangeability and improvement ofproducts, and assisting the purchaser in selecting and obtaining with minimum delay the proper product for hi

3、sparticular need. Existence of such Standards and Publications shall not in any respect preclude any member ornonmember of TIA/EIA from manufacturing or selling products not conforming to such Standards and Publications,nor shall the existence of such Standards and Publications preclude their volunt

4、ary use by those other than TIA/EIAmembers, whether the standard is to be used either domestically or internationally.Standards and Publications are adopted by TIA/EIA in accordance with the American National Standards Institute(ANSI) patent policy. By such action, TIA/EIA does not assume any liabil

5、ity to any patent owner, nor does itassume any obligation whatever to parties adopting the Standard or Publication. TIA/EIA INTERIM STANDARDSTIA/EIA Interim Standards contain information deemed to be of technical value to the industry, and are published atthe request of the originating Committee wit

6、hout necessarily following the rigorous public review and resolution ofcomments which is a procedural part of the development of a TIA/EIA Standard.TIA/EIA Interim Standards should be reviewed on an annual basis by the formulating Committee and a decisionmade on whether to proceed to develop a TIA/E

7、IA Standard on this subject. TIA/EIA Interim Standards must becancelled by the Committee and removed from the TIA/EIA Standards Catalog before the end of their third year ofexistence.Publication of this TIA/EIA Interim Standard for trial use and comment has been approved by theTelecommunications Ind

8、ustry Association. Distribution of this TIA/EIA Interim Standard for comment shall notcontinue beyond 36 months from the date of publication. It is expected that following this 36 month period, thisTIA/EIA Interim Standard, revised as necessary, will be submitted to the American National Standards I

9、nstitute forapproval as an American National Standard. Suggestions for revision should be directed to: Standards Automatic Roaming Information Flows Enhancements . 24.33 SMSNotification. 24.33.1 Successful SMSNotification: MS-Based SME Availability Report . 24.33.2 Successful SMSNotification: MS-Bas

10、ed SME Unavailability Report 44.34 SMSRequest 54.34.1 Successful SMSRequest: MS-Based SME Address Request 64.34.2 Unsuccessful SMSRequest: MS-Based SME Address Request 86 VOICE FEATURES SCENARIOS 106.13 Message Waiting Notofication.6.13.x1 Message Waiting Update from a Voice Mail System (proprietary

11、 interface). 106.13.x2 Message Waiting Update from a Message Center or Voice Mail System 116.13.x3 Message Waiting Update from a Voice Mail System 127 SHORT MESSAGE SERVICE SCENARIOS . 147.1 Successful Short Message to a Known MS-Based SME 147.2 Short Message to a Denied MS-Based SME without Current

12、 Address 187.3 Short Message Time-Out to an MS-Based SME without Notification 207.4 Short Message Time-Out to an MS-Based SME with Notification 227.5 Short Message with Originating SMS Supplementary Services to an MS-BasedSME. 247.8 Successful Short Message Between Two MS-Based SMEs 267.9 Short Mess

13、age Between Two MSs with Originating SMS Supplementary Services . 277.10 Postponed SMSRequest without Current Address 297.11 Postponed SMDPP 31TIA/EIA/IS-841123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960Contents ii3. TIA/EIA-41.5-D Sta

14、ge 3; Signaling Protocol Enhancements . 336.4.1.2 Operation Specifiers. 336.4.2 Operation Definitions. 336.4.2.xx MessageDirective 366.4.2.43 SMSDeliveryPointToPoint. 346.4.2.44 SMSNotification. 396.4.2.45 SMSRequest 414. TIA/EIA-41.6-D Stage 3; Signaling Procedures Enhancements. 434.XX Message Dire

15、ctive . 434.XX.1 HLR Receiving MessageDirective INVOKE. 434.47 SMS NOTIFICATION. 444.47.1 MSC Initiating SMS Notification 444.47.2 MSC Initiating SMS Notification 454.47.3 MC Receiving an SMSNotification INVOKE. 464.48.1 MC Initiating SMS Request 464.48.2 HLR Receiving an SMSRequest INVOKE. 477 OPER

16、ATION TIMER VALUES 48TIA/EIA/IS-841123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960iii List Of FiguresLIST OF FIGURESFigure 78 Successful SMSNotification: MS-Based SME Availability Report 2Figure 79 Successful SMSNotification: MS-Based S

17、ME Unavailability Report . 4Figure 80 Successful SMSRequest: MS-Based SME Address Request. 6Figure 81 Unsuccessful SMSRequest: MS-Based SME Address Request . 8Figure 6.13.X1 Message Waiting Update from Voice Mail System (proprietary interface) 10Figure 6.13.X2 Message Waiting Update from a Message C

18、enter or Voice Mail System . 11Figure 6.13.X3 Message Waiting Update from a Voice Mail System. 12Figure 197 Successful Short Message from a Fixed SME to a Known MS-BasedSME 15Figure 198 Short Message from a Fixed SME to a Denied MS-Based SME withoutCurrent Address 18Figure 199 Short Message Time-Out

19、 to an MS-Based SME without Notification. 20Figure 200 Short Message Time-Out to an MS-Based SME with Notification. 22Figure 201 Short Message from a Fixed SME with Originating SupplementaryServices to an Active MS-Based SME 24Figure 204 Successful Short Message Between Two MS-Based SMEs . 26Figure

20、205 Short Message Between Two MS-Based SMEs with Originating SMSSupplementary Services. 28Figure 206 Postponed SMSRequest without Current Address . 29Figure 207 Postponed SMDPP. 31TIA/EIA/IS-8411234567891011121314151617181920212223242526272829303132333435363738394041424344454647484950515253545556575

21、85960List Of Tables ivLIST OF TABLESTIA/EIA-41.3-DTable 33 FE Combinations for SMSNOT . 2Table 34 FE Combinations for SMSREQ . 5Table 8 (concluded) 33Table 10 (concluded) Table 6.4.2.X FE Combinations for MSGDIR 34Table 6.4.2.X1 MessageDirective INVOKE Parameters. 34Table 6.4.2.X2 MessageDirective I

22、RETURN RESULTS Parameters. 35Table 94 SMSDeliveryPointToPoint INVOKE Parameters . 36Table 96 SMSNotification INVOKE Parameters. 39Table 97 SMSNotification RETURN RESULT Parameters 40Table 98 SMSRequest INVOKE Parameters. 41Table 99 SMSRequest RETURN RESULT Parameters 42Table 4.xx1 HLR Receiving Mess

23、ageDirective INVOKE 43Table 63 Operation Timer Values (continued). 48TIA/EIA/IS-841123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960V Revision HistoryREVISION HISTORYRevision Date Remarks1.0 September 2000 Initial publication.EDITORIAL KE

24、Ya. ANSI-41-D, ANSI-124-B or ANSI-664-A totally new sections are identifiedvia text with right hand margin “diffmarks“, as:A totally new sections text.b. ANSI-41-D, ANSI-124-B or ANSI-664-A new enhanced text is identifiedvia text with “under-score“ lines and right hand margin “diffmarks“, as:. . exi

25、sting text new enhanced text existing text. . .c. ANSI-41-D, ANSI-124-B or ANSI-664-A deleted existing text is identifiedvia text with “strike-through“ lines and right hand margin “diffmarks“, as:. . existing text deleted text existing text . .d. ANSI-41-D, ANSI-124-B or ANSI-664-A new enhanced text

26、 is identifiedvia text with “double under-score“ lines and right hand margin “diffmarks“when another standard modifies the same section, as:. . existing text new enhanced text other standards text existing text. . .TIA/EIA/IS-84112345678910111213141516171819202122232425262728293031323334353637383940

27、41424344454647484950515253545556575859601 Introduction1. INTRODUCTION1.1 OBJECTIVEThis document is intended to identify TIA/EIA-41-D WNP-PH3 (Wireless NumberPortability - Phase III) technical enhancements required to support SMS (ShortMessage Service) delivery to MDN (Mobile Directory Number) based

28、MCs (MessageCenters). These enhancements have been supported for incorporation into PN-3590(TIA/EIA-41-E) and are being published as a TIA/EIA-41-D enhancement InterimStandard (IS).1.2 SCOPEThis document is to be published as an ANSI-41-D enhancement and is planned to beincorporated into ANSI-41-F.1

29、.3 ORGANIZATIONThis document is organized per TIA/EIA-41-D.TIA/EIA/IS-841123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960Stage 2 (Signaling Scenarios) 2 TIA/EIA-41.3-D Modifications2. TIA/EIA-41.3-D Stage 2Signaling Scenarios Enhancement

30、s4.33 SMSNotification(TIA/EIA-41-D Chapter 3, page 3-147)The SMSNotification (SMSNOT) operation is used to report a change in an MSsability to receive SMS messages based on the location or status of the MS. Thismessage, at a minimum, is used to report the accessibility of an MS following apostponed

31、SMSRequest or SMSDeliveryPointToPoint. This message may also beused to revoke delivery permission previously granted with either an SMSRequest oran SMSNotification.The following table lists the valid combinations of invoking and responding FEs.Table 33 FE Combinations for SMSNOTINVOKINGFERESPONDINGF

32、EWhenCase 1 HLR MC To report a change in an MSs ability toreceive SMS messages.Case 2 MSC MC To report a change in an MSs ability toreceive SMS messages.The SMSNotification operation has two variations:1. Used to report MS-based SME availability.2. Used to report MS-based SME unavailability.4.33.1 S

33、uccessful SMSNotification: MS-Based SMEAvailability Report(TIA/EIA-41-D Chapter 3, page 3-147)This scenario describes the successful use of the SMSNotification operation,conveying to the MC the SMS_Address of an MS-based SME.abFEsmsnot SNTSMSNOT MSID, ESN, SMSADDR, MDNMCInvoking EntityFigure 78 Succ

34、essful SMSNotification: MS-Based SME Availability Reporta. The Invoking FE detects a change of an MSs status or location indicating theavailability of an MS-based SME. The Invoking FE may send an SMSNOT toTIA/EIA/IS-841123456789101112131415161718192021222324252627282930313233343536373839404142434445

35、464748495051525354555657585960TIA/EIA-41.3-D Modifications 3 Stage 2 (Signaling Scenarios)the responsible MC. If the Invoking FE has a pending request for the address ofan MS-based SME, it must respond.Parameters Usage TypeMSID MIN Used to identify the MS based SME.RESN Used to identify the MS. RSMS

36、ADDR Temporary routing address that can be used todeliver one or more short messages to theindicated MS.RMDN Used to identify the MS based SME . Ob. The MC confirms the receipt of the address by returning an smsnot to theInvoking FE.TIA/EIA/IS-84112345678910111213141516171819202122232425262728293031

37、3233343536373839404142434445464748495051525354555657585960Stage 2 (Signaling Scenarios) 4 TIA/EIA-41.3-D Modifications4.33.2 Successful SMSNotification: MS-Based SMEUnavailability Report(TIA/EIA-41-D Chapter 3, page 3-148)(TIA/EIA IS-751 page 13)This scenario describes the successful use of the SMSN

38、otification operation,revoking a previously granted permission to send SMS messages.abFEsmsnot SNTMCSMSNOT MSID, ESN, SMSACCDEN, MDNInvoking EntityFigure 79 Successful SMSNotification: MS-Based SME UnavailabilityReporta. The Invoking FE detects a change of an MSs status or location indicating theuna

39、vailability of an MS-based SME previously granted permission to send. TheInvoking FE may send a SMSNOT to the responsible MC.Parameters Usage TypeMSID MIN Used to identify the MS based SME.RESN Used to identify the MS. RSMSACCDEN Reason why messages cannot be delivered tothe MS.RMDN Used to identify

40、 the MS based SME . Ob. The MC confirms the receipt of the status change by sending a smsnot.TIA/EIA/IS-841123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960TIA/EIA-41.3-D Modifications 5 Stage 2 (Signaling Scenarios)4.34 SMSRequest(TIA/EI

41、A-41-D Chapter 3, page 3-149)The SMSRequest (SMSREQ) operation is used to request a roaming MSs temporarySMS routing address.The following table lists the valid combinations of invoking and responding FEs.Table 34 FE Combinations for SMSREQINVOKINGFERESPONDINGFEWhenCase 1 MC HLR MSs SMS routing addr

42、ess is required.Case 2 HLR Serving VLR HLR does not have current address.Case 3 Serving VLR Serving MSC SMSREQ received by Serving VLR.The SMSRequest operation has two variations:1. Successful address request, with address returned.2. Unsuccessful address request, with reason returned.TIA/EIA/IS-841

43、123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960Stage 2 (Signaling Scenarios) 6 TIA/EIA-41.3-D Modifications4.34.1 Successful SMSRequest: MS-Based SME AddressRequest(TIA/EIA-41-D Chapter 3, page 3-149)(TIA/EIA IS-751, page 14)This scenar

44、io describes the successful use of the SMSRequest operation, resulting inthe return of the SMS_Address of an MS-based SME to the MC.efcdabMSCBSMCDestinationHome SystemVLRHLRSMSREQ MSID or MDN, ESN, SMSNOTINDsmsreq SMSADDRSRTSRTSRTDestinationServing SystemSMSREQ MSID, ESN, SMSNOTINDSMSREQ MSID, ESN,

45、SMSNOTINDsmsreq SMSADDRsmsreq SMSADDR, MSIDFigure 80 Successful SMSRequest: MS-Based SME Address Requesta. If the MC does not have the current network address of the indicated MS-basedSME, it sends a SMSREQ toward the HLR (possibly using SCCP global titletranslation of the MSID or MDN MIN). The MC m

46、ay use either the MDN orthe MSID to identify the MS-based SME.Parameters Usage TypeMSID MIN Used to identify the MS based SME. O RESN Used to identify the MS. OSMSNOTIND Include if a notification of MS availability isnot required.OMDN Used to identify the MS based SME. OTIA/EIA/IS-841123456789101112

47、131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960TIA/EIA-41.3-D Modifications 7 Stage 2 (Signaling Scenarios)b. If the HLR has the current address of indicated MS-based SME, proceed toStep-f; otherwise, the HLR uses the MSID to identify the MS and forwa

48、rds theSMSREQ toward the VLR serving the addressed MS-based SME. Parameters areas in Step-a.Parameters Usage TypeMSID Used to identify the MS based SME. RESN Used to identify the MS. OSMSNOTIND Include if a notification of MS availability isnot required.Oc. The VLR forwards the SMSREQ toward the MSC

49、 serving the addressed MS-based SME. Parameters are as in Step-b Step-a.d. The Serving MSC returns an smsreq to the VLR indicating the currentnetwork address that can be associated with the indicated MS-based SME.Parameters Usage TypeSMSADDR Temporary routing address that can be used todeliver one or more short messages to theindicated MS.Re. The VLR forwards the smsreq to the requesting HLR. Parameters are as inStep-d.f. The HLR sends an smsreq