TIA/EIA
`INTERIM STANDARD
`
`Ct
`
`it1
`
`Data Service Options for Wideband
`Spread Spectrum Systems
`
`TIA/EIA/IS-707-A
`
`Revision of TIAIEL/IS-707
`
`APRIL 1999
`
`TELECOMMUNICATIONS INDUSTRY ASSOCIATION
`
`TEL ft 0MM/A CA rIDMS
`
`WDUSWYASS8AflVM
`
`Representing the telecoinmonications
`
`indnst in
`
`association ssith the Electronic
`
`Industries Alliance
`
`ElEctronic Industries AIli2nce
`
`Broadcom v. Ericsson
`IPR2013-00601
`Broadcom 1010
`
`

`

`ARIB STD-T64-C.S0O1 7-0
`
`Data Service Options for Spread
`Spectrum Systems
`
`Refer
`
`to Industrial Property Rights IPR in the preface of ARIB STD-T64 for Related Industrial
`to Notice in the preface of ARIB STD-T64 for Copyrights
`
`Property Rights Refer
`
`

`

`NOTICE
`
`TIA/EIA Engineering Standards and Publications
`are designed to serve the public interest
`through eliminating
`misunderstandings between manufacturers
`and purchasers facilitating interchangeability and improvement of
`in selecting and obtaining with minimum delay the proper product
`products and assisting the purchaser
`his particular need Existence of such Standards and Publications shall not
`in any respect preclude any
`member or nomnember of TIA/EIA from manufacturing or selling products not confonning to such
`Standards and Publications nor shall
`the existence of such Standards and Publications preclude their
`voluntary use by those other than TIA/EIA members whether
`or intemationally
`
`the standard is to be used either domestically
`
`for
`
`are adopted by TIA/EIA in accordance with the American National Standards
`Standards and Publications
`Institute ANSI patent policy By such action TIA/EIA does not assume any liability
`to any patent owner
`nor does it assume any obligation whatever
`to parties adopting the Standard or Publication
`
`TIA/EIA INTERIM STANDARDS
`
`TIA/EIA Interim Standards contain infonnation deemed to be of teclmical value to the industry and are
`published at the request of the originating Committee without necessarily
`following the rigorous public review
`and resolution of comments which is
`procedural part of the development of TIA/EIA Standard
`
`TIA/EIA Interim Standards should be reviewed on an annual basis by the formulating Committee and
`TIA/EIA
`decision made on whether
`Standard on this subject TIA/EIA Interim
`to proceed to develop
`Standards must be cancelled by the Committee and removed from the TIA/EIA Standards Catalog before the
`end of their third year of existence
`
`Publication of this TL/EIA Interim Standard for trial use and comment has been approved by the
`Telecommunications Industry Association Distribution of this TIA/EIA Interim Standard for comment shall
`not continue beyond 36 months from the date of publication
`is expected that following this 36 month
`period this TIA/EIA Interim Standard revised as necessary will be submitted to the American National
`Standards Institute for approval as an American National Standard
`Suggestions for revision should be
`Technology Department Telecommunications Industry Association 2500 Wilson
`directed to Standards
`Boulevard Arlington VA 22201
`
`It
`
`From Project No 4145 formulated under the cognizance of the TIA TR-45.5 Subcommittee
`Spectrum Digital Technology
`
`on Spread
`
`Published by
`
`INDUSTRY ASSOCIATION 1999
`8TELECOMMUNICATIONS
`Technology Department
`Standards
`2500 Wilson Boulevard
`Arlington VA 22201
`
`PRICE Please refer to current Catalog of
`EIA ELECTRONIC INDUSTRIES ALLIANCE STANDARDS and ENGINEERING
`PUBLICATIONS or call Global Engineering Documents USA and Canada 1-800-854-7179
`International 303-397-7956
`
`All rights reserved
`Printed in USA
`
`

`

`1waw __ __
`
`-_
`
`A-
`
`Data Service Options for Spread Spectrum
`Systems High Speed Packet Data Services
`TINE INIS-70 7-A PN-4 145.9
`
`Ballot Resolution Version
`
`March 1999
`
`

`

`Copyright 1999 TIA
`Copyright 1999 TIA
`
`

