ANSI TIA-41.641-E-2005 Mobile Application Part (MAP)-Short Message Service (SMS) Procedures《系统间无线电通信.短信息服务（SMS）》.pdf

《ANSI TIA-41.641-E-2005 Mobile Application Part (MAP)-Short Message Service (SMS) Procedures《系统间无线电通信.短信息服务（SMS）》.pdf》由会员分享，可在线阅读，更多相关《ANSI TIA-41.641-E-2005 Mobile Application Part (MAP)-Short Message Service (SMS) Procedures《系统间无线电通信.短信息服务（SMS）》.pdf（58页珍藏版）》请在麦多课文档分享上搜索。

1、 TIA-41.641-E (Revision of TIA/EIA-41-D) December 2005Mobile Application Part (MAP)- Short Message Service (SMS) Procedures ANSI/TIA-41.641-E-2012 APPROVED: NOVEMBER 16, 2005 REAFFIRMED: APRIL 13, 2012 NOTICE TIA Engineering Standards and Publications are designed to serve the public interest throug

2、h eliminating misunderstandings 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

3、shall not in any respect 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 internati

4、onally. Standards and Publications 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.

5、This Standard does not purport 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 bef

6、ore its use. (From Project No. ANSI/TIA-PN-41.641-E-RF1, formulated under 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 chang

7、ed 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”), including pending or issued patents, or copyrights, owned by one or more parties. TIA makes no search or investigation for IPR. When I

8、PR 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 accordance with the Manual. TIA takes no position with reference to, and disclaims any obligation to investigate or inquire into, the

9、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, nor will TIA opine or judge whether proposed licensing terms or conditions are reasonable or non-discriminatory. TIA does not warra

10、nt 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 contains one or more Normative References to a document published by another organization (“other SSO”) engaged in the formulation, devel

