Network Support for MDN-Based Message Centers

Transcription

1 GPP N.S00-0 version.0 Version Date: November 00 Network Support for MDN-Based Message Centers COPYRIGHT GPP and its Organizational Partners claim copyright in this document and individual Organizational Partners may copyright and issue documents or standards publications in individual Organizational Partner's name based on this document. Requests for reproduction of this document should be directed to the GPP Secretariat at Requests to reproduce individual Organizational Partner's documents should be directed to that Organizational Partner. See for more information.

2

3 N.S00-0 v.0 0 CELLULAR RADIOTELECOMMUNICATIONS INTERSYSTEM OPERATIONS CONTENTS Network Support for MDN Based Message Centers LIST OF FIGURES...iii LIST OF TABLES...iv REVISION HISTORY...v EDITORIAL KEY...v. INTRODUCTION.... OBJECTIVE.... SCOPE.... ORGANIZATION.... TIA/EIA-.-D Stage ; Automatic Roaming Information Flows Enhancements.... SMSNotification..... Successful SMSNotification: MS-Based SME Availability Report..... Successful SMSNotification: MS-Based SME Unavailability Report.... SMSRequest..... Successful SMSRequest: MS-Based SME Address Request..... Unsuccessful SMSRequest: MS-Based SME Address Request... VOICE FEATURES SCENARIOS Message Waiting Notofication x Message Waiting Update from a Voice Mail System (proprietary interface) x Message Waiting Update from a Message Center or Voice Mail System.....x Message Waiting Update from a Voice Mail System... SHORT MESSAGE SERVICE SCENARIOS.... Successful Short Message to a Known MS-Based SME.... Short Message to a Denied MS-Based SME without Current Address.... Short Message Time-Out to an MS-Based SME without Notification.... Short Message Time-Out to an MS-Based SME with Notification.... Short Message with Originating SMS Supplementary Services to an MS-Based SME.... Successful Short Message Between Two MS-Based SMEs.... Short Message Between Two MSs with Originating SMS Supplementary Services....0 Postponed SMSRequest without Current Address.... Postponed SMDPP...

4 N.S00-0 v.0. TIA/EIA-.-D Stage ; Signaling Protocol Enhancements Operation Specifiers..... Operation Definitions......xx MessageDirective SMSDeliveryPointToPoint SMSNotification SMSRequest.... TIA/EIA-.-D Stage ; Signaling Procedures Enhancements....XX Message Directive....XX. HLR Receiving MessageDirective INVOKE.... SMS NOTIFICATION..... MSC Initiating SMS Notification..... MSC Initiating SMS Notification..... MC Receiving an SMSNotification INVOKE..... MC Initiating SMS Request..... HLR Receiving an SMSRequest INVOKE... OPERATION TIMER VALUES... 0 Contents ii

5 N.S00-0 v.0 0 LIST OF FIGURES Figure Successful SMSNotification: MS-Based SME Availability Report... Figure Successful SMSNotification: MS-Based SME Unavailability Report... Figure 0 Successful SMSRequest: MS-Based SME Address Request... Figure Unsuccessful SMSRequest: MS-Based SME Address Request... Figure..X Message Waiting Update from Voice Mail System (proprietary interface)... 0 Figure..X Message Waiting Update from a Message Center or Voice Mail System... Figure..X Message Waiting Update from a Voice Mail System... Figure Successful Short Message from a Fixed SME to a Known MS-Based SME... Figure Short Message from a Fixed SME to a Denied MS-Based SME without Current Address... Figure Short Message Time-Out to an MS-Based SME without Notification... Figure 0 Short Message Time-Out to an MS-Based SME with Notification... Figure Short Message from a Fixed SME with Originating Supplementary Services to an Active MS-Based SME... Figure Successful Short Message Between Two MS-Based SMEs... Figure Short Message Between Two MS-Based SMEs with Originating SMS Supplementary Services... Figure Postponed SMSRequest without Current Address... Figure Postponed SMDPP... iii List Of Figures