`

`TIA/EIA/IS-707
`
`A.9
`
`CONTENTS
`
`INTRODUCTION
`
`1.1 General Description
`
`.3
`
`1.2
`
`Terms
`
`1.3
`
`References
`
`1.4 Overview of Packet Data Service
`
`1.4.1
`
`Packet Data Service Types and Configurations
`
`1.4.2
`
`Protocol Options
`1.4.2.1 Relay Layer Rm Interface Protocol Option
`
`1.4.2.2 Network Layer Rm Interface Protocol Option
`
`1.4.3
`
`Packet Data Protocol States
`
`1.4.3.1
`
`IWF Link Layer Connection States
`
`1.4.3.2 Mobile Station Packet Data Service States
`
`1.4.3.3
`
`BS/MSC Packet Data Service States
`
`RELAY LAYER
`
`2.1
`
`Introduction
`2.2 Um Interface Requirements
`
`2.2.1
`
`RLP Requirements
`
`2.2.2
`
`Service and Call Control Procedures
`
`2.2.2.1 Mobile Station Procedures
`
`2.2.2.1.1
`
`Packet Data Service Control Procedures
`
`2.2.2.1.1.1
`
`Inactive State
`
`2.2.2.1.1.2 Active State
`
`2.2.2.1.2 Packet Data Service Call Control Function
`
`2.2.2.1.2.1 Null State
`
`2.2.2.1.2.2 Initialization/Idle State
`
`2.2.2.1.2.3 Initialization/Traffic State
`
`2.2.2.1.2.4 Connected State
`
`2.2.2.1.2.5
`
`Dormant/IdleState
`
`2.2.2.1.2.6 Dormant/Traffic
`
`State
`
`2.2.2.1.2.7 Reconnect/Idle State
`
`2.2.2.1.2.8 Reconnect/Traffic State
`
`2.2.2.2 BS/MSC Procedures
`
`10
`
`11
`
`12
`
`13
`
`14
`
`16
`
`17
`
`18
`
`19
`
`20
`
`21
`
`22
`
`23
`
`24
`
`25
`
`26
`
`27
`
`28
`
`29
`
`30
`
`31
`
`.32
`
`1-1
`
`1-1
`
`1-1
`
`1-4
`
`1-4
`
`1-4
`
`1-5
`
`1-6
`
`1-7
`
`1-9
`
`2-1
`
`2-1
`
`2-1
`
`22
`
`2-2
`
`23
`
`24
`
`2-6
`
`2-8
`
`2-8
`
`

`

`TIA/EIA/IS 707-A.9
`
`2.2.2.2.1
`
`Packet Data Service Control Procedures
`
`CONTENTS
`
`2.2.2.2.1.1
`
`Inactive State
`
`2.2.2.2.1.2 Active State
`
`2.2.2.2.2
`
`Packet Data Service Call Control Function
`
`2.2.2.2.2.1 NuliState
`
`2.2.2.2.2.1.1 1WF Initiated Link Layer Connection Reactivation
`
`2.2.2.2.2.1.2 Mobile Station Originated Link Layer Connection Activation...2
`
`2.2.2.2.2.1.3 Mobile Station Negotiated Link Layer Connection Activation
`
`2.2.2.2.2.1.4 IWF Link Layer Closure
`
`2.2.2.2.2.1.5 1WF Transfer
`
`2.2.2.2.2.2
`
`PagingState
`
`2.2.2.2.2.3 Initialization/Idle State
`
`2.2.2.2.2.4 Initialization/Traffic State
`
`2.2.2.2.2.5 Connected State
`
`2.2.3
`
`Initialization and Connection of Packet Data Sen ice Options
`
`2.2.3.1 Mobile Station Procedures
`
`2.2.3.2 BS/MSC Requirements
`
`2.2.4 Optional Zone-Based Registration or Reconnection
`
`2.2.5 Optional Reconnect After Hard Handoff
`
`2.2.6 Optional Packet Data Dormant Timer Control
`
`2.2.7 Optional Packet Zone Reconnection Control
`
`2.2.8
`
`High Speed Operation
`
`2.2.8.1 Mobile Station Procedures for Reverse High Speed Operation
`
`2.2.8.2 Reverse High Speed Operation Messages
`
`2.2.8.2.1 General Message Format and Coding
`
`2.2.8.2.2 Reverse Bandwidth Request Message
`
`2-8
`
`2-8
`
`10
`
`2-10
`
`10
`
`11
`
`12
`
`2-12
`
`12
`
`13
`
`2-13
`
`14
`
`2-14
`
`15
`
`2-16
`
`2-18
`
`18
`
`2-19
`
`2-21
`
`23
`
`2-28
`
`28
`
`29
`
`29
`
`31
`
`32
`
`of Reverse
`
`Supplemental
`
`Code Channels
`33
`
`of
`
`Reverse
`
`Supplerhental
`
`Code
`
`Channels
`
`2-33
`
`2-34
`
`2.2.8.2.2.1
`
`Request Type
`
`2.2.8.2.2.2 Maximum Number
`Information Element
`
`2.2.8.2.2.3 Preferred Number
`Information Element
`
`2.2.8.2.2.4 Requested Duration Information Element
`
`11
`
`10
`
`11
`
`12
`
`13
`
`14
`
`16
`
`17
`
`is
`
`19
`
`20
`
`21
`
`22
`
`23
`
`24
`
`23
`
`26
`
`27
`
`28
`
`29
`
`30
`
`31
`
`32
`
`

`