11、opment or publication of standards (whether designated as a standard, 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 sear

12、ch 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 disclosure (see Engineering Manual Section 6.5.1) of Essential Patent(s) and published pending patent applications shall apply; and

13、(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 published pending patent applications. TIA does not enforce or monitor compliance with the contents of the Document. TIA does not cert

14、ify, inspect, test or otherwise investigate products, designs or services 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 AP

15、PROPRIATENESS FOR A PARTICULAR PURPOSE OR USE, ITS MERCHANTABILITY AND 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 COMPLIA

16、NCE 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 RENDERED TO COMPLY WITH THE CONTENTS. TIA SHALL NOT BE LIABLE FOR ANY AND ALL DAMAGES, DIRECT OR INDIRECT, ARISING FROM OR RELATIN

17、G TO ANY USE OF THE CONTENTS CONTAINED HEREIN, INCLUDING WITHOUT LIMITATION 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 (INCLUDIN

18、G 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 OF THE CONTENTS HEREOF, AND THESE CONTENTS WOULD NOT BE PUBLISHED BY TIA WITHOUT SUCH LIMITATIONS. REVISION HISTORY Copyright Telec

19、ommunications Industry Association 2005, All rights reserved.This document is subject to change.Revision Date RemarksIS-41-D December 1997 Initial ANSI publication.TIA-41.641-E July 2005 Initial publication with new part structure.TIA-41.641-E123456789101112131415161718192021222324252627282930313233

20、343536373839404142434445464748495051525354555657585960641-1 SMS Delivery BackwardPART 641SHORT MESSAGE SERVICE (SMS)1 SMS DELIVERY BACKWARD1.1 MSC Initiating SMS Delivery BackwardUpon request to send an MS-originated SMS point-to-point message up the handoff chain, the MSCshall do the following:1 In

21、clude InterMSCCircuitID parameter set to the trunk used in the direction toward the Anchor MSC.2 IF the MSC is the Serving MSC:2-1 IF the destination address was provided (by the MS):2-1-1 Include the SMS_DestinationAddress parameter set to the destination address.2-2 ENDIF.2-3 Include the SMS_Origi

22、nalDestinationAddress parameter set to the original destination address (provided by the MS).2-4 IF the original originating address was provided (by the MS):2-4-1 Include the SMS_OriginalOriginatingAddress parameter set to the original originatingaddress.2-5 ENDIF.2-6 Include other parameters as ap

23、propriate.3 ELSE (the MSC is acting as a Tandem MSC for the MS):3-1 Include all parameters received from the calling task (see Part 540).4 ENDIF.5 Send a SMSDeliveryBackward INVOKE message toward the Destination Address.6 Start the Short Message Backward Timer (SBT).7 WAIT for an SMS Delivery Backwa

24、rd response:8 WHEN a RETURN RESULT is received:8-1 Stop the timer (SBT).8-2 IF the message can be processed:8-2-1 IF the SMSDeliveryBackward INVOKE was initiated by an initial Serving MSC:8-2-1-1 IF an intersystem handoff (handoff forward) has occurred:8-2-1-1-1 Execute the “MSC Initiating SMS Deliv

25、ery Point To Point Ack“ task (see Part 641, sec. 4.1).8-2-1-1-2 Exit this task.8-2-1-2 ENDIF.8-2-2 ENDIF.TIA-41.641-EMSC Initiating SMS Delivery Backward123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960641-28-2-3 Relay all parameters rece

26、ived.8-2-4 Return to the calling task as accepted.8-3 ELSE (the message cannot be processed):8-3-1 Return to the calling task with the SMS_CauseCode indicating Other Network Problem.8-4 ENDIF.9 WHEN a FacilitiesRelease INVOKE is received :9-1 Stop the timer (SBT).9-2 Exit this task.10 WHEN a RETURN

27、ERROR1is received :10-1 Stop the timer (SBT).10-2 Return to the calling task with the SMS_CauseCode indicating Other Network Problem.11 WHEN a REJECT is received:11-1 Stop the timer (SBT).11-2 CASE reject problem specifier OF:11-3 Unrecognized component,11-4 Incorrect component portion,11-5 Badly st

28、ructured component portion,11-6 Incorrect parameter,11-7 Unrecognized package type,11-8 Incorrect transaction portion,11-9 Badly structured transaction portion:11-9-1 Return to the calling task with the SMS_CauseCode indicating Encoding Problem.11-10 Unrecognized operation code:11-10-1 Return to the

29、 calling task with the SMS_CauseCode indicating SMS not supported.11-11 DEFAULT:11-12 Return to the calling task with the SMS_CauseCode indicating Network failure.11-13 ENDCASE:12 WHEN the timer (SBT) expires:12-1 Return to the calling task with the SMS_CauseCode indicating Network failure.13 ENDWAI

30、T.1The sending of an SMS DeliveryBackward RETURN ERROR is not recommended and error tables are not supplied.TIA-41.641-E123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960641-3 MSC Receiving an SMSDeliveryBackwardINVOKE1.2 MSC Receiving an

31、SMSDeliveryBackward INVOKEUpon receipt of an SMSDeliveryBackward INVOKE, the MSC shall do the following:1 IF the received message can be processed:1-1 IF the SMS_DestinationAddress parameter is received:1-1-1 Set the destination address with the address in the received SMS_DestinationAddress paramet

32、er.1-2 ENDIF.1-3 IF the SMS_OriginalDestinationAddress parameter is received:1-3-1 Set the original destination address with the address in the received SMS_OriginalDestinationAddress parameter.1-4 ELSE:1-4-1 Include the SMS_CauseCode parameter set to Missing Expected Parameter.1-4-2 Send a RETURN R

33、ESULT.1-4-3 Exit this task.1-5 ENDIF.1-6 IF the SMS_OriginalOriginatingAddress parameter is received:1-6-1 Set the original originating address with the address in the received SMS_OriginalOriginatingAddress parameter.1-7 ENDIF.1-8 Relay all parameters received.1-9 IF the MSC is the Anchor MSC:1-9-1

34、 Execute the “Anchor MSC Initiating SMS Delivery Point-To-Point” task (see Part 641, sec. 3.5).1-9-2 Relay all parameters received.1-10 ELSE (the MSC is a Tandem MSC):1-10-1 Execute the “MSC Initiating SMS Delivery Backward” task (see Part 641, sec. 1.1).1-10-1-1 Discard the InterMSCCircuitID parame

35、ter.1-10-1-2 Relay all parameters received.1-10-2 ELSE (the handing-off system does not support SMS):1-10-2-1 Include the SMS_CauseCode parameter set to Network failure.1-10-3 ENDIF.1-11 ENDIF.1-12 Send a RETURN RESULT towards the Serving MSC.2 ELSE (the received message cannot be processed):2-1 Inc

36、lude the SMS_CauseCode parameter indicating the proper value.2-2 Send a RETURN RESULT.3 ENDIF.4 Exit this task.TIA-41.641-ESMS Delivery Forward123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960641-42 SMS DELIVERY FORWARD2.1 MSC Initiating

37、SMS Delivery ForwardUpon request to send an MS terminated SMS point-to-point message down a handoff chain, theMSC shall do the following:1 Relay included parameters.2 Include the SMS_OriginalDestinationAddress parameter received from the invoking task.3 IF the MSC is the Anchor MSC AND IF the MCs ad

38、dress may be sent to the MS:3-1 Include the SMS_OriginatingAddress parameter set to the originating address.4 ENDIF.5 IF the message original originating address is not the same as the originating address:5-1 Include the SMS_OriginalOriginatingAddress parameter set to the original originating addres

39、s.6 ELSEIF the SMS_OriginatingAddress was received from the invoking task:6-1 Include the received SMS_OriginatingAddress parameter.7 ENDIF.8 Send a SMSDeliveryForward INVOKE message toward the MSC currently serving the destination MS.9 Start the Short Message Forward Timer (SFT).10 WAIT for an SMS

40、Delivery Forward response:11 WHEN a RETURN RESULT is received:11-1 Stop the timer (SFT).11-2 IF the message can be processed:11-2-1 Return to the calling task with the received parameters.11-3 ELSE (the message cannot be processed):11-3-1 Include the SMS_CauseCode parameter indicating Other Network

41、Problem.11-3-2 Return to the calling task.11-4 ENDIF.12 WHEN a RETURN ERROR1 is received:12-1 Stop the timer (SFT).12-2 Include the SMS_CauseCode parameter indicating Other Network Problem.12-3 Return to the calling task.13 WHEN a REJECT is received:13-1 Stop the timer (SBT).13-2 CASE reject problem

42、 specifier OF:13-3 Unrecognized component,13-4 Incorrect component portion,1The sending of an SMS DeliveryForward RETURN ERROR is not recommended and error tables are not supplied.TIA-41.641-E123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585

43、960641-5 MSC Initiating SMS Delivery Forward13-5 Badly structured component portion,13-6 Incorrect parameter,13-7 Unrecognized package type,13-8 Incorrect transaction portion,13-9 Badly structured transaction portion:13-9-1 Return to the calling task with the SMS_CauseCode indicating Encoding Proble

44、m.13-10 Unrecognized operation code:13-10-1 Return to the calling task with the SMS_CauseCode indicating SMS not supported.13-11 DEFAULT13-11-1 Return to the calling task with the SMS_CauseCode indicating Network failure.13-12 ENDCASE:14 WHEN the timer (SFT) expires:14-1 Include the SMS_CauseCode pa

45、rameter indicating Network failure.14-2 Return to the calling task.15 ENDWAIT.TIA-41.641-EMSC Receiving an SMSDeliveryForward INVOKE123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960641-62.2 MSC Receiving an SMSDeliveryForward INVOKEUpon r

46、eceipt of an SMSDeliveryForward INVOKE, the MSC shall do the following:1 IF the received message can be processed:1-1 IF neither the MobileIdentificationNumber or IMSI parameter is received:1-1-1 Include the SMS_CauseCode parameter set to Missing Expected Parameter.1-1-2 Send a RETURN RESULT.1-1-3 E

47、xit this task.1-2 ENDIF.1-3 IF the SMS_OriginalDestinationAddress parameter is received:1-3-1 Set the original destination address with the address in the received SMS_OriginalDestinationAddress parameter.1-4 ELSE:1-4-1 Include the SMS_CauseCode parameter set to Missing Expected Parameter.1-4-2 Send

48、 a RETURN RESULT.1-4-3 Exit this task.1-5 ENDIF.1-6 IF the SMS_OriginatingAddress parameter is received:1-6-1 Set the originating address with received SMS_OriginatingAddress.1-7 ENDIF.1-8 IF the SMS_OriginalOriginatingAddress parameter is received:1-8-1 Set the original originating address with the

49、 address in the received SMS_OriginalOriginatingAddress parameter.1-9 ELSE:1-9-1 Include the SMS_CauseCode parameter set to Missing Expected Parameter.1-9-2 Send a RETURN RESULT.1-9-3 Exit this task.1-10 ENDIF.1-11 IF the MSC is the Serving MSC:1-11-1 IF the MS is currently able to receive SMS messages:1-11-1-1 Execute the “MSC Initiating SMD-REQUEST toward an MS-Based SME” task (see Part 691, sec. 4).1-11-1-2 Relay all received parameters.1-11-2 ELSE (the MS is unable to receive SMS messages):1-11-2-1 Include the SMS_CauseCode parameter set to the appropriate value.1-11-3 ENDIF.1-12 ELS