6 N.S00-0 v.0 LIST OF TABLES TIA/EIA-.-D Table FE Combinations for SMSNOT... Table FE Combinations for SMSREQ... Table (concluded)... Table 0 (concluded)... Table...X FE Combinations for MSGDIR... Table...X MessageDirective INVOKE Parameters... Table...X MessageDirective IRETURN RESULTS Parameters... Table SMSDeliveryPointToPoint INVOKE Parameters... Table SMSNotification INVOKE Parameters... Table SMSNotification RETURN RESULT Parameters... Table SMSRequest INVOKE Parameters... Table SMSRequest RETURN RESULT Parameters... Table.xx HLR Receiving MessageDirective INVOKE... Table Operation Timer Values (continued)... 0 List Of Tables iv

7 N.S00-0 v.0 0 REVISION HISTORY Revision Date Remarks.0 September 00 Initial publication. EDITORIAL KEY a. ANSI--D, ANSI--B or ANSI--A totally new sections are identified via text with right hand margin "diffmarks", as: A totally new section's text. b. ANSI--D, ANSI--B or ANSI--A new enhanced text is identified via text with "under-score" lines and right hand margin "diffmarks", as:.. existing text new enhanced text existing text... c. ANSI--D, ANSI--B or ANSI--A deleted existing text is identified via text with "strike-through" lines and right hand margin "diffmarks", as:.. existing text deleted text existing text.. d. ANSI--D, ANSI--B or ANSI--A new enhanced text is identified via 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 standard's text existing text... V Revision History

8

9 N.S00-0 v.0 0. INTRODUCTION. OBJECTIVE. SCOPE This document is intended to identify TIA/EIA--D WNP-PH (Wireless Number Portability - Phase III) technical enhancements required to support SMS (Short Message Service) delivery to MDN (Mobile Directory Number) based MCs (Message Centers). These enhancements have been supported for incorporation into PN-0 (TIA/EIA--E) and are being published as a TIA/EIA--D enhancement Interim Standard (IS). This document is to be published as an ANSI--D enhancement and is planned to be incorporated into ANSI--F.. ORGANIZATION This document is organized per TIA/EIA--D. Introduction

10 N.S00-0 v.0. TIA/EIA-.-D Stage Signaling Scenarios Enhancements Figure. SMSNotification (TIA/EIA--D Chapter, page -) The SMSNotification (SMSNOT) operation is used to report a change in an MS s ability to receive SMS messages based on the location or status of the MS. This message, at a minimum, is used to report the accessibility of an MS following a postponed SMSRequest or SMSDeliveryPointToPoint. This message may also be used to revoke delivery permission previously granted with either an SMSRequest or an SMSNotification. The following table lists the valid combinations of invoking and responding FEs. Table FE Combinations for SMSNOT INVOKING FE RESPONDING FE When Case HLR MC To report a change in an MS s ability to receive SMS messages. Case MSC MC To report a change in an MS s ability to receive SMS messages. The SMSNotification operation has two variations:. Used to report MS-based SME availability.. Used to report MS-based SME unavailability... Successful SMSNotification: MS-Based SME Availability Report (TIA/EIA--D Chapter, page -) This scenario describes the successful use of the SMSNotification operation, conveying to the MC the SMS_Address of an MS-based SME. Invoking Entity FE SMSNOT [MSID, ESN, SMSADDR, MDN] SNT smsnot [ ] Successful SMSNotification: MS-Based SME Availability Report a. The Invoking FE detects a change of an MS s status or location indicating the availability of an MS-based SME. The Invoking FE may send an SMSNOT to MC a b 0 Stage (Signaling Scenarios) TIA/EIA-.-D Modifications

11 N.S00-0 v.0 0 the responsible MC. If the Invoking FE has a pending request for the address of an MS-based SME, it must respond. Parameters Usage Type MSID MIN Used to identify the MS based SME. R ESN Used to identify the MS. R SMSADDR Temporary routing address that can be used to deliver one or more short messages to the indicated MS. MDN Used to identify the MS based SME. O b. The MC confirms the receipt of the address by returning an smsnot to the Invoking FE. R TIA/EIA-.-D Modifications Stage (Signaling Scenarios)