`CONTENTS
`
`2.2.8.2.2.5 Additional SO Request
`
`Information Element
`
`Z.2.8.Z.Z.b Priority Information Element
`
`2.3
`
`Llnterface
`
`2.3
`
`Logical Connections
`
`2.3.2 Mobile Data
`
`LINK LAYER
`
`3.1
`
`LinkLayerProtocols
`
`3.2
`
`Link Layer Connections
`
`3.2.1
`
`1WF Link Layer Connection Opening
`
`3.2.2
`
`IWF Link Layer Connection Maintenance
`
`3.2.3
`
`IWF Link Layer Connection Closure
`
`3.2.3.1 BS/MSC Closure
`
`3.2.3.2
`
`IWF Closure
`
`3.2.3.3 TE2 Closure
`
`3.2.3.4 MT2Closure
`
`NETWORK LAYER
`
`4.1
`
`4.2
`
`4.3
`
`Internet Protocol Support
`
`ISO Protocol Support
`
`CDPD Application Support
`
`10
`
`12
`
`13
`
`15
`
`16
`
`17
`
`is
`
`19
`
`TIA/EIA/IS 707 A.9
`
`2-34
`
`Z-35
`
`35
`
`35
`
`36
`
`3-2
`
`3-3
`
`33
`
`4-1
`
`4-1
`
`111
`
`

`

`TIA/EIA/IS-707-A.9
`
`FIGURES
`
`Figure
`
`Relay Layer Rm Interface Protocol Option
`
`Figure
`
`Network Layer Rm Interface Protocol Option
`
`Figure
`
`Figure
`
`Packet Data Service Call Control States in the Mobile Station
`
`Packet Data Service Call Control States in the BS/MSC
`
`11
`
`10
`
`ii
`
`13
`
`14
`
`13
`
`16
`
`17
`
`18
`
`19
`
`20
`
`21
`
`22
`
`23
`
`24
`
`25
`
`26
`
`TABLES
`
`Table
`
`Valid Service Configuration Attributes for Service Options 22 and 26
`
`Table
`
`Valid Service Configuration Attributes for Service Options 23 and 27
`
`Table
`
`Valid Service Configuration Attributes for Service Options 24 and 28
`
`Valid Service Configuration Attributes for Service Options 25 and 29
`
`Table
`
`Table
`
`16
`
`2-17
`
`2-17
`
`2-17
`
`ORDQ Format and Type-Specific Fields for Zone Based Registration/Reconnection
`219
`
`Table
`
`Zone Based Registration/Reconnection Control Field
`
`Table
`
`ORDQ Format and Type Specific Fields for Reconnect After Hard Handoff
`
`Table
`
`Reconnect After Hard Handoff Control Field
`
`Table
`
`Type-Specific Fields for Data Dormant Timer Control
`
`Table 10 Dormant Timer Control Field
`
`Table 11 Minimum Value of Mobile Station Dormant Timer
`
`Table 12 Type Specific Fields for Packet Connection Control
`
`Table 13 Packet Zone Connection Control Field
`
`Table 14 Type-Specific
`
`Fields for Packet Zone Connection Response
`
`Table 15 Reverse Bandwidth Request Message Contents
`
`Table 16 Requesting Service Type
`
`2-19
`
`20
`
`21
`
`2-21
`
`2-23
`
`23
`
`2-24
`
`2-26
`
`27
`
`31
`
`32
`
`iv
`
`

`

`TIA/EIA/IS-707-A.9
`
`INTRODUCTION
`
`1.1 General Description
`
`This chapter defines requirements for support of high speed packet data transmission
`capability on TIA/EJA 95
`spread spectrum systems Packet data transmission is
`supported on TIA/EIA 95
`Traffic Channels using primary or secondary traffic
`For
`packet data transmission using TIA/EJA 95
`Traffic Channels the Radio Link Protocol
`specified in IS 707 A.8 is used
`Type
`
`packet data bearer service for communication between terminal
`This standard specifies
`interworking function IWF via
`equipment and
`base station/mobile
`switching
`packet
`renter BS/MSC It provides procedures that can apply to multiple packet data services
`e.g CDPD and Mobile IP
`
`Packet data service options provide means of establishing and maintaining Traffic
`Channels for packet data service Service Options 22 23 24 and 25 are used to request
`packet data service through an IWF supporting an Internet standard Point-to Point
`Protocol PPP interface to network layer protocols see 4.1 and 4.2 Service Options 26
`27 28 and 29 are used to request packet data service through an IWF supporting CDPD
`PPP interface see 4.3 Additional packet data service options may be
`data services over
`defined in future revisions to select other types of IWF resources or services
`
`1.2
`
`Terms
`Base Station BS fixed station used for communicating with mobile stations
`Depending upon the context the term base station may refer to
`cell or other part of the cellular system
`BS See base station
`
`cell
`
`sector within
`
`BS/MSC The base station and mobile switching center considered as
`entity
`CDPD Cellular Digital Packet Data
`CLNP Connectionless Network Protocol See ISO 8473 1988
`Data Circuit-Terminating Equipment DCE
`DCE connects
`series modem
`typical DCE would be
`DTE Data Terminal Equipment
`Forward Supplemental Code Channel
`forward direction
`
`single functional
`
`DTE to the PSTN
`
`Supplemental Code Channel operating in the
`
`Fundamental Code Cbannel
`Traffic Channel Forward or Reverse that is
`portion of
`always present and carries primary traffic secondary traffic signaling and power control
`information
`GHDM General Handoff Direction Message see 7.7.3.3.2.3
`IWF Interworking Function see 1.4.2
`
`of TIA/EIA-95-B
`
`IP Internet Protocol
`
`11
`
`in
`
`ii
`
`12
`
`13
`
`14
`
`la
`
`17
`
`18
`
`19
`
`20
`
`21
`
`22
`
`23
`
`24
`
`25
`
`26
`
`27
`
`28
`
`29
`
`30
`
`31
`
`32
`
`is
`
`34
`
`ss
`
`so
`
`37
`
`38
`
`

