1、 ANSI/TIA-136-610-B-2002 APPROVED: APRIL 15, 2002 APPROVED: SEPTEMBER 18, 2013 WITHDRAWN: JUNE 12, 2015 TIA-136-610-B (Revision of TIA-136-610-A) April 2002TDMA Third Generation Wireless- R-Data/SMDPP Transport NOTICE TIA Engineering Standards and Publications are designed to serve the public intere
2、st 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 product for their particular need. The existence of such Standards and Publ
3、ications 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
4、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 assume any obligation whatever to parties adopting the Standard or Publ
5、ication. 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 limita
6、tions before its use. 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.610-B-WD, formulated under the cognizance of the TIA TR-45 Mobile (b)
7、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 changed in the standards development or any editing process. The use or practice of contents of this Document may involve
8、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 IPR consisting of patents and published pending patent applications are claimed and called to TIAs attention, a statem
9、ent 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 scope or validity of any claims of IPR. TIA will neither be a party to discussions of any licensing terms or conditio
10、ns, 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 warrant or represent that procedures or practices suggested or provided in the Manual have been complied with as respects
11、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, development or publication of standards (whether designated as a standard, specification, recommendation or otherwise), wh
12、ether such reference consists 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 Norma
13、tive Reference; (ii) TIAs 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 o
14、ther 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 certify, inspect, test or otherwise investigate products, designs or services or
15、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 APPROPRIATENESS FOR A PARTICULAR PURPOSE OR USE, ITS MERCHANTABILITY AND ITS NO
16、NINFRINGEMENT 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 COMPLIANCE WITH ANY APPLICABLE STATUTE, RULE OR REGULATION, OR THE SAFETY OR HEALTH
17、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 RELATING TO ANY USE OF THE CONTENTS CONTAINED HEREIN, INCLUDING WITHOUT LIMITATION A
18、NY 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 (INCLUDING NEGLIGENCE), PRODUCT LIABILITY OR OTHERWISE, EVEN IF ADVISED OF THE POSSIBI
19、LITY 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. TIA/EIA-136-610-B-2013 iContents 1 1. Introduction 1 2 2. Mapping of R-DATA and SMDPP Messages 3 3 3. R-DATA/
20、SMDPP Transport 6 4 3.1 Teleservice Segmentation and Reassembly 6 5 3.2 Broadcast Air-Interface Teleservice Transport (BATS). 6 6 4. R-DATA/SMDPP Transport in Teleservices. 7 7 4.1 Cellular Messaging Teleservices 7 8 4.1.1 Example Message flow for SMS delivery 7 9 4.2 Over-the-Air Activation Teleser
21、vice (OATS) 9 10 4.3 Over-the-Air Programming Teleservice (OPTS). 9 11 4.4 General UDP Transport Service (GUTS). 10 12 4.5 Charge Indication Teleservice (CIT) 10 13 4.6 GSM Hosted SMS Teleservice (GHOST). 10 14 4.7 System Assisted Mobile Positioning through Satellite (SAMPS) . 10 15 5. Change Histor
22、y for TIA/EIA-136-610. 12 16 TIA/EIA-136-610-B-2013 ii Figures 1 Figure 1 Network model for a teleservice. 1 2 Figure 2 Teleservice Protocol Stack . 2 3 Figure 3 TIA/EIA-41 to TIA/EIA-136 Map for SMS DELIVER Message 4 4 Figure 4 TIA/EIA-136 to TIA/EIA-41 Map for SMS SUBMIT Message 5 5 Figure 5 Examp
23、le Message flow for SMS delivery8 6 Figure 6 Network model for Over-the-air Activation Teleservice 9 7 TIA/EIA-136-610-B-2013 11. Introduction 1 R-DATA and SMDPP (Short Message Delivery Point-to-Point) are the messages that 2 are used for information transfer through the TIA/EIA-136 air interface an
24、d the 3 TIA/EIA-41 network interface. The purpose of this chapter is to demonstrate the 4 transport of R-DATA messages through the TIA/EIA-41 SMDPP and vice versa. Figure 5 1 illustrates the network model for information transfer between the air and network 6 interfaces. 7 8 9 Figure 1 Network model
25、 for a teleservice 10 TeleserviceserverHLR/ACMSC/VLRBSTIA/EIA-136R-DATATIA/EIA-41SMDPP TIA/EIA-41TIA/EIA-41MS11 12 The mechanism for information transfer between a source and a destination through the 13 BMI is called a teleservice. The source maybe a mobile station or a Teleservice Server 14 (TS).
26、A teleservice is delivered across the TIA/EIA-136 air interface on a DCCH or DTC 15 inside a layer 3 R-DATA message, and across the TIA/EIA-41 network interface inside a 16 layer 3 Short Message Delivery Point-to-Point (SMDPP) Invoke message. The delivery 17 of the layer 3 message may be acknowledge
27、d by the destination in a TIA/EIA-136 18 R-DATA ACCEPT or R-DATA REJECT message and a TIA/EIA-41 SMDPP Return 19 (smdpp) Result message. The BMI provides the interworking between the Teleservice 20 Server and the mobile station by translating between the TIA/EIA-136 and TIA/EIA-41 21 protocols. 22 2
28、3 A teleservice may be delivered in point-to-point mode or broadcast mode. It may be text 24 based, such as Cellular Messaging Teleservice (CMT), or it may be coded information 25 destined for the mobile stations storage and use, such as Over-the-Air Activation 26 Teleservice (OATS) and Over-the-Air
29、 Programming Teleservice (OPTS). The teleservice 27 protocol stack is as shown in Figure 2. 28 TIA/EIA-136-610-B-2013 2 Figure 2 Teleservice Protocol Stack 1 2 (conditional)*TeleserviceTSARTIA/EIA-136 Air Interface*R-DATAPt-Pt orBroadcastChannelTeleserviceTSARMS BMI TS*: beyond the scope of this doc
30、ument*IWFR-DATAPt-Pt orBroadcastChannelTIA/EIA-136-610-B-2013 32. Mapping of R-DATA and SMDPP 1 Messages 2 3 The R-DATA message is used to carry point-to-point teleservice layer messages on the 4 SMSCH (e.g., SMS CMT, see TIA/EIA-136-710 or OATS, see TIA/EIA-136-720) or 5 point-to-multipoint teleser
31、vice layer messages on the S-BCCH (see TIA/EIA-136-630). 6 See Section 5.3.11 of TIA/EIA-136-123A for detailed format of the R-DATA message. 7 8 Figures 3 and 4 show the TIA/EIA-41 (MAP-layer) to TIA/EIA-136 mapping of SMDPP 9 INVOKE containing SMS Deliver and SMS submit teleservice-layer message fo
32、r 10 Cellular Message Teleservices. From the figures it can be seen that there is a one-to-one 11 mapping of many of the SMDPP parameters and the elements in the R-DATA message. 12 The SMS_Teleservice ID and the SMS_Bearer Data of the SMDPP Invoke message are 13 mapped to the Higher Layer Protocol I
33、D and the HLPDU of the R-Data Unit information 14 element within the R-Data message. 15 16 TIA/EIA-136-610-B-2013 4 Figure 3 TIA/EIA-41 to TIA/EIA-136 Map for SMS DELIVER Message 1 SMS_OriginalDestinationAddress(of SME)OSMS_OriginalDestinationSubaddress(of SME)OSMS_OriginalOriginatingAddress(of SME)
34、OSMS_OriginalOriginatingSubaddress(of SME)OSMS_ChargeIndicatorOSMS_TeleserviceIDMSMS_BearerData MESNMINSMS_DestinationAddressSMS_OriginatingAddressSMS_MessageCountSMS_NotificationIndicatorOOOOOONote: SS7 MSU SIF containinga TCAP message islimited to 272 octetsProtocolDiscriminator(2 bits)MMessage Ty
35、pe(R-DATA)(6 bits)MR-TransactionID(8 bits)MR-Data Unit(16 - * bits)MTeleserviceServer Address(20 bits)OUser DestinationAddress(20 - * bits)OUser DestinationSubaddress(20 - 180 bits)OUser OriginatingAddress(20 - * bits)User OriginatingSubaddress(20 - 180 bits)User OriginatingAddressPresentationIndica
36、tor(8 bits)OOONote: R-DATA is limitedto 255 octetsLength(8 bits)MHigher LayerProtocol ID(Pt. to Pt. SMS)(8 bits)MHigher Layer PDU(8 * (N-1) bitsMMessage Type(SMS Deliver)(3 bits)MMessageReference(13 bits)MPrivacy Indicator(3 bits)MUgency Indicator(2 bits)MDelivery AckRequest(1 bit)MManual AckRequest
37、(1 bit)MMessageUpdate(1 bit)MValidity(3 bits)Display Time(2 bits)User DataUnit(16 - * bits)MC TimeStamp(48 bits)SMS Signal(16 bits)Call BackNumber(20 - * bits)MMMOOOCall Back NumberPresent, Indicator(8 bits)CBN Alpha Tag(20 - * bits)OOTIA/EIA-41SMDPPINVOKE R-DATAR-Data UnitSMS DeliverTIA/EIA-136TIA/
38、EIA-136-610-B-2013 5Figure 4 TIA/EIA-136 to TIA/EIA-41 Map for SMS SUBMIT Message 1 Message Type(3 bits)MMessageReference(13 bits)MPrivacy Indicator(3 bits)MUgency Indicator(2 bits)MDelivery AckRequest(1 bit)MManual AckRequest(1 bit)MMessageUpdating(1 bit)MUser Data Unit(16 - * bits)ValidityPeriod(1
39、3 or 49 bits)Def Del Times(13 or 49 bits)Call Back Number(20 - * bits)CB Pres Ind(8 bits)CB Alpha Tag(20 - * bits)MOOOOOSMS SubmitLength(8 bits)MHLPI(8 bits)MHigher Layer PDU(8 * (N-1) bitsMR-Data UnitProtocolDiscriminator(2 bits)MMessage Type(6 bits)MR-TransactionID(8 bits)MR-Data Unit(16 - * bits)
40、MTeleserviceServer Address(20 - * bits)OUser DestinationAddress(20 - * bits)OUser DestinationSubaddress(20 - 180 bits)OUser OriginatingAddress(20 - * bits)User OriginatingSubaddress(20 - 180 bits)User OriginatingAPI(8 bits)OOOR-DATASMS_BearerDataMSMS_TID MESN OMIN OSMS_ChargeIndicatorOSMS_Destinatio
41、nAddressOSMS_MessageCountOSMS_NotificationIndicatorSMS_OrigDestinationAddressSMS_OrigDestinationSubaddressSMS_OrigOriginationAddressSMS_OrigOriginatingSubaddressSMS_OriginatingAddressOOOOOOTIA/EIA-41SMDPPTIA/EIA-1362 3 4 TIA/EIA-136-610-B-2013 6 3. R-DATA/SMDPP Transport 1 2 This section deals with
42、the mechanisms to support the transport of teleservice messages. 3 4 5 3.1 Teleservice Segmentation and Reassembly 6 7 The R-DATA message size is limited by the SS7 limitations on the TIA-EIA-41 8 SMS_Bearer data parameter and the number of optional parameters used in the SMDPP 9 message. Teleservic
43、e Segmentation and Reassembly (TSAR) provides a mechanism to 10 deliver TIA/EIA-136 Teleservice Messages (e.g., as defined in CMT or OATS) that are 11 not constrained by any message length limitations imposed by the air interface or 12 network layers supporting the teleservice. The service consists
44、of the application of 13 segmentation the acknowledgment of correct receipt of segments 20 is either via the R-DATA ACCEPT or an explicit TSAR Response message. See 21 TIA/EIA-136-620 for further details regarding TSAR. 22 23 24 3.2 Broadcast Air-Interface Teleservice Transport (BATS) 25 26 BATS ope
45、rates between a Teleservice Server (TS) and mobile stations using both 27 TIA/EIA-136 and TIA/EIA-41 based protocol stacks along with a BMI based relay 28 function. BATS is a general-purpose broadcast transport mechanism that can be used by 29 existing teleservices (e.g., CMT, OPTS, GUTS, and carrie
46、r-specific teleservices) as well 30 as other future teleservices/applications requiring broadcast transport support. The 31 broadcast teleservice is encapsulated by the SMDPP and R-DATA messages and 32 delivered on the DCCH. See TIA/EIA-136-630 for further details regarding BATS. 33 34 35 TIA/EIA-13
47、6-610-B-2013 74. R-DATA/SMDPP Transport in Teleservices 1 2 This section deals with the teleservices where the critical message transfer is via the R-3 DATA and SMDPP messages. 4 5 4.1 Cellular Messaging Teleservices 6 7 The Higher Layer Protocol Data Unit field in the R-DATA Unit information elemen
48、t is 8 used to carry the Short Message Service (SMS) Cellular Messaging Teleservice (CMT) 9 messages when the Higher Layer Protocol Identifier indicates Point-to-Point SMS. 10 11 12 4.1.1 Example Message flow for SMS delivery 13 An example message flow for Mobile-Terminated and Mobile-Originated SMS
49、 is 14 illustrated in Figure 5. The short message text from MS1 is encapsulated into the user 15 data unit of the SMS SUBMIT message. The SMS SUBMIT message is delivered to the 16 cellular network in an R-DATA message on either the DCCH or the DTC. The R-DATA 17 message is translated into an SMDPP message by the BMI of MS1 and delivered to the 18 teleservice server of MS1. The teleservice server of MS1 sends an acknowledgement in 19 the form of an smdpp message to the BMI. The BMI in turn sends out an R-DATA 20 ACCEPT message to the mobile to indicate that the message ha