12 N.S00-0 v.0.. Successful SMSNotification: MS-Based SME Unavailability Report Invoking Entity Figure FE (TIA/EIA--D Chapter, page -) (TIA/EIA IS- page ) This scenario describes the successful use of the SMSNotification operation, revoking a previously granted permission to send SMS messages. SMSNOT [MSID, ESN, SMSACCDEN, MDN] SNT smsnot [ ] Successful SMSNotification: MS-Based SME Unavailability Report a. The Invoking FE detects a change of an MS s status or location indicating the unavailability of an MS-based SME previously granted permission to send. The Invoking FE may send a SMSNOT to the responsible MC. Parameters Usage Type MSID MIN Used to identify the MS based SME. R ESN Used to identify the MS. R SMSACCDEN MC Reason why messages cannot be delivered to the MS. MDN Used to identify the MS based SME. O b. The MC confirms the receipt of the status change by sending a smsnot. a b R 0 Stage (Signaling Scenarios) TIA/EIA-.-D Modifications

13 N.S00-0 v.0 0. SMSRequest (TIA/EIA--D Chapter, page -) The SMSRequest (SMSREQ) operation is used to request a roaming MS s temporary SMS routing address. The following table lists the valid combinations of invoking and responding FEs. Table FE Combinations for SMSREQ INVOKING FE RESPONDING FE When Case MC HLR MS s SMS routing address is required. Case HLR Serving VLR HLR does not have current address. Case Serving VLR Serving MSC SMSREQ received by Serving VLR. The SMSRequest operation has two variations:. Successful address request, with address returned.. Unsuccessful address request, with reason returned. TIA/EIA-.-D Modifications Stage (Signaling Scenarios)

14 N.S00-0 v.0.. Successful SMSRequest: MS-Based SME Address Request MC Figure 0 (TIA/EIA--D Chapter, page -) (TIA/EIA IS-, page ) This scenario describes the successful use of the SMSRequest operation, resulting in the return of the SMS_Address of an MS-based SME to the MC. Home System HLR SMSREQ [MSID or MDN, ESN, SMSNOTIND] VLR SRT SRT SRT smsreq [SMSADDR, MSID] SMSREQ [MSID, ESN, SMSNOTIND] Serving System SMSREQ [MSID, ESN, SMSNOTIND] smsreq [SMSADDR] MSC BS smsreq [SMSADDR] Successful SMSRequest: MS-Based SME Address Request a. If the MC does not have the current network address of the indicated MS-based SME, it sends a SMSREQ toward the HLR (possibly using SCCP global title translation of the MSID or MDN MIN). The MC may use either the MDN or the MSID to identify the MS-based SME. Parameters Usage Type MSID MIN Used to identify the MS based SME. O R ESN Used to identify the MS. O SMSNOTIND Include if a notification of MS availability is not required. MDN Used to identify the MS based SME. O a b c d e f O 0 Stage (Signaling Scenarios) TIA/EIA-.-D Modifications

15 N.S00-0 v.0 0 b. If the HLR has the current address of indicated MS-based SME, proceed to Step-f; otherwise, the HLR uses the MSID to identify the MS and forwards the SMSREQ toward the VLR serving the addressed MS-based SME. Parameters are as in Step-a. Parameters Usage Type MSID Used to identify the MS based SME. R ESN Used to identify the MS. O SMSNOTIND Include if a notification of MS availability is not required. c. The VLR forwards the SMSREQ toward the MSC serving the addressed MSbased SME. Parameters are as in Step-b Step-a. d. The Serving MSC returns an smsreq to the VLR indicating the current network address that can be associated with the indicated MS-based SME. Parameters Usage Type SMSADDR Temporary routing address that can be used to deliver one or more short messages to the indicated MS. e. The VLR forwards the smsreq to the requesting HLR. Parameters are as in Step-d. f. The HLR sends an smsreq to the requesting MC. Parameters are as in Step-d. Parameters Usage Type SMSADDR MSID Temporary routing address that can be used to deliver one or more short messages to the indicated MS. Identifier that should be used for SMS delivery. Use the MIN form of the MSID if the MS has a MIN; otherwise use the IMSI. O R O O TIA/EIA-.-D Modifications Stage (Signaling Scenarios)