`

`TIA/EIA/IS-707
`
`A.9
`
`IPCP Internet Protocol Control Protocol see RFC 1332
`LCP PPP Link Control Protocol see RFC 1661
`
`Mobile IP Mobile Internet Protocol see RFC 2002
`
`Mobile Station
`station in the Public Cellular Radio Telecommunications Service
`intended to be used while in motion or during halts at unspecified points Mobile stations
`include portable units e.g hand-held personal units and units installed in vehicles
`MSC Mobile Switching Center
`MTO Mobile Termination
`MT2 Mobile Termination
`
`see 1.4.2
`
`see 1.4.2
`
`10
`
`ii
`
`12
`
`13
`
`14
`
`16
`
`17
`
`is
`
`is
`
`20
`
`21
`
`22
`
`23
`
`24
`
`25
`
`26
`
`28
`
`29
`
`30
`
`31
`
`32
`
`33
`
`34
`
`OSINLCP OSI Network Layer Control Protocol see RFC 1377
`PPDN Public Packet Data Network
`
`PPP Point
`
`to Point Protocol see RFC 1661
`PSTN Public Switched Telephone Network
`
`Supplemental Code Channel operating in the
`
`Reverse Supplemental Code Channel
`reverse direction
`RFC Request
`for Comments The generic name of
`Internet Engineering Task Force IETF
`RLP Radio Link Protocol
`SCAM Supplemental Channel Assignment Message see 7.7.3.3.2.24 of TIA/EIA 95-B
`SCRM Supplemental Channel Request Message see 6.7.2.3.2.18 of TIA/EIA-95-B
`SLIP Serial Line IP
`
`specification developed by the
`
`Supplemental Code Channel
`portion of Traffic Channel Forward or Reverse that is
`optionally present and carries either primary or secondary traffic
`TCP Transmission Control Protocol
`
`TE2 Terminal Equipment
`Traffic Channel
`Fundamental Code Channel Forward or Reverse and optionally up to
`seven Supplemental Code Channels used to transport user data and signaling traffic
`between the base station and the mobile station
`
`see 1.4.2
`
`1.3
`
`References
`
`ANSI/TIA/EIA-617
`
`Inband DCE Control for Asynchronous DTEDCE Interfaces
`An ITAR
`Common Cryptographic Algorithms Revision
`controlled document subject to restricted distribution Contact
`the Telecommunications Industry Association Washington
`D.C April 25 1995
`
`1-2
`
`

`

`TIA/EIA/IS-707-A
`
`RLP FRAME FORMATS
`
`For RLP control frames RLP shall use the formats defined iii 4.1
`
`RLP shall use the
`For Fundamental RLP data frames whose rate is less than Rate
`Fundamental or Supplemental RLP data frames RLP
`
`formats in 4.2.1 or 4.2.2 For Rate
`
`shall use the formats in 4.2.3
`
`For idle frames RLP shall use the format in 4.3
`
`4.1 Control Frames
`
`Control
`
`frames are distinguished by the CTL field
`
`bits of L_VS in order that missing
`Control frames shall contain the least significant
`data frames may be quickly detected RLP shall not increment L_VS after generating
`frame
`control
`
`4.1.1
`
`SYNC SYNC/ACK and ACK Control Frames
`
`SYNC SYNC/ACK and ACK control
`
`frames are used during RLP initialization
`
`Field
`
`SEQ
`
`CTL
`ENCRYPTION MODE
`EM
`
`EXT_SEQ_M
`
`Paddingi
`
`FCS
`
`Padding2
`
`SEQ
`
`CTL
`
`Length bits
`
`Oor2
`
`or 18
`
`Variable
`
`16
`
`Variable
`
`Data frame sequence number
`For SYNC SYNC/ACK and ACK control
`RLP frame type
`frames the CTL field is defined as follows
`1101 10 SYNC Requests return of
`ACK bit set
`
`frame with the
`
`control
`
`ACK Acknowledges
`1110 10
`with the SYNC bit set
`1111 10 SYNC/ACK Indicates both SYNC and ACK
`
`receipt of
`
`control
`
`frame
`
`ENCRYPTION MODE
`
`Encryption Mode
`
`This
`field indicates
`the
`or desired user data
`supported
`encryption modes set according to Table 11
`
`EM
`
`Encryption Request
`
`Indicator
`
`4-1
`
`10
`
`ii
`
`12
`
`13
`
`14
`
`15
`
`16
`
`17
`
`18
`
`19
`
`20
`
`21
`
`22
`
`23
`
`24
`
`25
`
`26
`
`

