TIA-136-711-2002 TDMA Third Generation Wireless-GSM Hosted SMS Teleservice (GHOST) (ANSI APPROVAL WITHDRAWN JUNE 12 2015).pdf

1、 ANSI/TIA-136-711-2002 APPROVED: APRIL 15, 2002 APPROVED: SEPTEMBER 18, 2013 WITHDRAWN: JUNE 12, 2015 TIA-136-711 April 2002TDMA Third Generation Wireless- GSM Hosted SMS Teleservice (GHOST) NOTICE TIA Engineering Standards and Publications are designed to serve the public interest through eliminati

2、ng 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 shall not i

3、n 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 internationally. Sta

4、ndards 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. This Standa

5、rd 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 before its use

6、. Any use of trademarks in this document are for information purposes and do not constitute an endorsement by TIA or this committee of the products or services of the company. (From Project No. ANSI/TIA-PN-136.711-WD, formulated under the cognizance of the TIA TR-45 Mobile (b) there is no assurance

7、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 practice of contents of this Document may involve the use of intellectua

8、l 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 are claimed and called to TIAs attention, a statement from the holder th

9、ereof 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 to discussions of any licensing terms or conditions, which are instead

10、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 the Manual have been complied with as respects the Document or its co

11、ntents. 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, specification, recommendation or otherwise), whether such reference c

12、onsists of mandatory, alternate or optional elements (as defined in the TIA Procedures for American National Standards) then (i) TIA disclaims any duty or obligation to search or investigate the records of any other SSO for IPR or letters of assurance relating to any such Normative Reference; (ii) T

13、IAs policy of encouragement of voluntary disclosure (see TIA Procedures for American National Standards Annex C.1.2.3) of Essential Patent(s) and published pending patent applications shall apply; and (iii) Information as to claims of IPR in the records or publications of the other SSO shall not con

14、stitute 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 services or any claims of complian

15、ce 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 AND ITS NONINFRINGEMENT OF ANY T

16、HIRD 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 HEALTH EFFECTS OF THE CONTENT

17、S 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 LIMITATION ANY AND ALL INDIRECT, S

18、PECIAL, 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 POSSIBILITY OF SUCH DAMAGES.

19、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. ANSI/TIA/EIA-136-711iForewordThis document references publications developed by ETSI (European Telecommunications StandardsInstitut

20、e). These referenced publications are freely available at http:/www.etsi.org.ANSI/TIA/EIA-136-711iiTHIS PAGE INTENTIONALLY LEFT BLANKANSI/TIA/EIA-136-711iiiContents121. INTRODUCTION 131.1 NORMATIVE REFERENCES142. PROTOCOL HIERARCHY 253. GHOST HIGHER LAYER PROTOCOL IDENTIFIER 364. GSM SMS PDU. 475. P

21、ROCEDURES . 585.1 MOBILE TERMINATED GHOST TELESERVICE595.2 MOBILE ORIGINATED GHOST TELESERVICE .5106. ACKNOWLEDGEMENTS . 6116.1 MOBILE TERMINATED SHORT MESSAGING ACKNOWLEDGEMENTS6126.2 MOBILE ORIGINATED SHORT MESSAGING ACKNOWLEDGEMENTS.7137. GHOST TELESERVICE MAPPING. 8148. MESSAGE SET.101516ANSI/TI

22、A/EIA-136-711ivFigures1Figure 1. Protocol Stack in a Mobile Station to support GHOST.22Figure 2. GHOST Example Protocol Stack23Figure 3. Mapping for Mobile Terminated GHOST Teleservice84Figure 4. Mapping for Mobile Originated GHOST Teleservice .9567ANSI/TIA/EIA-136-711 vTables12Table 1. Mapping of G

23、SM RP-ERROR Cause to R-Cause for Mobile Station Response to Mobile3Terminated Transfer Attempt.64Table 2. Mapping of TIA/EIA-136 R-Cause Code to RP-ERROR Cause within the Mobile Station75ANSI/TIA/EIA-136-71111. Introduction12GSM Hosted SMS Teleservice, GHOST, is used to deliver GSM SMS Protocol Data

24、3Units (PDUs) to and from a mobile station operating in a TIA/EIA-136 network. The4Higher Layer Protocol Data Unit field in the R-DATA Unit information element is used5to carry the GSM SMS PDUs when the Higher Layer Protocol Identifier indicates6GHOST. Refer to GSM 03.40 and GSM 04.11 for a full des