16 N.S00-0 v.0.. Unsuccessful SMSRequest: MS-Based SME Address Request MC Figure (TIA/EIA--D Chapter, page -) (TIA/EIA IS- page ) This scenario describes the unsuccessful use of the SMSRequest operation, resulting in the reason why short messages cannot be delivered to an MS-based SME. Home System HLR SMSREQ [MSID or MDN, ESN, SMSNOTIND] SRT VLR SMSREQ [MSID, ESN, SMSNOTIND] SRT smsreq [SMSACCDEN, MSID] Serving System SMSREQ [MSID, ESN, SMSNOTIND] smsreq [SMSACCDEN] MSC BS smsreq [SMSACCDEN] Unsuccessful SMSRequest: MS-Based SME Address Request a-c. Same as Section.., Steps a-c. d. The Serving MSC returns an smsreq to the VLR indicating the reason why SMS messages cannot be delivered to the indicated MS-based SME. SRT Parameters Usage Type SMSACCDEN Reason why messages cannot be delivered to the MS-based SME. e. The VLR forwards the smsreq to the requesting HLR. Parameters are as in Step-d. a b c d e f R 0 Stage (Signaling Scenarios) TIA/EIA-.-D Modifications

17 N.S00-0 v.0 0 f. The HLR sends an smsreq to the requesting MC. Parameters are as in Step-d. Parameters Usage Type SMSACCDEN MSID Reason why messages cannot be delivered to the MS-based SME. Identifier that should be used for SMS delivery. Use the MIN form of the MSID if the MS has a MIN; otherwise use the IMSI. R O TIA/EIA-.-D Modifications Stage (Signaling Scenarios)

18 N.S00-0 v.0 VOICE FEATURE SCENARIOS (TIA/EIA--D Chapter, page -) Note: the omitted existing text is retained without modification.. Message Waiting Notification VMS Note: the omitted existing text is retained without modification...x message waiting (TIA/EIA--D Chapter, page -) Message Waiting Update from a Voice Mail System (proprietary interface) (new for TIA/EIA--D Chapter, page -) This scenario describes the updating of message waiting information for voice mail messages. The VMS has a proprietary interface with a MSC host. VMS Host System MSC MSGDIR [MDN, MWNCOUNT] MDT msgdir message waiting confirmation HLR QUALDIR [MIN, MWNTYPE, MWNCOUNT] QDT qualdir VLR QUALDIR [MIN, MWNTYPE, MWNCOUNT] Serving System qualdir MSC message waiting indication Figure..X Message Waiting Update from a Voice Mail System (proprietary interface) a. The VMS-MSC is notified that there is a message waiting for a served MS. b. The VMS-MSC reports the change in the MS's MWN status by sending a MSGDIR to the HLR. c. The HLR sends an msgdir to the VMS-MSC. d. Optionally, the MSC notifies the VMS of the outcome of the update. QDT MS a b c d e f g h i 0 Stage (Voice Feature Scenarios) 0 TIA/EIA-.-D Modifications