`

`10
`
`11
`
`13
`
`14
`
`13
`
`16
`
`17
`
`18
`
`19
`
`20
`
`TIA/EIA/IS-707-A.8
`
`EXT_SEQ_M
`
`Padding
`
`FCS
`
`no RLP data frame
`
`RLP data frame encryption
`
`00 Default Requests or Acknowledges
`encryption not supported or inactive
`01 Requests or Acknowledges
`capability
`This field shall be included when the EM field is included
`When the EM field is set to 01 this field shall be set
`to the
`of EXT_VS
`18 most
`see
`3.1.1.2.1
`bits
`significant
`Otherwise this field shall be set to all zeros
`Padding bits As required to octet align the FCS field These
`bits shall be set to
`
`The contents shall be as generated
`Frame Check Sequence
`by the 16 bit FCS polynomial specified in 3.1 of RFC 1662
`The FCS shall cover all fields before the FCS field
`
`Padding
`
`Padding bits As required to fill
`These bits shall be set to
`
`the remainder of the frame
`
`Table 11 User Data Encryption Modes
`
`Encryption Mode binary
`
`Meaning
`
`00
`
`01
`
`10
`
`11
`
`Encryption not supported default
`
`Enhanced encryption mode
`
`Both basic and enhanced encryption modes
`This value shall not be used in ACK control
`frames
`
`Basic encryption mode
`
`4.1.2
`
`NAK Control Frame
`
`NAK control
`
`frame requests the retransmission of one or more data frames
`
`42
`
`

`

`TIA/EIA/IS-707
`
`A.8
`
`Length bits
`
`Field
`
`SEQ
`
`CTL
`
`NAK_TYPE
`
`L_SEQ HI
`If NAK TYPE 00 the following fields shall be
`FIRST
`
`12
`
`LAST
`12
`If NAK TYPE 01 the following fields shall be
`NAK Map_Count
`NAK Map Count
`
`occurrences of the following record
`
`NAK Map_SEQ
`NAK Map
`For any NAK_TYPE value the following fields shall be
`
`12
`
`Padding_i
`
`FCS
`
`Padding
`
`SEQ
`
`CTL
`
`NAK TYPE
`
`SEQ HI
`
`FIRST
`
`LAST
`
`Padding
`
`FCS
`
`Variable
`
`16
`
`variable
`
`Data frame sequence number
`1100 00 NAK Requests retransmission of data frames
`NAK type as defined below
`00 Requests retransmission of data frames numbered
`FIRST through LAST inclusive
`01 Requests retransmission of data frames as specified by
`the NAK Maps
`The most significant
`
`bits of L_VS
`The 12-bit sequence number of the first data frame for which
`retransmission is requested
`
`The 12-bit sequence number of the last data frame for which
`retransmission is requested
`Padding bits As required to octet align the FCS field These
`bits shall be set to
`
`The contents shall be as generated
`Frame Check Sequence
`in 3.1 of RFC 1662
`by the 16-bit FCS polynomial
`specified
`The FCS shall cover all fields before the FCS field
`
`Padding
`
`Padding bits As required to fill
`These bits shall be set to
`
`the remainder of the frame
`
`4-3
`
`is
`
`11
`
`12
`
`13
`
`14
`
`16
`
`17
`
`18
`
`19
`
`20
`
`

`

`TIA/EIA/IS 707 A.8
`
`NAK Map Count
`
`NAK_Map SEQ
`
`NAK Map
`
`One less than the number of NAK Maps in this NAK control
`frame
`
`The 12-bit sequence number of the first data frame for which
`retransmission is requested
`
`bitmap identiing additional missing data frames for which
`The most
`retransmission is
`bit
`requested
`significant
`corresponds to the data frame identified by NAK Map SEQ
`modulo 4096 Each less significant bit corresponds to the
`next sequential data frame
`indicates that the
`bit set
`to
`corresponding data frame is missing
`
`4.2 Data Frames
`
`4.2.1 Unsegmented Data Frames
`
`Unsegmented data frames carry
`indicate the number of octets
`
`variable number of data octets using
`
`length field to
`
`Field
`
`SEQ
`
`CTL
`
`REXMIT
`
`LEN
`
`Data
`
`Padding
`
`SEQ
`
`CTL
`
`REXMIT
`
`LEN
`
`Length bits
`
`8xLEN
`
`Variable
`
`Data frame sequence number See 3.1.2
`
`For
`
`set to
`
`frame carrying unsegmented data the CTL field shall be
`18
`
`Retransmitted frame indicator This bit
`is set to
`retransmitted data frame Otherwise it
`frame is
`
`when the
`is set to
`
`Data length May be any value in the range from to the
`maximum allowable for the data frame Maximum values of
`LEN MAX_LEN are given in Table 12
`
`When LEN is zero the frame is treated as an idle frame
`
`Data
`
`Data octets
`
`18Note that the most significant bit of the CTL field of
`
`control
`
`frame and
`
`segmented data frame is
`
`always set to
`
`4-4
`
`10
`
`ii
`
`12
`
`13
`
`14
`
`lo
`
`16
`
`17
`
`18
`
`19
`
`20
`
`21
`
`22
`
`23
`
`24
`
`25
`
`26
`
`

`