25、cription of the GSM SMS7PDUs.89It should be noted that network support for GHOST operation is beyond the scope of this10document and references to the Message Center are only provided to aid in describing the11support of GHOST operation over the air interface.12131.1 Normative References1415GSM 03.4

26、0 Digital cellular telecommunications system (Phase 2+); Technical16realization of the Short Message Service (SMS) (GSM 03.40 version177.4.0 Release 1998)1819GSM 04.11 Digital cellular telecommunications system (Phase 2+); Point-to-Point20(PP) Short Message Service (SMS) support on mobile radio inte

27、rface21(GSM 04.11 version 7.0.0 Release 1998)22ANSI/TIA/EIA-136-71122. Protocol Hierarchy12Figure 1 shows the protocol stack to support GHOST in a mobile station. The Short3Message Entity within the mobile station shall be capable of using the TIA/EIA-136 R-4DATA message transport.56Figure 1. Protoc

28、ol Stack in a Mobile Station to support7GHOST8R-DATA LayerGHOST (GSM SMS PDUs)SM-ALTIA/EIA-136 Layers 1&291011The GHOST teleservice, which exchanges GSM SMS PDUs, shall use the SAP (Service12Access Point) to the R-DATA layer1314Figure 2 shows an example of the protocol stack for the origination and

29、delivery of a15SMS PDU for a mobile station, using GHOST. This description of the processing of a16GHOST teleservice is meant to provide a high level view of the workings of the network17elements, including the mobile station, and is not meant to mandate a particular18processing algorithm.1920Figure

30、 2. GHOST Example Protocol Stack21TIA/EIA-136 Layers 1 & 2 TIA/EIA-41 Layers 1 & 2R-DATAGHOST(GSM SMS PDU)R-DATA SMDPPIWFGHOST(GSM SMS PDU)MS BMI TIA/EIA-41 MCSMDPPSM-AL SM-AL2223ANSI/TIA/EIA-136-71133. GHOST Higher Layer Protocol Identifier12The Teleservice Protocol Identifier field of the GHOST HL

31、PI as defined in TIA/EIA-3136-700-A shall be set to 000 111.4ANSI/TIA/EIA-136-71144. GSM SMS PDU12GHOST supports the following GSM SMS PDUs:34 SMS-DELIVER (BMI MS). Support per GSM 03.40 and 04.11.5 SMS-SUBMIT (MS BMI). Support per GSM 03.40 and 04.11, except that if the6Validity Period is included,

32、 it must be set to an integer value (1 octet instead of 7 in7length) when the SMS-SUBMIT is sent as part of GHOST.8 SMS-STATUS-REPORT (BMI MS). Support per GSM 03.40 and 04.11.910The SMS-COMMAND PDU (MS BMI), SMS-DELIVER-REPORT (MS BMI),11and SMS-SUBMIT-REPORT (BMI MS) are not supported by GHOST. (N

33、ote: The12SMS-DELIVER-REPORT and SMS-SUBMIT-REPORT transfer PDUs are carried13within RP-ACK or RP-ERROR relay PDUs within GSM, and there is no equivalent14within TIA/EIA-136 and TIA/EIA-41.)1516GHOST supports concatenation of multiple PDUs of the same type, as described in GSM1703.40.18ANSI/TIA/EIA-

34、136-71155. Procedures125.1 Mobile Terminated GHOST Teleservice34The BMI converts the TIA/EIA-41 SMDPP message to an R-DATA message for delivery5of the GHOST teleservice to the mobile station without opening the SMS_BearerData. At6the mobile station, the R-DATA message is processed at layer 3, which

35、passes the Higher7Layer Protocol Data Unit to the GHOST layer. The GHOST layer shall then process the8GSM SMS PDU according to GSM 03.40.9105.2 Mobile Originated GHOST Teleservice11When a mobile station is required to originate a GHOST teleservice message, the mobile12station shall proceed as follow

36、s:131. Formulate a GSM SMS PDU, the structure and maximum length of which is defined14in Section 9.2 of GSM 03.40, except that if the Validity Period is included, it shall be15set to an integer value (1 octet instead of 7 in length).162. Insert the GSM SMS PDU into the Higher Layer Protocol Data Uni