19 N.S00-0 v.0 0..X MC or VMS e. The HLR reports the change in the MS's MWN status by sending a QUALDIR to the VLR where the MS is registered. f. The VLR sends a qualdir to the HLR. g. The VLR reports the change in the MS's MWN status by sending a QUALDIR to the Serving MSC. h. The Serving MSC sends a qualdir to the VLR. i. The Serving MSC notifies the served MS of the change in the MS's MWN status via the appropriate method (i.e., Message Waiting Indication, Count Indication, or both). Message Waiting Update from a Message Center or Voice Mail System (new for TIA/EIA--D Chapter, page -) This scenario describes the updating of message waiting information from a message center or a voice mail system. MSGDIR [MDN, MWNCOUNT] MDT Figure..X msgdir HLR QUALDIR [MIN, MWNCOUNT] QDT qualdir VLR QUALDIR [MIN, MWNTYPE, MWNCOUNT] QDT qualdir MSC Message Waiting Indication Message Waiting Update from a Message Center or a Voice Mail System a. The MC or VMS reports the change in the MS's MWN status by sending a MSGDIR to the HLR. The MC may identify the MS by MobileDirectoryNumber, MIN or IMSI. We showed the usage of the MobileDirectoryNumber in this scenario. MS a b c d e f g TIA/EIA-.-D Modifications Stage (Voice Feature Scenarios)

20 N.S00-0 v.0..x b. The HLR sends a msgdir to the MC/VMS. c. The HLR reports the change in the MS's MWN status by sending a QUALDIR to the VLR where the MS is registered. d. The VLR sends a qualdir to the HLR. e. The VLR reports the change in the MSs MWN status by sending a QUALDIR to the Serving MSC. f. The Serving MSC sends a qualdir to the VLR. g. The Serving MSC notifies the served MS of the change in the MS's MWN status via the appropriate method (i.e., Message Waiting Indication, Count Indication, or both). Message Waiting Update from a Voice Mail System (new for TIA/EIA--D Chapter, page -) This scenario describes the updating of message waiting information for voice mail messages. VMS Host System Serving System VMS MC HLR VLR MSC MS MSGDIR [MDN, MWNCOUNT] MDT msgdir MSGDIR [MDN, MWNCOUNT] MDT msgdir QUALDIR [MIN, MWNTYPE, MWNCOUNT] QDT qualdir QUALDIR [MIN, MWNTYPE, MWNCOUNT] QDT qualdir Figure..X Message Waiting Update from a Voice Mail System a. The VMS reports the change in the MS's MWN status by sending a MSGDIR to the MC. b. The MC sends an msgdir to the VMS. c. The MC reports the change in the MS's MWN status by sending a MSGDIR to the HLR. d. The HLR sends an msgdir to the MC. a b c d e f g h 0 Stage (Voice Feature Scenarios) TIA/EIA-.-D Modifications

21 N.S00-0 v.0 0 e. The HLR reports the change in the MS's MWN status by sending a QUALDIR to the VLR where the MS is registered. f. The VLR sends a qualdir to the HLR. g. The VLR reports the change in the MS's MWN status by sending a QUALDIR to the Serving MSC. h. The Serving MSC sends a qualdir to the VLR. TIA/EIA-.-D Modifications Stage (Voice Feature Scenarios)

22 N.S00-0 v.0 SHORT MESSAGE SERVICE SCENARIOS (TIA/EIA--D Chapter, page -) This section depicts the interactions between network entities in the situations related to short message service support under automatic roaming conditions. The following abbreviations, which are in addition to those described in Section., are used in this section: SMD-REQUEST An implementation dependent air interface message for a short message delivery request. SMD-ACK An implementation dependent air interface message for a short message delivery positive acknowledgment. SMD-NAK An implementation dependent air interface message for a short message delivery negative acknowledgment. {A} The address of SME A. {A A s MC} The address of SME A implying the address of SME A s home MC. {A s MSC} The address of the MSC serving MS-based SME A. {B} The address of SME B. {B B s MC} The address of SME B implying the address of SME B s home MC. {B s MSC} The address of the MSC serving MS-based SME B. ACK NACK smsdpf ([ACK]) Absence of cause code. ([NACK=cause code]) Presence of a cause code. The SMS Delivery Pending Flag.. Successful Short Message to a Known MS-Based SME (TIA/EIA--D Chapter, page -) (TIA/EIA IS- page ) This scenario describes the successful delivery of a short message to an active MSbased SME via its MC (terminating SMS supplementary services are possible). 0 Stage (SMS Scenarios) TIA/EIA-.-D Modifications

