1、 ANSI/TIA/EIA-136-910-C-2002 APPROVED: APRIL 15, 2002 APPROVED: SEPTEMBER 17, 2013 WITHDRAWN: JUNE 12, 2015 TIA/EIA-136-910-C (Revision of TIA/EIA-136-910-B) April 2002TDMA Third Generation Wireless- Informative Information NOTICE TIA Engineering Standards and Publications are designed to serve the
2、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 product for their particular need. The existence of such Stand
3、ards 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 preclude their voluntary use by Non-TIA members, either dom
4、estically 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 assume any obligation whatever to parties adopting the Sta
5、ndard 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 health practices and to determine the applicability of regu
6、latory limitations 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.910-C-WD, formulated under the cognizance of the TIA TR-4
7、5 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 changed in the standards development or any editing process. The use or practice of contents of this Document
8、 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 IPR consisting of patents and published pending patent applications are claimed and called to TIAs attent
9、ion, 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 scope or validity of any claims of IPR. TIA will neither be a party to discussions of any licensing term
10、s 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 warrant or represent that procedures or practices suggested or provided in the Manual have been complied with
11、 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, development or publication of standards (whether designated as a standard, specification, recommendation or o
12、therwise), whether 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 a
13、ny such Normative 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 publicat
14、ions 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 certify, inspect, test or otherwise investigate products, designs or
15、 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 APPROPRIATENESS FOR A PARTICULAR PURPOSE OR USE, ITS MERCHANTABILI
16、TY 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 COMPLIANCE WITH ANY APPLICABLE STATUTE, RULE OR REGULATION, OR THE SAFE
17、TY 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 RELATING TO ANY USE OF THE CONTENTS CONTAINED HEREIN, INCLUDING WITHOUT
18、 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 (INCLUDING NEGLIGENCE), PRODUCT LIABILITY OR OTHERWISE, EVEN IF ADVISED O
19、F 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. TIA/EIA-136-910-C-2013 iContents 1. Example of a SMS-CMT Message Delivery (Informative)1 1.1 Sco
20、pe .1 1.2 A 63 Octet Character Message Delivery .1 2. Frame Formats (Informative) 3 2.1 List of F-BCCH Frames 3 2.2 List of E-BCCH Frames 4 2.3 List of SPACH Frames5 2.4 List of Normal Length RACH Frames 7 2.5 List of Abbreviated Length RACH Frames.15 3. Calculation of R-DATA Message Length (Informa
21、tive).22 3.1 Introduction .22 3.2 Calculation Procedure For R-DATA Message Length on TIA/EIA-41 22 3.2.1 X.25 Link 22 3.2.2 SS7 Link23 3.2.2.1 Calculation of the Maximum Size of SMS_Bearer Data in SMDPP . 23 3.2.2.2 Calculation of TIA/EIA-136 R-DATA Unit: Higher Layer Protocol Data Unit 30 3.2.2.3 C
22、alculation of R-DATA Message Length . 30 3.3 Calculation of User Data Unit (Payload) for Teleservice Messages .31 3.3.1 Limitations on User Data Unit of SMS Teleservice Messages .31 3.3.2 Limitations on OATS Teleservice Messages 33 4. Addressing for Mobile Originated and Terminated R-DATA (Informati
23、ve).39 4.1 Mobile Originated R-DATA .39 4.1.1 Mobile-Originated R-DATA Addressing Relationships .39 4.1.2 Teleservice Server Address in Mobile-Originated R-DATA Messages40 4.1.2.1 Special Case: Teleservice Server Address in OATS. 41 4.1.3 Mapping of R-DATA to SMDPP for Mobile-Originated R-DATA Messa
24、ges.42 4.2 Mobile Terminated R-DATA 44 4.2.1 Mobile-Terminated R-DATA Addressing Relationships44 4.2.2 Teleservice Server Address in Mobile-Terminated R-DATA Messages 45 4.2.3 Mapping of R-DATA to SMDPP for Mobile-Terminated R-DATA Messages46 5. Implementation Aspects of R-DATA Encryption in TIA/EIA
25、-13648 5.1 Statement of Problem 48 5.2 Proposed Solution48 6. + Code Dialing 49 6.1 Introduction .49 6.2 Suggested Implementation, Mobile Originated .49 6.3 Suggested Implementation, Mobile Terminated50 TIA/EIA-136-910-C-2013 ii 7. Other Useful Documents51 8. Change History for TIA/EIA-136-910 53 TI
26、A/EIA-136-910-C-2013 iiiTables Table 1 Example of a SMS DELIVER Message Format .1 Table 2 Example of a R-DATA Message Format 2 Table 3 Field Breakdown for the TIA/EIA-41 (SS7) SMDPP .27 Table 4 Mapping of TIA/EIA-41 and TIA/EIA-136 Messages28 Table 5 Maximum and Minimum Lengths of SMS DELIVER and SM
27、S SUBMIT Messages29 Table 6 Maximum and Minimum R-DATA Message Length.31 Table 7 Maximum and Minimum Length of User Data Unit (Payload) of SMS Teleservices Messages32 Table 8 Configuration Data Response Information Elements Sizes.34 Table 9 SMDPP Parameter Sizes for OATS Download Request.36 Table 10
28、 Download Request Information Elements Sizes .36 TIA/EIA-136-910-C-2013 iv Figures Figure 1 TIA/EIA-41 to TIA/EIA-136 Map for SMS DELIVER Message.24 Figure 2 TIA/EIA-136 to TIA/EIA-41 Map for SMS SUBMIT Message.25 Figure 3 Mapping of Mobile-Originated OATS Message to TIA/EIA-41 SMDPP.35 Figure 4 Map
29、ping of Mobile-Terminated OATS Message to TIA/EIA-136 R-DATA .38 Figure 5 Mobile Originated R-DATA Addressing Relationships39 Figure 6 Teleservice Server Address in Mobile-Originated R-DATA Messages 40 Figure 7 Teleservice Server Address in OATS 42 Figure 8 Mobile Originated R-DATA43 Figure 9 Mobile
30、 Terminated R-DATA Addressing Relationships.44 Figure 10 Mobile-Terminated R-DATA 46 TIA/EIA-136-910-C-2013 11. Example of a SMS-CMT Message Delivery 1 (Informative) 2 1.1 Scope 3 This chapter is provided for information only. It provides an brief example of a MS 4 Terminated SMS, without mobile sta
31、tion user acknowledgment. 5 1.2 A 63 Octet Character Message Delivery 6 Consider the following text message to be sent to the mobile station: 7 “Votre rendez-vous de cet apres-midi est cancelle! Salut, Eric“ 8 This message is 63 character long. The SMS-CMT teleservice layer SMS DELIVER 9 message sen
32、t by the Message Center will be as follows: 10 Table 1 Example of a SMS DELIVER Message Format 11 Information Element Type Length (bits) Description Message Type Indicator M 3 Message Reference M 13 Privacy Indicator M 3 Urgency Indicator M 2 Delivery Acknowledgment Request M 1 Manual Acknowledgment
33、 Request M 1 Message Updating M 1 Validity M 3 Display Time M 2 Reserved M 3 User Data Unit M 520 Text message Originating Address Presentation Indicator O 0 Not present Message Center Time Stamp O 0 Not present SMS Signal O 0 Not present (Padding) M 0 To make message length an exact number of octet
34、s Total = 552 TIA/EIA-136-910-C-2013 2 The SMS DELIVER is then encapsulated in a layer 3 message at the Message Center and 1 sent to the BMI. The BMI receives the layer 3 message from the Message Center, and 2 will format a layer 3 R-DATA message to be delivered to the mobile station. The 3 R-DATA m
35、essage is: 4 Table 2 Example of a R-DATA Message Format 5 Information Element Type Length (bits) Description Protocol Discriminator M 2 Message Type M 6 R-Transaction Identifier M 8 R-DATA Unit M 568 SMS DELIVER encapsulated within this IE Message Center Originating Address O 0 Assumed to be not pre
36、sent User Destination Address O 0 Not used in message delivery by this teleservice User Destination Subaddress O 0 Not used in message delivery by this teleservice User Originating Address O 52 Assumed to be 7 digit number, coded TBCD User Originating Subaddress O 0 Not present Total = 636 Therefore
37、 a 636-bit layer 3 message will be transmitted to the mobile station over the air 6 interface. 7 If we assume that the MS has received and accepted the R-DATA message, the mobile 8 station will then return a layer 3 R-DATA ACCEPT message to the BMI. This message 9 is 2 octets long (1 for layer 3 Pro
38、tocol Discriminator and Message Type, and 1 for 10 R-Transaction Identifier). This layer 3 acknowledgment will be used by the BMI to 11 provide an SMS (transport layer) acknowledgment to the Message Center, confirming 12 delivery to the mobile terminal. 13 TIA/EIA-136-910-C-2013 32. Frame Formats (I
39、nformative) 1 2.1 List of F-BCCH Frames 2 Field 1Field 2Field 3Field 4Field 5Field 6Field 7Field 8Field9Field 10Field 11Field 12Field 13Field 14Field 15Field 16Field 17Begin frame(Onecompletemessage)BC(BC=0)FCECL3LIL3DATAB1(B1=0)FILLERCRCBegin frame(Complete orcontinuingmessage)BC(BC=0)FCECL3LIL3DAT
40、ACRCBegin frame(more thanone message)BC(BC=0)FCECL3LIL3DATAB1(B1=1)L3LI. . .N:thL3DATABI(B1=0)FILLERCRCBegin frame(more thanone message)BC(BC=0)FCECL3LIL3DATAB1(B1=1)L3LI. . .N:thL3DATACRCContinueframe(Messageending)BC(BC=1)FCECCLIL3DATAB1(B1=0)FILLERCRCContinueframe(Messageending orcontinuing)BC(BC
41、=1)FCECCLIL3DATACRCContinueframe(Messageending)BC(BC=1)FCECCLIL3DATABI (B1=1)L3LI. . .N:thL3DATAB1(B1=0)FILLERCRCContinueframe(Messageending orcontinuing)BC(BC=1)FCECCLIL3DATAB1(B1=1)L3LI. . .N:thL3DATACRCTIA/EIA-136-910-C-2013 4 2.2 List of E-BCCH Frames 1 Field 1Field 2Field 3Field 4Field 5Field 6
42、Field 7Field 8Field 9Field 10Field 11Field 12Field 13Field 14Field 15Field 16Field 17Begin frame(Onecompletemessage)BC(BC=0)ECLL3LIL3DATAB1(B1=0)FILLERCRCBegin frame(Complete orcontinuingmessage)BC(BC=0)ECLL3LIL3DATACRCBegin frame(more thanone message)BC(BC=0)ECLL3LIL3DATAB1(B1=1)2:nd L3LI. . .N:thL
43、3DATABI(BI=0)FILLERCRCBegin frame(more thanone message)BC(BC=0)ECLL3LIL3DATAB1(B1=1)2:nd L3LI. . .N:thL3DATACRCContinueframe(Messageending)BC(BC=1)RSVDCLIL3DATAB1(B1=0)FILLERCRCContinueframe(Messageending orcontinuing)BC(BC=1)RSVDCLIL3DATACRCContinueframe(Messageending)BC(BC=1)RSVDCLIL3DATABI (B1=1)
44、L3LI. . .N:thL3DATABI(BI=0)FILLERCRCContinueframe(Messageending orcontinuing)BC(BC=1)RSVDCLIL3DATAB1(B1=1)L3LI. . .N:thL3DATACRCTIA/EIA-136-910-C-2013 52.3 List of SPACH Frames 1 Field1Field2Field3Field4Field5Field6Field7Field8Field9Field10Field11Field12Field13Field14Field15Field16Field17Null FrameH
45、eaderA(BU=000)GAFILLERCRCHardDoubleIMSIPageHeaderA(BU=010)MSID(50bits)MSID (50bits)FILLERCRCHardTriplePageframeHeaderA(BU=101)MSID(34bits)MSID (34bits)MSID(34bits)CRCHardQuadruplePageframeHeaderA(BU=110)IDTMSID(20 or24bits)MSID(20or24bits)MSID(20 or24bits)FILLERCRCHardPenta PageframeHeaderA(BU=001)M
46、SID(20bits)MSID(20 bits)MSID(20bits)MSID(20bits)MSID(20 bits)FILLERCRCSingleMSIDframeHeaderA(BU=011,100 or111)HeaderB(BT=000)EHI(EHI=0)MSID(20,24,34or50bits)L3LIL3DATAFILLERCRCSingleMSIDframeHeaderA(BU=011,100or111)HeaderB(BT=000)EHI(EHI=1)ExtensionHeaderMSID(20,24,34or50bits)L3LIL3DATAFILLERCRCDoub
47、leMSIDframeHeaderA(BU=011 or111)HeaderB(BT=001,MM=0)EHI(EHI=0)MSID(20,24or34bits)MSID(20,24or34bits)L3LIL3LIL3DATAL3DATAFILLERCRCDoubleMSIDframe withcontinuationHeaderA(BU=011 or111)HeaderB(BT=001,MM=1)EHI(EHI=0)MSID(20,24or34bits)MSID(20,24or34bits)L3LIL3DATACRCDoubleMSIDframeHeaderA(BU=011 or111)H
48、eaderB(BT=001,MM=0)EHI(EHI=1)ExtensionHeaderMSID(20,24or34bits)MSID(20,24or34bits)L3LIL3LIL3DATAL3DATAFILLERCRCDoubleMSIDframe withcontinuationHeaderA(BU=011 or111)HeaderB(BT=001,MM=1)EHI(EHI=1)ExtensionHeaderMSID(20,24or34bits)MSID(20,24or34bits)L3LIL3DATACRCTripleMSIDframewithoutcontinuationHeader
49、A(BU=011 or111)HeaderB(BT=010,MM=1)EHI(EHI=0)MSID(20or24bits)MSID(20 or24bits)MSID(20 or24bits)L3LIL3DATAFILLERCRCTripleMSIDframewithoutcontinuationHeaderA(BU=011 or111)HeaderB(BT=010,MM=1)EHI(EHI=1)ExtensionHeaderMSID(20 or24bits)MSID(20 bits)MSID(20or24bits)L3LIL3DATAFILLERCRCTripleMSIDframewithcontinuationHeaderA(BU=011 or111)HeaderB(BT=010,MM=0)EHI (EHI=0)MSID(20bits)MSID (20bits)MSID(20bits)L3LI (8bits)L3LIL3LIL3DATACRCTripleMSIDframewithcontinuationHeaderA(BU=011 or111)HeaderB(BT=010,MM=0)EHI(EHI=1)ExtensionHeaderMSID(20 bits)MSID(20 bits)MSID(20bits)L3LIL3LIL3LI(8bits)CRCTr