`Padding
`
`Padding bits As required to fill
`These bits shall be set to
`
`the remainder of the frame
`
`TIA/EIA/IS-707-A.8
`
`Table 12 Values of the Maximum Allowable Data Length MAX_LEN
`
`RLP Frame Type
`
`MAX LEN
`
`MAX LEN
`
`Multiplex
`
`Options3579
`
`11 13 and
`15
`
`Multiplex
`Options
`46810
`12 14 and
`16
`
`Primary Traffic
`
`Rate
`
`Format
`
`see 4.2.3.1.1
`
`19
`
`Rate 1/2
`
`Rate 1/4
`
`Secondary Traffic
`
`Rate
`
`Format
`
`see 4.2.3.1.2
`
`Rate 7/8
`
`Rate 3/4
`
`Rate 1/2
`
`Rate 7/16
`
`Rate 3/8
`
`Rate 1/4
`
`Rate 3/16
`
`Not Used
`
`19
`
`17
`
`14
`
`N/A
`
`N/A
`
`Not Used
`
`N/A
`
`31
`
`13
`
`30
`
`28
`
`24
`
`15
`
`13
`
`10
`
`4.2.2
`
`Segmented Data Frames
`
`variable number of data octets using
`Segmented data frames carry
`length field to
`indicate the number of octets This type of data frame shall only be used to carry
`retransmitted data frames see 3.1.4
`
`10
`
`11
`
`Field
`
`SEQ
`
`CTL
`
`LEN
`
`Data
`
`Padding
`
`Length bits
`
`Oor4
`
`or 8xLEN
`
`Variable
`
`45
`
`

`

`TIA/EIA/IS-707
`
`A.8
`
`SEQ
`
`CTL
`
`LEN
`
`Data
`
`10
`
`11
`
`12
`
`13
`
`14
`
`16
`
`17
`
`18
`
`19
`
`20
`
`21
`
`22
`
`23
`
`24
`
`26
`
`27
`
`28
`
`29
`
`30
`
`31
`
`32
`
`33
`
`Data frame sequence number See 3.1.4
`
`For segmented
`follows
`
`data
`
`frames the CTL field
`
`is defined as
`
`First Segment Contains the first LEN octets of the
`1000
`segmented data frame
`
`Second Segment Contains the next LEN octets of
`1001
`the segmented data frame
`
`Last Segment Contains the last LEN octets of the
`1010
`segmented data frame
`
`1011
`
`fill
`
`Intersegment Fill Frame When Multiplex Option
`10 12 14 or 16 is used intersegment
`frames can
`be sent before or between segmented data frames see 3.1.4
`frames are not used with Multiplex Option
`Intersegment
`3.579.1113orlS
`
`fill
`
`Data length When CTL is set to 1000 1001 or 1010 the
`LEN field may be any
`value
`to the
`in the range from
`maximum allowable for the data frame or 15 whichever
`the maximum allowable
`less
`Values
`data
`of
`length
`lvIAX LEN are given in Table 12 When CTL is set to 1011
`the LEN field shall not be included
`
`is
`
`Data octets When CTL is set to 1000 1001 or 1010 this
`to 1011
`field shall carry LEN Data octets When CTL is set
`the Data field shall not be included
`
`Padding
`
`Padding bits As required to fill
`These bits shall be set to
`
`the remainder of the frame
`
`4.2.2.1
`
`Rate 1/8 and Rate 1/16 Intersegment Fill Frames
`
`10 12 14 or 16 Rate 1/8 primary traffic RLP frames and
`For Multiplex Option
`frames
`Rate 1/16 secondary traffic RLP frames may be intersegment
`
`fill
`
`Field
`
`SEQ
`
`FCS
`
`1SF
`
`SEQ
`
`FCS
`
`Length bits
`
`Data frame sequence number See 3.1.4
`
`to the FCS
`Frame Check Sequence
`This field is identical
`field of an idle frame with matching SEQ field See 4.3
`
`4-6
`
`

`

`TIA/EIA/IS-707
`
`A.8
`
`1SF
`
`Intersegment Fill
`an intersegment
`
`frame indicator The value 1111 indicates
`frame
`
`fill
`
`4.2.3
`
`Rate
`
`RLP Frames
`
`For Rate
`
`RLP data frames two special frame formats are used Format
`RLP data
`frames are described in 4.2.3.1 Format
`RLP data frames are described in 4.2.3.2
`
`4.2.3.1
`
`Rate
`
`RLP Frame FormatA
`
`4.2.3.1.1
`
`Format
`
`for Primary Traffic
`
`When RLP frames are carried as primary traffic by Multiplex Option
`and 15
`format
`frame is defined as follows
`
`11 13
`
`Field
`
`Information
`
`TYPE
`
`Length bits
`
`168
`
`Information
`
`Control or data frame Formatted according
`to the control
`and data frame formats described in 4.1 4.2.1 and 4.2.2
`
`TYPE
`
`Frame type The TYPE field shall be set to 001
`
`When RLP frames are carried as primary traffic by Multiplex Option
`and 16
`format
`frame is defined as follows
`
`10 12 14
`
`Field
`
`Information
`
`TYPE
`
`Length bits
`
`264
`
`Information
`
`TYPE
`
`Control or data frame Formatted according
`to the control
`and data frame formats described in 4.1 4.2.1 and 4.2.2
`Frame type The TYPE field shall be set to 01
`
`4.2.3.1.2 Format
`
`for Secondary Traffic
`
`When RLP frames are carried as secondary traffic by Multiplex Option
`and 15
`format
`frame is defined as follows
`
`11 13
`
`10
`
`11
`
`12
`
`13
`
`14
`
`16
`
`17
`
`18
`
`19
`
`20
`
`21
`
`22
`
`23
`
`24
`
`25
`
`26
`
`27
`
`4-7
`
`