23 N.S00-0 v.0 0 B MS SME system access Serving System MSC BS REGNOT [SMSADDR] SMD-REQ SADT SMD-ACK Figure VLR Home System HLR MC SME REGNOT [SMSADDR] RNT RNT regnot [SMSRestrictions] SMSREQ [MSID] SRT smsreq [SMSADDR] smdpp [ACK] SMSDPF clear regnot [SMSRestrictions] SMSREQ [MSID] smsreq [SMSADDR] smsreq [SMSADDR, MSID] SMDPP [MSID] SMDPP SMT smdpp [ACK] SMSREQ [MSID or MDN] SRT SMSDPF don't care SRT SMT A Originator SMSDPF set Successful Short Message from a Fixed SME to a Known MS-Based SME a b c d e f g h i j k l m n o p q TIA/EIA-.-D Modifications Stage (SMS Scenarios)

24 N.S00-0 v.0 a. A MS supporting a SME becomes known to a MSC through registration or other system access. b. The MSC sends a REGNOT message to notify the VLR of the location of an MS. Additional Parameters Usage Type SMSADDR Address of the serving system to be used for the delivery of short messages. c. The VLR forwards the REGNOT message to the MS s HLR. Same parameters as in Step-b. d. The HLR records the SMS delivery address for the MS and responds with a regnot message to the VLR containing subscriber profile information. Additional Parameters Usage Type SMSRestrictions: SMS_Termination- Restrictions SMS_Origination- Restrictions SMS origination and termination restrictions for MS: Indicates that the MS is allowed to receive SMS termination messages (other than no charge messages). Include if profile was requested and the MS is SMS capable. Indicates that the MS is allowed to originate SMS messages. Include if profile was requested and the MS is SMS capable. e. The VLR forwards the regnot message to the Serving MSC. Same parameters as in Step-d. f. The MC receives and accepts an SMDPP requesting delivery of an SMS message to an MS-based SME Parameters Usage Type SMS_BearerData Any desired message. R SMS_Original- Address SMS_OriginalOriginating- Address SMS_TeleserviceIdentifier Network address of the destination SME; i.e., {B Β s MC}. Network address of the originating SME; i.e., {A}. Identification of the teleservice; used for interpreting the bearer data. g. and responds with an smdpp positive acknowledgment (which may include an SMS_BearerData parameter if there is bearer data to return). h. Steps h-m are executed because the MC does not have a current, temporary SMS routing address and status for the addressed MS-based SME. The MC sends an SMSREQ to the HLR serving the MS, containing the addressed SME. The MC may include either the MDN or the MSID to identify the MS-based SME. i. Steps i-l are executed if the HLR does not have a current temporary SMS routing address and status for the addressed MS-based SME. The HLR uses the MSID to identify the MS and forwards the SMSREQ to the VLR serving the MS, containing the addressed SME. O O O R R R 0 Stage (SMS Scenarios) TIA/EIA-.-D Modifications

25 N.S00-0 v.0 0 j. The VLR forwards the SMSREQ to the MSC serving the MS, containing the addressed SME. k. The MSC responds with an smsreq containing the temporary SMS routing address for the served MS. Parameters Usage Type SMSADDR Temporary address that can be used to route SMS messages. This address may be MSC-, or MS-specific. m. The HLR responds with an smsreq toward the MC. Parameters are as in Step-k. Parameters Usage Type SMSADDR MSID Temporary routing address that can be used to route SMS. This address may be MSC specific, or MS specific. Include preferred identifier. Use the MIN form of the MSID if the MS has a MIN; otherwise use the IMSI. n. The destination MC forwards the SMDPP toward the destination SME using the temporary SMS routing address for the MS-based SME. Parameters Usage Type MSID MIN Mobile Station Identity Identification Number. R l. The VLR forwards the smsreq toward the HLR. Same parameters as in Stepk. SMS_Original- Address SMS_OriginalOriginating- Address SMS_TeleserviceIdentifier SMS_BearerData Network address of the destination SME; i.e., {B}. Network address of the originating SME; i.e., {A}. Number of the teleservice for interpreting the SMS_BearerData. Any desired message as modified per terminating supplementary services. o. The MSC, BS, or both forward the SMD-REQUEST toward the destination SME using the air interface address of the MS-based SME (usually B s MSID MIN). p. The destination SME responds with an automatic acknowledgment (SMD- ACK) to signal the acceptance of the SMD-REQUEST. The acknowledgment may include the SMS_BearerData parameter if there is data to return. q. The MSC translates the SMD-ACK into an smdpp positive acknowledgment and returns it to the source of the corresponding SMDPP. The smdpp may include an SMS_BearerData parameter if bearer data was provided in Step-p. R R O R R R R TIA/EIA-.-D Modifications Stage (SMS Scenarios)

