《TIA-41.641-E-2005.pdf》由会员分享，可在线阅读，更多相关《TIA-41.641-E-2005.pdf（56页珍藏版）》请在三一文库上搜索。
1、 TIA STANDARD Mobile Application Part (MAP) - Short Message Service (SMS) Procedures TIA-41.641-E (Revision of TIA/EIA-41-D) December 2005 TELECOMMUNICATIONS INDUSTRY ASSOCIATION Representing the telecommunications industry in association with the Electronic Industries Alliance ANSI/TIA-41.641-E-200
2、5 Approved: November 16, 2005 Copyright Telecommunications Industry Association Provided by IHS under license with EIALicensee=IHS Employees/1111111001, User=Wing, Bernie Not for Resale, 03/29/2007 02:16:12 MDTNo reproduction or networking permitted without license from IHS -,-,- NOTICE TIA Engineer
3、ing Standards and Publications are designed to serve the public interest through 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 produ
4、ct 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 manufacturing or selling products not conforming to such Standards and Publications. Neither shall the existence of such Standards and Publications pr
5、eclude their voluntary use by Non-TIA members, either domestically or internationally. 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 a
6、ssume any obligation whatever to parties adopting the Standard or Publication. 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 he
7、alth practices and to determine the applicability of regulatory limitations before its use. (From Standards Proposal No. 3-3590.641-RV5, formulated under the cognizance of the TIA TR-45.2 Subcommittee on Core Networks). Published by TELECOMMUNICATIONS INDUSTRY ASSOCIATION Standards and Technology De
8、partment 2500 Wilson Boulevard Arlington, VA 22201 U.S.A. PRICE: Please refer to current Catalog of TIA TELECOMMUNICATIONS INDUSTRY ASSOCIATION STANDARDS AND ENGINEERING PUBLICATIONS or call Global Engineering Documents, USA and Canada (1-800-854-7179) International (303-397-7956) or search online a
9、t http:/www.tiaonline.org/standards/search_n_order.cfm All rights reserved Printed in U.S.A. Copyright Telecommunications Industry Association Provided by IHS under license with EIALicensee=IHS Employees/1111111001, User=Wing, Bernie Not for Resale, 03/29/2007 02:16:12 MDTNo reproduction or networki
10、ng permitted without license from IHS -,-,- 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
11、document, please contact TIA Standards 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/about/faqDetail.cfm?id=18 OR Telecommunications Industry Association Standards (b) there is no assurance that the D
12、ocument 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 practice of contents of this Document may involve the use of intellectual property
13、 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 are claimed and called to TIAs attention, a statement from the holder thereof is r
14、equested, 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 to discussions of any licensing terms or conditions, which are instead left to th
15、e 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 the Manual have been complied with as respects the Document or its contents. TI
16、A 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 IMPLIED, ARE DISCLAIMED, INCLUDING WITHOUT
17、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 NON- INFRINGEMENT OF ANY THIRD PARTYS INTELLECTUAL PROPERTY RIGHTS. TIA EXPRESSLY DISCLAIMS ANY AND ALL RESPONSIBILITIES FOR THE ACC
18、URACY 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 RENDERED TO COMPLY WITH THE CONTENT
19、S. 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 OF BUSINESS, LOSS OF PROFITS, LITI
20、GATION, 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 OF THE CONTENTS HEREOF, AND THESE CO
21、NTENTS WOULD NOT BE PUBLISHED BY TIA WITHOUT SUCH LIMITATIONS. Copyright Telecommunications Industry Association Provided by IHS under license with EIALicensee=IHS Employees/1111111001, User=Wing, Bernie Not for Resale, 03/29/2007 02:16:12 MDTNo reproduction or networking permitted without license f
22、rom IHS -,-,- REVISION HISTORY Copyright Telecommunications Industry Association 2005, All rights reserved. This document is subject to change. RevisionDateRemarks IS-41-DDecember 1997Initial ANSI publication. TIA-41.641-EJuly 2005Initial publication with new part structure. Copyright Telecommunicat
23、ions Industry Association Provided by IHS under license with EIALicensee=IHS Employees/1111111001, User=Wing, Bernie Not for Resale, 03/29/2007 02:16:12 MDTNo reproduction or networking permitted without license from IHS -,-,- Copyright Telecommunications Industry Association Provided by IHS under l
24、icense with EIALicensee=IHS Employees/1111111001, User=Wing, Bernie Not for Resale, 03/29/2007 02:16:12 MDTNo reproduction or networking permitted without license from IHS -,-,- TIA-41.641-E 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 4
25、0 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 641-1SMS Delivery Backward PART 641 SHORT MESSAGE SERVICE (SMS) 1SMS DELIVERY BACKWARD 1.1MSC Initiating SMS Delivery Backward Upon request to send an MS-originated SMS point-to-point message up the handoff chain, the MSC shall do the fol
26、lowing: 1Include InterMSCCircuitID parameter set to the trunk used in the direction toward the Anchor MSC. 2IF the MSC is the Serving MSC: 2-1IF the destination address was provided (by the MS): 2-1-1Include the SMS_DestinationAddress parameter set to the destination address. 2-2ENDIF. 2-3Include th
27、e SMS_OriginalDestinationAddress parameter set to the original destination address (provided by the MS). 2-4IF the original originating address was provided (by the MS): 2-4-1Include the SMS_OriginalOriginatingAddress parameter set to the original originating address. 2-5ENDIF. 2-6Include other para
28、meters as appropriate. 3ELSE (the MSC is acting as a Tandem MSC for the MS): 3-1Include all parameters received from the calling task (see Part 540). 4ENDIF. 5Send a SMSDeliveryBackward INVOKE message toward the Destination Address. 6Start the Short Message Backward Timer (SBT). 7WAIT for an SMS Del
29、ivery Backward response: 8WHEN a RETURN RESULT is received: 8-1Stop the timer (SBT). 8-2IF the message can be processed: 8-2-1IF the SMSDeliveryBackward INVOKE was initiated by an initial Serving MSC: 8-2-1-1IF an intersystem handoff (handoff forward) has occurred: 8-2-1-1-1Execute the “MSC Initiati
30、ng SMS Delivery Point To Point Ack“ task (see Part 641, sec. 4.1). 8-2-1-1-2Exit this task. 8-2-1-2ENDIF. 8-2-2ENDIF. Copyright Telecommunications Industry Association Provided by IHS under license with EIALicensee=IHS Employees/1111111001, User=Wing, Bernie Not for Resale, 03/29/2007 02:16:12 MDTNo
31、 reproduction or networking permitted without license from IHS -,-,- TIA-41.641-E MSC Initiating SMS Delivery Backward 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 641-2 8-2-
32、3Relay all parameters received. 8-2-4Return to the calling task as accepted. 8-3ELSE (the message cannot be processed): 8-3-1Return to the calling task with the SMS_CauseCode indicating Other Network Problem. 8-4ENDIF. 9WHEN a FacilitiesRelease INVOKE is received : 9-1Stop the timer (SBT). 9-2Exit t
33、his task. 10WHEN a RETURN ERROR1 is received : 10-1Stop the timer (SBT). 10-2Return to the calling task with the SMS_CauseCode indicating Other Network Problem. 11WHEN a REJECT is received: 11-1Stop the timer (SBT). 11-2CASE reject problem specifier OF: 11-3Unrecognized component, 11-4Incorrect comp
34、onent portion, 11-5Badly structured component portion, 11-6Incorrect parameter, 11-7Unrecognized package type, 11-8Incorrect transaction portion, 11-9Badly structured transaction portion: 11-9-1Return to the calling task with the SMS_CauseCode indicating Encoding Problem. 11-10Unrecognized operation
35、 code: 11-10-1Return to the calling task with the SMS_CauseCode indicating SMS not supported. 11-11DEFAULT: 11-12Return to the calling task with the SMS_CauseCode indicating Network failure. 11-13ENDCASE: 12WHEN the timer (SBT) expires: 12-1Return to the calling task with the SMS_CauseCode indicatin
36、g Network failure. 13ENDWAIT. 1 The sending of an SMS DeliveryBackward RETURN ERROR is not recommended and error tables are not supplied. Copyright Telecommunications Industry Association Provided by IHS under license with EIALicensee=IHS Employees/1111111001, User=Wing, Bernie Not for Resale, 03/29
37、/2007 02:16:12 MDTNo reproduction or networking permitted without license from IHS -,-,- TIA-41.641-E 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 641-3MSC Receiving an SMSDe
38、liveryBackward INVOKE 1.2MSC Receiving an SMSDeliveryBackward INVOKE Upon receipt of an SMSDeliveryBackward INVOKE, the MSC shall do the following: 1IF the received message can be processed: 1-1IF the SMS_DestinationAddress parameter is received: 1-1-1Set the destination address with the address in
39、the received SMS_DestinationAddress parameter. 1-2ENDIF. 1-3IF the SMS_OriginalDestinationAddress parameter is received: 1-3-1Set the original destination address with the address in the received SMS_OriginalDestinationAddress parameter. 1-4ELSE: 1-4-1Include the SMS_CauseCode parameter set to Missi
40、ng Expected Parameter. 1-4-2Send a RETURN RESULT. 1-4-3Exit this task. 1-5ENDIF. 1-6IF the SMS_OriginalOriginatingAddress parameter is received: 1-6-1Set the original originating address with the address in the received SMS_OriginalOriginatingAddress parameter. 1-7ENDIF. 1-8Relay all parameters rece
41、ived. 1-9IF the MSC is the Anchor MSC: 1-9-1Execute the “Anchor MSC Initiating SMS Delivery Point-To-Point” task (see Part 641, sec. 3.5). 1-9-2Relay all parameters received. 1-10ELSE (the MSC is a Tandem MSC): 1-10-1Execute the “MSC Initiating SMS Delivery Backward” task (see Part 641, sec. 1.1). 1
42、-10-1-1Discard the InterMSCCircuitID parameter. 1-10-1-2Relay all parameters received. 1-10-2ELSE (the handing-off system does not support SMS): 1-10-2-1Include the SMS_CauseCode parameter set to Network failure. 1-10-3ENDIF. 1-11ENDIF. 1-12Send a RETURN RESULT towards the Serving MSC. 2ELSE (the re
43、ceived message cannot be processed): 2-1Include the SMS_CauseCode parameter indicating the proper value. 2-2Send a RETURN RESULT. 3ENDIF. 4Exit this task. Copyright Telecommunications Industry Association Provided by IHS under license with EIALicensee=IHS Employees/1111111001, User=Wing, Bernie Not
44、for Resale, 03/29/2007 02:16:12 MDTNo reproduction or networking permitted without license from IHS -,-,- TIA-41.641-E SMS Delivery Forward 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 5
45、7 58 59 60 641-4 2SMS DELIVERY FORWARD 2.1MSC Initiating SMS Delivery Forward Upon request to send an MS terminated SMS point-to-point message down a handoff chain, the MSC shall do the following: 1Relay included parameters. 2Include the SMS_OriginalDestinationAddress parameter received from the inv
46、oking task. 3IF the MSC is the Anchor MSC AND IF the MCs address may be sent to the MS: 3-1Include the SMS_OriginatingAddress parameter set to the originating address. 4ENDIF. 5IF the message original originating address is not the same as the originating address: 5-1Include the SMS_OriginalOriginat
47、ingAddress parameter set to the original originating address. 6ELSEIF the SMS_OriginatingAddress was received from the invoking task: 6-1Include the received SMS_OriginatingAddress parameter. 7ENDIF. 8Send a SMSDeliveryForward INVOKE message toward the MSC currently serving the destination MS. 9Star
48、t the Short Message Forward Timer (SFT). 10WAIT for an SMS Delivery Forward response: 11WHEN a RETURN RESULT is received: 11-1Stop the timer (SFT). 11-2IF the message can be processed: 11-2-1Return to the calling task with the received parameters. 11-3ELSE (the message cannot be processed): 11-3-1Include the SMS_CauseCode parameter indicating Other Network Problem. 11-3-2Return to the calling task. 11-4ENDIF. 12WHEN a RETURN ERROR1 is received: 12-1Stop the timer (SFT). 12-2Include the SMS_CauseCode parameter indicating Ot