1、 TIA STANDARD Forward Link Only Transport Specification TIA-1120 July 2007 TELECOMMUNICATIONS INDUSTRY ASSOCIATION Representing the telecommunications industry in association with the Electronic Industries Alliance NOTICE TIA Engineering Standards and Publications are designed to serve the public in
2、terest 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
3、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 domestically
4、 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 Standard or
5、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 regulatory li
6、mitations before its use. (From Project No. 3-0270 formulated under the cognizance of the TIA TR-47 Committee on Terrestrial Mobile Multimedia Multicast. TR-47.1 Subcommittee on Terrestrial Mobile Multimedia Multicast based on Forward Link Only Technology, Active Components and Reliability). Publish
7、ed by TELECOMMUNICATIONS INDUSTRY ASSOCIATION Standards and Technology Department 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 Information Handling Services USA an
8、d Canada (1-800-525-7052) International (303-790-0600) or search online at http:/www.tiaonline.org/standards/catalog/ All rights reserved Printed in U.S.A. NOTICE OF COPYRIGHT This document is copyrighted by the TIA. Reproduction of these documents either in hard copy or soft copy (including posting
9、 on the web) is prohibited without copyright permission. For copyright permission to reproduce portions of this 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/sta
10、ndards/catalog/info.cfm#copyright OR Telecommunications Industry Association Standards (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 develo
11、pment 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 IPR consisting of patents a
12、nd 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 scope or validity of any c
13、laims 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 warrant or represent that proce
14、dures 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, development or publication of s
15、tandards (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 search or investigate the reco
16、rds 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 (iii) Information as to cl
17、aims 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 certify, inspect, test or othe
18、rwise 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 APPROPRIATENESS FOR A PARTIC
19、ULAR 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 COMPLIANCE WITH ANY APPLICABLE ST
20、ATUTE, 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 RELATING TO ANY USE OF THE CONTEN
21、TS 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 (INCLUDING NEGLIGENCE), PRODUCT LIA
22、BILITY 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. TIA-1120 Forward Link Only Transport Specification i Table
23、 of Contents 1 Introduction and Scope 2 2 Apparatus .3 2.1 Compliance Terminology 3 2.2 Symbols and Abbreviations.3 2.3 Message Description Rules 3 2.4 Definitions6 2.5 Normative References 7 3 Transport Layer Overview8 3.1 Introduction8 3.2 Reference Model.8 3.3 Transport Layer Protocol Architectur
24、e 8 4 Stream Encryption/Decryption Layer .12 4.1 Introduction12 4.2 Stream Encryption and Decryption .12 4.3 Initial Counter Value in AES CTR Flow Cipher.12 5 Framing Layer 15 5.1 Introduction15 5.2 Framing Protocol.16 5.3 Flow Configuration Options.19 6 Stream 0 Messages .20 Forward Link Only Trans
25、port Specification TIA-1120 ii No text Forward Link Only Transport Specification TIA-1120 iii Table of Figures Figure 1: Transport Layer Reference Architecture 8 Figure 2: Transport Layer Protocol Architecture 9 Figure 3: Mapping of Flows to MLC and Streams . 10 Figure 4: Working of the Framing Laye
26、r 15 Forward Link Only Transport Specification TIA-1120 iv No text Forward Link Only Transport Specification TIA-1120 v Table of Tables Table 1: Example Message Specification 4 Table 2: Bit and Byte Order of UINT(32) Values .5 Table 3: Example Complex Field Type 5 Table 4: Bit and Byte Order of Comp
27、lex Field Type Example. 5 Table 5: Initial Counter Value for AES CTR Flow Cipher 14 Table 6: Fragment Header Format 18 Table 7: Assigment of FlowBLOB Bits for Flow Configuration Options. 19 Table 8: Format of Stream 0 Messages 20 Forward Link Only Transport Specification TIA-1120 vi No text TIA-1120
28、 Forward Link Only Transport Specification 1 FOREWORD 1 (This foreword is not part of this Standard.) 2 This draft Standard is intended for use in TM3 networks using TIA 1099 4. This draft Standard 3 makes use of certain standards and recommendations defined by TIA and other bodies as listed in 4 su
29、bclause 2.5. 5 6 Forward Link Only Transport Specification TIA-1120 2 1 INTRODUCTION AND SCOPE 1 This Standard specifies the Transport Layer for TM3 systems using TIA 1099 4. The Standard 2 specifies the framing formats and procedures for delivering application service packets securely over 3 the ai
30、r interface specified in TIA 1099. 4 This Standard is organized into the following clauses: 5 Clause 1: An informative clause describing the scope and the organization of the Standard. 6 Clause 2: A normative clause defining compliance terminology, acronyms, definitions of terms, 7 conventions for s
31、pecifying data types, and references. 8 Clause 3: An informative clause providing an overview of the services provided by the Transport 9 Layer, the reference model assumed by the Transport Layer, and an overview of the protocol 10 hierarchy specified in this Standard. 11 Clause 4: A normative claus
32、e defining the encryption procedures optionally associated with Streams 12 specified in TIA 1099. 13 Clause 5: A normative clause defining the framing and CRC procedures for transport of application 14 service packets over Streams in Multicast Logical Channels specified in TIA 1099. 15 Clause 6: A n
33、ormative clause defining the transport and message structures of control messages 16 transported in Stream 0 of Multicast Logical Channels. 17 TIA-1120 Forward Link Only Transport Specification 3 2 APPARATUS 1 2.1 Compliance Terminology 2 The key words “shall”, “shall not”, “should”, “should not”, “
34、may”, “need not”, “can” and “cannot”, when 3 used in this Standard, are to be interpreted as specified in Annex C of the TIA Style Manual 3. 4 2.2 Symbols and Abbreviations 5 The following symbols and abbreviations are used in this Standard: 6 AES: Advanced Encryption Standard 7 ANSI: American Natio
35、nal Standard Institute 8 CAS: Conditional Access System 9 CRC: Cyclic Redundancy Check 10 CTR: CounTeR 11 ECM: Entitlement Control Message 12 FASB: Fragmentation Across Superframe Boundaries 13 FH: Fragment Header 14 FIPS: Federal Information Processing Standard 15 LSB: Least Significant Bit 16 MAC:
36、 Media Access Control 17 MLC: Multicast Logical Channel 18 MSB: Most Significant Bit 19 TIA: Telecommunications Industry Association 20 TM3: Terrestrial Mobile Multicast Multimedia 21 UINT: Unsigned INTeger 22 2.3 Message Description Rules 23 The formats of messages transported in Stream 0 are speci
37、fied as binary structures. The 24 conventions for specifying binary structures are specified in subclause 2.3.1. 25 2.3.1 Binary Message Specifications 26 This subclause specifies the atomic data types used in this Standard and describes the general 27 message guidelines and ordering rules. 28 Forwa
38、rd Link Only Transport Specification TIA-1120 4 2.3.1.1 Message Specification Tables 1 A message is an ordered collection of fields. Messages are specified in tables. An example is shown 2 in Table 1. 3 Table 1: Example Message Specification 4 Field Name Field Type Field Presence Subclause Reference
39、FIELD_A UINT(8) MANDATORY Field A subclause FIELD_B BIT(1) MANDATORY Field B subclause FIELD_C FIELD_C_TYPE CONDITIONAL Field C subclause 5 In the above example, the message has three fields, FIELD_A, FIELD_B and FIELD_C. The second 6 column in the table defines the type of the field. For example, F
40、IELD_A is an unsigned 8-bit integer 7 (UINT(8) and FIELD_B is a bit field of size 1 bit. UINT(8) and BIT(N) are basic types. The list of basic 8 types is defined in subclause 2.3.1.3. 9 FIELD_C is of type FIELD_C_TYPE. FIELD_C_TYPE is a composite data type which is defined 10 elsewhere by a similar
41、table specifying its sub-fields. 11 The third column of the table specifies the rules for the presence of a field. Fields can be 12 MANDATORY, CONDITIONAL or OPTIONAL. 13 The fourth column of the table identifies the subclause of this Standard where the field is specified. 14 2.3.1.2 Field Presence
42、Classes 15 The possible Field Presence classes are specified in the following subclauses. 16 2.3.1.2.1 MANDATORY field 17 A MANDATORY field shall occur in every instance of the message. 18 2.3.1.2.2 CONDITIONAL field 19 The presence of a CONDITIONAL field is conditioned on the value of another field
43、. The conditions 20 under which the field is present are specified in the subclause where the field is described. 21 2.3.1.2.3 OPTIONAL field 22 An OPTIONAL field may occur in an instance of the message, according to the requirements of the 23 message source. 24 2.3.1.3 Basic Data Types 25 The follo
44、wing basic data types are used in this Standard. 26 2.3.1.3.1 UINT(n) 27 This is an n-bit unsigned integer. The possible range of values is 0 to 2n 1. A field of this type may 28 be restricted to a subset of these values. 29 2.3.1.3.2 BIT(n) 30 This is an n-bit pattern type. 31 TIA-1120 Forward Link
45、 Only Transport Specification 5 2.3.1.3.3 INT(n) 1 This is an n-bit signed integer. Twos complement representation is used. The possible range of 2 values is -2(n-1)to 2(n 1) 1. A field of this type may be further restricted to a subset of this range. 3 2.3.1.4 Ordering Rules 4 In general, message f
46、ields are arranged in “little endian” order. Bits are numbered from 1 to 8 in a 5 byte, where bit 1 is the least significant bit. Bytes are numbered from 1 to N, where byte 1 is the least 6 significant byte of an N-byte quantity. 7 For example, the ordering of the bits and bytes of a field of type U
47、INT(32) is shown in Table 2. The 8 least significant bit of the field is bit 1 of byte 1. The most significant bit is bit 8 of byte 4. 9 Table 2: Bit and Byte Order of UINT(32) Values 10 8 7 6 5 4 3 2 1 LSB 1 2, 3 MSB 4 11 A more complex field type with two sub-fields is shown in Table 3. 12 Table 3
48、: Example Complex Field Type 13 Field Name Field Type Field Presence VALUE UINT(5) MANDATORY INDEX UINT(5) MANDATORY 14 In this example, the bits are arranged as shown in Table 4. The VALUE field is listed in the table 15 before the INDEX field. The bits of the VALUE field appear in the least signif
49、icant bits of byte 1. The 16 least significant bit of INDEX appears at bit 6 of byte 1 and the most significant bit appears in bit 2 of 17 byte 2. 18 Table 4: Bit and Byte Order of Complex Field Type Example 19 8 7 6 5 4 3 2 1 LSB of INDEX MSB of VALUE LSB of VALUE 1 OTHER BITS MSB of INDEX 2 20 2.3.1.5 Byte Alignment 21 All messages shall contain an integer number of bytes. Padding bits shall be added to the last byte at 22 the most significant end, if necessary. 23 Byte alignment of individual fields, if required, is specified on a case-by-case basis. 24 Forw