26 N.S00-0 v.0. Short Message to a Denied MS-Based SME without Current Address MS SME Figure B (TIA/EIA--D Chapter, page -) This scenario describes an SMSREQ operation to an MS-based SME whose address is not current and short message delivery is denied. Serving System MSC BS VLR SMSREQ [MSID, ESN] SMSREQ [MSID, ESN] SRT SRT smsreq [SMSACCDEN] smsreq [SMSACCDEN] Home System smsreq [SMSACCDEN, MSID] SMSDPF clear HLR MC SME SMDPP SMT smdpp [ACK] Originator SMSREQ [MSID or MDN] SRT SMSDPF set Short Message from a Fixed SME to a Denied MS-Based SME without Current Address a. The MC receives and accepts an SMDPP requesting delivery of an SMS message to an MS-based SME Include the same parameters as.(f). b. and responds with an smdpp positive acknowledgment (which may include an SMS_BearerData parameter if there is bearer data to return). c. Steps c-h are executed because the MC does not have a current, temporary SMS routing address and status for the addressed MS-based SME. The MC sends an SMSREQ to the HLR serving the MS, containing the addressed SME. The MC may include either the MDN or the MSID to identify the MS-based SME. d. Steps d-g are executed if the HLR does not have a current temporary SMS routing address and status for the addressed MS-based SME. The HLR uses the MSID to identify the MS and forwards the SMSREQ to the VLR serving the MS, containing the addressed SME. Include the same parameters as Step-c with A a b c d e f g h 0 Stage (SMS Scenarios) TIA/EIA-.-D Modifications

27 N.S00-0 v.0 0 the addition of ESN. Substitute the MDN parameter, if present, with the MSID parameter. e. The VLR forwards the SMSREQ to the MSC serving the MS, containing the addressed SME. Same parameters as in Step-d. f. The request for Short Message Service is denied. The MS may be unavailable for short message delivery and no notification was requested. Notification may have been requested but the MS may be denied for other reasons. The MSC responds with an smsreq with an indication to this effect. There is no effect to the SMS Delivery Pending Flag. Parameters Usage Type SMSACCDEN Reason why messages cannot be delivered to the MS. g. The VLR forwards the smsreq toward the HLR. Same parameters as in Step-f. h. The HLR responds with an smsreq toward the MC. Parameters Usage Type SMSACCDEN MSID Reason why messages cannot be delivered to the MS-based SME. Mobile Station Identity. Use the MIN form of the MSID if the MS has a MIN; otherwise use the IMSI. R R O TIA/EIA-.-D Modifications Stage (SMS Scenarios)

28 N.S00-0 v.0. Short Message Time-Out to an MS-Based SME without Notification B MS SME Figure (TIA/EIA--D Chapter, page -) This scenario describes an unsuccessful short message delivery attempt to an MSbased SME. No notification had been requested; the MSC does not set the SMS Delivery Pending Flag. Serving System MSC BS SMD-REQ SADT time-out VLR smsreq [SMSADDR] smdpp [NAK] SMSDPF clear SMSREQ [MSID, ESN] SMSREQ [MSID, ESN] SRT SRT smsreq [SMSADDR] a-j. Home System Source HLR MC SME SMDPP SMT smdpp [ACK] SMSREQ [MSID or MDN] smsreq [SMSADDR, MSID] SMDPP [MSID, SMSNOTIND=Do not notify] SMSDPF don't care SRT SMT A SMSDPF set Short Message Time-Out to an MS-Based SME without Notification Same as Section., Steps f-o, respectively, except the message is discarded at Step-i because notification is not required. k. The SADT timer for the air interface SMD-ACK message expires (or some other problem is detected, such as a power-down de-registration or intersystem handoff). a b c d e f g h i j k l 0 Stage (SMS Scenarios) TIA/EIA-.-D Modifications