`

`TIA/EIA/IS 707-A.8
`
`Field
`
`Information
`
`TYPE
`
`Length bits
`
`165
`
`Information
`
`Control or data frame Formatted according to the control
`and data frame formats described in 4.1 4.2.1 and 4.2.2
`
`TYPE
`
`Frame type The TYPE field shall be set to 001
`
`When RLP frames are carried as secondary traffic by Multiplex Option
`and 16
`format
`frame is defined as follows
`
`10 12 14
`
`Field
`
`Information
`
`TYPE
`
`Length bits
`
`260
`
`Information
`
`Control or data frame
`Formatted according to the control
`and data frame formats described in 4.1 4.2.1 and 4.2.2
`
`TYPE
`
`Frame type The TYPE field shall be set to 01
`
`4.2.3.2
`
`Rate
`
`RLP Data Frame Format
`
`4.2.3.2.1
`
`Format
`
`for Primary Traffic
`
`When RLP frames are carried as primary traffic by Multiplex Option
`and 15
`format
`frame is defined as follows
`
`11 13
`
`Field
`
`SEQ
`
`Data
`
`TYPE
`
`SEQ
`
`Data
`
`TYPE
`
`Length bits
`
`160
`
`Data frame sequence number See 3.1.2 and 3.1.4
`
`Data octets This field shall contain 20 octets of data
`
`to 010 for
`Frame type The TYPE field is set
`new data
`frame and set to 011 for
`retransmitted data frame
`
`48
`
`io
`
`11
`
`12
`
`13
`
`14
`
`ic
`
`17
`
`18
`
`19
`
`20
`
`21
`
`22
`
`23
`
`

`

`When RLP frames are carried as primary traffic by Multiplex Option
`and 16
`format
`frame is defined as follows
`
`10 12 14
`
`hA/ETA/IS 707-A.8
`
`Field
`
`SEQ
`
`Data
`
`TYPE
`
`SEQ
`
`Data
`
`TYPE
`
`Length bits
`
`256
`
`Data frame sequence number See 3.1.2 and 3.1.4
`
`Data octets This field shall contain 32 octets of data
`
`Frame type The TYPE field is set to 10 for
`and set to 11 for
`retransmitted data frame
`
`new data frame
`
`4.2.3.2.2 Format
`
`for Secondary Traffic
`
`When RLP frames are carried as secondary traffic by Multiplex Option
`and 15
`format
`frame is defined as follows
`
`11 13
`
`Field
`
`SEQ
`
`Data
`
`TYPE
`
`SEQ
`
`Data
`
`TYPE
`
`Length bits
`
`152
`
`Data frame sequence number See 3.1.2 and 3.1.4
`
`Data octets This field shall contain 19 octets of data
`
`new
`to 00000010 for
`Frame type The TYPE field is set
`to 00000011 for
`data frame and set
`retransmitted data
`frame
`
`When RLP frames are carried as primary traffic by Multiplex Option
`and 16
`format
`frame is defined as follows
`
`10 12 14
`
`Field
`
`SEQ
`
`Data
`
`TYPE
`
`Length bits
`
`248
`
`49
`
`10
`
`ii
`
`14
`
`13
`
`14
`
`15
`
`16
`
`18
`
`19
`
`20
`
`21
`
`22
`
`

`

`TIA/EIA/IS-707
`
`A.8
`
`SEQ
`
`Data
`
`TYPE
`
`Data frame sequence number See 3.1.2 and 3.1.4
`
`Data octets This field shall contain 31 octets of data
`
`new data
`Frame type The TYPE field is set to 000010 for
`frame and set to 000011 for
`retransmitted data frame
`
`4.3
`
`Idle Frames
`For Multiplex Option 13579 11 13 and 15 Rate 1/8 RLP frames are idle frames
`10 12 14 and 16 Rate 1/8 primary traffic RLP frames
`For Multiplex Option
`and Rate
`16 secondary traffic RLP frames may be idle frames Higher rate RLP data
`frames with zero length LEN
`see 4.2.1 are also idle frames
`
`Field
`
`SEQ
`
`FCS
`
`Padding
`
`SEQ
`
`FCS
`
`Length bits
`
`or
`
`Data frame sequence number See 3.1.2
`
`Frame Check Sequence based on modified
`Nordstrom-Robinson code
`
`Let the sequence number to be coded be denoted as
`
`AxAç
`
`Let the FCS be denoted as
`y7çy574y3y2y
`
`The FCS is generated as follows
`
`y0 x7ee
`xex.x ex2sxex5e
`
`Where
`denotes modulo
`addition Code bits
`are found by cyclically shifting AT0
`words
`is substituted
`
`for
`
`through
`In other
`
`through AT6
`in the generating
`
`parity bit over the previous 15 bits
`equation for V1
`V7 is
`The final step in generating the FCS is to complement
`the last
`three bits
`table specifying the code is provided in Table
`13
`
`4-10
`
`11
`
`12
`
`13
`
`14
`
`15
`
`16
`
`17
`
`18
`
`20
`
`21
`
`22
`
`23
`
`24
`
`26
`
`27
`
`28
`
`

`

