1、 ANSI/TIA-136-310-A-2000 APPROVED: MARCH 31, 2000 REAFFIRMED: OCTOBER 20, 2004 REAFFIRMED: AUGUST 14, 2013 WITHDRAWN: JUNE 12, 2015 TIA-136-310-A (Revision of TIA-136-310) March 2000TDMA Third Generation Wireless- Radio Link Protocol- 1 NOTICE TIA Engineering Standards and Publications are designed
2、to serve the 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
3、of such Standards 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 member
4、s, either domestically 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 ado
5、pting the Standard 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 applicab
6、ility of regulatory 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.310-A-RF2-WD, formulated under the cognizanc
7、e of the TIA TR-45 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
8、 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 and published pending patent applications are claimed and call
9、ed 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 claims of IPR. TIA will neither be a party to discussions of a
10、ny 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 procedures or practices suggested or provided in the Manual have b
11、een 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 standards (whether designated as a standard, specification, re
12、commendation or otherwise), 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 assura
13、nce relating to any 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 re
14、cords 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 otherwise investigate pro
15、ducts, 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 PARTICULAR PURPOSE OR USE,
16、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 STATUTE, RULE OR REGULA
17、TION, 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 CONTENTS CONTAINED HEREIN,
18、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 LIABILITY OR OTHERWISE,
19、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/EIA-136-310-AiForeword This foreword is not part of TIA/EIA-136-310-A.This
20、standard specifies a Radio Link Protocol (RLP1) that layer-3functions may use to asynchronously transport data octets across aTDMA radio interface.RLP1 supports two multiplexed data links, each link accessed through aunique Service Access Point (SAP). Through each SAP, RLP1 providesthe following ser
21、vices to layer 3: link establishment, link supervision,acknowledged data transport, unacknowledged data transport, dataqualification, data compression, encryption, and flow control.This standard was developed by TR-45.3.2, the Data Services WorkingGroup of TR-45.3, the TIA TDMA Wireless Standards Su
22、bcommittee. Itcontains two annexes: Annex A contains no requirements, just an illustrative exampleof protocol operation. Annex B contains no requirements: it lists and defines acro-nyms used within the standard.TIA welcomes suggestions for improvement of this standard. Pleasesend suggestions to the
23、following address:Telecommunications Industry Association2500 Wilson Boulevard Suite 300Arlington VA 22201-3836TIA/EIA-136-310-AiiChanges in this RevisionThis revision incorporates the following enhancements and corrections:1. The encryptor ( 5.7) now supports the SCEMA algorithm.2. The transmission
24、 controller (Drawing 136-310-1, Figure 310) nowgenerates the correct short feedback when the receive transmissionwindow is empty.TIA/EIA-136-310-AiiiContents1. Purpose and Scope. 12. Overview . 22.1 Services Provided by RLP1 22.2 Services Required from Layer 1 . 33. RLP1 Structure 43.1 Data Bufferin
25、g. 43.2 Compression .3.3 Blocking 63.4 Transmission Control3.5 Encryption . 73.6 Concatenation .3.7 Frame Check Sequence (FCS) 3.8 Forward Error Correction (FEC). 73.9 Layer Management .4. Signals . 84.1 RLP1 SDUs . 84.2 RLP1 Frames.4.3 RLP1 Protocol Data Units. 94.4 XID Data Unit . 184.5 Service Pr
26、imitives . 215. Processes . 285.1 Receive Data Buffer (RxB) . 285.2 Compressor (CMP) . 305.3 Expandor (EXP) 335.4 Blocker (BLK) 365.5 Deblocker (DBK) 385.6 Transmission Controller (ARQ) . 395.7 Encryptor (ENC) . 435.8 Concatenator (CON) . 455.9 Separator (SEP) . 465.10 FCS Encoder (FCE) 475.11 FCS D
27、ecoder (FCD) . 515.12 Convolutional Encoder (CE). 535.13 Convolutional Decoder (CD) 585.14 Layer Manager (LM). 616. References . 62A. Transmission-Control Example. 63B. Acronyms 72TIA/EIA-136-310-AivFigures and DrawingsFigure 21 RLP1 Position in Protocol Stack . 2Figure 31 RLP1 Reference Model . 5Fi
28、gure 41 Protocol Data Units . 10Figure 42 Service Primitives and Signal Routes for Transmit Functions . 22Figure 43 Service Primitives and Signal Routes for Receive Functions . 23Figure 51 Receive-Buffer Process . 29Figure 52 Compressor Reference Model . 31Figure 53 Compressor-Controller Process. 32
29、Figure 54 Expandor Reference Model . 34Figure 55 Expandor-Controller Process. 35Figure 56 Blocker Process . 37Figure 57 Deblocker Process . 38Figure 58 Encryptor Process 44Figure 59 FCS-Encoder Process 47Figure 510 FCS-Decoder Process 51Figure 511 Convolutional-Encoder Process 53Figure 512 Convoluti
30、onal-Decoder Process 58Figure A1A Transmission-Control Example Part 1 . 66Figure A1B Transmission-Control Example Part 2 . 68Figure A1C Transmission-Control Example Part 3 . 70136-310-1 Transmission Controller Enclosure (3)136-310-2 Concatenator and Separator. Enclosure (1)136-310-3 Layer Manager. E
31、nclosure (1)TIA/EIA-136-310-AvRevision HistoryVersion DescriptionIS-130 First release.IS-130-A 1. IS-130-1 Figure 101 (D5) now specifies that T1 expiry shall only be interpreted in statesCM2, CM3, CM5, and CM6. Otherwise, T1 expiry may be interpreted in states that are nottimed, which may cause RLP1
32、 to abort a connection that would otherwise connectsuccessfully.2. IS-130-1 Figure 201 (C6) now specifies that if Send_B_Once is true, an S PDU shall be sentinstead of an LS PDU. This enhancement increases full-duplex throughput.3. IS-130-1 Figure 201 (B5) now has a note explaining the function perf
33、ormed by the N=1?test. This should aid implementors in understanding the standard.4. IS-130-1 Figure 305B (D4) uses a new receive-counter formula. The original formulaallowed the decryptor to lose synchronization with the encryptor. This correction requiredminor changes to IS-130-1 Figures 301 (D6)
34、and 315 (B1).5. 5.7 was modified to conform with the latest version of Common CryptographicAlgorithms.6. 5.12.2.4 contains a new example output for the convolutional encoder. The originalexample was wrong.7. 5.13.2.3 now references a paper that describes a technique for convolutional decoding.TIA/EI
35、A-136-3101. Portions of the transmission controller (Drawing 136-310-1, Figures 306, 307, 311, 312,313, 318, 319, and 320) now update only the portion of the receive table that corresponds tothe received partial bitmap. As a result, only PDUs that need to be retransmitted will beretransmitted, and b
36、idirectional data throughput will improve.2. Another part of the transmission controller (Drawing 136-310-1, Figure 310) no longer triesto set BP_Tx to B_RxT for values delivered to the deblocker and therefore deleted from thereceive table, i.e., those values corresponding to NS_RxT less than NR_Rx.
37、3. The concatenator (Drawing 136-310-2, Figure 101) now pads or fills concatenated PDUs toa fixed length of 27 octets. The FCS encoder (Figure 59) strips 2 or 3 Null PDUs from theconcatenated PDU, as appropriate, before adding 2 or 3 octets of FCS (Frame CheckSequence). The original concatenator cou
38、ld not determine the appropriate length ofconcatenated PDUs.4. The layer manager (Drawing 136-310-3, Figure 101) now issues connect primitives(Connect_Ind and Connect_Con) after sending Init_Reqs to the compressor and theexpandor, not before. This prevents data loss if layer 3 immediately issues a D
39、ata_Req uponreceiving a connect primitive.5. IS-130-A incorporated the following enhancement to the transmission-controllerconcatenator handler (Drawing 136-310-1, Figure 201): If Send_B_Once is true, an S PDUshall be sent instead of an LS PDU. This enhancement causes the receiver to time out whenex
40、erting flow control for extended periods. The drawing reverts to its previous form wherean LS PDU shall be sent.TIA/EIA-136-310-A1. The encryptor ( 5.7) now supports the SCEMA algorithm.2. The transmission controller (Drawing 136-310-1, Figure 310) now generates the correctshort feedback when the re
41、ceive transmission window is empty.TIA/EIA-136-310-AviSpare pageTIA/EIA-136-310-A11. Purpose and Scope1This standard specifies a Radio Link Protocol (RLP1) that layer-32functions may use to asynchronously transport data octets across a3TDMA radio interface. RLP1 requires an underlying half-rate, ful
42、l-rate,4double-rate, or triple-rate digital traffic channel as specified in5TIA-136-131, 132, and 133 7.6To aid the reader, 2 and 3 contain descriptive information: 2 pro-7vides an overview; 3 describes the protocols structure. 4 and 58contain requirements: 4 specifies RLP1 signals; 5 specifies pro-
43、9cesses. References appear in 6. Finally, Annex A illustrates protocol10operation, and Annex B lists and defines acronyms. Note that 5 refers11to figures too large to fit within the body of the standard. These figures12are enclosed in a separate envelope.13Readers will find the following documents h
44、elpful in understanding this14standard: X.200 4 and Z.100 5.15Similar to X.200, this standard uses reference models to organize con-16cepts and requirements into a logical structure. These reference models17are not meant to unnecessarily constrain implementations any RLP118implementation that, as a
45、whole, behaves the same as the RLP1 speci-19fied in this standard, by definition, complies with this standard.20If the requirements of this standard conflict with the requirements of21referenced standards, this standard shall govern.22TIA/EIA-136-310-A22. Overview1RLP1 asynchronously transports data
46、 octets between unspecified2layer-3 functions. It resides at the link layer (layer 2), just above the3physical layer (layer 1) and just below the network layer (layer 3). See4Figure 21.5Figure 21 RLP1 Position in Protocol Stack6Layer 1Layer 3 Unspecified Layer-3 FunctionRadio Link Protocol 1Digital
47、Traffic ChannelRadio InterfaceLayer 2Unspecified Layer-3 FunctionSAP1SAP0 SAP1SAP0Digital Traffic ChannelRadio Link Protocol 172.1 Services Provided by RLP18RLP1 supports two multiplexed data links, each link accessed through a9unique Service Access Point (SAP). Through each of these SAPs,10RLP1 pro
48、vides the following services to layer 3:11 Link establishment. At the request of layer 3, RLP1 connects or12disconnects a reliable data link.13 Link supervision. RLP1 informs layer 3 if a reliable link has14disconnected or if RLP1 has detected a protocol error.15 Acknowledged data transport. In ackn
49、owledged mode, RLP116provides a reliable data link: it delivers all data received from17the transmitting layer 3 to the receiving layer 3. It controls the18error rate at the expense of variable throughput and delay. It19preserves the order of data octets but not their relative timing.20 Unacknowledged data transport. In unacknowledged mode,21RLP1 does not guarantee a reliable data link. It provides con-22stant throughput and delay at the expense of a variable error23rate. It preserves the order