37、t of the R-Data17Unit183. The HLPI of the R-Data Unit is coded with the GHOST Teleservice Protocol19Identifier and the TSAR Indicator bit is set to 0.204. Formulate an R-DATA message. If the maximum length of the GHOST teleservice21SMS PDU together with the layer 3 overhead (see TIA/EIA-136-123) exc

38、eeds the R-22DATA Message Length in TIA/EIA-136-123 (see TIA/EIA-136-910 for further23information on mobile-originated message length limitation), then the ME shall send24an error response to the originator of the GSM SMS PDU.255. Send the R-Data message to the BMI. If the Teleservice Server Address

39、 information26element is present in the R-DATA message containing the corresponding mobile-27terminated GHOST message, then the mobile station shall use this as the Teleservice28Server Address. Otherwise, the mobile station shall use the stored Teleservice Server29Address for the GHOST HLPI.3031The

40、BMI then inter-works the R-DATA message to TIA/EIA-41 SMDPP message and32sends it to the destination specified in the Teleservice Server Address. The BMI does not33open the Higher Layer Protocol Data Unit, but converts it directly to SMS_BearerData.34ANSI/TIA/EIA-136-71166. Acknowledgements12It may

41、be noted that within GSM there are multiple levels of acknowledgement for GSM3SMS messages, as described in GSM 03.40. The lower layer acknowledgement is4provided via the CP-ACK or CP-ERROR message. The relay layer acknowledgement is5provided via the RP-ACK or RP-ERROR message. Included in an RP-ERR

42、OR message6is an RP-Cause value that gives the failure reason. A transfer layer acknowledgement7may be provided via a transfer PDU, where transfer layer errors are reported in the8TP-Failure-Cause parameter within an SMS-DELIVER-REPORT or SMS-SUBMIT-9REPORT message. Since GHOST does not support the

43、GSM SMS-DELIVER-REPORT10or SMS-SUBMIT-REPORT transfer PDUs, there is not an explicit transfer layer11acknowledgement with GHOST.12136.1 Mobile Terminated Short Messaging14Acknowledgements1516When a mobile terminated GHOST teleservice message is received the RP-layer in the17MS shall ensure that the

44、message can been transferred to the destination (as defined in18GSM 03.40) before sending an acknowledgement. If the GSM RP-layer generates a19failure, then the mobile station shall map the resulting GSM RP-Cause value into its20equivalent R-Cause code according to Table 1.2122At the BMI, the R-Caus

45、e code returned by a mobile station is mapped into a23corresponding TIA/EIA-41 SMS_CauseCode for inclusion in an SMDPP Return Result24message.25Table 1. Mapping of GSM RP-ERROR Cause to R-Cause for26Mobile Station Response to Mobile Terminated27Transfer Attempt.28GSM RP-ERROR Cause TIA/EIA-136 R-Cau

46、seMemory capacity exceeded (22) Memory capacity exceeded (22)Invalid short message transfer referencevalue (81)Invalid short message transfer referencevalue (81)Semantically incorrect message(95) Invalid message, unspecified (95)Invalid mandatory information (96) Mandatory information element error

47、(96)Message type nonexistent or notimplemented (97)Message type non-existent or notimplemented (97)Message not compatible with short messageprotocol state (98)Message not compatible with the shortmessage transfer state (101)Information element nonexistent or notimplemented (99)Information element no

48、n-existent or notimplemented (99)Protocol error, unspecified (111) Protocol error, unspecified (111)Interworking, unspecified (127) Interworking, unspecified (127)29ANSI/TIA/EIA-136-71176.2 Mobile Originated Short Messaging1Acknowledgements23At the BMI, the TIA/EIA-41 SMS_CauseCodes are mapped to TI

49、A/EIA-136 R-DATA4REJECT R-Cause codes. The mobile station in turn maps those R-Cause codes to GSM5RP-ERROR Causes according to Table 2.67Table 2. Mapping of TIA/EIA-136 R-Cause Code to RP-8ERROR Cause within the Mobile Station.9TIA/EIA-136 R-Cause RP-ERROR CauseDestination out of service (27) Destination out of service (27)Unidentified subscriber (28) Unidentified subscriber (28)Facility rejected (29) Facility rejected (29)Unknown subscriber (30) Unknown subscriber (30)Network out of order (38) Network out of order (38)Congestion (42) Congestion (42)Requested faci