`TIA/EJA/IS
`
`707 A.8
`
`Pad
`
`Padding bits As required to fill
`These bits shall be set to
`
`the remainder of the frame
`
`Table 13 presents the modified Nordstrom Robinson code used to protect Rate
`and
`Rate 1/16 idle frames In Table 13 the most significant byte in word is the SEQ value to
`be protected and the least significant byte is the FCS All numbers are hexadecimal
`
`4-11
`
`

`

`TIA/EJA/IS
`
`707-A.8
`
`Table 13 Modified Nordstrom Robinson Code
`
`0007
`01d4
`
`02a0
`034a
`04c9
`
`057f
`
`061c
`0793
`089a
`
`092c
`0a76
`
`Obf9
`
`0c31
`Ode2
`
`Oeaf
`
`0f45
`
`20f3
`2119
`226d
`
`23be
`242a
`25a5
`
`26c6
`2770
`2840
`
`29cf
`
`2a95
`2b23
`
`2cfc
`
`2d16
`2e5b
`
`2f88
`
`4Oee
`4161
`
`423b
`438d
`4452
`45b8
`
`46f5
`4726
`485d
`
`49b7
`
`4ac3
`4b10
`
`6034
`6182
`62d8
`
`6357
`
`649f
`
`654c
`6601
`67eb
`68a9
`
`697a
`6aOe
`6be4
`
`6c67
`4c84
`4dOb 6ddl
`4e68
`6eb2
`
`4fde
`
`6f3d
`
`70c5
`
`8078
`8lab
`
`82df
`
`8335
`84b6
`8500
`
`8663
`
`87ec
`88e5
`
`8953
`8a09
`8b86
`
`8c4e
`8d9d
`8edO
`
`8f3a
`
`aO8c
`a166
`
`a212
`
`a3cl
`a455
`
`asda
`a6b9
`
`a7Of
`
`a83f
`
`c091
`cue
`c244
`
`c3f2
`c42d
`
`c5c7
`
`c68a
`c759
`c822
`
`a9bO c9c8
`
`aaea
`absc
`
`ac83
`ad69
`
`ae24
`
`cabc
`
`cb6f
`ccl
`
`cd74
`
`cel7
`
`aff7
`
`cfal
`
`e04b
`
`elfd
`
`e2a7
`
`e328
`
`e4eO
`e533
`
`e67e
`e794
`e8d6
`
`e905
`
`ea7l
`eb9b
`
`ecl8
`
`edae
`
`eecd
`
`ef42
`
`fOba
`
`10
`
`11
`
`12
`
`13
`
`14
`
`16
`
`ii
`
`18
`
`19
`
`20
`
`lObd
`113Z
`
`1251
`
`13e7
`
`1464
`
`158e
`
`l6fa
`1729
`
`186b
`
`1981
`
`lacc
`
`lblf
`
`lcd7
`
`1d58
`
`1e02
`114
`
`305e
`31e8
`328b
`3304
`
`3490
`3543
`3637
`37dd
`
`38a6
`3975
`3a38
`3bd2
`3cOd
`
`3dbb
`
`3eel
`
`3f6e
`
`5008
`51db
`5296
`537c
`
`54a3
`5515
`
`564f
`
`57c0
`
`58f0
`5946
`5a25
`Sbaa
`
`5c3e
`Sded
`5e99
`
`5173
`
`712f
`7262
`73b1
`
`7479
`
`75f6
`
`76ac
`
`771a
`7813
`799c
`
`7aff
`7b49
`
`7cca
`7d20
`7e54
`
`7f87
`
`90c2
`914d
`922e
`9398
`
`941b
`
`95f1
`9685
`9756
`
`9814
`
`99fe
`9ab3
`9b60
`
`9ca8
`9d27
`9e7d
`
`9fcb
`
`b021
`b197
`
`b2f4
`b37b
`
`b4ef
`b53c
`b648
`b7a2
`
`b8d9
`b9Oa
`ba47
`bbad
`
`bc72
`bdc4
`
`be9e
`
`bfl
`
`d077
`dla4
`d2e9
`d303
`d4dc
`
`d56a
`d630
`
`d7bf
`
`d88f
`d939
`dasa
`dbd5
`
`dc4l
`
`dd92
`
`dee6
`
`dfoc
`
`f150
`
`f2ld
`
`f3ce
`
`f406
`
`f589
`
`f6d3
`
`1765
`
`f86c
`
`f9e3
`
`fa8O
`136
`
`fcbs
`
`fd5f
`
`fe2b
`
`fff8
`
`21
`
`22
`
`23
`
`24
`
`25
`
`26
`
`27
`
`23
`
`30
`
`31
`
`32
`
`ss
`
`34
`
`35
`
`4-12
`
`