29 N.S00-0 v.0 0 l. The serving MSC formulates a negative acknowledgment smdpp message and sends it toward the requesting entity. Since no notification was requested, there is no change to the SMS Delivery Pending Flag. Parameters Usage Type NAK: [SMS_CauseCode] Negative acknowledgment signal: Indicates the reason for not delivering the SMS message. R TIA/EIA-.-D Modifications Stage (SMS Scenarios)

30 N.S00-0 v.0. Short Message Time-Out to an MS-Based SME with Notification B MS SME Figure 0 (TIA/EIA--D Chapter, page -) This scenario describes an unsuccessful short message delivery attempt to an MSbased SME. Notification had been requested; the MSC sets its SMS Delivery Pending Flag. Serving System MSC BS SMD-REQ SADT time-out VLR SMSREQ [MSID,ESN] SMSREQ [MSID,ESN] SRT SRT smsreq [SMSADDR] smsreq [SMSADDR] smdpp [NAK=Postponed] SMSDPF clear Home System Source HLR MC SME SMDPP SMT smdpp [ACK] SMSREQ [MSID or MDN] smsreq [SMSADDR, MSID] SMDPP [MSID] SMSDPF don't care SRT SMT A SMSDPF set Short Message Time-Out to an MS-Based SME with Notification a b c d e f g h i j k l 0 Stage (SMS Scenarios) TIA/EIA-.-D Modifications

31 N.S00-0 v.0 0 a-j. Same as Section., Steps f-o, respectively. k. The SADT timer for the air interface SMD-ACK message expires (or some other problem is detected, such as a power-down de-registration or intersystem handoff) l. Since notification was requested, the serving MSC formulates a negative acknowledgment smdpp message indicating postponed delivery and sends it toward the requesting entity. The MSC sets its SMS Delivery Pending Flag. Parameters Usage Type NAK: [SMS_CauseCode] The MC should wait for notification. Negative acknowledgment signal: Indicates the reason for not delivering the SMS message. R TIA/EIA-.-D Modifications Stage (SMS Scenarios)

32 N.S00-0 v.0. Short Message with Originating SMS Supplementary Services to an MS-Based SME B MS SME (TIA/EIA--D Chapter, page -) This scenario describes a successful short message delivery to an MS-based SME via the originating SME's MC, invoking originating SMS supplementary services. Serving System MSC BS smdpp [ACK] Home System VLR HLR MC MC SME SMSREQ [MSID, ESN] SMSREQ [MSID, ESN] SRT smsreq [SMSADDR] SRT SMD-REQ SADT SMD-ACK smsreq [SMSADDR] smsreq [SMSADDR, MSID] SMSDPF clear SMDPP SMT smdpp [ACK] SMSREQ [MSID or MDN] SRT SMDPP [MSID] SMT SMSDPF don't care Originator Home System SMDPP SMT smdpp [ACK] SMSDPF set Originator Figure Short Message from a Fixed SME with Originating Supplementary Services to an Active MS-Based SME A a b c d e f g h i j k l m n 0 Stage (SMS Scenarios) TIA/EIA-.-D Modifications

33 N.S00-0 v.0 0 a. The MC receives and accepts an SMDPP requesting delivery of an SMS message to an MS-based SME b. and responds with an smdpp positive acknowledgment (which may include an SMS_BearerData parameter if there is bearer data to return). At this point, the originator s MC originating supplementary services, such as delayed delivery, may be performed before proceeding. c-n. Same as Section., Steps f-q. TIA/EIA-.-D Modifications Stage (SMS Scenarios)