1、 ANSI/TIA-136-320-2000 APPROVED: MARCH 31, 2000 REAFFIRMED: OCTOBER 20, 2004 REAFFIRMED: AUGUST 14, 2013 WITHDRAWN: JUNE 12, 2015 TIA-136-320 March 2000TDMA Third Generation Wireless- Radio Link Protocol- 2 NOTICE TIA Engineering Standards and Publications are designed to serve the public interest t
2、hrough 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 Publicat
3、ions 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 inte
4、rnationally. 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 Publicat
5、ion. 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 limitation
6、s 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.320-RF2-WD, formulated under the cognizance of the TIA TR-45 Mobile (b) th
7、ere 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 th
8、e 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 statemen
9、t 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 conditions
10、, 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 th
11、e 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), whet
12、her 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 Normati
13、ve 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 oth
14、er 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 an
15、y 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 NONI
16、NFRINGEMENT 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 EF
17、FECTS 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 ANY
18、 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 POSSIBILI
19、TY 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-320iForeword This foreword is not part of TIA-136-320.This standard specifies a Radio Link Protocol
20、 (RLP2) that layer-3functions may use to isochronously transport data across a TDMA radiointerface. The protocol maintains bit-count integrity by deliveringcumulative nibble counts to layer 3.RLP2 supports a single data link accessed through a single ServiceAccess Point (SAP). Through this SAP, RLP2
21、 provides the followingservices to layer 3: unacknowledged data transport and bit-countsupervision.This standard was developed by TR45.3.2, the Data Services WorkingGroup of TR45.3, the TIA TDMA Wireless Standards Subcommittee. Itcontains a single annex: Annex A contains no requirements: it lists an
22、d defines acro-nyms used within the standard.TIA welcomes suggestions for improvement of this standard. Pleasesend suggestions to the following address:Telecommunications Industry Association2500 Wilson Boulevard Suite 300Arlington VA 22201-3836TIA/EIA-136-320iiSpare pageTIA/EIA-136-320iiiContents1.
23、 Purpose and Scope. 12. Overview . 23. RLP2 Structure 33.1 Blocking 43.2 Transmission Control3.3 Frame Check Sequence (FCS) 43.4 Forward Error Correction (FEC).4. Signals . 54.1 RLP2 Service Data Units 54.2 RLP2 Frames.4.3 RLP2 Protocol Data Units.4.4 Service Primitives . 65. Processes . 95.1 Blocke
24、r (BLK) 95.2 Transmission Controller Transmit (TCT) 115.3 Transmission Controller Receive (TCR) . 125.4 FCS Encoder (FCE) 145.5 FCS Decoder (FCD) . 175.6 Convolutional Encoder (CE). 185.7 Convolutional Decoder (CD) 236. References . 24A. Acronyms 25TIA/EIA-136-320ivFiguresFigure 21 RLP2 Position in
25、Protocol Stack . 2Figure 31 RLP2 Reference Model . 3Figure 41 Service Primitives and Signal Routes . 7Figure 51 Blocker Process . 10Figure 52 Transmission Control Process Transmit. 11Figure 53 Transmission Control Process Receive 13Figure 54 FCS-Encoder Process 14Figure 55 FCS-Decoder Process 17Figu
26、re 56 Convolutional-Encoder Process 18Figure 57 Convolutional-Decoder Process 23TIA/EIA-136-320vRevision HistoryVersion DescriptionIS-684 First release.TIA/EIA-136-320Second release.TIA/EIA-136-320viSpare pageTIA/EIA-136-32011. Purpose and Scope1This standard specifies a Radio Link Protocol (RLP2) t
27、hat layer-32functions may use to isochronously transport data across a TDMA radio3interface. The protocol maintains bit-count integrity by delivering4cumulative nibble counts to layer 3. It requires an underlying half-rate,5full-rate, double-rate, or triple-rate digital traffic channel as specified
28、in6TIA-136-131, 132, and 133 5.7To aid the reader, 2 and 3 contain descriptive information: 2 pro-8vides an overview; 3 describes the protocols structure. 4 and 59contain requirements: 4 specifies RLP2 signals; 5 specifies pro-10cesses. References appear in 6. Finally, Annex A lists and defines11acr
29、onyms.12Readers will find the following documents helpful in understanding this13standard: X.200 3 and Z.100 4.14Similar to X.200, this standard uses reference models to organize con-15cepts and requirements into a logical structure. These reference models16are not meant to unnecessarily constrain i
30、mplementations any RLP217implementation that, as a whole, behaves the same as the RLP2 speci-18fied in this standard, by definition, complies with this standard.19If the requirements of this standard conflict with the requirements of20referenced standards, this standard shall govern.21TIA/EIA-136-32
31、022. Overview1RLP2 isochronously transports data between unspecified layer-3 func-2tions. It resides at the link layer (layer 2), just above the physical layer3(layer 1) and just below the network layer (layer 3). See Figure 21.4Figure 21 RLP2 Position in Protocol Stack5Layer 1Layer 3 Unspecified La
32、yer-3 FunctionRadio Link Protocol 2Digital Traffic ChannelRadio InterfaceLayer 2Unspecified Layer-3 FunctionSAP SAPDigital Traffic ChannelRadio Link Protocol 26RLP2 supports a single data link accessed through a single Service7Access Point (SAP). Through this SAP, RLP2 provides the following8service
33、s to layer 3:9 Unacknowledged data transport. RLP2 provides constant10throughput and delay at the expense of a variable error rate.11 Bit-count supervision. RLP2 tracks the cumulative number of12bits transmitted, and it provides this information to the receiv-13ing layer 3.14RLP2 requires the follow
34、ing services from layer 1:15 A half-rate, full-rate, double-rate, or triple-rate digital traffic16channel as specified in TIA-136-131, 132, and 133.17TIA/EIA-136-32033. RLP2 Structure1Figure 31 presents a reference model for RLP2.2RLP2 performs the following transmit functions on RLP2 SDUs3received
35、through its SAP: blocking, transmission control, frame-check-4sequence encoding, and convolutional encoding. Once RLP2 has per-5formed these functions, it delivers RLP2 Encoded Frames to layer 1.6As specified in TIA-136-131, layer 1 provides the following transmit7services to layer 2: interleaving,
36、multiplexing, and modulation. It also8provides the following receive services: demodulation, demultiplexing,9and deinterleaving.10RLP2 performs the following receive functions on RLP2 Encoded11Frames received from layer 1: convolutional decoding, frame checking,12and transmission control. Once RLP2
37、has performed these functions, it13delivers RLP2 Blocked Service Data Units to layer 3.14Figure 31 RLP2 Reference Model15Convolutional Encoder(CE)FCS Encoder(FCE)21L1Transmit Radio ChannelFCS Decoder(FCD)Convolutional Decoder(CD)Physical LayerL1Receive Radio Channelto layer 3from layer 3Layer 2Layer
38、 1Blocker(BLK)Physical Layer+16to other side of radio interface from other side of radio interfaceTransmission Controller (Transmit)(TCT)Radio Interface21+16Transmission Controller(Receive)(TCR)RLP2 Blocked SDUsUser dataRLP2 PDUsUser dataRLP2 FramesRLP2 Encoded FramesCount LengthFrame CheckUser data
39、 Count LengthSAPRLP2 SDUs16TIA/EIA-136-32043.1 Blocking1The blocker (BLK) buffers RLP2 SDUs received from layer 3, and it2blocks multiple RLP2 SDUs into single RLP2 Blocked SDUs. Each3RLP2 SDU is a single bit. Each Blocked SDU contains 23, 24, or 254nibbles.53.2 Transmission Control6The transmit tra
40、nsmission controller (TCT) places each RLP2 Blocked7SDU into a single RLP2 PDU for transmission over the radio interface.8A field within the RLP2 PDU indicates the cumulative number of9nibbles transmitted during the peer-to-peer connection. For each RLP210PDU received without unrecoverable errors, t
41、he peer receive11transmission controller (TCR) delivers to its layer 3 an RLP2 Blocked12SDU and a cumulative nibble count.133.3 Frame Check Sequence (FCS)14The FCS encoder (FCE) calculates a Cyclic Redundancy Check (CRC)15for each RLP2 PDU. It appends the CRC to the RLP2 PDU, forming an16RLP2 Frame.
42、 The FCS decoder (FCD) uses the CRC to detect if the re-17ceived RLP2 Frame contains errors and will indicate to the transmis-18sion controller the quality of the received frame: pass or fail. To assure19that the FCD will not pass frames received from an interfering co-20channel, the stored value of
43、 DVCC (Digital Verification Color Code) is21used in the CRC calculation.223.4 Forward Error Correction (FEC)23To reduce the error rate over the radio interface, the convolutional24encoder (CE) starts the FEC process by convolutionally encoding RLP225Frames into Encoded RLP2 Frames. It encodes at rat
44、e 1/2 the26encoder outputs 2 bits for every input bit. The convolutional decoder27(CD) completes the FEC process by decoding Encoded RLP2 Frames28into RLP2 Frames. A number of decoding algorithms may be used,29including Viterbi decoding with soft decision.30TIA/EIA-136-32054. Signals1RLP2 uses four
45、types of signals:2 SDUs received from layer 3 and delivered to layer 3.3 RLP2 Frames for transporting RLP2 PDUs.4 RLP2 PDUs for peer-to-peer communication.5 Service primitives for providing service to layer 3, for provid-6ing interfunction communication within RLP2, and for obtain-7ing service from
46、layer 1.84.1 RLP2 Service Data Units9From layer 3, RLP2 receives single-bit RLP2 SDUs. To layer 3, RLP210delivers RLP2 Blocked SDUs of length 23, 24, or 25 nibbles.114.2 RLP2 Frames12RLP2 Frames shall have a 114-bit body followed by a 16-bit FCS. The13body shall contain a single RLP2 PDU.144.3 RLP2
47、Protocol Data Units15RLP2 implementations shall use protocol data units of the following16form:17Bit fiOctet fl876543211 Information or Filler Information or Filler2 Information13 Information C: Count14 C: Count15 L: Length18RLP2 PDUs contain the fields described below. Fields read left to right,19t
48、op to bottom, i.e., the most-significant bit (MSB) appears in the highest20bit position of the lowest-numbered octet and the least-significant bit21(LSB) appears in the lowest bit position of the highest-numbered octet.22C Count Field 12 bits23C indicates the cumulative number of information nibbles
49、 transmitted,24modulo 4096, including the nibbles within the PDU that contains the25count field. C shall be binary coded.26TIA/EIA-136-3206Filler Filler Field 1 or 2 nibbles1Filler pads the RLP2 PDU to a fixed length. Each filler nibble shall be2coded as follows: 0000.3Information Information Field 23, 24, or 25 nibbles4The information field comprises an RLP2 Blocked SDU. It contains 23,524, or 25 nibbles of layer-3 data.6L Length Field 2 bits7L indicates the number of information nibbles in the RLP2 PDU. L8shall be coded as fo
